group.of.nepali.translators team mailing list archive

[ChristianEhrhardt <1614248@xxxxxxxxxxxxxxxxxx>]

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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614248

Title:
  Package autofs does not include autofs.service file

Status in autofs:
  Fix Released
Status in autofs package in Ubuntu:
  Fix Released
Status in autofs source package in Xenial:
  Confirmed

Bug description:
  Package autofs in Ubuntu 16.04 includes SysV startup script
  (/etc/init.d/autofs) and Upstart unit (/etc/init/autofs.conf), but
  does not include systemd service file. As a result, systemd starts
  autofs as part of its LSB (sysv) processing, which makes it difficult
  to ensure that autofs is started after services that it requires for
  proper functioning. In particular, unit autogenerated by systemd-sysv-
  generator for autofs does not include dependency on sssd.service.

  It appears that on the installation that I tested, systemd starts LSB
  services well after sssd is started, so the issue does not cause any
  visible problems, but this startup sequence is accidental. Given the
  number of other issues related to autofs startup in Xenial, requiring
  users to get their hands dirty just to have autofs run properly after
  boot, I think it would be advantageous to fix this simple oversight.
  (See bug 1566508, bug 1584818, bug 1588915)

  I attach an example service file for autofs that fixes this problem.
  In addition to sssd.service, this unit could also list nslcd.service,
  slapd.service and ypbind.service/nis.service in its After= line.
  However, these service files are also missing from their respective
  packages, and I am not even sure how NIS client service file would be
  called.

  $lsb_release -rd
  Description:    Ubuntu 16.04.1 LTS
  Release:        16.04

  $apt-cache policy autofs
  autofs:
    Installed: 5.1.1-1ubuntu3
    Candidate: 5.1.1-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/autofs/+bug/1614248/+subscriptions