Killing itself is not proper design.
Even systemd(Init process, system manager) has task of Managing
services/daemons running on system included in duty list.
On Sun, Nov 6, 2016 at 10:51 PM, Jakub Hrozek <jhrozek(a)redhat.com> wrote:
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 :-)
sssd-devel mailing list -- sssd-devel(a)lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-leave(a)lists.fedorahosted.org