Date: Sat, 10 Sep 2005 14:03:10 +0400 From: Yar Tikhiy <yar@comp.chem.msu.su> To: Nielsen <nielsen@memberwebs.com> Cc: freebsd-security@freebsd.org, talonz <talonz@gmail.com> Subject: Re: ee using 99% cpu after user ssh session terminates abnormaly Message-ID: <20050910100309.GA19194@comp.chem.msu.su> In-Reply-To: <20050909213137.C0C3470DBC4@mail.npubs.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050910100309.GA19194>