Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!usc!cs.utexas.edu!natinst.com!hrd769.brooks.af.mil!hrd769.brooks.af.mil!not-for-mail From: burgess@hrd769.brooks.af.mil (Dave Burgess) Newsgroups: comp.os.386bsd.bugs Subject: Re: Problems with new execle() in NetBSD 0.9 Date: 10 Sep 1993 09:17:07 -0500 Organization: Armstrong Laboratory, Brooks AFB, TX Lines: 33 Message-ID: <26q29h$42a@hrd769.brooks.af.mil> References: <26l67i$6qs@hrd769.brooks.af.mil> <26o88r$heb@pessoa.ecs.soton.ac.uk> NNTP-Posting-Host: hrd769.brooks.af.mil In article <26o88r$heb@pessoa.ecs.soton.ac.uk> rsk@ecs.soton.ac.uk (Bob Kemp) writes: >In <26l67i$6qs@hrd769.brooks.af.mil> burgess@hrd769.brooks.af.mil (Dave Burgess) writes: > >>/usr/bin/finger nasanews@space.mit.edu > /etc/nasanews: No such file or directory >O > >I've been getting this message from crond too but _only_ for root's crontab. >In my own (non-root) crontab arguments to commands work fine. >I agree that the shell used seems to be irrelevant. > >Presumably it is either crond or the exec code? > >Bob > Chris E-Mailed me and reminded me that the exec*() code has not changed in recent history. It probably isn't that. If it only happens in the 'root' crontab, that would pretty effectively tell me that it isn't exec*(). There is a block of code in do_command.c in crond/ that does some special processing for the root crontab. Since the problem appears to be solely in the root crontab, it is reasonable to assume that is broken in that section. My next suspect will be the stat() function... I will keep on it and see if I can fix it. -- ------ TSgt Dave Burgess NCOIC AL/Management Information Systems Office Brooks AFB, TX