On Fri, Feb 22, 2019 at 3:08 AM Yann Ylavic <ylavic....@gmail.com> wrote:
> On Fri, Feb 22, 2019 at 9:33 AM Branko Čibej <br...@apache.org> wrote: > > Even if that tool did work this way 16 years ago, this was the wrong way > > to solve the "problem". It's not APR's job to support such tools (except > > for pool debugging modes); it's the downstream application's. > > On Fri, Feb 22, 2019 at 9:52 AM Joe Orton <jor...@redhat.com> wrote: > > +1 definitely, it's a bit bizarre that's done by default TBH. > > OK, so it's a candidate to 1.6 possibly? :p > > Frankly, I don't see how it could break someone, SIGUSR2 has never > been received by any apr_signal_thread() handler so is in the list of > ignored signals so far, and still will for existing users who don't > care.. > If you are developing code to actually work, testing major.minor for the support of your desired feature makes more sense than checking m.m.s. I'd suggest the enhancement to 1.7.0 is more appropriate than 1.6.6.
