diff options
| author | Brian Cameron <brian.cameron@sun.com> | 2006-01-07 01:43:14 +0000 |
|---|---|---|
| committer | Brian Cameron <bcameron@src.gnome.org> | 2006-01-07 01:43:14 +0000 |
| commit | 1051b4041254a483688b5e35f97650b466e6eb26 (patch) | |
| tree | c1ca5901c5b149599bb1272961118a48bf12dfea /docs | |
| parent | 74a65bba388196e59298bce8148c2456265ec629 (diff) | |
| download | gdm-1051b4041254a483688b5e35f97650b466e6eb26.tar.gz | |
Added "Performance" section to discuss the --with-prefetch option.
2006-01-04 Brian Cameron <brian.cameron@sun.com>
* docs/C/gdm.xml: Added "Performance" section to discuss
the --with-prefetch option.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/C/gdm.xml | 30 | ||||
| -rw-r--r-- | docs/es/es.po | 11202 | ||||
| -rw-r--r-- | docs/es/gdm.xml | 3034 |
3 files changed, 5326 insertions, 8940 deletions
diff --git a/docs/C/gdm.xml b/docs/C/gdm.xml index c56a6109..e9fb6839 100644 --- a/docs/C/gdm.xml +++ b/docs/C/gdm.xml @@ -148,7 +148,9 @@ <para> For further information about GDM, see the <ulink type="http" url="http://www.gnome.org/projects/gdm/"> - the GDM project website</ulink>. + the GDM project website</ulink>. Please submit any bug reports or + enhancement requests to the "gdm" category in + <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink>. </para> </sect2> @@ -615,6 +617,32 @@ time. </para> </sect2> + + <sect2 id="performance"> + <title>GDM Performance</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 --with-prefetch option. + This will cause GDM to install the gdmprefetch program to the + EXPANDED_LIBEXEC directory, install the gdmprefetchlist to the + <etc>/gdm directory, and set the PreFetchProgram configuration + variable so that the gdmprefetch program is called with the default + gdmprefetchlist file. The default gdmprefetchlist 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> <sect1 id="Security"> diff --git a/docs/es/es.po b/docs/es/es.po index 193a984e..59b35e2e 100644 --- a/docs/es/es.po +++ b/docs/es/es.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: es\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2006-01-05 13:20-0800\n" +"POT-Creation-Date: 2006-01-06 17:41-0800\n" "PO-Revision-Date: 2006-01-07 00:09+0100\n" "Last-Translator: Francisco Javier F. Serrador <serrador@cvs.gnome.org>\n" "Language-Team: Spanish <traductores@es.gnome.org>\n" @@ -234,11 +234,16 @@ msgstr "Términos y convenciones usados en este manual" msgid "" "Chooser - A program used to select a remote host for managing a display " "remotely on the local display (<command>gdmchooser</command>)." -msgstr "Selector- Un programa usado para seleccionar un host remoto para gestionar una pantalla remotamente en la pantalla local (<command>gdmchooser</command>)." +msgstr "" +"Selector- Un programa usado para seleccionar un host remoto para gestionar " +"una pantalla remotamente en la pantalla local (<command>gdmchooser</" +"command>)." #: ../C/gdm.xml:82 (para) -msgid "Configurator - The configuration application (<command>gdmsetup</command>)." -msgstr "Configurador - La aplicación de configuración (<command>gdmsetup</command>)." +msgid "" +"Configurator - The configuration application (<command>gdmsetup</command>)." +msgstr "" +"Configurador - La aplicación de configuración (<command>gdmsetup</command>)." #: ../C/gdm.xml:87 (para) msgid "" @@ -262,15 +267,19 @@ msgstr "" #: ../C/gdm.xml:101 (para) msgid "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)." -msgstr "Interfaz GTK+ - La ventana de entrada estándar (<command>gdmlogin</command>)." +msgstr "" +"Interfaz GTK+ - La ventana de entrada estándar (<command>gdmlogin</command>)." #: ../C/gdm.xml:105 (para) msgid "PAM - Pluggable Authentication Mechanism" msgstr "PAM - Mecanismo de autenticación enchufable" #: ../C/gdm.xml:109 (para) -msgid "Themed Greeter - The themable login window ( <command>gdmgreeter</command>)." -msgstr "Interfaz con temas - La ventana de entrada con temas intercambiables ( <command>gdmgreeter</command>)." +msgid "" +"Themed Greeter - The themable login window ( <command>gdmgreeter</command>)." +msgstr "" +"Interfaz con temas - La ventana de entrada con temas intercambiables " +"( <command>gdmgreeter</command>)." #: ../C/gdm.xml:114 (para) msgid "XDMCP - X Display Manage Protocol" @@ -297,8 +306,8 @@ msgstr "" "<filename><etc>/gdm/PreSession</filename> usualmente significa " "<filename><etc/X11>/gdm/PreSession</filename>. note que para " "interoperatibilidad se recomienda que use un --prefix de <filename>/usr</" -"filename> y un directorio de configuración del sistema (--sysconfdir) <filename>/etc/X11</" -"filename>." +"filename> y un directorio de configuración del sistema (--sysconfdir) " +"<filename>/etc/X11</filename>." #: ../C/gdm.xml:134 (title) msgid "Overview" @@ -319,18 +328,22 @@ msgstr "" "nada de código de XDM /X Consortium." #: ../C/gdm.xml:148 (para) +#, fuzzy msgid "" "For further information about GDM, see the <ulink type=\"http\" url=\"http://" -"www.gnome.org/projects/gdm/\"> the GDM project website</ulink>." +"www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. Please " +"submit any bug reports or enhancement requests to the \"gdm\" category in " +"<ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</" +"ulink>." msgstr "" "Para más información acerca de GDM, vea <ulink type=\"http\" url=\"http://" "www.gnome.org/projects/gdm/\"> el sitio web del proyecto GDM</ulink>." -#: ../C/gdm.xml:156 (title) +#: ../C/gdm.xml:158 (title) msgid "The GDM Daemon" msgstr "El demonio GDM" -#: ../C/gdm.xml:158 (para) +#: ../C/gdm.xml:160 (para) msgid "" "The GDM daemon is responsible for managing displays on the system. This " "includes authenticating users, starting the user session, and terminating " @@ -341,14 +354,14 @@ msgid "" "scripts discussed below are discussed in this \"Configuring GDM section\"." msgstr "" -#: ../C/gdm.xml:169 (para) +#: ../C/gdm.xml:171 (para) msgid "" "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." msgstr "" -#: ../C/gdm.xml:176 (para) +#: ../C/gdm.xml:178 (para) msgid "" "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 " @@ -358,7 +371,7 @@ msgid "" "discussed in the next section." msgstr "" -#: ../C/gdm.xml:186 (para) +#: ../C/gdm.xml:188 (para) msgid "" "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 " @@ -374,7 +387,7 @@ msgid "" "input/output so the daemon can handle the actual authentication." msgstr "" -#: ../C/gdm.xml:203 (para) +#: ../C/gdm.xml:205 (para) msgid "" "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 " @@ -389,7 +402,7 @@ msgid "" "(after entering the root password)." msgstr "" -#: ../C/gdm.xml:218 (para) +#: ../C/gdm.xml:220 (para) msgid "" "GDM, by default, will use Pluggable Authentication Modules (PAM) for " "authentication, but can also support regular crypt and shadow passwords on " @@ -407,11 +420,11 @@ msgid "" "as root." msgstr "" -#: ../C/gdm.xml:237 (title) +#: ../C/gdm.xml:239 (title) msgid "Different Display Types" msgstr "Tipos de pantalla diferentes" -#: ../C/gdm.xml:239 (para) +#: ../C/gdm.xml:241 (para) msgid "" "GDM supports three different display types: static (local) displays, " "flexible (on-demand) displays, and XDMCP (remote) displays. The \"X Server " @@ -420,17 +433,19 @@ msgid "" "displays are defined in the GDM configuration file." msgstr "" -#: ../C/gdm.xml:248 (para) +#: ../C/gdm.xml:250 (para) msgid "" "Local static displays are always started by the daemon, and when they die or " "are killed, they are restarted. GDM can run as many of these as needed. GDM " "can also manage displays on which it does not manage a GUI login, thus GDM " "can be used for supporting X terminals." msgstr "" -"Las pantallas locales estáticas siempre se inician por el demonio, y cuando mueren o son matadas, se reinician. " -"GDM puede además gestionar pantallas que en las cuales él no gestione la entrada, así que GDM puede usarse para soportar terminales X." +"Las pantallas locales estáticas siempre se inician por el demonio, y cuando " +"mueren o son matadas, se reinician. GDM puede además gestionar pantallas que " +"en las cuales él no gestione la entrada, así que GDM puede usarse para " +"soportar terminales X." -#: ../C/gdm.xml:255 (para) +#: ../C/gdm.xml:257 (para) msgid "" "Flexible, or on demand displays, are started via the socket protocol with " "the <command>gdmflexiserver</command> command. This feature is only " @@ -451,7 +466,7 @@ msgid "" "that the X server supports Xnest." msgstr "" -#: ../C/gdm.xml:276 (para) +#: ../C/gdm.xml:278 (para) msgid "" "The last display type is the XDMCP remote displays which are described in " "the next section. Remote hosts can connect to GDM and present the login " @@ -460,11 +475,11 @@ msgid "" "suspend, or configure GDM are not shown." msgstr "" -#: ../C/gdm.xml:286 (title) +#: ../C/gdm.xml:288 (title) msgid "XDMCP" msgstr "XDMCP" -#: ../C/gdm.xml:290 (para) +#: ../C/gdm.xml:292 (para) msgid "" "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 " @@ -473,7 +488,7 @@ msgid "" "GDM service section in the TCP Wrappers configuration file." msgstr "" -#: ../C/gdm.xml:299 (para) +#: ../C/gdm.xml:301 (para) msgid "" "GDM includes several measures making it more resistant to denial of service " "attacks on the XDMCP service. A lot of the protocol parameters, handshaking " @@ -481,7 +496,7 @@ msgid "" "however. Do not change them unless you know what you are doing." msgstr "" -#: ../C/gdm.xml:307 (para) +#: ../C/gdm.xml:309 (para) msgid "" "GDM listens to UDP port 177 and will respond to QUERY and BROADCAST_QUERY " "requests by sending a WILLING packet to the originator." @@ -489,7 +504,7 @@ msgstr "" "GDM escucha en el puerto UDP 177 y responderá a las peticiones QUERY y " "BROADCAST_QUERY enviando un paquete WILLING al originador." -#: ../C/gdm.xml:312 (para) +#: ../C/gdm.xml:314 (para) msgid "" "GDM can also be configured to honor INDIRECT queries and present a host " "chooser to the remote display. GDM will remember the user's choice and " @@ -507,17 +522,17 @@ msgstr "" "Esta extensión está soportada sólo si ambos demonios son GDM. Es " "transparente y será ignorada por XDM u otros demonios que implementan XDMCP." -#: ../C/gdm.xml:322 (para) +#: ../C/gdm.xml:324 (para) msgid "" "Refer to the \"Security\" section for information about security concerns " "when using XDMCP." msgstr "" -#: ../C/gdm.xml:329 (title) +#: ../C/gdm.xml:331 (title) msgid "The GTK+ Greeter" msgstr "El interfaz GTK+" -#: ../C/gdm.xml:331 (para) +#: ../C/gdm.xml:333 (para) msgid "" "The GTK+ Greeter is the default graphical user interface that is presented " "to the user. The greeter contains a menu at the top, an optional face " @@ -527,7 +542,7 @@ msgstr "" "usuario. El interfaz contiene un menú en la parte superior, un visor de " "rostros opcional, un logo opcional y un widget para entrada de texto." -#: ../C/gdm.xml:337 (para) +#: ../C/gdm.xml:339 (para) msgid "" "The text entry field is used for entering logins, passwords, passphrases " "etc. <command>gdmlogin</command> is controlled by the underlying daemon and " @@ -545,7 +560,7 @@ msgstr "" "la etiqueta sobre la entrada de texto para corresponder con el valor que el " "sistema de autenticación quiere que el usuario introduzca." -#: ../C/gdm.xml:347 (para) +#: ../C/gdm.xml:349 (para) msgid "" "The menu bar in the top of the greeter enables the user to select the " "requested session type/desktop environment, select an appropriate locale/" @@ -553,23 +568,30 @@ msgid "" "user knows the root password), change the GTK+ theme, or start an XDMCP " "chooser." msgstr "" -"La barra de menú en la parte superior del interfaz permite al usuario seleccionar el tipo/escritorio de entorno de sesión, seleccionar una " -"configuración regional/idioma adecuado, apagar/reiniciar/suspender el equipo, configurar GDM (siempre que el usuario conozca la contraseña " -"de administrador), cambiar el tema GTK+ o iniciar un selector XDMCP." +"La barra de menú en la parte superior del interfaz permite al usuario " +"seleccionar el tipo/escritorio de entorno de sesión, seleccionar una " +"configuración regional/idioma adecuado, apagar/reiniciar/suspender el " +"equipo, configurar GDM (siempre que el usuario conozca la contraseña de " +"administrador), cambiar el tema GTK+ o iniciar un selector XDMCP." -#: ../C/gdm.xml:355 (para) +#: ../C/gdm.xml:357 (para) msgid "" "The greeter can optionally display a logo in the login window. The image " "must be in a format readable to the gdk-pixbuf library (GIF, JPG, PNG, TIFF, " "XPM and possibly others), and it must be readable to the GDM user. See the " "<filename>Logo</filename> option in the reference section below for details." -msgstr "El interfaz de entrada puede mostrar opcionalmente un logotipo en la ventana de entrada. La imagen debe estar en un formato legible por la biblioteca gdk-pixbuf (GIF, JPG, PNG, TIFF, XPM y posiblemente otros), y debe tener permiso de lectura para el usuario de GDM. Vea la opción <filename>Logotipo</filename> en la sección de referencia inferior para los detalles." +msgstr "" +"El interfaz de entrada puede mostrar opcionalmente un logotipo en la ventana " +"de entrada. La imagen debe estar en un formato legible por la biblioteca gdk-" +"pixbuf (GIF, JPG, PNG, TIFF, XPM y posiblemente otros), y debe tener permiso " +"de lectura para el usuario de GDM. Vea la opción <filename>Logotipo</" +"filename> en la sección de referencia inferior para los detalles." -#: ../C/gdm.xml:365 (title) +#: ../C/gdm.xml:367 (title) msgid "The Themed Greeter" msgstr "El interfaz con temas" -#: ../C/gdm.xml:367 (para) +#: ../C/gdm.xml:369 (para) msgid "" "The Themed Greeter is a greeter interface that takes up the whole screen and " "is very themable. Themes can be selected and new themes can be installed by " @@ -579,7 +601,7 @@ msgid "" "is controlled by the daemon using the same simple protocol." msgstr "" -#: ../C/gdm.xml:377 (para) +#: ../C/gdm.xml:379 (para) msgid "" "The look and feel of this greeter is really controlled by the theme and so " "the user interface elements that are present may be different. The only " @@ -590,7 +612,7 @@ msgid "" "an XDMCP chooser." msgstr "" -#: ../C/gdm.xml:387 (para) +#: ../C/gdm.xml:389 (para) msgid "" "You can always get a menu of available actions by pressing the F10 key. This " "can be useful if the theme doesn't provide certain buttons when you really " @@ -600,11 +622,11 @@ msgstr "" "F10. Esto puede ser útil si el tema no proporciona ciertos botones cuando " "realmente quiere hacer alguna acción." -#: ../C/gdm.xml:395 (title) +#: ../C/gdm.xml:397 (title) msgid "The GDM Face Browser" msgstr "El visor de rostros de GDM" -#: ../C/gdm.xml:397 (para) +#: ../C/gdm.xml:399 (para) msgid "" "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 " @@ -619,7 +641,7 @@ msgstr "" "el Interfaz con Temas si usa un tema de GDM que incluya un tipo de elemento " "\"userlist\", tal como \"happygnome-list\"" -#: ../C/gdm.xml:407 (para) +#: ../C/gdm.xml:409 (para) msgid "" "By default, the face browser is disabled since revealing usernames on the " "login screen is not appropriate on many systems for security reasons and " @@ -635,7 +657,7 @@ msgstr "" "command>. Esta característica es más práctica de usar en un sistema con un " "número pequeño de usuarios." -#: ../C/gdm.xml:416 (para) +#: ../C/gdm.xml:418 (para) msgid "" "The icons used by GDM can be installed globally by the sysadmin or can be " "located in the users' home directories. If installed globally they should be " @@ -658,7 +680,7 @@ msgstr "" "embargo, el demonio, proximiza las fotografías de los usuarios al interfaz y " "debido a esto no tienen que ser leíbles por el usuario GDM sino por el root." -#: ../C/gdm.xml:429 (para) +#: ../C/gdm.xml:431 (para) msgid "" "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 " @@ -679,7 +701,7 @@ msgstr "" "estén escaladas de forma adecuada así que un usuario puede crear su archivo " "<filename>~/.face</filename> a mano." -#: ../C/gdm.xml:441 (para) +#: ../C/gdm.xml:443 (para) msgid "" "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 " @@ -696,7 +718,7 @@ msgstr "" "photo</filename> los cuales están obsoletos y se soportan por compatibilidad " "hacia atrás." -#: ../C/gdm.xml:452 (para) +#: ../C/gdm.xml:454 (para) msgid "" "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 " @@ -709,7 +731,7 @@ msgstr "" "configuración <filename>DefaultFace</filename> como resguardo, normalmente /" "usr/share/pixmaps/nobody.png." -#: ../C/gdm.xml:460 (para) +#: ../C/gdm.xml:462 (para) msgid "" "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 " @@ -732,12 +754,12 @@ msgstr "" "opción <filename>Include</filename> de <filename>gdm.conf</filename> puede " "usarse para especificar un conjunto de usuarios que deberían aparecer en el " "visor de rostros. Mientras los usuarios a incluir tengan un tamaño " -"razonable, no debería haber ningún problema con GDM siendo incapaz de acceder " -"a las imágenes de rostros. Para evitar estos problemas, se recomienda situar " -"las imágenes de rostros en el directorio especificado por la opción de " -"configuración <filename>GlobalFaceDir</filename>." +"razonable, no debería haber ningún problema con GDM siendo incapaz de " +"acceder a las imágenes de rostros. Para evitar estos problemas, se " +"recomienda situar las imágenes de rostros en el directorio especificado por " +"la opción de configuración <filename>GlobalFaceDir</filename>." -#: ../C/gdm.xml:476 (para) +#: ../C/gdm.xml:478 (para) msgid "" "To control the users who get displayed in the face browser, there are a " "number of configuration options that can be used. If the " @@ -754,7 +776,7 @@ msgid "" "than a small number of users over the network.." msgstr "" -#: ../C/gdm.xml:493 (para) +#: ../C/gdm.xml:495 (para) msgid "" "When the browser is turned on, valid usernames on the computer are " "inherently exposed to a potential intruder. This may be a bad idea if you " @@ -762,11 +784,11 @@ msgid "" "XDMCP (turned off by default)." msgstr "" -#: ../C/gdm.xml:502 (title) +#: ../C/gdm.xml:504 (title) msgid "Logging" msgstr "Registro de actividad" -#: ../C/gdm.xml:504 (para) +#: ../C/gdm.xml:506 (para) msgid "" "GDM itself will use syslog to log errors or status. It can also log " "debugging information, which can be useful for tracking down problems if GDM " @@ -777,7 +799,7 @@ msgstr "" "encontrar problemas si GDM no funciona apropiadamente. Esto puede activarse " "en el archivo de configuración." -#: ../C/gdm.xml:511 (para) +#: ../C/gdm.xml:513 (para) msgid "" "Output from the various X servers is stored in the GDM log directory, which " "is configurable, but is usually <filename><var>/log/gdm/</filename>. " @@ -787,10 +809,16 @@ msgid "" "be rotated as new sessions on that display are started. You can use these " "logs to view what the X server said when it started up." msgstr "" -"La salida de varios servidores X está almacenada en el directorio de registros de GDM, el cual es configurable, pero normalmente es <filename>/var/log/gdm/</filename>. La salida desde la sesión puede encontrarse en un archivo llamado <filename><display>.log</filename>. Cuatro archivos más antiguos se almacenan también con " -" <filename>.1</filename> a <filename>.4</filename> anexado. Éstos se rotarán a medida que se inicien nuevas sesiones en esa pantalla. Puede usar estos registros para ver que decía el servidor X cuando arrancaba." +"La salida de varios servidores X está almacenada en el directorio de " +"registros de GDM, el cual es configurable, pero normalmente es <filename>/" +"var/log/gdm/</filename>. La salida desde la sesión puede encontrarse en un " +"archivo llamado <filename><display>.log</filename>. Cuatro archivos " +"más antiguos se almacenan también con <filename>.1</filename> a " +"<filename>.4</filename> anexado. Éstos se rotarán a medida que se inicien " +"nuevas sesiones en esa pantalla. Puede usar estos registros para ver que " +"decía el servidor X cuando arrancaba." -#: ../C/gdm.xml:523 (para) +#: ../C/gdm.xml:525 (para) msgid "" "The output from the user session is redirected to <filename>~/.xsession-" "errors</filename> before even the <filename>PreSession</filename> script is " @@ -800,9 +828,17 @@ msgid "" "this file in a dialog before returning to the login screen. This way the " "user can view the session errors from the last session and correct the " "problem this way." -msgstr "La salida de la sesión de usuario está redirigida a <filename>~/.xsession-errors</filename> incluso antes de se inicie el script <filename>PreSession</filename>. Así que no es realmente necesario redirigir esto otra vez en el script de configuración de la sesión. Tal como se hace normalmente, si la sesión del usuario duró menos de 10 segundos, GDM asume que la sesión reventó y permite al usuario ver este archivo en un diálogo antes de volver a la pantalla de entrada. De esta manera el usuario puede ver los errores de la última sesión y corregir el problema." +msgstr "" +"La salida de la sesión de usuario está redirigida a <filename>~/.xsession-" +"errors</filename> incluso antes de se inicie el script <filename>PreSession</" +"filename>. Así que no es realmente necesario redirigir esto otra vez en el " +"script de configuración de la sesión. Tal como se hace normalmente, si la " +"sesión del usuario duró menos de 10 segundos, GDM asume que la sesión " +"reventó y permite al usuario ver este archivo en un diálogo antes de volver " +"a la pantalla de entrada. De esta manera el usuario puede ver los errores de " +"la última sesión y corregir el problema." -#: ../C/gdm.xml:535 (para) +#: ../C/gdm.xml:537 (para) msgid "" "You can suppress the 10 second warning by returning code 66 from the " "<filename>Xsession</filename>script or from your session binary (the default " @@ -811,9 +847,16 @@ msgid "" "to return less then 10 seconds later, or if you setup the session to already " "display some error message and the GDM message would be confusing and " "redundant." -msgstr "Puede suprimir la advertencia de los 10 segundos devolviendo un código 66 desde el script <filename>Xsession</filename> desde el binario de la sesión (el script <filename>Xsession</filename> predeterminado propaga esos códigos hacia atrás). Esto es útil si tiene alguna clase de inicios de sesión especiales para los que no es un error retornar menos de esos 10 segundos después, o si configura la sesión para mostrar algún mensaje de error y el mensaje de GDM podría ser confuso y redundante." +msgstr "" +"Puede suprimir la advertencia de los 10 segundos devolviendo un código 66 " +"desde el script <filename>Xsession</filename> desde el binario de la sesión " +"(el script <filename>Xsession</filename> predeterminado propaga esos códigos " +"hacia atrás). Esto es útil si tiene alguna clase de inicios de sesión " +"especiales para los que no es un error retornar menos de esos 10 segundos " +"después, o si configura la sesión para mostrar algún mensaje de error y el " +"mensaje de GDM podría ser confuso y redundante." -#: ../C/gdm.xml:545 (para) +#: ../C/gdm.xml:547 (para) msgid "" "The session output is piped through the GDM daemon and so the <filename>~/." "xsession-errors</filename> file is capped at about 200 kilobytes by GDM to " @@ -825,10 +868,18 @@ msgid "" "and stops writing the file, which would lead to killed sessions if the file " "was redirected in the old fashioned way from the script." msgstr "" -"La salida de la sesión se encauza a través del demonio gdm y así el archivo <filename>~/." -"xsession-errors</filename> está capado a cerca de 200 Kbytes por GDM para prevenir una posible denegación de servicio en la sesión. Una aplicación podría quizás leer algunos datos erróneos, imprimir advertencias o errores en stderr o stdout. Esto podría quizás llenar el directorio personal del usuario quien tendría que cerrar sesión e iniciar sesión de nuevo para limpiar esto. Esto podría ser especialmente duro si hay cuotas puestas. GDM además atrapa correctamente la señal XFSZ y para de escribir el archivo, lo que podría conducir a sesiones matadas si el archivo fue redirigido en la forma antigua desde el script." +"La salida de la sesión se encauza a través del demonio gdm y así el archivo " +"<filename>~/.xsession-errors</filename> está capado a cerca de 200 Kbytes " +"por GDM para prevenir una posible denegación de servicio en la sesión. Una " +"aplicación podría quizás leer algunos datos erróneos, imprimir advertencias " +"o errores en stderr o stdout. Esto podría quizás llenar el directorio " +"personal del usuario quien tendría que cerrar sesión e iniciar sesión de " +"nuevo para limpiar esto. Esto podría ser especialmente duro si hay cuotas " +"puestas. GDM además atrapa correctamente la señal XFSZ y para de escribir el " +"archivo, lo que podría conducir a sesiones matadas si el archivo fue " +"redirigido en la forma antigua desde el script." -#: ../C/gdm.xml:558 (para) +#: ../C/gdm.xml:560 (para) msgid "" "Note that some distributors seem to override the <filename>~/.xsession-" "errors</filename> redirection and do it themselves in their own Xsession " @@ -840,34 +891,45 @@ msgid "" "<filename>BaseXsession</filename> configuration key for more information, " "especially on how to handle multiple display managers using the same script." msgstr "" -"Note que algunos distribuidores parecen ignorar la redirección de <filename>~/.xsession-" -"errors</filename> y la hacen ellos mismos en su propio script Xsession (establecido por la " -"clave de configuración <filename>BaseXsession</filename>) que significa que GDM no será capaz de " -"atrapar la salida y cubrir este archivo. Puede también perder datos de salida del script <filename>PreSession</filename> lo " -"que puede hacer la depuración mucho más complicada ya que quizás la salida de lo que está equivocado no se imprimirá. Vea la " -"descripción de la clave de configuración <filename>BaseXsession</filename> para más información, especialmente acerca de cómo " -"manejar múltiples gestores de entrada usando el mismo script." - -#: ../C/gdm.xml:572 (para) +"Note que algunos distribuidores parecen ignorar la redirección de " +"<filename>~/.xsession-errors</filename> y la hacen ellos mismos en su propio " +"script Xsession (establecido por la clave de configuración " +"<filename>BaseXsession</filename>) que significa que GDM no será capaz de " +"atrapar la salida y cubrir este archivo. Puede también perder datos de " +"salida del script <filename>PreSession</filename> lo que puede hacer la " +"depuración mucho más complicada ya que quizás la salida de lo que está " +"equivocado no se imprimirá. Vea la descripción de la clave de configuración " +"<filename>BaseXsession</filename> para más información, especialmente acerca " +"de cómo manejar múltiples gestores de entrada usando el mismo script." + +#: ../C/gdm.xml:574 (para) msgid "" "Note that if the session is a failsafe session, or if GDM can't open this " "file for some reason, then a fallback file will be created in the <filename>/" "tmp</filename> directory named <filename>/tmp/xses-<user>.XXXXXX</" "filename> where the <filename>XXXXXX</filename> are some random characters." -msgstr "Note que si la sesión es una sesión a prueba de fallos, o si GDM no puede abrir este archivo por alguna razón, entonces se creará un archivo de apoyo en el directorio <filename>/tmp</filename> llamado <filename>/tmp/xses-<user>.XXXXXX</filename> donde <filename>XXXXXX</filename> son caracteres aleatorios." +msgstr "" +"Note que si la sesión es una sesión a prueba de fallos, o si GDM no puede " +"abrir este archivo por alguna razón, entonces se creará un archivo de apoyo " +"en el directorio <filename>/tmp</filename> llamado <filename>/tmp/xses-<" +"user>.XXXXXX</filename> donde <filename>XXXXXX</filename> son caracteres " +"aleatorios." -#: ../C/gdm.xml:580 (para) +#: ../C/gdm.xml:582 (para) msgid "" "If you run a system with quotas set, it would be good to delete the " "<filename>~/.xsession-errors</filename> in the <filename>PostSession</" "filename> script. Such that this log file doesn't unnecessarily stay around." -msgstr "Si ejecuta un sistema sin cuotas activadas, será bueno borrar el archivo <filename>~/.xsession-errors</filename> en el script <filename>PostSession</filename>. Así este archivo de registro no está por medio innecesariamente." +msgstr "" +"Si ejecuta un sistema sin cuotas activadas, será bueno borrar el archivo " +"<filename>~/.xsession-errors</filename> en el script <filename>PostSession</" +"filename>. Así este archivo de registro no está por medio innecesariamente." -#: ../C/gdm.xml:589 (title) +#: ../C/gdm.xml:591 (title) msgid "Accessing Files" msgstr "Acceso a los archivos" -#: ../C/gdm.xml:591 (para) +#: ../C/gdm.xml:593 (para) msgid "" "In general GDM is very reluctant regarding reading/writing of user files " "(such as the ~/.dmrc, ~/.face, ~/.xsession-errors, and ~/.Xauthority files). " @@ -875,18 +937,30 @@ msgid "" "and devices are ignored. The value of the <filename>RelaxPermissions</" "filename> parameter determines whether GDM should accept files writable by " "the user's group or others. These are ignored by default." -msgstr "En general GDM es muy quisquilloso respecto a la lectura/escritura de archivos de usuario (como ~/.dmrc, ~/.face, ~/.xsession-errors, y ~/.Xauthority ). Por ejemplo se niega a acceder a cualquier cosa excepto archivos regulares. Enlaces, sockets y dispositivos se ignoran. El valor del parámetro <filename>RelaxPermissions</filename> determina si GDM debería aceptar archivos escribibles por el grupo del usuario u otros. Éstos se ignoran por omisión." +msgstr "" +"En general GDM es muy quisquilloso respecto a la lectura/escritura de " +"archivos de usuario (como ~/.dmrc, ~/.face, ~/.xsession-errors, y ~/." +"Xauthority ). Por ejemplo se niega a acceder a cualquier cosa excepto " +"archivos regulares. Enlaces, sockets y dispositivos se ignoran. El valor del " +"parámetro <filename>RelaxPermissions</filename> determina si GDM debería " +"aceptar archivos escribibles por el grupo del usuario u otros. Éstos se " +"ignoran por omisión." -#: ../C/gdm.xml:601 (para) +#: ../C/gdm.xml:603 (para) msgid "" "All operations on user files are done with the effective user id of the " "user. If the sanity check fails on the user's <filename>.Xauthority</" "filename> file, a fallback cookie is created in the directory specified by " "the <filename>UserAuthFBDir</filename> configuration setting (/tmp by " "default)." -msgstr "Todas las operaciones en los archivos del usuario se realizan con el id de usuario efectivo del usuario. Si el control de sanidad falla en el archivo <filename>.Xauthority</filename> del usuario, se crea una cookie de recuperación de errores en el directorio especificado por la opción de configuración <filename>UserAuthFBDir</filename> (/tmp por omisión)." +msgstr "" +"Todas las operaciones en los archivos del usuario se realizan con el id de " +"usuario efectivo del usuario. Si el control de sanidad falla en el archivo " +"<filename>.Xauthority</filename> del usuario, se crea una cookie de " +"recuperación de errores en el directorio especificado por la opción de " +"configuración <filename>UserAuthFBDir</filename> (/tmp por omisión)." -#: ../C/gdm.xml:609 (para) +#: ../C/gdm.xml:611 (para) msgid "" "Finally, the sysadmin can specify the maximum file size GDM should accept, " "and, if the face browser is enabled, a tunable maximum icon size is also " @@ -901,6793 +975,6108 @@ msgstr "" "Mirar iconos en directorios personales, escalarlos y renderizarlos puede " "llevar mucho tiempo." -#: ../C/gdm.xml:621 (title) -msgid "Security" -msgstr "Seguridad" - -#: ../C/gdm.xml:624 (title) -msgid "The GDM User" -msgstr "El usuario GDM" - -#: ../C/gdm.xml:626 (para) -msgid "" -"The GDM daemon normally runs as root, as does the slave. However GDM should " -"also have a dedicated user id and a group id which it uses for its graphical " -"interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</" -"command>. You can choose the name of this user and group in the <filename>" -"[daemon]</filename> section of the configuration file." -msgstr "" - -#: ../C/gdm.xml:635 (para) -msgid "" -"The GDM user, and group, which are normally just <command>gdm</command> " -"should not be user or group of any particular privilege. The reason for " -"using them is to have the user interface run as a user without privileges so " -"that in the unlikely case that someone finds a weakness in the GUI, they " -"cannot access root on the computer." -msgstr "El usuario y el grupo GDM, que son normalmente <command>gdm</command> no deberían tener ningún privilegio. La razón para usarlos es tener el interfaz de usuario ejecutándose como un usuario sin privilegios para que en el improbable caso de que alguien encuentre una debilidad en el IGU, no puedan acceder como root a la computadora." - -#: ../C/gdm.xml:644 (para) -msgid "" -"It should however be noted that the GDM user and group have some privileges " -"that make them somewhat dangerous. For one they have access to the X server " -"authorization directory (the <filename>ServAuthDir</filename>), which " -"contains all the X server authorization files and other private information. " -"This means 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>." -msgstr "" - -#: ../C/gdm.xml:658 (title) -msgid "X Server Authentication Scheme" -msgstr "Esquema de autenticación del servidor X" +#: ../C/gdm.xml:622 (title) +#, fuzzy +msgid "GDM Performance" +msgstr "Comandos de usuario de GDM" -#: ../C/gdm.xml:660 (para) -msgid "" -"The X server authorization directory (the <filename>ServAuthDir</filename>) " +#: ../C/gdm.xml:624 (para) +msgid "" +"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." +msgstr "" + +#: ../C/gdm.xml:632 (para) +msgid "" +"To use this feature, configure GDM with the --with-prefetch option. This " +"will cause GDM to install the gdmprefetch program to the EXPANDED_LIBEXEC " +"directory, install the gdmprefetchlist to the <etc>/gdm directory, and " +"set the PreFetchProgram configuration variable so that the gdmprefetch " +"program is called with the default gdmprefetchlist file. The default " +"gdmprefetchlist 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." +msgstr "" + +#: ../C/gdm.xml:621 (sect2) +msgid "" +"<placeholder-1/><placeholder-2/><placeholder-3/> Security The GDM User The " +"GDM daemon normally runs as root, as does the slave. However GDM should also " +"have a dedicated user id and a group id which it uses for its graphical " +"interfaces such as gdmgreeter and gdmlogin. You can choose the name of this " +"user and group in the [daemon] section of the configuration file. The GDM " +"user, and group, which are normally just gdm should not be user or group of " +"any particular privilege. The reason for using them is to have the user " +"interface run as a user without privileges so that in the unlikely case that " +"someone finds a weakness in the GUI, they cannot access root on the " +"computer. It should however be noted that the GDM user and group have some " +"privileges that make them somewhat dangerous. For one they have access to " +"the X server authorization directory (the ServAuthDir), which contains all " +"the X server authorization files and other private information. This means " +"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 nobody. X Server " +"Authentication Scheme The X server authorization directory (the ServAuthDir) " "is used for a host of random internal data in addition to the X server " "authorization files, and the naming is really a relic of history. GDM daemon " -"enforces this directory to be owned by <filename>root.gdm</filename> with " -"the permissions of 1770. This way, only root and the GDM group have write " -"access to this directory, but the GDM group cannot remove the root owned " -"files from this directory, such as the X server authorization files." -msgstr "" - -#: ../C/gdm.xml:672 (para) -msgid "" -"GDM by default doesn't trust the X server authorization directory and treats " -"it in the same way as the temporary directory with respect to creating " -"files. This way someone breaking the GDM user cannot mount attacks by " -"creating links in this directory. Similarly the X server log directory is " -"treated safely, but that directory should really be owned and writable only " -"by root." -msgstr "" - -#: ../C/gdm.xml:681 (para) -msgid "" -"GDM only supports the MIT-MAGIC-COOKIE-1 X server authentication scheme. " -"Normally little is gained from the other schemes, and no effort has been " -"made to implement them so far. Be especially careful about using XDMCP " -"because the X server authentication cookie goes over the wire as clear text. " -"If snooping is possible, then an attacker could simply snoop your " -"authentication password as you log in, regardless of the authentication " -"scheme being used. If snooping is possible and undesirable, then you should " -"use ssh for tunneling an X connection rather then using XDMCP. You could " -"think of XDMCP as a sort of graphical telnet, having the same security " -"issues." -msgstr "" - -#: ../C/gdm.xml:694 (para) -msgid "" -"On the upside, GDM's random number generation is very conservative and GDM " -"goes to extraordinary measures to truly get a 128 bit random number, using " -"hardware random number generators (if available), plus the current time (in " +"enforces this directory to be owned by root.gdm with the permissions of " +"1770. This way, only root and the GDM group have write access to this " +"directory, but the GDM group cannot remove the root owned files from this " +"directory, such as the X server authorization files. GDM by default doesn't " +"trust the X server authorization directory and treats it in the same way as " +"the temporary directory with respect to creating files. This way someone " +"breaking the GDM user cannot mount attacks by creating links in this " +"directory. Similarly the X server log directory is treated safely, but that " +"directory should really be owned and writable only by root. GDM only " +"supports the MIT-MAGIC-COOKIE-1 X server authentication scheme. Normally " +"little is gained from the other schemes, and no effort has been made to " +"implement them so far. Be especially careful about using XDMCP because the X " +"server authentication cookie goes over the wire as clear text. If snooping " +"is possible, then an attacker could simply snoop your authentication " +"password as you log in, regardless of the authentication scheme being used. " +"If snooping is possible and undesirable, then you should use ssh for " +"tunneling an X connection rather then using XDMCP. You could think of XDMCP " +"as a sort of graphical telnet, having the same security issues. On the " +"upside, GDM's random number generation is very conservative and GDM goes to " +"extraordinary measures to truly get a 128 bit random number, using hardware " +"random number generators (if available), plus the current time (in " "microsecond precision), a 20 byte array of pseudorandom numbers, process " -"pid's, and other random information (possibly using <filename>/dev/audio</" -"filename> or <filename>/dev/mem</filename> if hardware random generators are " -"not available) to create a large buffer and then run MD5 digest on this. " -"Obviously, all this work is wasted if you send this cookie over an open " -"network or store it on an NFS directory (see <filename>UserAuthDir</" -"filename> configuration key). So be careful about where you use remote X " -"display." -msgstr "" - -#: ../C/gdm.xml:711 (title) -msgid "Firewall Security" -msgstr "Seguridad con cortafuegos" - -#: ../C/gdm.xml:713 (para) -msgid "" -"Even though GDM tries to outsmart potential attackers trying to take " -"advantage of XDMCP, it is still advised that you block the XDMCP port " -"(normally UDP port 177) on your firewall unless you really need it. GDM " -"guards against DoS (Denial of Service) attacks, but the X protocol is still " -"inherently insecure and should only be used in controlled environments. Also " -"each remote connection takes up lots of resources, so it is much easier to " -"DoS via XDMCP then a webserver." -msgstr "" - -#: ../C/gdm.xml:723 (para) -msgid "" -"It is also wise to block all of the X Server ports. These are TCP ports 6000 " -"+ the display number of course) on your firewall. Note that GDM will use " -"display numbers 20 and higher for flexible on-demand servers." -msgstr "" - -#: ../C/gdm.xml:730 (para) -msgid "" -"X is not a very safe protocol for leaving on the net, and XDMCP is even less " -"safe." -msgstr "" - -#: ../C/gdm.xml:737 (title) -msgid "GDM Security With NFS" -msgstr "Seguridad de GDM con NFS" - -#: ../C/gdm.xml:739 (para) -msgid "" -"Note that NFS traffic really goes \"over the wire\" and thus can be snooped. " -"When accessing the user's X authorization file (~/.Xauthority), GDM will try " -"to open the file for reading as root. If it fails, GDM will conclude that it " -"is on an NFS mount and it will automatically use <filename>UserAuthFBDir</" -"filename>, which by default is set to <filename>/tmp</filename>. This " -"behavior can be changed by setting the <filename>NeverPlaceCookiesOnNFS</" -"filename> in the <filename>[security]</filename> section to false." -msgstr "" - -#: ../C/gdm.xml:752 (title) -msgid "XDMCP Security" -msgstr "Seguridad de XDMCP" - -#: ../C/gdm.xml:754 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:760 (para) -msgid "" -"XDMCP is primarily useful for running thin clients such as in terminal labs. " -"Those thin clients will only ever need the network to access the server, and " -"so it seems like the best security policy to have those thin clients on a " -"separate network that cannot be accessed by the outside world, and can only " -"connect to the server. The only point from which you need to access outside " -"is the server." -msgstr "" - -#: ../C/gdm.xml:769 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:778 (title) -msgid "XDMCP Access Control" -msgstr "Control de acceso XDMCP" - -#: ../C/gdm.xml:780 (para) -msgid "" -"XDMCP access control is done using TCP wrappers. It is possible to compile " -"GDM without TCP wrappers however, so you should test your configuration and " -"verify that they work." -msgstr "El control de acceso XDMCP se realiza por medio de TCP wrappers. Es posible compilar GDM sin TCP wrappers sin embargo debería probar su configuración y verificar que funciona." - -#: ../C/gdm.xml:786 (para) -msgid "" -"You should use the daemon name <command>gdm</command> in the <filename><" -"etc>/hosts.allow</filename> and <filename><etc>hosts.deny</" -"filename> files. For example to deny computers from <filename>.evil.domain</" -"filename> from logging in, then add" -msgstr "" -"Debería usar el nombre del demonio <command>gdm</command> en el archivo " -"<filename><etc>/hosts.allow</filename> y en el archivo <filename><" -"etc>hosts.deny</filename>. Por ejemplo para denegar la entrada a equipos " -"de <filename>.evil.domain</filename> , añada" - -#: ../C/gdm.xml:793 (screen) -#, no-wrap -msgid "gdm: .evil.domain" -msgstr "gdm: .dominio.maligno" - -#: ../C/gdm.xml:794 (para) -msgid "to <filename><etc>/hosts.deny</filename>. You may also need to add" -msgstr "a <filename><etc>/hosts.deny</filename>. También necesitará añadir " - -#: ../C/gdm.xml:798 (screen) -#, no-wrap -msgid "gdm: .your.domain" -msgstr "gdm: .su.dominio" - -#: ../C/gdm.xml:799 (para) -msgid "" -"to your <filename><etc>/hosts.allow</filename> if you normally " -"disallow all services from all hosts. See the <ulink type=\"help\" url=\"man:" -"hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" -"a su <filename><etc>/hosts.allow</filename> si normalmente no permite " -"todos los servicios desde todos los equipos. Vea la página del manual <ulink " -"type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> para más " -"detalles." - -#: ../C/gdm.xml:809 (title) -msgid "Configuration" -msgstr "Configuración" - -#: ../C/gdm.xml:811 (para) -msgid "" -"This section will cover the configuration of GDM and the format of the GDM " -"configuration files. You can use the <command>gdmsetup</command> command to " -"configure GDM, but the configuration application does not let you configure " -"every aspect of GDM. The information in this section explains how to further " -"configure GDM." -msgstr "Esta sección cubrirá la configuración de GDM y el formato de los archivos de configuración de GDM. Puede usar el comando <command>gdmsetup</command> para configurar GDM, pero la aplicación de configuración no le deja configurar cada aspecto de GDM. La información de esta sección le explica en profundidad cómo configurar GDM." - -#: ../C/gdm.xml:819 (para) -msgid "" -"The configuration files (especially the <filename>gdm.conf</filename> and " -"<filename>gdm.conf-custom</filename> files) contains useful comments and " -"examples, so read this for more information about changing your setup." -msgstr "Los archivos de configuración (especialmente <filename>gdm.conf</filename> y <filename>gdm.conf-custom</filename>) contienen comentarios útiles y ejemplos, así que léalos para más información acerca de cambiar su configuración." - -#: ../C/gdm.xml:826 (para) -msgid "" -"Some keys in the configuration file as shipped are commented out while " -"others are set. This is done so that defaults can be easily changed in the " -"future for some keys. GDM considers lines that start with the \"#\" " -"character a comment, and these lines will be ignored by GDM." -msgstr "Algunas claves en el archivo de configuración se entregan comentadas mientras que otras están activadas. Esto se hace para que los predeterminados para algunas claves puedan cambiarse fácilmente en el futuro. GDM considera que las líneas que comienzan con el carácter «#» un comentario, y estas líneas se ignorarán." - -#: ../C/gdm.xml:834 (para) -msgid "" -"The <filename>gdm.conf</filename> file contains the default configuration " -"choices for GDM, and should not be modified by the user. The <filename>gdm." -"conf-custom</filename> file is where users may specify their custom " -"configuration choices. Configuration options specified in the <filename>gdm." -"conf-custom</filename> file override the values in the main <filename>gdm." -"conf</filename> file. Running the <command>gdmsetup</command> command will " -"cause the <filename>gdm.conf-custom</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>gdm.conf</filename> file, so if using an older version of GDM just " -"edit that file directly." -msgstr "EL archivo <filename>gdm.conf</filename> contiene las opciones de configuración predeterminadas para GDM, y no debería ser modificado por el usuario. El archivo <filename>gdm.conf-custom</filename> es donde los usuarios pueden especificar sus opciones de configuración personalizadas. Las opciones de configuración especificadas en el archivo <filename>gdm.conf-custom</filename> toman precedencia sobre los valores en el archivo principal <filename>gdm.conf</filename>. Ejecutar el comando <command>gdmsetup</command> hará que el archivo <filename>gdm.conf-custom</filename> se modifique con las opciones de configuración del usuario y hará que cualquier programa del IGU de GDM se actualice automáticamente. Anteriormente a la versión 2.13.0.4 GDM sólo soportaba el archivo <filename>gdm.conf</filename>, así que si está usando una versión más antigua de GDM tan sólo edite ese archivo directamente." - -#: ../C/gdm.xml:849 (para) -msgid "" -"GDM may be configured to support system-wide configuration if built with the " -"<command>--with-configdir</command> option. This allows the gdm.conf file to " -"be installed to a directory that can be mounted across multiple-systems. The " -"GDM --config option may also be used to specify the configuration file " -"location. The GDM2 daemon must be restarted to change the configuration file " -"being used." -msgstr "GDM puede configurarse para soportar configuración para todo el sistema si se compila con la opción <command>--with-configdir</command>. Esto permite instalar el archivo gdm.conf en un directorio que pueda montarse a través de múltiples sistemas. La opción --config también podría usarse para especificar la ubicación del archivo de configuración. El demonio GDM2 debe reiniciarse para cambiar el archivo de configuración en uso." - -#: ../C/gdm.xml:859 (para) -msgid "" -"<filename>factory-gdm.conf</filename> is the configuration file as shipped " -"with the daemon. This can be useful if you wish to revert to the default " -"configuration." -msgstr "<filename>factory-gdm.conf</filename> es el archivo de configuración tal como se empaqueta con el demonio. Esto puede ser útil si desea volver a la configuración predeterminada." - -#: ../C/gdm.xml:865 (para) -msgid "" -"The other GDM configuration files are located, by default, in the " -"<filename><etc>/gdm/</filename> folder or its subdirectories. However, " -"the location of all configuration files can be defined in the <filename>gdm." -"conf</filename> file, so the sysadmin may choose to locate these files in " -"any location." -msgstr "Los demás archivos de configuración de GDM se encuentran, por omisión, en la carpeta <filename><etc>/gdm/</filename> o sus subdirectorios. sin embargo, la ubicación de todos los archivos de configuración pueden definirse en el archivo <filename>gdm.conf</filename>, así que el administrador del sistema puede elegir situar estos archivos en cualquier lugar." - -#: ../C/gdm.xml:873 (para) -msgid "This is a listing of the config directory contents:" -msgstr "Esta es una lista de los contenidos del directorio de configuración:" - -#: ../C/gdm.xml:877 (screen) -#, no-wrap -msgid "" -"\n" -"locale.alias\n" -"Xsession\n" -"XKeepsCrashing\n" -"modules/\n" -"Init/\n" -"PostLogin/\n" -"PreSession/\n" -"PostSession/\n" -" " -msgstr "" - -#: ../C/gdm.xml:888 (para) -msgid "" -"<filename>locale.alias</filename> is a file which looks much like the system " -"locale alias but in fact it is not the same. These are the languages that " -"are available on your system. All the languages are still tested to see if " -"they actually exist before presenting them to the user." -msgstr "" -"<filename>locale.alias</filename> es un archivo que se parece mucho al archivo de alias regionales del sistema " -"pero no es el mismo. Éstos son los idiomas que están disponibles en su sitema. Todos los idiomas además se prueban para " -"ver si actualmente existen antes de presentárselos al usuario." - -#: ../C/gdm.xml:896 (para) -msgid "" -"<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." -msgstr "" -"<filename>Xsession</filename> es un script que configura una sesión de usuario y " -"después ejecuta la selección de sesión del usuario. Note que el script de sesión se inicia típicamente por el " -"archivo <filename>desktop</filename> asociado con la sesión que el usuario a escogido. " -"Algunas sesiones quizá inicien la sesión del usuario por medio de un mecanismo diferente " -"que el script <filename>Xsession</filename> así que marque el <filename>desktop</filename> apropiado antes de " -"asumir que el problema de inicio está causado por este archivo." - -#: ../C/gdm.xml:907 (para) -msgid "" -"<filename>XKeepsCrashing</filename> is a script which gets run when the X " -"server keeps crashing and we cannot recover. The shipped default script will " -"work with most Linux distributions and can run the X configuration " -"application provided the person on the console knows the root password." -msgstr "" -"<filename>XKeepsCrashing</filename> es un script que se ejecuta cuando el servidor X " -"continúa colgándose y no se puede recuperar. El script predeterminado incluido funcionará con " -"la mayoría de las distribuciones de Linux y puede ejecutar la aplicación de configuración de X " -"siempre que la persona en la consola conozca la contraseña de root." - -#: ../C/gdm.xml:915 (para) -msgid "" -"Accessibility modules are configured in the <filename>modules/</filename> " -"subdirectory, and are a separate topic. Read the default files provided, " -"they have adequate documentation. Again normally the default install is " -"given in the files with <filename>factory</filename> in their name, and " -"those files are not read, they are just there for you so you can always " -"revert to default config." -msgstr "" - -#: ../C/gdm.xml:924 (para) -msgid "" -"Files describing available GDM session follow the freedesktop.org desktop " -"file specification and are <filename>.desktop</filename>-style files are " -"installed to <filename><etc>/X11/sessions/</filename>. This directory " -"is also read by the KDE desktop manager (KDM) for common configuration. Next " -"the directory <filename><share>/gdm/BuiltInSessions/</filename> is " -"read for GDM specific built-in sessions (KDM hardcodes these at time of this " -"writing). Lastly the default setup will also read <filename><share>/" -"xsessions/</filename> (which should be <filename>/usr/share/xsessions/</" -"filename> if you really wish to cooperate with KDM) where desktop packages " -"can install their session files. The directories under the <filename><" -"etc></filename> should be reserved for configuration. The desktop file " +"pid's, and other random information (possibly using /dev/audio or /dev/mem " +"if hardware random generators are not available) to create a large buffer " +"and then run MD5 digest on this. Obviously, all this work is wasted if you " +"send this cookie over an open network or store it on an NFS directory (see " +"UserAuthDir configuration key). So be careful about where you use remote X " +"display. Firewall Security Even though GDM tries to outsmart potential " +"attackers trying to take advantage of XDMCP, it is still advised that you " +"block the XDMCP port (normally UDP port 177) on your firewall unless you " +"really need it. GDM guards against DoS (Denial of Service) attacks, but the " +"X protocol is still inherently insecure and should only be used in " +"controlled environments. Also each remote connection takes up lots of " +"resources, so it is much easier to DoS via XDMCP then a webserver. It is " +"also wise to block all of the X Server ports. These are TCP ports 6000 + the " +"display number of course) on your firewall. Note that GDM will use display " +"numbers 20 and higher for flexible on-demand servers. X is not a very safe " +"protocol for leaving on the net, and XDMCP is even less safe. GDM Security " +"With NFS Note that NFS traffic really goes over the wire and thus can be " +"snooped. When accessing the user's X authorization file (~/.Xauthority), GDM " +"will try to open the file for reading as root. If it fails, GDM will " +"conclude that it is on an NFS mount and it will automatically use " +"UserAuthFBDir, which by default is set to /tmp. This behavior can be changed " +"by setting the NeverPlaceCookiesOnNFS in the [security] section to false. " +"XDMCP Security 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. XDMCP is primarily useful for " +"running thin clients such as in terminal labs. Those thin clients will only " +"ever need the network to access the server, and so it seems like the best " +"security policy to have those thin clients on a separate network that cannot " +"be accessed by the outside world, and can only connect to the server. The " +"only point from which you need to access outside is the server. 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. XDMCP Access Control XDMCP " +"access control is done using TCP wrappers. It is possible to compile GDM " +"without TCP wrappers however, so you should test your configuration and " +"verify that they work. You should use the daemon name gdm in the etc/hosts." +"allow and etchosts.deny files. For example to deny computers from .evil." +"domain from logging in, then add gdm: .evil.domain to etc/hosts.deny. You " +"may also need to add gdm: .your.domain to your etc/hosts.allow if you " +"normally disallow all services from all hosts. See the hosts.allow(5) man " +"page for details. Configuration This section will cover the configuration of " +"GDM and the format of the GDM configuration files. You can use the gdmsetup " +"command to configure GDM, but the configuration application does not let you " +"configure every aspect of GDM. The information in this section explains how " +"to further configure GDM. The configuration files (especially the gdm.conf " +"and gdm.conf-custom files) contains useful comments and examples, so read " +"this for more information about changing your setup. Some keys in the " +"configuration file as shipped are commented out while others are set. This " +"is done so that defaults can be easily changed in the future for some keys. " +"GDM considers lines that start with the # character a comment, and these " +"lines will be ignored by GDM. The gdm.conf file contains the default " +"configuration choices for GDM, and should not be modified by the user. The " +"gdm.conf-custom file is where users may specify their custom configuration " +"choices. Configuration options specified in the gdm.conf-custom file " +"override the values in the main gdm.conf file. Running the gdmsetup command " +"will cause the gdm.conf-custom 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 gdm.conf file, so if " +"using an older version of GDM just edit that file directly. GDM may be " +"configured to support system-wide configuration if built with the --with-" +"configdir option. This allows the gdm.conf file to be installed to a " +"directory that can be mounted across multiple-systems. The GDM --config " +"option may also be used to specify the configuration file location. The GDM2 " +"daemon must be restarted to change the configuration file being used. " +"factory-gdm.conf is the configuration file as shipped with the daemon. This " +"can be useful if you wish to revert to the default configuration. The other " +"GDM configuration files are located, by default, in the etc/gdm/ folder or " +"its subdirectories. However, the location of all configuration files can be " +"defined in the gdm.conf file, so the sysadmin may choose to locate these " +"files in any location. This is a listing of the config directory contents: " +"locale.alias Xsession XKeepsCrashing modules/ Init/ PostLogin/ PreSession/ " +"PostSession/ locale.alias is a file which looks much like the system locale " +"alias but in fact it is not the same. These are the languages that are " +"available on your system. All the languages are still tested to see if they " +"actually exist before presenting them to the user. Xsession 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 desktop file " +"associated with the session the user has picked. Some sessions may start the " +"user's session via a different mechanism than the Xsession script, so please " +"check the appropriate desktop before assuming a session startup issue is " +"being caused by this file. XKeepsCrashing is a script which gets run when " +"the X server keeps crashing and we cannot recover. The shipped default " +"script will work with most Linux distributions and can run the X " +"configuration application provided the person on the console knows the root " +"password. Accessibility modules are configured in the modules/ subdirectory, " +"and are a separate topic. Read the default files provided, they have " +"adequate documentation. Again normally the default install is given in the " +"files with factory in their name, and those files are not read, they are " +"just there for you so you can always revert to default config. Files " +"describing available GDM session follow the freedesktop.org desktop file " +"specification and are .desktop-style files are installed to etc/X11/" +"sessions/. This directory is also read by the KDE desktop manager (KDM) for " +"common configuration. Next the directory share/gdm/BuiltInSessions/ is read " +"for GDM specific built-in sessions (KDM hardcodes these at time of this " +"writing). Lastly the default setup will also read share/xsessions/ (which " +"should be /usr/share/xsessions/ if you really wish to cooperate with KDM) " +"where desktop packages can install their session files. The directories " +"under the etc should be reserved for configuration. The desktop file " "specification approach makes it easy for package management systems to " "install window managers and different session types without requiring the " -"sysadmin to edit files. See the <filename>SessionDesktopDir</filename> " -"configuration key for changing the paths. It used to be that GDM stored its " -"built in sessions in <filename><etc>/dm/Sessions/</filename> but this " -"is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the " -"<filename><etc>/dm/Sessions/</filename> was being read." -msgstr "" - -#: ../C/gdm.xml:947 (para) -msgid "" -"A session can be disabled (if it was installed in <filename>/usr/share/" -"xsessions/</filename>) by adding an identically named <filename>.desktop</" -"filename> to one of the directories earlier in the path (likely " -"<filename><etc>/X11/sessions</filename>) and using " -"<filename>Hidden=true</filename> in that file." -msgstr "" - -#: ../C/gdm.xml:956 (title) -msgid "The Script Directories" -msgstr "Los directorios de scripts" - -#: ../C/gdm.xml:958 (para) -msgid "" -"In this section we will explain the <filename>Init</filename>, " -"<filename>PostLogin</filename>, <filename>PreSession</filename> and " -"<filename>PostSession</filename> directories as they are very similar." -msgstr "" -"En esta sección explicaremos los directorios <filename>Init</filename>, " -"<filename>PostLogin</filename>, <filename>PreSession</filename> y " -"<filename>PostSession</filename> ya que son muy similares." - -#: ../C/gdm.xml:964 (para) -msgid "" -"When the X server has been successfully started, GDM will try to run the " -"script called <filename>Init/<displayname></filename>. I.e. " -"<filename>Init/:0</filename> for the first local display. If this file is " -"not found, GDM will attempt to to run <filename>Init/<hostname></" -"filename>. I.e. <filename>Init/somehost</filename>. If this still is not " -"found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins or " -"<filename>Init/Flexi</filename> for all on demand flexible displays. If none " -"of the above were found, GDM will run <filename>Init/Default</filename>. The " -"script will be run as root and GDM blocks until it terminates. Use the " -"<filename>Init/*</filename> script for applications that are supposed to run " -"alongside with the GDM login window. xconsole for instance. Commands to set " -"the background etc. goes in this file too." -msgstr "" - -#: ../C/gdm.xml:982 (para) -msgid "" -"It is up to the sysadmin to decide whether clients started by the Init " -"script should be killed before starting the user session. This is controlled " -"with the <filename>KillInitClients</filename> configuration option." -msgstr "" - -#: ../C/gdm.xml:989 (para) -msgid "" -"When the user has been successfully authenticated GDM tries the scripts in " -"the <filename>PostLogin</filename> directory in the same manner as for the " -"<filename>Init</filename> directory. This is done before any session setup " -"is done, and so this would be the script where you might setup the home " -"directory if you need to (though you should use the <filename>pam_mount</" -"filename> module if you can for this). You have the <filename>$USER</" -"filename> and <filename>$DISPLAY</filename> environment variables set for " +"sysadmin to edit files. See the SessionDesktopDir configuration key for " +"changing the paths. It used to be that GDM stored its built in sessions in " +"etc/dm/Sessions/ but this is deprecated as of 2.5.90.0. Note that prior to " +"version 2.4.4.2 only the etc/dm/Sessions/ was being read. A session can be " +"disabled (if it was installed in /usr/share/xsessions/) by adding an " +"identically named .desktop to one of the directories earlier in the path " +"(likely etc/X11/sessions) and using Hidden=true in that file. The Script " +"Directories In this section we will explain the Init, PostLogin, PreSession " +"and PostSession directories as they are very similar. When the X server has " +"been successfully started, GDM will try to run the script called Init/" +"displayname. I.e. Init/:0 for the first local display. If this file is not " +"found, GDM will attempt to to run Init/hostname. I.e. Init/somehost. If this " +"still is not found, GDM will try Init/XDMCP for all XDMCP logins or Init/" +"Flexi for all on demand flexible displays. If none of the above were found, " +"GDM will run Init/Default. The script will be run as root and GDM blocks " +"until it terminates. Use the Init/* script for applications that are " +"supposed to run alongside with the GDM login window. xconsole for instance. " +"Commands to set the background etc. goes in this file too. It is up to the " +"sysadmin to decide whether clients started by the Init script should be " +"killed before starting the user session. This is controlled with the " +"KillInitClients configuration option. When the user has been successfully " +"authenticated GDM tries the scripts in the PostLogin directory in the same " +"manner as for the Init directory. This is done before any session setup is " +"done, and so this would be the script where you might setup the home " +"directory if you need to (though you should use the pam_mount module if you " +"can for this). You have the $USER and $DISPLAY environment variables set for " "this script, and again it is run as root. The script should return 0 on " "success as otherwise the user won't be logged in. This is not true for " -"failsafe session however." -msgstr "" - -#: ../C/gdm.xml:1003 (para) -msgid "" -"After the user session has been setup from the GDM side of things, GDM will " -"run the scripts in the <filename>PreSession</filename> directory, again in " -"the same manner as the <filename>Init</filename> directory. Use this script " -"for local session management or accounting stuff. The <filename>$USER</" -"filename> environment variable contains the login of the authenticated user " -"and <filename>$DISPLAY</filename> is set to the current display. The script " -"should return 0 on success. Any other value will cause GDM to terminate the " -"current login process. This is not true for failsafe sessions however. Also " -"<filename>$X_SERVERS</filename> environmental variable is set and this " -"points to a fake generated X servers file for use with the sessreg " -"accounting application." -msgstr "" - -#: ../C/gdm.xml:1018 (para) -msgid "" -"After this the base <filename>Xsession</filename> script is run with the " -"selected session executable as the first argument. This is run as the user, " -"and really this is the user session. The available session executables are " -"taken from the <filename>Exec=</filename> line in the <filename>.desktop</" -"filename> files in the path specified by <filename>SessionDesktopDir</" -"filename>. Usually this path is <filename><etc>/X11/sessions/:<" -"etc>/dm/Sessions:/usr/share/xsessions/</filename>. The first found file " -"is used. The user either picks from these sessions or GDM will look inside " -"the file <filename>~/.dmrc</filename> for the stored preference." -msgstr "" - -#: ../C/gdm.xml:1031 (para) -msgid "" -"This script should really load the users profile and generally do all the " -"voodoo that is needed to launch a session. Since many systems reset the " -"language selections done by GDM, GDM will also set the <filename>$GDM_LANG</" -"filename> variable to the selected language. You can use this to reset the " -"language environmental variables after you run the users profile. If the " -"user elected to use the system language, then <filename>$GDM_LANG</filename> " -"is not set." +"failsafe session however. After the user session has been setup from the GDM " +"side of things, GDM will run the scripts in the PreSession directory, again " +"in the same manner as the Init directory. Use this script for local session " +"management or accounting stuff. The $USER environment variable contains the " +"login of the authenticated user and $DISPLAY is set to the current display. " +"The script should return 0 on success. Any other value will cause GDM to " +"terminate the current login process. This is not true for failsafe sessions " +"however. Also $X_SERVERS environmental variable is set and this points to a " +"fake generated X servers file for use with the sessreg accounting " +"application. After this the base Xsession script is run with the selected " +"session executable as the first argument. This is run as the user, and " +"really this is the user session. The available session executables are taken " +"from the Exec= line in the .desktop files in the path specified by " +"SessionDesktopDir. Usually this path is etc/X11/sessions/:etc/dm/Sessions:/" +"usr/share/xsessions/. The first found file is used. The user either picks " +"from these sessions or GDM will look inside the file ~/.dmrc for the stored " +"preference. This script should really load the users profile and generally " +"do all the voodoo that is needed to launch a session. Since many systems " +"reset the language selections done by GDM, GDM will also set the $GDM_LANG " +"variable to the selected language. You can use this to reset the language " +"environmental variables after you run the users profile. If the user elected " +"to use the system language, then $GDM_LANG is not set. When the user " +"terminates his session, the PostSession script will be run. Again operation " +"is similar to Init, PostLogin and PreSession. Again the script will be run " +"with root privileges, the slave daemon will block and the $USER environment " +"variable will contain the name of the user who just logged out and $DISPLAY " +"will be set to the display the user used, however note that the X server for " +"this display may already be dead and so you shouldn't try to access it. Also " +"$X_SERVERS environmental variable is set and this points to a fake generated " +"X servers file for use with the sessreg accounting application. Note that " +"the PostSession script will be run even when the display fails to respond " +"due to an I/O error or similar. Thus, there is no guarantee that X " +"applications will work during script execution. Except for the Xsession " +"script all of these scripts will also have the environment variable " +"$RUNNING_UNDER_GDM set to yes, so that you could perhaps use similar scripts " +"for different display managers. The Xsession will always have the " +"$GDMSESSION set to the basename of the session that the user chose to run " +"without the .desktop extension. In addition $DESKTOP_SESSION is also set to " +"the same value and in fact this will also be set by KDM in future versions. " +"Neither of the Init, PostLogin, PreSession or PostSession scripts are " +"necessary and can be left out. The Xsession script is however required as " +"well as at least one session .desktop file. The Configuration File - gdm." +"conf and gdm.conf-custom GDM uses two configuration files: gdm.conf and gdm." +"conf-custom. The gdm.conf file contains the default configuration choices " +"for GDM, and should not be modified by the user. The gdm.conf-custom file is " +"where users may specify their custom configuration choices. Configuration " +"options specified in the gdm.conf-custom file override the values in the " +"main gdm.conf file. If a configuration option is not defined in either file, " +"GDM will default to the value described in the comments in the gdm.conf " +"file. Running the gdmsetup command will cause the gdm.conf-custom to be " +"modified with the user's configuration choices. Previous to GDM 2.13.0.4 " +"only the gdm.conf existed. If upgrading to the new version of GDM, install " +"will check to see if your gdm.conf file is different than your factory-gdm." +"conf file. If so, your gdm.conf file will be automatically copied to gdm." +"conf-custom to preserve your configuration changes. GDM may be configured to " +"support system-wide configuration if built with the --with-configdir option. " +"This allows the gdm.conf file to be installed to a directory that can be " +"mounted across multiple-systems. The GDM --config option may instead be used " +"to specify a configuration file installed to another location. The GDM2 " +"daemon must be restarted to change the configuration file being used. Both " +"configuration files are divided into sections each containing variables that " +"define the behavior for a specific part of the GDM suite. Refer to the " +"comments in the gdm.conf file for additional information about each " +"configuration setting. The gdm.conf and gdm.conf-custom files follow the " +"standard .ini style configuration file syntax. Keywords in brackets define " +"sections, strings before an equal sign (=) are variables and the data after " +"equal sign represents their value. Empty lines or lines starting with the " +"hash mark (#) are ignored. The graphical configurator will try to preserve " +"both comments (lines with a hash mark) and the overall structure of the file " +"so you can intermix using the GUI or hand editing the configuration file. " +"Daemon Configuration [daemon] AddGtkModules AddGtkModules=false If true, " +"then enables gdmgreeter or gdmlogin to be launched with additional Gtk+ " +"modules. This is useful when extra features are required such as accessible " +"login. Note that only trusted modules should be used to minimize security " +"issues. Usually this is used for accessibility modules. The modules which " +"are loaded are specified with the GtkModulesList key. AlwaysRestartServer " +"AlwaysRestartServer=false If true, then gdm never tries to reuse existing X " +"servers by reinitializing them. It will just kill the existing X server and " +"start over. Normally, just reinitializing is a nicer way to go but if the X " +"server memory usage keeps growing this may be a safer option. On Solaris, " +"this value is always true, and this configuration setting is ignored. " +"AutomaticLoginEnable AutomaticLoginEnable=false If the user given in " +"AutomaticLogin should be logged in upon first bootup. No password will be " +"asked. This is useful for single user workstations where local console " +"security is not an issue. Also could be useful for public terminals, " +"although there see TimedLogin. AutomaticLogin AutomaticLogin= This user " +"should be automatically logged in on first bootup. AutomaticLoginEnable must " +"be true and this must be a valid user for this to happen. root can never be " +"autologged in however and gdm will just refuse to do it even if you set it " +"up. The following control chars are recognized within the specified name: " +"the `' character d display's name h display's hostname Alternatively, the " +"name may end with a vertical bar |, the pipe symbol. The name is then used " +"as a application to execute which returns the desired username on standard " +"output. If an empty or otherwise invalid username is returned, automatic " +"login is not performed. This feature is typically used when several remote " +"displays are used as internet kiosks, with a specific user to automatically " +"login for each display. BaseXsession BaseXsession=etc/gdm/Xsession 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 " +"Exec= from the .desktop file of the session. 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 GDMSESSION " +"environmental variable. This will always be set to the basename of .desktop " +"(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 " +"GDM_LANG, but that is only set when the user picks a non-system default " +"language. This script should take care of doing the login for the user and " +"so it should source the etc/profile and friends. The standard script shipped " +"with GDM sources the files in this order: etc/profile then ~/.profile then " +"etc/xprofile and finally ~/.xprofile. Note that different distributions may " +"change this however. Sometimes users personal setup will be in ~/." +"bash_profile, however broken that is. Chooser Chooser=bin/gdmchooser Full " +"path and name of the chooser executable followed by optional arguments. " +"Configurator Configurator=bin/gdmsetup --disable-sound --disable-crash-" +"dialog The pathname to the configurator binary. If the greeter " +"ConfigAvailable 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. ConsoleCannotHandle ConsoleCannotHandle=am,ar,az,bn,el,fa,gu," +"hi,ja,ko,ml,mr,pa,ta,zh 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. " +"ConsoleNotify ConsoleNotify=true If false, gdm will not display a message " +"dialog on the console when an error happens. DefaultPath DefaultPath=/bin:/" +"usr/bin:/usr/bin/X11:/usr/local/bin Specifies the path which will be set in " +"the user's session. This value will be overridden with the value from /etc/" +"default/login if it contains ROOT=pathname. If the /etc/default/login file " +"exists, but contains no value for ROOT, the value as defined in the GDM " +"configuration will be be used. DefaultSession DefaultSession=gnome.desktop " +"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 ShowLastSession key. DisplayInitDir " +"DisplayInitDir=etc/gdm/Init Directory containing the display init scripts. " +"See the ``The Script Directories'' section for more info. DisplayLastLogin " +"DisplayLastLogin=true 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. 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 http://www.radium.ncsc.mil/tpep/" +"library/rainbow/CSC-STD-002-85.html for more info. DoubleLoginWarning " +"DoubleLoginWarning=true 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. DynamicXServers " +"DynamicXServers=false If true, the GDM daemon will honor requests to manage " +"displays via the /tmp/.gdm_socket socket connection. Displays can be " +"created, started, and deleted with the appropriate commands. The gdmdynamic " +"command is a convenient method to send these messages. FailsafeXServer " +"FailsafeXServer= 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 " +"XKeepsCrashing script is run. FirstVT FirstVT=7 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 " +"VTAllocation. FlexibleXServers FlexibleXServers=5 The maximum number of " +"allowed flexible displays. These are displays that can be run using the /" +"tmp/.gdm_socket socket connection. This is used for both full flexible " +"displays and for Xnest displays. FlexiReapDelayMinutes " +"FlexiReapDelayMinutes=5 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 behaviour set this value to 0. This was added in version 2.5.90.0. " +"Greeter Greeter=bin/gdmlogin 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 RemoteGreeter Group Group=gdm " +"The group name under which gdmlogin, gdmgreeter, gdmchooser and the internal " +"failsafe GTK+ dialogs are run. Also see User. 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 ServAuthDir is owned by this group. The ownership and permissions of " +"ServAuthDir should be root.gdm and 1770. GtkModulesList " +"GtkModulesList=module-1:module-2:... A colon separated list of Gtk+ modules " +"that gdmgreeter or gdmlogin will be invoked with if AddGtkModules is true. " +"The format is the same as the standard Gtk+ module interface. HaltCommand " +"HaltCommand=/sbin/shutdown -h now Full path and arguments to command to be " +"executed when user selects Shutdown from the Actions menu. This can be a ';' " +"separated list of commands to try. If a value is missing, the shutdown " +"command is not available. Note that the default for this value is not empty " +"so to disable shutdown you must set this explicitly to an empty value. " +"KillInitClients KillInitClients=true Determines whether GDM should kill X " +"clients started by the init scripts when the user logs in. LogDir LogDir=var/" +"log/gdm Directory containing the log files for the individual displays. By " +"default this is the same as the ServAuthDir. PidFile PidFile=var/run/gdm.pid " +"Name of the file containing the gdm process id. PreFetchProgram " +"PreFetchProgram=command 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. PostLoginScriptDir PostLoginScriptDir=etc/gdm/PostLogin 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. PostSessionScriptDir PostSessionScriptDir=etc/gdm/PostSession " +"Directory containing the scripts run after the user logs out. See the ``The " +"Script Directories'' section for more info. PreSessionScriptDir " +"PreSessionScriptDir=etc/gdm/PreSession Directory containing the scripts run " +"before the user logs in. See the ``The Script Directories'' section for more " +"info. RebootCommand RebootCommand=/sbin/shutdown -r now 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. RemoteGreeter RemoteGreeter=bin/gdmlogin 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 Greeter key. RootPath RootPath=/sbin:/usr/sbin:/bin:/usr/bin:/" +"usr/bin/X11:/usr/local/bin 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 /etc/" +"default/login if it contains SUROOT=pathname. If the /etc/default/login file " +"exists, but contains no value for SUROOT, the value as defined in the GDM " +"configuration will be used. ServAuthDir ServAuthDir=var/gdm Directory " +"containing the X authentication files for the individual displays. Should be " +"owned by root.gdm with permissions 1770, where gdm is the GDM group as " +"defined by the Group option. That is should be owned by root, with gdm 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. SessionDesktopDir SessionDesktopDir=etc/X11/" +"sessions/:etc/dm/Sessions/:/usr/share/xsessions/ Directory containing the ." +"desktop 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. " +"SoundProgram SoundProgram=/usr/bin/play Application to use when playing a " +"sound. Currently used for playing the login sound, see the SoundOnLoginFile " +"key. Supported since 2.5.90.0. StandardXServer StandardXServer=/usr/X11R6/" +"bin/X 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. SuspendCommand SuspendCommand= 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. TimedLoginEnable TimedLoginEnable=false If the user given in " +"TimedLogin should be logged in after a number of seconds (set with " +"TimedLoginDelay) 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 TimedLoginDelay " +"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. TimedLogin TimedLogin= 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 AutomaticLogin are supported. The same control chars and " +"piping to a application are supported. TimedLoginDelay TimedLoginDelay=30 " +"This is the delay before the TimedLogin user will be logged in. It must be " +"greater then or equal to 10. User User=gdm The username under which " +"gdmlogin, gdmgreeter, gdmchooser and the internal failsafe GTK+ dialogs are " +"run. Also see Group. 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. UserAuthDir UserAuthDir= " +"The directory where user's .Xauthority 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: ~/authdir/. If you do not use the tilde " +"expansion, then the filename created will be random, like in UserAuthFBDir. " +"This way many users can have the same authentication directory. For example " +"you might want to set this to /tmp 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 /tmp directory. 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 NeverPlaceCookiesOnNFS in the [security] section to " +"false. UserAuthFBDir UserAuthFBDir=/tmp If GDM fails to update the user's ." +"Xauthority file a fallback cookie is created in this directory. UserAuthFile " +"UserAuthFile=.Xauthority Name of the file used for storing user cookies. " +"VTAllocation VTAllocation=true 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 FirstVT. XKeepsCrashing " +"XKeepsCrashing=etc/gdm/XKeepsCrashing 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 XKeepsCrashing 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. In case FailsafeXServer is setup, " +"that will be tried first. and this only used as a backup if even that X " +"server keeps crashing. Xnest Xnest=/usr/bin/X11/Xnest (/usr/openwin/bin/" +"Xnest on Solaris) 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. Security Options " +"[security] AllowRoot AllowRoot=true Allow root (privileged user) to log in " +"through GDM. Set this to false if you want to disallow such logins. 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. " +"AllowRemoteRoot AllowRemoteRoot=false 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. 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. This value will be overridden and set to false " +"if the /etc/default/login file exists and contains CONSOLE=/dev/login, and " +"set to true if the /etc/default/login file exists and contains any other " +"value or no value for CONSOLE. AllowRemoteAutoLogin " +"AllowRemoteAutoLogin=false 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. Note that this can make a system quite insecure, and thus is " +"off by default. CheckDirOwner CheckDirOwner=true 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 " +"RelaxPermissions 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. " +"DisallowTCP DisallowTCP=true If true, then always append -nolisten tcp 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. NeverPlaceCookiesOnNFS " +"NeverPlaceCookiesOnNFS=true 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. PasswordRequired PasswordRequired=false 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 /etc/default/login if it contains PASSREQ=[YES|NO]. If the /etc/default/" +"login file exists, but contains no value for PASSREQ, the value as defined " +"in the GDM configuration will be used. RelaxPermissions RelaxPermissions=0 " +"By default GDM ignores files and directories writable to other users than " +"the owner. Changing the value of RelaxPermissions makes it possible to alter " +"this behavior: 0 - Paranoia option. Only accepts user owned files and " +"directories. 1 - Allow group writable files and directories. 2 - Allow world " +"writable files and directories. RetryDelay RetryDelay=1 The number of " +"seconds GDM should wait before reactivating the entry field after a failed " +"login. UserMaxFile UserMaxFile=65536 GDM will refuse to read/write files " +"bigger than this number (specified in bytes). 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 RelaxPermissions option for more " +"info. XDCMP Support [xdmcp] DisplaysPerHost DisplaysPerHost=1 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 " +"DisplaysPerHost value accordingly. Note that the number of connections from " +"the local computer is unlimited. Only remote connections are limited by this " +"number. Enable Enable=false Setting this to true enables XDMCP support " +"allowing remote displays/X terminals to be managed by GDM. gdm listens for " +"requests on UDP port 177. See the Port option for more information. If GDM " +"is compiled to support it, access from remote displays can be controlled " +"using the TCP Wrappers library. The service name is gdm You should add gdm:." +"my.domain to your etc/hosts.allow, depending on your TCP Wrappers " +"configuration. See the hosts.allow(5) man page for details. Please note that " +"XDMCP is not a particularly secure protocol and that it is a good idea to " +"block UDP port 177 on your firewall unless you really need it. EnableProxy " +"EnableProxy=false 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. Note, however, " +"that this mode will significantly increase the burden on the machine hosting " +"the XDMCP sessions See the FlexiProxy and FlexiProxyDisconnect options for " +"further details on how to configure support for this feature. HonorIndirect " +"HonorIndirect=true Enables XDMCP INDIRECT choosing (i.e. remote execution of " +"gdmchooser) for X-terminals which don't supply their own display browser. " +"MaxPending MaxPending=4 To avoid denial of service attacks, GDM has fixed " +"size queue of pending connections. Only MaxPending displays can start at the " +"same time. 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. MaxPendingIndirect " +"MaxPendingIndirect=4 GDM will only provide MaxPendingIndirect displays with " +"host choosers simultaneously. If more queries from different hosts come in, " +"the oldest ones will be forgotten. MaxSessions MaxSessions=16 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. MaxWait MaxWait=30 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. GDM will then place the session id in the " +"pending queue waiting for the display to respond with a MANAGE request. 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. MaxWaitIndirect MaxWaitIndirect=30 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 MaxPendingIndirect. Port Port=177 The UDP port number " +"gdm should listen to for XDMCP requests. Don't change this unless you know " +"what you are doing. PingIntervalSeconds PingIntervalSeconds=15 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. Note that GDM in the past used to have a PingInterval 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. ProxyReconnect FlexiProxyReconnect= 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. 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. " +"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. ProxyXServer ProxyXServer= The " +"X server command line for a XDMCP proxy. Any nested X server like Xnest, " +"Xephr or Xdmx should work fairly well. Willing Willing=etc/gdm/Xwilling 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. Common GUI Configuration Options [gui] AllowGtkThemeChange " +"AllowGtkThemeChange=true 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. GtkRC GtkRC= Path to a " +"gtkrc to read when GDM puts up a window. You should really now use the " +"GtkTheme key for just setting a theme. GtkTheme GtkTheme=Default 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. " +"GtkThemesToAllow GtkThemesToAllow=all 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 AllowGtkThemeChange key. Supported since " +"2.5.90.2. MaxIconWidth MaxIconWidth=128 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. MaxIconHeight " +"MaxIconHeight=128 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. Greeter Configuration [greeter] " +"BackgroundColor BackgroundColor=#76848F 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. BackgroundProgramInitialDelay " +"BackgroundProgramInitialDelay=30 The background application will be started " +"after at least that many seconds of inactivity. RestartBackgroundProgram " +"RestartBackgroundProgram=true 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. BackgroundProgramRestartDelay " +"BackgroundProgramRestartDelay=30 The background application will be " +"restarted after at least that many seconds of inactivity. BackgroundImage " +"BackgroundImage=somefile.png If the BackgroundType is 1, then display this " +"file as the background in the greeter. This only affects the GTK+ Greeter. " +"BackgroundProgram BackgroundProgram=/usr/bin/xeyes 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. BackgroundRemoteOnlyColor BackgroundRemoteOnlyColor=true On remote " +"displays only set the color background. This is to make network load " +"lighter. The BackgroundProgram is also not run. This only affects the GTK+ " +"Greeter. BackgroundScaleToFit BackgroundScaleToFit=true Scale background " +"image to fit the screen. This only affects the GTK+ Greeter. BackgroundType " +"BackgroundType=2 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. " +"Browser Browser=true 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 ChooserButton " +"ChooserButton=true 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. ConfigAvailable " +"ConfigAvailable=false 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 Configurator option in the daemon section. " +"DefaultFace DefaultFace=share/pixmaps/nophoto.png 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, the image specified by DefaultFace will " +"be used. The image must be in an gdk-pixbuf supported format and the file " +"must be readable to the GDM user. Include Include= Comma separated list of " +"users to be included in the face browser and in the gdmsetup selection list " +"for Automatic/Timed login. See also Exclude, IncludeAll, and MinimalUID. " +"Exclude Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,... Comma " +"separated list of users to be excluded from the face browser and from the " +"gdmsetup selection list for Automatic/Timed login. Excluded users will still " +"be able to log in, but will have to type their username. See also Include, " +"IncludeAll, and MinimalUID. IncludeAll IncludeAll=false By default, an empty " +"include list means display no users. By setting IncludeAll to true, the " +"password file will be scanned and all users will be displayed aside from " +"users excluded via the Exclude setting and user ID's less than MinimalUID. " +"Scanning the password file can be slow on systems with large numbers of " +"users and this feature should not be used in such environments. See also " +"Include, Exclude, and MinimalUID. GlobalFaceDir GlobalFaceDir=share/pixmaps/" +"faces/ Systemwide directory for face files. The sysadmin can place icons for " +"users here without touching their homedirs. Faces are named after their " +"users' logins. I.e. GlobalFaceDir/johndoe would contain the face icon for " +"the user ``johndoe''. No image format extension should be specified. The " +"face images must be stored in gdk-pixbuf supported formats and they must be " +"readable for the GDM user. A user's own icon file will always take " +"precedence over the sysadmin provided one. GraphicalTheme " +"GraphicalTheme=circles The graphical theme that the Themed Greeter should " +"use. it should refer to a directory in the theme directory set by " +"GraphicalThemeDir. GraphicalThemes GraphicalThemes=circles The graphical " +"themes that the Themed Greeter should use is the Mode is set on Random " +"Themes. This is a /: delimited list. It should refer to a directory in the " +"theme directory set by GraphicalThemeDir. This is only used if " +"GraphicalThemeRand is set to true. GraphicalThemeRand " +"GraphicalThemeRand=false Whether the graphical greeter will use Only One " +"Theme or Random Theme mode. Only One Theme mode uses themes listed by " +"GraphicalTheme, Random Themes mode uses themes listed by GraphicalThemes. A " +"value of false sets greeter to use Only One Theme mode, a value of true sets " +"the greeter to use Random Theme mode. GraphicalThemeDir " +"GraphicalThemeDir=share/gdm/themes/ The directory where themes for the " +"Themed Greeter are installed. GraphicalThemedColor " +"GraphicalThemedColor=#76848F Use this color in the background of the Themed " +"Greeter. This only affects the Themed Greeter. InfoMsgFile InfoMsgFile=/path/" +"to/infofile 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. InfoMsgFont " +"InfoMsgFont=fontspec 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. " +"LocaleFile LocaleFile=etc/gdm/locale.alias 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. LockPosition " +"LockPosition=true If true the position of the login window of the GTK+ " +"Greeter cannot be changed even if the title bar is turned on. Logo " +"Logo=share/pixmaps/gnome-logo-large.png 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. ChooserButtonLogo " +"ChooserButtonLogo=share/pixmaps/gnome-logo-large.png Image file to display " +"in the file chooser button in gdmsetup. This key is modified by gdmsetup and " +"should not be manually modified by the user. This only affects the Login " +"Window Preferences (gdmsetup). MinimalUID MinimalUID=100 The minimal UID " +"that GDM should consider a user. All users with a lower UID will be excluded " +"from the face browser. See also Include, Exclude, and IncludeAll. PositionX " +"PositionX=200 The horizontal position of the login window of the GTK+ " +"Greeter. PositionY PositionY=100 The vertical position of the login window " +"of the GTK+ Greeter. Quiver Quiver=true Controls whether gdmlogin should " +"shake the display when an incorrect username/password is entered. This only " +"affects the GTK+ Greeter. DefaultRemoteWelcome DefaultRemoteWelcome=true If " +"set to true, the value Welcome to %n is used for the RemoteWelcome. This " +"value is translated into the appropriate language for the user. If set to " +"false, the RemoteWelcome setting is used. This string can use the same " +"special character sequences as explained in the Text Node section of the " +"Themed Greeter chapter. This explains the meaning of %n. RemoteWelcome " +"RemoteWelcome=Welcome to n Controls which text to display next to the logo " +"image in the greeter for remote XDMCP sessions. The same expansion is done " +"here as in the Welcome string. This string can use the same special " +"character sequences as explained in the Text Node section of the Themed " +"Greeter chapter. chapter. RunBackgroundProgramAlways " +"RunBackgroundProgramAlways=false If this is true then the background " +"application is run always, otherwise it is only run when the BackgroundType " +"is 0 (None) This only affects the GTK+ Greeter. SetPosition SetPosition=true " +"If true the position of the login window of the GTK+ Greeter is determined " +"by PositionX / PositionY. ShowGnomeFailsafeSession " +"ShowGnomeFailsafeSession=true Should the greeter show the Gnome Failsafe " +"session in th sessions list. ShowLastSession ShowLastSession=true 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 DefaultSession) unless then pick something else for " +"this session only. So if this is off, this really circumvents saving of the " +"last session. ShowXtermFailsafeSession ShowXtermFailsafeSession=true Should " +"the greeter show the Xterm Failsafe session in the sessions list. " +"SoundOnLogin SoundOnLogin=true If true, the greeter will play a sound or " +"beep when it is ready for a login. See also the SoundOnLoginFile key. " +"Supported since 2.5.90.0. SoundOnLoginSuccess SoundOnLoginSuccess=true If " +"true, the greeter will play a sound after a successful login attempt. See " +"also the SoundOnLoginSuccessFile key. SoundOnLoginFailure " +"SoundOnLoginFailure=true If true, the greeter will play a sound after a " +"failed login attempt. See also the SoundOnLoginFailureFile key. " +"SoundOnLoginFile SoundOnLoginFile=/path/to/sound.wav The file that will be " +"played using the specified sound application (by default that is /usr/bin/" +"play) instead of a beep when the greeter is ready for a login. See also the " +"SoundOnLogin key and the SoundProgram key. Supported since 2.5.90.0. " +"SoundOnLoginSuccessFile SoundOnLoginSuccessFile=/path/to/sound.wav The file " +"that will be played using the specified sound application (by default that " +"is /usr/bin/play) after a successful login attempt. See also the " +"SoundOnLoginSuccess key and the SoundProgram key. SoundOnLoginFailureFile " +"SoundOnLoginFailureFile=/path/to/sound.wav The file that will be played " +"using the specified sound application (by default that is /usr/bin/play) " +"after a failed login attempt. See also the SoundOnLoginFailure key and the " +"SoundProgram key. SystemMenu SystemMenu=true 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. 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. TitleBar " +"TitleBar=true Display the title bar in the greeter. This only affects the GTK" +"+ Greeter. Use24Clock Use24Clock=auto Select the use of 24 hour clock. Some " +"locales do not support 12 hour format (like Finnish, that is fi_FI), and in " +"those locales this setting has no effect at all. 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. UseCirclesInEntry " +"UseCirclesInEntry=false Use circles instead of asterisks in the password " +"entry. This may not work with all fonts however. UseInvisibleInEntry " +"UseInvisibleInEntry=false Do not show any visual feedback is the password " +"entry. This is the standard in console and xdm. Settings this option " +"discards the UseCirclesInEntry option. DefaultWelcome DefaultWelcome=true If " +"set to true, the value Welcome is used for the Welcome. This value is " +"translated into the appropriate language for the user. If set to false, the " +"Welcome setting is used. Welcome Welcome=Welcome Controls which text to " +"display next to the logo image in the standard greeter. The following " +"control chars are supported: the `' character d display's hostname h Fully " +"qualified hostname m machine (processor type) n Nodename (i.e. hostname " +"without .domain) r release (OS version) s sysname (i.e. OS) This string is " +"only used for local logins. For remote XDMCP logins we use RemoteWelcome. 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. XineramaScreen XineramaScreen=0 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...). XDCMP Chooser Options [chooser] " +"AllowAdd AllowAdd=true 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. Broadcast Broadcast=true 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 Hosts key. Multicast " +"Multicast=true 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 Hosts key. The host will respond if it is " +"listening to XDMCP requests and IPv6 is enabled there. MulticastAddr " +"MulticastAddr=ff02::1 This is the Link-local Multicast address and is " +"hardcoded here. DefaultHostImage DefaultHostImage=share/pixmaps/nohost.png " +"File name for the default host icon. This image will be displayed if no icon " +"is specified for a given host. The file must be in an gdk-pixbuf supported " +"format and it must be readable for the GDM user. HostImageDir " +"HostImageDir=share/hosts Repository for host icon files. The sysadmin can " +"place icons for remote hosts here and they will appear in gdmchooser. The " +"file name must match the fully qualified name (FQDN) for the host. The icons " +"must be stored in gdk-pixbuf supported formats and they must be readable to " +"the GDM user. Hosts Hosts=host1,host2 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 Broadcast 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. ScanTime ScanTime=4 " +"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. Debug " +"Configuration [debug] Enable Enable=false 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. " +"Gestures Gestures=false 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. X Server Definitions " +"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 Standard is required. If you do " +"not specify this server, GDM will assume default values for a 'Standard' " +"server and the path given by daemon/StandardXServer. Standard is used as the " +"default, in situations when no other server has been defined. Servers are " +"defined by sections named server- 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, server- sections in the gdm.conf-custom file override " +"values in the gdm.conf file. In other words, if a server-Standard section is " +"defined in gdm.conf-custom, then that will be used and the section in the " +"gdm.conf file will be ignored. [server-Standard] name name=Standard server " +"The name that will be displayed to the user. command command=/usr/bin/X11/X " +"The command to execute, with full path to the binary of the X server, and " +"any extra arguments needed. flexible flexible=true Indicates if this server " +"is available as a choice when a user wishes to run a flexible, on demand " +"server. handled handled=true 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 -" +"terminate 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. chooser chooser=false 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. Local Static X Display Configuration 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 [servers] section corresponds to the display number to be " +"managed. Normally there is only one key, which is the key 0, which " +"corresponds to the display :0. 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 [servers] section in the gdm.conf-custom file overrides values " +"in the gdm.conf file. [servers] display number 0=Standard 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). 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 gdm.conf-custom to turn off a display that is defined in the gdm." +"conf file. GDM will splice -auth ServAuthDir/:n.Xauth :n, where n is the " +"display number. Inside the command line before all other arguments before " +"running the X server. 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 " +"VTAllocation key is set. Normally you do not need to add a -nolisten tcp " +"flag as this is added automatically for local X servers when the DisallowTCP " +"option is set. priority priority=0 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. Per User Configuration 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 " +"UserMaxFile 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. First there is the ~/.dmrc " +"file. In theory this file should be shared between GDM and KDM, so users " +"only have to configure things once. This is a standard .ini style " +"configuration file. It has one section called [Desktop] which has two keys: " +"Session and Language. The Session key specifies the basename of the session ." +"desktop file that the user wishes to normally use (without the .desktop " +"extension, in other words). The Language 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: [Desktop] " +"Session=gnome Language=cs_CZ.UTF-8 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. If the GDM Face Browser " +"is turned, then the file $HOME/.face 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 MaxIconWidth and MaxIconHeight values defined in the GDM " +"configuration or it will be ignored. Users can run the gdmphotosetup program " +"to specify a face image and it will copy the file to the $HOME/.face " +"location and scale it so its longest dimension is not larger than the " +"MaxIconWidth or MaxIconHeight values. gdmphotosetup takes care to not change " +"the aspect ratio of the image. Face images can also be placed in the global " +"face directory, which is specified by the GlobalFaceDir configuration option " +"( normally share/pixmaps/faces/) and the filename should be the name of the " +"user, optionally with a .png, .jpg, etc. appended. Controlling GDM You can " +"control GDM behavior during runtime in several different ways. You can " +"either run certain commands, or you can talk to GDM using either a unix " +"socket protocol, or a FIFO protocol. Commands To stop GDM, you can either " +"send the TERM signal to the main daemon or run the gdm-stop command which is " +"in the sbin/ directory. To restart GDM, you can either send the HUP signal " +"to the main daemon or run the gdm-restart command which is also in the sbin/ " +"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 gdm-safe-" +"restart command which is in the sbin/ directory as well. The gdmflexiserver " +"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 gdmflexiserver 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 gdmflexiserver --help to get a " +"listing of possible options. The FIFO protocol GDM also provides a FIFO " +"called .gdmfifo in the ServAuthDir directory (usually var/gdm/.gdmfifo). 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). Full and up to " +"date documentation of the commands and their use is contained in the GDM " +"source tree in the file daemon/gdm.h. Look for the defines starting with " +"GDM_SOP_. 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. Socket Protocol GDM provides a unix " +"domain socket for communication at /tmp/.gdm_socket. 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 gdmflexiserver command uses this protocol, for example, to launch " +"flexible (on-demand) displays. gdmflexiserver accepts the following commands " +"with the --command option: VERSION AUTH_LOCAL FLEXI_XSERVER FLEXI_XNEST " +"ATTACHED_SERVERS ALL_SERVERS GET_SERVER_LIST GET_SERVER_DETAILS GET_CONFIG " +"GET_CONFIG_FILE UPDATE_CONFIG GREETERPIDS QUERY_LOGOUT_ACTION " +"SET_LOGOUT_ACTION SET_SAFE_LOGOUT_ACTION QUERY_VT SET_VT CLOSE These are " +"described in detail below, including required arguments, response format, " +"and return codes. VERSION VERSION: Query GDM version Supported since: " +"2.2.4.0 Arguments: None Answers: GDM gdm version ERROR err number english " +"error description 200 = Too many messages 999 = Unknown error AUTH_LOCAL " +"AUTH_LOCAL: Setup this connection as authenticated for FLEXI_SERVER. Because " +"all full blown (non-Xnest) displays can be started only from users logged in " +"locally, and here GDM assumes only users logged in from GDM. They must pass " +"the xauth MIT-MAGIC-COOKIE-1 that they were passed before the connection is " +"authenticated. Note: The AUTH LOCAL command requires the --authenticate " +"option, although only FLEXI XSERVER uses this currently. Note: Since 2.6.0.6 " +"you can also use a global ServAuthDir/.cookie, which works for all " +"authentication except for SET_LOGOUT_ACTION and QUERY_LOGOUT_ACTION and " +"SET_SAFE_LOGOUT_ACTION which require a logged in display. Supported since: " +"2.2.4.0 Arguments: xauth cookie xauth cookie is in hex form with no 0x " +"prefix Answers: OK ERROR err number english error description 0 = Not " +"implemented 100 = Not authenticated 200 = Too many messages 999 = Unknown " +"error FLEXI_XSERVER FLEXI_XSERVER: Start a new X flexible display. Only " +"supported on connection that passed AUTH_LOCAL Supported since: 2.2.4.0 " +"Arguments: xserver type If no arguments, starts the standard X server " +"Answers: OK display ERROR err number english error description 0 = Not " +"implemented 1 = No more flexi servers 2 = Startup errors 3 = X failed 4 = X " +"too busy 6 = No server binary 100 = Not authenticated 200 = Too many " +"messages 999 = Unknown error FLEXI_XNEST FLEXI_XNEXT: Start a new flexible " +"Xnest display. Note: Supported on older version from 2.2.4.0, later 2.2.4.2, " +"but since 2.3.90.4 you must supply 4 arguments or ERROR 100 will be " +"returned. This will start Xnest using the XAUTHORITY file supplied and as " +"the uid same as the owner of that file (and same as you supply). You must " +"also supply the cookie as the third argument for this display, to prove that " +"you indeed are this user. Also this file must be readable ONLY by this user, " +"that is have a mode of 0600. If this all is not met, ERROR 100 is returned. " +"Note: The cookie should be the MIT-MAGIC-COOKIE-1, the first one GDM can " +"find in the XAUTHORITY file for this display. If that's not what you use you " +"should generate one first. The cookie should be in hex form. Supported " +"since: 2.3.90.4 Arguments: display to run on uid of requesting user xauth " +"cookie for the display xauth file Answers: OK display ERROR err number " +"english error description 0 = Not implemented 1 = No more flexi servers 2 = " +"Startup errors 3 = X failed 4 = X too busy 5 = Xnest can't connect 6 = No " +"server binary 100 = Not authenticated 200 = Too many messages 999 = Unknown " +"error ADD_DYNAMIC_DISPLAY ADD_DYNAMIC_DISPLAY: Create a new server " +"definition that will run on the specified display leaving, it in " +"DISPLAY_CONFIG state. Supported since: 2.8.0.0 Arguments: display to run " +"on=server Where server is either a configuration named in the GDM " +"configuration or a literal command name. Answers: OK display ERROR err " +"number english error description 0 = Not implemented 2 = Existing display 3 " +"= No server string 4 = Display startup failure 100 = Not authenticated 200 = " +"Dynamic Displays not allowed 999 = Unknown error RELEASE_DYNAMIC_DISPLAYS " +"RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in " +"DISPLAY_CONFIG state Supported since: 2.8.0.0 Arguments: None Answers: OK " +"display ERROR err number english error description 0 = Not implemented 100 = " +"Not authenticated 200 = Dynamic Displays not allowed 999 = Unknown error " +"REMOVE_DYNAMIC_DISPLAY REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, " +"killing the server and purging the display configuration Supported since: " +"2.8.0.0 Arguments: display to remove Answers: OK display ERROR err number " +"english error description 0 = Not implemented 1 = Bad display number 100 = " +"Not authenticated 200 = Dynamic Displays not allowed 999 = Unknown error " +"ATTACHED_SERVERS ATTACHED_SERVERS: List all attached displays. Doesn't list " +"XDMCP and xnest non-attached displays. Note: This command used to be named " +"CONSOLE_SERVERS, which is still recognized for backwards compatibility. The " +"optional pattern argument is supported as of version 2.8.0.0. Supported " +"since: 2.2.4.0 Arguments: pattern (optional) With no argument, all attached " +"displays are returned. The optional pattern is a string that may contain " +"glob characters '*', '?', and '[]'. Only displays that match the pattern " +"will be returned. Answers: OK server;server;... server is display,logged in " +"user,vt or xnest display logged in user can be empty in case no one logged " +"in yet, and vt can be -1 if it's not known or not supported (on non-Linux " +"for example). If the display is an xnest display and is a console one (that " +"is, it is an xnest inside another console display) it is listed and instead " +"of vt, it lists the parent display in standard form. ERROR err number " +"english error description 1 = Not implemented 200 = Too many messages 999 = " +"Unknown error ALL_SERVERS ALL_SERVERS: List all displays, including console, " +"remote, xnest. This can, for example, be useful to figure out if the display " +"you are on is managed by the gdm daemon, by seeing if it is in the list. It " +"is also somewhat like the 'w' command but for graphical sessions. Supported " +"since: 2.4.2.96 Arguments: None Answers: OK server;server;... server is " +"display,logged in user logged in user can be empty in case no one logged in " +"yet ERROR err number english error description 0 = Not implemented 200 = Too " +"many messages 999 = Unknown error GET_SERVER_LIST GET_SERVER_LIST: Get a " +"list of the server sections from the configuration file. Supported since: " +"2.13.0.4 Arguments: None Answers: OK value;value;... ERROR err number " +"english error description 0 = Not implemented 1 = No servers found 50 = " +"Unsupported key 200 = Too many messages 999 = Unknown error " +"GET_SERVER_DETAILS GET_SERVER_DETAILS: Get detail information for a specific " +"server. Supported since: 2.13.0.4 Arguments: server key Key values include: " +"NAME - Returns the server name COMMAND - Returns the server command FLEXIBLE " +"- Returns true if flexible, false otherwise CHOOSABLE - Returns true if " +"choosable, false otherwise HANDLED - Returns true if handled, false " +"otherwise CHOOSER - Returns true if chooser, false otherwise PRIORITY - " +"Returns process priority Answers: OK value ERROR err number english error " +"description 0 = Not implemented 1 = Server not found 2 = Key not valid 50 = " +"Unsupported key 200 = Too many messages 999 = Unknown error GET_CONFIG " +"GET_CONFIG: Get configuration value for key. Useful so that other " +"applications can request configuration information from GDM. Any key defined " +"as GDM_KEY_* in gdm.h is supported. Starting with version 2.13.0.2 " +"translated keys (such as greeter/GdmWelcome[cs] are supported via " +"GET_CONFIG. Also starting with version 2.13.0.2 it is no longer necessary to " +"include the default value (i.e. you can use key greeter/IncludeAll instead " +"of having to use greeter/IncludeAll=false. Supported since: 2.6.0.9 " +"Arguments: key Answers: OK value ERROR err number english error description " +"0 = Not implemented 50 = Unsupported key 200 = Too many messages 999 = " +"Unknown error GET_CONFIG_FILE GET_CONFIG_FILE: Get config file location " +"being used by the daemon. If the GDM daemon was started with the --config " +"option, it will return the value passed in via the argument. Supported " +"since: 2.8.0.2 Arguments: None Answers: OK full path to GDM configuration " +"file ERROR err number english error description 0 = Not implemented 200 = " +"Too many messages 999 = Unknown error UPDATE_CONFIG UPDATE_CONFIG: Tell the " +"daemon to re-read a key from the GDM configuration file. Any user can " +"request that values are re-read but the daemon will only do so if the file " +"has been modified since GDM first read the file. Only users who can change " +"the GDM configuration file (normally writable only by the root user) can " +"actually modify the GDM configuration. This command is useful to cause the " +"GDM to update itself to recognize a change made to the GDM configuration " +"file by the root user. Starting with version 2.13.0.0, all GDM keys are " +"supported except for the following: daemon/PidFile daemon/ConsoleNotify " +"daemon/User daemon/Group daemon/LogDir daemon/ServAuthDir daemon/UserAuthDir " +"daemon/UserAuthFile daemon/UserAuthFBDir GDM also supports the following " +"Psuedokeys: xdmcp/PARAMETERS (2.3.90.2) updates the following: xdmcp/" +"MaxPending xdmcp/MaxSessions xdmcp/MaxWait xdmcp/DisplaysPerHost xdmcp/" +"HonorIndirect xdmcp/MaxPendingIndirect xdmcp/MaxWaitIndirect xdmcp/" +"PingIntervalSeconds (only affects new connections) xservers/PARAMETERS " +"(2.13.0.4) updates the following: all [server-foo] sections. Supported keys " +"for previous versions of GDM: security/AllowRoot (2.3.90.2) security/" +"AllowRemoteRoot (2.3.90.2) security/AllowRemoteAutoLogin (2.3.90.2) security/" +"RetryDelay (2.3.90.2) security/DisallowTCP (2.4.2.0) daemon/Greeter " +"(2.3.90.2) daemon/RemoteGreeter (2.3.90.2) xdmcp/Enable (2.3.90.2) xdmcp/" +"Port (2.3.90.2) daemon/TimedLogin (2.3.90.3) daemon/TimedLoginEnable " +"(2.3.90.3) daemon/TimedLoginDelay (2.3.90.3) greeter/SystemMenu (2.3.90.3) " +"greeter/ConfigAvailable (2.3.90.3) greeter/ChooserButton (2.4.2.0) greeter/" +"SoundOnLoginFile (2.5.90.0) daemon/AddGtkModules (2.5.90.0) daemon/" +"GtkModulesList (2.5.90.0) Supported since: 2.3.90.2 Arguments: key key is " +"just the base part of the key such as security/AllowRemoteRoot Answers: OK " +"ERROR err number english error description 0 = Not implemented 50 = " +"Unsupported key 200 = Too many messages 999 = Unknown error GREETERPIDS " +"GREETERPIDS: List all greeter pids so that one can send HUP to them for " +"config rereading. Of course one must be root to do that. Supported since: " +"2.3.90.2 Arguments: None Answers: OK pid;pid;... ERROR err number english " +"error description 0 = Not implemented 200 = Too many messages 999 = Unknown " +"error QUERY_LOGOUT_ACTION QUERY_LOGOUT_ACTION: Query which logout actions " +"are possible Only supported on connections that passed AUTH_LOCAL. Supported " +"since: 2.5.90.0 Answers: OK action;action;... Where action is one of HALT, " +"REBOOT or SUSPEND. An empty list can also be returned if no action is " +"possible. A '!' is appended to an action if it was already set with " +"SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION. Note that SET_LOGOUT_ACTION has " +"precedence over SET_SAFE_LOGOUT_ACTION. ERROR err number english error " +"description 0 = Not implemented 100 = Not authenticated 200 = Too many " +"messages 999 = Unknown error SET_LOGOUT_ACTION SET_LOGOUT_ACTION: Tell the " +"daemon to halt/restart/suspend after slave process exits. Only supported on " +"connections that passed AUTH_LOCAL. Supported since: 2.5.90.0 Arguments: " +"action NONE Set exit action to 'none' HALT Set exit action to 'halt' REBOOT " +"Set exit action to 'reboot' SUSPEND Set exit action to 'suspend' Answers: OK " +"ERROR err number english error description 0 = Not implemented 7 = Unknown " +"logout action, or not available 100 = Not authenticated 200 = Too many " +"messages 999 = Unknown error SET_SAFE_LOGOUT_ACTION SET_SAFE_LOGOUT_ACTION: " +"Tell the daemon to halt/restart/suspend after everybody logs out. If only " +"one person logs out, then this is obviously the same as the " +"SET_LOGOUT_ACTION. Note that SET_LOGOUT_ACTION has precedence over " +"SET_SAFE_LOGOUT_ACTION if it is set to something other then NONE. If no one " +"is logged in, then the action takes effect effect immediately. Only " +"supported on connections that passed AUTH_LOCAL. Supported since: 2.5.90.0 " +"Arguments: action NONE Set exit action to 'none' HALT Set exit action to " +"'halt' REBOOT Set exit action to 'reboot' SUSPEND Set exit action to " +"'suspend' Answers: OK ERROR err number english error description 0 = Not " +"implemented 7 = Unknown logout action, or not available 100 = Not " +"authenticated 200 = Too many messages 999 = Unknown error QUERY_VT QUERY_VT: " +"Ask the daemon about which VT we are currently on. This is useful for logins " +"which don't own /dev/console but are still console logins. Only supported on " +"Linux currently, other places will just get ERROR 8. This is also the way to " +"query if VT support is available in the daemon in the first place. Only " +"supported on connections that passed AUTH_LOCAL. Supported since: 2.5.90.0 " +"Arguments: None Answers: OK vt number ERROR err number english error " +"description 0 = Not implemented 8 = Virtual terminals not supported 100 = " +"Not authenticated 200 = Too many messages 999 = Unknown error SET_VT SET_VT: " +"Change to the specified virtual terminal. This is useful for logins which " +"don't own /dev/console but are still console logins. Only supported on Linux " +"currently, other places will just get ERROR 8. Only supported on connections " +"that passed AUTH_LOCAL. Supported since: 2.5.90.0 Arguments: vt Answers: OK " +"ERROR err number english error description 0 = Not implemented 8 = Virtual " +"terminals not supported 9 = Invalid virtual terminal number 100 = Not " +"authenticated 200 = Too many messages 999 = Unknown error CLOSE CLOSE: Close " +"sockets connection Supported since: 2.2.4.0 Arguments: None Answers: None " +"GDM Commands GDM User Commands The GDM package provides the following " +"different commands in EXPANDED_BINDIR intended to be used by the end-user: " +"gdmXnestchooser and gdmXnest Command Line Options The gdmXnestchooser " +"command automatically gets the correct display number, sets up access, and " +"runs Xnest 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 gdmXnestchooser somehost will run the " +"XDMCP chooser from host somehost inside an Xnest session. You can make this " +"command do a direct query instead by passing the -d option as well. In " +"addition to the following options, this command also supports standard GNOME " +"options. gdmXnestchooser Command Line Options -x, --xnest=STRING Xnest " +"command line, default is Xnest -o, --xnest-extra-options=OPTIONS Extra " +"options for Xnest, default is no options. -n, --no-query Just run Xnest, no " +"query (no chooser) -d, --direct Do direct query instead of indirect " +"(chooser) -B, --broadcast Run broadcast instead of indirect (chooser) -b, --" +"background Run in background --no-gdm-check Don't check for running GDM " +"gdmflexichooser Command Line Options The gdmflexiserver 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. 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. 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. The " +"gdmflexiserver --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. " +"In addition to the following options, gdmflexiserver also supports standard " +"GNOME options. gdmflexichooser Command Line Options -c, --command=COMMAND " +"Send the specified protocol command to GDM -n, --xnest Start a flexible X " +"display in Xnest mode -l, --no-lock Do not lock current screen -d, --debug " +"Turns on debugging output which gets sent to syslog. Same as turning on " +"debug in the configuration file. -a, --authenticate Authenticate before " +"running --command -s, --startnew Starts a new flexible display without " +"displaying a dialog asking the user if they wish to continue any existing " +"sessions. gdmdynamic Command Line Options The gdmdynamic command which " +"creates, runs, and removes displays (X servers) on demand. 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 gdmdynamic command can be used to create a new display on a " +"particular display number, run all newly created displays, or remove a " +"display. The gdmdynamic command can also be used to list all attached " +"displays, or only attached displays that match a pattern. gdmdynamic Command " +"Line Options One of the following options can be used per instance: -a " +"display=server Add a new display configuration. For example, -a " +"2=StandardServerTwo -a 3=/usr/X11R6/bin/X -dev /dev/fb2 -r Release (run) all " +"displays waiting in the DISPLAY_CONFIG state. -d display Delete a display, " +"killing the X server and purging the display configuration. For example, -d " +"3. -l [pattern] 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: -l Standard* -l *Xorg* These " +"options can be added to the above: -v Verbose mode. Prinr diagnostic " +"messages about each message sent to GDM. -b Background mode. Fork child to " +"do the work and return immediately. gdmphotosetup Command Line Options " +"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 ~/." +"face. This command accepts standard GNOME options. gdmthemetester Command " +"Line Options gdmthemetester 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. gdmthemetester requires " +"that the system support gdmXnest. Note that themes can display differently " +"depending on the theme's Show mode. gdmthemetester allows viewing the themes " +"in different modes via the environment option. Valid environment values and " +"their meanings follow: 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. GDM Root User Commands The GDM " +"package provides the following different commands in EXPANDED_SBINDIR " +"intended to be used by the root user: gdm and gdm-binary Command Line " +"Options The gdm command is really just a script which runs the gdm-binary, " +"passing along any options. Before launching gdm-binary, the gdm wrapper " +"script will source the etc/profile 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. gdm and gdm-" +"binary Command Line Options --help Gives a brief overview of the command " +"line options. -nodaemon If this option is specified, then GDM does not fork " +"into the background when run. You can use just a single dash with this " +"option to preserve compatibility with XDM. --no-console Tell the daemon that " +"it should not run anything on the console. This means that none of the local " +"servers from the [servers] section will be run, and the console will not be " +"used for communicating errors to the user. An empty [servers] section " +"automatically implies this option. --config=CONFIGFILE Specify an " +"alternative configuration file. --preserve-ld-vars When clearing the " +"environment internally, preserve all variables starting with LD_. This is " +"mostly for debugging purposes. --version Print the version of the GDM " +"daemon. --wait-for-go 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. gdmsetup Command " +"Line Options gdmsetup 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 gdmsetup 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. gdm-restart Command Line Options gdm-restart 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. gdm-safe-restart Command Line Options gdm-safe-restart stops and " +"restarts GDM by sending the GDM daemon a USR1 signal. GDM will be restarted " +"as soon as all users log out. gdm-stop Command Line Options gdm-stop stops " +"GDM by sending the GDM daemon a TERM signal. GDM Internal Commands The GDM " +"package provides the following different commands in EXPANDED_LIBEXECDIR " +"intended to be used by the gdm daemon process. gdmchooser and gdmlogin " +"Command Line Options The gdmgreeter and gdmlogin are two different login " +"applications, either can be used by GDM. gdmgreeter is themeable with GDM " +"themes while gdmlogin is themable with GTK+ themes. These applications are " +"normally executed by the GDM daemon. Both commands support standard GNOME " +"options. gdmchooser Command Line Options The gdmchooser is the XDMCP chooser " +"application. The gdmchooser 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. " +"gdmchooser Command Line Options -xdmaddress=SOCKET Socket for XDM " +"communication. --clientaddress=ADDRESS Client address to return in response " +"to XDM. This option is for running gdmchooser with XDM, and is not used " +"within GDM. -connectionType=TYPE Connection type to return in response to " +"XDM. This option is for running gdmchooser with XDM, and is not used within " +"GDM. Themed Greeter This section describes the creation of themes for the " +"Themed Greeter. For examples including screenshots, see the standard " +"installed themes and the themes from the theme website. Theme Overview 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 share/" +"gdm/themes/theme_name. Usually this would be under /usr/share. The theme " +"directory should contain a file called GdmGreeterTheme.desktop which has " +"similar format to other .desktop files and looks like: [GdmGreeterTheme] " +"Encoding=UTF-8 Greeter=circles.xml Name=Circles Description=Theme with blue " +"circles Author=Bond, James Bond Copyright=(c) 2002 Bond, James Bond " +"Screenshot=screenshot.png The Name, Description, Author and Copyright fields " +"can be translated just like the other .desktopfiles. All the files that are " +"mentioned should be in the theme directory itself. The Screenshot field " +"points to a file which should be a 200x150 screenshot of the theme in action " +"(it is OK not to have one, but it makes it nicer for user). The Greeter " +"field points to an XML file that contains the description of the theme. The " +"description will be given later. Once you have theme ready and installed you " +"can test it with the installed gdmthemetester 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: gdmthemetester xdmcp circles 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. Once you have all this done, then " +"make a tarball that contains the directory name (so that you could just " +"untar it in the /usr/share/gdm/themes directory). And this is the tarball " +"you distribute and people can install from the graphical configuration " +"application. You can do this with the commands: cd /usr/share/gdm/themes tar " +"czvf theme_name.tar.gz theme_name/ Detailed Description of Theme XML format " +"Box Nodes Box nodes are container nodes for item nodes. Box nodes are " +"specified as follows: box orientation=alignment min-width=num xpadding=num " +"ypadding=num spacing=num homogeneous=bool 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. If the box is " +"homogeneous then the children are allocated equal amount of space. The min-" +"width must be specified in pixels. Obviously there is also a corresponding " +"min-height property as well. Fixed Nodes 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: fixed Then you put other items with " +"proper position nodes inside this. The toplevel node is really just like a " +"fixed node. Item Nodes A GDM Theme is created by specifying a hierarchy of " +"item and box nodes. Item nodes can have the following value for type: entry " +"Text entry field. list A list widget. label A text label. Must have a text " +"node to specify the text. pixmap An pixmap image in a format that gdk-pixbuf " +"supports like PNG, JPEG, Tiff, etc...) rect Rectangle. svg Scaled Vector " +"Graphic image. For example: item type=label 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) Entry items can have id values as " +"follows: user-pw-entry Entry field for userid and password entry. This is " +"the field used for responses for the PAM/GDM questions (Username, Password, " +"etc..). List items can have id values as follows: userlist A Face Browser " +"list, so that users can pick their username by clicking on this instead of " +"typing. 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' Label " +"items can have id values as follows: clock Label that displays the date and " +"time. pam-prompt Label that displays the PAM prompt. This is the prompt that " +"PAM uses to ask for username, password, etc... pam-error Label that " +"displayst PAM/GDM error messages. Such as when user can't log in. pam-" +"message 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. timed-label Label that displays timed login information. " +"Rectangles can have id values as follows: caps-lock-warning Displays an icon " +"that shows if the CAPS LOCK key is depressed. This rectangle will be hidden/" +"shown appropriately If an item is of type rect, the item can be a button. " +"Buttons must also include a button value as follows: item type=rect " +"id=disconnect_button button=true. Possible values for button ids are as " +"follows: chooser_button Runs the XDMCP chooser. config_button Runs the GDM " +"configuration application. disconnect_button Disconnect from remote session. " +"language_button Displays the language selection dialog. halt_button Halt " +"(shuts down) the system. reboot_button Restart the system. session_button " +"List and select from available sessions. suspend_button Suspend the system. " +"system_button 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. Position Node Each " +"item can specify its position and size via the pos node. For example: pos " +"x=0 y=4 width=100% height=100%/ Both position and size can be given in " +"percent and it will be taken as the percentage of the size of the current " +"container. For toplevel items it's the percentage of the whole screen. 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. 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: pos x=10% y=50% anchor=w " +"width=80% height=95/ 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. 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. 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). 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: item type=label pos x=" +"\"10%\" max-screen-percent-width=\"50%\"/ Show Node 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: console - In console mode. console-fixed - In console non-flexi " +"mode. console-flexi - In console flexi mode. flexi - In flexi mode. remote - " +"In remote mode. remote-flexi - In remote flexi mode. For example: show " +"modes=flexi,remote/ 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: chooser, if ChooserButton is set to true in the GDM " +"configuration. config, if ConfigAvailable is set to true in the GDM " +"configuration. halt, if HaltDaemon is specified in the GDM configuration. " +"reboot, if RebootCommand is specified in the GDM configuration. suspend, if " +"SuspendCommand is specified in the GDM configuration. system, if SystemMenu " +"is specified in the GDM configuration. timed, if TimedLoginEnabled is set to " +"true in the GDM configuration. For example: show modes=console type=system/ " +"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. Normal/" +"Active/Prelight Nodes 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: normal - normal state. active - when the item has active " +"focus. prelight - when the mouse is hovering over the item. When item is " +"rect (alpha can be omitted and defaults to 0.0): normal color=#ffffff " +"alpha=0.0 When item is label normal color=#ffffff font=Sans 14/ When the " +"item type is pixmap or SVG, then the normal, active, and prelight tags " +"specify the images to use as follows: normal file=picture.png tint=#dddddd/ " +"Note that relative pathnames are assumed to be in the same directory as the " +"theme .xml file in share/gdm/themes/theme_name. Face Browser Icon/Label " +"Color Nodes 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: color " +"iconcolor=#dddddd labelcolor=#ffffff/ Text Node 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): text xml:lang=frOption/" +"text You can include pango markup in the text nodes for labels, however you " +"must encode it. So for example to have the label of foosupbar/sup, you must " +"type: textfoolt;supbarlt;/sup/text Text nodes can contain the following " +"special character sequences which will be translated as follows: %% - A " +"literal % character %c - Clock time. Only labels with the clock id will " +"update automatically every second. Other labels will contain a static " +"timestamp. %d - Display name (DISPLAY environment variable) %h - Hostname " +"(gethostname output) %m - Machine name (uname.machine output) %n - Node name " +"(uname.nodename output) %o - Domain name (getdomainname output) %r - Release " +"name (uname.release output) %s - System name (uname.sysname output) %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. %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. \\n - Carriage return " +"_ - An underscore causes the following character to be underlined. If it " +"precedes a % character sequence, the string that replaces the character " +"sequence is underlined. Stock Certain common localized labels can be " +"specified via the stock tags. The text tag is ignored if the stock tag is " +"used. You should really use the stock labels rather then just putting all " +"the translations into the themes. This gives faster load times and likely " +"better translations. The following values are valid: cancel, _(_Cancel caps-" +"lock-warning, _(You've got capslock on! chooser, _(_XDMCP Chooser " +"disconnect, _(D_isconnect halt, _(Shut_down language, _(_Language ok, _(_OK " +"quit, _(_Quit reboot, _(_Restart session, _(_Session suspend, _(Sus_pend " +"system, _(_Actions (Formerly S_ystem timed-label, _(User %u will login in %t " +"username-label, _(Username: welcome-label, _(Welcome to %n For example: " +"stock type=welcome-label Custom Widgetry Currently there is one item which " +"can be customizable and this is the list item. If you need to ask the user " +"extra things, such as to pick from a list of places to log into, or set of " +"custom login sessions you can setup the list item and add listitem children " +"that describe the choices. Each listitem must have an id and a text child. " +"The choice will be recorded in the file ServAuthDir/display.GreeterInfo as " +"list id=listitem id. For example suppose we are on display :0, ServAuthDir " +"is var/gdm and we have the following in the theme: item type=list id=custom-" +"config pos anchor=nw x=1 y=1 height=200 width=100 listitem id=foo textFoo/" +"text /listitem listitem id=bar textBar/text /listitem /item Then if the user " +"chooses 'Foo' then var/gdm/:0.GreeterInfo will contain: custom-config=foo " +"Accessibility 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. This feature allows the user to launch assistive " +"technologies at login time by means of special gestures from the standard " +"keyboard and from a keyboard, pointing device, or switch device attached to " +"the USB or PS/2 mouse port. It also allows the user to change the visual " +"appearance of the login UI before logging in, for instance to use a higher-" +"contrast color scheme for better visibility. GDM only supports accessibility " +"with the GTK+ Greeter, so the Greeter parameter in the GDM configuration " +"must be set to the GTK+ Greeter gdmlogin Accessibility Configuration 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. In order to allow users to " +"change the color and contrast scheme of the login dialog, make sure the " +"AllowThemeChange parameter in the GDM configuration is set to true. To " +"restrict user changes to the visual appearance to a subset of available " +"themes, the GtkThemesToAllow parameter in the GDM configuration can be set " +"to a list of acceptable themes separated by commas. For example: " +"GtkThemesToAllow=HighContrast,HighContrastInverse To enable the use of " +"assistive technologies such as the Onscreen Keyboard, Screen Reader, or " +"Magnifier, the AddGtkModules parameter in the GDM configuration must be " +"uncommented and set to true. Also the GtkModulesList parameter must be " +"uncommented and set as follows: GtkModulesList=gail:atk-bridge:" +"dwellmouselistener:keymouselistener 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. 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. 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. 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. 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. 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 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. 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. Accessibility Login Sound Configuration 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 /usr/bin/play (or /usr/bin/audioplay 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. Solaris Specific Features GDM supports a few features specific " +"to Solaris, as follows: GDM supports Solaris Auditing if running on Solaris " +"10 or higher. 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. Solaris supports the /etc/default/login interface, which affects the " +"DefaultPath, RootPath, PasswordRequired, and AllowRemoteRoot options as " +"described in the Configuration section. Example Configurations This section " +"has some example configurations that are useful for various setups. Terminal " +"Lab With One Server 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 xterminal " +"and let's call the server machine appserver. You install GDM on both. On " +"appserver you enable XDMCP, so you have [xdmcp] Enable=true If you want no " +"local screens here, you can then make the [servers] section empty. On the " +"xterminal you disable XDMCP (you don't want anyone to connect to the " +"xterminal really). You will add a server type perhaps called Terminal as " +"follows: [server-Terminal] name=Terminal server command=/usr/X11R6/bin/X -" +"terminate flexible=false handled=false This definition should in fact be " +"included in the standard configuration file. Notice that we made the handled " +"key false since we don't want GDM to handle this server localy. Also note " +"that we have not yet added the -query argument, you can add that here, or in " +"the [servers] section. We'll define our local servers as follows: [servers] " +"0=Terminal -query appserver This will run a direct XDMCP query to the server " +"named appserver. Terminal Lab With Two Or More Servers Suppose you want to " +"make a lab full of X terminals that all connect to some choice of servers. " +"For now let's make it appserverone and appservertwo. Again we'll call our " +"example X terminal server xterminal. The setup on both servers is the same " +"as with the case of one server in the previous section. You do not need to " +"explicitly enable indirect queries on the server since we'll run the " +"choosers locally on the X terminals. So on the xterminal you again disable " +"XDMCP. You will add a server type perhaps called Chooser as follows: [server-" +"Chooser] name=Chooser server command=/usr/X11R6/bin/X flexible=false " +"chooser=true And again this definition should in fact be included in the " +"standard configuration file. Notice that we made the chooser 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: [servers] 0=Chooser 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 [chooser] section you " +"would have: Hosts=appserverone,appservertwo and any other servers you wish " +"the users to be able to connect to. 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 appserver and on the X " +"terminals you'd have [servers] 0=Terminal -indirect appserver This way for " +"example you only have to maintain one Hosts entry. However as a disadvantage " +"then, the appserver must then always be available. So it's not good for " +"situations where you want to have serveral 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. " +"License This program is free software; you can redistribute it and/or modify " +"it under the terms of the GNU General Public License as published by the " +"Free Software Foundation; either version 2 of the License, or (at your " +"option) any later version. 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 GNU General " +"Public License for more details. A copy of the GNU General Public License is " +"included as an appendix to the GNOME Users Guide. You may also obtain a copy " +"of the GNU General Public License from the Free Software Foundation by " +"visiting their Web site or by writing to Free Software Foundation, Inc. 59 " +"Temple Place - Suite 330 Boston, MA 02111-1307 USA" msgstr "" -#: ../C/gdm.xml:1041 (para) -msgid "" -"When the user terminates his session, the <filename>PostSession</filename> " -"script will be run. Again operation is similar to <filename>Init</filename>, " -"<filename>PostLogin</filename> and <filename>PreSession</filename>. Again " -"the script will be run with root privileges, the slave daemon will block and " -"the <filename>$USER</filename> environment variable will contain the name of " -"the user who just logged out and <filename>$DISPLAY</filename> will be set " -"to the display the user used, however note that the X server for this " -"display may already be dead and so you shouldn't try to access it. Also " -"<filename>$X_SERVERS</filename> environmental variable is set and this " -"points to a fake generated X servers file for use with the sessreg " -"accounting application." -msgstr "" +#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2. +#: ../C/gdm.xml:0 (None) +msgid "translator-credits" +msgstr "Francisco Javier F. Serrador <serrador@cvs.gnome.org>, 2003, 2005." -#: ../C/gdm.xml:1056 (para) -msgid "" -"Note that the <filename>PostSession</filename> script will be run even when " -"the display fails to respond due to an I/O error or similar. Thus, there is " -"no guarantee that X applications will work during script execution." -msgstr "" +#~ msgid "Security" +#~ msgstr "Seguridad" -#: ../C/gdm.xml:1063 (para) -msgid "" -"Except for the <filename>Xsession</filename> script all of these scripts " -"will also have the environment variable <filename>$RUNNING_UNDER_GDM</" -"filename> set to <filename>yes</filename>, so that you could perhaps use " -"similar scripts for different display managers. The <filename>Xsession</" -"filename> will always have the <filename>$GDMSESSION</filename> set to the " -"basename of the session that the user chose to run without the <filename>." -"desktop</filename> extension. In addition <filename>$DESKTOP_SESSION</" -"filename> is also set to the same value and in fact this will also be set by " -"KDM in future versions." -msgstr "" +#~ msgid "The GDM User" +#~ msgstr "El usuario GDM" -#: ../C/gdm.xml:1077 (para) -msgid "" -"Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, " -"<filename>PreSession</filename> or <filename>PostSession</filename> scripts " -"are necessary and can be left out. The <filename>Xsession</filename> script " -"is however required as well as at least one session <filename>.desktop</" -"filename> file." -msgstr "" +#~ msgid "" +#~ "The GDM user, and group, which are normally just <command>gdm</command> " +#~ "should not be user or group of any particular privilege. The reason for " +#~ "using them is to have the user interface run as a user without privileges " +#~ "so that in the unlikely case that someone finds a weakness in the GUI, " +#~ "they cannot access root on the computer." +#~ msgstr "" +#~ "El usuario y el grupo GDM, que son normalmente <command>gdm</command> no " +#~ "deberían tener ningún privilegio. La razón para usarlos es tener el " +#~ "interfaz de usuario ejecutándose como un usuario sin privilegios para que " +#~ "en el improbable caso de que alguien encuentre una debilidad en el IGU, " +#~ "no puedan acceder como root a la computadora." -#: ../C/gdm.xml:1088 (title) -msgid "" -"The Configuration File - <filename>gdm.conf</filename> and <filename>gdm." -"conf-custom</filename>" -msgstr "" +#~ msgid "X Server Authentication Scheme" +#~ msgstr "Esquema de autenticación del servidor X" -#: ../C/gdm.xml:1091 (para) -msgid "" -"GDM uses two configuration files: <filename>gdm.conf</filename> and " -"<filename>gdm.conf-custom</filename>. The <filename>gdm.conf</filename> file " -"contains the default configuration choices for GDM, and should not be " -"modified by the user. The <filename>gdm.conf-custom</filename> file is where " -"users may specify their custom configuration choices. Configuration options " -"specified in the <filename>gdm.conf-custom</filename> file override the " -"values in the main <filename>gdm.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>gdm.conf</filename> file." -msgstr "" +#~ msgid "Firewall Security" +#~ msgstr "Seguridad con cortafuegos" -#: ../C/gdm.xml:1106 (para) -msgid "" -"Running the <command>gdmsetup</command> command will cause the <filename>gdm." -"conf-custom</filename> to be modified with the user's configuration choices." -msgstr "" +#~ msgid "GDM Security With NFS" +#~ msgstr "Seguridad de GDM con NFS" -#: ../C/gdm.xml:1112 (para) -msgid "" -"Previous to GDM 2.13.0.4 only the <filename>gdm.conf</filename> existed. If " -"upgrading to the new version of GDM, install will check to see if your " -"<filename>gdm.conf</filename> file is different than your <filename>factory-" -"gdm.conf</filename> file. If so, your <filename>gdm.conf</filename> file " -"will be automatically copied to <filename>gdm.conf-custom</filename> to " -"preserve your configuration changes." -msgstr "" +#~ msgid "XDMCP Security" +#~ msgstr "Seguridad de XDMCP" -#: ../C/gdm.xml:1122 (para) -msgid "" -"GDM may be configured to support system-wide configuration if built with the " -"<command>--with-configdir</command> option. This allows the <filename>gdm." -"conf</filename> file to be installed to a directory that can be mounted " -"across multiple-systems. The GDM --config option may instead be used to " -"specify a configuration file installed to another location. The GDM2 daemon " -"must be restarted to change the configuration file being used." -msgstr "" +#~ msgid "XDMCP Access Control" +#~ msgstr "Control de acceso XDMCP" -#: ../C/gdm.xml:1132 (para) -msgid "" -"Both configuration files are divided into sections each containing variables " -"that define the behavior for a specific part of the GDM suite. Refer to the " -"comments in the <filename>gdm.conf</filename> file for additional " -"information about each configuration setting." -msgstr "" +#~ msgid "" +#~ "XDMCP access control is done using TCP wrappers. It is possible to " +#~ "compile GDM without TCP wrappers however, so you should test your " +#~ "configuration and verify that they work." +#~ msgstr "" +#~ "El control de acceso XDMCP se realiza por medio de TCP wrappers. Es " +#~ "posible compilar GDM sin TCP wrappers sin embargo debería probar su " +#~ "configuración y verificar que funciona." -#: ../C/gdm.xml:1139 (para) -msgid "" -"The <filename>gdm.conf</filename> and <filename>gdm.conf-custom</filename> " -"files follow the standard <filename>.ini</filename> style configuration file " -"syntax. Keywords in brackets define sections, strings before an equal sign " -"(=) are variables and the data after equal sign represents their value. " -"Empty lines or lines starting with the hash mark (#) are ignored. The " -"graphical configurator will try to preserve both comments (lines with a hash " -"mark) and the overall structure of the file so you can intermix using the " -"GUI or hand editing the configuration file." -msgstr "" +#~ msgid "" +#~ "You should use the daemon name <command>gdm</command> in the " +#~ "<filename><etc>/hosts.allow</filename> and <filename><etc>" +#~ "hosts.deny</filename> files. For example to deny computers from " +#~ "<filename>.evil.domain</filename> from logging in, then add" +#~ msgstr "" +#~ "Debería usar el nombre del demonio <command>gdm</command> en el archivo " +#~ "<filename><etc>/hosts.allow</filename> y en el archivo " +#~ "<filename><etc>hosts.deny</filename>. Por ejemplo para denegar la " +#~ "entrada a equipos de <filename>.evil.domain</filename> , añada" -#: ../C/gdm.xml:1152 (title) -msgid "Daemon Configuration" -msgstr "Configuración del demonio" +#~ msgid "gdm: .evil.domain" +#~ msgstr "gdm: .dominio.maligno" -#: ../C/gdm.xml:1155 (title) -msgid "[daemon]" -msgstr "[daemon]" +#~ msgid "" +#~ "to <filename><etc>/hosts.deny</filename>. You may also need to add" +#~ msgstr "" +#~ "a <filename><etc>/hosts.deny</filename>. También necesitará añadir " -#: ../C/gdm.xml:1158 (term) -msgid "AddGtkModules" -msgstr "AddGtkModules" +#~ msgid "gdm: .your.domain" +#~ msgstr "gdm: .su.dominio" -#: ../C/gdm.xml:1160 (synopsis) -#, no-wrap -msgid "AddGtkModules=false" -msgstr "AddGtkModules=false" +#~ msgid "" +#~ "to your <filename><etc>/hosts.allow</filename> if you normally " +#~ "disallow all services from all hosts. See the <ulink type=\"help\" url=" +#~ "\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details." +#~ msgstr "" +#~ "a su <filename><etc>/hosts.allow</filename> si normalmente no " +#~ "permite todos los servicios desde todos los equipos. Vea la página del " +#~ "manual <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</" +#~ "ulink> para más detalles." -#: ../C/gdm.xml:1161 (para) -msgid "" -"If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</" -"command> to be launched with additional Gtk+ modules. This is useful when " -"extra features are required such as accessible login. Note that only " -"\"trusted\" modules should be used to minimize security issues." -msgstr "Si es true, entonces activa <command>gdmgreeter</command> o <command>gdmlogin</command> para que se lancen con módulos GTK+ adicionales. esto es útil cuando se requieren características extra como un inicio sesión accesible. Note que sólo deberían usarse los módulos «confiables» para minimizar las cuestiones de seguridad." +#~ msgid "Configuration" +#~ msgstr "Configuración" -#: ../C/gdm.xml:1168 (para) -msgid "" -"Usually this is used for accessibility modules. The modules which are loaded " -"are specified with the <filename>GtkModulesList</filename> key." -msgstr "Usualmente esto se usa para los módulos de accesibilidad. Los módulos que se cargan se especifican con la clave <filename>GtkModulesList</filename>." +#~ msgid "" +#~ "This section will cover the configuration of GDM and the format of the " +#~ "GDM configuration files. You can use the <command>gdmsetup</command> " +#~ "command to configure GDM, but the configuration application does not let " +#~ "you configure every aspect of GDM. The information in this section " +#~ "explains how to further configure GDM." +#~ msgstr "" +#~ "Esta sección cubrirá la configuración de GDM y el formato de los archivos " +#~ "de configuración de GDM. Puede usar el comando <command>gdmsetup</" +#~ "command> para configurar GDM, pero la aplicación de configuración no le " +#~ "deja configurar cada aspecto de GDM. La información de esta sección le " +#~ "explica en profundidad cómo configurar GDM." -#: ../C/gdm.xml:1177 (term) -msgid "AlwaysRestartServer" -msgstr "AlwaysRestartServer" +#~ msgid "" +#~ "The configuration files (especially the <filename>gdm.conf</filename> and " +#~ "<filename>gdm.conf-custom</filename> files) contains useful comments and " +#~ "examples, so read this for more information about changing your setup." +#~ msgstr "" +#~ "Los archivos de configuración (especialmente <filename>gdm.conf</" +#~ "filename> y <filename>gdm.conf-custom</filename>) contienen comentarios " +#~ "útiles y ejemplos, así que léalos para más información acerca de cambiar " +#~ "su configuración." -#: ../C/gdm.xml:1179 (synopsis) -#, no-wrap -msgid "AlwaysRestartServer=false" -msgstr "AlwaysRestartServer=false" +#~ msgid "" +#~ "Some keys in the configuration file as shipped are commented out while " +#~ "others are set. This is done so that defaults can be easily changed in " +#~ "the future for some keys. GDM considers lines that start with the \"#\" " +#~ "character a comment, and these lines will be ignored by GDM." +#~ msgstr "" +#~ "Algunas claves en el archivo de configuración se entregan comentadas " +#~ "mientras que otras están activadas. Esto se hace para que los " +#~ "predeterminados para algunas claves puedan cambiarse fácilmente en el " +#~ "futuro. GDM considera que las líneas que comienzan con el carácter «#» un " +#~ "comentario, y estas líneas se ignorarán." -#: ../C/gdm.xml:1180 (para) -msgid "" -"If true, then gdm never tries to reuse existing X servers by reinitializing " -"them. It will just kill the existing X server and start over. Normally, just " -"reinitializing is a nicer way to go but if the X server memory usage keeps " -"growing this may be a safer option. On Solaris, this value is always true, " -"and this configuration setting is ignored." -msgstr "" +#~ msgid "" +#~ "The <filename>gdm.conf</filename> file contains the default configuration " +#~ "choices for GDM, and should not be modified by the user. The " +#~ "<filename>gdm.conf-custom</filename> file is where users may specify " +#~ "their custom configuration choices. Configuration options specified in " +#~ "the <filename>gdm.conf-custom</filename> file override the values in the " +#~ "main <filename>gdm.conf</filename> file. Running the <command>gdmsetup</" +#~ "command> command will cause the <filename>gdm.conf-custom</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>gdm.conf</filename> file, so if " +#~ "using an older version of GDM just edit that file directly." +#~ msgstr "" +#~ "EL archivo <filename>gdm.conf</filename> contiene las opciones de " +#~ "configuración predeterminadas para GDM, y no debería ser modificado por " +#~ "el usuario. El archivo <filename>gdm.conf-custom</filename> es donde los " +#~ "usuarios pueden especificar sus opciones de configuración personalizadas. " +#~ "Las opciones de configuración especificadas en el archivo <filename>gdm." +#~ "conf-custom</filename> toman precedencia sobre los valores en el archivo " +#~ "principal <filename>gdm.conf</filename>. Ejecutar el comando " +#~ "<command>gdmsetup</command> hará que el archivo <filename>gdm.conf-" +#~ "custom</filename> se modifique con las opciones de configuración del " +#~ "usuario y hará que cualquier programa del IGU de GDM se actualice " +#~ "automáticamente. Anteriormente a la versión 2.13.0.4 GDM sólo soportaba " +#~ "el archivo <filename>gdm.conf</filename>, así que si está usando una " +#~ "versión más antigua de GDM tan sólo edite ese archivo directamente." -#: ../C/gdm.xml:1192 (term) -msgid "AutomaticLoginEnable" -msgstr "AutomaticLoginEnable" +#~ msgid "" +#~ "GDM may be configured to support system-wide configuration if built with " +#~ "the <command>--with-configdir</command> option. This allows the gdm.conf " +#~ "file to be installed to a directory that can be mounted across multiple-" +#~ "systems. The GDM --config option may also be used to specify the " +#~ "configuration file location. The GDM2 daemon must be restarted to change " +#~ "the configuration file being used." +#~ msgstr "" +#~ "GDM puede configurarse para soportar configuración para todo el sistema " +#~ "si se compila con la opción <command>--with-configdir</command>. Esto " +#~ "permite instalar el archivo gdm.conf en un directorio que pueda montarse " +#~ "a través de múltiples sistemas. La opción --config también podría usarse " +#~ "para especificar la ubicación del archivo de configuración. El demonio " +#~ "GDM2 debe reiniciarse para cambiar el archivo de configuración en uso." -#: ../C/gdm.xml:1194 (synopsis) -#, no-wrap -msgid "AutomaticLoginEnable=false" -msgstr "AutomaticLoginEnable=false" +#~ msgid "" +#~ "<filename>factory-gdm.conf</filename> is the configuration file as " +#~ "shipped with the daemon. This can be useful if you wish to revert to the " +#~ "default configuration." +#~ msgstr "" +#~ "<filename>factory-gdm.conf</filename> es el archivo de configuración tal " +#~ "como se empaqueta con el demonio. Esto puede ser útil si desea volver a " +#~ "la configuración predeterminada." -#: ../C/gdm.xml:1195 (para) -#, fuzzy -msgid "" -"If the user given in AutomaticLogin should be logged in upon first bootup. " -"No password will be asked. This is useful for single user workstations where " -"local console security is not an issue. Also could be useful for public " -"terminals, although there see <filename>TimedLogin</filename>." -msgstr "AutomaticLogin<filename> TimedLogin</filename>." - -#: ../C/gdm.xml:1206 (term) -msgid "AutomaticLogin" -msgstr "AutomaticLogin" - -#: ../C/gdm.xml:1208 (synopsis) -#, no-wrap -msgid "AutomaticLogin=" -msgstr "AutomaticLogin=" - -#: ../C/gdm.xml:1209 (para) -msgid "" -"This user should be automatically logged in on first bootup. " -"AutomaticLoginEnable must be true and this must be a valid user for this to " -"happen. \"root\" can never be autologged in however and gdm will just refuse " -"to do it even if you set it up." -msgstr "" +#~ msgid "" +#~ "The other GDM configuration files are located, by default, in the " +#~ "<filename><etc>/gdm/</filename> folder or its subdirectories. " +#~ "However, the location of all configuration files can be defined in the " +#~ "<filename>gdm.conf</filename> file, so the sysadmin may choose to locate " +#~ "these files in any location." +#~ msgstr "" +#~ "Los demás archivos de configuración de GDM se encuentran, por omisión, en " +#~ "la carpeta <filename><etc>/gdm/</filename> o sus subdirectorios. " +#~ "sin embargo, la ubicación de todos los archivos de configuración pueden " +#~ "definirse en el archivo <filename>gdm.conf</filename>, así que el " +#~ "administrador del sistema puede elegir situar estos archivos en cualquier " +#~ "lugar." + +#~ msgid "This is a listing of the config directory contents:" +#~ msgstr "" +#~ "Esta es una lista de los contenidos del directorio de configuración:" -#: ../C/gdm.xml:1217 (para) -msgid "The following control chars are recognized within the specified name:" -msgstr "Los siguientes caracteres de control se reconocen dentro del nombre especificado:" +#~ msgid "" +#~ "<filename>locale.alias</filename> is a file which looks much like the " +#~ "system locale alias but in fact it is not the same. These are the " +#~ "languages that are available on your system. All the languages are still " +#~ "tested to see if they actually exist before presenting them to the user." +#~ msgstr "" +#~ "<filename>locale.alias</filename> es un archivo que se parece mucho al " +#~ "archivo de alias regionales del sistema pero no es el mismo. Éstos son " +#~ "los idiomas que están disponibles en su sitema. Todos los idiomas además " +#~ "se prueban para ver si actualmente existen antes de presentárselos al " +#~ "usuario." -#: ../C/gdm.xml:1222 (para) ../C/gdm.xml:3209 -msgid "the `' character" -msgstr "" +#~ msgid "" +#~ "<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." +#~ msgstr "" +#~ "<filename>Xsession</filename> es un script que configura una sesión de " +#~ "usuario y después ejecuta la selección de sesión del usuario. Note que el " +#~ "script de sesión se inicia típicamente por el archivo <filename>desktop</" +#~ "filename> asociado con la sesión que el usuario a escogido. Algunas " +#~ "sesiones quizá inicien la sesión del usuario por medio de un mecanismo " +#~ "diferente que el script <filename>Xsession</filename> así que marque el " +#~ "<filename>desktop</filename> apropiado antes de asumir que el problema de " +#~ "inicio está causado por este archivo." -#: ../C/gdm.xml:1226 (para) -msgid "d display's name" -msgstr "d nombre del display" +#~ msgid "" +#~ "<filename>XKeepsCrashing</filename> is a script which gets run when the X " +#~ "server keeps crashing and we cannot recover. The shipped default script " +#~ "will work with most Linux distributions and can run the X configuration " +#~ "application provided the person on the console knows the root password." +#~ msgstr "" +#~ "<filename>XKeepsCrashing</filename> es un script que se ejecuta cuando el " +#~ "servidor X continúa colgándose y no se puede recuperar. El script " +#~ "predeterminado incluido funcionará con la mayoría de las distribuciones " +#~ "de Linux y puede ejecutar la aplicación de configuración de X siempre que " +#~ "la persona en la consola conozca la contraseña de root." -#: ../C/gdm.xml:1230 (para) -msgid "h display's hostname" -msgstr "h nombre de host del display" +#~ msgid "The Script Directories" +#~ msgstr "Los directorios de scripts" -#: ../C/gdm.xml:1234 (para) -msgid "" -"Alternatively, the name may end with a vertical bar |, the pipe symbol. The " -"name is then used as a application to execute which returns the desired " -"username on standard output. If an empty or otherwise invalid username is " -"returned, automatic login is not performed. This feature is typically used " -"when several remote displays are used as internet kiosks, with a specific " -"user to automatically login for each display." -msgstr "" +#~ msgid "" +#~ "In this section we will explain the <filename>Init</filename>, " +#~ "<filename>PostLogin</filename>, <filename>PreSession</filename> and " +#~ "<filename>PostSession</filename> directories as they are very similar." +#~ msgstr "" +#~ "En esta sección explicaremos los directorios <filename>Init</filename>, " +#~ "<filename>PostLogin</filename>, <filename>PreSession</filename> y " +#~ "<filename>PostSession</filename> ya que son muy similares." -#: ../C/gdm.xml:1247 (term) -msgid "BaseXsession" -msgstr "BaseXsession" +#~ msgid "Daemon Configuration" +#~ msgstr "Configuración del demonio" -#: ../C/gdm.xml:1249 (synopsis) -#, no-wrap -msgid "BaseXsession=<etc>/gdm/Xsession" -msgstr "BaseXsession=<etc>/gdm/Xsession" +#~ msgid "[daemon]" +#~ msgstr "[daemon]" -#: ../C/gdm.xml:1250 (para) -msgid "" -"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." -msgstr "" +#~ msgid "AddGtkModules" +#~ msgstr "AddGtkModules" -#: ../C/gdm.xml:1258 (para) -msgid "" -"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." -msgstr "" +#~ msgid "AddGtkModules=false" +#~ msgstr "AddGtkModules=false" -#: ../C/gdm.xml:1271 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</" +#~ "command> to be launched with additional Gtk+ modules. This is useful when " +#~ "extra features are required such as accessible login. Note that only " +#~ "\"trusted\" modules should be used to minimize security issues." +#~ msgstr "" +#~ "Si es true, entonces activa <command>gdmgreeter</command> o " +#~ "<command>gdmlogin</command> para que se lancen con módulos GTK+ " +#~ "adicionales. esto es útil cuando se requieren características extra como " +#~ "un inicio sesión accesible. Note que sólo deberían usarse los módulos " +#~ "«confiables» para minimizar las cuestiones de seguridad." -#: ../C/gdm.xml:1288 (term) -msgid "Chooser" -msgstr "Chooser" +#~ msgid "" +#~ "Usually this is used for accessibility modules. The modules which are " +#~ "loaded are specified with the <filename>GtkModulesList</filename> key." +#~ msgstr "" +#~ "Usualmente esto se usa para los módulos de accesibilidad. Los módulos que " +#~ "se cargan se especifican con la clave <filename>GtkModulesList</filename>." -#: ../C/gdm.xml:1290 (synopsis) -#, no-wrap -msgid "Chooser=<bin>/gdmchooser" -msgstr "Chooser=<bin>/gdmchooser" +#~ msgid "AlwaysRestartServer" +#~ msgstr "AlwaysRestartServer" -#: ../C/gdm.xml:1291 (para) -msgid "Full path and name of the chooser executable followed by optional arguments." -msgstr "Ruta completa y nombre del ejecutable del selector seguido de archumentos opcionales." +#~ msgid "AlwaysRestartServer=false" +#~ msgstr "AlwaysRestartServer=false" -#: ../C/gdm.xml:1299 (term) -msgid "Configurator" -msgstr "Configurator" +#~ msgid "AutomaticLoginEnable" +#~ msgstr "AutomaticLoginEnable" -#: ../C/gdm.xml:1301 (synopsis) -#, no-wrap -msgid "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" -msgstr "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" +#~ msgid "AutomaticLoginEnable=false" +#~ msgstr "AutomaticLoginEnable=false" -#: ../C/gdm.xml:1302 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename></filename> Configuración." - -#: ../C/gdm.xml:1314 (term) -msgid "ConsoleCannotHandle" -msgstr "ConsoleCannotHandle" - -#: ../C/gdm.xml:1316 (synopsis) -#, no-wrap -msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" -msgstr "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" - -#: ../C/gdm.xml:1317 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:1327 (term) -msgid "ConsoleNotify" -msgstr "ConsoleNotify" - -#: ../C/gdm.xml:1329 (synopsis) -#, no-wrap -msgid "ConsoleNotify=true" -msgstr "ConsoleNotify=true" - -#: ../C/gdm.xml:1330 (para) -msgid "" -"If false, gdm will not display a message dialog on the console when an error " -"happens." -msgstr "" - -#: ../C/gdm.xml:1338 (term) -msgid "DefaultPath" -msgstr "DefaultPath" - -#: ../C/gdm.xml:1340 (synopsis) -#, no-wrap -msgid "DefaultPath=/bin:/usr/bin:/usr/bin/X11:/usr/local/bin" -msgstr "DefaultPath=/bin:/usr/bin:/usr/bin/X11:/usr/local/bin" - -#: ../C/gdm.xml:1341 (para) -msgid "" -"Specifies the path which will be set in the user's session. This value will " -"be overridden with the value from /etc/default/login if it contains " -"\"ROOT=<pathname>\". If the /etc/default/login file exists, but " -"contains no value for ROOT, the value as defined in the GDM configuration " -"will be be used." -msgstr "" - -#: ../C/gdm.xml:1353 (term) -msgid "DefaultSession" -msgstr "DefaultSession" - -#: ../C/gdm.xml:1355 (synopsis) -#, no-wrap -msgid "DefaultSession=gnome.desktop" -msgstr "DefaultSession=gnome.desktop" - -#: ../C/gdm.xml:1356 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:1367 (term) -msgid "DisplayInitDir" -msgstr "DisplayInitDir" - -#: ../C/gdm.xml:1369 (synopsis) -#, no-wrap -msgid "DisplayInitDir=<etc>/gdm/Init" -msgstr "DisplayInitDir=<etc>/gdm/Init" - -#: ../C/gdm.xml:1370 (para) -msgid "" -"Directory containing the display init scripts. See the ``The Script " -"Directories'' section for more info." -msgstr "" +#~ msgid "" +#~ "If the user given in AutomaticLogin should be logged in upon first " +#~ "bootup. No password will be asked. This is useful for single user " +#~ "workstations where local console security is not an issue. Also could be " +#~ "useful for public terminals, although there see <filename>TimedLogin</" +#~ "filename>." +#~ msgstr "AutomaticLogin<filename> TimedLogin</filename>." -#: ../C/gdm.xml:1378 (term) -msgid "DisplayLastLogin" -msgstr "DisplayLastLogin" +#~ msgid "AutomaticLogin" +#~ msgstr "AutomaticLogin" -#: ../C/gdm.xml:1380 (synopsis) -#, no-wrap -msgid "DisplayLastLogin=true" -msgstr "DisplayLastLogin=true" +#~ msgid "AutomaticLogin=" +#~ msgstr "AutomaticLogin=" -#: ../C/gdm.xml:1381 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "The following control chars are recognized within the specified name:" +#~ msgstr "" +#~ "Los siguientes caracteres de control se reconocen dentro del nombre " +#~ "especificado:" -#: ../C/gdm.xml:1390 (para) -msgid "" -"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." -msgstr "" +#~ msgid "d display's name" +#~ msgstr "d nombre del display" -#: ../C/gdm.xml:1402 (term) -msgid "DoubleLoginWarning" -msgstr "DoubleLoginWarning" +#~ msgid "h display's hostname" +#~ msgstr "h nombre de host del display" -#: ../C/gdm.xml:1404 (synopsis) -#, no-wrap -msgid "DoubleLoginWarning=true" -msgstr "DoubleLoginWarning=true" +#~ msgid "BaseXsession" +#~ msgstr "BaseXsession" -#: ../C/gdm.xml:1405 (para) -msgid "" -"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." -msgstr "" +#~ msgid "BaseXsession=<etc>/gdm/Xsession" +#~ msgstr "BaseXsession=<etc>/gdm/Xsession" -#: ../C/gdm.xml:1415 (term) -msgid "DynamicXServers" -msgstr "DynamicXServers" +#~ msgid "Chooser" +#~ msgstr "Chooser" -#: ../C/gdm.xml:1417 (synopsis) -#, no-wrap -msgid "DynamicXServers=false" -msgstr "DynamicXServers=false" +#~ msgid "Chooser=<bin>/gdmchooser" +#~ msgstr "Chooser=<bin>/gdmchooser" -#: ../C/gdm.xml:1418 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "Full path and name of the chooser executable followed by optional " +#~ "arguments." +#~ msgstr "" +#~ "Ruta completa y nombre del ejecutable del selector seguido de archumentos " +#~ "opcionales." -#: ../C/gdm.xml:1430 (term) -msgid "FailsafeXServer" -msgstr "FailsafeXServer" +#~ msgid "Configurator" +#~ msgstr "Configurator" -#: ../C/gdm.xml:1432 (synopsis) -#, no-wrap -msgid "FailsafeXServer=" -msgstr "FailsafeXServer=" +#~ msgid "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" +#~ msgstr "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" -#: ../C/gdm.xml:1433 (para) #, fuzzy -msgid "" -"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." -msgstr "command<filename> XKeepsCrashing</filename>." - -#: ../C/gdm.xml:1444 (term) -msgid "FirstVT" -msgstr "FirstVT" - -#: ../C/gdm.xml:1446 (synopsis) -#, no-wrap -msgid "FirstVT=7" -msgstr "FirstVT=7" - -#: ../C/gdm.xml:1447 (para) -msgid "" -"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>." -msgstr "" - -#: ../C/gdm.xml:1457 (term) -msgid "FlexibleXServers" -msgstr "FlexibleXServers" - -#: ../C/gdm.xml:1459 (synopsis) -#, no-wrap -msgid "FlexibleXServers=5" -msgstr "FlexibleXServers=5" - -#: ../C/gdm.xml:1460 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:1471 (term) -msgid "FlexiReapDelayMinutes" -msgstr "FlexiReapDelayMinutes" - -#: ../C/gdm.xml:1473 (synopsis) -#, no-wrap -msgid "FlexiReapDelayMinutes=5" -msgstr "FlexiReapDelayMinutes=5" - -#: ../C/gdm.xml:1474 (para) -msgid "" -"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 behaviour set this " -"value to 0. This was added in version 2.5.90.0." -msgstr "" - -#: ../C/gdm.xml:1485 (term) -msgid "Greeter" -msgstr "Greeter" - -#: ../C/gdm.xml:1487 (synopsis) -#, no-wrap -msgid "Greeter=<bin>/gdmlogin" -msgstr "Greeter=<bin>/gdmlogin" - -#: ../C/gdm.xml:1488 (para) -msgid "" -"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>" -msgstr "" - -#: ../C/gdm.xml:1498 (term) -msgid "Group" -msgstr "Group" +#~ msgid "" +#~ "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." +#~ msgstr "<filename></filename> Configuración." -#: ../C/gdm.xml:1500 (synopsis) -#, no-wrap -msgid "Group=gdm" -msgstr "Group=gdm" +#~ msgid "ConsoleCannotHandle" +#~ msgstr "ConsoleCannotHandle" -#: ../C/gdm.xml:1501 (para) -msgid "" -"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." -msgstr "" +#~ msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" +#~ msgstr "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" -#: ../C/gdm.xml:1518 (term) -msgid "GtkModulesList" -msgstr "GtkModulesList" +#~ msgid "ConsoleNotify" +#~ msgstr "ConsoleNotify" -#: ../C/gdm.xml:1520 (synopsis) -#, no-wrap -msgid "GtkModulesList=module-1:module-2:..." -msgstr "GtkModulesList=module-1:module-2:..." +#~ msgid "ConsoleNotify=true" +#~ msgstr "ConsoleNotify=true" -#: ../C/gdm.xml:1521 (para) -msgid "" -"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." -msgstr "" +#~ msgid "DefaultPath" +#~ msgstr "DefaultPath" -#: ../C/gdm.xml:1532 (term) -msgid "HaltCommand" -msgstr "HaltCommand" +#~ msgid "DefaultPath=/bin:/usr/bin:/usr/bin/X11:/usr/local/bin" +#~ msgstr "DefaultPath=/bin:/usr/bin:/usr/bin/X11:/usr/local/bin" -#: ../C/gdm.xml:1534 (synopsis) -#, no-wrap -msgid "HaltCommand=/sbin/shutdown -h now" -msgstr "HaltCommand=/sbin/shutdown -h now" +#~ msgid "DefaultSession" +#~ msgstr "DefaultSession" -#: ../C/gdm.xml:1535 (para) -msgid "" -"Full path and arguments to command to be executed when user selects Shutdown " -"from the Actions menu. This can be a ';' separated list of commands to try. " -"If a value is missing, the shutdown command is not available. Note that the " -"default for this value is not empty so to disable shutdown you must set this " -"explicitly to an empty value." -msgstr "" +#~ msgid "DefaultSession=gnome.desktop" +#~ msgstr "DefaultSession=gnome.desktop" -#: ../C/gdm.xml:1547 (term) -msgid "KillInitClients" -msgstr "KillInitClients" +#~ msgid "DisplayInitDir" +#~ msgstr "DisplayInitDir" -#: ../C/gdm.xml:1549 (synopsis) -#, fuzzy, no-wrap -msgid "KillInitClients=true" -msgstr "KillInitClients=true" +#~ msgid "DisplayInitDir=<etc>/gdm/Init" +#~ msgstr "DisplayInitDir=<etc>/gdm/Init" -#: ../C/gdm.xml:1550 (para) -msgid "" -"Determines whether GDM should kill X clients started by the init scripts " -"when the user logs in." -msgstr "" +#~ msgid "DisplayLastLogin" +#~ msgstr "DisplayLastLogin" -#: ../C/gdm.xml:1558 (term) -msgid "LogDir" -msgstr "Directorio de registro" +#~ msgid "DisplayLastLogin=true" +#~ msgstr "DisplayLastLogin=true" -#: ../C/gdm.xml:1560 (synopsis) -#, no-wrap -msgid "LogDir=<var>/log/gdm" -msgstr "LogDir=<var>/log/gdm" +#~ msgid "DoubleLoginWarning" +#~ msgstr "DoubleLoginWarning" -#: ../C/gdm.xml:1561 (para) -#, fuzzy -msgid "" -"Directory containing the log files for the individual displays. By default " -"this is the same as the ServAuthDir." -msgstr "ServAuthDir." +#~ msgid "DoubleLoginWarning=true" +#~ msgstr "DoubleLoginWarning=true" -#: ../C/gdm.xml:1569 (term) -msgid "PidFile" -msgstr "PidFile" +#~ msgid "DynamicXServers" +#~ msgstr "DynamicXServers" -#: ../C/gdm.xml:1571 (synopsis) -#, no-wrap -msgid "PidFile=<var>/run/gdm.pid" -msgstr "PidFile=<var>/run/gdm.pid" +#~ msgid "DynamicXServers=false" +#~ msgstr "DynamicXServers=false" -#: ../C/gdm.xml:1572 (para) -msgid "Name of the file containing the <filename>gdm</filename> process id." -msgstr "" +#~ msgid "FailsafeXServer" +#~ msgstr "FailsafeXServer" -#: ../C/gdm.xml:1580 (term) -msgid "PrefetchProgram" -msgstr "" +#~ msgid "FailsafeXServer=" +#~ msgstr "FailsafeXServer=" -#: ../C/gdm.xml:1582 (synopsis) -#, no-wrap #, fuzzy -msgid "PrefetchProgram=command" -msgstr "command" - -#: ../C/gdm.xml:1583 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "command<filename> XKeepsCrashing</filename>." -#: ../C/gdm.xml:1594 (term) -msgid "PostLoginScriptDir" -msgstr "PostLoginScriptDir" +#~ msgid "FirstVT" +#~ msgstr "FirstVT" -#: ../C/gdm.xml:1596 (synopsis) -#, no-wrap -msgid "PostLoginScriptDir=<etc>/gdm/PostLogin" -msgstr "PostLoginScriptDir=<etc>/gdm/PostLogin" +#~ msgid "FirstVT=7" +#~ msgstr "FirstVT=7" -#: ../C/gdm.xml:1597 (para) -msgid "" -"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." -msgstr "" +#~ msgid "FlexibleXServers" +#~ msgstr "FlexibleXServers" -#: ../C/gdm.xml:1606 (term) -msgid "PostSessionScriptDir" -msgstr "PostSessionScriptDir" - -#: ../C/gdm.xml:1608 (synopsis) -#, no-wrap -msgid "PostSessionScriptDir=<etc>/gdm/PostSession" -msgstr "PostSessionScriptDir=<etc>/gdm/PostSession" - -#: ../C/gdm.xml:1609 (para) -msgid "" -"Directory containing the scripts run after the user logs out. See the ``The " -"Script Directories'' section for more info." -msgstr "" +#~ msgid "FlexibleXServers=5" +#~ msgstr "FlexibleXServers=5" -#: ../C/gdm.xml:1617 (term) -msgid "PreSessionScriptDir" -msgstr "PreSessionScriptDir" +#~ msgid "FlexiReapDelayMinutes" +#~ msgstr "FlexiReapDelayMinutes" -#: ../C/gdm.xml:1619 (synopsis) -#, no-wrap -msgid "PreSessionScriptDir=<etc>/gdm/PreSession" -msgstr "PreSessionScriptDir=<etc>/gdm/PreSession" +#~ msgid "FlexiReapDelayMinutes=5" +#~ msgstr "FlexiReapDelayMinutes=5" -#: ../C/gdm.xml:1620 (para) -msgid "" -"Directory containing the scripts run before the user logs in. See the ``The " -"Script Directories'' section for more info." -msgstr "" +#~ msgid "Greeter" +#~ msgstr "Greeter" -#: ../C/gdm.xml:1628 (term) -msgid "RebootCommand" -msgstr "RebootCommand" +#~ msgid "Greeter=<bin>/gdmlogin" +#~ msgstr "Greeter=<bin>/gdmlogin" -#: ../C/gdm.xml:1630 (synopsis) -#, no-wrap -msgid "RebootCommand=/sbin/shutdown -r now" -msgstr "RebootCommand=/sbin/shutdown -r now" +#~ msgid "Group" +#~ msgstr "Group" -#: ../C/gdm.xml:1631 (para) -msgid "" -"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." -msgstr "" +#~ msgid "Group=gdm" +#~ msgstr "Group=gdm" -#: ../C/gdm.xml:1643 (term) -msgid "RemoteGreeter" -msgstr "RemoteGreeter" +#~ msgid "GtkModulesList" +#~ msgstr "GtkModulesList" -#: ../C/gdm.xml:1645 (synopsis) -#, no-wrap -msgid "RemoteGreeter=<bin>/gdmlogin" -msgstr "RemoteGreeter=<bin>/gdmlogin" +#~ msgid "GtkModulesList=module-1:module-2:..." +#~ msgstr "GtkModulesList=module-1:module-2:..." -#: ../C/gdm.xml:1646 (para) -#, fuzzy -msgid "" -"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." -msgstr "nombre XDMCP Greeter<filename> Greeter</filename>." - -#: ../C/gdm.xml:1657 (term) -msgid "RootPath" -msgstr "RootPath" - -#: ../C/gdm.xml:1659 (synopsis) -#, no-wrap -msgid "RootPath=/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/local/bin" -msgstr "RootPath=/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/local/bin" - -#: ../C/gdm.xml:1660 (para) -msgid "" -"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 /etc/default/login if it contains " -"\"SUROOT=<pathname>\". If the /etc/default/login file exists, but " -"contains no value for SUROOT, the value as defined in the GDM configuration " -"will be used." -msgstr "" +#~ msgid "HaltCommand" +#~ msgstr "HaltCommand" -#: ../C/gdm.xml:1674 (term) -msgid "ServAuthDir" -msgstr "ServAuthDir" +#~ msgid "HaltCommand=/sbin/shutdown -h now" +#~ msgstr "HaltCommand=/sbin/shutdown -h now" -#: ../C/gdm.xml:1676 (synopsis) -#, no-wrap -msgid "ServAuthDir=<var>/gdm" -msgstr "ServAuthDir=<var>/gdm" +#~ msgid "KillInitClients" +#~ msgstr "KillInitClients" -#: ../C/gdm.xml:1677 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename></filename><filename></filename><filename> Group</filename><filename></filename>." - -#: ../C/gdm.xml:1699 (term) -msgid "SessionDesktopDir" -msgstr "SessionDesktopDir" - -#: ../C/gdm.xml:1701 (synopsis) -#, no-wrap -msgid "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:</usr/share>/xsessions/" -msgstr "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:</usr/share>/xsessions/" - -#: ../C/gdm.xml:1702 (para) -msgid "" -"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." -msgstr "" +#~ msgid "KillInitClients=true" +#~ msgstr "KillInitClients=true" -#: ../C/gdm.xml:1712 (term) -msgid "SoundProgram" -msgstr "SoundProgram" +#~ msgid "LogDir" +#~ msgstr "Directorio de registro" -#: ../C/gdm.xml:1714 (synopsis) -#, no-wrap -msgid "SoundProgram=/usr/bin/play" -msgstr "SoundProgram=/usr/bin/play" +#~ msgid "LogDir=<var>/log/gdm" +#~ msgstr "LogDir=<var>/log/gdm" -#: ../C/gdm.xml:1715 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:1725 (term) -msgid "StandardXServer" -msgstr "StandardXServer" - -#: ../C/gdm.xml:1727 (synopsis) -#, no-wrap -msgid "StandardXServer=/usr/X11R6/bin/X" -msgstr "StandardXServer=/usr/X11R6/bin/X" - -#: ../C/gdm.xml:1728 (para) #, fuzzy -msgid "" -"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." -msgstr "command." +#~ msgid "" +#~ "Directory containing the log files for the individual displays. By " +#~ "default this is the same as the ServAuthDir." +#~ msgstr "ServAuthDir." -#: ../C/gdm.xml:1739 (term) -msgid "SuspendCommand" -msgstr "SuspendCommand" +#~ msgid "PidFile" +#~ msgstr "PidFile" -#: ../C/gdm.xml:1741 (synopsis) -#, no-wrap -msgid "SuspendCommand=" -msgstr "SuspendCommand=" +#~ msgid "PidFile=<var>/run/gdm.pid" +#~ msgstr "PidFile=<var>/run/gdm.pid" -#: ../C/gdm.xml:1742 (para) #, fuzzy -msgid "" -"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." -msgstr "command." - -#: ../C/gdm.xml:1753 (term) -msgid "TimedLoginEnable" -msgstr "TimedLoginEnable" - -#: ../C/gdm.xml:1755 (synopsis) -#, no-wrap -msgid "TimedLoginEnable=false" -msgstr "TimedLoginEnable=false" - -#: ../C/gdm.xml:1756 (para) -msgid "" -"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." -msgstr "" +#~ msgid "PrefetchProgram=command" +#~ msgstr "command" -#: ../C/gdm.xml:1776 (term) -msgid "TimedLogin" -msgstr "TimedLogin" +#~ msgid "PostLoginScriptDir" +#~ msgstr "PostLoginScriptDir" -#: ../C/gdm.xml:1778 (synopsis) -#, no-wrap -msgid "TimedLogin=" -msgstr "TimedLogin=" +#~ msgid "PostLoginScriptDir=<etc>/gdm/PostLogin" +#~ msgstr "PostLoginScriptDir=<etc>/gdm/PostLogin" -#: ../C/gdm.xml:1779 (para) -msgid "" -"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." -msgstr "" +#~ msgid "PostSessionScriptDir" +#~ msgstr "PostSessionScriptDir" -#: ../C/gdm.xml:1791 (term) -msgid "TimedLoginDelay" -msgstr "TimedLoginDelay" +#~ msgid "PostSessionScriptDir=<etc>/gdm/PostSession" +#~ msgstr "PostSessionScriptDir=<etc>/gdm/PostSession" -#: ../C/gdm.xml:1793 (synopsis) -#, no-wrap -msgid "TimedLoginDelay=30" -msgstr "TimedLoginDelay=30" +#~ msgid "PreSessionScriptDir" +#~ msgstr "PreSessionScriptDir" -#: ../C/gdm.xml:1794 (para) -msgid "" -"This is the delay before the <filename>TimedLogin</filename> user will be " -"logged in. It must be greater then or equal to 10." -msgstr "Este es el retardo antes de que el usuario <filename> TimedLogin</filename> entre en la sesión. Debe ser mayor o igual a 10." +#~ msgid "PreSessionScriptDir=<etc>/gdm/PreSession" +#~ msgstr "PreSessionScriptDir=<etc>/gdm/PreSession" -#: ../C/gdm.xml:1802 (term) -msgid "User" -msgstr "User" +#~ msgid "RebootCommand" +#~ msgstr "RebootCommand" -#: ../C/gdm.xml:1804 (synopsis) -#, no-wrap -msgid "User=gdm" -msgstr "User=gdm" +#~ msgid "RebootCommand=/sbin/shutdown -r now" +#~ msgstr "RebootCommand=/sbin/shutdown -r now" -#: ../C/gdm.xml:1805 (para) -msgid "" -"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." -msgstr "" +#~ msgid "RemoteGreeter" +#~ msgstr "RemoteGreeter" -#: ../C/gdm.xml:1819 (term) -msgid "UserAuthDir" -msgstr "UserAuthDir" +#~ msgid "RemoteGreeter=<bin>/gdmlogin" +#~ msgstr "RemoteGreeter=<bin>/gdmlogin" -#: ../C/gdm.xml:1821 (synopsis) -#, no-wrap -msgid "UserAuthDir=" -msgstr "UserAuthDir=" +#, fuzzy +#~ msgid "" +#~ "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." +#~ msgstr "nombre XDMCP Greeter<filename> Greeter</filename>." -#: ../C/gdm.xml:1822 (para) -msgid "" -"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>." -msgstr "" +#~ msgid "RootPath" +#~ msgstr "RootPath" -#: ../C/gdm.xml:1829 (para) -msgid "" -"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." -msgstr "" +#~ msgid "RootPath=/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/local/bin" +#~ msgstr "RootPath=/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/local/bin" -#: ../C/gdm.xml:1842 (para) -msgid "" -"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." -msgstr "" +#~ msgid "ServAuthDir" +#~ msgstr "ServAuthDir" -#: ../C/gdm.xml:1853 (term) -msgid "UserAuthFBDir" -msgstr "UserAuthFBDir" +#~ msgid "ServAuthDir=<var>/gdm" +#~ msgstr "ServAuthDir=<var>/gdm" -#: ../C/gdm.xml:1855 (synopsis) -#, no-wrap -msgid "UserAuthFBDir=/tmp" -msgstr "UserAuthFBDir=/tmp" +#, fuzzy +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "<filename></filename><filename></filename><filename> Group</" +#~ "filename><filename></filename>." -#: ../C/gdm.xml:1856 (para) -msgid "" -"If GDM fails to update the user's <filename>.Xauthority</filename> file a " -"fallback cookie is created in this directory." -msgstr "" +#~ msgid "SessionDesktopDir" +#~ msgstr "SessionDesktopDir" -#: ../C/gdm.xml:1865 (term) -msgid "UserAuthFile" -msgstr "UserAuthFile" +#~ msgid "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:</usr/share>/xsessions/" +#~ msgstr "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:</usr/share>/xsessions/" -#: ../C/gdm.xml:1867 (synopsis) -#, no-wrap -msgid "UserAuthFile=.Xauthority" -msgstr "UserAuthFile=.Xauthority" +#~ msgid "SoundProgram" +#~ msgstr "SoundProgram" -#: ../C/gdm.xml:1868 (para) -msgid "Name of the file used for storing user cookies." -msgstr "" +#~ msgid "SoundProgram=/usr/bin/play" +#~ msgstr "SoundProgram=/usr/bin/play" -#: ../C/gdm.xml:1875 (term) -msgid "VTAllocation" -msgstr "VTAllocation" +#~ msgid "StandardXServer" +#~ msgstr "StandardXServer" -#: ../C/gdm.xml:1877 (synopsis) -#, no-wrap -msgid "VTAllocation=true" -msgstr "VTAllocation=true" +#~ msgid "StandardXServer=/usr/X11R6/bin/X" +#~ msgstr "StandardXServer=/usr/X11R6/bin/X" -#: ../C/gdm.xml:1878 (para) #, fuzzy -msgid "" -"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>." -msgstr "<filename> FirstVT</filename>." +#~ msgid "" +#~ "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." +#~ msgstr "command." -#: ../C/gdm.xml:1890 (term) -msgid "XKeepsCrashing" -msgstr "XKeepsCrashing" +#~ msgid "SuspendCommand" +#~ msgstr "SuspendCommand" -#: ../C/gdm.xml:1892 (synopsis) -#, no-wrap -msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" -msgstr "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" +#~ msgid "SuspendCommand=" +#~ msgstr "SuspendCommand=" -#: ../C/gdm.xml:1893 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename> XKeepsCrashing</filename>." - -#: ../C/gdm.xml:1902 (para) -msgid "" -"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." -msgstr "En caso de que esté configurado <filename> FailsafeXServer</filename>, ése se intentará primero, y este sólo se usará como un respaldo en el caso de que el servidor X se mantenga colgado." +#~ msgid "" +#~ "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." +#~ msgstr "command." -#: ../C/gdm.xml:1911 (term) -msgid "Xnest" -msgstr "Xnest" +#~ msgid "TimedLoginEnable" +#~ msgstr "TimedLoginEnable" -#: ../C/gdm.xml:1913 (synopsis) -#, no-wrap -msgid "Xnest=/usr/bin/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)" -msgstr "Xnest=/usr/bin/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)" +#~ msgid "TimedLoginEnable=false" +#~ msgstr "TimedLoginEnable=false" -#: ../C/gdm.xml:1914 (para) -msgid "" -"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." -msgstr "" +#~ msgid "TimedLogin" +#~ msgstr "TimedLogin" -#: ../C/gdm.xml:1928 (title) -msgid "Security Options" -msgstr "Opciones de seguridad" +#~ msgid "TimedLogin=" +#~ msgstr "TimedLogin=" -#: ../C/gdm.xml:1931 (title) -msgid "[security]" -msgstr "[security]" +#~ msgid "TimedLoginDelay" +#~ msgstr "TimedLoginDelay" -#: ../C/gdm.xml:1934 (term) -msgid "AllowRoot" -msgstr "AllowRoot" +#~ msgid "TimedLoginDelay=30" +#~ msgstr "TimedLoginDelay=30" -#: ../C/gdm.xml:1936 (synopsis) -#, no-wrap -msgid "AllowRoot=true" -msgstr "AllowRoot=true" +#~ msgid "" +#~ "This is the delay before the <filename>TimedLogin</filename> user will be " +#~ "logged in. It must be greater then or equal to 10." +#~ msgstr "" +#~ "Este es el retardo antes de que el usuario <filename> TimedLogin</" +#~ "filename> entre en la sesión. Debe ser mayor o igual a 10." -#: ../C/gdm.xml:1937 (para) -msgid "" -"Allow root (privileged user) to log in through GDM. Set this to false if you " -"want to disallow such logins." -msgstr "Permite al usuario root (usuario privilegiado) entrar a través de GDM. Establezca esta opción a false si quiere no permitir dichas entradas." +#~ msgid "User" +#~ msgstr "User" -#: ../C/gdm.xml:1941 (para) -msgid "" -"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." -msgstr "" +#~ msgid "User=gdm" +#~ msgstr "User=gdm" -#: ../C/gdm.xml:1951 (term) -msgid "AllowRemoteRoot" -msgstr "AllowRemoteRoot" +#~ msgid "UserAuthDir" +#~ msgstr "UserAuthDir" -#: ../C/gdm.xml:1953 (synopsis) -#, no-wrap -msgid "AllowRemoteRoot=false" -msgstr "AllowRemoteRoot=false" +#~ msgid "UserAuthDir=" +#~ msgstr "UserAuthDir=" -#: ../C/gdm.xml:1954 (para) -msgid "" -"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." -msgstr "" +#~ msgid "UserAuthFBDir" +#~ msgstr "UserAuthFBDir" -#: ../C/gdm.xml:1959 (para) -msgid "" -"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." -msgstr "" +#~ msgid "UserAuthFBDir=/tmp" +#~ msgstr "UserAuthFBDir=/tmp" -#: ../C/gdm.xml:1964 (para) -msgid "" -"This value will be overridden and set to false if the /etc/default/login " -"file exists and contains \"CONSOLE=/dev/login\", and set to true if the /etc/" -"default/login file exists and contains any other value or no value for " -"CONSOLE." -msgstr "" +#~ msgid "UserAuthFile" +#~ msgstr "UserAuthFile" -#: ../C/gdm.xml:1975 (term) -msgid "AllowRemoteAutoLogin" -msgstr "AllowRemoteAutoLogin" +#~ msgid "UserAuthFile=.Xauthority" +#~ msgstr "UserAuthFile=.Xauthority" -#: ../C/gdm.xml:1977 (synopsis) -#, no-wrap -msgid "AllowRemoteAutoLogin=false" -msgstr "AllowRemoteAutoLogin=false" +#~ msgid "VTAllocation" +#~ msgstr "VTAllocation" -#: ../C/gdm.xml:1978 (para) -msgid "" -"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." -msgstr "" +#~ msgid "VTAllocation=true" +#~ msgstr "VTAllocation=true" -#: ../C/gdm.xml:1984 (para) -msgid "Note that this can make a system quite insecure, and thus is off by default." -msgstr "" +#, fuzzy +#~ msgid "" +#~ "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>." +#~ msgstr "<filename> FirstVT</filename>." -#: ../C/gdm.xml:1992 (term) -msgid "CheckDirOwner" -msgstr "CheckDirOwner" +#~ msgid "XKeepsCrashing" +#~ msgstr "XKeepsCrashing" -#: ../C/gdm.xml:1994 (synopsis) -#, no-wrap -msgid "CheckDirOwner=true" -msgstr "CheckDirOwner=true" +#~ msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" +#~ msgstr "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" -#: ../C/gdm.xml:1995 (para) -msgid "" -"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." -msgstr "" +#, fuzzy +#~ msgid "" +#~ "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." +#~ msgstr "<filename> XKeepsCrashing</filename>." -#: ../C/gdm.xml:2009 (term) -msgid "DisallowTCP" -msgstr "DisallowTCP" +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "En caso de que esté configurado <filename> FailsafeXServer</filename>, " +#~ "ése se intentará primero, y este sólo se usará como un respaldo en el " +#~ "caso de que el servidor X se mantenga colgado." -#: ../C/gdm.xml:2011 (synopsis) -#, no-wrap -msgid "DisallowTCP=true" -msgstr "DisallowTCP=true" +#~ msgid "Xnest" +#~ msgstr "Xnest" -#: ../C/gdm.xml:2012 (para) -msgid "" -"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." -msgstr "" +#~ msgid "Xnest=/usr/bin/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)" +#~ msgstr "Xnest=/usr/bin/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)" -#: ../C/gdm.xml:2025 (term) -msgid "NeverPlaceCookiesOnNFS" -msgstr "NeverPlaceCookiesOnNFS" +#~ msgid "Security Options" +#~ msgstr "Opciones de seguridad" -#: ../C/gdm.xml:2027 (synopsis) -#, no-wrap -msgid "NeverPlaceCookiesOnNFS=true" -msgstr "NeverPlaceCookiesOnNFS=true" +#~ msgid "[security]" +#~ msgstr "[security]" -#: ../C/gdm.xml:2028 (para) -msgid "" -"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." -msgstr "" +#~ msgid "AllowRoot" +#~ msgstr "AllowRoot" -#: ../C/gdm.xml:2042 (term) -msgid "PasswordRequired" -msgstr "PasswordRequired" +#~ msgid "AllowRoot=true" +#~ msgstr "AllowRoot=true" -#: ../C/gdm.xml:2044 (synopsis) -#, no-wrap -msgid "PasswordRequired=false" -msgstr "PasswordRequired=false" +#~ msgid "" +#~ "Allow root (privileged user) to log in through GDM. Set this to false if " +#~ "you want to disallow such logins." +#~ msgstr "" +#~ "Permite al usuario root (usuario privilegiado) entrar a través de GDM. " +#~ "Establezca esta opción a false si quiere no permitir dichas entradas." -#: ../C/gdm.xml:2045 (para) -msgid "" -"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 /etc/default/login if it contains \"PASSREQ=" -"[YES|NO]\". If the /etc/default/login file exists, but contains no value for " -"PASSREQ, the value as defined in the GDM configuration will be used." -msgstr "" +#~ msgid "AllowRemoteRoot" +#~ msgstr "AllowRemoteRoot" -#: ../C/gdm.xml:2060 (term) -msgid "RelaxPermissions" -msgstr "RelaxPermissions" +#~ msgid "AllowRemoteRoot=false" +#~ msgstr "AllowRemoteRoot=false" -#: ../C/gdm.xml:2062 (synopsis) -#, no-wrap -msgid "RelaxPermissions=0" -msgstr "RelaxPermissions=0" +#~ msgid "AllowRemoteAutoLogin" +#~ msgstr "AllowRemoteAutoLogin" -#: ../C/gdm.xml:2063 (para) -msgid "" -"By default GDM ignores files and directories writable to other users than " -"the owner." -msgstr "" +#~ msgid "AllowRemoteAutoLogin=false" +#~ msgstr "AllowRemoteAutoLogin=false" -#: ../C/gdm.xml:2068 (para) -msgid "" -"Changing the value of RelaxPermissions makes it possible to alter this " -"behavior:" -msgstr "Cambiar el valor de RelaxPermissions hace posible alterar este comportamiento:" +#~ msgid "CheckDirOwner" +#~ msgstr "CheckDirOwner" -#: ../C/gdm.xml:2073 (para) -msgid "0 - Paranoia option. Only accepts user owned files and directories." -msgstr "" +#~ msgid "CheckDirOwner=true" +#~ msgstr "CheckDirOwner=true" -#: ../C/gdm.xml:2077 (para) -msgid "1 - Allow group writable files and directories." -msgstr "" +#~ msgid "DisallowTCP" +#~ msgstr "DisallowTCP" -#: ../C/gdm.xml:2080 (para) -msgid "2 - Allow world writable files and directories." -msgstr "" +#~ msgid "DisallowTCP=true" +#~ msgstr "DisallowTCP=true" -#: ../C/gdm.xml:2087 (term) -msgid "RetryDelay" -msgstr "RetryDelay" +#~ msgid "NeverPlaceCookiesOnNFS" +#~ msgstr "NeverPlaceCookiesOnNFS" -#: ../C/gdm.xml:2089 (synopsis) -#, no-wrap -msgid "RetryDelay=1" -msgstr "RetryDelay=1" +#~ msgid "NeverPlaceCookiesOnNFS=true" +#~ msgstr "NeverPlaceCookiesOnNFS=true" -#: ../C/gdm.xml:2090 (para) -msgid "" -"The number of seconds GDM should wait before reactivating the entry field " -"after a failed login." -msgstr "" +#~ msgid "PasswordRequired" +#~ msgstr "PasswordRequired" -#: ../C/gdm.xml:2098 (term) -msgid "UserMaxFile" -msgstr "UserMaxFile" +#~ msgid "PasswordRequired=false" +#~ msgstr "PasswordRequired=false" -#: ../C/gdm.xml:2100 (synopsis) -#, no-wrap -msgid "UserMaxFile=65536" -msgstr "UserMaxFile=65536" +#~ msgid "RelaxPermissions" +#~ msgstr "RelaxPermissions" -#: ../C/gdm.xml:2101 (para) -msgid "" -"GDM will refuse to read/write files bigger than this number (specified in " -"bytes)." -msgstr "GDM rechazará a leer/escribir archivos mayores que este número (especificado en bytes)." +#~ msgid "RelaxPermissions=0" +#~ msgstr "RelaxPermissions=0" -#: ../C/gdm.xml:2106 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "Changing the value of RelaxPermissions makes it possible to alter this " +#~ "behavior:" +#~ msgstr "" +#~ "Cambiar el valor de RelaxPermissions hace posible alterar este " +#~ "comportamiento:" -#: ../C/gdm.xml:2120 (title) -msgid "XDCMP Support" -msgstr "Soporte XDCMP" +#~ msgid "RetryDelay" +#~ msgstr "RetryDelay" -#: ../C/gdm.xml:2123 (title) -msgid "[xdmcp]" -msgstr "[xdmcp]" +#~ msgid "RetryDelay=1" +#~ msgstr "RetryDelay=1" -#: ../C/gdm.xml:2126 (term) -msgid "DisplaysPerHost" -msgstr "DisplaysPerHost" +#~ msgid "UserMaxFile" +#~ msgstr "UserMaxFile" -#: ../C/gdm.xml:2128 (synopsis) -#, no-wrap -msgid "DisplaysPerHost=1" -msgstr "DisplaysPerHost=1" +#~ msgid "UserMaxFile=65536" +#~ msgstr "UserMaxFile=65536" -#: ../C/gdm.xml:2129 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "GDM will refuse to read/write files bigger than this number (specified in " +#~ "bytes)." +#~ msgstr "" +#~ "GDM rechazará a leer/escribir archivos mayores que este número " +#~ "(especificado en bytes)." -#: ../C/gdm.xml:2137 (para) -msgid "" -"Note that the number of connections from the local computer is unlimited. " -"Only remote connections are limited by this number." -msgstr "" +#~ msgid "XDCMP Support" +#~ msgstr "Soporte XDCMP" -#: ../C/gdm.xml:2145 (term) ../C/gdm.xml:3397 -msgid "Enable" -msgstr "Enable" +#~ msgid "[xdmcp]" +#~ msgstr "[xdmcp]" -#: ../C/gdm.xml:2147 (synopsis) ../C/gdm.xml:3399 -#, no-wrap -msgid "Enable=false" -msgstr "Enable=false" +#~ msgid "DisplaysPerHost" +#~ msgstr "DisplaysPerHost" -#: ../C/gdm.xml:2148 (para) -msgid "" -"Setting this to true enables XDMCP support allowing remote displays/X " -"terminals to be managed by GDM." -msgstr "" +#~ msgid "DisplaysPerHost=1" +#~ msgstr "DisplaysPerHost=1" -#: ../C/gdm.xml:2153 (para) -msgid "" -"<filename>gdm</filename> listens for requests on UDP port 177. See the Port " -"option for more information." -msgstr "" +#~ msgid "Enable" +#~ msgstr "Enable" -#: ../C/gdm.xml:2158 (para) -msgid "" -"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>" -msgstr "" +#~ msgid "Enable=false" +#~ msgstr "Enable=false" -#: ../C/gdm.xml:2164 (para) #, fuzzy -msgid "" -"You should add <screen>gdm:.my.domain</screen> to your <filename><etc>/" -"hosts.allow</filename>, depending on your TCP Wrappers configuration. See " -"the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man " -"page for details." -msgstr "" -"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." +#~ msgid "" +#~ "You should add <screen>gdm:.my.domain</screen> to your <filename><" +#~ "etc>/hosts.allow</filename>, depending on your TCP Wrappers " +#~ "configuration. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts." +#~ "allow(5)</ulink> man page for details." +#~ msgstr "" +#~ "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." -#: ../C/gdm.xml:2173 (para) -msgid "" -"Please note that XDMCP is not a particularly secure protocol and that it is " -"a good idea to block UDP port 177 on your firewall unless you really need it." -msgstr "Note que XDMCP no es un protocolo particularmente seguro y que es una buena idea bloquear el puerto UDP 177 en su cortafuegos a no ser que realmente lo necesite." +#~ msgid "" +#~ "Please note that XDMCP is not a particularly secure protocol and that it " +#~ "is a good idea to block UDP port 177 on your firewall unless you really " +#~ "need it." +#~ msgstr "" +#~ "Note que XDMCP no es un protocolo particularmente seguro y que es una " +#~ "buena idea bloquear el puerto UDP 177 en su cortafuegos a no ser que " +#~ "realmente lo necesite." -#: ../C/gdm.xml:2182 (term) #, fuzzy -msgid "EnableProxy" -msgstr "TimedLoginEnable=false" - -#: ../C/gdm.xml:2184 (synopsis) -#, fuzzy, no-wrap -msgid "EnableProxy=false" -msgstr "EnableProxy=false" - -#: ../C/gdm.xml:2185 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:2192 (para) -msgid "" -"Note, however, that this mode will significantly increase the burden on the " -"machine hosting the XDMCP sessions" -msgstr "" - -#: ../C/gdm.xml:2196 (para) -msgid "" -"See the <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</" -"filename> options for further details on how to configure support for this " -"feature." -msgstr "" - -#: ../C/gdm.xml:2205 (term) -msgid "HonorIndirect" -msgstr "" - -#: ../C/gdm.xml:2207 (synopsis) -#, no-wrap -msgid "HonorIndirect=true" -msgstr "HonorIndirect=true" - -#: ../C/gdm.xml:2208 (para) -msgid "" -"Enables XDMCP INDIRECT choosing (i.e. remote execution of " -"<filename>gdmchooser</filename>) for X-terminals which don't supply their " -"own display browser." -msgstr "" - -#: ../C/gdm.xml:2217 (term) -msgid "MaxPending" -msgstr "MaxPending" - -#: ../C/gdm.xml:2219 (synopsis) -#, no-wrap -msgid "MaxPending=4" -msgstr "MaxPending=4" - -#: ../C/gdm.xml:2220 (para) -msgid "" -"To avoid denial of service attacks, GDM has fixed size queue of pending " -"connections. Only MaxPending displays can start at the same time." -msgstr "" - -#: ../C/gdm.xml:2226 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:2235 (term) -msgid "MaxPendingIndirect" -msgstr "MaxPendingIndirect" - -#: ../C/gdm.xml:2237 (synopsis) -#, no-wrap -msgid "MaxPendingIndirect=4" -msgstr "MaxPendingIndirect=4" - -#: ../C/gdm.xml:2238 (para) -msgid "" -"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." -msgstr "" +#~ msgid "EnableProxy" +#~ msgstr "TimedLoginEnable=false" -#: ../C/gdm.xml:2248 (term) -msgid "MaxSessions" -msgstr "MaxSessions" - -#: ../C/gdm.xml:2250 (synopsis) -#, no-wrap -msgid "MaxSessions=16" -msgstr "MaxSessions=16" - -#: ../C/gdm.xml:2251 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:2260 (term) -msgid "MaxWait" -msgstr "MaxWait" - -#: ../C/gdm.xml:2262 (synopsis) -#, no-wrap -msgid "MaxWait=30" -msgstr "MaxWait=30" - -#: ../C/gdm.xml:2263 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:2269 (para) -msgid "" -"GDM will then place the session id in the pending queue waiting for the " -"display to respond with a MANAGE request." -msgstr "" - -#: ../C/gdm.xml:2274 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:2283 (term) -msgid "MaxWaitIndirect" -msgstr "MaxWaitIndirect" - -#: ../C/gdm.xml:2285 (synopsis) -#, no-wrap -msgid "MaxWaitIndirect=30" -msgstr "MaxWaitIndirect=30" +#, fuzzy +#~ msgid "EnableProxy=false" +#~ msgstr "EnableProxy=false" -#: ../C/gdm.xml:2286 (para) -msgid "" -"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>." -msgstr "" +#~ msgid "HonorIndirect=true" +#~ msgstr "HonorIndirect=true" -#: ../C/gdm.xml:2300 (term) -msgid "Port" -msgstr "Port" +#~ msgid "MaxPending" +#~ msgstr "MaxPending" -#: ../C/gdm.xml:2302 (synopsis) -#, no-wrap -msgid "Port=177" -msgstr "Port=177" +#~ msgid "MaxPending=4" +#~ msgstr "MaxPending=4" -#: ../C/gdm.xml:2303 (para) -msgid "" -"The UDP port number <filename>gdm</filename> should listen to for XDMCP " -"requests. Don't change this unless you know what you are doing." -msgstr "" +#~ msgid "MaxPendingIndirect" +#~ msgstr "MaxPendingIndirect" -#: ../C/gdm.xml:2312 (term) -msgid "PingIntervalSeconds" -msgstr "PingIntervalSeconds" +#~ msgid "MaxPendingIndirect=4" +#~ msgstr "MaxPendingIndirect=4" -#: ../C/gdm.xml:2314 (synopsis) -#, no-wrap -msgid "PingIntervalSeconds=15" -msgstr "PingIntervalSeconds=15" +#~ msgid "MaxSessions" +#~ msgstr "MaxSessions" -#: ../C/gdm.xml:2315 (para) -msgid "" -"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." -msgstr "" +#~ msgid "MaxSessions=16" +#~ msgstr "MaxSessions=16" -#: ../C/gdm.xml:2323 (para) -msgid "" -"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." -msgstr "" +#~ msgid "MaxWait" +#~ msgstr "MaxWait" -#: ../C/gdm.xml:2336 (term) -msgid "ProxyReconnect" -msgstr "ProxyReconnect" +#~ msgid "MaxWait=30" +#~ msgstr "MaxWait=30" -#: ../C/gdm.xml:2338 (synopsis) -#, no-wrap -msgid "FlexiProxyReconnect=" -msgstr "FlexiProxyReconnect=" +#~ msgid "MaxWaitIndirect" +#~ msgstr "MaxWaitIndirect" -#: ../C/gdm.xml:2339 (para) -msgid "" -"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." -msgstr "" +#~ msgid "MaxWaitIndirect=30" +#~ msgstr "MaxWaitIndirect=30" -#: ../C/gdm.xml:2345 (para) -msgid "" -"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." -msgstr "" +#~ msgid "Port" +#~ msgstr "Port" -#: ../C/gdm.xml:2352 (para) -msgid "" -"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." -msgstr "" +#~ msgid "Port=177" +#~ msgstr "Port=177" -#: ../C/gdm.xml:2361 (term) -msgid "ProxyXServer" -msgstr "ProxyXServer" +#~ msgid "PingIntervalSeconds" +#~ msgstr "PingIntervalSeconds" -#: ../C/gdm.xml:2363 (synopsis) -#, no-wrap -msgid "ProxyXServer=" -msgstr "ProxyXServer=" +#~ msgid "PingIntervalSeconds=15" +#~ msgstr "PingIntervalSeconds=15" -#: ../C/gdm.xml:2364 (para) -msgid "" -"The X server command line for a XDMCP proxy. Any nested X server like Xnest, " -"Xephr or Xdmx should work fairly well." -msgstr "" +#~ msgid "ProxyReconnect" +#~ msgstr "ProxyReconnect" -#: ../C/gdm.xml:2372 (term) -msgid "Willing" -msgstr "" +#~ msgid "FlexiProxyReconnect=" +#~ msgstr "FlexiProxyReconnect=" -#: ../C/gdm.xml:2374 (synopsis) -#, fuzzy, no-wrap -msgid "Willing=<etc>/gdm/Xwilling" -msgstr "Willing=<etc>/gdm/Xwilling" +#~ msgid "ProxyXServer" +#~ msgstr "ProxyXServer" -#: ../C/gdm.xml:2375 (para) -msgid "" -"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." -msgstr "" +#~ msgid "ProxyXServer=" +#~ msgstr "ProxyXServer=" -#: ../C/gdm.xml:2394 (title) #, fuzzy -msgid "Common GUI Configuration Options" -msgstr "Opciones comunes de configuración a través del IGU" +#~ msgid "Willing=<etc>/gdm/Xwilling" +#~ msgstr "Willing=<etc>/gdm/Xwilling" -#: ../C/gdm.xml:2397 (title) -msgid "[gui]" -msgstr "[gui]" - -#: ../C/gdm.xml:2400 (term) #, fuzzy -msgid "AllowGtkThemeChange" -msgstr "AllowGtkThemeChange" +#~ msgid "Common GUI Configuration Options" +#~ msgstr "Opciones comunes de configuración a través del IGU" -#: ../C/gdm.xml:2402 (synopsis) -#, no-wrap -msgid "AllowGtkThemeChange=true" -msgstr "AllowGtkThemeChange=true" +#~ msgid "[gui]" +#~ msgstr "[gui]" -#: ../C/gdm.xml:2403 (para) -msgid "" -"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." -msgstr "" +#, fuzzy +#~ msgid "AllowGtkThemeChange" +#~ msgstr "AllowGtkThemeChange" -#: ../C/gdm.xml:2415 (term) -msgid "GtkRC" -msgstr "GtkRC" +#~ msgid "AllowGtkThemeChange=true" +#~ msgstr "AllowGtkThemeChange=true" -#: ../C/gdm.xml:2417 (synopsis) -#, no-wrap -msgid "GtkRC=" -msgstr "GtkRC=" +#~ msgid "GtkRC" +#~ msgstr "GtkRC" -#: ../C/gdm.xml:2418 (para) -msgid "" -"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." -msgstr "" +#~ msgid "GtkRC=" +#~ msgstr "GtkRC=" -#: ../C/gdm.xml:2427 (term) #, fuzzy -msgid "GtkTheme" -msgstr "GtkTheme" - -#: ../C/gdm.xml:2429 (synopsis) -#, no-wrap -msgid "GtkTheme=Default" -msgstr "GtkTheme=Default" - -#: ../C/gdm.xml:2430 (para) -msgid "" -"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." -msgstr "" +#~ msgid "GtkTheme" +#~ msgstr "GtkTheme" -#: ../C/gdm.xml:2439 (term) -msgid "GtkThemesToAllow" -msgstr "GtkThemesToAllow" +#~ msgid "GtkTheme=Default" +#~ msgstr "GtkTheme=Default" -#: ../C/gdm.xml:2441 (synopsis) -#, no-wrap -msgid "GtkThemesToAllow=all" -msgstr "GtkThemesToAllow=all" +#~ msgid "GtkThemesToAllow" +#~ msgstr "GtkThemesToAllow" -#: ../C/gdm.xml:2442 (para) -msgid "" -"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." -msgstr "" +#~ msgid "GtkThemesToAllow=all" +#~ msgstr "GtkThemesToAllow=all" -#: ../C/gdm.xml:2454 (term) #, fuzzy -msgid "MaxIconWidth" -msgstr "MaxIconWidth" +#~ msgid "MaxIconWidth" +#~ msgstr "MaxIconWidth" -#: ../C/gdm.xml:2456 (synopsis) -#, no-wrap #, fuzzy -msgid "MaxIconWidth=128" -msgstr "MaxIconWidth=128" +#~ msgid "MaxIconWidth=128" +#~ msgstr "MaxIconWidth=128" -#: ../C/gdm.xml:2457 (para) #, fuzzy -msgid "" -"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." -msgstr "XDMCP chooser." +#~ msgid "" +#~ "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." +#~ msgstr "XDMCP chooser." -#: ../C/gdm.xml:2466 (term) #, fuzzy -msgid "MaxIconHeight" -msgstr "MaxIconHeight" +#~ msgid "MaxIconHeight" +#~ msgstr "MaxIconHeight" -#: ../C/gdm.xml:2468 (synopsis) -#, no-wrap #, fuzzy -msgid "MaxIconHeight=128" -msgstr "MaxIconHeight=128" - -#: ../C/gdm.xml:2469 (para) -msgid "" -"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." -msgstr "" +#~ msgid "MaxIconHeight=128" +#~ msgstr "MaxIconHeight=128" -#: ../C/gdm.xml:2482 (title) -msgid "Greeter Configuration" -msgstr "Configuración del interfaz" +#~ msgid "Greeter Configuration" +#~ msgstr "Configuración del interfaz" -#: ../C/gdm.xml:2485 (title) -msgid "[greeter]" -msgstr "[greeter]" +#~ msgid "[greeter]" +#~ msgstr "[greeter]" -#: ../C/gdm.xml:2488 (term) -msgid "BackgroundColor" -msgstr "BackgroundColor" +#~ msgid "BackgroundColor" +#~ msgstr "BackgroundColor" -#: ../C/gdm.xml:2490 (synopsis) -#, fuzzy, no-wrap -msgid "BackgroundColor=#76848F" -msgstr "BackgroundColor=#76848F" +#, fuzzy +#~ msgid "BackgroundColor=#76848F" +#~ msgstr "BackgroundColor=#76848F" -#: ../C/gdm.xml:2491 (para) #, fuzzy -msgid "" -"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." -msgstr "BackgroundType BackgroundRemoteOnlyColor Greeter." - -#: ../C/gdm.xml:2502 (term) -msgid "BackgroundProgramInitialDelay" -msgstr "BackgroundProgramInitialDelay" - -#: ../C/gdm.xml:2504 (synopsis) -#, no-wrap -msgid "BackgroundProgramInitialDelay=30" -msgstr "BackgroundProgramInitialDelay=30" - -#: ../C/gdm.xml:2505 (para) -msgid "" -"The background application will be started after at least that many seconds " -"of inactivity." -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "BackgroundType BackgroundRemoteOnlyColor Greeter." -#: ../C/gdm.xml:2513 (term) -msgid "RestartBackgroundProgram" -msgstr "RestartBackgroundProgram" +#~ msgid "BackgroundProgramInitialDelay" +#~ msgstr "BackgroundProgramInitialDelay" -#: ../C/gdm.xml:2515 (synopsis) -#, no-wrap -msgid "RestartBackgroundProgram=true" -msgstr "RestartBackgroundProgram=true" +#~ msgid "BackgroundProgramInitialDelay=30" +#~ msgstr "BackgroundProgramInitialDelay=30" -#: ../C/gdm.xml:2516 (para) -msgid "" -"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." -msgstr "" +#~ msgid "RestartBackgroundProgram" +#~ msgstr "RestartBackgroundProgram" -#: ../C/gdm.xml:2526 (term) -msgid "BackgroundProgramRestartDelay" -msgstr "BackgroundProgramRestartDelay" +#~ msgid "RestartBackgroundProgram=true" +#~ msgstr "RestartBackgroundProgram=true" -#: ../C/gdm.xml:2528 (synopsis) -#, no-wrap -msgid "BackgroundProgramRestartDelay=30" -msgstr "BackgroundProgramRestartDelay=30" +#~ msgid "BackgroundProgramRestartDelay" +#~ msgstr "BackgroundProgramRestartDelay" -#: ../C/gdm.xml:2529 (para) -msgid "" -"The background application will be restarted after at least that many " -"seconds of inactivity." -msgstr "" +#~ msgid "BackgroundProgramRestartDelay=30" +#~ msgstr "BackgroundProgramRestartDelay=30" -#: ../C/gdm.xml:2537 (term) -msgid "BackgroundImage" -msgstr "BackgroundImage" +#~ msgid "BackgroundImage" +#~ msgstr "BackgroundImage" -#: ../C/gdm.xml:2539 (synopsis) -#, no-wrap -msgid "BackgroundImage=somefile.png" -msgstr "BackgroundImage=somefile.png" +#~ msgid "BackgroundImage=somefile.png" +#~ msgstr "BackgroundImage=somefile.png" -#: ../C/gdm.xml:2540 (para) -msgid "" -"If the BackgroundType is 1, then display this file as the background in the " -"greeter. This only affects the GTK+ Greeter." -msgstr "" +#~ msgid "BackgroundProgram" +#~ msgstr "BackgroundProgram" -#: ../C/gdm.xml:2549 (term) -msgid "BackgroundProgram" -msgstr "BackgroundProgram" +#~ msgid "BackgroundProgram=/usr/bin/xeyes" +#~ msgstr "BackgroundProgram=/usr/bin/xeyes" -#: ../C/gdm.xml:2551 (synopsis) -#, no-wrap -msgid "BackgroundProgram=/usr/bin/xeyes" -msgstr "BackgroundProgram=/usr/bin/xeyes" - -#: ../C/gdm.xml:2552 (para) #, fuzzy -msgid "" -"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." -msgstr "command Greeter." - -#: ../C/gdm.xml:2564 (term) -msgid "BackgroundRemoteOnlyColor" -msgstr "BackgroundRemoteOnlyColor" - -#: ../C/gdm.xml:2566 (synopsis) -#, no-wrap -msgid "BackgroundRemoteOnlyColor=true" -msgstr "BackgroundRemoteOnlyColor=true" - -#: ../C/gdm.xml:2567 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "command Greeter." -#: ../C/gdm.xml:2577 (term) -msgid "BackgroundScaleToFit" -msgstr "BackgroundScaleToFit" +#~ msgid "BackgroundRemoteOnlyColor" +#~ msgstr "BackgroundRemoteOnlyColor" -#: ../C/gdm.xml:2579 (synopsis) -#, no-wrap -msgid "BackgroundScaleToFit=true" -msgstr "BackgroundScaleToFit=true" +#~ msgid "BackgroundRemoteOnlyColor=true" +#~ msgstr "BackgroundRemoteOnlyColor=true" -#: ../C/gdm.xml:2580 (para) -#, fuzzy -msgid "Scale background image to fit the screen. This only affects the GTK+ Greeter." -msgstr "Greeter." +#~ msgid "BackgroundScaleToFit" +#~ msgstr "BackgroundScaleToFit" -#: ../C/gdm.xml:2588 (term) -msgid "BackgroundType" -msgstr "BackgroundType" +#~ msgid "BackgroundScaleToFit=true" +#~ msgstr "BackgroundScaleToFit=true" -#: ../C/gdm.xml:2590 (synopsis) -#, no-wrap -msgid "BackgroundType=2" -msgstr "BackgroundType=2" +#, fuzzy +#~ msgid "" +#~ "Scale background image to fit the screen. This only affects the GTK+ " +#~ "Greeter." +#~ msgstr "Greeter." -#: ../C/gdm.xml:2591 (para) -msgid "" -"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." -msgstr "El tipo de fondo a establecer. 0 es ninguno, 1 es imagen y color, 2 es color y 3 es imagen. Esto sólo afecta al interfaz GTK+." +#~ msgid "BackgroundType" +#~ msgstr "BackgroundType" -#: ../C/gdm.xml:2599 (term) -msgid "Browser" -msgstr "Browser" +#~ msgid "BackgroundType=2" +#~ msgstr "BackgroundType=2" -#: ../C/gdm.xml:2601 (synopsis) -#, no-wrap -msgid "Browser=true" -msgstr "Browser=true" +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "El tipo de fondo a establecer. 0 es ninguno, 1 es imagen y color, 2 es " +#~ "color y 3 es imagen. Esto sólo afecta al interfaz GTK+." -#: ../C/gdm.xml:2602 (para) -msgid "" -"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" -msgstr "" +#~ msgid "Browser" +#~ msgstr "Browser" -#: ../C/gdm.xml:2613 (term) -msgid "ChooserButton" -msgstr "ChooserButton" +#~ msgid "Browser=true" +#~ msgstr "Browser=true" -#: ../C/gdm.xml:2615 (synopsis) -#, no-wrap -msgid "ChooserButton=true" -msgstr "ChooserButton=true" +#~ msgid "ChooserButton" +#~ msgstr "ChooserButton" -#: ../C/gdm.xml:2616 (para) -#, fuzzy -msgid "" -"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." -msgstr "chooser chooser XDMCP." +#~ msgid "ChooserButton=true" +#~ msgstr "ChooserButton=true" -#: ../C/gdm.xml:2625 (term) #, fuzzy -msgid "ConfigAvailable" -msgstr "TimedLoginEnable=false" - -#: ../C/gdm.xml:2627 (synopsis) -#, fuzzy, no-wrap -msgid "ConfigAvailable=false" -msgstr "ConfigAvailable=false" +#~ msgid "" +#~ "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." +#~ msgstr "chooser chooser XDMCP." -#: ../C/gdm.xml:2628 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename> Configurator</filename>." +#~ msgid "ConfigAvailable" +#~ msgstr "TimedLoginEnable=false" -#: ../C/gdm.xml:2640 (term) #, fuzzy -msgid "DefaultFace" -msgstr "DefaultFace" +#~ msgid "ConfigAvailable=false" +#~ msgstr "ConfigAvailable=false" -#: ../C/gdm.xml:2642 (synopsis) -#, no-wrap #, fuzzy -msgid "DefaultFace=<share>/pixmaps/nophoto.png" -msgstr "DefaultFace=<share>/pixmaps/nophoto.png" +#~ msgid "" +#~ "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." +#~ msgstr "<filename> Configurator</filename>." -#: ../C/gdm.xml:2643 (para) #, fuzzy -msgid "" -"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, the image " -"specified by <filename>DefaultFace</filename> will be used. The image must " -"be in an gdk-pixbuf supported format and the file must be readable to the " -"GDM user." -msgstr "" -"Si un usuario no tiene una imagen de rostro definida, GDM usará el icono " -"\"stock_person\" definido en el tema GTK+ actual. Si dicha imagen no está " -"definida, entonces usará la imagen especificada en la opción de " -"configuración <filename>DefaultFace</filename>. La imagen debe estar en un formato soportado por " -"gdk-pixbuf y el archivo debe poderlo leer el usuario de GDM." +#~ msgid "DefaultFace" +#~ msgstr "DefaultFace" -#: ../C/gdm.xml:2655 (term) #, fuzzy -msgid "Include" -msgstr "Include" +#~ msgid "DefaultFace=<share>/pixmaps/nophoto.png" +#~ msgstr "DefaultFace=<share>/pixmaps/nophoto.png" -#: ../C/gdm.xml:2657 (synopsis) -#, no-wrap #, fuzzy -msgid "Include=" -msgstr "Include=" +#~ msgid "" +#~ "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, the " +#~ "image specified by <filename>DefaultFace</filename> will be used. The " +#~ "image must be in an gdk-pixbuf supported format and the file must be " +#~ "readable to the GDM user." +#~ msgstr "" +#~ "Si un usuario no tiene una imagen de rostro definida, GDM usará el icono " +#~ "\"stock_person\" definido en el tema GTK+ actual. Si dicha imagen no está " +#~ "definida, entonces usará la imagen especificada en la opción de " +#~ "configuración <filename>DefaultFace</filename>. La imagen debe estar en " +#~ "un formato soportado por gdk-pixbuf y el archivo debe poderlo leer el " +#~ "usuario de GDM." -#: ../C/gdm.xml:2658 (para) #, fuzzy -msgid "" -"Comma separated list of users to be included in the face browser and in the " -"<command>gdmsetup</command> selection list for Automatic/Timed login. See " -"also <filename>Exclude</filename>, <filename>IncludeAll</filename>, and " -"<filename>MinimalUID</filename>." -msgstr "" -"Lista separada por comas de usuarios que serán incluidos en el visor de rostros y en la lista de selección de " -"<command>gdmsetup</command> para el inicio de sesión automático/temporizado. Vea además <filename>Exclude</filename>, <filename>IncludeAll</filename>, y " -"<filename>MinimalUID</filename>." +#~ msgid "Include" +#~ msgstr "Include" -#: ../C/gdm.xml:2670 (term) #, fuzzy -msgid "Exclude" -msgstr "Exclude" +#~ msgid "Include=" +#~ msgstr "Include=" -#: ../C/gdm.xml:2672 (synopsis) -#, no-wrap #, fuzzy -msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." -msgstr "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." +#~ msgid "" +#~ "Comma separated list of users to be included in the face browser and in " +#~ "the <command>gdmsetup</command> selection list for Automatic/Timed login. " +#~ "See also <filename>Exclude</filename>, <filename>IncludeAll</filename>, " +#~ "and <filename>MinimalUID</filename>." +#~ msgstr "" +#~ "Lista separada por comas de usuarios que serán incluidos en el visor de " +#~ "rostros y en la lista de selección de <command>gdmsetup</command> para el " +#~ "inicio de sesión automático/temporizado. Vea además <filename>Exclude</" +#~ "filename>, <filename>IncludeAll</filename>, y <filename>MinimalUID</" +#~ "filename>." -#: ../C/gdm.xml:2673 (para) #, fuzzy -msgid "" -"Comma separated list of users to be excluded from the face browser and from " -"the <command>gdmsetup</command> selection list for Automatic/Timed login. " -"Excluded users will still be able to log in, but will have to type their " -"username. See also <filename>Include</filename>, <filename>IncludeAll</" -"filename>, and <filename>MinimalUID</filename>." -msgstr "" -"Lista separada por comas de usuarios que serán excluidos en el visor de rostros y en la lista de selección de " -"<command>gdmsetup</command> para el inicio de sesión automático/temporizado. Vea además <filename>Exclude</filename>, <filename>IncludeAll</filename>, y " -"<filename>MinimalUID</filename>." +#~ msgid "Exclude" +#~ msgstr "Exclude" -#: ../C/gdm.xml:2686 (term) #, fuzzy -msgid "IncludeAll" -msgstr "IncludeAll" +#~ msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." +#~ msgstr "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." -#: ../C/gdm.xml:2688 (synopsis) -#, fuzzy, no-wrap -msgid "IncludeAll=false" -msgstr "IncludeAll=false" - -#: ../C/gdm.xml:2689 (para) #, fuzzy -msgid "" -"By default, an empty include list means display no users. By setting " -"IncludeAll to true, the password file will be scanned and all users will be " -"displayed aside from users excluded via the Exclude setting and user ID's " -"less than MinimalUID. Scanning the password file can be slow on systems with " -"large numbers of users and this feature should not be used in such " -"environments. See also <filename>Include</filename>, <filename>Exclude</" -"filename>, and <filename>MinimalUID</filename>." -msgstr "" -"Por omisión, una lista de inclusión vacía significa no mostrar ningún usuario. Estableciendo IncludeAll al valor «true», se inspeccionará el archivo de contraseñas y todos los usuarios se mostrarán excepto los usuarios excluidos por medio del ajuste de exclusión y los IDs de usuario menores que MinimalUID. Examinar el archivo de contraseñas puede ser lento en sistemas con gran número de usuarios y esta característica no se usará en dichos entornos. Vea además <filename>Include</filename>, <filename>Exclude</" -"filename>, y <filename>MinimalUID</filename>." +#~ msgid "" +#~ "Comma separated list of users to be excluded from the face browser and " +#~ "from the <command>gdmsetup</command> selection list for Automatic/Timed " +#~ "login. Excluded users will still be able to log in, but will have to type " +#~ "their username. See also <filename>Include</filename>, " +#~ "<filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." +#~ msgstr "" +#~ "Lista separada por comas de usuarios que serán excluidos en el visor de " +#~ "rostros y en la lista de selección de <command>gdmsetup</command> para el " +#~ "inicio de sesión automático/temporizado. Vea además <filename>Exclude</" +#~ "filename>, <filename>IncludeAll</filename>, y <filename>MinimalUID</" +#~ "filename>." -#: ../C/gdm.xml:2705 (term) #, fuzzy -msgid "GlobalFaceDir" -msgstr "GlobalFaceDir" +#~ msgid "IncludeAll" +#~ msgstr "IncludeAll" -#: ../C/gdm.xml:2707 (synopsis) -#, fuzzy, no-wrap -msgid "GlobalFaceDir=<share>/pixmaps/faces/" -msgstr "GlobalFaceDir=<share>/pixmaps/faces/" +#, fuzzy +#~ msgid "IncludeAll=false" +#~ msgstr "IncludeAll=false" -#: ../C/gdm.xml:2708 (para) #, fuzzy -msgid "" -"Systemwide directory for face files. The sysadmin can place icons for users " -"here without touching their homedirs. Faces are named after their users' " -"logins." -msgstr "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." +#~ msgid "" +#~ "By default, an empty include list means display no users. By setting " +#~ "IncludeAll to true, the password file will be scanned and all users will " +#~ "be displayed aside from users excluded via the Exclude setting and user " +#~ "ID's less than MinimalUID. Scanning the password file can be slow on " +#~ "systems with large numbers of users and this feature should not be used " +#~ "in such environments. See also <filename>Include</filename>, " +#~ "<filename>Exclude</filename>, and <filename>MinimalUID</filename>." +#~ msgstr "" +#~ "Por omisión, una lista de inclusión vacía significa no mostrar ningún " +#~ "usuario. Estableciendo IncludeAll al valor «true», se inspeccionará el " +#~ "archivo de contraseñas y todos los usuarios se mostrarán excepto los " +#~ "usuarios excluidos por medio del ajuste de exclusión y los IDs de " +#~ "usuario menores que MinimalUID. Examinar el archivo de contraseñas puede " +#~ "ser lento en sistemas con gran número de usuarios y esta característica " +#~ "no se usará en dichos entornos. Vea además <filename>Include</filename>, " +#~ "<filename>Exclude</filename>, y <filename>MinimalUID</filename>." -#: ../C/gdm.xml:2714 (para) #, fuzzy -msgid "" -"I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the " -"face icon for the user ``johndoe''. No image format extension should be " -"specified." -msgstr "<filename>< GlobalFaceDir></filename>." +#~ msgid "GlobalFaceDir" +#~ msgstr "GlobalFaceDir" -#: ../C/gdm.xml:2720 (para) #, fuzzy -msgid "" -"The face images must be stored in gdk-pixbuf supported formats and they must " -"be readable for the GDM user." -msgstr "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." +#~ msgid "GlobalFaceDir=<share>/pixmaps/faces/" +#~ msgstr "GlobalFaceDir=<share>/pixmaps/faces/" -#: ../C/gdm.xml:2725 (para) -msgid "" -"A user's own icon file will always take precedence over the sysadmin " -"provided one." -msgstr "" +#, fuzzy +#~ msgid "" +#~ "Systemwide directory for face files. The sysadmin can place icons for " +#~ "users here without touching their homedirs. Faces are named after their " +#~ "users' logins." +#~ msgstr "" +#~ "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." -#: ../C/gdm.xml:2733 (term) #, fuzzy -msgid "GraphicalTheme" -msgstr "GraphicalTheme" +#~ msgid "" +#~ "I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the " +#~ "face icon for the user ``johndoe''. No image format extension should be " +#~ "specified." +#~ msgstr "<filename>< GlobalFaceDir></filename>." -#: ../C/gdm.xml:2735 (synopsis) -#, no-wrap #, fuzzy -msgid "GraphicalTheme=circles" -msgstr "GraphicalTheme=circles" +#~ msgid "" +#~ "The face images must be stored in gdk-pixbuf supported formats and they " +#~ "must be readable for the GDM user." +#~ msgstr "" +#~ "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." -#: ../C/gdm.xml:2736 (para) #, fuzzy -msgid "" -"The graphical theme that the Themed Greeter should use. it should refer to a " -"directory in the theme directory set by <filename>GraphicalThemeDir</" -"filename>." -msgstr "Greeter<filename> GraphicalThemeDir</filename>." +#~ msgid "GraphicalTheme" +#~ msgstr "GraphicalTheme" -#: ../C/gdm.xml:2745 (term) #, fuzzy -msgid "GraphicalThemes" -msgstr "Temas gráficos" +#~ msgid "GraphicalTheme=circles" +#~ msgstr "GraphicalTheme=circles" -#: ../C/gdm.xml:2747 (synopsis) -#, no-wrap #, fuzzy -msgid "GraphicalThemes=circles" -msgstr "GraphicalThemes=circles" +#~ msgid "" +#~ "The graphical theme that the Themed Greeter should use. it should refer " +#~ "to a directory in the theme directory set by <filename>GraphicalThemeDir</" +#~ "filename>." +#~ msgstr "Greeter<filename> GraphicalThemeDir</filename>." -#: ../C/gdm.xml:2748 (para) #, fuzzy -msgid "" -"The graphical themes that the Themed Greeter should use is the Mode is set " -"on Random Themes. This is a \"/:\" delimited list. It should refer to a " -"directory in the theme directory set by <filename>GraphicalThemeDir</" -"filename>. This is only used if <filename>GraphicalThemeRand</filename> is " -"set to true." -msgstr "Los temas gráficos que el Interfaz de entrada debería usar si el modo está puesto a Temas aleatorios. Esto es una lista delimitada por \"/:\" . Debería referirse a un directorio en el directorio del tema designado por <filename>GraphicalThemeDir</filename>. Esto se usa sólo si <filename>GraphicalThemeRand</filename> está establecido a «true»." +#~ msgid "GraphicalThemes" +#~ msgstr "Temas gráficos" -#: ../C/gdm.xml:2760 (term) #, fuzzy -msgid "GraphicalThemeRand" -msgstr "GraphicalThemeRand" +#~ msgid "GraphicalThemes=circles" +#~ msgstr "GraphicalThemes=circles" -#: ../C/gdm.xml:2762 (synopsis) -#, fuzzy, no-wrap -msgid "GraphicalThemeRand=false" -msgstr "GraphicalThemeRand=false" +#, fuzzy +#~ msgid "" +#~ "The graphical themes that the Themed Greeter should use is the Mode is " +#~ "set on Random Themes. This is a \"/:\" delimited list. It should refer to " +#~ "a directory in the theme directory set by <filename>GraphicalThemeDir</" +#~ "filename>. This is only used if <filename>GraphicalThemeRand</filename> " +#~ "is set to true." +#~ msgstr "" +#~ "Los temas gráficos que el Interfaz de entrada debería usar si el modo " +#~ "está puesto a Temas aleatorios. Esto es una lista delimitada por \"/:" +#~ "\" . Debería referirse a un directorio en el directorio del tema " +#~ "designado por <filename>GraphicalThemeDir</filename>. Esto se usa sólo si " +#~ "<filename>GraphicalThemeRand</filename> está establecido a «true»." -#: ../C/gdm.xml:2763 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename> GraphicalTheme</filename><filename> Temas gráficos</filename>." +#~ msgid "GraphicalThemeRand" +#~ msgstr "GraphicalThemeRand" -#: ../C/gdm.xml:2775 (term) #, fuzzy -msgid "GraphicalThemeDir" -msgstr "GraphicalThemeDir" +#~ msgid "GraphicalThemeRand=false" +#~ msgstr "GraphicalThemeRand=false" -#: ../C/gdm.xml:2777 (synopsis) -#, no-wrap #, fuzzy -msgid "GraphicalThemeDir=<share>/gdm/themes/" -msgstr "GraphicalThemeDir=<share>/gdm/themes/" +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "<filename> GraphicalTheme</filename><filename> Temas gráficos</filename>." -#: ../C/gdm.xml:2778 (para) #, fuzzy -msgid "The directory where themes for the Themed Greeter are installed." -msgstr "Greeter." +#~ msgid "GraphicalThemeDir" +#~ msgstr "GraphicalThemeDir" -#: ../C/gdm.xml:2786 (term) #, fuzzy -msgid "GraphicalThemedColor" -msgstr "GraphicalThemedColor" +#~ msgid "GraphicalThemeDir=<share>/gdm/themes/" +#~ msgstr "GraphicalThemeDir=<share>/gdm/themes/" -#: ../C/gdm.xml:2788 (synopsis) -#, fuzzy, no-wrap -msgid "GraphicalThemedColor=#76848F" -msgstr "GraphicalThemedColor=#76848F" +#, fuzzy +#~ msgid "The directory where themes for the Themed Greeter are installed." +#~ msgstr "Greeter." -#: ../C/gdm.xml:2789 (para) #, fuzzy -msgid "" -"Use this color in the background of the Themed Greeter. This only affects " -"the Themed Greeter." -msgstr "Greeter Greeter." +#~ msgid "GraphicalThemedColor" +#~ msgstr "GraphicalThemedColor" -#: ../C/gdm.xml:2797 (term) #, fuzzy -msgid "InfoMsgFile" -msgstr "InfoMsgFile" +#~ msgid "GraphicalThemedColor=#76848F" +#~ msgstr "GraphicalThemedColor=#76848F" -#: ../C/gdm.xml:2799 (synopsis) -#, no-wrap #, fuzzy -msgid "InfoMsgFile=/path/to/infofile" -msgstr "InfoMsgFile=/path/to/infofile" +#~ msgid "" +#~ "Use this color in the background of the Themed Greeter. This only affects " +#~ "the Themed Greeter." +#~ msgstr "Greeter Greeter." -#: ../C/gdm.xml:2800 (para) -msgid "" -"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." -msgstr "" +#, fuzzy +#~ msgid "InfoMsgFile" +#~ msgstr "InfoMsgFile" -#: ../C/gdm.xml:2811 (term) #, fuzzy -msgid "InfoMsgFont" -msgstr "InfoMsgFont" +#~ msgid "InfoMsgFile=/path/to/infofile" +#~ msgstr "InfoMsgFile=/path/to/infofile" -#: ../C/gdm.xml:2813 (synopsis) -#, no-wrap #, fuzzy -msgid "InfoMsgFont=fontspec" -msgstr "InfoMsgFont=fontspec" +#~ msgid "InfoMsgFont" +#~ msgstr "InfoMsgFont" -#: ../C/gdm.xml:2814 (para) #, fuzzy -msgid "" -"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." -msgstr "InfoMsgFile InfoMsgFile." +#~ msgid "InfoMsgFont=fontspec" +#~ msgstr "InfoMsgFont=fontspec" -#: ../C/gdm.xml:2826 (term) #, fuzzy -msgid "LocaleFile" -msgstr "LocaleFile" +#~ msgid "" +#~ "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." +#~ msgstr "InfoMsgFile InfoMsgFile." -#: ../C/gdm.xml:2828 (synopsis) -#, fuzzy, no-wrap -msgid "LocaleFile=<etc>/gdm/locale.alias" -msgstr "LocaleFile=<etc>/gdm/locale.alias" +#, fuzzy +#~ msgid "LocaleFile" +#~ msgstr "LocaleFile" -#: ../C/gdm.xml:2829 (para) -msgid "" -"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." -msgstr "" +#, fuzzy +#~ msgid "LocaleFile=<etc>/gdm/locale.alias" +#~ msgstr "LocaleFile=<etc>/gdm/locale.alias" -#: ../C/gdm.xml:2838 (term) #, fuzzy -msgid "LockPosition" -msgstr "LockPosition" +#~ msgid "LockPosition" +#~ msgstr "LockPosition" -#: ../C/gdm.xml:2840 (synopsis) -#, fuzzy, no-wrap -msgid "LockPosition=true" -msgstr "LockPosition=true" +#, fuzzy +#~ msgid "LockPosition=true" +#~ msgstr "LockPosition=true" -#: ../C/gdm.xml:2841 (para) #, fuzzy -msgid "" -"If true the position of the login window of the GTK+ Greeter cannot be " -"changed even if the title bar is turned on." -msgstr "Greeter." +#~ msgid "" +#~ "If true the position of the login window of the GTK+ Greeter cannot be " +#~ "changed even if the title bar is turned on." +#~ msgstr "Greeter." -#: ../C/gdm.xml:2849 (term) #, fuzzy -msgid "Logo" -msgstr "Logo" +#~ msgid "Logo" +#~ msgstr "Logo" -#: ../C/gdm.xml:2851 (synopsis) -#, no-wrap #, fuzzy -msgid "Logo=<share>/pixmaps/gnome-logo-large.png" -msgstr "Logo=<share>/pixmaps/gnome-logo-large.png" +#~ msgid "Logo=<share>/pixmaps/gnome-logo-large.png" +#~ msgstr "Logo=<share>/pixmaps/gnome-logo-large.png" -#: ../C/gdm.xml:2852 (para) #, fuzzy -msgid "" -"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." -msgstr "Greeter." +#~ msgid "" +#~ "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." +#~ msgstr "Greeter." -#: ../C/gdm.xml:2863 (term) #, fuzzy -msgid "ChooserButtonLogo" -msgstr "ChooserButtonLogo" +#~ msgid "ChooserButtonLogo" +#~ msgstr "ChooserButtonLogo" -#: ../C/gdm.xml:2865 (synopsis) -#, no-wrap #, fuzzy -msgid "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" -msgstr "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" +#~ msgid "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" +#~ msgstr "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" -#: ../C/gdm.xml:2866 (para) #, fuzzy -msgid "" -"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>)." -msgstr "chooser<command></command><command></command><command></command>." +#~ msgid "" +#~ "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>)." +#~ msgstr "chooser<command></command><command></command><command></command>." -#: ../C/gdm.xml:2877 (term) #, fuzzy -msgid "MinimalUID" -msgstr "MinimalUID" +#~ msgid "MinimalUID" +#~ msgstr "MinimalUID" -#: ../C/gdm.xml:2879 (synopsis) -#, no-wrap #, fuzzy -msgid "MinimalUID=100" -msgstr "MinimalUID=100" +#~ msgid "MinimalUID=100" +#~ msgstr "MinimalUID=100" -#: ../C/gdm.xml:2880 (para) #, fuzzy -msgid "" -"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>." -msgstr "<filename> Include</filename><filename> Exclude</filename><filename> IncludeAll</filename>." +#~ msgid "" +#~ "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>." +#~ msgstr "" +#~ "<filename> Include</filename><filename> Exclude</filename><filename> " +#~ "IncludeAll</filename>." -#: ../C/gdm.xml:2891 (term) -msgid "PositionX" -msgstr "PositionX" +#~ msgid "PositionX" +#~ msgstr "PositionX" -#: ../C/gdm.xml:2893 (synopsis) -#, no-wrap -msgid "PositionX=200" -msgstr "PositionX=200" +#~ msgid "PositionX=200" +#~ msgstr "PositionX=200" -#: ../C/gdm.xml:2894 (para) #, fuzzy -msgid "The horizontal position of the login window of the GTK+ Greeter." -msgstr "La posición horizontal de la ventana de entrada del interfaz GTK+." +#~ msgid "The horizontal position of the login window of the GTK+ Greeter." +#~ msgstr "La posición horizontal de la ventana de entrada del interfaz GTK+." -#: ../C/gdm.xml:2902 (term) -msgid "PositionY" -msgstr "PositionY" +#~ msgid "PositionY" +#~ msgstr "PositionY" -#: ../C/gdm.xml:2904 (synopsis) -#, no-wrap -msgid "PositionY=100" -msgstr "PositionY=100" +#~ msgid "PositionY=100" +#~ msgstr "PositionY=100" -#: ../C/gdm.xml:2905 (para) #, fuzzy -msgid "The vertical position of the login window of the GTK+ Greeter." -msgstr "La posición vertical de la ventana de entrada del interfaz GTK+." +#~ msgid "The vertical position of the login window of the GTK+ Greeter." +#~ msgstr "La posición vertical de la ventana de entrada del interfaz GTK+." -#: ../C/gdm.xml:2913 (term) -msgid "Quiver" -msgstr "Quiver" +#~ msgid "Quiver" +#~ msgstr "Quiver" -#: ../C/gdm.xml:2915 (synopsis) -#, no-wrap -msgid "Quiver=true" -msgstr "Quiver=true" +#~ msgid "Quiver=true" +#~ msgstr "Quiver=true" -#: ../C/gdm.xml:2916 (para) #, fuzzy -msgid "" -"Controls whether <command>gdmlogin</command> should shake the display when " -"an incorrect username/password is entered. This only affects the GTK+ " -"Greeter." -msgstr "<command></command> Greeter." +#~ msgid "" +#~ "Controls whether <command>gdmlogin</command> should shake the display " +#~ "when an incorrect username/password is entered. This only affects the GTK" +#~ "+ Greeter." +#~ msgstr "<command></command> Greeter." -#: ../C/gdm.xml:2926 (term) -msgid "DefaultRemoteWelcome" -msgstr "DefaultRemoteWelcome" +#~ msgid "DefaultRemoteWelcome" +#~ msgstr "DefaultRemoteWelcome" -#: ../C/gdm.xml:2928 (synopsis) -#, no-wrap -msgid "DefaultRemoteWelcome=true" -msgstr "DefaultRemoteWelcome=true" +#~ msgid "DefaultRemoteWelcome=true" +#~ msgstr "DefaultRemoteWelcome=true" -#: ../C/gdm.xml:2929 (para) #, fuzzy -msgid "" -"If set to true, the value \"Welcome to %n\" is used for the " -"<filename>RemoteWelcome</filename>. This value is translated into the " -"appropriate language for the user. If set to false, the " -"<filename>RemoteWelcome</filename> setting is used. This string can use the " -"same special character sequences as explained in the \"Text Node\" section " -"of the \"Themed Greeter\" chapter. This explains the meaning of \"%n\"." -msgstr "Welcome<filename> RemoteWelcome</filename><filename> RemoteWelcome</filename> Greeter." +#~ msgid "" +#~ "If set to true, the value \"Welcome to %n\" is used for the " +#~ "<filename>RemoteWelcome</filename>. This value is translated into the " +#~ "appropriate language for the user. If set to false, the " +#~ "<filename>RemoteWelcome</filename> setting is used. This string can use " +#~ "the same special character sequences as explained in the \"Text Node\" " +#~ "section of the \"Themed Greeter\" chapter. This explains the meaning of " +#~ "\"%n\"." +#~ msgstr "" +#~ "Welcome<filename> RemoteWelcome</filename><filename> RemoteWelcome</" +#~ "filename> Greeter." -#: ../C/gdm.xml:2943 (term) -msgid "RemoteWelcome" -msgstr "RemoteWelcome" +#~ msgid "RemoteWelcome" +#~ msgstr "RemoteWelcome" -#: ../C/gdm.xml:2945 (synopsis) -#, no-wrap -msgid "RemoteWelcome=Welcome to n" -msgstr "RemoteWelcome=Welcome to n" +#~ msgid "RemoteWelcome=Welcome to n" +#~ msgstr "RemoteWelcome=Welcome to n" -#: ../C/gdm.xml:2946 (para) #, fuzzy -msgid "" -"Controls which text to display next to the logo image in the greeter for " -"remote XDMCP sessions. The same expansion is done here as in the " -"<filename>Welcome</filename> string. This string can use the same special " -"character sequences as explained in the \"Text Node\" section of the " -"\"Themed Greeter\" chapter. chapter." -msgstr "XDMCP<filename> Welcome</filename> Greeter." +#~ msgid "" +#~ "Controls which text to display next to the logo image in the greeter for " +#~ "remote XDMCP sessions. The same expansion is done here as in the " +#~ "<filename>Welcome</filename> string. This string can use the same special " +#~ "character sequences as explained in the \"Text Node\" section of the " +#~ "\"Themed Greeter\" chapter. chapter." +#~ msgstr "XDMCP<filename> Welcome</filename> Greeter." -#: ../C/gdm.xml:2959 (term) -msgid "RunBackgroundProgramAlways" -msgstr "RunBackgroundProgramAlways" +#~ msgid "RunBackgroundProgramAlways" +#~ msgstr "RunBackgroundProgramAlways" -#: ../C/gdm.xml:2961 (synopsis) -#, no-wrap -msgid "RunBackgroundProgramAlways=false" -msgstr "RunBackgroundProgramAlways=false" +#~ msgid "RunBackgroundProgramAlways=false" +#~ msgstr "RunBackgroundProgramAlways=false" -#: ../C/gdm.xml:2962 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename> BackgroundType</filename> Greeter." +#~ msgid "" +#~ "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." +#~ msgstr "<filename> BackgroundType</filename> Greeter." -#: ../C/gdm.xml:2972 (term) -msgid "SetPosition" -msgstr "SetPosition" +#~ msgid "SetPosition" +#~ msgstr "SetPosition" -#: ../C/gdm.xml:2974 (synopsis) -#, no-wrap -msgid "SetPosition=true" -msgstr "SetPosition=true" +#~ msgid "SetPosition=true" +#~ msgstr "SetPosition=true" -#: ../C/gdm.xml:2975 (para) #, fuzzy -msgid "" -"If true the position of the login window of the GTK+ Greeter is determined " -"by <filename>PositionX</filename> / <filename>PositionY</filename>." -msgstr "Greeter<filename> PositionX</filename><filename> PositionY</filename>." +#~ msgid "" +#~ "If true the position of the login window of the GTK+ Greeter is " +#~ "determined by <filename>PositionX</filename> / <filename>PositionY</" +#~ "filename>." +#~ msgstr "" +#~ "Greeter<filename> PositionX</filename><filename> PositionY</filename>." -#: ../C/gdm.xml:2984 (term) #, fuzzy -msgid "ShowGnomeFailsafeSession" -msgstr "ShowGnomeFailsafeSession" +#~ msgid "ShowGnomeFailsafeSession" +#~ msgstr "ShowGnomeFailsafeSession" -#: ../C/gdm.xml:2986 (synopsis) -#, fuzzy, no-wrap -msgid "ShowGnomeFailsafeSession=true" -msgstr "ShowGnomeFailsafeSession=true" +#, fuzzy +#~ msgid "ShowGnomeFailsafeSession=true" +#~ msgstr "ShowGnomeFailsafeSession=true" -#: ../C/gdm.xml:2987 (para) #, fuzzy -msgid "Should the greeter show the Gnome Failsafe session in th sessions list." -msgstr "list." +#~ msgid "" +#~ "Should the greeter show the Gnome Failsafe session in th sessions list." +#~ msgstr "list." -#: ../C/gdm.xml:2995 (term) #, fuzzy -msgid "ShowLastSession" -msgstr "ShowLastSession" +#~ msgid "ShowLastSession" +#~ msgstr "ShowLastSession" -#: ../C/gdm.xml:2997 (synopsis) -#, no-wrap -msgid "ShowLastSession=true" -msgstr "ShowLastSession=true" +#~ msgid "ShowLastSession=true" +#~ msgstr "ShowLastSession=true" -#: ../C/gdm.xml:2998 (para) #, fuzzy -msgid "" -"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." -msgstr "list<filename> DefaultSession</filename>." - -#: ../C/gdm.xml:3011 (term) -msgid "ShowXtermFailsafeSession" -msgstr "ShowXtermFailsafeSession" - -#: ../C/gdm.xml:3013 (synopsis) -#, no-wrap -msgid "ShowXtermFailsafeSession=true" -msgstr "ShowXtermFailsafeSession=true" - -#: ../C/gdm.xml:3014 (para) -#, fuzzy -msgid "Should the greeter show the Xterm Failsafe session in the sessions list." -msgstr "list." - -#: ../C/gdm.xml:3022 (term) -msgid "SoundOnLogin" -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "list<filename> DefaultSession</filename>." -#: ../C/gdm.xml:3024 (synopsis) -#, no-wrap -#, fuzzy -msgid "SoundOnLogin=true" -msgstr "SoundOnLogin=true" +#~ msgid "ShowXtermFailsafeSession" +#~ msgstr "ShowXtermFailsafeSession" -#: ../C/gdm.xml:3025 (para) -msgid "" -"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." -msgstr "" +#~ msgid "ShowXtermFailsafeSession=true" +#~ msgstr "ShowXtermFailsafeSession=true" -#: ../C/gdm.xml:3035 (term) #, fuzzy -msgid "SoundOnLoginSuccess" -msgstr "SoundOnLoginSuccess" +#~ msgid "" +#~ "Should the greeter show the Xterm Failsafe session in the sessions list." +#~ msgstr "list." -#: ../C/gdm.xml:3037 (synopsis) -#, no-wrap #, fuzzy -msgid "SoundOnLoginSuccess=true" -msgstr "SoundOnLoginSuccess=true" +#~ msgid "SoundOnLogin=true" +#~ msgstr "SoundOnLogin=true" -#: ../C/gdm.xml:3038 (para) -msgid "" -"If true, the greeter will play a sound after a successful login attempt. See " -"also the <filename>SoundOnLoginSuccessFile</filename> key." -msgstr "" - -#: ../C/gdm.xml:3047 (term) #, fuzzy -msgid "SoundOnLoginFailure" -msgstr "SoundOnLoginFailure" +#~ msgid "SoundOnLoginSuccess" +#~ msgstr "SoundOnLoginSuccess" -#: ../C/gdm.xml:3049 (synopsis) -#, no-wrap #, fuzzy -msgid "SoundOnLoginFailure=true" -msgstr "SoundOnLoginFailure=true" - -#: ../C/gdm.xml:3050 (para) -msgid "" -"If true, the greeter will play a sound after a failed login attempt. See " -"also the <filename>SoundOnLoginFailureFile</filename> key." -msgstr "" - -#: ../C/gdm.xml:3059 (term) -msgid "SoundOnLoginFile" -msgstr "" - -#: ../C/gdm.xml:3061 (synopsis) -#, no-wrap -msgid "SoundOnLoginFile=/path/to/sound.wav" -msgstr "" +#~ msgid "SoundOnLoginSuccess=true" +#~ msgstr "SoundOnLoginSuccess=true" -#: ../C/gdm.xml:3062 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename></filename><filename></filename><filename> SoundProgram</filename>." - -#: ../C/gdm.xml:3074 (term) -msgid "SoundOnLoginSuccessFile" -msgstr "" +#~ msgid "SoundOnLoginFailure" +#~ msgstr "SoundOnLoginFailure" -#: ../C/gdm.xml:3076 (synopsis) -#, no-wrap -msgid "SoundOnLoginSuccessFile=/path/to/sound.wav" -msgstr "" - -#: ../C/gdm.xml:3077 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename></filename><filename> SoundOnLoginSuccess</filename><filename> SoundProgram</filename>." - -#: ../C/gdm.xml:3088 (term) -msgid "SoundOnLoginFailureFile" -msgstr "" - -#: ../C/gdm.xml:3090 (synopsis) -#, no-wrap -msgid "SoundOnLoginFailureFile=/path/to/sound.wav" -msgstr "" +#~ msgid "SoundOnLoginFailure=true" +#~ msgstr "SoundOnLoginFailure=true" -#: ../C/gdm.xml:3091 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename></filename><filename> SoundOnLoginFailure</filename><filename> SoundProgram</filename>." - -#: ../C/gdm.xml:3102 (term) -msgid "SystemMenu" -msgstr "" - -#: ../C/gdm.xml:3104 (synopsis) -#, no-wrap -msgid "SystemMenu=true" -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "<filename></filename><filename></filename><filename> SoundProgram</" +#~ "filename>." -#: ../C/gdm.xml:3105 (para) #, fuzzy -msgid "" -"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." -msgstr "XDMCP chooser." - -#: ../C/gdm.xml:3118 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "<filename></filename><filename> SoundOnLoginSuccess</filename><filename> " +#~ "SoundProgram</filename>." -#: ../C/gdm.xml:3129 (term) #, fuzzy -msgid "TitleBar" -msgstr "Quiver=true" - -#: ../C/gdm.xml:3131 (synopsis) -#, fuzzy, no-wrap -msgid "TitleBar=true" -msgstr "TitleBar=true" +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "<filename></filename><filename> SoundOnLoginFailure</filename><filename> " +#~ "SoundProgram</filename>." -#: ../C/gdm.xml:3132 (para) #, fuzzy -msgid "Display the title bar in the greeter. This only affects the GTK+ Greeter." -msgstr "Greeter." - -#: ../C/gdm.xml:3140 (term) -msgid "Use24Clock" -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "XDMCP chooser." -#: ../C/gdm.xml:3142 (synopsis) -#, no-wrap #, fuzzy -msgid "Use24Clock=auto" -msgstr "Use24Clock=auto" +#~ msgid "TitleBar" +#~ msgstr "Quiver=true" -#: ../C/gdm.xml:3143 (para) #, fuzzy -msgid "" -"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." -msgstr "clock<filename></filename>." - -#: ../C/gdm.xml:3149 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:3164 (term) -msgid "UseCirclesInEntry" -msgstr "" - -#: ../C/gdm.xml:3166 (synopsis) -#, no-wrap -msgid "UseCirclesInEntry=false" -msgstr "" +#~ msgid "TitleBar=true" +#~ msgstr "TitleBar=true" -#: ../C/gdm.xml:3167 (para) #, fuzzy -msgid "" -"Use circles instead of asterisks in the password entry. This may not work " -"with all fonts however." -msgstr "entry." +#~ msgid "" +#~ "Display the title bar in the greeter. This only affects the GTK+ Greeter." +#~ msgstr "Greeter." -#: ../C/gdm.xml:3175 (term) #, fuzzy -msgid "UseInvisibleInEntry" -msgstr "UseInvisibleInEntry" +#~ msgid "Use24Clock=auto" +#~ msgstr "Use24Clock=auto" -#: ../C/gdm.xml:3177 (synopsis) -#, no-wrap #, fuzzy -msgid "UseInvisibleInEntry=false" -msgstr "UseInvisibleInEntry=false" +#~ msgid "" +#~ "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." +#~ msgstr "clock<filename></filename>." -#: ../C/gdm.xml:3178 (para) #, fuzzy -msgid "" -"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." -msgstr "entry<filename></filename>." +#~ msgid "" +#~ "Use circles instead of asterisks in the password entry. This may not work " +#~ "with all fonts however." +#~ msgstr "entry." -#: ../C/gdm.xml:3188 (term) #, fuzzy -msgid "DefaultWelcome" -msgstr "DefaultWelcome" +#~ msgid "UseInvisibleInEntry" +#~ msgstr "UseInvisibleInEntry" -#: ../C/gdm.xml:3190 (synopsis) -#, fuzzy, no-wrap -msgid "DefaultWelcome=true" -msgstr "DefaultWelcome=true" - -#: ../C/gdm.xml:3191 (para) #, fuzzy -msgid "" -"If set to true, the value \"Welcome\" is used for the <filename>Welcome</" -"filename>. This value is translated into the appropriate language for the " -"user. If set to false, the <filename>Welcome</filename> setting is used." -msgstr "" -"Si está establecido a «true» el valor \"Welcome\" se usa para la <filename>Welcome</" -"filename>. Este valor está traducido en el idioma apropiado para el usuario. Si se establece a «false», se usa el ajuste <filename>Welcome</filename>." +#~ msgid "UseInvisibleInEntry=false" +#~ msgstr "UseInvisibleInEntry=false" -#: ../C/gdm.xml:3201 (term) #, fuzzy -msgid "Welcome" -msgstr "Welcome" +#~ msgid "" +#~ "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." +#~ msgstr "entry<filename></filename>." -#: ../C/gdm.xml:3203 (synopsis) -#, fuzzy, no-wrap -msgid "Welcome=Welcome" -msgstr "Welcome=Welcome" +#, fuzzy +#~ msgid "DefaultWelcome" +#~ msgstr "DefaultWelcome" -#: ../C/gdm.xml:3204 (para) #, fuzzy -msgid "" -"Controls which text to display next to the logo image in the standard " -"greeter. The following control chars are supported:" -msgstr "Controla qué texto se muestra junto a la imagen del logotipo en el interfaz estándar. Están soportados los siguientes caracteres de control:" +#~ msgid "DefaultWelcome=true" +#~ msgstr "DefaultWelcome=true" -#: ../C/gdm.xml:3213 (para) #, fuzzy -msgid "d display's hostname" -msgstr "h nombre de host de la pantalla" +#~ msgid "" +#~ "If set to true, the value \"Welcome\" is used for the <filename>Welcome</" +#~ "filename>. This value is translated into the appropriate language for the " +#~ "user. If set to false, the <filename>Welcome</filename> setting is used." +#~ msgstr "" +#~ "Si está establecido a «true» el valor \"Welcome\" se usa para la " +#~ "<filename>Welcome</filename>. Este valor está traducido en el idioma " +#~ "apropiado para el usuario. Si se establece a «false», se usa el ajuste " +#~ "<filename>Welcome</filename>." -#: ../C/gdm.xml:3217 (para) #, fuzzy -msgid "h Fully qualified hostname" -msgstr "h nombre del host completamente cualificado" +#~ msgid "Welcome" +#~ msgstr "Welcome" -#: ../C/gdm.xml:3221 (para) #, fuzzy -msgid "m machine (processor type)" -msgstr "m máquina (tipo de procesador)" +#~ msgid "Welcome=Welcome" +#~ msgstr "Welcome=Welcome" -#: ../C/gdm.xml:3225 (para) #, fuzzy -msgid "n Nodename (i.e. hostname without .domain)" -msgstr "n nombre del nodo (i.e. nombre del host sin .dominio)" +#~ msgid "" +#~ "Controls which text to display next to the logo image in the standard " +#~ "greeter. The following control chars are supported:" +#~ msgstr "" +#~ "Controla qué texto se muestra junto a la imagen del logotipo en el " +#~ "interfaz estándar. Están soportados los siguientes caracteres de control:" -#: ../C/gdm.xml:3229 (para) #, fuzzy -msgid "r release (OS version)" -msgstr "r release (OS version)" +#~ msgid "d display's hostname" +#~ msgstr "h nombre de host de la pantalla" -#: ../C/gdm.xml:3233 (para) #, fuzzy -msgid "s sysname (i.e. OS)" -msgstr "s sysname (i.e. OS)" +#~ msgid "h Fully qualified hostname" +#~ msgstr "h nombre del host completamente cualificado" -#: ../C/gdm.xml:3237 (para) #, fuzzy -msgid "" -"This string is only used for local logins. For remote XDMCP logins we use " -"<filename>RemoteWelcome</filename>." -msgstr "Estas cadenas se usan sólo para inicios de sesión locales. Para inicios de sesión remotos XDMCP se usa <filename>RemoteWelcome</filename>." +#~ msgid "m machine (processor type)" +#~ msgstr "m máquina (tipo de procesador)" -#: ../C/gdm.xml:3242 (para) #, fuzzy -msgid "" -"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." -msgstr "Greeter." +#~ msgid "n Nodename (i.e. hostname without .domain)" +#~ msgstr "n nombre del nodo (i.e. nombre del host sin .dominio)" -#: ../C/gdm.xml:3252 (term) #, fuzzy -msgid "XineramaScreen" -msgstr "XineramaScreen" +#~ msgid "r release (OS version)" +#~ msgstr "r release (OS version)" -#: ../C/gdm.xml:3254 (synopsis) -#, no-wrap #, fuzzy -msgid "XineramaScreen=0" -msgstr "XineramaScreen=0" +#~ msgid "s sysname (i.e. OS)" +#~ msgstr "s sysname (i.e. OS)" -#: ../C/gdm.xml:3255 (para) -msgid "" -"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...)." -msgstr "" +#, fuzzy +#~ msgid "" +#~ "This string is only used for local logins. For remote XDMCP logins we use " +#~ "<filename>RemoteWelcome</filename>." +#~ msgstr "" +#~ "Estas cadenas se usan sólo para inicios de sesión locales. Para inicios " +#~ "de sesión remotos XDMCP se usa <filename>RemoteWelcome</filename>." -#: ../C/gdm.xml:3269 (title) #, fuzzy -msgid "XDCMP Chooser Options" -msgstr "Opciones del selector XDCMP" +#~ msgid "" +#~ "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." +#~ msgstr "Greeter." -#: ../C/gdm.xml:3272 (title) #, fuzzy -msgid "[chooser]" -msgstr "[chooser]" +#~ msgid "XineramaScreen" +#~ msgstr "XineramaScreen" -#: ../C/gdm.xml:3275 (term) #, fuzzy -msgid "AllowAdd" -msgstr "AllowAdd" +#~ msgid "XineramaScreen=0" +#~ msgstr "XineramaScreen=0" -#: ../C/gdm.xml:3277 (synopsis) -#, fuzzy, no-wrap -msgid "AllowAdd=true" -msgstr "AllowAdd=true" +#, fuzzy +#~ msgid "XDCMP Chooser Options" +#~ msgstr "Opciones del selector XDCMP" -#: ../C/gdm.xml:3278 (para) #, fuzzy -msgid "" -"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." -msgstr "chooser XDMCP chooser." +#~ msgid "[chooser]" +#~ msgstr "[chooser]" -#: ../C/gdm.xml:3287 (term) #, fuzzy -msgid "Broadcast" -msgstr "Broadcast" +#~ msgid "AllowAdd" +#~ msgstr "AllowAdd" -#: ../C/gdm.xml:3289 (synopsis) -#, fuzzy, no-wrap -msgid "Broadcast=true" -msgstr "Broadcast=true" +#, fuzzy +#~ msgid "AllowAdd=true" +#~ msgstr "AllowAdd=true" -#: ../C/gdm.xml:3290 (para) #, fuzzy -msgid "" -"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." -msgstr "chooser chooser list<filename> Hosts</filename>." +#~ msgid "" +#~ "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." +#~ msgstr "chooser XDMCP chooser." -#: ../C/gdm.xml:3302 (term) #, fuzzy -msgid "Multicast" -msgstr "Multicast" +#~ msgid "Broadcast" +#~ msgstr "Broadcast" -#: ../C/gdm.xml:3304 (synopsis) -#, fuzzy, no-wrap -msgid "Multicast=true" -msgstr "Multicast=true" +#, fuzzy +#~ msgid "Broadcast=true" +#~ msgstr "Broadcast=true" -#: ../C/gdm.xml:3305 (para) #, fuzzy -msgid "" -"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." -msgstr "chooser<filename> Hosts</filename> XDMCP." +#~ msgid "" +#~ "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." +#~ msgstr "chooser chooser list<filename> Hosts</filename>." -#: ../C/gdm.xml:3317 (term) #, fuzzy -msgid "MulticastAddr" -msgstr "MulticastAddr" +#~ msgid "Multicast" +#~ msgstr "Multicast" -#: ../C/gdm.xml:3319 (synopsis) -#, no-wrap #, fuzzy -msgid "MulticastAddr=ff02::1" -msgstr "MulticastAddr=ff02::1" +#~ msgid "Multicast=true" +#~ msgstr "Multicast=true" -#: ../C/gdm.xml:3320 (para) #, fuzzy -msgid "This is the Link-local Multicast address and is hardcoded here." -msgstr "Multicast." +#~ msgid "" +#~ "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." +#~ msgstr "chooser<filename> Hosts</filename> XDMCP." -#: ../C/gdm.xml:3327 (term) #, fuzzy -msgid "DefaultHostImage" -msgstr "DefaultHostImage" +#~ msgid "MulticastAddr" +#~ msgstr "MulticastAddr" -#: ../C/gdm.xml:3329 (synopsis) -#, fuzzy, no-wrap -msgid "DefaultHostImage=<share>/pixmaps/nohost.png" -msgstr "DefaultHostImage<>" +#, fuzzy +#~ msgid "MulticastAddr=ff02::1" +#~ msgstr "MulticastAddr=ff02::1" -#: ../C/gdm.xml:3330 (para) #, fuzzy -msgid "" -"File name for the default host icon. This image will be displayed if no icon " -"is specified for a given host. The file must be in an gdk-pixbuf supported " -"format and it must be readable for the GDM user." -msgstr "nombre." +#~ msgid "This is the Link-local Multicast address and is hardcoded here." +#~ msgstr "Multicast." -#: ../C/gdm.xml:3340 (term) #, fuzzy -msgid "HostImageDir" -msgstr "HostImageDir" +#~ msgid "DefaultHostImage" +#~ msgstr "DefaultHostImage" -#: ../C/gdm.xml:3342 (synopsis) -#, fuzzy, no-wrap -msgid "HostImageDir=<share>/hosts" -msgstr "HostImageDir=<share>/hosts" +#, fuzzy +#~ msgid "DefaultHostImage=<share>/pixmaps/nohost.png" +#~ msgstr "DefaultHostImage<>" -#: ../C/gdm.xml:3343 (para) -msgid "" -"Repository for host icon files. The sysadmin can place icons for remote " -"hosts here and they will appear in <filename>gdmchooser</filename>." -msgstr "" +#, fuzzy +#~ msgid "" +#~ "File name for the default host icon. This image will be displayed if no " +#~ "icon is specified for a given host. The file must be in an gdk-pixbuf " +#~ "supported format and it must be readable for the GDM user." +#~ msgstr "nombre." -#: ../C/gdm.xml:3349 (para) #, fuzzy -msgid "" -"The file name must match the fully qualified name (FQDN) for the host. The " -"icons must be stored in gdk-pixbuf supported formats and they must be " -"readable to the GDM user." -msgstr "nombre nombre." +#~ msgid "HostImageDir" +#~ msgstr "HostImageDir" -#: ../C/gdm.xml:3359 (term) #, fuzzy -msgid "Hosts" -msgstr "Hosts" +#~ msgid "HostImageDir=<share>/hosts" +#~ msgstr "HostImageDir=<share>/hosts" -#: ../C/gdm.xml:3361 (synopsis) -#, no-wrap #, fuzzy -msgid "Hosts=host1,host2" -msgstr "Hosts=host1,host2" +#~ msgid "" +#~ "The file name must match the fully qualified name (FQDN) for the host. " +#~ "The icons must be stored in gdk-pixbuf supported formats and they must be " +#~ "readable to the GDM user." +#~ msgstr "nombre nombre." -#: ../C/gdm.xml:3362 (para) #, fuzzy -msgid "" -"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." -msgstr "chooser chooser list<filename> Broadcast</filename> list." +#~ msgid "Hosts" +#~ msgstr "Hosts" -#: ../C/gdm.xml:3374 (term) #, fuzzy -msgid "ScanTime" -msgstr "ScanTime" +#~ msgid "Hosts=host1,host2" +#~ msgstr "Hosts=host1,host2" -#: ../C/gdm.xml:3376 (synopsis) -#, no-wrap #, fuzzy -msgid "ScanTime=4" -msgstr "ScanTime=4" +#~ msgid "" +#~ "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." +#~ msgstr "chooser chooser list<filename> Broadcast</filename> list." -#: ../C/gdm.xml:3377 (para) #, fuzzy -msgid "" -"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." -msgstr "chooser list." +#~ msgid "ScanTime" +#~ msgstr "ScanTime" -#: ../C/gdm.xml:3391 (title) -msgid "Debug Configuration" -msgstr "Configuración de depuración" +#, fuzzy +#~ msgid "ScanTime=4" +#~ msgstr "ScanTime=4" -#: ../C/gdm.xml:3394 (title) #, fuzzy -msgid "[debug]" -msgstr "[debug]" +#~ msgid "" +#~ "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." +#~ msgstr "chooser list." -#: ../C/gdm.xml:3400 (para) -msgid "" -"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." -msgstr "" +#~ msgid "Debug Configuration" +#~ msgstr "Configuración de depuración" -#: ../C/gdm.xml:3410 (term) #, fuzzy -msgid "Gestures" -msgstr "Gestures" - -#: ../C/gdm.xml:3412 (synopsis) -#, no-wrap -msgid "Gestures=false" -msgstr "Gestures=false" +#~ msgid "[debug]" +#~ msgstr "[debug]" -#: ../C/gdm.xml:3413 (para) -msgid "" -"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." -msgstr "" +#, fuzzy +#~ msgid "Gestures" +#~ msgstr "Gestures" -#: ../C/gdm.xml:3427 (title) -msgid "X Server Definitions" -msgstr "" +#~ msgid "Gestures=false" +#~ msgstr "Gestures=false" -#: ../C/gdm.xml:3429 (para) #, fuzzy -msgid "" -"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." -msgstr "nombre nombre<filename></filename><filename> StandardXServer</filename><filename></filename>." - -#: ../C/gdm.xml:3440 (para) -msgid "" -"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>gdm.conf-custom</filename> file override " -"values in the <filename>gdm.conf</filename> file. In other words, if a " -"<filename>server-Standard</filename> section is defined in <filename>gdm." -"conf-custom</filename>, then that will be used and the section in the " -"<filename>gdm.conf</filename> file will be ignored." -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "nombre nombre<filename></filename><filename> StandardXServer</" +#~ "filename><filename></filename>." -#: ../C/gdm.xml:3456 (title) #, fuzzy -msgid "[server-Standard]" -msgstr "[server-Standard]" +#~ msgid "[server-Standard]" +#~ msgstr "[server-Standard]" -#: ../C/gdm.xml:3459 (term) #, fuzzy -msgid "name" -msgstr "nombre" +#~ msgid "name" +#~ msgstr "nombre" -#: ../C/gdm.xml:3461 (synopsis) -#, no-wrap -msgid "name=Standard server" -msgstr "name=Standard server" +#~ msgid "name=Standard server" +#~ msgstr "name=Standard server" -#: ../C/gdm.xml:3462 (para) #, fuzzy -msgid "The name that will be displayed to the user." -msgstr "El nombre que se mostrará al usuario." +#~ msgid "The name that will be displayed to the user." +#~ msgstr "El nombre que se mostrará al usuario." -#: ../C/gdm.xml:3469 (term) -msgid "command" -msgstr "command" +#~ msgid "command" +#~ msgstr "command" -#: ../C/gdm.xml:3471 (synopsis) -#, no-wrap -msgid "command=/usr/bin/X11/X" -msgstr "command=/usr/bin/X11/X" +#~ msgid "command=/usr/bin/X11/X" +#~ msgstr "command=/usr/bin/X11/X" -#: ../C/gdm.xml:3472 (para) #, fuzzy -msgid "" -"The command to execute, with full path to the binary of the X server, and " -"any extra arguments needed." -msgstr "El comando a ejecutar, con ruta completa al binario del servidor X, y cualesquier argumentos adicionales necesitados." +#~ msgid "" +#~ "The command to execute, with full path to the binary of the X server, and " +#~ "any extra arguments needed." +#~ msgstr "" +#~ "El comando a ejecutar, con ruta completa al binario del servidor X, y " +#~ "cualesquier argumentos adicionales necesitados." -#: ../C/gdm.xml:3480 (term) -msgid "flexible" -msgstr "flexible" +#~ msgid "flexible" +#~ msgstr "flexible" -#: ../C/gdm.xml:3482 (synopsis) -#, no-wrap -msgid "flexible=true" -msgstr "flexible=true" +#~ msgid "flexible=true" +#~ msgstr "flexible=true" -#: ../C/gdm.xml:3483 (para) #, fuzzy -msgid "" -"Indicates if this server is available as a choice when a user wishes to run " -"a flexible, on demand server." -msgstr "flexible." +#~ msgid "" +#~ "Indicates if this server is available as a choice when a user wishes to " +#~ "run a flexible, on demand server." +#~ msgstr "flexible." -#: ../C/gdm.xml:3491 (term) -msgid "handled" -msgstr "handled" +#~ msgid "handled" +#~ msgstr "handled" -#: ../C/gdm.xml:3493 (synopsis) -#, no-wrap -msgid "handled=true" -msgstr "handled=true" +#~ msgid "handled=true" +#~ msgstr "handled=true" -#: ../C/gdm.xml:3494 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename></filename> command." - -#: ../C/gdm.xml:3510 (term) -msgid "chooser" -msgstr "chooser" - -#: ../C/gdm.xml:3512 (synopsis) -#, no-wrap -msgid "chooser=false" -msgstr "chooser=false" - -#: ../C/gdm.xml:3513 (para) +#~ msgid "" +#~ "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." +#~ msgstr "<filename></filename> command." + +#~ msgid "chooser" +#~ msgstr "chooser" + +#~ msgid "chooser=false" +#~ msgstr "chooser=false" + #, fuzzy -msgid "" -"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." -msgstr "chooser." +#~ msgid "" +#~ "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." +#~ msgstr "chooser." -#: ../C/gdm.xml:3526 (title) #, fuzzy -msgid "Local Static X Display Configuration" -msgstr "Configuración de la pantalla X local estática" +#~ msgid "Local Static X Display Configuration" +#~ msgstr "Configuración de la pantalla X local estática" -#: ../C/gdm.xml:3528 (para) -msgid "" -"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>." -msgstr "" +#~ msgid "[servers]" +#~ msgstr "[servers]" -#: ../C/gdm.xml:3543 (para) -msgid "" -"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>gdm.conf-custom</filename> " -"file overrides values in the <filename>gdm.conf</filename> file." -msgstr "" +#~ msgid "<display number>" +#~ msgstr "<display number>" -#: ../C/gdm.xml:3553 (title) -msgid "[servers]" -msgstr "[servers]" +#~ msgid "0=Standard" +#~ msgstr "0=Standard" -#: ../C/gdm.xml:3556 (term) -msgid "<display number>" -msgstr "<display number>" +#, fuzzy +#~ msgid "" +#~ "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)." +#~ msgstr "command." -#: ../C/gdm.xml:3558 (synopsis) -#, no-wrap -msgid "0=Standard" -msgstr "0=Standard" +#, fuzzy +#~ msgid "" +#~ "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>gdm.conf-" +#~ "custom</filename> to turn off a display that is defined in the " +#~ "<filename>gdm.conf</filename> file." +#~ msgstr "command nombre command<filename></filename><filename></filename>." -#: ../C/gdm.xml:3559 (para) #, fuzzy -msgid "" -"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)." -msgstr "command." +#~ msgid "" +#~ "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." +#~ msgstr "<filename>< ServAuthDir></filename> command." -#: ../C/gdm.xml:3565 (para) #, fuzzy -msgid "" -"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>gdm.conf-custom</filename> to " -"turn off a display that is defined in the <filename>gdm.conf</filename> file." -msgstr "command nombre command<filename></filename><filename></filename>." +#~ msgid "" +#~ "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." +#~ msgstr "command<filename> VTAllocation</filename>." -#: ../C/gdm.xml:3578 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename>< ServAuthDir></filename> command." +#~ msgid "" +#~ "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." +#~ msgstr "<filename></filename><filename> DisallowTCP</filename>." -#: ../C/gdm.xml:3585 (para) #, fuzzy -msgid "" -"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." -msgstr "command<filename> VTAllocation</filename>." +#~ msgid "Per User Configuration" +#~ msgstr "Configuración por usuario" -#: ../C/gdm.xml:3594 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename></filename><filename> DisallowTCP</filename>." +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "Hay algunos ajustes de configuración por usuario que controlan cómo se " +#~ "comporta GDM. GDM es bastante estricto con el propietario y los permisos " +#~ "de los archivos de usuario a los que accede, e ignorará los archivos si " +#~ "no pertenecen al usuario o tienen permiso de escritura para el grupo o " +#~ "para todos. Ignorará el usuario si la carpeta personal del usuario " +#~ "($HOME) no pertenece al usuario o si la carpeta $HOME tiene permiso de " +#~ "escritura para el grupo o para todos. Los archivos deben ser además más " +#~ "pequeños que el valor <filename>UserMaxFile</filename> tal como se define " +#~ "en la configuración de GDM. Si parece que GDM no está accediendo " +#~ "apropiadamente a los ajustes de configuración del usuario, el problema se " +#~ "debe la mayoría de las veces a que una de estas comprobaciones falla." -#: ../C/gdm.xml:3604 (term) -msgid "priority" -msgstr "" +#, fuzzy +#~ msgid "" +#~ "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>." +#~ msgstr "" +#~ "Primero está el archivo <filename>~/.dmrc</filename>. En teoría este " +#~ "archivo debería ser compartido entre GDM y KDM, así que los usuarios sólo " +#~ "tienen que configurar las cosas una vez. Esto es un archivo de " +#~ "configuración de estilo <filename>.ini</filename> estándar. Tiene una " +#~ "sección llamada <filename>[Desktop]</filename> que tiene dos claves: " +#~ "<filename>Session</filename> y <filename>Language</filename>." -#: ../C/gdm.xml:3606 (synopsis) -#, no-wrap -msgid "priority=0" -msgstr "" +#, fuzzy +#~ msgid "" +#~ "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:" +#~ msgstr "" +#~ "La clave <filename>Session</filename> especifica el nombre base del " +#~ "archivo <filename>.desktop</filename> de sesión que el usuario quiere " +#~ "usar normalmente (sin la extensión <filename>.desktop</filename>, en " +#~ "otras palabras). La clave <filename>Language</filename> especifica el " +#~ "idioma que el usuario quiere usar por omisión. Si cualquiera de estas dos " +#~ "claves falta, se usa el predeterminado del sistema. El archivo " +#~ "normalmente tiene la apariencia siguiente:" -#: ../C/gdm.xml:3607 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "\n" +#~ "[Desktop]\n" +#~ "Session=gnome\n" +#~ "Language=cs_CZ.UTF-8\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "[Desktop]\n" +#~ "Session=gnome\n" +#~ "Language=cs_CZ.UTF-8\n" +#~ " " -#: ../C/gdm.xml:3623 (title) #, fuzzy -msgid "Per User Configuration" -msgstr "Configuración por usuario" +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "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." -#: ../C/gdm.xml:3625 (para) #, fuzzy -msgid "" -"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." -msgstr "Hay algunos ajustes de configuración por usuario que controlan cómo se comporta GDM. GDM es bastante estricto con el propietario y los permisos de los archivos de usuario a los que accede, e ignorará los archivos si no pertenecen al usuario o tienen permiso de escritura para el grupo o para todos. Ignorará el usuario si la carpeta personal del usuario ($HOME) no pertenece al usuario o si la carpeta $HOME tiene permiso de escritura para el grupo o para todos. Los archivos deben ser además más pequeños que el valor <filename>UserMaxFile</filename> tal como se define en la configuración de GDM. Si parece que GDM no está accediendo apropiadamente a los ajustes de configuración del usuario, el problema se debe la mayoría de las veces a que una de estas comprobaciones falla." - -#: ../C/gdm.xml:3639 (para) -#, fuzzy -msgid "" -"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>." -msgstr "Primero está el archivo <filename>~/.dmrc</filename>. En teoría este archivo debería ser compartido entre GDM y KDM, así que los usuarios sólo tienen que configurar las cosas una vez. Esto es un archivo de configuración de estilo <filename>.ini</filename> estándar. Tiene una sección llamada <filename>[Desktop]</filename> que tiene dos claves: <filename>Session</filename> y <filename>Language</filename>." +#~ msgid "" +#~ "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 $HOME/.face 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." +#~ msgstr "" +#~ "Si está activada la visualización de rostros, entonces se accede al " +#~ "archivo <filename>$HOME/.face</filename>. Este archivo debería ser una " +#~ "imagen estándar que GTK+ pueda leer, como PNG o JPEG. Además debe ser más " +#~ "pequeña que los valores <filename>MaxIconWidth</filename> y " +#~ "<filename>MaxIconHeight</filename> definidos en la configuración de GDM o " +#~ "será ignorada. Los usuarios pueden ejecutar el comando " +#~ "<command>gdmphotosetup</command> para especificar una imagen para el " +#~ "rostro y se copiará el archivo al lugar $HOME/.face escalándose para que " +#~ "su dimensión más larga no sea mayor que los valores " +#~ "<filename>MaxIconWidth</filename> o <filename>MaxIconHeight</filename>. " +#~ "<command>gdmphotosetup</command> tiene cuidado de no cambiar las " +#~ "proporciones de la imagen." -#: ../C/gdm.xml:3648 (para) #, fuzzy -msgid "" -"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:" -msgstr "La clave <filename>Session</filename> especifica el nombre base del archivo <filename>.desktop</filename> de sesión que el usuario quiere usar normalmente (sin la extensión <filename>.desktop</filename>, en otras palabras). La clave <filename>Language</filename> especifica el idioma que el usuario quiere usar por omisión. Si cualquiera de estas dos claves falta, se usa el predeterminado del sistema. El archivo normalmente tiene la apariencia siguiente:" - -#: ../C/gdm.xml:3657 (screen) -#, no-wrap -msgid "" -"\n" -"[Desktop]\n" -"Session=gnome\n" -"Language=cs_CZ.UTF-8\n" -" " -msgstr "" -"\n" -"[Desktop]\n" -"Session=gnome\n" -"Language=cs_CZ.UTF-8\n" -" " +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "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. " -#: ../C/gdm.xml:3663 (para) #, fuzzy -msgid "" -"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." -msgstr "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." +#~ msgid "Controlling GDM" +#~ msgstr "Controlando GDM" -#: ../C/gdm.xml:3669 (para) #, fuzzy -msgid "" -"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 $HOME/.face 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." -msgstr "" -"Si está activada la visualización de rostros, entonces se accede al archivo <filename>$HOME/.face</" -"filename>. Este archivo debería ser una imagen estándar que GTK+ pueda leer, como PNG o JPEG. Además debe ser más pequeña que los valores <filename>MaxIconWidth</filename> y <filename>MaxIconHeight</filename> definidos en la configuración de GDM o será ignorada. Los usuarios pueden ejecutar el comando <command>gdmphotosetup</command> para especificar una imagen para el rostro y se copiará el archivo al lugar " -"$HOME/.face escalándose para que su dimensión más larga no sea mayor que los valores <filename>MaxIconWidth</filename> o <filename>MaxIconHeight</filename>. <command>gdmphotosetup</command> tiene cuidado de no cambiar las proporciones de la imagen." +#~ msgid "" +#~ "You can control GDM behavior during runtime in several different ways. " +#~ "You can either run certain commands, or you can talk to GDM using either " +#~ "a unix socket protocol, or a FIFO protocol." +#~ msgstr "" +#~ "Puede controlar el comportamiento de GDM durante la ejecución de varias " +#~ "formas diferentes. Puede o ejecutar ciertos comandos, o puede hablar con " +#~ "GDM usando un protocolo de sockets UNIX, o un protocolo FIFO." -#: ../C/gdm.xml:3684 (para) -#, fuzzy -msgid "" -"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." -msgstr "" -"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. " +#~ msgid "Commands" +#~ msgstr "Comandos" -#: ../C/gdm.xml:3696 (title) #, fuzzy -msgid "Controlling GDM" -msgstr "Controlando GDM" +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "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." -#: ../C/gdm.xml:3698 (para) #, fuzzy -msgid "" -"You can control GDM behavior during runtime in several different ways. You " -"can either run certain commands, or you can talk to GDM using either a unix " -"socket protocol, or a FIFO protocol." -msgstr "Puede controlar el comportamiento de GDM durante la ejecución de varias formas diferentes. Puede o ejecutar ciertos comandos, o puede hablar con GDM usando un protocolo de sockets UNIX, o un protocolo FIFO." +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "<command></command> command flexible command flexible<command></" +#~ "command><command></command>." -#: ../C/gdm.xml:3705 (title) -msgid "Commands" -msgstr "Comandos" +#, fuzzy +#~ msgid "The FIFO protocol" +#~ msgstr "El protocolo FIFO" -#: ../C/gdm.xml:3707 (para) #, fuzzy -msgid "" -"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." -msgstr "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." - -#: ../C/gdm.xml:3720 (para) +#~ msgid "" +#~ "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)." +#~ msgstr "" +#~ "<filename></filename><filename> ServAuthDir</filename><filename><></" +#~ "filename> command." + #, fuzzy -msgid "" -"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." -msgstr "<command></command> command flexible command flexible<command></command><command></command>." +#~ msgid "Socket Protocol" +#~ msgstr "El protocolo socket" -#: ../C/gdm.xml:3736 (title) #, fuzzy -msgid "The FIFO protocol" -msgstr "El protocolo FIFO" +#~ msgid "" +#~ "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." +#~ msgstr "<filename></filename><command></command> command flexible." -#: ../C/gdm.xml:3738 (para) #, fuzzy -msgid "" -"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)." -msgstr "<filename></filename><filename> ServAuthDir</filename><filename><></filename> command." - -#: ../C/gdm.xml:3749 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "gdmflexiserver accepts the following commands with the --command option:" +#~ msgstr "command:" -#: ../C/gdm.xml:3761 (title) #, fuzzy -msgid "Socket Protocol" -msgstr "El protocolo socket" +#~ msgid "" +#~ "\n" +#~ "VERSION\n" +#~ "AUTH_LOCAL\n" +#~ "FLEXI_XSERVER\n" +#~ "FLEXI_XNEST\n" +#~ "ATTACHED_SERVERS\n" +#~ "ALL_SERVERS\n" +#~ "GET_SERVER_LIST\n" +#~ "GET_SERVER_DETAILS\n" +#~ "GET_CONFIG\n" +#~ "GET_CONFIG_FILE\n" +#~ "UPDATE_CONFIG\n" +#~ "GREETERPIDS\n" +#~ "QUERY_LOGOUT_ACTION\n" +#~ "SET_LOGOUT_ACTION\n" +#~ "SET_SAFE_LOGOUT_ACTION\n" +#~ "QUERY_VT\n" +#~ "SET_VT\n" +#~ "CLOSE\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "VERSION\n" +#~ "AUTH_LOCAL\n" +#~ "FLEXI_XSERVER\n" +#~ "FLEXI_XNEST\n" +#~ "ATTACHED_SERVERS\n" +#~ "ALL_SERVERS\n" +#~ "GET_SERVER_LIST\n" +#~ "GET_SERVER_DETAILS\n" +#~ "GET_CONFIG\n" +#~ "GET_CONFIG_FILE\n" +#~ "UPDATE_CONFIG\n" +#~ "GREETERPIDS\n" +#~ "QUERY_LOGOUT_ACTION\n" +#~ "SET_LOGOUT_ACTION\n" +#~ "SET_SAFE_LOGOUT_ACTION\n" +#~ "QUERY_VT\n" +#~ "SET_VT\n" +#~ "CLOSE\n" +#~ " " + +#~ msgid "VERSION" +#~ msgstr "VERSION" -#: ../C/gdm.xml:3763 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename></filename><command></command> command flexible." - -#: ../C/gdm.xml:3773 (para) -#, fuzzy -msgid "gdmflexiserver accepts the following commands with the --command option:" -msgstr "command:" - -#: ../C/gdm.xml:3778 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"VERSION\n" -"AUTH_LOCAL\n" -"FLEXI_XSERVER\n" -"FLEXI_XNEST\n" -"ATTACHED_SERVERS\n" -"ALL_SERVERS\n" -"GET_SERVER_LIST\n" -"GET_SERVER_DETAILS\n" -"GET_CONFIG\n" -"GET_CONFIG_FILE\n" -"UPDATE_CONFIG\n" -"GREETERPIDS\n" -"QUERY_LOGOUT_ACTION\n" -"SET_LOGOUT_ACTION\n" -"SET_SAFE_LOGOUT_ACTION\n" -"QUERY_VT\n" -"SET_VT\n" -"CLOSE\n" -" " -msgstr "" -"\n" -"VERSION\n" -"AUTH_LOCAL\n" -"FLEXI_XSERVER\n" -"FLEXI_XNEST\n" -"ATTACHED_SERVERS\n" -"ALL_SERVERS\n" -"GET_SERVER_LIST\n" -"GET_SERVER_DETAILS\n" -"GET_CONFIG\n" -"GET_CONFIG_FILE\n" -"UPDATE_CONFIG\n" -"GREETERPIDS\n" -"QUERY_LOGOUT_ACTION\n" -"SET_LOGOUT_ACTION\n" -"SET_SAFE_LOGOUT_ACTION\n" -"QUERY_VT\n" -"SET_VT\n" -"CLOSE\n" -" " - -#: ../C/gdm.xml:3799 (para) -msgid "" -"These are described in detail below, including required arguments, response " -"format, and return codes." -msgstr "" +#~ msgid "" +#~ "\n" +#~ "VERSION: Query GDM version\n" +#~ "Supported since: 2.2.4.0\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " GDM <gdm version>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "VERSION: Query GDM version\n" +#~ "Supported since: 2.2.4.0\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " GDM <gdm version>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " -#: ../C/gdm.xml:3805 (title) -msgid "VERSION" -msgstr "VERSION" +#~ msgid "AUTH_LOCAL" +#~ msgstr "AUTH_LOCAL" -#: ../C/gdm.xml:3806 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"VERSION: Query GDM version\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers:\n" -" GDM <gdm version>\n" -" ERROR <err number> <english error description>\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"VERSION: Query GDM version\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers:\n" -" GDM <gdm version>\n" -" ERROR <err number> <english error description>\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " - -#: ../C/gdm.xml:3819 (title) -msgid "AUTH_LOCAL" -msgstr "AUTH_LOCAL" - -#: ../C/gdm.xml:3820 (screen) -#, no-wrap -#, fuzzy -msgid "" -"\n" -"AUTH_LOCAL: Setup this connection as authenticated for\n" -" FLEXI_SERVER. Because all full blown (non-Xnest)\n" -" displays can be started only from users logged in\n" -" locally, and here GDM assumes only users logged\n" -" in from GDM. They must pass the xauth\n" -" MIT-MAGIC-COOKIE-1 that they were passed before\n" -" the connection is authenticated.\n" -"Note: The AUTH LOCAL command requires the\n" -" --authenticate option, although only\n" -" FLEXI XSERVER uses this currently.\n" -"Note: Since 2.6.0.6 you can also use a global\n" -" <ServAuthDir>/.cookie, which works for all\n" -" authentication except for SET_LOGOUT_ACTION and\n" -" QUERY_LOGOUT_ACTION and SET_SAFE_LOGOUT_ACTION\n" -" which require a logged in display.\n" -"Supported since: 2.2.4.0\n" -"Arguments: <xauth cookie>\n" -" <xauth cookie> is in hex form with no 0x prefix\n" -"Answers:\n" -" OK\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 100 = Not authenticated\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -" Xnest\n" -"\n" -"\n" -"\n" -"\n" -" command\n" -"\n" -"\n" -"< ServAuthDir>\n" -"\n" -"\n" -"<>\n" -"<>\n" -"\n" -"<><>\n" -"\n" -"\n" -"\n" -" " - -#: ../C/gdm.xml:3850 (title) -msgid "FLEXI_XSERVER" -msgstr "FLEXI_XSERVER" - -#: ../C/gdm.xml:3851 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"FLEXI_XSERVER: Start a new X flexible display. Only supported on\n" -" connection that passed AUTH_LOCAL\n" -"Supported since: 2.2.4.0\n" -"Arguments: <xserver type>\n" -" If no arguments, starts the standard X server\n" -"Answers:\n" -" OK <display>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 1 = No more flexi servers\n" -" 2 = Startup errors\n" -" 3 = X failed\n" -" 4 = X too busy\n" -" 6 = No server binary\n" -" 100 = Not authenticated\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"flexible\n" -"<>\n" -"\n" -"<>\n" -"<><>\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -" " - -#: ../C/gdm.xml:3873 (title) -msgid "FLEXI_XNEST" -msgstr "FLEXI_XNEST" - -#: ../C/gdm.xml:3874 (screen) -#, no-wrap #, fuzzy -msgid "" -"\n" -"FLEXI_XNEXT: Start a new flexible Xnest display.\n" -"Note: Supported on older version from 2.2.4.0, later\n" -" 2.2.4.2, but since 2.3.90.4 you must supply 4\n" -" arguments or ERROR 100 will be returned. This\n" -" will start Xnest using the XAUTHORITY file\n" -" supplied and as the uid same as the owner of\n" -" that file (and same as you supply). You must\n" -" also supply the cookie as the third argument\n" -" for this display, to prove that you indeed are\n" -" this user. Also this file must be readable\n" -" ONLY by this user, that is have a mode of 0600.\n" -" If this all is not met, ERROR 100 is returned.\n" -"Note: The cookie should be the MIT-MAGIC-COOKIE-1,\n" -" the first one GDM can find in the XAUTHORITY\n" -" file for this display. If that's not what you\n" -" use you should generate one first. The cookie\n" -" should be in hex form.\n" -"Supported since: 2.3.90.4\n" -"Arguments: <display to run on> <uid of requesting user>\n" -" <xauth cookie for the display> <xauth file>\n" -"Answers:\n" -" OK <display>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 1 = No more flexi servers\n" -" 2 = Startup errors\n" -" 3 = X failed\n" -" 4 = X too busy\n" -" 5 = Xnest can't connect\n" -" 6 = No server binary\n" -" 100 = Not authenticated\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"flexible Xnest\n" -"\n" -"\n" -" Xnest\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"<><>\n" -"<><>\n" -"<>\n" -"<><>\n" -"\n" -"\n" -"\n" -"\n" -"\n" -" Xnest\n" -"\n" -"\n" -"\n" -" " - -#: ../C/gdm.xml:3912 (title) -msgid "ADD_DYNAMIC_DISPLAY" -msgstr "ADD_DYNAMIC_DISPLAY" - -#: ../C/gdm.xml:3913 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"ADD_DYNAMIC_DISPLAY: Create a new server definition that will\n" -" run on the specified display leaving, it\n" -" in DISPLAY_CONFIG state.\n" -"Supported since: 2.8.0.0\n" -"Arguments: <display to run on>=<server>\n" -" Where <server> is either a configuration named in the\n" -" GDM configuration or a literal command name.\n" -"Answers:\n" -" OK <display>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 2 = Existing display\n" -" 3 = No server string\n" -" 4 = Display startup failure\n" -" 100 = Not authenticated\n" -" 200 = Dynamic Displays not allowed\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"ADD_DYNAMIC_DISPLAY: Create a new server definition that will\n" -" run on the specified display leaving, it\n" -" in DISPLAY_CONFIG state.\n" -"Supported since: 2.8.0.0\n" -"Arguments: <display to run on>=<server>\n" -" Where <server> is either a configuration named in the\n" -" GDM configuration or a literal command name.\n" -"Answers:\n" -" OK <display>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 2 = Existing display\n" -" 3 = No server string\n" -" 4 = Display startup failure\n" -" 100 = Not authenticated\n" -" 200 = Dynamic Displays not allowed\n" -" 999 = Unknown error\n" -" " - -#: ../C/gdm.xml:3935 (title) -msgid "RELEASE_DYNAMIC_DISPLAYS" -msgstr "RELEASE_DYNAMIC_DISPLAYS" - -#: ../C/gdm.xml:3936 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in \n" -" DISPLAY_CONFIG state\n" -"Supported since: 2.8.0.0\n" -"Arguments: None\n" -"Answers:\n" -" OK <display>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 100 = Not authenticated\n" -" 200 = Dynamic Displays not allowed\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in \n" -" DISPLAY_CONFIG state\n" -"Supported since: 2.8.0.0\n" -"Arguments: None\n" -"Answers:\n" -" OK <display>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 100 = Not authenticated\n" -" 200 = Dynamic Displays not allowed\n" -" 999 = Unknown error\n" -" " - -#: ../C/gdm.xml:3952 (title) -msgid "REMOVE_DYNAMIC_DISPLAY" -msgstr "REMOVE_DYNAMIC_DISPLAY" - -#: ../C/gdm.xml:3953 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server\n" -" and purging the display configuration\n" -"Supported since: 2.8.0.0\n" -"Arguments: <display to remove>\n" -"Answers:\n" -" OK <display>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 1 = Bad display number\n" -" 100 = Not authenticated\n" -" 200 = Dynamic Displays not allowed\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server\n" -" and purging the display configuration\n" -"Supported since: 2.8.0.0\n" -"Arguments: <display to remove>\n" -"Answers:\n" -" OK <display>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 1 = Bad display number\n" -" 100 = Not authenticated\n" -" 200 = Dynamic Displays not allowed\n" -" 999 = Unknown error\n" -" " - -#: ../C/gdm.xml:3970 (title) -msgid "ATTACHED_SERVERS" -msgstr "ATTACHED_SERVERS" - -#: ../C/gdm.xml:3971 (screen) -#, no-wrap +#~ msgid "" +#~ "\n" +#~ "AUTH_LOCAL: Setup this connection as authenticated for\n" +#~ " FLEXI_SERVER. Because all full blown (non-Xnest)\n" +#~ " displays can be started only from users logged in\n" +#~ " locally, and here GDM assumes only users logged\n" +#~ " in from GDM. They must pass the xauth\n" +#~ " MIT-MAGIC-COOKIE-1 that they were passed before\n" +#~ " the connection is authenticated.\n" +#~ "Note: The AUTH LOCAL command requires the\n" +#~ " --authenticate option, although only\n" +#~ " FLEXI XSERVER uses this currently.\n" +#~ "Note: Since 2.6.0.6 you can also use a global\n" +#~ " <ServAuthDir>/.cookie, which works for all\n" +#~ " authentication except for SET_LOGOUT_ACTION and\n" +#~ " QUERY_LOGOUT_ACTION and SET_SAFE_LOGOUT_ACTION\n" +#~ " which require a logged in display.\n" +#~ "Supported since: 2.2.4.0\n" +#~ "Arguments: <xauth cookie>\n" +#~ " <xauth cookie> is in hex form with no 0x prefix\n" +#~ "Answers:\n" +#~ " OK\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ " Xnest\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " command\n" +#~ "\n" +#~ "\n" +#~ "< ServAuthDir>\n" +#~ "\n" +#~ "\n" +#~ "<>\n" +#~ "<>\n" +#~ "\n" +#~ "<><>\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " " + +#~ msgid "FLEXI_XSERVER" +#~ msgstr "FLEXI_XSERVER" + #, fuzzy -msgid "" -"\n" -"ATTACHED_SERVERS: List all attached displays. Doesn't list XDMCP\n" -" and xnest non-attached displays.\n" -"Note: This command used to be named CONSOLE_SERVERS,\n" -" which is still recognized for backwards\n" -" compatibility. The optional pattern argument\n" -" is supported as of version 2.8.0.0.\n" -"Supported since: 2.2.4.0\n" -"Arguments: <pattern> (optional)\n" -" With no argument, all attached displays are returned. The optional\n" -" <pattern> is a string that may contain glob characters '*', '?', and\n" -" '[]'. Only displays that match the pattern will be returned.\n" -"Answers:\n" -" OK <server>;<server>;...\n" -"\n" -" <server> is <display>,<logged in user>,<vt or xnest display>\n" -"\n" -" <logged in user> can be empty in case no one logged\n" -" in yet, and <vt> can be -1 if it's not known or not\n" -" supported (on non-Linux for example). If the display is an\n" -" xnest display and is a console one (that is, it is an xnest\n" -" inside another console display) it is listed and instead of\n" -" vt, it lists the parent display in standard form.\n" -"\n" -" ERROR <err number> <english error description>\n" -" 1 = Not implemented\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"list XDMCP\n" -" command\n" -"\n" -"\n" -"<>\n" -"\n" -"<>\n" -"\n" -"<><>\n" -"<><><><>\n" -"<>\n" -"<>\n" -"\n" -"\n" -"\n" -"\n" -"<><>\n" -"\n" -"\n" -" " - -#: ../C/gdm.xml:4003 (title) -msgid "ALL_SERVERS" -msgstr "ALL_SERVERS" - -#: ../C/gdm.xml:4004 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"ALL_SERVERS: List all displays, including console, remote, xnest.\n" -" This can, for example, be useful to figure out if\n" -" the display you are on is managed by the gdm daemon,\n" -" by seeing if it is in the list. It is also somewhat\n" -" like the 'w' command but for graphical sessions.\n" -"Supported since: 2.4.2.96\n" -"Arguments: None\n" -"Answers:\n" -" OK <server>;<server>;...\n" -"\n" -" <server> is <display>,<logged in user>\n" -"\n" -" <logged in user> can be empty in case no one logged in yet\n" -"\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"\n" -"\n" -" list\n" -" command\n" -"<><>\n" -"<><><>\n" -"<>\n" -"<><>\n" -"\n" -"\n" -" " - -#: ../C/gdm.xml:4027 (title) -#, fuzzy -msgid "GET_SERVER_LIST" -msgstr "GET_SERVER_LIST" - -#: ../C/gdm.xml:4028 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"GET_SERVER_LIST: Get a list of the server sections from\n" -" the configuration file.\n" -"Supported since: 2.13.0.4\n" -"Arguments: None\n" -"Answers:\n" -" OK <value>;<value>;...\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 1 = No servers found\n" -" 50 = Unsupported key\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"list\n" -"\n" -"<><>\n" -"<><>\n" -"\n" -"\n" -"\n" -"\n" -" " - -#: ../C/gdm.xml:4045 (title) -#, fuzzy -msgid "GET_SERVER_DETAILS" -msgstr "GET_SERVER_DETAILS" - -#: ../C/gdm.xml:4046 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"GET_SERVER_DETAILS: Get detail information for a specific server.\n" -"Supported since: 2.13.0.4\n" -"Arguments: <server> <key>\n" -" Key values include:\n" -" NAME - Returns the server name\n" -" COMMAND - Returns the server command\n" -" FLEXIBLE - Returns \"true\" if flexible, \"false\"\n" -" otherwise\n" -" CHOOSABLE - Returns \"true\" if choosable, \"false\"\n" -" otherwise\n" -" HANDLED - Returns \"true\" if handled, \"false\"\n" -" otherwise\n" -" CHOOSER - Returns \"true\" if chooser, \"false\"\n" -" otherwise\n" -" PRIORITY - Returns process priority\n" -"Answers:\n" -" OK <value>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 1 = Server not found\n" -" 2 = Key not valid\n" -" 50 = Unsupported key\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"<><>\n" -"\n" -" nombre\n" -" command\n" -" flexible\n" -"\n" -"\n" -"\n" -" handled\n" -"\n" -" chooser\n" -"\n" -"\n" -"<>\n" -"<><>\n" -"\n" -"\n" -"\n" -"\n" -"\n" -" " - -#: ../C/gdm.xml:4075 (title) -msgid "GET_CONFIG" -msgstr "GET_CONFIG" - -#: ../C/gdm.xml:4076 (screen) -#, no-wrap +#~ msgid "" +#~ "\n" +#~ "FLEXI_XSERVER: Start a new X flexible display. Only supported on\n" +#~ " connection that passed AUTH_LOCAL\n" +#~ "Supported since: 2.2.4.0\n" +#~ "Arguments: <xserver type>\n" +#~ " If no arguments, starts the standard X server\n" +#~ "Answers:\n" +#~ " OK <display>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 1 = No more flexi servers\n" +#~ " 2 = Startup errors\n" +#~ " 3 = X failed\n" +#~ " 4 = X too busy\n" +#~ " 6 = No server binary\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "flexible\n" +#~ "<>\n" +#~ "\n" +#~ "<>\n" +#~ "<><>\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " " + +#~ msgid "FLEXI_XNEST" +#~ msgstr "FLEXI_XNEST" + #, fuzzy -msgid "" -"\n" -"GET_CONFIG: Get configuration value for key. Useful so\n" -" that other applications can request configuration\n" -" information from GDM. Any key defined as GDM_KEY_*\n" -" in gdm.h is supported. Starting with version 2.13.0.2\n" -" translated keys (such as \"greeter/GdmWelcome[cs]\" are\n" -" supported via GET_CONFIG. Also starting with version\n" -" 2.13.0.2 it is no longer necessary to include the\n" -" default value (i.e. you can use key \"greeter/IncludeAll\"\n" -" instead of having to use \"greeter/IncludeAll=false\". \n" -"Supported since: 2.6.0.9\n" -"Arguments: <key>\n" -"Answers:\n" -" OK <value>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 50 = Unsupported key\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -" IncludeAll\n" -" IncludeAll<>\n" -"<>\n" -"<><>\n" -"\n" -"\n" -"\n" -" " - -#: ../C/gdm.xml:4099 (title) -msgid "GET_CONFIG_FILE" -msgstr "GET_CONFIG_FILE" - -#: ../C/gdm.xml:4100 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"GET_CONFIG_FILE: Get config file location being used by\n" -" the daemon. If the GDM daemon was started\n" -" with the --config option, it will return\n" -" the value passed in via the argument.\n" -"Supported since: 2.8.0.2\n" -"Arguments: None\n" -"Answers:\n" -" OK <full path to GDM configuration file>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"VERSION: Query version\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers:\n" -" GDM <gdm version>\n" -" ERROR <err number> <english error description>\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " - -#: ../C/gdm.xml:4117 (title) -msgid "UPDATE_CONFIG" -msgstr "UPDATE_CONFIG" - -#: ../C/gdm.xml:4118 (screen) -#, no-wrap +#~ msgid "" +#~ "\n" +#~ "FLEXI_XNEXT: Start a new flexible Xnest display.\n" +#~ "Note: Supported on older version from 2.2.4.0, later\n" +#~ " 2.2.4.2, but since 2.3.90.4 you must supply 4\n" +#~ " arguments or ERROR 100 will be returned. This\n" +#~ " will start Xnest using the XAUTHORITY file\n" +#~ " supplied and as the uid same as the owner of\n" +#~ " that file (and same as you supply). You must\n" +#~ " also supply the cookie as the third argument\n" +#~ " for this display, to prove that you indeed are\n" +#~ " this user. Also this file must be readable\n" +#~ " ONLY by this user, that is have a mode of 0600.\n" +#~ " If this all is not met, ERROR 100 is returned.\n" +#~ "Note: The cookie should be the MIT-MAGIC-COOKIE-1,\n" +#~ " the first one GDM can find in the XAUTHORITY\n" +#~ " file for this display. If that's not what you\n" +#~ " use you should generate one first. The cookie\n" +#~ " should be in hex form.\n" +#~ "Supported since: 2.3.90.4\n" +#~ "Arguments: <display to run on> <uid of requesting user>\n" +#~ " <xauth cookie for the display> <xauth file>\n" +#~ "Answers:\n" +#~ " OK <display>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 1 = No more flexi servers\n" +#~ " 2 = Startup errors\n" +#~ " 3 = X failed\n" +#~ " 4 = X too busy\n" +#~ " 5 = Xnest can't connect\n" +#~ " 6 = No server binary\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "flexible Xnest\n" +#~ "\n" +#~ "\n" +#~ " Xnest\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "<><>\n" +#~ "<><>\n" +#~ "<>\n" +#~ "<><>\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " Xnest\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " " + +#~ msgid "ADD_DYNAMIC_DISPLAY" +#~ msgstr "ADD_DYNAMIC_DISPLAY" + #, fuzzy -msgid "" -"\n" -"UPDATE_CONFIG: Tell the daemon to re-read a key from the \n" -" GDM configuration file. Any user can request\n" -" that values are re-read but the daemon will\n" -" only do so if the file has been modified\n" -" since GDM first read the file. Only users\n" -" who can change the GDM configuration file\n" -" (normally writable only by the root user) can\n" -" actually modify the GDM configuration. This\n" -" command is useful to cause the GDM to update\n" -" itself to recognize a change made to the GDM\n" -" configuration file by the root user.\n" -"\n" -" Starting with version 2.13.0.0, all GDM keys are\n" -" supported except for the following:\n" -"\n" -" daemon/PidFile\n" -" daemon/ConsoleNotify\n" -" daemon/User\n" -" daemon/Group\n" -" daemon/LogDir\n" -" daemon/ServAuthDir\n" -" daemon/UserAuthDir\n" -" daemon/UserAuthFile\n" -" daemon/UserAuthFBDir\n" -"\n" -" GDM also supports the following Psuedokeys:\n" -"\n" -" xdmcp/PARAMETERS (2.3.90.2) updates the following:\n" -" xdmcp/MaxPending\n" -" xdmcp/MaxSessions\n" -" xdmcp/MaxWait\n" -" xdmcp/DisplaysPerHost\n" -" xdmcp/HonorIndirect\n" -" xdmcp/MaxPendingIndirect\n" -" xdmcp/MaxWaitIndirect\n" -" xdmcp/PingIntervalSeconds (only affects new connections)\n" -"\n" -" xservers/PARAMETERS (2.13.0.4) updates the following:\n" -" all [server-foo] sections.\n" -"\n" -" Supported keys for previous versions of GDM:\n" -"\n" -" security/AllowRoot (2.3.90.2)\n" -" security/AllowRemoteRoot (2.3.90.2)\n" -" security/AllowRemoteAutoLogin (2.3.90.2)\n" -" security/RetryDelay (2.3.90.2)\n" -" security/DisallowTCP (2.4.2.0)\n" -" daemon/Greeter (2.3.90.2)\n" -" daemon/RemoteGreeter (2.3.90.2)\n" -" xdmcp/Enable (2.3.90.2)\n" -" xdmcp/Port (2.3.90.2)\n" -" daemon/TimedLogin (2.3.90.3)\n" -" daemon/TimedLoginEnable (2.3.90.3)\n" -" daemon/TimedLoginDelay (2.3.90.3)\n" -" greeter/SystemMenu (2.3.90.3)\n" -" greeter/ConfigAvailable (2.3.90.3)\n" -" greeter/ChooserButton (2.4.2.0)\n" -" greeter/SoundOnLoginFile (2.5.90.0)\n" -" daemon/AddGtkModules (2.5.90.0)\n" -" daemon/GtkModulesList (2.5.90.0)\n" -"Supported since: 2.3.90.2\n" -"Arguments: <key>\n" -" <key> is just the base part of the key such as\n" -" \"security/AllowRemoteRoot\"\n" -"Answers:\n" -" OK\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 50 = Unsupported key\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -" command\n" -"\n" -"\n" -"\n" -"\n" -" PidFile\n" -" ConsoleNotify\n" -" User\n" -" Group\n" -" Directorio de registro\n" -" ServAuthDir\n" -" UserAuthDir\n" -" UserAuthFile\n" -" UserAuthFBDir\n" -"\n" -"\n" -"\n" -" MaxSessions\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -"\n" -" AllowRoot\n" -" AllowRemoteRoot\n" -" AllowRemoteAutoLogin\n" -"\n" -" DisallowTCP\n" -" Greeter\n" -" RemoteGreeter\n" -"\n" -"\n" -" TimedLogin\n" -" TimedLoginEnable\n" -" TimedLoginDelay\n" -"\n" -"\n" -" ChooserButton\n" -"\n" -" AddGtkModules\n" -" GtkModulesList<>\n" -"<>\n" -" AllowRemoteRoot\n" -"\n" -"<><>\n" -"\n" -"\n" -"\n" -" " - -#: ../C/gdm.xml:4194 (title) -msgid "GREETERPIDS" -msgstr "GREETERPIDS" - -#: ../C/gdm.xml:4195 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"GREETERPIDS: List all greeter pids so that one can send HUP\n" -" to them for config rereading. Of course one\n" -" must be root to do that.\n" -"Supported since: 2.3.90.2\n" -"Arguments: None\n" -"Answers:\n" -" OK <pid>;<pid>;...\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"VERSION: Query version\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers:\n" -" GDM <gdm version>\n" -" ERROR <err number> <english error description>\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " - -#: ../C/gdm.xml:4211 (title) -msgid "QUERY_LOGOUT_ACTION" -msgstr "QUERY_LOGOUT_ACTION" - -#: ../C/gdm.xml:4212 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"QUERY_LOGOUT_ACTION: Query which logout actions are possible\n" -" Only supported on connections that passed\n" -" AUTH_LOCAL.\n" -"Supported since: 2.5.90.0\n" -"Answers:\n" -" OK <action>;<action>;...\n" -" Where action is one of HALT, REBOOT or SUSPEND. An\n" -" empty list can also be returned if no action is possible.\n" -" A '!' is appended to an action if it was already set with\n" -" SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION. Note that\n" -" SET_LOGOUT_ACTION has precedence over\n" -" SET_SAFE_LOGOUT_ACTION.\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 100 = Not authenticated\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"\n" -"\n" -"<><>\n" -"\n" -" list\n" -"\n" -"\n" -"\n" -"\n" -"<><>\n" -"\n" -"\n" -"\n" -" " - -#: ../C/gdm.xml:4234 (title) -#, fuzzy -msgid "SET_LOGOUT_ACTION" -msgstr "SET_LOGOUT_ACTION" - -#: ../C/gdm.xml:4235 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -" slave process exits. Only supported on\n" -" connections that passed AUTH_LOCAL.\n" -"Supported since: 2.5.90.0\n" -"Arguments: <action>\n" -" NONE Set exit action to 'none'\n" -" HALT Set exit action to 'halt'\n" -" REBOOT Set exit action to 'reboot'\n" -" SUSPEND Set exit action to 'suspend'\n" -"Answers:\n" -" OK\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 7 = Unknown logout action, or not available\n" -" 100 = Not authenticated\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"VERSION: Query version\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers:\n" -" GDM <gdm version>\n" -" ERROR <err number> <english error description>\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " - -#: ../C/gdm.xml:4257 (title) -msgid "SET_SAFE_LOGOUT_ACTION" -msgstr "SET_SAFE_LOGOUT_ACTION" - -#: ../C/gdm.xml:4258 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"SET_SAFE_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend\n" -" after everybody logs out. If only one\n" -" person logs out, then this is obviously\n" -" the same as the SET_LOGOUT_ACTION. Note\n" -" that SET_LOGOUT_ACTION has precedence\n" -" over SET_SAFE_LOGOUT_ACTION if it is set\n" -" to something other then NONE. If no one\n" -" is logged in, then the action takes effect\n" -" effect immediately. Only supported on\n" -" connections that passed AUTH_LOCAL.\n" -"Supported since: 2.5.90.0\n" -"Arguments: <action>\n" -" NONE Set exit action to 'none'\n" -" HALT Set exit action to 'halt'\n" -" REBOOT Set exit action to 'reboot'\n" -" SUSPEND Set exit action to 'suspend'\n" -"Answers:\n" -" OK\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 7 = Unknown logout action, or not available\n" -" 100 = Not authenticated\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"VERSION: Query version\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers:\n" -" GDM <gdm version>\n" -" ERROR <err number> <english error description>\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " - -#: ../C/gdm.xml:4287 (title) -msgid "QUERY_VT" -msgstr "QUERY_VT" - -#: ../C/gdm.xml:4288 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"QUERY_VT: Ask the daemon about which VT we are currently on.\n" -" This is useful for logins which don't own\n" -" /dev/console but are still console logins. Only\n" -" supported on Linux currently, other places will\n" -" just get ERROR 8. This is also the way to query\n" -" if VT support is available in the daemon in the\n" -" first place. Only supported on connections that\n" -" passed AUTH_LOCAL.\n" -"Supported since: 2.5.90.0\n" -"Arguments: None\n" -"Answers:\n" -" OK <vt number>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 8 = Virtual terminals not supported\n" -" 100 = Not authenticated\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"VERSION: Query version\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers:\n" -" GDM <gdm version>\n" -" ERROR <err number> <english error description>\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " - -#: ../C/gdm.xml:4311 (title) -msgid "SET_VT" -msgstr "SET_VT" - -#: ../C/gdm.xml:4312 (screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"SET_VT: Change to the specified virtual terminal.\n" -" This is useful for logins which don't own /dev/console\n" -" but are still console logins. Only supported on Linux\n" -" currently, other places will just get ERROR 8.\n" -" Only supported on connections that passed AUTH_LOCAL.\n" -"Supported since: 2.5.90.0\n" -"Arguments: <vt>\n" -"Answers:\n" -" OK\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 8 = Virtual terminals not supported\n" -" 9 = Invalid virtual terminal number\n" -" 100 = Not authenticated\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " -msgstr "" -"\n" -"VERSION: Query version\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers:\n" -" GDM <gdm version>\n" -" ERROR <err number> <english error description>\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -" " - -#: ../C/gdm.xml:4333 (title) -msgid "CLOSE" -msgstr "CLOSE" - -#: ../C/gdm.xml:4334 (screen) -#, no-wrap -msgid "" -"\n" -"CLOSE: Close sockets connection\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers: None\n" -" " -msgstr "" +#~ msgid "" +#~ "\n" +#~ "ADD_DYNAMIC_DISPLAY: Create a new server definition that will\n" +#~ " run on the specified display leaving, it\n" +#~ " in DISPLAY_CONFIG state.\n" +#~ "Supported since: 2.8.0.0\n" +#~ "Arguments: <display to run on>=<server>\n" +#~ " Where <server> is either a configuration named in the\n" +#~ " GDM configuration or a literal command name.\n" +#~ "Answers:\n" +#~ " OK <display>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 2 = Existing display\n" +#~ " 3 = No server string\n" +#~ " 4 = Display startup failure\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Dynamic Displays not allowed\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "ADD_DYNAMIC_DISPLAY: Create a new server definition that will\n" +#~ " run on the specified display leaving, it\n" +#~ " in DISPLAY_CONFIG state.\n" +#~ "Supported since: 2.8.0.0\n" +#~ "Arguments: <display to run on>=<server>\n" +#~ " Where <server> is either a configuration named in the\n" +#~ " GDM configuration or a literal command name.\n" +#~ "Answers:\n" +#~ " OK <display>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 2 = Existing display\n" +#~ " 3 = No server string\n" +#~ " 4 = Display startup failure\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Dynamic Displays not allowed\n" +#~ " 999 = Unknown error\n" +#~ " " + +#~ msgid "RELEASE_DYNAMIC_DISPLAYS" +#~ msgstr "RELEASE_DYNAMIC_DISPLAYS" -#: ../C/gdm.xml:4347 (title) #, fuzzy -msgid "GDM Commands" -msgstr "Comandos de GDM" +#~ msgid "" +#~ "\n" +#~ "RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in \n" +#~ " DISPLAY_CONFIG state\n" +#~ "Supported since: 2.8.0.0\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " OK <display>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Dynamic Displays not allowed\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in \n" +#~ " DISPLAY_CONFIG state\n" +#~ "Supported since: 2.8.0.0\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " OK <display>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Dynamic Displays not allowed\n" +#~ " 999 = Unknown error\n" +#~ " " + +#~ msgid "REMOVE_DYNAMIC_DISPLAY" +#~ msgstr "REMOVE_DYNAMIC_DISPLAY" -#: ../C/gdm.xml:4350 (title) #, fuzzy -msgid "GDM User Commands" -msgstr "Comandos de usuario de GDM" +#~ msgid "" +#~ "\n" +#~ "REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server\n" +#~ " and purging the display configuration\n" +#~ "Supported since: 2.8.0.0\n" +#~ "Arguments: <display to remove>\n" +#~ "Answers:\n" +#~ " OK <display>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 1 = Bad display number\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Dynamic Displays not allowed\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server\n" +#~ " and purging the display configuration\n" +#~ "Supported since: 2.8.0.0\n" +#~ "Arguments: <display to remove>\n" +#~ "Answers:\n" +#~ " OK <display>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 1 = Bad display number\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Dynamic Displays not allowed\n" +#~ " 999 = Unknown error\n" +#~ " " + +#~ msgid "ATTACHED_SERVERS" +#~ msgstr "ATTACHED_SERVERS" -#: ../C/gdm.xml:4352 (para) -msgid "" -"The GDM package provides the following different commands in EXPANDED_BINDIR " -"intended to be used by the end-user:" -msgstr "" +#, fuzzy +#~ msgid "" +#~ "\n" +#~ "ATTACHED_SERVERS: List all attached displays. Doesn't list XDMCP\n" +#~ " and xnest non-attached displays.\n" +#~ "Note: This command used to be named CONSOLE_SERVERS,\n" +#~ " which is still recognized for backwards\n" +#~ " compatibility. The optional pattern argument\n" +#~ " is supported as of version 2.8.0.0.\n" +#~ "Supported since: 2.2.4.0\n" +#~ "Arguments: <pattern> (optional)\n" +#~ " With no argument, all attached displays are returned. The optional\n" +#~ " <pattern> is a string that may contain glob characters '*', '?', " +#~ "and\n" +#~ " '[]'. Only displays that match the pattern will be returned.\n" +#~ "Answers:\n" +#~ " OK <server>;<server>;...\n" +#~ "\n" +#~ " <server> is <display>,<logged in user>,<vt or " +#~ "xnest display>\n" +#~ "\n" +#~ " <logged in user> can be empty in case no one logged\n" +#~ " in yet, and <vt> can be -1 if it's not known or not\n" +#~ " supported (on non-Linux for example). If the display is an\n" +#~ " xnest display and is a console one (that is, it is an xnest\n" +#~ " inside another console display) it is listed and instead of\n" +#~ " vt, it lists the parent display in standard form.\n" +#~ "\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 1 = Not implemented\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "list XDMCP\n" +#~ " command\n" +#~ "\n" +#~ "\n" +#~ "<>\n" +#~ "\n" +#~ "<>\n" +#~ "\n" +#~ "<><>\n" +#~ "<><><><>\n" +#~ "<>\n" +#~ "<>\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "<><>\n" +#~ "\n" +#~ "\n" +#~ " " + +#~ msgid "ALL_SERVERS" +#~ msgstr "ALL_SERVERS" -#: ../C/gdm.xml:4358 (title) #, fuzzy -msgid "" -"<command>gdmXnestchooser</command> and <command>gdmXnest</command> Command " -"Line Options" -msgstr "Opciones de línea de comandos de <command>gdmXnestchooser</command> y <command>gdmXnest</command>" +#~ msgid "" +#~ "\n" +#~ "ALL_SERVERS: List all displays, including console, remote, xnest.\n" +#~ " This can, for example, be useful to figure out if\n" +#~ " the display you are on is managed by the gdm daemon,\n" +#~ " by seeing if it is in the list. It is also somewhat\n" +#~ " like the 'w' command but for graphical sessions.\n" +#~ "Supported since: 2.4.2.96\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " OK <server>;<server>;...\n" +#~ "\n" +#~ " <server> is <display>,<logged in user>\n" +#~ "\n" +#~ " <logged in user> can be empty in case no one logged in yet\n" +#~ "\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " list\n" +#~ " command\n" +#~ "<><>\n" +#~ "<><><>\n" +#~ "<>\n" +#~ "<><>\n" +#~ "\n" +#~ "\n" +#~ " " -#: ../C/gdm.xml:4361 (para) #, fuzzy -msgid "" -"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." -msgstr "<command></command> command<command> Xnest</command> XDMCP chooser chooser<command></command> XDMCP chooser<command></command> Xnest command<command></command> command." +#~ msgid "GET_SERVER_LIST" +#~ msgstr "GET_SERVER_LIST" -#: ../C/gdm.xml:4376 (title) #, fuzzy -msgid "<command>gdmXnestchooser</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmXnestchooser</command>" +#~ msgid "" +#~ "\n" +#~ "GET_SERVER_LIST: Get a list of the server sections from\n" +#~ " the configuration file.\n" +#~ "Supported since: 2.13.0.4\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " OK <value>;<value>;...\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 1 = No servers found\n" +#~ " 50 = Unsupported key\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "list\n" +#~ "\n" +#~ "<><>\n" +#~ "<><>\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " " -#: ../C/gdm.xml:4379 (term) #, fuzzy -msgid "-x, --xnest=STRING" -msgstr "-x, --xnest=STRING" +#~ msgid "GET_SERVER_DETAILS" +#~ msgstr "GET_SERVER_DETAILS" -#: ../C/gdm.xml:4381 (para) #, fuzzy -msgid "Xnest command line, default is \"Xnest\"" -msgstr "Línea de comandos de Xnest, lo predeterminado es «Xnest»" +#~ msgid "" +#~ "\n" +#~ "GET_SERVER_DETAILS: Get detail information for a specific server.\n" +#~ "Supported since: 2.13.0.4\n" +#~ "Arguments: <server> <key>\n" +#~ " Key values include:\n" +#~ " NAME - Returns the server name\n" +#~ " COMMAND - Returns the server command\n" +#~ " FLEXIBLE - Returns \"true\" if flexible, \"false\"\n" +#~ " otherwise\n" +#~ " CHOOSABLE - Returns \"true\" if choosable, \"false\"\n" +#~ " otherwise\n" +#~ " HANDLED - Returns \"true\" if handled, \"false\"\n" +#~ " otherwise\n" +#~ " CHOOSER - Returns \"true\" if chooser, \"false\"\n" +#~ " otherwise\n" +#~ " PRIORITY - Returns process priority\n" +#~ "Answers:\n" +#~ " OK <value>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 1 = Server not found\n" +#~ " 2 = Key not valid\n" +#~ " 50 = Unsupported key\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "<><>\n" +#~ "\n" +#~ " nombre\n" +#~ " command\n" +#~ " flexible\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " handled\n" +#~ "\n" +#~ " chooser\n" +#~ "\n" +#~ "\n" +#~ "<>\n" +#~ "<><>\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " " + +#~ msgid "GET_CONFIG" +#~ msgstr "GET_CONFIG" -#: ../C/gdm.xml:4388 (term) #, fuzzy -msgid "-o, --xnest-extra-options=OPTIONS" -msgstr "-o, --xnest-extra-options=OPCIONES" +#~ msgid "" +#~ "\n" +#~ "GET_CONFIG: Get configuration value for key. Useful so\n" +#~ " that other applications can request configuration\n" +#~ " information from GDM. Any key defined as GDM_KEY_*\n" +#~ " in gdm.h is supported. Starting with version 2.13.0.2\n" +#~ " translated keys (such as \"greeter/GdmWelcome[cs]\" are\n" +#~ " supported via GET_CONFIG. Also starting with version\n" +#~ " 2.13.0.2 it is no longer necessary to include the\n" +#~ " default value (i.e. you can use key \"greeter/IncludeAll\"\n" +#~ " instead of having to use \"greeter/IncludeAll=false\". \n" +#~ "Supported since: 2.6.0.9\n" +#~ "Arguments: <key>\n" +#~ "Answers:\n" +#~ " OK <value>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 50 = Unsupported key\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " IncludeAll\n" +#~ " IncludeAll<>\n" +#~ "<>\n" +#~ "<><>\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " " + +#~ msgid "GET_CONFIG_FILE" +#~ msgstr "GET_CONFIG_FILE" -#: ../C/gdm.xml:4390 (para) #, fuzzy -msgid "Extra options for Xnest, default is no options." -msgstr "Opciones extra para Xnest, lo predeterminado es sin opciones." +#~ msgid "" +#~ "\n" +#~ "GET_CONFIG_FILE: Get config file location being used by\n" +#~ " the daemon. If the GDM daemon was started\n" +#~ " with the --config option, it will return\n" +#~ " the value passed in via the argument.\n" +#~ "Supported since: 2.8.0.2\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " OK <full path to GDM configuration file>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "VERSION: Query version\n" +#~ "Supported since: 2.2.4.0\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " GDM <gdm version>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " + +#~ msgid "UPDATE_CONFIG" +#~ msgstr "UPDATE_CONFIG" -#: ../C/gdm.xml:4397 (term) #, fuzzy -msgid "-n, --no-query" -msgstr "-n, --no-query" +#~ msgid "" +#~ "\n" +#~ "UPDATE_CONFIG: Tell the daemon to re-read a key from the \n" +#~ " GDM configuration file. Any user can request\n" +#~ " that values are re-read but the daemon will\n" +#~ " only do so if the file has been modified\n" +#~ " since GDM first read the file. Only users\n" +#~ " who can change the GDM configuration file\n" +#~ " (normally writable only by the root user) can\n" +#~ " actually modify the GDM configuration. This\n" +#~ " command is useful to cause the GDM to update\n" +#~ " itself to recognize a change made to the GDM\n" +#~ " configuration file by the root user.\n" +#~ "\n" +#~ " Starting with version 2.13.0.0, all GDM keys are\n" +#~ " supported except for the following:\n" +#~ "\n" +#~ " daemon/PidFile\n" +#~ " daemon/ConsoleNotify\n" +#~ " daemon/User\n" +#~ " daemon/Group\n" +#~ " daemon/LogDir\n" +#~ " daemon/ServAuthDir\n" +#~ " daemon/UserAuthDir\n" +#~ " daemon/UserAuthFile\n" +#~ " daemon/UserAuthFBDir\n" +#~ "\n" +#~ " GDM also supports the following Psuedokeys:\n" +#~ "\n" +#~ " xdmcp/PARAMETERS (2.3.90.2) updates the following:\n" +#~ " xdmcp/MaxPending\n" +#~ " xdmcp/MaxSessions\n" +#~ " xdmcp/MaxWait\n" +#~ " xdmcp/DisplaysPerHost\n" +#~ " xdmcp/HonorIndirect\n" +#~ " xdmcp/MaxPendingIndirect\n" +#~ " xdmcp/MaxWaitIndirect\n" +#~ " xdmcp/PingIntervalSeconds (only affects new " +#~ "connections)\n" +#~ "\n" +#~ " xservers/PARAMETERS (2.13.0.4) updates the following:\n" +#~ " all [server-foo] sections.\n" +#~ "\n" +#~ " Supported keys for previous versions of GDM:\n" +#~ "\n" +#~ " security/AllowRoot (2.3.90.2)\n" +#~ " security/AllowRemoteRoot (2.3.90.2)\n" +#~ " security/AllowRemoteAutoLogin (2.3.90.2)\n" +#~ " security/RetryDelay (2.3.90.2)\n" +#~ " security/DisallowTCP (2.4.2.0)\n" +#~ " daemon/Greeter (2.3.90.2)\n" +#~ " daemon/RemoteGreeter (2.3.90.2)\n" +#~ " xdmcp/Enable (2.3.90.2)\n" +#~ " xdmcp/Port (2.3.90.2)\n" +#~ " daemon/TimedLogin (2.3.90.3)\n" +#~ " daemon/TimedLoginEnable (2.3.90.3)\n" +#~ " daemon/TimedLoginDelay (2.3.90.3)\n" +#~ " greeter/SystemMenu (2.3.90.3)\n" +#~ " greeter/ConfigAvailable (2.3.90.3)\n" +#~ " greeter/ChooserButton (2.4.2.0)\n" +#~ " greeter/SoundOnLoginFile (2.5.90.0)\n" +#~ " daemon/AddGtkModules (2.5.90.0)\n" +#~ " daemon/GtkModulesList (2.5.90.0)\n" +#~ "Supported since: 2.3.90.2\n" +#~ "Arguments: <key>\n" +#~ " <key> is just the base part of the key such as\n" +#~ " \"security/AllowRemoteRoot\"\n" +#~ "Answers:\n" +#~ " OK\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 50 = Unsupported key\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " command\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " PidFile\n" +#~ " ConsoleNotify\n" +#~ " User\n" +#~ " Group\n" +#~ " Directorio de registro\n" +#~ " ServAuthDir\n" +#~ " UserAuthDir\n" +#~ " UserAuthFile\n" +#~ " UserAuthFBDir\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " MaxSessions\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " AllowRoot\n" +#~ " AllowRemoteRoot\n" +#~ " AllowRemoteAutoLogin\n" +#~ "\n" +#~ " DisallowTCP\n" +#~ " Greeter\n" +#~ " RemoteGreeter\n" +#~ "\n" +#~ "\n" +#~ " TimedLogin\n" +#~ " TimedLoginEnable\n" +#~ " TimedLoginDelay\n" +#~ "\n" +#~ "\n" +#~ " ChooserButton\n" +#~ "\n" +#~ " AddGtkModules\n" +#~ " GtkModulesList<>\n" +#~ "<>\n" +#~ " AllowRemoteRoot\n" +#~ "\n" +#~ "<><>\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " " + +#~ msgid "GREETERPIDS" +#~ msgstr "GREETERPIDS" -#: ../C/gdm.xml:4399 (para) #, fuzzy -msgid "Just run Xnest, no query (no chooser)" -msgstr "Tan sólo ejecute Xnest, sin consulta (sin selector)" +#~ msgid "" +#~ "\n" +#~ "GREETERPIDS: List all greeter pids so that one can send HUP\n" +#~ " to them for config rereading. Of course one\n" +#~ " must be root to do that.\n" +#~ "Supported since: 2.3.90.2\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " OK <pid>;<pid>;...\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "VERSION: Query version\n" +#~ "Supported since: 2.2.4.0\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " GDM <gdm version>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " + +#~ msgid "QUERY_LOGOUT_ACTION" +#~ msgstr "QUERY_LOGOUT_ACTION" -#: ../C/gdm.xml:4406 (term) #, fuzzy -msgid "-d, --direct" -msgstr "-d, --direct" +#~ msgid "" +#~ "\n" +#~ "QUERY_LOGOUT_ACTION: Query which logout actions are possible\n" +#~ " Only supported on connections that passed\n" +#~ " AUTH_LOCAL.\n" +#~ "Supported since: 2.5.90.0\n" +#~ "Answers:\n" +#~ " OK <action>;<action>;...\n" +#~ " Where action is one of HALT, REBOOT or SUSPEND. An\n" +#~ " empty list can also be returned if no action is possible.\n" +#~ " A '!' is appended to an action if it was already set with\n" +#~ " SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION. Note that\n" +#~ " SET_LOGOUT_ACTION has precedence over\n" +#~ " SET_SAFE_LOGOUT_ACTION.\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "<><>\n" +#~ "\n" +#~ " list\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ "<><>\n" +#~ "\n" +#~ "\n" +#~ "\n" +#~ " " + +#, fuzzy +#~ msgid "SET_LOGOUT_ACTION" +#~ msgstr "SET_LOGOUT_ACTION" -#: ../C/gdm.xml:4408 (para) #, fuzzy -msgid "Do direct query instead of indirect (chooser)" -msgstr "Hace una consulta directa en lugar de indirecta (selector)" +#~ msgid "" +#~ "\n" +#~ "SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" +#~ " slave process exits. Only supported on\n" +#~ " connections that passed AUTH_LOCAL.\n" +#~ "Supported since: 2.5.90.0\n" +#~ "Arguments: <action>\n" +#~ " NONE Set exit action to 'none'\n" +#~ " HALT Set exit action to 'halt'\n" +#~ " REBOOT Set exit action to 'reboot'\n" +#~ " SUSPEND Set exit action to 'suspend'\n" +#~ "Answers:\n" +#~ " OK\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 7 = Unknown logout action, or not available\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "VERSION: Query version\n" +#~ "Supported since: 2.2.4.0\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " GDM <gdm version>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " + +#~ msgid "SET_SAFE_LOGOUT_ACTION" +#~ msgstr "SET_SAFE_LOGOUT_ACTION" -#: ../C/gdm.xml:4415 (term) #, fuzzy -msgid "-B, --broadcast" -msgstr "-B, --broadcast" +#~ msgid "" +#~ "\n" +#~ "SET_SAFE_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend\n" +#~ " after everybody logs out. If only one\n" +#~ " person logs out, then this is obviously\n" +#~ " the same as the SET_LOGOUT_ACTION. Note\n" +#~ " that SET_LOGOUT_ACTION has precedence\n" +#~ " over SET_SAFE_LOGOUT_ACTION if it is set\n" +#~ " to something other then NONE. If no one\n" +#~ " is logged in, then the action takes effect\n" +#~ " effect immediately. Only supported on\n" +#~ " connections that passed AUTH_LOCAL.\n" +#~ "Supported since: 2.5.90.0\n" +#~ "Arguments: <action>\n" +#~ " NONE Set exit action to 'none'\n" +#~ " HALT Set exit action to 'halt'\n" +#~ " REBOOT Set exit action to 'reboot'\n" +#~ " SUSPEND Set exit action to 'suspend'\n" +#~ "Answers:\n" +#~ " OK\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 7 = Unknown logout action, or not available\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "VERSION: Query version\n" +#~ "Supported since: 2.2.4.0\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " GDM <gdm version>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " + +#~ msgid "QUERY_VT" +#~ msgstr "QUERY_VT" -#: ../C/gdm.xml:4417 (para) #, fuzzy -msgid "Run broadcast instead of indirect (chooser)" -msgstr "Ejecutar en difusión en vez de indirecto (selector)" +#~ msgid "" +#~ "\n" +#~ "QUERY_VT: Ask the daemon about which VT we are currently on.\n" +#~ " This is useful for logins which don't own\n" +#~ " /dev/console but are still console logins. Only\n" +#~ " supported on Linux currently, other places will\n" +#~ " just get ERROR 8. This is also the way to query\n" +#~ " if VT support is available in the daemon in the\n" +#~ " first place. Only supported on connections that\n" +#~ " passed AUTH_LOCAL.\n" +#~ "Supported since: 2.5.90.0\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " OK <vt number>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 8 = Virtual terminals not supported\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "VERSION: Query version\n" +#~ "Supported since: 2.2.4.0\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " GDM <gdm version>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " + +#~ msgid "SET_VT" +#~ msgstr "SET_VT" -#: ../C/gdm.xml:4424 (term) #, fuzzy -msgid "-b, --background" -msgstr "-b, --background" +#~ msgid "" +#~ "\n" +#~ "SET_VT: Change to the specified virtual terminal.\n" +#~ " This is useful for logins which don't own /dev/console\n" +#~ " but are still console logins. Only supported on Linux\n" +#~ " currently, other places will just get ERROR 8.\n" +#~ " Only supported on connections that passed AUTH_LOCAL.\n" +#~ "Supported since: 2.5.90.0\n" +#~ "Arguments: <vt>\n" +#~ "Answers:\n" +#~ " OK\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 0 = Not implemented\n" +#~ " 8 = Virtual terminals not supported\n" +#~ " 9 = Invalid virtual terminal number\n" +#~ " 100 = Not authenticated\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "VERSION: Query version\n" +#~ "Supported since: 2.2.4.0\n" +#~ "Arguments: None\n" +#~ "Answers:\n" +#~ " GDM <gdm version>\n" +#~ " ERROR <err number> <english error description>\n" +#~ " 200 = Too many messages\n" +#~ " 999 = Unknown error\n" +#~ " " + +#~ msgid "CLOSE" +#~ msgstr "CLOSE" -#: ../C/gdm.xml:4426 (para) #, fuzzy -msgid "Run in background" -msgstr "Ejecutar en segundo plano" +#~ msgid "GDM Commands" +#~ msgstr "Comandos de GDM" -#: ../C/gdm.xml:4433 (term) #, fuzzy -msgid "--no-gdm-check" -msgstr "--no-gdm-check" +#~ msgid "" +#~ "<command>gdmXnestchooser</command> and <command>gdmXnest</command> " +#~ "Command Line Options" +#~ msgstr "" +#~ "Opciones de línea de comandos de <command>gdmXnestchooser</command> y " +#~ "<command>gdmXnest</command>" -#: ../C/gdm.xml:4435 (para) #, fuzzy -msgid "Don't check for running GDM" -msgstr "No comprueba si hay un GDM funcionando" +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "<command></command> command<command> Xnest</command> XDMCP chooser " +#~ "chooser<command></command> XDMCP chooser<command></command> Xnest " +#~ "command<command></command> command." -#: ../C/gdm.xml:4444 (title) ../C/gdm.xml:4488 #, fuzzy -msgid "<command>gdmflexichooser</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmflexichooser</command>" +#~ msgid "<command>gdmXnestchooser</command> Command Line Options" +#~ msgstr "Opciones de línea de comandos de <command>gdmXnestchooser</command>" -#: ../C/gdm.xml:4446 (para) #, fuzzy -msgid "" -"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." -msgstr "<command></command> command flexible flexible Xnest." +#~ msgid "-x, --xnest=STRING" +#~ msgstr "-x, --xnest=STRING" -#: ../C/gdm.xml:4453 (para) #, fuzzy -msgid "" -"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." -msgstr "flexible flexible." - -#: ../C/gdm.xml:4467 (para) +#~ msgid "Xnest command line, default is \"Xnest\"" +#~ msgstr "Línea de comandos de Xnest, lo predeterminado es «Xnest»" + #, fuzzy -msgid "" -"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." -msgstr "Xnest flexible flexible." +#~ msgid "-o, --xnest-extra-options=OPTIONS" +#~ msgstr "-o, --xnest-extra-options=OPCIONES" -#: ../C/gdm.xml:4475 (para) #, fuzzy -msgid "" -"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." -msgstr "<command> command</command>." +#~ msgid "Extra options for Xnest, default is no options." +#~ msgstr "Opciones extra para Xnest, lo predeterminado es sin opciones." -#: ../C/gdm.xml:4481 (para) -msgid "" -"In addition to the following options, <command>gdmflexiserver</command> also " -"supports standard GNOME options." -msgstr "" +#, fuzzy +#~ msgid "-n, --no-query" +#~ msgstr "-n, --no-query" -#: ../C/gdm.xml:4491 (term) #, fuzzy -msgid "-c, --command=COMMAND" -msgstr "command" +#~ msgid "Just run Xnest, no query (no chooser)" +#~ msgstr "Tan sólo ejecute Xnest, sin consulta (sin selector)" -#: ../C/gdm.xml:4493 (para) -msgid "Send the specified protocol command to GDM" -msgstr "Enviar el comando de protocolo especificado a GDM" +#, fuzzy +#~ msgid "-d, --direct" +#~ msgstr "-d, --direct" -#: ../C/gdm.xml:4500 (term) -msgid "-n, --xnest" -msgstr "-n, --xnest" +#, fuzzy +#~ msgid "Do direct query instead of indirect (chooser)" +#~ msgstr "Hace una consulta directa en lugar de indirecta (selector)" -#: ../C/gdm.xml:4502 (para) #, fuzzy -msgid "Start a flexible X display in Xnest mode" -msgstr "flexible Xnest" +#~ msgid "-B, --broadcast" +#~ msgstr "-B, --broadcast" -#: ../C/gdm.xml:4509 (term) -msgid "-l, --no-lock" -msgstr "-l, --no-lock" +#, fuzzy +#~ msgid "Run broadcast instead of indirect (chooser)" +#~ msgstr "Ejecutar en difusión en vez de indirecto (selector)" -#: ../C/gdm.xml:4511 (para) -msgid "Do not lock current screen" -msgstr "No bloquear la pantalla actual" +#, fuzzy +#~ msgid "-b, --background" +#~ msgstr "-b, --background" -#: ../C/gdm.xml:4518 (term) -msgid "-d, --debug" -msgstr "-d, --debug" +#, fuzzy +#~ msgid "Run in background" +#~ msgstr "Ejecutar en segundo plano" -#: ../C/gdm.xml:4520 (para) -msgid "" -"Turns on debugging output which gets sent to syslog. Same as turning on " -"debug in the configuration file." -msgstr "" -"Activar salida de depuración para enviarla a syslog. Lo mismo que cuadno se " -"activa la depuración en el archivo de configuración." +#, fuzzy +#~ msgid "--no-gdm-check" +#~ msgstr "--no-gdm-check" -#: ../C/gdm.xml:4528 (term) -msgid "-a, --authenticate" -msgstr "-a, --authenticate" +#, fuzzy +#~ msgid "Don't check for running GDM" +#~ msgstr "No comprueba si hay un GDM funcionando" -#: ../C/gdm.xml:4530 (para) -msgid "Authenticate before running --command" -msgstr "Autenticar antes de ejecutar --command" +#, fuzzy +#~ msgid "<command>gdmflexichooser</command> Command Line Options" +#~ msgstr "Opciones de línea de comandos de <command>gdmflexichooser</command>" -#: ../C/gdm.xml:4537 (term) -msgid "-s, --startnew" -msgstr "-s, --startnew" +#, fuzzy +#~ msgid "" +#~ "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." +#~ msgstr "<command></command> command flexible flexible Xnest." -#: ../C/gdm.xml:4539 (para) #, fuzzy -msgid "" -"Starts a new flexible display without displaying a dialog asking the user if " -"they wish to continue any existing sessions." -msgstr "flexible." +#~ msgid "" +#~ "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." +#~ msgstr "flexible flexible." -#: ../C/gdm.xml:4550 (title) ../C/gdm.xml:4568 -msgid "<command>gdmdynamic</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmdynamic</command>" +#, fuzzy +#~ msgid "" +#~ "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." +#~ msgstr "Xnest flexible flexible." -#: ../C/gdm.xml:4552 (para) #, fuzzy -msgid "" -"The <command>gdmdynamic</command> command which creates, runs, and removes " -"displays (X servers) on demand." -msgstr "<command></command> command." +#~ msgid "" +#~ "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." +#~ msgstr "<command> command</command>." -#: ../C/gdm.xml:4557 (para) #, fuzzy -msgid "" -"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." -msgstr "list<command></command> command<command></command> command list." +#~ msgid "-c, --command=COMMAND" +#~ msgstr "command" + +#~ msgid "Send the specified protocol command to GDM" +#~ msgstr "Enviar el comando de protocolo especificado a GDM" -#: ../C/gdm.xml:4573 (emphasis) -msgid "One of the following options can be used per instance:" -msgstr "Una de las siguientes opciones pueden usarse por instancia:" +#~ msgid "-n, --xnest" +#~ msgstr "-n, --xnest" -#: ../C/gdm.xml:4580 (term) #, fuzzy -msgid "-a display=server" -msgstr "-a display=server" +#~ msgid "Start a flexible X display in Xnest mode" +#~ msgstr "flexible Xnest" -#: ../C/gdm.xml:4582 (para) -msgid "" -"Add a new display configuration. For example, <command>\"-a " -"2=StandardServerTwo\"</command><command>\"-a 3=/usr/X11R6/bin/X -dev /dev/fb2" -"\"</command>" -msgstr "" +#~ msgid "-l, --no-lock" +#~ msgstr "-l, --no-lock" -#: ../C/gdm.xml:4591 (term) -msgid "-r" -msgstr "" +#~ msgid "Do not lock current screen" +#~ msgstr "No bloquear la pantalla actual" -#: ../C/gdm.xml:4593 (para) -msgid "Release (run) all displays waiting in the DISPLAY_CONFIG state." -msgstr "" +#~ msgid "-d, --debug" +#~ msgstr "-d, --debug" -#: ../C/gdm.xml:4600 (term) -#, fuzzy -msgid "-d display" -msgstr "-d display" +#~ msgid "" +#~ "Turns on debugging output which gets sent to syslog. Same as turning on " +#~ "debug in the configuration file." +#~ msgstr "" +#~ "Activar salida de depuración para enviarla a syslog. Lo mismo que cuadno " +#~ "se activa la depuración en el archivo de configuración." -#: ../C/gdm.xml:4602 (para) -msgid "" -"Delete a display, killing the X server and purging the display " -"configuration. For example, \"-d 3\"." -msgstr "" +#~ msgid "-a, --authenticate" +#~ msgstr "-a, --authenticate" -#: ../C/gdm.xml:4610 (term) -msgid "-l [pattern]" -msgstr "" +#~ msgid "Authenticate before running --command" +#~ msgstr "Autenticar antes de ejecutar --command" + +#~ msgid "-s, --startnew" +#~ msgstr "-s, --startnew" -#: ../C/gdm.xml:4612 (para) #, fuzzy -msgid "" -"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>" -msgstr "command<command></command><command></command>" - -#: ../C/gdm.xml:4625 (emphasis) -msgid "These options can be added to the above:" -msgstr "" +#~ msgid "" +#~ "Starts a new flexible display without displaying a dialog asking the user " +#~ "if they wish to continue any existing sessions." +#~ msgstr "flexible." -#: ../C/gdm.xml:4632 (term) -msgid "-v" -msgstr "" +#~ msgid "<command>gdmdynamic</command> Command Line Options" +#~ msgstr "Opciones de línea de comandos de <command>gdmdynamic</command>" -#: ../C/gdm.xml:4634 (para) -msgid "Verbose mode. Prinr diagnostic messages about each message sent to GDM." -msgstr "" +#, fuzzy +#~ msgid "" +#~ "The <command>gdmdynamic</command> command which creates, runs, and " +#~ "removes displays (X servers) on demand." +#~ msgstr "<command></command> command." -#: ../C/gdm.xml:4642 (term) -msgid "-b" -msgstr "" +#, fuzzy +#~ msgid "" +#~ "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." +#~ msgstr "list<command></command> command<command></command> command list." -#: ../C/gdm.xml:4644 (para) -msgid "Background mode. Fork child to do the work and return immediately." -msgstr "" +#~ msgid "One of the following options can be used per instance:" +#~ msgstr "Una de las siguientes opciones pueden usarse por instancia:" -#: ../C/gdm.xml:4653 (title) #, fuzzy -msgid "<command>gdmphotosetup</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmphotosetup</command>" +#~ msgid "-a display=server" +#~ msgstr "-a display=server" -#: ../C/gdm.xml:4655 (para) #, fuzzy -msgid "" -"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 ~/." -"face. This command accepts standard GNOME options." -msgstr "command." +#~ msgid "-d display" +#~ msgstr "-d display" -#: ../C/gdm.xml:4663 (title) #, fuzzy -msgid "<command>gdmthemetester</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmthemetester</command>" +#~ msgid "" +#~ "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>" +#~ msgstr "command<command></command><command></command>" -#: ../C/gdm.xml:4665 (para) #, fuzzy -msgid "" -"<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>\n" -"console - In console mode.\n" -"console-timed - In console non-flexi mode.\n" -"flexi - In flexi mode.\n" -"xdmcp - In remote (XDMCP) mode.\n" -"remote-flexi - In remote (XDMCP) & flexi mode.\n" -" </screen>" -msgstr "" -"<command></command> nombre nombre<command></command><command></command><command></command><screen> XDMCP XDMCP&\n" -"</screen>" +#~ msgid "<command>gdmphotosetup</command> Command Line Options" +#~ msgstr "Opciones de línea de comandos de <command>gdmphotosetup</command>" -#: ../C/gdm.xml:4691 (title) #, fuzzy -msgid "GDM Root User Commands" -msgstr "Comandos del administrador de GDM" +#~ msgid "" +#~ "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 " +#~ "~/.face. This command accepts standard GNOME options." +#~ msgstr "command." -#: ../C/gdm.xml:4693 (para) -msgid "" -"The GDM package provides the following different commands in " -"EXPANDED_SBINDIR intended to be used by the root user:" -msgstr "" +#, fuzzy +#~ msgid "<command>gdmthemetester</command> Command Line Options" +#~ msgstr "Opciones de línea de comandos de <command>gdmthemetester</command>" -#: ../C/gdm.xml:4699 (title) ../C/gdm.xml:4715 #, fuzzy -msgid "<command>gdm</command> and <command>gdm-binary</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdm</command> y <command>gdm-binary</command>" +#~ msgid "" +#~ "<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>\n" +#~ "console - In console mode.\n" +#~ "console-timed - In console non-flexi mode.\n" +#~ "flexi - In flexi mode.\n" +#~ "xdmcp - In remote (XDMCP) mode.\n" +#~ "remote-flexi - In remote (XDMCP) & flexi mode.\n" +#~ " </screen>" +#~ msgstr "" +#~ "<command></command> nombre nombre<command></command><command></" +#~ "command><command></command><screen> XDMCP XDMCP&\n" +#~ "</screen>" -#: ../C/gdm.xml:4702 (para) #, fuzzy -msgid "" -"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." -msgstr "<command></command> command<command></command><command></command><filename><></filename>." +#~ msgid "GDM Root User Commands" +#~ msgstr "Comandos del administrador de GDM" -#: ../C/gdm.xml:4719 (term) -msgid "--help" -msgstr "--help" +#, fuzzy +#~ msgid "" +#~ "<command>gdm</command> and <command>gdm-binary</command> Command Line " +#~ "Options" +#~ msgstr "" +#~ "Opciones de línea de comandos de <command>gdm</command> y <command>gdm-" +#~ "binary</command>" -#: ../C/gdm.xml:4721 (para) #, fuzzy -msgid "Gives a brief overview of the command line options." -msgstr "Da un breve resumen de las opciones de línea de comandos." +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "<command></command> command<command></command><command></" +#~ "command><filename><></filename>." -#: ../C/gdm.xml:4728 (term) -msgid "-nodaemon" -msgstr "-nodaemon" +#~ msgid "--help" +#~ msgstr "--help" -#: ../C/gdm.xml:4730 (para) #, fuzzy -msgid "" -"If this option is specified, then GDM does not fork into the background when " -"run. You can use just a single dash with this option to preserve " -"compatibility with XDM." -msgstr "Si se especifica esta opción, entonces GDM no se bifurca a un segundo plano cuando se ejecuta. Puede usar tan sólo un simple guión con esta opción para preservar compatibilidad con XDM." +#~ msgid "Gives a brief overview of the command line options." +#~ msgstr "Da un breve resumen de las opciones de línea de comandos." -#: ../C/gdm.xml:4739 (term) -msgid "--no-console" -msgstr "--no-console" +#~ msgid "-nodaemon" +#~ msgstr "-nodaemon" -#: ../C/gdm.xml:4741 (para) -msgid "" -"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." -msgstr "" +#, fuzzy +#~ msgid "" +#~ "If this option is specified, then GDM does not fork into the background " +#~ "when run. You can use just a single dash with this option to preserve " +#~ "compatibility with XDM." +#~ msgstr "" +#~ "Si se especifica esta opción, entonces GDM no se bifurca a un segundo " +#~ "plano cuando se ejecuta. Puede usar tan sólo un simple guión con esta " +#~ "opción para preservar compatibilidad con XDM." -#: ../C/gdm.xml:4753 (term) -msgid "--config=CONFIGFILE" -msgstr "--config=CONFIGFILE" +#~ msgid "--no-console" +#~ msgstr "--no-console" -#: ../C/gdm.xml:4755 (para) -#, fuzzy -msgid "Specify an alternative configuration file." -msgstr "Especificar un archivo de configuración alternativo" +#~ msgid "--config=CONFIGFILE" +#~ msgstr "--config=CONFIGFILE" -#: ../C/gdm.xml:4762 (term) -msgid "--preserve-ld-vars" -msgstr "--preserve-ld-vars" +#, fuzzy +#~ msgid "Specify an alternative configuration file." +#~ msgstr "Especificar un archivo de configuración alternativo" -#: ../C/gdm.xml:4764 (para) -msgid "" -"When clearing the environment internally, preserve all variables starting " -"with LD_. This is mostly for debugging purposes." -msgstr "" +#~ msgid "--preserve-ld-vars" +#~ msgstr "--preserve-ld-vars" -#: ../C/gdm.xml:4772 (term) -msgid "--version" -msgstr "--version" +#~ msgid "--version" +#~ msgstr "--version" -#: ../C/gdm.xml:4774 (para) #, fuzzy -msgid "Print the version of the GDM daemon." -msgstr "Imprime la versión del demonio GDM." +#~ msgid "Print the version of the GDM daemon." +#~ msgstr "Imprime la versión del demonio GDM." -#: ../C/gdm.xml:4781 (term) -msgid "--wait-for-go" -msgstr "--wait-for-go" +#~ msgid "--wait-for-go" +#~ msgstr "--wait-for-go" -#: ../C/gdm.xml:4783 (para) #, fuzzy -msgid "" -"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." -msgstr "XDMCP." - -#: ../C/gdm.xml:4801 (title) -#, fuzzy -msgid "<command>gdmsetup</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmsetup</command>" - -#: ../C/gdm.xml:4803 (para) -msgid "" -"<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." -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "XDMCP." -#: ../C/gdm.xml:4815 (title) #, fuzzy -msgid "<command>gdm-restart</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdm-restart</command>" +#~ msgid "<command>gdmsetup</command> Command Line Options" +#~ msgstr "Opciones de línea de comandos de <command>gdmsetup</command>" -#: ../C/gdm.xml:4817 (para) #, fuzzy -msgid "" -"<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." -msgstr "<command>gdm-restart</command> para y reinicia GDM enviando al demonio de GDM una señal HUP. Este comando inmediatamente terminará todas las sesiones y echará fuera a los usuarios que hayan entrado con GDM." +#~ msgid "<command>gdm-restart</command> Command Line Options" +#~ msgstr "Opciones de línea de comandos de <command>gdm-restart</command>" -#: ../C/gdm.xml:4825 (title) #, fuzzy -msgid "<command>gdm-safe-restart</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdm-safe-restart</command>" +#~ msgid "" +#~ "<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." +#~ msgstr "" +#~ "<command>gdm-restart</command> para y reinicia GDM enviando al demonio " +#~ "de GDM una señal HUP. Este comando inmediatamente terminará todas las " +#~ "sesiones y echará fuera a los usuarios que hayan entrado con GDM." -#: ../C/gdm.xml:4827 (para) #, fuzzy -msgid "" -"<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." -msgstr "<command>gdm-safe-restart</command> para y reinicia GDM enviando al demonio GDM una señal USR1. GDM re reiniciará tan pronto como todos los usuarios salgan." +#~ msgid "<command>gdm-safe-restart</command> Command Line Options" +#~ msgstr "" +#~ "Opciones de línea de comandos de <command>gdm-safe-restart</command>" -#: ../C/gdm.xml:4835 (title) #, fuzzy -msgid "<command>gdm-stop</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdm-stop</command>" +#~ msgid "" +#~ "<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." +#~ msgstr "" +#~ "<command>gdm-safe-restart</command> para y reinicia GDM enviando al " +#~ "demonio GDM una señal USR1. GDM re reiniciará tan pronto como todos los " +#~ "usuarios salgan." -#: ../C/gdm.xml:4837 (para) #, fuzzy -msgid "" -"<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM " -"signal." -msgstr "<command>gdm-stop</command> para GDM enviando al demonio GDM una señal TERM" - -#: ../C/gdm.xml:4845 (title) -msgid "GDM Internal Commands" -msgstr "Comandos internos de GDM" +#~ msgid "<command>gdm-stop</command> Command Line Options" +#~ msgstr "Opciones de línea de comandos de <command>gdm-stop</command>" -#: ../C/gdm.xml:4847 (para) -msgid "" -"The GDM package provides the following different commands in " -"EXPANDED_LIBEXECDIR intended to be used by the gdm daemon process." -msgstr "" - -#: ../C/gdm.xml:4853 (title) #, fuzzy -msgid "" -"<command>gdmchooser</command> and <command>gdmlogin</command> Command Line " -"Options" -msgstr "Opciones de línea de comandos de <command>gdmchooser</command> y <command>gdmlogin</command>" +#~ msgid "" +#~ "<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM " +#~ "signal." +#~ msgstr "" +#~ "<command>gdm-stop</command> para GDM enviando al demonio GDM una señal " +#~ "TERM" -#: ../C/gdm.xml:4856 (para) -msgid "" -"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." -msgstr "" +#~ msgid "GDM Internal Commands" +#~ msgstr "Comandos internos de GDM" -#: ../C/gdm.xml:4867 (title) ../C/gdm.xml:4878 #, fuzzy -msgid "<command>gdmchooser</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmchooser</command>" +#~ msgid "" +#~ "<command>gdmchooser</command> and <command>gdmlogin</command> Command " +#~ "Line Options" +#~ msgstr "" +#~ "Opciones de línea de comandos de <command>gdmchooser</command> y " +#~ "<command>gdmlogin</command>" -#: ../C/gdm.xml:4869 (para) #, fuzzy -msgid "" -"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." -msgstr "<command></command> XDMCP chooser<command></command> command." +#~ msgid "<command>gdmchooser</command> Command Line Options" +#~ msgstr "Opciones de línea de comandos de <command>gdmchooser</command>" -#: ../C/gdm.xml:4881 (term) -msgid "-xdmaddress=SOCKET" -msgstr "-xdmaddress=SOCKET" - -#: ../C/gdm.xml:4883 (para) #, fuzzy -msgid "Socket for XDM communication." -msgstr "Socket para comunicación XDM." +#~ msgid "" +#~ "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." +#~ msgstr "<command></command> XDMCP chooser<command></command> command." -#: ../C/gdm.xml:4890 (term) -msgid "--clientaddress=ADDRESS" -msgstr "--clientaddress=ADDRESS" +#~ msgid "-xdmaddress=SOCKET" +#~ msgstr "-xdmaddress=SOCKET" -#: ../C/gdm.xml:4892 (para) -msgid "" -"Client address to return in response to XDM. This option is for running " -"gdmchooser with XDM, and is not used within GDM." -msgstr "" +#, fuzzy +#~ msgid "Socket for XDM communication." +#~ msgstr "Socket para comunicación XDM." -#: ../C/gdm.xml:4900 (term) -msgid "-connectionType=TYPE" -msgstr "-connectionType=TYPE" +#~ msgid "--clientaddress=ADDRESS" +#~ msgstr "--clientaddress=ADDRESS" -#: ../C/gdm.xml:4902 (para) -msgid "" -"Connection type to return in response to XDM. This option is for running " -"gdmchooser with XDM, and is not used within GDM." -msgstr "" +#~ msgid "-connectionType=TYPE" +#~ msgstr "-connectionType=TYPE" -#: ../C/gdm.xml:4916 (title) -msgid "Themed Greeter" -msgstr "Interfaz con temas" +#~ msgid "Themed Greeter" +#~ msgstr "Interfaz con temas" -#: ../C/gdm.xml:4918 (para) #, fuzzy -msgid "" -"This section describes the creation of themes for the Themed Greeter. For " -"examples including screenshots, see the standard installed themes and the " -"themes from <ulink type=\"http\" url=\"http://art.gnome.org/themes/" -"gdm_greeter/\"> the theme website</ulink>." -msgstr "" -"Esta sección describe la creación de temas para el Interfaz con temas. Para los ejemplos incluidos en las capturas, vea los temas estándar instalados y los temas del <ulink type=\"http\" url=\"http://art.gnome.org/themes/" -"gdm_greeter/\">sitio web de temas</ulink>." +#~ msgid "" +#~ "This section describes the creation of themes for the Themed Greeter. For " +#~ "examples including screenshots, see the standard installed themes and the " +#~ "themes from <ulink type=\"http\" url=\"http://art.gnome.org/themes/" +#~ "gdm_greeter/\"> the theme website</ulink>." +#~ msgstr "" +#~ "Esta sección describe la creación de temas para el Interfaz con temas. " +#~ "Para los ejemplos incluidos en las capturas, vea los temas estándar " +#~ "instalados y los temas del <ulink type=\"http\" url=\"http://art.gnome." +#~ "org/themes/gdm_greeter/\">sitio web de temas</ulink>." -#: ../C/gdm.xml:4927 (title) -msgid "Theme Overview" -msgstr "Descripción de los temas" +#~ msgid "Theme Overview" +#~ msgstr "Descripción de los temas" -#: ../C/gdm.xml:4929 (para) #, fuzzy -msgid "" -"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:" -msgstr "<filename><>< nombre></filename><filename></filename><filename></filename>:" +#~ msgid "" +#~ "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:" +#~ msgstr "" +#~ "<filename><>< nombre></filename><filename></" +#~ "filename><filename></filename>:" -#: ../C/gdm.xml:4940 (screen) -#, no-wrap -#, fuzzy -msgid "" -"\n" -"[GdmGreeterTheme]\n" -"Encoding=UTF-8\n" -"Greeter=circles.xml\n" -"Name=Circles\n" -"Description=Theme with blue circles\n" -"Author=Bond, James Bond\n" -"Copyright=(c) 2002 Bond, James Bond\n" -"Screenshot=screenshot.png\n" -" " -msgstr "" -"\n" -"[GdmGreeterTheme]\n" -"Encoding=UTF-8\n" -"Greeter=circles.xml\n" -"Name=Circles\n" -"Description=Theme with blue circles\n" -"Author=Bond, James Bond\n" -"Copyright=(c) 2002 Bond, James Bond\n" -"Screenshot=screenshot.png\n" -" " - -#: ../C/gdm.xml:4951 (para) #, fuzzy -msgid "" -"The Name, Description, Author and Copyright fields can be translated just " -"like the other <filename>.desktop</filename>files. All the files that are " -"mentioned should be in the theme directory itself. The Screenshot field " -"points to a file which should be a 200x150 screenshot of the theme in action " -"(it is OK not to have one, but it makes it nicer for user). The Greeter " -"field points to an XML file that contains the description of the theme. The " -"description will be given later." -msgstr "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." +#~ msgid "" +#~ "\n" +#~ "[GdmGreeterTheme]\n" +#~ "Encoding=UTF-8\n" +#~ "Greeter=circles.xml\n" +#~ "Name=Circles\n" +#~ "Description=Theme with blue circles\n" +#~ "Author=Bond, James Bond\n" +#~ "Copyright=(c) 2002 Bond, James Bond\n" +#~ "Screenshot=screenshot.png\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "[GdmGreeterTheme]\n" +#~ "Encoding=UTF-8\n" +#~ "Greeter=circles.xml\n" +#~ "Name=Circles\n" +#~ "Description=Theme with blue circles\n" +#~ "Author=Bond, James Bond\n" +#~ "Copyright=(c) 2002 Bond, James Bond\n" +#~ "Screenshot=screenshot.png\n" +#~ " " -#: ../C/gdm.xml:4961 (para) #, fuzzy -msgid "" -"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:" -msgstr "<command></command> Xnest command flexible Xnest XDMCP nombre XDMCP:" - -#: ../C/gdm.xml:4975 (command) -msgid "gdmthemetester xdmcp circles" -msgstr "" +#~ msgid "" +#~ "The Name, Description, Author and Copyright fields can be translated just " +#~ "like the other <filename>.desktop</filename>files. All the files that are " +#~ "mentioned should be in the theme directory itself. The Screenshot field " +#~ "points to a file which should be a 200x150 screenshot of the theme in " +#~ "action (it is OK not to have one, but it makes it nicer for user). The " +#~ "Greeter field points to an XML file that contains the description of the " +#~ "theme. The description will be given later." +#~ msgstr "" +#~ "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." -#: ../C/gdm.xml:4977 (para) #, fuzzy -msgid "" -"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." -msgstr "Xnest Xnest." +#~ msgid "" +#~ "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:" +#~ msgstr "" +#~ "<command></command> Xnest command flexible Xnest XDMCP nombre XDMCP:" -#: ../C/gdm.xml:4985 (para) #, fuzzy -msgid "" -"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>/usr/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>\n" -"cd /usr/share/gdm/themes\n" -"tar czvf <theme_name>.tar.gz <theme_name>/\n" -" </screen>" -msgstr "" -"nombre<filename></filename><screen>< nombre>< nombre>\n" -"</screen>" - -#: ../C/gdm.xml:5000 (title) -msgid "Detailed Description of Theme XML format" -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "Xnest Xnest." -#: ../C/gdm.xml:5003 (title) #, fuzzy -msgid "Box Nodes" -msgstr "Nodos contenedores." - -#: ../C/gdm.xml:5005 (para) -msgid "" -"Box nodes are container nodes for item nodes. Box nodes are specified as " -"follows: <screen>\n" -"<box orientation=\"alignment\" min-width=\"num\"\n" -"xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -"homogeneous=\"bool\">\n" -" </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." -msgstr "" +#~ msgid "" +#~ "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>/usr/" +#~ "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>\n" +#~ "cd /usr/share/gdm/themes\n" +#~ "tar czvf <theme_name>.tar.gz <theme_name>/\n" +#~ " </screen>" +#~ msgstr "" +#~ "nombre<filename></filename><screen>< nombre>< nombre>\n" +#~ "</screen>" -#: ../C/gdm.xml:5021 (para) #, fuzzy -msgid "" -"If the box is homogeneous then the children are allocated equal amount of " -"space." -msgstr "Si la caja es homogénea entonces los hijos se les reserver la misma cantidad de espacio." - -#: ../C/gdm.xml:5026 (para) -msgid "" -"The \"min-width\" must be specified in pixels. Obviously there is also a " -"corresponding \"min-height\" property as well." -msgstr "" +#~ msgid "Box Nodes" +#~ msgstr "Nodos contenedores." -#: ../C/gdm.xml:5034 (title) #, fuzzy -msgid "Fixed Nodes" -msgstr "Nodos fijos" - -#: ../C/gdm.xml:5036 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "If the box is homogeneous then the children are allocated equal amount of " +#~ "space." +#~ msgstr "" +#~ "Si la caja es homogénea entonces los hijos se les reserver la misma " +#~ "cantidad de espacio." -#: ../C/gdm.xml:5045 (para) -msgid "The \"toplevel\" node is really just like a fixed node." -msgstr "" +#, fuzzy +#~ msgid "Fixed Nodes" +#~ msgstr "Nodos fijos" -#: ../C/gdm.xml:5051 (title) #, fuzzy -msgid "Item Nodes" -msgstr "Nodos de elemento" +#~ msgid "Item Nodes" +#~ msgstr "Nodos de elemento" -#: ../C/gdm.xml:5053 (para) #, fuzzy -msgid "" -"A GDM Theme is created by specifying a hierarchy of item and box nodes. Item " -"nodes can have the following value for \"type\":" -msgstr "Un tema GDM se crea especificando una gerarquía de nodos de elementos y cajas. Los nodos de elementos pueden tener el siguiente valor para el tipo:" +#~ msgid "" +#~ "A GDM Theme is created by specifying a hierarchy of item and box nodes. " +#~ "Item nodes can have the following value for \"type\":" +#~ msgstr "" +#~ "Un tema GDM se crea especificando una gerarquía de nodos de elementos y " +#~ "cajas. Los nodos de elementos pueden tener el siguiente valor para el " +#~ "tipo:" -#: ../C/gdm.xml:5061 (term) -msgid "entry" -msgstr "entrada" +#~ msgid "entry" +#~ msgstr "entrada" -#: ../C/gdm.xml:5063 (para) -msgid "Text entry field." -msgstr "Campo de entrada de texto." +#~ msgid "Text entry field." +#~ msgstr "Campo de entrada de texto." -#: ../C/gdm.xml:5070 (term) -msgid "list" -msgstr "lista" +#~ msgid "list" +#~ msgstr "lista" -#: ../C/gdm.xml:5072 (para) -msgid "A list widget." -msgstr "Un widget de lista" +#~ msgid "A list widget." +#~ msgstr "Un widget de lista" -#: ../C/gdm.xml:5079 (term) -msgid "label" -msgstr "etiqueta" +#~ msgid "label" +#~ msgstr "etiqueta" -#: ../C/gdm.xml:5081 (para) #, fuzzy -msgid "A text label. Must have a \"text\" node to specify the text." -msgstr "Una etiqueta de texto. Debe tener un nodo \"text\" para especificar el texto." +#~ msgid "A text label. Must have a \"text\" node to specify the text." +#~ msgstr "" +#~ "Una etiqueta de texto. Debe tener un nodo \"text\" para especificar el " +#~ "texto." -#: ../C/gdm.xml:5089 (term) -msgid "pixmap" -msgstr "imagen" +#~ msgid "pixmap" +#~ msgstr "imagen" -#: ../C/gdm.xml:5091 (para) #, fuzzy -msgid "" -"An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, " -"etc...)" -msgstr "Una imagen pixmap en un formato que gdk-pixbuf soporte como PNG, JPEG, Tiff, etc...)" +#~ msgid "" +#~ "An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, " +#~ "Tiff, etc...)" +#~ msgstr "" +#~ "Una imagen pixmap en un formato que gdk-pixbuf soporte como PNG, JPEG, " +#~ "Tiff, etc...)" -#: ../C/gdm.xml:5099 (term) -msgid "rect" -msgstr "rect" +#~ msgid "rect" +#~ msgstr "rect" -#: ../C/gdm.xml:5101 (para) -msgid "Rectangle." -msgstr "Rectángulo." +#~ msgid "Rectangle." +#~ msgstr "Rectángulo." -#: ../C/gdm.xml:5108 (term) -msgid "svg" -msgstr "svg" +#~ msgid "svg" +#~ msgstr "svg" -#: ../C/gdm.xml:5110 (para) -msgid "Scaled Vector Graphic image." -msgstr "Imagen Scaled Vector Graphic" +#~ msgid "Scaled Vector Graphic image." +#~ msgstr "Imagen Scaled Vector Graphic" -#: ../C/gdm.xml:5117 (para) #, fuzzy -msgid "" -"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)" -msgstr "<screen>< label></screen> list" +#~ msgid "" +#~ "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)" +#~ msgstr "<screen>< label></screen> list" -#: ../C/gdm.xml:5126 (para) #, fuzzy -msgid "Entry items can have id values as follows:" -msgstr "Los elementos de entradas pueden tener valores id como siguen:" +#~ msgid "Entry items can have id values as follows:" +#~ msgstr "Los elementos de entradas pueden tener valores id como siguen:" -#: ../C/gdm.xml:5132 (term) #, fuzzy -msgid "user-pw-entry" -msgstr "user-pw-entry" +#~ msgid "user-pw-entry" +#~ msgstr "user-pw-entry" -#: ../C/gdm.xml:5134 (para) #, fuzzy -msgid "" -"Entry field for userid and password entry. This is the field used for " -"responses for the PAM/GDM questions (Username, Password, etc..)." -msgstr "entry." +#~ msgid "" +#~ "Entry field for userid and password entry. This is the field used for " +#~ "responses for the PAM/GDM questions (Username, Password, etc..)." +#~ msgstr "entry." -#: ../C/gdm.xml:5144 (para) #, fuzzy -msgid "List items can have id values as follows:" -msgstr "Los elementos de listas pueden tener valores id como siguen:" +#~ msgid "List items can have id values as follows:" +#~ msgstr "Los elementos de listas pueden tener valores id como siguen:" -#: ../C/gdm.xml:5150 (term) -msgid "userlist" -msgstr "lista de usuarios" +#~ msgid "userlist" +#~ msgstr "lista de usuarios" -#: ../C/gdm.xml:5152 (para) #, fuzzy -msgid "" -"A Face Browser list, so that users can pick their username by clicking on " -"this instead of typing." -msgstr "Browser list." - -#: ../C/gdm.xml:5161 (para) -msgid "" -"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'" -msgstr "" - -#: ../C/gdm.xml:5168 (para) -msgid "Label items can have id values as follows:" -msgstr "" +#~ msgid "" +#~ "A Face Browser list, so that users can pick their username by clicking on " +#~ "this instead of typing." +#~ msgstr "Browser list." -#: ../C/gdm.xml:5174 (term) -msgid "clock" -msgstr "reloj" +#~ msgid "clock" +#~ msgstr "reloj" -#: ../C/gdm.xml:5176 (para) #, fuzzy -msgid "Label that displays the date and time." -msgstr "Etiqueta que muesta la fecha y la hora." +#~ msgid "Label that displays the date and time." +#~ msgstr "Etiqueta que muesta la fecha y la hora." -#: ../C/gdm.xml:5183 (term) #, fuzzy -msgid "pam-prompt" -msgstr "pam-prompt" +#~ msgid "pam-prompt" +#~ msgstr "pam-prompt" -#: ../C/gdm.xml:5185 (para) -msgid "" -"Label that displays the PAM prompt. This is the prompt that PAM uses to ask " -"for username, password, etc..." -msgstr "" - -#: ../C/gdm.xml:5193 (term) #, fuzzy -msgid "pam-error" -msgstr "pam-error" +#~ msgid "pam-error" +#~ msgstr "pam-error" -#: ../C/gdm.xml:5195 (para) -msgid "Label that displayst PAM/GDM error messages. Such as when user can't log in." -msgstr "" - -#: ../C/gdm.xml:5203 (term) #, fuzzy -msgid "pam-message" -msgstr "pam-message" +#~ msgid "pam-message" +#~ msgstr "pam-message" -#: ../C/gdm.xml:5205 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:5214 (term) #, fuzzy -msgid "timed-label" -msgstr "timed-label" +#~ msgid "timed-label" +#~ msgstr "timed-label" -#: ../C/gdm.xml:5216 (para) -msgid "Label that displays timed login information." -msgstr "Etiqueta que muestra la información de la entrada temporizada." +#~ msgid "Label that displays timed login information." +#~ msgstr "Etiqueta que muestra la información de la entrada temporizada." -#: ../C/gdm.xml:5223 (para) #, fuzzy -msgid "Rectangles can have id values as follows:" -msgstr "Los rectángulos pueden tener valores id como los siguientes:" +#~ msgid "Rectangles can have id values as follows:" +#~ msgstr "Los rectángulos pueden tener valores id como los siguientes:" -#: ../C/gdm.xml:5229 (term) #, fuzzy -msgid "caps-lock-warning" -msgstr "caps-lock-warning" - -#: ../C/gdm.xml:5231 (para) -msgid "" -"Displays an icon that shows if the CAPS LOCK key is depressed. This " -"rectangle will be hidden/shown appropriately" -msgstr "" +#~ msgid "caps-lock-warning" +#~ msgstr "caps-lock-warning" -#: ../C/gdm.xml:5240 (para) #, fuzzy -msgid "" -"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>" -msgstr "rect<screen>< rect></screen>" - -#: ../C/gdm.xml:5246 (para) -msgid "Possible values for button ids are as follows:" -msgstr "" +#~ msgid "" +#~ "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>" +#~ msgstr "rect<screen>< rect></screen>" -#: ../C/gdm.xml:5252 (term) #, fuzzy -msgid "chooser_button" -msgstr "chooser_button" +#~ msgid "chooser_button" +#~ msgstr "chooser_button" -#: ../C/gdm.xml:5254 (para) #, fuzzy -msgid "Runs the XDMCP chooser." -msgstr "XDMCP chooser." +#~ msgid "Runs the XDMCP chooser." +#~ msgstr "XDMCP chooser." -#: ../C/gdm.xml:5261 (term) #, fuzzy -msgid "config_button" -msgstr "config_button" +#~ msgid "config_button" +#~ msgstr "config_button" -#: ../C/gdm.xml:5263 (para) -msgid "Runs the GDM configuration application." -msgstr "Ejecuta la aplicación de configuración de GDM." +#~ msgid "Runs the GDM configuration application." +#~ msgstr "Ejecuta la aplicación de configuración de GDM." -#: ../C/gdm.xml:5270 (term) #, fuzzy -msgid "disconnect_button" -msgstr "disconnect_button" +#~ msgid "disconnect_button" +#~ msgstr "disconnect_button" -#: ../C/gdm.xml:5272 (para) -msgid "Disconnect from remote session." -msgstr "Desconectar de una sesión remota." +#~ msgid "Disconnect from remote session." +#~ msgstr "Desconectar de una sesión remota." -#: ../C/gdm.xml:5279 (term) -msgid "language_button" -msgstr "botón_idioma" +#~ msgid "language_button" +#~ msgstr "botón_idioma" -#: ../C/gdm.xml:5281 (para) -msgid "Displays the language selection dialog." -msgstr "Muestra el diálogo de selección del idioma." +#~ msgid "Displays the language selection dialog." +#~ msgstr "Muestra el diálogo de selección del idioma." -#: ../C/gdm.xml:5288 (term) -msgid "halt_button" -msgstr "botón_detener" +#~ msgid "halt_button" +#~ msgstr "botón_detener" -#: ../C/gdm.xml:5290 (para) #, fuzzy -msgid "Halt (shuts down) the system." -msgstr "Detiene (apaga) el sistema." +#~ msgid "Halt (shuts down) the system." +#~ msgstr "Detiene (apaga) el sistema." -#: ../C/gdm.xml:5297 (term) -msgid "reboot_button" -msgstr "botón reiniciar" +#~ msgid "reboot_button" +#~ msgstr "botón reiniciar" -#: ../C/gdm.xml:5299 (para) #, fuzzy -msgid "Restart the system." -msgstr "Reiniciar el sistema" +#~ msgid "Restart the system." +#~ msgstr "Reiniciar el sistema" -#: ../C/gdm.xml:5306 (term) -msgid "session_button" -msgstr "botón_sesión" +#~ msgid "session_button" +#~ msgstr "botón_sesión" -#: ../C/gdm.xml:5308 (para) #, fuzzy -msgid "List and select from available sessions." -msgstr "Lista y selecciona las sesiones disponibles." +#~ msgid "List and select from available sessions." +#~ msgstr "Lista y selecciona las sesiones disponibles." -#: ../C/gdm.xml:5315 (term) -msgid "suspend_button" -msgstr "botón_suspender" +#~ msgid "suspend_button" +#~ msgstr "botón_suspender" -#: ../C/gdm.xml:5317 (para) -msgid "Suspend the system." -msgstr "Suspender el sistema" +#~ msgid "Suspend the system." +#~ msgstr "Suspender el sistema" -#: ../C/gdm.xml:5324 (term) -msgid "system_button" -msgstr "botón_sistema" - -#: ../C/gdm.xml:5326 (para) -msgid "" -"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." -msgstr "" +#~ msgid "system_button" +#~ msgstr "botón_sistema" -#: ../C/gdm.xml:5340 (title) #, fuzzy -msgid "Position Node" -msgstr "Nodo de posición" - -#: ../C/gdm.xml:5342 (para) -msgid "" -"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>" -msgstr "" - -#: ../C/gdm.xml:5348 (para) -msgid "" -"Both position and size can be given in percent and it will be taken as the " -"percentage of the size of the current container. For toplevel items it's the " -"percentage of the whole screen." -msgstr "" - -#: ../C/gdm.xml:5354 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:5361 (para) -msgid "" -"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>" -msgstr "" - -#: ../C/gdm.xml:5370 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:5376 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:5382 (para) -msgid "" -"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)." -msgstr "" +#~ msgid "Position Node" +#~ msgstr "Nodo de posición" -#: ../C/gdm.xml:5389 (para) #, fuzzy -msgid "" -"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>\n" -"<item type=\"label\">\n" -"<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -" </screen>" -msgstr "" -"label label label<screen>\n" -"< label>\n" -"<>\n" -"</screen>" +#~ msgid "" +#~ "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>\n" +#~ "<item type=\"label\">\n" +#~ "<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" +#~ " </screen>" +#~ msgstr "" +#~ "label label label<screen>\n" +#~ "< label>\n" +#~ "<>\n" +#~ "</screen>" -#: ../C/gdm.xml:5406 (title) -msgid "Show Node" -msgstr "Mostrar nodo." +#~ msgid "Show Node" +#~ msgstr "Mostrar nodo." -#: ../C/gdm.xml:5408 (para) -msgid "" -"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:" -msgstr "" - -#: ../C/gdm.xml:5414 (para) #, fuzzy -msgid "<filename>console</filename> - In console mode." -msgstr "<filename>console</filename> - En modo consola." - -#: ../C/gdm.xml:5417 (para) -msgid "<filename>console-fixed</filename> - In console non-flexi mode." -msgstr "" - -#: ../C/gdm.xml:5420 (para) -msgid "<filename>console-flexi</filename> - In console & flexi mode." -msgstr "" +#~ msgid "<filename>console</filename> - In console mode." +#~ msgstr "<filename>console</filename> - En modo consola." -#: ../C/gdm.xml:5423 (para) -msgid "<filename>flexi</filename> - In flexi mode." -msgstr "" - -#: ../C/gdm.xml:5426 (para) -msgid "<filename>remote</filename> - In remote mode." -msgstr "" - -#: ../C/gdm.xml:5429 (para) -msgid "<filename>remote-flexi</filename> - In remote & flexi mode." -msgstr "" - -#: ../C/gdm.xml:5433 (para) -msgid "For example: <screen><show modes=\"flexi,remote\"/></screen>" -msgstr "" - -#: ../C/gdm.xml:5438 (para) -msgid "" -"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:" -msgstr "" - -#: ../C/gdm.xml:5444 (para) #, fuzzy -msgid "" -"<filename>chooser</filename>, if ChooserButton is set to \"true\" in the GDM " -"configuration." -msgstr "<filename>chooser</filename>, si ChooserButton está puesto a «true» en la configuración de GDM." +#~ msgid "" +#~ "<filename>chooser</filename>, if ChooserButton is set to \"true\" in the " +#~ "GDM configuration." +#~ msgstr "" +#~ "<filename>chooser</filename>, si ChooserButton está puesto a «true» en la " +#~ "configuración de GDM." -#: ../C/gdm.xml:5448 (para) #, fuzzy -msgid "" -"<filename>config</filename>, if ConfigAvailable is set to \"true\" in the " -"GDM configuration." -msgstr "<filename>configurar</filename>, si ConfigAvailable está puesto a «true» en la configuración de GDM." +#~ msgid "" +#~ "<filename>config</filename>, if ConfigAvailable is set to \"true\" in the " +#~ "GDM configuration." +#~ msgstr "" +#~ "<filename>configurar</filename>, si ConfigAvailable está puesto a «true» " +#~ "en la configuración de GDM." -#: ../C/gdm.xml:5452 (para) #, fuzzy -msgid "" -"<filename>halt</filename>, if HaltDaemon is specified in the GDM " -"configuration." -msgstr "<filename>halt</filename>, si HaltDaemon está especificado en la configuración de GDM." +#~ msgid "" +#~ "<filename>halt</filename>, if HaltDaemon is specified in the GDM " +#~ "configuration." +#~ msgstr "" +#~ "<filename>halt</filename>, si HaltDaemon está especificado en la " +#~ "configuración de GDM." -#: ../C/gdm.xml:5456 (para) #, fuzzy -msgid "" -"<filename>reboot</filename>, if RebootCommand is specified in the GDM " -"configuration." -msgstr "<filename>reiniciar</filename>, si RebootCommand está especificado en la configuración de GDM." +#~ msgid "" +#~ "<filename>reboot</filename>, if RebootCommand is specified in the GDM " +#~ "configuration." +#~ msgstr "" +#~ "<filename>reiniciar</filename>, si RebootCommand está especificado en la " +#~ "configuración de GDM." -#: ../C/gdm.xml:5460 (para) #, fuzzy -msgid "" -"<filename>suspend</filename>, if SuspendCommand is specified in the GDM " -"configuration." -msgstr "<filename>suspend</filename>, si SuspendCommand está especificado en la configuración de GDM." +#~ msgid "" +#~ "<filename>suspend</filename>, if SuspendCommand is specified in the GDM " +#~ "configuration." +#~ msgstr "" +#~ "<filename>suspend</filename>, si SuspendCommand está especificado en la " +#~ "configuración de GDM." -#: ../C/gdm.xml:5464 (para) #, fuzzy -msgid "" -"<filename>system</filename>, if SystemMenu is specified in the GDM " -"configuration." -msgstr "<filename>system</filename>, si SystemMenu está especificado en la configuración de GDM." +#~ msgid "" +#~ "<filename>system</filename>, if SystemMenu is specified in the GDM " +#~ "configuration." +#~ msgstr "" +#~ "<filename>system</filename>, si SystemMenu está especificado en la " +#~ "configuración de GDM." -#: ../C/gdm.xml:5468 (para) #, fuzzy -msgid "" -"<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in the " -"GDM configuration." -msgstr "<filename>timed</filename>, si TimedLoginEnabled está puesto a \"true\" en la configuración de GDM." +#~ msgid "" +#~ "<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in " +#~ "the GDM configuration." +#~ msgstr "" +#~ "<filename>timed</filename>, si TimedLoginEnabled está puesto a \"true\" " +#~ "en la configuración de GDM." -#: ../C/gdm.xml:5473 (para) #, fuzzy -msgid "For example: <screen><show modes=\"console\" type=\"system\"/></screen>" -msgstr "Por ejemplo: <screen><show modes=\"console\" type=\"system\"/></screen>" +#~ msgid "" +#~ "For example: <screen><show modes=\"console\" type=\"system\"/></" +#~ "screen>" +#~ msgstr "" +#~ "Por ejemplo: <screen><show modes=\"console\" type=\"system\"/></" +#~ "screen>" -#: ../C/gdm.xml:5478 (para) #, fuzzy -msgid "" -"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." -msgstr "chooser." - -#: ../C/gdm.xml:5487 (title) -msgid "Normal/Active/Prelight Nodes" -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "chooser." -#: ../C/gdm.xml:5489 (para) #, fuzzy -msgid "" -"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:" -msgstr "userlist:" - -#: ../C/gdm.xml:5494 (para) -msgid "<filename>normal</filename> - normal state." -msgstr "" - -#: ../C/gdm.xml:5497 (para) -msgid "<filename>active</filename> - when the item has active focus." -msgstr "" - -#: ../C/gdm.xml:5500 (para) -msgid "<filename>prelight</filename> - when the mouse is hovering over the item." -msgstr "" +#~ msgid "" +#~ "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:" +#~ msgstr "userlist:" -#: ../C/gdm.xml:5505 (para) #, fuzzy -msgid "" -"When item is \"rect\" (alpha can be omitted and defaults to 0.0): " -"<screen><normal color=\"#ffffff\" alpha=\"0.0\"></screen>" -msgstr "rect<screen><></screen>" +#~ msgid "" +#~ "When item is \"rect\" (alpha can be omitted and defaults to 0.0): " +#~ "<screen><normal color=\"#ffffff\" alpha=\"0.0\"></screen>" +#~ msgstr "rect<screen><></screen>" -#: ../C/gdm.xml:5511 (para) #, fuzzy -msgid "" -"When item is \"label\" <screen><normal color=\"#ffffff\" font=\"Sans 14\"/" -"></screen>" -msgstr "label<screen><></screen>" +#~ msgid "" +#~ "When item is \"label\" <screen><normal color=\"#ffffff\" font=\"Sans 14" +#~ "\"/></screen>" +#~ msgstr "label<screen><></screen>" -#: ../C/gdm.xml:5516 (para) #, fuzzy -msgid "" -"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>" -msgstr "pixmap<screen><></screen>" +#~ msgid "" +#~ "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>" +#~ msgstr "pixmap<screen><></screen>" -#: ../C/gdm.xml:5523 (para) #, fuzzy -msgid "" -"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>." -msgstr "<filename></filename><filename><>< nombre></filename>." +#~ msgid "" +#~ "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>." +#~ msgstr "<filename></filename><filename><>< nombre></filename>." -#: ../C/gdm.xml:5531 (title) #, fuzzy -msgid "Face Browser Icon/Label Color Nodes" -msgstr "Browser" +#~ msgid "Face Browser Icon/Label Color Nodes" +#~ msgstr "Browser" -#: ../C/gdm.xml:5533 (para) #, fuzzy -msgid "" -"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:" -msgstr "userlist label:" - -#: ../C/gdm.xml:5539 (screen) -#, no-wrap -msgid "<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>" -msgstr "" +#~ msgid "" +#~ "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:" +#~ msgstr "userlist label:" -#: ../C/gdm.xml:5544 (title) #, fuzzy -msgid "Text Node" -msgstr "Nodo de texto" +#~ msgid "Text Node" +#~ msgstr "Nodo de texto" -#: ../C/gdm.xml:5546 (para) -msgid "" -"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>" -msgstr "" - -#: ../C/gdm.xml:5553 (para) #, fuzzy -msgid "" -"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&lt;sup&>" -"bar&lt;/sup&></text></screen>" -msgstr "label<><><screen><>&&>&&><></screen>" - -#: ../C/gdm.xml:5560 (para) -msgid "" -"Text nodes can contain the following special character sequences which will " -"be translated as follows:" -msgstr "" +#~ msgid "" +#~ "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&lt;" +#~ "sup&>bar&lt;/sup&></text></screen>" +#~ msgstr "" +#~ "label<><><screen><>&&>&&><>" +#~ "</screen>" -#: ../C/gdm.xml:5565 (para) #, fuzzy -msgid "%% - A literal % character" -msgstr "%% - Un carácter literal %" +#~ msgid "%% - A literal % character" +#~ msgstr "%% - Un carácter literal %" -#: ../C/gdm.xml:5568 (para) #, fuzzy -msgid "" -"%c - Clock time. Only labels with the \"clock\" id will update automatically " -"every second. Other labels will contain a static timestamp." -msgstr "clock." +#~ msgid "" +#~ "%c - Clock time. Only labels with the \"clock\" id will update " +#~ "automatically every second. Other labels will contain a static timestamp." +#~ msgstr "clock." -#: ../C/gdm.xml:5573 (para) #, fuzzy -msgid "%d - Display name (DISPLAY environment variable)" -msgstr "nombre" +#~ msgid "%d - Display name (DISPLAY environment variable)" +#~ msgstr "nombre" -#: ../C/gdm.xml:5576 (para) -msgid "%h - Hostname (gethostname output)" -msgstr "" - -#: ../C/gdm.xml:5579 (para) #, fuzzy -msgid "%m - Machine name (uname.machine output)" -msgstr "nombre" +#~ msgid "%m - Machine name (uname.machine output)" +#~ msgstr "nombre" -#: ../C/gdm.xml:5582 (para) #, fuzzy -msgid "%n - Node name (uname.nodename output)" -msgstr "nombre" +#~ msgid "%n - Node name (uname.nodename output)" +#~ msgstr "nombre" -#: ../C/gdm.xml:5585 (para) #, fuzzy -msgid "%o - Domain name (getdomainname output)" -msgstr "nombre" +#~ msgid "%o - Domain name (getdomainname output)" +#~ msgstr "nombre" -#: ../C/gdm.xml:5588 (para) #, fuzzy -msgid "%r - Release name (uname.release output)" -msgstr "nombre" +#~ msgid "%r - Release name (uname.release output)" +#~ msgstr "nombre" -#: ../C/gdm.xml:5591 (para) #, fuzzy -msgid "%s - System name (uname.sysname output)" -msgstr "nombre" +#~ msgid "%s - System name (uname.sysname output)" +#~ msgstr "nombre" -#: ../C/gdm.xml:5594 (para) #, fuzzy -msgid "" -"%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." -msgstr "label." +#~ msgid "" +#~ "%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." +#~ msgstr "label." -#: ../C/gdm.xml:5602 (para) #, fuzzy -msgid "" -"%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." -msgstr "label." +#~ msgid "" +#~ "%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." +#~ msgstr "label." -#: ../C/gdm.xml:5608 (para) #, fuzzy -msgid "\\n - Carriage return" -msgstr "\\n - Retorno de carro" +#~ msgid "\\n - Carriage return" +#~ msgstr "\\n - Retorno de carro" -#: ../C/gdm.xml:5611 (para) -msgid "" -"_ - An underscore causes the following character to be underlined. If it " -"precedes a % character sequence, the string that replaces the character " -"sequence is underlined." -msgstr "" - -#: ../C/gdm.xml:5619 (title) -msgid "Stock" -msgstr "Stock" +#~ msgid "Stock" +#~ msgstr "Stock" -#: ../C/gdm.xml:5621 (para) -msgid "" -"Certain common localized labels can be specified via the stock tags. The " -"\"text\" tag is ignored if the \"stock\" tag is used. You should really use " -"the stock labels rather then just putting all the translations into the " -"themes. This gives faster load times and likely better translations. The " -"following values are valid:" -msgstr "" - -#: ../C/gdm.xml:5630 (para) -msgid "<filename>cancel</filename>, _(\"_Cancel\"" -msgstr "" - -#: ../C/gdm.xml:5633 (para) -msgid "<filename>caps-lock-warning</filename>, _(\"You've got capslock on!\"" -msgstr "" - -#: ../C/gdm.xml:5636 (para) #, fuzzy -msgid "<filename>chooser</filename>, _(\"_XDMCP Chooser\"" -msgstr "<filename> chooser</filename> XDMCP Chooser" - -#: ../C/gdm.xml:5639 (para) -msgid "<filename>disconnect</filename>, _(\"D_isconnect\"" -msgstr "" - -#: ../C/gdm.xml:5642 (para) -msgid "<filename>halt</filename>, _(\"Shut_down\"" -msgstr "" - -#: ../C/gdm.xml:5645 (para) -msgid "<filename>language</filename>, _(\"_Language\"" -msgstr "" - -#: ../C/gdm.xml:5648 (para) -msgid "<filename>ok</filename>, _(\"_OK\"" -msgstr "" - -#: ../C/gdm.xml:5651 (para) -msgid "<filename>quit</filename>, _(\"_Quit\"" -msgstr "" +#~ msgid "<filename>chooser</filename>, _(\"_XDMCP Chooser\"" +#~ msgstr "<filename> chooser</filename> XDMCP Chooser" -#: ../C/gdm.xml:5654 (para) -msgid "<filename>reboot</filename>, _(\"_Restart\"" -msgstr "" - -#: ../C/gdm.xml:5657 (para) -msgid "<filename>session</filename>, _(\"_Session\"" -msgstr "" - -#: ../C/gdm.xml:5660 (para) -msgid "<filename>suspend</filename>, _(\"Sus_pend\"" -msgstr "" - -#: ../C/gdm.xml:5663 (para) -msgid "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\"" -msgstr "" - -#: ../C/gdm.xml:5666 (para) #, fuzzy -msgid "<filename>timed-label</filename>, _(\"User %u will login in %t\"" -msgstr "<filename> label</filename> User" +#~ msgid "<filename>timed-label</filename>, _(\"User %u will login in %t\"" +#~ msgstr "<filename> label</filename> User" -#: ../C/gdm.xml:5669 (para) #, fuzzy -msgid "<filename>username-label</filename>, _(\"Username:\"" -msgstr "<filename> label</filename>" +#~ msgid "<filename>username-label</filename>, _(\"Username:\"" +#~ msgstr "<filename> label</filename>" -#: ../C/gdm.xml:5672 (para) #, fuzzy -msgid "<filename>welcome-label</filename>, _(\"Welcome to %n\"" -msgstr "<filename> label</filename> Welcome" +#~ msgid "<filename>welcome-label</filename>, _(\"Welcome to %n\"" +#~ msgstr "<filename> label</filename> Welcome" -#: ../C/gdm.xml:5676 (para) #, fuzzy -msgid "For example: <screen><stock type=\"welcome-label\"></screen>" -msgstr "<screen>< label></screen>" +#~ msgid "For example: <screen><stock type=\"welcome-label\"></screen>" +#~ msgstr "<screen>< label></screen>" -#: ../C/gdm.xml:5683 (title) -msgid "Custom Widgetry" -msgstr "" - -#: ../C/gdm.xml:5685 (para) #, fuzzy -msgid "" -"Currently there is one item which can be customizable and this is the list " -"item. If you need to ask the user extra things, such as to pick from a list " -"of places to log into, or set of custom login sessions you can setup the " -"list item and add listitem children that describe the choices. Each listitem " -"must have an id and a text child. The choice will be recorded in the file " -"<filename><ServAuthDir>/<display>.GreeterInfo</filename> as " -"<filename><list id>=<listitem id></filename>." -msgstr "list list list<filename>< ServAuthDir><></filename><filename>< list><></filename>." +#~ msgid "" +#~ "Currently there is one item which can be customizable and this is the " +#~ "list item. If you need to ask the user extra things, such as to pick from " +#~ "a list of places to log into, or set of custom login sessions you can " +#~ "setup the list item and add listitem children that describe the choices. " +#~ "Each listitem must have an id and a text child. The choice will be " +#~ "recorded in the file <filename><ServAuthDir>/<display>." +#~ "GreeterInfo</filename> as <filename><list id>=<listitem id></" +#~ "filename>." +#~ msgstr "" +#~ "list list list<filename>< ServAuthDir><></" +#~ "filename><filename>< list><></filename>." -#: ../C/gdm.xml:5696 (para) #, fuzzy -msgid "" -"For example suppose we are on display :0, <filename>ServAuthDir</filename> " -"is <filename><var>/gdm</filename> and we have the following in the " -"theme:" -msgstr "Por ejemplo suponga que estamos en la pantalla 0, <filename>ServAuthDir</filename> es <filename>/var/gdm</filename> y necesitamos tener lo siguiente en el tema:" +#~ msgid "" +#~ "For example suppose we are on display :0, <filename>ServAuthDir</" +#~ "filename> is <filename><var>/gdm</filename> and we have the " +#~ "following in the theme:" +#~ msgstr "" +#~ "Por ejemplo suponga que estamos en la pantalla 0, <filename>ServAuthDir</" +#~ "filename> es <filename>/var/gdm</filename> y necesitamos tener lo " +#~ "siguiente en el tema:" -#: ../C/gdm.xml:5702 (screen) -#, no-wrap #, fuzzy -msgid "" -"\n" -"<item type=\"list\" id=\"custom-config\">\n" -"<pos anchor=\"nw\" x=\"1\" y=\"1\" height=\"200\" width=\"100\">\n" -"<listitem id=\"foo\">\n" -"<text>Foo</text>\n" -"</listitem>\n" -"<listitem id=\"bar\">\n" -"<text>Bar</text>\n" -"</listitem>\n" -"</item>\n" -" " -msgstr "" -"\n" -"< list>\n" -"<>\n" -"<>\n" -"<><>\n" -"<>\n" -"<>\n" -"<><>\n" -"<>\n" -"<> " - -#: ../C/gdm.xml:5714 (para) -msgid "" -"Then if the user chooses 'Foo' then <filename><var>/gdm/:0." -"GreeterInfo</filename> will contain: <screen>custom-config=foo</screen>" -msgstr "" +#~ msgid "" +#~ "\n" +#~ "<item type=\"list\" id=\"custom-config\">\n" +#~ "<pos anchor=\"nw\" x=\"1\" y=\"1\" height=\"200\" width=\"100\">\n" +#~ "<listitem id=\"foo\">\n" +#~ "<text>Foo</text>\n" +#~ "</listitem>\n" +#~ "<listitem id=\"bar\">\n" +#~ "<text>Bar</text>\n" +#~ "</listitem>\n" +#~ "</item>\n" +#~ " " +#~ msgstr "" +#~ "\n" +#~ "< list>\n" +#~ "<>\n" +#~ "<>\n" +#~ "<><>\n" +#~ "<>\n" +#~ "<>\n" +#~ "<><>\n" +#~ "<>\n" +#~ "<> " -#: ../C/gdm.xml:5724 (title) -msgid "Accessibility" -msgstr "Accesibilidad" +#~ msgid "Accessibility" +#~ msgstr "Accesibilidad" -#: ../C/gdm.xml:5725 (para) #, fuzzy -msgid "" -"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. This feature allows the user to launch assistive technologies at " -"login time by means of special \"gestures\" from the standard keyboard and " -"from a keyboard, pointing device, or switch device attached to the USB or " -"PS/2 mouse port. It also allows the user to change the visual appearance of " -"the login UI before logging in, for instance to use a higher-contrast color " -"scheme for better visibility. GDM only supports accessibility with the GTK+ " -"Greeter, so the \"Greeter\" parameter in the GDM configuration must be set " -"to the GTK+ Greeter \"gdmlogin\"" -msgstr "Greeter Greeter Greeter" - -#: ../C/gdm.xml:5740 (title) -msgid "Accessibility Configuration" -msgstr "Configuración de accesibilidad" - -#: ../C/gdm.xml:5741 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:5749 (para) -msgid "" -"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\"." -msgstr "" +#~ msgid "" +#~ "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. This feature allows the user to launch " +#~ "assistive technologies at login time by means of special \"gestures\" " +#~ "from the standard keyboard and from a keyboard, pointing device, or " +#~ "switch device attached to the USB or PS/2 mouse port. It also allows the " +#~ "user to change the visual appearance of the login UI before logging in, " +#~ "for instance to use a higher-contrast color scheme for better visibility. " +#~ "GDM only supports accessibility with the GTK+ Greeter, so the \"Greeter\" " +#~ "parameter in the GDM configuration must be set to the GTK+ Greeter " +#~ "\"gdmlogin\"" +#~ msgstr "Greeter Greeter Greeter" + +#~ msgid "Accessibility Configuration" +#~ msgstr "Configuración de accesibilidad" -#: ../C/gdm.xml:5756 (para) #, fuzzy -msgid "" -"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:" -msgstr "<filename> GtkThemesToAllow</filename> list:" +#~ msgid "" +#~ "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:" +#~ msgstr "<filename> GtkThemesToAllow</filename> list:" -#: ../C/gdm.xml:5763 (screen) -#, no-wrap #, fuzzy -msgid "GtkThemesToAllow=HighContrast,HighContrastInverse" -msgstr "GtkThemesToAllow" +#~ msgid "GtkThemesToAllow=HighContrast,HighContrastInverse" +#~ msgstr "GtkThemesToAllow" -#: ../C/gdm.xml:5765 (para) #, fuzzy -msgid "" -"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:" -msgstr "<filename> AddGtkModules</filename><filename> GtkModulesList</filename>:" +#~ msgid "" +#~ "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:" +#~ msgstr "" +#~ "<filename> AddGtkModules</filename><filename> GtkModulesList</filename>:" -#: ../C/gdm.xml:5774 (screen) -#, no-wrap #, fuzzy -msgid "GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener" -msgstr "GtkModulesList" - -#: ../C/gdm.xml:5776 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:5793 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:5804 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:5813 (para) -msgid "" -"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." -msgstr "" +#~ msgid "GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener" +#~ msgstr "GtkModulesList" -#: ../C/gdm.xml:5823 (para) -msgid "" -"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." -msgstr "" - -#: ../C/gdm.xml:5832 (para) -msgid "" -"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" -msgstr "" - -#: ../C/gdm.xml:5839 (para) #, fuzzy -msgid "" -"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." -msgstr "chooser." - -#: ../C/gdm.xml:5850 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "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." +#~ msgstr "chooser." -#: ../C/gdm.xml:5871 (title) #, fuzzy -msgid "Accessibility Login Sound Configuration" -msgstr "Configuración de sonido de accesibilidad en la entrada" +#~ msgid "Accessibility Login Sound Configuration" +#~ msgstr "Configuración de sonido de accesibilidad en la entrada" -#: ../C/gdm.xml:5872 (para) #, fuzzy -msgid "" -"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>/usr/bin/play</filename> (or <filename>/usr/" -"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." -msgstr "<filename></filename><filename></filename> SoundProgram." - -#: ../C/gdm.xml:5887 (title) -msgid "Solaris Specific Features" -msgstr "Características específicas de Solaris" - -#: ../C/gdm.xml:5889 (para) -msgid "GDM supports a few features specific to Solaris, as follows:" -msgstr "" -"GDM soporta unas pocas características específicas a Solaris, como las " -"siguientes:" +#~ msgid "" +#~ "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>/usr/bin/play</filename> (or " +#~ "<filename>/usr/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." +#~ msgstr "<filename></filename><filename></filename> SoundProgram." + +#~ msgid "Solaris Specific Features" +#~ msgstr "Características específicas de Solaris" + +#~ msgid "GDM supports a few features specific to Solaris, as follows:" +#~ msgstr "" +#~ "GDM soporta unas pocas características específicas a Solaris, como las " +#~ "siguientes:" -#: ../C/gdm.xml:5893 (para) -msgid "GDM supports Solaris Auditing if running on Solaris 10 or higher." -msgstr "GDM soporta Solaris Auditing si se ejecuta sobre Solaris 10 o superior." +#~ msgid "GDM supports Solaris Auditing if running on Solaris 10 or higher." +#~ msgstr "" +#~ "GDM soporta Solaris Auditing si se ejecuta sobre Solaris 10 o superior." -#: ../C/gdm.xml:5897 (para) #, fuzzy -msgid "" -"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." -msgstr "AlwaysRestartServer." +#~ msgid "" +#~ "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." +#~ msgstr "AlwaysRestartServer." -#: ../C/gdm.xml:5906 (para) #, fuzzy -msgid "" -"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." -msgstr "<filename></filename><filename> DefaultPath</filename><filename> RootPath</filename><filename> PasswordRequired</filename><filename> AllowRemoteRoot</filename> Configuración." - -#: ../C/gdm.xml:5918 (title) -msgid "Example Configurations" -msgstr "Configuraciones de ejemplo" - -#: ../C/gdm.xml:5920 (para) -msgid "" -"This section has some example configurations that are useful for various " -"setups." -msgstr "" -"Esta sección tiene algunas configuraciones de ejemplo que son útiles para " -"varias configuraciones." +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "<filename></filename><filename> DefaultPath</filename><filename> " +#~ "RootPath</filename><filename> PasswordRequired</filename><filename> " +#~ "AllowRemoteRoot</filename> Configuración." -#: ../C/gdm.xml:5926 (title) -msgid "Terminal Lab With One Server" -msgstr "" +#~ msgid "Example Configurations" +#~ msgstr "Configuraciones de ejemplo" -#: ../C/gdm.xml:5928 (para) -msgid "" -"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." -msgstr "" +#~ msgid "" +#~ "This section has some example configurations that are useful for various " +#~ "setups." +#~ msgstr "" +#~ "Esta sección tiene algunas configuraciones de ejemplo que son útiles para " +#~ "varias configuraciones." -#: ../C/gdm.xml:5935 (para) #, fuzzy -msgid "" -"On <filename>appserver</filename> you enable XDMCP, so you have <screen>\n" -"[xdmcp]\n" -"Enable=true\n" -" </screen> If you want no local screens here, you can then make the " -"<filename>[servers]</filename> section empty." -msgstr "" -"<filename></filename> XDMCP<screen>\n" -"</screen><filename></filename>." +#~ msgid "" +#~ "On <filename>appserver</filename> you enable XDMCP, so you have <screen>\n" +#~ "[xdmcp]\n" +#~ "Enable=true\n" +#~ " </screen> If you want no local screens here, you can then make " +#~ "the <filename>[servers]</filename> section empty." +#~ msgstr "" +#~ "<filename></filename> XDMCP<screen>\n" +#~ "</screen><filename></filename>." -#: ../C/gdm.xml:5945 (para) #, fuzzy -msgid "" -"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>\n" -"[server-Terminal]\n" -"name=Terminal server\n" -"command=/usr/X11R6/bin/X -terminate\n" -"flexible=false\n" -"handled=false\n" -" </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>\n" -"[servers]\n" -"0=Terminal -query appserver\n" -" </screen> This will run a direct XDMCP query to the server named " -"<filename>appserver</filename>." -msgstr "" -"<filename></filename> XDMCP<filename></filename><screen>\n" -"</screen><filename> handled</filename><filename></filename><filename></filename><screen>\n" -"</screen> XDMCP<filename></filename>." +#~ msgid "" +#~ "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>\n" +#~ "[server-Terminal]\n" +#~ "name=Terminal server\n" +#~ "command=/usr/X11R6/bin/X -terminate\n" +#~ "flexible=false\n" +#~ "handled=false\n" +#~ " </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>\n" +#~ "[servers]\n" +#~ "0=Terminal -query appserver\n" +#~ " </screen> This will run a direct XDMCP query to the server named " +#~ "<filename>appserver</filename>." +#~ msgstr "" +#~ "<filename></filename> XDMCP<filename></filename><screen>\n" +#~ "</screen><filename> handled</filename><filename></filename><filename></" +#~ "filename><screen>\n" +#~ "</screen> XDMCP<filename></filename>." -#: ../C/gdm.xml:5973 (title) #, fuzzy -msgid "Terminal Lab With Two Or More Servers" -msgstr "Laboratorio con terminales con dos o más servidores" +#~ msgid "Terminal Lab With Two Or More Servers" +#~ msgstr "Laboratorio con terminales con dos o más servidores" -#: ../C/gdm.xml:5975 (para) #, fuzzy -msgid "" -"Suppose you want to make a lab full of X terminals that all connect to some " -"choice of servers. For now let's make it <filename>appserverone</filename> " -"and <filename>appservertwo</filename>. Again we'll call our example X " -"terminal server <filename>xterminal</filename>. The setup on both servers is " -"the same as with the case of one server in the previous section. You do not " -"need to explicitly enable indirect queries on the server since we'll run the " -"choosers locally on the X terminals." -msgstr "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." +#~ msgid "" +#~ "Suppose you want to make a lab full of X terminals that all connect to " +#~ "some choice of servers. For now let's make it <filename>appserverone</" +#~ "filename> and <filename>appservertwo</filename>. Again we'll call our " +#~ "example X terminal server <filename>xterminal</filename>. The setup on " +#~ "both servers is the same as with the case of one server in the previous " +#~ "section. You do not need to explicitly enable indirect queries on the " +#~ "server since we'll run the choosers locally on the X terminals." +#~ msgstr "" +#~ "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." -#: ../C/gdm.xml:5986 (para) #, fuzzy -msgid "" -"So on the <filename>xterminal</filename> you again disable XDMCP. You will " -"add a server type perhaps called <filename>Chooser</filename> as follows: " -"<screen>\n" -"[server-Chooser]\n" -"name=Chooser server\n" -"command=/usr/X11R6/bin/X\n" -"flexible=false\n" -"chooser=true\n" -" </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>\n" -"[servers]\n" -"0=Chooser\n" -" </screen>" -msgstr "" -"<filename></filename> XDMCP<filename> Chooser</filename><screen> Chooser Chooser\n" -"</screen><filename> chooser</filename> XDMCP chooser<screen> Chooser\n" -"</screen>" +#~ msgid "" +#~ "So on the <filename>xterminal</filename> you again disable XDMCP. You " +#~ "will add a server type perhaps called <filename>Chooser</filename> as " +#~ "follows: <screen>\n" +#~ "[server-Chooser]\n" +#~ "name=Chooser server\n" +#~ "command=/usr/X11R6/bin/X\n" +#~ "flexible=false\n" +#~ "chooser=true\n" +#~ " </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>\n" +#~ "[servers]\n" +#~ "0=Chooser\n" +#~ " </screen>" +#~ msgstr "" +#~ "<filename></filename> XDMCP<filename> Chooser</filename><screen> Chooser " +#~ "Chooser\n" +#~ "</screen><filename> chooser</filename> XDMCP chooser<screen> Chooser\n" +#~ "</screen>" -#: ../C/gdm.xml:6009 (para) #, fuzzy -msgid "" -"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." -msgstr "XDMCP chooser<filename> chooser</filename><screen> Hosts</screen>." +#~ msgid "" +#~ "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." +#~ msgstr "XDMCP chooser<filename> chooser</filename><screen> Hosts</screen>." -#: ../C/gdm.xml:6019 (para) #, fuzzy -msgid "" -"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>\n" -"[servers]\n" -"0=Terminal -indirect appserver\n" -" </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 serveral 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." -msgstr "" -"chooser XDMCP<filename></filename><screen>\n" -"</screen><filename> Hosts</filename> entry<filename></filename> XDMCP chooser." +#~ msgid "" +#~ "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>\n" +#~ "[servers]\n" +#~ "0=Terminal -indirect appserver\n" +#~ " </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 serveral 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." +#~ msgstr "" +#~ "chooser XDMCP<filename></filename><screen>\n" +#~ "</screen><filename> Hosts</filename> entry<filename></filename> XDMCP " +#~ "chooser." -#: ../C/gdm.xml:6043 (title) #, fuzzy -msgid "License" -msgstr "Licencia" +#~ msgid "License" +#~ msgstr "Licencia" -#: ../C/gdm.xml:6044 (para) #, fuzzy -msgid "" -"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." -msgstr "<ulink type=\"help\" url=\"gnome-help:gpl\"><citetitle> Licencia</citetitle></ulink> Licencia." +#~ msgid "" +#~ "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." +#~ msgstr "" +#~ "<ulink type=\"help\" url=\"gnome-help:gpl\"><citetitle> Licencia</" +#~ "citetitle></ulink> Licencia." -#: ../C/gdm.xml:6052 (para) #, fuzzy -msgid "" -"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." -msgstr "<citetitle> Licencia</citetitle>." +#~ msgid "" +#~ "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." +#~ msgstr "<citetitle> Licencia</citetitle>." -#: ../C/gdm.xml:6058 (para) #, fuzzy -msgid "" -"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>" -msgstr "<citetitle> Licencia</citetitle><citetitle></citetitle><citetitle> Licencia</citetitle><ulink type=\"http\" url=\"http://www.fsf.org\"></ulink><address><street></street><city></city><state></state><postcode></postcode><country></country></address>" - -#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2. -#: ../C/gdm.xml:0 (None) -msgid "translator-credits" -msgstr "Francisco Javier F. Serrador <serrador@cvs.gnome.org>, 2003, 2005." +#~ msgid "" +#~ "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>" +#~ msgstr "" +#~ "<citetitle> Licencia</citetitle><citetitle></citetitle><citetitle> " +#~ "Licencia</citetitle><ulink type=\"http\" url=\"http://www.fsf.org\"></" +#~ "ulink><address><street></street><city></city><state></state><postcode></" +#~ "postcode><country></country></address>" #~ msgid "" #~ "Chooser - The host chooser which appears on remote displays sending " @@ -7859,4 +7248,3 @@ msgstr "Francisco Javier F. Serrador <serrador@cvs.gnome.org>, 2003, 2005." #~ msgid "BackgroundColor=#007777" #~ msgstr "BackgroundColor=#007777" - diff --git a/docs/es/gdm.xml b/docs/es/gdm.xml index 56f4351a..0ca26330 100644 --- a/docs/es/gdm.xml +++ b/docs/es/gdm.xml @@ -102,7 +102,7 @@ <para>GDM es un reemplazo de XDM, el gestor de pantallas de X, a diferencia de sus competidores, (X3DM, KDM, WDM), GDM se escribió desde cero y no contiene nada de código de XDM /X Consortium.</para> - <para>Para más información acerca de GDM, vea <ulink type="http" url="http://www.gnome.org/projects/gdm/"> el sitio web del proyecto GDM</ulink>.</para> + <para>For further information about GDM, see the <ulink type="http" url="http://www.gnome.org/projects/gdm/"> the GDM project website</ulink>. Please submit any bug reports or enhancement requests to the "gdm" category in <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink>.</para> </sect2> <sect2 id="daemonov"> @@ -220,3035 +220,5 @@ <para>Finalmente, el administrador del sistema puede especificar el tamaño máximo del archivo que GDM debería aceptar y, en el caso de que el visor de rostros esté activado, se fuerza un tamaño máximo del icono. En sistemas grandes se avisa además que desactive el visor de rostros por razones de rendimiento. Mirar iconos en directorios personales, escalarlos y renderizarlos puede llevar mucho tiempo.</para> </sect2> - </sect1> - - <sect1 id="Security"> - <title>Seguridad</title> - - <sect2 id="gdmuser"> - <title>El usuario GDM</title> - - <para>The GDM daemon normally runs as root, as does the slave. However GDM should also have a dedicated user id and a group id which it uses for its graphical interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</command>. You can choose the name of this user and group in the <filename>[daemon]</filename> section of the configuration file.</para> - - <para>El usuario y el grupo GDM, que son normalmente <command>gdm</command> no deberían tener ningún privilegio. La razón para usarlos es tener el interfaz de usuario ejecutándose como un usuario sin privilegios para que en el improbable caso de que alguien encuentre una debilidad en el IGU, no puedan acceder como root a la computadora.</para> - - <para>It should however be noted that the GDM user and group have some privileges that make them somewhat dangerous. For one they have access to the X server authorization directory (the <filename>ServAuthDir</filename>), which contains all the X server authorization files and other private information. This means 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>.</para> - </sect2> - - <sect2 id="xauth"> - <title>Esquema de autenticación del servidor X</title> - - <para>The X server authorization directory (the <filename>ServAuthDir</filename>) is used for a host of random internal data in addition to the X server authorization files, and the naming is really a relic of history. GDM daemon enforces this directory to be owned by <filename>root.gdm</filename> with the permissions of 1770. This way, only root and the GDM group have write access to this directory, but the GDM group cannot remove the root owned files from this directory, such as the X server authorization files.</para> - - <para>GDM by default doesn't trust the X server authorization directory and treats it in the same way as the temporary directory with respect to creating files. This way someone breaking the GDM user cannot mount attacks by creating links in this directory. Similarly the X server log directory is treated safely, but that directory should really be owned and writable only by root.</para> - - <para>GDM only supports the MIT-MAGIC-COOKIE-1 X server authentication scheme. Normally little is gained from the other schemes, and no effort has been made to implement them so far. Be especially careful about using XDMCP because the X server authentication cookie goes over the wire as clear text. If snooping is possible, then an attacker could simply snoop your authentication password as you log in, regardless of the authentication scheme being used. If snooping is possible and undesirable, then you should use ssh for tunneling an X connection rather then using XDMCP. You could think of XDMCP as a sort of graphical telnet, having the same security issues.</para> - - <para>On the upside, GDM's random number generation is very conservative and GDM goes to extraordinary measures to truly get a 128 bit random number, using hardware random number generators (if available), plus the current time (in microsecond precision), a 20 byte array of pseudorandom numbers, process pid's, and other random information (possibly using <filename>/dev/audio</filename> or <filename>/dev/mem</filename> if hardware random generators are not available) to create a large buffer and then run MD5 digest on this. Obviously, all this work is wasted if you send this cookie over an open network or store it on an NFS directory (see <filename>UserAuthDir</filename> configuration key). So be careful about where you use remote X display.</para> - </sect2> - - <sect2 id="firewall"> - <title>Seguridad con cortafuegos</title> - - <para>Even though GDM tries to outsmart potential attackers trying to take advantage of XDMCP, it is still advised that you block the XDMCP port (normally UDP port 177) on your firewall unless you really need it. GDM guards against DoS (Denial of Service) attacks, but the X protocol is still inherently insecure and should only be used in controlled environments. Also each remote connection takes up lots of resources, so it is much easier to DoS via XDMCP then a webserver.</para> - - <para>It is also wise to block all of the X Server ports. These are TCP ports 6000 + the display number of course) on your firewall. Note that GDM will use display numbers 20 and higher for flexible on-demand servers.</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"> - <title>Seguridad de GDM con NFS</title> - - <para>Note that NFS traffic really goes "over the wire" and thus can be snooped. When accessing the user's X authorization file (~/.Xauthority), GDM will try to open the file for reading as root. If it fails, GDM will conclude that it is on an NFS mount and it will automatically use <filename>UserAuthFBDir</filename>, which by default is set to <filename>/tmp</filename>. This behavior can be changed by setting the <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false.</para> - </sect2> - - <sect2 id="xdmcpsecurity"> - <title>Seguridad de XDMCP</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>XDMCP is primarily useful for running thin clients such as in terminal labs. Those thin clients will only ever need the network to access the server, and so it seems like the best security policy to have those thin clients on a separate network that cannot be accessed by the outside world, and can only connect to the server. The only point from which you need to access outside is the server.</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> - </sect2> - - <sect2 id="xdmcpaccess"> - <title>Control de acceso XDMCP</title> - - <para>El control de acceso XDMCP se realiza por medio de TCP wrappers. Es posible compilar GDM sin TCP wrappers sin embargo debería probar su configuración y verificar que funciona.</para> - - <para>Debería usar el nombre del demonio <command>gdm</command> en el archivo <filename><etc>/hosts.allow</filename> y en el archivo <filename><etc>hosts.deny</filename>. Por ejemplo para denegar la entrada a equipos de <filename>.evil.domain</filename> , añada</para> - <screen>gdm: .dominio.maligno</screen> - <para>a <filename><etc>/hosts.deny</filename>. También necesitará añadir </para> - <screen>gdm: .su.dominio</screen> - <para>a su <filename><etc>/hosts.allow</filename> si normalmente no permite todos los servicios desde todos los equipos. Vea la página del manual <ulink type="help" url="man:hosts.allow">hosts.allow(5)</ulink> para más detalles.</para> - </sect2> - </sect1> - - <sect1 id="configuration"> - <title>Configuración</title> - - <para>Esta sección cubrirá la configuración de GDM y el formato de los archivos de configuración de GDM. Puede usar el comando <command>gdmsetup</command> para configurar GDM, pero la aplicación de configuración no le deja configurar cada aspecto de GDM. La información de esta sección le explica en profundidad cómo configurar GDM.</para> - - <para>Los archivos de configuración (especialmente <filename>gdm.conf</filename> y <filename>gdm.conf-custom</filename>) contienen comentarios útiles y ejemplos, así que léalos para más información acerca de cambiar su configuración.</para> - - <para>Algunas claves en el archivo de configuración se entregan comentadas mientras que otras están activadas. Esto se hace para que los predeterminados para algunas claves puedan cambiarse fácilmente en el futuro. GDM considera que las líneas que comienzan con el carácter «#» un comentario, y estas líneas se ignorarán.</para> - - <para>EL archivo <filename>gdm.conf</filename> contiene las opciones de configuración predeterminadas para GDM, y no debería ser modificado por el usuario. El archivo <filename>gdm.conf-custom</filename> es donde los usuarios pueden especificar sus opciones de configuración personalizadas. Las opciones de configuración especificadas en el archivo <filename>gdm.conf-custom</filename> toman precedencia sobre los valores en el archivo principal <filename>gdm.conf</filename>. Ejecutar el comando <command>gdmsetup</command> hará que el archivo <filename>gdm.conf-custom</filename> se modifique con las opciones de configuración del usuario y hará que cualquier programa del IGU de GDM se actualice automáticamente. Anteriormente a la versión 2.13.0.4 GDM sólo soportaba el archivo <filename>gdm.conf</filename>, así que si está usando una versión más antigua de GDM tan sólo edite ese archivo directamente.</para> - - <para>GDM puede configurarse para soportar configuración para todo el sistema si se compila con la opción <command>--with-configdir</command>. Esto permite instalar el archivo gdm.conf en un directorio que pueda montarse a través de múltiples sistemas. La opción --config también podría usarse para especificar la ubicación del archivo de configuración. El demonio GDM2 debe reiniciarse para cambiar el archivo de configuración en uso.</para> - - <para><filename>factory-gdm.conf</filename> es el archivo de configuración tal como se empaqueta con el demonio. Esto puede ser útil si desea volver a la configuración predeterminada.</para> - - <para>Los demás archivos de configuración de GDM se encuentran, por omisión, en la carpeta <filename><etc>/gdm/</filename> o sus subdirectorios. sin embargo, la ubicación de todos los archivos de configuración pueden definirse en el archivo <filename>gdm.conf</filename>, así que el administrador del sistema puede elegir situar estos archivos en cualquier lugar.</para> - - <para>Esta es una lista de los contenidos del directorio de configuración:</para> - - <screen> -locale.alias -Xsession -XKeepsCrashing -modules/ -Init/ -PostLogin/ -PreSession/ -PostSession/ - </screen> - - <para><filename>locale.alias</filename> es un archivo que se parece mucho al archivo de alias regionales del sistema pero no es el mismo. Éstos son los idiomas que están disponibles en su sitema. Todos los idiomas además se prueban para ver si actualmente existen antes de presentárselos al usuario.</para> - - <para><filename>Xsession</filename> es un script que configura una sesión de usuario y después ejecuta la selección de sesión del usuario. Note que el script de sesión se inicia típicamente por el archivo <filename>desktop</filename> asociado con la sesión que el usuario a escogido. Algunas sesiones quizá inicien la sesión del usuario por medio de un mecanismo diferente que el script <filename>Xsession</filename> así que marque el <filename>desktop</filename> apropiado antes de asumir que el problema de inicio está causado por este archivo.</para> - - <para><filename>XKeepsCrashing</filename> es un script que se ejecuta cuando el servidor X continúa colgándose y no se puede recuperar. El script predeterminado incluido funcionará con la mayoría de las distribuciones de Linux y puede ejecutar la aplicación de configuración de X siempre que la persona en la consola conozca la contraseña de root.</para> - - <para>Accessibility modules are configured in the <filename>modules/</filename> subdirectory, and are a separate topic. Read the default files provided, they have adequate documentation. Again normally the default install is given in the files with <filename>factory</filename> in their name, and those files are not read, they are just there for you so you can always revert to default config.</para> - - <para>Files describing available GDM session follow the freedesktop.org desktop file specification and are <filename>.desktop</filename>-style files are installed to <filename><etc>/X11/sessions/</filename>. This directory is also read by the KDE desktop manager (KDM) for common configuration. Next the directory <filename><share>/gdm/BuiltInSessions/</filename> is read for GDM specific built-in sessions (KDM hardcodes these at time of this writing). Lastly the default setup will also read <filename><share>/xsessions/</filename> (which should be <filename>/usr/share/xsessions/</filename> if you really wish to cooperate with KDM) where desktop packages can install their session files. The directories under the <filename><etc></filename> should be reserved for configuration. The desktop file specification approach makes it easy for package management systems to install window managers and different session types without requiring the sysadmin to edit files. See the <filename>SessionDesktopDir</filename> configuration key for changing the paths. It used to be that GDM stored its built in sessions in <filename><etc>/dm/Sessions/</filename> but this is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the <filename><etc>/dm/Sessions/</filename> was being read.</para> - - <para>A session can be disabled (if it was installed in <filename>/usr/share/xsessions/</filename>) by adding an identically named <filename>.desktop</filename> to one of the directories earlier in the path (likely <filename><etc>/X11/sessions</filename>) and using <filename>Hidden=true</filename> in that file.</para> - - <sect2 id="scriptdirs"> - <title>Los directorios de scripts</title> - - <para>En esta sección explicaremos los directorios <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> y <filename>PostSession</filename> ya que son muy similares.</para> - - <para>When the X server has been successfully started, GDM will try to run the script called <filename>Init/<displayname></filename>. I.e. <filename>Init/:0</filename> for the first local display. If this file is not found, GDM will attempt to to run <filename>Init/<hostname></filename>. I.e. <filename>Init/somehost</filename>. If this still is not found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins or <filename>Init/Flexi</filename> for all on demand flexible displays. If none of the above were found, GDM will run <filename>Init/Default</filename>. The script will be run as root and GDM blocks until it terminates. Use the <filename>Init/*</filename> script for applications that are supposed to run alongside with the GDM login window. xconsole for instance. Commands to set the background etc. goes in this file too.</para> - - <para>It is up to the sysadmin to decide whether clients started by the Init script should be killed before starting the user session. This is controlled with the <filename>KillInitClients</filename> configuration option.</para> - - <para>When the user has been successfully authenticated GDM tries the scripts in the <filename>PostLogin</filename> directory in the same manner as for the <filename>Init</filename> directory. This is done before any session setup is done, and so this would be the script where you might setup the home directory if you need to (though you should use the <filename>pam_mount</filename> module if you can for this). You have the <filename>$USER</filename> and <filename>$DISPLAY</filename> environment variables set for this script, and again it is run as root. The script should return 0 on success as otherwise the user won't be logged in. This is not true for failsafe session however.</para> - - <para>After the user session has been setup from the GDM side of things, GDM will run the scripts in the <filename>PreSession</filename> directory, again in the same manner as the <filename>Init</filename> directory. Use this script for local session management or accounting stuff. The <filename>$USER</filename> environment variable contains the login of the authenticated user and <filename>$DISPLAY</filename> is set to the current display. The script should return 0 on success. Any other value will cause GDM to terminate the current login process. This is not true for failsafe sessions however. Also <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application.</para> - - <para>After this the base <filename>Xsession</filename> script is run with the selected session executable as the first argument. This is run as the user, and really this is the user session. The available session executables are taken from the <filename>Exec=</filename> line in the <filename>.desktop</filename> files in the path specified by <filename>SessionDesktopDir</filename>. Usually this path is <filename><etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/xsessions/</filename>. The first found file is used. The user either picks from these sessions or GDM will look inside the file <filename>~/.dmrc</filename> for the stored preference.</para> - - <para>This script should really load the users profile and generally do all the voodoo that is needed to launch a session. Since many systems reset the language selections done by GDM, GDM will also set the <filename>$GDM_LANG</filename> variable to the selected language. You can use this to reset the language environmental variables after you run the users profile. If the user elected to use the system language, then <filename>$GDM_LANG</filename> is not set.</para> - - <para>When the user terminates his session, the <filename>PostSession</filename> script will be run. Again operation is similar to <filename>Init</filename>, <filename>PostLogin</filename> and <filename>PreSession</filename>. Again the script will be run with root privileges, the slave daemon will block and the <filename>$USER</filename> environment variable will contain the name of the user who just logged out and <filename>$DISPLAY</filename> will be set to the display the user used, however note that the X server for this display may already be dead and so you shouldn't try to access it. Also <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application.</para> - - <para>Note that the <filename>PostSession</filename> script will be run even when the display fails to respond due to an I/O error or similar. Thus, there is no guarantee that X applications will work during script execution.</para> - - <para>Except for the <filename>Xsession</filename> script all of these scripts will also have the environment variable <filename>$RUNNING_UNDER_GDM</filename> set to <filename>yes</filename>, so that you could perhaps use similar scripts for different display managers. The <filename>Xsession</filename> will always have the <filename>$GDMSESSION</filename> set to the basename of the session that the user chose to run without the <filename>.desktop</filename> extension. In addition <filename>$DESKTOP_SESSION</filename> is also set to the same value and in fact this will also be set by KDM in future versions.</para> - - <para>Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> or <filename>PostSession</filename> scripts are necessary and can be left out. The <filename>Xsession</filename> script is however required as well as at least one session <filename>.desktop</filename> file.</para> - - </sect2> - - <sect2 id="configfile"> - <title>The Configuration File - <filename>gdm.conf</filename> and <filename>gdm.conf-custom</filename></title> - - <para>GDM uses two configuration files: <filename>gdm.conf</filename> and <filename>gdm.conf-custom</filename>. The <filename>gdm.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename>gdm.conf-custom</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename>gdm.conf-custom</filename> file override the values in the main <filename>gdm.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>gdm.conf</filename> file.</para> - - <para>Running the <command>gdmsetup</command> command will cause the <filename>gdm.conf-custom</filename> to be modified with the user's configuration choices.</para> - - <para>Previous to GDM 2.13.0.4 only the <filename>gdm.conf</filename> existed. If upgrading to the new version of GDM, install will check to see if your <filename>gdm.conf</filename> file is different than your <filename>factory-gdm.conf</filename> file. If so, your <filename>gdm.conf</filename> file will be automatically copied to <filename>gdm.conf-custom</filename> to preserve your configuration changes.</para> - - <para>GDM may be configured to support system-wide configuration if built with the <command>--with-configdir</command> option. This allows the <filename>gdm.conf</filename> file to be installed to a directory that can be mounted across multiple-systems. The GDM --config option may instead be used to specify a configuration file installed to another location. The GDM2 daemon must be restarted to change the configuration file being used.</para> - - <para>Both configuration files are divided into sections each containing variables that define the behavior for a specific part of the GDM suite. Refer to the comments in the <filename>gdm.conf</filename> file for additional information about each configuration setting.</para> - - <para>The <filename>gdm.conf</filename> and <filename>gdm.conf-custom</filename> files follow the standard <filename>.ini</filename> style configuration file syntax. Keywords in brackets define sections, strings before an equal sign (=) are variables and the data after equal sign represents their value. Empty lines or lines starting with the hash mark (#) are ignored. The graphical configurator will try to preserve both comments (lines with a hash mark) and the overall structure of the file so you can intermix using the GUI or hand editing the configuration file.</para> - - <sect3 id="daemonsection"> - <title>Configuración del demonio</title> - - <variablelist> - <title>[daemon]</title> - - <varlistentry> - <term>AddGtkModules</term> - <listitem> - <synopsis>AddGtkModules=false</synopsis> - <para>Si es true, entonces activa <command>gdmgreeter</command> o <command>gdmlogin</command> para que se lancen con módulos GTK+ adicionales. esto es útil cuando se requieren características extra como un inicio sesión accesible. Note que sólo deberían usarse los módulos «confiables» para minimizar las cuestiones de seguridad.</para> - <para>Usualmente esto se usa para los módulos de accesibilidad. Los módulos que se cargan se especifican con la clave <filename>GtkModulesList</filename>.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AlwaysRestartServer</term> - <listitem> - <synopsis>AlwaysRestartServer=false</synopsis> - <para>If true, then gdm never tries to reuse existing X servers by reinitializing them. It will just kill the existing X server and start over. Normally, just reinitializing is a nicer way to go but if the X server memory usage keeps growing this may be a safer option. On Solaris, this value is always true, and this configuration setting is ignored.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AutomaticLoginEnable</term> - <listitem> - <synopsis>AutomaticLoginEnable=false</synopsis> - <para>If the user given in AutomaticLogin should be logged in upon first bootup. No password will be asked. This is useful for single user workstations where local console security is not an issue. Also could be useful for public terminals, although there see <filename>TimedLogin</filename>.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AutomaticLogin</term> - <listitem> - <synopsis>AutomaticLogin=</synopsis> - <para>This user should be automatically logged in on first bootup. AutomaticLoginEnable must be true and this must be a valid user for this to happen. "root" can never be autologged in however and gdm will just refuse to do it even if you set it up.</para> - - <para>Los siguientes caracteres de control se reconocen dentro del nombre especificado:</para> - - <para>the `' character</para> - - <para>d nombre del display</para> - - <para>h nombre de host del display</para> - - <para>Alternatively, the name may end with a vertical bar |, the pipe symbol. The name is then used as a application to execute which returns the desired username on standard output. If an empty or otherwise invalid username is returned, automatic login is not performed. This feature is typically used when several remote displays are used as internet kiosks, with a specific user to automatically login for each display.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>Chooser</term> - <listitem> - <synopsis>Chooser=<bin>/gdmchooser</synopsis> - <para>Ruta completa y nombre del ejecutable del selector seguido de archumentos opcionales.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultPath</term> - <listitem> - <synopsis>DefaultPath=/bin:/usr/bin:/usr/bin/X11:/usr/local/bin</synopsis> - <para>Specifies the path which will be set in the user's session. This value will be overridden with the value from /etc/default/login if it contains "ROOT=<pathname>". If the /etc/default/login file exists, but contains no value for ROOT, the value as defined in the GDM configuration will be be used.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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 behaviour set this value to 0. This was added in version 2.5.90.0.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>HaltCommand</term> - <listitem> - <synopsis>HaltCommand=/sbin/shutdown -h now</synopsis> - <para>Full path and arguments to command to be executed when user selects Shutdown from the Actions menu. This can be a ';' separated list of commands to try. If a value is missing, the shutdown command is not available. Note that the default for this value is not empty so to disable shutdown you must set this explicitly to an empty value.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>PidFile</term> - <listitem> - <synopsis>PidFile=<var>/run/gdm.pid</synopsis> - <para>Name of the file containing the <filename>gdm</filename> process id.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>RootPath</term> - <listitem> - <synopsis>RootPath=/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/local/bin</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 /etc/default/login if it contains "SUROOT=<pathname>". If the /etc/default/login file exists, but contains no value for SUROOT, the value as defined in the GDM configuration will be used.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>SessionDesktopDir</term> - <listitem> - <synopsis>SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:</usr/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> - </listitem> - </varlistentry> - - <varlistentry> - <term>SoundProgram</term> - <listitem> - <synopsis>SoundProgram=/usr/bin/play</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> - </listitem> - </varlistentry> - - <varlistentry> - <term>StandardXServer</term> - <listitem> - <synopsis>StandardXServer=/usr/X11R6/bin/X</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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>TimedLoginDelay</term> - <listitem> - <synopsis>TimedLoginDelay=30</synopsis> - <para>Este es el retardo antes de que el usuario <filename> TimedLogin</filename> entre en la sesión. Debe ser mayor o igual a 10.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>UserAuthFile</term> - <listitem> - <synopsis>UserAuthFile=.Xauthority</synopsis> - <para>Name of the file used for storing user cookies.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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>En caso de que esté configurado <filename> FailsafeXServer</filename>, ése se intentará primero, y este sólo se usará como un respaldo en el caso de que el servidor X se mantenga colgado.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Xnest</term> - <listitem> - <synopsis>Xnest=/usr/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> - </listitem> - </varlistentry> - </variablelist> - - </sect3> - - <sect3 id="securitysection"> - <title>Opciones de seguridad</title> - - <variablelist> - <title>[security]</title> - - <varlistentry> - <term>AllowRoot</term> - <listitem> - <synopsis>AllowRoot=true</synopsis> - <para>Permite al usuario root (usuario privilegiado) entrar a través de GDM. Establezca esta opción a false si quiere no permitir dichas entradas.</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> - - <varlistentry> - <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 /etc/default/login file exists and contains "CONSOLE=/dev/login", and set to true if the /etc/default/login file exists and contains any other value or no value for CONSOLE.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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 /etc/default/login if it contains "PASSREQ=[YES|NO]". If the /etc/default/login file exists, but contains no value for PASSREQ, the value as defined in the GDM configuration will be used.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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>Cambiar el valor de RelaxPermissions hace posible alterar este comportamiento:</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> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>UserMaxFile</term> - <listitem> - <synopsis>UserMaxFile=65536</synopsis> - <para>GDM rechazará a leer/escribir archivos mayores que este número (especificado en 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> - </listitem> - </varlistentry> - </variablelist> - - </sect3> - - <sect3 id="xdmcpsection"> - <title>Soporte XDCMP</title> - - <variablelist> - <title>[xdmcp]</title> - - <varlistentry> - <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>Note that the number of connections from the local computer is unlimited. Only remote connections are limited by this number.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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><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>You should add <screen>gdm:.my.domain</screen> to your <filename><etc>/hosts.allow</filename>, depending on your TCP Wrappers configuration. See the <ulink type="help" url="man:hosts.allow">hosts.allow(5)</ulink> man page for details.</para> - - <para>Note que XDMCP no es un protocolo particularmente seguro y que es una buena idea bloquear el puerto UDP 177 en su cortafuegos a no ser que realmente lo necesite.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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>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> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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>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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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>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> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - </variablelist> - - </sect3> - - <sect3 id="commonguioptions"> - <title>Common GUI Configuration Options</title> - - <variablelist> - <title>[gui]</title> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - </variablelist> - - </sect3> - - <sect3 id="greetersection"> - - <title>Configuración del interfaz</title> - - <variablelist> - <title>[greeter]</title> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundProgramInitialDelay</term> - <listitem> - <synopsis>BackgroundProgramInitialDelay=30</synopsis> - <para>The background application will be started after at least that many seconds of inactivity.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundProgramRestartDelay</term> - <listitem> - <synopsis>BackgroundProgramRestartDelay=30</synopsis> - <para>The background application will be restarted after at least that many seconds of inactivity.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundProgram</term> - <listitem> - <synopsis>BackgroundProgram=/usr/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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundScaleToFit</term> - <listitem> - <synopsis>BackgroundScaleToFit=true</synopsis> - <para>Scale background image to fit the screen. This only affects the GTK+ Greeter.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundType</term> - <listitem> - <synopsis>BackgroundType=2</synopsis> - <para>El tipo de fondo a establecer. 0 es ninguno, 1 es imagen y color, 2 es color y 3 es imagen. Esto sólo afecta al interfaz GTK+.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultFace</term> - <listitem> - <synopsis>DefaultFace=<share>/pixmaps/nophoto.png</synopsis> - <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, the image specified by <filename>DefaultFace</filename> will be used. The image must be in an gdk-pixbuf supported format and the file must be readable to the GDM user.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Include</term> - <listitem> - <synopsis>Include=</synopsis> - <para>Comma separated list of users to be included in the face browser and in the <command>gdmsetup</command> selection list for Automatic/Timed login. See also <filename>Exclude</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Exclude</term> - <listitem> - <synopsis>Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,...</synopsis> - <para>Comma separated list of users to be excluded from the face browser and from the <command>gdmsetup</command> selection list for Automatic/Timed login. Excluded users will still be able to log in, but will have to type their username. See also <filename>Include</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>IncludeAll</term> - <listitem> - <synopsis>IncludeAll=false</synopsis> - <para>By default, an empty include list means display no users. By setting IncludeAll to true, the password file will be scanned and all users will be displayed aside from users excluded via the Exclude setting and user ID's less than MinimalUID. Scanning the password file can be slow on systems with large numbers of users and this feature should not be used in such environments. See also <filename>Include</filename>, <filename>Exclude</filename>, and <filename>MinimalUID</filename>.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GlobalFaceDir</term> - <listitem> - <synopsis>GlobalFaceDir=<share>/pixmaps/faces/</synopsis> - <para>Systemwide directory for face files. The sysadmin can place icons for users here without touching their homedirs. Faces are named after their users' logins.</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>The face images must be stored in gdk-pixbuf supported formats and they must be readable for the GDM user.</para> - - <para>A user's own icon file will always take precedence over the sysadmin provided one.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>GraphicalThemes</term> - <listitem> - <synopsis>GraphicalThemes=circles</synopsis> - <para>The graphical themes that the Themed Greeter should use is the Mode is set on Random Themes. This is a "/:" delimited list. It should refer to a directory in the theme directory set by <filename>GraphicalThemeDir</filename>. This is only used if <filename>GraphicalThemeRand</filename> is set to true.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>GraphicalThemeDir</term> - <listitem> - <synopsis>GraphicalThemeDir=<share>/gdm/themes/</synopsis> - <para>The directory where themes for the Themed Greeter are installed.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>LockPosition</term> - <listitem> - <synopsis>LockPosition=true</synopsis> - <para>If true the position of the login window of the GTK+ Greeter cannot be changed even if the title bar is turned on.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>PositionX</term> - <listitem> - <synopsis>PositionX=200</synopsis> - <para>The horizontal position of the login window of the GTK+ Greeter.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PositionY</term> - <listitem> - <synopsis>PositionY=100</synopsis> - <para>The vertical position of the login window of the GTK+ Greeter.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultRemoteWelcome</term> - <listitem> - <synopsis>DefaultRemoteWelcome=true</synopsis> - <para>If set to true, the value "Welcome to %n" is used for the <filename>RemoteWelcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>RemoteWelcome</filename> setting is used. This string can use the same special character sequences as explained in the "Text Node" section of the "Themed Greeter" chapter. This explains the meaning of "%n".</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RemoteWelcome</term> - <listitem> - <synopsis>RemoteWelcome=Welcome to n</synopsis> - <para>Controls which text to display next to the logo image in the greeter for remote XDMCP sessions. The same expansion is done here as in the <filename>Welcome</filename> string. This string can use the same special character sequences as explained in the "Text Node" section of the "Themed Greeter" chapter. chapter.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>ShowGnomeFailsafeSession</term> - <listitem> - <synopsis>ShowGnomeFailsafeSession=true</synopsis> - <para>Should the greeter show the Gnome Failsafe session in th sessions list.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>ShowXtermFailsafeSession</term> - <listitem> - <synopsis>ShowXtermFailsafeSession=true</synopsis> - <para>Should the greeter show the Xterm Failsafe session in the sessions list.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>TitleBar</term> - <listitem> - <synopsis>TitleBar=true</synopsis> - <para>Display the title bar in the greeter. This only affects the GTK+ Greeter.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultWelcome</term> - <listitem> - <synopsis>DefaultWelcome=true</synopsis> - <para>If set to true, the value "Welcome" is used for the <filename>Welcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>Welcome</filename> setting is used.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Welcome</term> - <listitem> - <synopsis>Welcome=Welcome</synopsis> - <para>Controls which text to display next to the logo image in the standard greeter. The following control chars are supported:</para> - - <para>the `' character</para> - - <para>d display's hostname</para> - - <para>h Fully qualified hostname</para> - - <para>m machine (processor type)</para> - - <para>n Nodename (i.e. hostname without .domain)</para> - - <para>r release (OS version)</para> - - <para>s sysname (i.e. OS)</para> - - <para>This string is only used for local logins. For remote XDMCP logins we use <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> - - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - </variablelist> - - </sect3> - - <sect3 id="choosersection"> - - <title>XDCMP Chooser Options</title> - - <variablelist> - <title>[chooser]</title> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>MulticastAddr</term> - <listitem> - <synopsis>MulticastAddr=ff02::1</synopsis> - <para>This is the Link-local Multicast address and is hardcoded here.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultHostImage</term> - <listitem> - <synopsis>DefaultHostImage=<share>/pixmaps/nohost.png</synopsis> - <para>File name for the default host icon. This image will be displayed if no icon is specified for a given host. The file must be in an gdk-pixbuf supported format and it must be readable for the GDM user.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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>The file name must match the fully qualified name (FQDN) for the host. The icons must be stored in gdk-pixbuf supported formats and they must be readable to the GDM user.</para> - - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - </variablelist> - - </sect3> - - <sect3 id="debugsection"> - - <title>Configuración de depuración</title> - - <variablelist> - <title>[debug]</title> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>Gestures</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> - </listitem> - </varlistentry> - </variablelist> - - </sect3> - - <sect3 id="serverdefs"> - - <title>X Server Definitions</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>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>gdm.conf-custom</filename> file override values in the <filename>gdm.conf</filename> file. In other words, if a <filename>server-Standard</filename> section is defined in <filename>gdm.conf-custom</filename>, then that will be used and the section in the <filename>gdm.conf</filename> file will be ignored.</para> - - <variablelist> - <title>[server-Standard]</title> - - <varlistentry> - <term>name</term> - <listitem> - <synopsis>name=Standard server</synopsis> - <para>The name that will be displayed to the user.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>command</term> - <listitem> - <synopsis>command=/usr/bin/X11/X</synopsis> - <para>The command to execute, with full path to the binary of the X server, and any extra arguments needed.</para> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - </variablelist> - - </sect3> - - <sect3 id="localservers"> - - <title>Local Static X Display Configuration</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 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>gdm.conf-custom</filename> file overrides values in the <filename>gdm.conf</filename> file.</para> - - <variablelist> - <title>[servers]</title> - - <varlistentry> - <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>gdm.conf-custom</filename> to turn off a display that is defined in the <filename>gdm.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> - </listitem> - </varlistentry> - - <varlistentry> - <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> - </listitem> - </varlistentry> - </variablelist> - </sect3> - </sect2> - - <sect2 id="userconfig"> - <title>Per User Configuration</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> - - <screen> -[Desktop] -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 $HOME/.face 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> - - <sect1 id="controlling"> - <title>Controlling GDM</title> - - <para>You can control GDM behavior during runtime in several different ways. You can either run certain commands, or you can talk to GDM using either a unix socket protocol, or a FIFO protocol.</para> - - <sect2 id="commands"> - <title>Comandos</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> - </sect2> - - <sect2 id="fifoprot"> - <title>The FIFO protocol</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> - </sect2> - - <sect2 id="socketprot"> - <title>Socket Protocol</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> - - <screen> -VERSION -AUTH_LOCAL -FLEXI_XSERVER -FLEXI_XNEST -ATTACHED_SERVERS -ALL_SERVERS -GET_SERVER_LIST -GET_SERVER_DETAILS -GET_CONFIG -GET_CONFIG_FILE -UPDATE_CONFIG -GREETERPIDS -QUERY_LOGOUT_ACTION -SET_LOGOUT_ACTION -SET_SAFE_LOGOUT_ACTION -QUERY_VT -SET_VT -CLOSE - </screen> - - <para>These are described in detail below, including required arguments, response format, and return codes.</para> - - <sect3 id="queryversion"> - <title>VERSION</title> - <screen> -VERSION: Query GDM version -Supported since: 2.2.4.0 -Arguments: None -Answers: - GDM <gdm version> - ERROR <err number> <english error description> - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="authlocal"> - <title>AUTH_LOCAL</title> - <screen> -AUTH_LOCAL: Setup this connection as authenticated for - FLEXI_SERVER. Because all full blown (non-Xnest) - displays can be started only from users logged in - locally, and here GDM assumes only users logged - in from GDM. They must pass the xauth - MIT-MAGIC-COOKIE-1 that they were passed before - the connection is authenticated. -Note: The AUTH LOCAL command requires the - --authenticate option, although only - FLEXI XSERVER uses this currently. -Note: Since 2.6.0.6 you can also use a global - <ServAuthDir>/.cookie, which works for all - authentication except for SET_LOGOUT_ACTION and - QUERY_LOGOUT_ACTION and SET_SAFE_LOGOUT_ACTION - which require a logged in display. -Supported since: 2.2.4.0 -Arguments: <xauth cookie> - <xauth cookie> is in hex form with no 0x prefix -Answers: - OK - ERROR <err number> <english error description> - 0 = Not implemented - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="flexixserver"> - <title>FLEXI_XSERVER</title> - <screen> -FLEXI_XSERVER: Start a new X flexible display. Only supported on - connection that passed AUTH_LOCAL -Supported since: 2.2.4.0 -Arguments: <xserver type> - If no arguments, starts the standard X server -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = No more flexi servers - 2 = Startup errors - 3 = X failed - 4 = X too busy - 6 = No server binary - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="flexixnest"> - <title>FLEXI_XNEST</title> - <screen> -FLEXI_XNEXT: Start a new flexible Xnest display. -Note: Supported on older version from 2.2.4.0, later - 2.2.4.2, but since 2.3.90.4 you must supply 4 - arguments or ERROR 100 will be returned. This - will start Xnest using the XAUTHORITY file - supplied and as the uid same as the owner of - that file (and same as you supply). You must - also supply the cookie as the third argument - for this display, to prove that you indeed are - this user. Also this file must be readable - ONLY by this user, that is have a mode of 0600. - If this all is not met, ERROR 100 is returned. -Note: The cookie should be the MIT-MAGIC-COOKIE-1, - the first one GDM can find in the XAUTHORITY - file for this display. If that's not what you - use you should generate one first. The cookie - should be in hex form. -Supported since: 2.3.90.4 -Arguments: <display to run on> <uid of requesting user> - <xauth cookie for the display> <xauth file> -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = No more flexi servers - 2 = Startup errors - 3 = X failed - 4 = X too busy - 5 = Xnest can't connect - 6 = No server binary - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="adddynamic"> - <title>ADD_DYNAMIC_DISPLAY</title> - <screen> -ADD_DYNAMIC_DISPLAY: Create a new server definition that will - run on the specified display leaving, it - in DISPLAY_CONFIG state. -Supported since: 2.8.0.0 -Arguments: <display to run on>=<server> - Where <server> is either a configuration named in the - GDM configuration or a literal command name. -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 2 = Existing display - 3 = No server string - 4 = Display startup failure - 100 = Not authenticated - 200 = Dynamic Displays not allowed - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="releasedynamic"> - <title>RELEASE_DYNAMIC_DISPLAYS</title> - <screen> -RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in - DISPLAY_CONFIG state -Supported since: 2.8.0.0 -Arguments: None -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 100 = Not authenticated - 200 = Dynamic Displays not allowed - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="removedynamic"> - <title>REMOVE_DYNAMIC_DISPLAY</title> - <screen> -REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server - and purging the display configuration -Supported since: 2.8.0.0 -Arguments: <display to remove> -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = Bad display number - 100 = Not authenticated - 200 = Dynamic Displays not allowed - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="attachedservers"> - <title>ATTACHED_SERVERS</title> - <screen> -ATTACHED_SERVERS: List all attached displays. Doesn't list XDMCP - and xnest non-attached displays. -Note: This command used to be named CONSOLE_SERVERS, - which is still recognized for backwards - compatibility. The optional pattern argument - is supported as of version 2.8.0.0. -Supported since: 2.2.4.0 -Arguments: <pattern> (optional) - With no argument, all attached displays are returned. The optional - <pattern> is a string that may contain glob characters '*', '?', and - '[]'. Only displays that match the pattern will be returned. -Answers: - OK <server>;<server>;... - - <server> is <display>,<logged in user>,<vt or xnest display> - - <logged in user> can be empty in case no one logged - in yet, and <vt> can be -1 if it's not known or not - supported (on non-Linux for example). If the display is an - xnest display and is a console one (that is, it is an xnest - inside another console display) it is listed and instead of - vt, it lists the parent display in standard form. - - ERROR <err number> <english error description> - 1 = Not implemented - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="allservers"> - <title>ALL_SERVERS</title> - <screen> -ALL_SERVERS: List all displays, including console, remote, xnest. - This can, for example, be useful to figure out if - the display you are on is managed by the gdm daemon, - by seeing if it is in the list. It is also somewhat - like the 'w' command but for graphical sessions. -Supported since: 2.4.2.96 -Arguments: None -Answers: - OK <server>;<server>;... - - <server> is <display>,<logged in user> - - <logged in user> can be empty in case no one logged in yet - - ERROR <err number> <english error description> - 0 = Not implemented - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="getserverlist"> - <title>GET_SERVER_LIST</title> - <screen> -GET_SERVER_LIST: Get a list of the server sections from - the configuration file. -Supported since: 2.13.0.4 -Arguments: None -Answers: - OK <value>;<value>;... - ERROR <err number> <english error description> - 0 = Not implemented - 1 = No servers found - 50 = Unsupported key - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="getserverdetails"> - <title>GET_SERVER_DETAILS</title> - <screen> -GET_SERVER_DETAILS: Get detail information for a specific server. -Supported since: 2.13.0.4 -Arguments: <server> <key> - Key values include: - NAME - Returns the server name - COMMAND - Returns the server command - FLEXIBLE - Returns "true" if flexible, "false" - otherwise - CHOOSABLE - Returns "true" if choosable, "false" - otherwise - HANDLED - Returns "true" if handled, "false" - otherwise - CHOOSER - Returns "true" if chooser, "false" - otherwise - PRIORITY - Returns process priority -Answers: - OK <value> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = Server not found - 2 = Key not valid - 50 = Unsupported key - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="getconfig"> - <title>GET_CONFIG</title> - <screen> -GET_CONFIG: Get configuration value for key. Useful so - that other applications can request configuration - information from GDM. Any key defined as GDM_KEY_* - in gdm.h is supported. Starting with version 2.13.0.2 - translated keys (such as "greeter/GdmWelcome[cs]" are - supported via GET_CONFIG. Also starting with version - 2.13.0.2 it is no longer necessary to include the - default value (i.e. you can use key "greeter/IncludeAll" - instead of having to use "greeter/IncludeAll=false". -Supported since: 2.6.0.9 -Arguments: <key> -Answers: - OK <value> - ERROR <err number> <english error description> - 0 = Not implemented - 50 = Unsupported key - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="getconfigfile"> - <title>GET_CONFIG_FILE</title> - <screen> -GET_CONFIG_FILE: Get config file location being used by - the daemon. If the GDM daemon was started - with the --config option, it will return - the value passed in via the argument. -Supported since: 2.8.0.2 -Arguments: None -Answers: - OK <full path to GDM configuration file> - ERROR <err number> <english error description> - 0 = Not implemented - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="updateconfig"> - <title>UPDATE_CONFIG</title> - <screen> -UPDATE_CONFIG: Tell the daemon to re-read a key from the - GDM configuration file. Any user can request - that values are re-read but the daemon will - only do so if the file has been modified - since GDM first read the file. Only users - who can change the GDM configuration file - (normally writable only by the root user) can - actually modify the GDM configuration. This - command is useful to cause the GDM to update - itself to recognize a change made to the GDM - configuration file by the root user. - - Starting with version 2.13.0.0, all GDM keys are - supported except for the following: - - daemon/PidFile - daemon/ConsoleNotify - daemon/User - daemon/Group - daemon/LogDir - daemon/ServAuthDir - daemon/UserAuthDir - daemon/UserAuthFile - daemon/UserAuthFBDir - - GDM also supports the following Psuedokeys: - - xdmcp/PARAMETERS (2.3.90.2) updates the following: - xdmcp/MaxPending - xdmcp/MaxSessions - xdmcp/MaxWait - xdmcp/DisplaysPerHost - xdmcp/HonorIndirect - xdmcp/MaxPendingIndirect - xdmcp/MaxWaitIndirect - xdmcp/PingIntervalSeconds (only affects new connections) - - xservers/PARAMETERS (2.13.0.4) updates the following: - all [server-foo] sections. - - Supported keys for previous versions of GDM: - - security/AllowRoot (2.3.90.2) - security/AllowRemoteRoot (2.3.90.2) - security/AllowRemoteAutoLogin (2.3.90.2) - security/RetryDelay (2.3.90.2) - security/DisallowTCP (2.4.2.0) - daemon/Greeter (2.3.90.2) - daemon/RemoteGreeter (2.3.90.2) - xdmcp/Enable (2.3.90.2) - xdmcp/Port (2.3.90.2) - daemon/TimedLogin (2.3.90.3) - daemon/TimedLoginEnable (2.3.90.3) - daemon/TimedLoginDelay (2.3.90.3) - greeter/SystemMenu (2.3.90.3) - greeter/ConfigAvailable (2.3.90.3) - greeter/ChooserButton (2.4.2.0) - greeter/SoundOnLoginFile (2.5.90.0) - daemon/AddGtkModules (2.5.90.0) - daemon/GtkModulesList (2.5.90.0) -Supported since: 2.3.90.2 -Arguments: <key> - <key> is just the base part of the key such as - "security/AllowRemoteRoot" -Answers: - OK - ERROR <err number> <english error description> - 0 = Not implemented - 50 = Unsupported key - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="greeterpids"> - <title>GREETERPIDS</title> - <screen> -GREETERPIDS: List all greeter pids so that one can send HUP - to them for config rereading. Of course one - must be root to do that. -Supported since: 2.3.90.2 -Arguments: None -Answers: - OK <pid>;<pid>;... - ERROR <err number> <english error description> - 0 = Not implemented - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="querylogoutaction"> - <title>QUERY_LOGOUT_ACTION</title> - <screen> -QUERY_LOGOUT_ACTION: Query which logout actions are possible - Only supported on connections that passed - AUTH_LOCAL. -Supported since: 2.5.90.0 -Answers: - OK <action>;<action>;... - Where action is one of HALT, REBOOT or SUSPEND. An - empty list can also be returned if no action is possible. - A '!' is appended to an action if it was already set with - SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION. Note that - SET_LOGOUT_ACTION has precedence over - SET_SAFE_LOGOUT_ACTION. - ERROR <err number> <english error description> - 0 = Not implemented - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="setlogoutaction"> - <title>SET_LOGOUT_ACTION</title> - <screen> -SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after - slave process exits. Only supported on - connections that passed AUTH_LOCAL. -Supported since: 2.5.90.0 -Arguments: <action> - NONE Set exit action to 'none' - HALT Set exit action to 'halt' - REBOOT Set exit action to 'reboot' - SUSPEND Set exit action to 'suspend' -Answers: - OK - ERROR <err number> <english error description> - 0 = Not implemented - 7 = Unknown logout action, or not available - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="setsafelogoutaction"> - <title>SET_SAFE_LOGOUT_ACTION</title> - <screen> -SET_SAFE_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend - after everybody logs out. If only one - person logs out, then this is obviously - the same as the SET_LOGOUT_ACTION. Note - that SET_LOGOUT_ACTION has precedence - over SET_SAFE_LOGOUT_ACTION if it is set - to something other then NONE. If no one - is logged in, then the action takes effect - effect immediately. Only supported on - connections that passed AUTH_LOCAL. -Supported since: 2.5.90.0 -Arguments: <action> - NONE Set exit action to 'none' - HALT Set exit action to 'halt' - REBOOT Set exit action to 'reboot' - SUSPEND Set exit action to 'suspend' -Answers: - OK - ERROR <err number> <english error description> - 0 = Not implemented - 7 = Unknown logout action, or not available - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="queryvt"> - <title>QUERY_VT</title> - <screen> -QUERY_VT: Ask the daemon about which VT we are currently on. - This is useful for logins which don't own - /dev/console but are still console logins. Only - supported on Linux currently, other places will - just get ERROR 8. This is also the way to query - if VT support is available in the daemon in the - first place. Only supported on connections that - passed AUTH_LOCAL. -Supported since: 2.5.90.0 -Arguments: None -Answers: - OK <vt number> - ERROR <err number> <english error description> - 0 = Not implemented - 8 = Virtual terminals not supported - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="setvt"> - <title>SET_VT</title> - <screen> -SET_VT: Change to the specified virtual terminal. - This is useful for logins which don't own /dev/console - but are still console logins. Only supported on Linux - currently, other places will just get ERROR 8. - Only supported on connections that passed AUTH_LOCAL. -Supported since: 2.5.90.0 -Arguments: <vt> -Answers: - OK - ERROR <err number> <english error description> - 0 = Not implemented - 8 = Virtual terminals not supported - 9 = Invalid virtual terminal number - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error - </screen> - </sect3> - - <sect3 id="close"> - <title>CLOSE</title> - <screen> -CLOSE: Close sockets connection -Supported since: 2.2.4.0 -Arguments: None -Answers: None - </screen> - </sect3> - </sect2> - </sect1> - - <!-- ============= GDM Commands ============================= --> - - <sect1 id="binaries"> - <title>GDM Commands</title> - - <sect2 id="bindir_binaries"> - <title>GDM User Commands</title> - - <para>The GDM package provides the following different commands in EXPANDED_BINDIR intended to be used by the end-user:</para> - - <sect3 id="gdmxnestchoosercommandline"> - <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> - - <variablelist> - <title><command>gdmXnestchooser</command> Command Line Options</title> - - <varlistentry> - <term>-x, --xnest=STRING</term> - <listitem> - <para>Xnest command line, default is "Xnest"</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-o, --xnest-extra-options=OPTIONS</term> - <listitem> - <para>Extra options for Xnest, default is no options.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-n, --no-query</term> - <listitem> - <para>Just run Xnest, no query (no chooser)</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-d, --direct</term> - <listitem> - <para>Do direct query instead of indirect (chooser)</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-B, --broadcast</term> - <listitem> - <para>Run broadcast instead of indirect (chooser)</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-b, --background</term> - <listitem> - <para>Run in background</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>--no-gdm-check</term> - <listitem> - <para>Don't check for running GDM</para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <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>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>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> - - <variablelist> - <title><command>gdmflexichooser</command> Command Line Options</title> - - <varlistentry> - <term>-c, --command=COMMAND</term> - <listitem> - <para>Enviar el comando de protocolo especificado a GDM</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-n, --xnest</term> - <listitem> - <para>Start a flexible X display in Xnest mode</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-l, --no-lock</term> - <listitem> - <para>No bloquear la pantalla actual</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-d, --debug</term> - <listitem> - <para>Activar salida de depuración para enviarla a syslog. Lo mismo que cuadno se activa la depuración en el archivo de configuración.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-a, --authenticate</term> - <listitem> - <para>Autenticar antes de ejecutar --command</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-s, --startnew</term> - <listitem> - <para>Starts a new flexible display without displaying a dialog asking the user if they wish to continue any existing sessions.</para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <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>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.</para> - - <variablelist> - <title>Opciones de línea de comandos de <command>gdmdynamic</command></title> - - <varlistentry> - <term/> - <listitem> - <para><emphasis>Una de las siguientes opciones pueden usarse por instancia:</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> - </listitem> - </varlistentry> - - <varlistentry> - <term>-r</term> - <listitem> - <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> - </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> - </listitem> - </varlistentry> - - <varlistentry> - <term/> - <listitem> - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>-b</term> - <listitem> - <para>Background mode. Fork child to do the work and return immediately.</para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <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 ~/.face. 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> -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> - </sect3> - </sect2> - - <sect2 id="sbindir_binaries"> - <title>GDM Root User Commands</title> - - <para>The GDM package provides the following different commands in EXPANDED_SBINDIR 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> - - <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> - - <varlistentry> - <term>--help</term> - <listitem> - <para>Gives a brief overview of the command line options.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-nodaemon</term> - <listitem> - <para>If this option is specified, then GDM does not fork into the background when run. You can use just a single dash with this option to preserve compatibility with XDM.</para> - </listitem> - </varlistentry> - - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>--config=CONFIGFILE</term> - <listitem> - <para>Specify an alternative configuration file.</para> - </listitem> - </varlistentry> - - <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> - </listitem> - </varlistentry> - - <varlistentry> - <term>--version</term> - <listitem> - <para>Print the version of the GDM daemon.</para> - </listitem> - </varlistentry> - - <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> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <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> - </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> - </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> - </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> - </sect3> - </sect2> - - <sect2 id="libexecdir_binaries"> - <title>Comandos internos de GDM</title> - - <para>The GDM package provides the following different commands in EXPANDED_LIBEXECDIR 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> - - <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> - - <variablelist> - <title><command>gdmchooser</command> Command Line Options</title> - - <varlistentry> - <term>-xdmaddress=SOCKET</term> - <listitem> - <para>Socket for XDM communication.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>--clientaddress=ADDRESS</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> - </listitem> - </varlistentry> - - <varlistentry> - <term>-connectionType=TYPE</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> - </listitem> - </varlistentry> - </variablelist> - </sect3> - </sect2> - </sect1> - - <!-- ============= Theme manual ============================= --> - - <sect1 id="thememanual"> - <title>Interfaz con temas</title> - - <para>This section describes the creation of themes for the Themed Greeter. For examples including screenshots, see the standard installed themes and the themes from <ulink type="http" url="http://art.gnome.org/themes/gdm_greeter/"> the theme website</ulink>.</para> - - <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> - - <screen> -[GdmGreeterTheme] -Encoding=UTF-8 -Greeter=circles.xml -Name=Circles -Description=Theme with blue circles -Author=Bond, James Bond -Copyright=(c) 2002 Bond, James Bond -Screenshot=screenshot.png - </screen> - - <para>The Name, Description, Author and Copyright fields can be translated just like the other <filename>.desktop</filename>files. All the files that are mentioned should be in the theme directory itself. The Screenshot field points to a file which should be a 200x150 screenshot of the theme in action (it is OK not to have one, but it makes it nicer for user). The Greeter field points to an XML file that contains the description of the theme. The description will be given later.</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>/usr/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 /usr/share/gdm/themes -tar czvf <theme_name>.tar.gz <theme_name>/ - </screen></para> - - </sect2> - - <sect2 id="descofthemeformat"> - <title>Detailed Description of Theme XML format</title> - - <sect3 id="boxnodes"> - <title>Box Nodes</title> - - <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> - - <para>If the box is homogeneous then the children are allocated equal amount of space.</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>Fixed Nodes</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><fixed></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> - </sect3> - - <sect3 id="itemnodes"> - <title>Item Nodes</title> - - <para>A GDM Theme is created by specifying a hierarchy of item and box nodes. Item nodes can have the following value for "type":</para> - - <variablelist> - <varlistentry> - <term>entrada</term> - <listitem> - <para>Campo de entrada de texto.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>lista</term> - <listitem> - <para>Un widget de lista</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>etiqueta</term> - <listitem> - <para>A text label. Must have a "text" node to specify the text.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>imagen</term> - <listitem> - <para>An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, etc...)</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>rect</term> - <listitem> - <para>Rectángulo.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>svg</term> - <listitem> - <para>Imagen Scaled Vector Graphic</para> - </listitem> - </varlistentry> - </variablelist> - - <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> - - <para>Entry items can have id values as follows:</para> - - <variablelist> - <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> - </listitem> - </varlistentry> - </variablelist> - - - <para>List items can have id values as follows:</para> - - <variablelist> - <varlistentry> - <term>lista de usuarios</term> - <listitem> - <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>Label items can have id values as follows:</para> - - <variablelist> - <varlistentry> - <term>reloj</term> - <listitem> - <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> - </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> - </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> - </listitem> - </varlistentry> - - <varlistentry> - <term>timed-label</term> - <listitem> - <para>Etiqueta que muestra la información de la entrada temporizada.</para> - </listitem> - </varlistentry> - </variablelist> - - <para>Rectangles can have id values as follows:</para> - - <variablelist> - <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> - </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><item type="rect" id="disconnect_button" button="true">.</screen></para> - - <para>Possible values for button ids are as follows:</para> - - <variablelist> - <varlistentry> - <term>chooser_button</term> - <listitem> - <para>Runs the XDMCP chooser.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>config_button</term> - <listitem> - <para>Ejecuta la aplicación de configuración de GDM.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>disconnect_button</term> - <listitem> - <para>Desconectar de una sesión remota.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>botón_idioma</term> - <listitem> - <para>Muestra el diálogo de selección del idioma.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>botón_detener</term> - <listitem> - <para>Halt (shuts down) the system.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>botón reiniciar</term> - <listitem> - <para>Restart the system.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>botón_sesión</term> - <listitem> - <para>List and select from available sessions.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>botón_suspender</term> - <listitem> - <para>Suspender el sistema</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>botón_sistema</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> - </listitem> - </varlistentry> - - </variablelist> - </sect3> - - <sect3 id="positionnodes"> - <title>Position Node</title> - - <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> - - <para>Both position and size can be given in percent and it will be taken as the percentage of the size of the current container. For toplevel items it's the percentage of the whole screen.</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><pos x="10%" y="50%" anchor="w" width="80%" height="95"/></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 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>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> - - </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><filename>console</filename> - In console mode.</para> - <para><filename>console-fixed</filename> - In console non-flexi mode.</para> - <para><filename>console-flexi</filename> - In console & flexi mode.</para> - <para><filename>flexi</filename> - In flexi mode.</para> - <para><filename>remote</filename> - In remote mode.</para> - <para><filename>remote-flexi</filename> - In remote & flexi mode.</para> - - <para>For example: <screen><show modes="flexi,remote"/></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><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><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> - </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><filename>normal</filename> - normal state.</para> - <para><filename>active</filename> - when the item has active focus.</para> - <para><filename>prelight</filename> - when the mouse is hovering over the item.</para> - - <para>When item is "rect" (alpha can be omitted and defaults to 0.0): <screen><normal color="#ffffff" alpha="0.0"></screen></para> - - <para>When item is "label" <screen><normal color="#ffffff" font="Sans 14"/></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><normal file="picture.png" tint="#dddddd"/></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> - </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> - <screen><color iconcolor="#dddddd" labelcolor="#ffffff"/></screen> - </para> - </sect3> - <sect3 id="textnodes"> - <title>Text Node</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><text xml:lang="fr">Option</text></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><text">foo&lt;sup&>bar&lt;/sup&></text></screen></para> - - <para>Text nodes can contain the following special character sequences which will be translated as follows:</para> - - <para>%% - A literal % character</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 - Carriage return</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"> - <title>Stock</title> - - <para>Certain common localized labels can be specified via the stock tags. The "text" tag is ignored if the "stock" tag is used. You should really use the stock labels rather then just putting all the translations into the themes. This gives faster load times and likely better translations. The following values are valid:</para> - - <para><filename>cancel</filename>, _("_Cancel"</para> - <para><filename>caps-lock-warning</filename>, _("You've got capslock on!"</para> - <para><filename>chooser</filename>, _("_XDMCP Chooser"</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> - </sect3> - - <sect3 id="customwidgetry"> - <title>Custom Widgetry</title> - - <para>Currently there is one item which can be customizable and this is the list item. If you need to ask the user extra things, such as to pick from a list of places to log into, or set of custom login sessions you can setup the list item and add listitem children that describe the choices. Each listitem must have an id and a text child. The choice will be recorded in the file <filename><ServAuthDir>/<display>.GreeterInfo</filename> as <filename><list id>=<listitem id></filename>.</para> - - <para>For example suppose we are on display :0, <filename>ServAuthDir</filename> is <filename><var>/gdm</filename> and we have the following in the theme:</para> - - <screen> -<item type="list" id="custom-config"> -<pos anchor="nw" x="1" y="1" height="200" width="100"> -<listitem id="foo"> -<text>Foo</text> -</listitem> -<listitem id="bar"> -<text>Bar</text> -</listitem> -</item> - </screen> - - <para>Then if the user chooses 'Foo' then <filename><var>/gdm/:0.GreeterInfo</filename> will contain: <screen>custom-config=foo</screen></para> - </sect3> - </sect2> - </sect1> - - <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. This feature allows the user to launch assistive technologies at login time by means of special "gestures" from the standard keyboard and from a keyboard, pointing device, or switch device attached to the USB or PS/2 mouse port. It also allows the user to change the visual appearance of the login UI before logging in, for instance to use a higher-contrast color scheme for better visibility. GDM only supports accessibility with the GTK+ Greeter, so the "Greeter" parameter in the GDM configuration must be set to the GTK+ Greeter "gdmlogin"</para> - - <sect2 id="accessibilityconfig"> - <title>Configuración de accesibilidad</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> - - <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> - - <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.</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>Accessibility Login Sound Configuration</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>/usr/bin/play</filename> (or <filename>/usr/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> - - <sect1 id="solaris"> - <title>Características específicas de Solaris</title> - - <para>GDM soporta unas pocas características específicas a Solaris, como las siguientes:</para> - - <para>GDM soporta Solaris Auditing si se ejecuta sobre Solaris 10 o superior.</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> - - </sect1> - - <sect1 id="exampleconf"> - <title>Configuraciones de ejemplo</title> - - <para>Esta sección tiene algunas configuraciones de ejemplo que son útiles para varias configuraciones.</para> - - <sect2 id="terminallab"> - <title>Terminal Lab With One Server</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>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> -[server-Terminal] -name=Terminal server -command=/usr/X11R6/bin/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> -[servers] -0=Terminal -query appserver - </screen> This will run a direct XDMCP query to the server named <filename>appserver</filename>.</para> - </sect2> - - <sect2 id="terminallabtwo"> - <title>Terminal Lab With Two Or More Servers</title> - - <para>Suppose you want to make a lab full of X terminals that all connect to some choice of servers. For now let's make it <filename>appserverone</filename> and <filename>appservertwo</filename>. Again we'll call our example X terminal server <filename>xterminal</filename>. The setup on both servers is the same as with the case of one server in the previous section. You do not need to explicitly enable indirect queries on the server since we'll run the choosers locally on the X terminals.</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> -[server-Chooser] -name=Chooser server -command=/usr/X11R6/bin/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> -[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>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> -[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 serveral 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> - - <!-- ============= Application License ============================= --> - - <sect1 id="license"> - <title>License</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> - </sect1> - -</article> -<!-- Keep this comment at the end of the file -Local variables: -mode: sgml -sgml-omittag:t -sgml-shorttag:t -sgml-minimize-attributes:nil -sgml-always-quote-attributes:t -sgml-indent-step:2 -sgml-indent-data:t -sgml-parent-document:nil -sgml-exposed-tags:nil -sgml-local-catalogs:nil -sgml-local-ecat-files:nil -End: ---> + <sect2 id="performance"><title>GDM Performance</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 --with-prefetch option. This will cause GDM to install the gdmprefetch program to the EXPANDED_LIBEXEC directory, install the gdmprefetchlist to the <etc>/gdm directory, and set the PreFetchProgram configuration variable so that the gdmprefetch program is called with the default gdmprefetchlist file. The default gdmprefetchlist 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> Security The GDM User The GDM daemon normally runs as root, as does the slave. However GDM should also have a dedicated user id and a group id which it uses for its graphical interfaces such as gdmgreeter and gdmlogin. You can choose the name of this user and group in the [daemon] section of the configuration file. The GDM user, and group, which are normally just gdm should not be user or group of any particular privilege. The reason for using them is to have the user interface run as a user without privileges so that in the unlikely case that someone finds a weakness in the GUI, they cannot access root on the computer. It should however be noted that the GDM user and group have some privileges that make them somewhat dangerous. For one they have access to the X server authorization directory (the ServAuthDir), which contains all the X server authorization files and other private information. This means 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 nobody. X Server Authentication Scheme The X server authorization directory (the ServAuthDir) is used for a host of random internal data in addition to the X server authorization files, and the naming is really a relic of history. GDM daemon enforces this directory to be owned by root.gdm with the permissions of 1770. This way, only root and the GDM group have write access to this directory, but the GDM group cannot remove the root owned files from this directory, such as the X server authorization files. GDM by default doesn't trust the X server authorization directory and treats it in the same way as the temporary directory with respect to creating files. This way someone breaking the GDM user cannot mount attacks by creating links in this directory. Similarly the X server log directory is treated safely, but that directory should really be owned and writable only by root. GDM only supports the MIT-MAGIC-COOKIE-1 X server authentication scheme. Normally little is gained from the other schemes, and no effort has been made to implement them so far. Be especially careful about using XDMCP because the X server authentication cookie goes over the wire as clear text. If snooping is possible, then an attacker could simply snoop your authentication password as you log in, regardless of the authentication scheme being used. If snooping is possible and undesirable, then you should use ssh for tunneling an X connection rather then using XDMCP. You could think of XDMCP as a sort of graphical telnet, having the same security issues. On the upside, GDM's random number generation is very conservative and GDM goes to extraordinary measures to truly get a 128 bit random number, using hardware random number generators (if available), plus the current time (in microsecond precision), a 20 byte array of pseudorandom numbers, process pid's, and other random information (possibly using /dev/audio or /dev/mem if hardware random generators are not available) to create a large buffer and then run MD5 digest on this. Obviously, all this work is wasted if you send this cookie over an open network or store it on an NFS directory (see UserAuthDir configuration key). So be careful about where you use remote X display. Firewall Security Even though GDM tries to outsmart potential attackers trying to take advantage of XDMCP, it is still advised that you block the XDMCP port (normally UDP port 177) on your firewall unless you really need it. GDM guards against DoS (Denial of Service) attacks, but the X protocol is still inherently insecure and should only be used in controlled environments. Also each remote connection takes up lots of resources, so it is much easier to DoS via XDMCP then a webserver. It is also wise to block all of the X Server ports. These are TCP ports 6000 + the display number of course) on your firewall. Note that GDM will use display numbers 20 and higher for flexible on-demand servers. X is not a very safe protocol for leaving on the net, and XDMCP is even less safe. GDM Security With NFS Note that NFS traffic really goes over the wire and thus can be snooped. When accessing the user's X authorization file (~/.Xauthority), GDM will try to open the file for reading as root. If it fails, GDM will conclude that it is on an NFS mount and it will automatically use UserAuthFBDir, which by default is set to /tmp. This behavior can be changed by setting the NeverPlaceCookiesOnNFS in the [security] section to false. XDMCP Security 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. XDMCP is primarily useful for running thin clients such as in terminal labs. Those thin clients will only ever need the network to access the server, and so it seems like the best security policy to have those thin clients on a separate network that cannot be accessed by the outside world, and can only connect to the server. The only point from which you need to access outside is the server. 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. XDMCP Access Control XDMCP access control is done using TCP wrappers. It is possible to compile GDM without TCP wrappers however, so you should test your configuration and verify that they work. You should use the daemon name gdm in the etc/hosts.allow and etchosts.deny files. For example to deny computers from .evil.domain from logging in, then add gdm: .evil.domain to etc/hosts.deny. You may also need to add gdm: .your.domain to your etc/hosts.allow if you normally disallow all services from all hosts. See the hosts.allow(5) man page for details. Configuration This section will cover the configuration of GDM and the format of the GDM configuration files. You can use the gdmsetup command to configure GDM, but the configuration application does not let you configure every aspect of GDM. The information in this section explains how to further configure GDM. The configuration files (especially the gdm.conf and gdm.conf-custom files) contains useful comments and examples, so read this for more information about changing your setup. Some keys in the configuration file as shipped are commented out while others are set. This is done so that defaults can be easily changed in the future for some keys. GDM considers lines that start with the # character a comment, and these lines will be ignored by GDM. The gdm.conf file contains the default configuration choices for GDM, and should not be modified by the user. The gdm.conf-custom file is where users may specify their custom configuration choices. Configuration options specified in the gdm.conf-custom file override the values in the main gdm.conf file. Running the gdmsetup command will cause the gdm.conf-custom 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 gdm.conf file, so if using an older version of GDM just edit that file directly. GDM may be configured to support system-wide configuration if built with the --with-configdir option. This allows the gdm.conf file to be installed to a directory that can be mounted across multiple-systems. The GDM --config option may also be used to specify the configuration file location. The GDM2 daemon must be restarted to change the configuration file being used. factory-gdm.conf is the configuration file as shipped with the daemon. This can be useful if you wish to revert to the default configuration. The other GDM configuration files are located, by default, in the etc/gdm/ folder or its subdirectories. However, the location of all configuration files can be defined in the gdm.conf file, so the sysadmin may choose to locate these files in any location. This is a listing of the config directory contents: locale.alias Xsession XKeepsCrashing modules/ Init/ PostLogin/ PreSession/ PostSession/ locale.alias is a file which looks much like the system locale alias but in fact it is not the same. These are the languages that are available on your system. All the languages are still tested to see if they actually exist before presenting them to the user. Xsession 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 desktop file associated with the session the user has picked. Some sessions may start the user's session via a different mechanism than the Xsession script, so please check the appropriate desktop before assuming a session startup issue is being caused by this file. XKeepsCrashing is a script which gets run when the X server keeps crashing and we cannot recover. The shipped default script will work with most Linux distributions and can run the X configuration application provided the person on the console knows the root password. Accessibility modules are configured in the modules/ subdirectory, and are a separate topic. Read the default files provided, they have adequate documentation. Again normally the default install is given in the files with factory in their name, and those files are not read, they are just there for you so you can always revert to default config. Files describing available GDM session follow the freedesktop.org desktop file specification and are .desktop-style files are installed to etc/X11/sessions/. This directory is also read by the KDE desktop manager (KDM) for common configuration. Next the directory share/gdm/BuiltInSessions/ is read for GDM specific built-in sessions (KDM hardcodes these at time of this writing). Lastly the default setup will also read share/xsessions/ (which should be /usr/share/xsessions/ if you really wish to cooperate with KDM) where desktop packages can install their session files. The directories under the etc should be reserved for configuration. The desktop file specification approach makes it easy for package management systems to install window managers and different session types without requiring the sysadmin to edit files. See the SessionDesktopDir configuration key for changing the paths. It used to be that GDM stored its built in sessions in etc/dm/Sessions/ but this is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the etc/dm/Sessions/ was being read. A session can be disabled (if it was installed in /usr/share/xsessions/) by adding an identically named .desktop to one of the directories earlier in the path (likely etc/X11/sessions) and using Hidden=true in that file. The Script Directories In this section we will explain the Init, PostLogin, PreSession and PostSession directories as they are very similar. When the X server has been successfully started, GDM will try to run the script called Init/displayname. I.e. Init/:0 for the first local display. If this file is not found, GDM will attempt to to run Init/hostname. I.e. Init/somehost. If this still is not found, GDM will try Init/XDMCP for all XDMCP logins or Init/Flexi for all on demand flexible displays. If none of the above were found, GDM will run Init/Default. The script will be run as root and GDM blocks until it terminates. Use the Init/* script for applications that are supposed to run alongside with the GDM login window. xconsole for instance. Commands to set the background etc. goes in this file too. It is up to the sysadmin to decide whether clients started by the Init script should be killed before starting the user session. This is controlled with the KillInitClients configuration option. When the user has been successfully authenticated GDM tries the scripts in the PostLogin directory in the same manner as for the Init directory. This is done before any session setup is done, and so this would be the script where you might setup the home directory if you need to (though you should use the pam_mount module if you can for this). You have the $USER and $DISPLAY environment variables set for this script, and again it is run as root. The script should return 0 on success as otherwise the user won't be logged in. This is not true for failsafe session however. After the user session has been setup from the GDM side of things, GDM will run the scripts in the PreSession directory, again in the same manner as the Init directory. Use this script for local session management or accounting stuff. The $USER environment variable contains the login of the authenticated user and $DISPLAY is set to the current display. The script should return 0 on success. Any other value will cause GDM to terminate the current login process. This is not true for failsafe sessions however. Also $X_SERVERS environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application. After this the base Xsession script is run with the selected session executable as the first argument. This is run as the user, and really this is the user session. The available session executables are taken from the Exec= line in the .desktop files in the path specified by SessionDesktopDir. Usually this path is etc/X11/sessions/:etc/dm/Sessions:/usr/share/xsessions/. The first found file is used. The user either picks from these sessions or GDM will look inside the file ~/.dmrc for the stored preference. This script should really load the users profile and generally do all the voodoo that is needed to launch a session. Since many systems reset the language selections done by GDM, GDM will also set the $GDM_LANG variable to the selected language. You can use this to reset the language environmental variables after you run the users profile. If the user elected to use the system language, then $GDM_LANG is not set. When the user terminates his session, the PostSession script will be run. Again operation is similar to Init, PostLogin and PreSession. Again the script will be run with root privileges, the slave daemon will block and the $USER environment variable will contain the name of the user who just logged out and $DISPLAY will be set to the display the user used, however note that the X server for this display may already be dead and so you shouldn't try to access it. Also $X_SERVERS environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application. Note that the PostSession script will be run even when the display fails to respond due to an I/O error or similar. Thus, there is no guarantee that X applications will work during script execution. Except for the Xsession script all of these scripts will also have the environment variable $RUNNING_UNDER_GDM set to yes, so that you could perhaps use similar scripts for different display managers. The Xsession will always have the $GDMSESSION set to the basename of the session that the user chose to run without the .desktop extension. In addition $DESKTOP_SESSION is also set to the same value and in fact this will also be set by KDM in future versions. Neither of the Init, PostLogin, PreSession or PostSession scripts are necessary and can be left out. The Xsession script is however required as well as at least one session .desktop file. The Configuration File - gdm.conf and gdm.conf-custom GDM uses two configuration files: gdm.conf and gdm.conf-custom. The gdm.conf file contains the default configuration choices for GDM, and should not be modified by the user. The gdm.conf-custom file is where users may specify their custom configuration choices. Configuration options specified in the gdm.conf-custom file override the values in the main gdm.conf file. If a configuration option is not defined in either file, GDM will default to the value described in the comments in the gdm.conf file. Running the gdmsetup command will cause the gdm.conf-custom to be modified with the user's configuration choices. Previous to GDM 2.13.0.4 only the gdm.conf existed. If upgrading to the new version of GDM, install will check to see if your gdm.conf file is different than your factory-gdm.conf file. If so, your gdm.conf file will be automatically copied to gdm.conf-custom to preserve your configuration changes. GDM may be configured to support system-wide configuration if built with the --with-configdir option. This allows the gdm.conf file to be installed to a directory that can be mounted across multiple-systems. The GDM --config option may instead be used to specify a configuration file installed to another location. The GDM2 daemon must be restarted to change the configuration file being used. Both configuration files are divided into sections each containing variables that define the behavior for a specific part of the GDM suite. Refer to the comments in the gdm.conf file for additional information about each configuration setting. The gdm.conf and gdm.conf-custom files follow the standard .ini style configuration file syntax. Keywords in brackets define sections, strings before an equal sign (=) are variables and the data after equal sign represents their value. Empty lines or lines starting with the hash mark (#) are ignored. The graphical configurator will try to preserve both comments (lines with a hash mark) and the overall structure of the file so you can intermix using the GUI or hand editing the configuration file. Daemon Configuration [daemon] AddGtkModules AddGtkModules=false If true, then enables gdmgreeter or gdmlogin to be launched with additional Gtk+ modules. This is useful when extra features are required such as accessible login. Note that only trusted modules should be used to minimize security issues. Usually this is used for accessibility modules. The modules which are loaded are specified with the GtkModulesList key. AlwaysRestartServer AlwaysRestartServer=false If true, then gdm never tries to reuse existing X servers by reinitializing them. It will just kill the existing X server and start over. Normally, just reinitializing is a nicer way to go but if the X server memory usage keeps growing this may be a safer option. On Solaris, this value is always true, and this configuration setting is ignored. AutomaticLoginEnable AutomaticLoginEnable=false If the user given in AutomaticLogin should be logged in upon first bootup. No password will be asked. This is useful for single user workstations where local console security is not an issue. Also could be useful for public terminals, although there see TimedLogin. AutomaticLogin AutomaticLogin= This user should be automatically logged in on first bootup. AutomaticLoginEnable must be true and this must be a valid user for this to happen. root can never be autologged in however and gdm will just refuse to do it even if you set it up. The following control chars are recognized within the specified name: the `' character d display's name h display's hostname Alternatively, the name may end with a vertical bar |, the pipe symbol. The name is then used as a application to execute which returns the desired username on standard output. If an empty or otherwise invalid username is returned, automatic login is not performed. This feature is typically used when several remote displays are used as internet kiosks, with a specific user to automatically login for each display. BaseXsession BaseXsession=etc/gdm/Xsession 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 Exec= from the .desktop file of the session. 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 GDMSESSION environmental variable. This will always be set to the basename of .desktop (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 GDM_LANG, but that is only set when the user picks a non-system default language. This script should take care of doing the login for the user and so it should source the etc/profile and friends. The standard script shipped with GDM sources the files in this order: etc/profile then ~/.profile then etc/xprofile and finally ~/.xprofile. Note that different distributions may change this however. Sometimes users personal setup will be in ~/.bash_profile, however broken that is. Chooser Chooser=bin/gdmchooser Full path and name of the chooser executable followed by optional arguments. Configurator Configurator=bin/gdmsetup --disable-sound --disable-crash-dialog The pathname to the configurator binary. If the greeter ConfigAvailable 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. ConsoleCannotHandle ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh 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. ConsoleNotify ConsoleNotify=true If false, gdm will not display a message dialog on the console when an error happens. DefaultPath DefaultPath=/bin:/usr/bin:/usr/bin/X11:/usr/local/bin Specifies the path which will be set in the user's session. This value will be overridden with the value from /etc/default/login if it contains ROOT=pathname. If the /etc/default/login file exists, but contains no value for ROOT, the value as defined in the GDM configuration will be be used. DefaultSession DefaultSession=gnome.desktop 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 ShowLastSession key. DisplayInitDir DisplayInitDir=etc/gdm/Init Directory containing the display init scripts. See the ``The Script Directories'' section for more info. DisplayLastLogin DisplayLastLogin=true 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. 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 http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html for more info. DoubleLoginWarning DoubleLoginWarning=true 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. DynamicXServers DynamicXServers=false If true, the GDM daemon will honor requests to manage displays via the /tmp/.gdm_socket socket connection. Displays can be created, started, and deleted with the appropriate commands. The gdmdynamic command is a convenient method to send these messages. FailsafeXServer FailsafeXServer= 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 XKeepsCrashing script is run. FirstVT FirstVT=7 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 VTAllocation. FlexibleXServers FlexibleXServers=5 The maximum number of allowed flexible displays. These are displays that can be run using the /tmp/.gdm_socket socket connection. This is used for both full flexible displays and for Xnest displays. FlexiReapDelayMinutes FlexiReapDelayMinutes=5 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 behaviour set this value to 0. This was added in version 2.5.90.0. Greeter Greeter=bin/gdmlogin 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 RemoteGreeter Group Group=gdm The group name under which gdmlogin, gdmgreeter, gdmchooser and the internal failsafe GTK+ dialogs are run. Also see User. 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 ServAuthDir is owned by this group. The ownership and permissions of ServAuthDir should be root.gdm and 1770. GtkModulesList GtkModulesList=module-1:module-2:... A colon separated list of Gtk+ modules that gdmgreeter or gdmlogin will be invoked with if AddGtkModules is true. The format is the same as the standard Gtk+ module interface. HaltCommand HaltCommand=/sbin/shutdown -h now Full path and arguments to command to be executed when user selects Shutdown from the Actions menu. This can be a ';' separated list of commands to try. If a value is missing, the shutdown command is not available. Note that the default for this value is not empty so to disable shutdown you must set this explicitly to an empty value. KillInitClients KillInitClients=true Determines whether GDM should kill X clients started by the init scripts when the user logs in. LogDir LogDir=var/log/gdm Directory containing the log files for the individual displays. By default this is the same as the ServAuthDir. PidFile PidFile=var/run/gdm.pid Name of the file containing the gdm process id. PreFetchProgram PreFetchProgram=command 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. PostLoginScriptDir PostLoginScriptDir=etc/gdm/PostLogin 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. PostSessionScriptDir PostSessionScriptDir=etc/gdm/PostSession Directory containing the scripts run after the user logs out. See the ``The Script Directories'' section for more info. PreSessionScriptDir PreSessionScriptDir=etc/gdm/PreSession Directory containing the scripts run before the user logs in. See the ``The Script Directories'' section for more info. RebootCommand RebootCommand=/sbin/shutdown -r now 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. RemoteGreeter RemoteGreeter=bin/gdmlogin 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 Greeter key. RootPath RootPath=/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/local/bin 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 /etc/default/login if it contains SUROOT=pathname. If the /etc/default/login file exists, but contains no value for SUROOT, the value as defined in the GDM configuration will be used. ServAuthDir ServAuthDir=var/gdm Directory containing the X authentication files for the individual displays. Should be owned by root.gdm with permissions 1770, where gdm is the GDM group as defined by the Group option. That is should be owned by root, with gdm 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. SessionDesktopDir SessionDesktopDir=etc/X11/sessions/:etc/dm/Sessions/:/usr/share/xsessions/ Directory containing the .desktop 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. SoundProgram SoundProgram=/usr/bin/play Application to use when playing a sound. Currently used for playing the login sound, see the SoundOnLoginFile key. Supported since 2.5.90.0. StandardXServer StandardXServer=/usr/X11R6/bin/X 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. SuspendCommand SuspendCommand= 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. TimedLoginEnable TimedLoginEnable=false If the user given in TimedLogin should be logged in after a number of seconds (set with TimedLoginDelay) 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 TimedLoginDelay 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. TimedLogin TimedLogin= 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 AutomaticLogin are supported. The same control chars and piping to a application are supported. TimedLoginDelay TimedLoginDelay=30 This is the delay before the TimedLogin user will be logged in. It must be greater then or equal to 10. User User=gdm The username under which gdmlogin, gdmgreeter, gdmchooser and the internal failsafe GTK+ dialogs are run. Also see Group. 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. UserAuthDir UserAuthDir= The directory where user's .Xauthority 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: ~/authdir/. If you do not use the tilde expansion, then the filename created will be random, like in UserAuthFBDir. This way many users can have the same authentication directory. For example you might want to set this to /tmp 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 /tmp directory. 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 NeverPlaceCookiesOnNFS in the [security] section to false. UserAuthFBDir UserAuthFBDir=/tmp If GDM fails to update the user's .Xauthority file a fallback cookie is created in this directory. UserAuthFile UserAuthFile=.Xauthority Name of the file used for storing user cookies. VTAllocation VTAllocation=true 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 FirstVT. XKeepsCrashing XKeepsCrashing=etc/gdm/XKeepsCrashing 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 XKeepsCrashing 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. In case FailsafeXServer is setup, that will be tried first. and this only used as a backup if even that X server keeps crashing. Xnest Xnest=/usr/bin/X11/Xnest (/usr/openwin/bin/Xnest on Solaris) 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. Security Options [security] AllowRoot AllowRoot=true Allow root (privileged user) to log in through GDM. Set this to false if you want to disallow such logins. 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. AllowRemoteRoot AllowRemoteRoot=false 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. 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. This value will be overridden and set to false if the /etc/default/login file exists and contains CONSOLE=/dev/login, and set to true if the /etc/default/login file exists and contains any other value or no value for CONSOLE. AllowRemoteAutoLogin AllowRemoteAutoLogin=false 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. Note that this can make a system quite insecure, and thus is off by default. CheckDirOwner CheckDirOwner=true 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 RelaxPermissions 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. DisallowTCP DisallowTCP=true If true, then always append -nolisten tcp 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. NeverPlaceCookiesOnNFS NeverPlaceCookiesOnNFS=true 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. PasswordRequired PasswordRequired=false 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 /etc/default/login if it contains PASSREQ=[YES|NO]. If the /etc/default/login file exists, but contains no value for PASSREQ, the value as defined in the GDM configuration will be used. RelaxPermissions RelaxPermissions=0 By default GDM ignores files and directories writable to other users than the owner. Changing the value of RelaxPermissions makes it possible to alter this behavior: 0 - Paranoia option. Only accepts user owned files and directories. 1 - Allow group writable files and directories. 2 - Allow world writable files and directories. RetryDelay RetryDelay=1 The number of seconds GDM should wait before reactivating the entry field after a failed login. UserMaxFile UserMaxFile=65536 GDM will refuse to read/write files bigger than this number (specified in bytes). 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 RelaxPermissions option for more info. XDCMP Support [xdmcp] DisplaysPerHost DisplaysPerHost=1 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 DisplaysPerHost value accordingly. Note that the number of connections from the local computer is unlimited. Only remote connections are limited by this number. Enable Enable=false Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM. gdm listens for requests on UDP port 177. See the Port option for more information. If GDM is compiled to support it, access from remote displays can be controlled using the TCP Wrappers library. The service name is gdm You should add gdm:.my.domain to your etc/hosts.allow, depending on your TCP Wrappers configuration. See the hosts.allow(5) man page for details. Please note that XDMCP is not a particularly secure protocol and that it is a good idea to block UDP port 177 on your firewall unless you really need it. EnableProxy EnableProxy=false 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. Note, however, that this mode will significantly increase the burden on the machine hosting the XDMCP sessions See the FlexiProxy and FlexiProxyDisconnect options for further details on how to configure support for this feature. HonorIndirect HonorIndirect=true Enables XDMCP INDIRECT choosing (i.e. remote execution of gdmchooser) for X-terminals which don't supply their own display browser. MaxPending MaxPending=4 To avoid denial of service attacks, GDM has fixed size queue of pending connections. Only MaxPending displays can start at the same time. 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. MaxPendingIndirect MaxPendingIndirect=4 GDM will only provide MaxPendingIndirect displays with host choosers simultaneously. If more queries from different hosts come in, the oldest ones will be forgotten. MaxSessions MaxSessions=16 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. MaxWait MaxWait=30 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. GDM will then place the session id in the pending queue waiting for the display to respond with a MANAGE request. 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. MaxWaitIndirect MaxWaitIndirect=30 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 MaxPendingIndirect. Port Port=177 The UDP port number gdm should listen to for XDMCP requests. Don't change this unless you know what you are doing. PingIntervalSeconds PingIntervalSeconds=15 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. Note that GDM in the past used to have a PingInterval 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. ProxyReconnect FlexiProxyReconnect= 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. 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. 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. ProxyXServer ProxyXServer= The X server command line for a XDMCP proxy. Any nested X server like Xnest, Xephr or Xdmx should work fairly well. Willing Willing=etc/gdm/Xwilling 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. Common GUI Configuration Options [gui] AllowGtkThemeChange AllowGtkThemeChange=true 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. GtkRC GtkRC= Path to a gtkrc to read when GDM puts up a window. You should really now use the GtkTheme key for just setting a theme. GtkTheme GtkTheme=Default 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. GtkThemesToAllow GtkThemesToAllow=all 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 AllowGtkThemeChange key. Supported since 2.5.90.2. MaxIconWidth MaxIconWidth=128 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. MaxIconHeight MaxIconHeight=128 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. Greeter Configuration [greeter] BackgroundColor BackgroundColor=#76848F 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. BackgroundProgramInitialDelay BackgroundProgramInitialDelay=30 The background application will be started after at least that many seconds of inactivity. RestartBackgroundProgram RestartBackgroundProgram=true 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. BackgroundProgramRestartDelay BackgroundProgramRestartDelay=30 The background application will be restarted after at least that many seconds of inactivity. BackgroundImage BackgroundImage=somefile.png If the BackgroundType is 1, then display this file as the background in the greeter. This only affects the GTK+ Greeter. BackgroundProgram BackgroundProgram=/usr/bin/xeyes 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. BackgroundRemoteOnlyColor BackgroundRemoteOnlyColor=true On remote displays only set the color background. This is to make network load lighter. The BackgroundProgram is also not run. This only affects the GTK+ Greeter. BackgroundScaleToFit BackgroundScaleToFit=true Scale background image to fit the screen. This only affects the GTK+ Greeter. BackgroundType BackgroundType=2 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. Browser Browser=true 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 ChooserButton ChooserButton=true 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. ConfigAvailable ConfigAvailable=false 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 Configurator option in the daemon section. DefaultFace DefaultFace=share/pixmaps/nophoto.png 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, the image specified by DefaultFace will be used. The image must be in an gdk-pixbuf supported format and the file must be readable to the GDM user. Include Include= Comma separated list of users to be included in the face browser and in the gdmsetup selection list for Automatic/Timed login. See also Exclude, IncludeAll, and MinimalUID. Exclude Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,... Comma separated list of users to be excluded from the face browser and from the gdmsetup selection list for Automatic/Timed login. Excluded users will still be able to log in, but will have to type their username. See also Include, IncludeAll, and MinimalUID. IncludeAll IncludeAll=false By default, an empty include list means display no users. By setting IncludeAll to true, the password file will be scanned and all users will be displayed aside from users excluded via the Exclude setting and user ID's less than MinimalUID. Scanning the password file can be slow on systems with large numbers of users and this feature should not be used in such environments. See also Include, Exclude, and MinimalUID. GlobalFaceDir GlobalFaceDir=share/pixmaps/faces/ Systemwide directory for face files. The sysadmin can place icons for users here without touching their homedirs. Faces are named after their users' logins. I.e. GlobalFaceDir/johndoe would contain the face icon for the user ``johndoe''. No image format extension should be specified. The face images must be stored in gdk-pixbuf supported formats and they must be readable for the GDM user. A user's own icon file will always take precedence over the sysadmin provided one. GraphicalTheme GraphicalTheme=circles The graphical theme that the Themed Greeter should use. it should refer to a directory in the theme directory set by GraphicalThemeDir. GraphicalThemes GraphicalThemes=circles The graphical themes that the Themed Greeter should use is the Mode is set on Random Themes. This is a /: delimited list. It should refer to a directory in the theme directory set by GraphicalThemeDir. This is only used if GraphicalThemeRand is set to true. GraphicalThemeRand GraphicalThemeRand=false Whether the graphical greeter will use Only One Theme or Random Theme mode. Only One Theme mode uses themes listed by GraphicalTheme, Random Themes mode uses themes listed by GraphicalThemes. A value of false sets greeter to use Only One Theme mode, a value of true sets the greeter to use Random Theme mode. GraphicalThemeDir GraphicalThemeDir=share/gdm/themes/ The directory where themes for the Themed Greeter are installed. GraphicalThemedColor GraphicalThemedColor=#76848F Use this color in the background of the Themed Greeter. This only affects the Themed Greeter. InfoMsgFile InfoMsgFile=/path/to/infofile 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. InfoMsgFont InfoMsgFont=fontspec 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. LocaleFile LocaleFile=etc/gdm/locale.alias 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. LockPosition LockPosition=true If true the position of the login window of the GTK+ Greeter cannot be changed even if the title bar is turned on. Logo Logo=share/pixmaps/gnome-logo-large.png 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. ChooserButtonLogo ChooserButtonLogo=share/pixmaps/gnome-logo-large.png Image file to display in the file chooser button in gdmsetup. This key is modified by gdmsetup and should not be manually modified by the user. This only affects the Login Window Preferences (gdmsetup). MinimalUID MinimalUID=100 The minimal UID that GDM should consider a user. All users with a lower UID will be excluded from the face browser. See also Include, Exclude, and IncludeAll. PositionX PositionX=200 The horizontal position of the login window of the GTK+ Greeter. PositionY PositionY=100 The vertical position of the login window of the GTK+ Greeter. Quiver Quiver=true Controls whether gdmlogin should shake the display when an incorrect username/password is entered. This only affects the GTK+ Greeter. DefaultRemoteWelcome DefaultRemoteWelcome=true If set to true, the value Welcome to %n is used for the RemoteWelcome. This value is translated into the appropriate language for the user. If set to false, the RemoteWelcome setting is used. This string can use the same special character sequences as explained in the Text Node section of the Themed Greeter chapter. This explains the meaning of %n. RemoteWelcome RemoteWelcome=Welcome to n Controls which text to display next to the logo image in the greeter for remote XDMCP sessions. The same expansion is done here as in the Welcome string. This string can use the same special character sequences as explained in the Text Node section of the Themed Greeter chapter. chapter. RunBackgroundProgramAlways RunBackgroundProgramAlways=false If this is true then the background application is run always, otherwise it is only run when the BackgroundType is 0 (None) This only affects the GTK+ Greeter. SetPosition SetPosition=true If true the position of the login window of the GTK+ Greeter is determined by PositionX / PositionY. ShowGnomeFailsafeSession ShowGnomeFailsafeSession=true Should the greeter show the Gnome Failsafe session in th sessions list. ShowLastSession ShowLastSession=true 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 DefaultSession) unless then pick something else for this session only. So if this is off, this really circumvents saving of the last session. ShowXtermFailsafeSession ShowXtermFailsafeSession=true Should the greeter show the Xterm Failsafe session in the sessions list. SoundOnLogin SoundOnLogin=true If true, the greeter will play a sound or beep when it is ready for a login. See also the SoundOnLoginFile key. Supported since 2.5.90.0. SoundOnLoginSuccess SoundOnLoginSuccess=true If true, the greeter will play a sound after a successful login attempt. See also the SoundOnLoginSuccessFile key. SoundOnLoginFailure SoundOnLoginFailure=true If true, the greeter will play a sound after a failed login attempt. See also the SoundOnLoginFailureFile key. SoundOnLoginFile SoundOnLoginFile=/path/to/sound.wav The file that will be played using the specified sound application (by default that is /usr/bin/play) instead of a beep when the greeter is ready for a login. See also the SoundOnLogin key and the SoundProgram key. Supported since 2.5.90.0. SoundOnLoginSuccessFile SoundOnLoginSuccessFile=/path/to/sound.wav The file that will be played using the specified sound application (by default that is /usr/bin/play) after a successful login attempt. See also the SoundOnLoginSuccess key and the SoundProgram key. SoundOnLoginFailureFile SoundOnLoginFailureFile=/path/to/sound.wav The file that will be played using the specified sound application (by default that is /usr/bin/play) after a failed login attempt. See also the SoundOnLoginFailure key and the SoundProgram key. SystemMenu SystemMenu=true 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. 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. TitleBar TitleBar=true Display the title bar in the greeter. This only affects the GTK+ Greeter. Use24Clock Use24Clock=auto Select the use of 24 hour clock. Some locales do not support 12 hour format (like Finnish, that is fi_FI), and in those locales this setting has no effect at all. 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. UseCirclesInEntry UseCirclesInEntry=false Use circles instead of asterisks in the password entry. This may not work with all fonts however. UseInvisibleInEntry UseInvisibleInEntry=false Do not show any visual feedback is the password entry. This is the standard in console and xdm. Settings this option discards the UseCirclesInEntry option. DefaultWelcome DefaultWelcome=true If set to true, the value Welcome is used for the Welcome. This value is translated into the appropriate language for the user. If set to false, the Welcome setting is used. Welcome Welcome=Welcome Controls which text to display next to the logo image in the standard greeter. The following control chars are supported: the `' character d display's hostname h Fully qualified hostname m machine (processor type) n Nodename (i.e. hostname without .domain) r release (OS version) s sysname (i.e. OS) This string is only used for local logins. For remote XDMCP logins we use RemoteWelcome. 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. XineramaScreen XineramaScreen=0 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...). XDCMP Chooser Options [chooser] AllowAdd AllowAdd=true 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. Broadcast Broadcast=true 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 Hosts key. Multicast Multicast=true 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 Hosts key. The host will respond if it is listening to XDMCP requests and IPv6 is enabled there. MulticastAddr MulticastAddr=ff02::1 This is the Link-local Multicast address and is hardcoded here. DefaultHostImage DefaultHostImage=share/pixmaps/nohost.png File name for the default host icon. This image will be displayed if no icon is specified for a given host. The file must be in an gdk-pixbuf supported format and it must be readable for the GDM user. HostImageDir HostImageDir=share/hosts Repository for host icon files. The sysadmin can place icons for remote hosts here and they will appear in gdmchooser. The file name must match the fully qualified name (FQDN) for the host. The icons must be stored in gdk-pixbuf supported formats and they must be readable to the GDM user. Hosts Hosts=host1,host2 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 Broadcast 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. ScanTime ScanTime=4 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. Debug Configuration [debug] Enable Enable=false 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. Gestures Gestures=false 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. X Server Definitions 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 Standard is required. If you do not specify this server, GDM will assume default values for a 'Standard' server and the path given by daemon/StandardXServer. Standard is used as the default, in situations when no other server has been defined. Servers are defined by sections named server- 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, server- sections in the gdm.conf-custom file override values in the gdm.conf file. In other words, if a server-Standard section is defined in gdm.conf-custom, then that will be used and the section in the gdm.conf file will be ignored. [server-Standard] name name=Standard server The name that will be displayed to the user. command command=/usr/bin/X11/X The command to execute, with full path to the binary of the X server, and any extra arguments needed. flexible flexible=true Indicates if this server is available as a choice when a user wishes to run a flexible, on demand server. handled handled=true 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 -terminate 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. chooser chooser=false 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. Local Static X Display Configuration 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 [servers] section corresponds to the display number to be managed. Normally there is only one key, which is the key 0, which corresponds to the display :0. 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 [servers] section in the gdm.conf-custom file overrides values in the gdm.conf file. [servers] display number 0=Standard 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). 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 gdm.conf-custom to turn off a display that is defined in the gdm.conf file. GDM will splice -auth ServAuthDir/:n.Xauth :n, where n is the display number. Inside the command line before all other arguments before running the X server. 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 VTAllocation key is set. Normally you do not need to add a -nolisten tcp flag as this is added automatically for local X servers when the DisallowTCP option is set. priority priority=0 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. Per User Configuration 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 UserMaxFile 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. First there is the ~/.dmrc file. In theory this file should be shared between GDM and KDM, so users only have to configure things once. This is a standard .ini style configuration file. It has one section called [Desktop] which has two keys: Session and Language. The Session key specifies the basename of the session .desktop file that the user wishes to normally use (without the .desktop extension, in other words). The Language 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: [Desktop] Session=gnome Language=cs_CZ.UTF-8 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. If the GDM Face Browser is turned, then the file $HOME/.face 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 MaxIconWidth and MaxIconHeight values defined in the GDM configuration or it will be ignored. Users can run the gdmphotosetup program to specify a face image and it will copy the file to the $HOME/.face location and scale it so its longest dimension is not larger than the MaxIconWidth or MaxIconHeight values. gdmphotosetup takes care to not change the aspect ratio of the image. Face images can also be placed in the global face directory, which is specified by the GlobalFaceDir configuration option ( normally share/pixmaps/faces/) and the filename should be the name of the user, optionally with a .png, .jpg, etc. appended. Controlling GDM You can control GDM behavior during runtime in several different ways. You can either run certain commands, or you can talk to GDM using either a unix socket protocol, or a FIFO protocol. Commands To stop GDM, you can either send the TERM signal to the main daemon or run the gdm-stop command which is in the sbin/ directory. To restart GDM, you can either send the HUP signal to the main daemon or run the gdm-restart command which is also in the sbin/ 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 gdm-safe-restart command which is in the sbin/ directory as well. The gdmflexiserver 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 gdmflexiserver 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 gdmflexiserver --help to get a listing of possible options. The FIFO protocol GDM also provides a FIFO called .gdmfifo in the ServAuthDir directory (usually var/gdm/.gdmfifo). 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). Full and up to date documentation of the commands and their use is contained in the GDM source tree in the file daemon/gdm.h. Look for the defines starting with GDM_SOP_. 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. Socket Protocol GDM provides a unix domain socket for communication at /tmp/.gdm_socket. 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 gdmflexiserver command uses this protocol, for example, to launch flexible (on-demand) displays. gdmflexiserver accepts the following commands with the --command option: VERSION AUTH_LOCAL FLEXI_XSERVER FLEXI_XNEST ATTACHED_SERVERS ALL_SERVERS GET_SERVER_LIST GET_SERVER_DETAILS GET_CONFIG GET_CONFIG_FILE UPDATE_CONFIG GREETERPIDS QUERY_LOGOUT_ACTION SET_LOGOUT_ACTION SET_SAFE_LOGOUT_ACTION QUERY_VT SET_VT CLOSE These are described in detail below, including required arguments, response format, and return codes. VERSION VERSION: Query GDM version Supported since: 2.2.4.0 Arguments: None Answers: GDM gdm version ERROR err number english error description 200 = Too many messages 999 = Unknown error AUTH_LOCAL AUTH_LOCAL: Setup this connection as authenticated for FLEXI_SERVER. Because all full blown (non-Xnest) displays can be started only from users logged in locally, and here GDM assumes only users logged in from GDM. They must pass the xauth MIT-MAGIC-COOKIE-1 that they were passed before the connection is authenticated. Note: The AUTH LOCAL command requires the --authenticate option, although only FLEXI XSERVER uses this currently. Note: Since 2.6.0.6 you can also use a global ServAuthDir/.cookie, which works for all authentication except for SET_LOGOUT_ACTION and QUERY_LOGOUT_ACTION and SET_SAFE_LOGOUT_ACTION which require a logged in display. Supported since: 2.2.4.0 Arguments: xauth cookie xauth cookie is in hex form with no 0x prefix Answers: OK ERROR err number english error description 0 = Not implemented 100 = Not authenticated 200 = Too many messages 999 = Unknown error FLEXI_XSERVER FLEXI_XSERVER: Start a new X flexible display. Only supported on connection that passed AUTH_LOCAL Supported since: 2.2.4.0 Arguments: xserver type If no arguments, starts the standard X server Answers: OK display ERROR err number english error description 0 = Not implemented 1 = No more flexi servers 2 = Startup errors 3 = X failed 4 = X too busy 6 = No server binary 100 = Not authenticated 200 = Too many messages 999 = Unknown error FLEXI_XNEST FLEXI_XNEXT: Start a new flexible Xnest display. Note: Supported on older version from 2.2.4.0, later 2.2.4.2, but since 2.3.90.4 you must supply 4 arguments or ERROR 100 will be returned. This will start Xnest using the XAUTHORITY file supplied and as the uid same as the owner of that file (and same as you supply). You must also supply the cookie as the third argument for this display, to prove that you indeed are this user. Also this file must be readable ONLY by this user, that is have a mode of 0600. If this all is not met, ERROR 100 is returned. Note: The cookie should be the MIT-MAGIC-COOKIE-1, the first one GDM can find in the XAUTHORITY file for this display. If that's not what you use you should generate one first. The cookie should be in hex form. Supported since: 2.3.90.4 Arguments: display to run on uid of requesting user xauth cookie for the display xauth file Answers: OK display ERROR err number english error description 0 = Not implemented 1 = No more flexi servers 2 = Startup errors 3 = X failed 4 = X too busy 5 = Xnest can't connect 6 = No server binary 100 = Not authenticated 200 = Too many messages 999 = Unknown error ADD_DYNAMIC_DISPLAY ADD_DYNAMIC_DISPLAY: Create a new server definition that will run on the specified display leaving, it in DISPLAY_CONFIG state. Supported since: 2.8.0.0 Arguments: display to run on=server Where server is either a configuration named in the GDM configuration or a literal command name. Answers: OK display ERROR err number english error description 0 = Not implemented 2 = Existing display 3 = No server string 4 = Display startup failure 100 = Not authenticated 200 = Dynamic Displays not allowed 999 = Unknown error RELEASE_DYNAMIC_DISPLAYS RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in DISPLAY_CONFIG state Supported since: 2.8.0.0 Arguments: None Answers: OK display ERROR err number english error description 0 = Not implemented 100 = Not authenticated 200 = Dynamic Displays not allowed 999 = Unknown error REMOVE_DYNAMIC_DISPLAY REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server and purging the display configuration Supported since: 2.8.0.0 Arguments: display to remove Answers: OK display ERROR err number english error description 0 = Not implemented 1 = Bad display number 100 = Not authenticated 200 = Dynamic Displays not allowed 999 = Unknown error ATTACHED_SERVERS ATTACHED_SERVERS: List all attached displays. Doesn't list XDMCP and xnest non-attached displays. Note: This command used to be named CONSOLE_SERVERS, which is still recognized for backwards compatibility. The optional pattern argument is supported as of version 2.8.0.0. Supported since: 2.2.4.0 Arguments: pattern (optional) With no argument, all attached displays are returned. The optional pattern is a string that may contain glob characters '*', '?', and '[]'. Only displays that match the pattern will be returned. Answers: OK server;server;... server is display,logged in user,vt or xnest display logged in user can be empty in case no one logged in yet, and vt can be -1 if it's not known or not supported (on non-Linux for example). If the display is an xnest display and is a console one (that is, it is an xnest inside another console display) it is listed and instead of vt, it lists the parent display in standard form. ERROR err number english error description 1 = Not implemented 200 = Too many messages 999 = Unknown error ALL_SERVERS ALL_SERVERS: List all displays, including console, remote, xnest. This can, for example, be useful to figure out if the display you are on is managed by the gdm daemon, by seeing if it is in the list. It is also somewhat like the 'w' command but for graphical sessions. Supported since: 2.4.2.96 Arguments: None Answers: OK server;server;... server is display,logged in user logged in user can be empty in case no one logged in yet ERROR err number english error description 0 = Not implemented 200 = Too many messages 999 = Unknown error GET_SERVER_LIST GET_SERVER_LIST: Get a list of the server sections from the configuration file. Supported since: 2.13.0.4 Arguments: None Answers: OK value;value;... ERROR err number english error description 0 = Not implemented 1 = No servers found 50 = Unsupported key 200 = Too many messages 999 = Unknown error GET_SERVER_DETAILS GET_SERVER_DETAILS: Get detail information for a specific server. Supported since: 2.13.0.4 Arguments: server key Key values include: NAME - Returns the server name COMMAND - Returns the server command FLEXIBLE - Returns true if flexible, false otherwise CHOOSABLE - Returns true if choosable, false otherwise HANDLED - Returns true if handled, false otherwise CHOOSER - Returns true if chooser, false otherwise PRIORITY - Returns process priority Answers: OK value ERROR err number english error description 0 = Not implemented 1 = Server not found 2 = Key not valid 50 = Unsupported key 200 = Too many messages 999 = Unknown error GET_CONFIG GET_CONFIG: Get configuration value for key. Useful so that other applications can request configuration information from GDM. Any key defined as GDM_KEY_* in gdm.h is supported. Starting with version 2.13.0.2 translated keys (such as greeter/GdmWelcome[cs] are supported via GET_CONFIG. Also starting with version 2.13.0.2 it is no longer necessary to include the default value (i.e. you can use key greeter/IncludeAll instead of having to use greeter/IncludeAll=false. Supported since: 2.6.0.9 Arguments: key Answers: OK value ERROR err number english error description 0 = Not implemented 50 = Unsupported key 200 = Too many messages 999 = Unknown error GET_CONFIG_FILE GET_CONFIG_FILE: Get config file location being used by the daemon. If the GDM daemon was started with the --config option, it will return the value passed in via the argument. Supported since: 2.8.0.2 Arguments: None Answers: OK full path to GDM configuration file ERROR err number english error description 0 = Not implemented 200 = Too many messages 999 = Unknown error UPDATE_CONFIG UPDATE_CONFIG: Tell the daemon to re-read a key from the GDM configuration file. Any user can request that values are re-read but the daemon will only do so if the file has been modified since GDM first read the file. Only users who can change the GDM configuration file (normally writable only by the root user) can actually modify the GDM configuration. This command is useful to cause the GDM to update itself to recognize a change made to the GDM configuration file by the root user. Starting with version 2.13.0.0, all GDM keys are supported except for the following: daemon/PidFile daemon/ConsoleNotify daemon/User daemon/Group daemon/LogDir daemon/ServAuthDir daemon/UserAuthDir daemon/UserAuthFile daemon/UserAuthFBDir GDM also supports the following Psuedokeys: xdmcp/PARAMETERS (2.3.90.2) updates the following: xdmcp/MaxPending xdmcp/MaxSessions xdmcp/MaxWait xdmcp/DisplaysPerHost xdmcp/HonorIndirect xdmcp/MaxPendingIndirect xdmcp/MaxWaitIndirect xdmcp/PingIntervalSeconds (only affects new connections) xservers/PARAMETERS (2.13.0.4) updates the following: all [server-foo] sections. Supported keys for previous versions of GDM: security/AllowRoot (2.3.90.2) security/AllowRemoteRoot (2.3.90.2) security/AllowRemoteAutoLogin (2.3.90.2) security/RetryDelay (2.3.90.2) security/DisallowTCP (2.4.2.0) daemon/Greeter (2.3.90.2) daemon/RemoteGreeter (2.3.90.2) xdmcp/Enable (2.3.90.2) xdmcp/Port (2.3.90.2) daemon/TimedLogin (2.3.90.3) daemon/TimedLoginEnable (2.3.90.3) daemon/TimedLoginDelay (2.3.90.3) greeter/SystemMenu (2.3.90.3) greeter/ConfigAvailable (2.3.90.3) greeter/ChooserButton (2.4.2.0) greeter/SoundOnLoginFile (2.5.90.0) daemon/AddGtkModules (2.5.90.0) daemon/GtkModulesList (2.5.90.0) Supported since: 2.3.90.2 Arguments: key key is just the base part of the key such as security/AllowRemoteRoot Answers: OK ERROR err number english error description 0 = Not implemented 50 = Unsupported key 200 = Too many messages 999 = Unknown error GREETERPIDS GREETERPIDS: List all greeter pids so that one can send HUP to them for config rereading. Of course one must be root to do that. Supported since: 2.3.90.2 Arguments: None Answers: OK pid;pid;... ERROR err number english error description 0 = Not implemented 200 = Too many messages 999 = Unknown error QUERY_LOGOUT_ACTION QUERY_LOGOUT_ACTION: Query which logout actions are possible Only supported on connections that passed AUTH_LOCAL. Supported since: 2.5.90.0 Answers: OK action;action;... Where action is one of HALT, REBOOT or SUSPEND. An empty list can also be returned if no action is possible. A '!' is appended to an action if it was already set with SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION. Note that SET_LOGOUT_ACTION has precedence over SET_SAFE_LOGOUT_ACTION. ERROR err number english error description 0 = Not implemented 100 = Not authenticated 200 = Too many messages 999 = Unknown error SET_LOGOUT_ACTION SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after slave process exits. Only supported on connections that passed AUTH_LOCAL. Supported since: 2.5.90.0 Arguments: action NONE Set exit action to 'none' HALT Set exit action to 'halt' REBOOT Set exit action to 'reboot' SUSPEND Set exit action to 'suspend' Answers: OK ERROR err number english error description 0 = Not implemented 7 = Unknown logout action, or not available 100 = Not authenticated 200 = Too many messages 999 = Unknown error SET_SAFE_LOGOUT_ACTION SET_SAFE_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after everybody logs out. If only one person logs out, then this is obviously the same as the SET_LOGOUT_ACTION. Note that SET_LOGOUT_ACTION has precedence over SET_SAFE_LOGOUT_ACTION if it is set to something other then NONE. If no one is logged in, then the action takes effect effect immediately. Only supported on connections that passed AUTH_LOCAL. Supported since: 2.5.90.0 Arguments: action NONE Set exit action to 'none' HALT Set exit action to 'halt' REBOOT Set exit action to 'reboot' SUSPEND Set exit action to 'suspend' Answers: OK ERROR err number english error description 0 = Not implemented 7 = Unknown logout action, or not available 100 = Not authenticated 200 = Too many messages 999 = Unknown error QUERY_VT QUERY_VT: Ask the daemon about which VT we are currently on. This is useful for logins which don't own /dev/console but are still console logins. Only supported on Linux currently, other places will just get ERROR 8. This is also the way to query if VT support is available in the daemon in the first place. Only supported on connections that passed AUTH_LOCAL. Supported since: 2.5.90.0 Arguments: None Answers: OK vt number ERROR err number english error description 0 = Not implemented 8 = Virtual terminals not supported 100 = Not authenticated 200 = Too many messages 999 = Unknown error SET_VT SET_VT: Change to the specified virtual terminal. This is useful for logins which don't own /dev/console but are still console logins. Only supported on Linux currently, other places will just get ERROR 8. Only supported on connections that passed AUTH_LOCAL. Supported since: 2.5.90.0 Arguments: vt Answers: OK ERROR err number english error description 0 = Not implemented 8 = Virtual terminals not supported 9 = Invalid virtual terminal number 100 = Not authenticated 200 = Too many messages 999 = Unknown error CLOSE CLOSE: Close sockets connection Supported since: 2.2.4.0 Arguments: None Answers: None GDM Commands GDM User Commands The GDM package provides the following different commands in EXPANDED_BINDIR intended to be used by the end-user: gdmXnestchooser and gdmXnest Command Line Options The gdmXnestchooser command automatically gets the correct display number, sets up access, and runs Xnest 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 gdmXnestchooser somehost will run the XDMCP chooser from host somehost inside an Xnest session. You can make this command do a direct query instead by passing the -d option as well. In addition to the following options, this command also supports standard GNOME options. gdmXnestchooser Command Line Options -x, --xnest=STRING Xnest command line, default is Xnest -o, --xnest-extra-options=OPTIONS Extra options for Xnest, default is no options. -n, --no-query Just run Xnest, no query (no chooser) -d, --direct Do direct query instead of indirect (chooser) -B, --broadcast Run broadcast instead of indirect (chooser) -b, --background Run in background --no-gdm-check Don't check for running GDM gdmflexichooser Command Line Options The gdmflexiserver 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. 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. 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. The gdmflexiserver --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. In addition to the following options, gdmflexiserver also supports standard GNOME options. gdmflexichooser Command Line Options -c, --command=COMMAND Send the specified protocol command to GDM -n, --xnest Start a flexible X display in Xnest mode -l, --no-lock Do not lock current screen -d, --debug Turns on debugging output which gets sent to syslog. Same as turning on debug in the configuration file. -a, --authenticate Authenticate before running --command -s, --startnew Starts a new flexible display without displaying a dialog asking the user if they wish to continue any existing sessions. gdmdynamic Command Line Options The gdmdynamic command which creates, runs, and removes displays (X servers) on demand. 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 gdmdynamic command can be used to create a new display on a particular display number, run all newly created displays, or remove a display. The gdmdynamic command can also be used to list all attached displays, or only attached displays that match a pattern. gdmdynamic Command Line Options One of the following options can be used per instance: -a display=server Add a new display configuration. For example, -a 2=StandardServerTwo -a 3=/usr/X11R6/bin/X -dev /dev/fb2 -r Release (run) all displays waiting in the DISPLAY_CONFIG state. -d display Delete a display, killing the X server and purging the display configuration. For example, -d 3. -l [pattern] 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: -l Standard* -l *Xorg* These options can be added to the above: -v Verbose mode. Prinr diagnostic messages about each message sent to GDM. -b Background mode. Fork child to do the work and return immediately. gdmphotosetup Command Line Options 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 ~/.face. This command accepts standard GNOME options. gdmthemetester Command Line Options gdmthemetester 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. gdmthemetester requires that the system support gdmXnest. Note that themes can display differently depending on the theme's Show mode. gdmthemetester allows viewing the themes in different modes via the environment option. Valid environment values and their meanings follow: 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. GDM Root User Commands The GDM package provides the following different commands in EXPANDED_SBINDIR intended to be used by the root user: gdm and gdm-binary Command Line Options The gdm command is really just a script which runs the gdm-binary, passing along any options. Before launching gdm-binary, the gdm wrapper script will source the etc/profile 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. gdm and gdm-binary Command Line Options --help Gives a brief overview of the command line options. -nodaemon If this option is specified, then GDM does not fork into the background when run. You can use just a single dash with this option to preserve compatibility with XDM. --no-console Tell the daemon that it should not run anything on the console. This means that none of the local servers from the [servers] section will be run, and the console will not be used for communicating errors to the user. An empty [servers] section automatically implies this option. --config=CONFIGFILE Specify an alternative configuration file. --preserve-ld-vars When clearing the environment internally, preserve all variables starting with LD_. This is mostly for debugging purposes. --version Print the version of the GDM daemon. --wait-for-go 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. gdmsetup Command Line Options gdmsetup 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 gdmsetup 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. gdm-restart Command Line Options gdm-restart 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. gdm-safe-restart Command Line Options gdm-safe-restart stops and restarts GDM by sending the GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out. gdm-stop Command Line Options gdm-stop stops GDM by sending the GDM daemon a TERM signal. GDM Internal Commands The GDM package provides the following different commands in EXPANDED_LIBEXECDIR intended to be used by the gdm daemon process. gdmchooser and gdmlogin Command Line Options The gdmgreeter and gdmlogin are two different login applications, either can be used by GDM. gdmgreeter is themeable with GDM themes while gdmlogin is themable with GTK+ themes. These applications are normally executed by the GDM daemon. Both commands support standard GNOME options. gdmchooser Command Line Options The gdmchooser is the XDMCP chooser application. The gdmchooser 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. gdmchooser Command Line Options -xdmaddress=SOCKET Socket for XDM communication. --clientaddress=ADDRESS Client address to return in response to XDM. This option is for running gdmchooser with XDM, and is not used within GDM. -connectionType=TYPE Connection type to return in response to XDM. This option is for running gdmchooser with XDM, and is not used within GDM. Themed Greeter This section describes the creation of themes for the Themed Greeter. For examples including screenshots, see the standard installed themes and the themes from the theme website. Theme Overview 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 share/gdm/themes/theme_name. Usually this would be under /usr/share. The theme directory should contain a file called GdmGreeterTheme.desktop which has similar format to other .desktop files and looks like: [GdmGreeterTheme] Encoding=UTF-8 Greeter=circles.xml Name=Circles Description=Theme with blue circles Author=Bond, James Bond Copyright=(c) 2002 Bond, James Bond Screenshot=screenshot.png The Name, Description, Author and Copyright fields can be translated just like the other .desktopfiles. All the files that are mentioned should be in the theme directory itself. The Screenshot field points to a file which should be a 200x150 screenshot of the theme in action (it is OK not to have one, but it makes it nicer for user). The Greeter field points to an XML file that contains the description of the theme. The description will be given later. Once you have theme ready and installed you can test it with the installed gdmthemetester 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: gdmthemetester xdmcp circles 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. Once you have all this done, then make a tarball that contains the directory name (so that you could just untar it in the /usr/share/gdm/themes directory). And this is the tarball you distribute and people can install from the graphical configuration application. You can do this with the commands: cd /usr/share/gdm/themes tar czvf theme_name.tar.gz theme_name/ Detailed Description of Theme XML format Box Nodes Box nodes are container nodes for item nodes. Box nodes are specified as follows: box orientation=alignment min-width=num xpadding=num ypadding=num spacing=num homogeneous=bool 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. If the box is homogeneous then the children are allocated equal amount of space. The min-width must be specified in pixels. Obviously there is also a corresponding min-height property as well. Fixed Nodes 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: fixed Then you put other items with proper position nodes inside this. The toplevel node is really just like a fixed node. Item Nodes A GDM Theme is created by specifying a hierarchy of item and box nodes. Item nodes can have the following value for type: entry Text entry field. list A list widget. label A text label. Must have a text node to specify the text. pixmap An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, etc...) rect Rectangle. svg Scaled Vector Graphic image. For example: item type=label 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) Entry items can have id values as follows: user-pw-entry Entry field for userid and password entry. This is the field used for responses for the PAM/GDM questions (Username, Password, etc..). List items can have id values as follows: userlist A Face Browser list, so that users can pick their username by clicking on this instead of typing. 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' Label items can have id values as follows: clock Label that displays the date and time. pam-prompt Label that displays the PAM prompt. This is the prompt that PAM uses to ask for username, password, etc... pam-error Label that displayst PAM/GDM error messages. Such as when user can't log in. pam-message 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. timed-label Label that displays timed login information. Rectangles can have id values as follows: caps-lock-warning Displays an icon that shows if the CAPS LOCK key is depressed. This rectangle will be hidden/shown appropriately If an item is of type rect, the item can be a button. Buttons must also include a button value as follows: item type=rect id=disconnect_button button=true. Possible values for button ids are as follows: chooser_button Runs the XDMCP chooser. config_button Runs the GDM configuration application. disconnect_button Disconnect from remote session. language_button Displays the language selection dialog. halt_button Halt (shuts down) the system. reboot_button Restart the system. session_button List and select from available sessions. suspend_button Suspend the system. system_button 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. Position Node Each item can specify its position and size via the pos node. For example: pos x=0 y=4 width=100% height=100%/ Both position and size can be given in percent and it will be taken as the percentage of the size of the current container. For toplevel items it's the percentage of the whole screen. 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. 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: pos x=10% y=50% anchor=w width=80% height=95/ 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. 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. 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). 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: item type=label pos x="10%" max-screen-percent-width="50%"/ Show Node 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: console - In console mode. console-fixed - In console non-flexi mode. console-flexi - In console flexi mode. flexi - In flexi mode. remote - In remote mode. remote-flexi - In remote flexi mode. For example: show modes=flexi,remote/ 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: chooser, if ChooserButton is set to true in the GDM configuration. config, if ConfigAvailable is set to true in the GDM configuration. halt, if HaltDaemon is specified in the GDM configuration. reboot, if RebootCommand is specified in the GDM configuration. suspend, if SuspendCommand is specified in the GDM configuration. system, if SystemMenu is specified in the GDM configuration. timed, if TimedLoginEnabled is set to true in the GDM configuration. For example: show modes=console type=system/ 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. Normal/Active/Prelight Nodes 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: normal - normal state. active - when the item has active focus. prelight - when the mouse is hovering over the item. When item is rect (alpha can be omitted and defaults to 0.0): normal color=#ffffff alpha=0.0 When item is label normal color=#ffffff font=Sans 14/ When the item type is pixmap or SVG, then the normal, active, and prelight tags specify the images to use as follows: normal file=picture.png tint=#dddddd/ Note that relative pathnames are assumed to be in the same directory as the theme .xml file in share/gdm/themes/theme_name. Face Browser Icon/Label Color Nodes 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: color iconcolor=#dddddd labelcolor=#ffffff/ Text Node 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): text xml:lang=frOption/text You can include pango markup in the text nodes for labels, however you must encode it. So for example to have the label of foosupbar/sup, you must type: textfoolt;supbarlt;/sup/text Text nodes can contain the following special character sequences which will be translated as follows: %% - A literal % character %c - Clock time. Only labels with the clock id will update automatically every second. Other labels will contain a static timestamp. %d - Display name (DISPLAY environment variable) %h - Hostname (gethostname output) %m - Machine name (uname.machine output) %n - Node name (uname.nodename output) %o - Domain name (getdomainname output) %r - Release name (uname.release output) %s - System name (uname.sysname output) %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. %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. \n - Carriage return _ - An underscore causes the following character to be underlined. If it precedes a % character sequence, the string that replaces the character sequence is underlined. Stock Certain common localized labels can be specified via the stock tags. The text tag is ignored if the stock tag is used. You should really use the stock labels rather then just putting all the translations into the themes. This gives faster load times and likely better translations. The following values are valid: cancel, _(_Cancel caps-lock-warning, _(You've got capslock on! chooser, _(_XDMCP Chooser disconnect, _(D_isconnect halt, _(Shut_down language, _(_Language ok, _(_OK quit, _(_Quit reboot, _(_Restart session, _(_Session suspend, _(Sus_pend system, _(_Actions (Formerly S_ystem timed-label, _(User %u will login in %t username-label, _(Username: welcome-label, _(Welcome to %n For example: stock type=welcome-label Custom Widgetry Currently there is one item which can be customizable and this is the list item. If you need to ask the user extra things, such as to pick from a list of places to log into, or set of custom login sessions you can setup the list item and add listitem children that describe the choices. Each listitem must have an id and a text child. The choice will be recorded in the file ServAuthDir/display.GreeterInfo as list id=listitem id. For example suppose we are on display :0, ServAuthDir is var/gdm and we have the following in the theme: item type=list id=custom-config pos anchor=nw x=1 y=1 height=200 width=100 listitem id=foo textFoo/text /listitem listitem id=bar textBar/text /listitem /item Then if the user chooses 'Foo' then var/gdm/:0.GreeterInfo will contain: custom-config=foo Accessibility 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. This feature allows the user to launch assistive technologies at login time by means of special gestures from the standard keyboard and from a keyboard, pointing device, or switch device attached to the USB or PS/2 mouse port. It also allows the user to change the visual appearance of the login UI before logging in, for instance to use a higher-contrast color scheme for better visibility. GDM only supports accessibility with the GTK+ Greeter, so the Greeter parameter in the GDM configuration must be set to the GTK+ Greeter gdmlogin Accessibility Configuration 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. In order to allow users to change the color and contrast scheme of the login dialog, make sure the AllowThemeChange parameter in the GDM configuration is set to true. To restrict user changes to the visual appearance to a subset of available themes, the GtkThemesToAllow parameter in the GDM configuration can be set to a list of acceptable themes separated by commas. For example: GtkThemesToAllow=HighContrast,HighContrastInverse To enable the use of assistive technologies such as the Onscreen Keyboard, Screen Reader, or Magnifier, the AddGtkModules parameter in the GDM configuration must be uncommented and set to true. Also the GtkModulesList parameter must be uncommented and set as follows: GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener 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. 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. 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. 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. 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. 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 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. 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. Accessibility Login Sound Configuration 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 /usr/bin/play (or /usr/bin/audioplay 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. Solaris Specific Features GDM supports a few features specific to Solaris, as follows: GDM supports Solaris Auditing if running on Solaris 10 or higher. 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. Solaris supports the /etc/default/login interface, which affects the DefaultPath, RootPath, PasswordRequired, and AllowRemoteRoot options as described in the Configuration section. Example Configurations This section has some example configurations that are useful for various setups. Terminal Lab With One Server 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 xterminal and let's call the server machine appserver. You install GDM on both. On appserver you enable XDMCP, so you have [xdmcp] Enable=true If you want no local screens here, you can then make the [servers] section empty. On the xterminal you disable XDMCP (you don't want anyone to connect to the xterminal really). You will add a server type perhaps called Terminal as follows: [server-Terminal] name=Terminal server command=/usr/X11R6/bin/X -terminate flexible=false handled=false This definition should in fact be included in the standard configuration file. Notice that we made the handled key false since we don't want GDM to handle this server localy. Also note that we have not yet added the -query argument, you can add that here, or in the [servers] section. We'll define our local servers as follows: [servers] 0=Terminal -query appserver This will run a direct XDMCP query to the server named appserver. Terminal Lab With Two Or More Servers Suppose you want to make a lab full of X terminals that all connect to some choice of servers. For now let's make it appserverone and appservertwo. Again we'll call our example X terminal server xterminal. The setup on both servers is the same as with the case of one server in the previous section. You do not need to explicitly enable indirect queries on the server since we'll run the choosers locally on the X terminals. So on the xterminal you again disable XDMCP. You will add a server type perhaps called Chooser as follows: [server-Chooser] name=Chooser server command=/usr/X11R6/bin/X flexible=false chooser=true And again this definition should in fact be included in the standard configuration file. Notice that we made the chooser 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: [servers] 0=Chooser 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 [chooser] section you would have: Hosts=appserverone,appservertwo and any other servers you wish the users to be able to connect to. 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 appserver and on the X terminals you'd have [servers] 0=Terminal -indirect appserver This way for example you only have to maintain one Hosts entry. However as a disadvantage then, the appserver must then always be available. So it's not good for situations where you want to have serveral 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. License This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. 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 GNU General Public License for more details. A copy of the GNU General Public License is included as an appendix to the GNOME Users Guide. You may also obtain a copy of the GNU General Public License from the Free Software Foundation by visiting their Web site or by writing to Free Software Foundation, Inc. 59 Temple Place - Suite 330 Boston, MA 02111-1307 USA</sect2></sect1></article> |