Bottom

bottom #

A customizable cross-platform graphical process/system monitor for the terminal.
Supports Linux, macOS, and Windows. Inspired by gtop, gotop, and htop.

bottom demo

Table of contents #

Features #

As (yet another) process/system visualization and management application, bottom supports the typical features:

You can find more details in the documentation.

Support #

Official #

bottom officially supports the following operating systems and corresponding architectures:

  • macOS (x86_64, aarch64)
  • Linux (x86_64, i686, aarch64)
  • Windows (x86_64, i686)

These platforms are tested to work for the most part and issues on these platforms will be fixed if possible. Furthermore, binaries are expected to be built and tested using the most recent version of stable Rust.

For more details on supported platforms and known problems, check out the documentation.

Unofficial #

bottom may work on a number of platforms that aren’t officially supported. Note that unsupported platforms:

  • Might not be tested in CI to build or pass tests (see here for checked platforms).
  • Might not be properly tested by maintainers prior to a stable release.
  • May only receive limited support, such as missing features or bugs that may not be fixed.

Note that some unsupported platforms may eventually be officially supported (e.g., FreeBSD).

A non-comprehensive list of some currently unofficially supported platforms that may compile/work include:

  • FreeBSD (x86_64)
  • Linux (armv6, armv7, powerpc64le, riscv64gc)

For more details on unsupported platforms and known problems, check out the documentation.

Installation #

Cargo #

Installation via cargo can be done by installing the bottom crate:

# If required, update Rust to the stable channel first
rustup update stable

# Install
cargo install bottom --locked

# If you use another channel by default, you can specify the stable channel as such:
cargo +stable install bottom --locked

# --locked may be omitted if you wish to not used locked dependencies, though this may also cause problems:
cargo +stable install bottom

Arch Linux #

There is an official package that can be installed with pacman:

sudo pacman -S bottom

Debian/Ubuntu #

A .deb file is provided on each stable release and nightly builds for x86, aarch64, and armv7 (note stable ARM builds are only available for 0.6.8 and later). If you want to install this way, do something like:

# x86-64
curl -LO https://github.com/ClementTsang/bottom/releases/download/0.8.0/bottom_0.8.0_amd64.deb
sudo dpkg -i bottom_0.8.0_amd64.deb

# ARM64
curl -LO https://github.com/ClementTsang/bottom/releases/download/0.8.0/bottom_0.8.0_arm64.deb
sudo dpkg -i bottom_0.8.0_arm64.deb

# ARM
curl -LO https://github.com/ClementTsang/bottom/releases/download/0.8.0/bottom_0.8.0_armhf.deb
sudo dpkg -i bottom_0.8.0_armhf.deb

Snap #

bottom is available as a snap:

sudo snap install bottom

# To allow the program to run as intended
sudo snap connect bottom:mount-observe
sudo snap connect bottom:hardware-observe
sudo snap connect bottom:system-observe
sudo snap connect bottom:process-control

Fedora/CentOS #

Available in COPR:

sudo dnf copr enable atim/bottom -y
sudo dnf install bottom

Gentoo #

Available in the official Gentoo repo:

sudo emerge --ask sys-process/bottom

Nix #

nix-env -i bottom

Solus #

sudo eopkg it bottom

Void #

sudo xbps-install bottom

Homebrew #

brew install bottom

MacPorts #

sudo port selfupdate
sudo port install bottom

Scoop #

scoop install bottom

Chocolatey #

Chocolatey packages are located here.

choco install bottom

# The version number may need to be specified for newer releases for the first
# few hours/days during the approval process:
choco install bottom --version=0.8.0

winget #

The winget package can be found here:

winget install bottom

# Alternatively, to be more specific:
winget install Clement.bottom

You can uninstall via Control Panel, Options, or winget --uninstall bottom.

Windows installer #

You can also manually install bottom as a Windows program by going to the latest release and installing via the .msi file.

Manual installation #

There are a few ways to go about doing this manually. Note that you probably want to do so using the most recent version of stable Rust, which is how the binaries are built:

# If required, update Rust on the stable channel first
rustup update stable

# Option 1 - Download from releases and install
curl -LO https://github.com/ClementTsang/bottom/archive/0.8.0.tar.gz
tar -xzvf 0.8.0.tar.gz
cargo install --path .

# Option 2 - Clone from master and install manually
git clone https://github.com/ClementTsang/bottom
cd bottom
cargo install --path .

# Option 3 - Clone and install directly from the repo all via Cargo
cargo install --git https://github.com/ClementTsang/bottom

# You can also pass in the target-cpu=native flag for
# better CPU-specific optimizations. For example:
RUSTFLAGS="-C target-cpu=native" cargo install --path .

Binaries #

You can also try to use the generated release binaries and manually install on your system:

To use, download and extract the binary that matches your system and run by doing:

./btm

Auto-completion #

The release binaries are packaged with shell auto-completion files for bash, fish, zsh, and Powershell. To install them:

  • For bash, move btm.bash to $XDG_CONFIG_HOME/bash_completion or /etc/bash_completion.d/.
  • For fish, move btm.fish to $HOME/.config/fish/completions/.
  • For zsh, move _btm to one of your $fpath directories.
  • For PowerShell, add _btm.ps1 to your PowerShell profile.

The individual auto-completion files are also included in the stable/nightly releases as completion.tar.gz.

Usage #

You can run bottom using btm.

  • For help on flags, use btm -h for a quick overview or btm --help for more details.
  • For info on key and mouse bindings, press ? inside bottom or refer to the documentation.

You can find more information on usage in the documentation.

Configuration #

bottom accepts a number of command-line arguments to change the behaviour of the application as desired. Additionally, bottom will automatically generate a configuration file on the first launch, which one can change as appropriate.

More details on configuration can be found in the documentation.

Troubleshooting #

If some things aren’t working, give the troubleshooting page a look. If things still aren’t working, then consider opening a question or filing a bug report.

Contribution #

Whether it’s reporting bugs, suggesting features, maintaining packages, or submitting a PR, contribution is always welcome! Please read CONTRIBUTING.md for details on how to contribute to bottom.

Contributors #

Thanks to all contributors:

Marcin Wojnarowski
Marcin Wojnarowski

💻 📦
Mahmoud Al-Qudsi
Mahmoud Al-Qudsi

💻
Andy
Andy

💻
Kim Brose
Kim Brose

💻
Sven-Hendrik Haase
Sven-Hendrik Haase

📖
Artem Polishchuk
Artem Polishchuk

📦 📖
Trung Lê
Trung Lê

📦 🚇
dm9pZCAq
dm9pZCAq

📦 📖
Lukas Rysavy
Lukas Rysavy

💻
Erlend Hamberg
Erlend Hamberg

💻
Frederick Zhang
Frederick Zhang

💻
pvanheus
pvanheus

💻
Zeb Piasecki
Zeb Piasecki

💻
Brian Di Palma
Brian Di Palma

📖
Lasha Kanteladze
Lasha Kanteladze

📖
Herby Gillot
Herby Gillot

📖
Greg Brown
Greg Brown

💻
TotalCaesar659
TotalCaesar659

📖
George Rawlinson
George Rawlinson

📖 📦
adiabatic
adiabatic

📖
Randy Barlow
Randy Barlow

💻
Patrick Jackson
Patrick Jackson

🤔 📖
Mateusz Mikuła
Mateusz Mikuła

💻
Guillaume Gomez
Guillaume Gomez

💻
shura
shura

💻
Wesley Moore
Wesley Moore

💻
xgdgsc
xgdgsc

📖
ViridiCanis
ViridiCanis

💻
Justin Martin
Justin Martin

💻 📖
Diana
Diana

💻
Hervy Qurrotul Ainur Rozi
Hervy Qurrotul Ainur Rozi

📖
Mike Rivnak
Mike Rivnak

📖
lroobrou
lroobrou

💻
database64128
database64128

💻
Chon Sou
Chon Sou

💻
DrSheppard
DrSheppard

📖
Rareș Constantin
Rareș Constantin

💻
felipesuri
felipesuri

📖
spital
spital

💻
Michael Bikovitsky
Michael Bikovitsky

💻
Dmitry Valter
Dmitry Valter

💻
Twan Stok
Twan Stok

💻

Thanks #

  • This project is very much inspired by gotop, gtop, and htop.

  • This application was written with many, many libraries, and built on the work of many talented people. This application would be impossible without their work. I used to thank them all individually but the list got too large…

  • And of course, another round of thanks to all the contributors and package maintainers!