Date: Wed, 12 Oct 2005 16:59:03 +0100 From: RW <list-freebsd-2004@morbius.sent.com> To: freebsd-questions@freebsd.org Subject: Re: portmanager Message-ID: <200510121659.05550.list-freebsd-2004@morbius.sent.com> In-Reply-To: <434B9883.3000108@speechpro.com> References: <fa8f05950510091227s136767e2w@mail.gmail.com> <20051010054556.BB30.GERARD@seibercom.net> <434B9883.3000108@speechpro.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 11 October 2005 11:48, Igor Robul wrote: > Gerard Seibert wrote: > >***** REPLY SEPARATOR ***** > >On 10/10/2005 5:45:56 AM, Gerard Seibert Replied: > > > >Would it be possible to issue a $PATH statement from within the CRON to > >alleviate this problem? I have not actually tried this method, but I do > >use it for other programs that I run from CRON and it seems to works > >just fine. > > You can always add shell script wrapper, which sets PATH. This way you > can avoid adding functions to cron. I'm probably missing something, because I can't see what the problem is. crontab(5) says you can define environmental variables in a crontab; and the default system crontab already has a PATH variable pre-defined, although it doesn't include /usr/local/bin in the path.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510121659.05550.list-freebsd-2004>