[Pkg-utopia-maintainers] Re: Bug#419049: quota: Causes shutdown

Michael Biebl biebl at debian.org
Mon Apr 16 20:29:37 UTC 2007


Hi Michael,

Michael Meskes wrote:
> On Mon, Apr 16, 2007 at 02:19:04PM +0200, Michael Biebl wrote:
>> reassign 419049 quota
>> ...
>> No, actually I don't quite agree that it's a bug in network-manager.
> 
> Maybe in dbus?

Moving dbus (or network-manager that is) to a later point in the
shutdown process won't really help.
It would have to be moved after S31umountnfs.sh, which in turn is run
after S20sendsigs.
So the dbus and network-manager daemon would be shut down too early
anyways by sendsigs (that's also the reason why S15wpa-ifupdown is run
before S20sendsigs. This also means that if you setup your connection
via wireless/WPA using the wpasupplicant roaming mode, you will
encounter the same problems as with network-manager).

>> I'd argue that quota (and also the nfs umount script) shouldn't rely on
>> a arbitrary priority number during shutdown.
> 
> Hmm, looking at the links in /etc/rc6.d it seems to me that we have a
> lot of buggy packages then. It cannot be correct IMO to down an
> interface while critical server processes are still running. For
> instance syslog might still try to remotely log the reboot process but
> cannot since the device went away.
> 
>> 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.
> 
> I'm willing to accept that there should be a solution to have
> dependancies in our initscripts that we do not have atm. The biggest
> risk IMO is not quota hanging but soem network filesystems not being
> unmounted at all. However, I fail to see why this is a quota bug. Would
> you please care to elaborate? 

I'm not saying, that quota is at fault here. I reassigned the bug mostly
because it's imho not a bug in network-manager. network-manager is
simply not conceived for such a use case.
network-manager is intended for highly dynamic network environments,
where networks come and go and where you switch between different networks.
Removing network-manager is probably the best "bug fix" there is atm.
For a static configuration with NFS mounts etc, as Johns' setup, I would
recommend to use plain ifupdown.

Cheers,
Michael

P.S.: What happens if you pull the network plug? Will quota then also
fail to stop? Is this a matter of how the nfs share was mounted (hard or
 soft)?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-utopia-maintainers/attachments/20070416/afa4997c/signature.pgp


More information about the Pkg-utopia-maintainers mailing list