rsync 2.5.5 segmentation fault on Linux x86.

tim.conway at tim.conway at
Wed Oct 2 17:51:01 EST 2002

stdin may be closed, or may appear to be a socket, fifo, pipe, or file, 
probably some stuff i don't know about.  I remember rsync used to look at 
something in stdio, and act as if it were invoked with --daemon, even 
without that flag.  Somebody'll correct the details.  I just know that I 
have had, in the past, applications that didn't run in cron without < > 
and 2>.

Tim Conway
conway.tim at reorder name and reverse domain
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me.... Tim?"

Erik Enge <eenge at>
Sent by: rsync-admin at
10/01/2002 02:10 PM

        To:     Tim Conway/LMT/SC/PHILIPS at AMEC
        cc:     rsync at
        Subject:        Re: rsync 2.5.5 segmentation fault on Linux x86.

tim.conway at writes:

> Erik: One more thing to try: redirect in /dev/null to the rsync
> command. At one time, at least, its behaviour was different based on
> the nature of its STDIN.  Make sure STDERR and STDIN are redirected
> somewhere, too... either a file or null.

All our output are redirected to a file.  What would STDIN for a cronjob
be?  Somehow that doesn't seem to make sense.

Thanks for your response,

To unsubscribe or change options:
Before posting, read:

More information about the rsync mailing list