public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "René Berber" <rene.berber@gmail.com>
To: cygwin@cygwin.com
Subject: Re: How to start and verify cron?
Date: Thu, 11 Jul 2019 22:57:00 -0000	[thread overview]
Message-ID: <4fe0eeb8-9de0-4c13-0d76-38a802247edd@gmail.com> (raw)
In-Reply-To: <CAA5t8Vpc=wGAap-K-J-qxn54_1EXPKgUdO2mvo1w8V5mKjm1ZA@mail.gmail.com>

On 7/11/2019 4:20 PM, David Karr wrote:

>>>> How do I add service dependencies to start up in a particular order?
>>>
>>> In an elevated cmd or bash shell:
>>> elevated > OR # sc config syslog-ng depend= cygserver
>>> elevated > OR # sc config cron depend= syslog-ng/cygserver
>>> N.B. the "=" is part of each keyword; multiple service dependencies are
>>> separated by "/".
>>
> After doing all of this, I still can't get cron jobs to work, and I can't
> get any info on why.

Doing all of "that" doesn't change a running cron daemon; those only
afect the initial run after boot up.

> This is the current output from "crontab -l":
...
> I've tried editing that last one and changing the minutes to include
> upcoming minutes, and then after those minutes, I check the results, and
> there are none.  Nothing in cron.log or syslog-ng.log.

Editing in this context means running 'crontab -e' (which uses vi to
edit the user's cron table).  After exiting that (with ZZ to save &
exit, or :wq) cron sends a message to the log, which, by the way may
need to be configured (i.e. syslog-ng has its own configuration, an in
there may be a line that says where cron's log goes, or if it is ignored).

Restarting the daemon should also produce a line in the log, which is
another notification that it is working.

In Linux I even have set the cron daemon's log level to show the start
of all cron jobs; that parameter in Cygwin would go as optional
parameter in the installation as service ("-L 1" in the cygrunsrv line
of the installation script, or maybe running cygrunsrv again, visible
and editable in the "Start parameters" at the service Properties view).
-- 
R.Berber



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-07-11 22:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 16:55 David Karr
2019-07-10 17:19 ` Brian Inglis
2019-07-10 22:15   ` David Karr
2019-07-10 23:04     ` Brian Inglis
2019-07-11 19:57       ` David Karr
2019-07-11 20:12         ` Vince Rice
2019-07-11 20:23           ` Vince Rice
2019-07-11 21:18             ` David Karr
2019-07-11 21:52               ` Vince Rice
2019-07-11 21:20         ` David Karr
2019-07-11 22:57           ` René Berber [this message]
2019-07-11 23:21             ` René Berber
2019-07-12 15:20           ` Brian Inglis
2019-07-12 16:18             ` David Karr
2019-07-13  8:26               ` Brian Inglis
2019-07-13  7:59             ` Henning
2019-07-13  8:21               ` Brian Inglis

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=4fe0eeb8-9de0-4c13-0d76-38a802247edd@gmail.com \
    --to=rene.berber@gmail.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).