| |||||||||||||
|
| |||||||||||||
SUSE has been doing this for agesSUSE has been doing this for agesPosted Jan 18, 2008 2:12 UTC (Fri) by wildpossum (guest, #17744)Parent article: Reordering the boot for fun and profit
SUSE init scripts have dependency metadata at the top. ### BEGIN INIT INFO # Provides: FOO # Required-Start: $syslog $remote_fs # Should-Start: $time ypbind smtp # Required-Stop: $syslog $remote_fs # Should-Stop: $time ypbind smtp # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Short-Description: FOO XYZ daemon providing ZYX # Description: Start FOO to allow XY and provide YZ # continued on second line by '#<TAB>' # should contain enough info for the runlevel editor # to give admin some idea what this service does and # what it's needed for ... # (The Short-Description should already be a good hint.) ### END INIT INFO The ordering of the scripts is done by SuSEconfig, not dynamically though. This can be triggered by insserv. This dependency ordering is why one FAQ on SUSE forums is how to add a numbered symlink in the runlevel directory and the answer is why one should not do that but create an init script with metadata.
(Log in to post comments)
init.d script comment block part of LSB Posted Jan 21, 2008 5:26 UTC (Mon) by pjm (subscriber, #2080) [Link] This comment block is part of the Linux Standard Base (http://refspecs.linux-foundation.org/LSB_3.1.0/LSB-Core-g...), so quite a few distributions will have such comment blocks to some extent; indeed, such comment blocks form the input to the reordering that the article describes.
|
|
||||||||||||