Date: Thu, 13 Aug 1998 13:11:00 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: Roman Katsnelson <romank@graphnet.com> Cc: "q's" <freebsd-questions@FreeBSD.ORG> Subject: Re: Cron daemon question Message-ID: <Pine.BSF.4.00.9808131310390.11633-100000@resnet.uoregon.edu> In-Reply-To: <35D1FCD8.AA09BFEF@graphnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Aug 1998, Roman Katsnelson wrote: > I have a little piece of code sitting in /usr/local/bin/stuff > directory... This code involves something like this, for example: > > cd morestuff #should now be in /usr/local/bin/stuff/morestuff > > do whatever, then exit > > When I run it command line, it works. > I made a crontab that calls it, and the cron daemon mailed me this: > > cd: morestuff: No such file or directory > > The crontab calls the code as /usr/local/bin/stuff/code.sh > > Should I change the code to make it do absolute paths? I'd rather not, > if there were a way around it, but if that's one of the crontab > requirements then I guess I will... Use absolute paths. Cron's starting directory is undefined. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.00.9808131310390.11633-100000>