From 4c0bebc335c279ecaea6fc0eb0acaa8c49c477b6 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 6 Jan 2012 03:11:17 +0100 Subject: kmsg-syslogd: remove kmsg-syslogd, since it's entirely obsoleted and replaced by journald --- units/syslog.socket | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) (limited to 'units') diff --git a/units/syslog.socket b/units/syslog.socket index 2d42305ec2..323fa86035 100644 --- a/units/syslog.socket +++ b/units/syslog.socket @@ -20,12 +20,17 @@ ListenDatagram=/run/systemd/journal/syslog SocketMode=0666 PassCredentials=yes -# The service we activate on incoming traffic is -# systemd-kmsg-syslogd.service. That doesn't mean however, that this -# is the main syslog daemon in the system. Another syslog -# implementation (which might be started via on-boot or another -# non-socket activation) can take over possession of the socket and -# terminate systemd-kmsg-syslogd. It could also simply replace the -# socket in the file system, and leave systemd-kmsg-syslogd untouched. - -Service=systemd-kmsg-syslogd.service +# The default syslog implementation should make syslog.service a +# symlink to itself, so that this socket activates the right actual +# syslog service. +# +# Examples: +# +# /etc/systemd/system/syslog.service -> /lib/systemd/system/rsyslog.service +# /etc/systemd/system/syslog.service -> /lib/systemd/system/syslog-ng.service +# +# Best way to achieve that is by adding this to your unit file +# (i.e. to rsyslog.service or syslog-ng.service): +# +# [Install] +# Alias=syslog.service -- cgit v1.2.3-54-g00ecf