From owner-freebsd-current Thu Jul 11 23:33:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 764DB37B400 for ; Thu, 11 Jul 2002 23:33:33 -0700 (PDT) Received: from gnuppy.monkey.org (wsip68-15-8-100.sd.sd.cox.net [68.15.8.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06BAD43E6D for ; Thu, 11 Jul 2002 23:33:33 -0700 (PDT) (envelope-from billh@gnuppy.monkey.org) Received: from billh by gnuppy.monkey.org with local (Exim 3.35 #1 (Debian)) id 17Stze-00013E-00; Thu, 11 Jul 2002 23:33:30 -0700 Date: Thu, 11 Jul 2002 23:33:30 -0700 To: Julian Elischer Cc: current@FreeBSD.ORG, Bill Huey Subject: Re: Another KSE problem? Message-ID: <20020712063330.GA4021@gnuppy.monkey.org> References: <20020712014336.GA3223@gnuppy.monkey.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i From: Bill Huey Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jul 11, 2002 at 10:58:56PM -0700, Julian Elischer wrote: > it may be in "NEW" state if it has just been forked. > if so then the "NEW" state is hanging around too long. > it should be fixed tomorrow after testing. What do you mean by just forked ? This is a running process that's block on a kernel of some sort within libc_r. If my reading of the problem is correct, then there might be a problem with signal delivery and things like select/poll. I don't know until I do some investigation. bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message