FC2T3 Shut down / reboot taking much longer to complete

[A1tmblwd at netscape.net]

Wayne Steenburg <w.steenburg at myactv.net> wrote:

>On Sat, 2004-05-01 at 16:54, A1tmblwd at netscape.net wrote:
>> Wayne Steenburg <w.steenburg at myactv.net> wrote:
>> 
>> >On Sat, 2004-05-01 at 01:13, A1tmblwd at netscape.net wrote:
>> >> After upgrading from FC1 to FC2T3 the shuting down / reboot process is taking much longer to complete.  The slow down begins when the message "Shutting down system logger" appears. Termiation of the process takes a minute or more. Then each of the following processes, "Shutting down interface eth0", "Shutting down loopback interface", and "Stopping iptables" exhibit similar behavior.  Termination of these four processes takes minutes to complete.  Whereas in the past it took only seconds.
>> >> 
>> >> Firewall and iptables are enabled.  SELinux is disabled.
>> >> 
>> >> What is causing the slowdown?  What do I need to do to get back the responsiveness of FC1?
>> >> 
>> >If your /home directory is on a separate partition or you have the
>> >diskspace necessary to backup your data, I would try a fresh install
>> >instead of an upgrade.
>> >
>> >
>> 
>> Thanks, that's the easy way out.  I really want to know what is causing the problem.  It's probably something the developers made to accomodate SELinux but haven't quite got working correctly.  It would be nice if the developers could fix it before the official release.
>> 
>> 
>I understand.  On my system (Soyo board with a KT-600 chipset) rebooting
>doesn't work. I've tried acpi=off apm=off and such to no avail.  I'd
>like to have that work properly as well.
>

I tried using system-config-securitylevel to turn off the firewall.  This had no effect on the shutdown time.  Found that running the utility re-enabled SELinux (already in bugzilla?) and that I need to "disable" SELinux before exiting the utility.  Also disabling SELinux via system-config-securitylevel has not effect.  On rebooting SELinux is still active.  Need to add "selinux=0" to boot parameters in grub. 

I examined /etc/rc.d/init.d/network.  The script on my FC2T3 system still has a reference to /etc/modules.conf.  I think it should now reference modprobe.conf.  Also the script differs from the one on my FC1 system as follows:

114d113
<                       unset DEVICE TYPE SLAVE BRIDGE
119d117
<                       unset DEVICE TYPE SLAVE BRIDGE
125d122
<                       unset DEVICE TYPE SLAVE BRIDGE
130d126
<                       unset DEVICE TYPE SLAVE BRIDGE
133d128
<               unset DEVICE TYPE SLAVE BRIDGE
214d208
<                       unset DEVICE TYPE BRIDGE
219d212
<                       unset DEVICE TYPE BRIDGE
224d216
<                       unset DEVICE TYPE BRIDGE
227d218
<               unset DEVICE TYPE BRIDGE

Don't know what it all means.  Could be just the differencs in the two motherboards.  For all I know anaconda may not have even updated /etc/rc.d/init.d/network.  The file has a Jan 28 date.


__________________________________________________________________
Introducing the New Netscape Internet Service. 
Only $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need. 

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp