|
Marc, The fix works by spawning a child then the
child immediately spawning another child (ch#2) that ch#2 will do the actual
work. Parent waits for ch#1 which returns immediately so no blocking occurs
there. After ch#2’s parent exits its new parent becomes system ‘init’
process which will properly reap it once completed. The above might sound confusing but that
is how it works (dark corners of UNIX legacy). I faced the same problem and made
this fix for myself a few months ago and have been happy with it ever since.
Several people are using sipp here. I had a real trouble submitting a message
to the forum because it uses very strong anti-spam (Sender Call Out). Best Regards, Vlad From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] >Marc, Olivier, As I won't have time until somewhere in November to
try this out, you'll have to wait a bit for my feedback. But, as said before, I'll test it somewhere in
November, Best regards, MarcVD (-: from Marc VAN DIEST (BELGACOM
ANS/NTA) +32 2 244 5078 ;-)
|
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
