On Tue, Dec 11, 2001 at 04:52:31PM -0500, Mark de Jong wrote:
> Hello,
> When using rsync with the -z option for compression, I get "Bit Length
> Overflow" errors during the transfer of files. The errors are sporatic
> and don't seem to have any type of pattern. Is t
Title: Message
Hello,
When using rsync
with the -z option for compression, I get "Bit Length Overflow" errors during
the transfer of files. The errors are sporatic and don't seem to have any type
of pattern. Is this something I should be concerned about?
Example:
bit lengt
I'm getting messages that look like this:
bit length overflow
code 6 bits 6->7
in rsync-2.5.1pre3 (and in 2.4.7pre4)
Is that an error, or a piece of verbose logging? the return code was zero,
which makes me think that everything's okay.
--
Daniel Sadinoff, Goldman, Sac
Martin Pool wrote:
>
> On 30 Nov 2001, Thomas J Pinkl <[EMAIL PROTECTED]> wrote:
> > I'm seeing:
> >
> > bit length overflow
> > code 4 bits 6->7
> >
> > in the output of rsync 2.5.0 between two Red Hat Linux systems.
> > One is
On 30 Nov 2001, Thomas J Pinkl <[EMAIL PROTECTED]> wrote:
> I'm seeing:
>
> bit length overflow
> code 4 bits 6->7
>
> in the output of rsync 2.5.0 between two Red Hat Linux systems.
> One is RH 6.1 (kernel 2.2.19-6.2.1, glibc 2.1.3-22), the other
> i
2.5.0 -- thanks for doing the new release with all the fixes. It appears
to be working fine.
I'm seeing a 'bit length overflow' warning to STDERR. (with -vv) It
doesn't appear to be an error -- zlib/trees.c seems to indicate that
this is a situation that is properly h
I'm seeing:
bit length overflow
code 4 bits 6->7
in the output of rsync 2.5.0 between two Red Hat Linux systems.
One is RH 6.1 (kernel 2.2.19-6.2.1, glibc 2.1.3-22), the other
is RH 7.2 (kernel 2.4.9-13, glibc 2.2.4-19). Both systems have
rsync 2.5.0.
On the RH 6.1 box, I
