How they were started does not seem to have much to do with chkconfig.
The init system used a series of hard-coded numbers in the init scripts
to judge which services were to be started in which sequence, which was
a horrible mess.
You had to make sure the service X's priority of 37 was in between
service Y'x priority of 18 and service Z's priority of 56.
With systemd, you just say things like:
After=syslog.target network.target auditd.service
and/or
Before=poweroff.service reboot.service halt.service
Which is MUCH more concise and easy to understand. The computer figures
it all out, instead of the user having to juggle priority levels.
Also, all init scripts with priorities > 37 would all have to wait for
the "service X" to finish. This is not so with systemd. The service
files specify the minimum dependencies. If service Z does not require
service X, it can go ahead, even if service X gets delayed.
See?
- Mike
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
