On Wed, 11.01.12 07:20, Michael Biebl (mbi...@gmail.com) wrote: > > Am 11. Januar 2012 05:19 schrieb Lennart Poettering <lenn...@poettering.net>: > > > > Compatibility with classic syslog implementations is provided, via a > > socket /run/systemd/journal/syslog, to which all messages are forwarded, > > Most systems setup rsyslog to use /etc/rsyslog.d/, so dropping a small > file like 00-systemd.conf there containing: > $SystemLogSocketName /run/systemd/journal/syslog > > might do the trick. Haven't really tested and run the new journal > yet, so there are probably more issues. > Just wanted to share this info. Maybe it is useful to someone.
Oh, yupp, forgot to mention that. The systemd RPM includes such a drop-in file for now, though I believe that we should move that to the rsyslog RPM proper. Another new thing that's important to do to hook a syslog implementation in properly is create a symlink from syslog.service to the service of the syslog implementation. That way activation of syslog.socket will spawn the right service. In the Fedora rawhide RPM i hacked things into shape for now by just symlinking that to rsyslog.service unconditionally but in the long run this should move into the [Install] section of rsyslog.service itself. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel