Write failed flushing stdout buffer.
Daniel
daniel at netwalk.org
Tue Jan 29 04:44:37 EST 2002
ssh get's used by default when I don't specify otherwise.
I'm using rsync version 2.5.2 protocol version 26
on FreeBSD on both machines, currently.
Any ideas? I tried implicitly using --rsh=/usr/bin/ssh which doesn't work
either.
Somtimes I get this error:
send_files failed to open upd: Permission denied
wrote 48 bytes read 213358 bytes 14717.66 bytes/sec
total size is 420008408 speedup is 1968.12
Write failed flushing stdout buffer.
write stdout: Broken pipe
Daniel
On Mon, 28 Jan 2002, Dave Dykstra wrote:
> On Sun, Jan 27, 2002 at 01:45:10PM -0500, lists at debonair.net wrote:
> > 3 100% 0.00kB/s 0:00:00
> > wrote 30496 bytes read 327051 bytes 14593.76 bytes/sec
> > total size is 419896352 speedup is 1174.38
> > Write failed flushing stdout buffer.
> > write stdout: Broken pipe
> >
> > time /usr/local/bin/rsync -avzP host: /bkup-zone --delete
> >
> > this is the command which is being run, and I get the above error message
> > everytime. The phenomenon doesn't happen when just copying certain
> > directories, but only when I do the full backup (size approx 126M).
> >
> > rsync version 2.5.1 protocol version 25
> >
> > help appriciated, i've checked everywhere for answers.
> >
> > Daniel
> >
>
> There's no string "Write failed" in rsync 2.5.1 source so that message
> must be coming from rsh. Is it rsync 2.5.1 on both sides? What operating
> systems?
>
> - Dave Dykstra
>
>
Please Note: No trees were destroyed in the sending of this contaminant free
message. However, a signicant number of electrons may have been inconvenienced.
More information about the rsync
mailing list