From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40499-done@debbugs.gnu.org
Subject: bug#40499: mcron missing initial directories?
Date: Mon, 23 Aug 2021 23:48:59 -0400 [thread overview]
Message-ID: <87k0kbtsd0.fsf@gmail.com> (raw)
In-Reply-To: <87y2r3yccf.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 10 Apr 2020 10:27:44 +0200")
Hello,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> On Wed, Apr 08, 2020 at 11:55:05AM +0200, Ludovic Courtès wrote:
>>> Hi Danny,
>>>
>>> Danny Milosavljevic <dannym@scratchpost.org> skribis:
>>>
>>> > $ crontab -e
>>> >
>>> > In unknown file:
>>> > 0 (copy-file "/tmp/crontab.10313" "/var/cron/tabs/dannym")
>>> >
>>> > ERROR: In procedure copy-file:
>>> > In procedure copy-file: No such file or directory
>>> >
>>> > /var/cron doesn't exit either. Maybe we should automatically create /var/cron ?
>>>
>>> Yes, this should be done in an activation snippet.
>>>
>>
>> Should this be part of a crontab service
>
> That’s what I had in mind.
>
>> or does the mere existence of the files allow cron tasks to start
>> working?
>
> Good question. Actually I think the crontab compatibility bit is rather
> separate in mcron: AIUI, you have to run ‘crond’, not ‘mcron’, if you
> want that to get that functionality (info "(mcron) Invoking cron or
> crond").
>
> So perhaps all this is moot unless/until we have an mcron-crond service.
I think so. And since Dale Mellor, the original author of GNU Mcron
advises to keep the crond service per-user rather than for the system
[0], if we want a crond service it seems we should turn ourselves to
Guix Home.
Closing.
[0] https://issues.guix.gnu.org/40950#5
prev parent reply other threads:[~2021-08-24 3:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 22:35 bug#40499: mcron missing initial directories? Danny Milosavljevic
2020-04-08 9:55 ` Ludovic Courtès
2020-04-09 20:39 ` Efraim Flashner
2020-04-10 8:27 ` Ludovic Courtès
2021-08-24 3:48 ` Maxim Cournoyer [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0kbtsd0.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=40499-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).