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. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
