Not sure if this was a later version of autofs, network or systemd which repaired this issue. At least with the versions installed it is now done the right way: unmount network mounted filesystems (any of them: nfs, smb, sshfs, ...), then turn down networking. Not as before: turn down networking, then fail to unmount network mounted filesystems, because the network is down.
On Mon, May 9, 2022 at 6:22 PM Paride Legovini <1968...@bugs.launchpad.net> wrote: > > Hello Thomas, I am a bit confused by your last comment. You reported > this bug against > > DistroRelease: Ubuntu 22.04 > Package: autofs 5.1.8-1ubuntu1 > > but then noted that this is "Solved by a later version of autofs", > however there is no newer version of autofs in Ubuntu. Were you > referring to a new upstream version of autofs? Could you please clarify? > Thanks! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1968127 > > Title: > autofs stopped after network must be before > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1968127/+subscriptions > -- Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968127 Title: autofs stopped after network must be before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1968127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
