Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: =?iso-8859-1?Q?=D8yvind_Harboe?= <oyvind DOT harboe AT zylin DOT com>
To: <cygwin AT cygwin DOT com>
Subject: cron problems finally resolved
Date: Fri, 26 Sep 2003 17:38:42 +0200
Message-ID: <LDEFIMCDLFJKECEABIHDGEDJCGAA.oyvind.harboe@zylin.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

After much knashing of teeth, I've finally figured out
what made my cron scripts fail:

In a normal shell, the /usr/bin is in at the front of
the $PATH.

When cron runs as a cygrunsrv service /usr/bin is at the
end of the $PATH.

In my case, I had a Windows version of "tar" that being executed
instead of CygWins "tar", but only when run from within cron
as a service.

My workaround was to launch the subcript in question via "bash":

bash --login -i -c "sh /cygdrive/c/foo/backup.sh"


This is not the first time I've run into $PATH problems between
Windows and CygWin. Something to look out for.

Øyvind


--
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/