X-Spam-Check-By: sourceware.org Message-ID: <44FB28E0.9030203@cygwin.com> Date: Sun, 03 Sep 2006 15:11:28 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060727 Fedora/1.5.0.5-1.fc4.remi Thunderbird/1.5.0.5 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cron job don't work correct References: <6096299 DOT post AT talk DOT nabble DOT com> <6125573 DOT post AT talk DOT nabble DOT com> In-Reply-To: <6125573.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Todde wrote: > > Igor Peshansky wrote: >> On Fri, 1 Sep 2006, Todde wrote: >> >>> With cygwin i want run a daily script that should build my source every >>> day. >>> I want do that with a cron job. >>> [snip] >>> >>> Here is the problem: >>> But i.e. if i call another script from the cronscript.sh it don't work >>> as a cronjob but it work when i enter it on the command line. >>> >>> [snip] >>> Any ideas why the behaviour is so different between command line and cron >>> job ?? >> Cron runs with different environment settings than your command line >> (which uses a login shell). You will need to either specify paths to >> executables explicitly in your cron scripts, or run them using the login >> bash shell (e.g., use this in your cron script: >> >> /bin/bash -l -c "check.sh" >> >> ). It's usually better to go with explicit paths, though. > Hi Igor, > Thx for the answer. > Is there a possibility to set the cron environment variables in a file (i.e. > crontab file) to get always the same behaviour between cron and bash shell > when i start cygwin? And which variables (settings) must i set ? 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/