LP: #1566508 looks like it's been resolved, and LP: #1614248 appears
still an issue in xenial but fixed in zesty and newer. LP: #1588915 is
still open but seems to be an ifupdown bug rather than autofs itself,
and has not been updated since 2017 and I'm not sure if it is still an
issue on newer releases.
From what I understand, this bug report was filed due to the
amalgamation of issues that made this use case malfunction. Given that
it appears a number of improvements have been introduced since 16.04,
and given that standard support for 16.04 has ended, I think we should
consider this bug report resolved, and if there are remaining issues
reproducible on newer Ubuntu releases, to have fresh new bug(s) filed
for them. Meanwhile, thanks again for raising this issue with us.
** Changed in: autofs (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614282
Title:
autofs does not recover from failure to read maps on startup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1614282/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
