When rebooting or shutting down system, or running rcfirewall2, the SuSEfirewall2 hangs while running rmmod. I can't kill the process and the cpu goes up 98%. Any ideas? root 23797 86.0 0.4 1584 552 pts/1 R 00:42 3:14 rmmod ipt_TCPMSS ipt_TOS ipt_MASQUERADE ipt_LOG ipt_state ipt_MARK ipt_MIRROR ipt_REDIRECT ipt_limit ipt_mac ipt_mark ipt_multiport ipt_owner ipt_tcpmss ipt_tos ipt_unclean ip_queue ip_nat_ftp ip_conntrack_ftp ipt_REJECT iptable_mangle iptable_nat iptable_filter ip_queue ip_conntrack iptable_filter ip_tables Haven't figured out what is making it hang. I then have to push reset -- _ _ __ _____ _____ ___| |_ | '__| / __\ \ /\ / / _ \/ _ \ __| -o) | | _ \__ \\ V V / __/ __/ |_ /\\ |_|(_) |___/ \_/\_/ \___|\___|\__|_\_v rsweet@socal.rr.com "unix soit qui mal y pense."
This has been reported before. It appears that you can comment this
section out of the SuSEfirewall2 script with no ill effect. Actually if you
waited between 15 and 20 minutes it would finish up and you would not
have to push reset. It does not hang, it just takes a very long time to
complete for some reason.
Jim
03/07/02 08:00:57 PM, Robert Sweet
When rebooting or shutting down system, or running rcfirewall2, the SuSEfirewall2 hangs while running rmmod. I can't kill the process and the cpu goes up 98%. Any ideas?
root 23797 86.0 0.4 1584 552 pts/1 R 00:42 3:14 rmmod ipt_TCPMSS ipt_TOS ipt_MASQUERADE ipt_LOG ipt_state ipt_MARK ipt_MIRROR ipt_REDIRECT ipt_limit ipt_mac ipt_mark ipt_multiport ipt_owner ipt_tcpmss ipt_tos ipt_unclean ip_queue ip_nat_ftp ip_conntrack_ftp ipt_REJECT iptable_mangle iptable_nat iptable_filter ip_queue ip_conntrack iptable_filter ip_tables
Haven't figured out what is making it hang. I then have to push reset
-- _ _ __ _____ _____ ___| |_ | '__| / __\ \ /\ / / _ \/ _ \ __| -o) | | _ \__ \\ V V / __/ __/ |_ /\\ |_|(_) |___/ \_/\_/ \___|\___|\__|_\_v rsweet@socal.rr.com "unix soit qui mal y pense."
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Friday 08 March 2002 19.08, James Bliss wrote:
This has been reported before. It appears that you can comment this section out of the SuSEfirewall2 script with no ill effect. Actually if you waited between 15 and 20 minutes it would finish up and you would not have to push reset. It does not hang, it just takes a very long time to complete for some reason.
I've found that if I manually rmmod all network modules (rcnetwork stop, rmmod 8139too etc etc etc) before shutting down the firewall it runs through without a problem //Anders
Do you have a script that does this? Also, do you have any idea as to why
this is happening? Seems like a bug of sorts.
Thanks,
Jim
03/08/02 01:39:44 PM, Anders Johansson
On Friday 08 March 2002 19.08, James Bliss wrote:
This has been reported before. It appears that you can comment this section out of the SuSEfirewall2 script with no ill effect. Actually if you waited between 15 and 20 minutes it would finish up and you would not have to push reset. It does not hang, it just takes a very long time to complete for some reason.
I've found that if I manually rmmod all network modules (rcnetwork stop, rmmod 8139too etc etc etc) before shutting down the firewall it runs through without a problem
//Anders
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Saturday 09 March 2002 02.16, James Bliss wrote:
Do you have a script that does this? Also, do you have any idea as to why this is happening? Seems like a bug of sorts.
No script, I just hardcoded all rmmods in /sbin/SuSEfirewall2. There are probably better solutions, and hopefully 8.0 will have it. I don't shut down that often, so I didn't feel it was too important. The "why" is most likely that the network kernel threads are somewhere inside the iptables/ipchains module (even with all network related userspace programs shut down, the Used By column is still not 0 for the iptables modules). I don't think it's a bug there, I just think that the proper order of shutdown is to take away the network before shutting down the firewall. Sometimes you have to do things in the proper order. //Anders
On Fri, Mar 08, 2002 at 12:08:26PM -0600, James Bliss beat on the keyboard:
This has been reported before. It appears that you can comment this section out of the SuSEfirewall2 script with no ill effect. Actually if you waited between 15 and 20 minutes it would finish up and you would not have to push reset. It does not hang, it just takes a very long time to complete for some reason.
Jim
The strange thing is, it doesn't always do it. It is a kind of a pain in the arse when you need to shut the firewall down. I have been testing a lot of netork things so sometimes I need to shut the firewall down just to see if that is blocking whatever I am testing. -- _ _ __ _____ _____ ___| |_ | '__| / __\ \ /\ / / _ \/ _ \ __| -o) | | _ \__ \\ V V / __/ __/ |_ /\\ |_|(_) |___/ \_/\_/ \___|\___|\__|_\_v rsweet@socal.rr.com "unix soit qui mal y pense."
participants (3)
-
Anders Johansson
-
James Bliss
-
Robert Sweet