From owner-freebsd-stable@FreeBSD.ORG Wed Feb 15 00:20:38 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92615106566C for ; Wed, 15 Feb 2012 00:20:38 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by mx1.freebsd.org (Postfix) with ESMTP id 7786A8FC13 for ; Wed, 15 Feb 2012 00:20:38 +0000 (UTC) Received: from omta07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by qmta07.emeryville.ca.mail.comcast.net with comcast id a0D11i0051GXsucA70LeLU; Wed, 15 Feb 2012 00:20:38 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta07.emeryville.ca.mail.comcast.net with comcast id a0Ld1i00E1t3BNj8U0Ld98; Wed, 15 Feb 2012 00:20:37 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 0A83E102C1E; Tue, 14 Feb 2012 16:20:37 -0800 (PST) Date: Tue, 14 Feb 2012 16:20:37 -0800 From: Jeremy Chadwick To: Julian Elischer Message-ID: <20120215002036.GA9938@icarus.home.lan> References: <4F3A1A19.7010803@freebsd.org> <4F3AEFA5.1020906@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F3AEFA5.1020906@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Stable Subject: Re: freebsd 9-stable TOP problem from around Jan 10 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2012 00:20:38 -0000 On Tue, Feb 14, 2012 at 03:35:01PM -0800, Julian Elischer wrote: > On 2/14/12 10:38 AM, Kevin Oberman wrote: > >On Tue, Feb 14, 2012 at 12:23 AM, Julian Elischer wrote: > >>Has anyone else seen a problem with top -H -S? > >> > >>after a short while the screen gets more and more corrupted.. > >> > >>hitting ^L or turning off S& H modes helps .. for a while. > >> > >>If this is a known fixed problem, let me know but I need to co-ordinate with > >>others > >>to upgrade the machine in question. > >Not seeing it here on 9-stable. Could it be a display issue? I am > >using gnome-terminal with TERM defined as 'xterm'. > > yeah I'm on a mac with iterm, but running through 'screen' . > > it's never been a problem before.. just since we upgraded to 9-stable. If you remove GNU screen from the picture does the problem go away? If so, I'm not surprised. :-) Make sure that when you're using GNU screen, that all shells launched "under/within" screen have TERM=screen. If they don't, then this is almost certainly the problem -- GNU screen "translates" between terminal types, meaning it translates its own terminal type ("screen") into whatever TERM is currently attached ("xterm", "iterm", whatever). See the last 4 paragraphs of my post here to understand what exactly GNU screen is doing: http://lists.freebsd.org/pipermail/freebsd-stable/2011-June/063052.html So, in general, make sure your dotfiles and so on don't mess about with the $TERM environment variable and you should generally be okay. If within GNU screen TERM=screen and you see the problem, but outside of screen you use TERM=xterm (or something else) but don't see the problem, then I would almost certainly blame GNU screen. If you're looking for something that simply keeps a terminal running in the background, try nohup or tmux. Alternately, possibly someone added a "screen" entry to /etc/termcap on RELENG_9? I don't use 9 so I have no way to confirm this, but on 8 there is no such entry. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |