Path: utzoo!attcan!uunet!bellcore!porthos!chaucer!rdm2 From: rdm2@chaucer.uucp (25362-roe mcburnett(H053)m000) Newsgroups: comp.lang.perl Subject: Re: lossage running perl script from crontab Message-ID: <1991Mar1.143125.29226@porthos.cc.bellcore.com> Date: 1 Mar 91 14:31:25 GMT References: <1991Feb28.193638.4002@uvaarpa.Virginia.EDU> <1991Feb28.212358.342@porthos.cc.bellcore.com> <1991Feb28.233630.21142@convex.com> Sender: netnews@porthos.cc.bellcore.com (USENET System Software) Reply-To: rdm2@chaucer.UUCP (25362-roe mcburnett) Organization: Bell Communications Research Lines: 32 In article <1991Feb28.233630.21142@convex.com> tchrist@convex.COM (Tom Christiansen) writes: >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: >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 > Tom Christiansen tchrist@convex.com convex!tchrist Yes Tom, You are quite correct. I was using ksh to get a good path. On some of the systems I work on cron lets me set the path, or automatically uses my login .profile to setup one. This is why I just executed ksh, because the cron would know that *I* setup the crontab for me, and would use my .profile (which would setup the path just fine). I also think that they all should work this way. But unfortunately some of us are stuck with systems that are old and clunky. (on some systems that I support the only OS available is u*ix V.2 where the old cron stuff reigns supreme) Thanks for the clarification -Roe Roe D McBurnett III Bellcore (908)699-2273 rdm2@chaucer.cc.bellcore.com #insert