public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: How to start and verify cron?
Date: Wed, 10 Jul 2019 23:04:00 -0000	[thread overview]
Message-ID: <74357359-436a-0ead-f7bc-b288572d6cc3@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAA5t8VpPvvt3c+CZHpSVrj_XAdJrTVCfq6Wd0mSBKhZpqv8Csg@mail.gmail.com>

On 2019-07-10 16:15, David Karr wrote:
> On Wed, Jul 10, 2019 at 10:20 AM Brian Inglis wrote:
>     On 2019-07-10 10:55, David Karr wrote:
>     > I've checked the user guide and the FAQ, and I can't find any information
>     > about how to start cron and verify that it's working.  I found other blog
>     > posts on other sites, but some of them are old.
> 
>     Did you run service setup script /bin/cron-config to set up the service?
> When I ran that now, it says "Cron is already installed as a service under
> account ...", so I assume that means that I did.
>     > I had installed cron, and I thought it was working, but now I think that it
>     > is not.  If I edit "~/crontab" and then run "crontab -l", it lists the
>     > changes I've made to jobs, so at least that is working.  The real job I
>     > have didn't appear to be doing what it was supposed to be doing, so I added
>     > a new trivial job that just appends output from "date" to a file in my
>     > homedir, and after the scheduled time of the job, the file was not created.
> 
>     Messages from cron and other active services should be visible in the Windows
>     application event log if you have not set up a syslog service.
> I went through it, but I didn't see any indications of issues with cron.  I'm
> not sure what to look for, or where in the event log interface.
>     > This is the additional job I added:
>     >
>     >     40,42,44 * * * * date >> /home/<myuid>/date.txt
>     >
>     > I did find a "/var/log/cron.log", but it is empty, and the modtime is from
>     > a few months ago.
>     >
>     > One blog post I found talks about running "cygrunsrv -I cron -p
>     > /usr/sbin/cron -a -D". I just did this, and it reports "The specified
>     > service already exists."
>     >
>     > This is my uname -a output:
>     >
>     >     CYGWIN_NT-6.1 ... 3.0.3(0.338/5/3) 2019-03-09 19:12 x86_64 Cygwi
>     For a more Unix like and self contained Cygwin approach, install syslog-ng, run
>     service setup scripts /bin/cygserver-config /bin/syslog-ng-config
>     /bin/cron-config, add service dependencies to start up in that order, and you
>     should see cron messages in /var/log/syslog if you run elevated: you can also
>     run chmod elevated to make /var/log/syslog world readable, or setfacl to add
>     user or group read ACLs.
> 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 "/".

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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-10 23:04 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 [this message]
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
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=74357359-436a-0ead-f7bc-b288572d6cc3@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).