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 05-30-2008, 08:54 AM
"Valent Turkovic"
 
Default Networkmanager service is shutdown too early

During the boot I have some samba shares mounted because I have them
configured to mount via fstab file.

When I shutdown or reboot I get a screen for 2-3 minutes that shows
smbfs service trying to unmount samba shares but NM service has
already shutdown and there is no working network connection

I have seen this "bad" behaviour in F8 and have reported it on this
mailinglist, but I hoped that the new and smarter NM would take care
of it, but unfortunately it didn't

So:
https://bugzilla.redhat.com/show_bug.cgi?id=449070

Cheers,
Valent.

--
http://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-30-2008, 05:32 PM
Dan Williams
 
Default Networkmanager service is shutdown too early

On Fri, 2008-05-30 at 10:54 +0200, Valent Turkovic wrote:
> During the boot I have some samba shares mounted because I have them
> configured to mount via fstab file.
>
> When I shutdown or reboot I get a screen for 2-3 minutes that shows
> smbfs service trying to unmount samba shares but NM service has
> already shutdown and there is no working network connection
>
> I have seen this "bad" behaviour in F8 and have reported it on this
> mailinglist, but I hoped that the new and smarter NM would take care
> of it, but unfortunately it didn't

Probably need to adjust the stop priorities of NM and haldaemon to be
right after messagebus (K85) rather than where they currently are...
The problem is that NM is being stopped to early.

Dan

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-30-2008, 05:41 PM
Bill Nottingham
 
Default Networkmanager service is shutdown too early

Dan Williams (dcbw@redhat.com) said:
> On Fri, 2008-05-30 at 10:54 +0200, Valent Turkovic wrote:
> > During the boot I have some samba shares mounted because I have them
> > configured to mount via fstab file.
> >
> > When I shutdown or reboot I get a screen for 2-3 minutes that shows
> > smbfs service trying to unmount samba shares but NM service has
> > already shutdown and there is no working network connection
> >
> > I have seen this "bad" behaviour in F8 and have reported it on this
> > mailinglist, but I hoped that the new and smarter NM would take care
> > of it, but unfortunately it didn't
>
> Probably need to adjust the stop priorities of NM and haldaemon to be
> right after messagebus (K85) rather than where they currently are...
> The problem is that NM is being stopped to early.

'After netfs' should be good enough. Although netfs stop should possibly
do lazy umounts.

Bill

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-30-2008, 05:46 PM
Dan Williams
 
Default Networkmanager service is shutdown too early

On Fri, 2008-05-30 at 13:41 -0400, Bill Nottingham wrote:
> Dan Williams (dcbw@redhat.com) said:
> > On Fri, 2008-05-30 at 10:54 +0200, Valent Turkovic wrote:
> > > During the boot I have some samba shares mounted because I have them
> > > configured to mount via fstab file.
> > >
> > > When I shutdown or reboot I get a screen for 2-3 minutes that shows
> > > smbfs service trying to unmount samba shares but NM service has
> > > already shutdown and there is no working network connection
> > >
> > > I have seen this "bad" behaviour in F8 and have reported it on this
> > > mailinglist, but I hoped that the new and smarter NM would take care
> > > of it, but unfortunately it didn't
> >
> > Probably need to adjust the stop priorities of NM and haldaemon to be
> > right after messagebus (K85) rather than where they currently are...
> > The problem is that NM is being stopped to early.
>
> 'After netfs' should be good enough. Although netfs stop should possibly
> do lazy umounts.

Ok, just need to bump NM a few bits later it looks like; might as well
be K84 to be right after messagebus.

Dan

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-30-2008, 05:59 PM
Bill Nottingham
 
Default Networkmanager service is shutdown too early

Dan Williams (dcbw@redhat.com) said:
> > 'After netfs' should be good enough. Although netfs stop should possibly
> > do lazy umounts.
>
> Ok, just need to bump NM a few bits later it looks like; might as well
> be K84 to be right after messagebus.

Well, NM will exit anyway when the messagebus exits, will it not?

Bill

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-30-2008, 06:24 PM
Dan Williams
 
Default Networkmanager service is shutdown too early

On Fri, 2008-05-30 at 13:59 -0400, Bill Nottingham wrote:
> Dan Williams (dcbw@redhat.com) said:
> > > 'After netfs' should be good enough. Although netfs stop should possibly
> > > do lazy umounts.
> >
> > Ok, just need to bump NM a few bits later it looks like; might as well
> > be K84 to be right after messagebus.
>
> Well, NM will exit anyway when the messagebus exits, will it not?

No, because the Debian guys got all cranky and want NM to handle dbus
dropouts, because if they need to restart dbus because of a security
issue they don't want that to take down the entire machine including
networking. So there's code to poll the bus every so often and try to
reconnect if NM gets disconnected (either due to an NM error like
sending a non-UTF8 string over the bus or if dbus quits/dies).

Dan

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-30-2008, 06:47 PM
Kostas Georgiou
 
Default Networkmanager service is shutdown too early

On Fri, May 30, 2008 at 01:46:42PM -0400, Dan Williams wrote:

> On Fri, 2008-05-30 at 13:41 -0400, Bill Nottingham wrote:
> > Dan Williams (dcbw@redhat.com) said:
> > > On Fri, 2008-05-30 at 10:54 +0200, Valent Turkovic wrote:
> > > > During the boot I have some samba shares mounted because I have them
> > > > configured to mount via fstab file.
> > > >
> > > > When I shutdown or reboot I get a screen for 2-3 minutes that shows
> > > > smbfs service trying to unmount samba shares but NM service has
> > > > already shutdown and there is no working network connection
> > > >
> > > > I have seen this "bad" behaviour in F8 and have reported it on this
> > > > mailinglist, but I hoped that the new and smarter NM would take care
> > > > of it, but unfortunately it didn't
> > >
> > > Probably need to adjust the stop priorities of NM and haldaemon to be
> > > right after messagebus (K85) rather than where they currently are...
> > > The problem is that NM is being stopped to early.
> >
> > 'After netfs' should be good enough. Although netfs stop should possibly
> > do lazy umounts.
>
> Ok, just need to bump NM a few bits later it looks like; might as well
> be K84 to be right after messagebus.

Why not go all the way to 90 as network to be on the safe side? With a
quick look I can see some scripts that might not be happy if the network
is down with a priority above 84, racoon/dund/rdisc/rpcgssd/nasd for example.

Kostas

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-30-2008, 06:50 PM
"Clyde E. Kunkel"
 
Default Networkmanager service is shutdown too early

Valent Turkovic wrote:

During the boot I have some samba shares mounted because I have them
configured to mount via fstab file.

When I shutdown or reboot I get a screen for 2-3 minutes that shows
smbfs service trying to unmount samba shares but NM service has
already shutdown and there is no working network connection

I have seen this "bad" behaviour in F8 and have reported it on this
mailinglist, but I hoped that the new and smarter NM would take care
of it, but unfortunately it didn't

So:
https://bugzilla.redhat.com/show_bug.cgi?id=449070

Cheers,
Valent.




Look like bz https://bugzilla.redhat.com/show_bug.cgi?id=218237

--
---------------------------------
Regards,

Old Fart

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-30-2008, 06:50 PM
"Colin Walters"
 
Default Networkmanager service is shutdown too early

On Fri, May 30, 2008 at 2:24 PM, Dan Williams <dcbw@redhat.com> wrote:

On Fri, 2008-05-30 at 13:59 -0400, Bill Nottingham wrote:

> Dan Williams (dcbw@redhat.com) said:

> > > 'After netfs' should be good enough. Although netfs stop should possibly

> > > do lazy umounts.

> >

> > Ok, just need to bump NM a few bits later it looks like; might as well

> > be K84 to be right after messagebus.

>

> Well, NM will exit anyway when the messagebus exits, will it not?
Another simple solution is to not have a shutdown script at all.* Just let NM get killed by the global kill -9 before filesystem unmounts.

(which is what we should do for pretty much all services with the exception of MySQL/Postgres basically too)


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-30-2008, 07:09 PM
Nicolas Mailhot
 
Default Networkmanager service is shutdown too early

Le vendredi 30 mai 2008 à 14:50 -0400, Colin Walters a écrit :

>
> Another simple solution is to not have a shutdown script at all. Just
> let NM get killed by the global kill -9 before filesystem unmounts.
> (which is what we should do for pretty much all services with the
> exception of MySQL/Postgres basically too)

The global kill -9 does not help you when you need to stop or restart a
single service

--
Nicolas Mailhot
--
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 01:31 PM.

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