From: Derrick Stolee <stolee@gmail.com>
To: "Kevin Daudt" <me@ikke.info>,
"Martin Ågren" <martin.agren@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] maintenance: specify explicit stdin for crontab
Date: Tue, 30 Mar 2021 15:32:39 -0400 [thread overview]
Message-ID: <bc4d77cd-5b2a-bdda-d447-8bf9d44c313f@gmail.com> (raw)
In-Reply-To: <YGNcA3paBeZ8mYVP@alpha>
On 3/30/2021 1:12 PM, Kevin Daudt wrote:
> On Tue, Mar 30, 2021 at 08:02:22AM -0400, Derrick Stolee wrote:
>> On 3/30/2021 1:41 AM, Martin Ågren wrote:
>>> On Mon, 29 Mar 2021 at 23:23, Kevin Daudt <me@ikke.info> wrote:
>>>>
>>>> There are multiple crontab implementations that require stdin for
>>>> editing a crontab to be explicitly specified as '-'.
>>
>> Thank you for reporting this, especially with a patch!
>>
>> However, I'm not sure about this adding of '-' being something that
>> crontab ignores so commonly. My Ubuntu machine reports this:
>>
>> $ crontab -e -
>> crontab: usage error: no arguments permitted after this option
>> usage: crontab [-u user] file
>> crontab [ -u user ] [ -i ] { -e | -l | -r }
>> (default operation is replace, per 1003.2)
>> -e (edit user's crontab)
>> -l (list user's crontab)
>> -r (delete user's crontab)
>> -i (prompt before deleting user's crontab)
>>
>> Is there a way we could attempt writing over stdin, notice the
>> failure, then retry with the '-' option?
>
> We do not use -e to edit, we run `crontab` and provide the contents to
> stdin. `crontab -e` just opens the crontab in the users editor, which
> would work with busybox as well, but that's not what's being done here.
Thank you. Of course. Muscle memory from testing crontab manually.
Thanks,
-Stolee
next prev parent reply other threads:[~2021-03-30 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 21:09 [PATCH] maintenance: specify explicit stdin for crontab Kevin Daudt
2021-03-30 5:41 ` Martin Ågren
2021-03-30 12:02 ` Derrick Stolee
2021-03-30 17:12 ` Kevin Daudt
2021-03-30 19:32 ` Derrick Stolee [this message]
2021-03-30 17:43 ` Todd Zullinger
2021-03-30 19:38 ` Derrick Stolee
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=bc4d77cd-5b2a-bdda-d447-8bf9d44c313f@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.agren@gmail.com \
--cc=me@ikke.info \
/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 NNTP newsgroup(s).