--On 6. Februar 2018 um 08:01:18 -0800 Mark Sapiro <m...@msapiro.net> wrote:
On 02/06/2018 03:51 AM, Sebastian Hagedorn wrote:
--On 4. Februar 2018 um 12:54:43 +0900 Yasuhito FUTATSUKI
<futat...@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.
Ah OK, I misunderstood that part.
--
.:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
.:.Regionales Rechenzentrum (RRZK).:.
.:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
