This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Fwd: Re: CRON and time
On Tue, Jul 10, 2001 at 01:19:50PM +0200, Michael Schaap wrote:
>
> >However, one thing is funny. My test crontab had a command like "date >>
> >/tmp/hello.txt", and that behaves slightly different with this version of cron.
> >When I run date from the cron-3.0.1-2 version, or when I run date from the
> >command line, I get output like:
> > Tue Jul 10 12:49:29 2001
> >But when I run it with this freshly compiled cron, I get:
> > Tue Jul 10 12:49:00 T-1 2001
> >I guess both are incorrect, from a UNIX point of view, and the second one
> >is actually a bit better than the first one...
>
> I've figured out what happens.
>
> Since the new cron copies the environment from the SYSTEM user, $PATH is
> set to the system path. On my machine, that contains the Apple Webobjects
> executables before Cygwin, and therefore it ran the WebObjects version of
> date.exe.
>
> If I specify /usr/bin/date as the command, or specify "PATH=/usr/bin" in
> the crontab, it works fine.
>
> Perhaps something for cron.README?
Our mails just crossed over :-)
No, I don't think it's worth to add that to the cron README. It's
a problem which always lurks for a chance to mess things up.
It's really a sort of a base problem. NT/W2K users (hm, no, say
"admins") are forced to keep track of the machines environment
setting, especially when using different POSIX emulations on the
same machine.
I think it could be worth a mentioning in the FAQ. I haven't yet
looked if sth. appropriate already exist in the FAQ, though.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/