unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: The 🐑 Shepherd gets a service collection
Date: Fri, 17 Mar 2023 12:28:07 -0400	[thread overview]
Message-ID: <87jzzf5omg.fsf@gmail.com> (raw)
In-Reply-To: <87zg8cdbo3.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 16 Mar 2023 15:16:12 +0100")

Hi Ludo,

Ludovic Courtès <ludo@gnu.org> writes:

> Hi,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>
> [...]
>
>>> 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?
>>
>> While I also find the journalctl interface to be convenient, the
>> underlying database logs is costly in terms of storage and complexity
>
> Agreed (that’s why I mentioned the user interface of ‘journalctl’, not
> the storage mechanism of ‘journald’).

OK. In my mind both are probably hard to separate though (database logs
are more malleable, which is what journald exploits).

-- 
Thanks,
Maxim


  reply	other threads:[~2023-03-17 16:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 16:11 The 🐑 Shepherd gets a service collection 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 [this message]
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=87jzzf5omg.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --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).