[SSSD] [PATCH] Resend SIGINT as SIGTERM in services

Jeff Schroeder jeffschroeder at computer.org
Fri Jun 25 17:54:46 UTC 2010


On Fri, Jun 25, 2010 at 11:39 AM, Jakub Hrozek <jhrozek at redhat.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 06/24/2010 03:32 PM, Stephen Gallagher wrote:
>> Nack. As I think about this, I think that we should have the child
>> processes ignore SIGINT entirely. The monitor should be the exception:
>> it should catch the SIGINT and just put it through the SIGTERM processing.
>>
>> This way, if we ever want to change how the monitor handles shutdown
>> (e.g. send a D-BUS message instead of signals to the children) we only
>> have to change it in one place.
>>
>
> Yes, I considered that but I thought that someone might still like to
> send SIGINT to the process manually. But SIGINT is meant to be sent from
> controlling terminal usually, so perhaps just blocking the signal except
> for monitor makes sense.

Not a SIGINT, but perhaps a SIGTERM. I actively try to kill sssd in
strange ways before rolling it out and that involves sending signals
to the various subprocesses. Would it ever make sense to send a SIGHUP
to a specific backend to have it re-read the config without the entire
sssd suite of daemons following suit?

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com



More information about the sssd-devel mailing list