Why does pm-utils/NM bring down the network for hibernate/suspend?

Dan Williams dcbw at redhat.com
Fri Mar 27 21:49:39 UTC 2009


On Fri, 2009-03-27 at 15:38 -0600, Orion Poplawski wrote:
> Dan Williams wrote:
> > On Fri, 2009-03-27 at 13:49 -0600, Orion Poplawski wrote:
> >> I'll ask my question a different way I guess:
> >>
> >> Why does pm-utils/NM bring down the network for hibernate/suspend?
> > 
> > Must have missed something here...
> > 
> > Are you referring to the periodic problem where "Networking Enabled" is
> > unchecked on resume?  If so, that's covered by a pm-utils bug already,
> > which is really a dbus bug that can be worked around in pm-utils.
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=477964
> > 
> > If you're referring in general to "why does NM bring down the network"
> > on suspend, there are a few reasons for that which I can elaborate on.
> 
> Well, the problem I'm seeing on a machine with NFS home directories and 
> LDAP authentication is that after the network is brought down calls by 
> pm-utils to sync hang (presumably NFS related) and I see lots of 
> nss_ldap cannont connect to LDAP server errors and the hibernate process 
> hangs.
> 
> I suppose I should file a bug - against pm-utils for incorrect ordering 
> of scripts?  Should I expect this to work?

Yeah, should probably get re-ordered.  NM is at 55, should probably be
one of the last things to get poked.

Dan





More information about the fedora-devel-list mailing list