On Tue, Jun 15, 2021 at 09:00:36AM +0000, Mike Gabriel wrote: > thanks for your contribution. To make an update possible for Debian bullseye > (we are in deep freeze), I need a more dramatic description of things that > might go wrong with the current .service file. > > Please explain the opposite of "robust" with concrete observations (i.e. > bugs). > > Furthermore, have you tested the proposed service file with autofs-ldap??? > With autofs-ldap we still have a nasty race condition that leaves autofs > non-function if it starts before nslcd (libnss LDAP caching daemon). >
I'm not sure I can help you with the latter, since we use sssd and have never experienced any issues in that regard. I'm currently debugging a race condition with another service that only depends on autofs where a single autofs mountpoint doesn't work but all the others (all backed via LDAP) are. The service in question usually starts at the same second as autofs. Since notify will notify readiness when the service thinks it's ready instead of at fork time, my hope is that it will go away if autofs is actually ready, when it is shown as such. Just spitballing here, but maybe that's the issue with nslcd for you, too? Unfortunately nslcd doesn't doesn't have notification support, but I once worked around a similar issue with autofs data in NIS by busy looping in ExecStartPre= until NIS was actually working. Fortunately, with sssd this was no longer an issue. :) And as a nit: the /var/run path was a log nuisance for a long time and the only reason this has stopped, is because the systemd package now carries a patch to silence the warning, because it was apparently easier to do that than fix the service files all over Debian. Since the autofs package is built without --with-systemd, the above service file cannot be used out of the box. I'll rebuild autofs for my machines and will let you know whether it fixes my issue, but even if it doesn't it would be a positive change for all people using autofs on systemd. I completely understand that this probably can't make it into bullseye, but maybe for bookworm we can use the service file, that upstream has been shipping since end of October 2018. :)
signature.asc
Description: PGP signature