Just guessing, here, but it's probably not finding rsync in the
path (/usr/local/bin/rsync or whatever). Cron usually assumes
no path info.
I would include full pathnames and use the --rsync-path= options
and log it to a file instead of /dev/null so you'd have something
better to go on if it pukes again.
-b
Bill Williams
Sr. Systems Administrator
Cisco Systems, Inc.
-->-----Original Message-----
-->From: Demicco, Matthew [mailto:[EMAIL PROTECTED]]
-->Sent: Wednesday, June 14, 2000 11:11 AM
-->To: Multiple recipients of list RSYNC
-->Subject: Rsync from Cron
-->
-->
-->In a Bourne Shell script, I'm issuing the following rsync command:
-->
-->if `rsync -e ssh $HOST:/usr/local/bds/etc/families/$i
-->$FAMILYDIR/`; then
-->
-->This works fine if I call the script from the command line, but fails
-->instantly when called from a cron job. I tried both:
-->
-->4 * * * * /myscript
-->and
-->4 * * * * /myscript >/dev/null 2>&1
-->
-->But I'm not getting any indication of why it's failing. Any
-->ideas? Thanks!
-->(BTW I looked at the FAQ, I'm not using --daemon, and even
-->so I've tried
-->that suggestion)
-->
-->---
-->Matthew R. Demicco
-->Taos Unix SysAdmin
-->
