From: ludo@gnu.org (Ludovic Courtès)
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Adding rottlog service in ‘%base-services’?
Date: Mon, 24 Oct 2016 23:02:11 +0200 [thread overview]
Message-ID: <87bmy9zcj0.fsf@gnu.org> (raw)
In-Reply-To: <CAL1_imkP4QvZgj00w2ih-KtJPk+yR9M8UB9LDyB_3gppfyuTBA@mail.gmail.com> (David Craven's message of "Sat, 22 Oct 2016 07:52:58 +0200")
David Craven <david@craven.ch> skribis:
>> Not sure I understand the problem. ‘mcron-jobs’ wouldn’t collide with
>> anything else AFAICS, and it would be clearer than just ‘jobs’ no?
>
> What I mean is that mcron-jobs assumes that the mcron-service is used.
> Calling it something general like jobs or cron-jobs wouldn't require
> renaming, if someone wants to use a different cron implementation. For
> example in an embedded system someone might prefer to use the
> busybox/toybox cron implementation. I'm not sure what other job time
> scheduling solutions exist. But a job is something that needs to run
> at specific times and has a bounded run time. I don't know how cron
> specific this feature is, or if the name of the job scheduler it's
> relevant as part of an operating-system declaration.
Oh, I see. The mcron jobs that we define in GuixSD directly use mcron’s
Scheme API; IOW, we don’t provide any abstraction over what mcron
provides. Thus it would be really hard to retarget such job specs to
tools other than mcron.
For this reason I think we should keep the ‘mcron-’ prefix here.
Does it make sense?
(The situation is comparable to that of Shepherd services.)
Ludo’.
next prev parent reply other threads:[~2016-10-24 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 8:24 Adding rottlog service in ‘%base-services’? Ludovic Courtès
2016-10-13 8:37 ` ng0
2016-10-13 8:44 ` David Craven
2016-10-19 15:03 ` Ludovic Courtès
2016-10-22 5:52 ` David Craven
2016-10-24 21:02 ` Ludovic Courtès [this message]
2016-10-25 12:53 ` David Craven
2016-10-13 8:40 ` Vincent Legoll
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=87bmy9zcj0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=david@craven.ch \
--cc=guix-devel@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).