Description of problem:

The new iptables init script calls modprobe -r to unload modules when stopping.
Unfortunately this causes a hang at "modprobe -r" (with e.g. the ipt_state
module) after e.g. "service iptables restart":

nils@wombat:~> sudo service iptables restart
Flushing firewall rules:                                   [  OK  ]
Setting chains to ACCEPT policy:                           [  OK  ]
Unloading iptables modules:Terminated [<-- had to kill script here]
nils@wombat:~> sudo su -
root@wombat:~> lsmod |grep ipt
iptable_filter          2444   0  (autoclean)
ip_tables              15264   1  [iptable_filter]
root@wombat:~> ps auxw|grep mod
nils      2336  0.0  1.3 17732 7032 ?        S    14:34   0:00
/usr/libexec/modemlights_applet2
--oaf-activate-iid=OAFIID:GNOME_ModemLightsApplet_Factory --oaf-ior-fd=26
root      2847 91.0  0.1  3348  824 pts/3    R    14:36   4:38 modprobe -r ipt_state
root      3370  0.0  0.1  4660  668 pts/3    S    14:41   0:00 grep mod
root@wombat:~> lsmod|grep ipt_stat

As you can see, modprobe apparently goes into an endless loop even after
successfully removing the module as per "lsmod" (I also had it looping with the
module to be removed listed as "(deleted)", but that was with a kernel from RHL9).

Version-Release number of selected component (if applicable):

modutils-2.4.25-8
kernel-2.4.21-20.1.2024.2.1.nptl   (module gets removed in "lsmod")
kernel-2.4.20-18.9                 (module is "(deleted)" in "lsmod")
iptables-1.2.8-6.1

How reproducible:

Easy.

Steps to Reproduce:
1. Boot system
2. Start iptables
3. Stop iptables
    
Actual results:

See above

Expected results:

Modules get unloaded, iptables script doesn't hang.