Can't restart daemon when the connection has failed

[HughMacdonald]

Hi,

I just tried something out here where I tried to restart the daemon while it was attempting to reconnect to Shotgun...

When I tell it to restart, the log starts chucking out loads of:

2011-04-24 09:59:18,420 - engine - WARNING - Unable to connect to Shotgun (attempt 1 of 5): [Errno 4] Interrupted system call
2011-04-24 09:59:18,521 - engine - WARNING - Unable to connect to Shotgun (attempt 2 of 5): [Errno 4] Interrupted system call
2011-04-24 09:59:18,622 - engine - WARNING - Unable to connect to Shotgun (attempt 3 of 5): [Errno 4] Interrupted system call
2011-04-24 09:59:18,722 - engine - WARNING - Unable to connect to Shotgun (attempt 4 of 5): [Errno 4] Interrupted system call
2011-04-24 09:59:18,823 - engine - ERROR - Unable to connect to Shotgun (attempt 5 of 5): [Errno 4] Interrupted system call

What's happening, I believe, is that the exception catcher that's meant to be catching Shotgun errors is also catching the kill that is being sent from daemonizer's stop() function.