SuseConfig changes firewall startscript boot order
Hello, Does anybody know how the program SuSEConfig determines how to change the Sxx and Kxx start and kill scripts in /etc/rc.d/rcX.d ? The problem is that I created my own firewall script and it only works when my network has started. So I create a SxxFirewall startcript where xx is a number higher than my Sxxnetwork script. In /etc/rc.config I ceated the line START_FIREWALL="yes", and all works fine......Until I run (or Yast runs) SuseConfig. SuSEConfig changes the Sxx and Kxx number to S01 and K01. So after SuseConfig has run, my firewall start before my network and the stuff dous not wordk anymore. I have to manualy change the S01 and K01 to higher numbers. Kan anybody give me some advise abiut this behavior? I know this is not a real security question, but I'm realy in need of a solution in this case becouse the system I'm working on is on a remote location and if the firewall script fails, security is broken.... Thanks. Dave
On Wednesday, 28. November 2001 17:38 Dave Woutersen wrote:
I have to manualy change the S01 and K01 to higher numbers. Kan anybody give me some advise abiut this behavior?
read the init.d (7) and insserv (8) manpage. Peter
participants (2)
-
Dave Woutersen
-
Peter Wiersig