Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!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.questions Subject: Strange crond behaviour Date: 29 Jul 1993 15:43:57 -0500 Organization: Armstrong Laboratory, Brooks AFB, TX Lines: 28 Message-ID: <239cqr$r43@hrd769.brooks.af.mil> NNTP-Posting-Host: hrd769.brooks.af.mil I have been playing around with NetBSD for a few months now, and I have done something to cron that I cannot figure out. Whenever anyone in the system (with one exception) uses cron, the jobs run and the output is produced. All jobs are happy, and everything seems to work fine. The one exception is root: Whenever root runs a cron task (/etc/daily, sup, it doesn't make any difference), the resulting mail is always the same: X-Cron-Cmd: </usr/local/bin/sup -sv> X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <USER=root> /usr/local/bin/sup -sv: No such file or directory - - - There it is. Crond is running from the rc file and seems to work flawlessly for all other users. It was working all right until the 28th of June, when it suddenly started this. Can anyone suggest what might be causing this behaviour? -- ------ TSgt Dave Burgess NCOIC AL/Management Information Systems Office Brooks AFB, TX