Displaying 3 results from an estimated 3 matches for "trevormarshall".
2002 Sep 09
4
Hardware - no way -Re: Crashes maybe due to: "error writing 4 unbuffered bytes"
...en+pipe%22&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=aemsfq%24894%
241%40FreeBSD.csie.NCTU.edu.tw&rnum=1
Oh - except he was Running Red Hat linux - so don't go blaming SuSe.
Appreciate you trying to help, but I didn't come down in the last
rain-shower :-)
Trevor
http://www.TrevorMarshall.com
>If running rsync crashes your (non-MS) server you have a
>problem with the server, not rsync. On a linux system
>application caused system crashes are either bad hardware or
>kernel bugs.
>
>Unless you have tweaked out SuSE i would say you have a
>hardware problem. Rsyn...
2002 Sep 08
2
Crashes maybe due to: "error writing 4 unbuffered bytes"
...or writing 70 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(464)
A search of Google Usenet showed two identical incidents in June 2002.
Is there any hope of my resolving this without too many more crashes?
Sincerely,
Trevor
http://www.TrevorMarshall.com
2002 Oct 01
4
rsync 2.5.5 segmentation fault on Linux x86.
Hi all.
I have a script which I call from cron. It basically does some stopping
of a few services, rsyncs all files to a remote server and then starts
the services again. However, rsync segfaults:
/share/bin/cron.root.backup.sh: line 28: 18453 Segmentation fault rsync -acx --delete ${_backup_dirs} backup-server::backup-client
If I run rsync from the command-line everything works as