[Twisted-Python] Odd behavior in IRC logbot

Phillip J. Eby pje at telecommunity.com
Sat Oct 25 13:44:02 EDT 2003

At 03:21 AM 10/26/03 +1100, Andrew Bennetts wrote:
>On Sat, Oct 25, 2003 at 10:07:42AM -0400, Phillip J. Eby wrote:
>     def clientConnectionFailed(self, connector, reason):
>         print "connection failed:", reason
>         reactor.stop()
>     ...
>Perhaps clientConnectionFailed is being triggered, instead of
>clientConnectionLost (which has no delay at all, as you can see)?  (The docs
>don't clearly say this, but ccF is called when there was no connection
>established, and ccL is called when a connection was made and then

But shouldn't reactor.stop() cause the process to exit, rather than 
hang?  I'm running the logbot under daemontools, so if it exited, it should 
be restarted.  But that's not what I'm seeing.  Instead, the process just 
goes idle.

More information about the Twisted-Python mailing list