On Tue, Mar 11, 2008 at 03:00:25PM +0100, Giuliano Gavazzi wrote:
> rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
This just tells you that the receiver side went away, but we don't know
why it went away. If it is crashing, try to get a core dump and report
the back
rsync 3.0.0. MacOSX 10.5.1 Server/Intel.
Trying to detect files with funny chars in their name, as I cannot
find them with "find", I use the error (Illegal byte sequence) given
by rsync when the target charset cannot reproduce them.
While doing this I have met this error:
/usr/local/bin/rsy
