bottom (btm) vs runit

bottom is a free graphical system and process monitor that runs in a terminal on Linux, macOS and Windows. It charts CPU use for each core and as an average, along with RAM and swap over time. Network and disk I/O are graphed too, with a control for zooming the displayed time interval. Its process widget lets users display, sort and search process information, use tree mode and send kill signals. Other widgets show disk capacity and use, temperature sensors and battery use. Appearance and behavior can be changed through command-line options or a configuration file, including themes, layout, widget behavior and filtering. An htop-inspired basic mode offers a simpler view, and a selected widget can be expanded to fill the terminal. A read-only option blocks actions that affect the system, such as stopping processes. Installation is documented through package managers, Cargo and pre-built release binaries. Official platform support covers macOS, Linux and Windows; architecture support varies by system. Android and some other systems may work unofficially with limited testing and support.

runit is a free Unix init scheme that supervises services and can replace sysvinit or other init schemes. It runs on GNU/Linux, BSD systems, MacOSX and Solaris, and can be adapted to other Unix operating systems. As process 1, it manages boot, normal operation and shutdown in three stages. The runsv component launches a service's run program and restarts it if it exits; an optional finish program and log service can also be used. The sv utility reports status and provides controls to start, stop, restart, pause or signal supervised services. For logs, svlogd can filter messages and write automatically rotated logs. The chpst utility changes process state and sets limits for resources such as memory, open files, process count, output size, core size and CPU time. runsvdir can start and monitor runsv processes for up to 1,000 service subdirectories. runit can supervise services alongside an existing init scheme without replacing it. The maker provides source and installation instructions, including manual installation without root access. Its documentation warns that UDP logging is unreliable and should be confined to private networks.