TOP(1)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 User Commands\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TOP(1)<\/p>\n
NAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
top – display Linux processes<\/p>\n
SYNOPSIS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
top -hv|-bcHiOSs -d secs -n max -u|U user -p pid -o fld -w [cols]<\/p>\n
The traditional switches `-‘ and whitespace are optional.<\/p>\n
DESCRIPTION\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
The top program provides a dynamic real-time view of a running
\nsystem.\u00a0 It can display system summary information as well as a list
\nof processes or threads currently being managed by the Linux kernel.
\nThe types of system summary information shown and the types, order
\nand size of information displayed for processes are all user
\nconfigurable and that configuration can be made persistent across
\nrestarts.<\/p>\n
The program provides a limited interactive interface for process
\nmanipulation as well as a much more extensive interface for personal
\nconfiguration\u00a0 —\u00a0 encompassing every aspect of its operation.\u00a0 And
\nwhile top is referred to throughout this document, you are free to
\nname the program anything you wish.\u00a0 That new name, possibly an
\nalias, will then be reflected on top’s display and used when reading
\nand writing a configuration file.<\/p>\n
OVERVIEW\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
Documentation
\nThe remaining Table of Contents<\/p>\n
1. COMMAND-LINE Options
\n2. SUMMARY Display
\na. UPTIME and LOAD Averages
\nb. TASK and CPU States
\nc. MEMORY Usage
\n3. FIELDS \/ Columns Display
\na. DESCRIPTIONS of Fields
\nb. MANAGING Fields
\n4. INTERACTIVE Commands
\na. GLOBAL Commands
\nb. SUMMARY AREA Commands
\nc. TASK AREA Commands
\n1. Appearance
\n2. Content
\n3. Size
\n4. Sorting
\nd. COLOR Mapping
\n5. ALTERNATE-DISPLAY Provisions
\na. WINDOWS Overview
\nb. COMMANDS for Windows
\nc. SCROLLING a Window
\nd. SEARCHING in a Window
\ne. FILTERING in a Window
\n6. FILES
\na. SYSTEM Configuration File
\nb. PERSONAL Configuration File
\nc. ADDING INSPECT Entries
\n7. STUPID TRICKS Sampler
\na. Kernel Magic
\nb. Bouncing Windows
\nc. The Big Bird Window
\nd. The Ol’ Switcheroo
\n8. BUGS, 9. HISTORY Former top, 10. AUTHOR, 11. SEE Also<\/p>\n
Operation
\nWhen operating top, the two most important keys are the help (h or ?)
\nkey and quit (‘q’) key.\u00a0 Alternatively, you could simply use the
\ntraditional interrupt key (^C) when you’re done.<\/p>\n
When started for the first time, you’ll be presented with these
\ntraditional elements on the main top screen: 1) Summary Area; 2)
\nFields\/Columns Header; 3) Task Area.\u00a0 Each of these will be explored
\nin the sections that follow.\u00a0 There is also an Input\/Message line
\nbetween the Summary Area and Columns Header which needs no further
\nexplanation.<\/p>\n
The main top screen is generally quite adaptive to changes in
\nterminal dimensions under X-Windows.\u00a0 Other top screens may be less
\nso, especially those with static text.\u00a0 It ultimately depends,
\nhowever, on your particular window manager and terminal emulator.
\nThere may be occasions when their view of terminal size and current
\ncontents differs from top’s view, which is always based on operating
\nsystem calls.<\/p>\n
Following any re-size operation, if a top screen is corrupted,
\nappears incomplete or disordered, simply typing something innocuous
\nlike a punctuation character or cursor motion key will usually
\nrestore it.\u00a0 In extreme cases, the following sequence almost
\ncertainly will:
\nkey\/cmd\u00a0 objective
\n^Z\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 suspend top
\nfg\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 resume top
\n<Left>\u00a0\u00a0 force a screen redraw (if necessary)<\/p>\n
But if the display is still corrupted, there is one more step you
\ncould try.\u00a0 Insert this command after top has been suspended but
\nbefore resuming it.
\nkey\/cmd\u00a0 objective
\nreset\u00a0\u00a0\u00a0 restore your terminal settings<\/p>\n
Note: the width of top’s display will be limited to 512 positions.
\nDisplaying all fields requires approximately 250 characters.
\nRemaining screen width is usually allocated to any variable width
\ncolumns currently visible.\u00a0 The variable width columns, such as
\nCOMMAND, are noted in topic 3a. DESCRIPTIONS of Fields.\u00a0 Actual
\noutput width may also be influenced by the -w switch, which is
\ndiscussed in topic 1. COMMAND-LINE Options.<\/p>\n
Lastly, some of top’s screens or functions require the use of cursor
\nmotion keys like the standard arrow keys plus the Home, End, PgUp and
\nPgDn keys.\u00a0 If your terminal or emulator does not provide those keys,
\nthe following combinations are accepted as alternatives:
\nkey\u00a0\u00a0\u00a0\u00a0\u00a0 equivalent-key-combinations
\nUp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 alt + \\\u00a0\u00a0\u00a0\u00a0\u00a0 or\u00a0 alt + k
\nDown\u00a0\u00a0\u00a0\u00a0 alt + \/\u00a0\u00a0\u00a0\u00a0\u00a0 or\u00a0 alt + j
\nLeft\u00a0\u00a0\u00a0\u00a0 alt + <\u00a0\u00a0\u00a0\u00a0\u00a0 or\u00a0 alt + h
\nRight\u00a0\u00a0\u00a0 alt + >\u00a0\u00a0\u00a0\u00a0\u00a0 or\u00a0 alt + l (lower case L)
\nPgUp\u00a0\u00a0\u00a0\u00a0 alt + Up\u00a0\u00a0\u00a0\u00a0 or\u00a0 alt + ctrl + k
\nPgDn\u00a0\u00a0\u00a0\u00a0 alt + Down\u00a0\u00a0 or\u00a0 alt + ctrl + j
\nHome\u00a0\u00a0\u00a0\u00a0 alt + Left\u00a0\u00a0 or\u00a0 alt + ctrl + h
\nEnd\u00a0\u00a0\u00a0\u00a0\u00a0 alt + Right\u00a0 or\u00a0 alt + ctrl + l<\/p>\n
The Up and Down arrow keys have special significance when prompted
\nfor line input terminated with the <Enter> key.\u00a0 Those keys, or their
\naliases, can be used to retrieve previous input lines which can then
\nbe edited and re-input.\u00a0 And there are four additional keys available
\nwith line oriented input.
\nkey\u00a0\u00a0\u00a0\u00a0\u00a0 special-significance
\nUp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 recall older strings for re-editing
\nDown\u00a0\u00a0\u00a0\u00a0 recall newer strings or erase entire line
\nInsert\u00a0\u00a0 toggle between insert and overtype modes
\nDelete\u00a0\u00a0 character removed at cursor, moving others left
\nHome\u00a0\u00a0\u00a0\u00a0 jump to beginning of input line
\nEnd\u00a0\u00a0\u00a0\u00a0\u00a0 jump to end of input line<\/p>\n
Startup Defaults
\nThe following startup defaults assume no configuration file, thus no
\nuser customizations.\u00a0 Even so, items shown with an asterisk (`*’)
\ncould be overridden through the command-line.\u00a0 All are explained in
\ndetail in the sections that follow.<\/p>\n
Global-defaults
\nA – Alt display\u00a0\u00a0\u00a0\u00a0\u00a0 Off (full-screen)
\n* d – Delay time\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1.5 seconds
\n* H – Threads mode\u00a0\u00a0\u00a0\u00a0 Off (summarize as tasks)
\nI – Irix mode\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 On\u00a0 (no, `solaris’ smp)
\n* p – PID monitoring\u00a0\u00a0 Off (show all processes)
\n* s – Secure mode\u00a0\u00a0\u00a0\u00a0\u00a0 Off (unsecured)
\nB – Bold enable\u00a0\u00a0\u00a0\u00a0\u00a0 On\u00a0 (yes, bold globally)
\nSummary-Area-defaults
\nl – Load Avg\/Uptime\u00a0 On\u00a0 (thus program name)
\nt – Task\/Cpu states\u00a0 On\u00a0 (1+1 lines, see `1′)
\nm – Mem\/Swap usage\u00a0\u00a0 On\u00a0 (2 lines worth)
\n1 – Single Cpu\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Off (thus multiple cpus)
\nTask-Area-defaults
\nb – Bold hilite\u00a0\u00a0\u00a0\u00a0\u00a0 Off (use `reverse’)
\n* c – Command line\u00a0\u00a0\u00a0\u00a0 Off (name, not cmdline)
\n* i – Idle tasks\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 On\u00a0 (show all tasks)
\nJ – Num align right\u00a0 On\u00a0 (not left justify)
\nj – Str align right\u00a0 Off (not right justify)
\nR – Reverse sort\u00a0\u00a0\u00a0\u00a0 On\u00a0 (pids high-to-low)
\n* S – Cumulative time\u00a0 Off (no, dead children)
\n* u – User filter\u00a0\u00a0\u00a0\u00a0\u00a0 Off (show euid only)
\n* U – User filter\u00a0\u00a0\u00a0\u00a0\u00a0 Off (show any uid)
\nV – Forest view\u00a0\u00a0\u00a0\u00a0\u00a0 On\u00a0 (show as branches)
\nx – Column hilite\u00a0\u00a0\u00a0 Off (no, sort field)
\ny – Row hilite\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 On\u00a0 (yes, running tasks)
\nz – color\/mono\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 On\u00a0 (show colors)<\/p>\n
1. COMMAND-LINE Options\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
The command-line syntax for top consists of:<\/p>\n
-hv|-bcHiOSs -d secs -n max -u|U user -p pid -o fld -w [cols]<\/p>\n
The typically mandatory switch (‘-‘) and even whitespace are
\ncompletely optional.<\/p>\n
-h | -v\u00a0 :Help\/Version
\nShow library version and the usage prompt, then quit.<\/p>\n
-b\u00a0 :Batch-mode operation
\nStarts top in Batch mode, which could be useful for sending
\noutput from top to other programs or to a file.\u00a0 In this mode,
\ntop will not accept input and runs until the iterations limit
\nyou’ve set with the `-n’ command-line option or until killed.<\/p>\n
-c\u00a0 :Command-line\/Program-name toggle
\nStarts top with the last remembered `c’ state reversed.\u00a0 Thus,
\nif top was displaying command lines, now that field will show
\nprogram names, and visa versa.\u00a0 See the `c’ interactive command
\nfor additional information.<\/p>\n
-d\u00a0 :Delay-time interval as:\u00a0 -d ss.t (secs.tenths)
\nSpecifies the delay between screen updates, and overrides the
\ncorresponding value in one’s personal configuration file or the
\nstartup default.\u00a0 Later this can be changed with the `d’ or `s’
\ninteractive commands.<\/p>\n
Fractional seconds are honored, but a negative number is not
\nallowed.\u00a0 In all cases, however, such changes are prohibited if
\ntop is running in Secure mode, except for root (unless the `s’
\ncommand-line option was used).\u00a0 For additional information on
\nSecure mode see topic 6a. SYSTEM Configuration File.<\/p>\n
-H\u00a0 :Threads-mode operation
\nInstructs top to display individual threads.\u00a0 Without this
\ncommand-line option a summation of all threads in each process
\nis shown.\u00a0 Later this can be changed with the `H’ interactive
\ncommand.<\/p>\n
-i\u00a0 :Idle-process toggle
\nStarts top with the last remembered `i’ state reversed.\u00a0 When
\nthis toggle is Off, tasks that have not used any CPU since the
\nlast update will not be displayed.\u00a0 For additional information
\nregarding this toggle see topic 4c. TASK AREA Commands, SIZE.<\/p>\n
-n\u00a0 :Number-of-iterations limit as:\u00a0 -n number
\nSpecifies the maximum number of iterations, or frames, top
\nshould produce before ending.<\/p>\n
-o\u00a0 :Override-sort-field as:\u00a0 -o fieldname
\nSpecifies the name of the field on which tasks will be sorted,
\nindependent of what is reflected in the configuration file.\u00a0 You
\ncan prepend a `+’ or `-‘ to the field name to also override the
\nsort direction.\u00a0 A leading `+’ will force sorting high to low,
\nwhereas a `-‘ will ensure a low to high ordering.<\/p>\n
This option exists primarily to support automated\/scripted batch
\nmode operation.<\/p>\n
-O\u00a0 :Output-field-names
\nThis option acts as a form of help for the above -o option.\u00a0 It
\nwill cause top to print each of the available field names on a
\nseparate line, then quit.\u00a0 Such names are subject to nls
\ntranslation.<\/p>\n
-p\u00a0 :Monitor-PIDs mode as:\u00a0 -pN1 -pN2 …\u00a0 or\u00a0 -pN1,N2,N3 …
\nMonitor only processes with specified process IDs.\u00a0 This option
\ncan be given up to 20 times, or you can provide a comma
\ndelimited list with up to 20 pids.\u00a0 Co-mingling both approaches
\nis permitted.<\/p>\n
A pid value of zero will be treated as the process id of the top
\nprogram itself once it is running.<\/p>\n
This is a command-line option only and should you wish to return
\nto normal operation, it is not necessary to quit and restart top
\n—\u00a0 just issue any of these interactive commands: `=’, `u’ or
\n`U’.<\/p>\n
The `p’, `u’ and `U’ command-line options are mutually
\nexclusive.<\/p>\n
-s\u00a0 :Secure-mode operation
\nStarts top with secure mode forced, even for root.\u00a0 This mode is
\nfar better controlled through the system configuration file (see
\ntopic 6. FILES).<\/p>\n
-S\u00a0 :Cumulative-time toggle
\nStarts top with the last remembered `S’ state reversed.\u00a0 When
\nCumulative time mode is On, each process is listed with the cpu
\ntime that it and its dead children have used.\u00a0 See the `S’
\ninteractive command for additional information regarding this
\nmode.<\/p>\n
-u | -U\u00a0 :User-filter-mode as:\u00a0 -u | -U number or name
\nDisplay only processes with a user id or user name matching that
\ngiven.\u00a0 The `-u’ option matches on\u00a0 effective user whereas the
\n`-U’ option matches on any user (real, effective, saved, or
\nfilesystem).<\/p>\n
Prepending an exclamation point (‘!’) to the user id or name
\ninstructs top to display only processes with users not matching
\nthe one provided.<\/p>\n
The `p’, `u’ and `U’ command-line options are mutually
\nexclusive.<\/p>\n
-w\u00a0 :Output-width-override as:\u00a0 -w [ number ]
\nIn Batch mode, when used without an argument top will format
\noutput using the COLUMNS= and LINES= environment variables, if
\nset.\u00a0 Otherwise, width will be fixed at the maximum 512 columns.
\nWith an argument, output width can be decreased or increased (up
\nto 512) but the number of rows is considered unlimited.<\/p>\n
In normal display mode, when used without an argument top will
\nattempt to format output using the COLUMNS= and LINES=
\nenvironment variables, if set.\u00a0 With an argument, output width
\ncan only be decreased, not increased.\u00a0 Whether using environment
\nvariables or an argument with -w, when not in Batch mode actual
\nterminal dimensions can never be exceeded.<\/p>\n
Note: Without the use of this command-line option, output width
\nis always based on the terminal at which top was invoked whether
\nor not in Batch mode.<\/p>\n
2. SUMMARY Display\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
Each of the following three areas are individually controlled through
\none or more interactive commands.\u00a0 See topic 4b. SUMMARY AREA
\nCommands for additional information regarding these provisions.<\/p>\n
2a. UPTIME and LOAD Averages
\nThis portion consists of a single line containing:
\nprogram or window name, depending on display mode
\ncurrent time and length of time since last boot
\ntotal number of users
\nsystem load avg over the last 1, 5 and 15 minutes<\/p>\n
2b. TASK and CPU States
\nThis portion consists of a minimum of two lines.\u00a0 In an SMP
\nenvironment, additional lines can reflect individual CPU state
\npercentages.<\/p>\n
Line 1 shows total tasks or threads, depending on the state of the
\nThreads-mode toggle.\u00a0 That total is further classified as:
\nrunning; sleeping; stopped; zombie<\/p>\n
Line 2 shows CPU state percentages based on the interval since the
\nlast refresh.<\/p>\n
As a default, percentages for these individual categories are
\ndisplayed.\u00a0 Where two labels are shown below, those for more recent
\nkernel versions are shown first.
\nus, user\u00a0\u00a0\u00a0 : time running un-niced user processes
\nsy, system\u00a0 : time running kernel processes
\nni, nice\u00a0\u00a0\u00a0 : time running niced user processes
\nid, idle\u00a0\u00a0\u00a0 : time spent in the kernel idle handler
\nwa, IO-wait : time waiting for I\/O completion
\nhi : time spent servicing hardware interrupts
\nsi : time spent servicing software interrupts
\nst : time stolen from this vm by the hypervisor<\/p>\n
In the alternate cpu states display modes, beyond the first
\ntasks\/threads line, an abbreviated summary is shown consisting of
\nthese elements:
\na\u00a0\u00a0\u00a0 b\u00a0\u00a0\u00a0\u00a0 c\u00a0\u00a0\u00a0 d
\n%Cpu(s):\u00a0 75.0\/25.0\u00a0 100[ …<\/p>\n
Where: a) is the combined us and ni percentage; b) is the sy
\npercentage; c) is the total; and d) is one of two visual graphs of
\nthose representations.\u00a0 See topic 4b. SUMMARY AREA Commands and the
\n`t’ command for additional information on that special 4-way toggle.<\/p>\n
2c. MEMORY Usage
\nThis portion consists of two lines which may express values in
\nkibibytes (KiB) through exbibytes (EiB) depending on the scaling
\nfactor enforced with the `E’ interactive command.<\/p>\n
As a default, Line 1 reflects physical memory, classified as:
\ntotal, free, used and buff\/cache<\/p>\n
Line 2 reflects mostly virtual memory, classified as:
\ntotal, free, used and avail (which is physical memory)<\/p>\n
The avail number on line 2 is an estimation of physical memory
\navailable for starting new applications, without swapping.\u00a0 Unlike
\nthe free field, it attempts to account for readily reclaimable page
\ncache and memory slabs.\u00a0 It is available on kernels 3.14, emulated on
\nkernels 2.6.27+, otherwise the same as free.<\/p>\n
In the alternate memory display modes, two abbreviated summary lines
\nare shown consisting of these elements:
\na\u00a0\u00a0\u00a0 b\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 c
\nGiB Mem : 18.7\/15.738\u00a0\u00a0 [ …
\nGiB Swap:\u00a0 0.0\/7.999\u00a0\u00a0\u00a0 [ …<\/p>\n
Where: a) is the percentage used; b) is the total available; and c)
\nis one of two visual graphs of those representations.<\/p>\n
In the case of physical memory, the percentage represents the total
\nminus the estimated avail noted above.\u00a0 The `Mem’ graph itself is
\ndivided between used and any remaining memory not otherwise accounted
\nfor by avail.\u00a0 See topic 4b. SUMMARY AREA Commands and the `m’
\ncommand for additional information on that special 4-way toggle.<\/p>\n
This table may help in interpreting the scaled values displayed:
\nKiB = kibibyte = 1024 bytes
\nMiB = mebibyte = 1024 KiB = 1,048,576 bytes
\nGiB = gibibyte = 1024 MiB = 1,073,741,824 bytes
\nTiB = tebibyte = 1024 GiB = 1,099,511,627,776 bytes
\nPiB = pebibyte = 1024 TiB = 1,125,899,906,842,624 bytes
\nEiB = exbibyte = 1024 PiB = 1,152,921,504,606,846,976 bytes<\/p>\n
3. FIELDS \/ Columns\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
3a. DESCRIPTIONS of Fields
\nListed below are top’s available process fields (columns).\u00a0 They are
\nshown in strict ascii alphabetical order.\u00a0 You may customize their
\nposition and whether or not they are displayable with the `f’ or `F’
\n(Fields Management) interactive commands.<\/p>\n
Any field is selectable as the sort field, and you control whether
\nthey are sorted high-to-low or low-to-high.\u00a0 For additional
\ninformation on sort provisions see topic 4c. TASK AREA Commands,
\nSORTING.<\/p>\n
The fields related to physical memory or virtual memory reference
\n`(KiB)’ which is the unsuffixed display mode.\u00a0 Such fields may,
\nhowever, be scaled from KiB through PiB.\u00a0 That scaling is influenced
\nvia the `e’ interactive command or established for startup through a
\nbuild option.<\/p>\n
1. %CPU\u00a0 —\u00a0 CPU Usage
\nThe task’s share of the elapsed CPU time since the last screen
\nupdate, expressed as a percentage of total CPU time.<\/p>\n
In a true SMP environment, if a process is multi-threaded and top
\nis not operating in Threads mode, amounts greater than 100% may
\nbe reported.\u00a0 You toggle Threads mode with the `H’ interactive
\ncommand.<\/p>\n
Also for multi-processor environments, if Irix mode is Off, top
\nwill operate in Solaris mode where a task’s cpu usage will be
\ndivided by the total number of CPUs.\u00a0 You toggle Irix\/Solaris
\nmodes with the `I’ interactive command.<\/p>\n
2. %MEM\u00a0 —\u00a0 Memory Usage (RES)
\nA task’s currently used share of available physical memory.<\/p>\n
3. CGROUPS\u00a0 —\u00a0 Control Groups
\nThe names of the control group(s) to which a process belongs, or
\n`-‘ if not applicable for that process.<\/p>\n
Control Groups provide for allocating resources (cpu, memory,
\nnetwork bandwidth, etc.) among installation-defined groups of
\nprocesses.\u00a0 They enable fine-grained control over allocating,
\ndenying, prioritizing, managing and monitoring those resources.<\/p>\n
Many different hierarchies of cgroups can exist simultaneously on
\na system and each hierarchy is attached to one or more
\nsubsystems.\u00a0 A subsystem represents a single resource.<\/p>\n
Note: The CGROUPS field, unlike most columns, is not fixed-width.
\nWhen displayed, it plus any other variable width columns will be
\nallocated all remaining screen width (up to the maximum 512
\ncharacters).\u00a0 Even so, such variable width fields could still
\nsuffer truncation.\u00a0 See topic 5c. SCROLLING a Window for
\nadditional information on accessing any truncated data.<\/p>\n
4. CODE\u00a0 —\u00a0 Code Size (KiB)
\nThe amount of physical memory devoted to executable code, also
\nknown as the Text Resident Set size or TRS.<\/p>\n
5. COMMAND\u00a0 —\u00a0 Command Name or Command Line
\nDisplay the command line used to start a task or the name of the
\nassociated program.\u00a0 You toggle between command line and name
\nwith `c’, which is both a command-line option and an interactive
\ncommand.<\/p>\n
When you’ve chosen to display command lines, processes without a
\ncommand line (like kernel threads) will be shown with only the
\nprogram name in brackets, as in this example:
\n[kthreadd]<\/p>\n
This field may also be impacted by the forest view display mode.
\nSee the `V’ interactive command for additional information
\nregarding that mode.<\/p>\n
Note: The COMMAND field, unlike most columns, is not fixed-width.
\nWhen displayed, it plus any other variable width columns will be
\nallocated all remaining screen width (up to the maximum 512
\ncharacters).\u00a0 Even so, such variable width fields could still
\nsuffer truncation.\u00a0 This is especially true for this field when
\ncommand lines are being displayed (the `c’ interactive command.)
\nSee topic 5c. SCROLLING a Window for additional information on
\naccessing any truncated data.<\/p>\n
6. DATA\u00a0 —\u00a0 Data + Stack Size (KiB)
\nThe amount of physical memory devoted to other than executable
\ncode, also known as the Data Resident Set size or DRS.<\/p>\n
7. ENVIRON\u00a0 —\u00a0 Environment variables
\nDisplay all of the environment variables, if any, as seen by the
\nrespective processes.\u00a0 These variables will be displayed in their
\nraw native order, not the sorted order you are accustomed to
\nseeing with an unqualified `set’.<\/p>\n
Note: The ENVIRON field, unlike most columns, is not fixed-width.
\nWhen displayed, it plus any other variable width columns will be
\nallocated all remaining screen width (up to the maximum 512
\ncharacters).\u00a0 Even so, such variable width fields could still
\nsuffer truncation.\u00a0 This is especially true for this field.\u00a0 See
\ntopic 5c. SCROLLING a Window for additional information on
\naccessing any truncated data.<\/p>\n
8. Flags\u00a0 —\u00a0 Task Flags
\nThis column represents the task’s current scheduling flags which
\nare expressed in hexadecimal notation and with zeros suppressed.
\nThese flags are officially documented in <linux\/sched.h>.<\/p>\n
9. GID\u00a0 —\u00a0 Group Id
\nThe effective group ID.<\/p>\n
10. GROUP\u00a0 —\u00a0 Group Name
\nThe effective group name.<\/p>\n
11. NI\u00a0 —\u00a0 Nice Value
\nThe nice value of the task.\u00a0 A negative nice value means higher
\npriority, whereas a positive nice value means lower priority.
\nZero in this field simply means priority will not be adjusted in
\ndetermining a task’s dispatch-ability.<\/p>\n
12. P\u00a0 —\u00a0 Last used CPU (SMP)
\nA number representing the last used processor.\u00a0 In a true SMP
\nenvironment this will likely change frequently since the kernel
\nintentionally uses weak affinity.\u00a0 Also, the very act of running
\ntop may break this weak affinity and cause more processes to
\nchange CPUs more often (because of the extra demand for cpu
\ntime).<\/p>\n
13. PGRP\u00a0 —\u00a0 Process Group Id
\nEvery process is member of a unique process group which is used
\nfor distribution of signals and by terminals to arbitrate
\nrequests for their input and output.\u00a0 When a process is created
\n(forked), it becomes a member of the process group of its parent.
\nBy convention, this value equals the process ID (see PID) of the
\nfirst member of a process group, called the process group leader.<\/p>\n
14. PID\u00a0 —\u00a0 Process Id
\nThe task’s unique process ID, which periodically wraps, though
\nnever restarting at zero.\u00a0 In kernel terms, it is a dispatchable
\nentity defined by a task_struct.<\/p>\n
This value may also be used as: a process group ID (see PGRP); a
\nsession ID for the session leader (see SID); a thread group ID
\nfor the thread group leader (see TGID); and a TTY process group
\nID for the process group leader (see TPGID).<\/p>\n
15. PPID\u00a0 —\u00a0 Parent Process Id
\nThe process ID (pid) of a task’s parent.<\/p>\n
16. PR\u00a0 —\u00a0 Priority
\nThe scheduling priority of the task.\u00a0 If you see `rt’ in this
\nfield, it means the task is running under real time scheduling
\npriority.<\/p>\n
Under linux, real time priority is somewhat misleading since
\ntraditionally the operating itself was not preemptible.\u00a0 And
\nwhile the 2.6 kernel can be made mostly preemptible, it is not
\nalways so.<\/p>\n
17. RES\u00a0 —\u00a0 Resident Memory Size (KiB)
\nThe non-swapped physical memory a task is using.<\/p>\n
18. RUID\u00a0 —\u00a0 Real User Id
\nThe real user ID.<\/p>\n
19. RUSER\u00a0 —\u00a0 Real User Name
\nThe real user name.<\/p>\n
20. S\u00a0 —\u00a0 Process Status
\nThe status of the task which can be one of:
\nD = uninterruptible sleep
\nR = running
\nS = sleeping
\nT = stopped by job control signal
\nt = stopped by debugger during trace
\nZ = zombie<\/p>\n
Tasks shown as running should be more properly thought of as
\nready to run\u00a0 —\u00a0 their task_struct is simply represented on the
\nLinux run-queue.\u00a0 Even without a true SMP machine, you may see
\nnumerous tasks in this state depending on top’s delay interval
\nand nice value.<\/p>\n
21. SHR\u00a0 —\u00a0 Shared Memory Size (KiB)
\nThe amount of shared memory available to a task, not all of which
\nis typically resident.\u00a0 It simply reflects memory that could be
\npotentially shared with other processes.<\/p>\n
22. SID\u00a0 —\u00a0 Session Id
\nA session is a collection of process groups (see PGRP), usually
\nestablished by the login shell.\u00a0 A newly forked process joins the
\nsession of its creator.\u00a0 By convention, this value equals the
\nprocess ID (see PID) of the first member of the session, called
\nthe session leader, which is usually the login shell.<\/p>\n
23. SUID\u00a0 —\u00a0 Saved User Id
\nThe saved user ID.<\/p>\n
24. SUPGIDS\u00a0 —\u00a0 Supplementary Group IDs
\nThe IDs of any supplementary group(s) established at login or
\ninherited from a task’s parent.\u00a0 They are displayed in a comma
\ndelimited list.<\/p>\n
Note: The SUPGIDS field, unlike most columns, is not fixed-width.
\nWhen displayed, it plus any other variable width columns will be
\nallocated all remaining screen width (up to the maximum 512
\ncharacters).\u00a0 Even so, such variable width fields could still
\nsuffer truncation.\u00a0 See topic 5c. SCROLLING a Window for
\nadditional information on accessing any truncated data.<\/p>\n
25. SUPGRPS\u00a0 —\u00a0 Supplementary Group Names
\nThe names of any supplementary group(s) established at login or
\ninherited from a task’s parent.\u00a0 They are displayed in a comma
\ndelimited list.<\/p>\n
Note: The SUPGRPS field, unlike most columns, is not fixed-width.
\nWhen displayed, it plus any other variable width columns will be
\nallocated all remaining screen width (up to the maximum 512
\ncharacters).\u00a0 Even so, such variable width fields could still
\nsuffer truncation.\u00a0 See topic 5c. SCROLLING a Window for
\nadditional information on accessing any truncated data.<\/p>\n
26. SUSER\u00a0 —\u00a0 Saved User Name
\nThe saved user name.<\/p>\n
27. SWAP\u00a0 —\u00a0 Swapped Size (KiB)
\nThe non-resident portion of a task’s address space.<\/p>\n
28. TGID\u00a0 —\u00a0 Thread Group Id
\nThe ID of the thread group to which a task belongs.\u00a0 It is the
\nPID of the thread group leader.\u00a0 In kernel terms, it represents
\nthose tasks that share an mm_struct.<\/p>\n
29. TIME\u00a0 —\u00a0 CPU Time
\nTotal CPU time the task has used since it started.\u00a0 When
\nCumulative mode is On, each process is listed with the cpu time
\nthat it and its dead children have used.\u00a0 You toggle Cumulative
\nmode with `S’, which is both a command-line option and an
\ninteractive command.\u00a0 See the `S’ interactive command for
\nadditional information regarding this mode.<\/p>\n
30. TIME+\u00a0 —\u00a0 CPU Time, hundredths
\nThe same as TIME, but reflecting more granularity through
\nhundredths of a second.<\/p>\n
31. TPGID\u00a0 —\u00a0 Tty Process Group Id
\nThe process group ID of the foreground process for the connected
\ntty, or -1 if a process is not connected to a terminal.\u00a0 By
\nconvention, this value equals the process ID (see PID) of the
\nprocess group leader (see PGRP).<\/p>\n
32. TTY\u00a0 —\u00a0 Controlling Tty
\nThe name of the controlling terminal.\u00a0 This is usually the device
\n(serial port, pty, etc.) from which the process was started, and
\nwhich it uses for input or output.\u00a0 However, a task need not be
\nassociated with a terminal, in which case you’ll see `?’
\ndisplayed.<\/p>\n
33. UID\u00a0 —\u00a0 User Id
\nThe effective user ID of the task’s owner.<\/p>\n
34. USED\u00a0 —\u00a0 Memory in Use (KiB)
\nThis field represents the non-swapped physical memory a task has
\nused (RES) plus the non-resident portion of its address space
\n(SWAP).<\/p>\n
35. USER\u00a0 —\u00a0 User Name
\nThe effective user name of the task’s owner.<\/p>\n
36. VIRT\u00a0 —\u00a0 Virtual Memory Size (KiB)
\nThe total amount of virtual memory used by the task.\u00a0 It includes
\nall code, data and shared libraries plus pages that have been
\nswapped out and pages that have been mapped but not used.<\/p>\n
37. WCHAN\u00a0 —\u00a0 Sleeping in Function
\nDepending on the availability of the kernel link map
\n(System.map), this field will show the name or the address of the
\nkernel function in which the task is currently sleeping.\u00a0 Running
\ntasks will display a dash (‘-‘) in this column.<\/p>\n
By displaying this field, top’s own working set could be
\nincreased by over 700Kb, depending on the kernel version.\u00a0 Should
\nthat occur, your only means of reducing that overhead will be to
\nstop and restart top.<\/p>\n
38. nDRT\u00a0 —\u00a0 Dirty Pages Count
\nThe number of pages that have been modified since they were last
\nwritten to auxiliary storage.\u00a0 Dirty pages must be written to
\nauxiliary storage before the corresponding physical memory
\nlocation can be used for some other virtual page.<\/p>\n
39. nMaj\u00a0 —\u00a0 Major Page Fault Count
\nThe number of major page faults that have occurred for a task.\u00a0 A
\npage fault occurs when a process attempts to read from or write
\nto a virtual page that is not currently present in its address
\nspace.\u00a0 A major page fault is when auxiliary storage access is
\ninvolved in making that page available.<\/p>\n
40. nMin\u00a0 —\u00a0 Minor Page Fault count
\nThe number of minor page faults that have occurred for a task.\u00a0 A
\npage fault occurs when a process attempts to read from or write
\nto a virtual page that is not currently present in its address
\nspace.\u00a0 A minor page fault does not involve auxiliary storage
\naccess in making that page available.<\/p>\n
41. nTH\u00a0 —\u00a0 Number of Threads
\nThe number of threads associated with a process.<\/p>\n
42. nsIPC\u00a0 —\u00a0 IPC namespace
\nThe Inode of the namespace used to isolate interprocess
\ncommunication (IPC) resources such as System V IPC objects and
\nPOSIX message queues.<\/p>\n
43. nsMNT\u00a0 —\u00a0 MNT namespace
\nThe Inode of the namespace used to isolate filesystem mount
\npoints thus offering different views of the filesystem hierarchy.<\/p>\n
44. nsNET\u00a0 —\u00a0 NET namespace
\nThe Inode of the namespace used to isolate resources such as
\nnetwork devices, IP addresses, IP routing, port numbers, etc.<\/p>\n
45. nsPID\u00a0 —\u00a0 PID namespace
\nThe Inode of the namespace used to isolate process ID numbers
\nmeaning they need not remain unique.\u00a0 Thus, each such namespace
\ncould have its own `init’ (PID #1) to manage various
\ninitialization tasks and reap orphaned child processes.<\/p>\n
46. nsUSER\u00a0 —\u00a0 USER namespace
\nThe Inode of the namespace used to isolate the user and group ID
\nnumbers.\u00a0 Thus, a process could have a normal unprivileged user
\nID outside a user namespace while having a user ID of 0, with
\nfull root privileges, inside that namespace.<\/p>\n
47. nsUTS\u00a0 —\u00a0 UTS namespace
\nThe Inode of the namespace used to isolate hostname and NIS
\ndomain name.\u00a0 UTS simply means “UNIX Time-sharing System”.<\/p>\n
48. vMj\u00a0 —\u00a0 Major Page Fault Count Delta
\nThe number of major page faults that have occurred since the last
\nupdate (see nMaj).<\/p>\n
49. vMn\u00a0 —\u00a0 Minor Page Fault Count Delta
\nThe number of minor page faults that have occurred since the last
\nupdate (see nMin).<\/p>\n
3b. MANAGING Fields
\nAfter pressing the interactive command `f’ or `F’ (Fields Management)
\nyou will be presented with a screen showing: 1) the `current’ window
\nname; 2) the designated sort field; 3) all fields in their current
\norder along with descriptions.\u00a0 Entries marked with an asterisk are
\nthe currently displayed fields, screen width permitting.<\/p>\n
\u00b7\u00a0 As the on screen instructions indicate, you navigate among the
\nfields with the Up and Down arrow keys.\u00a0 The PgUp, PgDn, Home
\nand End keys can also be used to quickly reach the first or
\nlast available field.<\/p>\n
\u00b7\u00a0 The Right arrow key selects a field for repositioning and the
\nLeft arrow key or the <Enter> key commits that field’s
\nplacement.<\/p>\n
\u00b7\u00a0 The `d’ key or the <Space> bar toggles a field’s display
\nstatus, and thus the presence or absence of the asterisk.<\/p>\n
\u00b7\u00a0 The `s’ key designates a field as the sort field.\u00a0 See topic
\n4c. TASK AREA Commands, SORTING for additional information
\nregarding your selection of a sort field.<\/p>\n
\u00b7\u00a0 The `a’ and `w’ keys can be used to cycle through all
\navailable windows and the `q’ or <Esc> keys exit Fields
\nManagement.<\/p>\n
The Fields Management screen can also be used to change the `current’
\nwindow\/field group in either full-screen mode or alternate-display
\nmode.\u00a0 Whatever was targeted when `q’ or <Esc> was pressed will be
\nmade current as you return to the top display.\u00a0 See topic 5.
\nALTERNATE-DISPLAY Provisions and the `g’ interactive command for
\ninsight into `current’ windows and field groups.<\/p>\n
Note: Any window that has been scrolled horizontally will be reset if
\nany field changes are made via the Fields Management screen.\u00a0 Any
\nvertical scrolled position, however, will not be affected.\u00a0 See topic
\n5c. SCROLLING a Window for additional information regarding vertical
\nand horizontal scrolling.<\/p>\n
4. INTERACTIVE Commands\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
Listed below is a brief index of commands within categories.\u00a0 Some
\ncommands appear more than once\u00a0 —\u00a0 their meaning or scope may vary
\ndepending on the context in which they are issued.<\/p>\n
4a. Global-Commands
\n<Ent\/Sp> ?, =, 0,
\nA, B, d, E, e, g, h, H, I, k, q, r, s, W, X, Y, Z
\n4b. Summary-Area-Commands
\nC, l, t, m, 1, 2, 3
\n4c. Task-Area-Commands
\nAppearance:\u00a0 b, J, j, x, y, z
\nContent:\u00a0\u00a0\u00a0\u00a0 c, f, F, o, O, S, u, U, V
\nSize:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #, i, n
\nSorting:\u00a0\u00a0\u00a0\u00a0 <, >, f, F, R
\n4d. Color-Mapping
\n<Ret>, a, B, b, H, M, q, S, T, w, z, 0 – 7
\n5b. Commands-for-Windows
\n-, _, =, +, A, a, g, G, w
\n5c. Scrolling-a-Window
\nC, Up, Dn, Left, Right, PgUp, PgDn, Home, End
\n5d. Searching-in-a-Window
\nL, &<\/p>\n
4a. GLOBAL Commands
\nThe global interactive commands are always available in both
\nfull-screen mode and alternate-display mode.\u00a0 However, some of these
\ninteractive commands are not available when running in Secure mode.<\/p>\n
If you wish to know in advance whether or not your top has been
\nsecured, simply ask for help and view the system summary on the
\nsecond line.<\/p>\n
<Enter> or <Space>\u00a0 :Refresh-Display
\nThese commands awaken top and following receipt of any input
\nthe entire display will be repainted.\u00a0 They also force an
\nupdate of any hotplugged cpu or physical memory changes.<\/p>\n
Use either of these keys if you have a large delay interval
\nand wish to see current status,<\/p>\n
? | h\u00a0 :Help
\nThere are two help levels available.\u00a0 The first will provide a
\nreminder of all the basic interactive commands.\u00a0 If top is
\nsecured, that screen will be abbreviated.<\/p>\n
Typing `h’ or `?’ on that help screen will take you to help
\nfor those interactive commands applicable to alternate-display
\nmode.<\/p>\n
=\u00a0 :Exit-Task-Limits
\nRemoves restrictions on which tasks are shown.\u00a0 This command
\nwill reverse any `i’ (idle tasks) and `n’ (max tasks) commands
\nthat might be active.\u00a0 It also provides for an exit from PID
\nmonitoring, User filtering and Other filtering.\u00a0 See the `-p’
\ncommand-line option for a discussion of PID monitoring, the
\n`U’ or `u’ interactive commands for User filtering and the `O’
\nor `o’ interactive commands for Other filtering.<\/p>\n
Additionally, any window that has been scrolled will be reset
\nwith this command.\u00a0 See topic 5c. SCROLLING a Window for
\nadditional information regarding vertical and horizontal
\nscrolling.<\/p>\n
When operating in alternate-display mode this command has a
\nbroader meaning.<\/p>\n
0\u00a0 :Zero-Suppress toggle
\nThis command determines whether zeros are shown or suppressed
\nfor many of the fields in a task window.\u00a0 Fields like UID,
\nGID, NI, PR or P are not affected by this toggle.<\/p>\n
A\u00a0 :Alternate-Display-Mode toggle
\nThis command will switch between full-screen mode and
\nalternate-display mode.\u00a0 See topic 5. ALTERNATE-DISPLAY
\nProvisions and the `g’ interactive command for insight into
\n`current’ windows and field groups.<\/p>\n
B\u00a0 :Bold-Disable\/Enable toggle
\nThis command will influence use of the bold terminfo
\ncapability and alters both the summary area and task area for
\nthe `current’ window.\u00a0 While it is intended primarily for use
\nwith dumb terminals, it can be applied anytime.<\/p>\n
Note: When this toggle is On and top is operating in
\nmonochrome mode, the entire display will appear as normal
\ntext.\u00a0 Thus, unless the `x’ and\/or `y’ toggles are using
\nreverse for emphasis, there will be no visual confirmation
\nthat they are even on.<\/p>\n
*\u00a0 d | s\u00a0 :Change-Delay-Time-interval
\nYou will be prompted to enter the delay time, in seconds,
\nbetween display updates.<\/p>\n
Fractional seconds are honored, but a negative number is not
\nallowed.\u00a0 Entering 0 causes (nearly) continuous updates, with
\nan unsatisfactory display as the system and tty driver try to
\nkeep up with top’s demands.\u00a0 The delay value is inversely
\nproportional to system loading, so set it with care.<\/p>\n
If at any time you wish to know the current delay time, simply
\nask for help and view the system summary on the second line.<\/p>\n
E\u00a0 :Extend-Memory-Scale in Summary Area
\nWith this command you can cycle through the available summary
\narea memory scaling which ranges from KiB (kibibytes or 1,024
\nbytes) through EiB (exbibytes or 1,152,921,504,606,846,976
\nbytes).<\/p>\n
If you see a `+’ between a displayed number and the following
\nlabel, it means that top was forced to truncate some portion
\nof that number.\u00a0 By raising the scaling factor, such
\ntruncation can be avoided.<\/p>\n
e\u00a0 :Extend-Memory-Scale in Task Windows
\nWith this command you can cycle through the available task
\nwindow memory scaling which ranges from KiB (kibibytes or
\n1,024 bytes) through PiB (pebibytes or 1,125,899,906,842,624
\nbytes).<\/p>\n
While top will try to honor the selected target range,
\nadditional scaling might still be necessary in order to
\naccommodate current values.\u00a0 If you wish to see a more
\nhomogeneous result in the memory columns, raising the scaling
\nrange will usually accomplish that goal.\u00a0 Raising it too high,
\nhowever, is likely to produce an all zero result which cannot
\nbe suppressed with the `0′ interactive command.<\/p>\n
g\u00a0 :Choose-Another-Window\/Field-Group
\nYou will be prompted to enter a number between 1 and 4
\ndesignating the field group which should be made the `current’
\nwindow.\u00a0 You will soon grow comfortable with these 4 windows,
\nespecially after experimenting with alternate-display mode.<\/p>\n
H\u00a0 :Threads-mode toggle
\nWhen this toggle is On, individual threads will be displayed
\nfor all processes in all visible task windows.\u00a0 Otherwise, top
\ndisplays a summation of all threads in each process.<\/p>\n
I\u00a0 :Irix\/Solaris-Mode toggle
\nWhen operating in Solaris mode (`I’ toggled Off), a task’s cpu
\nusage will be divided by the total number of CPUs.\u00a0 After
\nissuing this command, you’ll be told the new state of this
\ntoggle.<\/p>\n
*\u00a0 k\u00a0 :Kill-a-task
\nYou will be prompted for a PID and then the signal to send.<\/p>\n
Entering no PID or a negative number will be interpreted as
\nthe default shown in the prompt (the first task displayed).\u00a0 A
\nPID value of zero means the top program itself.<\/p>\n
The default signal, as reflected in the prompt, is SIGTERM.
\nHowever, you can send any signal, via number or name.<\/p>\n
If you wish to abort the kill process, do one of the following
\ndepending on your progress:
\n1) at the pid prompt, type an invalid number
\n2) at the signal prompt, type 0 (or any invalid signal)
\n3) at any prompt, type <Esc><\/p>\n
q\u00a0 :Quit<\/p>\n
*\u00a0 r\u00a0 :Renice-a-Task
\nYou will be prompted for a PID and then the value to nice it
\nto.<\/p>\n
Entering no PID or a negative number will be interpreted as
\nthe default shown in the prompt (the first task displayed).\u00a0 A
\nPID value of zero means the top program itself.<\/p>\n
A positive nice value will cause a process to lose priority.
\nConversely, a negative nice value will cause a process to be
\nviewed more favorably by the kernel.\u00a0 As a general rule,
\nordinary users can only increase the nice value and are
\nprevented from lowering it.<\/p>\n
If you wish to abort the renice process, do one of the
\nfollowing depending on your progress:
\n1) at the pid prompt, type an invalid number
\n2) at the nice prompt, type <Enter> with no input
\n3) at any prompt, type <Esc><\/p>\n
W\u00a0 :Write-the-Configuration-File
\nThis will save all of your options and toggles plus the
\ncurrent display mode and delay time.\u00a0 By issuing this command
\njust before quitting top, you will be able restart later in
\nexactly that same state.<\/p>\n
X\u00a0 :Extra-Fixed-Width
\nSome fields are fixed width and not scalable.\u00a0 As such, they
\nare subject to truncation which would be indicated by a `+’ in
\nthe last position.<\/p>\n
This interactive command can be used to alter the widths of
\nthe following fields:<\/p>\n
field\u00a0 default\u00a0\u00a0\u00a0 field\u00a0 default\u00a0\u00a0\u00a0 field\u00a0 default
\nGID\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 5\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 GROUP\u00a0\u00a0\u00a0\u00a0 8\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 WCHAN\u00a0\u00a0\u00a0 10
\nRUID\u00a0\u00a0\u00a0\u00a0\u00a0 5\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 RUSER\u00a0\u00a0\u00a0\u00a0 8\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 nsIPC\u00a0\u00a0\u00a0 10
\nSUID\u00a0\u00a0\u00a0\u00a0\u00a0 5\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SUSER\u00a0\u00a0\u00a0\u00a0 8\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 nsMNT\u00a0\u00a0\u00a0 10
\nUID\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 5\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 USER\u00a0\u00a0\u00a0\u00a0\u00a0 8\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 nsNET\u00a0\u00a0\u00a0 10
\nTTY\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 8\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 nsPID\u00a0\u00a0\u00a0 10
\nnsUSER\u00a0\u00a0 10
\nnsUTS\u00a0\u00a0\u00a0 10<\/p>\n
You will be prompted for the amount to be added to the default
\nwidths shown above.\u00a0 Entering zero forces a return to those
\ndefaults.<\/p>\n
If you enter a negative number, top will automatically
\nincrease the column size as needed until there is no more
\ntruncated data.\u00a0 You can accelerate this process by reducing
\nthe delay interval or holding down the <Space> bar.<\/p>\n
Note: Whether explicitly or automatically increased, the
\nwidths for these fields are never decreased by top.\u00a0 To narrow
\nthem you must specify a smaller number or restore the
\ndefaults.<\/p>\n
Y\u00a0 :Inspect-Other-Output
\nAfter issuing the `Y’ interactive command, you will be
\nprompted for a target PID.\u00a0 Typing a value or accepting the
\ndefault results in a separate screen.\u00a0 That screen can be used
\nto view a variety of files or piped command output while the
\nnormal top iterative display is paused.<\/p>\n
Note: This interactive command is only fully realized when
\nsupporting entries have been manually added to the end of the
\ntop configuration file.\u00a0 For details on creating those
\nentries, see topic 6c. ADDING INSPECT Entries.<\/p>\n
Most of the keys used to navigate the Inspect feature are
\nreflected in its header prologue.\u00a0 There are, however,
\nadditional keys available once you have selected a particular
\nfile or command.\u00a0 They are familiar to anyone who has used the
\npager `less’ and are summarized here for future reference.<\/p>\n
key\u00a0\u00a0\u00a0\u00a0\u00a0 function
\n=\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 alternate status-line, file or pipeline
\n\/\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 find, equivalent to `L’ locate
\nn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 find next, equivalent to `&’ locate next
\n<Space>\u00a0 scroll down, equivalent to <PgDn>
\nb\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 scroll up, equivalent to <PgUp>
\ng\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 first line, equivalent to <Home>
\nG\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 last line, equivalent to <End><\/p>\n
Z\u00a0 :Change-Color-Mapping
\nThis key will take you to a separate screen where you can
\nchange the colors for the `current’ window, or for all
\nwindows.\u00a0 For details regarding this interactive command see
\ntopic 4d. COLOR Mapping.<\/p>\n
*\u00a0 The commands shown with an asterisk (`*’) are not available in
\nSecure mode, nor will they be shown on the level-1 help screen.<\/p>\n
4b. SUMMARY AREA Commands
\nThe summary area interactive commands are always available in both
\nfull-screen mode and alternate-display mode.\u00a0 They affect the
\nbeginning lines of your display and will determine the position of
\nmessages and prompts.<\/p>\n
These commands always impact just the `current’ window\/field group.
\nSee topic 5. ALTERNATE-DISPLAY Provisions and the `g’ interactive
\ncommand for insight into `current’ windows and field groups.<\/p>\n
C\u00a0 :Show-scroll-coordinates toggle
\nToggle an informational message which is displayed whenever
\nthe message line is not otherwise being used.\u00a0 For additional
\ninformation see topic 5c. SCROLLING a Window.<\/p>\n
l\u00a0 :Load-Average\/Uptime toggle
\nThis is also the line containing the program name (possibly an
\nalias) when operating in full-screen mode or the `current’
\nwindow name when operating in alternate-display mode.<\/p>\n
t\u00a0 :Task\/Cpu-States toggle
\nThis command affects from 2 to many summary area lines,
\ndepending on the state of the `1′, `2′ or `3′ command toggles
\nand whether or not top is running under true SMP.<\/p>\n
This portion of the summary area is also influenced by the `H’
\ninteractive command toggle, as reflected in the total label
\nwhich shows either Tasks or Threads.<\/p>\n
This command serves as a 4-way toggle, cycling through these
\nmodes:
\n1. detailed percentages by category (default)
\n2. abbreviated user\/system and total % + bar graph
\n3. abbreviated user\/system and total % + block graph
\n4. turn off task and cpu states display<\/p>\n
When operating in either of the graphic modes, the display
\nbecomes much more meaningful when individual CPUs or NUMA
\nnodes are also displayed.\u00a0 See the the `1′, `2′ and `3′
\ncommands below for additional information.<\/p>\n
m\u00a0 :Memory\/Swap-Usage toggle
\nThis command affects the two summary area lines dealing with
\nphysical and virtual memory.<\/p>\n
This command serves as a 4-way toggle, cycling through these
\nmodes:
\n1. detailed percentages by memory type (default)
\n2. abbreviated % used\/total available + bar graph
\n3. abbreviated % used\/total available + block graph
\n4. turn off memory display<\/p>\n
1\u00a0 :Single\/Separate-Cpu-States toggle
\nThis command affects how the `t’ command’s Cpu States portion
\nis shown.\u00a0 Although this toggle exists primarily to serve
\nmassively-parallel SMP machines, it is not restricted to
\nsolely SMP environments.<\/p>\n
When you see `%Cpu(s):’ in the summary area, the `1′ toggle is
\nOn and all cpu information is gathered in a single line.
\nOtherwise, each cpu is displayed separately as: `%Cpu0, %Cpu1,
\n…’\u00a0 up to available screen height.<\/p>\n
2\u00a0 :NUMA-Nodes\/Cpu-Summary toggle
\nThis command toggles between the `1′ command cpu summary
\ndisplay (only) or a summary display plus the cpu usage
\nstatistics for each NUMA Node.\u00a0 It is only available if a
\nsystem has the requisite NUMA support.<\/p>\n
3\u00a0 :Expand-NUMA-Node
\nYou will be invited to enter a number representing a NUMA
\nNode.\u00a0 Thereafter, a node summary plus the statistics for each
\ncpu in that node will be shown until either the `1′ or `2′
\ncommand toggle is pressed.\u00a0 This interactive command is only
\navailable if a system has the requisite NUMA support.<\/p>\n
Note: If the entire summary area has been toggled Off for any window,
\nyou would be left with just the message line.\u00a0 In that way, you will
\nhave maximized available task rows but (temporarily) sacrificed the
\nprogram name in full-screen mode or the `current’ window name when in
\nalternate-display mode.<\/p>\n
4c. TASK AREA Commands
\nThe task area interactive commands are always available in
\nfull-screen mode.<\/p>\n
The task area interactive commands are never available in
\nalternate-display mode if the `current’ window’s task display has
\nbeen toggled Off (see topic 5. ALTERNATE-DISPLAY Provisions).<\/p>\n
APPEARANCE of task window<\/p>\n
J\u00a0 :Justify-Numeric-Columns toggle
\nAlternates between right-justified (the default) and left-
\njustified numeric data.\u00a0 If the numeric data completely fills
\nthe available column, this command toggle may impact the
\ncolumn header only.<\/p>\n
j\u00a0 :Justify-Character-Columns toggle
\nAlternates between left-justified (the default) and right-
\njustified character data.\u00a0 If the character data completely
\nfills the available column, this command toggle may impact the
\ncolumn header only.<\/p>\n
The following commands will also be influenced by the state of the
\nglobal `B’ (bold enable) toggle.<\/p>\n
b\u00a0 :Bold\/Reverse toggle
\nThis command will impact how the `x’ and `y’ toggles are
\ndisplayed.\u00a0 It may also impact the summary area when a bar
\ngraph has been selected for cpu states or memory usage via the
\n‘t’ or ‘m’ toggles.<\/p>\n
x\u00a0 :Column-Highlight toggle
\nChanges highlighting for the current sort field.\u00a0 If you
\nforget which field is being sorted this command can serve as a
\nquick visual reminder, providing the sort field is being
\ndisplayed.\u00a0 The sort field might not be visible because:
\n1) there is insufficient Screen Width
\n2) the `f’ interactive command turned it Off<\/p>\n
Note: Whenever Searching and\/or Other Filtering is active in a
\nwindow, column highlighting is temporarily disabled.\u00a0 See the
\nnotes at the end of topics 5d. SEARCHING and 5e. FILTERING for
\nan explanation why.<\/p>\n
y\u00a0 :Row-Highlight toggle
\nChanges highlighting for “running” tasks.\u00a0 For additional
\ninsight into this task state, see topic 3a. DESCRIPTIONS of
\nFields, the `S’ field (Process Status).<\/p>\n
Use of this provision provides important insight into your
\nsystem’s health.\u00a0 The only costs will be a few additional tty
\nescape sequences.<\/p>\n
z\u00a0 :Color\/Monochrome toggle
\nSwitches the `current’ window between your last used color
\nscheme and the older form of black-on-white or white-on-black.
\nThis command will alter both the summary area and task area
\nbut does not affect the state of the `x’, `y’ or `b’ toggles.<\/p>\n
CONTENT of task window<\/p>\n
c\u00a0 :Command-Line\/Program-Name toggle
\nThis command will be honored whether or not the COMMAND column
\nis currently visible.\u00a0 Later, should that field come into
\nview, the change you applied will be seen.<\/p>\n
f | F\u00a0 :Fields-Management
\nThese keys display a separate screen where you can change
\nwhich fields are displayed, their order and also designate the
\nsort field.\u00a0 For additional information on these interactive
\ncommands see topic 3b. MANAGING Fields.<\/p>\n
o | O\u00a0 :Other-Filtering
\nYou will be prompted for the selection criteria which then
\ndetermines which tasks will be shown in the `current’ window.
\nYour criteria can be made case sensitive or case can be
\nignored.\u00a0 And you determine if top should include or exclude
\nmatching tasks.<\/p>\n
See topic 5e. FILTERING in a window for details on these and
\nadditional related interactive commands.<\/p>\n
S\u00a0 :Cumulative-Time-Mode toggle
\nWhen Cumulative mode is On, each process is listed with the
\ncpu time that it and its dead children have used.<\/p>\n
When Off, programs that fork into many separate tasks will
\nappear less demanding.\u00a0 For programs like `init’ or a shell
\nthis is appropriate but for others, like compilers, perhaps
\nnot.\u00a0 Experiment with two task windows sharing the same sort
\nfield but with different `S’ states and see which
\nrepresentation you prefer.<\/p>\n
After issuing this command, you’ll be informed of the new
\nstate of this toggle.\u00a0 If you wish to know in advance whether
\nor not Cumulative mode is in effect, simply ask for help and
\nview the window summary on the second line.<\/p>\n
u | U\u00a0 :Show-Specific-User-Only
\nYou will be prompted for the uid or name of the user to
\ndisplay.\u00a0 The -u option matches on\u00a0 effective user whereas the
\n-U option matches on any user (real, effective, saved, or
\nfilesystem).<\/p>\n
Thereafter, in that task window only matching users will be
\nshown, or possibly no processes will be shown.\u00a0 Prepending an
\nexclamation point (‘!’) to the user id or name instructs top
\nto display only processes with users not matching the one
\nprovided.<\/p>\n
Different task windows can be used to filter different users.
\nLater, if you wish to monitor all users again in the `current’
\nwindow, re-issue this command but just press <Enter> at the
\nprompt.<\/p>\n
V\u00a0 :Forest-View-Mode toggle
\nIn this mode, processes are reordered according to their
\nparents and the layout of the COMMAND column resembles that of
\na tree.\u00a0 In forest view mode it is still possible to toggle
\nbetween program name and command line (see the `c’ interactive
\ncommand) or between processes and threads (see the `H’
\ninteractive command).<\/p>\n
Note: Typing any key affecting the sort order will exit forest
\nview mode in the `current’ window.\u00a0 See topic 4c. TASK AREA
\nCommands, SORTING for information on those keys.<\/p>\n
SIZE of task window<\/p>\n
i\u00a0 :Idle-Process toggle
\nDisplays all tasks or just active tasks.\u00a0 When this toggle is
\nOff, tasks that have not used any CPU since the last update
\nwill not be displayed.\u00a0 However, due to the granularity of the
\n%CPU and TIME+ fields, some processes may still be displayed
\nthat appear to have used no CPU.<\/p>\n
If this command is applied to the last task display when in
\nalternate-display mode, then it will not affect the window’s
\nsize, as all prior task displays will have already been
\npainted.<\/p>\n
n | #\u00a0 :Set-Maximum-Tasks
\nYou will be prompted to enter the number of tasks to display.
\nThe lessor of your number and available screen rows will be
\nused.<\/p>\n
When used in alternate-display mode, this is the command that
\ngives you precise control over the size of each currently
\nvisible task display, except for the very last.\u00a0 It will not
\naffect the last window’s size, as all prior task displays will
\nhave already been painted.<\/p>\n
Note: If you wish to increase the size of the last visible
\ntask display when in alternate-display mode, simply decrease
\nthe size of the task display(s) above it.<\/p>\n
SORTING of task window<\/p>\n
For compatibility, this top supports most of the former top sort
\nkeys.\u00a0 Since this is primarily a service to former top users,
\nthese commands do not appear on any help screen.
\ncommand\u00a0\u00a0 sorted-field\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 supported
\nA\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 start time (non-display)\u00a0\u00a0\u00a0\u00a0\u00a0 No
\nM\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 %MEM\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Yes
\nN\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PID\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Yes
\nP\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 %CPU\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Yes
\nT\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TIME+\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Yes<\/p>\n
Before using any of the following sort provisions, top suggests
\nthat you temporarily turn on column highlighting using the `x’
\ninteractive command.\u00a0 That will help ensure that the actual sort
\nenvironment matches your intent.<\/p>\n
The following interactive commands will only be honored when the
\ncurrent sort field is visible.\u00a0 The sort field might not be
\nvisible because:
\n1) there is insufficient Screen Width
\n2) the `f’ interactive command turned it Off<\/p>\n
<\u00a0 :Move-Sort-Field-Left
\nMoves the sort column to the left unless the current sort
\nfield is the first field being displayed.<\/p>\n
>\u00a0 :Move-Sort-Field-Right
\nMoves the sort column to the right unless the current sort
\nfield is the last field being displayed.<\/p>\n
The following interactive commands will always be honored whether
\nor not the current sort field is visible.<\/p>\n
f | F\u00a0 :Fields-Management
\nThese keys display a separate screen where you can change
\nwhich field is used as the sort column, among other
\nfunctions.\u00a0 This can be a convenient way to simply verify
\nthe current sort field, when running top with column
\nhighlighting turned Off.<\/p>\n
R\u00a0 :Reverse\/Normal-Sort-Field toggle
\nUsing this interactive command you can alternate between
\nhigh-to-low and low-to-high sorts.<\/p>\n
Note: Field sorting uses internal values, not those in column
\ndisplay.\u00a0 Thus, the TTY and WCHAN fields will violate strict ASCII
\ncollating sequence.<\/p>\n
4d. COLOR Mapping
\nWhen you issue the `Z’ interactive command, you will be presented
\nwith a separate screen.\u00a0 That screen can be used to change the colors
\nin just the `current’ window or in all four windows before returning
\nto the top display.<\/p>\n
The following interactive commands are available.
\n4 upper case letters to select a target
\n8 numbers to select a color
\nnormal toggles available
\nB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 :bold disable\/enable
\nb\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 :running tasks “bold”\/reverse
\nz\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 :color\/mono
\nother commands available
\na\/w\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 :apply, then go to next\/prior
\n<Enter>\u00a0\u00a0 :apply and exit
\nq\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 :abandon current changes and exit<\/p>\n
If you use `a’ or `w’ to cycle the targeted window, you will have
\napplied the color scheme that was displayed when you left that
\nwindow.\u00a0 You can, of course, easily return to any window and reapply
\ndifferent colors or turn colors Off completely with the `z’ toggle.<\/p>\n
The Color Mapping screen can also be used to change the `current’
\nwindow\/field group in either full-screen mode or alternate-display
\nmode.\u00a0 Whatever was targeted when `q’ or <Enter> was pressed will be
\nmade current as you return to the top display.<\/p>\n
5. ALTERNATE-DISPLAY Provisions\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
5a. WINDOWS Overview
\nField Groups\/Windows:
\nIn full-screen mode there is a single window represented by the
\nentire screen.\u00a0 That single window can still be changed to display
\n1 of 4 different field groups (see the `g’ interactive command,
\nrepeated below).\u00a0 Each of the 4 field groups has a unique
\nseparately configurable summary area and its own configurable task
\narea.<\/p>\n
In alternate-display mode, those 4 underlying field groups can now
\nbe made visible simultaneously, or can be turned Off individually
\nat your command.<\/p>\n
The summary area will always exist, even if it’s only the message
\nline.\u00a0 At any given time only one summary area can be displayed.
\nHowever, depending on your commands, there could be from zero to
\nfour separate task displays currently showing on the screen.<\/p>\n
Current Window:
\nThe `current’ window is the window associated with the summary
\narea and the window to which task related commands are always
\ndirected.\u00a0 Since in alternate-display mode you can toggle the task
\ndisplay Off, some commands might be restricted for the `current’
\nwindow.<\/p>\n
A further complication arises when you have toggled the first
\nsummary area line Off.\u00a0 With the loss of the window name (the `l’
\ntoggled line), you’ll not easily know what window is the `current’
\nwindow.<\/p>\n
5b. COMMANDS for Windows
\n– | _\u00a0 :Show\/Hide-Window(s) toggles
\nThe `-‘ key turns the `current’ window’s task display On and
\nOff.\u00a0 When On, that task area will show a minimum of the
\ncolumns header you’ve established with the `f’ interactive
\ncommand.\u00a0 It will also reflect any other task area
\noptions\/toggles you’ve applied yielding zero or more tasks.<\/p>\n
The `_’ key does the same for all task displays.\u00a0 In other
\nwords, it switches between the currently visible task
\ndisplay(s) and any task display(s) you had toggled Off.\u00a0 If
\nall 4 task displays are currently visible, this interactive
\ncommand will leave the summary area as the only display
\nelement.<\/p>\n
*\u00a0 = | +\u00a0 :Equalize-(reinitialize)-Window(s)
\nThe `=’ key forces the `current’ window’s task display to be
\nvisible.\u00a0 It also reverses any `i’ (idle tasks), `n’ (max
\ntasks), `u\/U’ (user filter) and `o\/O’ (other filter) commands
\nthat might be active.\u00a0 Also, if the window had been scrolled,
\nit will be reset with this command.\u00a0 See topic 5c. SCROLLING a
\nWindow for additional information regarding vertical and
\nhorizontal scrolling.<\/p>\n
The `+’ key does the same for all windows.\u00a0 The four task
\ndisplays will reappear, evenly balanced.\u00a0 They will also have
\nretained any customizations you had previously applied, except
\nfor the `i’ (idle tasks), `n’ (max tasks), `u\/U’ (user
\nfilter), `o\/O’ (other filter) and scrolling interactive
\ncommands.<\/p>\n
*\u00a0 A\u00a0 :Alternate-Display-Mode toggle
\nThis command will switch between full-screen mode and
\nalternate-display mode.<\/p>\n
The first time you issue this command, all four task displays
\nwill be shown.\u00a0 Thereafter when you switch modes, you will see
\nonly the task display(s) you’ve chosen to make visible.<\/p>\n
*\u00a0 a | w\u00a0 :Next-Window-Forward\/Backward
\nThis will change the `current’ window, which in turn changes
\nthe window to which commands are directed.\u00a0 These keys act in
\na circular fashion so you can reach any desired window using
\neither key.<\/p>\n
Assuming the window name is visible (you have not toggled `l’
\nOff), whenever the `current’ window name loses its
\nemphasis\/color, that’s a reminder the task display is Off and
\nmany commands will be restricted.<\/p>\n
*\u00a0 g\u00a0 :Choose-Another-Window\/Field-Group
\nYou will be prompted to enter a number between 1 and 4
\ndesignating the field group which should be made the `current’
\nwindow.<\/p>\n
In full-screen mode, this command is necessary to alter the
\n`current’ window.\u00a0 In alternate-display mode, it is simply a
\nless convenient alternative to the `a’ and `w’ commands.<\/p>\n
G\u00a0 :Change-Window\/Field-Group-Name
\nYou will be prompted for a new name to be applied to the
\n`current’ window.\u00a0 It does not require that the window name be
\nvisible (the `l’ toggle to be On).<\/p>\n
*\u00a0 The interactive commands shown with an asterisk (`*’) have use
\nbeyond alternate-display mode.
\n=, A, g\u00a0\u00a0\u00a0 are always available
\na, w\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 act the same with color mapping
\nand fields management<\/p>\n
5c. SCROLLING a Window
\nTypically a task window is a partial view into a systems’s total
\ntasks\/threads which shows only some of the available fields\/columns.
\nWith these scrolling keys, you can move that view vertically or
\nhorizontally to reveal any desired task or column.<\/p>\n
Up,PgUp\u00a0 :Scroll-Tasks
\nMove the view up toward the first task row, until the first task
\nis displayed at the top of the `current’ window.\u00a0 The Up arrow
\nkey moves a single line while PgUp scrolls the entire window.<\/p>\n
Down,PgDn\u00a0 :Scroll-Tasks
\nMove the view down toward the last task row, until the last task
\nis the only task displayed at the top of the `current’ window.
\nThe Down arrow key moves a single line while PgDn scrolls the
\nentire window.<\/p>\n
Left,Right\u00a0 :Scroll-Columns
\nMove the view of displayable fields horizontally one column at a
\ntime.<\/p>\n
Note: As a reminder, some fields\/columns are not fixed-width but
\nallocated all remaining screen width when visible.\u00a0 When
\nscrolling right or left, that feature may produce some unexpected
\nresults initially.<\/p>\n
Additionally, there are special provisions for any variable width
\nfield when positioned as the last displayed field.\u00a0 Once that
\nfield is reached via the right arrow key, and is thus the only
\ncolumn shown, you can continue scrolling horizontally within such
\na field.\u00a0 See the `C’ interactive command below for additional
\ninformation.<\/p>\n
Home\u00a0 :Jump-to-Home-Position
\nReposition the display to the un-scrolled coordinates.<\/p>\n
End\u00a0 :Jump-to-End-Position
\nReposition the display so that the rightmost column reflects the
\nlast displayable field and the bottom task row represents the
\nlast task.<\/p>\n
Note: From this position it is still possible to scroll down and
\nright using the arrow keys.\u00a0 This is true until a single column
\nand a single task is left as the only display element.<\/p>\n
C\u00a0 :Show-scroll-coordinates toggle
\nToggle an informational message which is displayed whenever the
\nmessage line is not otherwise being used.\u00a0 That message will take
\none of two forms depending on whether or not a variable width
\ncolumn has also been scrolled.<\/p>\n
scroll coordinates: y = n\/n (tasks), x = n\/n (fields)
\nscroll coordinates: y = n\/n (tasks), x = n\/n (fields) + nn<\/p>\n
The coordinates shown as n\/n are relative to the upper left
\ncorner of the `current’ window.\u00a0 The additional `+ nn’ represents
\nthe displacement into a variable width column when it has been
\nscrolled horizontally.\u00a0 Such displacement occurs in normal 8
\ncharacter tab stop amounts via the right and left arrow keys.<\/p>\n
y = n\/n (tasks)
\nThe first n represents the topmost visible task and is
\ncontrolled by scrolling keys.\u00a0 The second n is updated
\nautomatically to reflect total tasks.<\/p>\n
x = n\/n (fields)
\nThe first n represents the leftmost displayed column and is
\ncontrolled by scrolling keys.\u00a0 The second n is the total
\nnumber of displayable fields and is established with the `f’
\ninteractive command.<\/p>\n
The above interactive commands are always available in full-screen
\nmode but never available in alternate-display mode if the `current’
\nwindow’s task display has been toggled Off.<\/p>\n
Note: When any form of filtering is active, you can expect some
\nslight aberrations when scrolling since not all tasks will be
\nvisible.\u00a0 This is particularly apparent when using the Up\/Down arrow
\nkeys.<\/p>\n
5d. SEARCHING in a Window
\nYou can use these interactive commands to locate a task row
\ncontaining a particular value.<\/p>\n
L\u00a0 :Locate-a-string
\nYou will be prompted for the case-sensitive string to locate
\nstarting from the current window coordinates.\u00a0 There are no
\nrestrictions on search string content.<\/p>\n
Searches are not limited to values from a single field or column.
\nAll of the values displayed in a task row are allowed in a search
\nstring.\u00a0 You may include spaces, numbers, symbols and even forest
\nview artwork.<\/p>\n
Keying <Enter> with no input will effectively disable the `&’ key
\nuntil a new search string is entered.<\/p>\n
&\u00a0 :Locate-next
\nAssuming a search string has been established, top will attempt
\nto locate the next occurrence.<\/p>\n
When a match is found, the current window is repositioned vertically
\nso the task row containing that string is first.\u00a0 The scroll
\ncoordinates message can provide confirmation of such vertical
\nrepositioning (see the `C’ interactive command).\u00a0 Horizontal
\nscrolling, however, is never altered via searching.<\/p>\n
The availability of a matching string will be influenced by the
\nfollowing factors.<\/p>\n
a. Which fields are displayable from the total available,
\nsee topic 3b. MANAGING Fields.<\/p>\n
b. Scrolling a window vertically and\/or horizontally,
\nsee topic 5c. SCROLLING a Window.<\/p>\n
c. The state of the command\/command-line toggle,
\nsee the `c’ interactive command.<\/p>\n
d. The stability of the chosen sort column,
\nfor example PID is good but %CPU bad.<\/p>\n
If a search fails, restoring the `current’ window home (unscrolled)
\nposition, scrolling horizontally, displaying command-lines or
\nchoosing a more stable sort field could yet produce a successful `&’
\nsearch.<\/p>\n
The above interactive commands are always available in full-screen
\nmode but never available in alternate-display mode if the `current’
\nwindow’s task display has been toggled Off.<\/p>\n
Note: Whenever a Search is active in a window, top will turn column
\nhighlighting Off to prevent false matches on internal non-display
\nescape sequences.\u00a0 Such highlighting will be restored when a window’s
\nsearch string is empty.\u00a0 See the `x’ interactive command for
\nadditional information on sort column highlighting.<\/p>\n
5e. FILTERING in a Window
\nYou can use this Other Filter feature to establish selection criteria
\nwhich will then determine which tasks are shown in the `current’
\nwindow.<\/p>\n
Establishing a filter requires: 1) a field name; 2) an operator; and
\n3) a selection value, as a minimum.\u00a0 This is the most complex of
\ntop’s user input requirements so, when you make a mistake, command
\nrecall will be your friend.\u00a0 Remember the Up\/Down arrow keys or their
\naliases when prompted for input.<\/p>\n
Filter Basics<\/p>\n
1. field names are case sensitive and spelled as in the header<\/p>\n
2. selection values need not comprise the full displayed field<\/p>\n
3. a selection is either case insensitive or sensitive to case<\/p>\n
4. the default is inclusion, prepending `!’ denotes exclusions<\/p>\n
5. multiple selection criteria can be applied to a task window<\/p>\n
6. inclusion and exclusion criteria can be used simultaneously<\/p>\n
7. the 1 equality and 2 relational filters can be freely mixed<\/p>\n
8. separate unique filters are maintained for each task window<\/p>\n
If a field is not turned on or is not currently in view, then your
\nselection criteria will not affect the display.\u00a0 Later, should a
\nfiltered field become visible, the selection criteria will then be
\napplied.<\/p>\n
Keyboard Summary<\/p>\n
o\u00a0 :Other-Filter (lower case)
\nYou will be prompted to establish a filter that ignores case
\nwhen matching.<\/p>\n
O\u00a0 :Other-Filter (upper case)
\nYou will be prompted to establish a case sensitive filter.<\/p>\n
^O\u00a0 :Show-Active-Filters (Ctrl key + `o’)
\nThis can serve as a reminder of which filters are active in the
\n`current’ window.\u00a0 A summary will be shown on the message line
\nuntil you press the <Enter> key.<\/p>\n
=\u00a0 :Reset-Filtering in current window
\nThis clears all of your selection criteria in the `current’
\nwindow.\u00a0 It also has additional impact so please see topic 4a.
\nGLOBAL Commands.<\/p>\n
+\u00a0 :Reset-Filtering in all windows
\nThis clears the selection criteria in all windows, assuming you
\nare in alternate-display mode.\u00a0 As with the `=’ interactive
\ncommand, it too has additional consequences so you might wish
\nto see topic 5b. COMMANDS for Windows.<\/p>\n
Input Requirements<\/p>\n
When prompted for selection criteria, the data you provide must
\ntake one of two forms.\u00a0 There are 3 required pieces of
\ninformation, with a 4th as optional.\u00a0 These examples use spaces
\nfor clarity but your input generally would not.
\n#1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #2\u00a0 #3\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ( required )
\nField-Name\u00a0\u00a0 ?\u00a0\u00a0 include-if-value
\n!\u00a0 Field-Name\u00a0\u00a0 ?\u00a0\u00a0 exclude-if-value
\n#4\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ( optional )<\/p>\n
Items #1, #3 and #4 should be self-explanatory.\u00a0 Item #2
\nrepresents both a required delimiter and the operator which must
\nbe one of either equality (`=’) or relation (`<‘ or `>’).<\/p>\n
The `=’ equality operator requires only a partial match and that
\ncan reduce your `if-value’ input requirements.\u00a0 The `>’ or `<‘
\nrelational operators always employ string comparisons, even with
\nnumeric fields.\u00a0 They are designed to work with a field’s default
\njustification and with homogeneous data.\u00a0 When some field’s
\nnumeric amounts have been subjected to scaling while others have
\nnot, that data is no longer homogeneous.<\/p>\n
If you establish a relational filter and you have changed the
\ndefault Numeric or Character justification, that filter is likely
\nto fail.\u00a0 When a relational filter is applied to a memory field
\nand you have not changed the scaling, it may produce misleading
\nresults.\u00a0 This happens, for example, because `100.0m’ (MiB) would
\nappear greater than `1.000g’ (GiB) when compared as strings.<\/p>\n
If your filtered results appear suspect, simply altering
\njustification or scaling may yet achieve the desired objective.
\nSee the `j’, `J’ and `e’ interactive commands for additional
\ninformation.<\/p>\n
Potential Problems<\/p>\n
These GROUP filters could produce the exact same results or the
\nsecond one might not display anything at all, just a blank task
\nwindow.
\nGROUP=root\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ( only the same results when )
\nGROUP=ROOT\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ( invoked via lower case `o’ )<\/p>\n
Either of these RES filters might yield inconsistent and\/or
\nmisleading results, depending on the current memory scaling
\nfactor.\u00a0 Or both filters could produce the exact same results.
\nRES>9999\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ( only the same results when )
\n!RES<10000\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ( memory scaling is at `KiB’ )<\/p>\n
This nMin filter illustrates a problem unique to scalable fields.
\nThis particular field can display a maximum of 4 digits, beyond
\nwhich values are automatically scaled to KiB or above.\u00a0 So while
\namounts greater than 9999 exist, they will appear as 2.6m, 197k,
\netc.
\nnMin>9999\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ( always a blank task window )<\/p>\n
Potential Solutions<\/p>\n
These examples illustrate how Other Filtering can be creatively
\napplied to achieve almost any desired result.\u00a0 Single quotes are
\nsometimes shown to delimit the spaces which are part of a filter
\nor to represent a request for status (^O) accurately.\u00a0 But if you
\nused them with if-values in real life, no matches would be found.<\/p>\n
Assuming field nTH is displayed, the first filter will result in
\nonly multi-threaded processes being shown.\u00a0 It also reminds us
\nthat a trailing space is part of every displayed field.\u00a0 The
\nsecond filter achieves the exact same results with less typing.
\n!nTH=` 1 ‘\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ( ‘ for clarity only )
\nnTH>1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ( same with less i\/p )<\/p>\n
With Forest View mode active and the COMMAND column in view, this
\nfilter effectively collapses child processes so that just 3 levels
\nare shown.
\n!COMMAND=`\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 `- ‘\u00a0\u00a0\u00a0\u00a0 ( ‘ for clarity only )<\/p>\n
The final two filters appear as in response to the status request
\nkey (^O).\u00a0 In reality, each filter would have required separate
\ninput.\u00a0 The PR example shows the two concurrent filters necessary
\nto display tasks with priorities of 20 or more, since some might
\nbe negative.\u00a0 Then by exploiting trailing spaces, the nMin series
\nof filters could achieve the failed `9999′ objective discussed
\nabove.
\n`PR>20’ + `!PR=-‘\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ( 2 for right result )
\n`!nMin=0 ‘ + `!nMin=1 ‘ + `!nMin=2 ‘ + `!nMin=3 ‘ …<\/p>\n
Note: Whenever Other Filtering is active in a window, top will turn
\ncolumn highlighting Off to prevent false matches on internal non-
\ndisplay escape sequences.\u00a0 Such highlighting will be restored when a
\nwindow is no longer subject to filtering.\u00a0 See the `x’ interactive
\ncommand for additional information on sort column highlighting.<\/p>\n
6. FILES\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
6a. SYSTEM Configuration File
\nThe presence of this file will influence which version of the help
\nscreen is shown to an ordinary user.\u00a0 More importantly, it will limit
\nwhat ordinary users are allowed to do when top is running.\u00a0 They will
\nnot be able to issue the following commands.
\nk\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Kill a task
\nr\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Renice a task
\nd or s\u00a0\u00a0 Change delay\/sleep interval<\/p>\n
The system configuration file is not created by top.\u00a0 Rather, you
\ncreate this file manually and place it in the \/etc directory.\u00a0 Its
\nname must be `toprc’ and must have no leading `.’ (period).\u00a0 It must
\nhave only two lines.<\/p>\n
Here is an example of the contents of \/etc\/toprc:
\ns\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 # line 1: secure mode switch
\n5.0\u00a0\u00a0\u00a0\u00a0\u00a0 # line 2: delay interval in seconds<\/p>\n
6b. PERSONAL Configuration File
\nThis file is written as `$HOME\/.your-name-4-top’ + `rc’.\u00a0 Use the `W’
\ninteractive command to create it or update it.<\/p>\n
Here is the general layout:
\nglobal\u00a0\u00a0 # line\u00a0 1: the program name\/alias notation
\n”\u00a0\u00a0\u00a0\u00a0\u00a0 # line\u00a0 2: id,altscr,irixps,delay,curwin
\nper ea\u00a0\u00a0 # line\u00a0 a: winname,fieldscur
\nwindow\u00a0\u00a0 # line\u00a0 b: winflags,sortindx,maxtasks,graph modes
\n”\u00a0\u00a0\u00a0\u00a0\u00a0 # line\u00a0 c: summclr,msgsclr,headclr,taskclr
\nglobal\u00a0\u00a0 # line 15: additional miscellaneous settings
\n”\u00a0\u00a0\u00a0\u00a0\u00a0 # any remaining lines are devoted to the
\n”\u00a0\u00a0\u00a0\u00a0\u00a0 # generalized inspect provisions
\n”\u00a0\u00a0\u00a0\u00a0\u00a0 # discussed below<\/p>\n
If the $HOME variable is not present, top will try to write the
\npersonal configuration file to the current directory, subject to
\npermissions.<\/p>\n
6c. ADDING INSPECT Entries
\nTo exploit the `Y’ interactive command, you must add entries at the
\nend of the top personal configuration file.\u00a0 Such entries simply
\nreflect a file to be read or command\/pipeline to be executed whose
\nresults will then be displayed in a separate scrollable, searchable
\nwindow.<\/p>\n
If you don’t know the location or name of your top rcfile, use the
\n`W’ interactive command to rewrite it and note those details.<\/p>\n
Inspect entries can be added with a redirected echo or by editing the
\nconfiguration file.\u00a0 Redirecting an echo risks overwriting the rcfile
\nshould it replace (>) rather than append (>>) to that file.
\nConversely, when using an editor care must be taken not to corrupt
\nexisting lines, some of which will contain unprintable data or
\nunusual characters.<\/p>\n
Those Inspect entries beginning with a `#’ character are ignored,
\nregardless of content.\u00a0 Otherwise they consist of the following 3
\nelements, each of which must be separated by a tab character (thus 2
\n`\\t’ total):<\/p>\n
.type:\u00a0 literal `file’ or `pipe’
\n.name:\u00a0 selection shown on the Inspect screen
\n.fmts:\u00a0 string representing a path or command<\/p>\n
The two types of Inspect entries are not interchangeable.\u00a0 Those
\ndesignated `file’ will be accessed using fopen and must reference a
\nsingle file in the `.fmts’ element.\u00a0 Entries specifying `pipe’ will
\nemploy popen, their `.fmts’ element could contain many pipelined
\ncommands and, none can be interactive.<\/p>\n
If the file or pipeline represented in your `.fmts’ deals with the
\nspecific PID input or accepted when prompted, then the format string
\nmust also contain the `%d’ specifier, as these examples illustrate.<\/p>\n
.fmts=\u00a0 \/proc\/%d\/numa_maps
\n.fmts=\u00a0 lsof -P -p %d<\/p>\n
For `pipe’ type entries only, you may also wish to redirect stderr to
\nstdout for a more comprehensive result.\u00a0 Thus the format string
\nbecomes:<\/p>\n
.fmts=\u00a0 pmap -x %d 2>&1<\/p>\n
Here are examples of both types of Inspect entries as they might
\nappear in the rcfile.\u00a0 The first entry will be ignored due to the
\ninitial `#’ character.\u00a0 For clarity, the pseudo tab depictions (^I)
\nare surrounded by an extra space but the actual tabs would not be.<\/p>\n
# pipe ^I Sockets ^I lsof -n -P -i 2>&1
\npipe ^I Open Files ^I lsof -P -p %d 2>&1
\nfile ^I NUMA Info ^I \/proc\/%d\/numa_maps
\npipe ^I Log ^I tail -n100 \/var\/log\/syslog | sort -Mr<\/p>\n
Except for the commented entry above, these next examples show what
\ncould be echoed to achieve similar results, assuming the rcfile name
\nwas `.toprc’.\u00a0 However, due to the embedded tab characters, each of
\nthese lines should be preceded by `\/bin\/echo -e’, not just a simple
\nan `echo’, to enable backslash interpretation regardless of which
\nshell you use.<\/p>\n
“pipe\\tOpen Files\\tlsof -P -p %d 2>&1” >> ~\/.toprc
\n“file\\tNUMA Info\\t\/proc\/%d\/numa_maps” >> ~\/.toprc
\n“pipe\\tLog\\ttail -n200 \/var\/log\/syslog | sort -Mr” >> ~\/.toprc<\/p>\n
Caution: If any inspect entry you create produces output with
\nunprintable characters they will be displayed in either the ^C
\nnotation or hexadecimal <FF> form, depending on their value.\u00a0 This
\napplies to tab characters as well, which will show as `^I’.\u00a0 If you
\nwant a truer representation, any embedded tabs should be expanded.<\/p>\n
# next would have contained `\\t’ …
\n# file ^I <your_name> ^I \/proc\/%d\/status
\n# but this will eliminate embedded `\\t’ …
\npipe ^I <your_name> ^I cat \/proc\/%d\/status | expand –<\/p>\n
The above example takes what could have been a `file’ entry but
\nemploys a `pipe’ instead so as to expand the embedded tabs.<\/p>\n
Note: While `pipe’ type entries have been discussed in terms of
\npipelines and commands, there is nothing to prevent you from
\nincluding\u00a0 shell scripts as well.\u00a0 Perhaps even newly created scripts
\ndesigned specifically for the `Y’ interactive command.<\/p>\n
Lastly, as the number of your Inspect entries grows over time, the
\n`Options:’ row will be truncated when screen width is exceeded.\u00a0 That
\ndoes not affect operation other than to make some selections
\ninvisible.<\/p>\n
However, if some choices are lost to truncation but you want to see
\nmore options, there is an easy solution hinted at below.<\/p>\n
Inspection Pause at pid …
\nUse:\u00a0 left\/right then <Enter> …
\nOptions:\u00a0 help\u00a0 1\u00a0 2\u00a0 3\u00a0 4\u00a0 5\u00a0 6\u00a0 7\u00a0 8\u00a0 9\u00a0 10\u00a0 11 …<\/p>\n
The entries in the top rcfile would have a number for the `.name’
\nelement and the `help’ entry would identify a shell script you’ve
\nwritten explaining what those numbered selections actually mean.\u00a0 In
\nthat way, many more choices can be made visible.<\/p>\n
7. STUPID TRICKS Sampler\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
Many of these tricks work best when you give top a scheduling boost.
\nSo plan on starting him with a nice value of -10, assuming you’ve got
\nthe authority.<\/p>\n
7a. Kernel Magic
\nFor these stupid tricks, top needs full-screen mode.<\/p>\n
\u00b7\u00a0 The user interface, through prompts and help, intentionally
\nimplies that the delay interval is limited to tenths of a second.
\nHowever, you’re free to set any desired delay.\u00a0 If you want to see
\nLinux at his scheduling best, try a delay of .09 seconds or less.<\/p>\n
For this experiment, under x-windows open an xterm and maximize
\nit.\u00a0 Then do the following:
\n. provide a scheduling boost and tiny delay via:
\nnice -n -10 top -d.09
\n. keep sorted column highlighting Off so as to
\nminimize path length
\n. turn On reverse row highlighting for emphasis
\n. try various sort columns (TIME\/MEM work well),
\nand normal or reverse sorts to bring the most
\nactive processes into view<\/p>\n
What you’ll see is a very busy Linux doing what he’s always done
\nfor you, but there was no program available to illustrate this.<\/p>\n
\u00b7\u00a0 Under an xterm using `white-on-black’ colors, on top’s Color
\nMapping screen set the task color to black and be sure that task
\nhighlighting is set to bold, not reverse.\u00a0 Then set the delay
\ninterval to around .3 seconds.<\/p>\n
After bringing the most active processes into view, what you’ll
\nsee are the ghostly images of just the currently running tasks.<\/p>\n
\u00b7\u00a0 Delete the existing rcfile, or create a new symlink.\u00a0 Start this
\nnew version then type `T’ (a secret key, see topic 4c. Task Area
\nCommands, SORTING) followed by `W’ and `q’.\u00a0 Finally, restart the
\nprogram with -d0 (zero delay).<\/p>\n
Your display will be refreshed at three times the rate of the
\nformer top, a 300% speed advantage.\u00a0 As top climbs the TIME
\nladder, be as patient as you can while speculating on whether or
\nnot top will ever reach the top.<\/p>\n
7b. Bouncing Windows
\nFor these stupid tricks, top needs alternate-display mode.<\/p>\n
\u00b7\u00a0 With 3 or 4 task displays visible, pick any window other than the
\nlast and turn idle processes Off using the `i’ command toggle.
\nDepending on where you applied `i’, sometimes several task
\ndisplays are bouncing and sometimes it’s like an accordion, as top
\ntries his best to allocate space.<\/p>\n
\u00b7\u00a0 Set each window’s summary lines differently: one with no memory
\n(‘m’); another with no states (‘t’); maybe one with nothing at
\nall, just the message line.\u00a0 Then hold down `a’ or `w’ and watch a
\nvariation on bouncing windows\u00a0 —\u00a0 hopping windows.<\/p>\n
\u00b7\u00a0 Display all 4 windows and for each, in turn, set idle processes to
\nOff using the `i’ command toggle.\u00a0 You’ve just entered the
\n“extreme bounce” zone.<\/p>\n
7c. The Big Bird Window
\nThis stupid trick also requires alternate-display mode.<\/p>\n
\u00b7\u00a0 Display all 4 windows and make sure that 1:Def is the `current’
\nwindow.\u00a0 Then, keep increasing window size with the `n’
\ninteractive command until all the other task displays are “pushed
\nout of the nest”.<\/p>\n
When they’ve all been displaced, toggle between all
\nvisible\/invisible windows using the `_’ command toggle.\u00a0 Then
\nponder this:
\nis top fibbing or telling honestly your imposed truth?<\/p>\n
7d. The Ol’ Switcheroo
\nThis stupid trick works best without alternate-display mode, since
\njustification is active on a per window basis.<\/p>\n
\u00b7\u00a0 Start top and make COMMAND the last (rightmost) column displayed.
\nIf necessary, use the `c’ command toggle to display command lines
\nand ensure that forest view mode is active with the `V’ command
\ntoggle.<\/p>\n
Then use the up\/down arrow keys to position the display so that
\nsome truncated command lines are shown (`+’ in last position).
\nYou may have to resize your xterm to produce truncation.<\/p>\n
Lastly, use the `j’ command toggle to make the COMMAND column
\nright justified.<\/p>\n
Now use the right arrow key to reach the COMMAND column.
\nContinuing with the right arrow key, watch closely the direction
\nof travel for the command lines being shown.<\/p>\n
some lines travel left, while others travel right<\/p>\n
eventually all lines will Switcheroo, and move right<\/p>\n
8. BUGS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
To report bugs, follow the instructions at:
\nhttp:\/\/www.debian.org\/Bugs\/Reporting<\/p>\n
9. HISTORY Former top\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
The original top was written by Roger Binns, based on Branko
\nLankester’s <lankeste@fwi.uva.nl> ps program.<\/p>\n
Robert Nation <nation@rocket.sanders.lockheed.com> adapted it for the
\nproc file system.<\/p>\n
Helmut Geyer <Helmut.Geyer@iwr.uni-heidelberg.de> added support for
\nconfigurable fields.<\/p>\n
Plus many other individuals contributed over the years.<\/p>\n
10. AUTHOR\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
This entirely new and enhanced replacement was written by:
\nJim Warner, <james.warner@comcast.net><\/p>\n
With invaluable help from:
\nCraig Small, <csmall@enc.com.au>
\nAlbert Cahalan, <albert@users.sf.net><\/p>\n
11. SEE Also\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
free(1), ps(1), uptime(1), atop(1), slabtop(1), vmstat(8), w(1).<\/p>\n
COLOPHON\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top<\/p>\n
This page is part of the procps-ng (\/proc filesystem utilities)
\nproject.\u00a0 Information about the project can be found at
\n\u27e8http:\/\/sourceforge.net\/projects\/procps-ng\/\u27e9.\u00a0 If you have a bug
\nreport for this manual page, see
\n\u27e8http:\/\/sourceforge.net\/p\/procps-ng\/tickets\/\u27e9.\u00a0 This page was obtained
\nfrom the project’s upstream Git repository
\n(https:\/\/gitorious.org\/procps) on 2014-12-30.\u00a0 If you discover any
\nrendering problems in this HTML version of the page, or you believe
\nthere is a better or more up-to-date source for the page, or you have
\ncorrections or improvements to the information in this COLOPHON
\n(which is not part of the original manual page), send a mail to
\nman-pages@man7.org<\/p>\n
procps-ng\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 July 2014\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TOP(1)<\/p>\n","protected":false},"excerpt":{"rendered":"
TOP(1)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 User Commands\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TOP(1) NAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top top – display Linux processes SYNOPSIS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top top -hv|-bcHiOSs -d secs -n max -u|U user -p pid -o fld -w [cols] The traditional switches `-‘ and whitespace are optional. DESCRIPTION\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 top The top program provides a dynamic real-time view of a running system.\u00a0 It can display system summary information […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":"","footnotes":""},"categories":[8],"tags":[],"class_list":["post-367","post","type-post","status-publish","format-standard","hentry","category-shell"],"a3_pvc":{"activated":false,"total_views":0,"today_views":0},"_links":{"self":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts\/367","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=367"}],"version-history":[{"count":0,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts\/367\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=367"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=367"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}