emo/procps
1
0
Fork 0
Code Issues Pull Requests Packages Releases Activity

New version of top from Jim

Browse Source
This commit is contained in:
Craig Small 2011-03-31 22:15:12 +11:00
parent ee5fd1dce1
commit fd62123562
5 changed files with 4046 additions and 3900 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
.gitignore vendored Normal file
View File

@ -0,0 +1,19 @@
free
kill
pgrep
pkill
pmap
proc/.depend
proc/libproc-3.2.8.so
ps/ps
pwdx
skill
slabtop
snice
sysctl
tload
top
uptime
vmstat
w
watch

845
README.top
View File

@ -1,545 +1,302 @@
Credit for this belongs to: Contents:
Jim / James C. Warner, <warnerjc@worldnet.att.net> DOCUMENT Changes
INTERNAL Improvements
---------------------------------- EXTERNAL Improvements
BUGS Previously Fixed and Preserved
Ok, ok, I yield -- most of what follows has been removed from the manual page BUGS Newly/Nearly Fixed
and packaged separately as this README (hey, it was only TEMPORARY insanity). BUGS/WISH-LISTS That Should Go Bye-bye
BUGS FIXED You Didn't Know You Had
Of course, that means that now absolutely nobody will ever read it. OTHER Changes, Hopefully They Won't Bite You
BENCHMARKS
This is probably a good thing...
DOCUMENT Changes =========================================================
## Table of Contents ---------------------------------------------------## . The entire file was cleaned up, standardized and expanded to include:
# the only darn thing that wasn't in the man page - a new section "2. SUMMARY Display" added for symmetry with Fields
CUSTOMIZING the Sources - nine new fields were added to section "3a. DESCRIPTIONS of Fields"
# the following carry their original topic numbers - a new section "3b. MANAGING Fields" replaced the obsolete section
DIFFERENCES / New Features "2b. SELECTING and ORDERING Columns" section
Interface Etiquette
Expanded Configurable Display Support . I don't know when the explanations for CODE and DATA were changed to
Enhanced Field/Column Management show 'virtual' memory, but I think there's a reason their alternate
Customization Flexibility names contain the word 'resident'. Thus they were changed back to
NOTES and Rantings say 'physical memory'.
The top Binary
Comparing Performance . And as I indicated in a previous email, the former string identifier
Cost of Stuff 'ME' was restored as were the 'h' key/command conventions (vs. <h>).
The top Sources
EXAMPLES of Windows . Also previously mentioned, the 'man2html' program translates top.1 to
The 'A' Mode Command Toggle html with perfect fidelity. I take that to mean there should be no
STACKIN' & WHACKIN' Windows problems with the top.1 source on most other platforms.
ALL TOGETHER Now, Window(s)
INTERNAL Improvements ====================================================
## CUSTOMIZING the Sources ---------------------------------------------## . The old restriction of 26 fields has been lifted. With this new-top
100+ fields are now possible. It currently supports up to 55, of
Listed below are the conditionals available should you wish to recompile which 35 are in use. Adding a new field is almost too easy.
this top. The author's favorite is: PRETEND4CPUS.
. Task row construction has been considerably improved -- both from
That's the #define allowing you to simulate an SMP environment, and a programming perspective and a performance perspective.
(perhaps) impress your friends. It's currently set to display four
separate CPUs, but could easily be changed. . The column highlighting costs for sort field visibility were
virtually eliminated.
Caution: do NOT use this provision in an effort to impress someone
who truly possesses such a machine! The fact that all 4 . The management of the HST_t structures, used for %cpu calculations,
CPUs show the same dynamic results will likely have the was optimized with a hashing scheme. Thus the need for a qsort then
opposite effect. a binary search in each frame was completely eliminated.
. This far more capable new-top executable is 33% smaller.
//#define ATEOJ_REPORT /* report a bunch of stuff, at end-of-job */
//#define CASEUP_HEXES /* show any hex values in upper case */ . The above combine to produce substantially improved performance
//#define CASEUP_SCALE /* show scaled time/num suffix upper case */ whose details are documented below under BENCHMARKS.
//#define CASEUP_SUMMK /* show memory summary kilobytes with 'K' */
//#define POSIX_CMDLIN /* use '[ ]' for kernel threads, not '( )' */
//#define PRETEND2_5_X /* pretend we're linux 2.5.x (for IO-wait) */ EXTERNAL Improvements ====================================================
//#define PRETEND4CPUS /* pretend we're smp with 4 ticsers (sic) */ . Field management has been completely redesigned. It's now embodied
//#define PRETENDNOCAP /* use a terminal without essential caps */ on a single screen where display-ability, position and sort selection
//#define SORT_SUPRESS /* *attempt* to reduce qsort overhead */ can be handled in one place -- for all windows at one time!
//#define STDOUT_IOLBF /* disable our own stdout _IOFBF override */
//#define USE_LIB_STA3 /* use lib status (3 ch) vs. proc_t (1 ch) */ This function is dependent on cursor motion keys and should a device
//#define WARN_NOT_SMP /* restrict '1' & 'I' commands to true smp */ not have the customary arrow keys, alternatives are provided and
documented under section '3b. MANAGING Fields'.
## 6. DIFFERENCES / New Features ---------------------------------------## . The following new fields have been added:
The following summarizes differences between this top and your Group Id
former top. It was originally based on procps-2.0.7. However, Minor Page Faults
except for the separate/summary CPU toggle, all of these differ- Number of Threads
ences also apply through procps-2.0.10. Process Group Id
Real User Id
6a. Interface Etiquette Saved User Id
-*- Input and output are far more carefully implemented in Saved User Name
this top. You won't be subjected to 4 - 5 'Unknown command' Session Id
messages should you press the wrong key. Tty Process Group Id
-*- You need suffer a confirmation message only when the results . User interactive line oriented input now provides for true line
of a command are not obvious by their effects on the display. editing supported by these new keys:
Left/Right arrow keys, Delete key, Backspace and
-*- The Help screen will no longer overflow, even when running Home/End keys (likely limited to xterm, not terminal)
with a 24 row xterm (vt100).
. User filtering via the -u | -U interactive commands is now window
-*- The fields selection/ordering screens do not carelessly based which means that different windows could be used to filter
destroy important information through unintended line wraps. different users.
-*- Should you narrow a xterm window to less than 80 columns . Signal handling has been normalized and is now consistent regardless
while this top is running, you will not be left with an of the particular top screen a user may have been using.
utterly worthless, embarrassing display.
. The 'i' toggle now shows any task that has used *some* cpu since the
6b. Expanded Configurable Display Support last screen update. It's no longer limited to just running tasks.
-*- In an SMP environment, you can choose between a summary dis-
play or you may show each cpu separately. No longer must . The summary area 'task states' line now reflects either 'Threads'
this choice be irrevocably made at startup. or 'Tasks' depending on the -H toggle.
-*- There are new fields and with this top, any field is
selectable for sorting. Plus, your sorted column can be BUGS Previously Fixed and Preserved ======================================
instantly reversed with just a single keystroke. ( but not necessarily literally)
. 228822, suspending top leaves xterm in slightly messed-up state
-*- You may optionally apply 2 distinct types of highlighting to . 256376, segfaults, if the xterm is to small
running tasks and/or sorted columns. With this top, you'll . 320289, segv on sigwinch
be able to instantly spot running tasks and always know the . 351065, wrong highlight 1st column (escape characters displayed)
current sort field. . 358724, accepts extra numeric args
. 378695, seg fault if "/proc" is not mounted
-*- While you could continue to use the more familiar (and . 426782, UID field is too narrow
boring) monochrome display, you might want to try this top's . 458986, should check xterm for EOF/EIO
new color display. You can even create your own unique col- . 459890, Irix mode should use %#4.1f when threads shown
ors used in summaries, messages, headings and tasks, each of
which can be made persistent until you choose to change them.
BUGS Newly/Nearly Fixed ==================================================
-*- Up to four separate windows can be displayed simultaneously, . 225542, 'Unknown command' message blocks further commands
giving you four separate ways to sort and view the tasks cur- The message is now displayed using usleep for 1.25 seconds, instead
rently cluttering up your system. You could have one view by of the former full 2 seconds. And while it still blocks further
pids, another by cpu usage, yet another showing memory con- commands, the delay is much more tolerable.
sumption. You get the idea...
Can we consider this bug 'nearly' fixed?
-*- Each window comes with pre-configured (but user configurable)
fields and you can size each window individually. . 410292, interface error when using backspace
Full line editing was added but could be disabled via a #define.
-*- Virtually every one of this top's options (summaries, fields, And via that define, even under basic termios support, the backspace
colors, sorted column, etc.) is separately configurable for problem was cured.
each of those four windows.
. 567509, top idle command ('i') not working for threaded programs
Heck, you can even change a window's name, if you don't care Since the 'i' command now reflects tasks that have used *some* cpu,
for top's choices. Your changes will be reflected not only and is no longer dependent on an 'R' state, I *believe/hope* this
when you're in what top calls alternate-display mode but also bug has been swatted.
on his special new 'Windows' help screen.
-*- And, [ ** Drum-Roll + Ta-Da ** ] with just one keystroke you BUGS/WISH-LISTS That Should Go Bye-bye ===================================
can quickly switch between full-screen and multiple window . 340751, wish for hostname to benefit multiple top sessions
modes! Or, with a different keystroke, toggle a single win- Craig's suggestion regarding symlinks is the perfect solution.
dow Off for now, then On again later!! How dare Craig say that the solution was "not ideal" !
6c. Enhanced Field/Column Management . 586497, wish for graceful degradation on small screen sizes
-*- Many Field/Column names have been changed to make them more This objective could be accomplished by setting up 2 symlinks for
intuitive, more self-descriptive. And with this top you top, personalizing them for the 2 tiny phone displays, then writing
won't be fooled with field choices that are "not yet imple- the respective configuration files.
mented".
I shudder at the programming effort suggested by Paul. And when it
-*- Task memory statistics are more meaningful and more accurate. was done you'd find everybody else would have different criteria.
-*- You'll finally have complete display integrity regardless of
field selections, their order or screen width. And that BUGS FIXED You Didn't Know You Had =======================================
means the command column no longer need be kept as the right- . Without amplifying the dirty details, the long standing occasionally
most field, lest your screen turn to <bleep> when all the reported display corruption, and an unreported source of performance
following columns get misaligned. degradation, has been eliminated. The cure is in the elimination of
the Pseudo_cols variable and the improved PUFF macro.
6d. Customization Flexibility
-*- You have complete program naming freedom with no internal . Line oriented input was not sensitive to screen width. Thus a user
ties to a specific personal configuration file. Symbolic could hold down any key and ultimately line wrap, overwriting the
links could be used to establish different configuration columns header and the entire screen. New top prevents this.
files reflecting the different personalities of your cus-
tomized "tops", under whatever aliases you've used. . User filtering (-u|-U) via a user ID (not name) now validates that
number. The old-top just made sure it was numeric, then blindly
Thus, you could have an alias for running top in 'Batch displayed no matching users (i.e. an empty window).
mode', another for when you work from the Linux console and
maybe a third used with X-Windows. All of that, yet still . The threads toggle ('H') is no longer window based but more properly
just a single binary image! applies to all windows. The previous implementation produced the
following aberration if multiple windows were being shown:
-*- All of your configuration choices can be preserved in a per- . -H would be acknowledged and applied to all visible windows
sonal configuration file, including any changes made on a . keying 'a' or 'w' would silently turn it off
per-window basis. Thus, once you personalize things they . then keying -H would turn it back on, but the user expected off
remain personalized until you decide to change them again.
This top has been completely cured of: . If you hit ^Z on any help or fields screen to suspend old-top, after
i-cant-remember-so-please-do-that-all-over-again issuing 'fg' you would then be left with a seemingly hung application
( and again, and again ... ) inviting ^C. In truth, one could recover with the space bar, but that
was far from intuitive.
The bottom line is this: if you save your configuration
before quitting top, upon restart the display will appear . The old-top consistently writes 1 extra byte for each task row or 1
exactly as you left it. And that means you no longer have to byte too few for columns headers, depending on your perspective.
keep top running until-the-end-of-time (ok, a long time The new top writes the same number of bytes for each.
anyway), lest your customizations go bye-bye.
. By failing to clear to eol, old top left the display in a terrible
state after exiting a 'fields' screen when only a few columns were
## 7. NOTES and Rantings -----------------------------------------------## being displayed.
7a. The top Binary
To whom it may (should) concern: this top, even with its vastly . The old-top used a zero value for the L_NONE library flag which could
expanded capabilities, is only slightly larger than the old top. cause repeated rebuilding of columns headers with each frame. In truth,
Were it not for extensive help text and additional sort callbacks, this was not likely to happen in real life since only two fields actually
it would be smaller. used that flag. However, if it did happen, performance could be degraded
Throw source carelessly at objectives, it will by 800%.
produce equally careless machine instructions.
example: (num_pages - an_address)/1024 == duh?
kicker: document result as broken, due to elf! OTHER Changes, Hopefully They Won't Bite You =============================
---------------------------------------------- . The undocumented TOPRC environment variable is no longer supported.
I know you're out there, are you getting this? Any similar need can be met through a symlink alias.
Now, as for all those new capabilities like colors and windows and . The use of environment variables to override terminal size is now
highlighting, you'd expect this top to be the "mother of all pigs" off by default but could be enabled through '#define TTYGETENVYES'.
compared to old top -- right?
. The global 'bold enable' toggle is active by default and thus agrees
Yea, with this top expect following piglets: with the documentation. It's been wrong ever since Al's wholesale
. A smaller virtual image and resident footprint 'cosmetic' changes in procps-3.2.2.
. Slightly fewer major page faults
. A large reduction in minor page faults for SMP . Task defaults now show bold (not reverse) and row highlighting.
. The same or better response time This agrees with what was always stated in the documentation.
. The same or even less CPU costs
. The 'H' toggle (thread mode) is not persistent. Persistence can be
Ideally any comparison of the old and new top should be against achieved with a simple shell script employing the -H switch.
the same libproc format (32-bit or 64-bit tics) and run in a true
or simulated SMP environment (producing separate CPU stats). This . Then 'g' and 'G' commands were reversed to reflect their likely use.
latter requirement will coax old top into handling his own
'/proc/stat' access -- something this top always does, but with
less cost. BENCHMARKS ===============================================================
Tested as root with nice -10 and using only common fields
7b. Comparing Performance ( on a pretty old, slow laptop under Debian Lenny )
Even with equivalent libraries and '/proc/stat' access, it's dif- but rcfiles specified identical sort fields and identical
ficult to accurately compare tops using their own displays. settings for the 'B', 'b', 'x' and 'y' toggles (even though
Results for these cpu-intensive programs (who frequently exceed the defaults are not necessarily identical).
their time-slice) generally show a wide disparity in %CPU. This
is due to differing call patterns, kernel preemptions and the tim- In every case new-top outperforms old-top, but I've shown %
ing of process snapshots. For slightly better results, start each improvements for only the most significant. Those cases mostly
program with the following commands: involve colors with both row & column highlighting. I suggested
./old-top -d 0.5 above that the highlighting cost was virtually eliminated in
nice -n-10 ./new-top -d 0.4 new-top, and these tests bare that out.
While actually putting this top at a performance disadvantage, the Note the much smaller differences for new-top between the 24x80
higher scheduling priority and staggered timing will periodically window results and full screen (but don't mix apples_terminal
yield a somewhat truer picture. You could even reverse those with oranges_xterm). This is a reflection of the simplification
roles and get similar results. of task row construction, also mentioned above.
The most consistent performance results will be obtained 'off- It's always been the case that any top in an xterm outperforms
line', using your shell's time pipe or the time program itself. that top under the terminal application, even when the xterm
And even in a single processor environment or without equivalent provides additional rows and columns. It's true below with
libraries, total cpu costs (user time + system time) are similar. Gnome and it was true nine years ago under KDE.
However, this top's cpu costs ARE influenced by the capabilities ----------------------------------------------------------
you choose to exploit, even if they don't SEEM to be reflected in The following comparisons were run with:
such timings. So let's examine some... 100 tasks & 160 threads
-d0 -n5000
7c. Cost of Stuff new-top old-top
Colors Cost -- Nada (almost). xterm 24x80
Once the terminfo strings are built (at and during a user's a 1 win, lflgs_none 11.2 secs 51.8 secs + 462.6%
behest) they are SAVED with each window's stuff. And while 1 win, default 61.0 secs 66.8 secs
there will be extra tty escape sequences transmitted because of 1 win, colors w/ x+y 61.3 secs 83.0 secs + 135.4%
colors, it makes no difference which 'char *' is actually used. 1 win, thread mode 88.3 secs 94.2 secs
b 1 win, every field on 99.7 secs 106.0 secs
Highlighting Cost -- Nada (maybe), or blame it on Rio. 1 win, cmdline 71.2 secs 76.6 secs
On second thought, let's blame it on the user. 4 wins, defaults 101.3 secs 107.2 secs
4 wins, colors w/ x+y 101.5 secs 122.8 secs + 121.0%
For row highlighting, there is only the cost of those extra tty
escape sequences (same as for colors). For column highlight- xterm, full screen (53x170)
ing, there is a fairly significant cost associated with column a 1 win, lflgs_none 15.9 secs 54.2 secs + 340.9%
transition management combined with even more tty output. 1 win, default 70.0 secs 73.2 secs
These increased costs are incurred on every task display row. 1 win, colors w/ x+y 69.4 secs 131.3 secs + 189.2%
1 win, thread mode 97.6 secs 102.6 secs
Sooo... hey USER -- do NOT highlight COLUMNS. You shouldn't c 1 win, every field on 122.1 secs 128.1 secs
need a constant visual reminder of your chosen sort field. 1 win, cmdline 80.8 secs 83.7 secs
However, if you forget which field top is sorting it can serve 4 wins, defaults 111.4 secs 115.8 secs
as a quick visual reminder. 4 wins, colors w/ x+y 112.0 secs 172.9 secs + 154.4%
Windows Cost -- Nada (if just 1 window). terminal 24x80
If more than 1 window, almost certainly NOT Nada so blame it on a 1 win, lflgs_none 8.9 secs 58.6 secs + 658.4%
reality. Colors are not an issue, but those sort fields are. 1 win, default 70.1 secs 80.3 secs
1 win, colors w/ x+y 70.6 secs 157.3 secs + 222.8%
If we could trust the user to always select the same 'c' state, 1 win, thread mode 104.7 secs 120.5 secs
'S' state and sort field (hey, why ya got multiple windows then b 1 win, every field on 111.2 secs 134.5 secs
user, huh?) AND if we can trust someone to recompile top with a 1 win, cmdline 83.8 secs 94.5 secs
#define enabled, then we could achieve 'Nada'. 4 wins, defaults 125.6 secs 146.7 secs
4 wins, colors w/ x+y 125.6 secs 206.9 secs + 176.7%
Ok, not likely, so we're gonna' be doing multiple sorts. BUT,
it may not be as bad as it sounds. Those sorts involve point- terminal, full screen (39x125)
ers only. And, that's as good as it gets ! (right Mr. N?) a 1 win, lflgs_none 9.1 secs 60.6 secs + 665.9%
1 win, default 74.3 secs 88.0 secs
7d. The top Sources 1 win, colors w/ x+y 73.9 secs 314.5 secs + 425.6%
top.h 1 win, thread mode 113.0 secs 140.9 secs
Unlike his predecessor, this top has a proper header file. It b 1 win, every field on 117.7 secs 154.9 secs
contains ONLY declarations, NOT definitions. And there are 1 win, cmdline 87.4 secs 107.2 secs
several conditionals present to help with further customiza- 4 wins, defaults 139.1 secs 166.7 secs
tions and experimentation. All are Off by default. 4 wins, colors w/ x+y 157.3 secs 423.2 secs + 269.0%
top.c ----------------------------------------------------------
Hopefully proves that source code needn't be a disorganized, The following comarisons were run with:
misaligned MESS. And, WHO says a source listing shouldn't 300 tasks & 360 threads
occasionally make you SMILE? Why, top.c even does a darn good -d0 -n3000
job of following the suggestions in a document hardly anybody new-top old-top
seems to observe. xterm, full screen (53x170)
a 1 win, lflgs_none 14.3 secs 79.0 secs + 552.4%
the Linus Torvalds CodingStyle guidelines ... 1 win, default 101.1 secs 104.5 secs
-*- -*- -*- on indentation + etc. -*- -*- -*- 1 win, colors w/ x+y 101.3 secs 140.0 secs + 138.2%
well almost all, except for those stinkin'... 1 win, thread mode 120.1 secs 123.1 secs
c 1 win, every field on 179.8 secs 185.6 secs
I suppose even Linus Torvalds is entitled to err now and again. 1 win, cmdline 124.9 secs 132.8 secs
How so you say? Tabs, me' bucko, stinkin' tabs! That, plus the 4 wins, defaults 174.8 secs 179.2 secs
simplistic position regarding indentation espoused in that other- 4 wins, colors w/ x+y 175.0 secs 215.2 secs + 123.0%
wise excellent document.
terminal, full screen (39x125)
-*- Rant On, and on -*- a 1 win, lflgs_none 12.3 secs 98.5 secs + 800.8%
Let's compare two approaches to the tab/indentation issue with a 1 win, default 117.4 secs 134.0 secs
small code sample using tabs then spaces. This snippet happens to 1 win, colors w/ x+y 111.6 secs 296.1 secs + 265.3%
be the key to top's use of dynamic colors on many static screens, 1 win, thread mode 141.3 secs 155.3 secs
while also ensuring screen width isn't exceeded so as to avoid b 1 win, every field on 197.7 secs 204.8 secs
line wraps. We'll view just the first 40 columns, assuming one 1 win, cmdline 143.9 secs 157.3 secs
wishes to occasionally provide comments to the right of actual 4 wins, defaults 204.0 secs 226.2 secs
code (you do, don't you?). 4 wins, colors w/ x+y 216.9 secs 434.5 secs + 200.3%
Then YOU decide which approach makes the most SENSE! . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stinkin' Tabs versus Spaces: the Linus way notes:
Hey, where'd my +----+----1----+----2----+----3----+----4+ a these results represent the library flags L_NONE zero value and
many code lines | while (*sub_beg) { : thus the hidden cost of rebuilding column headers w/ every frame
up-and-gone-to? | switch (*sub_end: b while every common field was turned on, not all fields could be
| case 0: : displayed due to limited screen width
Gosh, wonder if | \ Tabs Induced / : c only in a full screen xterm window could all common fields
Linus expects a | case 1: : actually be displayed
fellow to stick | + WASTE-Lands! + case 5: :
his comments on | :
the left side?! | + Not a Living + :
| :
Ever see source | + line-of-code + :
with not enough | :
whitespace; and | / To Be Found! \ :
this is better? | default::
| :
Oh lookie here, \ } :
there's just a hint of REAL code! ----> if (0 >= room) b:
/ } /* end: while 'subtrin:
+----------------------------------------+
Spaces versus Stinkin' Tabs: the other way
+----+----1----+----2----+----3----+----4+
Wow, now this is | while (*sub_beg) { :
Visible hackin'! | switch (*sub_end) { :
| case 0: :
Hmmm, wonder how | *(sub_end + 1) = '\0'; :
many programmers | case 1: case 2: case 3: case:
read those lines | case 5: case 6: case 7: case:
from the LEFT to | cap = Curwin->captab[(int:
the RIGHT? This | *sub_end = '\0'; :
"innovation" may | PUTP("%s%.*s%s", cap, roo:
possibly benefit | room -= (sub_end - sub_be:
those particular | sub_beg = ++sub_end; :
kinds of people, | break; :
you agree? Duh! | default: :
| ++sub_end; :
AND, there might | } :
even be room for | if (0 >= room) break; :
unseen comments! | } /* end: while 'subtrings' */ :
+----------------------------------------+
Gosh, I just don't KNOW -- it's such a TOUGH choice...
Oh you Stinkin' Tabs: correspondence, Who-Cares; documentation,
Oh-Alright; even scripts, Well-If-You-Must. But you have NO place
within the code-space of MY C-source listing! So be gone
already!!
In Summation...
- If you want to use tabs to the right of the code, go-for-it.
But PLEASE, not ever in the C-source code-space, thank-you-
kindly. Just use three little ol' spaces (exactly 3, no-more,
no-less) where you WOULD have stuck a stinkin' tab.
We'll get far more READABLE files, much less WAISTED precious
horizontal space, more consistent CURSORS and on, and ON, AND
ON! Plus, without those awful *the-devil's-own-handiwork*, the
aforementioned document need NEVER speak of their EVILS again.
- Lastly, since SPACES (not stinkin' tabs) are SO beneficial,
maybe we should use just a few more of 'em. Some of those C-
thingies are VERY sensitive -- they don't like being TOUCHED
by any other syntax element! Which ones? Why these guys:
braces, reserved words and binary operators
( it's the TRUTH, they told me themselves )
It's so EASY to keep 'em HAPPY! And lo-and-behold, the combi-
nation of <sp>thingy<sp> turns out to be a darn effective bug
repellent, too. So much so, one can actually code while
TOTALLY NUDE yet still avoid them ol' bug-bytes (sic-sic)!
step
down_from
me_punctilious
soap-box_once_again
[1 +5 +5 +5 = huh?]
## 4c. EXAMPLES of Windows ---------------------------------------------##
-*- The 'A' Mode Command Toggle -*-
Here's what you'll see when you first invoke the alternate-display
mode interactive command.
This particular display was produce on a VT100 xterm, with only 24
rows. All four task displays are visible, but they could not be sized
the same. Available lines are parceled out in the fairest way possi-
ble so the last two task displays have an extra line each.
Notice the 'current' window name in the summary area -- it's been
emphasized because the associated task display is visible. Since
1:Def has a task area, the full range of interactive commands would be
at your disposal. But remember, many of those commands will apply
only to window 1:Def.
+--------------------------------------+
1:Def name is bold, |1:Def - 15:46:37 up 16:25, 9 users, :
thus all commands |Tasks: 76 total, 1 running, 75 sle:
will be available. |Cpu(s): 0.7% user, 1.3% system, :
|Mem: 126588k total, 123688k used,:
|Swap: 265032k total, 8232k used,:
|______________________________________:
Tough luck windows |1__PID_USER______PR__NI_%CPU____TIME+_:
#1 & 2 - you lost | 7343 jtwm 16 0 0.9 0:00.59:
one line each -- | 7339 jtwm 9 0 0.0 0:00.02:
guess you'll just |__7337_root_______9___0__0.0___0:01.30:
have to learn how |2__PID__PPID_Command____________TIME+_:
to live with it. | 997 952 kdeinit 17:59.59:
| 1115 952 kdeinit 2:16.47:
|__1803__1116_led_______________1:55.30:
|3__PID_%MEM__VIRT_SWAP__RES_CODE_DATA_:
The #3 & #4 windows | 4634 12.3 15620 0 15m 860 14m :
better not gloat | 7337 11.3 14396 92 13m 36 13m :
over 1 extra line. | 923 10.6 30524 16m 13m 1120 12m :
That user could yet |___991__7.2__9492__316_9176___12_9164_:
sock 'em with the |4_UID_USER_____GROUP____TTY________PID:
'n' command and | 43 xfs xfs ? 806:
take those lines, | 0 ykde users pts/7 5561:
plus others, away! | 0 wgnome users pts/7 5560:
| 0 root root pts/7 5325:
+--------------------------------------+
So, what say we start applying some of those "full range of interac-
tive commands"?
Onward + Downward...
-*- STACKIN' & WHACKIN' Windows -*-
Whoa, hold on mate. Someone has already whacked these windows. See,
there are no task areas for windows 1:Def and 4:Usr. Well, we can at
least retrace their steps...
Here's what was done, after issuing the 'A' command and entering
alternate-display mode.
1) When #1 was the 'current' window, '-' was pressed,
toggling Off the associated task display
( if 'l t m' had been applied to its summary, too )
( then there'll be only a msg line when 'current' )
2) Then the 'w' key was struck to cycle backward,
making 4:Usr the 'current' window
(could have used 'a a a', if one likes to type)
3) Then step #1 was repeated, and bye-bye window #4
4) Finally, window #2 was made the 'current' window
( Q. how many keystrokes were used? )
( A. minimum of 2: 'a a' or 'w w'. )
+--------------------------------------+
No 'l','t','m','1' |2:Top - 15:48:35 up 16:27, 9 users, :
commands have been |Tasks: 75 total, 1 running, 74 sle:
issued here, |Cpu(s): 2.0% user, 0.7% system, :
but... |Mem: 126588k total, 123712k used,:
|Swap: 265032k total, 8232k used,:
|______________________________________:
#2's been changed; |2__PID__PPID_Command____________TIME+_:
user applied a 'c' | 997 952 kdeinit: konsol 18:00.70:
command (when it | 1115 952 kdeinit: konsol 2:16.47:
was current) - now | 1803 1116 led tiptop.HELP 1:55.30:
shows cmd lines vs. | 923 922 X :0 1:09.60:
program names; | 973 1 klaptopdaemon 0:59.63:
still seems to be | 981 952 /usr/bin/artsd 0:48.63:
sorted on TIME+ | 987 1 kdeinit: kdeskt 0:24.34:
though |___991_____1_kdeinit:_kicker___0:04.59:
|3__PID_%MEM__VIRT_SWAP__RES_CODE_DATA_:
This #3 guy appears | 4634 12.3 15620 0 15m 860 14m :
to still be running | 7337 11.3 14396 92 13m 36 13m :
with the supplied | 923 10.6 30544 16m 13m 1120 12m :
defaults, but no | 991 7.2 9492 316 9176 12 9164 :
telling what damage | 7329 7.0 9036 140 8896 36 8860 :
might have been | 1115 6.9 8956 160 8796 36 8760 :
done to it's | 987 6.4 8668 524 8144 20 8124 :
summary info stuff | 1131 6.4 8268 144 8124 36 8088 :
+--------------------------------------+
And that's what brought us to this current state. No, wait. Oh
lordy, will you look at that -- someone has changed the name of win-
dow #2 from 'Job' to 'Top'!
How'd they do that? Well, they just issued the 'g' interactive com-
mand, of course. That command is available whenever alternate-display
mode is active and always impacts just the 'current' window. Gosh,
you can even issue the 'g' command when 'l' has toggled Off the very
summary area line containing the window name!
Almost Done...
-*- ALL TOGETHER Now, Window(s) -*-
Here, the window 1:Def task display has been toggled Off but it
remains the 'current' window. Since there is no task area, many com-
mands will be restricted. However, the commands ('l', 't', 'm', '1')
affecting the summary area, as well as some other global commands
('k', 'Z', etc.), would still be active.
Notice that the Mem and Swap lines are not shown. This means that the
loser (oops, user) has, in fact, issued the 'm' command! Now, if you
were to cycle the 'current' window with the 'a' or 'w' commands, the
task display would remain the same (except possibly growing/shrinking
slightly) but the summary area would change periodically.
The comments to the left of the image provide additional insights into
how things came to be. Note especially the comments for window 4:Usr
-- the one with some empty rows...
1:Def no highlight, +--------------------------------------+
thus disabled cmds: |1:Def - 15:50:32 up 16:29, 9 users, :
b,i,n,u,x,y, etc. |Tasks: 75 total, 2 running, 73 sle:
& m = lost Mem/Swap |Cpu(s): 10.6% user, 0.0% system, :
|______________________________________:
2:Job was very busy: |2__PID__PPID_Command____________TIME+_:
'n' cmd, w/ 7 tasks | 80 1 ( khubd ) 0:00.00:
'c' cmd, cmd line | 6 0 ( kreclaimd ) 0:00.00:
'O' cmd, sort cmd | 9 1 ( mdrecoveryd ) 0:00.00:
'R' cmd, sort bkwd | 11358 1 /bin/bash/ /usr 0:00.00:
'x' cmd, hi column | 1297 1 /sbin/mingetty 0:00.00:
(when 2 WAS current) | 683 1 xinetd -stayali 0:00.00:
|___836_____1_login_--_root_____0:00.00:
3:Mem has altered |3__PID_%MEM__VIRT_SWAP__RES_CODE_DATA_:
some std defaults: | 4634 12.3 15620 0 15m 860 14m :
'y' turned Off | 7337 11.3 14396 92 13m 36 13m :
'x' turned On | 923 10.6 30544 16m 13m 1120 12m :
(when 3 WAS current) | 991 7.2 9492 316 9176 12 9164 :
|__7329__7.0__9036__140_8896___36_8860_:
Huh? 4:Usr has some |4_UID_USER_____GROUP____TTY________PID:
blank rows! ? ? ? ? | 0 jtwm root pts/2 5561:
Aha, the 'i' command | 0 root root ? 5560:
applied (when 4 WAS | :
current); could be | :
reversed with '=', | :
when 4 IS current! +--------------------------------------+
Ok now, how about that 'current' window 1:Def and its unseen tasks?
At any time, you can quickly retrieve lost tasks in a number of ways:
1) Press '-', toggling just the 'current' window
2) Press '_', toggling all visible/invisible windows
( 1:Def is the only window currently not shown )
( afterward, it'll be the only window showing! )
* 3) Press '+', forcing all task displays to become visible
4) Press 'A' to return to full-screen mode,
with only 1:Def tasks shown and without a window name
Now that should be enough ways of getting a task area visible again to
satisfy almost any user, don't ya think?
Note: Use #3 above when you've messed up your screen beyond
redemption. The four task displays will reappear, nice and even.
They will also have retained any customizations you had previously
applied, except for the 'i' (idle tasks) and 'n' (max tasks) com-
mands.
That's It ! Piece of Cake !! Enjoy them there windows !!!

1381
top.1
View File

File diff suppressed because it is too large Load Diff

4829
top.c
View File

File diff suppressed because it is too large Load Diff

872
top.h
View File

File diff suppressed because it is too large Load Diff