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

[Andrey Borzenkov]

В Fri, 20 Jun 2014 18:38:27 +0200
Lennart Poettering <lennart at poettering.net> пишет:

> On Fri, 13.06.14 16:41, Werner Fink (werner at suse.de) wrote:
> 
> > 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 am not entirely sure how emergecny.service should have been reached
> with syslog.socket in place? isolate should not have left it around?
> 

commit 80cfe9e163b1c92f917e0a5e053b148fca790677
Author: Dr. Tilmann Bubeck <t.bubeck at reinform.de>
Date:   Fri May 4 10:32:47 2012 +0200

    Do no isolate in case of emergency or severe problems


> > 
> > ---
> >  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]
> 
> 
> Lennart
>