DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E40ED3985830
To: cygwin@cygwin.com
References: <CAHZxHH+KsSz_mUASC5fD2aw5fo=6wZxvF1WjJxv79fAkLk5syg@mail.gmail.com>
 <CAHZxHHLAPVMEWqYd5vmaUu-vnJ9MGvF-PV6rd9tRgDFwfyrfew@mail.gmail.com>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Organization: Systematic Software
Subject: Re: cron problem -- can't switch user context
Message-ID: <34b44dbc-8522-4af8-f973-4c401a7e4ed3@SystematicSw.ab.ca>
Date: Tue, 20 Jul 2021 00:53:12 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <CAHZxHHLAPVMEWqYd5vmaUu-vnJ9MGvF-PV6rd9tRgDFwfyrfew@mail.gmail.com>
Content-Language: en-CA
Precedence: list
Reply-To: cygwin@cygwin.com
Cc: jhetzler@chabaso.com, Jeremy Hetzler <jhetzler.atticus@gmail.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On 2021-07-19 11:40, Jeremy Hetzler via Cygwin wrote:
> Upon installing Cygwin and cron on a new Windows Server 2019 machine,
> we are unable to get cron to work.
> 
> I installed cron using cron-config. Cron is configured to run under
> account cyg_server, which cron-config set up. cron-config reported
> that "cyg_server is a valid privileged account".
> 
>>From cronevents, I see numerous errors saying "can't switch user
> context". It looks like every time cron tries to run a job, it emits
> one of these errors.
> 
> Example:
>> 2021/07/15 18:45:02 [cyg_server] /usr/sbin/cron: PID 6421: (CRON) error (can't switch user context)
> 
> See attached for cronbug output.
> 
> I tried rebooting the machine, but this did not help.
> 
> How can we get cron to work on this new machine?
> 
> Please copy me on any responses; thank you.

Use the recommended local System account and you should have no problems 
with recent Cygwin services under recent Windows:

"To run multiple users, cron must change user context without knowing 
the passwords. There are three methods to do that, as explained in

	http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd1

If all the cron users have executed "passwd -R" (see man passwd),
which provides access to network drives, or if you are using the
[obsolete] cyglsa package, then cron should run under the
local system account."

-- 
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.
[Data in binary units and prefixes, physical quantities in SI.]

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