From 52f319b29398d36ed8d1a70f68a170c0a85f401d Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Wed, 20 Oct 2010 17:48:01 +0200 Subject: syslog: enable kmsg bridge by default and enable syslogging for early boot services --- units/syslog.socket | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 units/syslog.socket (limited to 'units/syslog.socket') diff --git a/units/syslog.socket b/units/syslog.socket new file mode 100644 index 000000000..c18da4643 --- /dev/null +++ b/units/syslog.socket @@ -0,0 +1,27 @@ +# This file is part of systemd. +# +# systemd is free software; you can redistribute it and/or modify it +# under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. + +# See systemd.special(7) for details + +[Unit] +Description=Syslog Socket +DefaultDependencies=no +Before=sockets.target + +[Socket] +ListenDatagram=/dev/log +SocketMode=0666 + +# 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 -- cgit v1.2.3