http://bugzilla.opensuse.org/show_bug.cgi?id=916737 --- Comment #10 from Frerk Meyer <frerk.meyer@gmx.de> --- I debug the autofs script with 'logger' statements like this: #! /bin/sh # # autofs dispatcher script for NetworkManager # # Matthias Koenig <mkoenig@suse.de> # . /etc/rc.status case "$2" in up) logger "NetworkManager network link is up, test autofs service" if test -x /bin/systemctl && systemctl -q is-enabled autofs.service; then logger "NetworkManager: autofs is enabled, try to restart" systemctl restart autofs.service logger "NetworkManager: autofs was restarted" elif rc_active autofs; then logger "NetworkManager: network link is up, restart autofs without systemd" /etc/init.d/autofs restart logger "NetworkManager: autofs was restarted without systemd" fi ;; *) logger "NetworkManager network link is down?" exit 0 ;; esac Result of booting, logging in and several times suspend & resume is # journalctl |grep logger .. Feb 17 20:50:56 moby.o2.box logger[817]: NetworkManager network link is down? Feb 17 20:51:05 moby.o2.box logger[951]: NetworkManager network link is up, test autofs service Feb 17 20:51:05 moby.o2.box logger[982]: NetworkManager: autofs is enabled, try to restart Feb 17 20:51:06 moby.o2.box logger[1081]: NetworkManager: autofs was restarted Feb 17 20:51:06 moby.o2.box logger[1085]: NetworkManager: network link is up, start nfs Feb 17 20:51:45 moby.o2.box logger[1674]: NetworkManager network link is down? Conclusion: in the boot process autofs script is called with parameter 'up' once, which is correct. Afterwards it was called once with another parameter (down?). And after that it is never called, may it be during suspend or resume. Now I use the workaround from Joschi Brauchle, that is not to wait for NetworkManager and restart autofs anyways. But NetworkManager should call autofs and log "NetworkManager network link is up, test autofs service" which it doesn't. BTW: NetworkManager seems to me like a total rewrite, the GUI has changed completly. Maybe some new bugs were introduced? -- You are receiving this mail because: You are on the CC list for the bug.