system scope threads entering STOP state

[David Xu]

You should tell us which version of FreeBSD you are using.


David Xu

Ady_Li at trendmicro.com.cn wrote:

>if i use vfork instead fork with compiling with libthr, my program will block in vfork at beginning,
>if i use fork with compiling with libthr, my program cannot be killed by input kill -9
>
>
>-----Original Message-----
>From: Julian Elischer [mailto:julian at elischer.org]
>Sent: 2005Äê7ÔÂ25ÈÕ 14:29
>To: Roman Streltsov
>Cc: freebsd-threads at freebsd.org; Ady Li (RD-CN)
>Subject: Re: system scope threads entering STOP state
>
>
>it may be worth looking at libthr too
>as it (the alternate threading library)
>is sufficiently different in this regard.
>  
>
>>Roman Streltsov wrote:
>>
>>    
>>
>>>It looks like a failure in signal handling. The faster box has much more chances to avoid extreme conditions.
>>>
>>>
>>>On Monday 25 July 2005 10:39, Ady_Li at trendmicro.com.cn wrote:
>>>
>>>
>>>      
>>>
>>>>Dear all,
>>>>
>>>>I have found this program too, I wrote a backgound server program which create out 14
>>>>SYSTEM_SCOPE threads, and fork a child process out in main-thread every inteval-times
>>>>and waitpid it with NOHUP, but run for sometimes, this program would be in STOP state,
>>>>and unkillabled.
>>>>
>>>>By the way, This occasion was found often in machines with single CPU,  Our QA  didnot tell me
>>>>this question when they run it with few clients. But when they launch about 500 client-processes to
>>>>connect to my program in the same machine, my program will be stoped. But In a 2-cpu-machine,
>>>>this occasion occurs fewly.
>>>>
>>>>I found Mr guy helmer has confronted this problem, could u tell me how did u solve it?
>>>>
>>>>Thank in advance for any helps.
>>>>
>>>>
>>>>Best Regards,
>>>>Ady Li
>>>>[TEL](86)25- 83190788x656
>>>>
>>>>
>>>>
>>>>TREND MICRO EMAIL NOTICE
>>>>The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
>>>>_______________________________________________
>>>>freebsd-threads at freebsd.org mailing list
>>>>http://lists.freebsd.org/mailman/listinfo/freebsd-threads
>>>>To unsubscribe, send any mail to "freebsd-threads-unsubscribe at freebsd.org"
>>>>
>>>>  
>>>>
>>>>        
>>>>
>>>_______________________________________________
>>>freebsd-threads at freebsd.org mailing list
>>>http://lists.freebsd.org/mailman/listinfo/freebsd-threads
>>>To unsubscribe, send any mail to "freebsd-threads-unsubscribe at freebsd.org"
>>>
>>>
>>>      
>>>
>>
>>TREND MICRO EMAIL NOTICE
>>The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
>>_______________________________________________
>>freebsd-threads at freebsd.org mailing list
>>http://lists.freebsd.org/mailman/listinfo/freebsd-threads
>>To unsubscribe, send any mail to "freebsd-threads-unsubscribe at freebsd.org"
>>
>>
>>    
>>