J.J J wrote on Sunday, May 17, 2015 2:54 AM
>Signal handler is ngx_signal_handler which in worker process does
>nothing but log exit code and release possible holded mutexes,
>only master process reap child by setting ngx_reap to 1 and spawn
>it in ngx_reap_children if registed in ngx_processes(wo
Signal handler is ngx_signal_handler which in worker process does nothing
but log exit code and release possible holded mutexes, only master process
reap child by setting ngx_reap to 1 and spawn it in ngx_reap_children if
registed in ngx_processes(worker, loader, manager)
So no, you can't, but you
I fork + exec child processes and I would like to get some kind of notification
when they exit. However, the nginx signal handler reaps my child processes and
logs a message like
2015/05/14 14:12:24 [notice] 28033#0: signal 17 (SIGCHLD) received
2015/05/14 14:12:24 [notice] 28033#0: unknown pro