Paul, Was running 2.5.4, Compiled and upgraded to 2.5.5 No crash this time, but it again failed on a (possibly open) logfile. There might be a hint there... Ran it again - no crash, same error... Verbose output was:
Trevors:~ # ./make_snapshot.sh umount: /dev/hdc1: not mounted building file list ... done ./ etc/ etc/mtab etc/ntp.drift var/log/ var/log/httpd/ var/log/httpd/access.combined.log rsync: error writing 4 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) Trevors:~ # ---second time snippet------- var/log/httpd/access.combined.log rsync: error writing 4 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) ---------------- I am not too comfortable using CRON to kill open rsync processes with the patch you suggested. Oh well. I will look at it later tonight. Thanks - at least it doesn't crash all processes now... Sincerely ..Trevor.. At 11:04 PM 9/8/2002 -0400, you wrote: >Looking at http://rsync.samba.org, we see under bug fixes for 2.5.5 > > Fix situation where failure to fork (e.g. because out of process > slots) would cause rsync to kill all processes owned by the > current user. Yes, really! (Paul Haas, Martin Pool) > >If rsync is running as root when it triggers this bug it will kill all >processes. This is indistinguishable from a system crash. Processes >running as root are allowed to shut down the system. So this is not a >Kernel bug. > >If you're still running 2.5.4, upgrade to 2.5.5. If you're running 2.5.5, >try replacing the calls to kill() with an fprintf() to a logfile. Then >manually kill any leftover rsync processes. > >-- >Paul Haas >[EMAIL PROTECTED] > > >-- >To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync >Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html > -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
