From 3136ec90adf6d797eb2ac756f52313581124f38e Mon Sep 17 00:00:00 2001 From: Martin Pitt Date: Wed, 27 Apr 2016 10:34:24 +0200 Subject: Stop syslog.socket when entering emergency mode (#3130) When enabling ForwardToSyslog=yes, the syslog.socket is active when entering emergency mode. Any log message then triggers the start of rsyslog.service (or other implementation) along with its dependencies such as local-fs.target and sysinit.target. As these might fail themselves (e. g. faulty /etc/fstab), this breaks the emergency mode. This causes syslog.socket to fail with "Failed to queue service startup job: Transition is destructive". Add Conflicts=syslog.socket to emergency.service to make sure the socket is stopped when emergency.service is started. Fixes #266 --- units/emergency.service.in | 1 + 1 file changed, 1 insertion(+) (limited to 'units/emergency.service.in') diff --git a/units/emergency.service.in b/units/emergency.service.in index fb390eacfe..0de16f24e8 100644 --- a/units/emergency.service.in +++ b/units/emergency.service.in @@ -11,6 +11,7 @@ Documentation=man:sulogin(8) DefaultDependencies=no Conflicts=shutdown.target Conflicts=rescue.service +Conflicts=syslog.socket Before=shutdown.target [Service] -- cgit v1.2.3-54-g00ecf