Modified suckless software for use on OpenBSD systems
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Evan Burkey ba1e99cb9d Set repo for OpenBSD 3 months ago
..
components add slstatus 3 months ago
LICENSE add slstatus 3 months ago
Makefile add slstatus 3 months ago
README add slstatus 3 months ago
arg.h add slstatus 3 months ago
config.def.h add slstatus 3 months ago
config.h add slstatus 3 months ago
config.mk add slstatus 3 months ago
slstatus.1 add slstatus 3 months ago
slstatus.c add slstatus 3 months ago
slstatus.h add slstatus 3 months ago
util.c add slstatus 3 months ago
util.h add slstatus 3 months ago

README

slstatus - suckless status
==========================
slstatus is a suckless status monitor for window managers that use WM_NAME
(e.g. dwm) or stdin to fill the status bar.


Features
--------
- Battery percentage/state/time left
- CPU usage
- CPU frequency
- Custom shell commands
- Date and time
- Disk status (free storage, percentage, total storage and used storage)
- Available entropy
- Username/GID/UID
- Hostname
- IP address (IPv4 and IPv6)
- Kernel version
- Keyboard indicators
- Keymap
- Load average
- Network speeds (RX and TX)
- Number of files in a directory (hint: Maildir)
- Memory status (free memory, percentage, total memory and used memory)
- Swap status (free swap, percentage, total swap and used swap)
- Temperature
- Uptime
- Volume percentage
- WiFi signal percentage and ESSID


Requirements
------------
Currently slstatus works on FreeBSD, Linux and OpenBSD.
In order to build slstatus you need the Xlib header files.


Installation
------------
Edit config.mk to match your local setup (slstatus is installed into the
/usr/local namespace by default).

Afterwards enter the following command to build and install slstatus (if
necessary as root):

make clean install


Running slstatus
----------------
See the man page for details.


Configuration
-------------
slstatus can be customized by creating a custom config.h and (re)compiling the
source code. This keeps it fast, secure and simple.


Upcoming
--------

A release (v1.0) will come soon... ;)
After a long phase of inactivity, development has been continued!