Re: [suse-security] What's keeps changing my inet.d sequence (not entirely security related)
On Wednesday 21 May 2003 01:11, Matt Gibson wrote:
To get it to apply the right sequence, check the "### BEGIN INIT INFO" section of the script. If you specify in there that it depends on the firewall (use the Required-Start line to specify whatever's in the Provides line in the firewall script) then it should get automatically shuffled into the right place. Check out the init.d and insserv man pages for more details.
Ah, now if that works it would be great. The man pages left the impression that only those services mentioned in the /etc/insserv.conf could be mentioned there And my tests with the following in the firewall script: # Provides: shorewall # Required-Start: $network vmware # Required-Stop: # Default-Start: 2 3 5 # Default-Stop: 0 1 6 # Description: starts and stops the shorewall firewall Were unsuccessfull in getting the thing to force vmware to load first. Infact the insserv -d command halted saying vmware was not enabled, yet chkconfig said it was. Maddening. If i manually set it and stay away from insserv it will stay put, but one trip thru yast and I have to adjust it again. thx anyway. -- _____________________________________ John Andersen
John Andersen wrote:
And my tests with the following in the firewall script: # Provides: shorewall # Required-Start: $network vmware
Were unsuccessfull in getting the thing to force vmware to load first.
And could you show us the info section of /etc/init.d/vmware, too? Peter
On Thu, 2003-05-22 at 04:46, Peter Wiersig wrote:
John Andersen wrote:
And my tests with the following in the firewall script: # Provides: shorewall # Required-Start: $network vmware
I may be wrong but, isn't the "# Required-Start:" part looking for variables? Here you have "$network and vmware", so wouldn't "$network $vmware" make more sense? -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998
Ken Schneider wrote:
Here you have "$network and vmware", so wouldn't "$network $vmware" make more sense?
No, that makes no sense. The $ is the sign for an system script whereas vmware is a direct link to a named runlevel script. In /etc/insserv.conf is defined which real script provides the System Facility (those are predefined in the LSB, so that the name is equal in all compliant distributions.) Read the LSB ( http://www.linuxbase.org ) and the insserv manpage for details. Peter
On Friday 23 May 2003 16:31, Peter Wiersig wrote:
Ken Schneider wrote:
Here you have "$network and vmware", so wouldn't "$network $vmware" make more sense?
No, that makes no sense. The $ is the sign for an system script whereas vmware is a direct link to a named runlevel script.
No, Peter, that's the same mistake I made, and it is why I started this thread. You are right about the $ bit (groups of services defined in /etc/insserv.conf) but the vmware does not refer to a script it refers to the name of something some other script PROVIDES. In this case, the Provides in the vmware script is named VMware and if you don't get the capitalization right things go wrong. -- _____________________________________ John Andersen
participants (3)
-
John Andersen -
Ken Schneider -
Peter Wiersig