On Sun, 20 Jun 2010 20:00:14 +1000, Ben Finney wrote:
>> I'm starting a SocketServer.TCPServer in my program, but since I want
>> to report problems to script starting the program, I want to go daemon
>> *after* TCPServer has done binding to port.
>>
>> Is this likely to cause problems? I mean, my
mk writes:
> I'm starting a SocketServer.TCPServer in my program, but since I want
> to report problems to script starting the program, I want to go daemon
> *after* TCPServer has done binding to port.
>
> Is this likely to cause problems? I mean, my client works when I do
> the above, that is, i
Hello everyone,
I'm starting a SocketServer.TCPServer in my program, but since I want to
report problems to script starting the program, I want to go daemon
*after* TCPServer has done binding to port.
Is this likely to cause problems? I mean, my client works when I do the
above, that is, it
