Something in SuSE 8.1 insists on changing the sequence of my start scripts in /etc/init.d/rc3.d and /etc/init.d/rc5.d to its idea of the perfect start order. What is it, where can I change it, and how can I get it to leave my sequence alone? It insists on starting my shorewall firewall before vmware, which causes a failure. -- _____________________________________ John Andersen
Hi, checkout YAST and insserv ;-( Both in Combination give some crazy results. Example: insserv -r nscd /etc/init.d/nscd stop Start yast ; stop yast reboot And wonder "nscd" is running again. And check out this Area in the start/stop script ;-) ### BEGIN INIT INFO # Provides: nscd # Required-Start: $remote_fs $time # X-UnitedLinux-Should-Start: $syslog $named # Required-Stop: # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Description: Start Name Service Cache Daemon ### END INIT INFO Greetings Dirk
-----Original Message----- From: John Andersen [mailto:jsa@pen.homeip.net] Sent: Wednesday, May 21, 2003 4:55 AM To: suse-security@suse.com Subject: [suse-security] What's keeps changing my inet.d sequence
Something in SuSE 8.1 insists on changing the sequence of my start scripts in /etc/init.d/rc3.d and /etc/init.d/rc5.d to its idea of the perfect start order.
What is it, where can I change it, and how can I get it to leave my sequence alone?
It insists on starting my shorewall firewall before vmware, which causes a failure.
-- _____________________________________ John Andersen
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
Dirk, To enable or disable a service you need the chkconfig command, e.g. chkconfig nscd off Altering the order the scripts run is harder, you need to edit the dependencies at the top of the files. Bob On Wed, 21 May 2003, Dirk Schreiner wrote:
Hi,
checkout YAST and insserv ;-( Both in Combination give some crazy results.
Example: insserv -r nscd /etc/init.d/nscd stop Start yast ; stop yast reboot
And wonder "nscd" is running again.
And check out this Area in the start/stop script ;-)
### BEGIN INIT INFO # Provides: nscd # Required-Start: $remote_fs $time # X-UnitedLinux-Should-Start: $syslog $named # Required-Stop: # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Description: Start Name Service Cache Daemon ### END INIT INFO
Greetings Dirk
-----Original Message----- From: John Andersen [mailto:jsa@pen.homeip.net] Sent: Wednesday, May 21, 2003 4:55 AM To: suse-security@suse.com Subject: [suse-security] What's keeps changing my inet.d sequence
Something in SuSE 8.1 insists on changing the sequence of my start scripts in /etc/init.d/rc3.d and /etc/init.d/rc5.d to its idea of the perfect start order.
What is it, where can I change it, and how can I get it to leave my sequence alone?
It insists on starting my shorewall firewall before vmware, which causes a failure.
-- _____________________________________ John Andersen
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
============================================================== Bob Vickers R.Vickers@cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691
On Wednesday 21 May 2003 02:02, Bob Vickers wrote:
Dirk,
To enable or disable a service you need the chkconfig command, e.g. chkconfig nscd off
Altering the order the scripts run is harder, you need to edit the dependencies at the top of the files.
But the chkconfig man page says its simply a frontend for insserv, so Dirks method (insserv -r ) should do just as well. Unless there is another database that contains the status of the "on and off" settings mentioned in man 8 chkconfig.??? -- _____________________________________ John Andersen
On Wednesday 21 May 2003 09:03, Dirk Schreiner wrote:
Hi,
checkout YAST and insserv ;-( Both in Combination give some crazy results.
Example: insserv -r nscd /etc/init.d/nscd stop Start yast ; stop yast reboot
And wonder "nscd" is running again.
Is START_NSCD="yes" in your /etc/rc.config? If so, running yast/SuSEconfig will re-insert the service for you. M -- "It's the small gaps between the rain that count, and learning how to live amongst them." -- Jeff Noon
Something in SuSE 8.1 insists on changing the sequence of my start scripts in /etc/init.d/rc3.d and /etc/init.d/rc5.d to its idea of the perfect start order. What is it, where can I change it, and how can I get it to leave my sequence alone?
Read man insserv -- James Ogley, Unix Systems Administrator, Pinnacle Insurance Plc Work: james.ogley@pinnacle.co.uk www.pinnacle.co.uk +44 (0) 20 8731 3619 Personal: james@rubberturnip.org.uk www.rubberturnip.org.uk Updated GNOME RPMs for SuSE Linux: www.usr-local-bin.org ********************************************************************** CONFIDENTIALITY.This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose, or store or copy the information in any medium. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Pinnacle Insurance plc. If you have received this email in error please immediately notify the Pinnacle Helpdesk on +44 (0) 20 8207 9555. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************
On Wednesday 21 May 2003 00:32, James Ogley wrote:
Something in SuSE 8.1 insists on changing the sequence of my start scripts in /etc/init.d/rc3.d and /etc/init.d/rc5.d to its idea of the perfect start order. What is it, where can I change it, and how can I get it to leave my sequence alone?
Read man insserv
But I never run it, (because I've discovered running it specifying a specific service file STILL causes it to adjust all files - Bug I think). So who/what is running insserv? -- _____________________________________ John Andersen
On Wednesday 21 May 2003 10:39, John Andersen wrote:
Read man insserv But I never run it, (because I've discovered running it specifying a specific service file STILL causes it to adjust all files - Bug I think).
So who/what is running insserv?
1) Read 'man insserv' 2) Repeat step 1) until you get it If you don't like the startup order, you need to modify the dependencies in the headers of the scripts that start the services. Not that I can think of a valid reason to do so, but it is possible. -- 51 N 25' 05.1" - 05 E 29' 13.3" Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57
On Wed, 2003-05-21 at 12:24, Arjen de Korte wrote:
On Wednesday 21 May 2003 10:39, John Andersen wrote:
Read man insserv But I never run it, (because I've discovered running it specifying a specific service file STILL causes it to adjust all files - Bug I think).
So who/what is running insserv?
1) Read 'man insserv' 2) Repeat step 1) until you get it
If you don't like the startup order, you need to modify the dependencies in the headers of the scripts that start the services. Not that I can think of a valid reason to do so, but it is possible.
Because some scripts NEED to start AFTER other scripts, I.E. webmin needs to start AFTER the network is up, but the default is to start before the network is up.
-- 51 N 25' 05.1" - 05 E 29' 13.3" Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57
On Wednesday 21 May 2003 18:59, Ken Schneider wrote:
If you don't like the startup order, you need to modify the dependencies in the headers of the scripts that start the services. Not that I can think of a valid reason to do so, but it is possible. Because some scripts NEED to start AFTER other scripts, I.E. webmin needs to start AFTER the network is up, but the default is to start before the network is up.
In that case, changing the startup order, may seem to work. It determines only the startup order of the scripts, it will NOT make sure the actual services are started. Therefor, if webmin can only start AFTER the network is up, you must verify that the network is up in the startup script of webmin. The bare fact that the webmin script is started after the network script will not guarantee this. I'm still not convinced of a valid reason to change the startup order. -- 51 N 25' 05.1" - 05 E 29' 13.3" Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57
On Wednesday 21 May 2003 09:24, Arjen de Korte wrote:
On Wednesday 21 May 2003 18:59, Ken Schneider wrote:
If you don't like the startup order, you need to modify the dependencies in the headers of the scripts that start the services. Not that I can think of a valid reason to do so, but it is possible.
Because some scripts NEED to start AFTER other scripts, I.E. webmin needs to start AFTER the network is up, but the default is to start before the network is up.
In that case, changing the startup order, may seem to work. It determines only the startup order of the scripts, it will NOT make sure the actual services are started. Therefor, if webmin can only start AFTER the network is up, you must verify that the network is up in the startup script of webmin. The bare fact that the webmin script is started after the network script will not guarantee this.
I'm still not convinced of a valid reason to change the startup order.
Are you trying to be difficult or does it come naturally? If webmin won't start before the network is up, then accepting the default of starting it before will yield a 100% failure rate. Verifying that network is up in the startup script (its probably already doing that) will, if the default are taken, always indicate that the network is down. You will have to deal with this problem each and every time you boot. The simple act of scheduling webmin to start later will alleviate this problem except in those cases where the network has failed to start, and in those cases you don't need webmin. If this is not a valid reason to change orders I would like to know which god I need pray to in order to be granted a "valid" reason. -- _____________________________________ John Andersen
On Thursday 22 May 2003 03:26, John Andersen wrote:
Are you trying to be difficult or does it come naturally?
:-)
If webmin won't start before the network is up, then accepting the default of starting it before will yield a 100% failure rate.
From the startup script of webmin-1.070-23: ### BEGIN INIT INFO # Provides: webmin # Required-Start: $network $syslog # Required-Stop: $network # Default-Start: 2 3 5 # Default-Stop: 0 1 6 # Description: Start or stop the Webmin server ### END INIT INFO There. Webmin already depends on $network, so it will not be started before the network startup script is run. If webmin fails to load with this setup (because the network is not up, although the script to start it must have been run before the webmin startup script) re-ordering likely will not help and you have to verify in the script that the network is actually up. Moving the webmin startup to somewhere later in the boot sequence will give a very unstable system, since you then depend on the delay caused by other startup scripts to allow for enough time for the network service to come up.Therefor, it makes no sense at all to me to try to shuffle the order of scripts around.
Verifying that network is up in the startup script (its probably already doing that) will,
No, it isn't. And that's where the problem lies... -- 51 N 25' 05.1" - 05 E 29' 13.3" Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57
On Wednesday 21 May 2003 22:15, Arjen de Korte wrote:
If webmin won't start before the network is up, then accepting the default of starting it before will yield a 100% failure rate.
From the startup script of webmin-1.070-23:
### BEGIN INIT INFO # Provides: webmin # Required-Start: $network $syslog # Required-Stop: $network # Default-Start: 2 3 5 # Default-Stop: 0 1 6 # Description: Start or stop the Webmin server ### END INIT INFO
There. Webmin already depends on $network, so it will not be started before the network startup script is run.
Those comments are ONLY used to set the order of the links, they do not affect anything at the time that the services in the runlevel (including webmin) are actually started. Therefore, if you see the webmin script linked into a runlevel BEFORE network, then It will still fail - regardless of what the comments say. Thats when you have to find out WHY insserv linked it into the runlevel in the wrong order, - and failing to get insserv to behave, you have to change the order yourself. As you know, the alphabetical order of the links in the /etc/init.d/rc?.d directory sets the order they are run. If those are wrong the Optimum way you make them right is setting the Required-Start list to include network and running insserv. insserv then attempts to change the order - if it condescends to work at all. In the Webmin example the Original Poster said his order started webmin prior to network, so clearly insserv failed to set the order in his case. I have a similar case. In my case, insserv insists on starting Shorewall AFTER vmware in spite of my having vmware as a pre-requsite to shorewall. That would be bad enough, I would just do the arangement the old fassion way (by hand) EXCEPT THAT something in the suse environment keeps undoing it. THATS the bit I was questioning. How to suppress that behavior. But the METHOD of changing the names (hence the order) of the runlevel scripts is all we are discussing, the fact that you MUST change the script name to change the order is a given. You see, this differes a great deal from your assertion that changing the order of the scrips (by virtue of the name change) is, in your opinion, unjustified. Changing the order is necessary, normal, and expected. -- _____________________________________ John Andersen
participants (7)
-
Arjen de Korte -
Bob Vickers -
Dirk Schreiner -
James Ogley -
John Andersen -
Ken Schneider -
Matt Gibson