137f0076c2
- Use file pointers instead of raw I/O, inspired by Kernel code. - Use OOM_SCORE_ADJ_MIN from linux/oom.h instead of working with magic values. - Stricter error checking and descriptive error messages. The reasoning for using the constant rather than magic values lies in the fact that this ensures people get the message. With "-1000", a code reviewer would question if that is really the lowest possible number or just an arbitrary value. The kernel ABI probably won't change, but even in the case, we wouldn't have to modify the code. The OOM killer only is guaranteed to not kill you if you have OOM_SCORE_ADJ_MIN. |
||
---|---|---|
LICENSE | ||
Makefile | ||
README | ||
arg.h | ||
config.def.h | ||
config.mk | ||
explicit_bzero.c | ||
slock.1 | ||
slock.c | ||
util.h |
README
slock - simple screen locker ============================ simple screen locker utility for X. Requirements ------------ In order to build slock you need the Xlib header files. Installation ------------ Edit config.mk to match your local setup (slock is installed into the /usr/local namespace by default). Afterwards enter the following command to build and install slock (if necessary as root): make clean install Running slock ------------- Simply invoke the 'slock' command. To get out of it, enter your password.