Per Debian fix in 5.1.2-1
"AFAIKS, autofs is providing a .service now with an After=sssd"
This is in Ubuntu as of Zesty.
I'll mark the tasks accordingly.
Adding the service in Xenial in general might have too much risk to cause other
regressions - not sure thou - I beg your pardon - this is just an area I rarely
work on.
Is there a way to express this in the sysv that xenial has, maybe via [1].
I can envision a setup with autofs and no ssh, so it is not required, but maybe
"should".
So maybe in header of /etc/init.d/autofs:
Should-Start: ssh
I wonder how that carries over into the systemd generator used in
Xenial.
Could one affected give it a try instead of adding the full .service file to
add that and then run the following to pick up the changes
$ sudo systemctl daemon-reload
** Also affects: autofs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: autofs (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: autofs (Ubuntu)
Status: Triaged => 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/1614248
Title:
Package autofs does not include autofs.service file
To manage notifications about this bug go to:
https://bugs.launchpad.net/autofs/+bug/1614248/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
