public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Wu Yongwei <adah@netstd.com>
To: cygwin@cygwin.com
Subject: Cron Problems
Date: Thu, 23 Jan 2003 06:24:00 -0000	[thread overview]
Message-ID: <3E2F595B.7050606@netstd.com> (raw)

I successfully ran some simple cron jobs under Cygwin, but two things 
puzzled me.

1) There are always some error messages in Event Log Viewer when running 
cron or crontab.  The error messages are like "Description of event ID 
(0) cannot be found (in resource (cron)).  There might be missing 
registry information ... crontab : Win32 Process Id = 0x34C : Cygwin 
Process Id = 0x340 : (Administrator) REPLACE (Administrator)" and "... 
/usr/sbin/cron : Win32 Process Id = 0x410 : Cygwin Process Id = 0x410 : 
(CRON) STARTUP (fork ok)" (this is a back-translation since I am using a 
Chinese system).  However, the scheduled job is successfully done.

2) How to start cron when starting the computer?  I tried running it as 
a service in cygrunsrv (cygrunsrv -I cron -p /usr/sbin/cron), but failed 
since starting the service always failed (cron : Win32 Process Id = 
0x3F8 : Cygwin Process Id = 0x3F8 : starting service `cron' failed: 
execv: 0, No error.) but the process cron appeared.

Thanks in advance.

Best regards,

Wu Yongwei

P.S.  When starting cron from a command prompt or shell, the process 
will be bound to the command prompt or shell, i.e., when the command 
prompt or shell exits, the cron process will exit too.  My method of 
curing this problem is to change byte 0xDC of cron.exe from 03 to 02 
(CUI to GUI).  Any better methods?


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

             reply	other threads:[~2003-01-23  2:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23  6:24 Wu Yongwei [this message]
2003-01-23  9:48 ` Elfyn McBratney
  -- strict thread matches above, loose matches on Subject: below --
2008-05-14 22:18 cron problems Charles Miller
2008-05-14 22:28 ` Pierre A. Humblet
2007-11-06 15:30 Helge Stenström
2007-11-06 15:56 ` Pierre A. Humblet
2007-05-14 14:45 CRON problems sabbella
2007-05-14 17:39 ` Pierre A. Humblet
2006-07-24 23:29 Cron Problems Andrew King
2006-07-24 23:38 ` René Berber
2004-05-07 15:17 CRON problems Harig, Mark
2004-05-07 15:15 Harig, Mark
2004-05-07 15:20 ` Igor Pechtchanski
2004-05-07 15:12 Harig, Mark
2004-05-06 22:47 Harig, Mark
2004-05-06 23:42 ` Hank Statscewich
2004-05-07  0:14   ` Igor Pechtchanski
2004-05-07  0:52     ` Hank Statscewich
2004-05-07  2:06       ` Brian Dessent
2004-05-07  6:55         ` Andrew DeFaria
2004-05-07  8:21           ` Brian Dessent
2004-05-07 15:06             ` Igor Pechtchanski
2004-05-07 15:23               ` Andrew DeFaria
2004-05-07 15:53                 ` Igor Pechtchanski
2004-05-07 20:08                   ` Andrew DeFaria
2004-05-07 15:20             ` Andrew DeFaria
2004-05-06  0:16 Hank Statscewich
2003-01-23 10:47 Cron Problems Wu Yongwei
2003-01-23 11:01 ` Elfyn McBratney
2001-10-31  8:51 cron problems Lou Rayman

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=3E2F595B.7050606@netstd.com \
    --to=adah@netstd.com \
    --cc=cygwin@cygwin.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).