From: "Gerhard Sittig"
... The rc script is called /sbin/init.d/firewall, and is called twice ....
There must be a reason. Have a look at what's between these invocations. I guess it's something changing the network setup which influences the packet filter, triggering it again will make it obey the new setup. ISDN, DHCP, ppp, et al come to mind. 'ls /sbin/init.d/rc3.d/S*' should give a clue.
yes, this is right, the splitting into three parts makes sense because the different status in runlevel, at first S01SuSEfirewall_init, then S07SuSEfirewall_setup and at least S99SuSEfirewall_final.
There is'nt a script firewall after package install.
What is the output of 'rpm -ql -p $RPMFILE'? And what is the output of 'rpm -ql $PACKAGE' after installation? Show what made you think that something's missing!
Another mysterious thing is the line ln -s /etc/rc.d/firewall /sbin/rcfirewall in the INSTALL script. This link shows to nothing.
Have you considered looking at 'file /etc/rc.d /sbin/init.d'? :)
You don't mention the distro you are using. Maybe that's where the irritation comes from?
There are two ways I see for installing SuSEfirewall, first the RPM from Suse distro (the last version I've found is 4.3), second the download from www.suse.de/~marc/ as tarball (recent version 4.6) with a script INSTALL. My irritation comes from the SuSEfirewall-technical.txt and the INSTALL script in the tarball. Line 42 in INSTALL makes the link shown below. I've take a further look at /sbin, there is also a link from /sbin/rcSuSEfirewall to /etc/rc.d/SuSEfirewall_final. So I think the correction of the SuSEfirewall-technical.txt was forgotten during the modification of the startup sequence. This link was'nt made from INSTALL probably from SuSEfirewall.rpm. O.k., however no longer confusion. The question now is how to stop/start/restart SuSEfirewall after modification the firewall.rc.config without rebooting ? I would do /etc/rc.d/SuSEfirewall_setup stop /etc/rc.d/SuSEfirewall_setup start /etc/rc.d/SuSEfirewall_final start is this right? Or is /etc/rc.d/SuSEfirewall_setup restart enough? In technical.txt is written thats right for modification on the fly, i.e. after ppp activation. I thought there is a one step restart, but I'm not sure how I should do it. Thank you for assistance, Frank