summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2026-02-13 23:06:30 +0200
committerPaul Buetow <paul@buetow.org>2026-02-13 23:06:30 +0200
commit8ce6aa0a181e123f156ef3d1b75d939f56757ac6 (patch)
tree4e89b84833f32c17ae8a8a2e1921d5b4967ecc66 /README.md
parent39fcaa7a69947ee45d445e3aab7b49ce868b9d9c (diff)
Fix core toggle off and add memory bars (key 2)
- Clear renderer every frame so toggling cores off shows single bar again - Add drawMemBar: RAM (dark grey/black) and Swap (grey/black) per host - Remove redrawBg; always clear before draw - README updates Co-authored-by: Cursor <cursoragent@cursor.com>
Diffstat (limited to 'README.md')
-rw-r--r--README.md16
1 files changed, 7 insertions, 9 deletions
diff --git a/README.md b/README.md
index c0f90dd..dbea91c 100644
--- a/README.md
+++ b/README.md
@@ -36,7 +36,7 @@ loadbars servername{01..50}.example.com --showcores 1
## Description
-Loadbars is a small script that can be used to observe CPU loads of several remote servers at once in real time. It connects with SSH (using SSH public/private key auth) to several servers at once and vizualizes all server CPUs and memory statistics right next each other (either summarized or each core separately). Loadbars is not a tool for collecting CPU loads and drawing graphs for later analysis. However, since such tools require a significant amount of time before producing results, Loadbars lets you observe the current state immediately. Loadbars does not remember or record any load information. It just shows the current CPU usages like top or vmstat does.
+Loadbars is a tool that can be used to observe CPU loads of several remote servers at once in real time. It connects with SSH (using SSH public/private key auth) to several servers at once and vizualizes all server CPUs and memory statistics right next each other (either summarized or each core separately). Loadbars is not a tool for collecting CPU loads and drawing graphs for later analysis. However, since such tools require a significant amount of time before producing results, Loadbars lets you observe the current state immediately. Loadbars does not remember or record any load information. It just shows the current CPU usages like top or vmstat does.
## Build and run
@@ -49,24 +49,22 @@ go build -o loadbars ./cmd/loadbars
Or use [mage](https://magefile.org): `mage build` (default), `mage test`, `mage install` (set `DESTDIR` for install path), `mage uninstall` / `mage deinstall`.
-Remote hosts need no Perl: the binary pipes `scripts/loadbars-remote.sh` over SSH.
+Remote hosts need no Go: the binary pipes `scripts/loadbars-remote.sh` over SSH.
## Installation
### Dependencies (Fedora/RHEL/CentOS)
-To run loadbars on Fedora Linux, you need to install the following packages:
+To run loadbars on Fedora Linux, you need the install the SDL2 development libraries:
```bash
-sudo dnf install perl perl-SDL perl-Alien-SDL perl-Proc-ProcessTable
+sudo dnf install SDL2-devel
```
-### Dependencies for Remote Hosts
-
-For monitoring remote servers via SSH, the remote hosts need:
+On Ubuntu/Debian:
```bash
-sudo dnf install perl-Time-HiRes
+sudo apt install libsdl2-dev
```
### Running from Source
@@ -138,4 +136,4 @@ The Go build of loadbars links to **go-sdl2** (github.com/veandco/go-sdl2), whic
## Author
-Paul Buetow - <http://buetow.org>
+Paul Buetow - <http://paul.buetow.org>