? xautolock - fire up programs in case of user inactivity under X   1 This man page applies to xautolock patchlevel 10.   A [-help] [-version] [-time mins] [-locker locker] [-notify margin] 4 [-notifier notifier] [-bell percent] [-corners xxxx]A [-cornerdelay secs] [-cornerredelay altsecs] [-cornersize pixels] E [-nocloseout] [-nocloseerr] [-noclose] [-disable] [-enable] [-toggle]   @ Xautolock monitors the user activity on an X Window display.  If= none is detected within mins minutes, a program is started as = specified by the -locker option.  Xautolock will typically be > used to lock the screen (hence its primary name) but it really> doesn't care what program you make it start.  For this reason,A xautolock does not interfere with the default screen saver.  This @ implies that it is the job of the locker to take the appropriate@ actions if the default screen saver is to be disabled.  The only@ real assumption made by xautolock is that a new countdown starts as soon as the locker exits.  ? In the presence of the -notify option, a warning signal will be : issued margin seconds before starting the locker.  Warning signals come in two kinds:  @     o You can use the -notifier option to specify the command to(       be issued to perform notification.  B     o Alternatively, you can let xautolock ring the bell.  In thisA       case, the -bell option specifies the loudness of the signal        in percent.   @ You can tell xautolock to take special actions when you move the@ mouse into one of the corners of the display and leave it there,7 by using the -corners, -cornerdelay, -cornerredelay and , -cornersize options.  This works as follows:  @ The xxxx argument to the -corners option must consist of exactlyA 4 characters from the following set:  '0', '+', '-'.  Each one of @ these specifies what xautolock should do when the mouse enters a? small square area located in each of the corners of the screen. A The corners are considered in the following order:  top left, top A right, bottom left, bottom right.  A '0' indicates that xautolock @ should ignore the corner.  A '+' indicates that xautolock shouldA start the locker after secs or altsecs seconds (see below for the ? difference between both), unless the mouse is moved or keyboard = input is received.  A '-' indicates that xautolock should not @ start the locker at all.  The pixels argument specifies the size in pixels of the corner areas.  = Most users of the -corners option want the locker to activate @ within a very short time interval after they move the mouse into? a '+' corner.  This can be achieved by specifying a small value 6 for the -cornerdelay option.  However, if the mouse is@ subsequently left where it is, xautolock will almost immediately? start a new locker right after the user quits the current one.  @ To prevent this from happening, the -cornerredelay option can be? used to specify the time-out interval to be used if and only if A the mouse is sitting in a `+' corner and has not been moved since  the previous locker exited.   > A running xautolock process can been also be disabled, in wich< case it will not attempt to start the locker.  To disable an? already running xautolock process, use the -disable option.  To A re-enable it, use -enable.  To toggle it between both states, use = -toggle.  Using this method is preferable to using sending it = SIGSTOP and SIGCONT signals, because while disabled xautolock ' will still be emptying its event queue.   A By default xautolock closes stdout and stderr.  This prevents the = locker from writing error messages to these files in case you = manually lock your display.  The -nocloseout, -nocloseerr and ; -noclose options cause xautolock to not close stdout and/or ; stderr.  On some platforms users of xnlock will need to use > -nocloseout, in order to make xnlock's witty sayings show up. ; These options can also be used for debugging cases in which $ locker invocation is not successful.  7 Xautolock is capable of managing multi-headed displays.   +     -help		Print a help message and exit.     2     -version		Print the version number and exit.    0     -time		Specifies the time-out interval.  The* 			default is 10 minutes, the minimum is 1& 			minute and the maximum is 1 hour.    2     -locker		Specifies the locker to be used.  The+ 			default is xlock.  Notice that if locker / 			contains several words, it must be specified - 			between quotes.  In order to use your PATH - 			to locate the program, xautolock feeds the - 			locker command to /bin/sh, so it should be ) 			understandable for whatever shell your + 			/bin/sh is.  Because this typically is a - 			Bourne shell, ~ expansion most likely will  			not work.    9     -notify		Warn the user margin seconds before locking. 0 			The default is to not warn the user.  If used& 			in conjunction with -cornerdelay or/ 			-cornerredelay, the notification margin used 2 			is the minimum of margin, secs and/or altsecs.   >     -notifier		Specifies the notifier to be used.  The default* 			is none.  This option is only useful in, 			conjunction with -notify.  Notice that if. 			notifier contains several words, it must be- 			specified between quotes.  In order to use - 			your PATH to locate the program, xautolock , 			feeds the notifier command to /bin/sh, so+ 			it should be understandable for whatever 1 			shell your /bin/sh is.  Because this typically . 			is a Bourne shell, ~ expansion 	most likely 			will not work.   5     -bell		Specifies the loudness of the notification 1 			signal in the absence of the -notifier option. 1 			The default is 40 percent. This option is only ' 			useful in conjunction with -notify.    9     -corners		Define special actions to be taken when the 2 			mouse enters one of the corners of the display.3 			The default is 0000, which means that no special  			action is taken.     ?     -cornerdelay	Specifies the number of seconds to wait before / 			reacting to the mouse entering a '+' corner.  			The default is 5 seconds.    A     -cornerredelay	Specifies the number of seconds to wait before 3 			reacting again if the current locker exits while - 			the mouse is sitting in a '+' corner.  The * 			default is for altsecs to equal secs.    ;     -cornersize		Specifies the size in pixels of the corner % 			areas.  The default is 10 pixels.    &     -nocloseout		Don't close stdout.    %     -nocloseerr		Don't close stderr.    0     -noclose		Close neither stdout nor stderr.    ;     -disable		Disables an already running xautolock process / 			(if there is one).  In any case, the current # 			invocation of xautolock exits.     9     -enable		Enables an already running xautolock process / 			(if there is one).  In any case, the current # 			invocation of xautolock exits.     9     -toggle		Toggles an already running xautolock process - 			(if there is one) between its disabled and , 			enabled modes of operation.  In any case,- 			the current invocation of xautolock exits.   @ Resources can be specified in your ~/.Xdefaults file, either for? class Xautolock, or for whatever name you renamed xautolock to. < This can be useful in case xautolock is to be used for other> purposes than simply locking the screen.  For example:  if you< have two copies of xautolock, one called "xmonitor", and one6 called "xlogout", then both will honour the following:        Xautolock.corners:  ++++   $ In addition, "xmonitor" will honour:        xmonitor.cornersize:  10    while "xlogout" will honour:        xlogout.cornersize:  5   @ Each command line option takes precedence over the corresponding default resource specification.   A If, when creating a window, an application waits for more than 30 = seconds before selecting KeyPress events on non-leaf windows, = xautolock may interfere with the event propagation mechanism. > This effect is theoretical and has never been observed in real@ life.  It can only occur in case xautolock has not been compiled? to support the Xidle extension or in case the X server does not  support Xidle.  > xautolock does not properly handle the secure keyboard mode of; terminal emulators like xterm, since that mode will prevent < xautolock from noticing the keyboard events occurring on the@ terminal. Therefore, xautolock sometimes thinks that there is noA keyboard activity while in reality there is.  This can only occur < in case xautolock has not been compiled to support the Xidle9 extension or in case the X server does not support Xidle.   ; xautolock does not check whether notifier and/or locker are 
 available.  4 The xautolock resources have dummy resource classes.  + X(1), xlock(1), xnlock(1), xscreensaver(1).   2 Copyright 1990, 1992-1995 by S.  De Troch and MCE.  @ Permission to use, copy, modify and distribute this software and; the supporting documentation without fee is hereby granted, A provided that Both the above copyright notice and this permission 8 notice appear in all copies of both the software and theB supporting documentation.  No financial profit is made out of it. A THE AUTHORS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, A INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS.  = IN NO EVENT SHALL THEY BE LIABLE FOR ANY SPECIAL, INDIRECT OR > CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM? LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, 9 NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN 8 CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.  5 Stefan De Troch detroch@imec.be Michel Eyckmans (MCE)  eyckmans@imec.be   Kris Croes croes@imec.be