writefd_unbuffered failed to write 4 bytes
ramkumar.santoshi at gmail.com
Fri May 2 02:38:12 GMT 2008
I'm pretty sure i grabbed the one from the build dir. Is there any way i
On Thu, May 1, 2008 at 12:17 AM, Wayne Davison <wayned at samba.org> wrote:
> On Tue, Apr 29, 2008 at 10:05:07AM +1000, Ramkumar Santoshi wrote:
> > On Mac OS10.4, using rsync 3.0, it stops during a transfer.
> That's an incomplete version. The last release was 3.0.2.
> > 2008/04/28 20:48:46  rsync: writefd_unbuffered failed to write 4
> bytes [sender]: Broken pipe (32)
> That just tells you that the receiver went away. Run a version of rsync
> that does not have the debug symbols stripped out (i.e. use the binary
> in the build dir, not the one that is installed), enable core dumps (use
> "ulimit -c unlimited"), and use a debugger on the core dump to get a
> backtrace ("gdb /build/dir/rsync core" followed by "bt"). Then, please
> let me know where it crashed.
> > Also, what's the characters mean in the logfile, such as:
> > >f..tpog.... RAID_One/data/file
> > 8.39M 100% 4.12MB/s 0:00:01 (xfer#3478, to-check=1224/8633)
> See the --itemize-changes option and the --progress option.
-------------- next part --------------
HTML attachment scrubbed and removed
More information about the rsync