SuSEconfig and /etc/init.d
Hi, I've looked through all the sysconfig options in Yast2, but I cannot find what causes SuSEconfig to reset my custom scripts in /etc/init.d Any time the system runs SuSEconfig, my links in /etc/init.d/rc5.d (and rc3.d) get reset to S01. For example, S12postgresql is changed to S01postgresql. This is inconvenient as the network doesn't start until S05network. Is there a way I can tell SuSEconfig to stop this? It doesn't seem to mind the stop scripts.... Thanks, Josh Trutwin http://trutwins.homeip.net
* Josh Trutwin (josh@trutwins.homeip.net) [030116 16:46]:
I've looked through all the sysconfig options in Yast2, but I cannot find what causes SuSEconfig to reset my custom scripts in /etc/init.d
See insserv(8)...you need to add the init info to your scripts. -- -ckm
On Thu, Jan 16, 2003 at 06:46:34PM -0600, Josh Trutwin wrote:
Hi,
I've looked through all the sysconfig options in Yast2, but I cannot find what causes SuSEconfig to reset my custom scripts in /etc/init.d
Any time the system runs SuSEconfig, my links in /etc/init.d/rc5.d (and rc3.d) get reset to S01. For example, S12postgresql is changed to S01postgresql. This is inconvenient as the network doesn't start until S05network. Is there a way I can tell SuSEconfig to stop this? It doesn't seem to mind the stop scripts....
Instead of assigning number manually you might want to put appropriate headers into your script--please see man page for insserv. The headers look like: ### BEGIN INIT INFO # Provides: boot_facility_1 [ boot_facility_2 ...] # Required-Start: boot_facility_1 [ boot_facility_2 ...] # Required-Stop: boot_facility_1 [ boot_facility_2 ...] # Default-Start: run_level_1 [ run_level_2 ...] # Default-Stop: run_level_1 [ run_level_2 ...] # Description: multiline_description ### END INIT INFO Based on dependencies specified in the headers insserv will calculate S?? number appropriate for your script. HTH, -Kastus
On Thu, Jan 16, Josh Trutwin wrote:
Hi,
I've looked through all the sysconfig options in Yast2, but I cannot find what causes SuSEconfig to reset my custom scripts in /etc/init.d
Any time the system runs SuSEconfig, my links in /etc/init.d/rc5.d (and rc3.d) get reset to S01. For example, S12postgresql is changed to S01postgresql. This is inconvenient as the network doesn't start until S05network. Is there a way I can tell SuSEconfig to stop this? It doesn't seem to mind the stop scripts....
You cannot stop SuSEconfig to do so, because SuSEconfig has really nothing to do with this. You should read: man insserv man chkconfig and adjust your custom scripts with adding a LSB conform header. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
On 2003.01.17 01:46 Josh Trutwin wrote:
Any time the system runs SuSEconfig, my links in /etc/init.d/rc5.d (and rc3.d) get reset to S01. For example, S12postgresql is changed to
It is documented: read "/etc/init.d/README" for starters. -- Cheers, Carlos Robinson
participants (5)
-
Carlos E. R.
-
Christopher Mahmood
-
Josh Trutwin
-
Konstantin (Kastus) Shchuka
-
Thorsten Kukuk