<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - remote file systems cannot be unmounted at shutdown" href="https://bugs.freedesktop.org/show_bug.cgi?id=73727#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - remote file systems cannot be unmounted at shutdown" href="https://bugs.freedesktop.org/show_bug.cgi?id=73727">bug 73727</a> from <a class="email" href="mailto:mario.natiello@gmail.com" title="Mario Natiello <mario.natiello@gmail.com>"> Mario Natiello</a> <pre>(In reply to <a href="show_bug.cgi?id=73727#c5">comment #5</a>) > > We also can't fix this by adding After=network.target and After=NetworkManager.service to every mount. > > To clarify, having re-read your comment, we also can't do this for > systemd-user-sessions.service for the same reasons. Addendum: The modification I proposed does not work either. Or it is at least erratic. Not having changed other things, I twice found myself in the situation where umount of the remote systems fails and the shutdown process is delayed by 90 sec before the timeout takes over. So which one is the proper After=... command remains unclear. The only thing that invariably works without obstacles is to umount the sshfs devices myself by hand right before issuing shutdown. I will attach a third journalfile with a umount failure, run in the same conditions as journalfile nr 2.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>