• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Consequences of not stopping my firewall script at shutdown?

M

MGMorden

Diamond Member
I'm running Slackware 8.1 and decided to put a firewall on my machine (it was running behind another machine that had a firewall so I hadn't bothered but I'm now moving it to it's own net connection so I want to get the fw up and running). I've got a script from the web and tweaked it to my likings, and it appears to work fine. Only one thing doesn't seem to work right: stopping it. It takes the standard start/stop arguments. I have the machine setup to start the script automatically at boot time and that works fine. If I stop it manually from the commandline that works fine too. BUT, if I pass the stop argument from my shutdown script something goes wrong (gives the message: "INIT: no more processes at this runlevel". The machine never powers down, and more importantly, never unmounts the filesystems. For right now I've just taken out the line (so I never stop the script). What are the consequences of such an action?
 
I don't think there would be any problems with shutdown your system without disabling the firewall.
What does your script look like?

Init should kill off all of the active proccesses and then shutdown your system, how do you start the script?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top