public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: Siegfried Heintze <siegfried@heintze.com>
Cc: cygwin@cygwin.com
Subject: RE: cron issue: The description for Event ID ( 0 ) in Source (  /usr/sbin/cron ) cannot be found
Date: Fri, 01 Jul 2005 00:25:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.61.0506302019570.15034@slinky.cs.nyu.edu> (raw)
In-Reply-To: <30138206.1120176635437.JavaMail.SYSTEM@CCC-NOVA1>

On Thu, 30 Jun 2005, Siegfried Heintze wrote:

> I'm having similar troubles. I have read the cron.README file. I installed
> cron some time ago. I believe I used the command described in cron.README. I
> see there are several cron.exes running on my system when I look at the
> process list. Should there be?

Depends.  Every time cron forks, you'll see an instance of the executable.
Whether cron forks or not depends on your config, IIRC.

> Here is one of the many entries in the event viewer.
>
> I need some help interpreting this:

Okay.

> The description for Event ID ( 0 ) in Source ( /usr/sbin/cron ) cannot be
> found. The local computer may not have the necessary registry information or
> message DLL files to display messages from a remote computer. You may be
> able to use the /AUXSOURCE= flag to retrieve this description; see Help and
> Support for details. The following information is part of the event:

Ignore the above.  It's Windows telling you that it can't find the
template to nicely format the event content, so it'll give you the raw
event data.

> /usr/sbin/cron : PID 1836 : (Siegfried) CMD (/c/Perl/bin/perl
> /c/WinOOP/Perl/bots/yahoo/finance/crawl-hot-jobs.pl /GUI=NONE /sleep=60
> /threads=8 >`date +").

Aha, this is the important one.  It's cron telling you the exact command
it tried to run.

> Any suggestions on how to resolve this?

Looks like your cron job command isn't
parsed correctly -- the name of the file to redirect the output to doesn't
look right.  Also, I'm assuming /c/Perl contains ActiveState perl, not
Cygwin's one.  If so, passing it a Cygwin path to the script won't work.

If it still doesn't work after you fix both of the problems above, please
post your crontab.

HTH,
	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!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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

  reply	other threads:[~2005-07-01  0:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 21:42 cron issue Imran Merali
2005-06-29 21:44 ` René Berber
2005-06-29 22:13   ` Larry Hall
2005-07-01 14:40     ` Imran Merali
2005-07-01  0:10   ` cron issue: The description for Event ID ( 0 ) in Source ( /usr/sbin/cron ) cannot be found Siegfried Heintze
2005-07-01  0:25     ` Igor Pechtchanski [this message]
2005-07-01  2:18     ` Siegfried Heintze
2005-07-01  2:44       ` Larry Hall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.GSO.4.61.0506302019570.15034@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin@cygwin.com \
    --cc=siegfried@heintze.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).