[systemd-devel] [PATCH 05/11] After emergency service had been started any incoming traffic on syslog.socket

Andrey Borzenkov arvidjaar at gmail.com
Mon Jun 16 19:52:04 PDT 2014


В Fri, 13 Jun 2014 16:41:04 +0200
Werner Fink <werner at suse.de> пишет:

> From: arvidjaar at gmail.com
> 
> will terminate emergency.service due to implicit dependencies on basic.target
> and therefore sysinit.target which in turn conflict with emergency.target.
> 

I always considered it as a stopgap not suitable for upstream. But I
still do not know what can be done to fix it.

It still looks rather wrong that any arbitrary service can displace
the whole run-level. May be we need counterpart for RefuseManualStart
so that some targets can only be displaced manually, not as result of
implicit dependency.

> ---
>  units/emergency.service.in |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git units/emergency.service.in units/emergency.service.in
> index 94c090f..59f7cda 100644
> --- units/emergency.service.in
> +++ units/emergency.service.in
> @@ -9,7 +9,7 @@
>  Description=Emergency Shell
>  Documentation=man:sulogin(8)
>  DefaultDependencies=no
> -Conflicts=shutdown.target
> +Conflicts=shutdown.target syslog.socket
>  Before=shutdown.target
>  
>  [Service]



More information about the systemd-devel mailing list