From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Subject: The 🐑 Shepherd gets a service collection
Date: Mon, 13 Mar 2023 17:11:34 +0100 [thread overview]
Message-ID: <87mt4gzl55.fsf@inria.fr> (raw)
Hello Guix!
I pushed some changes yesterday that confirm that the Shepherd paves the
way for init system innovation, synergistic cross-domain fertilization,
and delimited continuations:
https://git.savannah.gnu.org/cgit/shepherd.git/log/?id=31d21fa083872d500c016b6b3b2587d25510702d
31d21fa * Add REPL service.
cd6f3fb * comm: Add 'open-server-socket'.
c64804f * Add resource monitoring service.
These new services are built into shepherd, allowing users to control it
and to fiddle with it. The REPL is functional but of course a bit
bumpy: you’d better know what you’re doing.
I imagine we could develop more convenient services like this, such as a
basic command scheduler similar to the ‘at’ command, and a syslogd
implementation. The latter could be nice for a couple of reasons:
logging would happen from the start and till the end (an improvement
over the external syslogd process), and it could let us provide a nicer
user interface to view logs (taking inspiration from that of
‘journalctl’).
Thoughts? Ideas?
Ludo’.
PS: It just occurred to me that we might as well rename the new
(shepherd service …) hierarchy to (shepherd sheep …) or even
(shepherd 🐑 …).
next reply other threads:[~2023-03-13 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 16:11 Ludovic Courtès [this message]
2023-03-13 19:59 ` The 🐑 Shepherd gets a service collection indieterminacy
2023-03-14 12:20 ` Maxim Cournoyer
2023-03-16 14:16 ` Ludovic Courtès
2023-03-17 16:28 ` Maxim Cournoyer
2023-03-14 14:43 ` Efraim Flashner
-- strict thread matches above, loose matches on Subject: below --
2023-03-13 23:39 Adam Faiz
2023-03-16 14:14 ` Ludovic Courtès
2023-03-17 6:55 ` Adam Faiz
2023-03-17 9:52 ` Csepp
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=87mt4gzl55.fsf@inria.fr \
--to=ludo@gnu.org \
--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).