6f6d1a8a6a
1. If we exited emergency mode immediately, we don't want to have an irreversible stop job still running for syslog.socket. I _suspect_ that can't happen, but let's not waste effort working out exactly why it's impossible and not just very improbable. 2. Similarly, it seems undesirable to have rescue.service and emergency.service both running with an open FD of /dev/console, for however short a period.
46 lines
1.3 KiB
SYSTEMD
46 lines
1.3 KiB
SYSTEMD
# This file is part of systemd.
|
|
#
|
|
# systemd is free software; you can redistribute it and/or modify it
|
|
# under the terms of the GNU Lesser General Public License as published by
|
|
# the Free Software Foundation; either version 2.1 of the License, or
|
|
# (at your option) any later version.
|
|
|
|
[Unit]
|
|
Description=Syslog Socket
|
|
Documentation=man:systemd.special(7)
|
|
Documentation=https://www.freedesktop.org/wiki/Software/systemd/syslog
|
|
DefaultDependencies=no
|
|
Before=sockets.target
|
|
|
|
# Don't allow logging until the very end
|
|
Conflicts=shutdown.target
|
|
Before=shutdown.target
|
|
|
|
# Don't try to activate syslog.service if sysinit.target has failed.
|
|
Conflicts=emergency.service
|
|
Before=emergency.service
|
|
|
|
[Socket]
|
|
ListenDatagram=/run/systemd/journal/syslog
|
|
SocketMode=0666
|
|
PassCredentials=yes
|
|
PassSecurity=yes
|
|
ReceiveBuffer=8M
|
|
|
|
# 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
|
|
#
|
|
# See https://www.freedesktop.org/wiki/Software/systemd/syslog for details.
|