From owner-freebsd-security@FreeBSD.ORG Sat Sep 10 10:03:22 2005 Return-Path: X-Original-To: freebsd-security@freebsd.org Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C65D16A41F for ; Sat, 10 Sep 2005 10:03:22 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 827A243D45 for ; Sat, 10 Sep 2005 10:03:21 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id j8AA3F2O020956; Sat, 10 Sep 2005 14:03:15 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id j8AA3Aoh020954; Sat, 10 Sep 2005 14:03:10 +0400 (MSD) (envelope-from yar) Date: Sat, 10 Sep 2005 14:03:10 +0400 From: Yar Tikhiy To: Nielsen Message-ID: <20050910100309.GA19194@comp.chem.msu.su> References: <431F6941.20006@gmail.com> <20050908001830.6A33270DCDB@mail.npubs.com> <431F841A.1060302@mawer.org> <20050909063328.GA47579@comp.chem.msu.su> <20050909213137.C0C3470DBC4@mail.npubs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050909213137.C0C3470DBC4@mail.npubs.com> User-Agent: Mutt/1.5.9i Cc: freebsd-security@freebsd.org, talonz Subject: Re: ee using 99% cpu after user ssh session terminates abnormaly X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Sep 2005 10:03:22 -0000 On Fri, Sep 09, 2005 at 09:31:38PM +0000, Nielsen wrote: > Yar Tikhiy wrote: > > On Thu, Sep 08, 2005 at 10:21:46AM +1000, Antony Mawer wrote: > >>Another "me too" -- usually when we notice our server (running FreeBSD > >>4.11) starting to crawl, the culprit is an "ee" session using up 99% > >>cpu. I just reproduced it then by logging in via ssh, running "ee" (not > >>opening any file) and then killing the Putty window. > > > > > > BTW, isn't the problem in bin/65892? > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=65892 > > For the record the same thing happens with basically any ncurses > program. Midnight commander has the same behavior for example. I'd like to rejoin that my favourite mutt-devel built against ncurses shipped with 4.11-RELEASE doesn't display this kind of behaviour. Perhaps it's Midnight commander that is really buggy, eh? As for ee, the fix from bin/65892 appears to have been applied to CURRENT and 5-STABLE, but not to 4-STABLE. Care to test the fix in 4.11 or 4-STABLE? It should be 100% safe. -- Yar