reassign 419049 quota thanks Michael Meskes wrote: > reassign 419049 network-manager > thanks > > On Sun, Apr 15, 2007 at 04:36:33PM +0200, Michael Biebl wrote: >>>> Indeed, after purging network-manager, the hang is fixed. >>>> >>>> Watching the console, it appears that without network-manager, the >>>> interface is taken down after quotas are. >>> Looking at the priorities I would guess that NFS filesystems are >>> unmounted even later in S31umountnfs.sh. The device should be taken down >>> in S35networking I would guess. So I wonder why network-manager is >>> taking it down and whether this is more of a network-manager bug. >> If the interface was brought up by network-manager, network-manager will >> also take it down. As network-manager relies on dbus, this has to happen >> before K20dbus (which of course is way before S31unmountnfs.sh) >> I'd indeed say, that if you use an NFS setup, network-manager is not the >> best choice and simply removing it is the best option. >> >> I'm open to other suggestions though. > > It seems we agree that this is not a quota bug, right? Therefore I > reassign this bug to network-manager although I'm unsure whether it's a > real bug. IMO it should be documented that network-manager doesn't work > well with NFS. I wouldn't want to run a system that won't be able to > unmount my NFS shares
No, actually I don't quite agree that it's a bug in network-manager. I'd argue that quota (and also the nfs umount script) shouldn't rely on a arbitrary priority number during shutdown. The real fix actually would have to happen within the init system. Our current init scheme is simply not flexible enough for that. I can do nothing about that in network-manager, that's why I reassign the bug again. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature