---

Heyho,

I wrote a patch to support running arbitrary commands after slock has
succesfully locked the screen. Mainly this is useful for suspending the system
after it has been locked like `slock s2ram`. If there are no objections, I will
merge it upstream.

--Markus


 slock.c | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/slock.c b/slock.c
index 6be8f22..b8d3d6e 100644
--- a/slock.c
+++ b/slock.c
@@ -289,7 +289,7 @@ lockscreen(Display *dpy, int screen)
 static void
 usage(void)
 {
-       fprintf(stderr, "usage: slock [-v]\n");
+       fprintf(stderr, "usage: slock [-v|POST_LOCK_CMD]\n");
        exit(1);
 }
 
@@ -303,7 +303,8 @@ main(int argc, char **argv) {
 
        if ((argc == 2) && !strcmp("-v", argv[1]))
                die("slock-%s, © 2006-2015 slock engineers\n", VERSION);
-       else if (argc != 1)
+
+       if ((argc == 2) && !strcmp("-h", argv[1]))
                usage();
 
 #ifdef __linux__
@@ -339,6 +340,13 @@ main(int argc, char **argv) {
                return 1;
        }
 
+       if (argc >= 2 && fork() == 0) {
+               if (dpy)
+                       close(ConnectionNumber(dpy));
+               execvp(argv[1], argv+1);
+               die("surf: execvp %s failed: %s\n", argv[1], strerror(errno));
+       }
+
        /* Everything is now blank. Now wait for the correct password. */
 #ifdef HAVE_BSD_AUTH
        readpw(dpy);
-- 
2.4.10


Reply via email to