From owner-freebsd-questions@FreeBSD.ORG Sun Dec 19 20:52:44 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30B5B16A4CE for ; Sun, 19 Dec 2004 20:52:44 +0000 (GMT) Received: from top.daemonsecurity.com (FW-182-254.go.retevision.es [62.174.254.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC9B143D5A for ; Sun, 19 Dec 2004 20:52:43 +0000 (GMT) (envelope-from norgaard@locolomo.org) Received: from [192.168.0.32] (charm.daemonsecurity.com [192.168.0.32]) by top.daemonsecurity.com (Postfix) with ESMTP id 61D15FD008; Sun, 19 Dec 2004 21:52:42 +0100 (CET) Message-ID: <41C5EA17.5040300@locolomo.org> Date: Sun, 19 Dec 2004 21:52:39 +0100 From: Erik Norgaard User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041114 X-Accept-Language: en, en-us, da, it, es MIME-Version: 1.0 To: cpghost@cordula.ws References: <41C5A5A1.5000401@locolomo.org> <20041219192729.GA1668@bsdbox.farid-hajji.net> In-Reply-To: <20041219192729.GA1668@bsdbox.farid-hajji.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD Questions Subject: Re: Getting back my shell is slow, Eterm/bash X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 20:52:44 -0000 cpghost@cordula.ws wrote: > I've noticed this too, but not only with the console. Just wild > guessing: the scheduler needs a long time to wake up processes > that have been swapped out. I don't know if this bug has been (completely) > fixed yet, 'cause I have no machine that I could upgrade right now. > > Just check if the sleepy shell has been swapped out before. This bug has > been often reported in disguise (X takes long time to exit, ssh takes > long time to connect, whatever). It's often not the exiting process' > fault, but the swapped out parent's or daemon's long wakeup latency. > > But again, I'm just wildguessing. This bug may well have been fixed > since last time I've cvsup-ed. Thanks, at least I have a good explanation that doesn't suggest I am just overlooking the obvious :-) I have only noticed it under X, and only with the shell, and only when terminating some program started from the console. But, I'll be patient and try another update :-) Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2