summaryrefslogtreecommitdiffstats
path: root/system/xautolock/README
diff options
context:
space:
mode:
author Heinz Wiesinger2010-05-13 00:09:33 +0200
committer Heinz Wiesinger2010-05-13 00:09:33 +0200
commitdb56b0cdeba43fbcfbbd9c9bae001c9ea7660c89 (patch)
tree85ef7419c41282cb6087488f21c695f8d6d90dfb /system/xautolock/README
parent89411eb387153dd4bd1f8647fee4faa9f45d7c75 (diff)
downloadslackbuilds-db56b0cdeba43fbcfbbd9c9bae001c9ea7660c89.tar.gz
system/xautolock: Removed from 13.0 repository
Diffstat (limited to 'system/xautolock/README')
-rw-r--r--system/xautolock/README13
1 files changed, 0 insertions, 13 deletions
diff --git a/system/xautolock/README b/system/xautolock/README
deleted file mode 100644
index 39350e7475..0000000000
--- a/system/xautolock/README
+++ /dev/null
@@ -1,13 +0,0 @@
-Xautolock monitors console activity under the X window system, and
-fires up a program of your choice if nothing happens during a
-user configurable period of time. You can use this to automatically
-start up a screen locker in case you tend to forget to do so manually
-before having a coffee break.
-
-Xautolock will typically be used to lock the screen but it really
-doesn't care what program you make it start. The only real assumption
-made by xautolock is that a new countdown starts as soon as the
-locker exits.
-
-One suggested use of autolock is like this:
- xautolock -time 10 -locker xlock