diff options
| author | Brian Cameron <brian.cameron@sun.com> | 2006-07-17 19:07:20 +0000 |
|---|---|---|
| committer | Brian Cameron <bcameron@src.gnome.org> | 2006-07-17 19:07:20 +0000 |
| commit | 2c1a2a023664c853ebcbbd86bc0ddbb961f1e8c2 (patch) | |
| tree | 4580ef402e4519a72e17eed4d0da53cf5ee104e5 | |
| parent | 91055a9c6320286f3f24827f4a5fa20b22e50fe4 (diff) | |
| download | gdm-2c1a2a023664c853ebcbbd86bc0ddbb961f1e8c2.tar.gz | |
Fix for bug causing gdmsetup to have performance issues starting up. Fixes
2006-07-17 Brian Cameron <brian.cameron@sun.com>
* gui/gdmsetup.c: Fix for bug causing gdmsetup to have
performance issues starting up. Fixes bug #345118.
Patch by Ray Strode <rstrode@redhat.com>.
| -rw-r--r-- | ChangeLog | 6 | ||||
| -rw-r--r-- | docs/es/gdm.xml | 2440 | ||||
| -rw-r--r-- | docs/es/legal.xml | 9 | ||||
| -rw-r--r-- | docs/uk/gdm.xml | 1792 | ||||
| -rw-r--r-- | docs/uk/legal.xml | 9 | ||||
| -rw-r--r-- | gui/gdmsetup.c | 29 |
6 files changed, 3646 insertions, 639 deletions
@@ -1,3 +1,9 @@ +2006-07-17 Brian Cameron <brian.cameron@sun.com> + + * gui/gdmsetup.c: Fix for bug causing gdmsetup to have + performance issues starting up. Fixes bug #345118. + Patch by Ray Strode <rstrode@redhat.com>. + 2006-06-30 Brian Cameron <brian.cameron@sun.com> * gui/gdmcommon.c: Fix timed login message so it works diff --git a/docs/es/gdm.xml b/docs/es/gdm.xml index f7cad1d3..6bd88b8a 100644 --- a/docs/es/gdm.xml +++ b/docs/es/gdm.xml @@ -59,18 +59,31 @@ <para>Muchos de los nombres utilizados por las empresas para distinguir sus productos y servicios se consideran marcas comerciales. Cuando estos nombres aparezcan en la documentación de GNOME, y siempre que se haya informado a los miembros del Proyecto de documentación de GNOME de dichas marcas comerciales, los nombres aparecerán en mayúsculas o con las iniciales en mayúsculas.</para> - <para>ESTE DOCUMENTO Y LAS VERSIONES MODIFICADAS DEL MISMO SE OFRECEN SEGÚN LAS CONDICIONES ESTABLECIDAS EN LA LICENCIA DE DOCUMENTACIÓN LIBRE DE GNU (GFDL) Y TENIENDO EN CUENTA QUE: <orderedlist><listitem><para>EL DOCUMENTO SE ENTREGA "TAL CUAL", SIN GARANTÍA DE NINGÚN TIPO, NI EXPLÍCITA NI IMPLÍCITA INCLUYENDO, SIN LIMITACIÓN, GARANTÍA DE QUE EL DOCUMENTO O VERSIÓN MODIFICADA DE ÉSTE CAREZCA DE DEFECTOS EN EL MOMENTO DE SU VENTA, SEA ADECUADO A UN FIN CONCRETO O INCUMPLA ALGUNA NORMATIVA. TODO EL RIESGO RELATIVO A LA CALIDAD, PRECISIÓN Y UTILIDAD DEL DOCUMENTO O SU VERSIÓN MODIFICADA RECAE EN USTED. SI CUALQUIER DOCUMENTO O VERSIÓN MODIFICADA DE AQUÉL RESULTARA DEFECTUOSO EN CUALQUIER ASPECTO, USTED (Y NO EL REDACTOR INICIAL, AUTOR O AUTOR DE APORTACIONES) ASUMIRÁ LOS COSTES DE TODA REPARACIÓN, MANTENIMIENTO O CORRECCIÓN NECESARIOS. ESTA EXENCIÓN DE RESPONSABILIDAD SOBRE LA GARANTÍA ES UNA PARTE ESENCIAL DE ESTA LICENCIA. NO SE AUTORIZA EL USO DE NINGÚN DOCUMENTO NI VERSIÓN MODIFICADA DE ÉSTE POR EL PRESENTE, SALVO DENTRO DEL CUMPLIMIENTO DE LA EXENCIÓN DE RESPONSABILIDAD;Y</para></listitem><listitem><para>EN NINGUNA CIRCUNSTANCIA NI BAJO NINGUNA TEORÍA LEGAL, SEA POR ERROR (INCLUYENDO NEGLIGENCIA) CONTRATO O DOCUMENTO DE OTRO TIPO, EL AUTOR, EL ESCRITOR INICIAL, EL AUTOR DE APORTACIONES NI NINGÚN DISTRIBUIDOR DEL DOCUMENTO O VERSIÓN MODIFICADA DEL DOCUMENTO, NI NINGÚN PROVEEDOR DE NINGUNA DE ESAS PARTES, SERÁ RESPONSABLE ANTE NINGUNA PERSONA POR NINGÚN DAÑO DIRECTO, INDIRECTO, ESPECIAL, INCIDENTAL O DERIVADO DE NINGÚN TIPO, INCLUYENDO, SIN LIMITACIÓN DAÑOS POR PÉRDIDA DE FONDO DE COMERCIO, PARO TÉCNICO, FALLO INFORMÁTICO O AVERÍA O CUALQUIER OTRO POSIBLE DAÑO O AVERÍA DERIVADO O RELACIONADO CON EL USO DEL DOCUMENTO O SUS VERSIONES MODIFICADAS, AUNQUE DICHA PARTE HAYA SIDO INFORMADA DE LA POSIBILIDAD DE QUE SE PRODUJESEN ESOS DAÑOS.</para></listitem></orderedlist></para> + <para>ESTE DOCUMENTO Y LAS VERSIONES MODIFICADAS DEL MISMO SE OFRECEN SEGÚN LAS CONDICIONES ESTABLECIDAS EN LA LICENCIA DE DOCUMENTACIÓN LIBRE DE GNU (GFDL) Y TENIENDO EN CUENTA QUE: <orderedlist> + <listitem> + <para>EL DOCUMENTO SE ENTREGA "TAL CUAL", SIN GARANTÍA DE NINGÚN TIPO, NI EXPLÍCITA NI IMPLÍCITA INCLUYENDO, SIN LIMITACIÓN, GARANTÍA DE QUE EL DOCUMENTO O VERSIÓN MODIFICADA DE ÉSTE CAREZCA DE DEFECTOS EN EL MOMENTO DE SU VENTA, SEA ADECUADO A UN FIN CONCRETO O INCUMPLA ALGUNA NORMATIVA. TODO EL RIESGO RELATIVO A LA CALIDAD, PRECISIÓN Y UTILIDAD DEL DOCUMENTO O SU VERSIÓN MODIFICADA RECAE EN USTED. SI CUALQUIER DOCUMENTO O VERSIÓN MODIFICADA DE AQUÉL RESULTARA DEFECTUOSO EN CUALQUIER ASPECTO, USTED (Y NO EL REDACTOR INICIAL, AUTOR O AUTOR DE APORTACIONES) ASUMIRÁ LOS COSTES DE TODA REPARACIÓN, MANTENIMIENTO O CORRECCIÓN NECESARIOS. ESTA EXENCIÓN DE RESPONSABILIDAD SOBRE LA GARANTÍA ES UNA PARTE ESENCIAL DE ESTA LICENCIA. NO SE AUTORIZA EL USO DE NINGÚN DOCUMENTO NI VERSIÓN MODIFICADA DE ÉSTE POR EL PRESENTE, SALVO DENTRO DEL CUMPLIMIENTO DE LA EXENCIÓN DE RESPONSABILIDAD;Y</para> + </listitem> + <listitem> + <para>EN NINGUNA CIRCUNSTANCIA NI BAJO NINGUNA TEORÍA LEGAL, SEA POR ERROR (INCLUYENDO NEGLIGENCIA) CONTRATO O DOCUMENTO DE OTRO TIPO, EL AUTOR, EL ESCRITOR INICIAL, EL AUTOR DE APORTACIONES NI NINGÚN DISTRIBUIDOR DEL DOCUMENTO O VERSIÓN MODIFICADA DEL DOCUMENTO, NI NINGÚN PROVEEDOR DE NINGUNA DE ESAS PARTES, SERÁ RESPONSABLE ANTE NINGUNA PERSONA POR NINGÚN DAÑO DIRECTO, INDIRECTO, ESPECIAL, INCIDENTAL O DERIVADO DE NINGÚN TIPO, INCLUYENDO, SIN LIMITACIÓN DAÑOS POR PÉRDIDA DE FONDO DE COMERCIO, PARO TÉCNICO, FALLO INFORMÁTICO O AVERÍA O CUALQUIER OTRO POSIBLE DAÑO O AVERÍA DERIVADO O RELACIONADO CON EL USO DEL DOCUMENTO O SUS VERSIONES MODIFICADAS, AUNQUE DICHA PARTE HAYA SIDO INFORMADA DE LA POSIBILIDAD DE QUE SE PRODUJESEN ESOS DAÑOS.</para> + </listitem> + </orderedlist></para> </legalnotice> - <releaseinfo>This manual describes version 2.14.0 of the GNOME Display Manager. It was last updated on 03/20/2006.</releaseinfo> + <releaseinfo> + This manual describes version 2.14.0 of the GNOME Display Manager. + It was last updated on 03/20/2006. + </releaseinfo> </articleinfo> <sect1 id="preface"> <title>Términos y convenciones usados en este manual</title> - <para>This manual describes version 2.14.0 of the GNOME Display Manager. It was last updated on 03/20/2006.</para> + <para> + This manual describes version 2.14.0 of the GNOME Display Manager. + It was last updated on 03/20/2006. + </para> <para>Selector - Un programa que se usa para seleccionar un equipo remoto para gestionar una pantalla remotamente en la pantalla local (<command>gdmchooser</command>).</para> @@ -246,7 +259,23 @@ <para>Para acelerar el rendimiento es posible construir GDM para que precargue las bibliotecas cuando el GDM muestre un programa de entrada por primera vez. Esto se ha mostrado para acelerar el primer inicio de sesión debido a que estas bibliotecas pueden cargarse en memoria mientras el usuario teclea su nombre y contraseña.</para> - <para>To use this feature, configure GDM with the <command>--with-prefetch</command> option. This will cause GDM to install the <command>gdmprefetch</command> program to the <filename>libexecdir</filename> directory, install the <filename>gdmprefetchlist</filename> to the <filename><etc>/gdm</filename> directory, and set the <filename>PreFetchProgram</filename> configuration variable so that the <command>gdmprefetch</command> program is called with the default <filename>gdmprefetchlist</filename> file. The default <filename>gdmprefetchlist</filename> file was optimized for a GNOME desktop running on Solaris, so may need fine-tuning on other systems. Alternative prefetchlist files can be contributed to the "gdm" category in <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink>, so that they can be included in future GDM releases.</para> + <para> + To use this feature, configure GDM with the + <command>--with-prefetch</command> option. This will cause GDM to + install the <command>gdmprefetch</command> program to the + <filename>libexecdir</filename> directory, install the + <filename>gdmprefetchlist</filename> to the + <filename><etc>/gdm</filename> directory, and set the + <filename>PreFetchProgram</filename> configuration variable so that the + <command>gdmprefetch</command> program is called with the default + <filename>gdmprefetchlist</filename> file. The default + <filename>gdmprefetchlist</filename> file was optimized + for a GNOME desktop running on Solaris, so may need fine-tuning on + other systems. Alternative prefetchlist files can be contributed + to the "gdm" category in + <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink>, + so that they can be included in future GDM releases. + </para> </sect2> </sect1> @@ -472,11 +501,17 @@ PostSession/ <para>Se reconocen los siguientes caracteres de control dentro del nombre especificado:</para> - <para>%%— the `%' character</para> + <para> + %% — the `%' character + </para> - <para>%d — display's name</para> + <para> + %d — display's name + </para> - <para>%h — display's hostname</para> + <para> + %h — display's hostname + </para> <para>Alternativamente, el nombre podría terminar con una barra vertical |, el símbolo de cauce. El nombre se usa entonces como una aplicación a ejecutar que revuelve el nombre de usuario deseado en la salida estándar. Si se devuelve un nombre de usuario vacío o inválido, no se realiza el inicio de sesión automático. Esta característica se usa típicamente cuando se usan varios visores remotos como kioskos de Internet, con un usuario específico para iniciar sesión automáticamente en cada visualizador.</para> </listitem> @@ -486,11 +521,40 @@ PostSession/ <term>BaseXsession</term> <listitem> <synopsis>BaseXsession=<etc>/gdm/Xsession</synopsis> - <para>This is the base X session file. When a user logs in, this script will be run with the selected session as the first argument. The selected session will be the <filename>Exec=</filename> from the <filename>.desktop</filename> file of the session.</para> - - <para>If you wish to use the same script for several different display managers, and wish to have some of the script run only for GDM, then you can check the presence of the <filename>GDMSESSION</filename> environmental variable. This will always be set to the basename of <filename>.desktop</filename> (without the extension) file that is being used for this session, and will only be set for GDM sessions. Previously some scripts were checking for <filename>GDM_LANG</filename>, but that is only set when the user picks a non-system default language.</para> - - <para>This script should take care of doing the "login" for the user and so it should source the <filename><etc>/profile</filename> and friends. The standard script shipped with GDM sources the files in this order: <filename><etc>/profile</filename> then <filename>~/.profile</filename> then <filename><etc>/xprofile</filename> and finally <filename>~/.xprofile</filename>. Note that different distributions may change this however. Sometimes users personal setup will be in <filename>~/.bash_profile</filename>, however broken that is.</para> + <para> + This is the base X session file. When a user logs in, this + script will be run with the selected session as the first + argument. The selected session will be the + <filename>Exec=</filename> from the + <filename>.desktop</filename> file of the session. + </para> + + <para> + If you wish to use the same script for several different + display managers, and wish to have some of the script run only + for GDM, then you can check the presence of the + <filename>GDMSESSION</filename> environmental variable. This + will always be set to the basename of + <filename>.desktop</filename> (without the extension) file that + is being used for this session, and will only be set for GDM + sessions. Previously some scripts were checking for + <filename>GDM_LANG</filename>, but that is only set when the + user picks a non-system default language. + </para> + + <para> + This script should take care of doing the "login" for + the user and so it should source the + <filename><etc>/profile</filename> and friends. The + standard script shipped with GDM sources the files in this + order: <filename><etc>/profile</filename> then + <filename>~/.profile</filename> then + <filename><etc>/xprofile</filename> and finally + <filename>~/.xprofile</filename>. Note that different + distributions may change this however. Sometimes users + personal setup will be in <filename>~/.bash_profile</filename>, + however broken that is. + </para> </listitem> </varlistentry> @@ -506,7 +570,14 @@ PostSession/ <term>Configurator</term> <listitem> <synopsis>Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog</synopsis> - <para>The pathname to the configurator binary. If the greeter <filename>ConfigAvailable</filename> option is set to true then run this binary when somebody chooses Configuration from the Actions menu. Of course GDM will first ask for root password however. And it will never allow this to happen from a remote display.</para> + <para> + The pathname to the configurator binary. If the greeter + <filename>ConfigAvailable</filename> option is set to true then + run this binary when somebody chooses Configuration from the + Actions menu. Of course GDM will first ask for root password + however. And it will never allow this to happen from a remote + display. + </para> </listitem> </varlistentry> @@ -514,7 +585,12 @@ PostSession/ <term>ConsoleCannotHandle</term> <listitem> <synopsis>ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh</synopsis> - <para>These are the languages that the console cannot handle because of font issues. Here we mean the text console, not X. This is only used when there are errors to report and we cannot start X.</para> + <para> + These are the languages that the console cannot handle because + of font issues. Here we mean the text console, not X. This + is only used when there are errors to report and we cannot + start X. + </para> </listitem> </varlistentry> @@ -522,7 +598,10 @@ PostSession/ <term>ConsoleNotify</term> <listitem> <synopsis>ConsoleNotify=true</synopsis> - <para>If false, gdm will not display a message dialog on the console when an error happens.</para> + <para> + If false, gdm will not display a message dialog on the + console when an error happens. + </para> </listitem> </varlistentry> @@ -530,7 +609,15 @@ PostSession/ <term>DefaultPath</term> <listitem> <synopsis>DefaultPath=defaultpath (value set by configure)</synopsis> - <para>Specifies the path which will be set in the user's session. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains "ROOT=<pathname>". If the <filename>/etc/default/login</filename> file exists, but contains no value for ROOT, the value as defined in the GDM configuration will be be used.</para> + <para> + Specifies the path which will be set in the user's session. + This value will be overridden with the value from + <filename>/etc/default/login</filename> if it contains + "ROOT=<pathname>". If the + <filename>/etc/default/login</filename> file exists, but + contains no value for ROOT, the value as defined in the GDM + configuration will be be used. + </para> </listitem> </varlistentry> @@ -538,7 +625,12 @@ PostSession/ <term>DefaultSession</term> <listitem> <synopsis>DefaultSession=gnome.desktop</synopsis> - <para>The session that is used by default if the user does not have a saved preference and has picked 'Last' from the list of sessions. Note that 'Last' need not be displayed, see the <filename>ShowLastSession</filename> key.</para> + <para> + The session that is used by default if the user does not have + a saved preference and has picked 'Last' from the list of + sessions. Note that 'Last' need not be displayed, see + the <filename>ShowLastSession</filename> key. + </para> </listitem> </varlistentry> @@ -547,7 +639,10 @@ PostSession/ <term>DisplayInitDir</term> <listitem> <synopsis>DisplayInitDir=<etc>/gdm/Init</synopsis> - <para>Directory containing the display init scripts. See the ``The Script Directories'' section for more info.</para> + <para> + Directory containing the display init scripts. See the + ``The Script Directories'' section for more info. + </para> </listitem> </varlistentry> @@ -555,8 +650,23 @@ PostSession/ <term>DisplayLastLogin</term> <listitem> <synopsis>DisplayLastLogin=true</synopsis> - <para>If true then the last login information is printed to the user before being prompted for password. While this gives away some info on what users are on a system, it on the other hand should give the user an idea of when they logged in and if it doesn't seem kosher to them, they can just abort the login and contact the sysadmin (avoids running malicious startup scripts). This was added in version 2.5.90.0.</para> - <para>This is for making GDM conformant to CSC-STD-002-85, although that is purely theoretical now. Someone should read that spec and ensure that this actually conforms (in addition to other places in GDM). See <filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> for more info.</para> + <para> + If true then the last login information is printed to the user + before being prompted for password. While this gives away some + info on what users are on a system, it on the other hand should + give the user an idea of when they logged in and if it doesn't + seem kosher to them, they can just abort the login and contact + the sysadmin (avoids running malicious startup scripts). + This was added in version 2.5.90.0. + </para> + <para> + This is for making GDM conformant to CSC-STD-002-85, although + that is purely theoretical now. Someone should read that spec + and ensure that this actually conforms (in addition to other + places in GDM). See + <filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> + for more info. + </para> </listitem> </varlistentry> @@ -564,7 +674,12 @@ PostSession/ <term>DoubleLoginWarning</term> <listitem> <synopsis>DoubleLoginWarning=true</synopsis> - <para>If true, GDM will warn the user if they are already logged in on another virtual terminal. On systems where GDM supports checking the X virtual terminals, GDM will let the user switch to the previous login virtual terminal instead of logging in.</para> + <para> + If true, GDM will warn the user if they are already logged in + on another virtual terminal. On systems where GDM supports + checking the X virtual terminals, GDM will let the user switch + to the previous login virtual terminal instead of logging in. + </para> </listitem> </varlistentry> @@ -572,7 +687,14 @@ PostSession/ <term>DynamicXServers</term> <listitem> <synopsis>DynamicXServers=false</synopsis> - <para>If true, the GDM daemon will honor requests to manage displays via the <filename>/tmp/.gdm_socket</filename> socket connection. Displays can be created, started, and deleted with the appropriate commands. The <filename>gdmdynamic</filename> command is a convenient method to send these messages.</para> + <para> + If true, the GDM daemon will honor requests to manage + displays via the <filename>/tmp/.gdm_socket</filename> + socket connection. Displays can be created, started, + and deleted with the appropriate commands. The + <filename>gdmdynamic</filename> command is a convenient + method to send these messages. + </para> </listitem> </varlistentry> @@ -580,7 +702,13 @@ PostSession/ <term>FailsafeXServer</term> <listitem> <synopsis>FailsafeXServer=</synopsis> - <para>An X command line in case we can't start the normal X server. should probably be some sort of a script that runs an appropriate low resolution X server that will just work. This is tried before the <filename>XKeepsCrashing</filename> script is run.</para> + <para> + An X command line in case we can't start the normal X server. + should probably be some sort of a script that runs an + appropriate low resolution X server that will just work. + This is tried before the <filename>XKeepsCrashing</filename> + script is run. + </para> </listitem> </varlistentry> @@ -588,7 +716,12 @@ PostSession/ <term>FirstVT</term> <listitem> <synopsis>FirstVT=7</synopsis> - <para>On systems where GDM supports automatic VT (virtual terminal) allocation, this is the first vt to try. Usually standard text logins are run on the lower vts. See also <filename>VTAllocation</filename>.</para> + <para> + On systems where GDM supports automatic VT (virtual terminal) + allocation, this is the first vt to try. Usually standard text + logins are run on the lower vts. See also + <filename>VTAllocation</filename>. + </para> </listitem> </varlistentry> @@ -596,7 +729,13 @@ PostSession/ <term>FlexibleXServers</term> <listitem> <synopsis>FlexibleXServers=5</synopsis> - <para>The maximum number of allowed flexible displays. These are displays that can be run using the <filename>/tmp/.gdm_socket</filename> socket connection. This is used for both full flexible displays and for Xnest displays.</para> + <para> + The maximum number of allowed flexible displays. These are + displays that can be run using the + <filename>/tmp/.gdm_socket</filename> socket connection. + This is used for both full flexible displays and for Xnest + displays. + </para> </listitem> </varlistentry> @@ -604,7 +743,13 @@ PostSession/ <term>FlexiReapDelayMinutes</term> <listitem> <synopsis>FlexiReapDelayMinutes=5</synopsis> - <para>After how many minutes of inactivity at the login screen should a flexi display be reaped. This is only in effect before a user logs in. Also it does not affect the Xnest flexiservers. To turn off this behavior set this value to 0. This was added in version 2.5.90.0.</para> + <para> + After how many minutes of inactivity at the login screen + should a flexi display be reaped. This is only in effect before + a user logs in. Also it does not affect the Xnest + flexiservers. To turn off this behavior set this value to 0. + This was added in version 2.5.90.0. + </para> </listitem> </varlistentry> @@ -612,7 +757,12 @@ PostSession/ <term>Greeter</term> <listitem> <synopsis>Greeter=<bin>/gdmlogin</synopsis> - <para>Full path and name of the greeter executable followed by optional arguments. This is the greeter used for all displays except for the XDMCP remote displays. See also <filename>RemoteGreeter</filename></para> + <para> + Full path and name of the greeter executable followed by + optional arguments. This is the greeter used for all displays + except for the XDMCP remote displays. See also + <filename>RemoteGreeter</filename> + </para> </listitem> </varlistentry> @@ -620,7 +770,19 @@ PostSession/ <term>Group</term> <listitem> <synopsis>Group=gdm</synopsis> - <para>The group name under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogs are run. Also see <filename>User</filename>. This user will have access to all the X authorization files, and perhaps to other internal GDM data and it should not therefore be a user such as nobody, but rather a dedicated user. The <filename>ServAuthDir</filename> is owned by this group. The ownership and permissions of <filename>ServAuthDir</filename> should be <filename>root.gdm</filename> and 1770.</para> + <para> + The group name under which <command>gdmlogin</command>, + <command>gdmgreeter</command>, + <command>gdmchooser</command> and the internal + failsafe GTK+ dialogs are run. Also see + <filename>User</filename>. This user will have access to all + the X authorization files, and perhaps to other internal GDM + data and it should not therefore be a user such as nobody, but + rather a dedicated user. The <filename>ServAuthDir</filename> + is owned by this group. The ownership and permissions of + <filename>ServAuthDir</filename> should be + <filename>root.gdm</filename> and 1770. + </para> </listitem> </varlistentry> @@ -628,7 +790,13 @@ PostSession/ <term>GtkModulesList</term> <listitem> <synopsis>GtkModulesList=module-1:module-2:...</synopsis> - <para>A colon separated list of Gtk+ modules that <command>gdmgreeter</command> or <command>gdmlogin</command> will be invoked with if <filename>AddGtkModules</filename> is true. The format is the same as the standard Gtk+ module interface.</para> + <para> + A colon separated list of Gtk+ modules that + <command>gdmgreeter</command> or <command>gdmlogin</command> + will be invoked with if <filename>AddGtkModules</filename> is + true. The format is the same as the standard Gtk+ module + interface. + </para> </listitem> </varlistentry> @@ -636,7 +804,15 @@ PostSession/ <term>HaltCommand</term> <listitem> <synopsis>HaltCommand=<sbin>/shutdown -h now</synopsis> - <para>Full path and arguments to command to be executed when user selects "Shut Down" from the Actions menu. This can be a ';' separated list of commands to try. If a value is missing, the shut down command is not available. Note that the default for this value is not empty, so to disable "Shut Down" it must be set to an empty value.</para> + <para> + Full path and arguments to command to be executed when user + selects "Shut Down" from the Actions menu. This can + be a ';' separated list of commands to try. If a value is + missing, the shut down command is not available. Note that the + default for this value is not empty, so to disable + "Shut Down" it must be + set to an empty value. + </para> </listitem> </varlistentry> @@ -644,7 +820,10 @@ PostSession/ <term>KillInitClients</term> <listitem> <synopsis>KillInitClients=true</synopsis> - <para>Determines whether GDM should kill X clients started by the init scripts when the user logs in.</para> + <para> + Determines whether GDM should kill X clients started by the + init scripts when the user logs in. + </para> </listitem> </varlistentry> @@ -652,7 +831,10 @@ PostSession/ <term>Directorio de registro</term> <listitem> <synopsis>LogDir=<var>/log/gdm</synopsis> - <para>Directory containing the log files for the individual displays. By default this is the same as the ServAuthDir.</para> + <para> + Directory containing the log files for the individual displays. + By default this is the same as the ServAuthDir. + </para> </listitem> </varlistentry> @@ -660,7 +842,10 @@ PostSession/ <term>PidFile</term> <listitem> <synopsis>PidFile=<var>/run/gdm.pid</synopsis> - <para>Name of the file containing the <filename>gdm</filename> process id.</para> + <para> + Name of the file containing the <filename>gdm</filename> + process id. + </para> </listitem> </varlistentry> @@ -668,7 +853,18 @@ PostSession/ <term>PreFetchProgram</term> <listitem> <synopsis>PreFetchProgram=command</synopsis> - <para>Program to be run by the GDM greeter/login program when the initial screen is displayed. The purpose is to provide a hook where files which will be used after login can be preloaded to speed performance for the user. The program will be called 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.</para> + <para> + Program to be run by the GDM greeter/login program when the + initial screen is displayed. The purpose is to provide a hook + where files which will be used after login can be preloaded to + speed performance for the user. The program will be called + 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. + </para> </listitem> </varlistentry> @@ -676,7 +872,11 @@ PostSession/ <term>PostLoginScriptDir</term> <listitem> <synopsis>PostLoginScriptDir=<etc>/gdm/PostLogin</synopsis> - <para>Directory containing the scripts run right after the user logs in, but before any session setup is done. See the ``The Script Directories'' section for more info.</para> + <para> + Directory containing the scripts run right after the user logs + in, but before any session setup is done. See the + ``The Script Directories'' section for more info. + </para> </listitem> </varlistentry> @@ -684,7 +884,10 @@ PostSession/ <term>PostSessionScriptDir</term> <listitem> <synopsis>PostSessionScriptDir=<etc>/gdm/PostSession</synopsis> - <para>Directory containing the scripts run after the user logs out. See the ``The Script Directories'' section for more info.</para> + <para> + Directory containing the scripts run after the user logs out. + See the ``The Script Directories'' section for more info. + </para> </listitem> </varlistentry> @@ -692,7 +895,10 @@ PostSession/ <term>PreSessionScriptDir</term> <listitem> <synopsis>PreSessionScriptDir=<etc>/gdm/PreSession</synopsis> - <para>Directory containing the scripts run before the user logs in. See the ``The Script Directories'' section for more info.</para> + <para> + Directory containing the scripts run before the user logs in. + See the ``The Script Directories'' section for more info. + </para> </listitem> </varlistentry> @@ -700,7 +906,14 @@ PostSession/ <term>RebootCommand</term> <listitem> <synopsis>RebootCommand=<sbin>/shutdown -r now</synopsis> - <para>Full path and optional arguments to the command to be executed when user selects Restart from the Actions menu. This can be a ';' separated list of commands to try. If missing, the restart command is not available. Note that the default for this value is not empty so to disable restart you must set this explicitly to an empty value.</para> + <para> + Full path and optional arguments to the command to be + executed when user selects Restart from the Actions menu. This + can be a ';' separated list of commands to try. If missing, + the restart command is not available. Note that the default + for this value is not empty so to disable restart you must set + this explicitly to an empty value. + </para> </listitem> </varlistentry> @@ -708,7 +921,13 @@ PostSession/ <term>RemoteGreeter</term> <listitem> <synopsis>RemoteGreeter=<bin>/gdmlogin</synopsis> - <para>Full path and name of the greeter executable followed by optional arguments. This is used for all remote XDMCP sessions. It is useful to have the less graphically demanding greeter here if you use the Themed Greeter for your main greeter. See also the <filename>Greeter</filename> key.</para> + <para> + Full path and name of the greeter executable followed by + optional arguments. This is used for all remote XDMCP + sessions. It is useful to have the less graphically demanding + greeter here if you use the Themed Greeter for your main + greeter. See also the <filename>Greeter</filename> key. + </para> </listitem> </varlistentry> @@ -716,7 +935,16 @@ PostSession/ <term>RootPath</term> <listitem> <synopsis>RootPath=defaultpath (value set by configure)</synopsis> - <para>Specifies the path which will be set in the root's session and the {Init,PostLogin,PreSession,PostSession} scripts executed by GDM. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains "SUROOT=<pathname>". If the <filename>/etc/default/login</filename> file exists, but contains no value for SUROOT, the value as defined in the GDM configuration will be used.</para> + <para> + Specifies the path which will be set in the root's + session and the {Init,PostLogin,PreSession,PostSession} scripts + executed by GDM. This value will be overridden with the value + from <filename>/etc/default/login</filename> if it + contains "SUROOT=<pathname>". If the + <filename>/etc/default/login</filename> file exists, but + contains no value for SUROOT, the value as defined in the GDM + configuration will be used. + </para> </listitem> </varlistentry> @@ -724,7 +952,24 @@ PostSession/ <term>ServAuthDir</term> <listitem> <synopsis>ServAuthDir=<var>/gdm</synopsis> - <para>Directory containing the X authentication files for the individual displays. Should be owned by <filename>root.gdm</filename> with permissions 1770, where <filename>gdm</filename> is the GDM group as defined by the <filename>Group</filename> option. That is should be owned by root, with <filename>gdm</filename> group having full write permissions and the directory should be sticky and others should have no permission to the directory. This way the GDM user can't remove files owned by root in that directory, while still being able to write its own files there. GDM will attempt to change permissions for you when it's first run if the permissions are not the above. This directory is also used for other private files that the daemon needs to store. Other users should not have any way to get into this directory and read/change it's contents. Anybody who can read this directory can connect to any display on this computer.</para> + <para> + Directory containing the X authentication files for the + individual displays. Should be owned by + <filename>root.gdm</filename> with permissions 1770, where + <filename>gdm</filename> is the GDM group as defined by the + <filename>Group</filename> option. That is should be owned by + root, with <filename>gdm</filename> group having full write + permissions and the directory should be sticky and others + should have no permission to the directory. This way the GDM + user can't remove files owned by root in that directory, while + still being able to write its own files there. GDM will + attempt to change permissions for you when it's first run if + the permissions are not the above. This directory is also used + for other private files that the daemon needs to store. Other + users should not have any way to get into this directory and + read/change it's contents. Anybody who can read this directory + can connect to any display on this computer. + </para> </listitem> </varlistentry> @@ -732,7 +977,12 @@ PostSession/ <term>SessionDesktopDir</term> <listitem> <synopsis>SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/</synopsis> - <para>Directory containing the <filename>.desktop</filename> files which are the available sessions on the system. Since 2.4.4.2 this is treated like a PATH type variable and the first file found is used.</para> + <para> + Directory containing the <filename>.desktop</filename> files + which are the available sessions on the system. Since 2.4.4.2 + this is treated like a PATH type variable and the first file + found is used. + </para> </listitem> </varlistentry> @@ -740,7 +990,12 @@ PostSession/ <term>SoundProgram</term> <listitem> <synopsis>SoundProgram=<filename><bin>/play</filename> (or <filename><bin>/audioplay</filename> on Solaris)</synopsis> - <para>Application to use when playing a sound. Currently used for playing the login sound, see the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0.</para> + <para> + Application to use when playing a sound. Currently used for + playing the login sound, see the + <filename>SoundOnLoginFile</filename> key. Supported since + 2.5.90.0. + </para> </listitem> </varlistentry> @@ -748,7 +1003,13 @@ PostSession/ <term>StandardXServer</term> <listitem> <synopsis>StandardXServer=/dir/to/X (value assigned by configuration file)</synopsis> - <para>Full path and arguments to the standard X server command. This is used when gdm cannot find any other definition, and it's used as the default and failsafe fallback in a number of places. This should be able to run some sort of X server.</para> + <para> + Full path and arguments to the standard X server command. + This is used when gdm cannot find any other definition, + and it's used as the default and failsafe fallback in a + number of places. This should be able to run some sort + of X server. + </para> </listitem> </varlistentry> @@ -756,7 +1017,13 @@ PostSession/ <term>SuspendCommand</term> <listitem> <synopsis>SuspendCommand=</synopsis> - <para>Full path and arguments to command to be executed when user selects Suspend from the Actions menu. If empty there is no such menu item. Note that the default for this value is not empty so to disable suspend you must set this explicitly to an empty value.</para> + <para> + Full path and arguments to command to be executed when + user selects Suspend from the Actions menu. If empty + there is no such menu item. Note that the default for this + value is not empty so to disable suspend you must set this + explicitly to an empty value. + </para> </listitem> </varlistentry> @@ -764,7 +1031,22 @@ PostSession/ <term>TimedLoginEnable</term> <listitem> <synopsis>TimedLoginEnable=false</synopsis> - <para>If the user given in <filename>TimedLogin</filename> should be logged in after a number of seconds (set with <filename>TimedLoginDelay</filename>) of inactivity on the login screen. This is useful for public access terminals or perhaps even home use. If the user uses the keyboard or browses the menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or 30 seconds, whichever is higher. If the user does not enter a username but just hits the ENTER key while the login program is requesting the username, then GDM will assume the user wants to login immediately as the timed user. Note that no password will be asked for this user so you should be careful, although if using PAM it can be configured to require password entry before allowing login.</para> + <para> + If the user given in <filename>TimedLogin</filename> should be + logged in after a number of seconds (set with + <filename>TimedLoginDelay</filename>) of inactivity on the + login screen. This is useful for public access terminals or + perhaps even home use. If the user uses the keyboard or + browses the menus, the timeout will be reset to + <filename>TimedLoginDelay</filename> or 30 seconds, whichever + is higher. If the user does not enter a username but just + hits the ENTER key while the login program is requesting the + username, then GDM will assume the user wants to login + immediately as the timed user. Note that no password will be + asked for this user so you should be careful, although if using + PAM it can be configured to require password entry before + allowing login. + </para> </listitem> </varlistentry> @@ -772,7 +1054,14 @@ PostSession/ <term>TimedLogin</term> <listitem> <synopsis>TimedLogin=</synopsis> - <para>This is the user that should be logged in after a specified number of seconds of inactivity. This can never be "root" and gdm will refuse to log in root this way. The same features as for <filename>AutomaticLogin</filename> are supported. The same control chars and piping to a application are supported.</para> + <para> + This is the user that should be logged in after a specified + number of seconds of inactivity. This can never be + "root" and gdm will refuse to log in root this way. + The same features as for <filename>AutomaticLogin</filename> + are supported. The same control chars and piping to a + application are supported. + </para> </listitem> </varlistentry> @@ -780,7 +1069,10 @@ PostSession/ <term>TimedLoginDelay</term> <listitem> <synopsis>TimedLoginDelay=30</synopsis> - <para>This is the delay before the <filename>TimedLogin</filename> user will be logged in. It must be greater then or equal to 10.</para> + <para> + This is the delay before the <filename>TimedLogin</filename> + user will be logged in. It must be greater then or equal to 10. + </para> </listitem> </varlistentry> @@ -788,7 +1080,16 @@ PostSession/ <term>User</term> <listitem> <synopsis>User=gdm</synopsis> - <para>The username under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogs are run. Also see <filename>Group</filename>. This user will have access to all the X authorization files, and perhaps to other internal GDM data and it should not therefore be a user such as nobody, but rather a dedicated user.</para> + <para> + The username under which <command>gdmlogin</command>, + <command>gdmgreeter</command>, + <command>gdmchooser</command> and the internal + failsafe GTK+ dialogs are run. Also see + <filename>Group</filename>. This user will have access to all + the X authorization files, and perhaps to other internal GDM + data and it should not therefore be a user such as nobody, but + rather a dedicated user. + </para> </listitem> </varlistentry> @@ -796,11 +1097,33 @@ PostSession/ <term>UserAuthDir</term> <listitem> <synopsis>UserAuthDir=</synopsis> - <para>The directory where user's <filename>.Xauthority</filename> file should be saved. When nothing is specified the user's home directory is used. This is tilde expanded so you can set it to things like: <filename>~/authdir/</filename>.</para> - - <para>If you do not use the tilde expansion, then the filename created will be random, like in <filename>UserAuthFBDir</filename>. This way many users can have the same authentication directory. For example you might want to set this to <filename>/tmp</filename> when user has the home directory on NFS, since you really don't want cookie files to go over the wire. The users should really have write privileges to this directory, and this directory should really be sticky and all that, just like the <filename>/tmp</filename> directory.</para> - - <para>Normally if this is the users home directory GDM will still refuse to put cookies there if it thinks it is NFS (by testing root-squashing). This can be changed by setting <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false.</para> + <para> + The directory where user's <filename>.Xauthority</filename> + file should be saved. When nothing is specified the user's + home directory is used. This is tilde expanded so you + can set it to things like: <filename>~/authdir/</filename>. + </para> + + <para> + If you do not use the tilde expansion, then the filename + created will be random, like in + <filename>UserAuthFBDir</filename>. This way many users can + have the same authentication directory. For example you might + want to set this to <filename>/tmp</filename> when user has the + home directory on NFS, since you really don't want cookie files + to go over the wire. The users should really have write + privileges to this directory, and this directory should really + be sticky and all that, just like the <filename>/tmp</filename> + directory. + </para> + + <para> + Normally if this is the users home directory GDM will still + refuse to put cookies there if it thinks it is NFS (by testing + root-squashing). This can be changed by setting + <filename>NeverPlaceCookiesOnNFS</filename> in the + <filename>[security]</filename> section to false. + </para> </listitem> </varlistentry> @@ -808,7 +1131,11 @@ PostSession/ <term>UserAuthFBDir</term> <listitem> <synopsis>UserAuthFBDir=/tmp</synopsis> - <para>If GDM fails to update the user's <filename>.Xauthority</filename> file a fallback cookie is created in this directory.</para> + <para> + If GDM fails to update the user's + <filename>.Xauthority</filename> file a fallback cookie is + created in this directory. + </para> </listitem> </varlistentry> @@ -816,7 +1143,9 @@ PostSession/ <term>UserAuthFile</term> <listitem> <synopsis>UserAuthFile=.Xauthority</synopsis> - <para>Name of the file used for storing user cookies.</para> + <para> + Name of the file used for storing user cookies. + </para> </listitem> </varlistentry> @@ -824,7 +1153,14 @@ PostSession/ <term>VTAllocation</term> <listitem> <synopsis>VTAllocation=true</synopsis> - <para>On systems where GDM supports automatic VT (virtual terminal) allocation (currently Linux and FreeBSD only), you can have GDM automatically append the vt argument to the X server executable. This way races that come up from each X server managing it's own vt allocation can be avoided. See also <filename>FirstVT</filename>.</para> + <para> + On systems where GDM supports automatic VT (virtual terminal) + allocation (currently Linux and FreeBSD only), you can have + GDM automatically append the vt argument to the X server + executable. This way races that come up from each X server + managing it's own vt allocation can be avoided. See also + <filename>FirstVT</filename>. + </para> </listitem> </varlistentry> @@ -832,8 +1168,20 @@ PostSession/ <term>XKeepsCrashing</term> <listitem> <synopsis>XKeepsCrashing=<etc>/gdm/XKeepsCrashing</synopsis> - <para>A script to run in case X keeps crashing. This is for running An X configuration or whatever else to make the X configuration work. See the script that came with the distribution for an example. The distributed <filename>XKeepsCrashing</filename> script is tested on Red Hat, but may work elsewhere. Your system integrator should make sure this script is up to date for your particular system.</para> - <para>In case <filename>FailsafeXServer</filename> is setup, that will be tried first. and this only used as a backup if even that X server keeps crashing.</para> + <para> + A script to run in case X keeps crashing. This is for running + An X configuration or whatever else to make the X configuration + work. See the script that came with the distribution for an + example. The distributed <filename>XKeepsCrashing</filename> + script is tested on Red Hat, but may work elsewhere. Your + system integrator should make sure this script is up to date + for your particular system. + </para> + <para> + In case <filename>FailsafeXServer</filename> is setup, that + will be tried first. and this only used as a backup if even + that X server keeps crashing. + </para> </listitem> </varlistentry> @@ -841,7 +1189,13 @@ PostSession/ <term>Xnest</term> <listitem> <synopsis>Xnest=<bin>/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)</synopsis> - <para>The full path and arguments to the Xnest command. This is used for the flexible Xnest displays. This way the user can start new login screens in a nested window. Of course you must have the Xnest display from your X server packages installed for this to work.</para> + <para> + The full path and arguments to the Xnest command. This is used + for the flexible Xnest displays. This way the user can start + new login screens in a nested window. Of course you must have + the Xnest display from your X server packages installed for + this to work. + </para> </listitem> </varlistentry> </variablelist> @@ -857,8 +1211,16 @@ PostSession/ <term>AllowRoot</term> <listitem> <synopsis>AllowRoot=true</synopsis> - <para>Allow root (privileged user) to log in through GDM. Set this to false if you want to disallow such logins.</para> - <para>On systems that support PAM, this parameter is not as useful as you can use PAM to do the same thing, and in fact do even more. However it is still followed, so you should probably leave it true for PAM systems.</para> + <para> + Allow root (privileged user) to log in through GDM. Set this + to false if you want to disallow such logins. + </para> + <para> + On systems that support PAM, this parameter is not as useful + as you can use PAM to do the same thing, and in fact do even + more. However it is still followed, so you should probably + leave it true for PAM systems. + </para> </listitem> </varlistentry> @@ -866,9 +1228,23 @@ PostSession/ <term>AllowRemoteRoot</term> <listitem> <synopsis>AllowRemoteRoot=false</synopsis> - <para>Allow root (privileged user) to log in remotely through GDM. This value should be set to true to allow such logins. Remote logins are any logins that come in through the XDMCP.</para> - <para>On systems that support PAM, this parameter is not as useful since you can use PAM to do the same thing, and do even more.</para> - <para>This value will be overridden and set to false if the <filename>/etc/default/login</filename> file exists and contains "CONSOLE=/dev/login", and set to true if the <filename>/etc/default/login</filename> file exists and contains any other value or no value for CONSOLE.</para> + <para> + Allow root (privileged user) to log in remotely through GDM. + This value should be set to true to allow such logins. + Remote logins are any logins that come in through the XDMCP. + </para> + <para> + On systems that support PAM, this parameter is not as useful + since you can use PAM to do the same thing, and do even + more. + </para> + <para> + This value will be overridden and set to false if the + <filename>/etc/default/login</filename> file exists and + contains "CONSOLE=/dev/login", and set to true if the + <filename>/etc/default/login</filename> file exists and + contains any other value or no value for CONSOLE. + </para> </listitem> </varlistentry> @@ -876,8 +1252,16 @@ PostSession/ <term>AllowRemoteAutoLogin</term> <listitem> <synopsis>AllowRemoteAutoLogin=false</synopsis> - <para>Allow the timed login to work remotely. That is, remote connections through XDMCP will be allowed to log into the "TimedLogin" user by letting the login window time out, just like the local user on the first console.</para> - <para>Note that this can make a system quite insecure, and thus is off by default.</para> + <para> + Allow the timed login to work remotely. That is, remote + connections through XDMCP will be allowed to log into the + "TimedLogin" user by letting the login window time + out, just like the local user on the first console. + </para> + <para> + Note that this can make a system quite insecure, and thus is + off by default. + </para> </listitem> </varlistentry> @@ -885,7 +1269,16 @@ PostSession/ <term>CheckDirOwner</term> <listitem> <synopsis>CheckDirOwner=true</synopsis> - <para>By default GDM checks the ownership of the home directories before writing to them, this prevents security issues in case of bad setup. However in some instances home directories will be owned by a different user and in this case it is necessary to turn this option on. You will also most likely have to turn the <filename>RelaxPermissions</filename> key to at least value 1 since in such a scenario home directories are likely to be group writable. Supported since 2.6.0.4.</para> + <para> + By default GDM checks the ownership of the home directories + before writing to them, this prevents security issues in case + of bad setup. However in some instances home directories will + be owned by a different user and in this case it is necessary + to turn this option on. You will also most likely have to + turn the <filename>RelaxPermissions</filename> key to at least + value 1 since in such a scenario home directories are likely + to be group writable. Supported since 2.6.0.4. + </para> </listitem> </varlistentry> @@ -893,7 +1286,15 @@ PostSession/ <term>DisallowTCP</term> <listitem> <synopsis>DisallowTCP=true</synopsis> - <para>If true, then always append <filename>-nolisten tcp</filename> to the command line of local X servers, thus disallowing TCP connection. This is useful if you do not care for allowing remote connections, since the X protocol could really be potentially a security hazard to leave open, even though no known security problems exist.</para> + <para> + If true, then always append <filename>-nolisten tcp</filename> + to the command line + of local X servers, thus disallowing TCP connection. This is + useful if you do not care for allowing remote connections, + since the X protocol could really be potentially a security + hazard to leave open, even though no known security problems + exist. + </para> </listitem> </varlistentry> @@ -901,7 +1302,16 @@ PostSession/ <term>NeverPlaceCookiesOnNFS</term> <listitem> <synopsis>NeverPlaceCookiesOnNFS=true</synopsis> - <para>Normally if this is true (which is by default), GDM will not place cookies into the users home directory if this directory is on NFS. Well, GDM will consider any filesystem with root-squashing an NFS filesystem. Sometimes however the remote file system can have root squashing and be safe (perhaps by using encryption). In this case set this to 'false'. Note that this option appeared in version 2.4.4.4 and is ignored in previous versions.</para> + <para> + Normally if this is true (which is by default), GDM will not + place cookies into the users home directory if this directory + is on NFS. Well, GDM will consider any filesystem with + root-squashing an NFS filesystem. Sometimes however the remote + file system can have root squashing and be safe (perhaps by + using encryption). In this case set this to 'false'. Note + that this option appeared in version 2.4.4.4 and is ignored in + previous versions. + </para> </listitem> </varlistentry> @@ -909,7 +1319,18 @@ PostSession/ <term>PasswordRequired</term> <listitem> <synopsis>PasswordRequired=false</synopsis> - <para>If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be passed as a flag to pam_authenticate and pam_acct_mgmt, disallowing NULL password. This setting will only take effect if PAM is being used by GDM. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains "PASSREQ=[YES|NO]". If the <filename>/etc/default/login</filename> file exists, but contains no value for PASSREQ, the value as defined in the GDM configuration will be used.</para> + <para> + If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be + passed as a flag to pam_authenticate and pam_acct_mgmt, + disallowing NULL password. This setting will only take + effect if PAM is being used by GDM. This value will be + overridden with the value from + <filename>/etc/default/login</filename> if it contains + "PASSREQ=[YES|NO]". If the + <filename>/etc/default/login</filename> file exists, but + contains no value for PASSREQ, the value as defined in the GDM + configuration will be used. + </para> </listitem> </varlistentry> @@ -917,13 +1338,26 @@ PostSession/ <term>RelaxPermissions</term> <listitem> <synopsis>RelaxPermissions=0</synopsis> - <para>By default GDM ignores files and directories writable to other users than the owner.</para> + <para> + By default GDM ignores files and directories writable to + other users than the owner. + </para> - <para>Changing the value of RelaxPermissions makes it possible to alter this behavior:</para> + <para> + Changing the value of RelaxPermissions makes it possible to + alter this behavior: + </para> - <para>0 - Paranoia option. Only accepts user owned files and directories.</para> - <para>1 - Allow group writable files and directories.</para> - <para>2 - Allow world writable files and directories.</para> + <para> + 0 - Paranoia option. Only accepts user owned files and + directories. + </para> + <para> + 1 - Allow group writable files and directories. + </para> + <para> + 2 - Allow world writable files and directories. + </para> </listitem> </varlistentry> @@ -931,7 +1365,10 @@ PostSession/ <term>RetryDelay</term> <listitem> <synopsis>RetryDelay=1</synopsis> - <para>The number of seconds GDM should wait before reactivating the entry field after a failed login.</para> + <para> + The number of seconds GDM should wait before reactivating the + entry field after a failed login. + </para> </listitem> </varlistentry> @@ -939,9 +1376,18 @@ PostSession/ <term>UserMaxFile</term> <listitem> <synopsis>UserMaxFile=65536</synopsis> - <para>GDM will refuse to read/write files bigger than this number (specified in bytes).</para> + <para> + GDM will refuse to read/write files bigger than this number + (specified in bytes). + </para> - <para>In addition to the size check GDM is extremely picky about accessing files in user directories. It will not follow symlinks and can optionally refuse to read files and directories writable by other than the owner. See the <filename>RelaxPermissions</filename> option for more info.</para> + <para> + In addition to the size check GDM is extremely picky about + accessing files in user directories. It will not follow + symlinks and can optionally refuse to read files and + directories writable by other than the owner. See the + <filename>RelaxPermissions</filename> option for more info. + </para> </listitem> </varlistentry> </variablelist> @@ -957,9 +1403,18 @@ PostSession/ <term>DisplaysPerHost</term> <listitem> <synopsis>DisplaysPerHost=1</synopsis> - <para>To prevent attackers from filling up the pending queue, GDM will only allow one connection for each remote computer. If you want to provide display services to computers with more than one screen, you should increase the <filename>DisplaysPerHost</filename> value accordingly.</para> + <para> + To prevent attackers from filling up the pending queue, GDM + will only allow one connection for each remote computer. If + you want to provide display services to computers with more + than one screen, you should increase the + <filename>DisplaysPerHost</filename> value accordingly. + </para> - <para>Note that the number of connections from the local computer is unlimited. Only remote connections are limited by this number.</para> + <para> + Note that the number of connections from the local computer is + unlimited. Only remote connections are limited by this number. + </para> </listitem> </varlistentry> @@ -967,11 +1422,21 @@ PostSession/ <term>Enable</term> <listitem> <synopsis>Enable=false</synopsis> - <para>Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM.</para> + <para> + Setting this to true enables XDMCP support allowing remote + displays/X terminals to be managed by GDM. + </para> - <para><filename>gdm</filename> listens for requests on UDP port 177. See the Port option for more information.</para> + <para> + <filename>gdm</filename> listens for requests on UDP port 177. + See the Port option for more information. + </para> - <para>If GDM is compiled to support it, access from remote displays can be controlled using the TCP Wrappers library. The service name is <filename>gdm</filename></para> + <para> + If GDM is compiled to support it, access from remote displays + can be controlled using the TCP Wrappers library. The service + name is <filename>gdm</filename> + </para> <para>Debería añadir <screen>gdm:.my.domain</screen> a su <filename><etc>/hosts.allow</filename>, dependiendo de su configuración de TCP Wrappers. Vea la página del manual <ulink type="help" url="man:hosts.allow">hosts.allow(5)</ulink> para más detalles.</para> @@ -983,9 +1448,22 @@ PostSession/ <term>EnableProxy</term> <listitem> <synopsis>EnableProxy=false</synopsis> - <para>Setting this to true enables support for running XDMCP sessions on a local proxy X server. This may improve the performance of XDMCP sessions, especially on high latency networks, as many X protocol operations can be completed without going over the network.</para> - <para>Note, however, that this mode will significantly increase the burden on the machine hosting the XDMCP sessions</para> - <para>See the <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</filename> options for further details on how to configure support for this feature.</para> + <para> + Setting this to true enables support for running XDMCP sessions + on a local proxy X server. This may improve the performance of + XDMCP sessions, especially on high latency networks, as many + X protocol operations can be completed without going over the + network. + </para> + <para> + Note, however, that this mode will significantly increase the + burden on the machine hosting the XDMCP sessions + </para> + <para> + See the <filename>FlexiProxy</filename> and + <filename>FlexiProxyDisconnect</filename> options for further + details on how to configure support for this feature. + </para> </listitem> </varlistentry> @@ -993,7 +1471,11 @@ PostSession/ <term>HonorIndirect</term> <listitem> <synopsis>HonorIndirect=true</synopsis> - <para>Enables XDMCP INDIRECT choosing (i.e. remote execution of <filename>gdmchooser</filename>) for X-terminals which don't supply their own display browser.</para> + <para> + Enables XDMCP INDIRECT choosing (i.e. remote execution of + <filename>gdmchooser</filename>) for X-terminals which don't + supply their own display browser. + </para> </listitem> </varlistentry> @@ -1001,9 +1483,17 @@ PostSession/ <term>MaxPending</term> <listitem> <synopsis>MaxPending=4</synopsis> - <para>To avoid denial of service attacks, GDM has fixed size queue of pending connections. Only MaxPending displays can start at the same time.</para> + <para> + To avoid denial of service attacks, GDM has fixed size queue + of pending connections. Only MaxPending displays can start at + the same time. + </para> - <para>Please note that this parameter does *not* limit the number of remote displays which can be managed. It only limits the number of displays initiating a connection simultaneously.</para> + <para> + Please note that this parameter does *not* limit the number of + remote displays which can be managed. It only limits the number + of displays initiating a connection simultaneously. + </para> </listitem> </varlistentry> @@ -1011,7 +1501,12 @@ PostSession/ <term>MaxPendingIndirect</term> <listitem> <synopsis>MaxPendingIndirect=4</synopsis> - <para>GDM will only provide <filename>MaxPendingIndirect</filename> displays with host choosers simultaneously. If more queries from different hosts come in, the oldest ones will be forgotten.</para> + <para> + GDM will only provide <filename>MaxPendingIndirect</filename> + displays with host choosers simultaneously. If more queries + from different hosts come in, the oldest ones will be + forgotten. + </para> </listitem> </varlistentry> @@ -1019,7 +1514,11 @@ PostSession/ <term>MaxSessions</term> <listitem> <synopsis>MaxSessions=16</synopsis> - <para>Determines the maximum number of remote display connections which will be managed simultaneously. I.e. the total number of remote displays that can use your host.</para> + <para> + Determines the maximum number of remote display connections + which will be managed simultaneously. I.e. the total number of + remote displays that can use your host. + </para> </listitem> </varlistentry> @@ -1027,11 +1526,22 @@ PostSession/ <term>MaxWait</term> <listitem> <synopsis>MaxWait=30</synopsis> - <para>When GDM is ready to manage a display an ACCEPT packet is sent to it containing a unique session id which will be used in future XDMCP conversations.</para> + <para> + When GDM is ready to manage a display an ACCEPT packet is sent + to it containing a unique session id which will be used in + future XDMCP conversations. + </para> - <para>GDM will then place the session id in the pending queue waiting for the display to respond with a MANAGE request.</para> + <para> + GDM will then place the session id in the pending queue + waiting for the display to respond with a MANAGE request. + </para> - <para>If no response is received within MaxWait seconds, GDM will declare the display dead and erase it from the pending queue freeing up the slot for other displays.</para> + <para> + If no response is received within MaxWait seconds, GDM will + declare the display dead and erase it from the pending queue + freeing up the slot for other displays. + </para> </listitem> </varlistentry> @@ -1039,7 +1549,16 @@ PostSession/ <term>MaxWaitIndirect</term> <listitem> <synopsis>MaxWaitIndirect=30</synopsis> - <para>The MaxWaitIndirect parameter determines the maximum number of seconds between the time where a user chooses a host and the subsequent indirect query where the user is connected to the host. When the timeout is exceeded, the information about the chosen host is forgotten and the indirect slot freed up for other displays. The information may be forgotten earlier if there are more hosts trying to send indirect queries then <filename>MaxPendingIndirect</filename>.</para> + <para> + The MaxWaitIndirect parameter determines the maximum number of + seconds between the time where a user chooses a host and the + subsequent indirect query where the user is connected to the + host. When the timeout is exceeded, the information about the + chosen host is forgotten and the indirect slot freed up for + other displays. The information may be forgotten earlier if + there are more hosts trying to send indirect queries then + <filename>MaxPendingIndirect</filename>. + </para> </listitem> </varlistentry> @@ -1047,7 +1566,11 @@ PostSession/ <term>Port</term> <listitem> <synopsis>Port=177</synopsis> - <para>The UDP port number <filename>gdm</filename> should listen to for XDMCP requests. Don't change this unless you know what you are doing.</para> + <para> + The UDP port number <filename>gdm</filename> should listen to + for XDMCP requests. Don't change this unless you know what + you are doing. + </para> </listitem> </varlistentry> @@ -1055,9 +1578,23 @@ PostSession/ <term>PingIntervalSeconds</term> <listitem> <synopsis>PingIntervalSeconds=15</synopsis> - <para>Interval in which to ping the X server in seconds. If the X server doesn't return before the next time we ping it, the connection is stopped and the session ended. This is a combination of the XDM PingInterval and PingTimeout, but in seconds.</para> + <para> + Interval in which to ping the X server in seconds. If the X + server doesn't return before the next time we ping it, the + connection is stopped and the session ended. This is a + combination of the XDM PingInterval and PingTimeout, but in + seconds. + </para> - <para>Note that GDM in the past used to have a <filename>PingInterval</filename> configuration key which was also in minutes. For most purposes you'd want this setting to be lower then one minute however since in most cases where XDMCP would be used (such as terminal labs), a lag of more than 15 or so seconds would really mean that the terminal was turned off or restarted and you would want to end the session.</para> + <para> + Note that GDM in the past used to have a + <filename>PingInterval</filename> configuration key which was + also in minutes. For most purposes you'd want this setting + to be lower then one minute however since in most cases where + XDMCP would be used (such as terminal labs), a lag of more + than 15 or so seconds would really mean that the terminal was + turned off or restarted and you would want to end the session. + </para> </listitem> </varlistentry> @@ -1065,9 +1602,24 @@ PostSession/ <term>ProxyReconnect</term> <listitem> <synopsis>FlexiProxyReconnect=</synopsis> - <para>Setting this option enables experimental support for session migration with XDMCP sessions. This enables users to disconnect from their session and later reconnect to that same session, possibly from a different terminal.</para> - <para>In order to use this feature, you must have a nested X server available which supports disconnecting from its parent X server and reconnecting to another X server. Currently, the Distributed Multihead X (DMX) server supports this feature to some extent and other projects like NoMachine NX are busy implementing it.</para> - <para>This option should be set to the path of a command which will handle reconnecting the XDMCP proxy to another backend display. A sample implementation for use with DMX is supplied.</para> + <para> + Setting this option enables experimental support for session + migration with XDMCP sessions. This enables users to disconnect + from their session and later reconnect to that same session, + possibly from a different terminal. + </para> + <para> + In order to use this feature, you must have a nested X server + available which supports disconnecting from its parent X server + and reconnecting to another X server. Currently, the Distributed + Multihead X (DMX) server supports this feature to some extent + and other projects like NoMachine NX are busy implementing it. + </para> + <para> + This option should be set to the path of a command which will + handle reconnecting the XDMCP proxy to another backend display. + A sample implementation for use with DMX is supplied. + </para> </listitem> </varlistentry> @@ -1075,7 +1627,10 @@ PostSession/ <term>ProxyXServer</term> <listitem> <synopsis>ProxyXServer=</synopsis> - <para>The X server command line for a XDMCP proxy. Any nested X server like Xnest, Xephr or Xdmx should work fairly well.</para> + <para> + The X server command line for a XDMCP proxy. Any nested X server + like Xnest, Xephr or Xdmx should work fairly well. + </para> </listitem> </varlistentry> @@ -1083,7 +1638,18 @@ PostSession/ <term>Willing</term> <listitem> <synopsis>Willing=<etc>/gdm/Xwilling</synopsis> - <para>When the machine sends a WILLING packet back after a QUERY it sends a string that gives the current status of this server. The default message is the system ID, but it is possible to create a script that displays customized message. If this script doesn't exist or this key is empty the default message is sent. If this script succeeds and produces some output, the first line of it's output is sent (and only the first line). It runs at most once every 3 seconds to prevent possible denial of service by flooding the machine with QUERY packets.</para> + <para> + When the machine sends a WILLING packet back after a QUERY it + sends a string that gives the current status of this server. + The default message is the system ID, but it is possible to + create a script that displays customized message. If this + script doesn't exist or this key is empty the default message + is sent. If this script succeeds and produces some output, + the first line of it's output is sent (and only the first + line). It runs at most once every 3 seconds to prevent + possible denial of service by flooding the machine with QUERY + packets. + </para> </listitem> </varlistentry> </variablelist> @@ -1099,7 +1665,14 @@ PostSession/ <term>AllowGtkThemeChange</term> <listitem> <synopsis>AllowGtkThemeChange=true</synopsis> - <para>If to allow changing the GTK+ (widget) theme from the greeter. Currently this only affects the standard greeter as the graphical greeter does not yet have this ability. The theme will stay in effect on this display until changed and will affect all the other windows that are put up by GDM. Supported since 2.5.90.2.</para> + <para> + If to allow changing the GTK+ (widget) theme from the greeter. + Currently this only affects the standard greeter as the + graphical greeter does not yet have this ability. + The theme will stay in effect on this display until changed + and will affect all the other windows that are put up by GDM. + Supported since 2.5.90.2. + </para> </listitem> </varlistentry> @@ -1107,7 +1680,11 @@ PostSession/ <term>GtkRC</term> <listitem> <synopsis>GtkRC=</synopsis> - <para>Path to a <filename>gtkrc</filename> to read when GDM puts up a window. You should really now use the <filename>GtkTheme</filename> key for just setting a theme.</para> + <para> + Path to a <filename>gtkrc</filename> to read when GDM puts up + a window. You should really now use the + <filename>GtkTheme</filename> key for just setting a theme. + </para> </listitem> </varlistentry> @@ -1115,7 +1692,11 @@ PostSession/ <term>GtkTheme</term> <listitem> <synopsis>GtkTheme=Default</synopsis> - <para>A name of an installed theme to use by default. It will be used in the greeter, chooser and all other GUI windows put up by GDM. Supported since 2.5.90.2.</para> + <para> + A name of an installed theme to use by default. It will be + used in the greeter, chooser and all other GUI windows put up + by GDM. Supported since 2.5.90.2. + </para> </listitem> </varlistentry> @@ -1123,7 +1704,14 @@ PostSession/ <term>GtkThemesToAllow</term> <listitem> <synopsis>GtkThemesToAllow=all</synopsis> - <para>Comma separated list of themes to allow. These must be the names of the themes installed in the standard locations for GTK+ themes. You can also specify 'all' to allow all installed themes. This is related to the <filename>AllowGtkThemeChange</filename> key. Supported since 2.5.90.2.</para> + <para> + Comma separated list of themes to allow. These must be the + names of the themes installed in the standard locations for + GTK+ themes. You can also specify 'all' to allow all installed + themes. This is related to the + <filename>AllowGtkThemeChange</filename> key. Supported since + 2.5.90.2. + </para> </listitem> </varlistentry> @@ -1131,7 +1719,11 @@ PostSession/ <term>MaxIconWidth</term> <listitem> <synopsis>MaxIconWidth=128</synopsis> - <para>Specifies the maximum icon width (in pixels) that the face browser will display. Icons larger than this will be scaled. This also affects icons in the XDMCP chooser.</para> + <para> + Specifies the maximum icon width (in pixels) that the face + browser will display. Icons larger than this will be scaled. + This also affects icons in the XDMCP chooser. + </para> </listitem> </varlistentry> @@ -1139,7 +1731,11 @@ PostSession/ <term>MaxIconHeight</term> <listitem> <synopsis>MaxIconHeight=128</synopsis> - <para>Specifies the maximum icon height (in pixels) that the face browser will display. Icons larger than this will be scaled. This also affects icons in the XDMCP chooser.</para> + <para> + Specifies the maximum icon height (in pixels) that the face + browser will display. Icons larger than this will be scaled. + This also affects icons in the XDMCP chooser. + </para> </listitem> </varlistentry> </variablelist> @@ -1155,7 +1751,13 @@ PostSession/ <term>BackgroundColor</term> <listitem> <synopsis>BackgroundColor=#76848F</synopsis> - <para>If the BackgroundType is 2, use this color in the background of the greeter. Also use it as the back of transparent images set on the background and if the BackgroundRemoteOnlyColor is set and this is a remote display. This only affects the GTK+ Greeter.</para> + <para> + If the BackgroundType is 2, use this color in the background + of the greeter. Also use it as the back of transparent images + set on the background and if the BackgroundRemoteOnlyColor + is set and this is a remote display. + This only affects the GTK+ Greeter. + </para> </listitem> </varlistentry> @@ -1163,7 +1765,10 @@ PostSession/ <term>BackgroundProgramInitialDelay</term> <listitem> <synopsis>BackgroundProgramInitialDelay=30</synopsis> - <para>The background application will be started after at least that many seconds of inactivity.</para> + <para> + The background application will be started after at least that + many seconds of inactivity. + </para> </listitem> </varlistentry> @@ -1171,7 +1776,12 @@ PostSession/ <term>RestartBackgroundProgram</term> <listitem> <synopsis>RestartBackgroundProgram=true</synopsis> - <para>If set the background application will be restarted when it has exited, after the delay described below has elapsed. This option can be useful when you wish to run a screen saver application when no user is using the computer.</para> + <para> + If set the background application will be restarted when it has + exited, after the delay described below has elapsed. This + option can be useful when you wish to run a screen saver + application when no user is using the computer. + </para> </listitem> </varlistentry> @@ -1179,7 +1789,10 @@ PostSession/ <term>BackgroundProgramRestartDelay</term> <listitem> <synopsis>BackgroundProgramRestartDelay=30</synopsis> - <para>The background application will be restarted after at least that many seconds of inactivity.</para> + <para> + The background application will be restarted after at least that + many seconds of inactivity. + </para> </listitem> </varlistentry> @@ -1187,7 +1800,11 @@ PostSession/ <term>BackgroundImage</term> <listitem> <synopsis>BackgroundImage=somefile.png</synopsis> - <para>If the BackgroundType is 1, then display this file as the background in the greeter. This only affects the GTK+ Greeter.</para> + <para> + If the BackgroundType is 1, then display this file as the + background in the greeter. This only affects the GTK+ + Greeter. + </para> </listitem> </varlistentry> @@ -1195,7 +1812,14 @@ PostSession/ <term>BackgroundProgram</term> <listitem> <synopsis>BackgroundProgram=<bin>/xeyes</synopsis> - <para>If set this command will be run in the background while the login window is being displayed. Note that not all applications will run this way, since GDM does not usually have a home directory. You could set up home directory for the GDM user if you wish to run applications which require it. This only affects the GTK+ Greeter.</para> + <para> + If set this command will be run in the background while + the login window is being displayed. Note that not all + applications will run this way, since GDM does not usually have + a home directory. You could set up home directory for the + GDM user if you wish to run applications which require it. + This only affects the GTK+ Greeter. + </para> </listitem> </varlistentry> @@ -1203,7 +1827,12 @@ PostSession/ <term>BackgroundRemoteOnlyColor</term> <listitem> <synopsis>BackgroundRemoteOnlyColor=true</synopsis> - <para>On remote displays only set the color background. This is to make network load lighter. The <filename>BackgroundProgram</filename> is also not run. This only affects the GTK+ Greeter.</para> + <para> + On remote displays only set the color background. This is to + make network load lighter. The + <filename>BackgroundProgram</filename> is also not run. This + only affects the GTK+ Greeter. + </para> </listitem> </varlistentry> @@ -1211,7 +1840,10 @@ PostSession/ <term>BackgroundScaleToFit</term> <listitem> <synopsis>BackgroundScaleToFit=true</synopsis> - <para>Scale background image to fit the screen. This only affects the GTK+ Greeter.</para> + <para> + Scale background image to fit the screen. This only affects + the GTK+ Greeter. + </para> </listitem> </varlistentry> @@ -1219,7 +1851,10 @@ PostSession/ <term>BackgroundType</term> <listitem> <synopsis>BackgroundType=2</synopsis> - <para>The type of background to set. 0 is none, 1 is image and color, 2 is color and 3 is image. This only affects the GTK+ Greeter.</para> + <para> + The type of background to set. 0 is none, 1 is image and color, + 2 is color and 3 is image. This only affects the GTK+ Greeter. + </para> </listitem> </varlistentry> @@ -1227,7 +1862,13 @@ PostSession/ <term>Browser</term> <listitem> <synopsis>Browser=true</synopsis> - <para>Set to true to enable the face browser. See the ``The GTK+ Greeter'' section for more information on the face browser. This option only works for the GTK+ Greeter. For the Themed Greeter, the face browser is enabled by choosing a theme which includes a face browser</para> + <para> + Set to true to enable the face browser. See the + ``The GTK+ Greeter'' section for more information on the + face browser. This option only works for the GTK+ Greeter. + For the Themed Greeter, the face browser is enabled by + choosing a theme which includes a face browser + </para> </listitem> </varlistentry> @@ -1235,7 +1876,11 @@ PostSession/ <term>ChooserButton</term> <listitem> <synopsis>ChooserButton=true</synopsis> - <para>If true, add a chooser button to the Actions menu that will restart the current X server with a chooser. XDMCP does not need to be enabled on the local computer for this to work.</para> + <para> + If true, add a chooser button to the Actions menu that will + restart the current X server with a chooser. XDMCP does not + need to be enabled on the local computer for this to work. + </para> </listitem> </varlistentry> @@ -1243,7 +1888,14 @@ PostSession/ <term>ConfigAvailable</term> <listitem> <synopsis>ConfigAvailable=false</synopsis> - <para>If true, allows the configurator to be run from the greeter. Note that the user will need to type in the root password before the configurator will be started. This is set to false by default for additional security. See the <filename>Configurator</filename> option in the daemon section.</para> + <para> + If true, allows the configurator to be run from the greeter. + Note that the user will need to type in the root password + before the configurator will be started. This is set to + false by default for additional security. See the + <filename>Configurator</filename> option in the daemon + section. + </para> </listitem> </varlistentry> @@ -1285,11 +1937,18 @@ PostSession/ <synopsis>GlobalFaceDir=<share>/pixmaps/faces/</synopsis> <para>Directorio para todo el sistema para los archivos de rostros. El administrador del sistema puede colocar iconos para los usuarios aquí sin tocar los directorios personales. Los rostros se llaman como los nombres de sus usuarios.</para> - <para>I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the face icon for the user ``johndoe''. No image format extension should be specified.</para> + <para> + I.e. <filename><GlobalFaceDir>/johndoe</filename> would + contain the face icon for the user ``johndoe''. No image format + extension should be specified. + </para> <para>Las imágenes de los rostros deben almacenarse en un formato soportado por gdk-pixbuf y deben tener permiso de lectura para el usuario GDM.</para> - <para>A user's own icon file will always take precedence over the sysadmin provided one.</para> + <para> + A user's own icon file will always take precedence over the + sysadmin provided one. + </para> </listitem> </varlistentry> @@ -1297,7 +1956,11 @@ PostSession/ <term>GraphicalTheme</term> <listitem> <synopsis>GraphicalTheme=circles</synopsis> - <para>The graphical theme that the Themed Greeter should use. it should refer to a directory in the theme directory set by <filename>GraphicalThemeDir</filename>.</para> + <para> + The graphical theme that the Themed Greeter should use. it + should refer to a directory in the theme directory set by + <filename>GraphicalThemeDir</filename>. + </para> </listitem> </varlistentry> @@ -1313,7 +1976,14 @@ PostSession/ <term>GraphicalThemeRand</term> <listitem> <synopsis>GraphicalThemeRand=false</synopsis> - <para>Whether the graphical greeter will use Only One Theme or Random Theme mode. Only One Theme mode uses themes listed by <filename>GraphicalTheme</filename>, Random Themes mode uses themes listed by <filename>GraphicalThemes</filename>. A value of false sets greeter to use Only One Theme mode, a value of true sets the greeter to use Random Theme mode.</para> + <para> + Whether the graphical greeter will use Only One Theme or Random + Theme mode. Only One Theme mode uses themes listed by + <filename>GraphicalTheme</filename>, Random Themes mode uses + themes listed by <filename>GraphicalThemes</filename>. A value + of false sets greeter to use Only One Theme mode, a value of + true sets the greeter to use Random Theme mode. + </para> </listitem> </varlistentry> @@ -1321,7 +1991,10 @@ PostSession/ <term>GraphicalThemeDir</term> <listitem> <synopsis>GraphicalThemeDir=<share>/gdm/themes/</synopsis> - <para>The directory where themes for the Themed Greeter are installed.</para> + <para> + The directory where themes for the Themed Greeter are + installed. + </para> </listitem> </varlistentry> @@ -1329,7 +2002,10 @@ PostSession/ <term>GraphicalThemedColor</term> <listitem> <synopsis>GraphicalThemedColor=#76848F</synopsis> - <para>Use this color in the background of the Themed Greeter. This only affects the Themed Greeter.</para> + <para> + Use this color in the background of the Themed Greeter. + This only affects the Themed Greeter. + </para> </listitem> </varlistentry> @@ -1337,7 +2013,13 @@ PostSession/ <term>InfoMsgFile</term> <listitem> <synopsis>InfoMsgFile=/path/to/infofile</synopsis> - <para>If present and /path/to/infofile specifies an existing and readable text file (e.g. <etc>/infomsg.txt) the contents of the file will be displayed in a modal dialog box before the user is allowed to login. This works both with the standard and the themable greeters.</para> + <para> + If present and /path/to/infofile specifies an existing and + readable text file (e.g. <etc>/infomsg.txt) the contents + of the file will be displayed in a modal dialog box before the + user is allowed to login. This works both with the standard + and the themable greeters. + </para> </listitem> </varlistentry> @@ -1345,7 +2027,13 @@ PostSession/ <term>InfoMsgFont</term> <listitem> <synopsis>InfoMsgFont=fontspec</synopsis> - <para>If present and InfoMsgFile (see above) is used, this specifies the font to use when displaying the contents of the InfoMsgFile text file. For example fontspec could be Sans 24 to get a sans serif font of size 24 points. This works both with the standard and the themable greeters.</para> + <para> + If present and InfoMsgFile (see above) is used, this specifies + the font to use when displaying the contents of the InfoMsgFile + text file. For example fontspec could be Sans 24 to get a + sans serif font of size 24 points. + This works both with the standard and the themable greeters. + </para> </listitem> </varlistentry> @@ -1354,7 +2042,11 @@ PostSession/ <term>LocaleFile</term> <listitem> <synopsis>LocaleFile=<etc>/gdm/locale.alias</synopsis> - <para>File in format similar to the GNU locale format with entries for all supported languages on the system. The format is described above or in a comment inside that file.</para> + <para> + File in format similar to the GNU locale format with entries + for all supported languages on the system. The format is + described above or in a comment inside that file. + </para> </listitem> </varlistentry> @@ -1370,7 +2062,13 @@ PostSession/ <term>Logo</term> <listitem> <synopsis>Logo=<share>/pixmaps/gnome-logo-large.png</synopsis> - <para>Image file to display in the logo box. The file must be in an gdk-pixbuf supported format and it must be readable by the GDM user. If no file is specified the logo feature is disabled. This only affects the GTK+ Greeter.</para> + <para> + Image file to display in the logo box. The file must be + in an gdk-pixbuf supported format and it must be readable by + the GDM user. If no file is specified the logo feature + is disabled. + This only affects the GTK+ Greeter. + </para> </listitem> </varlistentry> @@ -1378,7 +2076,13 @@ PostSession/ <term>ChooserButtonLogo</term> <listitem> <synopsis>ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png</synopsis> - <para>Image file to display in the file chooser button in <command>gdmsetup</command>. This key is modified by <command>gdmsetup</command> and should not be manually modified by the user. This only affects the Login Window Preferences (<command>gdmsetup</command>).</para> + <para> + Image file to display in the file chooser button in + <command>gdmsetup</command>. This key is modified by + <command>gdmsetup</command> and should not be manually + modified by the user. This only affects the Login Window + Preferences (<command>gdmsetup</command>). + </para> </listitem> </varlistentry> @@ -1386,7 +2090,13 @@ PostSession/ <term>MinimalUID</term> <listitem> <synopsis>MinimalUID=100</synopsis> - <para>The minimal UID that GDM should consider a user. All users with a lower UID will be excluded from the face browser. See also <filename>Include</filename>, <filename>Exclude</filename>, and <filename>IncludeAll</filename>.</para> + <para> + The minimal UID that GDM should consider a user. All + users with a lower UID will be excluded from the face browser. + See also <filename>Include</filename>, + <filename>Exclude</filename>, and + <filename>IncludeAll</filename>. + </para> </listitem> </varlistentry> @@ -1410,7 +2120,12 @@ PostSession/ <term>Quiver</term> <listitem> <synopsis>Quiver=true</synopsis> - <para>Controls whether <command>gdmlogin</command> should shake the display when an incorrect username/password is entered. This only affects the GTK+ Greeter.</para> + <para> + Controls whether <command>gdmlogin</command> should + shake the display when an incorrect username/password is + entered. + This only affects the GTK+ Greeter. + </para> </listitem> </varlistentry> @@ -1434,7 +2149,12 @@ PostSession/ <term>RunBackgroundProgramAlways</term> <listitem> <synopsis>RunBackgroundProgramAlways=false</synopsis> - <para>If this is true then the background application is run always, otherwise it is only run when the <filename>BackgroundType</filename> is 0 (None) This only affects the GTK+ Greeter.</para> + <para> + If this is true then the background application is run always, + otherwise it is only run when the + <filename>BackgroundType</filename> is 0 (None) + This only affects the GTK+ Greeter. + </para> </listitem> </varlistentry> @@ -1442,7 +2162,11 @@ PostSession/ <term>SetPosition</term> <listitem> <synopsis>SetPosition=true</synopsis> - <para>If true the position of the login window of the GTK+ Greeter is determined by <filename>PositionX</filename> / <filename>PositionY</filename>.</para> + <para> + If true the position of the login window of the GTK+ Greeter + is determined by <filename>PositionX</filename> + / <filename>PositionY</filename>. + </para> </listitem> </varlistentry> @@ -1450,7 +2174,10 @@ PostSession/ <term>ShowGnomeFailsafeSession</term> <listitem> <synopsis>ShowGnomeFailsafeSession=true</synopsis> - <para>Should the greeter show the Gnome Failsafe session in th sessions list.</para> + <para> + Should the greeter show the Gnome Failsafe session in th + sessions list. + </para> </listitem> </varlistentry> @@ -1458,7 +2185,15 @@ PostSession/ <term>ShowLastSession</term> <listitem> <synopsis>ShowLastSession=true</synopsis> - <para>Should the greeter show the 'Last' session in the session list. If this is off, then GDM is in the so called 'switchdesk' mode which for example Red Hat uses. That is, the users can't pick the last session and will just then get the default session (see <filename>DefaultSession</filename>) unless then pick something else for this session only. So if this is off, this really circumvents saving of the last session.</para> + <para> + Should the greeter show the 'Last' session in the session list. + If this is off, then GDM is in the so called 'switchdesk' mode + which for example Red Hat uses. That is, the users can't pick + the last session and will just then get the default session + (see <filename>DefaultSession</filename>) unless then pick + something else for this session only. So if this is off, this + really circumvents saving of the last session. + </para> </listitem> </varlistentry> @@ -1466,7 +2201,10 @@ PostSession/ <term>ShowXtermFailsafeSession</term> <listitem> <synopsis>ShowXtermFailsafeSession=true</synopsis> - <para>Should the greeter show the Xterm Failsafe session in the sessions list.</para> + <para> + Should the greeter show the Xterm Failsafe session in the + sessions list. + </para> </listitem> </varlistentry> @@ -1474,7 +2212,12 @@ PostSession/ <term>SoundOnLogin</term> <listitem> <synopsis>SoundOnLogin=true</synopsis> - <para>If true, the greeter will play a sound or beep when it is ready for a login. See also the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0.</para> + <para> + If true, the greeter will play a sound or beep when it is + ready for a login. See also the + <filename>SoundOnLoginFile</filename> key. + Supported since 2.5.90.0. + </para> </listitem> </varlistentry> @@ -1482,7 +2225,11 @@ PostSession/ <term>SoundOnLoginSuccess</term> <listitem> <synopsis>SoundOnLoginSuccess=true</synopsis> - <para>If true, the greeter will play a sound after a successful login attempt. See also the <filename>SoundOnLoginSuccessFile</filename> key.</para> + <para> + If true, the greeter will play a sound after a successful login + attempt. See also the + <filename>SoundOnLoginSuccessFile</filename> key. + </para> </listitem> </varlistentry> @@ -1490,7 +2237,11 @@ PostSession/ <term>SoundOnLoginFailure</term> <listitem> <synopsis>SoundOnLoginFailure=true</synopsis> - <para>If true, the greeter will play a sound after a failed login attempt. See also the <filename>SoundOnLoginFailureFile</filename> key.</para> + <para> + If true, the greeter will play a sound after a failed login + attempt. See also the + <filename>SoundOnLoginFailureFile</filename> key. + </para> </listitem> </varlistentry> @@ -1498,7 +2249,15 @@ PostSession/ <term>SoundOnLoginFile</term> <listitem> <synopsis>SoundOnLoginFile=/path/to/sound.wav</synopsis> - <para>The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) instead of a beep when the greeter is ready for a login. See also the <filename>SoundOnLogin</filename> key and the <filename>SoundProgram</filename> key. Supported since 2.5.90.0.</para> + <para> + The file that will be played using the specified sound + application (by default that is + <filename>/usr/bin/play</filename>) instead of a beep when the + greeter is ready for a login. See also the + <filename>SoundOnLogin</filename> key and the + <filename>SoundProgram</filename> key. Supported since + 2.5.90.0. + </para> </listitem> </varlistentry> @@ -1506,7 +2265,13 @@ PostSession/ <term>SoundOnLoginSuccessFile</term> <listitem> <synopsis>SoundOnLoginSuccessFile=/path/to/sound.wav</synopsis> - <para>The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a successful login attempt. See also the <filename>SoundOnLoginSuccess</filename> key and the <filename>SoundProgram</filename> key.</para> + <para> + The file that will be played using the specified sound + application (by default that is + <filename>/usr/bin/play</filename>) after a successful login + attempt. See also the <filename>SoundOnLoginSuccess</filename> + key and the <filename>SoundProgram</filename> key. + </para> </listitem> </varlistentry> @@ -1514,7 +2279,13 @@ PostSession/ <term>SoundOnLoginFailureFile</term> <listitem> <synopsis>SoundOnLoginFailureFile=/path/to/sound.wav</synopsis> - <para>The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a failed login attempt. See also the <filename>SoundOnLoginFailure</filename> key and the <filename>SoundProgram</filename> key.</para> + <para> + The file that will be played using the specified sound + application (by default that is + <filename>/usr/bin/play</filename>) after a failed login + attempt. See also the <filename>SoundOnLoginFailure</filename> + key and the <filename>SoundProgram</filename> key. + </para> </listitem> </varlistentry> @@ -1522,9 +2293,26 @@ PostSession/ <term>SystemMenu</term> <listitem> <synopsis>SystemMenu=true</synopsis> - <para>Turns the Actions menu (which used to be called System menu) on or off. If this is off then one of the actions will be available anywhere. These actions include Shutdown, Restart, Configure, XDMCP chooser and such. All of those can however be turned off individually. Shutdown, Restart and Suspend can be turned off by just setting the corresponding keys to empty. Note that the actions menu is only shown on local logins as it would not be safe or even desirable on remote logins, so you don't have to worry about remote users having any sort of console privileges.</para> - - <para>Note that if this is off none of the actions will be available even if a theme for a graphical greeter mistakenly shows them. Also note that sometimes a graphical theme may not show all the available actions as buttons and you may have to press F10 to see the menu.</para> + <para> + Turns the Actions menu (which used to be called System menu) on + or off. If this is off then one of the actions will be + available anywhere. These actions include Shutdown, Restart, + Configure, XDMCP chooser and such. All of those can however + be turned off individually. Shutdown, Restart and Suspend can + be turned off by just setting the corresponding keys to empty. + Note that the actions menu is only shown on local logins as it + would not be safe or even desirable on remote logins, so you + don't have to worry about remote users having any sort of + console privileges. + </para> + + <para> + Note that if this is off none of the actions will be available + even if a theme for a graphical greeter mistakenly shows them. + Also note that sometimes a graphical theme may not show all + the available actions as buttons and you may have to press + F10 to see the menu. + </para> </listitem> </varlistentry> @@ -1532,7 +2320,10 @@ PostSession/ <term>TitleBar</term> <listitem> <synopsis>TitleBar=true</synopsis> - <para>Display the title bar in the greeter. This only affects the GTK+ Greeter.</para> + <para> + Display the title bar in the greeter. + This only affects the GTK+ Greeter. + </para> </listitem> </varlistentry> @@ -1540,8 +2331,23 @@ PostSession/ <term>Use24Clock</term> <listitem> <synopsis>Use24Clock=auto</synopsis> - <para>Select the use of 24 hour clock. Some locales do not support 12 hour format (like Finnish, that is <filename>fi_FI</filename>), and in those locales this setting has no effect at all.</para> - <para>Possible values are "auto" (default), "true", and "false". If this is set to "auto" or left empty, then time format is chosen from locale settings. Locale settings are based on the language in use, thus it is changed by setting environment variables LANGUAGE (GNU extension), LANG, LC_MESSAGES or LC_ALL in the GDM's runtime environment. Priorities between the mentioned environment variables can be found from your system's C library manual.</para> + <para> + Select the use of 24 hour clock. Some locales do not + support 12 hour format (like Finnish, that is + <filename>fi_FI</filename>), and in those locales this + setting has no effect at all. + </para> + <para> + Possible values are "auto" (default), + "true", and "false". If this is set to + "auto" or left empty, then time format is chosen from + locale settings. Locale settings are based on the language in + use, thus it is changed by setting environment variables + LANGUAGE (GNU extension), LANG, LC_MESSAGES or LC_ALL in the + GDM's runtime environment. Priorities between the mentioned + environment variables can be found from your system's + C library manual. + </para> </listitem> </varlistentry> @@ -1549,7 +2355,10 @@ PostSession/ <term>UseCirclesInEntry</term> <listitem> <synopsis>UseCirclesInEntry=false</synopsis> - <para>Use circles instead of asterisks in the password entry. This may not work with all fonts however.</para> + <para> + Use circles instead of asterisks in the password entry. + This may not work with all fonts however. + </para> </listitem> </varlistentry> @@ -1557,7 +2366,12 @@ PostSession/ <term>UseInvisibleInEntry</term> <listitem> <synopsis>UseInvisibleInEntry=false</synopsis> - <para>Do not show any visual feedback is the password entry. This is the standard in console and xdm. Settings this option discards the <filename>UseCirclesInEntry</filename> option.</para> + <para> + Do not show any visual feedback is the password entry. + This is the standard in console and xdm. Settings this + option discards the <filename>UseCirclesInEntry</filename> + option. + </para> </listitem> </varlistentry> @@ -1575,23 +2389,41 @@ PostSession/ <synopsis>Welcome=Welcome</synopsis> <para>Controla qué texto se muestra junto a la imagen del logotipo en el interfaz estándar. Están soportados los siguientes caracteres de control:</para> - <para>%%— the `%' character</para> + <para> + %% — the `%' character + </para> - <para>%d — display's hostname</para> + <para> + %d — display's hostname + </para> - <para>%h — Fully qualified hostname</para> + <para> + %h — Fully qualified hostname + </para> - <para>%m — machine (processor type)</para> + <para> + %m — machine (processor type) + </para> - <para>%n — Nodename (i.e. hostname without .domain)</para> + <para> + %n — Nodename (i.e. hostname without .domain) + </para> - <para>%r — release (OS version)</para> + <para> + %r — release (OS version) + </para> - <para>%s — sysname (i.e. OS)</para> + <para> + %s — sysname (i.e. OS) + </para> <para>Estas cadenas se usan sólo para inicios de sesión locales. Para inicios de sesión remotos XDMCP se usa <filename>RemoteWelcome</filename>.</para> - <para>In the Themed Greeter the location of this text depends on the theme. Unless the theme uses the stock welcome string somewhere this string will not be displayed at all.</para> + <para> + In the Themed Greeter the location of this text depends on + the theme. Unless the theme uses the stock welcome string + somewhere this string will not be displayed at all. + </para> </listitem> </varlistentry> @@ -1600,7 +2432,11 @@ PostSession/ <term>XineramaScreen</term> <listitem> <synopsis>XineramaScreen=0</synopsis> - <para>If the Xinerama extension is active the login window will be centered on this physical screen (use 0 for the first screen, 1 for the second...).</para> + <para> + If the Xinerama extension is active the login window will be + centered on this physical screen (use 0 for the first screen, + 1 for the second...). + </para> </listitem> </varlistentry> </variablelist> @@ -1616,7 +2452,11 @@ PostSession/ <term>AllowAdd</term> <listitem> <synopsis>AllowAdd=true</synopsis> - <para>If true, allow the user to add arbitrary hosts to the chooser. This way the user could connect to any host that responds to XDMCP queries from the chooser.</para> + <para> + If true, allow the user to add arbitrary hosts to the chooser. + This way the user could connect to any host that responds to + XDMCP queries from the chooser. + </para> </listitem> </varlistentry> @@ -1624,7 +2464,14 @@ PostSession/ <term>Broadcast</term> <listitem> <synopsis>Broadcast=true</synopsis> - <para>If true, the chooser will broadcast a query to the local network and collect responses. This way the chooser will always show all available managers on the network. If you need to add some hosts not local to this network, or if you don't want to use a broadcast, you can list them explicitly in the <filename>Hosts</filename> key.</para> + <para> + If true, the chooser will broadcast a query to the local + network and collect responses. This way the chooser will + always show all available managers on the network. If you + need to add some hosts not local to this network, or if you + don't want to use a broadcast, you can list them explicitly + in the <filename>Hosts</filename> key. + </para> </listitem> </varlistentry> @@ -1632,7 +2479,14 @@ PostSession/ <term>Multicast</term> <listitem> <synopsis>Multicast=true</synopsis> - <para>If true and IPv6 is enabled, the chooser will send a multicast query to the local network and collect responses from the hosts who have joined multicast group. If you don't want to send a multicast, you can specify IPv6 address in the <filename>Hosts </filename> key. The host will respond if it is listening to XDMCP requests and IPv6 is enabled there.</para> + <para> + If true and IPv6 is enabled, the chooser will send a multicast + query to the local network and collect responses from the hosts + who have joined multicast group. If you don't want to send a + multicast, you can specify IPv6 address in the <filename>Hosts + </filename> key. The host will respond if it is listening to + XDMCP requests and IPv6 is enabled there. + </para> </listitem> </varlistentry> @@ -1640,7 +2494,9 @@ PostSession/ <term>MulticastAddr</term> <listitem> <synopsis>MulticastAddr=ff02::1</synopsis> - <para>This is the Link-local Multicast address and is hardcoded here.</para> + <para> + This is the Link-local Multicast address and is hardcoded here. + </para> </listitem> </varlistentry> @@ -1656,7 +2512,11 @@ PostSession/ <term>HostImageDir</term> <listitem> <synopsis>HostImageDir=<share>/hosts</synopsis> - <para>Repository for host icon files. The sysadmin can place icons for remote hosts here and they will appear in <filename>gdmchooser</filename>.</para> + <para> + Repository for host icon files. The sysadmin can place icons + for remote hosts here and they will appear in + <filename>gdmchooser</filename>. + </para> <para>El nombre del archvivo debe coincidir con el nombre completamente cualificado (FQDN) para el host. Los iconos deben almacenarse en un formato soportado por gdk-pixbuf y deben tener permiso de lectura para el usuario de GDM.</para> @@ -1667,7 +2527,14 @@ PostSession/ <term>Hosts</term> <listitem> <synopsis>Hosts=host1,host2</synopsis> - <para>The hosts which should be listed in the chooser. The chooser will only list them if they respond. This is done in addition to broadcast (if <filename>Broadcast</filename> is set), so you need not list hosts on the local network. This is useful if your networking setup doesn't allow all hosts to be reachable by a broadcast packet.</para> + <para> + The hosts which should be listed in the chooser. The chooser + will only list them if they respond. This is done in addition + to broadcast (if <filename>Broadcast</filename> is set), so you + need not list hosts on the local network. This is useful if + your networking setup doesn't allow all hosts to be reachable + by a broadcast packet. + </para> </listitem> </varlistentry> @@ -1675,7 +2542,12 @@ PostSession/ <term>ScanTime</term> <listitem> <synopsis>ScanTime=4</synopsis> - <para>Specifies how many seconds the chooser should wait for replies to its BROADCAST_QUERY. Really this is only the time in which we expect a reply. We will still add hosts to the list even if they reply after this time.</para> + <para> + Specifies how many seconds the chooser should wait for + replies to its BROADCAST_QUERY. Really this is only the time + in which we expect a reply. We will still add hosts to the + list even if they reply after this time. + </para> </listitem> </varlistentry> </variablelist> @@ -1708,9 +2580,33 @@ PostSession/ <sect3 id="serverdefs"> <title>Definiciones del servidor X</title> - <para>To set up X servers, you need to provide GDM with information about the installed X servers. You can have as many different definitions as you wish, each identified with a unique name. The name <filename>Standard</filename> is required. If you do not specify this server, GDM will assume default values for a 'Standard' server and the path given by <filename>daemon/StandardXServer</filename>. <filename>Standard</filename> is used as the default, in situations when no other server has been defined.</para> + <para> + To set up X servers, you need to provide GDM with information about + the installed X servers. You can have as many different definitions + as you wish, each identified with a unique name. The name + <filename>Standard</filename> is required. If you do not specify + this server, GDM will assume default values for a 'Standard' server + and the path given by <filename>daemon/StandardXServer</filename>. + <filename>Standard</filename> is used as the default, + in situations when no other server has been defined. + </para> - <para>Servers are defined by sections named <filename>server-</filename> followed by the identifier of this server. This should be a simple ASCII string with no spaces. The GUI configuration program allows users to edit the servers defined in the GDM configuration files but currently does not allow adding or deleting entries. Like normal configuration options, <filename>server-</filename> sections in the <filename><etc>/gdm/custom.conf</filename> file override values in the <filename><share>/gdm/defaults.conf</filename> file. In other words, if a <filename>server-Standard</filename> section is defined in <filename><etc>/gdm/custom.conf</filename>, then that will be used and the section in the <filename><share>/gdm/defaults.conf</filename> file will be ignored.</para> + <para> + Servers are defined by sections named <filename>server-</filename> + followed by the identifier of this server. This should be a simple + ASCII string with no spaces. The GUI configuration program allows + users to edit the servers defined in the GDM configuration files + but currently does not allow adding or deleting entries. Like + normal configuration options, <filename>server-</filename> + sections in the <filename><etc>/gdm/custom.conf</filename> + file override values in the + <filename><share>/gdm/defaults.conf</filename> file. In other + words, if a <filename>server-Standard</filename> section is defined + in <filename><etc>/gdm/custom.conf</filename>, then that + will be used and the section in the + <filename><share>/gdm/defaults.conf</filename> file will be + ignored. + </para> <variablelist> <title>[server-Standard]</title> @@ -1735,7 +2631,10 @@ PostSession/ <term>flexible</term> <listitem> <synopsis>flexible=true</synopsis> - <para>Indicates if this server is available as a choice when a user wishes to run a flexible, on demand server.</para> + <para> + Indicates if this server is available as a choice when a + user wishes to run a flexible, on demand server. + </para> </listitem> </varlistentry> @@ -1743,7 +2642,18 @@ PostSession/ <term>handled</term> <listitem> <synopsis>handled=true</synopsis> - <para>Indicates that GDM should run the login window on this server and allow a user to log in. If set to false, then GDM will just run this server and wait for it to terminate. This can be useful to run an X terminal using GDM. When this is done you should normally also add <filename>-terminate</filename> to the command line of the server to make the server terminate after each session. Otherwise the control of the slave will never come back to GDM and, for example, soft restarts won't work. This is because GDM assumes there is a login in progress for the entire time this server is active.</para> + <para> + Indicates that GDM should run the login window on this server + and allow a user to log in. If set to false, then GDM will + just run this server and wait for it to terminate. This can be + useful to run an X terminal using GDM. When this is done you + should normally also add <filename>-terminate</filename> to the + command line of the server to make the server terminate after + each session. Otherwise the control of the slave will never + come back to GDM and, for example, soft restarts won't work. + This is because GDM assumes there is a login in progress for + the entire time this server is active. + </para> </listitem> </varlistentry> @@ -1751,7 +2661,11 @@ PostSession/ <term>chooser</term> <listitem> <synopsis>chooser=false</synopsis> - <para>Indicates that GDM should instead of a login window run a chooser on this window and allow the user to choose which server to log into.</para> + <para> + Indicates that GDM should instead of a login window run a + chooser on this window and allow the user to choose which + server to log into. + </para> </listitem> </varlistentry> </variablelist> @@ -1760,9 +2674,30 @@ PostSession/ <sect3 id="localservers"> <title>Configuración de la pantalla X local estática</title> - <para>The static display configuration specifies what displays should be always managed by GDM. GDM will restart the X server on the display if it dies, for example. There may be as many static displays that are managed as you wish, although typically each display is associated with a real display. For example, if a machine has two displays (say display ":0" and display ":1"), then this section can be used to specify that a separate login screen be managed for each screen. Each key in the <filename>[servers]</filename> section corresponds to the display number to be managed. Normally there is only one key, which is the key <filename>0</filename>, which corresponds to the display <filename>:0</filename>.</para> + <para> + The static display configuration specifies what displays should be + always managed by GDM. GDM will restart the X server on the display + if it dies, for example. There may be as many static displays that + are managed as you wish, although typically each display is + associated with a real display. For example, if a machine has two + displays (say display ":0" and display ":1"), + then this section can be used to specify that a separate login + screen be managed for each screen. Each key in the + <filename>[servers]</filename> section corresponds to the display + number to be managed. Normally there is only one key, which is the + key <filename>0</filename>, which corresponds to the display + <filename>:0</filename>. + </para> - <para>The GUI configuration program allows users to edit the static display configuration defined in the GDM configuration files and allows the user to add or delete entries. Like normal configuration options, the <filename>[servers]</filename> section in the <filename><etc>/gdm/custom.conf</filename> file overrides values in the <filename><share>/gdm/defaults.conf</filename> file.</para> + <para> + The GUI configuration program allows users to edit the static + display configuration defined in the GDM configuration files + and allows the user to add or delete entries. Like normal + configuration options, the <filename>[servers]</filename> + section in the <filename><etc>/gdm/custom.conf</filename> + file overrides values in the + <filename><share>/gdm/defaults.conf</filename> file. + </para> <variablelist> <title>[servers]</title> @@ -1771,15 +2706,48 @@ PostSession/ <term><display number></term> <listitem> <synopsis>0=Standard</synopsis> - <para>Control section for local displays. Each line indicates the local display number and the command that needs to be run to start the X server(s).</para> - - <para>The command can either be a path to an X executable, or a name of one of the server definitions. This can be followed by some arguments that should be passed to the X server when executed. The gdm daemon doesn't enforce the numbers to be in order or for them to be "packed". They keyword "inactive" can be used instead of a command to specify that the display should be not managed. This can be used in the <filename><etc>/gdm/custom.conf</filename> to turn off a display that is defined in the <filename><share>/gdm/defaults.conf</filename> file.</para> + <para> + Control section for local displays. Each line indicates + the local display number and the command that needs to + be run to start the X server(s). + </para> + + <para> + The command can either be a path to an X executable, or a name + of one of the server definitions. This can be followed by some + arguments that should be passed to the X server when executed. + The gdm daemon doesn't enforce the numbers to be in order or + for them to be "packed". They keyword + "inactive" can be used instead of a command to + specify that the display should be not managed. This can be + used in the + <filename><etc>/gdm/custom.conf</filename> to turn + off a display that is defined in the + <filename><share>/gdm/defaults.conf</filename> file. + </para> - <para>GDM will splice "<filename>-auth <ServAuthDir>/:n.Xauth :n</filename>", where n is the display number. Inside the command line before all other arguments before running the X server.</para> - - <para>On some systems it is necessary for GDM to know on which virtual consoles to run the X server. In this case, (if running XFree86) add "vt7" to the command line, for example, to run on virtual console 7. However on Linux and FreeBSD this is normally done automatically if the <filename>VTAllocation</filename> key is set.</para> - - <para>Normally you do not need to add a <filename>-nolisten tcp</filename> flag as this is added automatically for local X servers when the <filename>DisallowTCP</filename> option is set.</para> + <para> + GDM will splice "<filename>-auth + <ServAuthDir>/:n.Xauth :n</filename>", where n is + the display number. Inside the command line before all + other arguments before running the X server. + </para> + + <para> + On some systems it is necessary for GDM to know on which + virtual consoles to run the X server. In this case, + (if running XFree86) add "vt7" to the command line, + for example, to run on virtual console 7. However on Linux and + FreeBSD this is normally done automatically if the + <filename>VTAllocation</filename> key is set. + </para> + + <para> + Normally you do not need to add a + <filename>-nolisten tcp</filename> flag as this is added + automatically for local X servers when the + <filename>DisallowTCP</filename> option is set. + </para> </listitem> </varlistentry> @@ -1787,7 +2755,15 @@ PostSession/ <term>priority</term> <listitem> <synopsis>priority=0</synopsis> - <para>Indicates that the X server should be started at a different process priority. Values can be any integer value accepted by the setpriority C library function (normally between -20 and 20) with 0 being the default. For highly interactive applications, -5 yields good responsiveness. The default value is 0 and the setpriority function is not called if the value is 0.</para> + <para> + Indicates that the X server should be started at a + different process priority. Values can be any integer + value accepted by the setpriority C library function + (normally between -20 and 20) with 0 being the default. + For highly interactive applications, -5 yields good + responsiveness. The default value is 0 and the + setpriority function is not called if the value is 0. + </para> </listitem> </varlistentry> </variablelist> @@ -1811,7 +2787,20 @@ Language=es_ES.UTF-8 <para>Normalmente GDM escribirá este archivo cuando el usuario entre por primera vez, y lo reescribirá si el usuario escoge cambiar su valor predeterminado en una entrada subsiguiente.</para> - <para>If the GDM Face Browser is turned, then the file <filename>$HOME/.face</filename> is accessed. This file should be a standard image that GTK+ can read, such as PNG or JPEG. It also must be smaller than the <filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> values defined in the GDM configuration or it will be ignored. Users can run the <command>gdmphotosetup</command> program to specify a face image and it will copy the file to the <filename>$HOME/.face</filename> location and scale it so its longest dimension is not larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> values. <command>gdmphotosetup</command> takes care to not change the aspect ratio of the image.</para> + <para> + If the GDM Face Browser is turned, then the file + <filename>$HOME/.face</filename> is accessed. This file should be a + standard image that GTK+ can read, such as PNG or JPEG. It also must + be smaller than the <filename>MaxIconWidth</filename> and + <filename>MaxIconHeight</filename> values defined in the GDM + configuration or it will be ignored. Users can run the + <command>gdmphotosetup</command> program to specify a face image + and it will copy the file to the <filename>$HOME/.face</filename> + location and scale it so its longest dimension is not larger than the + <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> + values. <command>gdmphotosetup</command> takes care to not change + the aspect ratio of the image. + </para> <para>Las imágenes de rostros pueden colocarse en el directorio global de rostros, que se especifica por la opción de configuración <filename>GlobalFaceDir</filename> (normalmente <filename><share>/pixmaps/faces/</filename>) y el nombre del archivo debería ser el nombre del usuario, opcionalmente con un <filename>.png</filename>, etc. agregado. </para> </sect2> @@ -1827,23 +2816,63 @@ Language=es_ES.UTF-8 <para>Para parar GDM, puede o bien enviar la señal TERM al demonio principal o ejecutar el comando <command>gdm-stop</command> que está en el directorio <filename>/sbin</filename>. Para reiniciar GDM, puede o bien enviar la señal HUP al demonio principal o ejecutar el comando <command>gdm-restart</command> que también está en el directorio <filename>/sbin</filename>. Para reiniciar GDM paro sólo después de que todos los usuarios hayan salido de su sesión puede o bien enviar la señal USR1 al demonio principal o ejecutar el comando <command>gdm-safe-restart</command> que está en el directorio <filename>/sbin</filename> también.</para> - <para>The <command>gdmflexiserver</command> command can be used to start new flexible (on demand) displays if your system supports virtual terminals. This command will normally lock the current session with a screensaver so that the user can safely walk away from the computer and let someone else log in. If more that two flexible displays have started <command>gdmflexiserver</command> will display a pop-up dialog allowing the user to select which session to continue. The user will normally have to enter a password to return to the session. On session exit the system will return to the previous virtual terminal. Run <command>gdmflexiserver --help</command> to get a listing of possible options.</para> + <para> + The <command>gdmflexiserver</command> command can be used to start + new flexible (on demand) displays if your system supports virtual + terminals. This command will normally lock the current session with a + screensaver so that the user can safely walk away from the computer and + let someone else log in. If more that two flexible displays have + started <command>gdmflexiserver</command> will display a pop-up dialog + allowing the user to select which session to continue. The user will + normally have to enter a password to return to the session. On session + exit the system will return to the previous virtual terminal. Run + <command>gdmflexiserver --help</command> to get a listing of possible + options. + </para> </sect2> <sect2 id="fifoprot"> <title>El protocolo FIFO</title> - <para>GDM also provides a FIFO called <filename>.gdmfifo</filename> in the <filename>ServAuthDir</filename> directory (usually <filename><var>/gdm/.gdmfifo</filename>). You must be root to use this protocol, and it is mostly used for internal GDM chatter. It is a very simple protocol where you just echo a command on a single line to this file. It can be used to tell GDM things such as restart, suspend the computer, or restart all X servers next time it has a chance (which would be useful from an X configuration application).</para> - - <para>Full and up to date documentation of the commands and their use is contained in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look for the defines starting with <filename>GDM_SOP_</filename>. The commands which require the pid of the slave as an argument are the ones that are really used for internal communication of the slave with the master and should not be used.</para> + <para> + GDM also provides a FIFO called <filename>.gdmfifo</filename> in the + <filename>ServAuthDir</filename> directory + (usually <filename><var>/gdm/.gdmfifo</filename>). You must be + root to use this protocol, and it is mostly used for internal GDM + chatter. It is a very simple protocol where you just echo a command on + a single line to this file. It can be used to tell GDM things such as + restart, suspend the computer, or restart all X servers next time it has + a chance (which would be useful from an X configuration application). + </para> + + <para> + Full and up to date documentation of the commands and their use is + contained in the GDM source tree in the file + <filename>daemon/gdm.h</filename>. Look for the defines starting with + <filename>GDM_SOP_</filename>. The commands which require the + pid of the slave as an argument are the ones that are really used for + internal communication of the slave with the master and should not be + used. + </para> </sect2> <sect2 id="socketprot"> <title>El protocolo socket</title> - <para>GDM provides a unix domain socket for communication at <filename>/tmp/.gdm_socket</filename>. Using this you can check if GDM is running, the version of the daemon, the current displays that are running and who is logged in on them, and if GDM supports it on your operating system, also the virtual terminals of all the console logins. The <command>gdmflexiserver</command> command uses this protocol, for example, to launch flexible (on-demand) displays.</para> - - <para>gdmflexiserver accepts the following commands with the --command option:</para> + <para> + GDM provides a unix domain socket for communication at + <filename>/tmp/.gdm_socket</filename>. Using this you can check if + GDM is running, the version of the daemon, the current displays that + are running and who is logged in on them, and if GDM supports it on + your operating system, also the virtual terminals of all the console + logins. The <command>gdmflexiserver</command> command uses this + protocol, for example, to launch flexible (on-demand) displays. + </para> + + <para> + gdmflexiserver accepts the following commands with the --command + option: + </para> <screen> ADD_DYNAMIC_DISPLAY @@ -1870,7 +2899,10 @@ UPDATE_CONFIG VERSION </screen> - <para>These are described in detail below, including required arguments, response format, and return codes.</para> + <para> + These are described in detail below, including required arguments, + response format, and return codes. + </para> <sect3 id="adddynamic"> <title>ADD_DYNAMIC_DISPLAY</title> @@ -2438,12 +3470,27 @@ Answers: <sect2 id="bindir_binaries"> <title>Comandos de usuario de GDM</title> - <para>The GDM package provides the following different commands in <filename>bindir</filename> intended to be used by the end-user:</para> + <para> + The GDM package provides the following different commands in + <filename>bindir</filename> intended to be used by the end-user: + </para> <sect3 id="gdmxnestchoosercommandline"> <title>Opciones de línea de comandos de <command>gdmXnestchooser</command> y <command>gdmXnest</command></title> - <para>The <command>gdmXnestchooser</command> command automatically gets the correct display number, sets up access, and runs <command>Xnest</command> with -indirect localhost. This way you get an XDMCP chooser provided by your computer. You can also supply as an argument the hostname whose chooser should be displayed, so <command>gdmXnestchooser somehost</command> will run the XDMCP chooser from host <command>somehost</command> inside an Xnest session. You can make this command do a direct query instead by passing the <command>-d</command> option as well. In addition to the following options, this command also supports standard GNOME options.</para> + <para> + The <command>gdmXnestchooser</command> command automatically gets + the correct display number, sets up access, and runs + <command>Xnest</command> with -indirect localhost. This way you + get an XDMCP chooser provided by your computer. You can also supply + as an argument the hostname whose chooser should be displayed, so + <command>gdmXnestchooser somehost</command> will run the XDMCP + chooser from host <command>somehost</command> inside an Xnest + session. You can make this command do a direct query instead by + passing the <command>-d</command> option as well. In addition to + the following options, this command also supports standard GNOME + options. + </para> <variablelist> <title><command>gdmXnestchooser</command> Command Line Options</title> @@ -2502,15 +3549,46 @@ Answers: <sect3 id="gdmflexichoosercommandline"> <title>Opciones de línea de comandos de <command>gdmflexichooser</command></title> - <para>The <command>gdmflexiserver</command> command provides three features. It can be used to run flexible (on demand) X displays, to run a flexible display via Xnest, and to send commands to the GDM daemon process.</para> + <para> + The <command>gdmflexiserver</command> command provides three + features. It can be used to run flexible (on demand) X displays, + to run a flexible display via Xnest, and to send commands to the + GDM daemon process. + </para> - <para>Starting a flexible X display will normally lock the current session with a screensaver and will redisplay the GDM login screen so a second user can log in. This feature is only available on systems that support virtual terminals and have them enabled. This feature is useful if you are logged in as user A, and user B wants to log in quickly but user A does not wish to log out. The X server takes care of the virtual terminal switching so it works transparently. If there is more than one running display defined with flexible=true, then the user is shown a dialog that displays the currently running sessions. The user can then pick which session to continue and will normally have to enter the password to unlock the screen.</para> + <para> + Starting a flexible X display will normally lock the current session + with a screensaver and will redisplay the GDM login screen so a second + user can log in. This feature is only available on systems that + support virtual terminals and have them enabled. This feature is + useful if you are logged in as user A, and user B wants to log in + quickly but user A does not wish to log out. The X server takes + care of the virtual terminal switching so it works transparently. + If there is more than one running display defined with flexible=true, + then the user is shown a dialog that displays the currently running + sessions. The user can then pick which session to continue and will + normally have to enter the password to unlock the screen. + </para> - <para>Flexible displays started via Xnest works on systems that do not support virtual terminals. This option starts a flexible display in a window in the current session. This does not lock the current session, so is not as secure as a flexible server started via virtual terminals.</para> + <para> + Flexible displays started via Xnest works on systems that do not + support virtual terminals. This option starts a flexible display + in a window in the current session. This does not lock the current + session, so is not as secure as a flexible server started via + virtual terminals. + </para> - <para>The <command>gdmflexiserver --command</command> option provides a way to send commands to the GDM daemon and can be used to debug problems or to change the GDM configuration.</para> + <para> + The <command>gdmflexiserver --command</command> option provides a way + to send commands to the GDM daemon and can be used to debug problems + or to change the GDM configuration. + </para> - <para>In addition to the following options, <command>gdmflexiserver</command> also supports standard GNOME options.</para> + <para> + In addition to the following options, + <command>gdmflexiserver</command> also supports standard GNOME + options. + </para> <variablelist> <title>Opciones de línea de comandos de <command>gdmflexichooser</command></title> @@ -2525,7 +3603,9 @@ Answers: <varlistentry> <term>-n, --xnest</term> <listitem> - <para>Start a flexible X display in Xnest mode</para> + <para> + Start a flexible X display in Xnest mode + </para> </listitem> </varlistentry> @@ -2562,9 +3642,28 @@ Answers: <sect3 id="gdmdynamiccommandline"> <title>Opciones de línea de comandos de <command>gdmdynamic</command></title> - <para>The <command>gdmdynamic</command> command which creates, runs, and removes displays (X servers) on demand.</para> + <para> + The <command>gdmdynamic</command> command which creates, runs, and + removes displays (X servers) on demand. + </para> - <para>Some environments need the ability to tell GDM to create and manage new displays on the fly, where it is not possible to list the possible displays in GDM configuration files. The <command>gdmdynamic</command> command can be used to create a new display on a particular display number, run all newly created displays, or remove a display. The <command>gdmdynamic</command> command can also be used to list all attached displays, or only attached displays that match a pattern. This program is designed to manage multiple simultaneous requests and works to avoid flooding the daemon with requests. If the socket connection is busy, it will sleep and retry a certain number of times that can be tuned with the <command>-t</command> and <command>-s</command> arguments. <command>gdmdynamic</command> returns 1 on normal failure, and returns 2 if it is unable to connect to the daemon. Callers can choose to call again if a return code of 2 is received.</para> + <para> + Some environments need the ability to tell GDM to create and manage new + displays on the fly, where it is not possible to list the possible + displays in GDM configuration files. The <command>gdmdynamic</command> + command can be used to create a new display on a particular display + number, run all newly created displays, or remove a display. The + <command>gdmdynamic</command> command can also be used to list all + attached displays, or only attached displays that match a pattern. + This program is designed to manage multiple simultaneous requests and + works to avoid flooding the daemon with requests. If the socket + connection is busy, it will sleep and retry a certain number of times + that can be tuned with the <command>-t</command> and + <command>-s</command> arguments. <command>gdmdynamic</command> + returns 1 on normal failure, and returns 2 if it is unable to + connect to the daemon. Callers can choose to call again if a + return code of 2 is received. + </para> <variablelist> <title>Opciones de línea de comandos de <command>gdmdynamic</command></title> @@ -2572,70 +3671,105 @@ Answers: <varlistentry> <term/> <listitem> - <para><emphasis>One of the following options can be used per instance:</emphasis></para> + <para><emphasis> + One of the following options can be used per instance: + </emphasis></para> </listitem> </varlistentry> <varlistentry> <term>-a display=server</term> <listitem> - <para>Add a new display configuration. For example, <command>"-a 2=StandardServerTwo"</command><command>"-a 3=/usr/X11R6/bin/X -dev /dev/fb2"</command></para> + <para> + Add a new display configuration. For example, + <command>"-a 2=StandardServerTwo"</command> + <command>"-a 3=/usr/X11R6/bin/X -dev /dev/fb2"</command> + </para> </listitem> </varlistentry> <varlistentry> <term>-r</term> <listitem> - <para>Release (run) all displays waiting in the DISPLAY_CONFIG state.</para> + <para> + Release (run) all displays waiting in the DISPLAY_CONFIG state. + </para> </listitem> </varlistentry> <varlistentry> <term>-d display</term> <listitem> - <para>Delete a display, killing the X server and purging the display configuration. For example, "-d 3".</para> + <para> + Delete a display, killing the X server and purging the + display configuration. For example, "-d 3". + </para> </listitem> </varlistentry> <varlistentry> <term>-l [pattern]</term> <listitem> - <para>List displays via the ATTACHED_SERVERS command. Without a pattern lists all attached displays. With a pattern will match using glob characters '*', '?', and '[]'. For example: <command>"-l Standard*"</command><command>"-l *Xorg*"</command></para> + <para> + List displays via the ATTACHED_SERVERS command. Without a pattern + lists all attached displays. With a pattern will match using glob + characters '*', '?', and '[]'. For example: + <command>"-l Standard*"</command> + <command>"-l *Xorg*"</command> + </para> </listitem> </varlistentry> <varlistentry> <term/> <listitem> - <para><emphasis>These options can be added to the above:</emphasis></para> + <para><emphasis> + These options can be added to the above: + </emphasis></para> </listitem> </varlistentry> <varlistentry> <term>-v</term> <listitem> - <para>Verbose mode. Prinr diagnostic messages about each message sent to GDM.</para> + <para> + Verbose mode. Prinr diagnostic messages about each message sent + to GDM. + </para> </listitem> </varlistentry> <varlistentry> <term>-b</term> <listitem> - <para>Background mode. Fork child to do the work and return immediately.</para> + <para> + Background mode. Fork child to do the work and return immediately. + </para> </listitem> </varlistentry> <varlistentry> <term>-t RETRY</term> <listitem> - <para>If the daemon socket is busy, <command>gdmdynamic</command> will retry to open the connection the specified RETRY number of times. Default value is 15.</para> + <para> + If the daemon socket is busy, <command>gdmdynamic</command> will + retry to open the connection the specified RETRY number of times. + Default value is 15. + </para> </listitem> </varlistentry> <varlistentry> <term>-s SLEEP</term> <listitem> - <para>If the daemon socket is busy, <command>gdmdynamic</command> will sleep an amount of time between retries. A random number of seconds 0-5 is added to the SLEEP value to help ensure that multiple calls to gdmdynamic do not all try to restart at the same time. A SLEEP value of zero causes the sleep time to be 1 second. Default value is 8 seconds.</para> + <para> + If the daemon socket is busy, <command>gdmdynamic</command> will + sleep an amount of time between retries. A random number of + seconds 0-5 is added to the SLEEP value to help ensure that + multiple calls to gdmdynamic do not all try to restart at the + same time. A SLEEP value of zero causes the sleep time to be + 1 second. Default value is 8 seconds. + </para> </listitem> </varlistentry> @@ -2645,31 +3779,64 @@ Answers: <sect3 id="gdmphotosetupcommandline"> <title>Opciones de línea de comandos de <command>gdmphotosetup</command></title> - <para>Allows the user to select an image that will be used as the user's photo by GDM's face browser, if enabled by GDM. The selected file is stored as <filename>~/.face</filename>. This command accepts standard GNOME options.</para> + <para> + Allows the user to select an image that will be used as the user's + photo by GDM's face browser, if enabled by GDM. The selected file + is stored as <filename>~/.face</filename>. This command accepts + standard GNOME options. + </para> </sect3> <sect3 id="gdmthemetestercommandline"> <title>Opciones de línea de comandos de <command>gdmthemetester</command></title> - <para><command>gdmthemetester</command> takes two parameters. The first parameter specifies the environment and the second parameter specifies the path name or the name of a theme to view. This is a tool for viewing a theme outside of GDM. It is useful for testing or viewing themes. <command>gdmthemetester</command> requires that the system support <command>gdmXnest</command>. Note that themes can display differently depending on the theme's "Show mode". <command>gdmthemetester</command> allows viewing the themes in different modes via the environment option. Valid environment values and their meanings follow: <screen> + <para> + <command>gdmthemetester</command> takes two parameters. The first + parameter specifies the environment and the second parameter + specifies the path name or the name of a theme to view. + + This is a tool for viewing a theme outside of GDM. It is useful for + testing or viewing themes. <command>gdmthemetester</command> requires + that the system support <command>gdmXnest</command>. + + Note that themes can display differently depending on the theme's + "Show mode". <command>gdmthemetester</command> allows + viewing the themes in different modes via the environment option. + Valid environment values and their meanings follow: + +<screen> console - In console mode. console-timed - In console non-flexi mode. flexi - In flexi mode. xdmcp - In remote (XDMCP) mode. remote-flexi - In remote (XDMCP) & flexi mode. -</screen></para> +</screen> + </para> </sect3> </sect2> <sect2 id="sbindir_binaries"> <title>Comandos del administrador de GDM</title> - <para>The GDM package provides the following different commands in <filename>sbindir</filename> intended to be used by the root user:</para> + <para> + The GDM package provides the following different commands in + <filename>sbindir</filename> intended to be used by the root user: + </para> <sect3 id="gdmcommandline"> <title>Opciones de línea de comandos de <command>gdm</command> y <command>gdm-binary</command></title> - <para>The <command>gdm</command> command is really just a script which runs the <command>gdm-binary</command>, passing along any options. Before launching <command>gdm-binary</command>, the gdm wrapper script will source the <filename><etc>/profile</filename> file to set the standard system environment variables. In order to better support internationalization, it will also set the LC_MESSAGES environment variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you really need to set some additional environment before launching GDM, you can do so in this script.</para> + <para> + The <command>gdm</command> command is really just a script which + runs the <command>gdm-binary</command>, passing along any options. + Before launching <command>gdm-binary</command>, the gdm wrapper script + will source the <filename><etc>/profile</filename> file to set + the standard system environment variables. In order to better support + internationalization, it will also set the LC_MESSAGES environment + variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you + really need to set some additional environment before launching GDM, + you can do so in this script. + </para> <variablelist> <title>Opciones de línea de comandos de <command>gdm</command> y <command>gdm-binary</command></title> @@ -2691,7 +3858,14 @@ remote-flexi - In remote (XDMCP) & flexi mode. <varlistentry> <term>--no-console</term> <listitem> - <para>Tell the daemon that it should not run anything on the console. This means that none of the local servers from the <filename>[servers]</filename> section will be run, and the console will not be used for communicating errors to the user. An empty <filename>[servers]</filename> section automatically implies this option.</para> + <para> + Tell the daemon that it should not run anything on the console. + This means that none of the local servers from the + <filename>[servers]</filename> section will be run, and the + console will not be used for communicating errors to the user. + An empty <filename>[servers]</filename> section automatically + implies this option. + </para> </listitem> </varlistentry> @@ -2705,7 +3879,10 @@ remote-flexi - In remote (XDMCP) & flexi mode. <varlistentry> <term>--preserve-ld-vars</term> <listitem> - <para>When clearing the environment internally, preserve all variables starting with LD_. This is mostly for debugging purposes.</para> + <para> + When clearing the environment internally, preserve all variables + starting with LD_. This is mostly for debugging purposes. + </para> </listitem> </varlistentry> @@ -2719,7 +3896,18 @@ remote-flexi - In remote (XDMCP) & flexi mode. <varlistentry> <term>--wait-for-go</term> <listitem> - <para>If started with this option, gdm will init, but only start the first local display and then wait for a GO message in the fifo protocol. No greeter will be shown until the GO message is sent. Also flexiserver requests will be denied and XDMCP will not be started until GO is given. This is useful for initialization scripts which wish to start X early, but where you don't yet want the user to start logging in. So the script would send the GO to the fifo once it is ready and GDM will then continue. This functionality was added in version 2.5.90.0.</para> + <para> + If started with this option, gdm will init, but only start the + first local display and then wait for a GO message in the fifo + protocol. No greeter will be shown until the GO message is + sent. Also flexiserver requests will be denied and XDMCP will + not be started until GO is given. This is useful for + initialization scripts which wish to start X early, but where + you don't yet want the user to start logging in. So the script + would send the GO to the fifo once it is ready and GDM will + then continue. This functionality was added in version + 2.5.90.0. + </para> </listitem> </varlistentry> </variablelist> @@ -2728,7 +3916,15 @@ remote-flexi - In remote (XDMCP) & flexi mode. <sect3 id="gdmsetupcommandline"> <title>Opciones de línea de comandos de <command>gdmsetup</command></title> - <para><command>gdmsetup</command> runs a graphical application for modifying the GDM configuration file. Normally on systems that support the PAM userhelper, this is setup such that when you run <command>gdmsetup</command> as an ordinary user, it will first ask you for your root password before starting. Otherwise, this application may only be run as root. This application supports standard GNOME options.</para> + <para> + <command>gdmsetup</command> runs a graphical application for modifying + the GDM configuration file. Normally on systems that support + the PAM userhelper, this is setup such that when you run + <command>gdmsetup</command> as an ordinary user, it will first + ask you for your root password before starting. Otherwise, this + application may only be run as root. This application supports + standard GNOME options. + </para> </sect3> <sect3 id="gdmrestartcommandline"> @@ -2753,18 +3949,35 @@ remote-flexi - In remote (XDMCP) & flexi mode. <sect2 id="libexecdir_binaries"> <title>Comandos internos de GDM</title> - <para>The GDM package provides the following different commands in <filename>libexecdir</filename> intended to be used by the gdm daemon process.</para> + <para> + The GDM package provides the following different commands in + <filename>libexecdir</filename> intended to be used by the gdm + daemon process. + </para> <sect3 id="gdmgreeterlogincommandline"> <title>Opciones de línea de comandos de <command>gdmchooser</command> y <command>gdmlogin</command></title> - <para>The <command>gdmgreeter</command> and <command>gdmlogin</command> are two different login applications, either can be used by GDM. <command>gdmgreeter</command> is themeable with GDM themes while <command>gdmlogin</command> is themable with GTK+ themes. These applications are normally executed by the GDM daemon. Both commands support standard GNOME options.</para> + <para> + The <command>gdmgreeter</command> and <command>gdmlogin</command> + are two different login applications, either can be used by GDM. + <command>gdmgreeter</command> is themeable with GDM themes while + <command>gdmlogin</command> is themable with GTK+ themes. These + applications are normally executed by the GDM daemon. Both commands + support standard GNOME options. + </para> </sect3> <sect3 id="gdmchoosercommandline"> <title>Opciones de línea de comandos de <command>gdmchooser</command></title> - <para>The <command>gdmchooser</command> is the XDMCP chooser application. The <command>gdmchooser</command> is normally executed by the GDM daemon. It supports the following options for XDM compatibility. This command supports standard GNOME options and is found in support standard GNOME options.</para> + <para> + The <command>gdmchooser</command> is the XDMCP chooser application. + The <command>gdmchooser</command> is normally executed by the GDM + daemon. It supports the following options for XDM compatibility. + This command supports standard GNOME options and is found in + support standard GNOME options. + </para> <variablelist> <title>Opciones de línea de comandos de <command>gdmchooser</command></title> @@ -2779,14 +3992,20 @@ remote-flexi - In remote (XDMCP) & flexi mode. <varlistentry> <term>--clientaddress=DIRECCIÓN</term> <listitem> - <para>Client address to return in response to XDM. This option is for running gdmchooser with XDM, and is not used within GDM.</para> + <para> + Client address to return in response to XDM. This option is for + running gdmchooser with XDM, and is not used within GDM. + </para> </listitem> </varlistentry> <varlistentry> <term>-connectionType=TIPO</term> <listitem> - <para>Connection type to return in response to XDM. This option is for running gdmchooser with XDM, and is not used within GDM.</para> + <para> + Connection type to return in response to XDM. This option is for + running gdmchooser with XDM, and is not used within GDM. + </para> </listitem> </varlistentry> </variablelist> @@ -2795,7 +4014,11 @@ remote-flexi - In remote (XDMCP) & flexi mode. <sect3 id="gdm-ssh-session"> <title><command>gdm-ssh-session</command></title> - <para>The <command>gdm-ssh-session</command> is normally executed by the GDM daemon when starting a secure remote connection through ssh. It does not take any options.</para> + <para> + The <command>gdm-ssh-session</command> is normally executed by the + GDM daemon when starting a secure remote connection through ssh. + It does not take any options. + </para> </sect3> </sect2> </sect1> @@ -2810,7 +4033,16 @@ remote-flexi - In remote (XDMCP) & flexi mode. <sect2 id="themeover"> <title>Descripción de los temas</title> - <para>GDM Themes can be created by creating an XML file that follows the specification in gui/greeter/greeter.dtd. Theme files are stored in the directory <filename><share>/gdm/themes/<theme_name></filename>. Usually this would be under <filename>/usr/share</filename>. The theme directory should contain a file called <filename>GdmGreeterTheme.desktop</filename> which has similar format to other .desktop files and looks like:</para> + <para> + GDM Themes can be created by creating an XML file that follows the + specification in gui/greeter/greeter.dtd. Theme files are stored + in the directory + <filename><share>/gdm/themes/<theme_name></filename>. + Usually this would be under <filename>/usr/share</filename>. The theme + directory should contain a file called + <filename>GdmGreeterTheme.desktop</filename> which has similar format + to other .desktop files and looks like: + </para> <screen> [GdmGreeterTheme] @@ -2825,18 +4057,43 @@ Screenshot=screenshot.png <para>Los campos del nombre, descripción, autor y copyright pueden traducirse como otros archivos <filename>.desktop</filename>. Todos los archivos que se mencionan deberían estar en el propio directorio de temas. El campo Screenshot apunta a un archivo que debería ser una captura de 200x150 del tema en acción (está bien no tener una, pero lo hace más agradable al usuario). El campo Greeter apunta a un archivo xml que contiene descripciones del tema. La descripción se dará más tarde.</para> - <para>Once you have theme ready and installed you can test it with the installed <command>gdmthemetester</command> script. This script assumes that the X server supports Xnest. This command takes two arguments, first the environment that should be used. This is one of console, console-timed, flexi, remote-flexi, xdmcp. Where console is a standard console login, console-timed is a console login with a timed login going on, flexi is for any local flexible display, remote-flexi is for flexi displays that are not local (such as an Xnest flexiserver run from a remote display) and xdmcp is for remote XDMCP connections. The second argument is the theme name. So for example to test how things look in the XDMCP mode with the circles theme you would run:</para> + <para> + Once you have theme ready and installed you can test it with the + installed <command>gdmthemetester</command> script. This script + assumes that the X server supports Xnest. This command takes two + arguments, first the environment that should be used. This is one of + console, console-timed, flexi, remote-flexi, xdmcp. Where console is a + standard console login, console-timed is a console login with a timed + login going on, flexi is for any local flexible display, remote-flexi + is for flexi displays that are not local (such as an Xnest flexiserver + run from a remote display) and xdmcp is for remote XDMCP connections. + The second argument is the theme name. So for example to test how + things look in the XDMCP mode with the circles theme you would run: + </para> <screen> <command>gdmthemetester xdmcp circles</command> </screen> - <para>Be sure to test all the environments with your theme, and make sure to test how the caps lock warning looks by pressing caps lock. This is also a good way to take screenshots, just take a screenshot of the Xnest window. This can be done in GNOME by focusing the Xnest window and pressing Alt-PrintScreen.</para> - - <para>Once you have all this done, then make a tarball that contains the directory name (so that you could just untar it in the <filename><share>/gdm/themes</filename> directory). And this is the tarball you distribute and people can install from the graphical configuration application. You can do this with the commands: <screen> + <para> + Be sure to test all the environments with your theme, and make sure to + test how the caps lock warning looks by pressing caps lock. This is + also a good way to take screenshots, just take a screenshot of the + Xnest window. This can be done in GNOME by focusing the Xnest window + and pressing Alt-PrintScreen. + </para> + + <para> + Once you have all this done, then make a tarball that contains the + directory name (so that you could just untar it in the + <filename><share>/gdm/themes</filename> directory). And this is + the tarball you distribute and people can install from the graphical + configuration application. You can do this with the commands: +<screen> cd <share>/gdm/themes tar czvf <theme_name>.tar.gz <theme_name>/ -</screen></para> +</screen> + </para> </sect2> <sect2 id="descofthemeformat"> @@ -2845,25 +4102,48 @@ tar czvf <theme_name>.tar.gz <theme_name>/ <sect3 id="boxnodes"> <title>Nodos contenedores.</title> - <para>Box nodes are container nodes for item nodes. Box nodes are specified as follows: <screen> + <para> + Box nodes are container nodes for item nodes. Box nodes are + specified as follows: +<screen> <box orientation="alignment" min-width="num" xpadding="num" ypadding="num" spacing="num" homogeneous="bool"> -</screen> Where "num" means number and bool means either "true" or "false" The alignment value can be either "horizontal" or "vertical". If you leave any property off it will default to zero or "false" in case of "homogeneous" and "vertical" for the orientation.</para> +</screen> + Where "num" means number and bool means either + "true" or "false" The alignment value can be + either "horizontal" or "vertical". If you leave + any property off it will default to zero or "false" in + case of "homogeneous" and "vertical" for the + orientation. + </para> <para>Si la caja es homogénea entonces los hijos se les reserver la misma cantidad de espacio.</para> - <para>The "min-width" must be specified in pixels. Obviously there is also a corresponding "min-height" property as well.</para> + <para> + The "min-width" must be specified in pixels. Obviously + there is also a corresponding "min-height" property as + well. + </para> </sect3> <sect3 id="fixednodes"> <title>Nodos fijos</title> - <para>Fixed is a container that has its children scattered about laid out with precise coordinates. The size of this container is the biggest rectangle that contains all the children. Fixed has no extra properties and so you just use: <screen> + <para> + Fixed is a container that has its children scattered about + laid out with precise coordinates. The size of this container + is the biggest rectangle that contains all the children. Fixed + has no extra properties and so you just use: +<screen> <fixed> -</screen> Then you put other items with proper position nodes inside this.</para> +</screen> + Then you put other items with proper position nodes inside this. + </para> - <para>The "toplevel" node is really just like a fixed node.</para> + <para> + The "toplevel" node is really just like a fixed node. + </para> </sect3> <sect3 id="itemnodes"> @@ -2915,9 +4195,16 @@ homogeneous="bool"> </varlistentry> </variablelist> - <para>For example: <screen> + <para> + For example: +<screen> <item type="label"> -</screen> Items can specify ID values which gives them a specific look and feel or formatting. Furthermore you can customize the login process by adding custom widgets with custom id's for some items (currently only the list item)</para> +</screen> + Items can specify ID values which gives them a specific look and feel + or formatting. Furthermore you can customize the login process by + adding custom widgets with custom id's for some items (currently only + the list item) + </para> <para>Los elementos de entradas pueden tener valores id como siguen:</para> @@ -2925,7 +4212,11 @@ homogeneous="bool"> <varlistentry> <term>user-pw-entry</term> <listitem> - <para>Entry field for userid and password entry. This is the field used for responses for the PAM/GDM questions (Username, Password, etc..).</para> + <para> + Entry field for userid and password entry. This is the field + used for responses for the PAM/GDM questions (Username, + Password, etc..). + </para> </listitem> </varlistentry> </variablelist> @@ -2937,12 +4228,21 @@ homogeneous="bool"> <varlistentry> <term>userlist</term> <listitem> - <para>A Face Browser list, so that users can pick their username by clicking on this instead of typing.</para> + <para> + A Face Browser list, so that users can pick + their username by clicking on this instead + of typing. + </para> </listitem> </varlistentry> </variablelist> - <para>Furthermore, you can have an arbitrary id (I'd recommend starting the id with 'custom' not to conflict with future additions to this spec) and ask extra information of the user. See the section 'Custom Widgetry'</para> + <para> + Furthermore, you can have an arbitrary id (I'd recommend starting + the id with 'custom' not to conflict with future additions to this + spec) and ask extra information of the user. See the section + 'Custom Widgetry' + </para> <para>Los elementos de etiquetas pueden tener valores id como siguen:</para> @@ -2957,21 +4257,31 @@ homogeneous="bool"> <varlistentry> <term>pam-prompt</term> <listitem> - <para>Label that displays the PAM prompt. This is the prompt that PAM uses to ask for username, password, etc...</para> + <para> + Label that displays the PAM prompt. This is the prompt that PAM + uses to ask for username, password, etc... + </para> </listitem> </varlistentry> <varlistentry> <term>pam-error</term> <listitem> - <para>Label that displayst PAM/GDM error messages. Such as when user can't log in.</para> + <para> + Label that displayst PAM/GDM error messages. Such as when user + can't log in. + </para> </listitem> </varlistentry> <varlistentry> <term>pam-message</term> <listitem> - <para>Label that displays the PAM message. These are messages that PAM/GDM gives about state of the account, help about the prompts and other information.</para> + <para> + Label that displays the PAM message. These are messages that + PAM/GDM gives about state of the account, help about the + prompts and other information. + </para> </listitem> </varlistentry> @@ -2989,14 +4299,22 @@ homogeneous="bool"> <varlistentry> <term>caps-lock-warning</term> <listitem> - <para>Displays an icon that shows if the CAPS LOCK key is depressed. This rectangle will be hidden/shown appropriately</para> + <para> + Displays an icon that shows if the + CAPS LOCK key is depressed. This rectangle + will be hidden/shown appropriately + </para> </listitem> </varlistentry> </variablelist> - <para>If an item is of type rect, the item can be a button. Buttons must also include a "button" value as follows: <screen> + <para> + If an item is of type rect, the item can be a button. Buttons + must also include a "button" value as follows: +<screen> <item type="rect" id="disconnect_button" button="true">. -</screen></para> +</screen> + </para> <para>Los valores posibles para los ids de los botones son los siguientes:</para> @@ -3075,28 +4393,66 @@ homogeneous="bool"> <para>Tanto la posición como el tamaño pueden darse en porcentaje y se tomará como el porcentaje del tamaño del contenedor actual. Para los elementos de nivel superior su porcentaje es respecto de la pantalla completa.</para> - <para>For x and y, you can also specify a negative position which means position from the right or bottom edge. But this only applies with absolute coordinates. With percentage you can specify negative position and it will be still from the same edge.</para> + <para> + For x and y, you can also specify a negative position which means + position from the right or bottom edge. But this only applies with + absolute coordinates. With percentage you can specify negative + position and it will be still from the same edge. + </para> - <para>The position also specifies the anchor of the item, this can be "n" "ne" "e" "se" "s" "sw" "w" and "nw" or "center" which stand for the different edges/corners or "center" for center. For example: <screen> + <para> + The position also specifies the anchor of the item, this can be + "n" "ne" "e" "se" + "s" "sw" "w" and "nw" or + "center" which stand for the different edges/corners or + "center" for center. For example: +<screen> <pos x="10%" y="50%" anchor="w" width="80%" height="95"/> -</screen></para> +</screen> + </para> - <para>If the item contains a box, you can specify width and height to be "box" to mean that they are supposed to be the width and height of the box, that is the items in the box plus the padding.</para> + <para> + If the item contains a box, you can specify width and height to be + "box" to mean that they are supposed to be the width and + height of the box, that is the items in the box plus the padding. + </para> - <para>If the item contains an SVG image, you can specify width and height to be "scale" to mean that the SVG image should be scaled to fit the requested area.</para> + <para> + If the item contains an SVG image, you can specify width and height + to be "scale" to mean that the SVG image should be scaled + to fit the requested area. + </para> - <para>You can also specify an "expand" property to either be "true" or false. If true then the child will be expanded in the box as much as possible (that is it will be given more space if available).</para> + <para> + You can also specify an "expand" property to either be + "true" or false. If true then the child will be expanded + in the box as much as possible (that is it will be given more space + if available). + </para> - <para>There are two extra properties you can specify (as of 2.4.4.3) for labels (and labels only). The first is "max-width" which will specify the maximum width of the label in pixels. And the second is "max-screen-percent-width" which specifies the maximum percentage of the screen width that the label can occupy. By default no label will occupy more then 90% of the screen by width. An example may be: <screen> + <para> + There are two extra properties you can specify (as of 2.4.4.3) for + labels (and labels only). The first is "max-width" which + will specify the maximum width of the label in pixels. And the + second is "max-screen-percent-width" which specifies the + maximum percentage of the screen width that the label can occupy. + By default no label will occupy more then 90% of the screen by width. + An example may be: +<screen> <item type="label"> <pos x="10%" max-screen-percent-width="50%"/> -</screen></para> +</screen> + </para> </sect3> <sect3 id="shownodes"> <title>Mostrar nodo</title> - <para>Some items may only display in certain modes, like when doing a remote display. Multiple values can be specified and must be separated with commas. The following values are possible:</para> + <para> + Some items may only display in certain modes, like when doing a + remote display. Multiple values can be specified and must be + separated with commas. The following values are possible: + </para> <para><filename>console</filename> - En modo consola.</para> <para><filename>console-fixed</filename> - En modo consola no-flexible.</para> @@ -3109,7 +4465,11 @@ homogeneous="bool"> <show modes="console" type="system"/> </screen></para> - <para>You can also specify the "type" value to indicate that certain items should only be displayed if the type is true. Valid values include the following:</para> + <para> + You can also specify the "type" value to indicate that + certain items should only be displayed if the type is true. Valid + values include the following: + </para> <para><filename>chooser</filename>, si ChooserButton está puesto a «true» en la configuración de GDM.</para> <para><filename>configurar</filename>, si ConfigAvailable está puesto a «true» en la configuración de GDM.</para> @@ -3123,37 +4483,65 @@ homogeneous="bool"> <show modes="console" type="system"/> </screen></para> - <para>Note that if SystemMenu is off then the halt, restart, suspend, chooser and config choices will not be shown, so this is a global toggle for them all. See some of the standard themes for how the show modes are used.</para> + <para> + Note that if SystemMenu is off then the halt, restart, suspend, + chooser and config choices will not be shown, so this is a global + toggle for them all. See some of the standard themes for how the + show modes are used. + </para> </sect3> <sect3 id="noractprenodes"> <title>Normal/Active/Prelight Nodes</title> - <para>Depending on the item type (except for userlist - refer to Color node below), it can specify its color, font, or image via the following tags:</para> + <para> + Depending on the item type (except for userlist - refer to Color node + below), it can specify its color, font, or image via the following + tags: + </para> <para><filename>normal</filename> - estado normal.</para> <para><filename>activo</filename> - cuando el elemento tiene foco activo.</para> <para><filename>prelight</filename> - cuando el ratón está sobre el elemento.</para> - <para>When item is "rect" (alpha can be omitted and defaults to 0.0): <screen> + <para> + When item is "rect" (alpha can be omitted and defaults to + 0.0): +<screen> <normal color="#ffffff" alpha="0.0"> -</screen></para> +</screen> + </para> - <para>When item is "label" <screen> + <para> + When item is "label" +<screen> <normal color="#ffffff" font="Sans 14"/> -</screen></para> +</screen> + </para> - <para>When the item type is "pixmap" or "SVG", then the normal, active, and prelight tags specify the images to use as follows: <screen> + <para> + When the item type is "pixmap" or "SVG", then the + normal, active, and prelight tags specify the images to use as + follows: +<screen> <normal file="picture.png" tint="#dddddd"/> -</screen></para> +</screen> + </para> - <para>Note that relative pathnames are assumed to be in the same directory as the theme <filename>.xml</filename> file in <filename><share>/gdm/themes/<theme_name></filename>.</para> + <para> + Note that relative pathnames are assumed to be in the same + directory as the theme <filename>.xml</filename> file in + <filename><share>/gdm/themes/<theme_name></filename>. + </para> </sect3> <sect3 id="listcoloronodes"> <title>Face Browser Icon/Label Color Nodes</title> - <para>If the item type is of userlist, then the background color for the icon and label can be set separately via the the following tag:</para> + <para> + If the item type is of userlist, then the background color for the + icon and label can be set separately via the the following tag: + </para> <para> <screen> @@ -3165,29 +4553,76 @@ homogeneous="bool"> <sect3 id="textnodes"> <title>Nodo de texto</title> - <para>Text tags are used by labels. They can be used to display localized text as follows (if the "xml:lang" attribute is omitted, the C locale is assumed): <screen> + <para> + Text tags are used by labels. They can be used to display + localized text as follows (if the "xml:lang" attribute is + omitted, the C locale is assumed): +<screen> <text xml:lang="fr">Option</text> -</screen></para> +</screen> + </para> - <para>You can include pango markup in the text nodes for labels, however you must encode it. So for example to have the label of "foo<sup>bar</sup>", you must type: <screen> + <para> + You can include pango markup in the text nodes for labels, however + you must encode it. So for example to have the label of + "foo<sup>bar</sup>", you must type: +<screen> <text>"foo<sup>bar</sup>"</text> -</screen></para> +</screen> + </para> - <para>Text nodes can contain the following special character sequences which will be translated as follows:</para> + <para> + Text nodes can contain the following special character sequences + which will be translated as follows: + </para> <para>%% - Un carácter literal %</para> - <para>%c - Clock time. Only labels with the "clock" id will update automatically every second. Other labels will contain a static timestamp.</para> - <para>%d - Display name (DISPLAY environment variable)</para> - <para>%h - Hostname (gethostname output)</para> - <para>%m - Machine name (uname.machine output)</para> - <para>%n - Node name (uname.nodename output)</para> - <para>%o - Domain name (getdomainname output)</para> - <para>%r - Release name (uname.release output)</para> - <para>%s - System name (uname.sysname output)</para> - <para>%t - Current timed delay value from configuration file (0 if off) followed by the word "seconds" if value is greater than 1 or the word "second" if the value is 1. This character sequence is intended to be only used internally to display the "timed-label" message, which is automatically updated every second.</para> - <para>%u - Timed username value from configuration file (empty if off) This character sequence is intended to be only used internally to display the "timed-label" message, which is automatically updated every second.</para> + <para> + %c - Clock time. Only labels with the "clock" id will + update automatically every second. Other labels will contain a + static timestamp. + </para> + <para> + %d - Display name (DISPLAY environment variable) + </para> + <para> + %h - Hostname (gethostname output) + </para> + <para> + %m - Machine name (uname.machine output) + </para> + <para> + %n - Node name (uname.nodename output) + </para> + <para> + %o - Domain name (getdomainname output) + </para> + <para> + %r - Release name (uname.release output) + </para> + <para> + %s - System name (uname.sysname output) + </para> + <para> + %t - Current timed delay value from configuration file (0 if off) + followed by the word "seconds" if value is greater than 1 + or the word "second" if the value is 1. This character + sequence is intended to be only used internally to display the + "timed-label" message, which is automatically updated every + second. + </para> + <para> + %u - Timed username value from configuration file (empty if off) + This character sequence is intended to be only used internally to + display the "timed-label" message, which is automatically + updated every second. + </para> <para>\n - Retorno de carro</para> - <para>_ - An underscore causes the following character to be underlined. If it precedes a % character sequence, the string that replaces the character sequence is underlined.</para> + <para> + _ - An underscore causes the following character to be underlined. + If it precedes a % character sequence, the string that replaces the + character sequence is underlined. + </para> </sect3> <sect3 id="stocklabels"> @@ -3245,9 +4680,26 @@ custom-config=foo <sect1 id="accessibility"> <title>Accesibilidad</title> - <para>GDM supports "Accessible Login" to allow users to log in to their desktop session even if they cannot easily use the screen, mouse, or keyboard in the usual way. Only the "Standard Greeter" supports accessibility, so use this login GUI for accessibility support. This is done by specifying the "Standard Greeter" in the "Local" tab for the console display and specifying the "Standard Greeter" in the "Remote" tab for remote displays. Or you can modify the <filename>Greeter</filename> configuration option by hand to be <command>gdmlogin</command>.</para> - - <para>The Standard Greeter supports the ability to launch assistive technologies at login time via configurable "gestures" from the standard keyboard, pointing device, or switch device attached to the USB or PS/2 mouse port. Also the user can change the visual appearance of the login UI before logging in, for instance to use a higher-contrast color scheme for better visibility.</para> + <para> + GDM supports "Accessible Login" to allow users to log in to + their desktop session even if they cannot easily use the screen, mouse, + or keyboard in the usual way. Only the "Standard Greeter" + supports accessibility, so use this login GUI for accessibility + support. This is done by specifying the "Standard Greeter" + in the "Local" tab for the console display and specifying + the "Standard Greeter" in the "Remote" tab for + remote displays. Or you can modify the <filename>Greeter</filename> + configuration option by hand to be <command>gdmlogin</command>. + </para> + + <para> + The Standard Greeter supports the ability to launch assistive + technologies at login time via configurable "gestures" from + the standard keyboard, pointing device, or switch device attached to + the USB or PS/2 mouse port. Also the user can change the visual + appearance of the login UI before logging in, for instance to use a + higher-contrast color scheme for better visibility. + </para> <sect2 id="accessibilityconfig"> <title>Configuración de accesibilidad</title> @@ -3269,23 +4721,99 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener <para>Los administradores de sistema quizá deseen cargar sólo un subconjunto mínimo de estos módulos que se requieren para soportar su base de usuarios. Dependiendo de las necesidades de los usuarios finales, no todos los GtkModules necesitan ser cargados. Si sus usuarios finales necesitan el lector de pantalla integrado y la lupa, debe incuir «gail» y «atk-bridge». Si sus usuarios finales estarán usando un dispositivo apuntador sin botones o interruptores, incluya «dwellmouselistener». si algunos de sus usuarios usarán dispositivos apuntadores con interruptores, alternativos a teclados físicos o despositivos de botones, incluya «keymouselistener». Incluir los cuatro es apropiado para la mayoría de las configuraciones del sistema. El teclado en pantalla puede funcionar singail o atk-bridge, pero con un conjunto de características reducido; paa accesibilidad optima recomendamos incluir tanto gail como atk-bridge.</para> - <para>Once "keymouselistener" and/or "dwellmouselistener" have been added to the GtkModules loaded by GDM, you can assign end-user actions with the launching of specific assistive technologies. These gesture associations are contained in files AccessKeyMouseEvents and AccessDwellMouseEvents, respectively. Both files are located in the <etc>/gdm/modules directory. The gesture format is described in the two configuration files.</para> - - <para>The AccessKeyMouseEvents file controls the keymouselistener Gesture Listener and is used to define key-press, mouse button, or XInput device sequences that can be used to launch applications needed for accessibility. In order to reduce the likelihood of unintentional launch, these "gestures" may be associated with multiple switch presses and/or minimum durations. Note that the XKB extension is needed for key gestures to work, so you may need to add +xkb to your Xserver command line for gestures to work properly.</para> - - <para>The DwellKeyMouseEvents file controls the dwellmouselistner and supports gestures that involve only motion of a pointing device such as the system mouse of an alternative pointing device such as a head pointer or trackball may also be defined. All gestures are specified by the same syntax; that is, there is no distinction between a "core mouse" gesture and motion from an alternate input device.</para> - - <para>Motion gestures are defined as "crossing events" into and out of the login dialog window. If the "dwellmouselistener" GtkModule is loaded, alternative pointing devices are temporarily "latched" to the core pointer, such that motion from alternative devices results in movement of the onscreen pointer.</para> - - <para>In order to use text-to-speech services at login time (for instance, when using the Screen Reader in speech mode) on some operating systems, the GDM user must be made a member of the "audio" group</para> - - <para>Currently GDM does not remember what accessible technology programs have been started when switching applications. So if the user switches between the login program and the chooser, for example, then it is necessary for the user to redo the gesture. Users may need to also set up their default session so that the assistive technologies required are started automatically (or have appropriate key-bindings defined to start them) after the user session has started.</para> - - <para>There are some issues that cause users to have problems getting the gesture listeners to work. It is recommended that people use GDM version 2.8.0.5 or later for best results. Some X servers have a bug which causes detectable autorepeat to fail when XEVIE is enabled (which happens when atk-bridge is included as a GTK Module). This bug causes key gestures with a duration greater than 0 to always fail. A workaround is to simply redefine all key gestures so they have zero length duration. Some versions of GOK and gnopernicus will not launch unless the "gdm" user has a writable home directory. If you see an hourglass cursor when you complete a gesture but the program does not start, then you are likely having this problem. It should be considered a bug for AT programs to require having a writable home directory, so please file a bug with the AT program if you encounter this problem. Also note that some input devices require X server configuration before GDM will recognize them.</para> + <para> + Once "keymouselistener" and/or + "dwellmouselistener" have been added to the GtkModules + loaded by GDM, you can assign end-user actions with the launching + of specific assistive technologies. These gesture associations + are contained in files AccessKeyMouseEvents and + AccessDwellMouseEvents, respectively. Both files are located in + the <etc>/gdm/modules directory. The gesture format is + described in the two configuration files. + </para> + + <para> + The AccessKeyMouseEvents file controls the keymouselistener + Gesture Listener and is used to define key-press, mouse button, + or XInput device sequences that can be used to launch applications + needed for accessibility. In order to reduce the likelihood of + unintentional launch, these "gestures" may be associated + with multiple switch presses and/or minimum durations. Note that + the XKB extension is needed for key gestures to work, so you may + need to add +xkb to your Xserver command line for gestures to + work properly. + </para> + + <para> + The DwellKeyMouseEvents file controls the dwellmouselistner and + supports gestures that involve only motion of a pointing device + such as the system mouse of an alternative pointing device such + as a head pointer or trackball may also be defined. All gestures + are specified by the same syntax; that is, there is no distinction + between a "core mouse" gesture and motion from an + alternate input device. + </para> + + <para> + Motion gestures are defined as "crossing events" into + and out of the login dialog window. If the + "dwellmouselistener" GtkModule is loaded, alternative + pointing devices are temporarily "latched" to the core + pointer, such that motion from alternative devices results in + movement of the onscreen pointer. + </para> + + <para> + In order to use text-to-speech services at login time (for + instance, when using the Screen Reader in speech mode) on some + operating systems, the GDM user must be made a member of the + "audio" group + </para> + + <para> + Currently GDM does not remember what accessible technology + programs have been started when switching applications. So + if the user switches between the login program and the + chooser, for example, then it is necessary for the user to + redo the gesture. Users may need to also set up their default + session so that the assistive technologies required are + started automatically (or have appropriate key-bindings + defined to start them) after the user session has started. + </para> + + <para> + There are some issues that cause users to have problems + getting the gesture listeners to work. It is recommended that + people use GDM version 2.8.0.5 or later for best results. + Some X servers have a bug which causes detectable autorepeat + to fail when XEVIE is enabled (which happens when atk-bridge + is included as a GTK Module). This bug causes key gestures + with a duration greater than 0 to always fail. A workaround + is to simply redefine all key gestures so they have zero length + duration. Some versions of GOK and gnopernicus will not launch + unless the "gdm" user has a writable home directory. + If you see an hourglass cursor when you complete a gesture but the + program does not start, then you are likely having this problem. + It should be considered a bug for AT programs to require having a + writable home directory, so please file a bug with the AT + program if you encounter this problem. Also note that some input + devices require X server configuration before GDM will recognize + them. + </para> </sect2> <sect2 id="accessibilitysound"> <title>Configuración de sonido de accesibilidad en la entrada</title> - <para>By default, GDM requires a media application such as "sox" to be present to play sounds for successful or failed login. GDM defaults the location of this application to <filename><bin>/play</filename> (or <filename><bin>/audioplay</filename> on Solaris. This can be changed via the SoundProgram GDM configuration option. Typically most text-to-speech programs (such as ORCA or Gnopernicus) use a separate mechanism to play audio.</para> + <para> + By default, GDM requires a media application such as + "sox" to be present to play sounds for successful or + failed login. GDM defaults + the location of this application to + <filename><bin>/play</filename> (or + <filename><bin>/audioplay</filename> on Solaris. This can + be changed via the SoundProgram GDM configuration option. + Typically most text-to-speech programs (such as ORCA or + Gnopernicus) use a separate mechanism to play audio. + </para> </sect2> </sect1> @@ -3294,35 +4822,83 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener <sect2 id="solarisconfiguration"> <title>Configuración de Solaris</title> - <para>On Solaris, the following configuration is recommended. This turns on IPv6 and also turns on PreFetch for performance benefit. <screen> + <para> + On Solaris, the following configuration is recommended. + This turns on IPv6 and also turns on PreFetch for + performance benefit. + +<screen> ./autogen.sh --prefix=/usr --sysconfdir=/etc/X11 --localstatedir=/var --libexecdir=/usr/lib --enable-ipv6=yes --with-at-bindir=/usr/sfw/bin --with-prefetch --with-post-path=/usr/openwin/bin -</screen></para> +</screen> + </para> - <para>Configuring GDM with the "--with-post-path=/usr/openwin/bin" on Solaris is recommended for access to programs like Xnest.</para> + <para> + Configuring GDM with the + "--with-post-path=/usr/openwin/bin" on Solaris is + recommended for access to programs like Xnest. + </para> </sect2> <sect2 id="solarislogindevperm"> <title>Solaris /etc/logindevperm</title> - <para>GDM supports /etc/logindevperm, but only on Solaris 10 and higher. Refer to the logindevperm.4 man page for more information.</para> - - <para>To make /etc/logindevperm functionality work on Solaris 9 or earlier you would have to hack the GDM PreSession and PostSession script to chmod the device permissions directly. In other words, if /etc/logindevperm had a listing like this:</para> + <para> + GDM supports /etc/logindevperm, but only on Solaris 10 and higher. + Refer to the logindevperm.4 man page for more information. + </para> + + <para> + To make /etc/logindevperm functionality work on Solaris 9 or + earlier you would have to hack the GDM PreSession and + PostSession script to chmod the device permissions directly. In + other words, if /etc/logindevperm had a listing like this: + </para> <screen> /dev/console 0600 /dev/sound/* # audio devices </screen> - <para>The PreSession script would need to be modified to chown /dev/console to the user:group who is logging into the console and ensure whatever permissions is specified in /etc/logindevperm (0600 for the line above). Then in the PostSession script chmod the device back to root:root and ensure 0600 this time (do not use the value in the /etc/logindevperm file). Linux uses a different mechanism for managing device permissions, so this extra scripting is not needed.</para> + <para> + The PreSession script would need to be modified to chown + /dev/console to the user:group who is logging into the console + and ensure whatever permissions is specified in /etc/logindevperm + (0600 for the line above). Then in the PostSession script chmod + the device back to root:root and ensure 0600 this time (do not + use the value in the /etc/logindevperm file). Linux uses a + different mechanism for managing device permissions, so this + extra scripting is not needed. + </para> </sect2> <sect2 id="solarisautomaticlogin"> <title>Inicio de sesión automático en Solaris</title> - <para>Automatic login does not work on Solaris because PAM is not configured to support this feature by default. Automatic login is a GDM feature that is not enabled by default, so you would only notice this problem if you try to make use of it. Turning this feature on causes your computer to login to a specified username on startup without asking for username and password. This is an unsecure way to set up your computer.</para> - - <para>If using Solaris 10 or lower, then you need to compile the pam_allow.c code provided with the GDM release and install it to /usr/lib/security (or provide the full path in /etc/pam.conf) and ensure it is owned by uid 0 and not group or world writable.</para> - - <para>The following are reasonable pam.conf values for turning on automatic login in GDM. Make sure to read the PAM documentation (e.g. pam.d/pam.conf man page) and be comfortable with the security implications of any changes you intend to make to your configuration.</para> + <para> + Automatic login does not work on Solaris because PAM is not + configured to support this feature by default. Automatic + login is a GDM feature that is not enabled by default, so you + would only notice this problem if you try to make use of it. + Turning this feature on causes your computer to login to a + specified username on startup without asking for username + and password. This is an unsecure way to set up your + computer. + </para> + + <para> + If using Solaris 10 or lower, then you need to compile + the pam_allow.c code provided with the GDM release and + install it to /usr/lib/security (or provide the full path + in /etc/pam.conf) and ensure it is owned by uid 0 and not + group or world writable. + </para> + + <para> + The following are reasonable pam.conf values for turning on + automatic login in GDM. Make sure to read the PAM documentation + (e.g. pam.d/pam.conf man page) and be comfortable with the + security implications of any changes you intend to make to + your configuration. + </para> <screen> gdm-autologin auth required pam_unix_cred.so.1 @@ -3332,7 +4908,10 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener gdm-autologin password sufficient pam_allow.so.1 </screen> - <para>The above setup will cause no lastlog entry to be generated. If a lastlog entry is desired, then use the following for session:</para> + <para> + The above setup will cause no lastlog entry to be generated. If + a lastlog entry is desired, then use the following for session: + </para> <screen> gdm-autologin session required pam_unix_session.so.1 @@ -3345,9 +4924,23 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener <para>GDM soporta Solaris Auditing si se ejecuta sobre Solaris 10 o superior. GDM no debería usarse si se necesita auditoría y se está ejecutando Solaris 9 o anterior.</para> - <para>GDM supports a security feature which causes the X server to run as the user instead of as the root user. GDM must be using PAM for this feature to be enabled, which is the normal case for Solaris. This second feature has the side-effect of causing the X server to always restart between sessions, which disables the AlwaysRestartServer configuration option.</para> - - <para>Solaris supports the <filename>/etc/default/login</filename> interface, which affects the <filename>DefaultPath</filename>, <filename>RootPath</filename>, <filename>PasswordRequired</filename>, and <filename>AllowRemoteRoot</filename> options as described in the "Configuration" section.</para> + <para> + GDM supports a security feature which causes the X server to + run as the user instead of as the root user. GDM must be using + PAM for this feature to be enabled, which is the normal case + for Solaris. This second feature has the side-effect of + causing the X server to always restart between sessions, which + disables the AlwaysRestartServer configuration option. + </para> + + <para> + Solaris supports the <filename>/etc/default/login</filename> + interface, which affects the <filename>DefaultPath</filename>, + <filename>RootPath</filename>, + <filename>PasswordRequired</filename>, and + <filename>AllowRemoteRoot</filename> options as described in the + "Configuration" section. + </para> </sect2> </sect1> @@ -3359,23 +4952,48 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener <sect2 id="terminallab"> <title>Laboratorio con terminales con un servidor</title> - <para>Suppose you want to make a lab full of X terminals that all connect to one server machine. So let's call one X terminal <filename>xterminal</filename> and let's call the server machine <filename>appserver</filename>. You install GDM on both.</para> + <para> + Suppose you want to make a lab full of X terminals that all connect + to one server machine. So let's call one X terminal + <filename>xterminal</filename> and let's call the server machine + <filename>appserver</filename>. You install GDM on both. + </para> - <para>On <filename>appserver</filename> you enable XDMCP, so you have <screen> + <para> + On <filename>appserver</filename> you enable XDMCP, so you have +<screen> [xdmcp] Enable=true -</screen> If you want no local screens here, you can then make the <filename>[servers]</filename> section empty.</para> - - <para>On the <filename>xterminal</filename> you disable XDMCP (you don't want anyone to connect to the xterminal really). You will add a server type perhaps called <filename>Terminal</filename> as follows: <screen> +</screen> + If you want no local screens here, you can then + make the <filename>[servers]</filename> section empty. + </para> + + <para> + On the <filename>xterminal</filename> you disable XDMCP (you don't + want anyone to connect to the xterminal really). You will add a + server type perhaps called <filename>Terminal</filename> as follows: +<screen> [server-Terminal] name=Terminal server command=/path/to/X -terminate flexible=false handled=false -</screen> This definition should in fact be included in the standard configuration file. Notice that we made the <filename>handled</filename> key false since we don't want GDM to handle this server localy. Also note that we have not yet added the <filename>-query</filename> argument, you can add that here, or in the <filename>[servers]</filename> section. We'll define our local servers as follows: <screen> +</screen> + This definition should in fact be included in the standard + configuration file. Notice that we made the + <filename>handled</filename> key false since we don't want GDM to + handle this server localy. Also note that we have not yet added the + <filename>-query</filename> argument, you can add that here, or in the + <filename>[servers]</filename> section. We'll define our local + servers as follows: +<screen> [servers] 0=Terminal -query appserver -</screen> This will run a direct XDMCP query to the server named <filename>appserver</filename>.</para> +</screen> + This will run a direct XDMCP query to the server named + <filename>appserver</filename>. + </para> </sect2> <sect2 id="terminallabtwo"> @@ -3383,25 +5001,59 @@ handled=false <para>Suponga que quiere hacer un laboratorio lleno de terminales X que todas se conectan a una selección de servidores. Por ahora llamémoslos <filename>appserveruno</filename> y<filename>appserverdos</filename>. De nuevo llamamos a nuestro servidor de terminales X <filename>xterminal</filename>. La configuración de ambos servidores es la mismoa que con el caso de un servidor en la sección anterior. No necesita activar explícitamente las consultas indirectas en el servidor debido a que ejecutamos los selectores localmente en las terminales X.</para> - <para>So on the <filename>xterminal</filename> you again disable XDMCP. You will add a server type perhaps called <filename>Chooser</filename> as follows: <screen> + <para> + So on the <filename>xterminal</filename> you again disable XDMCP. + You will add a server type perhaps called <filename>Chooser</filename> + as follows: +<screen> [server-Chooser] name=Chooser server command=/path/to/X flexible=false chooser=true -</screen> And again this definition should in fact be included in the standard configuration file. Notice that we made the <filename>chooser</filename> key true here. This will run the XDMCP chooser for this server, and when the user chooses a host GDM will run a query for that host. Then we will define our local servers as follows: <screen> +</screen> + And again this definition should in fact be included in the standard + configuration file. Notice that we made the + <filename>chooser</filename> key true here. This will run the XDMCP + chooser for this server, and when the user chooses a host GDM will run + a query for that host. Then we will define our local servers as + follows: +<screen> [servers] 0=Chooser -</screen></para> - - <para>The XDMCP chooser on the X terminal will normally give a broadcast query to see which servers exist on the network. If the two servers are not reachable by a broadcast query, you must add them by hand to the configuration file. So in the <filename>[chooser]</filename> section you would have: <screen> +</screen> + </para> + + <para> + The XDMCP chooser on the X terminal will normally give a broadcast + query to see which servers exist on the network. If the two servers + are not reachable by a broadcast query, you must add them by hand to + the configuration file. So in the <filename>[chooser]</filename> + section you would have: +<screen> Hosts=appserverone,appservertwo -</screen> and any other servers you wish the users to be able to connect to.</para> - - <para>Sometimes you may want to run the chooser on the server side however. Then what you want to do is to run a configuration similar to the previous section about the one server configuration with XDMCP indirect queries enabled on <filename>appserver</filename> and on the X terminals you'd have <screen> +</screen> + and any other servers you wish the users to be able to connect to. + </para> + + <para> + Sometimes you may want to run the chooser on the server side however. + Then what you want to do is to run a configuration similar to the + previous section about the one server configuration with XDMCP + indirect queries enabled on <filename>appserver</filename> and on the + X terminals you'd have +<screen> [servers] 0=Terminal -indirect appserver -</screen> This way for example you only have to maintain one <filename>Hosts</filename> entry. However as a disadvantage then, the <filename>appserver</filename> must then always be available. So it's not good for situations where you want to have several servers and not all of them have to be on all the time. You could also have one of the X terminals handle indirect XDMCP queries and serve up the chooser to the other X terminals.</para> +</screen> + This way for example you only have to maintain one + <filename>Hosts</filename> entry. However as a disadvantage then, + the <filename>appserver</filename> must then always be available. So + it's not good for situations where you want to have several servers + and not all of them have to be on all the time. You could also have + one of the X terminals handle indirect XDMCP queries and serve up the + chooser to the other X terminals. + </para> </sect2> </sect1> @@ -3410,26 +5062,86 @@ Hosts=appserverone,appservertwo <para>Esta sección hace acerca de consejos útiles para hacer funcionar GDM. En general, si tiene un problema al usar GDM, puede enviar un bug a la categoría «gdm» en <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink> o enviar un correo-e a la lista de correo <address><email>gdm-list@gnome.org</email></address>.</para> - <para>If GDM is failing to work properly, it is always a good idea to include debug information. Use the <command>gdmsetup</command> command to turn on debug ("Enable debug messages to system log" checkbox in the "Security" tab), then use GDM to the point where it fails, and include the GDM output sent to your system log (<filename><var>/log/messages</filename> or <filename><var>/adm/messages</filename> depending on your operating system). Since the system log can be large, please only include the GDM debug information and do not sent the entire file. If you do not see any GDM syslog output, you may need to configure syslog (see syslog.3c man page).</para> - - <para>You should not leave debug on after collecting data. It will clutter your syslog and slow system performance.</para> + <para> + If GDM is failing to work properly, it is always a good idea to include + debug information. Use the <command>gdmsetup</command> command to turn + on debug ("Enable debug messages to system log" checkbox in the + "Security" tab), then use GDM to the point where it fails, and + include the GDM output sent to your system log + (<filename><var>/log/messages</filename> or + <filename><var>/adm/messages</filename> depending on your operating + system). Since the system log can be large, please only include the GDM + debug information and do not sent the entire file. If you do not see any + GDM syslog output, you may need to configure syslog (see syslog.3c man + page). + </para> + + <para> + You should not leave debug on after collecting data. It will clutter your + syslog and slow system performance. + </para> <sect2 id="wontstart"> <title>GDM no se inicia</title> - <para>There are a many problems that can cause GDM to fail to start, but this section will discuss a few common problems and how to approach tracking down a problem with GDM starting. Some problems will cause GDM to respond with an error message or dialog when it tries to start, but it can be difficult to track down problems when GDM fails silently.</para> - - <para>First make sure that the Xserver is configured properly. The GDM configuration file contains a command in the [server-Standard] section that is used for starting the Xserver. Verify that this command works on your system. Running this command from the console should start the Xserver. If it fails, then the problem is likely with your Xserver configuration. Refer to your Xserver error log for an idea of what the problem may be. The problem may also be that your Xserver requires different command-line options. If so, then modify the Xserver command in the GDM configuration file so that it is correct for your system.</para> - - <para>Another common problem is that the GDM greeter program is having trouble starting. This can happen, for example, if GDM cannot find a needed library or other resource. Try starting the Xserver and a terminal program, set the shell environment variable DOING_GDM_DEVELOPMENT=1 and run <command><lib>/gdmlogin</command> or <command><lib>/gdmgreeter</command>. Any error messages echoed to the terminal will likely highlight the problem. Also, turning on debug and checking the output sent to the system log will often highlight the problem.</para> - - <para>Also make sure that the <filename>/tmp</filename> directory has reasonable ownership and permissions, and that the machine's file system is not full. These problems will cause GDM to fail to start.</para> + <para> + There are a many problems that can cause GDM to fail to start, but + this section will discuss a few common problems and how to approach + tracking down a problem with GDM starting. Some problems will + cause GDM to respond with an error message or dialog when it tries + to start, but it can be difficult to track down problems when GDM + fails silently. + </para> + + <para> + First make sure that the Xserver is configured properly. The + GDM configuration file contains a command in the [server-Standard] + section that is used for starting the Xserver. Verify that this + command works on your system. Running this command from the + console should start the Xserver. If it fails, then the problem + is likely with your Xserver configuration. Refer to your Xserver + error log for an idea of what the problem may be. The problem may + also be that your Xserver requires different command-line options. + If so, then modify the Xserver command in the GDM configuration file + so that it is correct for your system. + </para> + + <para> + Another common problem is that the GDM greeter program is having + trouble starting. This can happen, for example, if GDM cannot find + a needed library or other resource. Try starting the Xserver and + a terminal program, set the shell environment variable + DOING_GDM_DEVELOPMENT=1 and run + <command><lib>/gdmlogin</command> + or <command><lib>/gdmgreeter</command>. Any error messages + echoed to the terminal will likely highlight the problem. Also, + turning on debug and checking the output sent to the system log + will often highlight the problem. + </para> + + <para> + Also make sure that the <filename>/tmp</filename> directory has + reasonable ownership and permissions, and that the machine's file + system is not full. These problems will cause GDM to fail to start. + </para> </sect2> <sect2 id="notaccessfile"> <title>GDM Will Not Access User Settings</title> - <para>GDM saves user settings, such as your default session and default language, in the <filename>~/.dmrc</filename>. Other files, such as the user's <filename>~/.Xauthority</filename> file will also affect login. GDM, by default, is strict about how it tries to access files in the users home directory, and will ignore the file if they do not conform to certain rules. You can use the <filename>RelaxPermissions</filename> configuration option to make GDM less strict about how it accesses files in the user's home directory, or correct the permissions issues that cause GDM to ignore the file. This is discussed in detail described in the "File Access" section of the "Overview".</para> + <para> + GDM saves user settings, such as your default session and default + language, in the <filename>~/.dmrc</filename>. Other files, such + as the user's <filename>~/.Xauthority</filename> file will also + affect login. GDM, by default, is strict about how it tries to + access files in the users home directory, and will ignore the file if + they do not conform to certain rules. You can use the + <filename>RelaxPermissions</filename> configuration option to + make GDM less strict about how it accesses files in the user's + home directory, or correct the permissions issues that cause GDM + to ignore the file. This is discussed in detail described in the + "File Access" section of the "Overview". + </para> </sect2> </sect1> @@ -3437,9 +5149,33 @@ Hosts=appserverone,appservertwo <sect1 id="license"> <title>Licencia</title> - <para>This program is free software; you can redistribute it and/or modify it under the terms of the <ulink type="help" url="gnome-help:gpl"><citetitle>GNU General Public License</citetitle></ulink> as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.</para> - <para>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public License</citetitle> for more details.</para> - <para>A copy of the <citetitle>GNU General Public License</citetitle> is included as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also obtain a copy of the <citetitle>GNU General Public License</citetitle> from the Free Software Foundation by visiting <ulink type="http" url="http://www.fsf.org">their Web site</ulink> or by writing to <address> Free Software Foundation, Inc. <street>59 Temple Place</street> - Suite 330 <city>Boston</city>, <state>MA</state><postcode>02111-1307</postcode><country>USA</country></address></para> + <para> + This program is free software; you can redistribute it and/or + modify it under the terms of the <ulink type="help" url="gnome-help:gpl"> + <citetitle>GNU General Public License</citetitle></ulink> as + published by the Free Software Foundation; + either version 2 of the License, or (at your option) any later + version. + </para> + <para> + This program is distributed in the hope that it will be useful, but + WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + <citetitle>GNU General Public License</citetitle> for more details. + </para> + <para> + A copy of the <citetitle>GNU General Public License</citetitle> is + included as an appendix to the <citetitle>GNOME Users + Guide</citetitle>. You may also obtain a copy of the + <citetitle>GNU General Public License</citetitle> from the Free + Software Foundation by visiting <ulink type="http" url="http://www.fsf.org">their Web site</ulink> or by writing to + <address> + Free Software Foundation, Inc. + <street>59 Temple Place</street> - Suite 330 + <city>Boston</city>, <state>MA</state> <postcode>02111-1307</postcode> + <country>USA</country> + </address> + </para> </sect1> </article> <!-- Keep this comment at the end of the file diff --git a/docs/es/legal.xml b/docs/es/legal.xml index 59ab4bf7..04954d24 100644 --- a/docs/es/legal.xml +++ b/docs/es/legal.xml @@ -5,5 +5,12 @@ <para>Muchos de los nombres utilizados por las empresas para distinguir sus productos y servicios se consideran marcas comerciales. Cuando estos nombres aparezcan en la documentación de GNOME, y siempre que se haya informado a los miembros del Proyecto de documentación de GNOME de dichas marcas comerciales, los nombres aparecerán en mayúsculas o con las iniciales en mayúsculas.</para> - <para>ESTE DOCUMENTO Y LAS VERSIONES MODIFICADAS DEL MISMO SE OFRECEN SEGÚN LAS CONDICIONES ESTABLECIDAS EN LA LICENCIA DE DOCUMENTACIÓN LIBRE DE GNU (GFDL) Y TENIENDO EN CUENTA QUE: <orderedlist><listitem><para>EL DOCUMENTO SE ENTREGA "TAL CUAL", SIN GARANTÍA DE NINGÚN TIPO, NI EXPLÍCITA NI IMPLÍCITA INCLUYENDO, SIN LIMITACIÓN, GARANTÍA DE QUE EL DOCUMENTO O VERSIÓN MODIFICADA DE ÉSTE CAREZCA DE DEFECTOS EN EL MOMENTO DE SU VENTA, SEA ADECUADO A UN FIN CONCRETO O INCUMPLA ALGUNA NORMATIVA. TODO EL RIESGO RELATIVO A LA CALIDAD, PRECISIÓN Y UTILIDAD DEL DOCUMENTO O SU VERSIÓN MODIFICADA RECAE EN USTED. SI CUALQUIER DOCUMENTO O VERSIÓN MODIFICADA DE AQUÉL RESULTARA DEFECTUOSO EN CUALQUIER ASPECTO, USTED (Y NO EL REDACTOR INICIAL, AUTOR O AUTOR DE APORTACIONES) ASUMIRÁ LOS COSTES DE TODA REPARACIÓN, MANTENIMIENTO O CORRECCIÓN NECESARIOS. ESTA EXENCIÓN DE RESPONSABILIDAD SOBRE LA GARANTÍA ES UNA PARTE ESENCIAL DE ESTA LICENCIA. NO SE AUTORIZA EL USO DE NINGÚN DOCUMENTO NI VERSIÓN MODIFICADA DE ÉSTE POR EL PRESENTE, SALVO DENTRO DEL CUMPLIMIENTO DE LA EXENCIÓN DE RESPONSABILIDAD;Y</para></listitem><listitem><para>EN NINGUNA CIRCUNSTANCIA NI BAJO NINGUNA TEORÍA LEGAL, SEA POR ERROR (INCLUYENDO NEGLIGENCIA) CONTRATO O DOCUMENTO DE OTRO TIPO, EL AUTOR, EL ESCRITOR INICIAL, EL AUTOR DE APORTACIONES NI NINGÚN DISTRIBUIDOR DEL DOCUMENTO O VERSIÓN MODIFICADA DEL DOCUMENTO, NI NINGÚN PROVEEDOR DE NINGUNA DE ESAS PARTES, SERÁ RESPONSABLE ANTE NINGUNA PERSONA POR NINGÚN DAÑO DIRECTO, INDIRECTO, ESPECIAL, INCIDENTAL O DERIVADO DE NINGÚN TIPO, INCLUYENDO, SIN LIMITACIÓN DAÑOS POR PÉRDIDA DE FONDO DE COMERCIO, PARO TÉCNICO, FALLO INFORMÁTICO O AVERÍA O CUALQUIER OTRO POSIBLE DAÑO O AVERÍA DERIVADO O RELACIONADO CON EL USO DEL DOCUMENTO O SUS VERSIONES MODIFICADAS, AUNQUE DICHA PARTE HAYA SIDO INFORMADA DE LA POSIBILIDAD DE QUE SE PRODUJESEN ESOS DAÑOS.</para></listitem></orderedlist></para> + <para>ESTE DOCUMENTO Y LAS VERSIONES MODIFICADAS DEL MISMO SE OFRECEN SEGÚN LAS CONDICIONES ESTABLECIDAS EN LA LICENCIA DE DOCUMENTACIÓN LIBRE DE GNU (GFDL) Y TENIENDO EN CUENTA QUE: <orderedlist> + <listitem> + <para>EL DOCUMENTO SE ENTREGA "TAL CUAL", SIN GARANTÍA DE NINGÚN TIPO, NI EXPLÍCITA NI IMPLÍCITA INCLUYENDO, SIN LIMITACIÓN, GARANTÍA DE QUE EL DOCUMENTO O VERSIÓN MODIFICADA DE ÉSTE CAREZCA DE DEFECTOS EN EL MOMENTO DE SU VENTA, SEA ADECUADO A UN FIN CONCRETO O INCUMPLA ALGUNA NORMATIVA. TODO EL RIESGO RELATIVO A LA CALIDAD, PRECISIÓN Y UTILIDAD DEL DOCUMENTO O SU VERSIÓN MODIFICADA RECAE EN USTED. SI CUALQUIER DOCUMENTO O VERSIÓN MODIFICADA DE AQUÉL RESULTARA DEFECTUOSO EN CUALQUIER ASPECTO, USTED (Y NO EL REDACTOR INICIAL, AUTOR O AUTOR DE APORTACIONES) ASUMIRÁ LOS COSTES DE TODA REPARACIÓN, MANTENIMIENTO O CORRECCIÓN NECESARIOS. ESTA EXENCIÓN DE RESPONSABILIDAD SOBRE LA GARANTÍA ES UNA PARTE ESENCIAL DE ESTA LICENCIA. NO SE AUTORIZA EL USO DE NINGÚN DOCUMENTO NI VERSIÓN MODIFICADA DE ÉSTE POR EL PRESENTE, SALVO DENTRO DEL CUMPLIMIENTO DE LA EXENCIÓN DE RESPONSABILIDAD;Y</para> + </listitem> + <listitem> + <para>EN NINGUNA CIRCUNSTANCIA NI BAJO NINGUNA TEORÍA LEGAL, SEA POR ERROR (INCLUYENDO NEGLIGENCIA) CONTRATO O DOCUMENTO DE OTRO TIPO, EL AUTOR, EL ESCRITOR INICIAL, EL AUTOR DE APORTACIONES NI NINGÚN DISTRIBUIDOR DEL DOCUMENTO O VERSIÓN MODIFICADA DEL DOCUMENTO, NI NINGÚN PROVEEDOR DE NINGUNA DE ESAS PARTES, SERÁ RESPONSABLE ANTE NINGUNA PERSONA POR NINGÚN DAÑO DIRECTO, INDIRECTO, ESPECIAL, INCIDENTAL O DERIVADO DE NINGÚN TIPO, INCLUYENDO, SIN LIMITACIÓN DAÑOS POR PÉRDIDA DE FONDO DE COMERCIO, PARO TÉCNICO, FALLO INFORMÁTICO O AVERÍA O CUALQUIER OTRO POSIBLE DAÑO O AVERÍA DERIVADO O RELACIONADO CON EL USO DEL DOCUMENTO O SUS VERSIONES MODIFICADAS, AUNQUE DICHA PARTE HAYA SIDO INFORMADA DE LA POSIBILIDAD DE QUE SE PRODUJESEN ESOS DAÑOS.</para> + </listitem> + </orderedlist></para> </legalnotice> diff --git a/docs/uk/gdm.xml b/docs/uk/gdm.xml index 8b6d2cb8..1b8ba318 100644 --- a/docs/uk/gdm.xml +++ b/docs/uk/gdm.xml @@ -59,18 +59,31 @@ <para>Більшість назв, що використовуються компаніями для розповсюдження їх продуктів та послуг є торговими марками. Якщо такі назви зустрічаються у документації з GNOME та учасникам проекту документування GNOME відомо, що вони є торговими марками, тоді ці назви пишуться великими літерами або починаються з великої літери.</para> - <para>ДОКУМЕНТ ТА ЗМІНЕНІ ВЕРСІЇ ЦЬОГО ДОКУМЕНТУ ПОСТАЧАЮТЬСЯ НА УМОВАХ ВІЛЬНОЇ ЛІЦЕНЗІЇ ДЛЯ ДОКУМЕНТАЦІЇ GNU З ПОДАЛЬШИМ РОЗУМІННЯМ ЩО: <orderedlist><listitem><para>ДОКУМЕНТ НАДАЄТЬСЯ "ЯК Є", БЕЗ БУДЬ-ЯКИХ ГАРАНТІЇ, ЯВНИХ ЧИ НЕЯВНИХ, ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ГАРАНТІЙ ЩО ЦЕЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ ДОКУМЕНТА ВІЛЬНІ ВІД ДЕФЕКТІВ, ПРИДАТНІ ДО ПРОДАЖУ, ВІДПОВІДАЮТЬ ПЕВНІЙ МЕТІ АБО НЕ ПОРУШУЮТЬ ЧИЇСЬ ПРАВА. ВЕСЬ РИЗИК ЗА ЯКІСТЬ, ТОЧНІСТЬ, ТА ЧИННІСТЬ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНИХ ВЕРСІЙ ЛЕЖИТЬ НА ВАС. ЯКЩО БУДЬ-ЯКИЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ БУДУТЬ ВИЗНАНІ ДЕФЕКТНИМИ У БУДЬ-ЯКОМУ ВІДНОШЕННІ, ВИ (НЕ ПОЧАТКОВИЙ УКЛАДАЧ, АВТОР АБО БУДЬ-ЯКИЙ СПІВАВТОР) БЕРЕТЕ НА СЕБЕ ВИТРАТИ ЗА БУДЬ-ЯКЕ НЕОБХІДНЕ ОБСЛУГОВУВАННЯ, РЕМОНТ ЧИ ВИПРАВЛЕННЯ. ЦЯ ВІДМОВА ВІД ГАРАНТІЙ СКЛАДАЄ ВАЖЛИВУ ЧАСТИНУ ЦІЄЇ ЛІЦЕНЗІЇ. НЕ ДОПУСКАЄТЬСЯ ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНОЇ ВЕРСІЇ БЕЗ ПРИЙНЯТТЯ ЦІЄЇ ВІДМОВИ; ТА</para></listitem><listitem><para>НІ ЗА ЯКИХ ОБСТАВИН ТА ЗА БУДЬ-ЯКОГО ЗАКОНОДАВСТВА, ЧИ ТО ГРОМАДЯНСЬКОЇ ВІДПОВІДАЛЬНОСТІ (ВКЛЮЧАЮЧИ ХАЛАТНІСТЬ), ДОГОВОРУ, ЧИ ЧОГОСЬ ІНШОГО, АВТОР, ПОЧАТКОВИЙ УКЛАДАЧ, БУДЬ-ЯКИЙ СПІВАВТОР, АБО ДИСТРИБ'ЮТОР ДОКУМЕНТУ ЧИ ЗМІНЕНОЇ ВЕРСІЇ ДОКУМЕНТУ, АБО БУДЬ-ЯКИЙ ПОСТАЧАЛЬНИК БУДЬ-ЯКОЇ З ЦИХ СТОРІН, НЕ НЕСЕ ВІДПОВІДАЛЬНІСТЬ ПЕРЕД БУДЬ-ЯКОЮ ОСОБОЮ ЗА БУДЬ-ЯКІ ПРЯМІ, НЕПРЯМІ, ОСОБЛИВІ, ВИПАДКОВІ, АБО ІСТОТНІ ЗБИТКИ БУДЬ-ЯКОГО ХАРАКТЕРУ ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ЗБИТКАМИ ВІД ВТРАТИ ПРЕСТИЖУ, ЗУПИНКИ РОБОТИ, ЗБОЇВ АБО НЕСПРАВНОСТЕЙ КОМП'ЮТЕРА, АБО БУДЬ-ЯКІ ІНШІ ЗБИТКИ АБО ВТРАТИ ЩО ВИНИКЛИ БЕЗВІДНОСНО АБО ВНАСЛІДОК ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ ТА ЗМІНЕНИХ ВЕРСІЙ ЦЬОГО ДОКУМЕНТУ, НАВІТЬ ЯКЩО ЦІ СТОРОНИ, МОЖЛИВО, БУЛИ ПРОІНФОРМОВАНІ ПРО МОЖЛИВІСТЬ ТАКИХ ЗБИТКІВ.</para></listitem></orderedlist></para> + <para>ДОКУМЕНТ ТА ЗМІНЕНІ ВЕРСІЇ ЦЬОГО ДОКУМЕНТУ ПОСТАЧАЮТЬСЯ НА УМОВАХ ВІЛЬНОЇ ЛІЦЕНЗІЇ ДЛЯ ДОКУМЕНТАЦІЇ GNU З ПОДАЛЬШИМ РОЗУМІННЯМ ЩО: <orderedlist> + <listitem> + <para>ДОКУМЕНТ НАДАЄТЬСЯ "ЯК Є", БЕЗ БУДЬ-ЯКИХ ГАРАНТІЇ, ЯВНИХ ЧИ НЕЯВНИХ, ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ГАРАНТІЙ ЩО ЦЕЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ ДОКУМЕНТА ВІЛЬНІ ВІД ДЕФЕКТІВ, ПРИДАТНІ ДО ПРОДАЖУ, ВІДПОВІДАЮТЬ ПЕВНІЙ МЕТІ АБО НЕ ПОРУШУЮТЬ ЧИЇСЬ ПРАВА. ВЕСЬ РИЗИК ЗА ЯКІСТЬ, ТОЧНІСТЬ, ТА ЧИННІСТЬ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНИХ ВЕРСІЙ ЛЕЖИТЬ НА ВАС. ЯКЩО БУДЬ-ЯКИЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ БУДУТЬ ВИЗНАНІ ДЕФЕКТНИМИ У БУДЬ-ЯКОМУ ВІДНОШЕННІ, ВИ (НЕ ПОЧАТКОВИЙ УКЛАДАЧ, АВТОР АБО БУДЬ-ЯКИЙ СПІВАВТОР) БЕРЕТЕ НА СЕБЕ ВИТРАТИ ЗА БУДЬ-ЯКЕ НЕОБХІДНЕ ОБСЛУГОВУВАННЯ, РЕМОНТ ЧИ ВИПРАВЛЕННЯ. ЦЯ ВІДМОВА ВІД ГАРАНТІЙ СКЛАДАЄ ВАЖЛИВУ ЧАСТИНУ ЦІЄЇ ЛІЦЕНЗІЇ. НЕ ДОПУСКАЄТЬСЯ ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНОЇ ВЕРСІЇ БЕЗ ПРИЙНЯТТЯ ЦІЄЇ ВІДМОВИ; ТА</para> + </listitem> + <listitem> + <para>НІ ЗА ЯКИХ ОБСТАВИН ТА ЗА БУДЬ-ЯКОГО ЗАКОНОДАВСТВА, ЧИ ТО ГРОМАДЯНСЬКОЇ ВІДПОВІДАЛЬНОСТІ (ВКЛЮЧАЮЧИ ХАЛАТНІСТЬ), ДОГОВОРУ, ЧИ ЧОГОСЬ ІНШОГО, АВТОР, ПОЧАТКОВИЙ УКЛАДАЧ, БУДЬ-ЯКИЙ СПІВАВТОР, АБО ДИСТРИБ'ЮТОР ДОКУМЕНТУ ЧИ ЗМІНЕНОЇ ВЕРСІЇ ДОКУМЕНТУ, АБО БУДЬ-ЯКИЙ ПОСТАЧАЛЬНИК БУДЬ-ЯКОЇ З ЦИХ СТОРІН, НЕ НЕСЕ ВІДПОВІДАЛЬНІСТЬ ПЕРЕД БУДЬ-ЯКОЮ ОСОБОЮ ЗА БУДЬ-ЯКІ ПРЯМІ, НЕПРЯМІ, ОСОБЛИВІ, ВИПАДКОВІ, АБО ІСТОТНІ ЗБИТКИ БУДЬ-ЯКОГО ХАРАКТЕРУ ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ЗБИТКАМИ ВІД ВТРАТИ ПРЕСТИЖУ, ЗУПИНКИ РОБОТИ, ЗБОЇВ АБО НЕСПРАВНОСТЕЙ КОМП'ЮТЕРА, АБО БУДЬ-ЯКІ ІНШІ ЗБИТКИ АБО ВТРАТИ ЩО ВИНИКЛИ БЕЗВІДНОСНО АБО ВНАСЛІДОК ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ ТА ЗМІНЕНИХ ВЕРСІЙ ЦЬОГО ДОКУМЕНТУ, НАВІТЬ ЯКЩО ЦІ СТОРОНИ, МОЖЛИВО, БУЛИ ПРОІНФОРМОВАНІ ПРО МОЖЛИВІСТЬ ТАКИХ ЗБИТКІВ.</para> + </listitem> + </orderedlist></para> </legalnotice> - <releaseinfo>This manual describes version 2.14.0 of the GNOME Display Manager. It was last updated on 03/20/2006.</releaseinfo> + <releaseinfo> + This manual describes version 2.14.0 of the GNOME Display Manager. + It was last updated on 03/20/2006. + </releaseinfo> </articleinfo> <sect1 id="preface"> <title>Терміни та домовленості використані у цьому посібнику</title> - <para>This manual describes version 2.14.0 of the GNOME Display Manager. It was last updated on 03/20/2006.</para> + <para> + This manual describes version 2.14.0 of the GNOME Display Manager. + It was last updated on 03/20/2006. + </para> <para>Селектор - програма, що використовується для керування дисплеєм віддаленого вузла з локального дисплея (<command>gdmchooser</command>).</para> @@ -107,47 +120,174 @@ <sect2 id="stability"> <title>Стабільність інтерфейсу</title> - <para>The key/value pairs defined in the GDM configuration files and the location of these files are considered "stable" interfaces and should only change in ways that are backwards compatible. Note that this includes functionality like the GDM scripts (Init, PreSession, PostSession, PostLogin, XKeepsCrashing, etc.); directory locations (ServAuthDir, PidFile, etc.), system applications (SoundProgram), etc. Some configuration values depend on OS interfaces may need to be modified to work on a given OS. Typical examples are HaltCommand, RebootCommand, SuspendCommand, StandardXServer, Xnest, SoundProgram, and the "command" value for each "server-foo".</para> - - <para>Note: distributions often change the default values of keys to support their platform. Command-line interfaces for GDM programs installed to <filename><bin></filename> and <filename><sbin></filename> are considered stable. Refer to your distribution documentation to see if there are any distribution-specific changes to these GDM interfaces and what support exists for them.</para> - - <para>If issues are discovered that break compatibility, please file a bug with an "urgent" priority.</para> + <para> + The key/value pairs defined in the GDM configuration files and + the location of these files are considered "stable" interfaces + and should only change in ways that are backwards compatible. Note that + this includes functionality like the GDM scripts (Init, PreSession, + PostSession, PostLogin, XKeepsCrashing, etc.); directory locations + (ServAuthDir, PidFile, etc.), system applications (SoundProgram), etc. + Some configuration values depend on OS interfaces may need to be + modified to work on a given OS. Typical examples are HaltCommand, + RebootCommand, SuspendCommand, StandardXServer, Xnest, SoundProgram, + and the "command" value for each "server-foo". + </para> + + <para> + Note: distributions often change the default values of keys to support + their platform. Command-line interfaces for GDM programs installed to + <filename><bin></filename> and <filename><sbin></filename> + are considered stable. Refer to your distribution documentation to see + if there are any distribution-specific changes to these GDM interfaces + and what support exists for them. + </para> + + <para> + If issues are discovered that break compatibility, please file a bug + with an "urgent" priority. + </para> </sect2> <sect2 id="daemonov"> <title>Сервер GDM</title> - <para>The GDM daemon is responsible for managing displays on the system. This includes authenticating users, starting the user session, and terminating the user session. GDM is configurable and the ways it can be configured are described in the "Configuring GDM" section of this document. The <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename>, and <filename>PostSession</filename> scripts discussed below are discussed in this "Configuring GDM section".</para> - - <para>The GDM daemon supports a UNIX domain socket protocol which can be used to control aspects of its behavior and to query information. This protocol is described in the "Controlling GDM" section of this document.</para> - - <para>GDM can be asked to manage a display a number of ways. Local displays are always managed when GDM starts and will be restarted when a user's session is finished. Displays can be requested via XDMCP, flexible displays can be requested by running the <command>gdmflexiserver</command> command. Displays that are started on request are not restarted on session exit. GDM also provides the <command>gdmdynamic</command> command to allow easier management of displays on a multi-user server. These display types are discussed further in the next section.</para> + <para> + The GDM daemon is responsible for managing displays on the system. + This includes authenticating users, starting the user session, and + terminating the user session. GDM is configurable and the ways it can + be configured are described in the "Configuring GDM" section + of this document. The <filename>Init</filename>, + <filename>PostLogin</filename>, <filename>PreSession</filename>, + and <filename>PostSession</filename> scripts discussed below are + discussed in this "Configuring GDM section". + </para> + + <para> + The GDM daemon supports a UNIX domain socket protocol which can be used + to control aspects of its behavior and to query information. This + protocol is described in the "Controlling GDM" section of + this document. + </para> + + <para> + GDM can be asked to manage a display a number of ways. Local displays + are always managed when GDM starts and will be restarted when a user's + session is finished. Displays can be requested via XDMCP, flexible + displays can be requested by running the + <command>gdmflexiserver</command> command. Displays that are started + on request are not restarted on session exit. GDM also provides the + <command>gdmdynamic</command> command to allow easier management of + displays on a multi-user server. These display types are discussed + further in the next section. + </para> - <para>When the GDM daemon is asked to manage a display, it will fork an X server process, then run the <filename>Init</filename> script as the root user, and start the login GUI dialog as a slave process on the display. GDM can be configured to use either <command>gdmgreeter</command> (the default) or <command>gdmlogin</command> as the GUI dialog program. The <command>gdmlogin</command> program supports accessibility while the <command>gdmgreeter</command> program supports greater themeability. The GUI dialog is run as the unpriviledged "gdm" user/group which is described in the "Security" section below. The GUI dialog communicates with the daemon via a sockets protocol and via standard input/output. The slave, for example passes the username and password information to the GDM daemon via standard input/output so the daemon can handle the actual authentication.</para> - - <para>The login GUI dialog screen allows the user to select which session they wish to start and which language they wish to use. Sessions are defined by files that end in the .desktop extension and more information about these files can be found in the "Configuration" section. The user enters their name and password and if these successfully authenticate, GDM will start the requested session for the user. It is possible to configure GDM to avoid the authentication process by turning on the Automatic or Timed Login features in the GDM configuration. The login GUI can also be configured to provide additional features to the user, such as the Face Browser; the ability to halt, restart, or suspend the system; and/or edit the login configuration (after entering the root password).</para> - - <para>GDM, by default, will use Pluggable Authentication Modules (PAM) for authentication, but can also support regular crypt and shadow passwords on legacy systems. After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, and forks a slave process to start the requested session. This slave process runs the <filename>PreSession</filename> script as root, sets up the users environment, and starts the requested session. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN interface after user authentication to tell the X server to be restarted as the user instead of as root for added security. When the users session exits, the GDM daemon will run the <filename>PostSession</filename> script as root.</para> + <para> + When the GDM daemon is asked to manage a display, it will fork an + X server process, then run the <filename>Init</filename> script as the + root user, and start the login GUI dialog as a slave process on the + display. GDM can be configured to use either + <command>gdmgreeter</command> (the default) or + <command>gdmlogin</command> as the GUI dialog program. The + <command>gdmlogin</command> program supports accessibility while the + <command>gdmgreeter</command> program supports greater themeability. + The GUI dialog is run as the unpriviledged "gdm" user/group + which is described in the "Security" section below. The GUI + dialog communicates with the daemon via a sockets protocol and via + standard input/output. The slave, for example passes the username and + password information to the GDM daemon via standard input/output so + the daemon can handle the actual authentication. + </para> + + <para> + The login GUI dialog screen allows the user to select which session + they wish to start and which language they wish to use. Sessions are + defined by files that end in the .desktop extension and more + information about these files can be found in the + "Configuration" section. The user enters their name and + password and if these successfully authenticate, GDM will start the + requested session for the user. It is possible to configure GDM to + avoid the authentication process by turning on the Automatic or Timed + Login features in the GDM configuration. The login GUI can also be + configured to provide additional features to the user, such as the + Face Browser; the ability to halt, restart, or suspend the system; + and/or edit the login configuration (after entering the root password). + </para> + + <para> + GDM, by default, will use Pluggable Authentication Modules (PAM) for + authentication, but can also support regular crypt and shadow passwords + on legacy systems. After authenticating a user, the daemon runs the + <filename>PostLogin</filename> script as root, and forks a slave + process to start the requested session. This slave process runs the + <filename>PreSession</filename> script as root, sets up the users + environment, and starts the requested session. GDM keeps track of the + user's default session and language in the user's + <filename>~/.dmrc</filename> and will use these defaults if the user + did not pick a session or language in the login GUI. On Solaris, GDM + (since version 2.8.0.3) uses the SDTLOGIN interface after user + authentication to tell the X server to be restarted as the user instead + of as root for added security. When the users session exits, the GDM + daemon will run the <filename>PostSession</filename> script as root. + </para> </sect2> <sect2 id="displaytypes"> <title>Різні типи дисплеїв</title> - <para>GDM supports three different display types: static (local) displays, flexible (on-demand) displays, and XDMCP (remote) displays. The "X Server Definitions" and the "Local Static X Display Configuration" subsections of the "Configuration" section explains how these various types of displays are defined in the GDM configuration file.</para> + <para> + GDM supports three different display types: static (local) displays, + flexible (on-demand) displays, and XDMCP (remote) displays. The + "X Server Definitions" and the "Local Static X Display + Configuration" subsections of the "Configuration" + section explains how these various types of displays are defined in + the GDM configuration file. + </para> <para>Локальні статичні дисплеї завжди запускаються службою, якщо вони завершуються або вмирають, вони перезапускаються. GDM може запускати їх стільки, скільки буде потрібно. GDM також може керувати серверами, на яких він не керує власне самим процесом входу, це дозволяє використовувати GDM при створенні X-терміналів.</para> - <para>Flexible, or on demand displays, are started via the socket protocol with the <command>gdmflexiserver</command> command. This feature is only available to users logged in on the console and will display a new login screen. If a flexible display has previously been started on the console, running <command>gdmflexiserver</command> again will display a menu allowing users to switch back to a previous session or start a new flexible session. The <command>gdmflexiserver</command> locks the current session before starting a new flexible display, so the user's password must be entered before returning to an existing session. The <command>gdmflexiserver</command> command can also be used to launch nested <command>Xnest</command> display. These are launched in a window in the user's current session. Nested displays can be started even if not logged into the console and are started by running the <command>gdmflexiserver -n</command> command. Flexible displays are not restarted when the user session ends. Flexible displays require virtual terminal (VT) support in the kernel, and will not be available if not supported (such as on Solaris). Nested displays require that the X server supports Xnest.</para> + <para> + Flexible, or on demand displays, are started via the socket protocol + with the <command>gdmflexiserver</command> command. This feature is + only available to users logged in on the console and will display a new + login screen. If a flexible display has previously been started on + the console, running <command>gdmflexiserver</command> again will + display a menu allowing users to switch back to a previous session + or start a new flexible session. The <command>gdmflexiserver</command> + locks the current session before starting a new flexible display, so + the user's password must be entered before returning to an existing + session. The <command>gdmflexiserver</command> command can also be + used to launch nested <command>Xnest</command> display. These are + launched in a window in the user's current session. Nested displays + can be started even if not logged into the console and are started by + running the <command>gdmflexiserver -n</command> command. Flexible + displays are not restarted when the user session ends. Flexible + displays require virtual terminal (VT) support in the kernel, and will + not be available if not supported (such as on Solaris). Nested + displays require that the X server supports Xnest. + </para> <para>Останній тип дисплеїв - віддалені XDMCP дисплеї, які описані у наступному розділі. Якщо цей параметр увімкнено, віддалені вузли можуть з'єднуватись з GDM та показувати вікно входу. Для цього типу сеансів є відмінності, наприклад, у меню <quote>Дії</quote> не показуються пункти, які дозволяють вимикати, перезавантажувати, або налаштовувати GDM.</para> - <para>Displays started via the <command>gdmdynamic</command> command are treated as local displays, so they are restarted automatically on when the session exits. This command is intended to more effectively manage the displays on a multi-user server (many displays connected to a single server).</para> + <para> + Displays started via the <command>gdmdynamic</command> command are + treated as local displays, so they are restarted automatically on + when the session exits. This command is intended to more effectively + manage the displays on a multi-user server (many displays connected + to a single server). + </para> </sect2> <sect2 id="xdmcp"> <title>XDMCP</title> - <para>The GDM daemon can be configured to listen for and manage X Display Manage Protocol (XDMCP) requests from remote displays. By default XDMCP support is turned off, but can be enabled if desired. If GDM is built with TCP Wrapper support, then the daemon will only grant access to hosts specified in the GDM service section in the TCP Wrappers configuration file.</para> + <para> + The GDM daemon can be configured to listen for and manage X Display + Manage Protocol (XDMCP) requests from remote displays. By default + XDMCP support is turned off, but can be enabled if desired. If GDM is + built with TCP Wrapper support, then the daemon will only grant access + to hosts specified in the GDM service section in the TCP Wrappers + configuration file. + </para> <para>GDM включає декілька заходів, які роблять його більш стійким до атак типу <quote>відмова у обслуговуванні</quote> на службу XDMCP. Можна налаштувати значну кількість параметрів протоколу, час очікування з'єднання, тощо. Проте, типові значення підійдуть для більшості систем. Не змінюйте їх, якщо не розумієте їх вплив на систему.</para> @@ -155,16 +295,35 @@ <para>GDM можна налаштувати на обробку INDIRECT запитів та відображення селектора вузлів на віддаленому дисплеї. GDM запам'ятовує вибір користувача та пересилає наступні запити вибраному менеджеру. GDM також підтримує розширення до протоколу, яке змушує забути про перенаправлення одразу після успішного з'єднання користувача. Це розширення підтримується якщо з обох сторін сервери GDM. Розширення прозоре і ігнорується XDM та іншими серверами, що підтримують XDMCP.</para> - <para>Refer to the "Security" section for information about security concerns when using XDMCP.</para> + <para> + Refer to the "Security" section for information about + security concerns when using XDMCP. + </para> </sect2> <sect2 id="secureremote"> <title>Безпечне віддалене з'єднання через SSH</title> - <para>As explained in the "Security" section, XDMCP does not use any kind of encryption and as such is inherently insecure. As XDMCP uses UDP as a network transport layer, it is not possible to simply secure it through an SSH tunnel.</para> - - <para>To remedy this problem, gdm can be configured at compilation-time with the option --enable-secureremote, in which case gdm proposes as a built-in session a session called "Secure Remote Connection". Starting such a session allows the user to enter the name or the address of the host on which to connect; provided the said host runs an SSH server, the user then gets connected to the server on which the default X session is started and displayed on the local host.</para> + <para> + As explained in the "Security" section, XDMCP does not use + any kind of encryption and as such is inherently insecure. As XDMCP + uses UDP as a network transport layer, it is not possible to simply + secure it through an SSH tunnel. + </para> + + <para> + To remedy this problem, gdm can be configured at compilation-time with + the option --enable-secureremote, in which case gdm proposes as a + built-in session a session called "Secure Remote Connection". + Starting such a session allows the user to enter the name or the + address of the host on which to connect; provided the said host runs an + SSH server, the user then gets connected to the server on which the + default X session is started and displayed on the local host. + </para> - <para>Using this session allows a much more secure network connection and only necessitates to have an SSH server running on the remote host.</para> + <para> + Using this session allows a much more secure network connection and + only necessitates to have an SSH server running on the remote host. + </para> </sect2> <sect2 id="gtkgreeter"> @@ -192,19 +351,73 @@ <sect2 id="facebrowser"> <title>Переглядач портретів GDM</title> - <para>GDM supports a face browser which will display a list of users who can login and an icon for each user. This feature can be used with the GTK+ Greeter if the <filename>Browser</filename> configuration option is set to "true". This feature can be used with the Themed Greeter if using a GDM theme which includes a "userlist" item type is defined, such as "happygnome-list"</para> - - <para>By default, the face browser is disabled since revealing usernames on the login screen is not appropriate on many systems for security reasons. Also GDM requires some setup to specify which users should be visible. Setup can be done on the "Users" tab in <command>gdmsetup</command>. This feature is most practical to use on a system with a smaller number of users.</para> + <para> + GDM supports a face browser which will display a list of users who + can login and an icon for each user. This feature can be used with + the GTK+ Greeter if the <filename>Browser</filename> configuration + option is set to "true". This feature can be used with + the Themed Greeter if using a GDM theme which includes a + "userlist" item type is defined, such as + "happygnome-list" + </para> + + <para> + By default, the face browser is disabled since revealing usernames on + the login screen is not appropriate on many systems for security + reasons. Also GDM requires some setup to specify which users should + be visible. Setup can be done on the "Users" tab in + <command>gdmsetup</command>. This feature is most practical to use + on a system with a smaller number of users. + </para> <para>Зображення можуть бути встановлені глобально адміністратором, або братись з домашніх каталогів користувачів. Якщо вони встановлені глобально, вони мають знаходитись у каталозі <filename><share>/pixmaps/faces/</filename> (шлях до каталогу можна змінити використовуючи конфігураційну змінну <filename>GlobalFaceDir</filename>) та назва файлу повинна відповідати імені користувача, з необов'язковим суфіксом <filename>.png</filename>. Значки програм з глобального каталогу мають бути доступні для читання користувачу GDM. Проте, програма сервера передає зображення програмі привітання та таким права на читання потрібні не не користувачу "gdm", а root.</para> - <para>Users may run the <command>gdmphotosetup</command> command to configure the image to use for their userid. This program properly scales the file down if it is larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> configuration options and places the icon in a file called <filename>~/.face</filename>. Although <command>gdmphotosetup</command> scales user images automatically, this does not guarantee that user images are properly scaled since a user may create their <filename>~/.face</filename> file by hand.</para> + <para> + Users may run the <command>gdmphotosetup</command> command to + configure the image to use for their userid. This program properly + scales the file down if it is larger than the + <filename>MaxIconWidth</filename> or + <filename>MaxIconHeight</filename> configuration options and places the + icon in a file called <filename>~/.face</filename>. Although + <command>gdmphotosetup</command> scales user images automatically, + this does not guarantee that user images are properly scaled since + a user may create their <filename>~/.face</filename> file by hand. + </para> - <para>GDM will first look for the user's face image in <filename>~/.face</filename>. If not found, it will try <filename>~/.face.icon</filename>. If still not found, it will use the value defined for "face/picture=" in the <filename>~/.gnome2/gdm</filename> file. Lastly, it will try <filename>~/.gnome2/photo</filename> and <filename>~/.gnome/photo</filename> which are deprecated and supported for backwards compatibility.</para> - - <para>If a user has no defined face image, GDM will use the "stock_person" icon defined in the current GTK+ theme. If no such image is defined, it will fallback to the image specified in the <filename>DefaultFace</filename> configuration option, normally <filename><share>/pixmaps/nobody.png</filename>.</para> + <para> + GDM will first look for the user's face image in + <filename>~/.face</filename>. If not found, it will try + <filename>~/.face.icon</filename>. If still not found, it will + use the value defined for "face/picture=" in the + <filename>~/.gnome2/gdm</filename> file. Lastly, it will try + <filename>~/.gnome2/photo</filename> and + <filename>~/.gnome/photo</filename> which are deprecated and + supported for backwards compatibility. + </para> + + <para> + If a user has no defined face image, GDM will use the + "stock_person" icon defined in the current GTK+ theme. If no + such image is defined, it will fallback to the image specified in the + <filename>DefaultFace</filename> configuration option, normally + <filename><share>/pixmaps/nobody.png</filename>. + </para> - <para>Please note that loading and scaling face icons located in user home directories can be a very time-consuming task. Since it not practical to load images over NIS or NFS, GDM does not attempt to load face images from remote home directories. Furthermore, GDM will give up loading face images after 5 seconds of activity and will only display the users whose pictures it has gotten so far. The <filename>Include</filename> configuration option can be used to specify a set of users who should appear on the face browser. As long as the users to include is of a reasonable size, there should not be a problem with GDM being unable to access the face images. To work around such problems, it is recommended to place face images in the directory specified by the <filename>GlobalFaceDir</filename> configuration option.</para> + <para> + Please note that loading and scaling face icons located in user home + directories can be a very time-consuming task. Since it not + practical to load images over NIS or NFS, GDM does not attempt to + load face images from remote home directories. Furthermore, GDM will + give up loading face images after 5 seconds of activity and will + only display the users whose pictures it has gotten so far. The + <filename>Include</filename> configuration option can be used to + specify a set of users who should appear on the face browser. As + long as the users to include is of a reasonable size, there should + not be a problem with GDM being unable to access the face images. + To work around such problems, it is recommended to place face images + in the directory specified by the <filename>GlobalFaceDir</filename> + configuration option. + </para> <para>Для керування відображенням портретів у конфігураційному файлі є декілька параметрів. Якщо параметр <filename>IncludeAll</filename> встановлено у true, тоді у параметрі <filename>Include</filename> вказується список розділених комою імен користувачів, які будуть відображатись. Не залежно від параметра <filename>IncludeAll</filename> не будуть відображатись будь-які користувачі, перелічені у списку <filename>Exclude</filename> та користувачі, ідентифікатор користувача (UID) яких менший за <filename>MinimalUID</filename>. <filename>IncludeAll</filename> не рекомендується для систем, на яких паролі передаються через мережу (наприклад NIS), тому що передавання великої кількості зображень через мережу може бути досить повільним.</para> @@ -244,9 +457,31 @@ <sect2 id="performance"> <title>Швидкодія GDM</title> - <para>To speed performance it is possible to build GDM so that it will preload libraries when GDM first displays a greeter program. This has been shown to speed first time login since these libraries can be loaded into memory while the user types in their username and password.</para> - - <para>To use this feature, configure GDM with the <command>--with-prefetch</command> option. This will cause GDM to install the <command>gdmprefetch</command> program to the <filename>libexecdir</filename> directory, install the <filename>gdmprefetchlist</filename> to the <filename><etc>/gdm</filename> directory, and set the <filename>PreFetchProgram</filename> configuration variable so that the <command>gdmprefetch</command> program is called with the default <filename>gdmprefetchlist</filename> file. The default <filename>gdmprefetchlist</filename> file was optimized for a GNOME desktop running on Solaris, so may need fine-tuning on other systems. Alternative prefetchlist files can be contributed to the "gdm" category in <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink>, so that they can be included in future GDM releases.</para> + <para> + To speed performance it is possible to build GDM so that it will + preload libraries when GDM first displays a greeter program. This + has been shown to speed first time login since these libraries can + be loaded into memory while the user types in their username and + password. + </para> + + <para> + To use this feature, configure GDM with the + <command>--with-prefetch</command> option. This will cause GDM to + install the <command>gdmprefetch</command> program to the + <filename>libexecdir</filename> directory, install the + <filename>gdmprefetchlist</filename> to the + <filename><etc>/gdm</filename> directory, and set the + <filename>PreFetchProgram</filename> configuration variable so that the + <command>gdmprefetch</command> program is called with the default + <filename>gdmprefetchlist</filename> file. The default + <filename>gdmprefetchlist</filename> file was optimized + for a GNOME desktop running on Solaris, so may need fine-tuning on + other systems. Alternative prefetchlist files can be contributed + to the "gdm" category in + <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink>, + so that they can be included in future GDM releases. + </para> </sect2> </sect1> @@ -255,31 +490,88 @@ <sect2 id="PAM"> <title>PAM</title> - <para>GDM uses PAM for username/authentication, though if your machine does not support PAM you can build GDM to work with shadow passwords and crypt.</para> - - <para>PAM stands for Pluggable Authentication Module, and is used by most programs that request username/password authentication on your computer. It allows the user to configure different authentication behavior for different programs.</para> - - <para>Some GDM features (like turning on automatic login) may require that you update your PAM configuration. PAM has different, but similar, interfaces on different operating systems, so check your pam.d or pam.conf man page for details about how to configure it. Make sure to read the PAM documentation (e.g. pam.d/pam.conf man page) and be comfortable with the security implications of any changes you intend to make to your configuration.</para> - - <para>If there is no entry for GDM in your system's PAM configuration file, then features like tomatic login may not work. Not having an entry will causes GDM to use default behavior, conservative settings are recommended and probably shipped with your distribution.</para> - - <para>If you wish to make GDM work with other types of authentication mechanisms (such as a SmartCard), then you should implement this by writing a PAM module rather than by trying to modify the GDM code directly. Refer to the PAM documentation on your system. This issue has been discussed on the <address><email>gdm-list@gnome.org</email></address> mail list, so you can refer to the list archives for more information.</para> + <para> + GDM uses PAM for username/authentication, though if your machine + does not support PAM you can build GDM to work with shadow + passwords and crypt. + </para> + + <para> + PAM stands for Pluggable Authentication Module, and is used by + most programs that request username/password authentication on + your computer. It allows the user to configure different + authentication behavior for different programs. + </para> + + <para> + Some GDM features (like turning on automatic login) may require that + you update your PAM configuration. PAM has different, but similar, + interfaces on different operating systems, so check your pam.d or + pam.conf man page for details about how to configure it. Make sure to + read the PAM documentation (e.g. pam.d/pam.conf man page) and + be comfortable with the security implications of any changes + you intend to make to your configuration. + </para> + + <para> + If there is no entry for GDM in your system's PAM configuration + file, then features like tomatic login may not work. Not having an + entry will causes GDM to use default behavior, conservative settings + are recommended and probably shipped with your distribution. + </para> + + <para> + If you wish to make GDM work with other types of authentication + mechanisms (such as a SmartCard), then you should implement this by + writing a PAM module rather than by trying to modify the GDM + code directly. Refer to the PAM documentation on your system. This + issue has been discussed on the + <address><email>gdm-list@gnome.org</email></address> mail list, + so you can refer to the list archives for more information. + </para> </sect2> <sect2 id="gdmuser"> <title>Користувач GDM</title> - <para>For security reasons a dedicated user and group id are required for proper operation! The need to be able to write Xauth files is why user "nobody" is not appropriate for gdm.</para> + <para> + For security reasons a dedicated user and group id are required for + proper operation! The need to be able to write Xauth files is why + user "nobody" is not appropriate for gdm. + </para> <para>Зазвичай GDM сервер запускається від імені адміністратора (root). Але GDM також має призначені ідентифікатори користувача (uid) та групи (gid), якими він користується для запуску графічного інтерфейсу, тобто <command>gdmgreeter</command> та <command>gdmlogin</command>. Вона налаштовуються у параметрах <filename>User</filename> та <filename>Group</filename> у файлі конфігурації GDM. Користувач та група мають існувати перед запуском "make install". Зазвичай користувач та група GDM називається "gdm". </para> - <para>This userid is used to run the GDM GUI programs required for login. All functionality that requires root authority is done by the GDM daemon process. This design ensures that if the GUI programs are somehow exploited, only the dedicated user privileges are available.</para> + <para> + This userid is used to run the GDM GUI programs required for login. + All functionality that requires root authority is done by the GDM + daemon process. This design ensures that if the GUI programs are + somehow exploited, only the dedicated user privileges are available. + </para> <para> слід зауважити, що користувач та група GDM мають деякі привілеї, які іноді можуть становити загрозу безпеці. По-перше, вони мають доступ до каталогу авторизації X-сервера. Також GDM повинен мати право на читання та запис ключів Xauth у <filename><var>/lib/gdm</filename>. Власником цього каталогу має бути root:gdm, а права доступу 1770. Ці права призначаються каталогу при виконанні "make install". Служба GDM буде встановлювати цьому каталогу правильні права, якщо вони відрізняються. </para> - <para>The danger is that someone who gains the GDM user/group privileges can then connect to any session. So you should not, under any circumstances, make this some user/group which may be easy to get access to, such as the user <filename>nobody</filename>. Users who gain access to the "gdm" user could also modify the Xauth keys causing Denial-Of-Service attacks. Also if a person gains the ability to run programs as the user "gdm", it would be possible to snoop on running GDM processes, including usernames and passwords as they are being typed in.</para> - - <para>Distributions and system administrators using GDM are expected to setup the dedicated user properly. It is recommended that this userid be configured to disallow login and to not have a default shell. Distributions and system administrators should set up the filesystem to ensure that the GDM user does not have read or write access to sensitive files.</para> + <para> + The danger is that someone who gains the GDM user/group privileges + can then connect to any session. So you should not, under any + circumstances, make this some user/group which may be easy to get + access to, such as the user <filename>nobody</filename>. + Users who gain access to the "gdm" user could also + modify the Xauth keys causing Denial-Of-Service attacks. Also + if a person gains the ability to run programs as the user + "gdm", it would be possible to snoop on running GDM + processes, including usernames and passwords as they are being + typed in. + </para> + + <para> + Distributions and system administrators using GDM are expected to + setup the dedicated user properly. It is recommended that this + userid be configured to disallow login and to not have a default + shell. Distributions and system administrators should set up + the filesystem to ensure that the GDM user does not have read or + write access to sensitive files. + </para> </sect2> <sect2 id="xauth"> @@ -301,7 +593,10 @@ <para>Також буде розумно блокувати на брандмауері всі порти X сервера (TCP порт 6000 + номер дисплею). Зауважте, що різні частини GDM використовують дисплеї з номером 20 та більше (наприклад, при запуску серверів за вимогою).</para> - <para>X is not a very safe protocol for leaving on the net, and XDMCP is even less safe.</para> + <para> + X is not a very safe protocol for leaving on the net, and XDMCP is + even less safe. + </para> </sect2> <sect2 id="nfssecurity"> @@ -313,13 +608,26 @@ <sect2 id="xdmcpsecurity"> <title>Безпека XDCMP</title> - <para>Even though your display is protected by cookies, XEvents and thus keystrokes typed when entering passwords will still go over the wire in clear text. It is trivial to capture these.</para> + <para> + Even though your display is protected by cookies, XEvents and thus + keystrokes typed when entering passwords will still go over the wire in + clear text. It is trivial to capture these. + </para> <para>Головним чином XDMCP використовується для тонких клієнтів у лабораторних умовах. Цім тонким клієнтам для доступу до сервера необхідна лише мережа, та, здається, найкращою політикою безпеки буде тримати їх у окремій мережі, до якої неможливо отримати доступ із зовнішнього світу, а зв'язок є лише з сервером. Єдиною точкою доступу до зовнішнього світу повинен бути сервер.</para> - <para>The above sections "X Server Authentication Scheme" and "Firewall Security" also contain important information about using XDMCP securely. The next section also discusses how to set up XDMCP access control.</para> - - <para>To workaround the inherent insecurity of XDMCP, gdm proposes a default built-in session that uses SSH to encrypt the remote connection. See the section "Securing remote connection through SSH" above.</para> + <para> + The above sections "X Server Authentication Scheme" and + "Firewall Security" also contain important information about + using XDMCP securely. The next section also discusses how to set up + XDMCP access control. + </para> + + <para> + To workaround the inherent insecurity of XDMCP, gdm proposes a default + built-in session that uses SSH to encrypt the remote connection. See + the section "Securing remote connection through SSH" above. + </para> </sect2> <sect2 id="xdmcpaccess"> @@ -344,11 +652,32 @@ gdm: .your.domain <para>У цьому розділі описується налаштовування GDM та формат конфігураційного файлу. Проте, для налаштовування GDM ви можете скористуватись графічною програмою <command>gdmsetup</command>. Але графічна програма не дозволяє налаштувати кожен аспект GDM.</para> - <para>You can either run <command>gdmsetup</command> as root or turn on the GDM configuration feature that allows you to run <command>gdmsetup</command> from the login screen (where it will run as root). If you believe running root owned GUI's is a security risk, then you would want to edit the files by hand.</para> - - <para>If you are a distribution and want to set machine defaults, you should edit the <filename><share>/gdm/defaults.conf</filename> file rather than editing the <filename><etc>/gdm/custom.conf</filename> file, so the distribution changes are preserved as defaults.</para> - - <para>If you want to change configuration by hand, edit the <filename><etc>/gdm/custom.conf</filename> file and make sure the keyname=value pair you want is included in the appropriate section. For example, to change the "Greeter" key in the "daemon" section, make sure the daemon section of the <filename><etc>/gdm/custom.conf</filename> file has the value like in this example. The modified option does not have to come anywhere in the section. The <command>gdmsetup</command> program manages editing these files for you.</para> + <para> + You can either run <command>gdmsetup</command> as root or turn on the GDM + configuration feature that allows you to run <command>gdmsetup</command> + from the login screen (where it will run as root). If you believe + running root owned GUI's is a security risk, then you would want to edit + the files by hand. + </para> + + <para> + If you are a distribution and want to set machine defaults, you should + edit the <filename><share>/gdm/defaults.conf</filename> file rather + than editing the <filename><etc>/gdm/custom.conf</filename> + file, so the distribution changes are preserved as defaults. + </para> + + <para> + If you want to change configuration by hand, edit the + <filename><etc>/gdm/custom.conf</filename> file and make + sure the keyname=value pair you want is included in the appropriate + section. For example, to change the "Greeter" key in the + "daemon" section, make sure the daemon section of the + <filename><etc>/gdm/custom.conf</filename> file has the value + like in this example. The modified option does not have to come anywhere + in the section. The <command>gdmsetup</command> program manages editing + these files for you. + </para> <screen> [daemon] @@ -359,9 +688,30 @@ Greeter=/usr/lib/gdmgreeter <para>Деякі змінні у початковому конфігураційному файлі закоментовані, інші - ні. Це зроблено через те, що типові значення деяких змінних можуть змінитись у майбутньому. GDM вважає коментарями рядки, що починаються зі знаку "#", та ігнорує їх.</para> - <para>The <filename><share>/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename><etc>/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename><etc>/gdm/custom.conf</filename> file override the values in the main <filename><share>/gdm/defaults.conf</filename> file. Running the <command>gdmsetup</command> command will cause the <filename><etc>/gdm/custom.conf</filename> to be modified with the user's configuration choices and will cause any running GDM GUI programs to automatically update. Previous to version 2.13.0.4 GDM only supported the <filename><etc>/gdm/gdm.conf</filename> file, so if using an older version of GDM just edit that file directly.</para> - - <para>The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may also be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used.</para> + <para> + The <filename><share>/gdm/defaults.conf</filename> file contains + the default configuration choices for GDM, and should not be modified by + the user. The <filename><etc>/gdm/custom.conf</filename> file + is where users may specify their custom configuration choices. + Configuration options specified in the + <filename><etc>/gdm/custom.conf</filename> file override the + values in the main <filename><share>/gdm/defaults.conf</filename> + file. Running the <command>gdmsetup</command> command will cause the + <filename><etc>/gdm/custom.conf</filename> to be modified with + the user's configuration choices and will cause any running GDM GUI + programs to automatically update. Previous to version 2.13.0.4 + GDM only supported the <filename><etc>/gdm/gdm.conf</filename> + file, so if using an older version of GDM just edit that file directly. + </para> + + <para> + The location of the configuration files may be controlled via the + <command>--with-defaults-conf</command> and + <command>--with-custom-conf</command> configuration options. The GDM + daemon --config option may also be used to specify the configuration + file location. The GDM daemon must be restarted to change the + configuration file being used. + </para> <para><filename><share>/gdm/factory-defaults.conf</filename> - конфігураційний файл, що постачається із службою. Він може знадобитись щоб побачити зміни у файлі <filename><share>/gdm/defaults.conf</filename> .</para> @@ -382,7 +732,16 @@ PostSession/ <para><filename>locale.alias</filename> - файл, який схожий на системний файл псевдонімів локалізацій, але насправді вони відрізняються. У ньому перелічені доступні у вашій системі мови. Підтримка кожної мови перевіряється, перш ніж показати її користувачу у списку.</para> - <para><filename>Xsession</filename> is a script which sets up a user session and then executes the users choice of session. Note that the session script is typically started via the <filename>desktop</filename> file associated with the session the user has picked. Some sessions may start the user's session via a different mechanism than the <filename>Xsession</filename> script, so please check the appropriate <filename>desktop</filename> before assuming a session startup issue is being caused by this file.</para> + <para> + <filename>Xsession</filename> is a script which sets up a user session + and then executes the users choice of session. Note that the session + script is typically started via the <filename>desktop</filename> + file associated with the session the user has picked. Some + sessions may start the user's session via a different mechanism than + the <filename>Xsession</filename> script, so please check the + appropriate <filename>desktop</filename> before assuming a session + startup issue is being caused by this file. + </para> <para><filename>XKeepsCrashing</filename> - сценарій, який запускається коли X-сервер аварійно завершується декілька разів. Типовий сценарій працює у більшості дистрибутивів Linux. Він може запустити програму налаштовування X-Window, за умови, що особа за консоллю знає пароль адміністратора (root).</para> @@ -421,13 +780,48 @@ PostSession/ <sect2 id="configfile"> <title>Конфігураційний файл - <filename>defaults.conf</filename> та <filename>custom.conf</filename></title> - <para>GDM uses two configuration files: <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename>. The <filename><share>/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename><etc>/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename><etc>/gdm/custom.conf</filename> file override the values in the <filename><share>/gdm/defaults.conf</filename> file. If a configuration option is not defined in either file, GDM will default to the value described in the comments in the <filename><share>/gdm/defaults.conf</filename> file.</para> - - <para>Running the <command>gdmsetup</command> command will cause the <filename><etc>/gdm/custom.conf</filename> to be modified with the user's configuration choices.</para> - - <para>Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</filename> existed. If upgrading to the new version of GDM, install will check to see if your <filename><etc>/gdm/gdm.conf</filename> file is different than your <filename><etc>/gdm/factory-gdm.conf</filename> file. If so, your <filename><etc>/gdm/gdm.conf</filename> file will be automatically copied to <filename><etc>/gdm/custom.conf</filename> to preserve any configuration changes.</para> + <para> + GDM uses two configuration files: + <filename><share>/gdm/defaults.conf</filename> + and <filename><etc>/gdm/custom.conf</filename>. The + <filename><share>/gdm/defaults.conf</filename> file contains the + default configuration choices for GDM, and should not be modified by + the user. The <filename><etc>/gdm/custom.conf</filename> + file is where users may specify their custom configuration choices. + Configuration options specified in the + <filename><etc>/gdm/custom.conf</filename> file override the + values in the <filename><share>/gdm/defaults.conf</filename> + file. If a configuration option is not defined in either file, GDM + will default to the value described in the comments in the + <filename><share>/gdm/defaults.conf</filename> file. + </para> + + <para> + Running the <command>gdmsetup</command> command will cause the + <filename><etc>/gdm/custom.conf</filename> to be modified + with the user's configuration choices. + </para> + + <para> + Previous to GDM 2.13.0.4 only the + <filename><etc>/gdm/gdm.conf</filename> existed. If upgrading + to the new version of GDM, install will check to see if your + <filename><etc>/gdm/gdm.conf</filename> file is different than + your <filename><etc>/gdm/factory-gdm.conf</filename> file. + If so, your <filename><etc>/gdm/gdm.conf</filename> file will be + automatically copied to + <filename><etc>/gdm/custom.conf</filename> to preserve any + configuration changes. + </para> - <para>The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may instead be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used.</para> + <para> + The location of the configuration files may be controlled via the + <command>--with-defaults-conf</command> and + <command>--with-custom-conf</command> configuration options. The + GDM daemon --config option may instead be used to specify the + configuration file location. The GDM daemon must be restarted to + change the configuration file being used. + </para> <para>Обидва конфігураційні файли поділяється на розділи, кожен з яких містить змінні, які визначають поведінку окремих частин пакету GDM. Додаткову інформацію про конфігураційні параметри можна отримати з коментарів у файлі <filename><share>/gdm/defaults.conf</filename>.</para> @@ -530,7 +924,15 @@ PostSession/ <term>DefaultPath</term> <listitem> <synopsis>DefaultPath=типовийшлях (значення визначається при configure)</synopsis> - <para>Specifies the path which will be set in the user's session. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains "ROOT=<pathname>". If the <filename>/etc/default/login</filename> file exists, but contains no value for ROOT, the value as defined in the GDM configuration will be be used.</para> + <para> + Specifies the path which will be set in the user's session. + This value will be overridden with the value from + <filename>/etc/default/login</filename> if it contains + "ROOT=<pathname>". If the + <filename>/etc/default/login</filename> file exists, but + contains no value for ROOT, the value as defined in the GDM + configuration will be be used. + </para> </listitem> </varlistentry> @@ -668,7 +1070,18 @@ PostSession/ <term>PreFetchProgram</term> <listitem> <synopsis>PreFetchProgram=command</synopsis> - <para>Program to be run by the GDM greeter/login program when the initial screen is displayed. The purpose is to provide a hook where files which will be used after login can be preloaded to speed performance for the user. The program will be called 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.</para> + <para> + Program to be run by the GDM greeter/login program when the + initial screen is displayed. The purpose is to provide a hook + where files which will be used after login can be preloaded to + speed performance for the user. The program will be called + 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. + </para> </listitem> </varlistentry> @@ -716,7 +1129,16 @@ PostSession/ <term>RootPath</term> <listitem> <synopsis>RootPath=типовийшлях (значення визначається при configure)</synopsis> - <para>Specifies the path which will be set in the root's session and the {Init,PostLogin,PreSession,PostSession} scripts executed by GDM. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains "SUROOT=<pathname>". If the <filename>/etc/default/login</filename> file exists, but contains no value for SUROOT, the value as defined in the GDM configuration will be used.</para> + <para> + Specifies the path which will be set in the root's + session and the {Init,PostLogin,PreSession,PostSession} scripts + executed by GDM. This value will be overridden with the value + from <filename>/etc/default/login</filename> if it + contains "SUROOT=<pathname>". If the + <filename>/etc/default/login</filename> file exists, but + contains no value for SUROOT, the value as defined in the GDM + configuration will be used. + </para> </listitem> </varlistentry> @@ -868,7 +1290,13 @@ PostSession/ <synopsis>AllowRemoteRoot=false</synopsis> <para>Чи дозволяти користувачу root (адміністратору) входити віддалено через GDM. Якщо треба вимкнути такий тип входу, встановіть значення false. Віддаленим входом є будь-який вхід через XDMCP.</para> <para>На системах, що підтримуються PAM, цей параметр не такий корисний, тому що те саме можна зробити за допомогою PAM, та навіть більше.</para> - <para>This value will be overridden and set to false if the <filename>/etc/default/login</filename> file exists and contains "CONSOLE=/dev/login", and set to true if the <filename>/etc/default/login</filename> file exists and contains any other value or no value for CONSOLE.</para> + <para> + This value will be overridden and set to false if the + <filename>/etc/default/login</filename> file exists and + contains "CONSOLE=/dev/login", and set to true if the + <filename>/etc/default/login</filename> file exists and + contains any other value or no value for CONSOLE. + </para> </listitem> </varlistentry> @@ -909,7 +1337,18 @@ PostSession/ <term>PasswordRequired</term> <listitem> <synopsis>PasswordRequired=false</synopsis> - <para>If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be passed as a flag to pam_authenticate and pam_acct_mgmt, disallowing NULL password. This setting will only take effect if PAM is being used by GDM. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains "PASSREQ=[YES|NO]". If the <filename>/etc/default/login</filename> file exists, but contains no value for PASSREQ, the value as defined in the GDM configuration will be used.</para> + <para> + If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be + passed as a flag to pam_authenticate and pam_acct_mgmt, + disallowing NULL password. This setting will only take + effect if PAM is being used by GDM. This value will be + overridden with the value from + <filename>/etc/default/login</filename> if it contains + "PASSREQ=[YES|NO]". If the + <filename>/etc/default/login</filename> file exists, but + contains no value for PASSREQ, the value as defined in the GDM + configuration will be used. + </para> </listitem> </varlistentry> @@ -1380,7 +1819,13 @@ gdm:.my.domain <term>ChooserButtonLogo</term> <listitem> <synopsis>ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png</synopsis> - <para>Image file to display in the file chooser button in <command>gdmsetup</command>. This key is modified by <command>gdmsetup</command> and should not be manually modified by the user. This only affects the Login Window Preferences (<command>gdmsetup</command>).</para> + <para> + Image file to display in the file chooser button in + <command>gdmsetup</command>. This key is modified by + <command>gdmsetup</command> and should not be manually + modified by the user. This only affects the Login Window + Preferences (<command>gdmsetup</command>). + </para> </listitem> </varlistentry> @@ -1693,7 +2138,12 @@ gdm:.my.domain <term>Enable</term> <listitem> <synopsis>Enable=false</synopsis> - <para>Setting to true sends debug ouput to the syslog. This can be useful for tracking down problems with GDM. This output tends to be verbose so should not be turned on for general use.</para> + <para> + Setting to true sends debug ouput to the syslog. This can be + useful for tracking down problems with GDM. This output + tends to be verbose so should not be turned on for general + use. + </para> </listitem> </varlistentry> @@ -1701,7 +2151,13 @@ gdm:.my.domain <term>Жести</term> <listitem> <synopsis>Gestures=false</synopsis> - <para>Setting to true sends debug ouput concerning the accessibility gesture listeners to the syslog. This can be useful for tracking down problems with them not working properly. This output tends to be verbose so should not be turned on for general use.</para> + <para> + Setting to true sends debug ouput concerning the accessibility + gesture listeners to the syslog. This can be useful for + tracking down problems with them not working properly. This + output tends to be verbose so should not be turned on for + general use. + </para> </listitem> </varlistentry> </variablelist> @@ -1712,7 +2168,22 @@ gdm:.my.domain <para>Щоб встановити X-сервери, слід вказати GDM інформацію про встановлені X-сервери. Можна створити довільну кількість різних визначень, кожна повинна мати унікальну назву. Назва <filename>Standard</filename> є обов'язковою. Якщо ви не вказали цей сервер, GDM беруться типові значення сервера 'Standard' та шлях вказаний у <filename>daemon/StandardXServer</filename>. Якщо не визначені інші сервери, використовується <filename>Standard</filename>.</para> - <para>Servers are defined by sections named <filename>server-</filename> followed by the identifier of this server. This should be a simple ASCII string with no spaces. The GUI configuration program allows users to edit the servers defined in the GDM configuration files but currently does not allow adding or deleting entries. Like normal configuration options, <filename>server-</filename> sections in the <filename><etc>/gdm/custom.conf</filename> file override values in the <filename><share>/gdm/defaults.conf</filename> file. In other words, if a <filename>server-Standard</filename> section is defined in <filename><etc>/gdm/custom.conf</filename>, then that will be used and the section in the <filename><share>/gdm/defaults.conf</filename> file will be ignored.</para> + <para> + Servers are defined by sections named <filename>server-</filename> + followed by the identifier of this server. This should be a simple + ASCII string with no spaces. The GUI configuration program allows + users to edit the servers defined in the GDM configuration files + but currently does not allow adding or deleting entries. Like + normal configuration options, <filename>server-</filename> + sections in the <filename><etc>/gdm/custom.conf</filename> + file override values in the + <filename><share>/gdm/defaults.conf</filename> file. In other + words, if a <filename>server-Standard</filename> section is defined + in <filename><etc>/gdm/custom.conf</filename>, then that + will be used and the section in the + <filename><share>/gdm/defaults.conf</filename> file will be + ignored. + </para> <variablelist> <title>[server-Standard]</title> @@ -1764,7 +2235,15 @@ gdm:.my.domain <para>Статичні X-сервери - це сервери, які завжди керуються GDM. Наприклад, якщо сервер будь-коли завершується, він перезапускається. Можна мати будь-яку кількість статичних серверів, хоча зазвичай кожен з них підключений до реального дисплею . Наприклад, якщо в комп'ютері є два дисплеї (скажімо дисплей ":0" та дисплей ":1"), тоді у цьому розділі можна вказати, що для кожного екрану має використовуватись окремий екран входу. Кожен ключ у розділі <filename>[servers]</filename> відповідає номеру дисплея, на якому запускається сервер. Наприклад, зазвичай є лише один ключ, це <filename>0</filename>, який відповідає дисплею <filename>:0</filename>.</para> - <para>The GUI configuration program allows users to edit the static display configuration defined in the GDM configuration files and allows the user to add or delete entries. Like normal configuration options, the <filename>[servers]</filename> section in the <filename><etc>/gdm/custom.conf</filename> file overrides values in the <filename><share>/gdm/defaults.conf</filename> file.</para> + <para> + The GUI configuration program allows users to edit the static + display configuration defined in the GDM configuration files + and allows the user to add or delete entries. Like normal + configuration options, the <filename>[servers]</filename> + section in the <filename><etc>/gdm/custom.conf</filename> + file overrides values in the + <filename><share>/gdm/defaults.conf</filename> file. + </para> <variablelist> <title>[servers]</title> @@ -1773,15 +2252,48 @@ gdm:.my.domain <term><номер дисплею></term> <listitem> <synopsis>0=Standard</synopsis> - <para>Control section for local displays. Each line indicates the local display number and the command that needs to be run to start the X server(s).</para> - - <para>The command can either be a path to an X executable, or a name of one of the server definitions. This can be followed by some arguments that should be passed to the X server when executed. The gdm daemon doesn't enforce the numbers to be in order or for them to be "packed". They keyword "inactive" can be used instead of a command to specify that the display should be not managed. This can be used in the <filename><etc>/gdm/custom.conf</filename> to turn off a display that is defined in the <filename><share>/gdm/defaults.conf</filename> file.</para> + <para> + Control section for local displays. Each line indicates + the local display number and the command that needs to + be run to start the X server(s). + </para> + + <para> + The command can either be a path to an X executable, or a name + of one of the server definitions. This can be followed by some + arguments that should be passed to the X server when executed. + The gdm daemon doesn't enforce the numbers to be in order or + for them to be "packed". They keyword + "inactive" can be used instead of a command to + specify that the display should be not managed. This can be + used in the + <filename><etc>/gdm/custom.conf</filename> to turn + off a display that is defined in the + <filename><share>/gdm/defaults.conf</filename> file. + </para> - <para>GDM will splice "<filename>-auth <ServAuthDir>/:n.Xauth :n</filename>", where n is the display number. Inside the command line before all other arguments before running the X server.</para> - - <para>On some systems it is necessary for GDM to know on which virtual consoles to run the X server. In this case, (if running XFree86) add "vt7" to the command line, for example, to run on virtual console 7. However on Linux and FreeBSD this is normally done automatically if the <filename>VTAllocation</filename> key is set.</para> - - <para>Normally you do not need to add a <filename>-nolisten tcp</filename> flag as this is added automatically for local X servers when the <filename>DisallowTCP</filename> option is set.</para> + <para> + GDM will splice "<filename>-auth + <ServAuthDir>/:n.Xauth :n</filename>", where n is + the display number. Inside the command line before all + other arguments before running the X server. + </para> + + <para> + On some systems it is necessary for GDM to know on which + virtual consoles to run the X server. In this case, + (if running XFree86) add "vt7" to the command line, + for example, to run on virtual console 7. However on Linux and + FreeBSD this is normally done automatically if the + <filename>VTAllocation</filename> key is set. + </para> + + <para> + Normally you do not need to add a + <filename>-nolisten tcp</filename> flag as this is added + automatically for local X servers when the + <filename>DisallowTCP</filename> option is set. + </para> </listitem> </varlistentry> @@ -1789,7 +2301,15 @@ gdm:.my.domain <term>priority</term> <listitem> <synopsis>priority=0</synopsis> - <para>Indicates that the X server should be started at a different process priority. Values can be any integer value accepted by the setpriority C library function (normally between -20 and 20) with 0 being the default. For highly interactive applications, -5 yields good responsiveness. The default value is 0 and the setpriority function is not called if the value is 0.</para> + <para> + Indicates that the X server should be started at a + different process priority. Values can be any integer + value accepted by the setpriority C library function + (normally between -20 and 20) with 0 being the default. + For highly interactive applications, -5 yields good + responsiveness. The default value is 0 and the + setpriority function is not called if the value is 0. + </para> </listitem> </varlistentry> </variablelist> @@ -1799,11 +2319,38 @@ gdm:.my.domain <sect2 id="userconfig"> <title>Параметри специфічні для користувача</title> - <para>There are some per user configuration settings that control how GDM behaves. GDM is picky about the file ownership and permissions of the user files it will access, and will ignore files if they are not owned by the user or files that have group/world write permission. It will also ignore the user if the user's $HOME directory is not owned by the user or if the user's $HOME directory has group/world write permission. files must also be smaller than the <filename>UserMaxFile</filename> value as defined in the GDM configuration. If it seems that GDM is not properly accessing user configuration settings, the problem is most likely caused by one of these checks failing.</para> - - <para>First there is the <filename>~/.dmrc</filename> file. In theory this file should be shared between GDM and KDM, so users only have to configure things once. This is a standard <filename>.ini</filename> style configuration file. It has one section called <filename>[Desktop]</filename> which has two keys: <filename>Session</filename> and <filename>Language</filename>.</para> - - <para>The <filename>Session</filename> key specifies the basename of the session <filename>.desktop</filename> file that the user wishes to normally use (without the <filename>.desktop</filename> extension, in other words). The <filename>Language</filename> key specifies the language that the user wishes to use by default. If either of these keys is missing, the system default is used. The file would normally look as follows:</para> + <para> + There are some per user configuration settings that control how GDM + behaves. GDM is picky about the file ownership and permissions of + the user files it will access, and will ignore files if they are not + owned by the user or files that have group/world write permission. + It will also ignore the user if the user's $HOME directory is not + owned by the user or if the user's $HOME directory has group/world + write permission. files must also be smaller than the + <filename>UserMaxFile</filename> value as defined in the GDM + configuration. If it seems that GDM is not properly accessing + user configuration settings, the problem is most likely + caused by one of these checks failing. + </para> + + <para> + First there is the <filename>~/.dmrc</filename> file. In + theory this file should be shared between GDM and KDM, so users only + have to configure things once. This is a standard + <filename>.ini</filename> style configuration file. It has one section + called <filename>[Desktop]</filename> which has two keys: + <filename>Session</filename> and <filename>Language</filename>. + </para> + + <para> + The <filename>Session</filename> key specifies the basename of the + session <filename>.desktop</filename> file that the user wishes to + normally use (without the <filename>.desktop</filename> extension, in + other words). The <filename>Language</filename> key specifies the + language that the user wishes to use by default. If either of these + keys is missing, the system default is used. The file would normally + look as follows: + </para> <screen> [Desktop] @@ -1811,11 +2358,34 @@ Session=gnome Language=cs_CZ.UTF-8 </screen> - <para>Normally GDM will write this file when the user logs in for the first time, and rewrite it if the user chooses to change their default values on a subsequent login.</para> - - <para>If the GDM Face Browser is turned, then the file <filename>$HOME/.face</filename> is accessed. This file should be a standard image that GTK+ can read, such as PNG or JPEG. It also must be smaller than the <filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> values defined in the GDM configuration or it will be ignored. Users can run the <command>gdmphotosetup</command> program to specify a face image and it will copy the file to the <filename>$HOME/.face</filename> location and scale it so its longest dimension is not larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> values. <command>gdmphotosetup</command> takes care to not change the aspect ratio of the image.</para> - - <para>Face images can also be placed in the global face directory, which is specified by the <filename>GlobalFaceDir</filename> configuration option ( normally <filename><share>/pixmaps/faces/</filename>) and the filename should be the name of the user, optionally with a <filename>.png</filename>, <filename>.jpg</filename>, etc. appended.</para> + <para> + Normally GDM will write this file when the user logs in for the first + time, and rewrite it if the user chooses to change their default values + on a subsequent login. + </para> + + <para> + If the GDM Face Browser is turned, then the file + <filename>$HOME/.face</filename> is accessed. This file should be a + standard image that GTK+ can read, such as PNG or JPEG. It also must + be smaller than the <filename>MaxIconWidth</filename> and + <filename>MaxIconHeight</filename> values defined in the GDM + configuration or it will be ignored. Users can run the + <command>gdmphotosetup</command> program to specify a face image + and it will copy the file to the <filename>$HOME/.face</filename> + location and scale it so its longest dimension is not larger than the + <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> + values. <command>gdmphotosetup</command> takes care to not change + the aspect ratio of the image. + </para> + + <para> + Face images can also be placed in the global face directory, which is + specified by the <filename>GlobalFaceDir</filename> configuration + option ( normally <filename><share>/pixmaps/faces/</filename>) + and the filename should be the name of the user, optionally with a + <filename>.png</filename>, <filename>.jpg</filename>, etc. appended. + </para> </sect2> </sect1> @@ -1827,9 +2397,32 @@ Language=cs_CZ.UTF-8 <sect2 id="commands"> <title>Команди</title> - <para>To stop GDM, you can either send the TERM signal to the main daemon or run the <command>gdm-stop</command> command which is in the <filename><sbin>/</filename> directory. To restart GDM, you can either send the HUP signal to the main daemon or run the <command>gdm-restart</command> command which is also in the <filename><sbin>/</filename> directory. To restart GDM but only after all the users have logged out, you can either send the USR1 signal to the main daemon or run the <command>gdm-safe-restart</command> command which is in the <filename><sbin>/</filename> directory as well.</para> - - <para>The <command>gdmflexiserver</command> command can be used to start new flexible (on demand) displays if your system supports virtual terminals. This command will normally lock the current session with a screensaver so that the user can safely walk away from the computer and let someone else log in. If more that two flexible displays have started <command>gdmflexiserver</command> will display a pop-up dialog allowing the user to select which session to continue. The user will normally have to enter a password to return to the session. On session exit the system will return to the previous virtual terminal. Run <command>gdmflexiserver --help</command> to get a listing of possible options.</para> + <para> + To stop GDM, you can either send the TERM signal to the main daemon or + run the <command>gdm-stop</command> command which is in the + <filename><sbin>/</filename> directory. To restart GDM, you can + either send the HUP signal to the main daemon or run the + <command>gdm-restart</command> command which is also in the + <filename><sbin>/</filename> directory. To restart GDM but only + after all the users have logged out, you can either send the USR1 + signal to the main daemon or run the + <command>gdm-safe-restart</command> command which is in the + <filename><sbin>/</filename> directory as well. + </para> + + <para> + The <command>gdmflexiserver</command> command can be used to start + new flexible (on demand) displays if your system supports virtual + terminals. This command will normally lock the current session with a + screensaver so that the user can safely walk away from the computer and + let someone else log in. If more that two flexible displays have + started <command>gdmflexiserver</command> will display a pop-up dialog + allowing the user to select which session to continue. The user will + normally have to enter a password to return to the session. On session + exit the system will return to the previous virtual terminal. Run + <command>gdmflexiserver --help</command> to get a listing of possible + options. + </para> </sect2> <sect2 id="fifoprot"> @@ -1843,7 +2436,15 @@ Language=cs_CZ.UTF-8 <sect2 id="socketprot"> <title>Протокол роботи з сокетом</title> - <para>GDM provides a unix domain socket for communication at <filename>/tmp/.gdm_socket</filename>. Using this you can check if GDM is running, the version of the daemon, the current displays that are running and who is logged in on them, and if GDM supports it on your operating system, also the virtual terminals of all the console logins. The <command>gdmflexiserver</command> command uses this protocol, for example, to launch flexible (on-demand) displays.</para> + <para> + GDM provides a unix domain socket for communication at + <filename>/tmp/.gdm_socket</filename>. Using this you can check if + GDM is running, the version of the daemon, the current displays that + are running and who is logged in on them, and if GDM supports it on + your operating system, also the virtual terminals of all the console + logins. The <command>gdmflexiserver</command> command uses this + protocol, for example, to launch flexible (on-demand) displays. + </para> <para>gdmflexiserver приймає наступні команди у командному рядку --command:</para> @@ -2438,12 +3039,28 @@ Answers: <sect2 id="bindir_binaries"> <title>Команди користувача GDM</title> - <para>The GDM package provides the following different commands in <filename>bindir</filename> intended to be used by the end-user:</para> + <para> + The GDM package provides the following different commands in + <filename>bindir</filename> intended to be used by the end-user: + </para> <sect3 id="gdmxnestchoosercommandline"> - <title><command>gdmXnestchooser</command> and <command>gdmXnest</command> Command Line Options</title> + <title><command>gdmXnestchooser</command> and + <command>gdmXnest</command> Command Line Options</title> - <para>The <command>gdmXnestchooser</command> command automatically gets the correct display number, sets up access, and runs <command>Xnest</command> with -indirect localhost. This way you get an XDMCP chooser provided by your computer. You can also supply as an argument the hostname whose chooser should be displayed, so <command>gdmXnestchooser somehost</command> will run the XDMCP chooser from host <command>somehost</command> inside an Xnest session. You can make this command do a direct query instead by passing the <command>-d</command> option as well. In addition to the following options, this command also supports standard GNOME options.</para> + <para> + The <command>gdmXnestchooser</command> command automatically gets + the correct display number, sets up access, and runs + <command>Xnest</command> with -indirect localhost. This way you + get an XDMCP chooser provided by your computer. You can also supply + as an argument the hostname whose chooser should be displayed, so + <command>gdmXnestchooser somehost</command> will run the XDMCP + chooser from host <command>somehost</command> inside an Xnest + session. You can make this command do a direct query instead by + passing the <command>-d</command> option as well. In addition to + the following options, this command also supports standard GNOME + options. + </para> <variablelist> <title><command>gdmXnestchooser</command> Command Line Options</title> @@ -2502,15 +3119,46 @@ Answers: <sect3 id="gdmflexichoosercommandline"> <title><command>gdmflexichooser</command> Command Line Options</title> - <para>The <command>gdmflexiserver</command> command provides three features. It can be used to run flexible (on demand) X displays, to run a flexible display via Xnest, and to send commands to the GDM daemon process.</para> + <para> + The <command>gdmflexiserver</command> command provides three + features. It can be used to run flexible (on demand) X displays, + to run a flexible display via Xnest, and to send commands to the + GDM daemon process. + </para> - <para>Starting a flexible X display will normally lock the current session with a screensaver and will redisplay the GDM login screen so a second user can log in. This feature is only available on systems that support virtual terminals and have them enabled. This feature is useful if you are logged in as user A, and user B wants to log in quickly but user A does not wish to log out. The X server takes care of the virtual terminal switching so it works transparently. If there is more than one running display defined with flexible=true, then the user is shown a dialog that displays the currently running sessions. The user can then pick which session to continue and will normally have to enter the password to unlock the screen.</para> + <para> + Starting a flexible X display will normally lock the current session + with a screensaver and will redisplay the GDM login screen so a second + user can log in. This feature is only available on systems that + support virtual terminals and have them enabled. This feature is + useful if you are logged in as user A, and user B wants to log in + quickly but user A does not wish to log out. The X server takes + care of the virtual terminal switching so it works transparently. + If there is more than one running display defined with flexible=true, + then the user is shown a dialog that displays the currently running + sessions. The user can then pick which session to continue and will + normally have to enter the password to unlock the screen. + </para> - <para>Flexible displays started via Xnest works on systems that do not support virtual terminals. This option starts a flexible display in a window in the current session. This does not lock the current session, so is not as secure as a flexible server started via virtual terminals.</para> + <para> + Flexible displays started via Xnest works on systems that do not + support virtual terminals. This option starts a flexible display + in a window in the current session. This does not lock the current + session, so is not as secure as a flexible server started via + virtual terminals. + </para> - <para>The <command>gdmflexiserver --command</command> option provides a way to send commands to the GDM daemon and can be used to debug problems or to change the GDM configuration.</para> + <para> + The <command>gdmflexiserver --command</command> option provides a way + to send commands to the GDM daemon and can be used to debug problems + or to change the GDM configuration. + </para> - <para>In addition to the following options, <command>gdmflexiserver</command> also supports standard GNOME options.</para> + <para> + In addition to the following options, + <command>gdmflexiserver</command> also supports standard GNOME + options. + </para> <variablelist> <title><command>gdmflexichooser</command> Command Line Options</title> @@ -2525,7 +3173,9 @@ Answers: <varlistentry> <term>-n, --xnest</term> <listitem> - <para>Start a flexible X display in Xnest mode</para> + <para> + Start a flexible X display in Xnest mode + </para> </listitem> </varlistentry> @@ -2539,7 +3189,10 @@ Answers: <varlistentry> <term>-d, --debug</term> <listitem> - <para>Turns on debugging output which gets sent to syslog. Same as turning on debug in the configuration file.</para> + <para> + Turns on debugging output which gets sent to syslog. Same as + turning on debug in the configuration file. + </para> </listitem> </varlistentry> @@ -2562,9 +3215,28 @@ Answers: <sect3 id="gdmdynamiccommandline"> <title><command>gdmdynamic</command> Command Line Options</title> - <para>The <command>gdmdynamic</command> command which creates, runs, and removes displays (X servers) on demand.</para> + <para> + The <command>gdmdynamic</command> command which creates, runs, and + removes displays (X servers) on demand. + </para> - <para>Some environments need the ability to tell GDM to create and manage new displays on the fly, where it is not possible to list the possible displays in GDM configuration files. The <command>gdmdynamic</command> command can be used to create a new display on a particular display number, run all newly created displays, or remove a display. The <command>gdmdynamic</command> command can also be used to list all attached displays, or only attached displays that match a pattern. This program is designed to manage multiple simultaneous requests and works to avoid flooding the daemon with requests. If the socket connection is busy, it will sleep and retry a certain number of times that can be tuned with the <command>-t</command> and <command>-s</command> arguments. <command>gdmdynamic</command> returns 1 on normal failure, and returns 2 if it is unable to connect to the daemon. Callers can choose to call again if a return code of 2 is received.</para> + <para> + Some environments need the ability to tell GDM to create and manage new + displays on the fly, where it is not possible to list the possible + displays in GDM configuration files. The <command>gdmdynamic</command> + command can be used to create a new display on a particular display + number, run all newly created displays, or remove a display. The + <command>gdmdynamic</command> command can also be used to list all + attached displays, or only attached displays that match a pattern. + This program is designed to manage multiple simultaneous requests and + works to avoid flooding the daemon with requests. If the socket + connection is busy, it will sleep and retry a certain number of times + that can be tuned with the <command>-t</command> and + <command>-s</command> arguments. <command>gdmdynamic</command> + returns 1 on normal failure, and returns 2 if it is unable to + connect to the daemon. Callers can choose to call again if a + return code of 2 is received. + </para> <variablelist> <title><command>gdmdynamic</command> Command Line Options</title> @@ -2645,34 +3317,69 @@ Answers: <sect3 id="gdmphotosetupcommandline"> <title><command>gdmphotosetup</command> Command Line Options</title> - <para>Allows the user to select an image that will be used as the user's photo by GDM's face browser, if enabled by GDM. The selected file is stored as <filename>~/.face</filename>. This command accepts standard GNOME options.</para> + <para> + Allows the user to select an image that will be used as the user's + photo by GDM's face browser, if enabled by GDM. The selected file + is stored as <filename>~/.face</filename>. This command accepts + standard GNOME options. + </para> </sect3> <sect3 id="gdmthemetestercommandline"> <title><command>gdmthemetester</command> Command Line Options</title> - <para><command>gdmthemetester</command> takes two parameters. The first parameter specifies the environment and the second parameter specifies the path name or the name of a theme to view. This is a tool for viewing a theme outside of GDM. It is useful for testing or viewing themes. <command>gdmthemetester</command> requires that the system support <command>gdmXnest</command>. Note that themes can display differently depending on the theme's "Show mode". <command>gdmthemetester</command> allows viewing the themes in different modes via the environment option. Valid environment values and their meanings follow: <screen> + <para> + <command>gdmthemetester</command> takes two parameters. The first + parameter specifies the environment and the second parameter + specifies the path name or the name of a theme to view. + + This is a tool for viewing a theme outside of GDM. It is useful for + testing or viewing themes. <command>gdmthemetester</command> requires + that the system support <command>gdmXnest</command>. + + Note that themes can display differently depending on the theme's + "Show mode". <command>gdmthemetester</command> allows + viewing the themes in different modes via the environment option. + Valid environment values and their meanings follow: + +<screen> console - In console mode. console-timed - In console non-flexi mode. flexi - In flexi mode. xdmcp - In remote (XDMCP) mode. remote-flexi - In remote (XDMCP) & flexi mode. -</screen></para> +</screen> + </para> </sect3> </sect2> <sect2 id="sbindir_binaries"> <title>GDM Root User Commands</title> - <para>The GDM package provides the following different commands in <filename>sbindir</filename> intended to be used by the root user:</para> + <para> + The GDM package provides the following different commands in + <filename>sbindir</filename> intended to be used by the root user: + </para> <sect3 id="gdmcommandline"> - <title><command>gdm</command> and <command>gdm-binary</command> Command Line Options</title> + <title><command>gdm</command> and <command>gdm-binary</command> + Command Line Options</title> - <para>The <command>gdm</command> command is really just a script which runs the <command>gdm-binary</command>, passing along any options. Before launching <command>gdm-binary</command>, the gdm wrapper script will source the <filename><etc>/profile</filename> file to set the standard system environment variables. In order to better support internationalization, it will also set the LC_MESSAGES environment variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you really need to set some additional environment before launching GDM, you can do so in this script.</para> + <para> + The <command>gdm</command> command is really just a script which + runs the <command>gdm-binary</command>, passing along any options. + Before launching <command>gdm-binary</command>, the gdm wrapper script + will source the <filename><etc>/profile</filename> file to set + the standard system environment variables. In order to better support + internationalization, it will also set the LC_MESSAGES environment + variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you + really need to set some additional environment before launching GDM, + you can do so in this script. + </para> <variablelist> - <title><command>gdm</command> and <command>gdm-binary</command> Command Line Options</title> + <title><command>gdm</command> and <command>gdm-binary</command> + Command Line Options</title> <varlistentry> <term>--help</term> @@ -2728,43 +3435,80 @@ remote-flexi - In remote (XDMCP) & flexi mode. <sect3 id="gdmsetupcommandline"> <title><command>gdmsetup</command> Command Line Options</title> - <para><command>gdmsetup</command> runs a graphical application for modifying the GDM configuration file. Normally on systems that support the PAM userhelper, this is setup such that when you run <command>gdmsetup</command> as an ordinary user, it will first ask you for your root password before starting. Otherwise, this application may only be run as root. This application supports standard GNOME options.</para> + <para> + <command>gdmsetup</command> runs a graphical application for modifying + the GDM configuration file. Normally on systems that support + the PAM userhelper, this is setup such that when you run + <command>gdmsetup</command> as an ordinary user, it will first + ask you for your root password before starting. Otherwise, this + application may only be run as root. This application supports + standard GNOME options. + </para> </sect3> <sect3 id="gdmrestartcommandline"> <title><command>gdm-restart</command> Command Line Options</title> - <para><command>gdm-restart</command> stops and restarts GDM by sending the GDM daemon a HUP signal. This command will immediately terminate all sessions and log out users currently logged in with GDM.</para> + <para> + <command>gdm-restart</command> stops and restarts GDM by sending + the GDM daemon a HUP signal. This command will immediately terminate + all sessions and log out users currently logged in with GDM. + </para> </sect3> <sect3 id="gdmsaferestartcommandline"> <title><command>gdm-safe-restart</command> Command Line Options</title> - <para><command>gdm-safe-restart</command> stops and restarts GDM by sending the GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out.</para> + <para> + <command>gdm-safe-restart</command> stops and restarts GDM by + sending the GDM daemon a USR1 signal. GDM will be restarted as soon + as all users log out. + </para> </sect3> <sect3 id="gdmstopcommandline"> <title><command>gdm-stop</command> Command Line Options</title> - <para><command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM signal.</para> + <para> + <command>gdm-stop</command> stops GDM by sending the GDM daemon + a TERM signal. + </para> </sect3> </sect2> <sect2 id="libexecdir_binaries"> <title>Внутрішні команди GDM</title> - <para>The GDM package provides the following different commands in <filename>libexecdir</filename> intended to be used by the gdm daemon process.</para> + <para> + The GDM package provides the following different commands in + <filename>libexecdir</filename> intended to be used by the gdm + daemon process. + </para> <sect3 id="gdmgreeterlogincommandline"> - <title><command>gdmchooser</command> and <command>gdmlogin</command> Command Line Options</title> + <title><command>gdmchooser</command> and <command>gdmlogin</command> + Command Line Options</title> - <para>The <command>gdmgreeter</command> and <command>gdmlogin</command> are two different login applications, either can be used by GDM. <command>gdmgreeter</command> is themeable with GDM themes while <command>gdmlogin</command> is themable with GTK+ themes. These applications are normally executed by the GDM daemon. Both commands support standard GNOME options.</para> + <para> + The <command>gdmgreeter</command> and <command>gdmlogin</command> + are two different login applications, either can be used by GDM. + <command>gdmgreeter</command> is themeable with GDM themes while + <command>gdmlogin</command> is themable with GTK+ themes. These + applications are normally executed by the GDM daemon. Both commands + support standard GNOME options. + </para> </sect3> <sect3 id="gdmchoosercommandline"> <title><command>gdmchooser</command> Command Line Options</title> - <para>The <command>gdmchooser</command> is the XDMCP chooser application. The <command>gdmchooser</command> is normally executed by the GDM daemon. It supports the following options for XDM compatibility. This command supports standard GNOME options and is found in support standard GNOME options.</para> + <para> + The <command>gdmchooser</command> is the XDMCP chooser application. + The <command>gdmchooser</command> is normally executed by the GDM + daemon. It supports the following options for XDM compatibility. + This command supports standard GNOME options and is found in + support standard GNOME options. + </para> <variablelist> <title><command>gdmchooser</command> Command Line Options</title> @@ -2825,7 +3569,19 @@ Screenshot=screenshot.png <para>Назва, опис, автор та авторські права можна перекладати як і у інших файлах типу <filename>.desktop</filename>. Усі файли вказані файли мають у каталозі з темами. Файл, на який вказує поле Screenshot повинен бутизнімком екрану теми з розмірами 200x150 (він може бути відсутній, але якщо він є - це краще для користувача). У полі Greeter вказується файл XML, який містить опис теми. Опис буде згаданий далі.</para> - <para>Once you have theme ready and installed you can test it with the installed <command>gdmthemetester</command> script. This script assumes that the X server supports Xnest. This command takes two arguments, first the environment that should be used. This is one of console, console-timed, flexi, remote-flexi, xdmcp. Where console is a standard console login, console-timed is a console login with a timed login going on, flexi is for any local flexible display, remote-flexi is for flexi displays that are not local (such as an Xnest flexiserver run from a remote display) and xdmcp is for remote XDMCP connections. The second argument is the theme name. So for example to test how things look in the XDMCP mode with the circles theme you would run:</para> + <para> + Once you have theme ready and installed you can test it with the + installed <command>gdmthemetester</command> script. This script + assumes that the X server supports Xnest. This command takes two + arguments, first the environment that should be used. This is one of + console, console-timed, flexi, remote-flexi, xdmcp. Where console is a + standard console login, console-timed is a console login with a timed + login going on, flexi is for any local flexible display, remote-flexi + is for flexi displays that are not local (such as an Xnest flexiserver + run from a remote display) and xdmcp is for remote XDMCP connections. + The second argument is the theme name. So for example to test how + things look in the XDMCP mode with the circles theme you would run: + </para> <screen> <command>gdmthemetester xdmcp circles</command> @@ -2833,10 +3589,17 @@ Screenshot=screenshot.png <para>Перевірте тему в усіх варіантах оточення, та перевірте вигляд попередження про натискання caps lock. Також було б добре зробити знімок екрану, просто зробіть знімок екрану вікна Xnest. це можна зробити у GNOME, якщо передати фоку вводу вікну Xnest та натиснути Alt-PrintScreen.</para> - <para>Once you have all this done, then make a tarball that contains the directory name (so that you could just untar it in the <filename><share>/gdm/themes</filename> directory). And this is the tarball you distribute and people can install from the graphical configuration application. You can do this with the commands: <screen> + <para> + Once you have all this done, then make a tarball that contains the + directory name (so that you could just untar it in the + <filename><share>/gdm/themes</filename> directory). And this is + the tarball you distribute and people can install from the graphical + configuration application. You can do this with the commands: +<screen> cd <share>/gdm/themes tar czvf <theme_name>.tar.gz <theme_name>/ -</screen></para> +</screen> + </para> </sect2> <sect2 id="descofthemeformat"> @@ -2845,11 +3608,21 @@ tar czvf <theme_name>.tar.gz <theme_name>/ <sect3 id="boxnodes"> <title>Box Nodes</title> - <para>Box nodes are container nodes for item nodes. Box nodes are specified as follows: <screen> + <para> + Box nodes are container nodes for item nodes. Box nodes are + specified as follows: +<screen> <box orientation="alignment" min-width="num" xpadding="num" ypadding="num" spacing="num" homogeneous="bool"> -</screen> Where "num" means number and bool means either "true" or "false" The alignment value can be either "horizontal" or "vertical". If you leave any property off it will default to zero or "false" in case of "homogeneous" and "vertical" for the orientation.</para> +</screen> + Where "num" means number and bool means either + "true" or "false" The alignment value can be + either "horizontal" or "vertical". If you leave + any property off it will default to zero or "false" in + case of "homogeneous" and "vertical" for the + orientation. + </para> <para>Якщо контейнер є однорідним, тоді дочірні елементи займають однаковий простір.</para> @@ -2859,9 +3632,16 @@ homogeneous="bool"> <sect3 id="fixednodes"> <title>Вузли Fixed</title> - <para>Fixed is a container that has its children scattered about laid out with precise coordinates. The size of this container is the biggest rectangle that contains all the children. Fixed has no extra properties and so you just use: <screen> + <para> + Fixed is a container that has its children scattered about + laid out with precise coordinates. The size of this container + is the biggest rectangle that contains all the children. Fixed + has no extra properties and so you just use: +<screen> <fixed> -</screen> Then you put other items with proper position nodes inside this.</para> +</screen> + Then you put other items with proper position nodes inside this. + </para> <para>Вузол "toplevel" подібний до вузла fixed.</para> </sect3> @@ -2915,9 +3695,16 @@ homogeneous="bool"> </varlistentry> </variablelist> - <para>For example: <screen> + <para> + For example: +<screen> <item type="label"> -</screen> Items can specify ID values which gives them a specific look and feel or formatting. Furthermore you can customize the login process by adding custom widgets with custom id's for some items (currently only the list item)</para> +</screen> + Items can specify ID values which gives them a specific look and feel + or formatting. Furthermore you can customize the login process by + adding custom widgets with custom id's for some items (currently only + the list item) + </para> <para>Елементи вузлів можуть мати такі значення ідентифікаторів:</para> @@ -2950,28 +3737,40 @@ homogeneous="bool"> <varlistentry> <term>clock</term> <listitem> - <para>Label that displays the date and time.</para> + <para> + Label that displays the date and time. + </para> </listitem> </varlistentry> <varlistentry> <term>pam-prompt</term> <listitem> - <para>Label that displays the PAM prompt. This is the prompt that PAM uses to ask for username, password, etc...</para> + <para> + Label that displays the PAM prompt. This is the prompt that PAM + uses to ask for username, password, etc... + </para> </listitem> </varlistentry> <varlistentry> <term>pam-error</term> <listitem> - <para>Label that displayst PAM/GDM error messages. Such as when user can't log in.</para> + <para> + Label that displayst PAM/GDM error messages. Such as when user + can't log in. + </para> </listitem> </varlistentry> <varlistentry> <term>pam-message</term> <listitem> - <para>Label that displays the PAM message. These are messages that PAM/GDM gives about state of the account, help about the prompts and other information.</para> + <para> + Label that displays the PAM message. These are messages that + PAM/GDM gives about state of the account, help about the + prompts and other information. + </para> </listitem> </varlistentry> @@ -2994,9 +3793,13 @@ homogeneous="bool"> </varlistentry> </variablelist> - <para>If an item is of type rect, the item can be a button. Buttons must also include a "button" value as follows: <screen> + <para> + If an item is of type rect, the item can be a button. Buttons + must also include a "button" value as follows: +<screen> <item type="rect" id="disconnect_button" button="true">. -</screen></para> +</screen> + </para> <para>Можливі значення для кнопок:</para> @@ -3060,7 +3863,13 @@ homogeneous="bool"> <varlistentry> <term>system_button</term> <listitem> - <para>Perform halt/restart/suspend/etc. options (if allowed by GDM configuration). Also allows user to run configurator if user enters root password (again if allowed by GDM configuration). This is usually now labeled Actions, and referred to as the Actions menu.</para> + <para> + Perform halt/restart/suspend/etc. options (if allowed by GDM + configuration). Also allows user to run configurator if user + enters root password (again if allowed by GDM configuration). + This is usually now labeled Actions, and referred to as the + Actions menu. + </para> </listitem> </varlistentry> </variablelist> @@ -3069,17 +3878,28 @@ homogeneous="bool"> <sect3 id="positionnodes"> <title>Вузол позиції</title> - <para>Each item can specify its position and size via the "pos" node. For example: <screen> + <para> + Each item can specify its position and size via the "pos" + node. For example: +<screen> <pos x="0" y="4" width="100%" height="100%"/> -</screen></para> +</screen> + </para> <para>Обидві позиції та розмір може бути вказаний у відсотках та елемент буде займати вказаний відсоток розміру поточного контейнера. Елементи, не укладені у контейнер, займаються вказаний відсоток екрану.</para> <para>Для x та y, також можна вказати від'ємне значення розташування, що буде означати відлік від правого чи нижнього боку. Але це стосується лише абсолютних координат. Якщо вказано від'ємне значення відсотків, відлік все одно буде з того самого боку.</para> - <para>The position also specifies the anchor of the item, this can be "n" "ne" "e" "se" "s" "sw" "w" and "nw" or "center" which stand for the different edges/corners or "center" for center. For example: <screen> + <para> + The position also specifies the anchor of the item, this can be + "n" "ne" "e" "se" + "s" "sw" "w" and "nw" or + "center" which stand for the different edges/corners or + "center" for center. For example: +<screen> <pos x="10%" y="50%" anchor="w" width="80%" height="95"/> -</screen></para> +</screen> + </para> <para>Якщо елемент містить контейнер, можна вказати ширину та висоту "box", що означає, що вони вважаються шириною та висотою контейнера, тобто елементи у контейнері плюс відступи.</para> @@ -3087,10 +3907,19 @@ homogeneous="bool"> <para>Можна вказати властивості "expand" значення "true" чи false. Якщо вказано true, тоді дочірній елемент буде розширено наскільки це можливо (тобто він займатиме більше простору, якщо він є).</para> - <para>There are two extra properties you can specify (as of 2.4.4.3) for labels (and labels only). The first is "max-width" which will specify the maximum width of the label in pixels. And the second is "max-screen-percent-width" which specifies the maximum percentage of the screen width that the label can occupy. By default no label will occupy more then 90% of the screen by width. An example may be: <screen> + <para> + There are two extra properties you can specify (as of 2.4.4.3) for + labels (and labels only). The first is "max-width" which + will specify the maximum width of the label in pixels. And the + second is "max-screen-percent-width" which specifies the + maximum percentage of the screen width that the label can occupy. + By default no label will occupy more then 90% of the screen by width. + An example may be: +<screen> <item type="label"> <pos x="10%" max-screen-percent-width="50%"/> -</screen></para> +</screen> + </para> </sect3> <sect3 id="shownodes"> @@ -3105,25 +3934,57 @@ homogeneous="bool"> <para><filename>remote</filename> - віддалений режим.</para> <para><filename>remote-flexi</filename> - віддалений та гнучкий режим.</para> - <para>For example: <screen> + <para> + For example: +<screen> <show modes="flexi,remote"/> -</screen></para> +</screen> + </para> <para>Також ви можете вказати значення "type", щоб позначити, що певні елементи мають відображатись якщо type має значення true. Допустимі значення:</para> - <para><filename>chooser</filename>, if ChooserButton is set to "true" in the GDM configuration.</para> - <para><filename>config</filename>, if ConfigAvailable is set to "true" in the GDM configuration.</para> - <para><filename>halt</filename>, if HaltDaemon is specified in the GDM configuration.</para> - <para><filename>reboot</filename>, if RebootCommand is specified in the GDM configuration.</para> - <para><filename>suspend</filename>, if SuspendCommand is specified in the GDM configuration.</para> - <para><filename>system</filename>, if SystemMenu is specified in the GDM configuration.</para> - <para><filename>timed</filename>, if TimedLoginEnabled is set to "true" in the GDM configuration.</para> + <para> + <filename>chooser</filename>, if ChooserButton is set to + "true" in the GDM configuration. + </para> + <para> + <filename>config</filename>, if ConfigAvailable is set to + "true" in the GDM configuration. + </para> + <para> + <filename>halt</filename>, if HaltDaemon is specified in + the GDM configuration. + </para> + <para> + <filename>reboot</filename>, if RebootCommand is specified in + the GDM configuration. + </para> + <para> + <filename>suspend</filename>, if SuspendCommand is specified in + the GDM configuration. + </para> + <para> + <filename>system</filename>, if SystemMenu is specified in + the GDM configuration. + </para> + <para> + <filename>timed</filename>, if TimedLoginEnabled is set to + "true" in the GDM configuration. + </para> - <para>For example: <screen> + <para> + For example: +<screen> <show modes="console" type="system"/> -</screen></para> +</screen> + </para> - <para>Note that if SystemMenu is off then the halt, restart, suspend, chooser and config choices will not be shown, so this is a global toggle for them all. See some of the standard themes for how the show modes are used.</para> + <para> + Note that if SystemMenu is off then the halt, restart, suspend, + chooser and config choices will not be shown, so this is a global + toggle for them all. See some of the standard themes for how the + show modes are used. + </para> </sect3> <sect3 id="noractprenodes"> @@ -3135,17 +3996,29 @@ homogeneous="bool"> <para><filename>active</filename> - стан, коли елемент має фокус вводу.</para> <para><filename>prelight</filename> - коли миша знаходиться над елементом.</para> - <para>When item is "rect" (alpha can be omitted and defaults to 0.0): <screen> + <para> + When item is "rect" (alpha can be omitted and defaults to + 0.0): +<screen> <normal color="#ffffff" alpha="0.0"> -</screen></para> +</screen> + </para> - <para>When item is "label" <screen> + <para> + When item is "label" +<screen> <normal color="#ffffff" font="Sans 14"/> -</screen></para> +</screen> + </para> - <para>When the item type is "pixmap" or "SVG", then the normal, active, and prelight tags specify the images to use as follows: <screen> + <para> + When the item type is "pixmap" or "SVG", then the + normal, active, and prelight tags specify the images to use as + follows: +<screen> <normal file="picture.png" tint="#dddddd"/> -</screen></para> +</screen> + </para> <para>Зауважте, що відносні назви шляхів мають бути у тому самому каталозі, що й <filename>.xml</filename> файл теми у <filename><share>/gdm/themes/<theme_name></filename>.</para> </sect3> @@ -3165,29 +4038,47 @@ homogeneous="bool"> <sect3 id="textnodes"> <title>Текстовий вузол</title> - <para>Text tags are used by labels. They can be used to display localized text as follows (if the "xml:lang" attribute is omitted, the C locale is assumed): <screen> + <para> + Text tags are used by labels. They can be used to display + localized text as follows (if the "xml:lang" attribute is + omitted, the C locale is assumed): +<screen> <text xml:lang="fr">Option</text> -</screen></para> +</screen> + </para> - <para>You can include pango markup in the text nodes for labels, however you must encode it. So for example to have the label of "foo<sup>bar</sup>", you must type: <screen> + <para> + You can include pango markup in the text nodes for labels, however + you must encode it. So for example to have the label of + "foo<sup>bar</sup>", you must type: +<screen> <text>"foo<sup>bar</sup>"</text> -</screen></para> +</screen> + </para> <para>Текстові вузли можуть містити наступні спеціальні послідовності символів:</para> - <para>%% - A literal % character</para> + <para> + %% - A literal % character + </para> <para>%c - час годинника. Лише позначки з ідентифікатором "clock" будуть оновлюватись кожну секунду. Інші позначки будуть містити статичне значення часу.</para> <para>%d - назва дисплею (змінна оточення DISPLAY)</para> <para>%h - назва вузла (вивід gethostname)</para> <para>%m - назва машини (вивід uname.machine)</para> - <para>%n - Node name (uname.nodename output)</para> + <para> + %n - Node name (uname.nodename output) + </para> <para>%o - назва домену (вивід getdomainname)</para> <para>%r - назва випуску (вивід uname.release)</para> <para>%s - назва системи (вивід uname.sysname)</para> <para>%t - поточне значення затримки для входу із затримкою з конфігураційного файл (0 - якщо вимкнено), за яким йде слово "seconds", якщо значення більше ніж 1 або слово "second" якщо значення дорівнює 1. Ця символьна послідовність призначена для внутрішнього використання всередині для відображення повідомлень типу "позначка часу", що автоматично оновлюються кожної секунди.</para> <para>%u - ім'я користувача для входу із затримкою з конфігураційного файлу (порожнє, якщо вимкнено) Ця символьна послідовність призначена для внутрішнього використання всередині для відображення повідомлень типу "позначка часу", що автоматично оновлюються кожної секунди.</para> <para>\n - переведення каретки</para> - <para>_ - An underscore causes the following character to be underlined. If it precedes a % character sequence, the string that replaces the character sequence is underlined.</para> + <para> + _ - An underscore causes the following character to be underlined. + If it precedes a % character sequence, the string that replaces the + character sequence is underlined. + </para> </sect3> <sect3 id="stocklabels"> @@ -3195,26 +4086,64 @@ homogeneous="bool"> <para>Деякі загальні локалізовані позначки можна вказувати через теги з набору. Якщо вказано тег "stock", тоді тег "text" ігнорується. Слід використовувати позначки з набору позначок, замість призначення перекладеного значення у тему. При цьому прискорюється час завантаження та краще відбувається переклад. Можливі значення:</para> - <para><filename>cancel</filename>, _("_Cancel"</para> - <para><filename>caps-lock-warning</filename>, _("Caps Lock key is on."</para> - <para><filename>chooser</filename>, _("Remote Login via _XDMCP"</para> - <para><filename>config</filename>, _("_Configure"</para> - <para><filename>disconnect</filename>, _("D_isconnect"</para> - <para><filename>halt</filename>, _("Shut _Down"</para> - <para><filename>language</filename>, _("_Language"</para> - <para><filename>ok</filename>, _("_OK"</para> - <para><filename>quit</filename>, _("_Quit"</para> - <para><filename>reboot</filename>, _("_Restart"</para> - <para><filename>session</filename>, _("_Session"</para> - <para><filename>suspend</filename>, _("Sus_pend"</para> - <para><filename>system</filename>, _("_Actions" (Formerly "S_ystem"</para> - <para><filename>timed-label</filename>, _("User %u will login in %t"</para> - <para><filename>username-label</filename>, _("Username:"</para> - <para><filename>welcome-label</filename>, _("Welcome to %n"</para> - - <para>For example: <screen> + <para> + <filename>cancel</filename>, _("_Cancel" + </para> + <para> + <filename>caps-lock-warning</filename>, + _("Caps Lock key is on." + </para> + <para> + <filename>chooser</filename>, _("Remote Login via _XDMCP" + </para> + <para> + <filename>config</filename>, _("_Configure" + </para> + <para> + <filename>disconnect</filename>, _("D_isconnect" + </para> + <para> + <filename>halt</filename>, _("Shut _Down" + </para> + <para> + <filename>language</filename>, _("_Language" + </para> + <para> + <filename>ok</filename>, _("_OK" + </para> + <para> + <filename>quit</filename>, _("_Quit" + </para> + <para> + <filename>reboot</filename>, _("_Restart" + </para> + <para> + <filename>session</filename>, _("_Session" + </para> + <para> + <filename>suspend</filename>, _("Sus_pend" + </para> + <para> + <filename>system</filename>, _("_Actions" + (Formerly "S_ystem" + </para> + <para> + <filename>timed-label</filename>, + _("User %u will login in %t" + </para> + <para> + <filename>username-label</filename>, _("Username:" + </para> + <para> + <filename>welcome-label</filename>, _("Welcome to %n" + </para> + + <para> + For example: +<screen> <stock type="welcome-label"> -</screen></para> +</screen> + </para> </sect3> <sect3 id="customwidgetry"> @@ -3236,56 +4165,186 @@ homogeneous="bool"> </item> </screen> - <para>Then if the user chooses 'Foo' then <filename><var>/gdm/:0.GreeterInfo</filename> will contain: <screen> + <para> + Then if the user chooses 'Foo' then + <filename><var>/gdm/:0.GreeterInfo</filename> will contain: +<screen> custom-config=foo -</screen></para> +</screen> + </para> </sect3> </sect2> </sect1> <sect1 id="accessibility"> <title>Спеціальні можливості</title> - <para>GDM supports "Accessible Login" to allow users to log in to their desktop session even if they cannot easily use the screen, mouse, or keyboard in the usual way. Only the "Standard Greeter" supports accessibility, so use this login GUI for accessibility support. This is done by specifying the "Standard Greeter" in the "Local" tab for the console display and specifying the "Standard Greeter" in the "Remote" tab for remote displays. Or you can modify the <filename>Greeter</filename> configuration option by hand to be <command>gdmlogin</command>.</para> - - <para>The Standard Greeter supports the ability to launch assistive technologies at login time via configurable "gestures" from the standard keyboard, pointing device, or switch device attached to the USB or PS/2 mouse port. Also the user can change the visual appearance of the login UI before logging in, for instance to use a higher-contrast color scheme for better visibility.</para> + <para> + GDM supports "Accessible Login" to allow users to log in to + their desktop session even if they cannot easily use the screen, mouse, + or keyboard in the usual way. Only the "Standard Greeter" + supports accessibility, so use this login GUI for accessibility + support. This is done by specifying the "Standard Greeter" + in the "Local" tab for the console display and specifying + the "Standard Greeter" in the "Remote" tab for + remote displays. Or you can modify the <filename>Greeter</filename> + configuration option by hand to be <command>gdmlogin</command>. + </para> + + <para> + The Standard Greeter supports the ability to launch assistive + technologies at login time via configurable "gestures" from + the standard keyboard, pointing device, or switch device attached to + the USB or PS/2 mouse port. Also the user can change the visual + appearance of the login UI before logging in, for instance to use a + higher-contrast color scheme for better visibility. + </para> <sect2 id="accessibilityconfig"> <title>Налаштовування спеціальних можливостей</title> - <para>In order to enable Accessible Login, the system administrator must make some changes to the default login configuration by manually modifying three human-readable configuration files, stored in the GDM configuration, AccessKeyMouseEvents and AccessDwellMouseEvents.</para> - - <para>In order to allow users to change the color and contrast scheme of the login dialog, make sure the <filename>AllowThemeChange</filename> parameter in the GDM configuration is set to "true".</para> - - <para>To restrict user changes to the visual appearance to a subset of available themes, the <filename>GtkThemesToAllow</filename> parameter in the GDM configuration can be set to a list of acceptable themes separated by commas. For example:</para> + <para> + In order to enable Accessible Login, the system administrator must + make some changes to the default login configuration by manually + modifying three human-readable configuration files, stored in + the GDM configuration, AccessKeyMouseEvents and + AccessDwellMouseEvents. + </para> + + <para> + In order to allow users to change the color and contrast scheme of + the login dialog, make sure the + <filename>AllowThemeChange</filename> parameter in the GDM + configuration is set to "true". + </para> + + <para> + To restrict user changes to the visual appearance to a subset of + available themes, the <filename>GtkThemesToAllow</filename> + parameter in the GDM configuration can be set to a list of + acceptable themes separated by commas. For example: + </para> <screen> GtkThemesToAllow=HighContrast,HighContrastInverse </screen> - <para>To enable the use of assistive technologies such as the Onscreen Keyboard, Screen Reader, or Magnifier, the <filename>AddGtkModules</filename> parameter in the GDM configuration must be uncommented and set to "true". Also the <filename>GtkModulesList</filename> parameter must be uncommented and set as follows:</para> + <para> + To enable the use of assistive technologies such as the Onscreen + Keyboard, Screen Reader, or Magnifier, the + <filename>AddGtkModules</filename> parameter in the GDM + configuration must be uncommented and set to "true". + Also the <filename>GtkModulesList</filename> parameter must be + uncommented and set as follows: + </para> <screen> GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener </screen> - <para>System administrators may wish to load only the minimum subset of these modules which is required to support their user base. Depending on the end-user needs, not all of the above GtkModules may need to be loaded. If your end-users need the integrated Screen Reader and Magnifier, you must include "gail" and "atk-bridge". If your end-users will be using a pointing device without buttons or switches, include "dwellmouselistener". If some of your users will use pointing devices with switches, alternative physical keyboards, or switch/button devices, include "keymouselistener". Including all four is suitable for most system configurations. The Onscreen Keyboard can operate without gail and atk-bridge, but with a reduced feature set; for optimum accessibility we recommend including both gail and atk-bridge.</para> - - <para>Once "keymouselistener" and/or "dwellmouselistener" have been added to the GtkModules loaded by GDM, you can assign end-user actions with the launching of specific assistive technologies. These gesture associations are contained in files AccessKeyMouseEvents and AccessDwellMouseEvents, respectively. Both files are located in the <etc>/gdm/modules directory. The gesture format is described in the two configuration files.</para> - - <para>The AccessKeyMouseEvents file controls the keymouselistener Gesture Listener and is used to define key-press, mouse button, or XInput device sequences that can be used to launch applications needed for accessibility. In order to reduce the likelihood of unintentional launch, these "gestures" may be associated with multiple switch presses and/or minimum durations. Note that the XKB extension is needed for key gestures to work, so you may need to add +xkb to your Xserver command line for gestures to work properly.</para> - - <para>The DwellKeyMouseEvents file controls the dwellmouselistner and supports gestures that involve only motion of a pointing device such as the system mouse of an alternative pointing device such as a head pointer or trackball may also be defined. All gestures are specified by the same syntax; that is, there is no distinction between a "core mouse" gesture and motion from an alternate input device.</para> - - <para>Motion gestures are defined as "crossing events" into and out of the login dialog window. If the "dwellmouselistener" GtkModule is loaded, alternative pointing devices are temporarily "latched" to the core pointer, such that motion from alternative devices results in movement of the onscreen pointer.</para> + <para> + System administrators may wish to load only the minimum subset of + these modules which is required to support their user base. + Depending on the end-user needs, not all of the above GtkModules + may need to be loaded. If your end-users need the integrated + Screen Reader and Magnifier, you must include "gail" and + "atk-bridge". If your end-users will be using a + pointing device without buttons or switches, include + "dwellmouselistener". If some of your users will use + pointing devices with switches, alternative physical keyboards, or + switch/button devices, include "keymouselistener". + Including all four is suitable for most system configurations. + The Onscreen Keyboard can operate without gail and atk-bridge, but + with a reduced feature set; for optimum accessibility we recommend + including both gail and atk-bridge. + </para> + + <para> + Once "keymouselistener" and/or + "dwellmouselistener" have been added to the GtkModules + loaded by GDM, you can assign end-user actions with the launching + of specific assistive technologies. These gesture associations + are contained in files AccessKeyMouseEvents and + AccessDwellMouseEvents, respectively. Both files are located in + the <etc>/gdm/modules directory. The gesture format is + described in the two configuration files. + </para> + + <para> + The AccessKeyMouseEvents file controls the keymouselistener + Gesture Listener and is used to define key-press, mouse button, + or XInput device sequences that can be used to launch applications + needed for accessibility. In order to reduce the likelihood of + unintentional launch, these "gestures" may be associated + with multiple switch presses and/or minimum durations. Note that + the XKB extension is needed for key gestures to work, so you may + need to add +xkb to your Xserver command line for gestures to + work properly. + </para> + + <para> + The DwellKeyMouseEvents file controls the dwellmouselistner and + supports gestures that involve only motion of a pointing device + such as the system mouse of an alternative pointing device such + as a head pointer or trackball may also be defined. All gestures + are specified by the same syntax; that is, there is no distinction + between a "core mouse" gesture and motion from an + alternate input device. + </para> + + <para> + Motion gestures are defined as "crossing events" into + and out of the login dialog window. If the + "dwellmouselistener" GtkModule is loaded, alternative + pointing devices are temporarily "latched" to the core + pointer, such that motion from alternative devices results in + movement of the onscreen pointer. + </para> <para>Для використання служби промови тексту під час входу (наприклад, при використанні програми читання екрану в режимі speech) на деяких операційних системах, GDM user must be made a member of the "audio" group</para> - <para>Currently GDM does not remember what accessible technology programs have been started when switching applications. So if the user switches between the login program and the chooser, for example, then it is necessary for the user to redo the gesture. Users may need to also set up their default session so that the assistive technologies required are started automatically (or have appropriate key-bindings defined to start them) after the user session has started.</para> - - <para>There are some issues that cause users to have problems getting the gesture listeners to work. It is recommended that people use GDM version 2.8.0.5 or later for best results. Some X servers have a bug which causes detectable autorepeat to fail when XEVIE is enabled (which happens when atk-bridge is included as a GTK Module). This bug causes key gestures with a duration greater than 0 to always fail. A workaround is to simply redefine all key gestures so they have zero length duration. Some versions of GOK and gnopernicus will not launch unless the "gdm" user has a writable home directory. If you see an hourglass cursor when you complete a gesture but the program does not start, then you are likely having this problem. It should be considered a bug for AT programs to require having a writable home directory, so please file a bug with the AT program if you encounter this problem. Also note that some input devices require X server configuration before GDM will recognize them.</para> + <para> + Currently GDM does not remember what accessible technology + programs have been started when switching applications. So + if the user switches between the login program and the + chooser, for example, then it is necessary for the user to + redo the gesture. Users may need to also set up their default + session so that the assistive technologies required are + started automatically (or have appropriate key-bindings + defined to start them) after the user session has started. + </para> + + <para> + There are some issues that cause users to have problems + getting the gesture listeners to work. It is recommended that + people use GDM version 2.8.0.5 or later for best results. + Some X servers have a bug which causes detectable autorepeat + to fail when XEVIE is enabled (which happens when atk-bridge + is included as a GTK Module). This bug causes key gestures + with a duration greater than 0 to always fail. A workaround + is to simply redefine all key gestures so they have zero length + duration. Some versions of GOK and gnopernicus will not launch + unless the "gdm" user has a writable home directory. + If you see an hourglass cursor when you complete a gesture but the + program does not start, then you are likely having this problem. + It should be considered a bug for AT programs to require having a + writable home directory, so please file a bug with the AT + program if you encounter this problem. Also note that some input + devices require X server configuration before GDM will recognize + them. + </para> </sect2> <sect2 id="accessibilitysound"> <title>Налаштовування звуку спеціальних пожливостей</title> - <para>By default, GDM requires a media application such as "sox" to be present to play sounds for successful or failed login. GDM defaults the location of this application to <filename><bin>/play</filename> (or <filename><bin>/audioplay</filename> on Solaris. This can be changed via the SoundProgram GDM configuration option. Typically most text-to-speech programs (such as ORCA or Gnopernicus) use a separate mechanism to play audio.</para> + <para> + By default, GDM requires a media application such as + "sox" to be present to play sounds for successful or + failed login. GDM defaults + the location of this application to + <filename><bin>/play</filename> (or + <filename><bin>/audioplay</filename> on Solaris. This can + be changed via the SoundProgram GDM configuration option. + Typically most text-to-speech programs (such as ORCA or + Gnopernicus) use a separate mechanism to play audio. + </para> </sect2> </sect1> @@ -3294,35 +4353,83 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener <sect2 id="solarisconfiguration"> <title>Налаштовування Solaris</title> - <para>On Solaris, the following configuration is recommended. This turns on IPv6 and also turns on PreFetch for performance benefit. <screen> + <para> + On Solaris, the following configuration is recommended. + This turns on IPv6 and also turns on PreFetch for + performance benefit. + +<screen> ./autogen.sh --prefix=/usr --sysconfdir=/etc/X11 --localstatedir=/var --libexecdir=/usr/lib --enable-ipv6=yes --with-at-bindir=/usr/sfw/bin --with-prefetch --with-post-path=/usr/openwin/bin -</screen></para> +</screen> + </para> - <para>Configuring GDM with the "--with-post-path=/usr/openwin/bin" on Solaris is recommended for access to programs like Xnest.</para> + <para> + Configuring GDM with the + "--with-post-path=/usr/openwin/bin" on Solaris is + recommended for access to programs like Xnest. + </para> </sect2> <sect2 id="solarislogindevperm"> <title>Solaris /etc/logindevperm</title> - <para>GDM supports /etc/logindevperm, but only on Solaris 10 and higher. Refer to the logindevperm.4 man page for more information.</para> - - <para>To make /etc/logindevperm functionality work on Solaris 9 or earlier you would have to hack the GDM PreSession and PostSession script to chmod the device permissions directly. In other words, if /etc/logindevperm had a listing like this:</para> + <para> + GDM supports /etc/logindevperm, but only on Solaris 10 and higher. + Refer to the logindevperm.4 man page for more information. + </para> + + <para> + To make /etc/logindevperm functionality work on Solaris 9 or + earlier you would have to hack the GDM PreSession and + PostSession script to chmod the device permissions directly. In + other words, if /etc/logindevperm had a listing like this: + </para> <screen> /dev/console 0600 /dev/sound/* # звукові пристрої </screen> - <para>The PreSession script would need to be modified to chown /dev/console to the user:group who is logging into the console and ensure whatever permissions is specified in /etc/logindevperm (0600 for the line above). Then in the PostSession script chmod the device back to root:root and ensure 0600 this time (do not use the value in the /etc/logindevperm file). Linux uses a different mechanism for managing device permissions, so this extra scripting is not needed.</para> + <para> + The PreSession script would need to be modified to chown + /dev/console to the user:group who is logging into the console + and ensure whatever permissions is specified in /etc/logindevperm + (0600 for the line above). Then in the PostSession script chmod + the device back to root:root and ensure 0600 this time (do not + use the value in the /etc/logindevperm file). Linux uses a + different mechanism for managing device permissions, so this + extra scripting is not needed. + </para> </sect2> <sect2 id="solarisautomaticlogin"> <title>Автоматичний вхід на Solaris</title> - <para>Automatic login does not work on Solaris because PAM is not configured to support this feature by default. Automatic login is a GDM feature that is not enabled by default, so you would only notice this problem if you try to make use of it. Turning this feature on causes your computer to login to a specified username on startup without asking for username and password. This is an unsecure way to set up your computer.</para> - - <para>If using Solaris 10 or lower, then you need to compile the pam_allow.c code provided with the GDM release and install it to /usr/lib/security (or provide the full path in /etc/pam.conf) and ensure it is owned by uid 0 and not group or world writable.</para> - - <para>The following are reasonable pam.conf values for turning on automatic login in GDM. Make sure to read the PAM documentation (e.g. pam.d/pam.conf man page) and be comfortable with the security implications of any changes you intend to make to your configuration.</para> + <para> + Automatic login does not work on Solaris because PAM is not + configured to support this feature by default. Automatic + login is a GDM feature that is not enabled by default, so you + would only notice this problem if you try to make use of it. + Turning this feature on causes your computer to login to a + specified username on startup without asking for username + and password. This is an unsecure way to set up your + computer. + </para> + + <para> + If using Solaris 10 or lower, then you need to compile + the pam_allow.c code provided with the GDM release and + install it to /usr/lib/security (or provide the full path + in /etc/pam.conf) and ensure it is owned by uid 0 and not + group or world writable. + </para> + + <para> + The following are reasonable pam.conf values for turning on + automatic login in GDM. Make sure to read the PAM documentation + (e.g. pam.d/pam.conf man page) and be comfortable with the + security implications of any changes you intend to make to + your configuration. + </para> <screen> gdm-autologin auth required pam_unix_cred.so.1 @@ -3332,7 +4439,10 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener gdm-autologin password sufficient pam_allow.so.1 </screen> - <para>The above setup will cause no lastlog entry to be generated. If a lastlog entry is desired, then use the following for session:</para> + <para> + The above setup will cause no lastlog entry to be generated. If + a lastlog entry is desired, then use the following for session: + </para> <screen> gdm-autologin session required pam_unix_session.so.1 @@ -3343,11 +4453,29 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener <title>Інші особливості Solaris</title> <para>GDM підтримує деякі специфічні властивості Solaris:</para> - <para>GDM supports Solaris Auditing if running on Solaris 10 or higher. GDM should not be used if auditing is needed and running Solaris 9 or older.</para> - - <para>GDM supports a security feature which causes the X server to run as the user instead of as the root user. GDM must be using PAM for this feature to be enabled, which is the normal case for Solaris. This second feature has the side-effect of causing the X server to always restart between sessions, which disables the AlwaysRestartServer configuration option.</para> - - <para>Solaris supports the <filename>/etc/default/login</filename> interface, which affects the <filename>DefaultPath</filename>, <filename>RootPath</filename>, <filename>PasswordRequired</filename>, and <filename>AllowRemoteRoot</filename> options as described in the "Configuration" section.</para> + <para> + GDM supports Solaris Auditing if running on Solaris 10 or + higher. GDM should not be used if auditing is needed and + running Solaris 9 or older. + </para> + + <para> + GDM supports a security feature which causes the X server to + run as the user instead of as the root user. GDM must be using + PAM for this feature to be enabled, which is the normal case + for Solaris. This second feature has the side-effect of + causing the X server to always restart between sessions, which + disables the AlwaysRestartServer configuration option. + </para> + + <para> + Solaris supports the <filename>/etc/default/login</filename> + interface, which affects the <filename>DefaultPath</filename>, + <filename>RootPath</filename>, + <filename>PasswordRequired</filename>, and + <filename>AllowRemoteRoot</filename> options as described in the + "Configuration" section. + </para> </sect2> </sect1> @@ -3359,23 +4487,48 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener <sect2 id="terminallab"> <title>Термінальна лабораторія з одним сервером</title> - <para>Suppose you want to make a lab full of X terminals that all connect to one server machine. So let's call one X terminal <filename>xterminal</filename> and let's call the server machine <filename>appserver</filename>. You install GDM on both.</para> + <para> + Suppose you want to make a lab full of X terminals that all connect + to one server machine. So let's call one X terminal + <filename>xterminal</filename> and let's call the server machine + <filename>appserver</filename>. You install GDM on both. + </para> - <para>On <filename>appserver</filename> you enable XDMCP, so you have <screen> + <para> + On <filename>appserver</filename> you enable XDMCP, so you have +<screen> [xdmcp] Enable=true -</screen> If you want no local screens here, you can then make the <filename>[servers]</filename> section empty.</para> - - <para>On the <filename>xterminal</filename> you disable XDMCP (you don't want anyone to connect to the xterminal really). You will add a server type perhaps called <filename>Terminal</filename> as follows: <screen> +</screen> + If you want no local screens here, you can then + make the <filename>[servers]</filename> section empty. + </para> + + <para> + On the <filename>xterminal</filename> you disable XDMCP (you don't + want anyone to connect to the xterminal really). You will add a + server type perhaps called <filename>Terminal</filename> as follows: +<screen> [server-Terminal] name=Terminal server command=/path/to/X -terminate flexible=false handled=false -</screen> This definition should in fact be included in the standard configuration file. Notice that we made the <filename>handled</filename> key false since we don't want GDM to handle this server localy. Also note that we have not yet added the <filename>-query</filename> argument, you can add that here, or in the <filename>[servers]</filename> section. We'll define our local servers as follows: <screen> +</screen> + This definition should in fact be included in the standard + configuration file. Notice that we made the + <filename>handled</filename> key false since we don't want GDM to + handle this server localy. Also note that we have not yet added the + <filename>-query</filename> argument, you can add that here, or in the + <filename>[servers]</filename> section. We'll define our local + servers as follows: +<screen> [servers] 0=Terminal -query appserver -</screen> This will run a direct XDMCP query to the server named <filename>appserver</filename>.</para> +</screen> + This will run a direct XDMCP query to the server named + <filename>appserver</filename>. + </para> </sect2> <sect2 id="terminallabtwo"> @@ -3383,53 +4536,154 @@ handled=false <para>Скажімо ви хочете створити лабораторію з X-терміналами, які з'єднані з кількома серверами. Тож створимо їх <filename>appserverone</filename> та <filename>appservertwo</filename>. Знову назвемо наш сервер X-терміналів <filename>xterminal</filename>. Параметри на обох серверах такі ж як і у випадку з одним сервером. Не слід явно вмикати непрямі запити до сервера, бо на X-терміналах локально запускається селектор вузлів.</para> - <para>So on the <filename>xterminal</filename> you again disable XDMCP. You will add a server type perhaps called <filename>Chooser</filename> as follows: <screen> + <para> + So on the <filename>xterminal</filename> you again disable XDMCP. + You will add a server type perhaps called <filename>Chooser</filename> + as follows: +<screen> [server-Chooser] name=Chooser server command=/path/to/X flexible=false chooser=true -</screen> And again this definition should in fact be included in the standard configuration file. Notice that we made the <filename>chooser</filename> key true here. This will run the XDMCP chooser for this server, and when the user chooses a host GDM will run a query for that host. Then we will define our local servers as follows: <screen> +</screen> + And again this definition should in fact be included in the standard + configuration file. Notice that we made the + <filename>chooser</filename> key true here. This will run the XDMCP + chooser for this server, and when the user chooses a host GDM will run + a query for that host. Then we will define our local servers as + follows: +<screen> [servers] 0=Chooser -</screen></para> - - <para>The XDMCP chooser on the X terminal will normally give a broadcast query to see which servers exist on the network. If the two servers are not reachable by a broadcast query, you must add them by hand to the configuration file. So in the <filename>[chooser]</filename> section you would have: <screen> +</screen> + </para> + + <para> + The XDMCP chooser on the X terminal will normally give a broadcast + query to see which servers exist on the network. If the two servers + are not reachable by a broadcast query, you must add them by hand to + the configuration file. So in the <filename>[chooser]</filename> + section you would have: +<screen> Hosts=appserverone,appservertwo -</screen> and any other servers you wish the users to be able to connect to.</para> - - <para>Sometimes you may want to run the chooser on the server side however. Then what you want to do is to run a configuration similar to the previous section about the one server configuration with XDMCP indirect queries enabled on <filename>appserver</filename> and on the X terminals you'd have <screen> +</screen> + and any other servers you wish the users to be able to connect to. + </para> + + <para> + Sometimes you may want to run the chooser on the server side however. + Then what you want to do is to run a configuration similar to the + previous section about the one server configuration with XDMCP + indirect queries enabled on <filename>appserver</filename> and on the + X terminals you'd have +<screen> [servers] 0=Terminal -indirect appserver -</screen> This way for example you only have to maintain one <filename>Hosts</filename> entry. However as a disadvantage then, the <filename>appserver</filename> must then always be available. So it's not good for situations where you want to have several servers and not all of them have to be on all the time. You could also have one of the X terminals handle indirect XDMCP queries and serve up the chooser to the other X terminals.</para> +</screen> + This way for example you only have to maintain one + <filename>Hosts</filename> entry. However as a disadvantage then, + the <filename>appserver</filename> must then always be available. So + it's not good for situations where you want to have several servers + and not all of them have to be on all the time. You could also have + one of the X terminals handle indirect XDMCP queries and serve up the + chooser to the other X terminals. + </para> </sect2> </sect1> <sect1 id="troubleshooting"> <title>Усунення проблем</title> - <para>This section discusses helpful tips for getting GDM working. In general, if you have a problem using GDM, you can submit a bug to the "gdm" category in <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink> or send an email to the <address><email>gdm-list@gnome.org</email></address> mail list.</para> - - <para>If GDM is failing to work properly, it is always a good idea to include debug information. Use the <command>gdmsetup</command> command to turn on debug ("Enable debug messages to system log" checkbox in the "Security" tab), then use GDM to the point where it fails, and include the GDM output sent to your system log (<filename><var>/log/messages</filename> or <filename><var>/adm/messages</filename> depending on your operating system). Since the system log can be large, please only include the GDM debug information and do not sent the entire file. If you do not see any GDM syslog output, you may need to configure syslog (see syslog.3c man page).</para> - - <para>You should not leave debug on after collecting data. It will clutter your syslog and slow system performance.</para> + <para> + This section discusses helpful tips for getting GDM working. In general, + if you have a problem using GDM, you can submit a bug to the + "gdm" category in + <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink> + or send an email to the + <address><email>gdm-list@gnome.org</email></address> mail list. + </para> + + <para> + If GDM is failing to work properly, it is always a good idea to include + debug information. Use the <command>gdmsetup</command> command to turn + on debug ("Enable debug messages to system log" checkbox in the + "Security" tab), then use GDM to the point where it fails, and + include the GDM output sent to your system log + (<filename><var>/log/messages</filename> or + <filename><var>/adm/messages</filename> depending on your operating + system). Since the system log can be large, please only include the GDM + debug information and do not sent the entire file. If you do not see any + GDM syslog output, you may need to configure syslog (see syslog.3c man + page). + </para> + + <para> + You should not leave debug on after collecting data. It will clutter your + syslog and slow system performance. + </para> <sect2 id="wontstart"> <title>GDM не запускається</title> - <para>There are a many problems that can cause GDM to fail to start, but this section will discuss a few common problems and how to approach tracking down a problem with GDM starting. Some problems will cause GDM to respond with an error message or dialog when it tries to start, but it can be difficult to track down problems when GDM fails silently.</para> - - <para>First make sure that the Xserver is configured properly. The GDM configuration file contains a command in the [server-Standard] section that is used for starting the Xserver. Verify that this command works on your system. Running this command from the console should start the Xserver. If it fails, then the problem is likely with your Xserver configuration. Refer to your Xserver error log for an idea of what the problem may be. The problem may also be that your Xserver requires different command-line options. If so, then modify the Xserver command in the GDM configuration file so that it is correct for your system.</para> - - <para>Another common problem is that the GDM greeter program is having trouble starting. This can happen, for example, if GDM cannot find a needed library or other resource. Try starting the Xserver and a terminal program, set the shell environment variable DOING_GDM_DEVELOPMENT=1 and run <command><lib>/gdmlogin</command> or <command><lib>/gdmgreeter</command>. Any error messages echoed to the terminal will likely highlight the problem. Also, turning on debug and checking the output sent to the system log will often highlight the problem.</para> - - <para>Also make sure that the <filename>/tmp</filename> directory has reasonable ownership and permissions, and that the machine's file system is not full. These problems will cause GDM to fail to start.</para> + <para> + There are a many problems that can cause GDM to fail to start, but + this section will discuss a few common problems and how to approach + tracking down a problem with GDM starting. Some problems will + cause GDM to respond with an error message or dialog when it tries + to start, but it can be difficult to track down problems when GDM + fails silently. + </para> + + <para> + First make sure that the Xserver is configured properly. The + GDM configuration file contains a command in the [server-Standard] + section that is used for starting the Xserver. Verify that this + command works on your system. Running this command from the + console should start the Xserver. If it fails, then the problem + is likely with your Xserver configuration. Refer to your Xserver + error log for an idea of what the problem may be. The problem may + also be that your Xserver requires different command-line options. + If so, then modify the Xserver command in the GDM configuration file + so that it is correct for your system. + </para> + + <para> + Another common problem is that the GDM greeter program is having + trouble starting. This can happen, for example, if GDM cannot find + a needed library or other resource. Try starting the Xserver and + a terminal program, set the shell environment variable + DOING_GDM_DEVELOPMENT=1 and run + <command><lib>/gdmlogin</command> + or <command><lib>/gdmgreeter</command>. Any error messages + echoed to the terminal will likely highlight the problem. Also, + turning on debug and checking the output sent to the system log + will often highlight the problem. + </para> + + <para> + Also make sure that the <filename>/tmp</filename> directory has + reasonable ownership and permissions, and that the machine's file + system is not full. These problems will cause GDM to fail to start. + </para> </sect2> <sect2 id="notaccessfile"> <title>GDM не може отримати доступ до параметрів користувача</title> - <para>GDM saves user settings, such as your default session and default language, in the <filename>~/.dmrc</filename>. Other files, such as the user's <filename>~/.Xauthority</filename> file will also affect login. GDM, by default, is strict about how it tries to access files in the users home directory, and will ignore the file if they do not conform to certain rules. You can use the <filename>RelaxPermissions</filename> configuration option to make GDM less strict about how it accesses files in the user's home directory, or correct the permissions issues that cause GDM to ignore the file. This is discussed in detail described in the "File Access" section of the "Overview".</para> + <para> + GDM saves user settings, such as your default session and default + language, in the <filename>~/.dmrc</filename>. Other files, such + as the user's <filename>~/.Xauthority</filename> file will also + affect login. GDM, by default, is strict about how it tries to + access files in the users home directory, and will ignore the file if + they do not conform to certain rules. You can use the + <filename>RelaxPermissions</filename> configuration option to + make GDM less strict about how it accesses files in the user's + home directory, or correct the permissions issues that cause GDM + to ignore the file. This is discussed in detail described in the + "File Access" section of the "Overview". + </para> </sect2> </sect1> diff --git a/docs/uk/legal.xml b/docs/uk/legal.xml index a9c75713..49a4a822 100644 --- a/docs/uk/legal.xml +++ b/docs/uk/legal.xml @@ -5,5 +5,12 @@ <para>Більшість назв, що використовуються компаніями для розповсюдження їх продуктів та послуг є торговими марками. Якщо такі назви зустрічаються у документації з GNOME та учасникам проекту документування GNOME відомо, що вони є торговими марками, тоді ці назви пишуться великими літерами або починаються з великої літери.</para> - <para>ДОКУМЕНТ ТА ЗМІНЕНІ ВЕРСІЇ ЦЬОГО ДОКУМЕНТУ ПОСТАЧАЮТЬСЯ НА УМОВАХ ВІЛЬНОЇ ЛІЦЕНЗІЇ ДЛЯ ДОКУМЕНТАЦІЇ GNU З ПОДАЛЬШИМ РОЗУМІННЯМ ЩО: <orderedlist><listitem><para>ДОКУМЕНТ НАДАЄТЬСЯ "ЯК Є", БЕЗ БУДЬ-ЯКИХ ГАРАНТІЇ, ЯВНИХ ЧИ НЕЯВНИХ, ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ГАРАНТІЙ ЩО ЦЕЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ ДОКУМЕНТА ВІЛЬНІ ВІД ДЕФЕКТІВ, ПРИДАТНІ ДО ПРОДАЖУ, ВІДПОВІДАЮТЬ ПЕВНІЙ МЕТІ АБО НЕ ПОРУШУЮТЬ ЧИЇСЬ ПРАВА. ВЕСЬ РИЗИК ЗА ЯКІСТЬ, ТОЧНІСТЬ, ТА ЧИННІСТЬ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНИХ ВЕРСІЙ ЛЕЖИТЬ НА ВАС. ЯКЩО БУДЬ-ЯКИЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ БУДУТЬ ВИЗНАНІ ДЕФЕКТНИМИ У БУДЬ-ЯКОМУ ВІДНОШЕННІ, ВИ (НЕ ПОЧАТКОВИЙ УКЛАДАЧ, АВТОР АБО БУДЬ-ЯКИЙ СПІВАВТОР) БЕРЕТЕ НА СЕБЕ ВИТРАТИ ЗА БУДЬ-ЯКЕ НЕОБХІДНЕ ОБСЛУГОВУВАННЯ, РЕМОНТ ЧИ ВИПРАВЛЕННЯ. ЦЯ ВІДМОВА ВІД ГАРАНТІЙ СКЛАДАЄ ВАЖЛИВУ ЧАСТИНУ ЦІЄЇ ЛІЦЕНЗІЇ. НЕ ДОПУСКАЄТЬСЯ ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНОЇ ВЕРСІЇ БЕЗ ПРИЙНЯТТЯ ЦІЄЇ ВІДМОВИ; ТА</para></listitem><listitem><para>НІ ЗА ЯКИХ ОБСТАВИН ТА ЗА БУДЬ-ЯКОГО ЗАКОНОДАВСТВА, ЧИ ТО ГРОМАДЯНСЬКОЇ ВІДПОВІДАЛЬНОСТІ (ВКЛЮЧАЮЧИ ХАЛАТНІСТЬ), ДОГОВОРУ, ЧИ ЧОГОСЬ ІНШОГО, АВТОР, ПОЧАТКОВИЙ УКЛАДАЧ, БУДЬ-ЯКИЙ СПІВАВТОР, АБО ДИСТРИБ'ЮТОР ДОКУМЕНТУ ЧИ ЗМІНЕНОЇ ВЕРСІЇ ДОКУМЕНТУ, АБО БУДЬ-ЯКИЙ ПОСТАЧАЛЬНИК БУДЬ-ЯКОЇ З ЦИХ СТОРІН, НЕ НЕСЕ ВІДПОВІДАЛЬНІСТЬ ПЕРЕД БУДЬ-ЯКОЮ ОСОБОЮ ЗА БУДЬ-ЯКІ ПРЯМІ, НЕПРЯМІ, ОСОБЛИВІ, ВИПАДКОВІ, АБО ІСТОТНІ ЗБИТКИ БУДЬ-ЯКОГО ХАРАКТЕРУ ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ЗБИТКАМИ ВІД ВТРАТИ ПРЕСТИЖУ, ЗУПИНКИ РОБОТИ, ЗБОЇВ АБО НЕСПРАВНОСТЕЙ КОМП'ЮТЕРА, АБО БУДЬ-ЯКІ ІНШІ ЗБИТКИ АБО ВТРАТИ ЩО ВИНИКЛИ БЕЗВІДНОСНО АБО ВНАСЛІДОК ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ ТА ЗМІНЕНИХ ВЕРСІЙ ЦЬОГО ДОКУМЕНТУ, НАВІТЬ ЯКЩО ЦІ СТОРОНИ, МОЖЛИВО, БУЛИ ПРОІНФОРМОВАНІ ПРО МОЖЛИВІСТЬ ТАКИХ ЗБИТКІВ.</para></listitem></orderedlist></para> + <para>ДОКУМЕНТ ТА ЗМІНЕНІ ВЕРСІЇ ЦЬОГО ДОКУМЕНТУ ПОСТАЧАЮТЬСЯ НА УМОВАХ ВІЛЬНОЇ ЛІЦЕНЗІЇ ДЛЯ ДОКУМЕНТАЦІЇ GNU З ПОДАЛЬШИМ РОЗУМІННЯМ ЩО: <orderedlist> + <listitem> + <para>ДОКУМЕНТ НАДАЄТЬСЯ "ЯК Є", БЕЗ БУДЬ-ЯКИХ ГАРАНТІЇ, ЯВНИХ ЧИ НЕЯВНИХ, ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ГАРАНТІЙ ЩО ЦЕЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ ДОКУМЕНТА ВІЛЬНІ ВІД ДЕФЕКТІВ, ПРИДАТНІ ДО ПРОДАЖУ, ВІДПОВІДАЮТЬ ПЕВНІЙ МЕТІ АБО НЕ ПОРУШУЮТЬ ЧИЇСЬ ПРАВА. ВЕСЬ РИЗИК ЗА ЯКІСТЬ, ТОЧНІСТЬ, ТА ЧИННІСТЬ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНИХ ВЕРСІЙ ЛЕЖИТЬ НА ВАС. ЯКЩО БУДЬ-ЯКИЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ БУДУТЬ ВИЗНАНІ ДЕФЕКТНИМИ У БУДЬ-ЯКОМУ ВІДНОШЕННІ, ВИ (НЕ ПОЧАТКОВИЙ УКЛАДАЧ, АВТОР АБО БУДЬ-ЯКИЙ СПІВАВТОР) БЕРЕТЕ НА СЕБЕ ВИТРАТИ ЗА БУДЬ-ЯКЕ НЕОБХІДНЕ ОБСЛУГОВУВАННЯ, РЕМОНТ ЧИ ВИПРАВЛЕННЯ. ЦЯ ВІДМОВА ВІД ГАРАНТІЙ СКЛАДАЄ ВАЖЛИВУ ЧАСТИНУ ЦІЄЇ ЛІЦЕНЗІЇ. НЕ ДОПУСКАЄТЬСЯ ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНОЇ ВЕРСІЇ БЕЗ ПРИЙНЯТТЯ ЦІЄЇ ВІДМОВИ; ТА</para> + </listitem> + <listitem> + <para>НІ ЗА ЯКИХ ОБСТАВИН ТА ЗА БУДЬ-ЯКОГО ЗАКОНОДАВСТВА, ЧИ ТО ГРОМАДЯНСЬКОЇ ВІДПОВІДАЛЬНОСТІ (ВКЛЮЧАЮЧИ ХАЛАТНІСТЬ), ДОГОВОРУ, ЧИ ЧОГОСЬ ІНШОГО, АВТОР, ПОЧАТКОВИЙ УКЛАДАЧ, БУДЬ-ЯКИЙ СПІВАВТОР, АБО ДИСТРИБ'ЮТОР ДОКУМЕНТУ ЧИ ЗМІНЕНОЇ ВЕРСІЇ ДОКУМЕНТУ, АБО БУДЬ-ЯКИЙ ПОСТАЧАЛЬНИК БУДЬ-ЯКОЇ З ЦИХ СТОРІН, НЕ НЕСЕ ВІДПОВІДАЛЬНІСТЬ ПЕРЕД БУДЬ-ЯКОЮ ОСОБОЮ ЗА БУДЬ-ЯКІ ПРЯМІ, НЕПРЯМІ, ОСОБЛИВІ, ВИПАДКОВІ, АБО ІСТОТНІ ЗБИТКИ БУДЬ-ЯКОГО ХАРАКТЕРУ ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ЗБИТКАМИ ВІД ВТРАТИ ПРЕСТИЖУ, ЗУПИНКИ РОБОТИ, ЗБОЇВ АБО НЕСПРАВНОСТЕЙ КОМП'ЮТЕРА, АБО БУДЬ-ЯКІ ІНШІ ЗБИТКИ АБО ВТРАТИ ЩО ВИНИКЛИ БЕЗВІДНОСНО АБО ВНАСЛІДОК ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ ТА ЗМІНЕНИХ ВЕРСІЙ ЦЬОГО ДОКУМЕНТУ, НАВІТЬ ЯКЩО ЦІ СТОРОНИ, МОЖЛИВО, БУЛИ ПРОІНФОРМОВАНІ ПРО МОЖЛИВІСТЬ ТАКИХ ЗБИТКІВ.</para> + </listitem> + </orderedlist></para> </legalnotice> diff --git a/gui/gdmsetup.c b/gui/gdmsetup.c index de7a2e85..3ebe4eb3 100644 --- a/gui/gdmsetup.c +++ b/gui/gdmsetup.c @@ -5412,15 +5412,13 @@ background_filechooser_response (GtkWidget *file_chooser, gpointer data) if (filename != NULL && (strcmp (ve_sure_string (value), ve_sure_string (filename)) != 0)) { - g_signal_handlers_disconnect_by_func (file_chooser, - (gpointer) background_filechooser_response, - file_chooser); - - gtk_file_chooser_set_filename (GTK_FILE_CHOOSER (file_chooser), - filename); + gchar *old_filename; + old_filename = gtk_file_chooser_get_filename (GTK_FILE_CHOOSER (file_chooser)); - g_signal_connect (G_OBJECT (file_chooser), "selection-changed", - G_CALLBACK (background_filechooser_response), file_chooser); + if (strcmp (old_filename, filename) == 0) + gtk_file_chooser_set_filename (GTK_FILE_CHOOSER (file_chooser), + filename); + g_free (old_filename); if (strcmp (ve_sure_string (value), ve_sure_string (filename)) != 0) { gdm_setup_config_set_string (key, (char *)ve_sure_string (filename)); @@ -5449,7 +5447,7 @@ logo_filechooser_response (GtkWidget *file_chooser, gpointer data) * value to the default in this case seems to work around this. */ if (filename == NULL && !ve_string_empty (value)) - filename = value; + filename = g_strdup (value); if (filename == NULL) { value = gdm_config_get_string (GDM_KEY_CHOOSER_BUTTON_LOGO); @@ -5470,15 +5468,14 @@ logo_filechooser_response (GtkWidget *file_chooser, gpointer data) if (filename != NULL && (strcmp (ve_sure_string (value), ve_sure_string (filename)) != 0)) { - g_signal_handlers_disconnect_by_func (file_chooser, - (gpointer) logo_filechooser_response, - file_chooser); + gchar *old_filename; - gtk_file_chooser_set_filename (GTK_FILE_CHOOSER (file_chooser), - filename); + old_filename = gtk_file_chooser_get_filename (GTK_FILE_CHOOSER (file_chooser)); - g_signal_connect (G_OBJECT (file_chooser), "selection-changed", - G_CALLBACK (logo_filechooser_response), file_chooser); + if (strcmp (old_filename, filename) != 0) + gtk_file_chooser_set_filename (GTK_FILE_CHOOSER (file_chooser), + filename); + g_free (old_filename); if (GTK_TOGGLE_BUTTON (image_toggle)->active == TRUE) { gdm_setup_config_set_string (key, |