Date: Mon, 25 Jul 2005 15:06:04 +0800 From: <Ady_Li@trendmicro.com.cn> To: <julian@elischer.org>, <warlock@voip.kg> Cc: freebsd-threads@freebsd.org Subject: RE: system scope threads entering STOP state Message-ID: <E1DCD76CEF4ABF4CB1334CFAC1229588378DF9@CDCEXMAIL01.tw.trendnet.org>
next in thread | raw e-mail | index | archive | help
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@elischer=2Eorg] Sent: 2005=C4=EA7=D4=C225=C8=D5 14:29 To: Roman Streltsov Cc: freebsd-threads@freebsd=2Eorg; 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=2E Roman Streltsov wrote: >It looks like a failure in signal handling=2E The faster box has much more= chances to avoid extreme conditions=2E > > >On Monday 25 July 2005 10:39, Ady_Li@trendmicro=2Ecom=2Ecn wrote: > =0D > >>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=2E >> >>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=2E But when they launch= about 500 client-processes to >> connect to my program in the same machine, my program will be stoped=2E= But In a 2-cpu-machine, >>this occasion occurs fewly=2E >> >>I found Mr guy helmer has confronted this problem, could u tell me how= did u solve it? >> >>Thank in advance for any helps=2E >> >> >>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=2E 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=2E >>_______________________________________________ >>freebsd-threads@freebsd=2Eorg mailing list >>http://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-threads >>To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd= =2Eorg" >> >> =0D >> >_______________________________________________ >freebsd-threads@freebsd=2Eorg mailing list >http://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-threads >To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd= =2Eorg" > =0D > 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= =2E 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=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1DCD76CEF4ABF4CB1334CFAC1229588378DF9>