xmtop/README.md at 5ada5315d940038fcd83777b1e73797bbbada108

LK/xmtop

Sean E. Russell 5ada5315d9 Fixes #92 , configurable temps; help text & docs clean-up; versions are now built into binaries at compile time; clean up old extensions params; adds --list command; adds --write-config command; fixes bug in colorscheme loading; fixes bug in Colorschemes -- all had empty Name attrs; adds ability to list devices.

2020-04-23 10:41:20 -05:00

11 KiB

Raw Blame History

Another terminal based graphical activity monitor, inspired by gtop and vtop, this time written in Go!

Join us in #gotop:matrix.org (matrix clients).

Installation

Working and tested on Linux, FreeBSD and MacOS. Windows binaries are provided, but have limited testing. OpenBSD works with some caveats; cross-compiling is difficult and binaries are not provided.

If you install gotop by hand, or you download or create new layouts or colorschemes, you will need to put the layout files where gotop can find them. To see the list of directories gotop looks for files, run gotop -h. The first directory is always the directory from which gotop is run.

Arch

AUR contains entries for gotop and gotop-bin. gotop-git still points at the old, unmaintained, repository for the moment.

yay -S gotop-bin

There is also a build-from-source package:

yay -S gotop

Gentoo

gotop is available on guru overlay. It's currently required to add this overlay in order to install gotop:

sudo layman -a guru
sudo emerge gotop

OSX

gotop can be installed with Homebrew; you'll need to tap the recipe. If you'd previously tapped cjbassi's recipe, you'll want to untap that first. The old version of gotop is also included in Homebrew's core library, and that will always be chosen before any taps, so you have to specify the tap specifically.

brew uninstall gotop        # If previously installed
brew untap cjbassi/gotop    # If previously tapped
brew tap xxxserxxx/gotop
brew install xxxserxxx/gotop/gotop

Prebuilt binaries

This doesn't require Go, is easy, and works across distributions. You have to manually upgrade the executable yourself, though, so using your distribution's package (if one is available) is a better approach.

Visit the releases page with your web browser and download the appropriate file for your OS and architecture. Unzip it (the archive contains a single file) and then move the resulting gotop binary into your $PATH somewhere. If you're on a Debian or Redhat derivative, you can download an .rpm or .deb and install that.

Source

This requires Go, and at the moment, Go 1.14 specifically.

go get -u github.com/xxxserxxx/gotop/cmd/gotop

If you don't have Go 1.14, you will want to follow the Building instructions in the next section.

Building

This is the download & compile approach.

gotop should build with most versions of Go. If you have a version other than 1.14 installed, remove the go line at the end of go.mod.

git clone https://github.com/xxxserxxx/gotop.git
cd gotop
sed -i '/^go/d' go.mod          # Do this if you have go != 1.14
go build -o gotop ./cmd/gotop

Move gotop to somewhere in your $PATH.

Usage

Keybinds

Quit: q or <C-c>
Process navigation:
- k and <Up>: up
- j and <Down>: down
- <C-u>: half page up
- <C-d>: half page down
- <C-b>: full page up
- <C-f>: full page down
- gg and <Home>: jump to top
- G and <End>: jump to bottom
Process actions:
- <Tab>: toggle process grouping
- dd: kill selected process or group of processes with SIGTERM
- d3: kill selected process or group of processes with SIGQUIT
- d9: kill selected process or group of processes with SIGKILL
Process sorting
- c: CPU
- m: Mem
- p: PID
Process filtering:
- /: start editing filter
- (while editing):
  - <Enter> accept filter
  - <C-c> and <Escape>: clear filter
CPU and Mem graph scaling:
- h: scale in
- l: scale out
?: toggles keybind help menu
b: toggles display of network traffic in mbps or TX (or RX) per second

Mouse

click to select process
mouse wheel to scroll through processes

Config file

Most command-line settings can be persisted into a configuration file. The config file is named gotop.conf and can be located in several places. The first place gotop will look is in the current directory; after this, the locations depend on the OS and distribution. On Linux using XDG, for instance, the home location of ~/.config/gotop/gotop.conf is the second location. The last location is a system-wide global location, such as /etc/gotop/gotop.conf. The -h help command will print out all of the locations, in order. Command-line options override values in any config files, and only the first config file found is loaded.

A configuration file can be created using the --write-config command-line argument. This will try to place the config file in the home config directory (the second location), but if it's unable to do so it'll write a file to the current directory.

Config file changes can be made by combining command-line arguments with --write-config. For example, to persist the solarized theme, call:

gotop -c solarized --write-config

Colorschemes

gotop ships with a few colorschemes which can be set with the -c flag followed by the name of one. You can find all the colorschemes in the colorschemes folder.

To make a custom colorscheme, check out the template for instructions and then use default.json as a starter. Then put the file at ~/.config/gotop/<name>.json and load it with gotop -c <name>. Colorschemes PR's are welcome!

To list all built-in color schemes, call:

gotop --list colorschemes

Layouts

gotop can parse and render layouts from a specification file. The format is
intentionally simple. The amount of nesting levels is limited. Some examples
are in the layouts directory; you can try each of these with, e.g.,
gotop --layout-file layouts/procs. If you stick your layouts in
$XDG_CONFIG_HOME/gotop, you can reference them on the command line with the
-l argument, e.g. gotop -l procs.

The syntax for each widget in a row is:

(rowspan:)?widget(/weight)?

and these are separated by spaces.

Each line is a row
Empty lines are skipped
Spaces are compressed (so you can do limited visual formatting)
Legal widget names are: cpu, disk, mem, temp, batt, net, procs
Widget names are not case sensitive
The simplest row is a single widget, by name, e.g. cpu
Weights
1. Widgets with no weights have a weight of 1.
2. If multiple widgets are put on a row with no weights, they will all have
  the same width.
3. Weights are integers
4. A widget will have a width proportional to its weight divided by the
  total weight count of the row. E.g.,
```
cpu      net
disk/2   mem/4
```
  The first row will have two widgets: the CPU and network widgets; each
  will be 50% of the total width wide. The second row will have two
  widgets: disk and memory; the first will be 2/6 ~= 33% wide, and the
  second will be 5/7 ~= 67% wide (or, memory will be twice as wide as disk).
If prefixed by a number and colon, the widget will span that number of
rows downward. E.g.
```
mem   2:cpu
net
```
Here, memory and network will be in the same row as CPU, one over the other,
and each half as high as CPU; it'll look like this:
```
 +------+------+
 | Mem  |      |
 +------+ CPU  |
 | Net  |      |
 +------+------+
```
Negative, 0, or non-integer weights will be recorded as "1". Same for row
spans.
Unrecognized widget names will cause the application to abort.
In rows with multi-row spanning widgets and weights, weights in
lower rows are ignored. Put the weight on the widgets in that row, not
in later (spanned) rows.
Widgets are filled in top down, left-to-right order.
The larges row span in a row defines the top-level row span; all smaller
row spans constitude sub-rows in the row. For example, cpu mem/3 net/5
means that net/5 will be 5 rows tall overall, and mem will compose 3 of
them. If following rows do not have enough widgets to fill the gaps,
spacers will be used.

Yes, you're clever enough to break the layout algorithm, but if you try to
build massive edifices, you're in for disappointment.

To list all built-in color schemes, call:

gotop --list layouts

Device filtering

Some devices have quite a number of data points; on OSX, for instance, there are dozens of temperature readings. These can be filtered through a configuration file. There is no command-line argument for this filter.

The list will grow, but for now the only device that supports filtering is the temperature widget. The configuration entry is called temperature, and it contains an exact-match list of comma-separated values with no spaces. To see the list of valid values, run gotop with the --list devices command. Gotop will print out the type of device and the legal values. For example, on Linux:

$ gotop --list devices
Temperatures:
        acpitz
        nvme_composite
        nvme_sensor1
        nvme_sensor2
        pch_cannonlake
        coretemp_packageid0
        coretemp_core0
        coretemp_core1
        coretemp_core2
        coretemp_core3
        ath10k_hwmon

You might then add the following line to the config file. First, find where gotop looks for config files:

$ gotop -h | tail -n 6
Colorschemes & layouts that are not built-in are searched for (in order) in:
/home/USER/workspace/gotop.d/gotop, /home/USER/.config/gotop, /etc/xdg/gotop
The first path in this list is always the cwd. The config file
'gotop.config' can also reside in one of these directories.

Log files are stored in /home/ser/.cache/gotop/errors.log

So you might use /home/YOU/.config/gotop.conf, and add (or modify) this line:

temperatures=acpitz,coretemp_core0,ath10k_hwmon

This will cause the temp widget to show only four of the eleven temps.

CLI Options

Run gotop -h to see the list of all command line options.

More screen shots

"-l battery"

"-l minimal"

Custom (layouts/procs)

Built With

History

The original author of gotop started a new tool in Rust, called ytop. This repository is a fork of original gotop project with a new maintainer.

11 KiB Raw Blame History