This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: cron does not do anything


Thanks for the quick response. The crontab line is literally like:

28 19 * * * /usr/bin/touch /tmp/abcd

Pierre, attached is the fgrep result of all the logs in /var/log. "cron.log" was created but is empty all along.

Let me know if I can supply further diagnostic information.

Thanks,
Ting

> -----Original Message-----
> From: William Sutton [mailto:william@trilug.org]
> Sent: Tuesday, April 21, 2009 10:26 AM
> To: Pierre A. Humblet
> Cc: Ting Zhou; cygwin@cygwin.com
> Subject: Re: cron does not do anything
> 
> Did you check that your cron job line is formatted correctly?  If your
> line is literally of the form
> 
> /usr/bin/touch /tmp/abcd
> 
> then it definitely won't run because it is incorrectly written.
> 
> William Sutton
> 
> On Tue, 21 Apr 2009, Pierre A. Humblet wrote:
> 
> >
> > ----- Original Message -----
> > From: "Ting Zhou" <>
> > To: <cygwin@cygwin.com>
> >
> >
> > I'd like to report a bug with Vixie cron. I have cygwin installed with
> cron option. And I ran
> > "cron-config" and set up everything. Cron-diagnose script didn't find any
> problem. Cron service
> > was also started without problem. However, cron just wouldn't run the
> simple command I set up in
> > the crontab "/usr/bin/touch /tmp/abcd".
> > ****************
> > Hi,
> >
> > On your system you have syslog running, instead of using the Windows
> event log.
> > That's fine, except that your syslog configuration now controls how the
> cron log messages
> > are handled. The current "cronbug" script is not smart enough to figure
> that out
> > and does not provide enough info to help you (everything looks normal to
> me)
> >
> > Please send us in attachment the file containing the cron logs (if they
> are kept).
> > If it's very long, use "fgrep -i cron" to isolate relevant lines.
> > Alternatively, stop both syslog and cron, then restart cron only, run the
> cronbug script
> > again and send us the output.
> >
> > Pierre
> >
> >
> >
> > --
> > 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/
> >
> >

Attachment: cron.log
Description: cron.log

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]