cron problems finally resolved

cron problems finally resolved

[Øyvind Harboe]

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/

Re: cron problems finally resolved

[Igor Pechtchanski]

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.
>
> Øyvind

Øyvind,

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:
<http://cygwin.com/ml/cygwin/2003-09/msg01633.html>.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,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
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

SV: cron problems finally resolved

[Øyvind Harboe]

>Take a look at the "-e" option to cygrunsrv --
>it might help.

I find it a bit unnerving that I test my scripts under
bash and then deploy them under a different environment
that I do not properly understand.

By using the "bash" trick in the last post, I was hoping
to more precisely copy the environment under which I
tested my scripts.

From the thread you referred to, it seems like "bash"
is the way to go for me, rather than "cygrunsrv -e".

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