Package: autofs Version: 5.1.1-1 Severity: normal Hi, FYI - this is a "mirror" of a bug we got, as it affects Debian just as much we think it should be integrated there. Reference: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1614248
Summary (stripped of Ubuntu references that don't matter to you): "Package autofs includes SysV startup script (/etc/init.d/autofs), 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. Suggested example service file for autofs that fixes this problem: https://launchpadlibrarian.net/279497607/autofs.service 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." -- Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd
