On Wed, Jan 17, 2018 at 6:14 PM, Eric Covener <[email protected]> wrote: >>> Maybe h2 could just call this on each new thread, but not the >>> primordial one child_init runs directly on? >> >> Or the MPM block signal before child_init(), it is usefull to create >> threads from there w/o boring with masks... > > I was being paranoid about breaking someone, but that doesn't really > make sense since they'd have to be setting handlers explicitly.
Yes, it's also my feeling, we are less protected against child_init() threads that would steal "our" MPM signals though, their bug IMO.
