https://bugzilla.samba.org/show_bug.cgi?id=4856
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
Fri, 3 Aug 2007 15:06:51 -0400, hashproduct+rsync wrote:
> No, that's just another SIGPIPE. There are a total of three rsync
> processes, forked in the following pattern:
>
> sender
> \_ generator
> \_ receiver
>
> Your first backtrace was for the sender. Setting gdb to always follow
> t
On 8/3/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Thanks. Now gdb's output it might be more useful?
>
> (gdb) show follow-fork-mode
> Debugger response to a program call of fork or vfork is "parent".
> (gdb) set follow-fork-mode child
> (gdb) show follow-fork-mode
> Debugger response to a p
Fri, 3 Aug 2007 11:48:02 +0200, paul wrote:
> On Fri 03 Aug 2007, [EMAIL PROTECTED] wrote:
> >
> > I understand, but I have no idea how I can solve this problem.
> >
> > Is rsync starting a second rsync instance?
>
> Yes.
>
> http://www.delorie.com/gnu/docs/gdb/gdb_26.html may help.
Thanks. Now g
On 8/3/07, Paul Slootman <[EMAIL PROTECTED]> wrote:
> On Fri 03 Aug 2007, [EMAIL PROTECTED] wrote:
>
> > Program received signal SIGPIPE, Broken pipe.
> > 0xe410 in __kernel_vsyscall ()
>
> Unfortunately this means you were not tracing the process that failed;
> you were tracing the process tha
https://bugzilla.samba.org/show_bug.cgi?id=4856
--- Comment #1 from [EMAIL PROTECTED] 2007-08-03 10:46 CST ---
Rsync always outputs the filename to the console before the transfer to inform
the user of what file it is working on. If you specify a log file with
--log-file=FILE , rsyn
Rather than waiting for the ignore case patch to be added to the
standard rsync,
One big reason I pinged the list (and you and Wayne) is to be the
'squeaky wheel' - I'm hoping this doesn't fall through the cracks and
actually does make it into the 3.0 release... otherwise, I'll have to
keep b
On Fri 03 Aug 2007, [EMAIL PROTECTED] wrote:
> Program received signal SIGPIPE, Broken pipe.
> 0xe410 in __kernel_vsyscall ()
Unfortunately this means you were not tracing the process that failed;
you were tracing the process that forked another process and got a
SIGPIPE when trying to write
Fri, 3 Aug 2007 10:10:30 +0200, paul wrote:
> On Fri 03 Aug 2007, Sven wrote:
> >
> > Yes, the cvs version from 20070803T08 started very modestly in terms of RAM,
> > but after some minutes:
> > > rsync -a --progress -v /c/ /data/c (source is mounted via nfs)
> > ...
> > ces/002495.ces
> >
https://bugzilla.samba.org/show_bug.cgi?id=4856
Summary: Filenames are displayed before successful transfer in
verbose mode
Product: rsync
Version: 2.5.7
Platform: All
OS/Version: Linux
Status: NEW
Severit
On Fri 03 Aug 2007, [EMAIL PROTECTED] wrote:
>
> Yes, the cvs version from 20070803T08 started very modestly in terms of RAM,
> but after some minutes:
> > rsync -a --progress -v /c/ /data/c (source is mounted via nfs)
> ...
> ces/002495.ces
> 105851 100% 859.88kB/s0:00:00 (xfer#23, t
Thu, 2 Aug 2007 16:52:53 +0200, paul wrote:
> On Thu 02 Aug 2007, Sven wrote:
> >
> > I once tried to rsync around 100 GB (10 million files), but version
> > 2.6.6 needed too much RAM and was too slow.
>
> I believe 2.6.7 had a number of memory-saving options; each subsequent
> version will of cour
12 matches
Mail list logo
