[systemd-devel] [PATCH] service: do not apply SysV ordering to native services

Michal Schmidt mschmidt at redhat.com
Thu Mar 24 11:57:32 PDT 2011


On Thu, 24 Mar 2011 21:37:12 +0300 Andrey Borzenkov wrote:
> Yes, you are right. But blindly resetting SysV priority is still wrong
> - native unit may have defined it as well.

That's a good point. I did not realize "SysVStartPriority=" exists.

> This ordering is applied only for service without LSB headers; you
> have really many of them.
> 
> It is still not clear whether this is a bug. We assume that SysV
> script and service unit with the same provide the same service. So
> what logically follows, if SysV script claims it needs to be started
> after this service and does not help with stating functional
> requirements (LSB headers), systemd have to ensure script gets what it
> asked for ...

But according to the rule "Native unit hides SysV script completely" we
should not care what the SysV script wants or which rc.d directory it
is linked from, given that a native service of the same name exists.
We'll never execute the SysV script.

Michal


More information about the systemd-devel mailing list