XScreenSaver(1) XScreenSaver(1) NNAAMMEE xscreensaver-command - control a running xscreensaver pro- cess SSYYNNOOPPSSIISS xxssccrreeeennssaavveerr--ccoommmmaanndd [-help] [-demo] [-activate] [-deacti- vate] [-lock] [-cycle] [-next] [-prev] [-exit] [-restart] [-version] [-time] DDEESSCCRRIIPPTTIIOONN The _x_s_c_r_e_e_n_s_a_v_e_r_-_c_o_m_m_a_n_d program controls a running _x_s_c_r_e_e_n_s_a_v_e_r process by sending it client-messages. OOPPTTIIOONNSS _x_s_c_r_e_e_n_s_a_v_e_r_-_c_o_m_m_a_n_d accepts the following options: --hheellpp Prints a brief summary of command-line options. --ddeemmoo Cause the screensaver to enter its interactive demo mode, in which one can experiment with the various graphics hacks available. See xxssccrreeeenn-- ssaavveerr(1) for details. --aaccttiivvaattee Tell the screensaver to turn on immediately (that is, pretend that the user been idle for long enough.) It will turn off as soon as there is any user activity, as usual. It is useful to run this from a menu; you may wish to run it as sleep 5 ; xscreensaver-command -activate to be sure that you have time to remove your hand from the mouse before the screensaver comes on. --ddeeaaccttiivvaattee Tell the screensaver to turn off, as if there had been user activity. If locking is enabled, then the screensaver will prompt for a password as usual. --lloocckk Like _-_a_c_t_i_v_a_t_e, but a password will be required before the screensaver turns off, even if the screensaver's _l_o_c_k resource is false. The display will be locked immediately even if the screen- saver's _l_o_c_k_T_i_m_e_o_u_t resource is non-zero. --ccyyccllee Tell the screensaver to change which graphics hack it is running, just as if the ``cycle'' timer had expired. A new hack will be chosen randomly. --nneexxtt This is like either _-_a_c_t_i_v_a_t_e or _-_c_y_c_l_e, depending X Version 11 31-May-97 1 XScreenSaver(1) XScreenSaver(1) on which is more appropriate, except that the screenhack that will be run is the next one in the list of programs, instead of a randomly-chosen one. Repeatedly executing this will cycle through each hack in turn (though using the _-_d_e_m_o option is probably an easier way to accomplish that.) --pprreevv This is like _-_n_e_x_t, but cycles in the other direc- tion. --eexxiitt Causes the screensaver process to exit gracefully. This is a safer and easier way to kill the screen- saver than by using _k_i_l_l. WWaarrnniinngg:: never use _k_i_l_l _-_9 with _x_s_c_r_e_e_n_s_a_v_e_r while the screensaver is active. If you are using a virtual root window manager, that can leave things in an inconsistent state, and you may need to restart your window manager to repair the damage. --rreessttaarrtt Causes the screensaver process to exit and then restart with the same command line arguments. This is a good way of causing the screensaver to re-read the resource database. If the screensaver is run from _x_d_m_(_1_) (that is, it is already running before you log in) then you may want to issue the ``restart'' command from one of your startup scripts, so that the screensaver gets your resource settings instead of the default ones. --vveerrssiioonn Print (on stdout) the version number of the xscreensaver program that is running on $DISPLAY. (To see the version number of _x_s_c_r_e_e_n_s_a_v_e_r_-_c_o_m_m_a_n_d itself, use the _-_h_e_l_p option.) --ttiimmee This option prints on stdout the time at which the screensaver last activated (blanked the screen) or deactivated (restored the screen.) Note that the activation-time is not the last time at which the user was active, but is some time later (it is the time at which either: xscreensaver decided that the user has been idle long enough; or, the user explicitly activated the screensaver or locker.) EENNVVIIRROONNMMEENNTT DDIISSPPLLAAYY to get the host and display number of the screen whose saver is to be manipulated. PPAATTHH to find the executable to restart (for the _-_r_e_s_t_a_r_t command). Note that this variable is X Version 11 31-May-97 2 XScreenSaver(1) XScreenSaver(1) consulted in the environment of the _x_s_c_r_e_e_n_s_a_v_e_r process, not the _x_s_c_r_e_e_n_s_a_v_e_r_-_c_o_m_m_a_n_d process. SSEEEE AALLSSOO XX(1), xxssccrreeeennssaavveerr(1) BBUUGGSS Some diagnostics are reported on the stderr of the _x_s_c_r_e_e_n_s_a_v_e_r process, not this process, so the caller of _x_s_c_r_e_e_n_s_a_v_e_r_-_c_o_m_m_a_n_d may not see the error messages. CCOOPPYYRRIIGGHHTT Copyright (C) 1992, 1993, 1997 by Jamie Zawinski. Permis- sion to use, copy, modify, distribute, and sell this soft- ware 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 pro- vided "as is" without express or implied warranty. AAUUTTHHOORR Jamie Zawinski , 13-aug-92. X Version 11 31-May-97 3