On Mon, Mar 7, 2016 at 2:13 PM, Lukáš Nykrýn <lnyk...@redhat.com> wrote: > Francis Moreau píše v Po 07. 03. 2016 v 08:04 +0100: >> Hello, >> >> Sorry for the long delay. >> >> On Fri, Feb 26, 2016 at 5:05 AM, Andrei Borzenkov < >> arvidj...@gmail.com> wrote: >> > 26.02.2016 00:55, Francis Moreau пишет: >> > > >> > > But now I'm wondering how the following case is handled: a >> > > sysinit >> > > script "a" has "Required-Start: b". But "b" is a native systemd >> > > service. I don't think the tool that enable/disable sysv services >> > > can >> > > enable and order correctly the native service. >> > > >> > >> > What difference does it make? >> >> The difference is that in my current understanding nothing will pull >> "b" in. >> >> Indeed "a" will have "After=b" ordering dep but that's not sufficient >> to start "b". And since "b" is native it will not have a "SXXb" >> installed by insserv. > > IIRC the behavior is still the same as it always was. Chkconfig on (at > least rhel-based systems) did not enable the dependencies for the > service. It only assured that the services will be started in the > correct order.
That doesnt seem to match what Lennart said previously: """ Well, on SysV the requirement in the "Required-Start:" concept is actually a request to the tool that enables/disables a service (i.e. the chkconfig or update-rcd tool, depending on the distro). It means that it shall enable another service "b" if "a" is to be enabled. """ Thanks. -- Francis _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel