Hi Maciej, I'm attaching the suggested patch to this bug, but bear in mind it's adapted to upstream's code.
Originally, SSSD creates the pidfile at an early stage (once it forks) before the providers have started. This patch moves the pidfile creation to a point where the providers are up and ready, allowing us to monitor this file creation in the boot scripts for upstart/systemd. With a few tweaks in the boot scripts, this would fix points #1 and #2 in the list. Regarding #3, SSSD monitors the status of the network interfaces using libnl, triggering an internal restart of the services when a change happens. It don't think this is a problem by itself, rather than a bad combination with #4 ** Patch added: "pidfile sssd.patch" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1566508/+attachment/4774029/+files/pidfile%20sssd.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566508 Title: autofs races with sssd on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1566508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
