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 [EMAIL PROTECTED] 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 <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 10/01/2002 02:10 PM To: Tim Conway/LMT/SC/PHILIPS@AMEC cc: [EMAIL PROTECTED] Subject: Re: rsync 2.5.5 segmentation fault on Linux x86. Classification: [EMAIL PROTECTED] 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, Erik. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html