Hi, thanks for reporting and making Ubuntu better! I guess the way things are interconnected there breaks you - just as you describe the IP connection by the VPN is gone before unmount.
Whenever I encountered "via VPN" mounts in the past people usually used the up/down directive of the VPN to mount/unmount instead of fstab and such. I'd recommend you e.g. http://askubuntu.com/questions/28733/how-do-i-run-a-script-after-openvpn-has-connected-successfully That said the 120sec is "just" a timeout until the umount gives up. IMHO your real problem is that you might already have lost data by loosing the IP connection before - like files that weren't flushed properly. So I really would recommend the up/down directive. I'd consider a solution inside e.g. systemd dependencies and such overly complex and error prone - therefore I set the report itself to Won'tFix for now. If you think it really should be "autoprevented" by the shutdown process itself please reopen it and provide some details why the "usual" workarounds wouldn't apply. ** Changed in: openvpn (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359296 Title: Shutting down OpenVPN before umount network shares causes 120 second timeout on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1359296/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
