Date: Wed, 15 Feb 2012 01:58:56 -0800 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Julian Elischer <julian@freebsd.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: freebsd 9-stable TOP problem from around Jan 10 Message-ID: <20120215095856.GA19213@icarus.home.lan> In-Reply-To: <4F3B5A01.4090109@freebsd.org> References: <4F3A1A19.7010803@freebsd.org> <CAN6yY1umQGASmFBN_=-X_OBtLsCTzrVYH4u6H--4-U-0f_tZyw@mail.gmail.com> <4F3AEFA5.1020906@freebsd.org> <20120215002036.GA9938@icarus.home.lan> <4F3B5A01.4090109@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 14, 2012 at 11:08:49PM -0800, Julian Elischer wrote:
> On 2/14/12 4:20 PM, Jeremy Chadwick wrote:
> >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<julian@freebsd.org> 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.
> it seems to have stopped doing it for no apparent reason
>
> will keep an eye on it. and save this email away for when it does it
> again.
>
> >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.
>
> SC|screen|VT 100/ANSI X3.64 virtual terminal:\
Sorry, I'm quite wrong here on the last point. Somehow my manual search
in vi did not come up with anything in /etc/termcap for screen, yet
there is absolutely a definition for it in RELENG_8. PEBKAC. :-)
--
| 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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120215095856.GA19213>