Windmill should gracefully exit if an existing entrance is already running

[omaciel]

I usually have an external windmill appliance which I ssh into in order to run a batch of scripts on another external appliance. If for whatever reason my previous attempt fails and windmill just sits there hanging, subsequent attempts will also fail with windmill hanging.

Traceback:

Exception in thread Thread-1: Traceback (most recent call last):

File "/usr/​lib/​python2.4/​threading.py", line 442, in bootstrap

self.run()

File "/usr/​lib/​python2.4/​threading.py", line 422, in run

self.target(*self.args, **self.kwargs)

File "/usr/​lib/​python2.4/​site-packages/​cherrypy/​wsgiserver/​init.py", line 851, in start

error: (98, 'Address already in use')

Feel free to ping me on #windmill if you need further information.

[mikeal]

I had a fix for this but it added a full 2 seconds to the startup time and that was unacceptable.

I think I might try to just try connect to the port and check for an error before running the thread. That should be fast and won't lock up the file handler on the port like binding to it did which took a second to clean out after I killed it.