systemd requires HTTP server and serves QR codes

Kay Sievers kay at vrfy.org
Wed Oct 10 20:22:43 UTC 2012


On Wed, Oct 10, 2012 at 10:06 PM, Richard W.M. Jones <rjones at redhat.com> wrote:
> On Tue, Oct 09, 2012 at 10:58:45AM +0000, "J├│hann B. Gu├░mundsson" wrote:
>> Like to me rsyslog since the journal is an integrated part of systemd.
>
> Leaving aside the merits or otherwise of the journal, why does it need
> to be part of systemd?  Why not have it as a separate project?
> (Perhaps requiring systemd, or as a plugin of systemd if it's really
> needed.)
>
> The init system and logging have always been two different things.

And init had never any idea what a service was doing after it
double-forked, it could never monitor it, could not tell much about
its current state, had no history about the behaviour, could not even
safely shut it down.

Systemd is a real service babysitter, and tracks everything across the
entire life time of all services; the logs are just integral part of
systemd's job. It also provides the kernel and userspace early boot
logging support, and the out-of-the-box service stdout/stderr logging
support; that's why the journal daemon is mandatory and not an add-on.

Kay


More information about the devel mailing list