JW,
I pushed everything to a LINUX box and did the diff again this time with the
-bur option.
It does look significantly different. I think I've got below what you are
looking for, so I am
resending it to [EMAIL PROTECTED]
I'm including two additional people as they have asked for the patch in
To Whom It May Concern:
Below is a patch, that I have used to eliminate the unexplained
errors in the rsync program. I was able to trace the problem to
the order in which the sigchld_handler and wait_process routines
were executed. If sigchld_handler executes first it retrieves
the status that
JW,
Sorry for p*ssing you off, that was not my intention.
I looked at the archives and saw no resolution to this specific problem in
any of the rsync-2.5.3-NEWS, rsync-2.5.4-NEWS or rsync-2.5.5-NEWS files.
I am somewhat new to the *NIX environment and don't yet understand all
the tools or prot
