Re: [Twisted-Python] buildProtocol never called

2009-07-04 Thread travis+ml-twisted
On Sat, May 30, 2009 at 06:17:54PM -0500, travis+ml-twis...@subspacefield.org wrote: > The problem I'm having is this; I upgraded my firewall from OpenBSD > 4.2 or so to OpenBSD 4.5, and now I'm working with newer versions of > all the software including Twisted. > > The program works fine normal

Re: [Twisted-Python] buildProtocol never called

2009-05-31 Thread Jean-Paul Calderone
On Sun, 31 May 2009 15:18:50 -0500, travis+ml-twis...@subspacefield.org wrote: >On Sat, May 30, 2009 at 08:26:40PM -0400, Jean-Paul Calderone wrote: >> Creating the reactor at all may create a file descriptor which is necessary >> for its operation. Closing these will very likely cause problems. >

Re: [Twisted-Python] buildProtocol never called

2009-05-31 Thread Johann Borck
travis+ml-twis...@subspacefield.org wrote: > On Sat, May 30, 2009 at 08:26:40PM -0400, Jean-Paul Calderone wrote: > >> Creating the reactor at all may create a file descriptor which is necessary >> for its operation. Closing these will very likely cause problems. >> > > This is all before

Re: [Twisted-Python] buildProtocol never called

2009-05-31 Thread travis+ml-twisted
On Sat, May 30, 2009 at 08:26:40PM -0400, Jean-Paul Calderone wrote: > Creating the reactor at all may create a file descriptor which is necessary > for its operation. Closing these will very likely cause problems. This is all before calling any Twisted routines > Also, Twisted has daemonization

Re: [Twisted-Python] buildProtocol never called

2009-05-30 Thread Jean-Paul Calderone
On Sat, 30 May 2009 18:36:16 -0500, travis+ml-twis...@subspacefield.org wrote: >On Sat, May 30, 2009 at 06:17:54PM -0500, travis+ml-twis...@subspacefield.org >wrote: >> The program works fine normally, and can run in the background, but if I >> invoke a daemonize() routine that turns it into a net

Re: [Twisted-Python] buildProtocol never called

2009-05-30 Thread travis+ml-twisted
On Sat, May 30, 2009 at 06:17:54PM -0500, travis+ml-twis...@subspacefield.org wrote: > The program works fine normally, and can run in the background, but if I > invoke a daemonize() routine that turns it into a network daemon, it > refuses to serve incoming TCP connections. Actually the TCP conn