>
Hi,
I am using dirvish to backup various machines in
my local network. It works pretty well. But sometimes the dirvish
process will give a RC=139 or RC=145 back, and I am trying to debug
that, still. I ping the target machines to check they are up before
attempting the backup on each machine.
I am running dirvish on an NSLU2 with USB disk connected.
Anyway someone answered me that (and I missed it, ashamed to say)
that any Dirvish RC over 128 is caused by a signal. So 139 would be
signal 11 and 145 would be signal 17. As dirvish just calls rsync I
assume it must be rsync that is dying, or being killed somehow. So
sig11 is a segmentation fault, that must be internal from rsync. sig17
is sigstop, will that be from something external to rsync?
Anyway if I start a backup then just kill (-9) rsync on the dirvish
machine, I get a RC=0 from dirvish. The tree is then only partially
filled, files and directories missing etc.
The summary file ends with "Status: Success", the log file ends with the
file name of a large file that was new, so it had to be transfered.
So, is it correct that I get an RC=0 from dirvish, for this?
How can I get more debugging output, only via the rsync options?
Cheers Brian
_______________________________________________
Dirvish mailing list
[email protected]
http://www.dirvish.org/mailman/listinfo/dirvish
