On Fri 13 Sep 2002 14:42, "Allen Smith" <[EMAIL PROTECTED]> wrote:
> 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!
HP-UX:
l1:/u/usr/merijn 101 > path -al patch
279 100555 -r-x 1 bin 53248 17 Mar 2000 13:11 /usr/bin/patch
l1:/u/usr/merijn 102 > path -al npatch
18217 100777 -rwx 1 merijn 106496 15 Oct 2001 17:31 /pro/local/bin/npatch
l1:/u/usr/merijn 103 >
That's why I had to rename the *useful* patch command to npatch :P
--
H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using perl-5.6.1, 5.8.0 & 633 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
WinNT 4, Win2K pro & WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED]
http:[EMAIL PROTECTED]/ [EMAIL PROTECTED]
send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
