Hi Ludo, Ludovic Courtès <l...@gnu.org> writes:
> Hi, > > Maxim Cournoyer <maxim.courno...@gmail.com> skribis: > >> Ludovic Courtès <l...@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
