https://bugzilla.novell.com/show_bug.cgi?id=861489
https://bugzilla.novell.com/show_bug.cgi?id=861489#c26
--- Comment #26 from Rainer Krienke 2014-02-24 10:17:29 UTC ---
Hello,
first thanks very much to Werner and to Andrey for your proposals over the
weekend.
This morning I tried the Wants=network-online.target configuration in
network@.service. I copied network@.service to /etc/systemd/system and edited
this file. Next I tested what happens upon a reboot. The results were not
reliable just as it happened earlier. Sometimes I could reboot a couple of
times with no problems then I removed the /etc/systemd/system/network@.service
file tested again, next put the file in place again (with the additional Wants
and Before lines in place ) but now a reboot did suddenly hang.
So there is something else wrong and I thought about what is nonstandard in my
tweaked installation of opensuse. All desktop installation I do have one thing
in common:
A non local, nfs mounted /usr/local directory that contains centrally installed
software for all linux clients and is also used for some central administration
tasks.
For this purpose /usr/local on each client is not a directory but a symbolic
link to a directory /import/sw. /import/sw again is a key for a automount map
that causes a NFS mount of the servers /export/sw directory to /import/sw on
the client. So accessing /usr/local triggers a NFS mount via automounter.
What I now tried is simply to remove the local symbolic link and to replace it
by a the original "local" on disk installation directory (which after all
contains only empty subdirectories like sbin, man, ...).
In this configuration I was able to reboot the system successfully even if a
user with NFS home directory has a running KDE session. It seems to work each
and every time I tried, at least up to now it did not fail. I could even remove
the modified /etc/systemd/system/network@.service file and it still worked
fine.
If I replace the directory /usr/local by the symbolic link "local" pointing to
the automount mount point the system hung again in several tries.
So my thoughts now are that some systemd-service uses /usr/local, at least it
accesses this directory and thus triggers a NFS mount, which might lead to a
hanging mount when shutting down this service, because the dependencies of this
service are not designed to be NFS dependent cause usually /usr/local is not a
NFS directory.
I'll go on searching in this direction, and see what more I can find out.
Rainer
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.