David Birnbaum davidb at
Wed Feb 6 03:28:54 EST 2002

I suspected that might be the to determine the "real"
problem?  Does rsync log it somewhere?  lsof shows that STDERR/STDOUT are
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?




On Tue, 5 Feb 2002, Dave Dykstra wrote:

> On Mon, Feb 04, 2002 at 12:24:02PM -0500, David Birnbaum wrote:
> > Howdy,
> >
> > We occassionally get the following error when running our nightly
> > backups:
> >
> >   rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
> >
> > This happens more on one or two machines than on any of the others.  We've
> > looked high and low to see if we're mistakenly sending these signals, but
> > nothing is that we can find.
> >
> > Does anyone know what this might be from?  Is it the server or the client
> > that's complaining about the signal?
> The side of rsync that receives files forks into two processes, and one
> sends the other a SIGUSR1 when it experiences a problem.  So this is
> probably a symptom of your real problem, not the real problem.
> - Dave Dykstra

More information about the rsync mailing list