Hi Per, [...]
Okay, I don't have that. You're right, it doesn't seem necessary, the mounts work anyway. I'll enable it.
We have progress - my nfs shares were mounted now. owncloud still doesn't wait. How do I make application wait for a network connection?
just the same way you now use for nfs. Create a script in /etc/NetworkManage/dispatcher.d, named "owncloud" for example. It can look similar to this snippet: ------------------------< snip snip snip >----------------------------- #!/bin/bash INTERFACE="$1" ACTION="$2" case "$ACTION" in pre-up) ;; vpn-pre-up) ;; up) for svc in owncloud blahsvc blubbsvc do _status=$( /usr/bin/sysctl is-enabled ${svc}.service ) case "$_status" in masked*|linked*) ;; *) # it is important to use "&" at least in the down cases # - the script only has a small amount of time to run, before it # gets killed to avoid blocking NetworkManager /usr/bin/sysctl restart ${svc}.service >/dev/null 2>&1 & ;; esac done ;; vpn-up) ;; pre-down) for svc in blubbsvc blahsvc owncloud do # it is important to use "&" at least in the down cases # - the script only has a small amount of time to run, before it # gets killed to avoid blocking NetworkManager /usr/bin/sysctl stop ${svc}.service >/dev/null 2>&1 & ;; esac done ;; vpn-pre-down) ;; down) ;; vpn-down) ;; esac ------------------------< snip snip snip >----------------------------- For the down cases you have to create new directories named "pre-down.d" and "vpn-pre-down.d" below /etc/NetworkManager/dispatcher.d and link the script into these directories. Be aware, though, that not all of these cases are handled correctly with NetworkManager 1.0.12, which is part of Leap 42.2. The newer versions as in Tumbleweed are dealing much better with the various conditions.
-- Per Jessen, Zürich (11.9°C)
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org