From: Stephen Carrier <carrier@berkeley.edu>
To: Keith Christian <keith1christian@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: CRON executes CRONTABS only when run from terminal as "/usr/sbin/cron &"
Date: Mon, 16 Nov 2020 12:44:33 -0800 [thread overview]
Message-ID: <20201116204433.GA16928@iguana.crashland.org> (raw)
In-Reply-To: <CAFWoy7F4Kjv_KSLhBCGaCuMzztLnZr+9GVKedHv7C=RvuwWtMQ@mail.gmail.com>
On Sun, Nov 15, 2020 at 02:03:28PM -0700, Keith Christian via Cygwin wrote:
> Cygwin people,
>
> Running with this version of Cygwin.
> CYGWIN_NT-10.0 DESKTOP-ASERVER 3.1.7(0.340/5/3) 2020-08-22 17:48 x86_64 Cygwin
>
> Windows info:
> $ /lib/csih/winProductName.exeMicrosoft Windows 10 Professional,
> 64-bit (build 18363)
>
> I installed using cron-config, and created the cyg_server user.cron
> starts OK, but does not appear to execute the crontabs.
> No messages or errors in /var/log/cron.log.
>
> $ cygrunsrv -Q cron
> Service : cron
> Display name : Cron daemon
> Current State : Running
> Controls Accepted : Stop
> Command : /usr/sbin/cron -n
What's the output of "cygrunsrv -V -Q cron"?
What are the file permissions on /var/log/cron.log? ("ls -l
/var/log/cron.log"). The uid running cron needs write permission there.
I run cron from the Local System account, which can setuid to other users.
I don't know the circumstances where one should still use a non-SYSTEM
account with Windows 10, but they aren't mine and I recommend running
as SYSTEM if possible.
Stephen
next prev parent reply other threads:[~2020-11-16 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 21:03 Keith Christian
2020-11-16 20:44 ` Stephen Carrier [this message]
2020-11-16 20:49 ` Stephen Carrier
[not found] ` <CAFWoy7F8UG+gx-TiFL=U03dRnnbW0iuTspSiE_5ETAuUr_n+8Q@mail.gmail.com>
2020-11-25 23:13 ` Stephen Carrier
2020-11-26 4:29 ` 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=20201116204433.GA16928@iguana.crashland.org \
--to=carrier@berkeley.edu \
--cc=cygwin@cygwin.com \
--cc=keith1christian@gmail.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).