David Newman writes:
My limited understanding of SIGQUIT is that it dumps core,
*chuckle* The differences among user signals like SIGTERM and SIGQUIT are a bit gibbous especially since you can change the handler or ignore them entirely. (SIGKILL of course is one of a very few signals that is well-defined since it cannot be caught or ignored and is handled entirely by the OS.)
but 'find / -type f -name '*.core' did not return any core dumps from this event.
Dumping core is the default action, but that requires that core dumps be enabled for that process. You can check the general environment from the shell with "ulimit -c" (if logged in as the Mailman user) but Mailman or Python itself might have different ideas, and either might be installing a handler that does something different. Mark might know, but I'm not familiar with that really low-level stuff (I should fix this .... ;-)