FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 04-23-2008, 08:49 PM
Mike Cronenworth
 
Default Network filesystems need to get unmounted earlier at shutdown

-------- Original Message --------
Subject: Network filesystems need to get unmounted earlier at shutdown
From: Orion Poplawski <orion@cora.nwra.com>
To: Development discussions related to Fedora Core
<fedora-devel-list@redhat.com>

Date: 04/23/2008 03:20 PM

This is the biggest issue for me at the moment in Fedora (8 & 9) -
NetworkManager gets stopped (and the network shut down) way before
network filesystems (in my case nfs mounted by autofs, but others as
well) are unmounted.


See https://bugzilla.redhat.com/show_bug.cgi?id=218237 for more info.

Anyone have any suggestions?




As mentioned in the bug you linked, remove NM from runlevel 0 and 6 to
prevent it from being killed. It will die when the system shuts
down/reboots. Hopefully "upstart" will help restructure the badly
structured initscripts setup.


Regards,
Mike

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-23-2008, 09:38 PM
Orion Poplawski
 
Default Network filesystems need to get unmounted earlier at shutdown

Mike Cronenworth wrote:
As mentioned in the bug you linked, remove NM from runlevel 0 and 6 to
prevent it from being killed. It will die when the system shuts
down/reboots. Hopefully "upstart" will help restructure the badly
structured initscripts setup.


Aside from doing "rm /etc/rc[06].d/K??NetworkManager", how does one
"remove NM from runlevel 0 and 6" permanently with upstart?


--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-23-2008, 11:10 PM
Mike Cronenworth
 
Default Network filesystems need to get unmounted earlier at shutdown

-------- Original Message --------
Subject: Re:Network filesystems need to get unmounted earlier at shutdown
From: Orion Poplawski <orion@cora.nwra.com>
To: Development discussions related to Fedora <fedora-devel-list@redhat.com>
Date: 04/23/2008 04:38 PM

Mike Cronenworth wrote:
As mentioned in the bug you linked, remove NM from runlevel 0 and 6
to prevent it from being killed. It will die when the system shuts
down/reboots. Hopefully "upstart" will help restructure the badly
structured initscripts setup.


Aside from doing "rm /etc/rc[06].d/K??NetworkManager", how does one
"remove NM from runlevel 0 and 6" permanently with upstart?


Bah, ignore what I said. You should be able to just turn NM from "off"
to "on" on those runlevels and then when the init level changes, init
won't bother with NM. I don't wish to test this, but it sounds correct
in theory...


chkconfig --level 06 NetworkManager on
chkconfig --level 06 NetworkManagerDispatcher on

I don't have my F9 preview machine with me, but upstart uses
compatibility with SysV stuff IIRC so this should work for you.


Mike

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-24-2008, 03:01 AM
Bill Nottingham
 
Default Network filesystems need to get unmounted earlier at shutdown

Mike Cronenworth (mike@cchtml.com) said:
> Bah, ignore what I said. You should be able to just turn NM from "off" to
> "on" on those runlevels and then when the init level changes, init won't
> bother with NM. I don't wish to test this, but it sounds correct in
> theory...
>
> chkconfig --level 06 NetworkManager on
> chkconfig --level 06 NetworkManagerDispatcher on
>
> I don't have my F9 preview machine with me, but upstart uses compatibility
> with SysV stuff IIRC so this should work for you.

Also, just resetting the priorities of hal & NM should do it.

Bill

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-24-2008, 07:35 PM
Orion Poplawski
 
Default Network filesystems need to get unmounted earlier at shutdown

Bill Nottingham wrote:
Mike Cronenworth (mike@cchtml.com) said:
Bah, ignore what I said. You should be able to just turn NM from "off" to
"on" on those runlevels and then when the init level changes, init won't
bother with NM. I don't wish to test this, but it sounds correct in
theory...


chkconfig --level 06 NetworkManager on
chkconfig --level 06 NetworkManagerDispatcher on

I don't have my F9 preview machine with me, but upstart uses compatibility
with SysV stuff IIRC so this should work for you.


Also, just resetting the priorities of hal & NM should do it.

Bill



yeah, can we do that please? If NM doesn't get stopped before dbus it
segfaults and spews to the console, so maybe K84 for NM (although
network is currently at K90)? Looks like it is at 73 currently which
after autofs (yay!) but not before netfs at 75.


Bigger problems with recent NM for F8 because chkconfig seems to insist
on putting it at S99 and K01 due to LSB init tags I assume.


I don't know what new capabilities upstart gives us, but looks like a
major review of startup/shutdown order is called for in F10.


--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 

Thread Tools




All times are GMT. The time now is 07:24 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org