On Sun, 24.11.13 22:36, Andrey Borzenkov (arvidj...@gmail.com) wrote: > Interesting case (https://bugzilla.novell.com/show_bug.cgi?id=852021). > Systemd enters emergency due to failed mount. At the same time syslog > socket triggers syslog.service. Due to implicit Requires on > basic.target which Requires sysinit.target which conflicts with > emergency.{service,target} syslog.service tries to start basic.target > (it is not there yet ...) which apparently kills emergency shell.
This was probably introduced by 80cfe9e163b1c92f917e0a5e053b148fca790677. I figure we should find something in the middle of OnActivationIsolate=yes and OnActivationIsolate=no. i.e. make use of the "replace-irreversible" job mode which will allow the emergency jobs to be queued without being reversible by later requests until they are finished or explicitly flushed out with "systemctl cancel". I figure I'll replace OnActivationIsolate=yes by OnActivationMode= which takes the full range of job modes, and then turn OnActiveIsolate= into a hidden compat switch Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
