From: Adam Faiz <adam.faiz@disroot.org>
To: ludo@gnu.org
Cc: guix-devel@gnu.org
Subject: Re: The 🐑 Shepherd gets a service collection
Date: Mon, 13 Mar 2023 23:39:32 +0000 [thread overview]
Message-ID: <bd0df1bf-6435-7f18-46f3-c25079769dc2@disroot.org> (raw)
> I imagine we could develop more convenient services like this, such as
> 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?I don't think a command scheduler should be added to the Shepherd, isn't that what mcron does?
If mcron has any deficiencies for being used as an `at` command, then that can be improved.
Regarding syslogd, I think a better approach is to tell the services to send their output to stdout and stderror,
so that logs don't depend on a separate logging service in the first place.
Per-service logging is already implemented in the Shepherd, but could be streamlined to have a default logs directory:
https://skarnet.org/software/s6/s6-log.html#loggingchain
I'm already happy with zless/any GUI log viewer, but it would be great to have a nicer user interface to view logs nonetheless.
next reply other threads:[~2023-03-13 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 23:39 Adam Faiz [this message]
2023-03-16 14:14 ` The 🐑 Shepherd gets a service collection Ludovic Courtès
2023-03-17 6:55 ` Adam Faiz
2023-03-17 9:52 ` Csepp
-- strict thread matches above, loose matches on Subject: below --
2023-03-13 16:11 Ludovic Courtès
2023-03-13 19:59 ` 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
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=bd0df1bf-6435-7f18-46f3-c25079769dc2@disroot.org \
--to=adam.faiz@disroot.org \
--cc=guix-devel@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).