Carlos E. R. wrote:
On Thursday, 2013-10-31 at 10:31 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On Thursday, 2013-10-31 at 09:53 +0100, Per Jessen wrote:
Ah, it wouldn't matter - still, priority 50 for everything seems unusual?
It is probably ignored, anyway.
The priority or the service (or both) ?
The priority. Systemd native services have no numbers, where to start a service in relation to other is determined, I think, dynamically based on the service file definitions.
Old systemv services have no corresponding systemd file, unless it is autocreated by systemd. The numbers in it have no meaning for systemd, as there are no numbers for the rest of services to compare with.
So, either prioriy is determined correctly by systemd somehow, or they are started somewhere in the middle. I guess the former.
Hmm, that sounds somewhat plausible. I found this: http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities/
LSB header dependency information matters. The SysV implementations on many distributions did not use the dependency information encoded in LSB init script headers, or used them only in very limited ways. Due to that they are often incorrect or incomplete. systemd however fully interprets these headers and follows them closely at runtime (and not at installation time like some implementations).
Which seems to imply that the priorities do not matter. -- Per Jessen, Zürich (7.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org