Use argv0 instead of passing "slock:" to die every time
No need for usage()
There are 2 arguments why -v and -h are broken:
1) if you are running off git, -v will show the last stable
release, effectively making this option useless.
people running stable versions leave open an attack surface
this way in case there are vulnerabilities found.
99% of the people are also using package managers to keep
their software up to date, instead of running $TOOL -v to
check how old it is.
2) -h is a sad excuse for not just looking at the manual page
(man 1 slock). Given we accept a post_lock_command, we can't
be as liberal and just intercept certain flags.
I changed the manpage to reflect this change.
Clarify config.def.h
Clear up the wording a bit and explain what failonclear means.
Simplify the oom-taming-function
There really is no need to source a defined variable from a linux
header. The OOM-rank ranges from -1000 to 1000, so we can safely
hardcode -1000, which is a sane thing to do given slock is suid and
we don't want to play around too much here anyway.
On another notice, let's not forget that this still is a shitty
heuristic. The OOM-killer still can kill us (thus I also changed
the wording in the error-message. We do not disable the OOM-killer,
we're just hiding.
Update license year
It actually was 2014 and not 2015.
Add myself to License
forgot that a while ago
update copyright year in -v output
add hint for suid to oom error message
error messages on grab failure
add option to run command after screen is locked
Don't change to failure colour on success
Slightly safer OOM killer disablement in linux
rework setting window color
consistently use () with sizeof
Option to not show failure color on clear