From owner-freebsd-current@FreeBSD.ORG  Fri Oct 22 19:42:05 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 1B72E16A4CF; Fri, 22 Oct 2004 19:42:05 +0000 (GMT)
Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E989643D2F; Fri, 22 Oct 2004 19:42:04 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from elischer.org (julian.vicor-nb.com [208.206.78.97])
	by mail.vicor-nb.com (Postfix) with ESMTP
	id A81707A403; Fri, 22 Oct 2004 12:42:04 -0700 (PDT)
Message-ID: <4179628C.4010409@elischer.org>
Date: Fri, 22 Oct 2004 12:42:04 -0700
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516
X-Accept-Language: en, hu
MIME-Version: 1.0
To: Giorgos Keramidas <keramida@freebsd.org>
References: <20041022112947.GA96234@orion.daedalusnetworks.priv>
	<20041022133333.GA561@bsdbox.farid-hajji.net>
	<20041022142603.GA43820@orion.daedalusnetworks.priv>
In-Reply-To: <20041022142603.GA43820@orion.daedalusnetworks.priv>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
cc: cpghost@cordula.ws
Subject: Re: delayed process exit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2004 19:42:05 -0000



Giorgos Keramidas wrote:

>On 2004-10-22 15:33, cpghost@cordula.ws wrote:
>  
>
>>The problem is not with the exiting process, but with the wakeup
>>of its parent. There seems to be some bug in the scheduler that
>>results in LONG (1 to 5 seconds) delays to wakeup processes that
>>have been swapped out. Nearly every swapped out process can be
>>affected by this bug.
>>    
>>
>
>Ah, I see... Thanks for the detailed explanation!
>
>At least, now I'm not worried that something I did locally has caused
>the problem.
>
>  
>

there is a fix in the works...

>  
>