This is the mail archive of the
mailing list for the Cygwin project.
Re: cron problems finally resolved
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Øyvind Harboe <oyvind dot harboe at zylin dot com>
- Cc: cygwin at cygwin dot com
- Date: Fri, 26 Sep 2003 11:43:55 -0400 (EDT)
- Subject: Re: cron problems finally resolved
- References: <LDEFIMCDLFJKECEABIHDGEDJCGAA.firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
On Fri, 26 Sep 2003, Øyvind Harboe wrote:
> 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.
FWIW, you don't have to invoke "sh" since you're already invoking bash,
i.e., you could change your invocation to
bash --login -i -c "cygdrive/c/foo/backup.sh"
(or even without a -c)... Take a look at the "-e" option to cygrunsrv --
it might help. Also, the following thread might be of interest:
|\ _,,,---,,_ email@example.com
ZZZzz /,`.-'`' -. ;-;;,_ firstname.lastname@example.org
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html