[systemd-devel] syslog makes impossible to enter emergency mode

David Timothy Strauss david at davidstrauss.net
Sun Nov 24 12:26:23 PST 2013


On Nov 25, 2013 4:36 AM, "Andrey Borzenkov" <arvidjaar at 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.
>
> I wonder if default service dependency should not be Requisite instead
> of Requires. After all, if we are not past basic.target, there should
> be really good reason for it and attempting to start it implicitly does
> not look the right thing to do.

I haven't looked at all, but have you checked whether this is a systemd
core issue versus just a SUSE one?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20131125/5f6f325b/attachment.html>


More information about the systemd-devel mailing list