Re: On SIGWINCH usage, switch to SIGUSR2 nowadays?

2019-02-21 Thread Yann Ylavic
On Thu, Feb 21, 2019 at 5:31 PM Yann Ylavic wrote: > > May I commit this (before unblocking graceful stop in ONE_PROCESS mode)? OK, it requires an APR change anyway because SIGUSR2 is blocked by apr_signal_thread(). I opened a thread there, wait and see, in any case it now depends on a minimal

Re: On SIGWINCH usage, switch to SIGUSR2 nowadays?

2019-02-21 Thread Yann Ylavic
After some bit of research, I couldn't find a platform (besides Linux < 2.6) where SIGUSR2 is "reserved", so possibly something like the attached patch would be acceptable. The patch adds --enable-graceful-stop-sigusr2 to configure(.in) which default to "yes" (for trunk, but would default to "no"

On SIGWINCH usage, switch to SIGUSR2 nowadays?

2019-02-21 Thread Yann Ylavic
Hi, as you probably know, SIGWINCH is used both by terminal (emulators) for window changes/redraw, and httpd for graceful stop (hardcoded AFAICT). This can cause issues when httpd is run in foreground from a terminal, and as such (I think) is ignored in -X/ONE_PROCESS mode otherwise gdb-ing