systemd: bugreports for missing service-files

Lennart Poettering mzerqung at 0pointer.de
Mon Jun 20 22:40:39 UTC 2011


On Tue, 21.06.11 00:15, Reindl Harald (h.reindl at thelounge.net) wrote:

> >> because there are a lot of services in LSB-Mode i filed for everyone a
> >> bugreport  - sad to see that most packages are not F15 ready
> > 
> > systemd reads SysV/LSB init scripts as alternative configuration source if
> > no native unit file is available for a service. 
> 
> it does not respect the start-order in tis case and fires services
> up like a blind butcher - thi smay be enough for a simple desktop
> but NOT if you have services depending on each other and started
> means NOT ready for connections
> 
> means: it reads them and fires up braindead with only speed in mind

systemd is actually quite smart about this and uses LSB header
information if it is available (as did chkconfig btw), falling back to
the startup priority values if a pair of services does not care any LSB
information at all.

As long as the LSB information that is included is reliable systemd will
do the right thing. systemd relies more on correct LSB information than
chkconfig did, but that doesn't change the fact that both want that.

> below a well defined and since years working starting order
> and now tell me how this will work with your blind "i fire up
> every service as fast as i can to make boot 5 seconds faster"
> when the result is nothing orks as expected?

If there are dependencies missing, then they should be added to the
respective init script headers, please file bugs against the respective
packages.

> so we come to the next major problem:
> https://bugzilla.redhat.com/show_bug.cgi?id=714525
> it does not really matter for the admin who and why fires up mysqld in
> this case - if i say "systemctl stop mysqld" i mean this exactly so,
> everytime in everycase and systemd has to respect this!

As Michal and I independently verified systemd is actually behaving
correctly here, and you are running into a different problem, most
likely because mysql is autospawned on your activated socket.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.


More information about the devel mailing list