From owner-freebsd-questions@FreeBSD.ORG Sun Dec 19 19:27:31 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 F333316A4CE for ; Sun, 19 Dec 2004 19:27:30 +0000 (GMT) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DDD243D49 for ; Sun, 19 Dec 2004 19:27:30 +0000 (GMT) (envelope-from cpghost@cordula.ws) Received: from bsdbox.farid-hajji.net (bsdbox [192.168.254.3]) by fw.farid-hajji.net (Postfix) with ESMTP id 5DBA24B79F; Sun, 19 Dec 2004 20:27:18 +0100 (CET) Date: Sun, 19 Dec 2004 20:27:29 +0100 From: cpghost@cordula.ws To: Erik Norgaard Message-ID: <20041219192729.GA1668@bsdbox.farid-hajji.net> References: <41C5A5A1.5000401@locolomo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41C5A5A1.5000401@locolomo.org> User-Agent: Mutt/1.5.6i 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 19:27:31 -0000 On Sun, Dec 19, 2004 at 05:00:33PM +0100, Erik Norgaard wrote: > Now the problem is that every time I exit some console program, less, > man, vi or a remote shell and return to the shell (bash 2.05) in Eterm, > the console hangs for some random time before giving me back my CLI. 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. > I have no such problems on 4.8 with bash2 or 5.3 with bash3, when I > login with ssh from my local Eterm console. I have had the problem since > upgrading to 6.0 from 5.2.1, but I can't exclude that this may be a > problem with Eterm (0.9.2_1). 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. Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/