[SSSD] [Design] Common SIGCHLD handling for providers

Simo Sorce simo at redhat.com
Fri Oct 14 21:36:48 UTC 2011


On Fri, 2011-10-14 at 15:27 -0400, Stephen Gallagher wrote:
> On Fri, 2011-10-14 at 13:10 +0200, Pavel Zůna wrote:
> > https://fedorahosted.org/sssd/wiki/DesignDocs/SigChld
> 
> 
> That's not exactly what I was looking for (among other things, it
> doesn't account for removal of children that are no longer alive). I
> added an alternate proposal to that page. Please read it and see if it
> makes sense to you.
> 
> Also, using the online/offline callbacks as an example wasn't a good
> place to work from. Those are designed the way they are because they can
> be triggered from multiple places, not just the SIGUSR1 and SIGUSR2
> debugging signals.

Isn't a hash table for children a bit overkill ? How many children do
you plan to have ?

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York




More information about the sssd-devel mailing list