-----Original Message----- From: Scott Leighton [mailto:helphand@pacbell.net] Sent: Sunday, February 13, 2005 9:11 PM To: suse-linux-e@suse.com Subject: Re: [SLE] insserv broken?
On Sunday 13 February 2005 11:14 am, Anders Norrbring wrote:
If you should define $ALL in there, you'd have to add every distribution script, PLUS all your own.. I think $ALL should just make insserv put your script at the highest possible S-value..
Well, I did some googling and some reading of the LSB on boot facility names http://www.linuxbase.org/modules.php?name=specrev&url=http://www.linuxbase .org/spec//booksets/LSB-Core-generic/LSB-Core-generic.html
I couldn't find any mention anywhere of $all as a valid facility.
From the /etc/init.d/skeleton file:
# * When specifying hard dependencies or ordering requirements, you can # use names of services (contents of their Provides: section) # or pseudo names starting with a $. The following ones are available # according to LSB (1.1): # $local_fs all local file systems are mounted # (most services should need this!) # $remote_fs all remote file systems are mounted # (note that /usr may be remote, so # many services should Require this!) # $syslog system logging facility up # $network low level networking (eth card, ...) # $named hostname resolution available # $netdaemons all network daemons are running # The $netdaemons pseudo service has been removed in LSB 1.2. # For now, we still offer it for backward compatibility. # These are new (LSB 1.2): # $time the system time has been set correctly # $portmap SunRPC portmapping service available # UnitedLinux extensions: # $ALL indicates that a script should be inserted # at the end Apparently I overlooked that $ALL is a UnitedLinux extension, nevertheless I think it's kind of confusing to put it in the skeleton file for a non-UL distribution. My mistake.. Anders.