Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!convex!news
From: tchrist@convex.COM (Tom Christiansen)
Newsgroups: comp.lang.perl
Subject: Re: lossage running perl script from crontab
Message-ID: <1991Feb28.233630.21142@convex.com>
Date: 28 Feb 91 23:36:30 GMT
References: <1991Feb28.193638.4002@uvaarpa.Virginia.EDU> <1991Feb28.212358.342@porthos.cc.bellcore.com>
Sender: news@convex.com (news access account)
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Software Development, Richardson, TX
Lines: 21
Nntp-Posting-Host: pixel.convex.com

From the keyboard of rdm2@chaucer.UUCP (25362-roe mcburnett):
:Remember,  cron uses sh (not ksh not csh) to run its commands.  You
:might get better results by using the following:
:
:0,5,10,15,20,25,30,35,40,45,50,55 * * * * ksh /usr/local/bin/perl  /usr/local/bin/cron_ping

don't you mean:

    ksh -c '/usr/local/bin/perl  /usr/local/bin/cron_ping'

right?  and you're just calling ksh to get a good path, right?
might as well just put it in the cron_ping thing.  

BTW, *MY* cron lets me set its path.  I think they all should.

--tom
--
"UNIX was not designed to stop you from doing stupid things, because
 that would also stop you from doing clever things." -- Doug Gwyn

 Tom Christiansen                tchrist@convex.com      convex!tchrist