[EMAIL PROTECTED] wrote:
>
> Hello all,
>
> subject: sipp defunct processes
>
> I'm using sipp for a while now (on linux), and wanted to generate some 
> syslog messages when things go wrong with the SUT.
>
> As no syslog functionality is built in, I started calling the external 
> program logger, and I noticed the same behaviour as found with google 
> and copied here below (between the dashes): hanging defunct child 
> processes.
>
> As I only subscribed the mailing list a few days ago and google didn't 
> indicate a solution to this problem yet, I hope I'm not too late with 
> this contribution.
>
> Now, I'm a (very;-) old programmer from the time C++ was not yet 
> really used, I found rather quickly what was the problem, but it's 
> somewhat hard for me to put all pieces correctly in the code. So I 
> made a description how to solve this problem, hoping somebody knowing 
> his way in the sipp code but knowing less about unix process handling 
> can easily add it. You can find the description below Harry's mail, 
> based on the code version 1.1rc6.
>
> Best regards,
>
>   MarcVD
>

Marc,

thanks for this contribution.
What about ignoring SIGCLD?
There are two places where SIPp forks: for the "system" command and for 
the background mode. In both places, this seems like an acceptable solution.

What do you think?

Olivier.


-------------------------------------------------------------------------
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

Reply via email to