Path: utzoo!attcan!uunet!decwrl!bacchus.pa.dec.com!vixie From: vixie@wrl.dec.com (Paul Vixie) Newsgroups: comp.lang.perl Subject: Re: Questions about exec and scripts called from cron Message-ID: <1990Oct4.064946.25547@wrl.dec.com> Date: 4 Oct 90 06:49:46 GMT References: <1180002@hpcc01.HP.COM> <1180004@hpcc01.HP.COM> Sender: news@wrl.dec.com (News) Organization: DEC Western Research Lab Lines: 18 # > Cron could conceivably be feeding the text above to /bin/sh through # > stdin, in which case $0 isn't going to be meaningful, and you'd # > probably try to execute the first argument of $*. # # I suspect this is exactly what is happening. Perhaps cron checks the # file type and only force-feeds through sh if it isn't a legitimate # executable? Sounds fishy, and stupid, which means that cron is probably doing it. I recommend use of my cron, which can be had from gatekeeper.dec.com's anonymous FTP, in /pub/misc/vixie. This is the released 2.0 version, which was due in comp.sources.unix last month and may appear in 4.4bsd whenever that comes out. -- Paul Vixie DEC Western Research Lab Palo Alto, California ...!decwrl!vixie