[Pkg-sysvinit-devel] Bug#481252: [initscripts] umountfs: network fs should be unmounted before network-manager is shutdown

[Petter Reinholdtsen]

[C Sights]
> Hello,
> When my laptop is rebooting a CIFS mounted directory is not unmounted before 
> the network interface, controlled by network-manager, is brought down.
> I think this could be fixed by adding NetworkManager to "Required-Stop" 
> or "Should-Stop" of /etc/init.d/umountfs.sh.

Hi.  I see the point, but I am not sure your proposal is the correct
one.  First of all, as it now is possible to use reverse dependencies,
I am not willing to add new dependencies to the sysvinit scripts.  I
belive these should form the framework other scripts relate to, and
thus if NetworkManager need to stop after umountfs, it should use the
X-Stop-After header.

> Rerhaps a separate bug or an indication I don't know what is going
> on: /etc/init.d/network-manager and
> /etc/init.d/network-manager-dispatcher has "$remote_fs" in its
> Required-Start and Required-Stop.  Why should remote_fs be around
> when there is a possibility that the interface to them will not
> exist or will be shutdown?

I have not investigated this issue, but suspect a solution might
involve looking at the omitpid feature in sendsigs, and changing the
shutdown dependencies of NetworkManager.  $remote_fs during shutdown
is the point where /usr/ is guaranteed to still be mounted, and just
before it might be umounted all/most processes are killed by sendsigs.

Happy hacking,
-- 
Petter Reinholdtsen