Path: utzoo!attcan!uunet!olivea!samsung!caen!ox.com!emv From: vixie@decwrl.dec.com (Paul A Vixie) Newsgroups: comp.archives Subject: [perl] Re: lossage running perl script from crontab Message-ID: <1991Mar2.194757.22655@ox.com> Date: 2 Mar 91 19:47:57 GMT References: <1991Feb28.193638.4002@uvaarpa.Virginia.EDU> <1991Feb28.212358.342@porthos.cc.bellcore.com> <1991Feb28.233630.21142@convex.com> Sender: emv@ox.com (Edward Vielmetti) Reply-To: vixie@decwrl.dec.com (Paul A Vixie) Followup-To: comp.lang.perl Organization: DEC Western Research Lab Lines: 21 Approved: emv@ox.com (Edward Vielmetti) X-Original-Newsgroups: comp.lang.perl Archive-name: unix/admin/vixie-cron/1991-03-01 Archive: gatekeeper.dec.com:/pub/misc/vixie/cron2.tar.Z [16.1.0.2] Original-posting-by: vixie@decwrl.dec.com (Paul A Vixie) Original-subject: Re: lossage running perl script from crontab Reposted-by: emv@ox.com (Edward Vielmetti) >> BTW, *MY* cron lets me set its path. I think they all should. Who cares? *MY* cron is in the public domain. Get it from a comp.sources.unix archive site near you. Or get it from gatekeeper.dec.com via prospero or anonftp. Or wait for 4.4BSD. A cron that doesn't let you set its path, will not send you mail if your commands generate output, and will not let each user have their own crontab, is, well, it's not my version, whatever it is. Cheers, -- Paul Vixie DEC Western Research Lab Palo Alto, California ...!decwrl!vixie