From owner-freebsd-threads@FreeBSD.ORG Mon Jul 25 06:16:30 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E86C916A41F for ; Mon, 25 Jul 2005 06:16:30 +0000 (GMT) (envelope-from warlock@voip.kg) Received: from mail.elcat.kg (imap.elcat.kg [212.42.96.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id E234C43D5C for ; Mon, 25 Jul 2005 06:16:28 +0000 (GMT) (envelope-from warlock@voip.kg) Received: from localhost (localhost [127.0.0.1]) by mail.elcat.kg (Postfix) with ESMTP id 4D008419706; Mon, 25 Jul 2005 12:16:23 +0600 (KGST) Received: from mail.elcat.kg ([127.0.0.1]) by localhost (imap.elcat.kg [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54406-17; Mon, 25 Jul 2005 12:16:22 +0600 (KGST) Received: from warcomp.elcat.kg (warcomp.elcat.kg [212.42.96.26]) by mail.elcat.kg (Postfix) with ESMTP id 9680F4196B2; Mon, 25 Jul 2005 12:16:22 +0600 (KGST) From: Roman Streltsov Organization: Elcat To: freebsd-threads@freebsd.org Date: Mon, 25 Jul 2005 12:16:22 +0600 User-Agent: KMail/1.8.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507251216.22500.warlock@voip.kg> X-Virus-Scanned: by amavisd-new at elcat.kg X-Spam-Status: No, hits=-56.743 tagged_above=-999 required=999 tests=[ALL_TRUSTED=-10, AWL=3.257, LOCAL_RCVD=-50] X-Spam-Level: Cc: Ady_Li@trendmicro.com.cn Subject: Re: system scope threads entering STOP state X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2005 06:16:31 -0000 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@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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >