This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: cron job don't work correct
Larry Hall (Cygwin) wrote:
>
>>
>
> Typically the variables that matter are those that affect how commands
> you've
> given are found, like PATH. It's rare to require access to allot of other
> environment variables for proper running and certainly it's buggy to build
> your own scripts that rely too much on environment variables. Obviously,
> if
> you do need some set, include them in the script that cron will run. But
> you are better off providing full paths to executables in your cron
> scripts,
> as Igor notes, and going without all the added complication of setting
> PATH.
> If you have special needs to set variables, then the variables involved
> are likely to be either immediately obvious or self-evident after
> reviewing
> the man/info page for the utilities in use.
>
>
> --
> Larry Hall http://www.rfk.com
> RFK Partners, Inc. (508) 893-9779 - RFK Office
> 216 Dalton Rd. (508) 893-9889 - FAX
> Holliston, MA 01746
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Problem reports: http://cygwin.com/problems.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
>
>
Hi guys,
thanks for the help. I add the environment variables "SHELL=/bin/bash" and
"PATH=/bin:/etc:/usr/sbin" directly in my crontab file. Now it works fine.
Todde
--
View this message in context: http://www.nabble.com/cron-job-don%27t-work-correct-tf2201821.html#a6185165
Sent from the Cygwin Users forum at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/