From: Andrey Repin <anrdaemon@yandex.ru>
To: Brian Inglis <cygwin@cygwin.com>, cygwin@cygwin.com
Subject: Re: Cron can't switch user context
Date: Wed, 28 Apr 2021 07:32:22 +0300 [thread overview]
Message-ID: <190195709.20210428073222@yandex.ru> (raw)
In-Reply-To: <19ee56d3-2cde-c385-c7e5-d7aa8b998e8b@SystematicSw.ab.ca>
Greetings, Brian Inglis!
>> We are aware that there are many tutorials and Q&A on the net which deal with
>> exactly this subject. However, none of the proposed solutions worked for us.
The one Q&A should have get you started: since Cygwin 3.1 (IIRC, may be
earlier), the core was changed to use LocalSystem account and some new(-ish)
facilities only available in Windows 7 and up to rebuild auth user token
without using CygLSA or what not.
This affecting SSHD, Cron and any other Cygwin daemon dealing with user
authorization.
>> We would be very glad if you could give us some hints how to solve the problem.
>> P.S. Please note that /var/log/cron.log and /home/Administrator/cron.log are
>> both empty, so we didn't attach them.
> I changed mine to run under LocalSystem account when system upgraded, had cyglsa
> installed previously (not used now I believe), and set passwd -R for account.
> Don't forget to either set PATH to scripts in crontab or set for system before
> cygrunsrv starts cron as a Windows service.
--
With best regards,
Andrey Repin
Wednesday, April 28, 2021 7:28:14
Sorry for my terrible english...
next prev parent reply other threads:[~2021-04-28 4:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 10:37 Peter Pfannenschmid
2021-04-28 0:14 ` Brian Inglis
2021-04-28 4:32 ` Andrey Repin [this message]
[not found] <BADF3C947A1BD54FBA75C70C241B0B9E763574@ex02.co.idirect.net >
2003-09-10 16:12 ` cron: " Larry Hall
2003-09-14 21:22 ` René Haber
-- strict thread matches above, loose matches on Subject: below --
2003-09-10 15:57 Harig, Mark
2003-09-07 17:06 René Haber
2003-09-07 18:08 ` Igor Pechtchanski
2003-09-08 17:30 ` René Haber
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=190195709.20210428073222@yandex.ru \
--to=anrdaemon@yandex.ru \
--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).