On 02/06/2018 03:51 AM, Sebastian Hagedorn wrote:
--On 4. Februar 2018 um 12:54:43 +0900 Yasuhito FUTATSUKI futatuki@poem.co.jp wrote:
As far as I read the code, if OutgoingRunner catch SIGINT during waiting for response from the MTA, the signal handler for SIGINT in qrunner set flag to exit from loop, then socket module raise socket.error for EINTR, but SMTP module retry to read from socket and waiting for response until receiving response or connection closing (from MTA side or by error). Thus it cannot reach to the code to exit if the connection is kept alive and MTA send no data.
Thanks. I think that might be a possible explanation, but what could cause a SIGINT to be sent to the OutgoingRunner?
The above is an explanation of why the runner doesn't exit when it receives a SIGINT or SIGTERM from the master when you restart or stop Mailman and why you have to SIGKILL it. It suggests that what's happening when it's hung is it's waiting for a response from the MTA.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan