summaryrefslogtreecommitdiff
path: root/xtrlock.man
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2016-05-07 16:58:07 +0100
committerMatthew Vernon <matthew@debian.org>2016-05-21 19:03:35 +0100
commiteb50973552a62e49274cfeeddf31245739c8f47e (patch)
tree3a9579994403c216d446836eb6fb3835a1e013fc /xtrlock.man
parent7331fbf2792a5ace5fab0ff6cff4390e05a82961 (diff)
Add -f option, to fork after a successful locking.
This permits a chain of commands of the form 'xtrlock -f && suspend', where 'suspend' is whatever CLI command suspends your particular laptop environment, so that when you unsuspend you then have to unlock the xtrlock. Without this option, you have to run xtrlock in the background, and then either include a bodgy sleep to try to avoid the suspend command winning the race, or else find a way to test by some X-related means that the locking has happened. Signed-off-by: Simon Tatham <anakin@pobox.com>
Diffstat (limited to 'xtrlock.man')
-rw-r--r--xtrlock.man6
1 files changed, 5 insertions, 1 deletions
diff --git a/xtrlock.man b/xtrlock.man
index 7a869a6..e211bd5 100644
--- a/xtrlock.man
+++ b/xtrlock.man
@@ -2,7 +2,7 @@
.SH NAME
xtrlock \- Lock X display until password supplied, leaving windows visible
.SH SYNOPSIS
-.B xtrlock [-b]
+.B xtrlock [-b] [-f]
.SH DESCRIPTION
.B xtrlock
locks the X server till the user enters their password at the keyboard.
@@ -30,6 +30,10 @@ touching a key (Shift, for example) or the mouse.
.TP
\fB\-b\fR
blank the screen as well as displaying the padlock
+.TP
+\fB\-f\fR
+fork after locking is complete, and return success from the parent
+process
.SH X RESOURCES, CONFIGURATION
None.
.SH BUGS