Re: error writing 4 unbuffered bytes - exiting: Broken pipe

2004-03-10 Thread Paul Slootman
On Mon 08 Mar 2004, Nepple, Bruce wrote: > > (BTW, I hate bottom posting but do it out of deference to the > handicapped weirdos that like to scroll > through lots of useless information to get to the useful stuff > and can't seem to deal with a backwards history) If there's "lots of useless inf

RE: error writing 4 unbuffered bytes - exiting: Broken pipe

2004-03-08 Thread Nepple, Bruce
sync -rluRtpPv --delete /net/moe/bne/* /net/burns/bne_old/ > | tee rsync_report2 > > I then get this: > > rsync: error writing 4 unbuffered bytes - exiting: Broken pipe > rsync error: error in rsync protocol data stream (code 12) at > io.c(463) > rsync: error writing 69 un

FW: error writing 4 unbuffered bytes - exiting: Broken pipe

2004-03-08 Thread Nepple, Bruce
t this: rsync: error writing 4 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) rsync: error writing 69 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) I searched the

error writing 4 unbuffered bytes - exiting: Broken pipe

2004-03-08 Thread Nepple, Bruce
t this: rsync: error writing 4 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) rsync: error writing 69 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) I searched the gmane