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

[Lennart Poettering]

On Fri, 20.06.14 20:51, Andrey Borzenkov (arvidjaar at gmail.com) wrote:

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

Ah, indeed!

Hmm, not sure what to do then, both goals are mutally incompatible:
either we don't isolate, and then risk that running some commands will
trigger the substantial amount of code. Or we isolate and then things
are much harder to debug, because the system is gone...

Lennart

-- 
Lennart Poettering, Red Hat