diff options
| -rw-r--r-- | docs/C/gdm.xml | 92 |
1 files changed, 50 insertions, 42 deletions
diff --git a/docs/C/gdm.xml b/docs/C/gdm.xml index ce1ca59f..5d89d3a1 100644 --- a/docs/C/gdm.xml +++ b/docs/C/gdm.xml @@ -1818,11 +1818,12 @@ Greeter=/usr/lib/gdmgreeter Specify which actions are supported by the QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</command> commands. Valid values are - HALT, REBOOT, SHUTDOWN, SUSPEND, and CUSTOM_CMD and these should be - separated by semicolons. This allows certain options to be disabled - if desired. Refer to the related + HALT, REBOOT, SHUTDOWN, SUSPEND, and CUSTOM_CMD and these + should be separated by semicolons. This allows certain + options to be disabled if desired. Refer to the related <filename>SystemCommandsInMenu</filename> and - <filename>RBACSystemCommandKeys</filename> configuration options. + <filename>RBACSystemCommandKeys</filename> configuration + options. </para> </listitem> </varlistentry> @@ -2235,9 +2236,9 @@ Greeter=/usr/lib/gdmgreeter once only, the first time a greeter is displayed. The gdmprefetch command may be used. This utility will load any libraries passed in on the command line, or if the argument - starts with a "@" character, it will process the file assuming - it is an ASCII file containing a list of libraries, one per - line, and load each library in the file. + starts with a "@" character, it will process the file + assuming it is an ASCII file containing a list of libraries, + one per line, and load each library in the file. </para> </listitem> </varlistentry> @@ -2282,22 +2283,24 @@ Greeter=/usr/lib/gdmgreeter <synopsis>RBACSystemCommandKeys</synopsis> <para> Support RBAC (Role Based Access Control) for system commands - (Shutdown, Reboot, Suspend, etc.). This feature is only functional - if GDM is compiled with RBAC support. Specify the RBAC key used - to determine if the user has permission to use the action via the - QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION - <command>gdmflexiserver</command> commands. Valid actions are - HALT, REBOOT, SUSPEND, and CUSTOM_CMD. The greeter will only - display the command if the gdm user (<filename>User</filename> - configuration key) has RBAC permissions to use the action. RBAC - keys for multiple actions can be specified by separating them with - semicolons. The format for each is "Action:RBAC key". If an - action is not specified, it is assumed that all users have - permission to use this action. For example, a valid value for - this configuration option would be - "HALT:key.for.halt;REBOOT:key.for.reboot". Refer to the - related <filename>AllowLogoutActions</filename> and - <filename>SystemCommandsInMenu</filename> configuration options. + (Shutdown, Reboot, Suspend, etc.). This feature is only + functional if GDM is compiled with RBAC support. Specify the + RBAC key used to determine if the user has permission to use + the action via the QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and + SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</command> + commands. Valid actions are HALT, REBOOT, SUSPEND, and + CUSTOM_CMD. The greeter will only display the command if the + gdm user (<filename>User</filename> configuration key) has + RBAC permissions to use the action. RBAC keys for multiple + actions can be specified by separating them with semicolons. + The format for each is "Action:RBAC key". If an action is not + specified, it is assumed that all users have permission to use + this action. For example, a valid value for this + configuration option would be + "HALT:key.for.halt;REBOOT:key.for.reboot". Refer to + the related <filename>AllowLogoutActions</filename> and + <filename>SystemCommandsInMenu</filename> configuration + options. </para> </listitem> </varlistentry> @@ -2432,17 +2435,20 @@ Greeter=/usr/lib/gdmgreeter <synopsis>SuspendCommand=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD</synopsis> <para> Specify which system commands are available in the greeter - menu. Valid values are HALT, REBOOT, SHUTDOWN, SUSPEND, and CUSTOM_CMD - and these should be separated by semicolons. This can be useful if you - want to disable some options in the menu, but still have them available - to authenticated users via the SET_LOGOUT_ACTION or - SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</command> commands. For - example, the GNOME panel uses these commands to provide Shutdown, - Reboot, and Suspend in the application menu. Therefore if you turn off - these options in the greeter, these options can still be available to - users who have authenticated via the GNOME panel. Refer to the related + menu. Valid values are HALT, REBOOT, SHUTDOWN, SUSPEND, and + CUSTOM_CMD and these should be separated by semicolons. This + can be useful if you want to disable some options in the menu, + but still have them available to authenticated users via the + SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION + <command>gdmflexiserver</command> commands. For example, the + GNOME panel uses these commands to provide Shutdown, Reboot, + and Suspend in the application menu. Therefore if you turn + off these options in the greeter, these options can still be + available to users who have authenticated via the GNOME panel. + Refer to the related <filename>AllowLogoutActions</filename> and - <filename>RBACSystemCommandKeys</filename> configuration options. + <filename>RBACSystemCommandKeys</filename> configuration + options. </para> </listitem> </varlistentry> @@ -4736,7 +4742,8 @@ Arguments: <pattern> (optional) Answers: OK <server>;<server>;... - <server> is <display>,<logged in user>,<vt or xnest display> + <server> is <display>,<logged in user>,<vt or xnest + display> <logged in user> can be empty in case no one logged in yet, and <vt> can be -1 if it's not known or not @@ -4845,8 +4852,8 @@ Note: The cookie should be the MIT-MAGIC-COOKIE-1, use you should generate one first. The cookie should be in hex form. Supported since: 2.17.7 -Arguments: <username> <display to run on> <uid of requesting user> - <xauth cookie for the display> <xauth file> +Arguments: <username> <display to run on> <uid of requesting + user> <xauth cookie for the display> <xauth file> Answers: OK <display> ERROR <err number> <english error description> @@ -4916,12 +4923,13 @@ Answers: GET_CONFIG: Get configuration value for key. Useful so that other applications can request configuration information from GDM. Any key defined as GDM_KEY_* - in gdm-daemon-config-keys.h is supported. Starting with version 2.13.0.2 - translated keys (such as "greeter/GdmWelcome[cs]" are - supported via GET_CONFIG. Also starting with version - 2.13.0.2 it is no longer necessary to include the - default value (i.e. you can use key "greeter/IncludeAll" - instead of having to use "greeter/IncludeAll=false". + in gdm-daemon-config-keys.h is supported. Starting with version + 2.13.0.2, translated keys (such as + "greeter/GdmWelcome[cs]" are supported via GET_CONFIG. + Also starting with version 2.13.0.2 it is no longer necessary to + include the default value (i.e. you can use key + "greeter/IncludeAll" instead of having to use + "greeter/IncludeAll=false". Supported since: 2.6.0.9 Arguments: <key> Answers: |