Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #22246 > unrolled thread

Re: Slow termination of process

Started byChris Angelico <rosuav@gmail.com>
First post2012-03-28 00:55 +1100
Last post2012-03-28 00:55 +1100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Slow termination of process Chris Angelico <rosuav@gmail.com> - 2012-03-28 00:55 +1100

#22246 — Re: Slow termination of process

FromChris Angelico <rosuav@gmail.com>
Date2012-03-28 00:55 +1100
SubjectRe: Slow termination of process
Message-ID<mailman.1040.1332856552.3037.python-list@python.org>
On Wed, Mar 28, 2012 at 12:03 AM, Roland Hedberg <roland@catalogix.se> wrote:
> When the main script is done it closes down the HTTP server by doing:
>
>    op.terminate()
>
> The problem I have is that if the main script is run again almost immediate then the old HTTP server
> process doesn't seem to have released the port yet. So setting up a new server fails.

You may wish to consider a more orderly shutdown (send the server a
signal upon which it shuts itself down), but the simplest and most
direct solution is to set the SO_REUSEADDR flag.

http://docs.python.org/library/socket.html?highlight=so_reuseaddr

I've not actually used the TCPServer class myself, but a cursory
glance at the docs suggests that it's possible if you subclass it:

http://docs.python.org/library/socketserver.html#SocketServer.BaseServer.allow_reuse_address

Chris Angelico

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web