public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Elfyn McBratney" <elfyn-cygwin@exposure.org.uk>
To: "cygwin" <cygwin@cygwin.com>, "Wu Yongwei" <adah@netstd.com>
Subject: Re: Cron Problems
Date: Thu, 23 Jan 2003 11:01:00 -0000	[thread overview]
Message-ID: <006001c2c294$3c1e6b10$a77286d9@webdev> (raw)
In-Reply-To: <3E2F65D1.8080406@netstd.com>

> Thanks.  However, where can I find the options of cron?  Now I only find
> some info in /usr/doc/Cygwin/cron.README, but only in the ChangeLog
> section, which I ignored on the first reading!

There are only two options you can pass to cron. 1) -D (got the meaning
wrong the last time; Means don't fork) and 2) -x which is a debugging option
which prints out, well, debugging info ;-)

> And what is the use of the option -a?

When I referred to the `-a' option I was talking about cygrunsrv. The `-a'
option  takes the arguments you wish to pass to the executable, cron.exe,
and when the service is started it is started with those arguments. For
example, taken from cron.README:

  $ cygrunsrv -I cron -p /usr/sbin/cron -a -D

Regards,

Elfyn McBratney
elfyn@exposure.org.uk
www.exposure.org.uk




--
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  4:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 10:47 Wu Yongwei
2003-01-23 11:01 ` Elfyn McBratney [this message]
  -- 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  6:24 Cron Problems Wu Yongwei
2003-01-23  9:48 ` 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='006001c2c294$3c1e6b10$a77286d9@webdev' \
    --to=elfyn-cygwin@exposure.org.uk \
    --cc=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).