>I often post them to the mailing list, but the best place to find fixes
>is in the CVS version. (This fix has been in CVS since early May, for
>instance.) See the "NEWS" file from CVS for a good summary of what has
>changed.
Ok. Many thanks again!
Bye, Andy
--
Andreas Ley, Rechenzentrum, Uni
On Tue, May 18, 2004 at 10:26:23AM +0200, Andreas Ley wrote:
> Bingo! This patch indeed fixes the problem. Is this an 'official' patch and
> is there an 'official' place to look for patches to released versions?
I often post them to the mailing list, but the best place to find fixes
is in the CVS
>http://lists.samba.org/archive/rsync/2004-May/009380.html
Bingo! This patch indeed fixes the problem. Is this an 'official' patch and
is there an 'official' place to look for patches to released versions?
Many thnx, Andy
--
Andreas Ley, Rechenzentrum, Universitaet Karlsruhe, D-76128 Karlsruhe,
On Mon, May 17, 2004 at 09:22:14AM -0700, Wayne Davison wrote:
> On Mon, May 17, 2004 at 04:45:21PM +0200, Andreas Ley wrote:
> > #0 0x400a46d9 in strncmp () from /lib/libc.so.6
>
> That looks like the segfault I fixed [that affected] 2.6.1.
No, that's not right. I'm mis-remembering when that c
Andreas Ley wrote:
I haven't been able to duplicate the crash you two are seeing, so if
either of you can send me a backtrace of the crash (either from a core
dump or by doing some creative gdb attaching), I'd appreciate it.
I didn't get a core, but suceeded tu run gdbserver:
#0 0x400a46d9 in str
On Mon, May 17, 2004 at 04:45:21PM +0200, Andreas Ley wrote:
> #0 0x400a46d9 in strncmp () from /lib/libc.so.6
That looks like the segfault I fixed in 2.6.1. I looked back at your
original message, and it looks like I misread ">= 2.6.1" as "> 2.6.1".
If you're using 2.6.1, please upgrade to 2.6.
>I haven't been able to duplicate the crash you two are seeing, so if
>either of you can send me a backtrace of the crash (either from a core
>dump or by doing some creative gdb attaching), I'd appreciate it.
I didn't get a core, but suceeded tu run gdbserver:
#0 0x400a46d9 in strncmp () from /l
On Fri, May 14, 2004 at 04:56:47PM +0200, Andreas Ley wrote:
> I get a SEGFAULT.
I haven't been able to duplicate the crash you two are seeing, so if
either of you can send me a backtrace of the crash (either from a core
dump or by doing some creative gdb attaching), I'd appreciate it.
..wayne..
Andreas Ley wrote:
The two machines are Debian stable with kernel 2.4.26.
I'm running rsync even on a single box, or through ssh between 2 boxes.
Both are linux-2.6.6.
Hope this helps finding the bug. Can I provide more information or run more
tests?
we are on the same bug ! that's sure.
--
Bapt
Hi!
I seem to have a similar problem. I checked different versions and options,
and it seems to happen when the server version is >= 2.6.1 - there's no
problem with 2.6.0. The client version doesn't matter. The --delete option
is required to show the bug. The two directories may well be uptodate a
I have this failing every times I want to "update" the "destination".
I've tried through SSH (from my box -/home is a NFS mount point here- to
the backup one) or directly through "local transport" (because /home/ is
a local RAID-5 mount point on the backup box).
$ rsync -v -e /usr/bin/ssh -ax -
11 matches
Mail list logo