On Monday 23 June 2014, jdd wrote:
Le 19/06/2014 03:08, Rodney Baker a écrit :
With SysV Init, one could fairly easily control the order in which services were started (at boot) and killed (at shutdown) simpy by changing the Sxx or Kxx prefix of the scripts in /etc/rc.d/init.d (or /etc/init.d, depending on your distro),
this was no more true, at least for openSUSE and for years, now. There already was requires of some sort inside the init scripts.
my understanding is that systemd was build to solve the dependency problems these init scripts are making, specially in our days where devices are hotplugged.
example, the mysql script (still present in 13.1)
### BEGIN INIT INFO # Provides: mysql # Required-Start: $network $remote_fs # Required-Stop: $network $remote_fs # Default-Start: 3 5 # (...)
This was only used for _creating_ these numbered links (insserv) but not when executing. In /etc/sysconfig/boot we had also the feature RUN_PARALLEL="no" I'm really missing it nowadays because it would avoid a lot of the systemd weiredness they same way we did it for sysvinit/startpar. Actually I have no motivation to correct any single init dependency. It's not worth to do this on my systems which have usually several months uptime. The most easy maintainable use case to have some simple sequentially executed tasks is gone ... cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org