March 12, 2007
4:28 p.m.
On 03:24 pm, jarek.zgoda@sensisoft.com wrote:
Jean-Paul Calderone napisa2(a):
If you are starting the thread before the process daemonizes, you might want to try starting it after daemonization instead and see if that helps.
You can do this by starting the thread in the startService method of a Service.
I see, I added the code for creating the thread in "after startup" event trigger and now it forks fine, thank you.
You might also consider using the reactor's built-in thread support, reactor.callInThread, rather than starting your own worker thread.