Something to check on - make sure that the PATH that cron is using has rsync
on it! Specifically, make sure that it's the _right_ rsync command. The
idiots at SGI decided to name some command of theirs dealing with RCS
"rsync", despite the _real_ rsync command having existed long before anyone
at SGI was doing anything with RCS... I've now put in a check for the exit
status of rsync in the server's smoke.sh here:
/usr/share/bin/rsync -avz --delete rsync://ftp.linux.activestate.com/perl-current/
"$BASE" || exit $?
along with explicitly specifying the path, and similar ones for copying from
one machine to another. As it was, one of our machines was repeatedly
testing some patchlevel in the early 178**s!
-Allen
--
Allen Smith http://cesario.rutgers.edu/easmith/
September 11, 2001 A Day That Shall Live In Infamy II
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." - Benjamin Franklin
