public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista•com>
To: Dan Kegel <dank@kegel•com>
Cc: zjzhou@newrocktech•com, "'Jaap-Jan Boor'" <jjboor@aimsys•nl>,
	linuxppc-embedded@lists•linuxppc.org
Subject: Re: display top CPU processes top tool
Date: Fri, 05 Sep 2003 11:39:38 -0500	[thread overview]
Message-ID: <3F58BC4A.1020509@mvista.com> (raw)
In-Reply-To: <3F58B305.7050007@kegel.com>


I bet that top is linked with ncurses instead of termcap.  As such look
at /usr/share/terminfo on the target and make sure the appropriate
directories and terminal emulations are there.

--Mark

Dan Kegel wrote:
>
> John Zhou wrote:
>
>> Jaap-Jan wrote:
>>
>>> On vrijdag, sep 5, 2003, at 10:26 Europe/Amsterdam, John Zhou wrote:
>>>
>>>> top: Unknown terminal "ansi" in $TERM
>>>> top: Unknown terminal "VT100" in $TERM
>>>
>>>
>>> Do you have a /etc/TERMCAP ?
>>
>>
>> Yes. I have a /etc/TERMCAP. But it's still failed. need other changes ?
>
>
> Use strace to see what it's looking for.
> - Dan
>
>
> --
> Dan Kegel
> http://www.kegel.com
> http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
>
>
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-09-05 16:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 13:43 Memory Profiling Tool mss59
2003-09-02 20:51 ` Dan Kegel
2003-09-04 11:02   ` Is there any tool like purify(memory leak check tool) for Embedded Linux/ELDK environment John Zhou
2003-09-04  5:58 ` Memory Profiling Tool Der Herr Hofrat
2003-09-04 14:42   ` Dan Kegel
2003-09-05  8:26     ` display top CPU processes top tool John Zhou
2003-09-05  9:02       ` Jaap-Jan Boor
2003-09-05  9:23         ` John Zhou
2003-09-05 16:00           ` Dan Kegel
2003-09-05 16:39             ` Mark Hatle [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F58BC4A.1020509@mvista.com \
    --to=fray@mvista$(echo .)com \
    --cc=dank@kegel$(echo .)com \
    --cc=jjboor@aimsys$(echo .)nl \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    --cc=zjzhou@newrocktech$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox