Bugzilla – Bug 115848
New sort of RequiredStart
Last modified: 2008-07-16 17:33:11 UTC
the init.d infos should have a field to define the order, e.g. something like RequiredStart, but without really needing it and only serving as an order mark. E.g. /etc/init.d/syslog: CURRENTLY RequiredStart: $network COULD BE: MustComeAfter: $network This is because syslog does not need 'network', only the lo interface, which is already set up during boot.localnet.
No it must not. Think twice you really do not need this. and therefore the LSB specs do not define this. Btw: The syslog _reqires_ networkl to be able to log over network to a remote log server, compare with the manual of syslogd.
Well this wasnot related to syslog really. The feature request is basically to have a field to define depencendies. If these dependencies are not started, that's ok, but the boot order is important. Not for syslog, but for general apps.
Believe me: the kausal order is always correct, if you switch between cause and impact you'll get the backward order. Think about make and Makefiles.
I do not know what you wanted to say by that, but to put it concretely: I've got my firewall which currently has RequiredStart: $network named named, because it resolves hostnames. However, there are also linux clients without a named and just libresolv (/etc/resolv.conf), therefore, the "named" in the RequiredStart would be a hindrance. Resolving would work anyway because of the properly setup resolv.conf.
Use Should-Start