tim.conway at tim.conway at
Thu Feb 7 04:39:03 EST 2002

When i was getting these, I traced the process and its children (solaris: 
truss -f).  I found that one of the spawned threads was experiencing an io 
timeout while the filelist was building.  I had set no timeout, but it did 
it at 60 seconds every time.  I found that this corresponded to a 
SELECT_TIMEOUT parameter, which was set to 60 if IO_TIMEOUT was 0.  BY 
setting my timeout to 86400 (1 day), i stopped those.  Of course, then, it 
choked farther along, but that's another story.
Try setting a timeout, even if you don't want one.  Make it the longest 
the process should ever take.

Tim Conway
tim.conway at
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn, 
".\n" '
"There are some who call me.... Tim?"

Dave Dykstra <dwd at>
Sent by: rsync-admin at
02/06/2002 10:16 AM

        To:     David Birnbaum <davidb at>
        cc:     rsync at
(bcc: Tim Conway/LMT/SC/PHILIPS)
        Subject:        Re: SIGUSR1 or SIGINT error

On Tue, Feb 05, 2002 at 11:28:54AM -0500, David Birnbaum wrote:
> I suspected that might be the to determine the "real"
> problem?  Does rsync log it somewhere?  lsof shows that STDERR/STDOUT 
> going to /dev/null, so I hope it's not writing it there.  Nothing
> informative in syslog, just the message about the SIG:
>   Feb  5 09:49:41 hite rsyncd[9279]: [ID 702911 daemon.warning] rsync 
error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
> Any clues?

I'm sorry, but I don't have any more suggestions.

- Dave Dykstra

More information about the rsync mailing list