http://bugzilla.suse.com/show_bug.cgi?id=931964
--- Comment #6 from Dr. Werner Fink ---
(In reply to Bernhard Wiedemann from comment #5)
Systemd does not disable network, this does NetworkManager or the old ifconfig
based boot script /etc/init.d/network on 13.1 ... and AFAICS the nfs boot
script does depend on the network script:
systemctl show -p RequiresOverridable -p Requires -p Wants -p WantedBy -p
Before -p After nfs
Requires=basic.target
RequiresOverridable=network.target rpcbind.target
Wants=remote-fs-pre.target system.slice
WantedBy=multi-user.target graphical.target
Before=SuSEfirewall2.service autofs.service remote-fs-pre.target
shutdown.target multi-user.target graphical.target
After=network.target rpcbind.target systemd-journald.socket basic.target
system.slice
Btw: a hanging NFS share due to a unreachable NFS server should not cause a
soft lock but show a normal and extrem long lasting timeout. A problem even
well known from SysVinit based systems.
Btw: does this also happen with systemd-210 from Base:System:Legacy
--
You are receiving this mail because:
You are on the CC list for the bug.