all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Dale Mellor <guix-devel-0brg6b@rdmp.org>
Cc: 40950@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
	"Marcin Karpezo" <sirmacik@wioo.waw.pl>
Subject: [bug#40950] [PATCH] mcron, create /var/cron/tabs on activation
Date: Mon, 09 Aug 2021 12:12:09 -0400	[thread overview]
Message-ID: <87bl661tt2.fsf_-_@gmail.com> (raw)
In-Reply-To: <e36bcec5b148119d067f0eddda77acf28b4b2e57.camel@rdmp.org> (Dale Mellor's message of "Wed, 17 Jun 2020 13:43:03 +0100")

Hello,

Dale Mellor <guix-devel-0brg6b@rdmp.org> writes:

> Hello,
>
>    for information I don't agree with having a central crond process
> running on the system.  I put it in mcron only for compatibility with
> legacy crons, but think that it is *much* better for each service which
> needs one, and each user, to run their own private daemon and manage their
> own configuration.  The reasons include:
>
>   * reliability: one faulty client or scheme configuration clause is less
> likely to make the system unavailable to others;
>   * security: UNIX users can only mess with their own configurations, and
> there is no need for any SUID programs;
>   * safety: I think the mcron personality gets much more use in practice,
> hence is tested by many more people;
>   * efficiency: using the legacy crontab directories means that the daemon
> has to wake up and scan all these files once per minute, even if the
> actions are only performed once per day or even once per month;
>   * convenience: I think it is actually simpler all round to have separate
> configurations for each utility that needs cron service, rather than
> splicing and editing existing central system-wide files.
>
>    Basically, all these things are the reasons I developed mcron in the
> first place.
>
>    As an aside, I would love to be able to pull out all of the legacy
> compatibility stuff from the mcron code, as it would massively simplify my
> life!  (Don't worry, it probably won't happen).

Thanks for tipping in!

In light of this, it seems it'd be a better option to add crond support
at the level of Guix Home, which would allow easily configuring mcrond
as a user service rather than at the system level.

Thanks,

Maxim




      parent reply	other threads:[~2021-08-09 16:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 21:28 [bug#40950] [PATCH] mcron, create /var/cron/tabs on activation Marcin Karpezo
2020-05-01 22:05 ` Ludovic Courtès
2020-05-02 10:03   ` Marcin Karpezo
2020-05-02 13:44     ` Ludovic Courtès
2020-05-25 18:08       ` sirmacik
2020-06-17 12:43 ` [bug#40950] Mcron originator: My opinion Dale Mellor
2020-06-17 12:50   ` Dale Mellor
2021-08-09 16:12   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bl661tt2.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=40950@debbugs.gnu.org \
    --cc=guix-devel-0brg6b@rdmp.org \
    --cc=ludo@gnu.org \
    --cc=sirmacik@wioo.waw.pl \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.