1 XScreenSaver(1) XScreenSaver(1) NNAAMMEE xscreensaver - graphics hack and screen locker, launched when the user is idle SSYYNNOOPPSSIISS xxssccrreeeennssaavveerr [-display _h_o_s_t_:_d_i_s_p_l_a_y_._s_c_r_e_e_n] [-timeout _i_n_t] [-cycle _i_n_t] [-nice _i_n_t] [-lock] [-no-lock] [-lock-timeout _i_n_t] [-demo] [-visual _v_i_s_u_a_l] [-install] [-no-install] [-verbose] [-silent] [-xidle-extension] [-no-xidle-exten- sion] [-sgi-extension] [-no-sgi-extension] [-mit-exten- sion] [-no-mit-extension] [-xrm _r_e_s_o_u_r_c_e_s] DDEESSCCRRIIPPTTIIOONN The _x_s_c_r_e_e_n_s_a_v_e_r program waits until the keyboard and mouse have been idle for a period, and then runs a graph- ics demo chosen at random. It turns off as soon as there is any mouse or keyboard activity. This program can lock your terminal in order to prevent others from using it, though its default mode of operation is merely to display pretty pictures on your screen when it is not in use. The benefit that this program has over the combination of the xxlloocckk(1) and xxaauuttoolloocckk(1) programs is the ease with which new graphics hacks can be installed. You don't need to recompile (or even re-run) this program to add a new display mode. OOPPTTIIOONNSS _x_s_c_r_e_e_n_s_a_v_e_r accepts the following command line options: --ttiimmeeoouutt _m_i_n_u_t_e_s The screensaver will activate after the keyboard and mouse have been idle for this many minutes. Default 10. --ccyyccllee _m_i_n_u_t_e_s After the screensaver has been running for this many minutes, the currently running graphics hack sub-process will be killed (with SSIIGGTTEERRMM), and a new one started. If this is 0, then the graphics hack will not be changed: only one demo will run until the screensaver is deactivated by user activity. Default 10. --nniiccee _i_n_t_e_g_e_r The sub-processes created by _x_s_c_r_e_e_n_s_a_v_e_r will be ``niced'' to this level, so that they are given lower priority than other processes on the system, and don't increase the load unnecessarily. The default is 20. (Higher numbers mean lower priority; see nniiccee(1) X Version 11 31-May-97 1 XScreenSaver(1) XScreenSaver(1) for details.) --lloocckk Enable locking: before the screensaver will turn off, it requires you to type the password of the person who launched the screensaver, or the root password. (Note: this doesn't work if the screen- saver is launched by xxddmm(1) because it can't know the user-id of the logged-in user.) --nnoo--lloocckk Disable locking. This is the default. --lloocckk--ttiimmeeoouutt _m_i_n_u_t_e_s This is how long after the screensaver activates that locking is enabled. For example, if this is 5, and _-_t_i_m_e_o_u_t is 10, then after 10 minutes, the screen would blank. If there was user activity at 12 minutes, no password would be required. But, if there was user activity at 15 minutes or later (_-_l_o_c_k_-_t_i_m_e_o_u_t minutes after activation) then a password would be required. The default is 0, meaning that if locking is enabled, then a pass- word will be required as soon as the screensaver activates. --ddeemmoo Enter the interactive demo mode immediately after startup. Normally demo mode is invoked via the xxssccrreeeennssaavveerr--ccoommmmaanndd(1) program, but this is a shortcut for new users. See below for a descrip- tion of how demo-mode works. --vviissuuaall _v_i_s_u_a_l Specify which X visual to use by default. Legal values are: ddeeffaauulltt Use the screen's default visual (the visual of the root window.) This is the default. bbeesstt Use the visual which supports the most colors. Note, however, that the visual with the most colors might be a TrueColor visual, which does not support colormap animation. mmoonnoo Use a monochrome visual, if there is one. ggrraayy Use a grayscale or staticgray visual, if there is one and it has more than one plane (that is, it's not monochrome.) ccoolloorr Use the best of the color visuals, if there are any. X Version 11 31-May-97 2 XScreenSaver(1) XScreenSaver(1) _c_l_a_s_s where _c_l_a_s_s is one of SSttaattiiccGGrraayy, SSttaattiiccCCoolloorr, TTrruueeCCoolloorr, GGrraayySSccaallee, PPsseeuuddooCCoolloorr, or DDiirreeccttCCoolloorr. Selects the deepest visual of the given class. _n_u_m_b_e_r where _n_u_m_b_e_r (decimal or hex) is inter- preted as a visual id number, as reported by the xxddppyyiinnffoo(1) program; in this way you can have finer control over exactly which visual gets used, for example, to select a shallower one than would other- wise have been chosen. Note that this option specifies only the _d_e_f_a_u_l_t visual that will be used: the visual used may be overridden on a program-by-program basis. See the description of the pprrooggrraammss resource, below. --iinnssttaallll When using a non-default visual, install a private colormap while the screensaver is active, so that the graphics hacks can get as many colors as pos- sible. This is the default. (This only applies when the screen's default visual is being used, since non-default visuals get their own colormaps automatically.) --nnoo--iinnssttaallll Use the default colormap. --vveerrbboossee Print diagnostics. --ssiilleenntt --xxiiddllee--eexxtteennssiioonn Use the XXIIDDLLEE server extension to decide whether the user is idle. This is the default if _x_s_c_r_e_e_n_- _s_a_v_e_r has been compiled with support for this extension. On X11R4 or X11R5 systems, the XIdle method is faster and more reliable than what will be done otherwise, so use it if you can. --nnoo--xxiiddllee--eexxtteennssiioonn Don't use the XXIIDDLLEE server extension. --ssggii--eexxtteennssiioonn Use the SGI SSCCRREEEENN__SSAAVVEERR server extension to decide whether the user is idle. This is the default if _x_s_c_r_e_e_n_s_a_v_e_r has been compiled with support for this extension (which is the default on SGI systems.). If it is available, the X Version 11 31-May-97 3 XScreenSaver(1) XScreenSaver(1) SSCCRREEEENN__SSAAVVEERR method is faster and more reliable than what will be done otherwise, so use it if you can. --nnoo--ssggii--eexxtteennssiioonn Don't use the SGI SSCCRREEEENN__SSAAVVEERR server extension. --mmiitt--eexxtteennssiioonn Use the MMIITT--SSCCRREEEENN--SSAAVVEERR server extension to decide whether the user is idle. This is the default if _x_s_c_r_e_e_n_s_a_v_e_r has been compiled with support for this extension. However, this exten- sion is flaky, so it's use is not really recom- mended. (It also makes the _f_a_d_e option not work properly.) --nnoo--mmiitt--eexxtteennssiioonn Don't use the MMIITT--SSCCRREEEENN--SSAAVVEERR server extension. XX RREESSOOUURRCCEESS _x_s_c_r_e_e_n_s_a_v_e_r understands the following resources: ttiimmeeoouutt (class TTiimmee) Same as the _-_t_i_m_e_o_u_t command-line option. Default 10 minutes. ccyyccllee (class TTiimmee) Same as the _-_c_y_c_l_e command-line option. Default 10 minutes. nniiccee (class NNiiccee) Same as the _-_n_i_c_e command-line option. Default 10. lloocckk (class BBoooolleeaann) Same as the _-_l_o_c_k command-line option. lloocckkTTiimmeeoouutt (class TTiimmee) Same as the _-_l_o_c_k_-_t_i_m_e_o_u_t command-line option. ppaasssswwddTTiimmeeoouutt (class TTiimmee) If the screen is locked, then this is how many seconds the password dialog box should be left on the screen before giving up (default 30.) This should not be too large: the X server is grabbed for the duration that the password dialog box is up (for security purposes) and leaving the server grabbed for too long can cause problems. vveerrbboossee (class BBoooolleeaann) Same as the _-_v_e_r_b_o_s_e command-line option. X Version 11 31-May-97 4 XScreenSaver(1) XScreenSaver(1) xxiiddllee (class BBoooolleeaann) Same as the _-_x_i_d_l_e command-line option. ffaaddee (class BBoooolleeaann) If this is true, then when the screensaver acti- vates, the current contents of the screen will fade to black instead of simply winking out. This only works on displays with writable colormaps, that is, if the screen's default visual is a Pseu- doColor visual. Default true. A fade will also be done when switching graphics hacks (when the _c_y_c_l_e timer expires.) uunnffaaddee (class BBoooolleeaann) If this is true, then when the screensaver deacti- vates, the original contents of the screen will fade in from black instead of appearing immedi- ately. This only works on displays with writable colormaps, and if _f_a_d_e is true as well. Default false. ffaaddeeSSeeccoonnddss (class TTiimmee) If _f_a_d_e is true, this is how long the fade will be in seconds (default 3.) ffaaddeeTTiicckkss (class IInntteeggeerr) If _f_a_d_e is true, this is how many times a second the colormap will be changed to effect a fade. Higher numbers yield smoother fades, but may make the fades take longer than the specified _f_a_d_e_S_e_c_- _o_n_d_s if your server isn't fast enough to keep up. Default 20. vviissuuaallIIDD (class VViissuuaallIIDD) Same as the _-_v_i_s_u_a_l command-line option. Default ddeeffaauulltt. iinnssttaallllCCoolloorrmmaapp (class BBoooolleeaann) Same as the _-_i_n_s_t_a_l_l command-line option. Default true. ccaappttuurreeSSttddeerrrr (class BBoooolleeaann) Whether _x_s_c_r_e_e_n_s_a_v_e_r should redirect its standard- error stream to the window itself. Since its nature is to take over the screen, you would not normally see error messages generated by the screensaver or the programs it runs; this resource will cause the output of all relevant programs to be drawn on the screensaver window itself instead of written to the controlling terminal of the screensaver driver process. Default true. ccaappttuurreeSSttddoouutt (class BBoooolleeaann) Like ccaappttuurreeSSttddeerrrr but for the standard-output X Version 11 31-May-97 5 XScreenSaver(1) XScreenSaver(1) stream. Default true. ffoonntt (class FFoonntt) The font used for the stdout/stderr text, if ccaapp-- ttuurreeSSttddoouutt or ccaappttuurreeSSttddeerrrr are true. Default **--mmeeddiiuumm--rr--**--114400--**--mm--** (a 14 point fixed-width font.) tteexxttFFoorreeggrroouunndd (class FFoorreeggrroouunndd) The foreground color used for the stdout/stderr text, if ccaappttuurreeSSttddoouutt or ccaappttuurreeSSttddeerrrr are true. Default: Yellow. tteexxttBBaacckkggrroouunndd (class BBaacckkggrroouunndd) The background color used for the stdout/stderr text, if ccaappttuurreeSSttddoouutt or ccaappttuurreeSSttddeerrrr are true. Default: Black. pprrooggrraammss (class PPrrooggrraammss) The graphics hacks which _x_s_c_r_e_e_n_s_a_v_e_r runs when the user is idle. The value of this resource is a string, one _s_h-syntax command per line. Each line must contain exactly one command -- no semicolons, no ampersands. When the screensaver starts up, one of these is selected at random, and run. After the _c_y_c_l_e period expires, it is killed, and another is selected and run. If the value of this resource is empty, then no programs will be run; the screen will simply be made black. If the display has multiple screens, then a dif- ferent program will be run for each screen. Note that you must escape the newlines; here is an example of how you might set this in your _._X_d_e_- _f_a_u_l_t_s file: xscreensaver.programs: \ qix -root \n\ ico -r -faces -sleep 1 -obj ico \n\ xdaliclock -builtin2 -root \n\ xv -root -rmode 5 image.gif -quit \n To use a program as a screensaver, two things are required: that that program draw on the root win- dow (or be able to be configured to draw on the root window); and that that program understand ``virtual root'' windows, as used by virtual win- dow managers such as _t_v_t_w_m. (Generally, this is accomplished by just including the _"_v_r_o_o_t_._h_" X Version 11 31-May-97 6 XScreenSaver(1) XScreenSaver(1) header file in the program's source.) If there are some programs that you want to run only when using a color display, and others that you want to run only when using a monochrome dis- play, you can specify that like this: mono: mono-program -root \n\ color: color-program -root \n\ More generally, you can specify the kind of visual that should be used for the window on which the program will be drawing. For example, if one pro- gram works best if it has a colormap, but another works best if it has a 24-bit visual, both can be accomidated: PseudoColor: cmap-program -root \n\ TrueColor: 24bit-program -root \n\ (This sort of thing used to be accomplished with the _c_o_l_o_r_P_r_o_g_r_a_m_s and _m_o_n_o_P_r_o_g_r_a_m_s resources, but those resources have now been removed; a warning will be issued if they are used.) If you specify a particular visual for a program, and that visual does not exist on the screen, then that program will not be chosen to run. This means that on displays with multiple screens of different depths, you can arrange for appropriate hacks to be run on each. For example, if one screen is color and the other is monochrome, hacks that look good in mono can be run on one, and hacks that only look good in color will show up on the other. Normally you won't need to change the following resources: bboouurrnneeSShheellll (class BBoouurrnneeSShheellll) The pathname of the shell that _x_s_c_r_e_e_n_s_a_v_e_r uses to start subprocesses. This must be whatever your local variant of //bbiinn//sshh is -- in particular, it must not be ccsshh. wwiinnddoowwCCrreeaattiioonnTTiimmeeoouutt (class TTiimmee) When server extensions are not in use, this con- trols the delay between when windows are created and when _x_s_c_r_e_e_n_s_a_v_e_r selects events on them. Default 30 seconds. ppooiinntteerrPPoollllTTiimmee (class TTiimmee) When server extensions are not in use, this con- trols how frequently _x_s_c_r_e_e_n_s_a_v_e_r checks to see if X Version 11 31-May-97 7 XScreenSaver(1) XScreenSaver(1) the mouse position or buttons have changed. Default 5 seconds. iinniittiiaallDDeellaayy (class TTiimmee) When server extensions are not in use, _x_s_c_r_e_e_n_- _s_a_v_e_r will wait this many seconds before selecting events on existing windows, under the assumption that _x_s_c_r_e_e_n_s_a_v_e_r is started during your login procedure, and the window state may be in flux. Default 30 seconds. oovveerrllaayySSttddeerrrr (class BBoooolleeaann) If ccaappttuurreeSSttddeerrrr or ccaappttuurreeSSttddoouutt are True, and your server supports ``overlay'' visuals, then the text will be written into one of the higher layers instead of into the same layer as the running screenhack. Set this to False to disable that (though you shouldn't need to.) HHOOWW IITT WWOORRKKSS When it is time to activate the screensaver, a full-screen black window is created on each screen of the display. The window or windows is given the appropriate properties so that, to any subsequently-created programs, it will appear to be a ``virtual root'' window. Because of this, any program which draws on the root window (and which understands virtual roots) can be used as a screensaver. When the user becomes active again, the screensaver win- dows are unmapped and the running subprocesses are killed by sending them SSIIGGTTEERRMM. This is also how the subpro- cesses are killed when the screensaver decides that it's time to run a different demo: the old one is killed and a new one is launched. Before launching a subprocess, _x_s_c_r_e_e_n_s_a_v_e_r stores an appropriate value for $$DDIISSPPLLAAYY in the environment that the child will recieve. (This is so that if you start _x_s_c_r_e_e_n_s_a_v_e_r with a _-_d_i_s_p_l_a_y argument, the programs which _x_s_c_r_e_e_n_s_a_v_e_r launches will draw on the same display; and so that the child will end up drawing on the appropriate screen of a multi-headed display.) When the screensaver turns off, or is killed, care is taken to restore the ``real'' virtual root window if there is one. Because of this, it is important that you not kill the screensaver process with _k_i_l_l _-_9 if you are run- ning a virtual-root window manager. If you kill it with -9, you may need to restart your window manager to repair the damage. This isn't an issue if you aren't running a virtual-root window manager. For all the gory details, see the commentary at the top of xscreensaver.c. X Version 11 31-May-97 8 XScreenSaver(1) XScreenSaver(1) You can control a running screensaver process by using the xxssccrreeeennssaavveerr--ccoommmmaanndd(1) program (which see.) UUSSIINNGG XXDDMM((11)) You can run _x_s_c_r_e_e_n_s_a_v_e_r from your xdm session, so that the screensaver will run even when nobody is logged in on the console. Simply add ""xxssccrreeeennssaavveerr &&"" to your _/_u_s_r_/_l_i_b_/_X_1_1_/_x_d_m_/_X_s_e_t_u_p file. Because _x_d_m grabs the key- board, keypresses will not make the screensaver deacti- vate, but any mouse activity will. (If your system does not seem to be executing the _X_s_e_t_u_p file, you may need to configure it to do so -- the tradi- tional way to do this is to make that file the value of the _D_i_s_p_l_a_y_M_a_n_a_g_e_r_*_s_e_t_u_p resource in the _x_d_m_-_c_o_n_f_i_g file. See the man page for xxddmm(1) for more details.) Users may want to add ""xxssccrreeeennssaavveerr--ccoommmmaanndd --rreessttaarrtt"" to their startup scripts, so that the screensaver will be reinitialized with their private resource settings when they log in. It is safe to run this program as root (as _x_d_m is likely to do.) If run as root, _x_s_c_r_e_e_n_s_a_v_e_r changes its effec- tive user and group ids to something safe (like _"_n_o_b_o_d_y_") before connecting to the X server or launching user-speci- fied programs. Locking doesn't work if the screensaver is launched by _x_d_m. To get around this, you can run the screensaver from _x_d_m without locking, and kill and restart it from your personal X startup script to enable locking; for example: xscreensaver-command -exit ; xscreensaver DDEEMMOO MMOODDEE If _x_s_c_r_e_e_n_s_a_v_e_r receives the DDEEMMOO ClientMessage, which is done by running the xxssccrreeeennssaavveerr--ccoommmmaanndd program with the --ddeemmoo option, the screensaver will black the screen and pop up a dialog box from which you can examine and experi- ment with the client programs. The dialog box contains a scrolling list, a text field, and a number of buttons. Double-clicking on one of the programs in the list will run it. Clicking the mouse again will bring the dialog box back. Single-clicking in the list will place the indicated pro- gram and its args in the text field to be edited. Edit the arguments and hit return to run the program with the parameters you have specified. (Note that these are one- X Version 11 31-May-97 9 XScreenSaver(1) XScreenSaver(1) time changes and won't be remembered; to make the changes permanent, you need to edit your X resource file.) The buttons are: RRuunn NNeexxtt Clicking this button will run the next program in the list after the currently-selected one, and will scroll around to the top when it reaches the bottom. RRuunn PPrreevviioouuss Opposite of Run Next; at the top, it scrolls around to the bottom. EEddiitt PPaarraammeetteerrss This pops up a second dialog box, in which you have the option to interactively change most of the screensaver's operational parameters, such as its timeouts, and whether it should lock the screen. Changing these parameters here will affect only the running _x_s_c_r_e_e_n_s_a_v_e_r process; to make the changes permanent, you need to edit your X resource file. EExxiitt DDeemmoo MMooddee Returns to normal screensaver operation. RReeiinniittiiaalliizzee This causes the X resource database to be re-read, to pick up any changes you might have made. This works by causing the screensaver process to exit and then restart itself with the same command-line arguments. This is just like the _-_r_e_s_t_a_r_t argu- ment to xxssccrreeeennssaavveerr--ccoommmmaanndd(1) except that when executed from this button, the screensaver will automatically return to demo mode after restart- ing. BBUUGGSS (This is not a bug, but) note that as of release 1.32, the ccoolloorrPPrrooggrraammss and mmoonnooPPrrooggrraammss resources are no longer used: they have been supplanted by the extended syntax of the pprrooggrraammss resource (see above.) Extensions If you are not making use of one of the server extensions (XXIIDDLLEE, SSCCRREEEENN__SSAAVVEERR, or MMIITT--SSCCRREEEENN-- SSAAVVEERR), then it is possible, in rare situations, for _x_s_c_r_e_e_n_s_a_v_e_r to interfere with event propaga- tion and make another X program malfunction. For this to occur, that other application would need to _n_o_t select KKeeyyPPrreessss events on its non-leaf win- dows within the first 30 seconds of their X Version 11 31-May-97 10 XScreenSaver(1) XScreenSaver(1) existence, but then select for them later. In this case, that client _m_i_g_h_t fail to receive those events. This isn't very likely, since programs generally select a constant set of events immedi- ately after creating their windows and then don't change them, but this is the reason that it's a good idea to install and use one of the server extensions instead, to work around this shortcom- ing in the X protocol. Machine Load Although this program ``nices'' the subprocesses that it starts, graphics-intensive subprograms can still overload the machine by causing the X server process itself (which is not ``niced'') to suck a lot of cycles. Care should be taken to slow down programs intended for use as screensavers by inserting strategic calls to sslleeeepp(3) or uusslleeeepp(3) (or making liberal use of any _-_d_e_l_a_y options which the programs may provide.) Also, an active screensaver will cause your X server to be pretty much permanently swapped in; but the same is true of any program that draws periodically, like xxcclloocckk(1) or xxllooaadd(1). Latency and Responsiveness If the subprocess is drawing too quickly and the connection to the X server is a slow one (such as an X terminal running over a phone line) then the screensaver might not turn off right away when the user becomes active again (the iiccoo(1) demo has this problem if being run in full-speed mode). This can be alleviated by inserting strategic calls to XXSSyynncc(3) in code intended for use as a screensaver. This prevents too much graphics activity from being buffered up. Locking and XDM Locking doesn't work if the screensaver is launched by _x_d_m. The reason for this is that when it is launched by _x_d_m, the screensaver process is owned by some standard user id (such as _r_o_o_t or _d_a_e_m_o_n) instead of the user who is logged in on the console: because the screensaver was started _b_e_f_o_r_e anyone was logged in. In order for the screensaver to prompt for the password of the per- son who had logged in from _x_d_m, it would need to know who that user was, and there is no reliable and safe way to figure that out. (And even if there was, there would be some other security issues here as well.) So if you want to use it as a locker, you must X Version 11 31-May-97 11 XScreenSaver(1) XScreenSaver(1) start it with your user id. If it has already been started by _x_d_m, you can kill it with xxssccrreeeenn-- ssaavveerr--ccoommmmaanndd --eexxiitt, and then start it again as you. Passwords If you get an error message like ``couldn't get password of _u_s_e_r'' then this probably means that you're on a system in which the ggeettppwweenntt(3) library routine can only be effectively used by root. If this is the case, then _x_s_c_r_e_e_n_s_a_v_e_r must be installed as setuid to root. Care has been taken to make this a safe thing to do. It also may mean that your system uses shadow passwords instead of the standard _g_e_t_p_w_e_n_t inter- face; in that case, you may need to change some options in _c_o_n_f_i_g_._h and recompile. TWM and Colormaps The iinnssttaallllCCoolloorrmmaapp option doesn't work very well with the ttwwmm(1) window manager and its descen- dants. There is a race condition between the screensaver and this window manager, which can result in the screensaver's colormap not getting installed prop- erly, meaning the graphics hacks will appear in essentially random colors. (If the screen goes white instead of black, this is probably why.) The mmwwmm(1) and oollwwmm(1) window managers don't seem to have this problem. The race condition exists because X apparently does not provide a way for an OverrideRedirect window to have its own colormap, short of grabbing the server (which is neither a good idea, nor really possible with the current design.) What happens is that, as soon as the screensaver installs its colormap, ttwwmm responds to the CCoolloorrmmaappNNoottiiffyy event that is generated by re- instaling the default colormap. Apparently, ttwwmm doesn't _a_l_w_a_y_s do this; it seems to do it regu- larly if the screensaver is activated from a menu item, but seems to not do it if the screensaver comes on of its own volition, or is activated from another console. Any thoughts on this problem are welcome... XView Clients Apparently there are some problems with XView pro- grams getting confused and thinking that the screensaver window is the real root window even when the screensaver is not active: ClientMessages intended for the window manager are sent to the X Version 11 31-May-97 12 XScreenSaver(1) XScreenSaver(1) screensaver window instead. This could be solved by making xscreensaver forward all unrecognised ClientMessages to the real root window, but there may be other problems as well. If anyone has any insight on the cause of this problem, please let me know. MIT Extension and Fading When using the MMIITT--SSCCRREEEENN--SSAAVVEERR extension in con- junction with the ffaaddee option, you may notice an unattractive flicker just before the fade begins. This is because the server maps a black window just before it tells the _x_s_c_r_e_e_n_s_a_v_e_r process to activate. The _x_s_c_r_e_e_n_s_a_v_e_r process immediately unmaps that window, but this results in a flicker. I haven't figured a way to get around this; it seems to be a fundamental property of the (mis-) design of this server extension. LessTif (Motif Clone) Rumor has it that demo mode is buggy if XScreen- Saver was compiled with the GNU LessTif reimple- mentation of Motif. Since it works fine with OSF Motif on a variety of systems, I assume these problems are due to bugs in LessTif. Again, any insight would be appreciated. Red Hot Lava There need to be a lot more graphics hacks. In particular, there should be a simulation of a Lavalite (tm). EENNVVIIRROONNMMEENNTT DDIISSPPLLAAYY to get the default host and display number, and to inform the sub-programs of the screen on which to draw. XXEENNVVIIRROONNMMEENNTT to get the name of a resource file that overrides the global resources stored in the RESOURCE_MAN- AGER property. UUPPGGRRAADDEESS The latest version can always be found at http://peo- ple.netscape.com/jwz/xscreensaver/ SSEEEE AALLSSOO XX(1), xxssccrreeeennssaavveerr--ccoommmmaanndd(1), xxlloocckk(1), xxnnlloocckk(1), xxaauu-- ttoolloocckk(1), xxddmm(1), aattttrraaccttiioonn(1), ggrreeyynneettiicc(1), hheelliixx(1), hhooppaalloonngg(1), nnoosseegguuyy(1), ppyyrroo(1), xxrrooggeerr(1), qqiixx(1), rroocckkss(1), rroorrsscchhaacchh(1), bblliittssppiinn(1), iimmssmmaapp(1), sslliiddeessccrreeeenn(1), ddeeccaayyssccrreeeenn(1), mmaazzee(1), hhyyppeerrccuubbee(1), hhaalloo(1), ffllaammee(1), ppeeddaall(1), llmmoorrpphh(1), ddeeccoo(1), mmooiirree(1), kkaalleeiiddeessccooppee(1), bbuubbbblleess(1), lliigghhttnniinngg(1), ssttrraannggee(1), X Version 11 31-May-97 13 XScreenSaver(1) XScreenSaver(1) ffrraacctt(1), ssppiirraall(1), llaasseerr(1), ggrraavv(1), ddrriifftt(1), iiffss(1), jjuulliiaa(1), ppeennrroossee(1), ssiieerrppiinnsskkii(1), hhooppaalloonngg(1), bbrraaiidd(1), bboouubboouullee(1), ggaallaaxxyy(1), ffllaagg(1), ffoorreesstt(1), sspphheerree(1), lliissaa(1), xxddaalliicclloocckk(1), xxbboouunncceebbiittss(1), iiccoo(1), xxsswwaarrmm(1), xxwwaavvee(1), xxvv(1), xxttaaccyy(1), bboonnggoo(1), xxffiisshh-- ttaannkk(1) CCOOPPYYRRIIGGHHTT Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997 by Jamie Zawinski. Permission to use, copy, modify, dis- tribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. No representations are made about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. AAUUTTHHOORR Jamie Zawinski . Written in late 1991; first posted to comp.sources.x on 13-Aug-1992. Please let me know if you find any bugs or make any improvements. Thanks to David Wojtowicz for implementing _l_o_c_k_T_i_m_e_o_u_t. Thanks to Martin Kraemer for adding support for shadow passwords and locking-disabled diagnostics. Thanks to the many people who have contributed graphics demos to the package. Thanks to Patrick Moreau for the VMS port. And huge thanks to Jon A. Christopher for implementing the Athena dialog support, so that locking and demo-mode work even if you don't have Motif. X Version 11 31-May-97 14