From: Andrey Repin <anrdaemon@yandex.ru>
To: Achim Gratz <Stromeko@nexgo.de>, cygwin@cygwin.com
Subject: Re: crontab message "must be privileged to use -u"
Date: Thu, 19 Mar 2020 00:06:26 +0300 [thread overview]
Message-ID: <1777191824.20200319000626@yandex.ru> (raw)
In-Reply-To: <87a74dtnwa.fsf@Rainer.invalid>
Greetings, Achim Gratz!
> Andrey Repin writes:
>> I'm trying to use Cygwin's cron, but have a small issue:
>>
>> # crontab -u 18 -l
>> must be privileged to use -u
>>
>> Is there a way around the problem?
>> I'm in an elevated shell, but it seems crontab is doing a dumb POSIX check for
>> EUID=0.
> Then wrapping it with fakesu should work (no I have not tried that).
Cool idea, but I'm not up for recompiling crontab >.>
Still, thanks for the reply.
--
With best regards,
Andrey Repin
Thursday, March 19, 2020 0:05:59
Sorry for my terrible english...
next prev parent reply other threads:[~2020-03-18 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 19:54 Andrey Repin
2020-03-18 20:21 ` Achim Gratz
2020-03-18 21:06 ` Andrey Repin [this message]
2020-03-18 21:39 ` Achim Gratz
2020-03-19 1:25 ` Brian Inglis
2020-03-19 7:01 ` ASSI
2020-03-20 16:08 ` Stephen Carrier
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=1777191824.20200319000626@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=Stromeko@nexgo.de \
--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).