Bug#798314: systemd: Systemd waits 30 minutes to shut down because of NFS share

Michael Biebl biebl at debian.org
Wed Sep 9 17:58:16 BST 2015


Am 09.09.2015 um 05:09 schrieb Javier Ayres:
> I edited the wpa_supplicant service as you suggested but the issue is still
> present. 

Hm, right. The issue here is, that you are using NetworkManager.service
to bring up your (wireless) interface. Unfortunately we can't bring up
NetworkManager.service before network.target, so NetworkManager is
stopped before your NFS mount is unmounted, i.e. the ordering is wrong here.

For ethernet connections, NetworkManager does not tear down the
connection on stop. For wireless connections, stopping NetworkManager
means you lose your network connection.

The reason why we can't oder NetworkManager.service  before
network.target is this leads to dependency cycles atm due to sysv init
scripts in /etc/rcS

I've also found that the behavior is not consistent, sometimes it
> waits 90 seconds and sometimes it waits 30 minutes (even after changing the
> fstab entry).

If you stop your network connection, how long does "umount /mnt/samsung"
block?

Michael

-- 
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: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150909/b6532d31/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list