[systemd-devel] systemd-logger and external syslog daemon

Andrey Borzenkov arvidjaar at mail.ru
Thu Mar 10 08:14:29 PST 2011


On Wed, Feb 23, 2011 at 10:48 AM, Mike Kazantsev <mk.fraggod at gmail.com> wrote:

> How the kmsg-syslogd->rsyslog migration (for systemd output) is supposed
> to work?
>

As I just went through all of it ...

you absolutely need rsyslog that supports passing sockets from
systemd. Otherwise it is race condition - rsyslog will remove and
recreate /dev/log on activation so you end up with

a) some processes still connected to removed /dev/log and passing
messages to /dev/kmsg this way

b) losing some messages for as long as /dev/log does not exist

Unless you have rsyslog that really supports  it - do not stop
systemd-kmsg-syslogd! It will result in process blocking on accessing
it creating all sorts of interesting deadlocks. I managed to
completely lock out any user this way ... :)


More information about the systemd-devel mailing list