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!hermes.chpc.utexas.edu!xenon.brooks.af.mil!bsdns.brooks.af.mil!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: Re: Strange crond behaviour Date: 1 Aug 1993 16:00:37 -0500 Organization: Armstrong Laboratory, Brooks AFB, TX Lines: 23 Message-ID: <23hau3$mrb@hrd769.brooks.af.mil> References: <239cqr$r43@hrd769.brooks.af.mil> NNTP-Posting-Host: hrd769.brooks.af.mil In article <239cqr$r43@hrd769.brooks.af.mil> burgess@hrd769.brooks.af.mil (Dave Burgess) writes: > >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. > I found a culprit for this after following up a hunch I had the other evening, reading a different newsgroup. I changed the default shell for crond from /bin/sh to /bin/bash. Apparently, the /bin/sh we are using (ash) is having a little trouble from the crond job's interface. All of the arguments are being passed to sh as the first argument, and are being processed as if they were the program name. By adding the line SHELL=/bin/bash at the top of my crontab, my dailies and sups are running flawlessly. -- ------ TSgt Dave Burgess NCOIC AL/Management Information Systems Office Brooks AFB, TX