Hi,
Currently the watchdog is enabled for all sssd processes, including the main sssd process.
I admit I only realised that now that I was looking into one user report where upgrading
the sssd database during package update took so long that the watchdog eventually killed
the sssd process..oops..
So we can either relax the watchdog during operations that we know might take a very long
time (like upgrading huge cache files) or remove it altogether. I’m leaning towards the
second option and just don’t setup the watchdog at all.
Does anyone see a reason to keep the watchdog for the monitor? I think the watchdog in the
current form makes sense only for “worker” processes where the monitor listens for SIGCHLD
signals and restarts the services. I think for the monitor process it would make more
sense to leverage some systemd functionality rather than kill itself :-)