Rivoreo Source Code Repositories
src.rivoreo.one / htop / 38fd1bfaba8b742d476a146ee111bf24cce9193e
commit38fd1bfaba8b742d476a146ee111bf24cce9193e[log] [download]
authorHisham Muhammad <hisham@gobolinux.org>Mon Mar 23 19:25:57 2015 -0300
committerHisham Muhammad <hisham@gobolinux.org>Mon Mar 23 19:25:57 2015 -0300
tree76891dde7030c461d625386c47e7320dd88a0217
parent7cb8cb05fbf005564c6eefe4fd6007ced9336a5f [diff]
Add a test plan.

A list of functionality to go through and test before releases.
1 file changed
tree: 76891dde7030c461d625386c47e7320dd88a0217
  1. .gitignore
  2. AUTHORS
  3. Action.c
  4. Action.h
  5. Affinity.c
  6. Affinity.h
  7. AffinityPanel.c
  8. AffinityPanel.h
  9. AvailableColumnsPanel.c
  10. AvailableColumnsPanel.h
  11. AvailableMetersPanel.c
  12. AvailableMetersPanel.h
  13. BatteryMeter.c
  14. BatteryMeter.h
  15. COPYING
  16. CPUMeter.c
  17. CPUMeter.h
  18. CRT.c
  19. CRT.h
  20. CategoriesPanel.c
  21. CategoriesPanel.h
  22. ChangeLog
  23. CheckItem.c
  24. CheckItem.h
  25. ClockMeter.c
  26. ClockMeter.h
  27. ColorsPanel.c
  28. ColorsPanel.h
  29. ColumnsPanel.c
  30. ColumnsPanel.h
  31. DisplayOptionsPanel.c
  32. DisplayOptionsPanel.h
  33. FunctionBar.c
  34. FunctionBar.h
  35. Hashtable.c
  36. Hashtable.h
  37. Header.c
  38. Header.h
  39. HostnameMeter.c
  40. HostnameMeter.h
  41. INSTALL
  42. IncSet.c
  43. IncSet.h
  44. ListItem.c
  45. ListItem.h
  46. LoadAverageMeter.c
  47. LoadAverageMeter.h
  48. MainPanel.c
  49. MainPanel.h
  50. Makefile.am
  51. MemoryMeter.c
  52. MemoryMeter.h
  53. Meter.c
  54. Meter.h
  55. MetersPanel.c
  56. MetersPanel.h
  57. NEWS
  58. Object.c
  59. Object.h
  60. OpenFilesScreen.c
  61. OpenFilesScreen.h
  62. Panel.c
  63. Panel.h
  64. Process.c
  65. Process.h
  66. ProcessList.c
  67. ProcessList.h
  68. README
  69. README.md ⇨ README
  70. RichString.c
  71. RichString.h
  72. ScreenManager.c
  73. ScreenManager.h
  74. Settings.c
  75. Settings.h
  76. SignalsPanel.c
  77. SignalsPanel.h
  78. String.c
  79. String.h
  80. SwapMeter.c
  81. SwapMeter.h
  82. TESTPLAN
  83. TasksMeter.c
  84. TasksMeter.h
  85. TraceScreen.c
  86. TraceScreen.h
  87. UptimeMeter.c
  88. UptimeMeter.h
  89. UsersTable.c
  90. UsersTable.h
  91. Vector.c
  92. Vector.h
  93. autogen.sh
  94. configure.ac
  95. freebsd/
  96. htop.1.in
  97. htop.c
  98. htop.desktop
  99. htop.h
  100. htop.png
  101. linux/
  102. m4/
  103. scripts/
  104. unsupported/
README.md

htop

by Hisham Muhammad hisham@gobolinux.org

May, 2004 - January, 2014

Note

Alert Mac users, click here! The htop version you are using is a 5-year old fork -- help bring htop 1.x to the Mac!

Introduction

This is htop, an interactive process viewer. It requires ncurses. It is tested with Linux 2.6, but is also reported to work (and was originally developed) with the 2.4 series.

Note that, while, htop is Linux specific -- it is based on the Linux /proc filesystem -- it is also reported to work with FreeBSD systems featuring a Linux-compatible /proc. This is, however, unsupported. Contact the packager for your system when reporting problems on platforms other than Linux.

This software has evolved considerably during the last years, and is reasonably complete, but there is still room for improvement. Read the TODO file to see what's known to be missing.

Comparison between ‘htop’ and ‘top’

  • In ‘htop’ you can scroll the list vertically and horizontally to see all processes and full command lines.
  • In ‘top’ you are subject to a delay for each unassigned key you press (especially annoying when multi-key escape sequences are triggered by accident).
  • ‘htop’ starts faster (‘top’ seems to collect data for a while before displaying anything).
  • In ‘htop’ you don't need to type the process number to kill a process, in ‘top’ you do.
  • In ‘htop’ you don't need to type the process number or the priority value to renice a process, in ‘top’ you do.
  • In ‘htop’ you can kill multiple processes at once.
  • ‘top’ is older, hence, more tested.

Compilation instructions

This program is distributed as a standard autotools-based package. See the INSTALL file for detailed instructions, but you are probably used to the common ./configure/make/make install routine.

When fetching the code from the development repository, you need to run the ./autogen.sh script, which in turn requires autotools to be installed.

See the manual page (man htop) or the on-line help (‘F1’ or ‘h’ inside htop) for a list of supported key commands.

if not all keys work check your curses configuration.