Bug#799549: systemd: Provide system-log-daemon

Matthias Urlichs matthias at urlichs.de
Sun Sep 20 16:57:13 BST 2015

On 20.09.2015 17:09, Michael Biebl wrote:
> I'm actually not sure if we should do that just yet.
> Keep in mind that we don't enable persistent logging in journald.
> One idea, that's coming from openSUSE, is a basically empty package
> which ships /var/log/journal, thus enabled persistent logging and this
> package would provide system-log-daemon.
I like this solution in general, but it'd still annoy me.

IMHO it should be the system admin's decision whether to enable
persistent logging, either by creating that directory or by installing
some syslog daemon or by starting a journal forwarder.

My problem case is nullmailer, which Recommends:
rsyslogd|system-log-daemon. It certainly makes sense to log emailer
errors, but this was a bunch of Raspberry Pi computers with verbose
logging-to-memory turned on – installing nullmailer turned this into a
bunch of small computers logging copiously to µSD cards. I lost two of
them before I realized what's going on. :-/  Installing an emailer
should not result in something like that.

-- Matthias Urlichs

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150920/95e84ac7/attachment-0002.sig>

More information about the Pkg-systemd-maintainers mailing list