2017-08-10 20:49:37 +01:00
|
|
|
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
|
|
|
|
|
--------
|
2018-05-18 16:25:09 +01:00
|
|
|
- Battery percentage/state/time left
|
2017-08-10 20:49:37 +01:00
|
|
|
- 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
|
2017-08-14 17:00:46 +01:00
|
|
|
- IP address (IPv4 and IPv6)
|
2017-08-10 20:49:37 +01:00
|
|
|
- Kernel version
|
|
|
|
|
- Keyboard indicators
|
2018-05-23 10:50:08 +01:00
|
|
|
- Keymap
|
2017-08-10 20:49:37 +01:00
|
|
|
- Load average
|
2018-05-18 23:31:33 +01:00
|
|
|
- Network speeds (RX and TX)
|
2017-08-10 20:49:37 +01:00
|
|
|
- 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
|
2020-11-30 20:32:14 +00:00
|
|
|
- Volume percentage
|
2017-08-10 20:49:37 +01:00
|
|
|
- WiFi signal percentage and ESSID
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Requirements
|
|
|
|
|
------------
|
2019-02-16 16:05:04 +00:00
|
|
|
Currently slstatus works on FreeBSD, Linux and OpenBSD.
|
2018-03-26 17:09:30 +01:00
|
|
|
In order to build slstatus you need the Xlib header files.
|
2017-08-10 20:49:37 +01:00
|
|
|
|
2022-10-26 11:57:12 +01:00
|
|
|
For volume percentage on Linux the kernel module `snd-mixer-oss` must be
|
|
|
|
|
loaded.
|
|
|
|
|
|
2017-08-10 20:49:37 +01:00
|
|
|
|
|
|
|
|
Installation
|
|
|
|
|
------------
|
Revert component-split
this reverts the commits from 92ab9ef52ebcb097add97d9f78e67ad1c1d6a6ec up to
d42870d6ca7fb587b38f8cf6d6821ae33a53a696.
After heavy consideration, the component split has more disadvantages
than advantages, especially given there will be utility-functions
sharing quite a lot of code that would then need to be duplicated, as it
does not fit into the util.c due to its speciality.
One big advantage of the component-wise build is readability, and
without doubt, this was achieved here. This point will be addressed
with a different approach that will be visible in the upcoming commits.
One big disadvantage of the component build is the fact that it
introduces state to the build process which is not necessary. Before its
introduction, the only influencing factors where the system-defines
__linux__ and __OpenBSD__. With the components, we are also relying on
the output of uname(1).
Additionally, if the os.mk is not present, make gives the output
$ make
Makefile:5: os.mk: No such file or directory
make: *** No rule to make target 'os.mk'. Stop.
This could easily be fixed by providing some sort of meta-rule for this
file, however, it indicates the problem we have here, and this entire
statefulness will heavily complicate packaging of this tool and makes
the build process much more complex than it actually has to be.
2018-05-01 17:10:39 +01:00
|
|
|
Edit config.mk to match your local setup (slstatus is installed into the
|
2019-02-08 14:37:17 +00:00
|
|
|
/usr/local namespace by default).
|
2017-08-10 20:49:37 +01:00
|
|
|
|
2017-08-12 12:37:12 +01:00
|
|
|
Afterwards enter the following command to build and install slstatus (if
|
|
|
|
|
necessary as root):
|
2017-08-10 20:49:37 +01:00
|
|
|
|
|
|
|
|
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.
|
2018-03-18 21:51:51 +00:00
|
|
|
|
|
|
|
|
|
2020-11-30 20:32:14 +00:00
|
|
|
Upcoming
|
|
|
|
|
--------
|
|
|
|
|
|
|
|
|
|
A release (v1.0) will come soon... ;)
|
|
|
|
|
After a long phase of inactivity, development has been continued!
|
