On Thu, 10.03.11 23:08, Mike Kazantsev (mk.frag...@gmail.com) wrote: > On Thu, 10 Mar 2011 19:14:29 +0300 > Andrey Borzenkov <arvidj...@mail.ru> wrote: > > > On Wed, Feb 23, 2011 at 10:48 AM, Mike Kazantsev <mk.frag...@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 > > > > The behaviour I've described is what actually happened to me with git > version of rsyslog from the master branch (that's what I meant by > "latest scm version") - it's 6-git version. > If that doesn't support passsing sockets from systemd, I don't think any > other version does ;)
rsyslog 5.7.7 contains all the necessary glue code. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
