Strange top(1) output

[Giorgos Keramidas]

On 2005-05-12 13:49, Dominic Marks <dom at goodforbusiness.co.uk> wrote:
>On Thursday 12 May 2005 11:39, you wrote:
>> That's an option too.  I'm currently trying to get top to display
>> something like this (80 columns are used for text, so use a slightly
>> wider terminal to view this properly:
>>
>> -------------------------------------------------------------------------------+
>> last pid: 11090;  load averages:  1.27,  1.26,  0.86    up 0+01:11:11  03:07:43|
>> 71 processes:  3 running, 68 sleeping                                          |
>> CPU states: 11.2% user,  0.0% nice, 77.1% system,  0.8% interrupt, 10.9% idle  |
>> Mem: 50M Active, 348M Inact, 70M Wired, 20M Cache, 60M Buf, 6340K Free         |
>> Swap: 5000M Total, 5000M Free                                                  |
>>                                                                                |
>>   PID USERNAME  PRI NICE   SIZE    RES STATE    TIME   WCPU COMMAND/NTHR       |
>>  4738 root      108    0  1360K   836K RUN      1:28 22.80% find/1             |
>>   638 giorgos    -8    0 13496K  4672K pcmwr    1:33  1.03% mpg123/1           |
>> 11062 giorgos    96    0  2428K  1520K RUN      0:00  1.54%  top/1             |
>> -------------------------------------------------------------------------------+
>
> If you don't mind I will share my thoughts on these changes.

Thanks :)

> > This includes at least the following changes (some not visible):
> >
> >   + The entire header line is limited to the window width too.
> >   + The USERNAME column is hard-limited to 8 characters.
>
> This makes me a little uneasy. Its a typical idiom, at least at my Business,
> to have usernames which are of the form 'firstnamelastname', for this reason
> they can be quite long and often the first 5-8 characters will be frequently
> repeated, for example the following contrived names:
>
> rogermoore -> rogermoo
> rogermoody -> rogermoo
> charlottelane -> charlott
> charlottedaniels -> charlott
>
> [...]
> If this behaviour could be turned on and off, I'd be very happy.

Hmmm, not a bad idea.  You have a good point here.

> >   + When the view is toggled between processes/threads, the NTHR part
> >     becomes the thread ID of the particular thread.
>
> Okay, not really sure what this will look like to me but no need to explain
> I'll wait until they hit -CURRENT and see for myself.

Instead of displaying a single named/7 line, which would mean that there
is a named process with 7 threads, in "thread mode" you would see 7
lines with named/0, named/1, named/2, ... which would be the thread IDs
of the distinct threads.