On Tue, Mar 24, 2009 at 11:20 PM, Ruediger Pluem <rpl...@apache.org> wrote:
> On 24.03.2009 19:12, Eric Covener wrote: > > SIGQUIT (3) does not go through sig_coredump(). Is this intentional to > > short-circuit the sig_coredump handling in the case something is > > broken there? > I dunno about the intentions. > > > IMHO SIGQUIT isn't supposed to cause a coredump. Only "fatal" signals are > supposed to do this. If you need a coredump of your running process just > use > gcore or gdb. See http://en.wikipedia.org/wiki/SIGQUIT I think the issue is that SIGQUIT does terminate the process with a core dump (at least on some systems). Given that, the question is whether we should respect any CoredumpDirectory setting on the way out. Respecting CoredumpDirectory seems reasonable. OS X: $ lsap 9292 1 ./httpd 9293 9292 ./httpd 9294 9292 ./httpd 9295 9292 ./httpd 9296 9292 ./httpd 9297 9292 ./httpd $ kill -QUIT 9297 $ ls /cores/ core.9297 (/cores/ is the default location here.)
