[systemd-devel] Standard syslog intergration?

Kay Sievers kay.sievers at vrfy.org
Sun Jan 23 04:45:41 PST 2011

On Sun, Jan 23, 2011 at 12:22, Andrey Borzenkov <arvidjaar at gmail.com> wrote:
> Could someone clarify what is supposed to be standard syslog
> integration in systemd? I.e. am I right, that
> - syslog.socket activates built-in systemd syslog implementation
> systemd-kmsg-syslogd which simply dumps everything to /dev/kmsg
> - at some point "real" syslog service is started which either takes
> over or creates new /dev/log.
> Is it correct?
> So questions
> 1. as there can be only one /dev/log socket activation, real syslog
> need not (and should not) supply it. It sould conflict with default
> syslog.socket. Am I right?
> 2. how can real syslog service "take over" /dev/log? Code example? I
> am not fond of idea to leave unused daemon hanging around.

Syslog services have been patched to be able to seemlessly take over
an already opened /dev/log. rsyslog is upstream already, the few
common other ones are in the distro packages, I think.


More information about the systemd-devel mailing list