diff --git a/Makefile.am b/Makefile.am
index f91ad73..f1a6524 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -11,22 +11,13 @@ SUBDIRS = 			\
 	tests 			\
 	$(NULL)
 
-# add these when help gets added back
-# omf-install
-
 EXTRA_DIST = \
 	MAINTAINERS		\
 	ChangeLog		\
 	README			\
-	gnome-doc-utils.make	\
-	xmldocs.make		\
-	omf.make		\
 	$(NULL)
 
 DISTCLEANFILES = \
-	gnome-doc-utils.make	\
 	$(NULL)
 
-DISTCHECK_CONFIGURE_FLAGS = --disable-scrollkeeper
-
-distuninstallcheck_listfiles = find . -type f -print | grep -v '^\./var/scrollkeeper'
+DISTCHECK_CONFIGURE_FLAGS = --enable-split-authentication --enable-introspection
diff --git a/configure.ac b/configure.ac
index c25fdd7..af5f1bf 100644
--- a/configure.ac
+++ b/configure.ac
@@ -27,7 +27,7 @@ AC_CONFIG_MACRO_DIR([m4])
 
 IT_PROG_INTLTOOL([0.40.0])
 
-GNOME_DOC_INIT
+YELP_HELP_INIT
 
 GETTEXT_PACKAGE=gdm
 AC_SUBST(GETTEXT_PACKAGE)
diff --git a/docs/C/gdm.xml b/docs/C/gdm.xml
deleted file mode 100644
index c510301..0000000
--- a/docs/C/gdm.xml
+++ /dev/null
@@ -1,2265 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" 
-    "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
-    <!ENTITY legal SYSTEM "legal.xml">
-    <!ENTITY version "2.26.0"> 
-    <!ENTITY date    "02/10/2009"> 
-    <!ENTITY mdash   "&#8212;"> 
-    <!ENTITY percnt  "&#x0025;">
-]>
-
-<article id="index" lang="en">
-  <articleinfo>
-    <title>GNOME Display Manager Reference Manual</title>
-
-    <revhistory>
-      <revision>
-        <revnumber>0.0</revnumber>
-        <date>2008-09</date>
-      </revision>
-    </revhistory>
-
-    <abstract role="description">
-      <para>
-        GDM is the GNOME Display Manager, a graphical login program.
-      </para>
-    </abstract>
-
-    <authorgroup>
-      <author>
-        <firstname>Martin</firstname><othername>K.</othername>
-           <surname>Petersen</surname>
-        <affiliation>
-          <address><email>mkp@mkp.net</email></address>
-        </affiliation>
-      </author>
-      <author>
-        <firstname>George</firstname><surname>Lebl</surname>
-        <affiliation>
-          <address><email>jirka@5z.com</email></address>
-        </affiliation>
-      </author>
-      <author>
-        <firstname>Jon</firstname><surname>McCann</surname>
-        <affiliation>
-          <address><email>mccann@jhu.edu</email></address>
-        </affiliation>
-      </author>
-      <author>
-        <firstname>Ray</firstname><surname>Strode</surname>
-        <affiliation>
-          <address><email>rstrode@redhat.com</email></address>
-        </affiliation>
-      </author>
-      <author role="maintainer">
-        <firstname>Brian</firstname><surname>Cameron</surname>
-        <affiliation>
-          <address><email>Brian.Cameron@Oracle.COM</email></address>
-        </affiliation>
-      </author>
-    </authorgroup>
-    <copyright>
-      <year>1998</year>
-      <year>1999</year>
-      <holder>Martin K. Petersen</holder>
-    </copyright>
-    <copyright>
-      <year>2001</year>
-      <year>2003</year>
-      <year>2004</year>
-      <holder>George Lebl</holder>
-    </copyright>
-    <copyright>
-      <year>2003</year>
-      <year>2007</year>
-      <year>2008</year>
-      <holder>Red Hat, Inc.</holder>
-    </copyright>
-    <copyright>
-      <year>2003</year>
-       <year>2011</year>
-       <holder>Oracle and/or its affiliates. All rights reserved.</holder>
-    </copyright>
-
-    &legal;
-
-    <releaseinfo>
-       This manual describes version &version; of the GNOME Display Manager.
-       It was last updated on &date;.
-    </releaseinfo>  
-  </articleinfo>
-
-  <!-- ============= Preface ================================== -->
-
-  <sect1 id="preface">
-    <title>Terms and Conventions Used in This Manual</title>
-
-    <para>
-      This manual describes version &version; of the GNOME Display Manager.
-      It was last updated on &date;.
-    </para>  
-
-    <para>
-      Chooser - A program used to select a remote host for managing a
-      display remotely on the attached display (<command>gdm-host-chooser</command>).
-    </para>
-
-    <para>
-      FreeDesktop - The organization providing desktop standards, such as the
-      Desktop Entry Specification used by GDM.
-      <ulink type="http" url="http://www.freedesktop.org/">
-      http://www.freedesktop.org</ulink>.
-    </para>
-    <para>
-      GDM - GNOME Display Manager. Used to describe the software package as a
-      whole.
-    </para>
-
-    <para>
-      Greeter - The graphical login window (<command>gdm-simple-greeter</command>).
-    </para>
-
-    <para>
-      PAM - Pluggable Authentication Mechanism
-    </para>
-
-    <para>
-      XDMCP - X Display Manage Protocol
-    </para>
-
-    <para>
-      Xserver - An implementation of the X Window System.  For example the
-      Xorg Xserver provided by the X.org Foundation
-      <ulink type="http" url="http://www.x.org/">http://www.x.org</ulink>.
-    </para>
-
-    <para>
-      Paths that start with a word in angle brackets are relative to the
-      installation prefix. I.e. <filename>&lt;share&gt;/pixmaps/</filename>
-      refers to <filename>/usr/share/pixmaps</filename> if GDM was
-      configured with <command>--prefix=/usr</command>.
-    </para>
-  </sect1>
-
-  <!-- ============= Overview ================================= -->
-
-  <sect1 id="overview">
-    <title>Overview</title>
-
-    <sect2 id="introduction">
-      <title>Introduction</title>
-
-      <para> 
-        The GNOME Display Manager (GDM) is a display manager that implements
-        all significant features required for managing attached and remote
-        displays.  GDM was written from scratch and does not contain any XDM or
-        X Consortium code.
-      </para>
-
-      <para>
-        Note that GDM is configurable, and many configuration settings have
-        an impact on security. Issues to be aware of are highlighted in this
-        document.
-      </para> 
-
-      <para>
-        Please note that some Operating Systems configure GDM to behave
-        differently than the default values as described in this document.  If
-        GDM does not seem to behave as documented, then check to see if any 
-        related configuration may be different than described here.
-      </para>
-
-      <para>
-        For further information about GDM, refer to the project website at
-        <ulink type="http" url="http://www.gnome.org/projects/gdm/">
-        http://www.gnome.org/projects/gdm</ulink> and the project
-        Wiki <ulink type="http" url="http://live.gnome.org/GDM">
-        http://live.gnome.org/GDM</ulink>.
-      </para>
-
-      <para>
-        For discussion or queries about GDM, refer to the
-        <address><email>gdm-list@gnome.org</email></address> mail list.  This
-        list is archived, and is a good resource to check to seek answers to
-        common questions.  This list is archived at
-        <ulink type="http" url="http://mail.gnome.org/archives/gdm-list/">
-        http://mail.gnome.org/archives/gdm-list/</ulink> and has a search
-        facility to look for messages with keywords.
-      </para>
-
-      <para>
-        Please submit any bug reports or enhancement requests to the
-        "gdm" category in
-        <ulink type="http" url="http://bugzilla.gnome.org/">
-        http://bugzilla.gnome.org</ulink>.
-      </para>
-    </sect2>
-
-    <sect2 id="stability">
-      <title>Interface Stability</title>
-
-      <para>
-        GDM 2.20 and earlier supported stable configuration interfaces.
-        However, the codebase was completely rewritten for GDM 2.22, and
-        is not completely backward compatible with older releases. This is
-        in part because things work differently, so some options just don't
-        make sense, in part because some options never made sense, and in
-        part because some functionality has not been reimplemented yet.
-      </para>
-
-      <para>
-        Interfaces which continue to be supported in a stable fashion include
-        the Init, PreSession, PostSession, PostLogin, and Xsession scripts.
-        Some daemon configuration options in the 
-        <filename>&lt;etc&gt;/gdm/custom.conf</filename> file continue to be
-        supported.  Also, the <filename>~/.dmrc</filename>, and face browser
-        image locations are still supported.
-      </para>
-
-      <para>
-        GDM 2.20 and earlier supported the ability to manage multiple displays
-        with separate graphics cards, such as used in terminal server
-        environments, login in a window via a program like Xnest or Xephyr, the
-        gdmsetup program, XML-based greeter themes, and the ability to run the
-        XDMCP chooser from the login screen.  These features were not 
-        added back during the 2.22 rewrite.
-      </para>
-
-    </sect2>
-
-    <sect2 id="functionaldesc">
-      <title>Functional Description</title>
-
-<!--
-<para>
-        TODO - Would be good to discuss D-Bus, perhaps the new GObject model,
-               and to explain the reasons why the rewrite made GDM better.
-               From a high-level overview perspective, rather than the
-               technical aspects.
-</para>
--->
-
-      <para>
-        GDM is responsible for managing displays on the system.  This includes
-        authenticating users, starting the user session, and terminating the
-        user session.  GDM is configurable and the ways it can be configured
-        are described in the "Configuring GDM" section of this
-        document.  GDM is also accessible for users with disabilities.
-      </para>
-
-      <para>
-        GDM provides the ability to manage the main console display, and 
-        displays launched via VT.  It is integrated with other programs, 
-        such as the Fast User Switch Applet (FUSA) and gnome-screensaver
-        to manage multiple displays on the console via the Xserver Virtual
-        Terminal (VT) interface.  It also can manage XDMCP displays.  
-      </para>
-
-      <para>
-        Regardless of the display type, GDM will do the following when it
-        manages the display.  It will start an Xserver process, then run the
-        <filename>Init</filename> script as the root user, and start the
-        greeter program on the display.
-      </para>
-
-      <para>
-        The greeter program is run as the unprivileged "gdm"
-        user/group.  This user and group are described in the
-        "Security" section of this document.  The main function of
-        the greeter program is to authenticate the user.  The authentication
-        process is driven by Pluggable Authentication Modules (PAM).  The PAM
-        modules determine what prompts (if any) are shown to the user to
-        authenticate.  On the average system, the greeter program will request
-        a username and password for authentication.  However some systems may
-        be configured to use alternative mechanisms such as a fingerprint or
-        SmartCard reader.  GDM and PAM can be configured to not require any
-        input, which will cause GDM to automatically log in and simply
-        start a session, which can be useful for some environments, such as
-        for kiosks.
-      </para>
-
-      <para>
-        In addition to authentication, the greeter program allows the user to
-        select which session to start and which language to use.  Sessions are
-        defined by files that end in the .desktop suffix and more information
-        about these files can be found in the "GDM User Session and Language
-        Configuration" section of this document.  By default, GDM is configured
-        to display a face browser so the user can select their user account by
-        clicking on an image instead of having to type their username. GDM
-        keeps track of the user's default session and language in the user's
-        <filename>~/.dmrc</filename> and will use these defaults if the user
-        did not pick a session or language in the login GUI.
-      </para>
-
-      <para> 
-        After authenticating a user, the daemon runs the
-        <filename>PostLogin</filename> script as root, then runs the  
-        <filename>PreSession</filename> script as root.  After running these
-        scripts, the user session is started.  When the user exits their 
-        session, the <filename>PostSession</filename> script is run as root.
-        These scripts are provided as hooks for distributions and end-users
-        to customize how sessions are managed.  For example, using these 
-        hooks you could set up a machine which creates the user's $HOME
-        directory on the fly, and erases it on logout.  The difference 
-        between the <filename>PostLogin</filename> and
-        <filename>PreSession</filename> scripts is that
-        <filename>PostLogin</filename> is run before the pam_open_session call
-        so is the right place to do anything which should be run before the
-        user session is initialized.  The <filename>PreSession</filename>
-        script is called after session initialization.
-      </para>
-    </sect2>
-
-    <sect2 id="greeterpanel">
-      <title>Greeter Panel</title>
-      <para>
-        The GDM greeter program displays a panel docked at the bottom of the
-        screen which provides additional functionality.  When a user is
-        selected, the panel allows the user to select which session, language,
-        and keyboard layout to use after logging in.  The keyboard layout
-        selector also changes the keyboard layout used when typing your
-        password.  The panel also contains an area for login services to leave
-        status icons.  Some example status icons include a battery icon for
-        current battery usage, and an icon for enabling accessibility features.
-        The greeter program also provides buttons which allow the user to
-        shutdown or restart the system.  It is possible to configure GDM to not
-        provide the shutdown and restart buttons, if desired.  GDM can also be
-        configured via PolicyKit (or via RBAC on Oracle Solaris) to require the
-        user have appropriate authorization before accepting the shutdown or
-        restart request.
-      </para>
-
-      <para>
-        Note that keyboard layout features are only available on systems that
-        support libxklavier.
-      </para>
-    </sect2>
-
-    <sect2 id="accessibility">
-      <title>Accessibility</title>
-
-        <para>
-          GDM supports "Accessible Login", allowing users to log into
-          their desktop session even if they cannot easily use the screen,
-          mouse, or keyboard in the usual way.  Accessible Technology (AT)
-          features such as an on-screen keyboard, screen reader, screen
-          magnifier, and Xserver AccessX keyboard accessibility are available.
-          It is also possible to enable large text or high contrast icons and
-          controls, if needed.  Refer to the "Accessibility
-          Configuration" section of the document for more information
-          how various accessibility features can be configured.
-        </para>
-
-        <para>
-          On some Operating Systems, it is necessary to make sure that the GDM
-          user is a member of the "audio" group for AT programs that
-          require audio output (such as text-to-speech) to be functional.
-        </para>
-    </sect2>
-
-    <sect2 id="facebrowser">
-      <title>The GDM Face Browser</title>
-
-      <para>
-        The Face Browser is the interface which allows users to select their
-        username by clicking on an image.  This feature can be enabled or
-        disabled via the /apps/gdm/simple-greeter/disable_user_list GConf
-        key and is on by default.  When disabled, users must type their
-        complete username by hand.  When enabled, it displays all local users
-        which are available for login on the system (all user accounts defined
-        in the /etc/passwd file that have a valid shell and sufficiently high
-        UID) and remote users that have recently logged in.
-        The face browser in GDM 2.20 and earlier would attempt to display all
-        remote users, which caused performance problems in large,
-        enterprise deployments.
-      </para>
-
-      <para>
-        The Face Browser is configured to display the users who log in most
-        frequently at the top of the list.  This helps to ensure that users
-        who log in frequently can quickly find their login image.
-      </para>
-
-      <para>
-        The Face Browser supports "type-ahead search" which dynamically
-        moves the face selection as the user types to the corresponding username
-        in the list.  This means that a user with a long username will only
-        have to type the first few characters of the username before the correct
-        item in the list gets selected.
-      </para>
-
-      <para>
-        The icons used by GDM can be installed globally by the sysadmin or can
-        be located in the user's home directories.  If installed globally
-        they should be in the <filename>&lt;share&gt;/pixmaps/faces/</filename>
-        directory and the filename should be the name of the user.  Face image
-        files should be a standard image that GTK+ can read, such as PNG or
-        JPEG.  Face icons placed in the global face directory must be readable
-        to the GDM user.
-      </para>
-
-<!--
-<para>
-        TODO - In the old GDM the ~/gnome2/gdm file is used, but the new code
-               seems to use ~/.gnome/gdm.  Error?
-</para>
--->
-      <para>
-        If there is no global icon for the user, GDM will look in the user's
-        $HOME directory for the image file.  GDM will first look for the user's
-        face image in <filename>~/.face</filename>.  If not found, it will try 
-        <filename>~/.face.icon</filename>.  If still not found, it will use the
-        value defined for "face/picture=" in the 
-        <filename>~/.gnome2/gdm</filename> file.
-      </para>
-
-      <para>
-        If a user has no defined face image, GDM will use the
-        "stock_person" icon defined in the current GTK+ theme.  If no
-        such image is defined, it will fallback to a generic face image.
-      </para>
-
-      <para>
-        Please note that loading and scaling face icons located in remote user
-        home directories can be a very time-consuming task.  Since it not
-        practical to load images over NIS or NFS, GDM does not attempt to load
-        face images from remote home directories.
-      </para>
-
-      <para>
-        When the browser is turned on, valid usernames on the computer are
-        exposed for everyone to see.  If XDMCP is enabled, then the usernames
-        are exposed to remote users.  This, of course, limits security
-        somewhat since a malicious user does not need to guess valid usernames.
-        In some very restrictive environments the face browser may not be
-        appropriate.
-      </para>
-
-    </sect2>
-
-    <sect2 id="xdmcp">
-      <title>XDMCP</title>
-
-<!--
-<para>
-        TODO - What XDMCP features actually work?   I know that the
-               chooser is missing.
-</para>
--->
-
-      <para>
-        The GDM daemon can be configured to listen for and manage X Display
-        Manage Protocol (XDMCP) requests from remote displays.  By default
-        XDMCP support is turned off, but can be enabled if desired.  If GDM is
-        built with TCP Wrapper support, then the daemon will only grant access
-        to hosts specified in the GDM service section in the TCP Wrappers
-        configuration file.
-      </para>
-
-      <para>
-        GDM includes several measures making it more resistant to denial of
-        service attacks on the XDMCP service.  A lot of the protocol
-        parameters, handshaking timeouts, etc. can be fine tuned. The default
-        configuration should work reasonably on most systems. 
-      </para>
-
-      <para>
-        GDM by default listens for XDMCP requests on the normal UDP port used
-        for XDMCP, port 177, and will respond to QUERY and BROADCAST_QUERY
-        requests by sending a WILLING packet to the originator.
-      </para>
-
-      <para>
-        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 forward subsequent requests to the chosen manager.  GDM
-        also supports an extension to the protocol which will make it forget
-        the redirection once the user's connection succeeds.  This extension
-        is only supported if both daemons are GDM.  It is transparent and
-        will be ignored by XDM or other daemons that implement XDMCP.
-      </para>
-
-      <para>
-        If XDMCP seems to not be working, make sure that all machines are
-        specified in <filename>/etc/hosts</filename>.
-      </para>
-
-      <para>
-        Refer to the "Security" section for information about
-        security concerns when using XDMCP.
-      </para>
-    </sect2>
-
-    <sect2 id="logging">
-      <title>Logging</title>
-
-      <para>
-        GDM uses syslog to log errors and status.  It can also log debugging
-        information, which can be useful for tracking down problems if GDM is
-        not working properly.  Debug output can be enabled by setting the
-        debug/Enable key to &quot;true&quot; in the
-        <filename>&lt;etc&gt;/gdm/custom.conf</filename> file.
-      </para>
-
-      <para>
-        Output from the various Xservers is stored in the GDM log directory,
-        which is normally <filename>&lt;var&gt;/log/gdm/</filename>.  Any
-        Xserver messages are saved to a file associated with the display value,
-        <filename>&lt;display&gt;.log</filename>.  
-      </para>
-
-      <para>
-        The session output is piped through the GDM daemon to the
-        <filename>~/.xsession-errors</filename> file.  The file is overwritten
-        on each login, so logging out and logging back into the same user via
-        GDM will cause any messages from the previous session to be lost.
-      </para>
-
-      <para>
-        Note that if GDM can not create this file for some reason, then a
-        fallback file will be created named <filename>~/.xsession-errors.XXXXXXXX</filename>
-        where the <filename>XXXXXXXX</filename> are some random characters.
-      </para>
-    </sect2>
-
-    <sect2 id="fusa">
-      <title>Fast User Switching</title>
-
-      <para>
-        GDM allows multiple users to be logged in at the same time.  After one
-        user is logged in, additional users can log in via the User Switcher
-        on the GNOME Panel, or from the "Switch User" button in Lock Screen dialog
-        of GNOME Screensaver.  The active session can be changed back and forth using
-        the same mechanism.  Note that some distributions may not add the User Switcher
-        to the default panel configuration.  It can be added using the panel context
-        menu.
-      </para>
-      <para>
-        Note this feature is available on systems that support Virtual
-        Terminals.  This feature will not function if Virtual Terminals is not
-        available.
-      </para>
-    </sect2>
-  </sect1>
-
-  <!-- ============= Security ================================= -->
-
-  <sect1 id="security">
-    <title>Security</title>
-
-    <sect2 id="gdmuser">
-      <title>The GDM User And Group</title>
-
-      <para>
-        For security reasons a dedicated user and group id are recommended for
-        proper operation.  This user and group are normally "gdm" on
-        most systems, but can be configured to any user or group.  All GDM
-        GUI programs are run as this user, so that the programs which interact
-        with the user are run in a sandbox.  This user and group should have
-        limited privilege.
-      </para>
-
-      <para>
-        The only special privilege the "gdm" user requires is the
-        ability to read and write Xauth files to the
-        <filename>&lt;var&gt;/run/gdm</filename> directory.  The
-        <filename>&lt;var&gt;/run/gdm</filename> directory should have
-        root:gdm ownership and 1777 permissions.
-      </para>
-
-      <para>
-        You should not, under any circumstances, configure the GDM user/group
-        to a user which a user could easily gain access to, such as the user
-        <filename>nobody</filename>.  Any user who gains access to an Xauth
-        key can snoop on and control running GUI programs running in the
-        associated session or perform a denial-of-service attack on it.  It
-        is important to ensure that the system is configured properly so that
-        only the "gdm" user has access to these files and that it
-        is not easy to login to this account.  For example, the account should
-        be setup to not have a password or allow non-root users to login to the
-        account.
-      </para>
-
-      <para>
-        The GDM greeter configuration is stored in GConf.  To allow the GDM
-        user to be able to write configuration, it is necessary for the 
-        "gdm" user to have a writable $HOME directory.  Users may
-        configure the default GConf configuration as desired to avoid the 
-        need to provide the "gdm" user with a writable $HOME
-        directory.  However, some features of GDM may be disabled if it is
-        unable to write state information to GConf configuration.
-      </para>
-    </sect2>
-
-    <sect2 id="PAM">
-      <title>PAM</title>
-
-      <para>
-        GDM uses PAM for login authentication.  PAM stands for Pluggable
-        Authentication Module, and is used by most programs that request
-        authentication on your computer.  It allows the administrator to
-        configure specific authentication behavior for different login programs
-        (such as ssh, login GUI, screensaver, etc.)
-      </para>
-
-      <para>
-        PAM is complicated and highly configurable, and this documentation does
-        not intend to explain this in detail.  Instead, it is intended to give
-        an overview of how PAM configuration relates with GDM, how PAM is
-        commonly configured with GDM, and known issues.  It is expected that
-        a person needing to do PAM configuration would need to do further
-        reading of PAM documentation to understand how to configure PAM and
-        to understand terms used in this section.
-      </para>
-        
-      <para>
-        PAM configuration has different, but similar, interfaces on different
-        Operating Systems, so check the
-        <ulink type="help" url="man:pam.d">pam.d</ulink> or
-        <ulink type="help" url="man:pam.conf">pam.conf</ulink> man page for
-        details.  Be sure you read the PAM documentation and are comfortable
-        with the security implications of any changes you intend to make to
-        your configuration.
-      </para>
-
-      <para>
-        Note that, by default, GDM uses the "gdm" PAM service name
-        for normal login and the "gdm-autologin" PAM service name for
-        automatic login.  These services may not be defined in your pam.d or
-        pam.conf configured file.  If there is no entry, then GDM will use the
-        default PAM behavior.  On most systems this should work fine.
-        However, the automatic login feature may not work if the gdm-autologin
-        service is not defined.
-      </para>
-
-      <para>
-        The <filename>PostLogin</filename> script is run before
-        pam_open_session is called, and the <filename>PreSession</filename>
-        script is called after.  This allows the system administrator to add
-        any scripting to the login process either before or after PAM 
-        initializes the session.
-      </para>
-
-      <para>
-        If you wish to make GDM work with other types of authentication
-        mechanisms (such as a fingerprint or SmartCard reader), then you should
-        implement this by using a PAM service module for the desired
-        authentication type rather than by trying to modify the GDM code
-        directly.  Refer to the PAM documentation on your system.  How to do
-        this is frequently discussed on the 
-        <address><email>gdm-list@gnome.org</email></address> mail list,
-        so you can refer to the list archives for more information.
-      </para>
-
-      <para>
-        PAM does have some limitations regarding being able to work with 
-        multiple types of authentication at the same time, like supporting
-        the ability to accept either SmartCard and the ability to type the
-        username and password into the login program.  There are techniques
-        that are used to make this work, and it is best to research how this
-        problem is commonly solved when setting up such a configuration.
-      </para>
-
-      <para>
-        If automatic login does not work on a system, check to see if the
-        "gdm-autologin" PAM stack is defined in the PAM configuration.  For
-        this to work, it is necessary to use a PAM module that simply does no
-        authentication, or which simply returns PAM_SUCCESS from all of its
-        public interfaces.  Assuming your system has a pam_allow.so PAM module
-        which does this, a PAM configuration to enable "gdm-autologin" would
-        look like this:
-      </para>
-
-<screen>
-       gdm-autologin auth  required    pam_unix_cred.so.1
-       gdm-autologin auth  sufficient  pam_allow.so.1
-       gdm-autologin account  sufficient  pam_allow.so.1
-       gdm-autologin session  sufficient  pam_allow.so.1
-       gdm-autologin password  sufficient  pam_allow.so.1
-</screen>
-
-      <para>
-        The above setup will cause no lastlog entry to be generated.  If a
-        lastlog entry is desired, then use the following for the session:
-      </para>
-
-<screen>
-       gdm-autologin session required pam_unix_session.so.1
-</screen>
-
-      <para>
-        If the computer is used by several people, which makes automatic login
-        unsuitable, you may want to allow some users to log in without entering
-        their password. This feature can be enabled as a per-user option in
-        the users-admin tool from the gnome-system-tools; it is achieved by
-        checking that the user is member a Unix group called
-        "nopasswdlogin" before asking for a password. For this to work,
-        the PAM configuration file for the "gdm" service must include
-        a line such as:
-      </para>
-
-<screen>
-      gdm auth  sufficient  pam_succeed_if.so  user ingroup nopasswdlogin
-</screen>
-
-    </sect2>
-
-    <sect2 id="utmpwtmp">
-      <title>utmp and wtmp</title>
-
-      <para>
-        GDM generates utmp and wtmp User Accounting Database entries upon
-        session login and logout.  The utmp database contains user access
-        and accounting information that is accessed by commands such as
-        <command>finger</command>, <command>last</command>,
-        <command>login</command>, and <command>who</command>.  The wtmp
-        database contains the history of user access and accounting 
-        information for the utmp database.  Refer to the 
-        <ulink type="help" url="man:utmp">utmp</ulink> and
-        <ulink type="help" url="man:wtmp">wtmp</ulink>
-        man pages on your system for more information.
-      </para>
-    </sect2>
-
-    <sect2 id="xauth">
-      <title>Xserver Authentication Scheme</title>
-
-      <para>
-        Xserver authorization files are stored in a newly created subdirectory
-        of <filename>&lt;var&gt;/run/gdm</filename> at start up.  These files
-        are used to store and share a "password" between X clients
-        and the Xserver.  This "password" is unique for each session
-        logged in, so users from one session can't snoop on users from another.
-      </para>
-
-      <para>
-        GDM only supports the MIT-MAGIC-COOKIE-1 Xserver 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 Xserver 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.  In most cases,
-        ssh -Y should be preferred over GDM's XDMCP features.
-      </para>
-
-    </sect2>
-
-    <sect2 id="xdmcpsecurity">
-      <title>XDMCP Security</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.  This type of set up
-        should never use an unmanaged hub or other sniffable network.
-      </para>
-
-    </sect2>
-
-    <sect2 id="xdmcpaccess">
-      <title>XDMCP Access Control</title>
-
-      <para>
-        XDMCP access control is done using TCP wrappers.  It is possible to
-        compile GDM without TCP wrapper support, so this feature may not be
-        supported on some Operating Systems.
-      </para>
-
-      <para>
-        You should use the daemon name <command>gdm</command> in the
-        <filename>&lt;etc&gt;/hosts.allow</filename> and
-        <filename>&lt;etc&gt;/hosts.deny</filename> files.  For example to 
-        deny computers from <filename>.evil.domain</filename> from logging in,
-        then add
-      </para>
-<screen>
-gdm: .evil.domain
-</screen>
-      <para>
-        to <filename>&lt;etc&gt;/hosts.deny</filename>.  You may also need
-        to add
-      </para>
-<screen>
-gdm: .your.domain
-</screen>
-      <para>
-        to your <filename>&lt;etc&gt;/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.
-      </para>
-    </sect2>
-
-    <sect2 id="firewall">
-      <title>Firewall Security</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 really needed.  GDM
-        guards against 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 do a denial of service attack via XDMCP than attacking a
-        webserver.
-      </para>
-
-      <para>
-        It is also wise to block all of the Xserver ports.  These are TCP
-        ports 6000+ (one for each display number) 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 when using it over the Internet, and
-         XDMCP is even less safe.
-      </para>
-    </sect2>
-
-    <sect2 id="policykit">
-      <title>PolicyKit</title>
-
-<!--
-<para>
-        TODO - Should we say more?
-</para>
--->
-
-      <para>
-        GDM may be configured to use PolicyKit to allow the system
-        administrator to control whether the login screen should provide
-        the shutdown and restart buttons on the greeter screen.
-      </para>
-
-      <para>
-        These buttons are controlled by the
-        <filename>org.freedesktop.consolekit.system.stop-multiple-users</filename>
-        and
-        <filename>org.freedesktop.consolekit.system.restart-multiple-users</filename>
-        actions respectively.  Policy for these actions can be set up using the
-        polkit-gnome-authorization tool, or the polkit-auth command line program.
-      </para>
- 
-    </sect2>
-
-    <sect2 id="rbac">
-      <title>RBAC (Role Based Access Control)</title>
-
-      <para>
-        GDM may be configured to use RBAC instead of PolicyKit.  In this
-        case the RBAC configuration is used to control whether the login screen
-        should provide the shutdown and restart buttons on the greeter screen.
-      </para>
-
-      <para>
-        For example, on Oracle Solaris, the "solaris.system.shutdown"
-        authorization is used to control this.  Simply modify the 
-        <filename>/etc/user_attr</filename> file so that the "gdm"
-        user has this authorization.
-      </para>
-    </sect2>
-
-  </sect1>
-
-  <!-- ============= ConsoleKit ================================ -->
-
-  <sect1 id="consolekit">
-    <title>Support for ConsoleKit</title>
-
-<!--
-<para>
-    TODO - Should we update these docs?  Probably should mention any 
-           configuration that users may want to do for using it with GDM?
-           If so, perhaps this section should be moved to a subsection of
-           the "Configure" section?
-</para>
--->
-
-    <para>
-      GDM includes support for publishing user login information with the user
-      and login session accounting framework known as ConsoleKit.  ConsoleKit
-      is able to keep track of all the users currently logged in.  In this
-      respect, it can be used as a replacement for the utmp or utmpx files that
-      are available on most Unix-like Operating Systems.
-    </para>
-
-    <para>
-      When GDM is about to create a new login process for a user it will call
-      a privileged method of ConsoleKit in order to open a new session for this
-      user.  At this time GDM also provides ConsoleKit with information about
-      this user session such as: the user ID, the X11 Display name that will be
-      associated with the session, the host-name from which the session
-      originates (useful in the case of an XDMCP session), whether or not this
-      session is attached, etc.  As the entity that initiates the user process,
-      GDM is in a unique position to know about the user session and to be 
-      trusted to provide these bits of information. The use of this privileged 
-      method is restricted by the use of the D-Bus system message bus security 
-      policy.
-    </para>
-
-    <para>
-      In case a user with an existing session has authenticated
-      at GDM and requests to resume that existing session, GDM calls a
-      privileged method of ConsoleKit to unlock that session.  The exact
-      details of what happens when the session receives this unlock signal are
-      undefined and session-specific.  However, most sessions will unlock a
-      screensaver in response.
-    </para>
-
-    <para>
-      When the user chooses to log out, or if GDM or the session quit
-      unexpectedly the user session will be unregistered from ConsoleKit.
-    </para>
-  </sect1>
-
-  <!-- ============= Configuration ============================= -->
-
-  <sect1 id="configuration">
-    <title>Configuration</title>
-
-    <para>
-      GDM has a number of configuration interfaces.  These include scripting
-      integration points, daemon configuration, greeter configuration, 
-      general session settings, integration with gnome-settings-daemon
-      configuration, and session configuration.  These types of integration are
-      described in detail below.
-    </para>
-
-    <sect2 id="scripting">
-      <title>Scripting Integration Points</title>
-      
-      <para>
-        The GDM script integration points can be found in the
-        <filename>&lt;etc&gt;/gdm/</filename> directory:
-      </para>
-
-<screen>
-Xsession
-Init/
-PostLogin/
-PreSession/
-PostSession/
-</screen>
-
-      <para>
-        The <filename>Init</filename>, <filename>PostLogin</filename>,
-        <filename>PreSession</filename>, and <filename>PostSession</filename>
-        scripts all work as described below.
-      </para>
-
-      <para>
-        For each type of script, the default one which will be executed is
-        called "Default" and is stored in a directory associated with
-        the script type.  So the default <filename>Init</filename> script is 
-        <filename>&lt;etc&gt;/gdm/Init/Default</filename>.  A per-display
-        script can be provided, and if it exists it will be run instead of the 
-        default script.  Such scripts are stored in the same directory as the
-        default script and have the same name as the Xserver DISPLAY value for
-        that display.  For example, if the <filename>&lt;Init&gt;/:0</filename>
-        script exists, it will be run for DISPLAY ":0".
-     </para>
-
-     <para>
-        All of these scripts are run with root privilege and return 0 if run
-        successfully, and a non-zero return code if there was any failure that
-        should cause the login session to be aborted.  Also note that GDM will
-        block until the scripts finish, so if any of these scripts hang, this
-        will cause the login process to also hang.
-      </para>
-
-      <para>
-        When the Xserver for the login GUI has been successfully started, but
-        before the login GUI is actually displayed, GDM will run the
-        <filename>Init</filename> script.  This script is useful for starting
-        programs that should be run while the login screen is showing, or for
-        doing any special initialization if required.
-      </para>
-
-      <para>
-        After the user has been successfully authenticated GDM will run the
-        <filename>PostLogin</filename> script.  This is done before any session
-        setup has been done, including before the pam_open_session call.  This
-        script is useful for doing any session initialization that needs to
-        happen before the session starts.  For example, you might setup the
-        user's $HOME directory if needed.
-      </para>
-
-      <para>
-        After the user session has been initialized, GDM will run the
-        <filename>PreSession</filename> script.  This script is useful for
-        doing any session initialization that needs to happen after the 
-        session has been initialized.  It can be used for session management or
-        accounting, for example.
-      </para>
-
-      <para> 
-        When a user terminates their session, GDM will run the
-        <filename>PostSession</filename> script.  Note that the Xserver will
-        have been stopped by the time this script is run, so it should not be
-        accessed.  
-      </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>
-        All of the above scripts will set the
-        <filename>$RUNNING_UNDER_GDM</filename> environment variable to
-        <filename>yes</filename>.  If the scripts are also shared with other
-        display managers, this allows you to identify when GDM is calling these
-        scripts, so you can run specific code when GDM is used.
-      </para>
-    </sect2>
-
-    <sect2 id="autostart">
-      <title>Autostart Configuration</title>
-      
-      <para>
-        The <filename>&lt;share&gt;/gdm/autostart/LoginWindow</filename>
-        directory contains files in the format specified by the
-        "FreeDesktop.org Desktop Application Autostart
-        Specification".  Standard features in the specification may be
-        used to specify programs that should auto-restart or only be launched
-        if a GConf configuration value is set, etc.
-      </para>
-
-      <para>
-        Any <filename>.desktop</filename> files in this directory will cause
-        the associated program to automatically start with the login GUI
-        greeter.  By default, GDM is shipped with files which will autostart
-        the gdm-simple-greeter login GUI greeter itself, the
-        gnome-power-manager application, the gnome-settings-daemon, and the
-        metacity window manager.  These programs are needed for the greeter
-        program to work.  In addition, desktop files are provided for starting
-        various AT programs if the configuration values specified in the
-        Accessibility Configuration section below are set.
-      </para>
-    </sect2>
-
-    <sect2 id="xsessionscript">
-      <title>Xsession Script</title>
-
-      <para>
-        There is also an <filename>Xsession</filename> script located at
-        <filename>&lt;etc&gt;/gdm/Xsession</filename> which is called between
-        the <filename>PreSession</filename> and the
-        <filename>PostSession</filename> scripts.  This script does not
-        support per-display like the other scripts.  This script is used for
-        actually starting the user session.  This script is run as the user,
-        and it will run whatever session was specified by the Desktop session
-        file the user selected to start. 
-      </para>
-    </sect2>
-
-    <sect2 id="daemonconfig">
-      <title>Daemon Configuration</title>
-
-      <para>
-        The GDM daemon is configured using the
-        <filename>&lt;etc&gt;/gdm/custom.conf</filename> file.  Default
-        values are stored in GConf in the <filename>gdm.schemas</filename>
-        file.  It is recommended that end-users modify the
-        <filename>&lt;etc&gt;/gdm/custom.conf</filename> file because the
-        schemas file may be overwritten when the user updates their system to
-        have a newer version of GDM.
-      </para>
-
-      <para>
-        Note that older versions of GDM supported additional configuration
-        options which are no longer supported in the latest versions of GDM.
-      </para>
-
-      <para>
-        The <filename>&lt;etc&gt;/gdm/custom.conf</filename> file is in the
-        <filename>keyfile</filename> format.  Keywords in brackets
-        define group sections, strings before an equal sign (=) are keys and
-        the data after equal sign represents their value.  Empty lines or
-        lines starting with the hash mark (#) are ignored.  
-      </para>
-
-      <para>
-        The file <filename>&lt;etc&gt;/gdm/custom.conf</filename> supports the
-        "[daemon]", "[security]", and "[xdmcp]"
-        group sections.  Within each group, there are particular key/value
-        pairs that can be specified to modify how GDM behaves.  For example,
-        to enable timed login and specify the timed login user to be a user
-        named "you", you would modify the file so it contains the
-        following lines:
-      </para>
-     
-<screen>
-[daemon]
-TimedLoginEnable=true
-TimedLogin=you
-</screen>
-
-      <para>
-        A full list of supported configuration keys follow:
-      </para>
-
-      <sect3 id="choosersection">
-        <title>[chooser]</title>
-        <variablelist>
-
-          <varlistentry>
-            <term>Multicast</term>
-            <listitem>
-              <synopsis>Multicast=false</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.
-              </para>
-            </listitem>
-          </varlistentry>
-         
-          <varlistentry>
-            <term>MulticastAddr</term>
-            <listitem>
-              <synopsis>MulticastAddr=ff02::1</synopsis>
-              <para>
-                This is the Link-local multicast address.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </sect3>
-
-      <sect3 id="daemonsection">
-        <title>[daemon]</title>
-        <variablelist>
-          <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.  Refer to the "Security->PAM"
-                section of the manual for more information, or for help if this
-                feature does not seem to work.
-              </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.
-              </para>
-              <para>
-                If the value ends with a vertical bar | (the pipe symbol),
-                then GDM will execute the program specified and use whatever
-                value is returned on standard out from the program as the user.
-                The program is run with the DISPLAY environment variable set so
-                that it is possible to specify the user in a per-display
-                fashion.  For example if the value is "/usr/bin/getloginuser|",
-                then the program "/usr/bin/getloginuser" will be run to get the
-                user value.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>TimedLoginDelay</term>
-            <listitem>
-              <synopsis>TimedLoginDelay=30</synopsis>
-              <para>
-                Delay in seconds before the <filename>TimedLogin</filename>
-                user will be logged in.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>AutomaticLoginEnable</term>
-            <listitem>
-              <synopsis>AutomaticLoginEnable=false</synopsis>
-              <para>
-                If true, the user given in <filename>AutomaticLogin</filename>
-                should be logged in immediately. This feature is like timed
-                login with a delay of 0 seconds.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>AutomaticLogin</term>
-            <listitem>
-              <synopsis>AutomaticLogin=</synopsis>
-              <para>
-                This is the user that should be logged in immediately if
-                <filename>AutomaticLoginEnable</filename> is true.
-              </para>
-              <para>
-                If the value ends with a vertical bar | (the pipe symbol),
-                then GDM will execute the program specified and use whatever
-                value is returned on standard out from the program as the user.
-                The program is run with the DISPLAY environment variable set so
-                that it is possible to specify the user in a per-display
-                fashion.  For example if the value is "/usr/bin/getloginuser|",
-                then the program "/usr/bin/getloginuser" will be run to get the
-                user value.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>User</term>
-            <listitem>
-              <synopsis>User=gdm</synopsis>
-              <para>
-                The username under which the greeter and other GUI programs
-                are run.  Refer to the <filename>Group</filename>
-                configuration key and to the "Security->GDM User And
-                Group" section of this document for more information.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>Group</term>
-            <listitem>
-              <synopsis>Group=gdm</synopsis>
-              <para>
-                The group name under which the greeter and other GUI programs
-                are run.  Refer to the <filename>User</filename>
-                configuration key and to the "Security->GDM User And
-                Group" section of this document for more information.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </sect3>
-
-      <sect3 id="debugsection">
-        <title>Debug Options</title>
-      
-        <variablelist>
-          <title>[debug]</title>
-          
-          <varlistentry>
-            <term>Enable</term>
-            <listitem>
-              <synopsis>Enable=false</synopsis>
-              <para>
-                To enable debugging, set the debug/Enable key to
-                &quot;true&quot; in the
-                <filename>&lt;etc&gt;/gdm/custom.conf</filename>
-                file and restart GDM.  Then debug output will be sent to the
-                system log file (<filename>&lt;var&gt;/log/messages</filename>
-                or <filename>&lt;var&gt;/adm/messages</filename> depending on
-                your Operating System).
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </sect3>
-
-      <sect3 id="greetersection">
-        <title>Greeter Options</title>
-      
-        <variablelist>
-          <title>[greeter]</title>
-          
-          <varlistentry>
-            <term>IncludeAll</term>
-            <listitem>
-              <synopsis>IncludeAll=true</synopsis>
-              <para>
-                If true, then the face browser will show all users on the local
-                machine.  If false, the face browser will only show users who
-                have recently logged in.
-              </para>
-
-              <para>
-                When this key is true, GDM will call fgetpwent() to get a list
-                of local users on the system.  Any users with a user id less
-                than 500 (or 100 if running on Oracle Solaris) are filtered
-                out.  The Face Browser also will display any users that have
-                previously logged in on the system  (for example NIS/LDAP
-                users).  It gets this list via calling the
-                <command>ck-history</command> ConsoleKit interface.  It will
-                also filter out any users which do not have a valid shell
-                (valid shells are any shell that getusershell() returns -
-                /sbin/nologin or /bin/false are considered invalid shells even
-                if getusershell() returns them).
-              </para>
-
-              <para>
-                If false, then GDM more simply only displays users that have
-                previously logged in on the system (local or NIS/LDAP users) by
-                calling the <command>ck-history</command> ConsoleKit interface.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>Include</term>
-            <listitem>
-              <synopsis>Include=</synopsis>
-              <para>
-                Set to a list of users to always include in the Face Browser.
-                This value is set to a list of users separated by commas.  By
-                default, the value is empty.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>Exclude</term>
-            <listitem>
-              <synopsis>Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap</synopsis>
-              <para>
-                Set to a list of users to always exclude in the Face Browser.
-                This value is set to a list of users separated by commas.  Note
-                that the setting in the <filename>custom.conf</filename>
-                overrides the default value, so if you wish to add additional
-                users to the list, then you need to set the value to the
-                default value with additional users appended to the list.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </sect3>
-
-      <sect3 id="securitysection">
-        <title>Security Options</title>
-      
-        <variablelist>
-          <title>[security]</title>
-          
-          <varlistentry>
-            <term>DisallowTCP</term>
-            <listitem>
-              <synopsis>DisallowTCP=true</synopsis>
-              <para>
-                If true, then always append <filename>-nolisten tcp</filename>
-                to the command line when starting attached Xservers, thus
-                disallowing TCP connection.  This is a more secure
-                configuration if you are not using remote connections.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </sect3>
-
-      <sect3 id="xdmcpsection">
-        <title>XDCMP Support</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 this value.
-              </para>
-
-              <para>
-                Note that the number of attached DISPLAYS allowed is not 
-                limited.  Only remote connections via XDMCP are limited by
-                this configuration option.
-              </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>&lt;etc&gt;/hosts.allow</filename>, depending
-                on your TCP Wrappers configuration.  See the
-                <ulink type="help" url="man:hosts.allow">hosts.allow</ulink>
-                man page for details.
-              </para>
-              
-              <para>
-                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.
-              </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 do not
-                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>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>PingIntervalSeconds</term>
-            <listitem>
-              <synopsis>PingIntervalSeconds=60</synopsis>
-              <para>
-                If the Xserver does not respond in the specified number of
-                seconds, then the connection is stopped and the session ended.
-                When this happens the slave daemon dies with an ALARM signal.
-                Note that GDM 2.20 and earlier multiplied this setting by 2,
-                so it may be necessary to increase the timeout if upgrading
-                from GDM 2.20 and earlier to a newer version.
-              </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 than 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>Port</term>
-            <listitem>
-              <synopsis>Port=177</synopsis>
-              <para>
-                The UDP port number <filename>gdm</filename> should listen to
-                for XDMCP requests. Do not change this unless you know what
-                you are doing.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>Willing</term>
-            <listitem>
-              <synopsis>Willing=&lt;etc&gt;/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 does not 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>
-    </sect2>
-
-    <sect2 id="greeterconfiguration">
-        <title>Simple Greeter Configuration</title>
-
-        <para>
-          The GDM default greeter is called the simple Greeter and is
-          configured via GConf.  Default values are stored in GConf in the
-          <filename>gdm-simple-greeter.schemas</filename> file.  These defaults
-          can be overridden if the "gdm" user has a writable $HOME
-          directory to store GConf settings.  These values can be edited using
-          the <command>gconftool-2</command> or <command>gconf-editor</command>
-          programs.  The following configuration options are supported:
-        </para>
-
-        <variablelist>
-          <title>Greeter Configuration Keys</title>
-
-          <varlistentry>
-            <term>/apps/gdm/simple-greeter/banner_message_enable</term>
-            <listitem>
-              <synopsis>false (boolean)</synopsis>
-              <para>
-                Controls whether the banner message text is displayed.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>/apps/gdm/simple-greeter/banner_message_text</term>
-            <listitem>
-              <synopsis>NULL (string)</synopsis>
-              <para>
-                Specifies the text banner message to show on the greeter
-                window.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>/apps/gdm/simple-greeter/disable_restart_buttons</term>
-            <listitem>
-              <synopsis>false (boolean)</synopsis>
-              <para>
-                Controls whether to show the restart buttons in the login
-                window.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>/apps/gdm/simple-greeter/disable_user_list</term>
-            <listitem>
-              <synopsis>false (boolean)</synopsis>
-              <para>
-                If true, then the face browser with known users is not shown
-                in the login window.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>/apps/gdm/simple-greeter/logo_icon_name</term>
-            <listitem>
-              <synopsis>computer (string)</synopsis>
-              <para>
-                Set to the themed icon name to use for the greeter logo.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>/apps/gdm/simple-greeter/recent-languages</term>
-            <listitem>
-              <synopsis>[] (string list)</synopsis>
-              <para>
-                Set to a list of languages to be shown by default in the login
-                window.  Default value is "[]".  With the default setting only
-                the system default language is shown and the option "Other..."
-                which pops-up a dialog box showing a full list of available
-                languages which the user can select.
-              </para>
-
-              <para>
-                Users are not intended to change this setting by hand.  Instead
-                GDM keeps track of any languages selected in this configuration
-                key, and will show them in the language combo box along with
-                the "Other..." choice.  This way, commonly selected languages
-                are easier to select.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>/apps/gdm/simple-greeter/recent-layouts</term>
-            <listitem>
-              <synopsis>[] (string list)</synopsis>
-              <para>
-                Set to a list of keyboard layouts to be shown by default in the
-                login panel.  Default value is "[]".  With the default setting
-                only the system default keyboard layout is shown and the option
-                "Other..." which pops-up a dialog box showing a full list of
-                available keyboard layouts which the user can select.
-              </para>
-
-              <para>
-                Users are not intended to change this setting by hand.  Instead
-                GDM keeps track of any keyboard layouts selected in this
-                configuration key, and will show them in the keyboard layout
-                combo box along with the "Other..." choice.  This way, commonly
-                selected keyboard layouts are easier to select.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>/apps/gdm/simple-greeter/wm_use_compiz</term>
-            <listitem>
-              <synopsis>false (boolean)</synopsis>
-              <para>
-                Controls whether compiz is used as the window manager instead
-                of metacity.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-    </sect2>
-
-    <sect2 id="accessibilityconfiguration">
-     <title>Accessibility Configuration</title>
-
-      <para>
-       This section describes the accessibility configuration options available
-       in GDM.
-      </para>
-
-      <sect3 id="accessibilitydialog">
-        <title>GDM Accessibility Dialog And GConf Keys</title>
-
-        <para>
-         The GDM greeter panel at the login screen displays an accessibility
-         icon.  Clicking on that icon opens the GDM Accessibility Dialog.  In
-         the GDM Accessibility Dialog, there is a list of checkboxes, so the
-         user can enable or disable the associated assistive tools.
-        </para>
-
-        <para>
-         The checkboxes that correspond to the on-screen keyboard, screen
-         magnifier and screen reader assistive tools act on the three GConf
-         keys that are described in the next section of this document. By
-         enabling or disabling these checkboxes, the associated GConf key is
-         set to "true" or "false".  When the GConf key is set to true, the 
-         assistive tools linked to this GConf key are launched.  When the 
-         GConf key is set to "false", any running assistive tool linked to
-         this GConf key are terminated.  These GConf keys are not automatically
-         reset to a default state after the user has logged in.  Consequently,
-         the assistive tools that were running during the last GDM login
-         session will automatically be launched at the next GDM login session.
-        </para>
-
-        <para>
-         The other checkboxes in the GDM Accessibility Dialog do not have
-         corresponding GConf keys because no additional program is launched to
-         provide the accessibility features that they offer.  These other
-         options correspond to accessibility features that are provided by the
-         Xserver, which is always running during the GDM session.
-        </para>
-      </sect3>
-
-      <sect3 id="accessibilitygconfconfiguration">
-        <title>Accessibility GConf Keys</title>
-
-        <para>
-         GDM offers the following GConf keys to control its accessibility
-         features:
-        </para>
-
-        <variablelist>
-          <title>GDM Configuration Keys</title>
-
-          <varlistentry>
-            <term>/desktop/gnome/interface/accessibility</term>
-            <listitem>
-              <synopsis>false (boolean)</synopsis>
-              <para>
-                Controls whether the Accessibility infrastructure will be
-                started with the GDM GUI.  This is needed for many
-                accessibility technology programs to work.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>/desktop/gnome/applications/at/screen_magnifier_enabled</term>
-            <listitem>
-              <synopsis>false (boolean)</synopsis>
-              <para>
-                If set, then the assistive tools linked to this GConf key will
-                be started with the GDM GUI program.  By default this is a
-                screen magnifier application.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>/desktop/gnome/applications/at/screen_keyboard_enabled</term>
-            <listitem>
-              <synopsis>false (boolean)</synopsis>
-              <para>
-                If set, then the assistive tools linked to this GConf key will
-                be started with the GDM GUI program.  By default this is an
-                on-screen keyboard application.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>/desktop/gnome/applications/at/screen_reader_enabled</term>
-            <listitem>
-              <synopsis>false (boolean)</synopsis>
-              <para>
-                If set, then the assistive tools linked to this GConf key will
-                be started with the GDM GUI program.  By default this is a
-                screen reader application.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </sect3>
-
-      <sect3 id="accessibilitytoolsconfiguration">
-        <title>Linking GConf Keys to Accessbility Tools</title>
-
-        <para>
-         For the screen_magnifier_enabled, the screen_keyboard_enabled, and the
-         screen_reader_enabled GConf keys, the assistive tool which gets
-         launched depends on the desktop files located in the GDM autostart
-         directory as described in the "Autostart Configuration" section of
-         this manual.  Any desktop file in the GDM autostart directory can be
-         linked to these GConf key via specifying that GConf key in the
-         AutostartCondition value in the desktop file.  So the exact
-         AutostartCondition line in the desktop file could be one of the
-         following:
-        </para>
-
-<screen>
-AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled
-AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled
-AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled
-</screen>
-
-        <para>
-         When an accessibility key is true, then any program which is linked to
-         that key in a GDM autostart desktop file will be launched (unless the
-         Hidden key is set to true in that desktop file).  A single GConf key
-         can even start multiple assistive tools if there are multiple desktop
-         files with this AutostartCondition in the GDM autostart directory.
-        </para>
-      </sect3>
-
-      <sect3 id="accessibilitytoolexample">
-        <title>Example Of Modifying Accessibility Tool Configuration</title>
-
-        <para>
-         For example, if GNOME is distributed with GOK as the default on-screen
-         keyboard, then this could be replaced with a different program if
-         desired.  To replace GOK with the on-screen keyboard application
-         "onboard" and additionally activate the assistive tool "mousetweaks"
-         for dwelling support, then the following configuration is needed.
-        </para>
-
-        <para>
-         Create a desktop file for onboard and a second one for mousetweaks;
-         for example, onboard.desktop and mousetweaks.desktop. These files
-         must be placed in the GDM autostart directory and be in the format
-         as explained in the "Autostart Configuration" section of this
-         document.
-        </para>
-
-        <para>
-         The following is an example <filename>onboard.desktop</filename> file:
-        </para>
-
-<screen>
-[Desktop Entry]
-Encoding=UTF-8
-Name=Onboard Onscreen Keyboard
-Comment=Use an on-screen keyboard
-TryExec=onboard
-Exec=onboard --size 500x180 -x 20 -y 10
-Terminal=false
-Type=Application
-StartupNotify=true
-Categories=GNOME;GTK;Accessibility;
-AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled
-</screen>
-
-        <para>
-         The following is an example <filename>mousetweaks.desktop</filename>
-         file:
-        </para>
-
-<screen>
-[Desktop Entry]
-Encoding=UTF-8
-Name=Software Mouse-Clicks
-Comment=Perform clicks by dwelling with the pointer
-TryExec=mousetweaks
-Exec=mousetweaks --enable-dwell -m window -c -x 20 -y 240 
-Terminal=false
-Type=Application
-StartupNotify=true
-Categories=GNOME;GTK;Accessibility;
-AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled
-</screen>
-
-        <para>
-         Note the line with the AutostartCondition that links both desktop
-         files to the GConf key for the on-screen keyboard.
-        </para>
-
-        <para>
-         To disable GOK from starting, the desktop file for the GOK on-screen
-         keyboard must be removed or deactivated.  Otherwise onboard and GOK
-         would simultaneously be started.  This can be done by removing the
-         gok.desktop file from the GDM autostart directory, or by adding the
-         "Hidden=true" key setting to the gok.desktop file.
-        </para>
-
-        <para>
-         After making these changes, GOK will no longer be started when the
-         user activates the on-screen keyboard in the GDM session; but onboard
-         and mousetweaks will instead be launched.
-        </para>
-      </sect3>
-    </sect2>
-
-    <sect2 id="generalsessionconfig">
-      <title>General Session Settings</title>
-<!--
-<para>
-          TODO - I think this section should be expanded upon.  What specific
-                 keys are of interest, or would some users be likely to want
-                 to configure?  Also, would be good to be more specific about
-                 how lock down management is handled.
-</para>
--->
-        <para>
-          The GDM Greeter uses some of the same framework that your desktop
-          session will use. And so, it is influenced by a number of the same
-          GConf settings. For each of these settings the Greeter will use the
-          default value unless it is specifically overridden by a) GDM's
-          installed mandatory policy b) system mandatory policy. GDM installs
-          its own mandatory policy to lock down some settings for security.
-        </para>
-    </sect2>
-
-    <sect2 id="gnomesettingsdaemon">
-      <title>GNOME Settings Daemon</title>
-<!--
-<para>
-          TODO - I think this section should be expanded upon.  What specific
-                 keys are of interest, or would some users be likely to want
-                 to configure?  Also, would be good to give a more complete
-                 list of plugins that users might want to consider disabling.
-                 Also, shouldn't we list the sound/active key in the Greeter
-                 configuration setting?  Oddly I do not find this key used
-                 in anything but the chooser in SVN.
-</para>
--->
-
-        <para>
-          GDM enables the following gnome-settings-daemon plugins:
-          a11y-keyboard, background, sound, xsettings.
-        </para>
-
-        <para>
-          These are responsible for things like the background image, font and
-          theme settings, sound events, etc.
-        </para>
-
-        <para>
-          Plugins can also be disabled using GConf. For example, if you want to
-          disable the sound plugin then unset the following key:
-          <filename>/apps/gdm/simple-greeter/settings-manager-plugins/sound/active</filename>.
-        </para>
-    </sect2>
-
-    <sect2 id="sessionconfig">
-      <title>GDM Session Configuration</title>
-
-      <para>
-        GDM sessions are specified using the FreeDesktop.org Desktop Entry
-        Specification, which can be referenced at the following URL:
-        <ulink url="http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec">
-        http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec</ulink>.
-      </para>
-
-      <para>
-        By default, GDM will install desktop files in the
-        <filename>&lt;share&gt;/xsessions</filename> directory.  GDM will
-        search the following directories in this order to find desktop files:
-        <filename>&lt;etc&gt;/X11/sessions/</filename>,
-        <filename>&lt;dmconfdir&gt;/Sessions</filename>, 
-        <filename>&lt;share&gt;/xsessions</filename>, and
-        <filename>&lt;share&gt;/gdm/BuiltInSessions</filename>.  By default the
-        <filename>&lt;dmconfdir&gt;</filename> is set to
-        <filename>&lt;etc&gt;/dm/</filename> unless GDM is configured to use
-        a different directory via the "--with-dmconfdir" option.
-      </para>
-
-      <para>
-        A session can be disabled by editing the desktop file and adding a line
-        as follows: <filename>Hidden=true</filename>.
-      </para>
-
-      <para>
-        GDM desktop files support a GDM-specific extension, a key named
-        &quot;X-GDM-BypassXsession&quot;.  If the key is not specified in a
-        desktop file, the value defaults to &quot;false&quot;.  If this key is
-        specified to be &quot;true&quot; in a desktop file, then GDM will
-        launch the program specified by the desktop file &quot;Exec&quot; key
-        directly when starting the user session.  It will not run the program
-        via the <filename>&lt;etc&gt;/gdm/Xsession</filename> script, which is
-        the normal behavior.  Since bypassing the
-        <filename>&lt;etc&gt;/gdm/Xsession</filename> script avoids setting up
-        the user session with the normal system and user settings, sessions
-        started this way can be useful for debugging problems in the system or
-        user scripts that might be preventing a user from being able to start
-        a session.
-      </para>
-
-    </sect2>
-
-    <sect2 id="userconfig">
-      <title>GDM User Session and Language Configuration</title>
-      <para>
-        The user's default session and language choices are stored in the
-        <filename>~/.dmrc</filename> file.  When a user logs in for the first
-        time, this file is created with the user's initial choices.  The user
-        can change these default values by simply changing to a different value
-        when logging in.  GDM will remember this change for subsequent logins.
-      </para>
-
-      <para>
-        The <filename>~/.dmrc</filename> file is in the standard
-        <filename>INI</filename> format.  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.
-        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>
-    </sect2>
-
-  </sect1>
-
-  <!-- ============= GDM Commands ============================= -->
-
-  <sect1 id="binaries">
-    <title>GDM Commands</title>
-
-    <sect2 id="sbindir_binaries">
-      <title>GDM Root User Commands</title>
-
-      <para>
-        The GDM package provides the following commands in
-        <filename>sbindir</filename> intended to be run 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>&lt;etc&gt;/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.  The <command>gdm-binary</command> is the actual GDM daemon.
-        </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>--fatal-warnings</term>
-            <listitem>
-              <para>
-                Make all warnings cause GDM to exit.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>--timed-exit</term>
-            <listitem>
-              <para>
-                Exit after 30 seconds.  Useful for debugging.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>--version</term>
-            <listitem>
-              <para>
-                Print the version of the GDM daemon.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </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>
-  </sect1>
-
-  <!-- ============= Troubleshooting =========================== -->
-
-  <sect1 id="troubleshooting">
-    <title>Troubleshooting</title>
-<!--
-<para>
-      TODO - any other tips we should add?  Might be useful to highlight any
-             common D-Bus configuration issues?
-</para>
--->
-
-    <para>
-      This section discusses helpful tips for getting GDM working.  In general,
-      if you have a problem using GDM, you can submit a bug or send an email
-      to the gdm-list mailing list.  Information about how to do this is in
-      the Introduction section of the document.
-    </para>
-
-    <para>
-      If GDM is failing to work properly, it is always a good idea to include
-      debug information.  To enable debugging, set the debug/Enable key to
-      &quot;true&quot; in the <filename>&lt;etc&gt;/gdm/custom.conf</filename>
-      file and restart GDM.  Then use GDM to the point where it fails, and
-      debug output will be sent to the system log file
-      (<filename>&lt;var&gt;/log/messages</filename> or
-      <filename>&lt;var&gt;/adm/messages</filename> depending on your Operating
-      System).  If you share this output with the GDM community via a bug
-      report or email, please only include the GDM related debug information
-      and not the entire file since it can be large.  If you do not see any
-      GDM syslog output, you may need to configure syslog (refer to the
-      <ulink type="help" url="man:syslog">syslog</ulink> man page).
-    </para>
-
-    <sect2 id="wontstart">
-      <title>GDM Will Not Start</title>
-
-      <para>
-         There are a many problems that can cause GDM to fail to start, but
-         this section will discuss a few common problems and how to approach
-         tracking down a problem with GDM starting.   Some problems will 
-         cause GDM to respond with an error message or dialog when it tries
-         to start, but it can be difficult to track down problems when GDM
-         fails silently.
-      </para>
-
-      <para>
-         First make sure that the Xserver is configured properly.  The 
-         GDM configuration file contains a command in the [server-Standard]
-         section that is used for starting the Xserver.  Verify that this
-         command works on your system.  Running this command from the 
-         console should start the Xserver.  If it fails, then the problem
-         is likely with your Xserver configuration.  Refer to your Xserver
-         error log for an idea of what the problem may be.  The problem may
-         also be that your Xserver requires different command-line options.
-         If so, then modify the Xserver command in the GDM configuration file
-         so that it is correct for your system.
-      </para>
-
-      <para>
-         Also make sure that the <filename>/tmp</filename> directory has
-         reasonable ownership and permissions, and that the machine's file
-         system is not full.  These problems will cause GDM to fail to start.
-      </para>
-    </sect2>
-  </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>51 Franklin Street, Fifth Floor</street>
-      <city>Boston</city>, <state>MA</state> <postcode>02110-1301</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:
--->               
diff --git a/docs/Makefile.am b/docs/Makefile.am
index 709043e..d0bb4f7 100644
--- a/docs/Makefile.am
+++ b/docs/Makefile.am
@@ -1,11 +1,10 @@
-include $(top_srcdir)/gnome-doc-utils.make
-dist-hook: doc-dist-hook
+@YELP_HELP_RULES@
 
-DOC_MODULE = gdm
-DOC_ENTITIES = legal.xml
-DOC_INCLUDES =
-DOC_LINGUAS = de el en_GB es fr it ko oc ru sv uk zh_CN
-# ja zh_HK zh_TW need to be transitioned to gnome-doc-utils
+HELP_ID = gdm
+
+HELP_FILES = \
+       index.docbook   \
+       legal.xml
+
+HELP_LINGUAS = ca de el en_GB es fr gl id it ko oc ru sl sv te uk zh_CN
 
-#man_MANS = gdm.1
-#EXTRA_DIST = gdm.1
diff --git a/docs/gdm.omf.in b/docs/gdm.omf.in
deleted file mode 100644
index 106f669..0000000
--- a/docs/gdm.omf.in
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" standalone="no"?>
-<omf>
-  <resource>
-    <subject category="GNOME|Applications|System Tools"/>
-    <type>
-      user's guide
-    </type>
-    <relation seriesid="04d4eadb-48ec-0cc0-6cfb-b23c6efee183f0"/>
-    <rights type="GNU FDL" license.version="1.1" holder="Sun Microsystems, Inc."/>
-  </resource>
-</omf>
diff --git a/omf.make b/omf.make
deleted file mode 100644
index 734f6d9..0000000
--- a/omf.make
+++ /dev/null
@@ -1,61 +0,0 @@
-# 
-# No modifications of this Makefile should be necessary.
-#
-# This file contains the build instructions for installing OMF files.  It is
-# generally called from the makefiles for particular formats of documentation.
-#
-# Note that you must configure your package with --localstatedir=/var
-# so that the scrollkeeper-update command below will update the database
-# in the standard scrollkeeper directory.
-#
-# If it is impossible to configure with --localstatedir=/var, then
-# modify the definition of scrollkeeper_localstate_dir so that
-# it points to the correct location. Note that you must still use 
-# $(localstatedir) in this or when people build RPMs it will update
-# the real database on their system instead of the one under RPM_BUILD_ROOT.
-#
-# Note: This make file is not incorporated into xmldocs.make because, in
-#       general, there will be other documents install besides XML documents
-#       and the makefiles for these formats should also include this file.
-#
-# About this file:
-#	This file was derived from scrollkeeper_example2, a package
-#	illustrating how to install documentation and OMF files for use with
-#	ScrollKeeper 0.3.x and 0.4.x.  For more information, see:
-#		http://scrollkeeper.sourceforge.net/	
-# 	Version: 0.1.3 (last updated: March 20, 2002)
-#
-
-omf_dest_dir=$(datadir)/omf/@PACKAGE@
-scrollkeeper_localstate_dir = $(localstatedir)/scrollkeeper
-
-# At some point, it may be wise to change to something like this:
-# scrollkeeper_localstate_dir = @SCROLLKEEPER_STATEDIR@
-
-omf: omf_timestamp
-
-omf_timestamp: $(omffile)
-	-for file in $(omffile); do \
-	  scrollkeeper-preinstall $(docdir)/$(docname).xml $(srcdir)/$$file $$file.out; \
-	done; \
-	touch omf_timestamp
-
-install-data-hook-omf:
-	$(mkinstalldirs) $(DESTDIR)$(omf_dest_dir)
-	for file in $(omffile); do \
-		$(INSTALL_DATA) $$file.out $(DESTDIR)$(omf_dest_dir)/$$file; \
-	done
-	-scrollkeeper-update -p $(scrollkeeper_localstate_dir) -o $(DESTDIR)$(omf_dest_dir)
-
-uninstall-local-omf:
-	-for file in $(srcdir)/*.omf; do \
-		basefile=`basename $$file`; \
-		rm -f $(DESTDIR)$(omf_dest_dir)/$$basefile; \
-	done
-	-rmdir $(DESTDIR)$(omf_dest_dir)
-	-scrollkeeper-update -p $(scrollkeeper_localstate_dir)
-
-clean-local-omf:
-	-for file in $(omffile); do \
-		rm -f $$file.out; \
-	done
diff --git a/xmldocs.make b/xmldocs.make
deleted file mode 100644
index 84d0f2b..0000000
--- a/xmldocs.make
+++ /dev/null
@@ -1,95 +0,0 @@
-#
-# No modifications of this Makefile should be necessary.
-#
-# To use this template:
-#     1) Define: figdir, docname, lang, omffile, and entities in
-#        your Makefile.am file for each document directory,
-#        although figdir, omffile, and entities may be empty
-#     2) Make sure the Makefile in (1) also includes 
-#	 "include $(top_srcdir)/xmldocs.make" and
-#	 "dist-hook: app-dist-hook".
-#     3) Optionally define 'entities' to hold xml entities which
-#        you would also like installed
-#     4) Figures must go under $(figdir)/ and be in PNG format
-#     5) You should only have one document per directory 
-#     6) Note that the figure directory, $(figdir)/, should not have its
-#        own Makefile since this Makefile installs those figures.
-#
-# example Makefile.am:
-#   figdir = figures
-#   docname = scrollkeeper-manual
-#   lang = C
-#   omffile=scrollkeeper-manual-C.omf
-#   entities = fdl.xml
-#   include $(top_srcdir)/xmldocs.make
-#   dist-hook: app-dist-hook
-#
-# About this file:
-#	This file was taken from scrollkeeper_example2, a package illustrating
-#	how to install documentation and OMF files for use with ScrollKeeper 
-#	0.3.x and 0.4.x.  For more information, see:
-#		http://scrollkeeper.sourceforge.net/
-#	Version: 0.1.2 (last updated: March 20, 2002)
-#
-
-
-# **********  Begin of section some packagers may need to modify  **********
-# This variable (docdir) specifies where the documents should be installed.
-# This default value should work for most packages.
-docdir = $(datadir)/gnome/help/$(docname)/$(lang)
-
-# **********  You should not have to edit below this line  **********
-xml_files = $(entities) $(docname).xml
-
-EXTRA_DIST = $(xml_files) $(omffile)
-CLEANFILES = omf_timestamp
-
-include $(top_srcdir)/omf.make
-
-all: omf
-
-$(docname).xml: $(entities)
-	-ourdir=`pwd`;  \
-	cd $(srcdir);   \
-	cp $(entities) $$ourdir
-
-app-dist-hook:
-	if test "$(figdir)"; then \
-	  $(mkinstalldirs) $(distdir)/$(figdir); \
-	  for file in $(srcdir)/$(figdir)/*.png; do \
-	    basefile=`echo $$file | sed -e  's,^.*/,,'`; \
-	    $(INSTALL_DATA) $$file $(distdir)/$(figdir)/$$basefile; \
-	  done \
-	fi
-
-install-data-local: omf
-	$(mkinstalldirs) $(DESTDIR)$(docdir)
-	for file in $(xml_files); do \
-	  cp $(srcdir)/$$file $(DESTDIR)$(docdir); \
-	done
-	if test "$(figdir)"; then \
-	  $(mkinstalldirs) $(DESTDIR)$(docdir)/$(figdir); \
-	  for file in $(srcdir)/$(figdir)/*.png; do \
-	    basefile=`echo $$file | sed -e  's,^.*/,,'`; \
-	    $(INSTALL_DATA) $$file $(DESTDIR)$(docdir)/$(figdir)/$$basefile; \
-	  done \
-	fi
-
-install-data-hook: install-data-hook-omf
-
-uninstall-local: uninstall-local-doc uninstall-local-omf
-
-uninstall-local-doc:
-	-if test "$(figdir)"; then \
-	  for file in $(srcdir)/$(figdir)/*.png; do \
-	    basefile=`echo $$file | sed -e  's,^.*/,,'`; \
-	    rm -f $(DESTDIR)$(docdir)/$(figdir)/$$basefile; \
-	  done; \
-	  rmdir $(DESTDIR)$(docdir)/$(figdir); \
-	fi
-	-for file in $(xml_files); do \
-	  rm -f $(DESTDIR)$(docdir)/$$file; \
-	done
-	-rmdir $(DESTDIR)$(docdir)
-
-clean-local: clean-local-omf
diff --git a/docs/C/index.docbook b/docs/C/index.docbook
new file mode 100644
index 0000000..ca6c6ee
--- /dev/null
+++ b/docs/C/index.docbook
@@ -0,0 +1,2287 @@
+<?xml version="1.0"?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" 
+    "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
+    <!ENTITY legal SYSTEM "legal.xml">
+    <!ENTITY version "2.26.0"> 
+    <!ENTITY date    "02/10/2009"> 
+    <!ENTITY mdash   "&#8212;"> 
+    <!ENTITY percnt  "&#x0025;">
+]>
+
+<article id="index" lang="en">
+  <articleinfo>
+    <title>GNOME Display Manager Reference Manual</title>
+
+    <revhistory>
+      <revision>
+        <revnumber>0.0</revnumber>
+        <date>2008-09</date>
+      </revision>
+    </revhistory>
+
+    <abstract role="description">
+      <para>
+        GDM is the GNOME Display Manager, a graphical login program.
+      </para>
+    </abstract>
+
+    <authorgroup>
+      <author>
+        <firstname>Martin</firstname><othername>K.</othername>
+           <surname>Petersen</surname>
+        <affiliation>
+          <address><email>mkp@mkp.net</email></address>
+        </affiliation>
+      </author>
+      <author>
+        <firstname>George</firstname><surname>Lebl</surname>
+        <affiliation>
+          <address><email>jirka@5z.com</email></address>
+        </affiliation>
+      </author>
+      <author>
+        <firstname>Jon</firstname><surname>McCann</surname>
+        <affiliation>
+          <address><email>mccann@jhu.edu</email></address>
+        </affiliation>
+      </author>
+      <author>
+        <firstname>Ray</firstname><surname>Strode</surname>
+        <affiliation>
+          <address><email>rstrode@redhat.com</email></address>
+        </affiliation>
+      </author>
+      <author role="maintainer">
+        <firstname>Brian</firstname><surname>Cameron</surname>
+        <affiliation>
+          <address><email>Brian.Cameron@Oracle.COM</email></address>
+        </affiliation>
+      </author>
+    </authorgroup>
+    <copyright>
+      <year>1998</year>
+      <year>1999</year>
+      <holder>Martin K. Petersen</holder>
+    </copyright>
+    <copyright>
+      <year>2001</year>
+      <year>2003</year>
+      <year>2004</year>
+      <holder>George Lebl</holder>
+    </copyright>
+    <copyright>
+      <year>2003</year>
+      <year>2007</year>
+      <year>2008</year>
+      <holder>Red Hat, Inc.</holder>
+    </copyright>
+    <copyright>
+      <year>2003</year>
+       <year>2011</year>
+       <holder>Oracle and/or its affiliates. All rights reserved.</holder>
+    </copyright>
+
+    &legal;
+
+    <releaseinfo>
+       This manual describes version &version; of the GNOME Display Manager.
+       It was last updated on &date;.
+    </releaseinfo>  
+  </articleinfo>
+
+  <!-- ============= Preface ================================== -->
+
+  <sect1 id="preface">
+    <title>Terms and Conventions Used in This Manual</title>
+
+    <para>
+      This manual describes version &version; of the GNOME Display Manager.
+      It was last updated on &date;.
+    </para>  
+
+    <para>
+      Chooser - A program used to select a remote host for managing a
+      display remotely on the attached display (<command>gdm-host-chooser</command>).
+    </para>
+
+    <para>
+      FreeDesktop - The organization providing desktop standards, such as the
+      Desktop Entry Specification used by GDM.
+      <ulink type="http" url="http://www.freedesktop.org/">
+      http://www.freedesktop.org</ulink>.
+    </para>
+    <para>
+      GDM - GNOME Display Manager. Used to describe the software package as a
+      whole.
+    </para>
+
+    <para>
+      Greeter - The graphical login window (<command>gdm-simple-greeter</command>).
+    </para>
+
+    <para>
+      PAM - Pluggable Authentication Mechanism
+    </para>
+
+    <para>
+      XDMCP - X Display Manage Protocol
+    </para>
+
+    <para>
+      Xserver - An implementation of the X Window System.  For example the
+      Xorg Xserver provided by the X.org Foundation
+      <ulink type="http" url="http://www.x.org/">http://www.x.org</ulink>.
+    </para>
+
+    <para>
+      Paths that start with a word in angle brackets are relative to the
+      installation prefix. I.e. <filename>&lt;share&gt;/pixmaps/</filename>
+      refers to <filename>/usr/share/pixmaps</filename> if GDM was
+      configured with <command>--prefix=/usr</command>.
+    </para>
+  </sect1>
+
+  <!-- ============= Overview ================================= -->
+
+  <sect1 id="overview">
+    <title>Overview</title>
+
+    <sect2 id="introduction">
+      <title>Introduction</title>
+
+      <para> 
+        The GNOME Display Manager (GDM) is a display manager that implements
+        all significant features required for managing attached and remote
+        displays.  GDM was written from scratch and does not contain any XDM or
+        X Consortium code.
+      </para>
+
+      <para>
+        Note that GDM is configurable, and many configuration settings have
+        an impact on security. Issues to be aware of are highlighted in this
+        document.
+      </para> 
+
+      <para>
+        Please note that some Operating Systems configure GDM to behave
+        differently than the default values as described in this document.  If
+        GDM does not seem to behave as documented, then check to see if any 
+        related configuration may be different than described here.
+      </para>
+
+      <para>
+        For further information about GDM, refer to the project website at
+        <ulink type="http" url="http://www.gnome.org/projects/gdm/">
+        http://www.gnome.org/projects/gdm</ulink> and the project
+        Wiki <ulink type="http" url="http://live.gnome.org/GDM">
+        http://live.gnome.org/GDM</ulink>.
+      </para>
+
+      <para>
+        For discussion or queries about GDM, refer to the
+        <address><email>gdm-list@gnome.org</email></address> mail list.  This
+        list is archived, and is a good resource to check to seek answers to
+        common questions.  This list is archived at
+        <ulink type="http" url="http://mail.gnome.org/archives/gdm-list/">
+        http://mail.gnome.org/archives/gdm-list/</ulink> and has a search
+        facility to look for messages with keywords.
+      </para>
+
+      <para>
+        Please submit any bug reports or enhancement requests to the
+        "gdm" category in
+        <ulink type="http" url="http://bugzilla.gnome.org/">
+        http://bugzilla.gnome.org</ulink>.
+      </para>
+    </sect2>
+
+    <sect2 id="stability">
+      <title>Interface Stability</title>
+
+      <para>
+        GDM 2.20 and earlier supported stable configuration interfaces.
+        However, the codebase was completely rewritten for GDM 2.22, and
+        is not completely backward compatible with older releases. This is
+        in part because things work differently, so some options just don't
+        make sense, in part because some options never made sense, and in
+        part because some functionality has not been reimplemented yet.
+      </para>
+
+      <para>
+        Interfaces which continue to be supported in a stable fashion include
+        the Init, PreSession, PostSession, PostLogin, and Xsession scripts.
+        Some daemon configuration options in the 
+        <filename>&lt;etc&gt;/gdm/custom.conf</filename> file continue to be
+        supported.  Also, the <filename>~/.dmrc</filename>, and face browser
+        image locations are still supported.
+      </para>
+
+      <para>
+        GDM 2.20 and earlier supported the ability to manage multiple displays
+        with separate graphics cards, such as used in terminal server
+        environments, login in a window via a program like Xnest or Xephyr, the
+        gdmsetup program, XML-based greeter themes, and the ability to run the
+        XDMCP chooser from the login screen.  These features were not 
+        added back during the 2.22 rewrite.
+      </para>
+
+    </sect2>
+
+    <sect2 id="functionaldesc">
+      <title>Functional Description</title>
+
+<!--
+<para>
+        TODO - Would be good to discuss D-Bus, perhaps the new GObject model,
+               and to explain the reasons why the rewrite made GDM better.
+               From a high-level overview perspective, rather than the
+               technical aspects.
+</para>
+-->
+
+      <para>
+        GDM is responsible for managing displays on the system.  This includes
+        authenticating users, starting the user session, and terminating the
+        user session.  GDM is configurable and the ways it can be configured
+        are described in the "Configuring GDM" section of this
+        document.  GDM is also accessible for users with disabilities.
+      </para>
+
+      <para>
+        GDM provides the ability to manage the main console display, and 
+        displays launched via VT.  It is integrated with other programs, 
+        such as the Fast User Switch Applet (FUSA) and gnome-screensaver
+        to manage multiple displays on the console via the Xserver Virtual
+        Terminal (VT) interface.  It also can manage XDMCP displays.  
+      </para>
+
+      <para>
+        Regardless of the display type, GDM will do the following when it
+        manages the display.  It will start an Xserver process, then run the
+        <filename>Init</filename> script as the root user, and start the
+        greeter program on the display.
+      </para>
+
+      <para>
+        The greeter program is run as the unprivileged "gdm"
+        user/group.  This user and group are described in the
+        "Security" section of this document.  The main functions of
+        the greeter program are to provide a mechanism for selecting
+        an account for log in and to drive the dialogue between
+        the user and system when authenticating that account. The authentication
+        process is driven by Pluggable Authentication Modules (PAM).  The PAM
+        modules determine what prompts (if any) are shown to the user to
+        authenticate.  On the average system, the greeter program will request
+        a username and password for authentication.  However some systems may
+        be configured to use supplemental mechanisms such as a fingerprint or
+        SmartCard readers. GDM can be configured to support these
+        alternatives in parallel with greeter login extensions and the
+        <command>--enable-split-authentication</command>
+        <filename>./configure</filename> option, or one at a
+        time via system PAM configuration.
+      </para>
+
+      <para>
+         The smartcard extension can be enabled or disabled via the
+         <filename>org.gnome.display-manager.extensions.smartcard.active</filename>
+         gsettings key.
+      </para>
+
+      <para>
+         Likewise, the fingerprint extension can be enabled or disabled via the
+         <filename>org.gnome.display-manager.extensions.fingerprint.active</filename>
+         gsettings key.
+      </para>
+
+      <para>
+        GDM and PAM can be configured to not require any
+        input, which will cause GDM to automatically log in and simply
+        start a session, which can be useful for some environments, such as
+        single user systems or kiosks.
+      </para>
+
+      <para>
+        In addition to authentication, the greeter program allows the user to
+        select which session to start and which language to use.  Sessions are
+        defined by files that end in the .desktop suffix and more information
+        about these files can be found in the "GDM User Session and Language
+        Configuration" section of this document.  By default, GDM is configured
+        to display a face browser so the user can select their user account by
+        clicking on an image instead of having to type their username. GDM
+        keeps track of the user's default session and language in the user's
+        <filename>~/.dmrc</filename> and will use these defaults if the user
+        did not pick a session or language in the login GUI.
+      </para>
+
+      <para> 
+        After authenticating a user, the daemon runs the
+        <filename>PostLogin</filename> script as root, then runs the  
+        <filename>PreSession</filename> script as root.  After running these
+        scripts, the user session is started.  When the user exits their 
+        session, the <filename>PostSession</filename> script is run as root.
+        These scripts are provided as hooks for distributions and end-users
+        to customize how sessions are managed.  For example, using these 
+        hooks you could set up a machine which creates the user's $HOME
+        directory on the fly, and erases it on logout.  The difference 
+        between the <filename>PostLogin</filename> and
+        <filename>PreSession</filename> scripts is that
+        <filename>PostLogin</filename> is run before the pam_open_session call
+        so is the right place to do anything which should be run before the
+        user session is initialized.  The <filename>PreSession</filename>
+        script is called after session initialization.
+      </para>
+    </sect2>
+
+    <sect2 id="greeterpanel">
+      <title>Greeter Panel</title>
+      <para>
+        The GDM greeter program displays a panel docked at the bottom of the
+        screen which provides additional functionality.  When a user is
+        selected, the panel allows the user to select which session, language,
+        and keyboard layout to use after logging in.  The keyboard layout
+        selector also changes the keyboard layout used when typing your
+        password.  The panel also contains an area for login services to leave
+        status icons.  Some example status icons include a battery icon for
+        current battery usage, and an icon for enabling accessibility features.
+        The greeter program also provides buttons which allow the user to
+        shutdown or restart the system.  It is possible to configure GDM to not
+        provide the shutdown and restart buttons, if desired.  GDM can also be
+        configured via PolicyKit (or via RBAC on Oracle Solaris) to require the
+        user have appropriate authorization before accepting the shutdown or
+        restart request.
+      </para>
+
+      <para>
+        Note that keyboard layout features are only available on systems that
+        support libxklavier.
+      </para>
+    </sect2>
+
+    <sect2 id="accessibility">
+      <title>Accessibility</title>
+
+        <para>
+          GDM supports "Accessible Login", allowing users to log into
+          their desktop session even if they cannot easily use the screen,
+          mouse, or keyboard in the usual way.  Accessible Technology (AT)
+          features such as an on-screen keyboard, screen reader, screen
+          magnifier, and Xserver AccessX keyboard accessibility are available.
+          It is also possible to enable large text or high contrast icons and
+          controls, if needed.  Refer to the "Accessibility
+          Configuration" section of the document for more information
+          how various accessibility features can be configured.
+        </para>
+
+        <para>
+          On some Operating Systems, it is necessary to make sure that the GDM
+          user is a member of the "audio" group for AT programs that
+          require audio output (such as text-to-speech) to be functional.
+        </para>
+    </sect2>
+
+    <sect2 id="facebrowser">
+      <title>The GDM Face Browser</title>
+
+      <para>
+        The Face Browser is the interface which allows users to select their
+        username by clicking on an image.  This feature can be enabled or
+        disabled via the /apps/gdm/simple-greeter/disable_user_list GConf
+        key and is on by default.  When disabled, users must type their
+        complete username by hand.  When enabled, it displays all local users
+        which are available for login on the system (all user accounts defined
+        in the /etc/passwd file that have a valid shell and sufficiently high
+        UID) and remote users that have recently logged in.
+        The face browser in GDM 2.20 and earlier would attempt to display all
+        remote users, which caused performance problems in large,
+        enterprise deployments.
+      </para>
+
+      <para>
+        The Face Browser is configured to display the users who log in most
+        frequently at the top of the list.  This helps to ensure that users
+        who log in frequently can quickly find their login image.
+      </para>
+
+      <para>
+        The Face Browser supports "type-ahead search" which dynamically
+        moves the face selection as the user types to the corresponding username
+        in the list.  This means that a user with a long username will only
+        have to type the first few characters of the username before the correct
+        item in the list gets selected.
+      </para>
+
+      <para>
+        The icons used by GDM can be installed globally by the sysadmin or can
+        be located in the user's home directories.  If installed globally
+        they should be in the <filename>&lt;share&gt;/pixmaps/faces/</filename>
+        directory and the filename should be the name of the user.  Face image
+        files should be a standard image that GTK+ can read, such as PNG or
+        JPEG.  Face icons placed in the global face directory must be readable
+        to the GDM user.
+      </para>
+
+<!--
+<para>
+        TODO - In the old GDM the ~/gnome2/gdm file is used, but the new code
+               seems to use ~/.gnome/gdm.  Error?
+</para>
+-->
+      <para>
+        If there is no global icon for the user, GDM will look in the user's
+        $HOME directory for the image file.  GDM will first look for the user's
+        face image in <filename>~/.face</filename>.  If not found, it will try 
+        <filename>~/.face.icon</filename>.  If still not found, it will use the
+        value defined for "face/picture=" in the 
+        <filename>~/.gnome2/gdm</filename> file.
+      </para>
+
+      <para>
+        If a user has no defined face image, GDM will use the
+        "stock_person" icon defined in the current GTK+ theme.  If no
+        such image is defined, it will fallback to a generic face image.
+      </para>
+
+      <para>
+        Please note that loading and scaling face icons located in remote user
+        home directories can be a very time-consuming task.  Since it not
+        practical to load images over NIS or NFS, GDM does not attempt to load
+        face images from remote home directories.
+      </para>
+
+      <para>
+        When the browser is turned on, valid usernames on the computer are
+        exposed for everyone to see.  If XDMCP is enabled, then the usernames
+        are exposed to remote users.  This, of course, limits security
+        somewhat since a malicious user does not need to guess valid usernames.
+        In some very restrictive environments the face browser may not be
+        appropriate.
+      </para>
+
+    </sect2>
+
+    <sect2 id="xdmcp">
+      <title>XDMCP</title>
+
+<!--
+<para>
+        TODO - What XDMCP features actually work?   I know that the
+               chooser is missing.
+</para>
+-->
+
+      <para>
+        The GDM daemon can be configured to listen for and manage X Display
+        Manage Protocol (XDMCP) requests from remote displays.  By default
+        XDMCP support is turned off, but can be enabled if desired.  If GDM is
+        built with TCP Wrapper support, then the daemon will only grant access
+        to hosts specified in the GDM service section in the TCP Wrappers
+        configuration file.
+      </para>
+
+      <para>
+        GDM includes several measures making it more resistant to denial of
+        service attacks on the XDMCP service.  A lot of the protocol
+        parameters, handshaking timeouts, etc. can be fine tuned. The default
+        configuration should work reasonably on most systems. 
+      </para>
+
+      <para>
+        GDM by default listens for XDMCP requests on the normal UDP port used
+        for XDMCP, port 177, and will respond to QUERY and BROADCAST_QUERY
+        requests by sending a WILLING packet to the originator.
+      </para>
+
+      <para>
+        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 forward subsequent requests to the chosen manager.  GDM
+        also supports an extension to the protocol which will make it forget
+        the redirection once the user's connection succeeds.  This extension
+        is only supported if both daemons are GDM.  It is transparent and
+        will be ignored by XDM or other daemons that implement XDMCP.
+      </para>
+
+      <para>
+        If XDMCP seems to not be working, make sure that all machines are
+        specified in <filename>/etc/hosts</filename>.
+      </para>
+
+      <para>
+        Refer to the "Security" section for information about
+        security concerns when using XDMCP.
+      </para>
+    </sect2>
+
+    <sect2 id="logging">
+      <title>Logging</title>
+
+      <para>
+        GDM uses syslog to log errors and status.  It can also log debugging
+        information, which can be useful for tracking down problems if GDM is
+        not working properly.  Debug output can be enabled by setting the
+        debug/Enable key to &quot;true&quot; in the
+        <filename>&lt;etc&gt;/gdm/custom.conf</filename> file.
+      </para>
+
+      <para>
+        Output from the various Xservers is stored in the GDM log directory,
+        which is normally <filename>&lt;var&gt;/log/gdm/</filename>.  Any
+        Xserver messages are saved to a file associated with the display value,
+        <filename>&lt;display&gt;.log</filename>.  
+      </para>
+
+      <para>
+        The session output is piped through the GDM daemon to the
+        <filename>~/.xsession-errors</filename> file.  The file is overwritten
+        on each login, so logging out and logging back into the same user via
+        GDM will cause any messages from the previous session to be lost.
+      </para>
+
+      <para>
+        Note that if GDM can not create this file for some reason, then a
+        fallback file will be created named <filename>~/.xsession-errors.XXXXXXXX</filename>
+        where the <filename>XXXXXXXX</filename> are some random characters.
+      </para>
+    </sect2>
+
+    <sect2 id="fusa">
+      <title>Fast User Switching</title>
+
+      <para>
+        GDM allows multiple users to be logged in at the same time.  After one
+        user is logged in, additional users can log in via the User Switcher
+        on the GNOME Panel, or from the "Switch User" button in Lock Screen dialog
+        of GNOME Screensaver.  The active session can be changed back and forth using
+        the same mechanism.  Note that some distributions may not add the User Switcher
+        to the default panel configuration.  It can be added using the panel context
+        menu.
+      </para>
+      <para>
+        Note this feature is available on systems that support Virtual
+        Terminals.  This feature will not function if Virtual Terminals is not
+        available.
+      </para>
+    </sect2>
+  </sect1>
+
+  <!-- ============= Security ================================= -->
+
+  <sect1 id="security">
+    <title>Security</title>
+
+    <sect2 id="gdmuser">
+      <title>The GDM User And Group</title>
+
+      <para>
+        For security reasons a dedicated user and group id are recommended for
+        proper operation.  This user and group are normally "gdm" on
+        most systems, but can be configured to any user or group.  All GDM
+        GUI programs are run as this user, so that the programs which interact
+        with the user are run in a sandbox.  This user and group should have
+        limited privilege.
+      </para>
+
+      <para>
+        The only special privilege the "gdm" user requires is the
+        ability to read and write Xauth files to the
+        <filename>&lt;var&gt;/run/gdm</filename> directory.  The
+        <filename>&lt;var&gt;/run/gdm</filename> directory should have
+        root:gdm ownership and 1777 permissions.
+      </para>
+
+      <para>
+        You should not, under any circumstances, configure the GDM user/group
+        to a user which a user could easily gain access to, such as the user
+        <filename>nobody</filename>.  Any user who gains access to an Xauth
+        key can snoop on and control running GUI programs running in the
+        associated session or perform a denial-of-service attack on it.  It
+        is important to ensure that the system is configured properly so that
+        only the "gdm" user has access to these files and that it
+        is not easy to login to this account.  For example, the account should
+        be setup to not have a password or allow non-root users to login to the
+        account.
+      </para>
+
+      <para>
+        The GDM greeter configuration is stored in GConf.  To allow the GDM
+        user to be able to write configuration, it is necessary for the 
+        "gdm" user to have a writable $HOME directory.  Users may
+        configure the default GConf configuration as desired to avoid the 
+        need to provide the "gdm" user with a writable $HOME
+        directory.  However, some features of GDM may be disabled if it is
+        unable to write state information to GConf configuration.
+      </para>
+    </sect2>
+
+    <sect2 id="PAM">
+      <title>PAM</title>
+
+      <para>
+        GDM uses PAM for login authentication.  PAM stands for Pluggable
+        Authentication Module, and is used by most programs that request
+        authentication on your computer.  It allows the administrator to
+        configure specific authentication behavior for different login programs
+        (such as ssh, login GUI, screensaver, etc.)
+      </para>
+
+      <para>
+        PAM is complicated and highly configurable, and this documentation does
+        not intend to explain this in detail.  Instead, it is intended to give
+        an overview of how PAM configuration relates with GDM, how PAM is
+        commonly configured with GDM, and known issues.  It is expected that
+        a person needing to do PAM configuration would need to do further
+        reading of PAM documentation to understand how to configure PAM and
+        to understand terms used in this section.
+      </para>
+        
+      <para>
+        PAM configuration has different, but similar, interfaces on different
+        Operating Systems, so check the
+        <ulink type="help" url="man:pam.d">pam.d</ulink> or
+        <ulink type="help" url="man:pam.conf">pam.conf</ulink> man page for
+        details.  Be sure you read the PAM documentation and are comfortable
+        with the security implications of any changes you intend to make to
+        your configuration.
+      </para>
+
+      <para>
+        Note that, by default, GDM uses the "gdm" PAM service name
+        for normal login and the "gdm-autologin" PAM service name for
+        automatic login.  These services may not be defined in your pam.d or
+        pam.conf configured file.  If there is no entry, then GDM will use the
+        default PAM behavior.  On most systems this should work fine.
+        However, the automatic login feature may not work if the gdm-autologin
+        service is not defined.
+      </para>
+
+      <para>
+        The <filename>PostLogin</filename> script is run before
+        pam_open_session is called, and the <filename>PreSession</filename>
+        script is called after.  This allows the system administrator to add
+        any scripting to the login process either before or after PAM 
+        initializes the session.
+      </para>
+
+      <para>
+        If you wish to make GDM work with other types of authentication
+        mechanisms (such as a fingerprint or SmartCard reader), then you should
+        implement this by using a PAM service module for the desired
+        authentication type rather than by trying to modify the GDM code
+        directly.  Refer to the PAM documentation on your system.  How to do
+        this is frequently discussed on the 
+        <address><email>gdm-list@gnome.org</email></address> mail list,
+        so you can refer to the list archives for more information.
+      </para>
+
+      <para>
+        PAM does have some limitations regarding being able to work with 
+        multiple types of authentication at the same time, like supporting
+        the ability to accept either SmartCard and the ability to type the
+        username and password into the login program.  There are techniques
+        that are used to make this work, and it is best to research how this
+        problem is commonly solved when setting up such a configuration.
+      </para>
+
+      <para>
+        If automatic login does not work on a system, check to see if the
+        "gdm-autologin" PAM stack is defined in the PAM configuration.  For
+        this to work, it is necessary to use a PAM module that simply does no
+        authentication, or which simply returns PAM_SUCCESS from all of its
+        public interfaces.  Assuming your system has a pam_allow.so PAM module
+        which does this, a PAM configuration to enable "gdm-autologin" would
+        look like this:
+      </para>
+
+<screen>
+       gdm-autologin auth  required    pam_unix_cred.so.1
+       gdm-autologin auth  sufficient  pam_allow.so.1
+       gdm-autologin account  sufficient  pam_allow.so.1
+       gdm-autologin session  sufficient  pam_allow.so.1
+       gdm-autologin password  sufficient  pam_allow.so.1
+</screen>
+
+      <para>
+        The above setup will cause no lastlog entry to be generated.  If a
+        lastlog entry is desired, then use the following for the session:
+      </para>
+
+<screen>
+       gdm-autologin session required pam_unix_session.so.1
+</screen>
+
+      <para>
+        If the computer is used by several people, which makes automatic login
+        unsuitable, you may want to allow some users to log in without entering
+        their password. This feature can be enabled as a per-user option in
+        the users-admin tool from the gnome-system-tools; it is achieved by
+        checking that the user is member a Unix group called
+        "nopasswdlogin" before asking for a password. For this to work,
+        the PAM configuration file for the "gdm" service must include
+        a line such as:
+      </para>
+
+<screen>
+      gdm auth  sufficient  pam_succeed_if.so  user ingroup nopasswdlogin
+</screen>
+
+    </sect2>
+
+    <sect2 id="utmpwtmp">
+      <title>utmp and wtmp</title>
+
+      <para>
+        GDM generates utmp and wtmp User Accounting Database entries upon
+        session login and logout.  The utmp database contains user access
+        and accounting information that is accessed by commands such as
+        <command>finger</command>, <command>last</command>,
+        <command>login</command>, and <command>who</command>.  The wtmp
+        database contains the history of user access and accounting 
+        information for the utmp database.  Refer to the 
+        <ulink type="help" url="man:utmp">utmp</ulink> and
+        <ulink type="help" url="man:wtmp">wtmp</ulink>
+        man pages on your system for more information.
+      </para>
+    </sect2>
+
+    <sect2 id="xauth">
+      <title>Xserver Authentication Scheme</title>
+
+      <para>
+        Xserver authorization files are stored in a newly created subdirectory
+        of <filename>&lt;var&gt;/run/gdm</filename> at start up.  These files
+        are used to store and share a "password" between X clients
+        and the Xserver.  This "password" is unique for each session
+        logged in, so users from one session can't snoop on users from another.
+      </para>
+
+      <para>
+        GDM only supports the MIT-MAGIC-COOKIE-1 Xserver 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 Xserver 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.  In most cases,
+        ssh -Y should be preferred over GDM's XDMCP features.
+      </para>
+
+    </sect2>
+
+    <sect2 id="xdmcpsecurity">
+      <title>XDMCP Security</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.  This type of set up
+        should never use an unmanaged hub or other sniffable network.
+      </para>
+
+    </sect2>
+
+    <sect2 id="xdmcpaccess">
+      <title>XDMCP Access Control</title>
+
+      <para>
+        XDMCP access control is done using TCP wrappers.  It is possible to
+        compile GDM without TCP wrapper support, so this feature may not be
+        supported on some Operating Systems.
+      </para>
+
+      <para>
+        You should use the daemon name <command>gdm</command> in the
+        <filename>&lt;etc&gt;/hosts.allow</filename> and
+        <filename>&lt;etc&gt;/hosts.deny</filename> files.  For example to 
+        deny computers from <filename>.evil.domain</filename> from logging in,
+        then add
+      </para>
+<screen>
+gdm: .evil.domain
+</screen>
+      <para>
+        to <filename>&lt;etc&gt;/hosts.deny</filename>.  You may also need
+        to add
+      </para>
+<screen>
+gdm: .your.domain
+</screen>
+      <para>
+        to your <filename>&lt;etc&gt;/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.
+      </para>
+    </sect2>
+
+    <sect2 id="firewall">
+      <title>Firewall Security</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 really needed.  GDM
+        guards against 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 do a denial of service attack via XDMCP than attacking a
+        webserver.
+      </para>
+
+      <para>
+        It is also wise to block all of the Xserver ports.  These are TCP
+        ports 6000+ (one for each display number) 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 when using it over the Internet, and
+         XDMCP is even less safe.
+      </para>
+    </sect2>
+
+    <sect2 id="policykit">
+      <title>PolicyKit</title>
+
+<!--
+<para>
+        TODO - Should we say more?
+</para>
+-->
+
+      <para>
+        GDM may be configured to use PolicyKit to allow the system
+        administrator to control whether the login screen should provide
+        the shutdown and restart buttons on the greeter screen.
+      </para>
+
+      <para>
+        These buttons are controlled by the
+        <filename>org.freedesktop.consolekit.system.stop-multiple-users</filename>
+        and
+        <filename>org.freedesktop.consolekit.system.restart-multiple-users</filename>
+        actions respectively.  Policy for these actions can be set up using the
+        polkit-gnome-authorization tool, or the polkit-auth command line program.
+      </para>
+ 
+    </sect2>
+
+    <sect2 id="rbac">
+      <title>RBAC (Role Based Access Control)</title>
+
+      <para>
+        GDM may be configured to use RBAC instead of PolicyKit.  In this
+        case the RBAC configuration is used to control whether the login screen
+        should provide the shutdown and restart buttons on the greeter screen.
+      </para>
+
+      <para>
+        For example, on Oracle Solaris, the "solaris.system.shutdown"
+        authorization is used to control this.  Simply modify the 
+        <filename>/etc/user_attr</filename> file so that the "gdm"
+        user has this authorization.
+      </para>
+    </sect2>
+
+  </sect1>
+
+  <!-- ============= ConsoleKit ================================ -->
+
+  <sect1 id="consolekit">
+    <title>Support for ConsoleKit</title>
+
+<!--
+<para>
+    TODO - Should we update these docs?  Probably should mention any 
+           configuration that users may want to do for using it with GDM?
+           If so, perhaps this section should be moved to a subsection of
+           the "Configure" section?
+</para>
+-->
+
+    <para>
+      GDM includes support for publishing user login information with the user
+      and login session accounting framework known as ConsoleKit.  ConsoleKit
+      is able to keep track of all the users currently logged in.  In this
+      respect, it can be used as a replacement for the utmp or utmpx files that
+      are available on most Unix-like Operating Systems.
+    </para>
+
+    <para>
+      When GDM is about to create a new login process for a user it will call
+      a privileged method of ConsoleKit in order to open a new session for this
+      user.  At this time GDM also provides ConsoleKit with information about
+      this user session such as: the user ID, the X11 Display name that will be
+      associated with the session, the host-name from which the session
+      originates (useful in the case of an XDMCP session), whether or not this
+      session is attached, etc.  As the entity that initiates the user process,
+      GDM is in a unique position to know about the user session and to be 
+      trusted to provide these bits of information. The use of this privileged 
+      method is restricted by the use of the D-Bus system message bus security 
+      policy.
+    </para>
+
+    <para>
+      In case a user with an existing session has authenticated
+      at GDM and requests to resume that existing session, GDM calls a
+      privileged method of ConsoleKit to unlock that session.  The exact
+      details of what happens when the session receives this unlock signal are
+      undefined and session-specific.  However, most sessions will unlock a
+      screensaver in response.
+    </para>
+
+    <para>
+      When the user chooses to log out, or if GDM or the session quit
+      unexpectedly the user session will be unregistered from ConsoleKit.
+    </para>
+  </sect1>
+
+  <!-- ============= Configuration ============================= -->
+
+  <sect1 id="configuration">
+    <title>Configuration</title>
+
+    <para>
+      GDM has a number of configuration interfaces.  These include scripting
+      integration points, daemon configuration, greeter configuration, 
+      general session settings, integration with gnome-settings-daemon
+      configuration, and session configuration.  These types of integration are
+      described in detail below.
+    </para>
+
+    <sect2 id="scripting">
+      <title>Scripting Integration Points</title>
+      
+      <para>
+        The GDM script integration points can be found in the
+        <filename>&lt;etc&gt;/gdm/</filename> directory:
+      </para>
+
+<screen>
+Xsession
+Init/
+PostLogin/
+PreSession/
+PostSession/
+</screen>
+
+      <para>
+        The <filename>Init</filename>, <filename>PostLogin</filename>,
+        <filename>PreSession</filename>, and <filename>PostSession</filename>
+        scripts all work as described below.
+      </para>
+
+      <para>
+        For each type of script, the default one which will be executed is
+        called "Default" and is stored in a directory associated with
+        the script type.  So the default <filename>Init</filename> script is 
+        <filename>&lt;etc&gt;/gdm/Init/Default</filename>.  A per-display
+        script can be provided, and if it exists it will be run instead of the 
+        default script.  Such scripts are stored in the same directory as the
+        default script and have the same name as the Xserver DISPLAY value for
+        that display.  For example, if the <filename>&lt;Init&gt;/:0</filename>
+        script exists, it will be run for DISPLAY ":0".
+     </para>
+
+     <para>
+        All of these scripts are run with root privilege and return 0 if run
+        successfully, and a non-zero return code if there was any failure that
+        should cause the login session to be aborted.  Also note that GDM will
+        block until the scripts finish, so if any of these scripts hang, this
+        will cause the login process to also hang.
+      </para>
+
+      <para>
+        When the Xserver for the login GUI has been successfully started, but
+        before the login GUI is actually displayed, GDM will run the
+        <filename>Init</filename> script.  This script is useful for starting
+        programs that should be run while the login screen is showing, or for
+        doing any special initialization if required.
+      </para>
+
+      <para>
+        After the user has been successfully authenticated GDM will run the
+        <filename>PostLogin</filename> script.  This is done before any session
+        setup has been done, including before the pam_open_session call.  This
+        script is useful for doing any session initialization that needs to
+        happen before the session starts.  For example, you might setup the
+        user's $HOME directory if needed.
+      </para>
+
+      <para>
+        After the user session has been initialized, GDM will run the
+        <filename>PreSession</filename> script.  This script is useful for
+        doing any session initialization that needs to happen after the 
+        session has been initialized.  It can be used for session management or
+        accounting, for example.
+      </para>
+
+      <para> 
+        When a user terminates their session, GDM will run the
+        <filename>PostSession</filename> script.  Note that the Xserver will
+        have been stopped by the time this script is run, so it should not be
+        accessed.  
+      </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>
+        All of the above scripts will set the
+        <filename>$RUNNING_UNDER_GDM</filename> environment variable to
+        <filename>yes</filename>.  If the scripts are also shared with other
+        display managers, this allows you to identify when GDM is calling these
+        scripts, so you can run specific code when GDM is used.
+      </para>
+    </sect2>
+
+    <sect2 id="autostart">
+      <title>Autostart Configuration</title>
+      
+      <para>
+        The <filename>&lt;share&gt;/gdm/autostart/LoginWindow</filename>
+        directory contains files in the format specified by the
+        "FreeDesktop.org Desktop Application Autostart
+        Specification".  Standard features in the specification may be
+        used to specify programs that should auto-restart or only be launched
+        if a GConf configuration value is set, etc.
+      </para>
+
+      <para>
+        Any <filename>.desktop</filename> files in this directory will cause
+        the associated program to automatically start with the login GUI
+        greeter.  By default, GDM is shipped with files which will autostart
+        the gdm-simple-greeter login GUI greeter itself, the
+        gnome-power-manager application, the gnome-settings-daemon, and the
+        metacity window manager.  These programs are needed for the greeter
+        program to work.  In addition, desktop files are provided for starting
+        various AT programs if the configuration values specified in the
+        Accessibility Configuration section below are set.
+      </para>
+    </sect2>
+
+    <sect2 id="xsessionscript">
+      <title>Xsession Script</title>
+
+      <para>
+        There is also an <filename>Xsession</filename> script located at
+        <filename>&lt;etc&gt;/gdm/Xsession</filename> which is called between
+        the <filename>PreSession</filename> and the
+        <filename>PostSession</filename> scripts.  This script does not
+        support per-display like the other scripts.  This script is used for
+        actually starting the user session.  This script is run as the user,
+        and it will run whatever session was specified by the Desktop session
+        file the user selected to start. 
+      </para>
+    </sect2>
+
+    <sect2 id="daemonconfig">
+      <title>Daemon Configuration</title>
+
+      <para>
+        The GDM daemon is configured using the
+        <filename>&lt;etc&gt;/gdm/custom.conf</filename> file.  Default
+        values are stored in GConf in the <filename>gdm.schemas</filename>
+        file.  It is recommended that end-users modify the
+        <filename>&lt;etc&gt;/gdm/custom.conf</filename> file because the
+        schemas file may be overwritten when the user updates their system to
+        have a newer version of GDM.
+      </para>
+
+      <para>
+        Note that older versions of GDM supported additional configuration
+        options which are no longer supported in the latest versions of GDM.
+      </para>
+
+      <para>
+        The <filename>&lt;etc&gt;/gdm/custom.conf</filename> file is in the
+        <filename>keyfile</filename> format.  Keywords in brackets
+        define group sections, strings before an equal sign (=) are keys and
+        the data after equal sign represents their value.  Empty lines or
+        lines starting with the hash mark (#) are ignored.  
+      </para>
+
+      <para>
+        The file <filename>&lt;etc&gt;/gdm/custom.conf</filename> supports the
+        "[daemon]", "[security]", and "[xdmcp]"
+        group sections.  Within each group, there are particular key/value
+        pairs that can be specified to modify how GDM behaves.  For example,
+        to enable timed login and specify the timed login user to be a user
+        named "you", you would modify the file so it contains the
+        following lines:
+      </para>
+     
+<screen>
+[daemon]
+TimedLoginEnable=true
+TimedLogin=you
+</screen>
+
+      <para>
+        A full list of supported configuration keys follow:
+      </para>
+
+      <sect3 id="choosersection">
+        <title>[chooser]</title>
+        <variablelist>
+
+          <varlistentry>
+            <term>Multicast</term>
+            <listitem>
+              <synopsis>Multicast=false</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.
+              </para>
+            </listitem>
+          </varlistentry>
+         
+          <varlistentry>
+            <term>MulticastAddr</term>
+            <listitem>
+              <synopsis>MulticastAddr=ff02::1</synopsis>
+              <para>
+                This is the Link-local multicast address.
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
+      </sect3>
+
+      <sect3 id="daemonsection">
+        <title>[daemon]</title>
+        <variablelist>
+          <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.  Refer to the "Security->PAM"
+                section of the manual for more information, or for help if this
+                feature does not seem to work.
+              </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.
+              </para>
+              <para>
+                If the value ends with a vertical bar | (the pipe symbol),
+                then GDM will execute the program specified and use whatever
+                value is returned on standard out from the program as the user.
+                The program is run with the DISPLAY environment variable set so
+                that it is possible to specify the user in a per-display
+                fashion.  For example if the value is "/usr/bin/getloginuser|",
+                then the program "/usr/bin/getloginuser" will be run to get the
+                user value.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>TimedLoginDelay</term>
+            <listitem>
+              <synopsis>TimedLoginDelay=30</synopsis>
+              <para>
+                Delay in seconds before the <filename>TimedLogin</filename>
+                user will be logged in.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>AutomaticLoginEnable</term>
+            <listitem>
+              <synopsis>AutomaticLoginEnable=false</synopsis>
+              <para>
+                If true, the user given in <filename>AutomaticLogin</filename>
+                should be logged in immediately. This feature is like timed
+                login with a delay of 0 seconds.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>AutomaticLogin</term>
+            <listitem>
+              <synopsis>AutomaticLogin=</synopsis>
+              <para>
+                This is the user that should be logged in immediately if
+                <filename>AutomaticLoginEnable</filename> is true.
+              </para>
+              <para>
+                If the value ends with a vertical bar | (the pipe symbol),
+                then GDM will execute the program specified and use whatever
+                value is returned on standard out from the program as the user.
+                The program is run with the DISPLAY environment variable set so
+                that it is possible to specify the user in a per-display
+                fashion.  For example if the value is "/usr/bin/getloginuser|",
+                then the program "/usr/bin/getloginuser" will be run to get the
+                user value.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>User</term>
+            <listitem>
+              <synopsis>User=gdm</synopsis>
+              <para>
+                The username under which the greeter and other GUI programs
+                are run.  Refer to the <filename>Group</filename>
+                configuration key and to the "Security->GDM User And
+                Group" section of this document for more information.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>Group</term>
+            <listitem>
+              <synopsis>Group=gdm</synopsis>
+              <para>
+                The group name under which the greeter and other GUI programs
+                are run.  Refer to the <filename>User</filename>
+                configuration key and to the "Security->GDM User And
+                Group" section of this document for more information.
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
+      </sect3>
+
+      <sect3 id="debugsection">
+        <title>Debug Options</title>
+      
+        <variablelist>
+          <title>[debug]</title>
+          
+          <varlistentry>
+            <term>Enable</term>
+            <listitem>
+              <synopsis>Enable=false</synopsis>
+              <para>
+                To enable debugging, set the debug/Enable key to
+                &quot;true&quot; in the
+                <filename>&lt;etc&gt;/gdm/custom.conf</filename>
+                file and restart GDM.  Then debug output will be sent to the
+                system log file (<filename>&lt;var&gt;/log/messages</filename>
+                or <filename>&lt;var&gt;/adm/messages</filename> depending on
+                your Operating System).
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
+      </sect3>
+
+      <sect3 id="greetersection">
+        <title>Greeter Options</title>
+      
+        <variablelist>
+          <title>[greeter]</title>
+          
+          <varlistentry>
+            <term>IncludeAll</term>
+            <listitem>
+              <synopsis>IncludeAll=true</synopsis>
+              <para>
+                If true, then the face browser will show all users on the local
+                machine.  If false, the face browser will only show users who
+                have recently logged in.
+              </para>
+
+              <para>
+                When this key is true, GDM will call fgetpwent() to get a list
+                of local users on the system.  Any users with a user id less
+                than 500 (or 100 if running on Oracle Solaris) are filtered
+                out.  The Face Browser also will display any users that have
+                previously logged in on the system  (for example NIS/LDAP
+                users).  It gets this list via calling the
+                <command>ck-history</command> ConsoleKit interface.  It will
+                also filter out any users which do not have a valid shell
+                (valid shells are any shell that getusershell() returns -
+                /sbin/nologin or /bin/false are considered invalid shells even
+                if getusershell() returns them).
+              </para>
+
+              <para>
+                If false, then GDM more simply only displays users that have
+                previously logged in on the system (local or NIS/LDAP users) by
+                calling the <command>ck-history</command> ConsoleKit interface.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>Include</term>
+            <listitem>
+              <synopsis>Include=</synopsis>
+              <para>
+                Set to a list of users to always include in the Face Browser.
+                This value is set to a list of users separated by commas.  By
+                default, the value is empty.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>Exclude</term>
+            <listitem>
+              <synopsis>Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap</synopsis>
+              <para>
+                Set to a list of users to always exclude in the Face Browser.
+                This value is set to a list of users separated by commas.  Note
+                that the setting in the <filename>custom.conf</filename>
+                overrides the default value, so if you wish to add additional
+                users to the list, then you need to set the value to the
+                default value with additional users appended to the list.
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
+      </sect3>
+
+      <sect3 id="securitysection">
+        <title>Security Options</title>
+      
+        <variablelist>
+          <title>[security]</title>
+          
+          <varlistentry>
+            <term>DisallowTCP</term>
+            <listitem>
+              <synopsis>DisallowTCP=true</synopsis>
+              <para>
+                If true, then always append <filename>-nolisten tcp</filename>
+                to the command line when starting attached Xservers, thus
+                disallowing TCP connection.  This is a more secure
+                configuration if you are not using remote connections.
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
+      </sect3>
+
+      <sect3 id="xdmcpsection">
+        <title>XDCMP Support</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 this value.
+              </para>
+
+              <para>
+                Note that the number of attached DISPLAYS allowed is not 
+                limited.  Only remote connections via XDMCP are limited by
+                this configuration option.
+              </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>&lt;etc&gt;/hosts.allow</filename>, depending
+                on your TCP Wrappers configuration.  See the
+                <ulink type="help" url="man:hosts.allow">hosts.allow</ulink>
+                man page for details.
+              </para>
+              
+              <para>
+                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.
+              </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 do not
+                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>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>PingIntervalSeconds</term>
+            <listitem>
+              <synopsis>PingIntervalSeconds=60</synopsis>
+              <para>
+                If the Xserver does not respond in the specified number of
+                seconds, then the connection is stopped and the session ended.
+                When this happens the slave daemon dies with an ALARM signal.
+                Note that GDM 2.20 and earlier multiplied this setting by 2,
+                so it may be necessary to increase the timeout if upgrading
+                from GDM 2.20 and earlier to a newer version.
+              </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 than 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>Port</term>
+            <listitem>
+              <synopsis>Port=177</synopsis>
+              <para>
+                The UDP port number <filename>gdm</filename> should listen to
+                for XDMCP requests. Do not change this unless you know what
+                you are doing.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>Willing</term>
+            <listitem>
+              <synopsis>Willing=&lt;etc&gt;/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 does not 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>
+    </sect2>
+
+    <sect2 id="greeterconfiguration">
+        <title>Simple Greeter Configuration</title>
+
+        <para>
+          The GDM default greeter is called the simple Greeter and is
+          configured via GConf.  Default values are stored in GConf in the
+          <filename>gdm-simple-greeter.schemas</filename> file.  These defaults
+          can be overridden if the "gdm" user has a writable $HOME
+          directory to store GConf settings.  These values can be edited using
+          the <command>gconftool-2</command> or <command>gconf-editor</command>
+          programs.  The following configuration options are supported:
+        </para>
+
+        <variablelist>
+          <title>Greeter Configuration Keys</title>
+
+          <varlistentry>
+            <term>/apps/gdm/simple-greeter/banner_message_enable</term>
+            <listitem>
+              <synopsis>false (boolean)</synopsis>
+              <para>
+                Controls whether the banner message text is displayed.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>/apps/gdm/simple-greeter/banner_message_text</term>
+            <listitem>
+              <synopsis>NULL (string)</synopsis>
+              <para>
+                Specifies the text banner message to show on the greeter
+                window.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>/apps/gdm/simple-greeter/disable_restart_buttons</term>
+            <listitem>
+              <synopsis>false (boolean)</synopsis>
+              <para>
+                Controls whether to show the restart buttons in the login
+                window.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>/apps/gdm/simple-greeter/disable_user_list</term>
+            <listitem>
+              <synopsis>false (boolean)</synopsis>
+              <para>
+                If true, then the face browser with known users is not shown
+                in the login window.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>/apps/gdm/simple-greeter/logo_icon_name</term>
+            <listitem>
+              <synopsis>computer (string)</synopsis>
+              <para>
+                Set to the themed icon name to use for the greeter logo.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>/apps/gdm/simple-greeter/recent-languages</term>
+            <listitem>
+              <synopsis>[] (string list)</synopsis>
+              <para>
+                Set to a list of languages to be shown by default in the login
+                window.  Default value is "[]".  With the default setting only
+                the system default language is shown and the option "Other..."
+                which pops-up a dialog box showing a full list of available
+                languages which the user can select.
+              </para>
+
+              <para>
+                Users are not intended to change this setting by hand.  Instead
+                GDM keeps track of any languages selected in this configuration
+                key, and will show them in the language combo box along with
+                the "Other..." choice.  This way, commonly selected languages
+                are easier to select.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>/apps/gdm/simple-greeter/recent-layouts</term>
+            <listitem>
+              <synopsis>[] (string list)</synopsis>
+              <para>
+                Set to a list of keyboard layouts to be shown by default in the
+                login panel.  Default value is "[]".  With the default setting
+                only the system default keyboard layout is shown and the option
+                "Other..." which pops-up a dialog box showing a full list of
+                available keyboard layouts which the user can select.
+              </para>
+
+              <para>
+                Users are not intended to change this setting by hand.  Instead
+                GDM keeps track of any keyboard layouts selected in this
+                configuration key, and will show them in the keyboard layout
+                combo box along with the "Other..." choice.  This way, commonly
+                selected keyboard layouts are easier to select.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>/apps/gdm/simple-greeter/wm_use_compiz</term>
+            <listitem>
+              <synopsis>false (boolean)</synopsis>
+              <para>
+                Controls whether compiz is used as the window manager instead
+                of metacity.
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
+    </sect2>
+
+    <sect2 id="accessibilityconfiguration">
+     <title>Accessibility Configuration</title>
+
+      <para>
+       This section describes the accessibility configuration options available
+       in GDM.
+      </para>
+
+      <sect3 id="accessibilitydialog">
+        <title>GDM Accessibility Dialog And GConf Keys</title>
+
+        <para>
+         The GDM greeter panel at the login screen displays an accessibility
+         icon.  Clicking on that icon opens the GDM Accessibility Dialog.  In
+         the GDM Accessibility Dialog, there is a list of checkboxes, so the
+         user can enable or disable the associated assistive tools.
+        </para>
+
+        <para>
+         The checkboxes that correspond to the on-screen keyboard, screen
+         magnifier and screen reader assistive tools act on the three GConf
+         keys that are described in the next section of this document. By
+         enabling or disabling these checkboxes, the associated GConf key is
+         set to "true" or "false".  When the GConf key is set to true, the 
+         assistive tools linked to this GConf key are launched.  When the 
+         GConf key is set to "false", any running assistive tool linked to
+         this GConf key are terminated.  These GConf keys are not automatically
+         reset to a default state after the user has logged in.  Consequently,
+         the assistive tools that were running during the last GDM login
+         session will automatically be launched at the next GDM login session.
+        </para>
+
+        <para>
+         The other checkboxes in the GDM Accessibility Dialog do not have
+         corresponding GConf keys because no additional program is launched to
+         provide the accessibility features that they offer.  These other
+         options correspond to accessibility features that are provided by the
+         Xserver, which is always running during the GDM session.
+        </para>
+      </sect3>
+
+      <sect3 id="accessibilitygconfconfiguration">
+        <title>Accessibility GConf Keys</title>
+
+        <para>
+         GDM offers the following GConf keys to control its accessibility
+         features:
+        </para>
+
+        <variablelist>
+          <title>GDM Configuration Keys</title>
+
+          <varlistentry>
+            <term>/desktop/gnome/interface/accessibility</term>
+            <listitem>
+              <synopsis>false (boolean)</synopsis>
+              <para>
+                Controls whether the Accessibility infrastructure will be
+                started with the GDM GUI.  This is needed for many
+                accessibility technology programs to work.
+              </para>
+            </listitem>
+          </varlistentry>
+          <varlistentry>
+            <term>/desktop/gnome/applications/at/screen_magnifier_enabled</term>
+            <listitem>
+              <synopsis>false (boolean)</synopsis>
+              <para>
+                If set, then the assistive tools linked to this GConf key will
+                be started with the GDM GUI program.  By default this is a
+                screen magnifier application.
+              </para>
+            </listitem>
+          </varlistentry>
+          <varlistentry>
+            <term>/desktop/gnome/applications/at/screen_keyboard_enabled</term>
+            <listitem>
+              <synopsis>false (boolean)</synopsis>
+              <para>
+                If set, then the assistive tools linked to this GConf key will
+                be started with the GDM GUI program.  By default this is an
+                on-screen keyboard application.
+              </para>
+            </listitem>
+          </varlistentry>
+          <varlistentry>
+            <term>/desktop/gnome/applications/at/screen_reader_enabled</term>
+            <listitem>
+              <synopsis>false (boolean)</synopsis>
+              <para>
+                If set, then the assistive tools linked to this GConf key will
+                be started with the GDM GUI program.  By default this is a
+                screen reader application.
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
+      </sect3>
+
+      <sect3 id="accessibilitytoolsconfiguration">
+        <title>Linking GConf Keys to Accessbility Tools</title>
+
+        <para>
+         For the screen_magnifier_enabled, the screen_keyboard_enabled, and the
+         screen_reader_enabled GConf keys, the assistive tool which gets
+         launched depends on the desktop files located in the GDM autostart
+         directory as described in the "Autostart Configuration" section of
+         this manual.  Any desktop file in the GDM autostart directory can be
+         linked to these GConf key via specifying that GConf key in the
+         AutostartCondition value in the desktop file.  So the exact
+         AutostartCondition line in the desktop file could be one of the
+         following:
+        </para>
+
+<screen>
+AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled
+AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled
+AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled
+</screen>
+
+        <para>
+         When an accessibility key is true, then any program which is linked to
+         that key in a GDM autostart desktop file will be launched (unless the
+         Hidden key is set to true in that desktop file).  A single GConf key
+         can even start multiple assistive tools if there are multiple desktop
+         files with this AutostartCondition in the GDM autostart directory.
+        </para>
+      </sect3>
+
+      <sect3 id="accessibilitytoolexample">
+        <title>Example Of Modifying Accessibility Tool Configuration</title>
+
+        <para>
+         For example, if GNOME is distributed with GOK as the default on-screen
+         keyboard, then this could be replaced with a different program if
+         desired.  To replace GOK with the on-screen keyboard application
+         "onboard" and additionally activate the assistive tool "mousetweaks"
+         for dwelling support, then the following configuration is needed.
+        </para>
+
+        <para>
+         Create a desktop file for onboard and a second one for mousetweaks;
+         for example, onboard.desktop and mousetweaks.desktop. These files
+         must be placed in the GDM autostart directory and be in the format
+         as explained in the "Autostart Configuration" section of this
+         document.
+        </para>
+
+        <para>
+         The following is an example <filename>onboard.desktop</filename> file:
+        </para>
+
+<screen>
+[Desktop Entry]
+Encoding=UTF-8
+Name=Onboard Onscreen Keyboard
+Comment=Use an on-screen keyboard
+TryExec=onboard
+Exec=onboard --size 500x180 -x 20 -y 10
+Terminal=false
+Type=Application
+StartupNotify=true
+Categories=GNOME;GTK;Accessibility;
+AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled
+</screen>
+
+        <para>
+         The following is an example <filename>mousetweaks.desktop</filename>
+         file:
+        </para>
+
+<screen>
+[Desktop Entry]
+Encoding=UTF-8
+Name=Software Mouse-Clicks
+Comment=Perform clicks by dwelling with the pointer
+TryExec=mousetweaks
+Exec=mousetweaks --enable-dwell -m window -c -x 20 -y 240 
+Terminal=false
+Type=Application
+StartupNotify=true
+Categories=GNOME;GTK;Accessibility;
+AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled
+</screen>
+
+        <para>
+         Note the line with the AutostartCondition that links both desktop
+         files to the GConf key for the on-screen keyboard.
+        </para>
+
+        <para>
+         To disable GOK from starting, the desktop file for the GOK on-screen
+         keyboard must be removed or deactivated.  Otherwise onboard and GOK
+         would simultaneously be started.  This can be done by removing the
+         gok.desktop file from the GDM autostart directory, or by adding the
+         "Hidden=true" key setting to the gok.desktop file.
+        </para>
+
+        <para>
+         After making these changes, GOK will no longer be started when the
+         user activates the on-screen keyboard in the GDM session; but onboard
+         and mousetweaks will instead be launched.
+        </para>
+      </sect3>
+    </sect2>
+
+    <sect2 id="generalsessionconfig">
+      <title>General Session Settings</title>
+<!--
+<para>
+          TODO - I think this section should be expanded upon.  What specific
+                 keys are of interest, or would some users be likely to want
+                 to configure?  Also, would be good to be more specific about
+                 how lock down management is handled.
+</para>
+-->
+        <para>
+          The GDM Greeter uses some of the same framework that your desktop
+          session will use. And so, it is influenced by a number of the same
+          GConf settings. For each of these settings the Greeter will use the
+          default value unless it is specifically overridden by a) GDM's
+          installed mandatory policy b) system mandatory policy. GDM installs
+          its own mandatory policy to lock down some settings for security.
+        </para>
+    </sect2>
+
+    <sect2 id="gnomesettingsdaemon">
+      <title>GNOME Settings Daemon</title>
+<!--
+<para>
+          TODO - I think this section should be expanded upon.  What specific
+                 keys are of interest, or would some users be likely to want
+                 to configure?  Also, would be good to give a more complete
+                 list of plugins that users might want to consider disabling.
+                 Also, shouldn't we list the sound/active key in the Greeter
+                 configuration setting?  Oddly I do not find this key used
+                 in anything but the chooser in SVN.
+</para>
+-->
+
+        <para>
+          GDM enables the following gnome-settings-daemon plugins:
+          a11y-keyboard, background, sound, xsettings.
+        </para>
+
+        <para>
+          These are responsible for things like the background image, font and
+          theme settings, sound events, etc.
+        </para>
+
+        <para>
+          Plugins can also be disabled using GConf. For example, if you want to
+          disable the sound plugin then unset the following key:
+          <filename>/apps/gdm/simple-greeter/settings-manager-plugins/sound/active</filename>.
+        </para>
+    </sect2>
+
+    <sect2 id="sessionconfig">
+      <title>GDM Session Configuration</title>
+
+      <para>
+        GDM sessions are specified using the FreeDesktop.org Desktop Entry
+        Specification, which can be referenced at the following URL:
+        <ulink url="http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec">
+        http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec</ulink>.
+      </para>
+
+      <para>
+        By default, GDM will install desktop files in the
+        <filename>&lt;share&gt;/xsessions</filename> directory.  GDM will
+        search the following directories in this order to find desktop files:
+        <filename>&lt;etc&gt;/X11/sessions/</filename>,
+        <filename>&lt;dmconfdir&gt;/Sessions</filename>, 
+        <filename>&lt;share&gt;/xsessions</filename>, and
+        <filename>&lt;share&gt;/gdm/BuiltInSessions</filename>.  By default the
+        <filename>&lt;dmconfdir&gt;</filename> is set to
+        <filename>&lt;etc&gt;/dm/</filename> unless GDM is configured to use
+        a different directory via the "--with-dmconfdir" option.
+      </para>
+
+      <para>
+        A session can be disabled by editing the desktop file and adding a line
+        as follows: <filename>Hidden=true</filename>.
+      </para>
+
+      <para>
+        GDM desktop files support a GDM-specific extension, a key named
+        &quot;X-GDM-BypassXsession&quot;.  If the key is not specified in a
+        desktop file, the value defaults to &quot;false&quot;.  If this key is
+        specified to be &quot;true&quot; in a desktop file, then GDM will
+        launch the program specified by the desktop file &quot;Exec&quot; key
+        directly when starting the user session.  It will not run the program
+        via the <filename>&lt;etc&gt;/gdm/Xsession</filename> script, which is
+        the normal behavior.  Since bypassing the
+        <filename>&lt;etc&gt;/gdm/Xsession</filename> script avoids setting up
+        the user session with the normal system and user settings, sessions
+        started this way can be useful for debugging problems in the system or
+        user scripts that might be preventing a user from being able to start
+        a session.
+      </para>
+
+    </sect2>
+
+    <sect2 id="userconfig">
+      <title>GDM User Session and Language Configuration</title>
+      <para>
+        The user's default session and language choices are stored in the
+        <filename>~/.dmrc</filename> file.  When a user logs in for the first
+        time, this file is created with the user's initial choices.  The user
+        can change these default values by simply changing to a different value
+        when logging in.  GDM will remember this change for subsequent logins.
+      </para>
+
+      <para>
+        The <filename>~/.dmrc</filename> file is in the standard
+        <filename>INI</filename> format.  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.
+        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>
+    </sect2>
+
+  </sect1>
+
+  <!-- ============= GDM Commands ============================= -->
+
+  <sect1 id="binaries">
+    <title>GDM Commands</title>
+
+    <sect2 id="sbindir_binaries">
+      <title>GDM Root User Commands</title>
+
+      <para>
+        The GDM package provides the following commands in
+        <filename>sbindir</filename> intended to be run 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>&lt;etc&gt;/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.  The <command>gdm-binary</command> is the actual GDM daemon.
+        </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>--fatal-warnings</term>
+            <listitem>
+              <para>
+                Make all warnings cause GDM to exit.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>--timed-exit</term>
+            <listitem>
+              <para>
+                Exit after 30 seconds.  Useful for debugging.
+              </para>
+            </listitem>
+          </varlistentry>
+
+          <varlistentry>
+            <term>--version</term>
+            <listitem>
+              <para>
+                Print the version of the GDM daemon.
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
+      </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>
+  </sect1>
+
+  <!-- ============= Troubleshooting =========================== -->
+
+  <sect1 id="troubleshooting">
+    <title>Troubleshooting</title>
+<!--
+<para>
+      TODO - any other tips we should add?  Might be useful to highlight any
+             common D-Bus configuration issues?
+</para>
+-->
+
+    <para>
+      This section discusses helpful tips for getting GDM working.  In general,
+      if you have a problem using GDM, you can submit a bug or send an email
+      to the gdm-list mailing list.  Information about how to do this is in
+      the Introduction section of the document.
+    </para>
+
+    <para>
+      If GDM is failing to work properly, it is always a good idea to include
+      debug information.  To enable debugging, set the debug/Enable key to
+      &quot;true&quot; in the <filename>&lt;etc&gt;/gdm/custom.conf</filename>
+      file and restart GDM.  Then use GDM to the point where it fails, and
+      debug output will be sent to the system log file
+      (<filename>&lt;var&gt;/log/messages</filename> or
+      <filename>&lt;var&gt;/adm/messages</filename> depending on your Operating
+      System).  If you share this output with the GDM community via a bug
+      report or email, please only include the GDM related debug information
+      and not the entire file since it can be large.  If you do not see any
+      GDM syslog output, you may need to configure syslog (refer to the
+      <ulink type="help" url="man:syslog">syslog</ulink> man page).
+    </para>
+
+    <sect2 id="wontstart">
+      <title>GDM Will Not Start</title>
+
+      <para>
+         There are a many problems that can cause GDM to fail to start, but
+         this section will discuss a few common problems and how to approach
+         tracking down a problem with GDM starting.   Some problems will 
+         cause GDM to respond with an error message or dialog when it tries
+         to start, but it can be difficult to track down problems when GDM
+         fails silently.
+      </para>
+
+      <para>
+         First make sure that the Xserver is configured properly.  The 
+         GDM configuration file contains a command in the [server-Standard]
+         section that is used for starting the Xserver.  Verify that this
+         command works on your system.  Running this command from the 
+         console should start the Xserver.  If it fails, then the problem
+         is likely with your Xserver configuration.  Refer to your Xserver
+         error log for an idea of what the problem may be.  The problem may
+         also be that your Xserver requires different command-line options.
+         If so, then modify the Xserver command in the GDM configuration file
+         so that it is correct for your system.
+      </para>
+
+      <para>
+         Also make sure that the <filename>/tmp</filename> directory has
+         reasonable ownership and permissions, and that the machine's file
+         system is not full.  These problems will cause GDM to fail to start.
+      </para>
+    </sect2>
+  </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>51 Franklin Street, Fifth Floor</street>
+      <city>Boston</city>, <state>MA</state> <postcode>02110-1301</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:
+-->               
diff --git a/docs/ca/ca.po b/docs/ca/ca.po
new file mode 100644
index 0000000..e1bd079
--- /dev/null
+++ b/docs/ca/ca.po
@@ -0,0 +1,3328 @@
+# Traducció del gdm de l'equip de Softcatalà.
+# Copyright © 2009 Free Software Foundation, Inc.
+# Joan Duran <jodufi@gmail.com>, 2009.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: gdm\n"
+"POT-Creation-Date: 2011-11-25 09:09+0000\n"
+"PO-Revision-Date: 2011-12-20 21:59+0100\n"
+"Last-Translator: Joan Duran <jodufi@gmail.com>\n"
+"Language-Team: Catalan <tradgnome@softcatala.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: C/gdm.xml:13(title)
+msgid "GNOME Display Manager Reference Manual"
+msgstr "Manual de referència del gestor de pantalla del GNOME"
+
+#: C/gdm.xml:17(revnumber)
+msgid "0.0"
+msgstr "0.0"
+
+#: C/gdm.xml:18(date)
+msgid "2008-09"
+msgstr "2008-09"
+
+#: C/gdm.xml:23(para)
+msgid "GDM is the GNOME Display Manager, a graphical login program."
+msgstr ""
+"El GDM és el gestor de pantalla del GNOME, un programa gràfic d'entrada."
+
+#: C/gdm.xml:30(firstname)
+msgid "Martin"
+msgstr "Martin"
+
+#: C/gdm.xml:30(othername)
+msgid "K."
+msgstr "K."
+
+#: C/gdm.xml:31(surname)
+msgid "Petersen"
+msgstr "Petersen"
+
+#: C/gdm.xml:33(email)
+msgid "mkp@mkp.net"
+msgstr "mkp@mkp.net"
+
+#: C/gdm.xml:37(firstname)
+msgid "George"
+msgstr "George"
+
+#: C/gdm.xml:37(surname)
+msgid "Lebl"
+msgstr "Lebl"
+
+#: C/gdm.xml:39(email)
+msgid "jirka@5z.com"
+msgstr "jirka@5z.com"
+
+#: C/gdm.xml:43(firstname)
+msgid "Jon"
+msgstr "Jon"
+
+#: C/gdm.xml:43(surname)
+msgid "McCann"
+msgstr "McCann"
+
+#: C/gdm.xml:45(email)
+msgid "mccann@jhu.edu"
+msgstr "mccann@jhu.edu"
+
+#: C/gdm.xml:49(firstname)
+msgid "Ray"
+msgstr "Ray"
+
+#: C/gdm.xml:49(surname)
+msgid "Strode"
+msgstr "Strode"
+
+#: C/gdm.xml:51(email)
+msgid "rstrode@redhat.com"
+msgstr "rstrode@redhat.com"
+
+#: C/gdm.xml:55(firstname)
+msgid "Brian"
+msgstr "Brian"
+
+#: C/gdm.xml:55(surname)
+msgid "Cameron"
+msgstr "Cameron"
+
+#: C/gdm.xml:57(email)
+msgid "Brian.Cameron@Oracle.COM"
+msgstr "Brian.Cameron@Oracle.COM"
+
+#: C/gdm.xml:62(year)
+msgid "1998"
+msgstr "1998"
+
+#: C/gdm.xml:63(year)
+msgid "1999"
+msgstr "1999"
+
+#: C/gdm.xml:64(holder)
+msgid "Martin K. Petersen"
+msgstr "Martin K. Petersen"
+
+#: C/gdm.xml:67(year)
+msgid "2001"
+msgstr "2001"
+
+#: C/gdm.xml:68(year) C/gdm.xml:73(year) C/gdm.xml:79(year)
+msgid "2003"
+msgstr "2003"
+
+#: C/gdm.xml:69(year)
+msgid "2004"
+msgstr "2004"
+
+#: C/gdm.xml:70(holder)
+msgid "George Lebl"
+msgstr "George Lebl"
+
+#: C/gdm.xml:74(year)
+msgid "2007"
+msgstr "2007"
+
+#: C/gdm.xml:75(year)
+msgid "2008"
+msgstr "2008"
+
+#: C/gdm.xml:76(holder)
+msgid "Red Hat, Inc."
+msgstr "Red Hat, Inc."
+
+#: C/gdm.xml:80(year)
+msgid "2011"
+msgstr "2011"
+
+#: C/gdm.xml:81(holder)
+msgid "Oracle and/or its affiliates. All rights reserved."
+msgstr "Oracle i els seus associats. Tots els drets reservats."
+
+#: C/gdm.xml:2(para)
+msgid ""
+"Permission is granted to copy, distribute and/or modify this document under "
+"the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any "
+"later version published by the Free Software Foundation with no Invariant "
+"Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy "
+"of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or "
+"in the file COPYING-DOCS distributed with this manual."
+msgstr ""
+"Teniu permís per copiar, distribuir i/o modificar aquest document, sota els "
+"termes de la Llicència de documentació lliure GNU (GFDL), versió 1.1 o "
+"qualsevol versió publicada posteriorment per la Free Software Foundation, "
+"sense seccions invariants, sense texts de portada i sense texts de "
+"contraportada. Podeu trobar una còpia de la GFDL en aquest <ulink type=\"help"
+"\" url=\"ghelp:fdl\">enllaç</ulink> o en el fitxer COPYING-DOCS distribuït "
+"amb aquest manual."
+
+#: C/gdm.xml:12(para)
+msgid ""
+"This manual is part of a collection of GNOME manuals distributed under the "
+"GFDL. If you want to distribute this manual separately from the collection, "
+"you can do so by adding a copy of the license to the manual, as described in "
+"section 6 of the license."
+msgstr ""
+"Aquest manual forma part d'una col·lecció de manuals del GNOME distribuïts "
+"sota la GFDL. Si voleu distribuir aquest manual independentment de la "
+"col·lecció, podeu fer-ho afegint una còpia de la llicència al manual, tal "
+"com es descriu a la secció 6 de la llicència."
+
+#: C/gdm.xml:19(para)
+msgid ""
+"Many of the names used by companies to distinguish their products and "
+"services are claimed as trademarks. Where those names appear in any GNOME "
+"documentation, and the members of the GNOME Documentation Project are made "
+"aware of those trademarks, then the names are in capital letters or initial "
+"capital letters."
+msgstr ""
+"Molts dels noms que les empreses utilitzen per distingir els seus productes "
+"i serveis es consideren marques comercials. Quan aquests noms apareguin en "
+"qualsevol documentació del GNOME, si els membres del Projecte de "
+"documentació del GNOME han estat avisats pel que fa a les marques, els noms "
+"apareixeran en majúscules o amb les inicials en majúscules."
+
+#: C/gdm.xml:35(para)
+msgid ""
+"DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, "
+"EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT "
+"THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS "
+"MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE "
+"RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR "
+"MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR "
+"MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL "
+"WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY "
+"SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN "
+"ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION "
+"OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND"
+msgstr ""
+"EL DOCUMENT S'OFEREIX «TAL COM ÉS», SENSE CAP TIPUS DE GARANTIA, NI EXPLÍCITA "
+"NI IMPLÍCITA; AIXÒ INCLOU, SENSE LIMITAR-S'HI, LES GARANTIES QUE EL DOCUMENT "
+"O LA VERSIÓ MODIFICADA DEL DOCUMENT NO TINGUI DEFECTES, SIGUI "
+"COMERCIALITZABLE, SIGUI ADEQUAT PER A UN ÚS CONCRET O NO INFRINGEIXI CAP "
+"LLEI. TOT EL RISC PEL QUE FA A LA QUALITAT, EXACTITUD I RENDIMENT DEL "
+"DOCUMENT O LA VERSIÓ MODIFICADA DEL DOCUMENT ÉS VOSTRE. EN CAS QUE EL "
+"DOCUMENT RESULTÉS DEFECTUÓS EN QUALSEVOL ASPECTE, VÓS (NO PAS L'ESCRIPTOR "
+"INICIAL, L'AUTOR O CAP ALTRE COL·LABORADOR) ASSUMIU TOT EL COST DE "
+"MANTENIMENT, REPARACIÓ O CORRECCIÓ. AQUESTA RENÚNCIA DE GARANTIA CONSTITUEIX "
+"UNA PART ESSENCIAL D'AQUESTA LLICÈNCIA. NO S'AUTORITZA L'ÚS DE CAP DOCUMENT "
+"O VERSIÓ MODIFICADA DEL DOCUMENT EXCEPTE SOTA AQUESTA RENÚNCIA DE GARANTIA; I"
+
+#: C/gdm.xml:55(para)
+msgid ""
+"UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING "
+"NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY "
+"CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE "
+"DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON "
+"FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF "
+"ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, "
+"WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES "
+"OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED "
+"VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE "
+"POSSIBILITY OF SUCH DAMAGES."
+msgstr ""
+"EN CAP CAS I SOTA CAP INTERPRETACIÓ LEGAL, JA SIGUI PER AGREUJAMENT "
+"(INCLOENT-HI LA NEGLIGÈNCIA), CONTRACTE O ALTRE CAS, L'AUTOR, L'ESCRIPTOR "
+"ORIGINAL, QUALSEVOL DELS COL·LABORADORS O DISTRIBUÏDORS DEL DOCUMENT O UNA "
+"VERSIÓ MODIFICADA DEL DOCUMENT NI CAP PROVEÏDOR D'AQUESTES PARTS NO SERAN "
+"RESPONSABLES DAVANT DE NINGÚ PER CAP DANY DIRECTE, INDIRECTE, ESPECIAL, "
+"ACCIDENTAL O CONSECUTIU DE QUALSEVOL TIPUS; AIXÒ INCLOU, SENSE LIMITAR-S'HI, "
+"ELS DANYS PER PÈRDUA DE CLIENTS, INTERRUPCIONS DE LA FEINA, FALLADA O "
+"MALFUNCIONAMENT DE L'ORDINADOR, O QUALSEVOL ALTRA PÈRDUA O DANY RELACIONAT "
+"AMB L'ÚS DEL DOCUMENT I LES VERSIONS MODIFICADES DEL DOCUMENT, FINS I TOT SI "
+"S'HA INFORMAT AQUESTA PART DE LA POSSIBILITAT D'AQUESTS DANYS."
+
+#: C/gdm.xml:28(para)
+msgid ""
+"DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS "
+"OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: "
+"<placeholder-1/>"
+msgstr ""
+"EL DOCUMENT I LES VERSIONS MODIFICADES DEL DOCUMENT S'OFEREIXEN SOTA ELS "
+"TERMES DE LA LLICÈNCIA DE DOCUMENTACIÓ LLIURE DE GNU, TENINT EN COMPTE QUE: "
+"<placeholder-1/>"
+
+#: C/gdm.xml:86(releaseinfo) C/gdm.xml:97(para)
+msgid ""
+"This manual describes version 2.26.0 of the GNOME Display Manager. It was "
+"last updated on 02/10/2009."
+msgstr ""
+"Aquest manual descriu la versió 2.26.0 del gestor de pantalla del GNOME. Es "
+"va actualitzar per últim cop el 10/02/2009."
+
+#: C/gdm.xml:95(title)
+msgid "Terms and Conventions Used in This Manual"
+msgstr "Termes i convencions utilitzats en aquest manual"
+
+#: C/gdm.xml:102(para)
+msgid ""
+"Chooser - A program used to select a remote host for managing a display "
+"remotely on the attached display (<command>gdm-host-chooser</command>)."
+msgstr ""
+"Seleccionador: un programa que s'utilitza per seleccionar un amfitrió remot "
+"per gestionar una pantalla remotament a la pantalla local (<command>gdm-host-"
+"chooser</command>)."
+
+#: C/gdm.xml:107(para)
+msgid ""
+"FreeDesktop - The organization providing desktop standards, such as the "
+"Desktop Entry Specification used by GDM. <ulink type=\"http\" url=\"http://"
+"www.freedesktop.org/\"> http://www.freedesktop.org</ulink>."
+msgstr ""
+"FreeDesktop: l'organització que proporciona estàndards per a l'escriptori, "
+"com ara l'especificació d'entrada de l'escriptori que utilitza el GDM. "
+"<ulink type=\"http\" url=\"http://www.freedesktop.org/\"> http://www."
+"freedesktop.org</ulink>."
+
+#: C/gdm.xml:113(para)
+msgid ""
+"GDM - GNOME Display Manager. Used to describe the software package as a "
+"whole."
+msgstr ""
+"GDM: el Gestor de pantalla del GNOME. S'utilitza per descriure el paquet de "
+"programari en la seva totalitat."
+
+#: C/gdm.xml:118(para)
+msgid ""
+"Greeter - The graphical login window (<command>gdm-simple-greeter</command>)."
+msgstr ""
+"Rebedor: la finestra d'entrada gràfica (<command>gdm-simple-greeter</"
+"command>)."
+
+#: C/gdm.xml:122(para)
+msgid "PAM - Pluggable Authentication Mechanism"
+msgstr "PAM: mòduls de connectors d'autenticació"
+
+#: C/gdm.xml:126(para)
+msgid "XDMCP - X Display Manage Protocol"
+msgstr "XDMCP: Protocol de gestió de pantalles d'X"
+
+#: C/gdm.xml:130(para)
+msgid ""
+"Xserver - An implementation of the X Window System. For example the Xorg "
+"Xserver provided by the X.org Foundation <ulink type=\"http\" url=\"http://"
+"www.x.org/\">http://www.x.org</ulink>."
+msgstr ""
+"Xserver: una implementació del sistema de finestres X. Per exemple el "
+"servidor d'X creat per la fundació X.org <ulink type=\"http\" url=\"http://"
+"www.x.org/\">http://www.x.org</ulink>."
+
+#: C/gdm.xml:136(para)
+msgid ""
+"Paths that start with a word in angle brackets are relative to the "
+"installation prefix. I.e. <filename>&lt;share&gt;/pixmaps/</filename> refers "
+"to <filename>/usr/share/pixmaps</filename> if GDM was configured with "
+"<command>--prefix=/usr</command>."
+msgstr ""
+"Els camins que comencen amb una paraula entre parèntesis angulars són "
+"relatius al prefix d'instal·lació. Per exemple, <filename>&lt;share&gt;/"
+"pixmaps/</filename> es refereix a <filename>/usr/share/pixmaps</filename> si "
+"el GDM es va configurar amb <command>--prefix=/usr</command>."
+
+#: C/gdm.xml:147(title)
+msgid "Overview"
+msgstr "Vista general"
+
+#: C/gdm.xml:150(title)
+msgid "Introduction"
+msgstr "Introducció"
+
+#: C/gdm.xml:152(para)
+msgid ""
+"The GNOME Display Manager (GDM) is a display manager that implements all "
+"significant features required for managing attached and remote displays. GDM "
+"was written from scratch and does not contain any XDM or X Consortium code."
+msgstr ""
+"El gestor de pantalla del GNOME (GDM) és un gestor de pantalla que "
+"implementa totes les funcions destacades que fan falta per gestionar "
+"pantalles locals i remotes. El GDM es va escriure des de zero i no conté cap "
+"codi de l'XDM o de l'X Consortium."
+
+#: C/gdm.xml:159(para)
+msgid ""
+"Note that GDM is configurable, and many configuration settings have an "
+"impact on security. Issues to be aware of are highlighted in this document."
+msgstr ""
+"Tingueu en compte que el GDM es pot configurar i que molts paràmetres de "
+"configuració poden afectar a la seguretat. En aquest document es ressalten "
+"els temes en que s'ha de vigilar."
+
+#: C/gdm.xml:165(para)
+msgid ""
+"Please note that some Operating Systems configure GDM to behave differently "
+"than the default values as described in this document. If GDM does not seem "
+"to behave as documented, then check to see if any related configuration may "
+"be different than described here."
+msgstr ""
+"Tingueu en compte que alguns sistemes operatius configuren el GDM per "
+"comportar-se de forma diferent als valors per defecte que es descriuen en "
+"aquest document. Si el GDM no sembla que es comporta com s'explica aquí, "
+"comproveu si alguna configuració relacionada és diferent a la descrita aquí."
+
+#: C/gdm.xml:172(para)
+msgid ""
+"For further information about GDM, refer to the project website at <ulink "
+"type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> http://www.gnome."
+"org/projects/gdm</ulink> and the project Wiki <ulink type=\"http\" url="
+"\"http://live.gnome.org/GDM\"> http://live.gnome.org/GDM</ulink>."
+msgstr ""
+"Per obtenir més informació sobre el GDM, consulteu el lloc web del projecte "
+"a <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\">http://www."
+"gnome.org/projects/gdm</ulink> i al Wiki del projecte <ulink type=\"http\" "
+"url=\"http://live.gnome.org/GDM\">http://live.gnome.org/GDM</ulink>."
+
+#: C/gdm.xml:180(para)
+msgid ""
+"For discussion or queries about GDM, refer to the <address><email>gdm-"
+"list@gnome.org</email></address> mail list. This list is archived, and is a "
+"good resource to check to seek answers to common questions. This list is "
+"archived at <ulink type=\"http\" url=\"http://mail.gnome.org/archives/gdm-"
+"list/\"> http://mail.gnome.org/archives/gdm-list/</ulink> and has a search "
+"facility to look for messages with keywords."
+msgstr ""
+"Per a qüestions o consultes sobre el GDM, consulteu la llista de correu "
+"<address><email>gdm-list@gnome.org</email></address>. Aquesta llista "
+"s'arxiva i és un bon recurs a comprovar per trobar respostes a les preguntes "
+"freqüents. Els arxius de la llista es troben a <ulink type=\"http\" url="
+"\"http://mail.gnome.org/archives/gdm-list/\">http://mail.gnome.org/archives/"
+"gdm-list/</ulink> i té una utilitat de cerca per cercar missatges amb "
+"paraules clau."
+
+#: C/gdm.xml:190(para)
+msgid ""
+"Please submit any bug reports or enhancement requests to the \"gdm\" "
+"category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\"> http://"
+"bugzilla.gnome.org</ulink>."
+msgstr ""
+"Envieu qualsevol informe d'error o sol·licituds de millora a la categoria "
+"«gdm» al <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">http://"
+"bugzilla.gnome.org</ulink>."
+
+#: C/gdm.xml:199(title)
+msgid "Interface Stability"
+msgstr "Estabilitat de la interfície"
+
+#: C/gdm.xml:201(para)
+msgid ""
+"GDM 2.20 and earlier supported stable configuration interfaces. However, the "
+"codebase was completely rewritten for GDM 2.22, and is not completely "
+"backward compatible with older releases. This is in part because things work "
+"differently, so some options just don't make sense, in part because some "
+"options never made sense, and in part because some functionality has not "
+"been reimplemented yet."
+msgstr ""
+"El GDM 2.20 i les versions anteriors admetien configuracions d'interfície "
+"estables. Tot i així, es va reescriure el codi totalment pel GDM 2.22 i no "
+"és del tot compatible amb les versions anteriors. Això és en part perquè ara "
+"funciona una mica diferent, de manera que algunes opcions no tenen cap "
+"sentit, entre d'altres coses perquè algunes opcions mai van tenir sentit i "
+"també perquè algunes funcions encara no s'han tornat a implementar."
+
+#: C/gdm.xml:210(para)
+msgid ""
+"Interfaces which continue to be supported in a stable fashion include the "
+"Init, PreSession, PostSession, PostLogin, and Xsession scripts. Some daemon "
+"configuration options in the <filename>&lt;etc&gt;/gdm/custom.conf</"
+"filename> file continue to be supported. Also, the <filename>~/.dmrc</"
+"filename>, and face browser image locations are still supported."
+msgstr ""
+"Les interfícies que encara són compatibles de manera estable inclouen els "
+"scripts Init, PreSession, PostSession, PostLogin i Xsession. Algunes opcions "
+"de configuració del dimoni en el fitxer <filename>&lt;etc&gt;/gdm/custom."
+"conf</filename> encara són compatibles. També encara són compatibles el "
+"<filename>~/.dmrc</filename> i les ubicacions del navegador d'imatges."
+
+#: C/gdm.xml:219(para)
+msgid ""
+"GDM 2.20 and earlier supported the ability to manage multiple displays with "
+"separate graphics cards, such as used in terminal server environments, login "
+"in a window via a program like Xnest or Xephyr, the gdmsetup program, XML-"
+"based greeter themes, and the ability to run the XDMCP chooser from the "
+"login screen. These features were not added back during the 2.22 rewrite."
+msgstr ""
+"El GDM 2.20 i les versions anteriors permetien gestionar diverses pantalles "
+"amb diferents targetes gràfiques, com s'utilitza en entorns de terminal de "
+"servidor, l'entrada dins d'una finestra mitjançant un programa com l'Xnest o "
+"el Xephyr, el programa gdmsetup, els temes de rebedor basats en XML i la "
+"capacitat d'executar el seleccionador XDMCP des de la pantalla d'entrada. "
+"Aquestes funcions no s'han tornat a afegir durant la reescriptura de la "
+"versió 2.22."
+
+#: C/gdm.xml:231(title)
+msgid "Functional Description"
+msgstr "Descripció funcional"
+
+#. <para>
+#.         TODO - Would be good to discuss D-Bus, perhaps the new GObject model,
+#.                and to explain the reasons why the rewrite made GDM better.
+#.                From a high-level overview perspective, rather than the
+#.                technical aspects.
+#. </para>
+#: C/gdm.xml:242(para)
+msgid ""
+"GDM is responsible for managing displays on the system. This includes "
+"authenticating users, starting the user session, and terminating the user "
+"session. GDM is configurable and the ways it can be configured are described "
+"in the \"Configuring GDM\" section of this document. GDM is also accessible "
+"for users with disabilities."
+msgstr ""
+"El GDM és el responsable de la gestió de les pantalles del sistema. Això "
+"inclou l'autenticació d'usuaris, l'inici de la sessió de l'usuari i la "
+"finalització d'aquesta. Les opcions de configuració del GDM estan descrites "
+"a la secció del document «Configuració del GDM». El GDM també és accessible "
+"per als usuaris amb discapacitats."
+
+#: C/gdm.xml:250(para)
+msgid ""
+"GDM provides the ability to manage the main console display, and displays "
+"launched via VT. It is integrated with other programs, such as the Fast User "
+"Switch Applet (FUSA) and gnome-screensaver to manage multiple displays on "
+"the console via the Xserver Virtual Terminal (VT) interface. It also can "
+"manage XDMCP displays."
+msgstr ""
+"El GDM proporciona la capacitat de gestionar la consola principal de la "
+"pantalla i les pantalles executades mitjançant el VT. S'integra amb altres "
+"programes, com ara la miniaplicació del commutador d'usuari ràpid (FUSA) i "
+"l'estalvi de pantalla (gnome-screensaver) per gestionar diverses pantalles a "
+"la consola mitjançant la interfície del terminal virtual (VT) del servidor "
+"d'X. També pot gestionar pantalles XDMCP."
+
+#: C/gdm.xml:258(para)
+msgid ""
+"Regardless of the display type, GDM will do the following when it manages "
+"the display. It will start an Xserver process, then run the <filename>Init</"
+"filename> script as the root user, and start the greeter program on the "
+"display."
+msgstr ""
+"Independentment del tipus de pantalla, el GDM realitzarà el següent quan "
+"gestioni la pantalla: iniciarà un procés del servidor d'X, seguidament "
+"executarà l'script <filename>Init</filename> com a usuari primari i iniciarà "
+"el programa rebedor a la pantalla."
+
+#: C/gdm.xml:265(para)
+msgid ""
+"The greeter program is run as the unprivileged \"gdm\" user/group. This user "
+"and group are described in the \"Security\" section of this document. The "
+"main functions of the greeter program are to provide a mechanism for "
+"selecting an account for log in and to drive the dialogue between the user "
+"and system when authenticating that account. The authentication process is "
+"driven by Pluggable Authentication Modules (PAM). The PAM modules determine "
+"what prompts (if any) are shown to the user to authenticate. On the average "
+"system, the greeter program will request a username and password for "
+"authentication. However some systems may be configured to use supplemental "
+"mechanisms such as a fingerprint or SmartCard readers. GDM can be configured "
+"to support these alternatives in parallel with greeter login extensions and "
+"the <command>--enable-split-authentication</command><filename>./configure</"
+"filename> option, or one at a time via system PAM configuration."
+msgstr ""
+"El programa rebedor s'executa amb l'usuari/grup sense privilegis «gdm». "
+"Aquest usuari i grup és descrit a la secció «Seguretat» d'aquest document. "
+"Les funcions principal del programa rebedor és proporcionar un mecanisme per "
+"seleccionar un compte per entrar i per conduir el diàleg entre l'usuari i el "
+"sistema en autenticar-se al compte. El procés d'autenticació és conduit pel "
+"mòduls de connectors d'autenticació (Pluggable Authentication Modules o "
+"PAM). Els mòduls del PAM determinen quines preguntes (si n'hi ha) es mostren "
+"a l'usuari per autenticar-lo. En sistemes mitjans, el programa rebedor "
+"sol·licitarà un nom d'usuari i una contrasenya per autenticar. Tot i això "
+"alguns sistemes es poden configurar per utilitzar sistemes alternatius com "
+"ara l'empremta dactilar o lectors de targetes SmartCard. El GDM es pot "
+"configurar per admetre aquestes alternatives en paral·lel amb extensions del "
+"rebedor d'entrada i l'opció <command>--enable-split-authentication</"
+"command><filename>./configure</filename> o només una a la vegada mitjançant "
+"el sistema de configuració PAM."
+
+#: C/gdm.xml:284(para)
+msgid ""
+"The smartcard extension can be enabled or disabled via the <filename>org."
+"gnome.display-manager.extensions.smartcard.active</filename> gsettings key."
+msgstr ""
+
+#: C/gdm.xml:290(para)
+msgid ""
+"Likewise, the fingerprint extension can be enabled or disabled via the "
+"<filename>org.gnome.display-manager.extensions.fingerprint.active</filename> "
+"gsettings key."
+msgstr ""
+
+#: C/gdm.xml:296(para)
+msgid ""
+"GDM and PAM can be configured to not require any input, which will cause GDM "
+"to automatically log in and simply start a session, which can be useful for "
+"some environments, such as single user systems or kiosks."
+msgstr ""
+
+#: C/gdm.xml:303(para)
+msgid ""
+"In addition to authentication, the greeter program allows the user to select "
+"which session to start and which language to use. Sessions are defined by "
+"files that end in the .desktop suffix and more information about these files "
+"can be found in the \"GDM User Session and Language Configuration\" section "
+"of this document. By default, GDM is configured to display a face browser so "
+"the user can select their user account by clicking on an image instead of "
+"having to type their username. GDM keeps track of the user's default session "
+"and language in the user's <filename>~/.dmrc</filename> and will use these "
+"defaults if the user did not pick a session or language in the login GUI."
+msgstr ""
+"A més de l'autenticació, el rebedor permet a l'usuari seleccionar quina "
+"sessió vol iniciar i quin idioma vol utilitzar. Les sessions es defineixen "
+"amb fitxers que finalitzen amb el sufix .desktop i en podeu obtenir més "
+"informació a la secció «Configuració de la sessió d'usuari i l'idioma» "
+"d'aquest document. Per defecte, el GDM està configurat per mostrar un "
+"navegador de cares de manera que l'usuari pugui seleccionar el seu compte "
+"d'usuari fent clic a una imatge enlloc d'haver d'introduir el seu nom "
+"d'usuari. El GDM manté la informació de la sessió i de l'idioma per defecte "
+"de l'usuari en el fitxer <filename>~/.dmrc</filename> i utilitzarà aquests "
+"valors si l'usuari no selecciona una sessió o idioma a la interfície gràfica "
+"d'usuari d'entrada."
+
+#: C/gdm.xml:316(para)
+msgid ""
+"After authenticating a user, the daemon runs the <filename>PostLogin</"
+"filename> script as root, then runs the <filename>PreSession</filename> "
+"script as root. After running these scripts, the user session is started. "
+"When the user exits their session, the <filename>PostSession</filename> "
+"script is run as root. These scripts are provided as hooks for distributions "
+"and end-users to customize how sessions are managed. For example, using "
+"these hooks you could set up a machine which creates the user's $HOME "
+"directory on the fly, and erases it on logout. The difference between the "
+"<filename>PostLogin</filename> and <filename>PreSession</filename> scripts "
+"is that <filename>PostLogin</filename> is run before the pam_open_session "
+"call so is the right place to do anything which should be run before the "
+"user session is initialized. The <filename>PreSession</filename> script is "
+"called after session initialization."
+msgstr ""
+"Després d'autenticar un usuari, el dimoni executa primer l'script "
+"<filename>PostLogin</filename> i després l'script <filename>PreSession</"
+"filename> com a usuari primari. Després de l'execució d'aquests scripts, "
+"s'iniciarà la sessió de l'usuari. Quan l'usuari surti de la sessió, "
+"s'executarà l'script <filename>PostSession</filename>, de nou com a usuari "
+"primari. Aquests scripts estan pensats com a punts de personalització, tan "
+"per les distribucions com pels usuaris finals, per personalitzar com es "
+"gestionen les sessions. Per exemple, utilitzant aquests punts de "
+"personalització podeu fer que una màquina creï el directori d'usuari $HOME "
+"sota demanda i el suprimeixi en sortir. La diferència entre els scripts "
+"<filename>PostLogin</filename> i <filename>PreSession</filename> és que "
+"l'script <filename>PostLogin</filename> s'executa abans de cridar el mètode "
+"pam_open_session, de manera que és el moment ideal per fer qualsevol cosa "
+"que s'hauria d'executar abans d'iniciar la sessió d'usuari. L'script "
+"<filename>PreSession</filename> es crida després d'iniciar la sessió."
+
+#: C/gdm.xml:336(title)
+msgid "Greeter Panel"
+msgstr "El quadre rebedor"
+
+#: C/gdm.xml:337(para)
+msgid ""
+"The GDM greeter program displays a panel docked at the bottom of the screen "
+"which provides additional functionality. When a user is selected, the panel "
+"allows the user to select which session, language, and keyboard layout to "
+"use after logging in. The keyboard layout selector also changes the keyboard "
+"layout used when typing your password. The panel also contains an area for "
+"login services to leave status icons. Some example status icons include a "
+"battery icon for current battery usage, and an icon for enabling "
+"accessibility features. The greeter program also provides buttons which "
+"allow the user to shutdown or restart the system. It is possible to "
+"configure GDM to not provide the shutdown and restart buttons, if desired. "
+"GDM can also be configured via PolicyKit (or via RBAC on Oracle Solaris) to "
+"require the user have appropriate authorization before accepting the "
+"shutdown or restart request."
+msgstr ""
+"El programa rebedor del GDM mostra un quadre acoblat a la part inferior de "
+"la pantalla que proporciona funcions addicionals. Quan es selecciona un "
+"usuari, el quadre permet seleccionar la sessió, l'idioma i la distribució "
+"del teclat que es vol utilitzar durant la sessió. El selector de la "
+"distribució del teclat també canvia la distribució del teclat quan "
+"s'introdueix la contrasenya. El quadre també conté una àrea on els serveis "
+"d'entrada poden deixar icones d'estat. Alguns exemples d'icones d'estat "
+"poden ser una icona de bateria amb la utilització actual de bateria i una "
+"icona per habilitar les funcions d'accessibilitat. El programa rebedor també "
+"proporciona botons que permeten a l'usuari aturar o tornar a iniciar el "
+"sistema. És possible configurar el GDM perquè no mostri els botons d'apagada "
+"i reinici. També es pot configurar mitjançant el PolicyKit (o mitjançant "
+"RBAC en Oracle Solaris) per sol·licitar que l'usuari tingui l'autorització "
+"necessària abans d'acceptar la sol·licitud d'apagada o reinici."
+
+#: C/gdm.xml:354(para)
+msgid ""
+"Note that keyboard layout features are only available on systems that "
+"support libxklavier."
+msgstr ""
+
+#: C/gdm.xml:361(title)
+msgid "Accessibility"
+msgstr "Accessibilitat"
+
+#: C/gdm.xml:363(para)
+msgid ""
+"GDM supports \"Accessible Login\", allowing users to log into their desktop "
+"session even if they cannot easily use the screen, mouse, or keyboard in the "
+"usual way. Accessible Technology (AT) features such as an on-screen "
+"keyboard, screen reader, screen magnifier, and Xserver AccessX keyboard "
+"accessibility are available. It is also possible to enable large text or "
+"high contrast icons and controls, if needed. Refer to the \"Accessibility "
+"Configuration\" section of the document for more information how various "
+"accessibility features can be configured."
+msgstr ""
+"El GDM admet l'«Entrada accessible», que permet als usuaris entrar a la "
+"sessió d'escriptori fins i tot si no poden utilitzar fàcilment la pantalla, "
+"el ratolí o el teclat de la manera habitual. Hi ha disponibles les funcions "
+"de la tecnologia assistiva (AT) com ara el teclat en pantalla, el lector de "
+"pantalla, l'ampliador de pantalla i l'accessibilitat del teclat del servidor "
+"d'X AccessX. Si és necessari, també és pot canviar el text per fer-lo més "
+"gran o mostrar icones i controls de contrast alt. Per a més informació sobre "
+"la configuració de les funcions d'accessibilitat, vegeu la secció "
+"«Configuració de l'accessibilitat» d'aquest document."
+
+#: C/gdm.xml:375(para)
+msgid ""
+"On some Operating Systems, it is necessary to make sure that the GDM user is "
+"a member of the \"audio\" group for AT programs that require audio output "
+"(such as text-to-speech) to be functional."
+msgstr ""
+"En alguns sistemes operatius és necessari assegurar-se que l'usuari del GDM "
+"és membre del grup «audio» per als programes de tecnologies assistives que "
+"utilitzen la sortida d'àudio (com ara el text-a-veu) per funcionar."
+
+#: C/gdm.xml:383(title)
+msgid "The GDM Face Browser"
+msgstr "El navegador de cares del GDM"
+
+#: C/gdm.xml:385(para)
+msgid ""
+"The Face Browser is the interface which allows users to select their "
+"username by clicking on an image. This feature can be enabled or disabled "
+"via the /apps/gdm/simple-greeter/disable_user_list GConf key and is on by "
+"default. When disabled, users must type their complete username by hand. "
+"When enabled, it displays all local users which are available for login on "
+"the system (all user accounts defined in the /etc/passwd file that have a "
+"valid shell and sufficiently high UID) and remote users that have recently "
+"logged in. The face browser in GDM 2.20 and earlier would attempt to display "
+"all remote users, which caused performance problems in large, enterprise "
+"deployments."
+msgstr ""
+"El navegador de cares és la interfície que permet als usuaris seleccionar el "
+"seu nom d'usuari en fer clic a una imatge. Es pot habilitar mitjançant la "
+"clau del GConf /apps/gdm/simple-greeter/disable_user_list i està habilitada "
+"per defecte. Si està inhabilitada, els usuaris han d'introduir el nom "
+"d'usuari complet a mà. Si està habilitat, es mostren tots els usuaris locals "
+"que hi ha disponibles per entrar al sistema (tots els comptes d'usuari "
+"definits al fitxer /etc/passwd que tenen un intèrpret d'ordres vàlid i un "
+"UID suficientment alt) i els usuaris remots que han entrat recentment. El "
+"navegador de cares del GDM 2.20 i versions anteriors intentava mostrar tots "
+"els usuaris remots, fet que provocava problemes de rendiment en entorns "
+"d'empresa grans."
+
+#: C/gdm.xml:399(para)
+msgid ""
+"The Face Browser is configured to display the users who log in most "
+"frequently at the top of the list. This helps to ensure that users who log "
+"in frequently can quickly find their login image."
+msgstr ""
+"El navegador de cares està configurat per mostrar els usuaris que entren amb "
+"més freqüència a la part superior de la llista. D'aquesta manera es facilita "
+"que els usuaris que entrin sovint puguin trobar ràpidament la seva imatge "
+"d'entrada."
+
+#: C/gdm.xml:405(para)
+msgid ""
+"The Face Browser supports \"type-ahead search\" which dynamically moves the "
+"face selection as the user types to the corresponding username in the list. "
+"This means that a user with a long username will only have to type the first "
+"few characters of the username before the correct item in the list gets "
+"selected."
+msgstr ""
+"El navegador d'imatges admet la «cerca en teclejar» que canvia dinàmicament "
+"la selecció de cares mentre l'usuari introdueix el nom d'usuari corresponent "
+"a la llista. Això significa que un usuari amb un nom d'usuari llarg només "
+"haurà d'introduir els primers caràcters del nom d'usuari abans que l'element "
+"correcte de la llista estigui seleccionat."
+
+#: C/gdm.xml:413(para)
+msgid ""
+"The icons used by GDM can be installed globally by the sysadmin or can be "
+"located in the user's home directories. If installed globally they should be "
+"in the <filename>&lt;share&gt;/pixmaps/faces/</filename> directory and the "
+"filename should be the name of the user. Face image files should be a "
+"standard image that GTK+ can read, such as PNG or JPEG. Face icons placed in "
+"the global face directory must be readable to the GDM user."
+msgstr ""
+"Les icones utilitzades pel GDM es poden instal·lar globalment per "
+"l'administrador del sistema o es poden ubicar al directori d'usuari. Si "
+"s'instal·len globalment haurien d'estar al directori <filename>&lt;share&gt;/"
+"pixmaps/faces/</filename> i el nom de fitxer hauria de ser el nom de "
+"l'usuari. Els fitxers d'imatge de cara haurien de ser una imatge estàndard "
+"que el GTK+ pugui llegir, com ara els formats PNG o JPEG. L'usuari del GDM "
+"ha de poder llegir les icones de cara ubicades al directori global de cares."
+
+#. <para>
+#.         TODO - In the old GDM the ~/gnome2/gdm file is used, but the new code
+#.                seems to use ~/.gnome/gdm.  Error?
+#. </para>
+#: C/gdm.xml:429(para)
+msgid ""
+"If there is no global icon for the user, GDM will look in the user's $HOME "
+"directory for the image file. GDM will first look for the user's face image "
+"in <filename>~/.face</filename>. If not found, it will try <filename>~/.face."
+"icon</filename>. If still not found, it will use the value defined for "
+"\"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file."
+msgstr ""
+"Si no hi ha cap icona global per l'usuari, el GDM cercarà el fitxer d'imatge "
+"al directori de l'usuari. El GDM primer cercarà la imatge de cara de "
+"l'usuari a <filename>~/.face</filename>. Si no el troba, ho provarà a "
+"<filename>~/.face.icon</filename>. Si encara no el troba, utilitzarà el "
+"valor definit per «face/picture=» al fitxer <filename>~/.gnome2/gdm</"
+"filename>."
+
+#: C/gdm.xml:438(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 "
+"fallback to a generic face image."
+msgstr ""
+"Si un usuari no ha definit cap imatge de cara, el GDM utilitzarà la icona "
+"«stock_person» definida en el tema actual del GTK+. Si no està definida, "
+"llavors s'utilitzarà una imatge de cara genèrica."
+
+#: C/gdm.xml:444(para)
+msgid ""
+"Please note that loading and scaling face icons located in remote user home "
+"directories can be a very time-consuming task. Since it not practical to "
+"load images over NIS or NFS, GDM does not attempt to load face images from "
+"remote home directories."
+msgstr ""
+"Tingueu en compte que la càrrega i l'escalat d'icones d'imatge ubicades a "
+"directoris d'usuari remots pot tardar molt. Com que no és pràctic carregar "
+"imatges mitjançant NIS o NFS, el GDM no intentarà carregar imatges de cara "
+"des de directoris d'usuari remots."
+
+#: C/gdm.xml:451(para)
+msgid ""
+"When the browser is turned on, valid usernames on the computer are exposed "
+"for everyone to see. If XDMCP is enabled, then the usernames are exposed to "
+"remote users. This, of course, limits security somewhat since a malicious "
+"user does not need to guess valid usernames. In some very restrictive "
+"environments the face browser may not be appropriate."
+msgstr ""
+"Quan el navegador està habilitat, es mostren els noms d'usuari vàlids de "
+"l'ordinador a tothom. Si l'XDMCP està habilitat, llavors els noms d'usuari "
+"es mostren a usuaris remots. Això, per suposat, limita la seguretat d'alguna "
+"manera ja que un usuari malintencionat no ha d'endevinar possibles noms "
+"d'usuari vàlids. En alguns entorns molt restrictius el navegador de cares "
+"pot no ser apropiat."
+
+#: C/gdm.xml:463(title)
+msgid "XDMCP"
+msgstr "XDMCP"
+
+#. <para>
+#.         TODO - What XDMCP features actually work?   I know that the
+#.                chooser is missing.
+#. </para>
+#: C/gdm.xml:472(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 "
+"turned off, but can be enabled if desired. If GDM is built with TCP Wrapper "
+"support, then the daemon will only grant access to hosts specified in the "
+"GDM service section in the TCP Wrappers configuration file."
+msgstr ""
+"El dimoni del GDM es pot configurar per escoltar i gestionar les "
+"sol·licituds del X Display Manage Protocol (XDMCP) de les pantalles remotes. "
+"Per defecte la compatibilitat de l'XDMCP està inhabilitada, però es pot "
+"habilitar si es vol. Si el GDM està construït amb compatibilitat de "
+"l'embolcall TCP, llavors el dimoni només permetrà l'accés a amfitrions "
+"especificats a la secció de servei del GDM al fitxer de configuració de "
+"l'embolcall TCP."
+
+#: C/gdm.xml:481(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 "
+"timeouts, etc. can be fine tuned. The default configuration should work "
+"reasonably on most systems."
+msgstr ""
+"El GDM inclou diverses mesures per fer-lo més resistent als atacs de "
+"denegació de servei al servei XDMCP. Molts dels paràmetres del protocol "
+"(temps d'espera de confirmació de connexió, etc.) es poden ajustar finament. "
+"La configuració estàndard hauria de funcionar bé en la majoria de sistemes."
+
+#: C/gdm.xml:488(para)
+msgid ""
+"GDM by default listens for XDMCP requests on the normal UDP port used for "
+"XDMCP, port 177, and will respond to QUERY and BROADCAST_QUERY requests by "
+"sending a WILLING packet to the originator."
+msgstr ""
+"Per defecte el GDM escolta les sol·licituds XDMCP al port UDP normal que "
+"s'utilitza per l'XDMCP, el port 177, i respondrà a les sol·licituds QUERY i "
+"BROADCAST_QUERY enviant un paquet WILLING a la font de la sol·licitud."
+
+#: C/gdm.xml:494(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 "
+"forward subsequent requests to the chosen manager. GDM also supports an "
+"extension to the protocol which will make it forget the redirection once the "
+"user's connection succeeds. This extension is only supported if both daemons "
+"are GDM. It is transparent and will be ignored by XDM or other daemons that "
+"implement XDMCP."
+msgstr ""
+"El GDM també es pot configurar perquè respecti les sol·licituds INDIRECT i "
+"mostri un seleccionador d'amfitrió a la pantalla remota. El GDM recordarà "
+"l'opció de l'usuari i reenviarà les següents sol·licituds al gestor "
+"seleccionat. El GDM també admet una extensió al protocol per oblidar el "
+"redireccionament un cop la connexió de l'usuari sigui satisfactòria. Aquesta "
+"extensió només és compatible si el dos dimonis són GDM. És transparent i "
+"l'ignorarà l'XDM o els altres dimonis que implementen l'XDMCP."
+
+#: C/gdm.xml:504(para)
+msgid ""
+"If XDMCP seems to not be working, make sure that all machines are specified "
+"in <filename>/etc/hosts</filename>."
+msgstr ""
+"Si l'XDMCP sembla que no funciona, assegureu-vos que tots els ordinadors "
+"estan especificats a <filename>/etc/hosts</filename>."
+
+#: C/gdm.xml:509(para)
+msgid ""
+"Refer to the \"Security\" section for information about security concerns "
+"when using XDMCP."
+msgstr ""
+"Consulteu la secció «Seguretat» per obtenir més informació sobre les notes de "
+"seguretat quan s'utilitza l'XDMCP."
+
+#: C/gdm.xml:516(title)
+msgid "Logging"
+msgstr "Registre"
+
+#: C/gdm.xml:518(para)
+msgid ""
+"GDM uses syslog to log errors and status. It can also log debugging "
+"information, which can be useful for tracking down problems if GDM is not "
+"working properly. Debug output can be enabled by setting the debug/Enable "
+"key to \"true\" in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file."
+msgstr ""
+"El GDM utilitza el registre del sistema per registrar els errors i l'estat. "
+"També pot registrar informació de depuració, la qual pot ser útil per "
+"descobrir problemes si el GDM no funciona correctament. Es pot habilitar la "
+"sortida de depuració si es canvia la clau «debug/Enable» a «true» al fitxer "
+"<filename>&lt;etc&gt;/gdm/custom.conf</filename>."
+
+#: C/gdm.xml:526(para)
+msgid ""
+"Output from the various Xservers is stored in the GDM log directory, which "
+"is normally <filename>&lt;var&gt;/log/gdm/</filename>. Any Xserver messages "
+"are saved to a file associated with the display value, <filename>&lt;"
+"display&gt;.log</filename>."
+msgstr ""
+"La sortida dels diversos servidors X s'emmagatzema al directori de registre "
+"del GDM, que normalment és el <filename>&lt;var&gt;/log/gdm/</filename>. "
+"Tots els missatges del servidor d'X es desen a un fitxer associat amb el "
+"valor de la pantalla, <filename>&lt;display&gt;.log</filename>."
+
+#: C/gdm.xml:533(para)
+msgid ""
+"The session output is piped through the GDM daemon to the <filename>~/."
+"xsession-errors</filename> file. The file is overwritten on each login, so "
+"logging out and logging back into the same user via GDM will cause any "
+"messages from the previous session to be lost."
+msgstr ""
+"La sortida de la sessió és conduïda a través del dimoni GDM al fitxer "
+"<filename>~/.xsession-errors</filename>. Se sobreescriu el fitxer a cada "
+"entrada, de manera que en sortir i tornar a entrar amb el mateix usuari "
+"mitjançant el GDM provocarà que es perdin els missatges de la sessió "
+"anterior."
+
+#: C/gdm.xml:540(para)
+msgid ""
+"Note that if GDM can not create this file for some reason, then a fallback "
+"file will be created named <filename>~/.xsession-errors.XXXXXXXX</filename> "
+"where the <filename>XXXXXXXX</filename> are some random characters."
+msgstr ""
+"Si pel que sigui el GDM no pot crear aquest fitxer, es crearà un fitxer "
+"alternatiu anomenat <filename>~/.xsession-errors.XXXXXXXX</filename> on les "
+"<filename>XXXXXXXX</filename> seran alguns caràcters aleatoris."
+
+#: C/gdm.xml:548(title)
+msgid "Fast User Switching"
+msgstr "Com commutar d'usuari ràpidament"
+
+#: C/gdm.xml:550(para)
+msgid ""
+"GDM allows multiple users to be logged in at the same time. After one user "
+"is logged in, additional users can log in via the User Switcher on the GNOME "
+"Panel, or from the \"Switch User\" button in Lock Screen dialog of GNOME "
+"Screensaver. The active session can be changed back and forth using the same "
+"mechanism. Note that some distributions may not add the User Switcher to the "
+"default panel configuration. It can be added using the panel context menu."
+msgstr ""
+"El GDM permet a diversos usuaris entrar a la mateixa vegada. Després que un "
+"usuari hagi entrat, poden entrar més usuaris mitjançant el commutador "
+"d'usuari al quadre del GNOME o des del botó «Commuta l'usuari» al diàleg de "
+"bloqueig de la pantalla de l'estalvi de pantalla del GNOME. La sessió activa "
+"es pot canviar de nou utilitzant el mateix mecanisme. Tingueu en compte que "
+"algunes distribucions no afegeixen el commutador d'usuari a la configuració "
+"per defecte del quadre. El podeu afegir a través del menú contextual del "
+"quadre."
+
+#: C/gdm.xml:559(para)
+msgid ""
+"Note this feature is available on systems that support Virtual Terminals. "
+"This feature will not function if Virtual Terminals is not available."
+msgstr ""
+
+#: C/gdm.xml:570(title)
+msgid "Security"
+msgstr "Seguretat"
+
+#: C/gdm.xml:573(title)
+msgid "The GDM User And Group"
+msgstr "L'usuari i grup del GDM"
+
+#: C/gdm.xml:575(para)
+msgid ""
+"For security reasons a dedicated user and group id are recommended for "
+"proper operation. This user and group are normally \"gdm\" on most systems, "
+"but can be configured to any user or group. All GDM GUI programs are run as "
+"this user, so that the programs which interact with the user are run in a "
+"sandbox. This user and group should have limited privilege."
+msgstr ""
+"Per raons de seguretat es recomana un identificador d'usuari i de grup "
+"específic pel correcte funcionament. A la majoria de sistemes aquest usuari "
+"i grup normalment és el «gdm», però pot ser qualsevol usuari o grup. Tots els "
+"programes d'interfície gràfica d'usuari del GDM s'executen amb aquest "
+"usuari, de manera que els programes que interactuen amb l'usuari s'executen "
+"en un entorn aïllat. L'usuari i el grup haurien de tenir els privilegis "
+"limitats."
+
+#: C/gdm.xml:584(para)
+msgid ""
+"The only special privilege the \"gdm\" user requires is the ability to read "
+"and write Xauth files to the <filename>&lt;var&gt;/run/gdm</filename> "
+"directory. The <filename>&lt;var&gt;/run/gdm</filename> directory should "
+"have root:gdm ownership and 1777 permissions."
+msgstr ""
+"L'únic privilegi especial que necessita l'usuari «gdm» és la capacitat de "
+"llegir i escriure fitxers Xauth al directori <filename>&lt;var&gt;/run/gdm</"
+"filename>. El propietari del directori <filename>&lt;var&gt;/run/gdm</"
+"filename> hauria de ser root i del grup gdm amb els permisos 1777."
+
+#: C/gdm.xml:592(para)
+msgid ""
+"You should not, under any circumstances, configure the GDM user/group to a "
+"user which a user could easily gain access to, such as the user "
+"<filename>nobody</filename>. Any user who gains access to an Xauth key can "
+"snoop on and control running GUI programs running in the associated session "
+"or perform a denial-of-service attack on it. It is important to ensure that "
+"the system is configured properly so that only the \"gdm\" user has access "
+"to these files and that it is not easy to login to this account. For "
+"example, the account should be setup to not have a password or allow non-"
+"root users to login to the account."
+msgstr ""
+"No hauríeu, baix cap concepte, de configurar l'usuari/grup del GDM a un "
+"usuari sobre el qual un usuari pogués guanyar-ne fàcilment accés, com ara "
+"l'usuari <filename>nobody</filename>. Qualsevol usuari que guanyi accés a "
+"una clau Xauth pot tafanejar i controlar programes en execució de la "
+"interfície gràfica d'usuari associats a la sessió, o realitzar-hi un atac de "
+"denegació de servei. És important assegurar-se que el sistema està "
+"configurat adequadament de manera que només l'usuari «gdm» té accés a aquests "
+"fitxers i que no és fàcil entrar a aquest compte. Per exemple, el compte "
+"s'hauria de configurar perquè no tingui contrasenya o no permetre que "
+"usuaris no primaris puguin entrar-hi."
+
+#: C/gdm.xml:605(para)
+msgid ""
+"The GDM greeter configuration is stored in GConf. To allow the GDM user to "
+"be able to write configuration, it is necessary for the \"gdm\" user to have "
+"a writable $HOME directory. Users may configure the default GConf "
+"configuration as desired to avoid the need to provide the \"gdm\" user with "
+"a writable $HOME directory. However, some features of GDM may be disabled if "
+"it is unable to write state information to GConf configuration."
+msgstr ""
+"La configuració del rebedor del GDM s'emmagatzema al GConf. Per permetre que "
+"l'usuari GDM pugui escriure la configuració, és necessari que l'usuari «gdm» "
+"tingui un directori d'usuari amb permisos d'escriptura. Els usuaris poden "
+"configurar la configuració per defecte del GConf com desitgin per evitar la "
+"necessitat de proporcionar a l'usuari «gdm» un directori d'usuari amb "
+"permisos d'escriptura. Tot i això, es poden inhabilitar algunes funcions del "
+"GDM si no es pot escriure informació d'estat a la configuració del GConf"
+
+#: C/gdm.xml:617(title)
+msgid "PAM"
+msgstr "PAM"
+
+#: C/gdm.xml:619(para)
+msgid ""
+"GDM uses PAM for login authentication. PAM stands for Pluggable "
+"Authentication Module, and is used by most programs that request "
+"authentication on your computer. It allows the administrator to configure "
+"specific authentication behavior for different login programs (such as ssh, "
+"login GUI, screensaver, etc.)"
+msgstr ""
+"El GDM utilitza el PAM per a l'autenticació d'entrada. PAM significa mòduls "
+"de connectors d'autenticació (Pluggable Authentication Modules) i "
+"l'utilitzen la majoria de programes que sol·liciten autenticació a "
+"l'ordinador. Això permet a l'administrador configurar els comportaments "
+"d'autenticació específics per diferents programes d'entrada (com ara el ssh, "
+"la interfície gràfica d'entrada, l'estalvi de pantalla, etc.)"
+
+#: C/gdm.xml:627(para)
+msgid ""
+"PAM is complicated and highly configurable, and this documentation does not "
+"intend to explain this in detail. Instead, it is intended to give an "
+"overview of how PAM configuration relates with GDM, how PAM is commonly "
+"configured with GDM, and known issues. It is expected that a person needing "
+"to do PAM configuration would need to do further reading of PAM "
+"documentation to understand how to configure PAM and to understand terms "
+"used in this section."
+msgstr ""
+"El PAM és complicat i altament configurable i en aquesta documentació no "
+"s'intenta d'explicar-lo amb pèls i senyals. La idea és donar una visó global "
+"de com afecta la configuració del PAM al GDM, com es configura normalment el "
+"PAM amb el GDM i els problemes coneguts. S'espera que qui hagi de realitzar "
+"una configuració del PAM llegirà més documentació del PAM per entendre com "
+"configurar-lo i entendre'n els termes utilitzats en aquesta secció."
+
+#: C/gdm.xml:637(para)
+msgid ""
+"PAM configuration has different, but similar, interfaces on different "
+"Operating Systems, so check the <ulink type=\"help\" url=\"man:pam.d\">pam."
+"d</ulink> or <ulink type=\"help\" url=\"man:pam.conf\">pam.conf</ulink> man "
+"page for details. Be sure you read the PAM documentation and are comfortable "
+"with the security implications of any changes you intend to make to your "
+"configuration."
+msgstr ""
+"La configuració del PAM te interfícies diferents, però similars, segons el "
+"sistema operatiu, de manera que comproveu les pàgines del manual del <ulink "
+"type=\"help\" url=\"man:pam.d\">pam.d</ulink> o del <ulink type=\"help\" url="
+"\"man:pam.conf\">pam.conf</ulink> per obtenir-ne tots els detalls. Assegureu-"
+"vos que llegiu la documentació del PAM i que esteu segurs de les "
+"implicacions de seguretat que qualsevol canvi que intenteu realitzar a la "
+"configuració pot ocasionar."
+
+#: C/gdm.xml:647(para)
+msgid ""
+"Note that, by default, GDM uses the \"gdm\" PAM service name for normal "
+"login and the \"gdm-autologin\" PAM service name for automatic login. These "
+"services may not be defined in your pam.d or pam.conf configured file. If "
+"there is no entry, then GDM will use the default PAM behavior. On most "
+"systems this should work fine. However, the automatic login feature may not "
+"work if the gdm-autologin service is not defined."
+msgstr ""
+"Tingueu en compte que, per defecte, el GDM utilitza el nom de servei del PAM "
+"«gdm» per a una entrada normal i el nom de servei del PAM «gdm-autologin» per "
+"a una entrada automàtica. Pot ser que aquests serveis no estiguin definits "
+"al fitxer de configuració pam.d o pam.conf. Si no hi ha cap entrada el GDM "
+"utilitzarà el comportament per defecte del PAM. A la majoria de sistemes "
+"aquest hauria de funciona sense cap problema. Tot i això, la funció "
+"d'entrada automàtica podria no funcionar si el servei gdm-autologin no està "
+"definit."
+
+#: C/gdm.xml:657(para)
+msgid ""
+"The <filename>PostLogin</filename> script is run before pam_open_session is "
+"called, and the <filename>PreSession</filename> script is called after. This "
+"allows the system administrator to add any scripting to the login process "
+"either before or after PAM initializes the session."
+msgstr ""
+"L'script <filename>PostLogin</filename> s'executa abans de cridar "
+"pam_open_session i l'script <filename>PreSession</filename> després. Això "
+"permet a l'administrador del sistema afegir qualsevol script al procés "
+"d'entrada abans o després que el PAM iniciï la sessió."
+
+#: C/gdm.xml:665(para)
+msgid ""
+"If you wish to make GDM work with other types of authentication mechanisms "
+"(such as a fingerprint or SmartCard reader), then you should implement this "
+"by using a PAM service module for the desired authentication type rather "
+"than by trying to modify the GDM code directly. Refer to the PAM "
+"documentation on your system. How to do this is frequently discussed on the "
+"<address><email>gdm-list@gnome.org</email></address> mail list, so you can "
+"refer to the list archives for more information."
+msgstr ""
+"Si voleu fer que el GDM funcioni amb altres tipus de mecanismes "
+"d'autenticació (com ara una empremta dactilar o un lector de targetes "
+"SmartCard), llavors hauríeu d'implementar-ho utilitzant un mòdul de servei "
+"del PAM per al tipus d'autenticació desitjat en comptes d'intentar modificar "
+"el codi del GDM directament. Consulteu la documentació del PAM del sistema. "
+"Se'n parla sovint a la llista de correu <address><email>gdm-list@gnome.org</"
+"email></address>, de manera que podeu consultar els arxius de la llista per "
+"saber-ne més."
+
+#: C/gdm.xml:676(para)
+msgid ""
+"PAM does have some limitations regarding being able to work with multiple "
+"types of authentication at the same time, like supporting the ability to "
+"accept either SmartCard and the ability to type the username and password "
+"into the login program. There are techniques that are used to make this "
+"work, and it is best to research how this problem is commonly solved when "
+"setting up such a configuration."
+msgstr ""
+"El PAM té algunes limitacions relacionades en ser capaç de treballar amb "
+"diversos tipus d'autenticació a la vegada, admetre l'habilitat d'acceptar "
+"targetes SmartCard i introduir el nom d'usuari i la contrasenya al programa "
+"d'entrada. S'utilitzen diverses tècniques per fer que això funcioni i és una "
+"bona idea conèixer-les si es vol utilitzar una configuració semblant."
+
+#: C/gdm.xml:685(para)
+msgid ""
+"If automatic login does not work on a system, check to see if the \"gdm-"
+"autologin\" PAM stack is defined in the PAM configuration. For this to work, "
+"it is necessary to use a PAM module that simply does no authentication, or "
+"which simply returns PAM_SUCCESS from all of its public interfaces. Assuming "
+"your system has a pam_allow.so PAM module which does this, a PAM "
+"configuration to enable \"gdm-autologin\" would look like this:"
+msgstr ""
+"Si a un sistema no funciona l'entrada automàtica, comproveu si la pila del "
+"PAM «gdm-autologin» està definida a la configuració del PAM. Per fer-ho "
+"funcionar, és necessari utilitzar un mòdul del PAM que simplement no faci "
+"autenticació o que simplement retorni PAM_SUCCESS des de totes les "
+"interfícies públiques. Si s'assumeix que el sistema té un mòdul del PAM "
+"pam_allow.so que fa això, una configuració del PAM per habilitar el «gdm-"
+"autologin» podria ser aquesta:"
+
+#: C/gdm.xml:695(screen)
+#, no-wrap
+msgid ""
+"\n"
+"       gdm-autologin auth  required    pam_unix_cred.so.1\n"
+"       gdm-autologin auth  sufficient  pam_allow.so.1\n"
+"       gdm-autologin account  sufficient  pam_allow.so.1\n"
+"       gdm-autologin session  sufficient  pam_allow.so.1\n"
+"       gdm-autologin password  sufficient  pam_allow.so.1\n"
+msgstr ""
+"\n"
+"       gdm-autologin auth  required    pam_unix_cred.so.1\n"
+"       gdm-autologin auth  sufficient  pam_allow.so.1\n"
+"       gdm-autologin account  sufficient  pam_allow.so.1\n"
+"       gdm-autologin session  sufficient  pam_allow.so.1\n"
+"       gdm-autologin password  sufficient  pam_allow.so.1\n"
+
+#: C/gdm.xml:703(para)
+msgid ""
+"The above setup will cause no lastlog entry to be generated. If a lastlog "
+"entry is desired, then use the following for the session:"
+msgstr ""
+"La configuració anterior provocarà que no es generi cap entrada de lastlog. "
+"Si voleu una entrada de lastlog, llavors utilitzeu el següent per a la "
+"sessió:"
+
+#: C/gdm.xml:708(screen)
+#, no-wrap
+msgid ""
+"\n"
+"       gdm-autologin session required pam_unix_session.so.1\n"
+msgstr ""
+"\n"
+"       gdm-autologin session required pam_unix_session.so.1\n"
+
+#: C/gdm.xml:712(para)
+msgid ""
+"If the computer is used by several people, which makes automatic login "
+"unsuitable, you may want to allow some users to log in without entering "
+"their password. This feature can be enabled as a per-user option in the "
+"users-admin tool from the gnome-system-tools; it is achieved by checking "
+"that the user is member a Unix group called \"nopasswdlogin\" before asking "
+"for a password. For this to work, the PAM configuration file for the \"gdm\" "
+"service must include a line such as:"
+msgstr ""
+
+#: C/gdm.xml:723(screen)
+#, no-wrap
+msgid ""
+"\n"
+"      gdm auth  sufficient  pam_succeed_if.so  user ingroup nopasswdlogin\n"
+msgstr ""
+"\n"
+"      gdm auth  sufficient  pam_succeed_if.so  user ingroup nopasswdlogin\n"
+
+#: C/gdm.xml:730(title)
+msgid "utmp and wtmp"
+msgstr "utmp i wtmp"
+
+#: C/gdm.xml:732(para)
+msgid ""
+"GDM generates utmp and wtmp User Accounting Database entries upon session "
+"login and logout. The utmp database contains user access and accounting "
+"information that is accessed by commands such as <command>finger</command>, "
+"<command>last</command>, <command>login</command>, and <command>who</"
+"command>. The wtmp database contains the history of user access and "
+"accounting information for the utmp database. Refer to the <ulink type=\"help"
+"\" url=\"man:utmp\">utmp</ulink> and <ulink type=\"help\" url=\"man:wtmp"
+"\">wtmp</ulink> man pages on your system for more information."
+msgstr ""
+"El GDM genera entrades utmp i wtmp a la base de dades de comptes d'usuari "
+"quan l'usuari entra i surt de la sessió. La base de dades utmp conté "
+"informació de l'accés de l'usuari i del compte que hi accedeixen ordres com "
+"ara el <command>finger</command>, el <command>last</command>, el "
+"<command>login</command> i el <command>who</command>. La base de dades wtmp "
+"conté l'historial de la informació de l'accés de l'usuari i del compte per a "
+"la base de dades utmp. Per obtenir més informació consulteu les pàgines del "
+"manual del sistema <ulink type=\"help\" url=\"man:utmp\">utmp</ulink> i "
+"<ulink type=\"help\" url=\"man:wtmp\">wtmp</ulink>."
+
+#: C/gdm.xml:747(title)
+msgid "Xserver Authentication Scheme"
+msgstr "Esquema d'autenticació del servidor d'X"
+
+#: C/gdm.xml:749(para)
+msgid ""
+"Xserver authorization files are stored in a newly created subdirectory of "
+"<filename>&lt;var&gt;/run/gdm</filename> at start up. These files are used "
+"to store and share a \"password\" between X clients and the Xserver. This "
+"\"password\" is unique for each session logged in, so users from one session "
+"can't snoop on users from another."
+msgstr ""
+"Els fitxers d'autorització del servidor d'X s'emmagatzemen en un "
+"subdirectori nou a <filename>&lt;var&gt;/run/gdm</filename> que es crea a "
+"l'inici. Els fitxers serveixen per emmagatzemar i compartir una «contrasenya» "
+"entre els clients d'X i el servidor d'X. Aquesta «contrasenya» és única per a "
+"cada sessió d'entrada, de manera que els usuaris d'una sessió no poden "
+"tafanejar a usuaris d'una altra."
+
+#: C/gdm.xml:757(para)
+msgid ""
+"GDM only supports the MIT-MAGIC-COOKIE-1 Xserver 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 Xserver 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. In most cases, ssh -Y should be preferred over GDM's XDMCP features."
+msgstr ""
+"El GDM només admet l'esquema d'autenticació MIT-MAGIC-COOKIE-1 del servidor "
+"d'X. La resta d'esquemes no aporten gairebé cap benefici, de manera que no "
+"s'ha realitzat cap esforç per implementar-los. Vigileu especialment la "
+"utilització de l'XDMCP perquè les galetes d'autenticació del servidor d'X "
+"circulen per la xarxa com a text pla. Si és possible tafanejar, llavors un "
+"atacant podria simplement tafanejar la vostra contrasenya d'autenticació "
+"quan entreu, independentment de l'esquema d'autenticació que s'utilitzes. Si "
+"és possible tafanejar però no és desitjable, llavors hauríeu d'utilitzar "
+"l'SSH per fer una tunelització d'una connexió d'X en comptes d'utilitzar "
+"l'XDMCP. Podeu pensar que l'XDMCP és una espècie de telnet gràfic, que té "
+"els mateixos problemes de seguretat. En la majoria de casos, s'hauria de fer "
+"servir l'SSH -Y en comptes de les funcions XDMCP del GDM."
+
+#: C/gdm.xml:774(title)
+msgid "XDMCP Security"
+msgstr "Seguretat de l'XDMCP"
+
+#: C/gdm.xml:776(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 ""
+"Encara que la pantalla està protegida per galetes, els XEvents i les "
+"pulsacions de tecles quan s'introdueix la contrasenya encara circularan per "
+"la xarxa com a text pla. És trivial capturar-les."
+
+#: C/gdm.xml:782(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. This type of set up should never use an unmanaged hub or "
+"other sniffable network."
+msgstr ""
+"L'XDMCP és útil principalment per executar clients lleugers com ara en "
+"terminals de laboratori. Aquests clients lleugers només necessiten la xarxa "
+"per accedir al servidor i per tant sembla que la millor política de "
+"seguretat és tenir aquests clients lleugers en una xarxa separada a la qual "
+"no es pot accedir des del món exterior i només es pot connectar al servidor. "
+"L'únic punt des d'on necessiteu accedir a fora és el servidor. Aquest tipus "
+"de configuració no hauria d'utilitzar un concentrador no gestionat o una "
+"altre xarxa que es pugui vigilar."
+
+#: C/gdm.xml:795(title)
+msgid "XDMCP Access Control"
+msgstr "Control d'accés de l'XDMCP"
+
+#: C/gdm.xml:797(para)
+msgid ""
+"XDMCP access control is done using TCP wrappers. It is possible to compile "
+"GDM without TCP wrapper support, so this feature may not be supported on "
+"some Operating Systems."
+msgstr ""
+"El control d'accés de l'XDMCP es realitza utilitzant embolcalls TCP. És "
+"possible compilar el GDM sense la compatibilitat d'embolcalls TCP, de manera "
+"que aquesta funció potser no està disponible en alguns sistemes operatius."
+
+#: C/gdm.xml:803(para)
+msgid ""
+"You should use the daemon name <command>gdm</command> in the <filename>&lt;"
+"etc&gt;/hosts.allow</filename> and <filename>&lt;etc&gt;/hosts.deny</"
+"filename> files. For example to deny computers from <filename>.evil.domain</"
+"filename> from logging in, then add"
+msgstr ""
+"Hauríeu d'utilitzar el nom del dimoni <command>gdm</command> als fitxers "
+"<filename>&lt;etc&gt;/hosts.allow</filename> i <filename>&lt;etc&gt;/hosts."
+"deny</filename>. Per exemple, per denegar l'entrada d'ordinadors des de "
+"<filename>.evil.domain</filename> heu d'afegir"
+
+#: C/gdm.xml:810(screen)
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .evil.domain\n"
+msgstr ""
+"\n"
+"gdm: .evil.domain\n"
+
+#: C/gdm.xml:813(para)
+msgid ""
+"to <filename>&lt;etc&gt;/hosts.deny</filename>. You may also need to add"
+msgstr "a <filename>&lt;etc&gt;/hosts.deny</filename>. També heu d'afegir"
+
+#: C/gdm.xml:817(screen)
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .your.domain\n"
+msgstr ""
+"\n"
+"gdm: .your.domain\n"
+
+#: C/gdm.xml:820(para)
+msgid ""
+"to your <filename>&lt;etc&gt;/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 ""
+"al vostre <filename>&lt;etc&gt;/hosts.allow</filename> si normalment no "
+"permeteu tots els serveis des de tots el amfitrions. Per obtenir més detalls "
+"vegeu la pàgina del manual <ulink type=\"help\" url=\"man:hosts.allow"
+"\">hosts.allow(5)</ulink>."
+
+#: C/gdm.xml:829(title)
+msgid "Firewall Security"
+msgstr "Seguretat del tallafoc"
+
+#: C/gdm.xml:831(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 really needed. GDM guards "
+"against 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 do a "
+"denial of service attack via XDMCP than attacking a webserver."
+msgstr ""
+"Encara que el GDM intenta diferenciar intel·ligentment atacants potencials "
+"utilitzant l'avantatge de l'XDMCP, encara es recomana que bloquegeu el port "
+"de l'XDMCP (normalment el port UDP 177) del tallafoc a no ser que realment "
+"el necessiteu. El GDM es protegeix contra atacs de denegació de servei, però "
+"el protocol d'X encara és inherentment insegur i només s'hauria d'utilitzar "
+"en entorns controlats. A més cada connexió remota utilitza molts recursos, "
+"de manera que és molt més fàcil realitzar un atac de denegació de servei "
+"mitjançant l'XDMCP que atacar un servidor web."
+
+#: C/gdm.xml:842(para)
+msgid ""
+"It is also wise to block all of the Xserver ports. These are TCP ports 6000+ "
+"(one for each display number) on your firewall. Note that GDM will use "
+"display numbers 20 and higher for flexible on-demand servers."
+msgstr ""
+"També es recomana bloquejar al tallafoc tots els ports del servidor d'X "
+"(aquests són els ports TCP 6000 + el número de la pantalla). Tingueu en "
+"compte que el GDM utilitzarà els números de pantalla 20 i superiors per als "
+"servidors sota demanda flexibles."
+
+#: C/gdm.xml:849(para)
+msgid ""
+"X is not a very safe protocol when using it over the Internet, and XDMCP is "
+"even less safe."
+msgstr ""
+"L'X no és un protocol molt segur per utilitzar-se per Internet i l'XDMCP ho "
+"és encara menys."
+
+#: C/gdm.xml:856(title)
+msgid "PolicyKit"
+msgstr "PolicyKit"
+
+#. <para>
+#.         TODO - Should we say more?
+#. </para>
+#: C/gdm.xml:864(para)
+msgid ""
+"GDM may be configured to use PolicyKit to allow the system administrator to "
+"control whether the login screen should provide the shutdown and restart "
+"buttons on the greeter screen."
+msgstr ""
+"Es pot configurar el GDM perquè utilitzi el PolicyKit per permetre a "
+"l'administrador del sistema controlar quan la pantalla d'entrada hauria de "
+"proporcionar els botons d'apagar i de tornar a iniciar a la pantalla del "
+"rebedor."
+
+#: C/gdm.xml:870(para)
+msgid ""
+"These buttons are controlled by the <filename>org.freedesktop.consolekit."
+"system.stop-multiple-users</filename> and <filename>org.freedesktop."
+"consolekit.system.restart-multiple-users</filename> actions respectively. "
+"Policy for these actions can be set up using the polkit-gnome-authorization "
+"tool, or the polkit-auth command line program."
+msgstr ""
+"Les accions <filename>org.freedesktop.consolekit.system.stop-multiple-users</"
+"filename> i <filename>org.freedesktop.consolekit.system.restart-multiple-"
+"users</filename> controlen aquests botons respectivament. Es pot ajustar la "
+"política les accions amb l'eina polkit-gnome-authorization o el programa de "
+"línia d'ordres polkit-auth."
+
+#: C/gdm.xml:882(title)
+msgid "RBAC (Role Based Access Control)"
+msgstr "RBAC (control d'accés basat en el rol)"
+
+#: C/gdm.xml:884(para)
+msgid ""
+"GDM may be configured to use RBAC instead of PolicyKit. In this case the "
+"RBAC configuration is used to control whether the login screen should "
+"provide the shutdown and restart buttons on the greeter screen."
+msgstr ""
+"El GDM es pot configurar perquè utilitzi el RBAC en comptes del PolicyKit. "
+"En aquest cas, s'utilitza la configuració del RBAC per controlar quan la "
+"pantalla d'entrada hauria de proporcionar els botons d'apagar i de tornar a "
+"iniciar a la pantalla del rebedor."
+
+#: C/gdm.xml:890(para)
+msgid ""
+"For example, on Oracle Solaris, the \"solaris.system.shutdown\" "
+"authorization is used to control this. Simply modify the <filename>/etc/"
+"user_attr</filename> file so that the \"gdm\" user has this authorization."
+msgstr ""
+"Per exemple, a l'Oracle Solaris, s'utilitza l'autorització «solaris.system."
+"shutdown» per controlar-ho. Només cal que modifiqueu el fitxer <filename>/"
+"etc/user_attr</filename> de manera que l'usuari «gdm» tingui aquesta "
+"autorització."
+
+#: C/gdm.xml:903(title)
+msgid "Support for ConsoleKit"
+msgstr "Compatibilitat per a ConsoleKit"
+
+#. <para>
+#.     TODO - Should we update these docs?  Probably should mention any 
+#.            configuration that users may want to do for using it with GDM?
+#.            If so, perhaps this section should be moved to a subsection of
+#.            the "Configure" section?
+#. </para>
+#: C/gdm.xml:914(para)
+msgid ""
+"GDM includes support for publishing user login information with the user and "
+"login session accounting framework known as ConsoleKit. ConsoleKit is able "
+"to keep track of all the users currently logged in. In this respect, it can "
+"be used as a replacement for the utmp or utmpx files that are available on "
+"most Unix-like Operating Systems."
+msgstr ""
+"El GDM inclou compatibilitat per publicar la informació d'entrada de "
+"l'usuari amb l'entorn de treball de comptabilitat d'usuaris i de sessions "
+"d'entrada conegut com a ConsoleKit. El ConsoleKit és capaç de fer el "
+"seguiment de tots els usuaris que estan connectats actualment. En aquest "
+"aspecte, es pot utilitzar com un substitut dels fitxers utmp o utmpx que hi "
+"ha disponibles a la majoria de sistemes operatius tipus UNIX."
+
+#: C/gdm.xml:922(para)
+msgid ""
+"When GDM is about to create a new login process for a user it will call a "
+"privileged method of ConsoleKit in order to open a new session for this "
+"user. At this time GDM also provides ConsoleKit with information about this "
+"user session such as: the user ID, the X11 Display name that will be "
+"associated with the session, the host-name from which the session originates "
+"(useful in the case of an XDMCP session), whether or not this session is "
+"attached, etc. As the entity that initiates the user process, GDM is in a "
+"unique position to know about the user session and to be trusted to provide "
+"these bits of information. The use of this privileged method is restricted "
+"by the use of the D-Bus system message bus security policy."
+msgstr ""
+"Quan el GDM va a crear un procés d'entrada nou per a un usuari cridarà un "
+"mètode privilegiat del ConsoleKit per obrir una sessió nova per a aquest "
+"usuari. En aquest moment el GDM també proporciona al ConsoleKit la "
+"informació sobre aquesta sessió d'usuari com ara: l'identificador de "
+"l'usuari, el nom de la pantalla X11 que estarà associada amb la sessió, el "
+"nom de l'amfitrió que origina la sessió (útil en el cas d'una sessió XDMCP), "
+"si la sessió és local, etc. Com a entitat que inicia el procés d'usuari, el "
+"GDM és en una posició única per conèixer la sessió de l'usuari i per confiar-"
+"hi aquestes dades. La utilitat d'aquest mètode privilegiat està restringit a "
+"la utilització d'una política de seguretat del bus del sistema de missatges "
+"del D-Bus."
+
+#: C/gdm.xml:936(para)
+msgid ""
+"In case a user with an existing session has authenticated at GDM and "
+"requests to resume that existing session, GDM calls a privileged method of "
+"ConsoleKit to unlock that session. The exact details of what happens when "
+"the session receives this unlock signal are undefined and session-specific. "
+"However, most sessions will unlock a screensaver in response."
+msgstr ""
+"En el cas on un usuari amb una sessió existent s'hagi autenticat al GDM i "
+"sol·liciti de continuar la sessió existent, el GDM crida un mètode "
+"privilegiat del ConsoleKit per desblocar la sessió. Els detalls exactes de "
+"què succeeix quan la sessió rep aquesta senyal de desblocatge són indefinits "
+"i específics de la sessió. Tot i això, la majoria de sessions desblocaran un "
+"estalvi de pantalla com a resposta."
+
+#: C/gdm.xml:945(para)
+msgid ""
+"When the user chooses to log out, or if GDM or the session quit unexpectedly "
+"the user session will be unregistered from ConsoleKit."
+msgstr ""
+"Quan l'usuari vol sortir o si el GDM o la sessió surten de manera "
+"inesperada, es desregistrarà la sessió de l'usuari al ConsoleKit."
+
+#: C/gdm.xml:954(title)
+msgid "Configuration"
+msgstr "Configuració"
+
+#: C/gdm.xml:956(para)
+msgid ""
+"GDM has a number of configuration interfaces. These include scripting "
+"integration points, daemon configuration, greeter configuration, general "
+"session settings, integration with gnome-settings-daemon configuration, and "
+"session configuration. These types of integration are described in detail "
+"below."
+msgstr ""
+"El GDM té tot un seguit d'interfícies de configuració. Aquestes inclouen "
+"punts d'integració pels scripts, la configuració de dimonis, la configuració "
+"del rebedor, els paràmetres de sessió generals, la integració amb la "
+"configuració del gnome-settings-daemon i la configuració de la sessió. "
+"Aquests tipus d'integració estan descrits en detall a sota."
+
+#: C/gdm.xml:965(title)
+msgid "Scripting Integration Points"
+msgstr "Punts d'integració pels scripts"
+
+#: C/gdm.xml:967(para)
+msgid ""
+"The GDM script integration points can be found in the <filename>&lt;etc&gt;/"
+"gdm/</filename> directory:"
+msgstr ""
+"Els punts d'integració pels scripts del GDM es poden trobar al directori "
+"<filename>&lt;etc&gt;/gdm/</filename>:"
+
+#: C/gdm.xml:972(screen)
+#, no-wrap
+msgid ""
+"\n"
+"Xsession\n"
+"Init/\n"
+"PostLogin/\n"
+"PreSession/\n"
+"PostSession/\n"
+msgstr ""
+"\n"
+"Xsession\n"
+"Init/\n"
+"PostLogin/\n"
+"PreSession/\n"
+"PostSession/\n"
+
+#: C/gdm.xml:980(para)
+msgid ""
+"The <filename>Init</filename>, <filename>PostLogin</filename>, "
+"<filename>PreSession</filename>, and <filename>PostSession</filename> "
+"scripts all work as described below."
+msgstr ""
+"Els scripts <filename>Init</filename>, <filename>PostLogin</filename>, "
+"<filename>PreSession</filename> i <filename>PostSession</filename> funcionen "
+"tal com es descriu a sota."
+
+#: C/gdm.xml:986(para)
+msgid ""
+"For each type of script, the default one which will be executed is called "
+"\"Default\" and is stored in a directory associated with the script type. So "
+"the default <filename>Init</filename> script is <filename>&lt;etc&gt;/gdm/"
+"Init/Default</filename>. A per-display script can be provided, and if it "
+"exists it will be run instead of the default script. Such scripts are stored "
+"in the same directory as the default script and have the same name as the "
+"Xserver DISPLAY value for that display. For example, if the <filename>&lt;"
+"Init&gt;/:0</filename> script exists, it will be run for DISPLAY \":0\"."
+msgstr ""
+"Per a cada tipus d'script, el que s'executarà per defecte s'anomena «Default» "
+"i s'emmagatzema en un directori associat amb el tipus d'script. De manera "
+"que l'script per defecte de l'<filename>Init</filename> és troba a "
+"<filename>&lt;etc&gt;/gdm/Init/Default</filename>. Es pot proporcionar un "
+"script per pantalla, si existeix, s'executarà en lloc de l'script per "
+"defecte. Aquests es troben al mateix directori que l'script per defecte i "
+"tenen el mateix nom que el valor DISPLAY del servidor d'X per a aquesta "
+"pantalla. Per exemple, si existeix l'script <filename>&lt;Init&gt;/:0</"
+"filename>, aquest s'executarà si la pantalla és «:0»"
+
+#: C/gdm.xml:998(para)
+msgid ""
+"All of these scripts are run with root privilege and return 0 if run "
+"successfully, and a non-zero return code if there was any failure that "
+"should cause the login session to be aborted. Also note that GDM will block "
+"until the scripts finish, so if any of these scripts hang, this will cause "
+"the login process to also hang."
+msgstr ""
+"Tots aquests scripts s'executen amb privilegis d'usuari primari i retornen 0 "
+"si s'executen correctament i retornen un codi diferent de zero si hi ha "
+"alguna fallada que hauria de causar que s'interrompés la sessió d'entrada. "
+"Tingueu en compte que el GDM es blocarà fins que l'script finalitzi, de "
+"manera que si algun d'aquests scripts es penja, això provocarà que el procés "
+"d'entrada també es pengi."
+
+#: C/gdm.xml:1006(para)
+msgid ""
+"When the Xserver for the login GUI has been successfully started, but before "
+"the login GUI is actually displayed, GDM will run the <filename>Init</"
+"filename> script. This script is useful for starting programs that should be "
+"run while the login screen is showing, or for doing any special "
+"initialization if required."
+msgstr ""
+"Quan s'ha iniciat correctament el servidor X per a la interfície gràfica "
+"d'entrada, però abans que s'hagi mostrat aquesta, el GDM executarà l'script "
+"<filename>Init</filename>. Aquest script és útil per iniciar programes que "
+"s'haurien d'executar mentre es mostra la pantalla d'entrada o per realitzar "
+"qualsevol inicialització especial necessària."
+
+#: C/gdm.xml:1014(para)
+msgid ""
+"After the user has been successfully authenticated GDM will run the "
+"<filename>PostLogin</filename> script. This is done before any session setup "
+"has been done, including before the pam_open_session call. This script is "
+"useful for doing any session initialization that needs to happen before the "
+"session starts. For example, you might setup the user's $HOME directory if "
+"needed."
+msgstr ""
+"Després de que s'hagi autenticat correctament a l'usuari, el GDM executarà "
+"l'script <filename>PostLogin</filename>. Aquest s'executa abans de "
+"configurar qualsevol sessió, fins i tot abans de la crida a "
+"pam_open_session. Aquest script és útil per realitzar qualsevol "
+"inicialització que ha de succeir abans d'iniciar la sessió. Per exemple, "
+"podeu configurar el directori $HOME de l'usuari si és necessari."
+
+#: C/gdm.xml:1023(para)
+msgid ""
+"After the user session has been initialized, GDM will run the "
+"<filename>PreSession</filename> script. This script is useful for doing any "
+"session initialization that needs to happen after the session has been "
+"initialized. It can be used for session management or accounting, for "
+"example."
+msgstr ""
+"Després d'inicialitzar la sessió de l'usuari, el GDM executarà l'script "
+"<filename>PreSession</filename>. Aquest script és útil per realitzar "
+"qualsevol inicialització que necessiti fer-se després d'inicialitzar la "
+"sessió. Per exemple, es pot utilitzar per la gestió de sessions o de comptes."
+
+#: C/gdm.xml:1031(para)
+msgid ""
+"When a user terminates their session, GDM will run the "
+"<filename>PostSession</filename> script. Note that the Xserver will have "
+"been stopped by the time this script is run, so it should not be accessed."
+msgstr ""
+"Quan un usuari finalitza la seva sessió, el GDM executarà l'script "
+"<filename>PostSession</filename>. Tingueu en compte que el servidor X "
+"s'aturarà al moment en què s'executi aquest script, de manera que no s'hi "
+"hauria d'accedir."
+
+#: C/gdm.xml:1038(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 ""
+"Tingueu en compte que l'script <filename>PostSession</filename> s'executarà "
+"encara que la pantalla no respongui degut a algun error d'E/S o semblant. De "
+"manera que no hi ha cap garantia que les aplicacions d'X funcionaran durant "
+"l'execució de l'script."
+
+#: C/gdm.xml:1045(para)
+msgid ""
+"All of the above scripts will set the <filename>$RUNNING_UNDER_GDM</"
+"filename> environment variable to <filename>yes</filename>. If the scripts "
+"are also shared with other display managers, this allows you to identify "
+"when GDM is calling these scripts, so you can run specific code when GDM is "
+"used."
+msgstr ""
+"Tots els scripts anteriors establiran la variable de l'entorn <filename>"
+"$RUNNING_UNDER_GDM</filename> a <filename>yes</filename>. Si els scripts "
+"també són compartits amb altres gestors de pantalla, us permetrà identificar "
+"quan s'està executant aquests scripts des del GDM, de manera que podeu "
+"executar codi específic quan s'està utilitzant el GDM."
+
+#: C/gdm.xml:1055(title)
+msgid "Autostart Configuration"
+msgstr "Configuració d'arrencada automàtica"
+
+#: C/gdm.xml:1057(para)
+msgid ""
+"The <filename>&lt;share&gt;/gdm/autostart/LoginWindow</filename> directory "
+"contains files in the format specified by the \"FreeDesktop.org Desktop "
+"Application Autostart Specification\". Standard features in the "
+"specification may be used to specify programs that should auto-restart or "
+"only be launched if a GConf configuration value is set, etc."
+msgstr ""
+
+#: C/gdm.xml:1066(para)
+msgid ""
+"Any <filename>.desktop</filename> files in this directory will cause the "
+"associated program to automatically start with the login GUI greeter. By "
+"default, GDM is shipped with files which will autostart the gdm-simple-"
+"greeter login GUI greeter itself, the gnome-power-manager application, the "
+"gnome-settings-daemon, and the metacity window manager. These programs are "
+"needed for the greeter program to work. In addition, desktop files are "
+"provided for starting various AT programs if the configuration values "
+"specified in the Accessibility Configuration section below are set."
+msgstr ""
+
+#: C/gdm.xml:1080(title)
+msgid "Xsession Script"
+msgstr "Script Xsession"
+
+#: C/gdm.xml:1082(para)
+msgid ""
+"There is also an <filename>Xsession</filename> script located at "
+"<filename>&lt;etc&gt;/gdm/Xsession</filename> which is called between the "
+"<filename>PreSession</filename> and the <filename>PostSession</filename> "
+"scripts. This script does not support per-display like the other scripts. "
+"This script is used for actually starting the user session. This script is "
+"run as the user, and it will run whatever session was specified by the "
+"Desktop session file the user selected to start."
+msgstr ""
+"També hi ha un script <filename>Xsession</filename> ubicat a <filename>&lt;"
+"etc&gt;/gdm/Xsession</filename> que es crida entre els scripts "
+"<filename>PreSession</filename> i <filename>PostSession</filename>. Aquest "
+"script no admet configuració per pantalla com els altres scripts. Aquest "
+"script s'utilitza per iniciar la sessió d'usuari. Aquest script s'executa "
+"com usuari i s'executarà sigui quina sigui la sessió especificada al fitxer "
+"de sessió de l'escriptori que l'usuari ha seleccionar per iniciar."
+
+#: C/gdm.xml:1095(title)
+msgid "Daemon Configuration"
+msgstr "Configuració del dimoni"
+
+#: C/gdm.xml:1097(para)
+msgid ""
+"The GDM daemon is configured using the <filename>&lt;etc&gt;/gdm/custom."
+"conf</filename> file. Default values are stored in GConf in the "
+"<filename>gdm.schemas</filename> file. It is recommended that end-users "
+"modify the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file because the "
+"schemas file may be overwritten when the user updates their system to have a "
+"newer version of GDM."
+msgstr ""
+"El dimoni del GDM es configura utilitzant el fitxer <filename>&lt;etc&gt;/"
+"gdm/custom.conf</filename>. Els valors predeterminats s'emmagatzemen al "
+"GConf en el fitxer <filename>gdm.schemas</filename>. Es recomana que els "
+"usuaris finals modifiquin el fitxer <filename>&lt;etc&gt;/gdm/custom.conf</"
+"filename> perquè es pot sobreescriure el fitxer d'esquemes quan l'usuari "
+"actualitzi el sistema amb una versió nova del GDM."
+
+#: C/gdm.xml:1107(para)
+msgid ""
+"Note that older versions of GDM supported additional configuration options "
+"which are no longer supported in the latest versions of GDM."
+msgstr ""
+"Tingueu en compte que les versions anteriors del GDM admetien opcions de "
+"configuració addicionals que ja no són compatibles amb les últimes versions "
+"del GDM."
+
+#: C/gdm.xml:1112(para)
+msgid ""
+"The <filename>&lt;etc&gt;/gdm/custom.conf</filename> file is in the "
+"<filename>keyfile</filename> format. Keywords in brackets define group "
+"sections, strings before an equal sign (=) are keys and the data after equal "
+"sign represents their value. Empty lines or lines starting with the hash "
+"mark (#) are ignored."
+msgstr ""
+"El fitxer <filename>&lt;etc&gt;/gdm/custom.conf</filename> està en el format "
+"<filename>keyfile</filename>. Les paraules clau entre claudàtors defineixen "
+"les seccions de grup, les cadenes abans del signe igual (=) són claus i les "
+"dades després del signe igual representen el seu valor. S'ignoren les línies "
+"buides o que comencen amb la marca de coixinet (#)."
+
+#: C/gdm.xml:1120(para)
+msgid ""
+"The file <filename>&lt;etc&gt;/gdm/custom.conf</filename> supports the "
+"\"[daemon]\", \"[security]\", and \"[xdmcp]\" group sections. Within each "
+"group, there are particular key/value pairs that can be specified to modify "
+"how GDM behaves. For example, to enable timed login and specify the timed "
+"login user to be a user named \"you\", you would modify the file so it "
+"contains the following lines:"
+msgstr ""
+"El fitxer <filename>&lt;etc&gt;/gdm/custom.conf</filename> admet les "
+"seccions de grup «[daemon]», «[security]» i «[xdmcp]». Existeixen parelles de "
+"clau/valor particulars amb cada grup que es poden especificar per modificar "
+"com es comporta el GDM. Per exemple, per habilitar l'entrada temporitzada i "
+"especificar que l'usuari d'entrada temporitzada sigui «usuari», hauríeu de "
+"modificar el fitxer de manera que contingués les línies següents:"
+
+#: C/gdm.xml:1130(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[daemon]\n"
+"TimedLoginEnable=true\n"
+"TimedLogin=you\n"
+msgstr ""
+"\n"
+"[daemon]\n"
+"TimedLoginEnable=true\n"
+"TimedLogin=usuari\n"
+
+#: C/gdm.xml:1136(para)
+msgid "A full list of supported configuration keys follow:"
+msgstr ""
+"A continuació hi ha una llista complerta de claus de configuració admeses:"
+
+#: C/gdm.xml:1141(title)
+msgid "[chooser]"
+msgstr ""
+
+#: C/gdm.xml:1145(term)
+msgid "Multicast"
+msgstr "Multicast"
+
+#: C/gdm.xml:1147(synopsis)
+#, no-wrap
+msgid "Multicast=false"
+msgstr "Multicast=false"
+
+#: C/gdm.xml:1148(para)
+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."
+msgstr ""
+
+#: C/gdm.xml:1157(term)
+msgid "MulticastAddr"
+msgstr "MulticastAddr"
+
+#: C/gdm.xml:1159(synopsis)
+#, no-wrap
+msgid "MulticastAddr=ff02::1"
+msgstr "MulticastAddr=ff02::1"
+
+#: C/gdm.xml:1160(para)
+msgid "This is the Link-local multicast address."
+msgstr ""
+
+#: C/gdm.xml:1169(title)
+msgid "[daemon]"
+msgstr "[daemon]"
+
+#: C/gdm.xml:1172(term)
+msgid "TimedLoginEnable"
+msgstr "TimedLoginEnable"
+
+#: C/gdm.xml:1174(synopsis)
+#, no-wrap
+msgid "TimedLoginEnable=false"
+msgstr "TimedLoginEnable=false"
+
+#: C/gdm.xml:1175(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. Refer to the \"Security-&gt;PAM\" section of the manual for "
+"more information, or for help if this feature does not seem to work."
+msgstr ""
+"Si l'usuari especificat a <filename>TimedLogin</filename> hauria d'entrar "
+"després d'un nombre de segons (especificats a <filename>TimedLoginDelay</"
+"filename>) d'inactivitat a la pantalla d'entrada. Això és útil per a "
+"terminals d'accés públic o fins i tot per ús domèstic. Si l'usuari utilitza "
+"el teclat o els menús de navegació, es reiniciarà el temps d'espera a "
+"<filename>TimedLoginDelay</filename> o 30 segons, el que sigui més alt. Si "
+"l'usuari no introdueix cap nom d'usuari si no que prem la tecla de retorn "
+"mentre el programa d'entrada sol·licita el nom d'usuari, el GDM assumirà que "
+"l'usuari vol entrar immediatament com a l'usuari definit a "
+"<filename>TimedLogin</filename>. Tingueu en compte que no se sol·licitarà "
+"cap contrasenya per aquest usuari de manera que hauríeu d'anar amb compte, "
+"tot i que si utilitzeu el PAM es podria configurar perquè sigui necessari "
+"introduir la contrasenya abans de permetre l'entrada. Per obtenir més "
+"informació consulteu la secció «Seguretat-&gt;PAM» del manual o per obtenir "
+"ajuda si aquesta funció no sembla funcionar."
+
+#: C/gdm.xml:1197(term)
+msgid "TimedLogin"
+msgstr "TimedLogin"
+
+#: C/gdm.xml:1199(synopsis)
+#, no-wrap
+msgid "TimedLogin="
+msgstr "TimedLogin="
+
+#: C/gdm.xml:1200(para)
+msgid ""
+"This is the user that should be logged in after a specified number of "
+"seconds of inactivity."
+msgstr ""
+"Aquest és l'usuari que hauria d'entrar després d'un nombre de segons "
+"d'inactivitat especificat."
+
+#: C/gdm.xml:1204(para) C/gdm.xml:1248(para)
+msgid ""
+"If the value ends with a vertical bar | (the pipe symbol), then GDM will "
+"execute the program specified and use whatever value is returned on standard "
+"out from the program as the user. The program is run with the DISPLAY "
+"environment variable set so that it is possible to specify the user in a per-"
+"display fashion. For example if the value is \"/usr/bin/getloginuser|\", "
+"then the program \"/usr/bin/getloginuser\" will be run to get the user value."
+msgstr ""
+
+#: C/gdm.xml:1218(term)
+msgid "TimedLoginDelay"
+msgstr "TimedLoginDelay"
+
+#: C/gdm.xml:1220(synopsis)
+#, no-wrap
+msgid "TimedLoginDelay=30"
+msgstr "TimedLoginDelay=30"
+
+#: C/gdm.xml:1221(para)
+msgid ""
+"Delay in seconds before the <filename>TimedLogin</filename> user will be "
+"logged in."
+msgstr ""
+"Retard en segons abans que l'usuari <filename>TimedLogin</filename> entri."
+
+#: C/gdm.xml:1229(term)
+msgid "AutomaticLoginEnable"
+msgstr "AutomaticLoginEnable"
+
+#: C/gdm.xml:1231(synopsis)
+#, no-wrap
+msgid "AutomaticLoginEnable=false"
+msgstr "AutomaticLoginEnable=false"
+
+#: C/gdm.xml:1232(para)
+msgid ""
+"If true, the user given in <filename>AutomaticLogin</filename> should be "
+"logged in immediately. This feature is like timed login with a delay of 0 "
+"seconds."
+msgstr ""
+"Si és cert, l'usuari especificat a <filename>AutomaticLogin</filename> "
+"hauria d'entrar immediatament. Aquesta funció és semblant a l'entrada "
+"temporitzada amb un retard de 0 segons."
+
+#: C/gdm.xml:1241(term)
+msgid "AutomaticLogin"
+msgstr "AutomaticLogin"
+
+#: C/gdm.xml:1243(synopsis)
+#, no-wrap
+msgid "AutomaticLogin="
+msgstr "AutomaticLogin="
+
+#: C/gdm.xml:1244(para)
+msgid ""
+"This is the user that should be logged in immediately if "
+"<filename>AutomaticLoginEnable</filename> is true."
+msgstr ""
+"Aquest és l'usuari que hauria d'entrar immediatament si "
+"<filename>AutomaticLoginEnable</filename> és cert."
+
+#: C/gdm.xml:1262(term)
+msgid "User"
+msgstr "User"
+
+#: C/gdm.xml:1264(synopsis)
+#, no-wrap
+msgid "User=gdm"
+msgstr "User=gdm"
+
+#: C/gdm.xml:1265(para)
+msgid ""
+"The username under which the greeter and other GUI programs are run. Refer "
+"to the <filename>Group</filename> configuration key and to the \"Security-"
+"&gt;GDM User And Group\" section of this document for more information."
+msgstr ""
+"El nom d'usuari sota el qual el rebedor i altres programes d'interfície "
+"gràfica d'usuari s'executen. Per obtenir més informació consulteu la clau de "
+"configuració <filename>Group</filename> i la secció «Seguretat-&gt;Usuari i "
+"grup del GDM» d'aquest document."
+
+#: C/gdm.xml:1275(term)
+msgid "Group"
+msgstr "Group"
+
+#: C/gdm.xml:1277(synopsis)
+#, no-wrap
+msgid "Group=gdm"
+msgstr "Group=gdm"
+
+#: C/gdm.xml:1278(para)
+msgid ""
+"The group name under which the greeter and other GUI programs are run. Refer "
+"to the <filename>User</filename> configuration key and to the \"Security-&gt;"
+"GDM User And Group\" section of this document for more information."
+msgstr ""
+"El nom de grup sota el qual el rebedor i altres programes d'interfície "
+"gràfica d'usuari s'executen. Per obtenir més informació consulteu la clau de "
+"configuració <filename>User</filename> i la secció «Seguretat-&gt;Usuari i "
+"grup del GDM» d'aquest document."
+
+#: C/gdm.xml:1290(title)
+msgid "Debug Options"
+msgstr "Opcions de depuració"
+
+#: C/gdm.xml:1293(title)
+msgid "[debug]"
+msgstr "[debug]"
+
+#: C/gdm.xml:1296(term) C/gdm.xml:1427(term)
+msgid "Enable"
+msgstr "Enable"
+
+#: C/gdm.xml:1298(synopsis) C/gdm.xml:1429(synopsis)
+#, no-wrap
+msgid "Enable=false"
+msgstr "Enable=false"
+
+#: C/gdm.xml:1299(para)
+#, fuzzy
+#| msgid ""
+#| "Print debug output to the syslog. This is typically <filename>&lt;var&gt;/"
+#| "log/messages</filename> or <filename>&lt;var&gt;/adm/messages</filename> "
+#| "depending on your Operating System."
+msgid ""
+"To enable debugging, set the debug/Enable key to \"true\" in the "
+"<filename>&lt;etc&gt;/gdm/custom.conf</filename> file and restart GDM. Then "
+"debug output will be sent to the system log file (<filename>&lt;var&gt;/log/"
+"messages</filename> or <filename>&lt;var&gt;/adm/messages</filename> "
+"depending on your Operating System)."
+msgstr ""
+"Imprimeix la sortida de depuració al registre del sistema. Aquest normalment "
+"és <filename>&lt;var&gt;/log/messages</filename> o <filename>&lt;var&gt;/adm/"
+"messages</filename> depenent del vostre sistema operatiu."
+
+#: C/gdm.xml:1314(title)
+msgid "Greeter Options"
+msgstr "Opcions del rebedor"
+
+#: C/gdm.xml:1317(title)
+msgid "[greeter]"
+msgstr "[greeter]"
+
+#: C/gdm.xml:1320(term)
+msgid "IncludeAll"
+msgstr "IncludeAll"
+
+#: C/gdm.xml:1322(synopsis)
+#, no-wrap
+msgid "IncludeAll=true"
+msgstr "IncludeAll=true"
+
+#: C/gdm.xml:1323(para)
+msgid ""
+"If true, then the face browser will show all users on the local machine. If "
+"false, the face browser will only show users who have recently logged in."
+msgstr ""
+
+#: C/gdm.xml:1329(para)
+msgid ""
+"When this key is true, GDM will call fgetpwent() to get a list of local "
+"users on the system. Any users with a user id less than 500 (or 100 if "
+"running on Oracle Solaris) are filtered out. The Face Browser also will "
+"display any users that have previously logged in on the system (for example "
+"NIS/LDAP users). It gets this list via calling the <command>ck-history</"
+"command> ConsoleKit interface. It will also filter out any users which do "
+"not have a valid shell (valid shells are any shell that getusershell() "
+"returns - /sbin/nologin or /bin/false are considered invalid shells even if "
+"getusershell() returns them)."
+msgstr ""
+
+#: C/gdm.xml:1343(para)
+msgid ""
+"If false, then GDM more simply only displays users that have previously "
+"logged in on the system (local or NIS/LDAP users) by calling the <command>ck-"
+"history</command> ConsoleKit interface."
+msgstr ""
+
+#: C/gdm.xml:1352(term)
+msgid "Include"
+msgstr "Include"
+
+#: C/gdm.xml:1354(synopsis)
+#, no-wrap
+msgid "Include="
+msgstr "Include="
+
+#: C/gdm.xml:1355(para)
+msgid ""
+"Set to a list of users to always include in the Face Browser. This value is "
+"set to a list of users separated by commas. By default, the value is empty."
+msgstr ""
+
+#: C/gdm.xml:1364(term)
+msgid "Exclude"
+msgstr "Exclude"
+
+#: C/gdm.xml:1366(synopsis)
+#, no-wrap
+msgid "Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap"
+msgstr "Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap"
+
+#: C/gdm.xml:1367(para)
+msgid ""
+"Set to a list of users to always exclude in the Face Browser. This value is "
+"set to a list of users separated by commas. Note that the setting in the "
+"<filename>custom.conf</filename> overrides the default value, so if you wish "
+"to add additional users to the list, then you need to set the value to the "
+"default value with additional users appended to the list."
+msgstr ""
+
+#: C/gdm.xml:1381(title)
+msgid "Security Options"
+msgstr "Opcions de seguretat"
+
+#: C/gdm.xml:1384(title)
+msgid "[security]"
+msgstr "[security]"
+
+#: C/gdm.xml:1387(term)
+msgid "DisallowTCP"
+msgstr "DisallowTCP"
+
+#: C/gdm.xml:1389(synopsis)
+#, no-wrap
+msgid "DisallowTCP=true"
+msgstr "DisallowTCP=true"
+
+#: C/gdm.xml:1390(para)
+msgid ""
+"If true, then always append <filename>-nolisten tcp</filename> to the "
+"command line when starting attached Xservers, thus disallowing TCP "
+"connection. This is a more secure configuration if you are not using remote "
+"connections."
+msgstr ""
+"Si és cert, sempre s'afegirà <filename>-nolisten tcp</filename> a la línia "
+"d'ordres quan s'iniciïn servidors d'X locals, d'aquesta manera no es "
+"permetran connexions TCP. Aquesta configuració és més segura si no utilitzeu "
+"connexions remotes."
+
+#: C/gdm.xml:1402(title)
+msgid "XDCMP Support"
+msgstr "Compatibilitat XDCMP"
+
+#: C/gdm.xml:1405(title)
+msgid "[xdmcp]"
+msgstr "[xdmcp]"
+
+#: C/gdm.xml:1408(term)
+msgid "DisplaysPerHost"
+msgstr "DisplaysPerHost"
+
+#: C/gdm.xml:1410(synopsis)
+#, no-wrap
+msgid "DisplaysPerHost=1"
+msgstr "DisplaysPerHost=1"
+
+#: C/gdm.xml:1411(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 this "
+"value."
+msgstr ""
+"Per evitar que els atacants omplin la cua de pendents, el GDM només permetrà "
+"una connexió per a cada ordinador remot. Si voleu proporcionar serveis de "
+"pantalla a ordinadors amb més d'una pantalla, hauríeu d'incrementar aquest "
+"valor."
+
+#: C/gdm.xml:1418(para)
+msgid ""
+"Note that the number of attached DISPLAYS allowed is not limited. Only "
+"remote connections via XDMCP are limited by this configuration option."
+msgstr ""
+"Tingueu en compte que el nombre de pantalles locals permeses no està "
+"limitat. Només les connexions remotes mitjançant l'XDMCP estan limitades per "
+"aquesta opció de configuració."
+
+#: C/gdm.xml:1430(para)
+msgid ""
+"Setting this to true enables XDMCP support allowing remote displays/X "
+"terminals to be managed by GDM."
+msgstr ""
+"En establir-ho a cert s'habilita la compatibilitat XDMCP, permetent que el "
+"GDM pugui gestionar les pantalles remotes o els terminals d'X."
+
+#: C/gdm.xml:1435(para)
+msgid ""
+"<filename>gdm</filename> listens for requests on UDP port 177. See the Port "
+"option for more information."
+msgstr ""
+"El <filename>gdm</filename> escolta les sol·licituds al port UDP 177. Per "
+"obtenir més informació vegeu la opció Port."
+
+#: C/gdm.xml:1440(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 ""
+"Si el GDM es compila per permetre-ho, es pot controlar l'accés des de "
+"pantalles remotes utilitzant la biblioteca de l'embolcall TCP. El nom de "
+"servei és <filename>gdm</filename>"
+
+#: C/gdm.xml:1446(para)
+msgid ""
+"You should add <screen>\n"
+"gdm:.my.domain\n"
+"</screen> to your <filename>&lt;etc&gt;/hosts.allow</filename>, depending on "
+"your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:"
+"hosts.allow\">hosts.allow</ulink> man page for details."
+msgstr ""
+"Hauríeu d'afegir <screen>\n"
+"gdm:.my.domain\n"
+"</screen> al <filename>&lt;etc&gt;/hosts.allow</filename>, depenent de la "
+"configuració de l'embolcall TCP. Per obtenir més detalls vegeu la pàgina del "
+"manual <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow</ulink>."
+
+#: C/gdm.xml:1457(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 ""
+"Tingueu en compte que l'XDMCP no és un protocol precisament segur i que és "
+"una bona idea bloquejar el port UDP 177 al tallafocs a no ser que realment "
+"el necessiteu."
+
+#: C/gdm.xml:1466(term)
+msgid "HonorIndirect"
+msgstr "HonorIndirect"
+
+#: C/gdm.xml:1468(synopsis)
+#, no-wrap
+msgid "HonorIndirect=true"
+msgstr "HonorIndirect=true"
+
+#: C/gdm.xml:1469(para)
+msgid ""
+"Enables XDMCP INDIRECT choosing (i.e. remote execution of "
+"<filename>gdmchooser</filename>) for X-terminals which do not supply their "
+"own display browser."
+msgstr ""
+"Habilita la selecció XDMCP INDIRECT (és a dir, l'execució remota del "
+"<filename>gdmchooser</filename>) per als terminals d'X que no subministren "
+"el seu explorador de pantalla propi."
+
+#: C/gdm.xml:1478(term)
+msgid "MaxPending"
+msgstr "MaxPending"
+
+#: C/gdm.xml:1480(synopsis)
+#, no-wrap
+msgid "MaxPending=4"
+msgstr "MaxPending=4"
+
+#: C/gdm.xml:1481(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 ""
+"Per evitar els atacs de denegació de servei, el GDM té una cua de connexions "
+"pendents de mida fixa. Només el nombre de les pantalles MaxPending poden "
+"iniciar a la vegada."
+
+#: C/gdm.xml:1487(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 ""
+"Tingueu en compte que aquest paràmetre no limita el número de pantalles "
+"remotes que es poden gestionar. Només limita el número de pantalles que "
+"inicien una connexió simultàniament."
+
+#: C/gdm.xml:1496(term)
+msgid "MaxSessions"
+msgstr "MaxSessions"
+
+#: C/gdm.xml:1498(synopsis)
+#, no-wrap
+msgid "MaxSessions=16"
+msgstr "MaxSessions=16"
+
+#: C/gdm.xml:1499(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 ""
+"Determina el número màxim de connexions de pantalles remotes que es poden "
+"gestionar simultàniament. És a dir, el número total de pantalles remotes que "
+"pot utilitzar el vostre amfitrió."
+
+#: C/gdm.xml:1508(term)
+msgid "MaxWait"
+msgstr "MaxWait"
+
+#: C/gdm.xml:1510(synopsis)
+#, no-wrap
+msgid "MaxWait=30"
+msgstr "MaxWait=30"
+
+#: C/gdm.xml:1511(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 ""
+"Quan el GDM està preparat per gestionar una pantalla se li envia un paquet "
+"ACCEPT que conté una identificador de sessió únic que s'utilitzarà en "
+"futures connexions XDMCP."
+
+#: C/gdm.xml:1517(para)
+msgid ""
+"GDM will then place the session id in the pending queue waiting for the "
+"display to respond with a MANAGE request."
+msgstr ""
+"Llavors el GDM ubicarà l'identificador de sessió a la cua de pendents "
+"esperant a que la pantalla respongui amb una sol·licitud MANAGE."
+
+#: C/gdm.xml:1522(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 ""
+"Si no es rep una resposta abans de MaxWait segons, el GDM declararà la "
+"pantalla com a morta i la suprimirà de la cua de pendents, alliberant la "
+"ranura per a altres pantalles."
+
+#: C/gdm.xml:1531(term)
+msgid "MaxWaitIndirect"
+msgstr "MaxWaitIndirect"
+
+#: C/gdm.xml:1533(synopsis)
+#, no-wrap
+msgid "MaxWaitIndirect=30"
+msgstr "MaxWaitIndirect=30"
+
+#: C/gdm.xml:1534(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 ""
+"El paràmetre MaxWaitIndirect determina el número màxim de segons entre el "
+"temps on un usuari tria un amfitrió i la sol·licitud indirecta que l'ha de "
+"seguir on l'usuari està connectat a l'amfitrió. Quan s'excedeix el temps "
+"d'espera, s'oblida la informació sobre l'amfitrió triat i s'allibera la "
+"ranura indirecte per a altres pantalles. Es pot oblidar la informació abans "
+"si hi ha més amfitrions intentant enviar sol·licituds indirectes que "
+"<filename>MaxPendingIndirect</filename>."
+
+#: C/gdm.xml:1548(term)
+msgid "PingIntervalSeconds"
+msgstr "PingIntervalSeconds"
+
+#: C/gdm.xml:1550(synopsis)
+#, no-wrap
+msgid "PingIntervalSeconds=60"
+msgstr "PingIntervalSeconds=60"
+
+#: C/gdm.xml:1551(para)
+msgid ""
+"If the Xserver does not respond in the specified number of seconds, then the "
+"connection is stopped and the session ended. When this happens the slave "
+"daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied "
+"this setting by 2, so it may be necessary to increase the timeout if "
+"upgrading from GDM 2.20 and earlier to a newer version."
+msgstr ""
+
+#: C/gdm.xml:1560(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 than 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 ""
+"Tingueu en compte que el GDM en el passat utilitzava la clau de configuració "
+"<filename>PingInterval</filename> que estava en minuts. Per a la majoria de "
+"propòsits voldreu que aquest paràmetre sigui inferior d'un minut ja que en "
+"la majoria de casos on l'XDMCP s'hauria d'utilitzar (com terminals de "
+"laboratori), un retard de 15 o més segons significaria realment que el "
+"terminal s'ha apagat o s'ha tornat a iniciar i voldríeu finalitzar la sessió."
+
+#: C/gdm.xml:1573(term)
+msgid "Port"
+msgstr "Port"
+
+#: C/gdm.xml:1575(synopsis)
+#, no-wrap
+msgid "Port=177"
+msgstr "Port=177"
+
+#: C/gdm.xml:1576(para)
+msgid ""
+"The UDP port number <filename>gdm</filename> should listen to for XDMCP "
+"requests. Do not change this unless you know what you are doing."
+msgstr ""
+"El número de port UDP en el qual el <filename>gdm</filename> hauria "
+"d'escoltar les sol·licituds XDMCP. No ho canvieu si no sabeu les "
+"conseqüències que en poden derivar."
+
+#: C/gdm.xml:1585(term)
+msgid "Willing"
+msgstr "Willing"
+
+#: C/gdm.xml:1587(synopsis)
+#, no-wrap
+msgid "Willing=&lt;etc&gt;/gdm/Xwilling"
+msgstr "Willing=&lt;etc&gt;/gdm/Xwilling"
+
+#: C/gdm.xml:1588(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 does not 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 ""
+"Quan l'ordinador retorna un paquet WILLING després d'un QUERY aquest envia "
+"una cadena que proporciona l'estat actual del servidor. El missatge per "
+"defecte es l'identificador del sistema, però és pot crear un script que "
+"mostri un missatge personalitzat. Si no existeix l'script o la clau està "
+"buida, s'enviarà el missatge per defecte. Si aquest script acaba bé i "
+"produeix alguna sortida, s'enviarà la primera línia de la seva sortida (i "
+"només la primera línia). S'executa com a molt cada 3 segons per evitar una "
+"possible denegació de servei per inundació de l'ordinador amb paquets QUERY."
+
+#: C/gdm.xml:1607(title)
+msgid "Simple Greeter Configuration"
+msgstr "Configuració del rebedor senzill"
+
+#: C/gdm.xml:1609(para)
+msgid ""
+"The GDM default greeter is called the simple Greeter and is configured via "
+"GConf. Default values are stored in GConf in the <filename>gdm-simple-"
+"greeter.schemas</filename> file. These defaults can be overridden if the "
+"\"gdm\" user has a writable $HOME directory to store GConf settings. These "
+"values can be edited using the <command>gconftool-2</command> or "
+"<command>gconf-editor</command> programs. The following configuration "
+"options are supported:"
+msgstr ""
+"El rebedor per defecte del GDM s'anomena rebedor senzill i es configura "
+"mitjançant el GConf. Els valors per defecte s'emmagatzemen al fitxer "
+"<filename>gdm-simple-greeter.schemas</filename> del GConf. Aquests valors "
+"per defecte es poden sobreescriure si l'usuari «gdm» té un directori $HOME "
+"amb permisos d'escriptura per emmagatzemar els paràmetres del GConf. Aquests "
+"valors es poden editar utilitzant els programes <command>gconftool-2</"
+"command> o <command>gconf-editor</command>. S'admeten les opcions de "
+"configuració següents:"
+
+#: C/gdm.xml:1620(title)
+msgid "Greeter Configuration Keys"
+msgstr "Claus de configuració del rebedor"
+
+#: C/gdm.xml:1623(term)
+msgid "/apps/gdm/simple-greeter/banner_message_enable"
+msgstr "/apps/gdm/simple-greeter/banner_message_enable"
+
+#: C/gdm.xml:1625(synopsis) C/gdm.xml:1646(synopsis) C/gdm.xml:1657(synopsis)
+#: C/gdm.xml:1722(synopsis) C/gdm.xml:1787(synopsis) C/gdm.xml:1798(synopsis)
+#: C/gdm.xml:1809(synopsis) C/gdm.xml:1820(synopsis)
+#, no-wrap
+msgid "false (boolean)"
+msgstr "false (booleà)"
+
+#: C/gdm.xml:1626(para)
+msgid "Controls whether the banner message text is displayed."
+msgstr "Controla si es mostra el missatge de text del bàner."
+
+#: C/gdm.xml:1633(term)
+msgid "/apps/gdm/simple-greeter/banner_message_text"
+msgstr "/apps/gdm/simple-greeter/banner_message_text"
+
+#: C/gdm.xml:1635(synopsis)
+#, no-wrap
+msgid "NULL (string)"
+msgstr "NULL (cadena)"
+
+#: C/gdm.xml:1636(para)
+msgid "Specifies the text banner message to show on the greeter window."
+msgstr ""
+"Especifica el missatge de text del bàner que es mostra a la finestra del "
+"rebedor."
+
+#: C/gdm.xml:1644(term)
+msgid "/apps/gdm/simple-greeter/disable_restart_buttons"
+msgstr "/apps/gdm/simple-greeter/disable_restart_buttons"
+
+#: C/gdm.xml:1647(para)
+msgid "Controls whether to show the restart buttons in the login window."
+msgstr ""
+"Controla si s'han de mostrar els botons de reiniciar a la finestra d'entrada."
+
+#: C/gdm.xml:1655(term)
+msgid "/apps/gdm/simple-greeter/disable_user_list"
+msgstr "/apps/gdm/simple-greeter/disable_user_list"
+
+#: C/gdm.xml:1658(para)
+msgid ""
+"If true, then the face browser with known users is not shown in the login "
+"window."
+msgstr ""
+
+#: C/gdm.xml:1666(term)
+msgid "/apps/gdm/simple-greeter/logo_icon_name"
+msgstr "/apps/gdm/simple-greeter/logo_icon_name"
+
+#: C/gdm.xml:1668(synopsis)
+#, no-wrap
+msgid "computer (string)"
+msgstr "ordinador (cadena)"
+
+#: C/gdm.xml:1669(para)
+msgid "Set to the themed icon name to use for the greeter logo."
+msgstr ""
+"Estableix el nom del tema d'icones que s'utilitza per al logotip del rebedor."
+
+#: C/gdm.xml:1676(term)
+msgid "/apps/gdm/simple-greeter/recent-languages"
+msgstr "/apps/gdm/simple-greeter/recent-languages"
+
+#: C/gdm.xml:1678(synopsis) C/gdm.xml:1700(synopsis)
+#, no-wrap
+msgid "[] (string list)"
+msgstr "[] (llista de cadenes)"
+
+#: C/gdm.xml:1679(para)
+msgid ""
+"Set to a list of languages to be shown by default in the login window. "
+"Default value is \"[]\". With the default setting only the system default "
+"language is shown and the option \"Other...\" which pops-up a dialog box "
+"showing a full list of available languages which the user can select."
+msgstr ""
+
+#: C/gdm.xml:1687(para)
+msgid ""
+"Users are not intended to change this setting by hand. Instead GDM keeps "
+"track of any languages selected in this configuration key, and will show "
+"them in the language combo box along with the \"Other...\" choice. This way, "
+"commonly selected languages are easier to select."
+msgstr ""
+
+#: C/gdm.xml:1698(term)
+msgid "/apps/gdm/simple-greeter/recent-layouts"
+msgstr "/apps/gdm/simple-greeter/recent-layouts"
+
+#: C/gdm.xml:1701(para)
+msgid ""
+"Set to a list of keyboard layouts to be shown by default in the login panel. "
+"Default value is \"[]\". With the default setting only the system default "
+"keyboard layout is shown and the option \"Other...\" which pops-up a dialog "
+"box showing a full list of available keyboard layouts which the user can "
+"select."
+msgstr ""
+
+#: C/gdm.xml:1709(para)
+msgid ""
+"Users are not intended to change this setting by hand. Instead GDM keeps "
+"track of any keyboard layouts selected in this configuration key, and will "
+"show them in the keyboard layout combo box along with the \"Other...\" "
+"choice. This way, commonly selected keyboard layouts are easier to select."
+msgstr ""
+
+#: C/gdm.xml:1720(term)
+msgid "/apps/gdm/simple-greeter/wm_use_compiz"
+msgstr "/apps/gdm/simple-greeter/wm_use_compiz"
+
+#: C/gdm.xml:1723(para)
+msgid ""
+"Controls whether compiz is used as the window manager instead of metacity."
+msgstr ""
+"Controla si s'utilitza el compiz com a gestor de finestres en lloc del "
+"metacity."
+
+#: C/gdm.xml:1733(title)
+msgid "Accessibility Configuration"
+msgstr "Configuració de l'accessibilitat"
+
+#: C/gdm.xml:1735(para)
+msgid ""
+"This section describes the accessibility configuration options available in "
+"GDM."
+msgstr ""
+"Aquesta secció descriu les opcions disponibles en la configuració "
+"d'accessibilitat del GDM."
+
+#: C/gdm.xml:1741(title)
+msgid "GDM Accessibility Dialog And GConf Keys"
+msgstr "Diàleg d'accessibilitat del GDM i claus del GConf"
+
+#: C/gdm.xml:1743(para)
+msgid ""
+"The GDM greeter panel at the login screen displays an accessibility icon. "
+"Clicking on that icon opens the GDM Accessibility Dialog. In the GDM "
+"Accessibility Dialog, there is a list of checkboxes, so the user can enable "
+"or disable the associated assistive tools."
+msgstr ""
+
+#: C/gdm.xml:1750(para)
+msgid ""
+"The checkboxes that correspond to the on-screen keyboard, screen magnifier "
+"and screen reader assistive tools act on the three GConf keys that are "
+"described in the next section of this document. By enabling or disabling "
+"these checkboxes, the associated GConf key is set to \"true\" or \"false\". "
+"When the GConf key is set to true, the assistive tools linked to this GConf "
+"key are launched. When the GConf key is set to \"false\", any running "
+"assistive tool linked to this GConf key are terminated. These GConf keys are "
+"not automatically reset to a default state after the user has logged in. "
+"Consequently, the assistive tools that were running during the last GDM "
+"login session will automatically be launched at the next GDM login session."
+msgstr ""
+
+#: C/gdm.xml:1764(para)
+msgid ""
+"The other checkboxes in the GDM Accessibility Dialog do not have "
+"corresponding GConf keys because no additional program is launched to "
+"provide the accessibility features that they offer. These other options "
+"correspond to accessibility features that are provided by the Xserver, which "
+"is always running during the GDM session."
+msgstr ""
+
+#: C/gdm.xml:1774(title)
+msgid "Accessibility GConf Keys"
+msgstr "Claus del GConf sobre l'accessibilitat"
+
+#: C/gdm.xml:1776(para)
+msgid ""
+"GDM offers the following GConf keys to control its accessibility features:"
+msgstr ""
+"El GDM ofereix les claus del GConf següents per controlar les seves funcions "
+"d'accessibilitat:"
+
+#: C/gdm.xml:1782(title)
+msgid "GDM Configuration Keys"
+msgstr "Claus de configuració del GDM"
+
+#: C/gdm.xml:1785(term)
+msgid "/desktop/gnome/interface/accessibility"
+msgstr "/desktop/gnome/interface/accessibility"
+
+#: C/gdm.xml:1788(para)
+msgid ""
+"Controls whether the Accessibility infrastructure will be started with the "
+"GDM GUI. This is needed for many accessibility technology programs to work."
+msgstr ""
+
+#: C/gdm.xml:1796(term)
+msgid "/desktop/gnome/applications/at/screen_magnifier_enabled"
+msgstr "/desktop/gnome/applications/at/screen_magnifier_enabled"
+
+#: C/gdm.xml:1799(para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is a screen magnifier application."
+msgstr ""
+
+#: C/gdm.xml:1807(term)
+msgid "/desktop/gnome/applications/at/screen_keyboard_enabled"
+msgstr "/desktop/gnome/applications/at/screen_keyboard_enabled"
+
+#: C/gdm.xml:1810(para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is an on-screen keyboard "
+"application."
+msgstr ""
+
+#: C/gdm.xml:1818(term)
+msgid "/desktop/gnome/applications/at/screen_reader_enabled"
+msgstr "/desktop/gnome/applications/at/screen_reader_enabled"
+
+#: C/gdm.xml:1821(para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is a screen reader application."
+msgstr ""
+
+#: C/gdm.xml:1832(title)
+msgid "Linking GConf Keys to Accessbility Tools"
+msgstr "Com enllaçar les claus del GConf a les eines d'accessibilitat"
+
+#: C/gdm.xml:1834(para)
+msgid ""
+"For the screen_magnifier_enabled, the screen_keyboard_enabled, and the "
+"screen_reader_enabled GConf keys, the assistive tool which gets launched "
+"depends on the desktop files located in the GDM autostart directory as "
+"described in the \"Autostart Configuration\" section of this manual. Any "
+"desktop file in the GDM autostart directory can be linked to these GConf key "
+"via specifying that GConf key in the AutostartCondition value in the desktop "
+"file. So the exact AutostartCondition line in the desktop file could be one "
+"of the following:"
+msgstr ""
+
+#: C/gdm.xml:1846(screen)
+#, no-wrap
+msgid ""
+"\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled\n"
+msgstr ""
+"\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled\n"
+
+#: C/gdm.xml:1852(para)
+msgid ""
+"When an accessibility key is true, then any program which is linked to that "
+"key in a GDM autostart desktop file will be launched (unless the Hidden key "
+"is set to true in that desktop file). A single GConf key can even start "
+"multiple assistive tools if there are multiple desktop files with this "
+"AutostartCondition in the GDM autostart directory."
+msgstr ""
+
+#: C/gdm.xml:1862(title)
+msgid "Example Of Modifying Accessibility Tool Configuration"
+msgstr "Exemple de com modificar l'eina de configuració d'accessibilitat"
+
+#: C/gdm.xml:1864(para)
+msgid ""
+"For example, if GNOME is distributed with GOK as the default on-screen "
+"keyboard, then this could be replaced with a different program if desired. "
+"To replace GOK with the on-screen keyboard application \"onboard\" and "
+"additionally activate the assistive tool \"mousetweaks\" for dwelling "
+"support, then the following configuration is needed."
+msgstr ""
+
+#: C/gdm.xml:1872(para)
+msgid ""
+"Create a desktop file for onboard and a second one for mousetweaks; for "
+"example, onboard.desktop and mousetweaks.desktop. These files must be placed "
+"in the GDM autostart directory and be in the format as explained in the "
+"\"Autostart Configuration\" section of this document."
+msgstr ""
+
+#: C/gdm.xml:1880(para)
+msgid "The following is an example <filename>onboard.desktop</filename> file:"
+msgstr ""
+"A continuació un exemple del fitxer <filename>onboard.desktop</filename>:"
+
+#: C/gdm.xml:1884(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Onboard Onscreen Keyboard\n"
+"Comment=Use an on-screen keyboard\n"
+"TryExec=onboard\n"
+"Exec=onboard --size 500x180 -x 20 -y 10\n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+msgstr ""
+
+#: C/gdm.xml:1898(para)
+msgid ""
+"The following is an example <filename>mousetweaks.desktop</filename> file:"
+msgstr ""
+"A continuació un exemple del fitxer <filename>mousetweaks.desktop</filename>:"
+
+#: C/gdm.xml:1903(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Software Mouse-Clicks\n"
+"Comment=Perform clicks by dwelling with the pointer\n"
+"TryExec=mousetweaks\n"
+"Exec=mousetweaks --enable-dwell -m window -c -x 20 -y 240 \n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+msgstr ""
+
+#: C/gdm.xml:1917(para)
+msgid ""
+"Note the line with the AutostartCondition that links both desktop files to "
+"the GConf key for the on-screen keyboard."
+msgstr ""
+
+#: C/gdm.xml:1922(para)
+msgid ""
+"To disable GOK from starting, the desktop file for the GOK on-screen "
+"keyboard must be removed or deactivated. Otherwise onboard and GOK would "
+"simultaneously be started. This can be done by removing the gok.desktop file "
+"from the GDM autostart directory, or by adding the \"Hidden=true\" key "
+"setting to the gok.desktop file."
+msgstr ""
+
+#: C/gdm.xml:1930(para)
+msgid ""
+"After making these changes, GOK will no longer be started when the user "
+"activates the on-screen keyboard in the GDM session; but onboard and "
+"mousetweaks will instead be launched."
+msgstr ""
+
+#: C/gdm.xml:1939(title)
+msgid "General Session Settings"
+msgstr "Paràmetres generals de sessió"
+
+#. <para>
+#.           TODO - I think this section should be expanded upon.  What specific
+#.                  keys are of interest, or would some users be likely to want
+#.                  to configure?  Also, would be good to be more specific about
+#.                  how lock down management is handled.
+#. </para>
+#: C/gdm.xml:1948(para)
+msgid ""
+"The GDM Greeter uses some of the same framework that your desktop session "
+"will use. And so, it is influenced by a number of the same GConf settings. "
+"For each of these settings the Greeter will use the default value unless it "
+"is specifically overridden by a) GDM's installed mandatory policy b) system "
+"mandatory policy. GDM installs its own mandatory policy to lock down some "
+"settings for security."
+msgstr ""
+"El rebedor del GDM utilitza alguns components de l'entorn de treball que "
+"utilitzarà la sessió d'escriptori. I per això l'hi afecten tot un seguit de "
+"paràmetres del GConf compartides. Per cada un d'aquests paràmetres el "
+"rebedor utilitzarà el valor per defecte a no ser que s'hagi sobreescrit per "
+"la política obligatòria instal·lada del GDM o per la política obligatòria "
+"del sistema. El GDM, per seguretat, instal·la la seva política obligatòria "
+"per bloquejar alguns paràmetres."
+
+#: C/gdm.xml:1959(title)
+msgid "GNOME Settings Daemon"
+msgstr "Dimoni de paràmetres del GNOME"
+
+#. <para>
+#.           TODO - I think this section should be expanded upon.  What specific
+#.                  keys are of interest, or would some users be likely to want
+#.                  to configure?  Also, would be good to give a more complete
+#.                  list of plugins that users might want to consider disabling.
+#.                  Also, shouldn't we list the sound/active key in the Greeter
+#.                  configuration setting?  Oddly I do not find this key used
+#.                  in anything but the chooser in SVN.
+#. </para>
+#: C/gdm.xml:1972(para)
+msgid ""
+"GDM enables the following gnome-settings-daemon plugins: a11y-keyboard, "
+"background, sound, xsettings."
+msgstr ""
+"El GDM habilita els connectors següents del gnome-settings-daemon: l'a11y-"
+"keyboard, el background, el sound i l'xsettings."
+
+#: C/gdm.xml:1977(para)
+msgid ""
+"These are responsible for things like the background image, font and theme "
+"settings, sound events, etc."
+msgstr ""
+"Aquests són responsables d'aspectes com la imatge de fons, el tipus de "
+"lletra i els paràmetres del tema, els esdeveniments de so, etc."
+
+#: C/gdm.xml:1982(para)
+msgid ""
+"Plugins can also be disabled using GConf. For example, if you want to "
+"disable the sound plugin then unset the following key: <filename>/apps/gdm/"
+"simple-greeter/settings-manager-plugins/sound/active</filename>."
+msgstr ""
+"Els connectors es poden inhabilitar utilitzant el GConf. Per exemple, si "
+"voleu inhabilitar el connector de so llavors inhabiliteu la clau següent: "
+"<filename>/apps/gdm/simple-greeter/settings-manager-plugins/sound/active</"
+"filename>."
+
+#: C/gdm.xml:1990(title)
+msgid "GDM Session Configuration"
+msgstr "Configuració de sessió del GDM"
+
+#: C/gdm.xml:1992(para)
+msgid ""
+"GDM sessions are specified using the FreeDesktop.org Desktop Entry "
+"Specification, which can be referenced at the following URL: <ulink url="
+"\"http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec\"> "
+"http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec</ulink>."
+msgstr ""
+"Les sessions del GDM s'especifiquen utilitzant l'Especificació d'entrada de "
+"l'escriptori de la FreeDesktop.org, que es pot consultar a l'URL següent: "
+"<ulink url=\"http://www.freedesktop.org/wiki/Specifications/desktop-entry-"
+"spec\">http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec</"
+"ulink>."
+
+#: C/gdm.xml:1999(para)
+msgid ""
+"By default, GDM will install desktop files in the <filename>&lt;share&gt;/"
+"xsessions</filename> directory. GDM will search the following directories in "
+"this order to find desktop files: <filename>&lt;etc&gt;/X11/sessions/</"
+"filename>, <filename>&lt;dmconfdir&gt;/Sessions</filename>, <filename>&lt;"
+"share&gt;/xsessions</filename>, and <filename>&lt;share&gt;/gdm/"
+"BuiltInSessions</filename>. By default the <filename>&lt;dmconfdir&gt;</"
+"filename> is set to <filename>&lt;etc&gt;/dm/</filename> unless GDM is "
+"configured to use a different directory via the \"--with-dmconfdir\" option."
+msgstr ""
+
+#: C/gdm.xml:2012(para)
+msgid ""
+"A session can be disabled by editing the desktop file and adding a line as "
+"follows: <filename>Hidden=true</filename>."
+msgstr ""
+"Es pot inhabilitar una sessió editant el fitxer d'escriptori i afegint una "
+"línia com segueix: <filename>Hidden=true</filename>."
+
+#: C/gdm.xml:2017(para)
+msgid ""
+"GDM desktop files support a GDM-specific extension, a key named \"X-GDM-"
+"BypassXsession\". If the key is not specified in a desktop file, the value "
+"defaults to \"false\". If this key is specified to be \"true\" in a desktop "
+"file, then GDM will launch the program specified by the desktop file \"Exec"
+"\" key directly when starting the user session. It will not run the program "
+"via the <filename>&lt;etc&gt;/gdm/Xsession</filename> script, which is the "
+"normal behavior. Since bypassing the <filename>&lt;etc&gt;/gdm/Xsession</"
+"filename> script avoids setting up the user session with the normal system "
+"and user settings, sessions started this way can be useful for debugging "
+"problems in the system or user scripts that might be preventing a user from "
+"being able to start a session."
+msgstr ""
+
+#: C/gdm.xml:2036(title)
+msgid "GDM User Session and Language Configuration"
+msgstr "Configuració de sessió i d'idioma de l'usuari del GDM"
+
+#: C/gdm.xml:2037(para)
+msgid ""
+"The user's default session and language choices are stored in the "
+"<filename>~/.dmrc</filename> file. When a user logs in for the first time, "
+"this file is created with the user's initial choices. The user can change "
+"these default values by simply changing to a different value when logging "
+"in. GDM will remember this change for subsequent logins."
+msgstr ""
+"Les opcions per defecte de sessió i d'idioma de l'usuari s'emmagatzemen al "
+"fitxer <filename>~/.dmrc</filename>. Quan un usuari entra per primer cop, es "
+"crea el fitxer amb les opcions inicials de l'usuari. L'usuari pot canviar "
+"aquests valors per defecte canviant-los a un valor diferent quan entra. El "
+"GDM recordarà aquests canvis per les entrades posteriors."
+
+#: C/gdm.xml:2045(para)
+msgid ""
+"The <filename>~/.dmrc</filename> file is in the standard <filename>INI</"
+"filename> format. It has one section called <filename>[Desktop]</filename> "
+"which has two keys: <filename>Session</filename> and <filename>Language</"
+"filename>."
+msgstr ""
+"El fitxer <filename>~/.dmrc</filename> està en format estàndard "
+"<filename>INI</filename>. Aquest té una secció anomenada <filename>[Desktop]"
+"</filename> la qual té dues claus: <filename>Session</filename> i "
+"<filename>Language</filename>."
+
+#: C/gdm.xml:2052(para)
+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. 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 clau <filename>Session</filename> especifica el nom base del fitxer de "
+"sessió <filename>.desktop</filename> que l'usuari vol utilitzar normalment "
+"sense l'extensió <filename>.desktop</filename>. La clau <filename>Language</"
+"filename> especifica l'idioma que l'usuari vol utilitzar per defecte. Si "
+"falta alguna d'aquestes claus, s'utilitzarà el valor predeterminat del "
+"sistema. El fitxer normalment té l'aparença següent:"
+
+#: C/gdm.xml:2061(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop]\n"
+"Session=gnome\n"
+"Language=cs_CZ.UTF-8\n"
+msgstr ""
+"\n"
+"[Desktop]\n"
+"Session=gnome\n"
+"Language=ca_ES.UTF-8\n"
+
+#: C/gdm.xml:2073(title)
+msgid "GDM Commands"
+msgstr "Ordres del GDM"
+
+#: C/gdm.xml:2076(title)
+msgid "GDM Root User Commands"
+msgstr "Ordres de l'usuari primari del GDM"
+
+#: C/gdm.xml:2078(para)
+msgid ""
+"The GDM package provides the following commands in <filename>sbindir</"
+"filename> intended to be run by the root user:"
+msgstr ""
+"El paquet GDM proporciona les ordres següents a <filename>sbindir</filename> "
+"amb la intenció de que siguin executades per l'usuari primari:"
+
+#: C/gdm.xml:2084(title) C/gdm.xml:2099(title)
+msgid ""
+"<command>gdm</command> and <command>gdm-binary</command> Command Line Options"
+msgstr ""
+"Opcions de la línia d'ordres del <command>gdm</command> i del <command>gdm-"
+"binary</command>"
+
+#: C/gdm.xml:2087(para)
+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>&lt;etc&gt;/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. The <command>gdm-binary</command> is the "
+"actual GDM daemon."
+msgstr ""
+"L'ordre <command>gdm</command> realment només és un script que executa el "
+"<command>gdm-binary</command>, passant qualsevol opció. Abans d'executar el "
+"<command>gdm-binary</command>, l'script de l'embolcall del gdm inclourà el "
+"fitxer <filename>&lt;etc&gt;/profile</filename> per establir les variables "
+"d'entorn estàndard del sistema. Per tenir una millor compatibilitat de la "
+"internacionalització, també s'establirà la variable d'entorn LC_MESSAGES a "
+"LANG si no s'han establert qualsevol cap d'elles. El dimoni del GDM en sí és "
+"el <command>gdm-binary</command>."
+
+#: C/gdm.xml:2103(term)
+msgid "-?, --help"
+msgstr "-?, --help"
+
+#: C/gdm.xml:2105(para)
+msgid "Gives a brief overview of the command line options."
+msgstr "Proporciona un resum general de les opcions de la línia d'ordres."
+
+#: C/gdm.xml:2112(term)
+msgid "--fatal-warnings"
+msgstr "--fatal-warnings"
+
+#: C/gdm.xml:2114(para)
+msgid "Make all warnings cause GDM to exit."
+msgstr "Fa que tots els avisos provoquin que el GDM surti."
+
+#: C/gdm.xml:2121(term)
+msgid "--timed-exit"
+msgstr "--timed-exit"
+
+#: C/gdm.xml:2123(para)
+msgid "Exit after 30 seconds. Useful for debugging."
+msgstr "Surt després de 30 segons. És útil per depurar."
+
+#: C/gdm.xml:2130(term)
+msgid "--version"
+msgstr "--version"
+
+#: C/gdm.xml:2132(para)
+msgid "Print the version of the GDM daemon."
+msgstr "Mostra la versió del dimoni del GDM."
+
+#: C/gdm.xml:2141(title)
+msgid "<command>gdm-restart</command> Command Line Options"
+msgstr "Opcions de la línia d'ordres del <command>gdm-restart</command>"
+
+#: C/gdm.xml:2143(para)
+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 ""
+"El <command>gdm-restart</command> atura i torna a iniciar el GDM enviant una "
+"senyal HUP al dimoni del GDM. Aquesta ordre finalitzarà immediatament totes "
+"les sessions i farà sortir als usuaris que estan connectats actualment amb "
+"el GDM."
+
+#: C/gdm.xml:2151(title)
+msgid "<command>gdm-safe-restart</command> Command Line Options"
+msgstr "Opcions de la línia d'ordres del <command>gdm-safe-restart</command>"
+
+#: C/gdm.xml:2153(para)
+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 ""
+"El <command>gdm-safe-restart</command> atura i torna a iniciar el GDM "
+"enviant una senyal USR1 al dimoni del GDM. Es tornarà a iniciar el GDM quan "
+"hagin sortit tots els usuaris."
+
+#: C/gdm.xml:2161(title)
+msgid "<command>gdm-stop</command> Command Line Options"
+msgstr "Opcions de la línia d'ordres del <command>gdm-stop</command>"
+
+#: C/gdm.xml:2163(para)
+msgid ""
+"<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM "
+"signal."
+msgstr ""
+"El <command>gdm-stop</command> atura el GDM enviant una senyal TERM al "
+"dimoni del GDM."
+
+#: C/gdm.xml:2174(title)
+msgid "Troubleshooting"
+msgstr "Resolució de problemes"
+
+#. <para>
+#.       TODO - any other tips we should add?  Might be useful to highlight any
+#.              common D-Bus configuration issues?
+#. </para>
+#: C/gdm.xml:2182(para)
+msgid ""
+"This section discusses helpful tips for getting GDM working. In general, if "
+"you have a problem using GDM, you can submit a bug or send an email to the "
+"gdm-list mailing list. Information about how to do this is in the "
+"Introduction section of the document."
+msgstr ""
+"Aquesta secció descriu consells útils per fer funcionar el GDM. En general, "
+"si teniu algun problema utilitzant el GDM, podeu transmetre un error o "
+"enviar un correu electrònic a la llista de correu gdm-list. Trobareu més "
+"informació sobre com fer-ho a la secció «Introducció» del document."
+
+#: C/gdm.xml:2189(para)
+msgid ""
+"If GDM is failing to work properly, it is always a good idea to include "
+"debug information. To enable debugging, set the debug/Enable key to \"true\" "
+"in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file and restart "
+"GDM. Then use GDM to the point where it fails, and debug output will be sent "
+"to the system log file (<filename>&lt;var&gt;/log/messages</filename> or "
+"<filename>&lt;var&gt;/adm/messages</filename> depending on your Operating "
+"System). If you share this output with the GDM community via a bug report or "
+"email, please only include the GDM related debug information and not the "
+"entire file since it can be large. If you do not see any GDM syslog output, "
+"you may need to configure syslog (refer to the <ulink type=\"help\" url="
+"\"man:syslog\">syslog</ulink> man page)."
+msgstr ""
+"Si el GDM no funciona correctament, sempre és una bona idea incloure "
+"informació de depuració. Per habilitar la depuració, establiu la clau «debug/"
+"Enable» a «true» en el fitxer <filename>&lt;etc&gt;/gdm/custom.conf</"
+"filename> i reinicieu el GDM. Llavors utilitzeu el GDM cap al punt on falla "
+"i la sortida de depuració s'enviarà al registre del sistema (<filename>&lt;"
+"var&gt;/log/messages</filename> o <filename>&lt;var&gt;/adm/messages</"
+"filename> en funció del vostre sistema operatiu). Si compartiu aquesta "
+"sortida amb la comunitat del GDM mitjançant un informe d'error o un correu "
+"electrònic, incloeu només la informació de depuració relacionada amb el GDM "
+"i no el fitxer sencer ja que pot ser molt gran. Si no veieu la sortida del "
+"registre del sistema del GDM, potser heu de configurar el registre del "
+"sistema (consulteu la pàgina del manual <ulink type=\"help\" url=\"man:syslog"
+"\">syslog</ulink>)."
+
+#: C/gdm.xml:2205(title)
+msgid "GDM Will Not Start"
+msgstr "El GDM no s'inicia"
+
+#: C/gdm.xml:2207(para)
+msgid ""
+"There are a many problems that can cause GDM to fail to start, but this "
+"section will discuss a few common problems and how to approach tracking down "
+"a problem with GDM starting. Some problems will cause GDM to respond with an "
+"error message or dialog when it tries to start, but it can be difficult to "
+"track down problems when GDM fails silently."
+msgstr ""
+"Hi ha molts problemes que poden provocar que el GDM falli en iniciar-se, en "
+"aquesta secció però només es descriu alguns problemes comuns i com descobrir "
+"la causa dels problemes amb l'inicialització del GDM. Alguns problemes faran "
+"que el GDM mostri un missatge o diàleg d'error quan intenta iniciar, però "
+"pot ser difícil saber la causa del problema si el GDM falla de forma "
+"silenciosa."
+
+#: C/gdm.xml:2216(para)
+msgid ""
+"First make sure that the Xserver is configured properly. The GDM "
+"configuration file contains a command in the [server-Standard] section that "
+"is used for starting the Xserver. Verify that this command works on your "
+"system. Running this command from the console should start the Xserver. If "
+"it fails, then the problem is likely with your Xserver configuration. Refer "
+"to your Xserver error log for an idea of what the problem may be. The "
+"problem may also be that your Xserver requires different command-line "
+"options. If so, then modify the Xserver command in the GDM configuration "
+"file so that it is correct for your system."
+msgstr ""
+"Primer assegureu-vos que el servidor d'X està configurat correctament. El "
+"fitxer de configuració del GDM conté una ordre a la secció [server-Standard] "
+"que s'utilitza per iniciar el servidor d'X. Verifiqueu que aquesta ordre "
+"funciona. En executar aquesta ordre des del terminal s'hauria d'iniciar el "
+"servidor d'X. Si aquesta falla, llavors el problema segurament és amb la "
+"configuració del servidor d'X. Consulteu el registre d'errors del servidor "
+"d'X per mirar quin pot ser el problema. El problema també pot ser que el "
+"servidor d'X necessita opcions diferents de la línia d'ordres. Si és així, "
+"modifiqueu l'ordre del servidor d'X al fitxer de configuració del GDM perquè "
+"sigui correcte pel vostre sistema."
+
+#: C/gdm.xml:2229(para)
+msgid ""
+"Also make sure that the <filename>/tmp</filename> directory has reasonable "
+"ownership and permissions, and that the machine's file system is not full. "
+"These problems will cause GDM to fail to start."
+msgstr ""
+"També assegureu-vos que el directori <filename>/tmp</filename> té un "
+"propietari i permisos raonables, i que el sistema de fitxers de l'ordinador "
+"no està ple. Aquests problemes poden provocar que el GDM falli en iniciar-se."
+
+#: C/gdm.xml:2240(title)
+msgid "License"
+msgstr "Llicència"
+
+#: C/gdm.xml:2241(para)
+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 ""
+"Aquest programa és programari lliure; podeu redistribuir-lo i/o modificar-lo "
+"sota els termes de la <citetitle>Llicència pública general de GNU</"
+"citetitle> tal com publica la Free Software Foundation; tant en la versió 2 "
+"de la llicència, o (a la vostra opció) una versió posterior."
+
+#: C/gdm.xml:2249(para)
+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 ""
+"Aquest programa es distribueix amb l'esperança de que sigui útil, però SENSE "
+"CAP GARANTIA; fins i tot sense la garantia implícita de COMERCIALITZACIÓ o "
+"ADEQUACIÓ A UN ÚS CONCRET. Per a més detalls vegeu la <citetitle>Llicència "
+"pública general de GNU</citetitle>."
+
+#: C/gdm.xml:2255(para)
+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>51 Franklin Street, Fifth Floor</"
+"street><city>Boston</city>, <state>MA</state><postcode>02110-1301</"
+"postcode><country>USA</country></address>"
+msgstr ""
+"S'inclou una còpia de la <citetitle>Llicència pública general de GNU</"
+"citetitle> en l'apèndix de la <citetitle>Guia d'usuaris del GNOME</"
+"citetitle>. També podeu obtenir una copia de la <citetitle>Llicència pública "
+"general de GNU</citetitle> de la Free Software Foundation visitant el <ulink "
+"type=\"http\" url=\"http://www.fsf.org\">seu lloc web</ulink> o escrivint a "
+"<address> Free Software Foundation, Inc. <street>51 Franklin Street, Fifth "
+"Floore</street><city>Boston</city>, <state>MA</state><postcode>02110-1301</"
+"postcode><country>USA</country></address>"
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
+#: C/gdm.xml:0(None)
+msgid "translator-credits"
+msgstr "Joan Duran <jodufi@gmail.com>, 2009"
diff --git a/docs/gl/gl.po b/docs/gl/gl.po
new file mode 100644
index 0000000..bd06519
--- /dev/null
+++ b/docs/gl/gl.po
@@ -0,0 +1,2605 @@
+# Galician translation for gdm.
+# Copyright (C) 2012 gdm's COPYRIGHT HOLDER
+# This file is distributed under the same license as the gdm package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+# Fran Dieguez <frandieguez@gnome.org>, 2012.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: gdm master\n"
+"POT-Creation-Date: 2012-03-04 11:50+0000\n"
+"PO-Revision-Date: 2012-03-04 23:10+0100\n"
+"Last-Translator: Fran Dieguez <frandieguez@gnome.org>\n"
+"Language-Team: Galician <gnome-l10n-gl@gnome.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n!=1);\n"
+
+#: C/gdm.xml:13(title)
+msgid "GNOME Display Manager Reference Manual"
+msgstr "Manual de referencia do Xestor de entrada de GNOME"
+
+#: C/gdm.xml:17(revnumber)
+msgid "0.0"
+msgstr "0.0"
+
+#: C/gdm.xml:18(date)
+msgid "2008-09"
+msgstr "2008-09"
+
+#: C/gdm.xml:23(para)
+msgid "GDM is the GNOME Display Manager, a graphical login program."
+msgstr ""
+"GDM é o Xestor de entrada de GNOME, un programa gráfico de inicio de sesión."
+
+#: C/gdm.xml:30(firstname)
+msgid "Martin"
+msgstr "Martin"
+
+#: C/gdm.xml:30(othername)
+msgid "K."
+msgstr "K."
+
+#: C/gdm.xml:31(surname)
+msgid "Petersen"
+msgstr "Petersen"
+
+#: C/gdm.xml:33(email)
+msgid "mkp@mkp.net"
+msgstr "mkp@mkp.net"
+
+#: C/gdm.xml:37(firstname)
+msgid "George"
+msgstr "George"
+
+#: C/gdm.xml:37(surname)
+msgid "Lebl"
+msgstr "Lebl"
+
+#: C/gdm.xml:39(email)
+msgid "jirka@5z.com"
+msgstr "jirka@5z.com"
+
+#: C/gdm.xml:43(firstname)
+msgid "Jon"
+msgstr "Jon"
+
+#: C/gdm.xml:43(surname)
+msgid "McCann"
+msgstr "McCann"
+
+#: C/gdm.xml:45(email)
+msgid "mccann@jhu.edu"
+msgstr "mccann@jhu.edu"
+
+#: C/gdm.xml:49(firstname)
+msgid "Ray"
+msgstr "Ray"
+
+#: C/gdm.xml:49(surname)
+msgid "Strode"
+msgstr "Strode"
+
+#: C/gdm.xml:51(email)
+msgid "rstrode@redhat.com"
+msgstr "rstrode@redhat.com"
+
+#: C/gdm.xml:55(firstname)
+msgid "Brian"
+msgstr "Brian"
+
+#: C/gdm.xml:55(surname)
+msgid "Cameron"
+msgstr "Cameron"
+
+#: C/gdm.xml:57(email)
+msgid "Brian.Cameron@Oracle.COM"
+msgstr "Brian.Cameron@Oracle.COM"
+
+#: C/gdm.xml:62(year)
+msgid "1998"
+msgstr "1998"
+
+#: C/gdm.xml:63(year)
+msgid "1999"
+msgstr "1999"
+
+#: C/gdm.xml:64(holder)
+msgid "Martin K. Petersen"
+msgstr "Martin K. Petersen"
+
+#: C/gdm.xml:67(year)
+msgid "2001"
+msgstr "2001"
+
+#: C/gdm.xml:68(year) C/gdm.xml:73(year) C/gdm.xml:79(year)
+msgid "2003"
+msgstr "2003"
+
+#: C/gdm.xml:69(year)
+msgid "2004"
+msgstr "2004"
+
+#: C/gdm.xml:70(holder)
+msgid "George Lebl"
+msgstr "George Lebl"
+
+#: C/gdm.xml:74(year)
+msgid "2007"
+msgstr "2007"
+
+#: C/gdm.xml:75(year)
+msgid "2008"
+msgstr "2008"
+
+#: C/gdm.xml:76(holder)
+msgid "Red Hat, Inc."
+msgstr "Red Hat, Inc."
+
+#: C/gdm.xml:80(year)
+msgid "2011"
+msgstr "2011"
+
+#: C/gdm.xml:81(holder)
+msgid "Oracle and/or its affiliates. All rights reserved."
+msgstr "Oracle e/ou os seus afiliados. Todos os dereitos reservados."
+
+#: C/gdm.xml:2(para)
+msgid ""
+"Permission is granted to copy, distribute and/or modify this document under "
+"the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any "
+"later version published by the Free Software Foundation with no Invariant "
+"Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy "
+"of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or "
+"in the file COPYING-DOCS distributed with this manual."
+msgstr ""
+"Pode copiar, distribuír e modificar este documento baixo os termos da "
+"Licenza de Documentación Libre GNU (GFDL) na súa versión 1.1 ou posterior, "
+"publicada pola Free Software Foundation, sen seccións invariantes e sen "
+"textos de portada ou de contraportada. Pode atopar unha copia da GFDL en "
+"<ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> ou no ficheiro COPYING-"
+"DOCS distribuído xunto con este manual."
+
+#: C/gdm.xml:12(para)
+msgid ""
+"This manual is part of a collection of GNOME manuals distributed under the "
+"GFDL. If you want to distribute this manual separately from the collection, "
+"you can do so by adding a copy of the license to the manual, as described in "
+"section 6 of the license."
+msgstr ""
+"Este manual forma parte dunha colección de documentos de GNOME distribuidos "
+"segundo a GFDL. Se desexa distribuír este manual de forma independente da "
+"colección, pode facelo agregando unha copia da licenza ao documento, segundo "
+"se descibe na sección 6 da mesma."
+
+#: C/gdm.xml:19(para)
+msgid ""
+"Many of the names used by companies to distinguish their products and "
+"services are claimed as trademarks. Where those names appear in any GNOME "
+"documentation, and the members of the GNOME Documentation Project are made "
+"aware of those trademarks, then the names are in capital letters or initial "
+"capital letters."
+msgstr ""
+
+#: C/gdm.xml:35(para)
+msgid ""
+"DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, "
+"EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT "
+"THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS "
+"MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE "
+"RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR "
+"MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR "
+"MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL "
+"WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY "
+"SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN "
+"ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION "
+"OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND"
+msgstr ""
+
+#: C/gdm.xml:55(para)
+msgid ""
+"UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING "
+"NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY "
+"CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE "
+"DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON "
+"FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF "
+"ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, "
+"WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES "
+"OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED "
+"VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE "
+"POSSIBILITY OF SUCH DAMAGES."
+msgstr ""
+
+#: C/gdm.xml:28(para)
+msgid ""
+"DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS "
+"OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: "
+"<placeholder-1/>"
+msgstr ""
+
+#: C/gdm.xml:86(releaseinfo) C/gdm.xml:97(para)
+msgid ""
+"This manual describes version 2.26.0 of the GNOME Display Manager. It was "
+"last updated on 02/10/2009."
+msgstr ""
+"Este manual describe a versión 2.26.0 do Xestor de entrada de GNOME. "
+"Actualizouse por última vez o 2 de febreiro de 2009."
+
+#: C/gdm.xml:95(title)
+msgid "Terms and Conventions Used in This Manual"
+msgstr "Termos e convencións usados neste manual"
+
+#: C/gdm.xml:102(para)
+msgid ""
+"Chooser - A program used to select a remote host for managing a display "
+"remotely on the attached display (<command>gdm-host-chooser</command>)."
+msgstr ""
+"Selector: Un programa que se usa para seleccionar un equipo remoto para "
+"xestionar unha pantalla remotamente na pantalla local (<command>gdm-host-"
+"chooser</command>)."
+
+#: C/gdm.xml:107(para)
+msgid ""
+"FreeDesktop - The organization providing desktop standards, such as the "
+"Desktop Entry Specification used by GDM. <ulink type=\"http\" url=\"http://"
+"www.freedesktop.org/\"> http://www.freedesktop.org</ulink>."
+msgstr ""
+"FreeDesktop: A organización que fornece estándares para o escritorio, tales "
+"como a Especificación de Entrada do Escritorio que usa GDM <ulink type=\"http"
+"\" url=\"http://www.freedesktop.org/\">http://www.freedesktop.org</ulink>."
+
+#: C/gdm.xml:113(para)
+msgid ""
+"GDM - GNOME Display Manager. Used to describe the software package as a "
+"whole."
+msgstr ""
+"GDM: O xestor de entrada de GNOME. Úsase para describir o paquete de "
+"software como un todo."
+
+#: C/gdm.xml:118(para)
+msgid ""
+"Greeter - The graphical login window (<command>gdm-simple-greeter</command>)."
+msgstr ""
+"Interface de entrada con temas: A xanela de entrada gráfica (<command>gdm-"
+"simple-greeter</command>)."
+
+#: C/gdm.xml:122(para)
+msgid "PAM - Pluggable Authentication Mechanism"
+msgstr ""
+"PAM: Mecanismo de engadidos de autenticación (Pluggable Autentication "
+"Mechanism)"
+
+#: C/gdm.xml:126(para)
+msgid "XDMCP - X Display Manage Protocol"
+msgstr ""
+"XDMCP: Protocolo de xestión de pantallas X (X Display Manager Protocol)"
+
+#: C/gdm.xml:130(para)
+msgid ""
+"Xserver - An implementation of the X Window System. For example the Xorg "
+"Xserver provided by the X.org Foundation <ulink type=\"http\" url=\"http://"
+"www.x.org/\">http://www.x.org</ulink>."
+msgstr ""
+"Servidor X: Unha implementación do X Windows System. Por exemplo, o servidor "
+"X de Xorg fornecido pola Fundación X.org <ulink type=\"http\" url=\"http://"
+"www.x.org/\">http://www.x.org</ulink>."
+
+#: C/gdm.xml:136(para)
+msgid ""
+"Paths that start with a word in angle brackets are relative to the "
+"installation prefix. I.e. <filename>&lt;share&gt;/pixmaps/</filename> refers "
+"to <filename>/usr/share/pixmaps</filename> if GDM was configured with "
+"<command>--prefix=/usr</command>."
+msgstr ""
+"Rutas que comezan cunha palabra entre parénteses son relativas ao prefixo de "
+"instalación, p.ex. <filename>&lt;share&gt;/pixmaps/</filename> refírese a "
+"<filename>/usr/share/pixmaps</filename> se GDM configurouse con <command>--"
+"prefix=/usr</command>."
+
+#: C/gdm.xml:147(title)
+msgid "Overview"
+msgstr "Vista xeral"
+
+#: C/gdm.xml:150(title)
+msgid "Introduction"
+msgstr "Introdución"
+
+#: C/gdm.xml:152(para)
+msgid ""
+"The GNOME Display Manager (GDM) is a display manager that implements all "
+"significant features required for managing attached and remote displays. GDM "
+"was written from scratch and does not contain any XDM or X Consortium code."
+msgstr ""
+"O Xestor de entrada de GNOME (GDM) é un xestor de entrada que implementa "
+"todas as características significativas requiridas para xestionar pantallas "
+"remotas e locais. GDM escribiuse desde cero e non contén nada de código de "
+"XDM ou do X Consortium."
+
+#: C/gdm.xml:159(para)
+msgid ""
+"Note that GDM is configurable, and many configuration settings have an "
+"impact on security. Issues to be aware of are highlighted in this document."
+msgstr ""
+"Note que o GDM é altamaente configurábel e moitos axustes de configuración "
+"poden afectar á seguranza. Os temas sobre os que debe prestar atención están "
+"realzados neste documento."
+
+#: C/gdm.xml:165(para)
+msgid ""
+"Please note that some Operating Systems configure GDM to behave differently "
+"than the default values as described in this document. If GDM does not seem "
+"to behave as documented, then check to see if any related configuration may "
+"be different than described here."
+msgstr ""
+"Note que algúns sistemas operativos configuran GDM para comportarse de forma "
+"diferente aos valores predetermiandos, como se describe neste documento. Se "
+"GDM non parece comportarse como se documenta, entón comprobe se algunha "
+"configuración relacionada difire da aquí describa."
+
+#: C/gdm.xml:172(para)
+msgid ""
+"For further information about GDM, refer to the project website at <ulink "
+"type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> http://www.gnome."
+"org/projects/gdm</ulink> and the project Wiki <ulink type=\"http\" url="
+"\"http://live.gnome.org/GDM\"> http://live.gnome.org/GDM</ulink>."
+msgstr ""
+"Para obter máis información sobre GDM consulte a páxina web do proxecto en "
+"<ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\">http://www."
+"gnome.org/projects/gdm</ulink> e o wiki do proxecto en <ulink type=\"http\" "
+"url=\"http://live.gnome.org/GDM\">http://live.gnome.org/GDM</ulink>."
+
+#: C/gdm.xml:180(para)
+msgid ""
+"For discussion or queries about GDM, refer to the <address><email>gdm-"
+"list@gnome.org</email></address> mail list. This list is archived, and is a "
+"good resource to check to seek answers to common questions. This list is "
+"archived at <ulink type=\"http\" url=\"http://mail.gnome.org/archives/gdm-"
+"list/\"> http://mail.gnome.org/archives/gdm-list/</ulink> and has a search "
+"facility to look for messages with keywords."
+msgstr ""
+
+#: C/gdm.xml:190(para)
+msgid ""
+"Please submit any bug reports or enhancement requests to the \"gdm\" "
+"category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\"> http://"
+"bugzilla.gnome.org</ulink>."
+msgstr ""
+
+#: C/gdm.xml:199(title)
+msgid "Interface Stability"
+msgstr "Estabilidade de interfaces"
+
+#: C/gdm.xml:201(para)
+msgid ""
+"GDM 2.20 and earlier supported stable configuration interfaces. However, the "
+"codebase was completely rewritten for GDM 2.22, and is not completely "
+"backward compatible with older releases. This is in part because things work "
+"differently, so some options just don't make sense, in part because some "
+"options never made sense, and in part because some functionality has not "
+"been reimplemented yet."
+msgstr ""
+
+#: C/gdm.xml:210(para)
+msgid ""
+"Interfaces which continue to be supported in a stable fashion include the "
+"Init, PreSession, PostSession, PostLogin, and Xsession scripts. Some daemon "
+"configuration options in the <filename>&lt;etc&gt;/gdm/custom.conf</"
+"filename> file continue to be supported. Also, the <filename>~/.dmrc</"
+"filename>, and face browser image locations are still supported."
+msgstr ""
+
+#: C/gdm.xml:219(para)
+msgid ""
+"GDM 2.20 and earlier supported the ability to manage multiple displays with "
+"separate graphics cards, such as used in terminal server environments, login "
+"in a window via a program like Xnest or Xephyr, the gdmsetup program, XML-"
+"based greeter themes, and the ability to run the XDMCP chooser from the "
+"login screen. These features were not added back during the 2.22 rewrite."
+msgstr ""
+
+#: C/gdm.xml:231(title)
+msgid "Functional Description"
+msgstr "Descrición funcional"
+
+#. <para>
+#.         TODO - Would be good to discuss D-Bus, perhaps the new GObject model,
+#.                and to explain the reasons why the rewrite made GDM better.
+#.                From a high-level overview perspective, rather than the
+#.                technical aspects.
+#. </para>
+#: C/gdm.xml:242(para)
+msgid ""
+"GDM is responsible for managing displays on the system. This includes "
+"authenticating users, starting the user session, and terminating the user "
+"session. GDM is configurable and the ways it can be configured are described "
+"in the \"Configuring GDM\" section of this document. GDM is also accessible "
+"for users with disabilities."
+msgstr ""
+
+#: C/gdm.xml:250(para)
+msgid ""
+"GDM provides the ability to manage the main console display, and displays "
+"launched via VT. It is integrated with other programs, such as the Fast User "
+"Switch Applet (FUSA) and gnome-screensaver to manage multiple displays on "
+"the console via the Xserver Virtual Terminal (VT) interface. It also can "
+"manage XDMCP displays."
+msgstr ""
+
+#: C/gdm.xml:258(para)
+msgid ""
+"Regardless of the display type, GDM will do the following when it manages "
+"the display. It will start an Xserver process, then run the <filename>Init</"
+"filename> script as the root user, and start the greeter program on the "
+"display."
+msgstr ""
+
+#: C/gdm.xml:265(para)
+msgid ""
+"The greeter program is run as the unprivileged \"gdm\" user/group. This user "
+"and group are described in the \"Security\" section of this document. The "
+"main functions of the greeter program are to provide a mechanism for "
+"selecting an account for log in and to drive the dialogue between the user "
+"and system when authenticating that account. The authentication process is "
+"driven by Pluggable Authentication Modules (PAM). The PAM modules determine "
+"what prompts (if any) are shown to the user to authenticate. On the average "
+"system, the greeter program will request a username and password for "
+"authentication. However some systems may be configured to use supplemental "
+"mechanisms such as a fingerprint or SmartCard readers. GDM can be configured "
+"to support these alternatives in parallel with greeter login extensions and "
+"the <command>--enable-split-authentication</command><filename>./configure</"
+"filename> option, or one at a time via system PAM configuration."
+msgstr ""
+
+#: C/gdm.xml:284(para)
+msgid ""
+"The smartcard extension can be enabled or disabled via the <filename>org."
+"gnome.display-manager.extensions.smartcard.active</filename> gsettings key."
+msgstr ""
+
+#: C/gdm.xml:290(para)
+msgid ""
+"Likewise, the fingerprint extension can be enabled or disabled via the "
+"<filename>org.gnome.display-manager.extensions.fingerprint.active</filename> "
+"gsettings key."
+msgstr ""
+
+#: C/gdm.xml:296(para)
+msgid ""
+"GDM and PAM can be configured to not require any input, which will cause GDM "
+"to automatically log in and simply start a session, which can be useful for "
+"some environments, such as single user systems or kiosks."
+msgstr ""
+
+#: C/gdm.xml:303(para)
+msgid ""
+"In addition to authentication, the greeter program allows the user to select "
+"which session to start and which language to use. Sessions are defined by "
+"files that end in the .desktop suffix and more information about these files "
+"can be found in the \"GDM User Session and Language Configuration\" section "
+"of this document. By default, GDM is configured to display a face browser so "
+"the user can select their user account by clicking on an image instead of "
+"having to type their username. GDM keeps track of the user's default session "
+"and language in the user's <filename>~/.dmrc</filename> and will use these "
+"defaults if the user did not pick a session or language in the login GUI."
+msgstr ""
+
+#: C/gdm.xml:316(para)
+msgid ""
+"After authenticating a user, the daemon runs the <filename>PostLogin</"
+"filename> script as root, then runs the <filename>PreSession</filename> "
+"script as root. After running these scripts, the user session is started. "
+"When the user exits their session, the <filename>PostSession</filename> "
+"script is run as root. These scripts are provided as hooks for distributions "
+"and end-users to customize how sessions are managed. For example, using "
+"these hooks you could set up a machine which creates the user's $HOME "
+"directory on the fly, and erases it on logout. The difference between the "
+"<filename>PostLogin</filename> and <filename>PreSession</filename> scripts "
+"is that <filename>PostLogin</filename> is run before the pam_open_session "
+"call so is the right place to do anything which should be run before the "
+"user session is initialized. The <filename>PreSession</filename> script is "
+"called after session initialization."
+msgstr ""
+
+#: C/gdm.xml:336(title)
+msgid "Greeter Panel"
+msgstr "O panel da interface de entrada con temas"
+
+#: C/gdm.xml:337(para)
+msgid ""
+"The GDM greeter program displays a panel docked at the bottom of the screen "
+"which provides additional functionality. When a user is selected, the panel "
+"allows the user to select which session, language, and keyboard layout to "
+"use after logging in. The keyboard layout selector also changes the keyboard "
+"layout used when typing your password. The panel also contains an area for "
+"login services to leave status icons. Some example status icons include a "
+"battery icon for current battery usage, and an icon for enabling "
+"accessibility features. The greeter program also provides buttons which "
+"allow the user to shutdown or restart the system. It is possible to "
+"configure GDM to not provide the shutdown and restart buttons, if desired. "
+"GDM can also be configured via PolicyKit (or via RBAC on Oracle Solaris) to "
+"require the user have appropriate authorization before accepting the "
+"shutdown or restart request."
+msgstr ""
+
+#: C/gdm.xml:354(para)
+msgid ""
+"Note that keyboard layout features are only available on systems that "
+"support libxklavier."
+msgstr ""
+
+#: C/gdm.xml:361(title)
+msgid "Accessibility"
+msgstr "Accesibilidade"
+
+#: C/gdm.xml:363(para)
+msgid ""
+"GDM supports \"Accessible Login\", allowing users to log into their desktop "
+"session even if they cannot easily use the screen, mouse, or keyboard in the "
+"usual way. Accessible Technology (AT) features such as an on-screen "
+"keyboard, screen reader, screen magnifier, and Xserver AccessX keyboard "
+"accessibility are available. It is also possible to enable large text or "
+"high contrast icons and controls, if needed. Refer to the \"Accessibility "
+"Configuration\" section of the document for more information how various "
+"accessibility features can be configured."
+msgstr ""
+
+#: C/gdm.xml:375(para)
+msgid ""
+"On some Operating Systems, it is necessary to make sure that the GDM user is "
+"a member of the \"audio\" group for AT programs that require audio output "
+"(such as text-to-speech) to be functional."
+msgstr ""
+
+#: C/gdm.xml:383(title)
+msgid "The GDM Face Browser"
+msgstr "O visor de rostros de GDM"
+
+#: C/gdm.xml:385(para)
+msgid ""
+"The Face Browser is the interface which allows users to select their "
+"username by clicking on an image. This feature can be enabled or disabled "
+"via the /apps/gdm/simple-greeter/disable_user_list GConf key and is on by "
+"default. When disabled, users must type their complete username by hand. "
+"When enabled, it displays all local users which are available for login on "
+"the system (all user accounts defined in the /etc/passwd file that have a "
+"valid shell and sufficiently high UID) and remote users that have recently "
+"logged in. The face browser in GDM 2.20 and earlier would attempt to display "
+"all remote users, which caused performance problems in large, enterprise "
+"deployments."
+msgstr ""
+
+#: C/gdm.xml:399(para)
+msgid ""
+"The Face Browser is configured to display the users who log in most "
+"frequently at the top of the list. This helps to ensure that users who log "
+"in frequently can quickly find their login image."
+msgstr ""
+
+#: C/gdm.xml:405(para)
+msgid ""
+"The Face Browser supports \"type-ahead search\" which dynamically moves the "
+"face selection as the user types to the corresponding username in the list. "
+"This means that a user with a long username will only have to type the first "
+"few characters of the username before the correct item in the list gets "
+"selected."
+msgstr ""
+
+#: C/gdm.xml:413(para)
+msgid ""
+"The icons used by GDM can be installed globally by the sysadmin or can be "
+"located in the user's home directories. If installed globally they should be "
+"in the <filename>&lt;share&gt;/pixmaps/faces/</filename> directory and the "
+"filename should be the name of the user. Face image files should be a "
+"standard image that GTK+ can read, such as PNG or JPEG. Face icons placed in "
+"the global face directory must be readable to the GDM user."
+msgstr ""
+
+#. <para>
+#.         TODO - In the old GDM the ~/gnome2/gdm file is used, but the new code
+#.                seems to use ~/.gnome/gdm.  Error?
+#. </para>
+#: C/gdm.xml:429(para)
+msgid ""
+"If there is no global icon for the user, GDM will look in the user's $HOME "
+"directory for the image file. GDM will first look for the user's face image "
+"in <filename>~/.face</filename>. If not found, it will try <filename>~/.face."
+"icon</filename>. If still not found, it will use the value defined for "
+"\"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file."
+msgstr ""
+
+#: C/gdm.xml:438(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 "
+"fallback to a generic face image."
+msgstr ""
+
+#: C/gdm.xml:444(para)
+msgid ""
+"Please note that loading and scaling face icons located in remote user home "
+"directories can be a very time-consuming task. Since it not practical to "
+"load images over NIS or NFS, GDM does not attempt to load face images from "
+"remote home directories."
+msgstr ""
+
+#: C/gdm.xml:451(para)
+msgid ""
+"When the browser is turned on, valid usernames on the computer are exposed "
+"for everyone to see. If XDMCP is enabled, then the usernames are exposed to "
+"remote users. This, of course, limits security somewhat since a malicious "
+"user does not need to guess valid usernames. In some very restrictive "
+"environments the face browser may not be appropriate."
+msgstr ""
+
+#: C/gdm.xml:463(title)
+msgid "XDMCP"
+msgstr "XDMCP"
+
+#. <para>
+#.         TODO - What XDMCP features actually work?   I know that the
+#.                chooser is missing.
+#. </para>
+#: C/gdm.xml:472(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 "
+"turned off, but can be enabled if desired. If GDM is built with TCP Wrapper "
+"support, then the daemon will only grant access to hosts specified in the "
+"GDM service section in the TCP Wrappers configuration file."
+msgstr ""
+
+#: C/gdm.xml:481(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 "
+"timeouts, etc. can be fine tuned. The default configuration should work "
+"reasonably on most systems."
+msgstr ""
+
+#: C/gdm.xml:488(para)
+msgid ""
+"GDM by default listens for XDMCP requests on the normal UDP port used for "
+"XDMCP, port 177, and will respond to QUERY and BROADCAST_QUERY requests by "
+"sending a WILLING packet to the originator."
+msgstr ""
+
+#: C/gdm.xml:494(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 "
+"forward subsequent requests to the chosen manager. GDM also supports an "
+"extension to the protocol which will make it forget the redirection once the "
+"user's connection succeeds. This extension is only supported if both daemons "
+"are GDM. It is transparent and will be ignored by XDM or other daemons that "
+"implement XDMCP."
+msgstr ""
+
+#: C/gdm.xml:504(para)
+msgid ""
+"If XDMCP seems to not be working, make sure that all machines are specified "
+"in <filename>/etc/hosts</filename>."
+msgstr ""
+
+#: C/gdm.xml:509(para)
+msgid ""
+"Refer to the \"Security\" section for information about security concerns "
+"when using XDMCP."
+msgstr ""
+
+#: C/gdm.xml:516(title)
+msgid "Logging"
+msgstr "Rexistro de actividade"
+
+#: C/gdm.xml:518(para)
+msgid ""
+"GDM uses syslog to log errors and status. It can also log debugging "
+"information, which can be useful for tracking down problems if GDM is not "
+"working properly. Debug output can be enabled by setting the debug/Enable "
+"key to \"true\" in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file."
+msgstr ""
+
+#: C/gdm.xml:526(para)
+msgid ""
+"Output from the various Xservers is stored in the GDM log directory, which "
+"is normally <filename>&lt;var&gt;/log/gdm/</filename>. Any Xserver messages "
+"are saved to a file associated with the display value, <filename>&lt;"
+"display&gt;.log</filename>."
+msgstr ""
+
+#: C/gdm.xml:533(para)
+msgid ""
+"The session output is piped through the GDM daemon to the <filename>~/."
+"xsession-errors</filename> file. The file is overwritten on each login, so "
+"logging out and logging back into the same user via GDM will cause any "
+"messages from the previous session to be lost."
+msgstr ""
+
+#: C/gdm.xml:540(para)
+msgid ""
+"Note that if GDM can not create this file for some reason, then a fallback "
+"file will be created named <filename>~/.xsession-errors.XXXXXXXX</filename> "
+"where the <filename>XXXXXXXX</filename> are some random characters."
+msgstr ""
+
+#: C/gdm.xml:548(title)
+msgid "Fast User Switching"
+msgstr "Cambio rápido de usuarios"
+
+#: C/gdm.xml:550(para)
+msgid ""
+"GDM allows multiple users to be logged in at the same time. After one user "
+"is logged in, additional users can log in via the User Switcher on the GNOME "
+"Panel, or from the \"Switch User\" button in Lock Screen dialog of GNOME "
+"Screensaver. The active session can be changed back and forth using the same "
+"mechanism. Note that some distributions may not add the User Switcher to the "
+"default panel configuration. It can be added using the panel context menu."
+msgstr ""
+
+#: C/gdm.xml:559(para)
+msgid ""
+"Note this feature is available on systems that support Virtual Terminals. "
+"This feature will not function if Virtual Terminals is not available."
+msgstr ""
+
+#: C/gdm.xml:570(title)
+msgid "Security"
+msgstr "Seguranza"
+
+#: C/gdm.xml:573(title)
+msgid "The GDM User And Group"
+msgstr ""
+
+#: C/gdm.xml:575(para)
+msgid ""
+"For security reasons a dedicated user and group id are recommended for "
+"proper operation. This user and group are normally \"gdm\" on most systems, "
+"but can be configured to any user or group. All GDM GUI programs are run as "
+"this user, so that the programs which interact with the user are run in a "
+"sandbox. This user and group should have limited privilege."
+msgstr ""
+
+#: C/gdm.xml:584(para)
+msgid ""
+"The only special privilege the \"gdm\" user requires is the ability to read "
+"and write Xauth files to the <filename>&lt;var&gt;/run/gdm</filename> "
+"directory. The <filename>&lt;var&gt;/run/gdm</filename> directory should "
+"have root:gdm ownership and 1777 permissions."
+msgstr ""
+
+#: C/gdm.xml:592(para)
+msgid ""
+"You should not, under any circumstances, configure the GDM user/group to a "
+"user which a user could easily gain access to, such as the user "
+"<filename>nobody</filename>. Any user who gains access to an Xauth key can "
+"snoop on and control running GUI programs running in the associated session "
+"or perform a denial-of-service attack on it. It is important to ensure that "
+"the system is configured properly so that only the \"gdm\" user has access "
+"to these files and that it is not easy to login to this account. For "
+"example, the account should be setup to not have a password or allow non-"
+"root users to login to the account."
+msgstr ""
+
+#: C/gdm.xml:605(para)
+msgid ""
+"The GDM greeter configuration is stored in GConf. To allow the GDM user to "
+"be able to write configuration, it is necessary for the \"gdm\" user to have "
+"a writable $HOME directory. Users may configure the default GConf "
+"configuration as desired to avoid the need to provide the \"gdm\" user with "
+"a writable $HOME directory. However, some features of GDM may be disabled if "
+"it is unable to write state information to GConf configuration."
+msgstr ""
+
+#: C/gdm.xml:617(title)
+msgid "PAM"
+msgstr "PAM"
+
+#: C/gdm.xml:619(para)
+msgid ""
+"GDM uses PAM for login authentication. PAM stands for Pluggable "
+"Authentication Module, and is used by most programs that request "
+"authentication on your computer. It allows the administrator to configure "
+"specific authentication behavior for different login programs (such as ssh, "
+"login GUI, screensaver, etc.)"
+msgstr ""
+
+#: C/gdm.xml:627(para)
+msgid ""
+"PAM is complicated and highly configurable, and this documentation does not "
+"intend to explain this in detail. Instead, it is intended to give an "
+"overview of how PAM configuration relates with GDM, how PAM is commonly "
+"configured with GDM, and known issues. It is expected that a person needing "
+"to do PAM configuration would need to do further reading of PAM "
+"documentation to understand how to configure PAM and to understand terms "
+"used in this section."
+msgstr ""
+
+#: C/gdm.xml:637(para)
+msgid ""
+"PAM configuration has different, but similar, interfaces on different "
+"Operating Systems, so check the <ulink type=\"help\" url=\"man:pam.d\">pam."
+"d</ulink> or <ulink type=\"help\" url=\"man:pam.conf\">pam.conf</ulink> man "
+"page for details. Be sure you read the PAM documentation and are comfortable "
+"with the security implications of any changes you intend to make to your "
+"configuration."
+msgstr ""
+
+#: C/gdm.xml:647(para)
+msgid ""
+"Note that, by default, GDM uses the \"gdm\" PAM service name for normal "
+"login and the \"gdm-autologin\" PAM service name for automatic login. These "
+"services may not be defined in your pam.d or pam.conf configured file. If "
+"there is no entry, then GDM will use the default PAM behavior. On most "
+"systems this should work fine. However, the automatic login feature may not "
+"work if the gdm-autologin service is not defined."
+msgstr ""
+
+#: C/gdm.xml:657(para)
+msgid ""
+"The <filename>PostLogin</filename> script is run before pam_open_session is "
+"called, and the <filename>PreSession</filename> script is called after. This "
+"allows the system administrator to add any scripting to the login process "
+"either before or after PAM initializes the session."
+msgstr ""
+
+#: C/gdm.xml:665(para)
+msgid ""
+"If you wish to make GDM work with other types of authentication mechanisms "
+"(such as a fingerprint or SmartCard reader), then you should implement this "
+"by using a PAM service module for the desired authentication type rather "
+"than by trying to modify the GDM code directly. Refer to the PAM "
+"documentation on your system. How to do this is frequently discussed on the "
+"<address><email>gdm-list@gnome.org</email></address> mail list, so you can "
+"refer to the list archives for more information."
+msgstr ""
+
+#: C/gdm.xml:676(para)
+msgid ""
+"PAM does have some limitations regarding being able to work with multiple "
+"types of authentication at the same time, like supporting the ability to "
+"accept either SmartCard and the ability to type the username and password "
+"into the login program. There are techniques that are used to make this "
+"work, and it is best to research how this problem is commonly solved when "
+"setting up such a configuration."
+msgstr ""
+
+#: C/gdm.xml:685(para)
+msgid ""
+"If automatic login does not work on a system, check to see if the \"gdm-"
+"autologin\" PAM stack is defined in the PAM configuration. For this to work, "
+"it is necessary to use a PAM module that simply does no authentication, or "
+"which simply returns PAM_SUCCESS from all of its public interfaces. Assuming "
+"your system has a pam_allow.so PAM module which does this, a PAM "
+"configuration to enable \"gdm-autologin\" would look like this:"
+msgstr ""
+
+#: C/gdm.xml:695(screen)
+#, no-wrap
+msgid ""
+"\n"
+"       gdm-autologin auth  required    pam_unix_cred.so.1\n"
+"       gdm-autologin auth  sufficient  pam_allow.so.1\n"
+"       gdm-autologin account  sufficient  pam_allow.so.1\n"
+"       gdm-autologin session  sufficient  pam_allow.so.1\n"
+"       gdm-autologin password  sufficient  pam_allow.so.1\n"
+msgstr ""
+"\n"
+"       gdm-autologin auth  required    pam_unix_cred.so.1\n"
+"       gdm-autologin auth  sufficient  pam_allow.so.1\n"
+"       gdm-autologin account  sufficient  pam_allow.so.1\n"
+"       gdm-autologin session  sufficient  pam_allow.so.1\n"
+"       gdm-autologin password  sufficient  pam_allow.so.1\n"
+
+#: C/gdm.xml:703(para)
+msgid ""
+"The above setup will cause no lastlog entry to be generated. If a lastlog "
+"entry is desired, then use the following for the session:"
+msgstr ""
+
+#: C/gdm.xml:708(screen)
+#, no-wrap
+msgid ""
+"\n"
+"       gdm-autologin session required pam_unix_session.so.1\n"
+msgstr ""
+"\n"
+"       gdm-autologin session required pam_unix_session.so.1\n"
+
+#: C/gdm.xml:712(para)
+msgid ""
+"If the computer is used by several people, which makes automatic login "
+"unsuitable, you may want to allow some users to log in without entering "
+"their password. This feature can be enabled as a per-user option in the "
+"users-admin tool from the gnome-system-tools; it is achieved by checking "
+"that the user is member a Unix group called \"nopasswdlogin\" before asking "
+"for a password. For this to work, the PAM configuration file for the \"gdm\" "
+"service must include a line such as:"
+msgstr ""
+
+#: C/gdm.xml:723(screen)
+#, no-wrap
+msgid ""
+"\n"
+"      gdm auth  sufficient  pam_succeed_if.so  user ingroup nopasswdlogin\n"
+msgstr ""
+"\n"
+"      gdm auth  sufficient  pam_succeed_if.so  user ingroup nopasswdlogin\n"
+
+#: C/gdm.xml:730(title)
+msgid "utmp and wtmp"
+msgstr ""
+
+#: C/gdm.xml:732(para)
+msgid ""
+"GDM generates utmp and wtmp User Accounting Database entries upon session "
+"login and logout. The utmp database contains user access and accounting "
+"information that is accessed by commands such as <command>finger</command>, "
+"<command>last</command>, <command>login</command>, and <command>who</"
+"command>. The wtmp database contains the history of user access and "
+"accounting information for the utmp database. Refer to the <ulink type=\"help"
+"\" url=\"man:utmp\">utmp</ulink> and <ulink type=\"help\" url=\"man:wtmp"
+"\">wtmp</ulink> man pages on your system for more information."
+msgstr ""
+
+#: C/gdm.xml:747(title)
+msgid "Xserver Authentication Scheme"
+msgstr "Esquema de autenticación do servidor X"
+
+#: C/gdm.xml:749(para)
+msgid ""
+"Xserver authorization files are stored in a newly created subdirectory of "
+"<filename>&lt;var&gt;/run/gdm</filename> at start up. These files are used "
+"to store and share a \"password\" between X clients and the Xserver. This "
+"\"password\" is unique for each session logged in, so users from one session "
+"can't snoop on users from another."
+msgstr ""
+
+#: C/gdm.xml:757(para)
+msgid ""
+"GDM only supports the MIT-MAGIC-COOKIE-1 Xserver 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 Xserver 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. In most cases, ssh -Y should be preferred over GDM's XDMCP features."
+msgstr ""
+
+#: C/gdm.xml:774(title)
+msgid "XDMCP Security"
+msgstr "Seguranza XDMCP"
+
+#: C/gdm.xml:776(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:782(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. This type of set up should never use an unmanaged hub or "
+"other sniffable network."
+msgstr ""
+
+#: C/gdm.xml:795(title)
+msgid "XDMCP Access Control"
+msgstr "Control de acceso XDMCP"
+
+#: C/gdm.xml:797(para)
+msgid ""
+"XDMCP access control is done using TCP wrappers. It is possible to compile "
+"GDM without TCP wrapper support, so this feature may not be supported on "
+"some Operating Systems."
+msgstr ""
+
+#: C/gdm.xml:803(para)
+msgid ""
+"You should use the daemon name <command>gdm</command> in the <filename>&lt;"
+"etc&gt;/hosts.allow</filename> and <filename>&lt;etc&gt;/hosts.deny</"
+"filename> files. For example to deny computers from <filename>.evil.domain</"
+"filename> from logging in, then add"
+msgstr ""
+
+#: C/gdm.xml:810(screen)
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .evil.domain\n"
+msgstr ""
+"\n"
+"gdm: .dominio.maligno\n"
+
+#: C/gdm.xml:813(para)
+msgid ""
+"to <filename>&lt;etc&gt;/hosts.deny</filename>. You may also need to add"
+msgstr ""
+
+#: C/gdm.xml:817(screen)
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .your.domain\n"
+msgstr ""
+"\n"
+"gdm: .o.seu.dominio\n"
+
+#: C/gdm.xml:820(para)
+msgid ""
+"to your <filename>&lt;etc&gt;/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 ""
+
+#: C/gdm.xml:829(title)
+msgid "Firewall Security"
+msgstr "Seguranza con devasa"
+
+#: C/gdm.xml:831(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 really needed. GDM guards "
+"against 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 do a "
+"denial of service attack via XDMCP than attacking a webserver."
+msgstr ""
+
+#: C/gdm.xml:842(para)
+msgid ""
+"It is also wise to block all of the Xserver ports. These are TCP ports 6000+ "
+"(one for each display number) on your firewall. Note that GDM will use "
+"display numbers 20 and higher for flexible on-demand servers."
+msgstr ""
+
+#: C/gdm.xml:849(para)
+msgid ""
+"X is not a very safe protocol when using it over the Internet, and XDMCP is "
+"even less safe."
+msgstr ""
+
+#: C/gdm.xml:856(title)
+msgid "PolicyKit"
+msgstr "PolicyKit"
+
+#. <para>
+#.         TODO - Should we say more?
+#. </para>
+#: C/gdm.xml:864(para)
+msgid ""
+"GDM may be configured to use PolicyKit to allow the system administrator to "
+"control whether the login screen should provide the shutdown and restart "
+"buttons on the greeter screen."
+msgstr ""
+
+#: C/gdm.xml:870(para)
+msgid ""
+"These buttons are controlled by the <filename>org.freedesktop.consolekit."
+"system.stop-multiple-users</filename> and <filename>org.freedesktop."
+"consolekit.system.restart-multiple-users</filename> actions respectively. "
+"Policy for these actions can be set up using the polkit-gnome-authorization "
+"tool, or the polkit-auth command line program."
+msgstr ""
+
+#: C/gdm.xml:882(title)
+msgid "RBAC (Role Based Access Control)"
+msgstr "RBAC (Control de acceso baseado en rol)"
+
+#: C/gdm.xml:884(para)
+msgid ""
+"GDM may be configured to use RBAC instead of PolicyKit. In this case the "
+"RBAC configuration is used to control whether the login screen should "
+"provide the shutdown and restart buttons on the greeter screen."
+msgstr ""
+
+#: C/gdm.xml:890(para)
+msgid ""
+"For example, on Oracle Solaris, the \"solaris.system.shutdown\" "
+"authorization is used to control this. Simply modify the <filename>/etc/"
+"user_attr</filename> file so that the \"gdm\" user has this authorization."
+msgstr ""
+
+#: C/gdm.xml:903(title)
+msgid "Support for ConsoleKit"
+msgstr "Compatibilidade para ConsoleKit"
+
+#. <para>
+#.     TODO - Should we update these docs?  Probably should mention any 
+#.            configuration that users may want to do for using it with GDM?
+#.            If so, perhaps this section should be moved to a subsection of
+#.            the "Configure" section?
+#. </para>
+#: C/gdm.xml:914(para)
+msgid ""
+"GDM includes support for publishing user login information with the user and "
+"login session accounting framework known as ConsoleKit. ConsoleKit is able "
+"to keep track of all the users currently logged in. In this respect, it can "
+"be used as a replacement for the utmp or utmpx files that are available on "
+"most Unix-like Operating Systems."
+msgstr ""
+
+#: C/gdm.xml:922(para)
+msgid ""
+"When GDM is about to create a new login process for a user it will call a "
+"privileged method of ConsoleKit in order to open a new session for this "
+"user. At this time GDM also provides ConsoleKit with information about this "
+"user session such as: the user ID, the X11 Display name that will be "
+"associated with the session, the host-name from which the session originates "
+"(useful in the case of an XDMCP session), whether or not this session is "
+"attached, etc. As the entity that initiates the user process, GDM is in a "
+"unique position to know about the user session and to be trusted to provide "
+"these bits of information. The use of this privileged method is restricted "
+"by the use of the D-Bus system message bus security policy."
+msgstr ""
+
+#: C/gdm.xml:936(para)
+msgid ""
+"In case a user with an existing session has authenticated at GDM and "
+"requests to resume that existing session, GDM calls a privileged method of "
+"ConsoleKit to unlock that session. The exact details of what happens when "
+"the session receives this unlock signal are undefined and session-specific. "
+"However, most sessions will unlock a screensaver in response."
+msgstr ""
+
+#: C/gdm.xml:945(para)
+msgid ""
+"When the user chooses to log out, or if GDM or the session quit unexpectedly "
+"the user session will be unregistered from ConsoleKit."
+msgstr ""
+
+#: C/gdm.xml:954(title)
+msgid "Configuration"
+msgstr "Configuración"
+
+#: C/gdm.xml:956(para)
+msgid ""
+"GDM has a number of configuration interfaces. These include scripting "
+"integration points, daemon configuration, greeter configuration, general "
+"session settings, integration with gnome-settings-daemon configuration, and "
+"session configuration. These types of integration are described in detail "
+"below."
+msgstr ""
+
+#: C/gdm.xml:965(title)
+msgid "Scripting Integration Points"
+msgstr "Puntos de integración de scripts"
+
+#: C/gdm.xml:967(para)
+msgid ""
+"The GDM script integration points can be found in the <filename>&lt;etc&gt;/"
+"gdm/</filename> directory:"
+msgstr ""
+
+#: C/gdm.xml:972(screen)
+#, no-wrap
+msgid ""
+"\n"
+"Xsession\n"
+"Init/\n"
+"PostLogin/\n"
+"PreSession/\n"
+"PostSession/\n"
+msgstr ""
+"\n"
+"Xsession\n"
+"Init/\n"
+"PostLogin/\n"
+"PreSession/\n"
+"PostSession/\n"
+
+#: C/gdm.xml:980(para)
+msgid ""
+"The <filename>Init</filename>, <filename>PostLogin</filename>, "
+"<filename>PreSession</filename>, and <filename>PostSession</filename> "
+"scripts all work as described below."
+msgstr ""
+
+#: C/gdm.xml:986(para)
+msgid ""
+"For each type of script, the default one which will be executed is called "
+"\"Default\" and is stored in a directory associated with the script type. So "
+"the default <filename>Init</filename> script is <filename>&lt;etc&gt;/gdm/"
+"Init/Default</filename>. A per-display script can be provided, and if it "
+"exists it will be run instead of the default script. Such scripts are stored "
+"in the same directory as the default script and have the same name as the "
+"Xserver DISPLAY value for that display. For example, if the <filename>&lt;"
+"Init&gt;/:0</filename> script exists, it will be run for DISPLAY \":0\"."
+msgstr ""
+
+#: C/gdm.xml:998(para)
+msgid ""
+"All of these scripts are run with root privilege and return 0 if run "
+"successfully, and a non-zero return code if there was any failure that "
+"should cause the login session to be aborted. Also note that GDM will block "
+"until the scripts finish, so if any of these scripts hang, this will cause "
+"the login process to also hang."
+msgstr ""
+
+#: C/gdm.xml:1006(para)
+msgid ""
+"When the Xserver for the login GUI has been successfully started, but before "
+"the login GUI is actually displayed, GDM will run the <filename>Init</"
+"filename> script. This script is useful for starting programs that should be "
+"run while the login screen is showing, or for doing any special "
+"initialization if required."
+msgstr ""
+
+#: C/gdm.xml:1014(para)
+msgid ""
+"After the user has been successfully authenticated GDM will run the "
+"<filename>PostLogin</filename> script. This is done before any session setup "
+"has been done, including before the pam_open_session call. This script is "
+"useful for doing any session initialization that needs to happen before the "
+"session starts. For example, you might setup the user's $HOME directory if "
+"needed."
+msgstr ""
+
+#: C/gdm.xml:1023(para)
+msgid ""
+"After the user session has been initialized, GDM will run the "
+"<filename>PreSession</filename> script. This script is useful for doing any "
+"session initialization that needs to happen after the session has been "
+"initialized. It can be used for session management or accounting, for "
+"example."
+msgstr ""
+
+#: C/gdm.xml:1031(para)
+msgid ""
+"When a user terminates their session, GDM will run the "
+"<filename>PostSession</filename> script. Note that the Xserver will have "
+"been stopped by the time this script is run, so it should not be accessed."
+msgstr ""
+
+#: C/gdm.xml:1038(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 ""
+
+#: C/gdm.xml:1045(para)
+msgid ""
+"All of the above scripts will set the <filename>$RUNNING_UNDER_GDM</"
+"filename> environment variable to <filename>yes</filename>. If the scripts "
+"are also shared with other display managers, this allows you to identify "
+"when GDM is calling these scripts, so you can run specific code when GDM is "
+"used."
+msgstr ""
+
+#: C/gdm.xml:1055(title)
+msgid "Autostart Configuration"
+msgstr "Configuración automática ao inicio"
+
+#: C/gdm.xml:1057(para)
+msgid ""
+"The <filename>&lt;share&gt;/gdm/autostart/LoginWindow</filename> directory "
+"contains files in the format specified by the \"FreeDesktop.org Desktop "
+"Application Autostart Specification\". Standard features in the "
+"specification may be used to specify programs that should auto-restart or "
+"only be launched if a GConf configuration value is set, etc."
+msgstr ""
+
+#: C/gdm.xml:1066(para)
+msgid ""
+"Any <filename>.desktop</filename> files in this directory will cause the "
+"associated program to automatically start with the login GUI greeter. By "
+"default, GDM is shipped with files which will autostart the gdm-simple-"
+"greeter login GUI greeter itself, the gnome-power-manager application, the "
+"gnome-settings-daemon, and the metacity window manager. These programs are "
+"needed for the greeter program to work. In addition, desktop files are "
+"provided for starting various AT programs if the configuration values "
+"specified in the Accessibility Configuration section below are set."
+msgstr ""
+
+#: C/gdm.xml:1080(title)
+msgid "Xsession Script"
+msgstr "Script Xsession"
+
+#: C/gdm.xml:1082(para)
+msgid ""
+"There is also an <filename>Xsession</filename> script located at "
+"<filename>&lt;etc&gt;/gdm/Xsession</filename> which is called between the "
+"<filename>PreSession</filename> and the <filename>PostSession</filename> "
+"scripts. This script does not support per-display like the other scripts. "
+"This script is used for actually starting the user session. This script is "
+"run as the user, and it will run whatever session was specified by the "
+"Desktop session file the user selected to start."
+msgstr ""
+
+#: C/gdm.xml:1095(title)
+msgid "Daemon Configuration"
+msgstr "Configuración do «daemon»"
+
+#: C/gdm.xml:1097(para)
+msgid ""
+"The GDM daemon is configured using the <filename>&lt;etc&gt;/gdm/custom."
+"conf</filename> file. Default values are stored in GConf in the "
+"<filename>gdm.schemas</filename> file. It is recommended that end-users "
+"modify the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file because the "
+"schemas file may be overwritten when the user updates their system to have a "
+"newer version of GDM."
+msgstr ""
+
+#: C/gdm.xml:1107(para)
+msgid ""
+"Note that older versions of GDM supported additional configuration options "
+"which are no longer supported in the latest versions of GDM."
+msgstr ""
+
+#: C/gdm.xml:1112(para)
+msgid ""
+"The <filename>&lt;etc&gt;/gdm/custom.conf</filename> file is in the "
+"<filename>keyfile</filename> format. Keywords in brackets define group "
+"sections, strings before an equal sign (=) are keys and the data after equal "
+"sign represents their value. Empty lines or lines starting with the hash "
+"mark (#) are ignored."
+msgstr ""
+
+#: C/gdm.xml:1120(para)
+msgid ""
+"The file <filename>&lt;etc&gt;/gdm/custom.conf</filename> supports the "
+"\"[daemon]\", \"[security]\", and \"[xdmcp]\" group sections. Within each "
+"group, there are particular key/value pairs that can be specified to modify "
+"how GDM behaves. For example, to enable timed login and specify the timed "
+"login user to be a user named \"you\", you would modify the file so it "
+"contains the following lines:"
+msgstr ""
+
+#: C/gdm.xml:1130(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[daemon]\n"
+"TimedLoginEnable=true\n"
+"TimedLogin=you\n"
+msgstr ""
+"\n"
+"[daemon]\n"
+"TimedLoginEnable=true\n"
+"TimedLogin=you\n"
+
+#: C/gdm.xml:1136(para)
+msgid "A full list of supported configuration keys follow:"
+msgstr ""
+
+#: C/gdm.xml:1141(title)
+msgid "[chooser]"
+msgstr "[chooser]"
+
+#: C/gdm.xml:1145(term)
+msgid "Multicast"
+msgstr "Multicast"
+
+#: C/gdm.xml:1147(synopsis)
+#, no-wrap
+msgid "Multicast=false"
+msgstr "Multicast=false"
+
+#: C/gdm.xml:1148(para)
+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."
+msgstr ""
+
+#: C/gdm.xml:1157(term)
+msgid "MulticastAddr"
+msgstr "MulticastAddr"
+
+#: C/gdm.xml:1159(synopsis)
+#, no-wrap
+msgid "MulticastAddr=ff02::1"
+msgstr "MulticastAddr=ff02::1"
+
+#: C/gdm.xml:1160(para)
+msgid "This is the Link-local multicast address."
+msgstr ""
+
+#: C/gdm.xml:1169(title)
+msgid "[daemon]"
+msgstr "[daemon]"
+
+#: C/gdm.xml:1172(term)
+msgid "TimedLoginEnable"
+msgstr "TimedLoginEnable"
+
+#: C/gdm.xml:1174(synopsis)
+#, no-wrap
+msgid "TimedLoginEnable=false"
+msgstr "TimedLoginEnable=false"
+
+#: C/gdm.xml:1175(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. Refer to the \"Security-&gt;PAM\" section of the manual for "
+"more information, or for help if this feature does not seem to work."
+msgstr ""
+
+#: C/gdm.xml:1197(term)
+msgid "TimedLogin"
+msgstr "TimedLogin"
+
+#: C/gdm.xml:1199(synopsis)
+#, no-wrap
+msgid "TimedLogin="
+msgstr "TimedLogin="
+
+#: C/gdm.xml:1200(para)
+msgid ""
+"This is the user that should be logged in after a specified number of "
+"seconds of inactivity."
+msgstr ""
+
+#: C/gdm.xml:1204(para) C/gdm.xml:1248(para)
+msgid ""
+"If the value ends with a vertical bar | (the pipe symbol), then GDM will "
+"execute the program specified and use whatever value is returned on standard "
+"out from the program as the user. The program is run with the DISPLAY "
+"environment variable set so that it is possible to specify the user in a per-"
+"display fashion. For example if the value is \"/usr/bin/getloginuser|\", "
+"then the program \"/usr/bin/getloginuser\" will be run to get the user value."
+msgstr ""
+
+#: C/gdm.xml:1218(term)
+msgid "TimedLoginDelay"
+msgstr "TimedLoginDelay"
+
+#: C/gdm.xml:1220(synopsis)
+#, no-wrap
+msgid "TimedLoginDelay=30"
+msgstr "TimedLoginDelay=30"
+
+#: C/gdm.xml:1221(para)
+msgid ""
+"Delay in seconds before the <filename>TimedLogin</filename> user will be "
+"logged in."
+msgstr ""
+
+#: C/gdm.xml:1229(term)
+msgid "AutomaticLoginEnable"
+msgstr "AutomaticLoginEnable"
+
+#: C/gdm.xml:1231(synopsis)
+#, no-wrap
+msgid "AutomaticLoginEnable=false"
+msgstr "AutomaticLoginEnable=false"
+
+#: C/gdm.xml:1232(para)
+msgid ""
+"If true, the user given in <filename>AutomaticLogin</filename> should be "
+"logged in immediately. This feature is like timed login with a delay of 0 "
+"seconds."
+msgstr ""
+
+#: C/gdm.xml:1241(term)
+msgid "AutomaticLogin"
+msgstr "AutomaticLogin"
+
+#: C/gdm.xml:1243(synopsis)
+#, no-wrap
+msgid "AutomaticLogin="
+msgstr "AutomaticLogin="
+
+#: C/gdm.xml:1244(para)
+msgid ""
+"This is the user that should be logged in immediately if "
+"<filename>AutomaticLoginEnable</filename> is true."
+msgstr ""
+
+#: C/gdm.xml:1262(term)
+msgid "User"
+msgstr "User"
+
+#: C/gdm.xml:1264(synopsis)
+#, no-wrap
+msgid "User=gdm"
+msgstr "User=gdm"
+
+#: C/gdm.xml:1265(para)
+msgid ""
+"The username under which the greeter and other GUI programs are run. Refer "
+"to the <filename>Group</filename> configuration key and to the \"Security-"
+"&gt;GDM User And Group\" section of this document for more information."
+msgstr ""
+
+#: C/gdm.xml:1275(term)
+msgid "Group"
+msgstr "Group"
+
+#: C/gdm.xml:1277(synopsis)
+#, no-wrap
+msgid "Group=gdm"
+msgstr "Group=gdm"
+
+#: C/gdm.xml:1278(para)
+msgid ""
+"The group name under which the greeter and other GUI programs are run. Refer "
+"to the <filename>User</filename> configuration key and to the \"Security-&gt;"
+"GDM User And Group\" section of this document for more information."
+msgstr ""
+
+#: C/gdm.xml:1290(title)
+msgid "Debug Options"
+msgstr "Opcións de depuración"
+
+#: C/gdm.xml:1293(title)
+msgid "[debug]"
+msgstr "[debug]"
+
+#: C/gdm.xml:1296(term) C/gdm.xml:1427(term)
+msgid "Enable"
+msgstr "Enable"
+
+#: C/gdm.xml:1298(synopsis) C/gdm.xml:1429(synopsis)
+#, no-wrap
+msgid "Enable=false"
+msgstr "Enable=false"
+
+#: C/gdm.xml:1299(para)
+msgid ""
+"To enable debugging, set the debug/Enable key to \"true\" in the "
+"<filename>&lt;etc&gt;/gdm/custom.conf</filename> file and restart GDM. Then "
+"debug output will be sent to the system log file (<filename>&lt;var&gt;/log/"
+"messages</filename> or <filename>&lt;var&gt;/adm/messages</filename> "
+"depending on your Operating System)."
+msgstr ""
+
+#: C/gdm.xml:1314(title)
+msgid "Greeter Options"
+msgstr "Opcións da interface"
+
+#: C/gdm.xml:1317(title)
+msgid "[greeter]"
+msgstr "[greeter]"
+
+#: C/gdm.xml:1320(term)
+msgid "IncludeAll"
+msgstr "IncludeAll"
+
+#: C/gdm.xml:1322(synopsis)
+#, no-wrap
+msgid "IncludeAll=true"
+msgstr "IncludeAll=true"
+
+#: C/gdm.xml:1323(para)
+msgid ""
+"If true, then the face browser will show all users on the local machine. If "
+"false, the face browser will only show users who have recently logged in."
+msgstr ""
+
+#: C/gdm.xml:1329(para)
+msgid ""
+"When this key is true, GDM will call fgetpwent() to get a list of local "
+"users on the system. Any users with a user id less than 500 (or 100 if "
+"running on Oracle Solaris) are filtered out. The Face Browser also will "
+"display any users that have previously logged in on the system (for example "
+"NIS/LDAP users). It gets this list via calling the <command>ck-history</"
+"command> ConsoleKit interface. It will also filter out any users which do "
+"not have a valid shell (valid shells are any shell that getusershell() "
+"returns - /sbin/nologin or /bin/false are considered invalid shells even if "
+"getusershell() returns them)."
+msgstr ""
+
+#: C/gdm.xml:1343(para)
+msgid ""
+"If false, then GDM more simply only displays users that have previously "
+"logged in on the system (local or NIS/LDAP users) by calling the <command>ck-"
+"history</command> ConsoleKit interface."
+msgstr ""
+
+#: C/gdm.xml:1352(term)
+msgid "Include"
+msgstr "Include"
+
+#: C/gdm.xml:1354(synopsis)
+#, no-wrap
+msgid "Include="
+msgstr "Include="
+
+#: C/gdm.xml:1355(para)
+msgid ""
+"Set to a list of users to always include in the Face Browser. This value is "
+"set to a list of users separated by commas. By default, the value is empty."
+msgstr ""
+
+#: C/gdm.xml:1364(term)
+msgid "Exclude"
+msgstr "Exclude"
+
+#: C/gdm.xml:1366(synopsis)
+#, no-wrap
+msgid "Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap"
+msgstr "Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap"
+
+#: C/gdm.xml:1367(para)
+msgid ""
+"Set to a list of users to always exclude in the Face Browser. This value is "
+"set to a list of users separated by commas. Note that the setting in the "
+"<filename>custom.conf</filename> overrides the default value, so if you wish "
+"to add additional users to the list, then you need to set the value to the "
+"default value with additional users appended to the list."
+msgstr ""
+
+#: C/gdm.xml:1381(title)
+msgid "Security Options"
+msgstr "Opcións de seguranza"
+
+#: C/gdm.xml:1384(title)
+msgid "[security]"
+msgstr "[security]"
+
+#: C/gdm.xml:1387(term)
+msgid "DisallowTCP"
+msgstr "DisallowTCP"
+
+#: C/gdm.xml:1389(synopsis)
+#, no-wrap
+msgid "DisallowTCP=true"
+msgstr "DisallowTCP=true"
+
+#: C/gdm.xml:1390(para)
+msgid ""
+"If true, then always append <filename>-nolisten tcp</filename> to the "
+"command line when starting attached Xservers, thus disallowing TCP "
+"connection. This is a more secure configuration if you are not using remote "
+"connections."
+msgstr ""
+
+#: C/gdm.xml:1402(title)
+msgid "XDCMP Support"
+msgstr "Compatibilidade XDMCP"
+
+#: C/gdm.xml:1405(title)
+msgid "[xdmcp]"
+msgstr "[xdmcp]"
+
+#: C/gdm.xml:1408(term)
+msgid "DisplaysPerHost"
+msgstr "DisplaysPerHost"
+
+#: C/gdm.xml:1410(synopsis)
+#, no-wrap
+msgid "DisplaysPerHost=1"
+msgstr "DisplaysPerHost=1"
+
+#: C/gdm.xml:1411(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 this "
+"value."
+msgstr ""
+
+#: C/gdm.xml:1418(para)
+msgid ""
+"Note that the number of attached DISPLAYS allowed is not limited. Only "
+"remote connections via XDMCP are limited by this configuration option."
+msgstr ""
+
+#: C/gdm.xml:1430(para)
+msgid ""
+"Setting this to true enables XDMCP support allowing remote displays/X "
+"terminals to be managed by GDM."
+msgstr ""
+
+#: C/gdm.xml:1435(para)
+msgid ""
+"<filename>gdm</filename> listens for requests on UDP port 177. See the Port "
+"option for more information."
+msgstr ""
+
+#: C/gdm.xml:1440(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 ""
+
+#: C/gdm.xml:1446(para)
+msgid ""
+"You should add <screen>\n"
+"gdm:.my.domain\n"
+"</screen> to your <filename>&lt;etc&gt;/hosts.allow</filename>, depending on "
+"your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:"
+"hosts.allow\">hosts.allow</ulink> man page for details."
+msgstr ""
+
+#: C/gdm.xml:1457(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 ""
+
+#: C/gdm.xml:1466(term)
+msgid "HonorIndirect"
+msgstr "HonorIndirect"
+
+#: C/gdm.xml:1468(synopsis)
+#, no-wrap
+msgid "HonorIndirect=true"
+msgstr "HonorIndirect=true"
+
+#: C/gdm.xml:1469(para)
+msgid ""
+"Enables XDMCP INDIRECT choosing (i.e. remote execution of "
+"<filename>gdmchooser</filename>) for X-terminals which do not supply their "
+"own display browser."
+msgstr ""
+
+#: C/gdm.xml:1478(term)
+msgid "MaxPending"
+msgstr "MaxPending"
+
+#: C/gdm.xml:1480(synopsis)
+#, no-wrap
+msgid "MaxPending=4"
+msgstr "MaxPending=4"
+
+#: C/gdm.xml:1481(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:1487(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:1496(term)
+msgid "MaxSessions"
+msgstr "MaxSessions"
+
+#: C/gdm.xml:1498(synopsis)
+#, no-wrap
+msgid "MaxSessions=16"
+msgstr "MaxSessions=16"
+
+#: C/gdm.xml:1499(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:1508(term)
+msgid "MaxWait"
+msgstr "MaxWait"
+
+#: C/gdm.xml:1510(synopsis)
+#, no-wrap
+msgid "MaxWait=30"
+msgstr "MaxWait=30"
+
+#: C/gdm.xml:1511(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:1517(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:1522(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:1531(term)
+msgid "MaxWaitIndirect"
+msgstr "MaxWaitIndirect"
+
+#: C/gdm.xml:1533(synopsis)
+#, no-wrap
+msgid "MaxWaitIndirect=30"
+msgstr "MaxWaitIndirect=30"
+
+#: C/gdm.xml:1534(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 ""
+
+#: C/gdm.xml:1548(term)
+msgid "PingIntervalSeconds"
+msgstr "PingIntervalSeconds"
+
+#: C/gdm.xml:1550(synopsis)
+#, no-wrap
+msgid "PingIntervalSeconds=60"
+msgstr "PingIntervalSeconds=60"
+
+#: C/gdm.xml:1551(para)
+msgid ""
+"If the Xserver does not respond in the specified number of seconds, then the "
+"connection is stopped and the session ended. When this happens the slave "
+"daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied "
+"this setting by 2, so it may be necessary to increase the timeout if "
+"upgrading from GDM 2.20 and earlier to a newer version."
+msgstr ""
+
+#: C/gdm.xml:1560(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 than 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 ""
+
+#: C/gdm.xml:1573(term)
+msgid "Port"
+msgstr "Port"
+
+#: C/gdm.xml:1575(synopsis)
+#, no-wrap
+msgid "Port=177"
+msgstr "Port=177"
+
+#: C/gdm.xml:1576(para)
+msgid ""
+"The UDP port number <filename>gdm</filename> should listen to for XDMCP "
+"requests. Do not change this unless you know what you are doing."
+msgstr ""
+
+#: C/gdm.xml:1585(term)
+msgid "Willing"
+msgstr "Willing"
+
+#: C/gdm.xml:1587(synopsis)
+#, no-wrap
+msgid "Willing=&lt;etc&gt;/gdm/Xwilling"
+msgstr "Willing=&lt;etc&gt;/gdm/Xwilling"
+
+#: C/gdm.xml:1588(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 does not 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 ""
+
+#: C/gdm.xml:1607(title)
+msgid "Simple Greeter Configuration"
+msgstr "Configuración da interface simple"
+
+#: C/gdm.xml:1609(para)
+msgid ""
+"The GDM default greeter is called the simple Greeter and is configured via "
+"GConf. Default values are stored in GConf in the <filename>gdm-simple-"
+"greeter.schemas</filename> file. These defaults can be overridden if the "
+"\"gdm\" user has a writable $HOME directory to store GConf settings. These "
+"values can be edited using the <command>gconftool-2</command> or "
+"<command>gconf-editor</command> programs. The following configuration "
+"options are supported:"
+msgstr ""
+
+#: C/gdm.xml:1620(title)
+msgid "Greeter Configuration Keys"
+msgstr "Chaves de configuración da interface"
+
+#: C/gdm.xml:1623(term)
+msgid "/apps/gdm/simple-greeter/banner_message_enable"
+msgstr "/apps/gdm/simple-greeter/banner_message_enable"
+
+#: C/gdm.xml:1625(synopsis) C/gdm.xml:1646(synopsis) C/gdm.xml:1657(synopsis)
+#: C/gdm.xml:1722(synopsis) C/gdm.xml:1787(synopsis) C/gdm.xml:1798(synopsis)
+#: C/gdm.xml:1809(synopsis) C/gdm.xml:1820(synopsis)
+#, no-wrap
+msgid "false (boolean)"
+msgstr "false (booleano)"
+
+#: C/gdm.xml:1626(para)
+msgid "Controls whether the banner message text is displayed."
+msgstr "Controla se se mostra ou non o mensaxe de texto."
+
+#: C/gdm.xml:1633(term)
+msgid "/apps/gdm/simple-greeter/banner_message_text"
+msgstr "/apps/gdm/simple-greeter/banner_message_text"
+
+#: C/gdm.xml:1635(synopsis)
+#, no-wrap
+msgid "NULL (string)"
+msgstr "NULL (cadea)"
+
+#: C/gdm.xml:1636(para)
+msgid "Specifies the text banner message to show on the greeter window."
+msgstr ""
+
+#: C/gdm.xml:1644(term)
+msgid "/apps/gdm/simple-greeter/disable_restart_buttons"
+msgstr "/apps/gdm/simple-greeter/disable_restart_buttons"
+
+#: C/gdm.xml:1647(para)
+msgid "Controls whether to show the restart buttons in the login window."
+msgstr ""
+
+#: C/gdm.xml:1655(term)
+msgid "/apps/gdm/simple-greeter/disable_user_list"
+msgstr "/apps/gdm/simple-greeter/disable_user_list"
+
+#: C/gdm.xml:1658(para)
+msgid ""
+"If true, then the face browser with known users is not shown in the login "
+"window."
+msgstr ""
+
+#: C/gdm.xml:1666(term)
+msgid "/apps/gdm/simple-greeter/logo_icon_name"
+msgstr "/apps/gdm/simple-greeter/logo_icon_name"
+
+#: C/gdm.xml:1668(synopsis)
+#, no-wrap
+msgid "computer (string)"
+msgstr "computer (cadea)"
+
+#: C/gdm.xml:1669(para)
+msgid "Set to the themed icon name to use for the greeter logo."
+msgstr ""
+
+#: C/gdm.xml:1676(term)
+msgid "/apps/gdm/simple-greeter/recent-languages"
+msgstr "/apps/gdm/simple-greeter/recent-languages"
+
+#: C/gdm.xml:1678(synopsis) C/gdm.xml:1700(synopsis)
+#, no-wrap
+msgid "[] (string list)"
+msgstr "[] (lista de cadeas)"
+
+#: C/gdm.xml:1679(para)
+msgid ""
+"Set to a list of languages to be shown by default in the login window. "
+"Default value is \"[]\". With the default setting only the system default "
+"language is shown and the option \"Other...\" which pops-up a dialog box "
+"showing a full list of available languages which the user can select."
+msgstr ""
+
+#: C/gdm.xml:1687(para)
+msgid ""
+"Users are not intended to change this setting by hand. Instead GDM keeps "
+"track of any languages selected in this configuration key, and will show "
+"them in the language combo box along with the \"Other...\" choice. This way, "
+"commonly selected languages are easier to select."
+msgstr ""
+
+#: C/gdm.xml:1698(term)
+msgid "/apps/gdm/simple-greeter/recent-layouts"
+msgstr "/apps/gdm/simple-greeter/recent-layouts"
+
+#: C/gdm.xml:1701(para)
+msgid ""
+"Set to a list of keyboard layouts to be shown by default in the login panel. "
+"Default value is \"[]\". With the default setting only the system default "
+"keyboard layout is shown and the option \"Other...\" which pops-up a dialog "
+"box showing a full list of available keyboard layouts which the user can "
+"select."
+msgstr ""
+
+#: C/gdm.xml:1709(para)
+msgid ""
+"Users are not intended to change this setting by hand. Instead GDM keeps "
+"track of any keyboard layouts selected in this configuration key, and will "
+"show them in the keyboard layout combo box along with the \"Other...\" "
+"choice. This way, commonly selected keyboard layouts are easier to select."
+msgstr ""
+
+#: C/gdm.xml:1720(term)
+msgid "/apps/gdm/simple-greeter/wm_use_compiz"
+msgstr "/apps/gdm/simple-greeter/wm_use_compiz"
+
+#: C/gdm.xml:1723(para)
+msgid ""
+"Controls whether compiz is used as the window manager instead of metacity."
+msgstr ""
+
+#: C/gdm.xml:1733(title)
+msgid "Accessibility Configuration"
+msgstr "Configuración da accesibilidade"
+
+#: C/gdm.xml:1735(para)
+msgid ""
+"This section describes the accessibility configuration options available in "
+"GDM."
+msgstr ""
+
+#: C/gdm.xml:1741(title)
+msgid "GDM Accessibility Dialog And GConf Keys"
+msgstr ""
+
+#: C/gdm.xml:1743(para)
+msgid ""
+"The GDM greeter panel at the login screen displays an accessibility icon. "
+"Clicking on that icon opens the GDM Accessibility Dialog. In the GDM "
+"Accessibility Dialog, there is a list of checkboxes, so the user can enable "
+"or disable the associated assistive tools."
+msgstr ""
+
+#: C/gdm.xml:1750(para)
+msgid ""
+"The checkboxes that correspond to the on-screen keyboard, screen magnifier "
+"and screen reader assistive tools act on the three GConf keys that are "
+"described in the next section of this document. By enabling or disabling "
+"these checkboxes, the associated GConf key is set to \"true\" or \"false\". "
+"When the GConf key is set to true, the assistive tools linked to this GConf "
+"key are launched. When the GConf key is set to \"false\", any running "
+"assistive tool linked to this GConf key are terminated. These GConf keys are "
+"not automatically reset to a default state after the user has logged in. "
+"Consequently, the assistive tools that were running during the last GDM "
+"login session will automatically be launched at the next GDM login session."
+msgstr ""
+
+#: C/gdm.xml:1764(para)
+msgid ""
+"The other checkboxes in the GDM Accessibility Dialog do not have "
+"corresponding GConf keys because no additional program is launched to "
+"provide the accessibility features that they offer. These other options "
+"correspond to accessibility features that are provided by the Xserver, which "
+"is always running during the GDM session."
+msgstr ""
+
+#: C/gdm.xml:1774(title)
+msgid "Accessibility GConf Keys"
+msgstr "Chaves de accesibilidade de GConf"
+
+#: C/gdm.xml:1776(para)
+msgid ""
+"GDM offers the following GConf keys to control its accessibility features:"
+msgstr ""
+
+#: C/gdm.xml:1782(title)
+msgid "GDM Configuration Keys"
+msgstr "Chaves de configuración de GDM"
+
+#: C/gdm.xml:1785(term)
+msgid "/desktop/gnome/interface/accessibility"
+msgstr "/desktop/gnome/interface/accessibility"
+
+#: C/gdm.xml:1788(para)
+msgid ""
+"Controls whether the Accessibility infrastructure will be started with the "
+"GDM GUI. This is needed for many accessibility technology programs to work."
+msgstr ""
+
+#: C/gdm.xml:1796(term)
+msgid "/desktop/gnome/applications/at/screen_magnifier_enabled"
+msgstr "/desktop/gnome/applications/at/screen_magnifier_enabled"
+
+#: C/gdm.xml:1799(para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is a screen magnifier application."
+msgstr ""
+
+#: C/gdm.xml:1807(term)
+msgid "/desktop/gnome/applications/at/screen_keyboard_enabled"
+msgstr "/desktop/gnome/applications/at/screen_keyboard_enabled"
+
+#: C/gdm.xml:1810(para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is an on-screen keyboard "
+"application."
+msgstr ""
+
+#: C/gdm.xml:1818(term)
+msgid "/desktop/gnome/applications/at/screen_reader_enabled"
+msgstr "/desktop/gnome/applications/at/screen_reader_enabled"
+
+#: C/gdm.xml:1821(para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is a screen reader application."
+msgstr ""
+
+#: C/gdm.xml:1832(title)
+msgid "Linking GConf Keys to Accessbility Tools"
+msgstr ""
+
+#: C/gdm.xml:1834(para)
+msgid ""
+"For the screen_magnifier_enabled, the screen_keyboard_enabled, and the "
+"screen_reader_enabled GConf keys, the assistive tool which gets launched "
+"depends on the desktop files located in the GDM autostart directory as "
+"described in the \"Autostart Configuration\" section of this manual. Any "
+"desktop file in the GDM autostart directory can be linked to these GConf key "
+"via specifying that GConf key in the AutostartCondition value in the desktop "
+"file. So the exact AutostartCondition line in the desktop file could be one "
+"of the following:"
+msgstr ""
+
+#: C/gdm.xml:1846(screen)
+#, no-wrap
+msgid ""
+"\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled\n"
+msgstr ""
+"\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled\n"
+
+#: C/gdm.xml:1852(para)
+msgid ""
+"When an accessibility key is true, then any program which is linked to that "
+"key in a GDM autostart desktop file will be launched (unless the Hidden key "
+"is set to true in that desktop file). A single GConf key can even start "
+"multiple assistive tools if there are multiple desktop files with this "
+"AutostartCondition in the GDM autostart directory."
+msgstr ""
+
+#: C/gdm.xml:1862(title)
+msgid "Example Of Modifying Accessibility Tool Configuration"
+msgstr ""
+
+#: C/gdm.xml:1864(para)
+msgid ""
+"For example, if GNOME is distributed with GOK as the default on-screen "
+"keyboard, then this could be replaced with a different program if desired. "
+"To replace GOK with the on-screen keyboard application \"onboard\" and "
+"additionally activate the assistive tool \"mousetweaks\" for dwelling "
+"support, then the following configuration is needed."
+msgstr ""
+
+#: C/gdm.xml:1872(para)
+msgid ""
+"Create a desktop file for onboard and a second one for mousetweaks; for "
+"example, onboard.desktop and mousetweaks.desktop. These files must be placed "
+"in the GDM autostart directory and be in the format as explained in the "
+"\"Autostart Configuration\" section of this document."
+msgstr ""
+
+#: C/gdm.xml:1880(para)
+msgid "The following is an example <filename>onboard.desktop</filename> file:"
+msgstr ""
+
+#: C/gdm.xml:1884(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Onboard Onscreen Keyboard\n"
+"Comment=Use an on-screen keyboard\n"
+"TryExec=onboard\n"
+"Exec=onboard --size 500x180 -x 20 -y 10\n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+msgstr ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Teclado en pantalla\n"
+"Comment=Usar un teclado en pantalla\n"
+"TryExec=onboard\n"
+"Exec=onboard --size 500x180 -x 20 -y 10\n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+
+#: C/gdm.xml:1898(para)
+msgid ""
+"The following is an example <filename>mousetweaks.desktop</filename> file:"
+msgstr ""
+"O seguinte é un exemplo de ficheiro <filename>mousetweaks.desktop</filename>:"
+
+#: C/gdm.xml:1903(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Software Mouse-Clicks\n"
+"Comment=Perform clicks by dwelling with the pointer\n"
+"TryExec=mousetweaks\n"
+"Exec=mousetweaks --enable-dwell -m window -c -x 20 -y 240 \n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+msgstr ""
+
+#: C/gdm.xml:1917(para)
+msgid ""
+"Note the line with the AutostartCondition that links both desktop files to "
+"the GConf key for the on-screen keyboard."
+msgstr ""
+
+#: C/gdm.xml:1922(para)
+msgid ""
+"To disable GOK from starting, the desktop file for the GOK on-screen "
+"keyboard must be removed or deactivated. Otherwise onboard and GOK would "
+"simultaneously be started. This can be done by removing the gok.desktop file "
+"from the GDM autostart directory, or by adding the \"Hidden=true\" key "
+"setting to the gok.desktop file."
+msgstr ""
+
+#: C/gdm.xml:1930(para)
+msgid ""
+"After making these changes, GOK will no longer be started when the user "
+"activates the on-screen keyboard in the GDM session; but onboard and "
+"mousetweaks will instead be launched."
+msgstr ""
+
+#: C/gdm.xml:1939(title)
+msgid "General Session Settings"
+msgstr "Configuracińo xeral de sesión"
+
+#. <para>
+#.           TODO - I think this section should be expanded upon.  What specific
+#.                  keys are of interest, or would some users be likely to want
+#.                  to configure?  Also, would be good to be more specific about
+#.                  how lock down management is handled.
+#. </para>
+#: C/gdm.xml:1948(para)
+msgid ""
+"The GDM Greeter uses some of the same framework that your desktop session "
+"will use. And so, it is influenced by a number of the same GConf settings. "
+"For each of these settings the Greeter will use the default value unless it "
+"is specifically overridden by a) GDM's installed mandatory policy b) system "
+"mandatory policy. GDM installs its own mandatory policy to lock down some "
+"settings for security."
+msgstr ""
+
+#: C/gdm.xml:1959(title)
+msgid "GNOME Settings Daemon"
+msgstr "«Daemon» de preferencias de GNOME"
+
+#. <para>
+#.           TODO - I think this section should be expanded upon.  What specific
+#.                  keys are of interest, or would some users be likely to want
+#.                  to configure?  Also, would be good to give a more complete
+#.                  list of plugins that users might want to consider disabling.
+#.                  Also, shouldn't we list the sound/active key in the Greeter
+#.                  configuration setting?  Oddly I do not find this key used
+#.                  in anything but the chooser in SVN.
+#. </para>
+#: C/gdm.xml:1972(para)
+msgid ""
+"GDM enables the following gnome-settings-daemon plugins: a11y-keyboard, "
+"background, sound, xsettings."
+msgstr ""
+
+#: C/gdm.xml:1977(para)
+msgid ""
+"These are responsible for things like the background image, font and theme "
+"settings, sound events, etc."
+msgstr ""
+
+#: C/gdm.xml:1982(para)
+msgid ""
+"Plugins can also be disabled using GConf. For example, if you want to "
+"disable the sound plugin then unset the following key: <filename>/apps/gdm/"
+"simple-greeter/settings-manager-plugins/sound/active</filename>."
+msgstr ""
+
+#: C/gdm.xml:1990(title)
+msgid "GDM Session Configuration"
+msgstr "Configuración de sesión de GDM"
+
+#: C/gdm.xml:1992(para)
+msgid ""
+"GDM sessions are specified using the FreeDesktop.org Desktop Entry "
+"Specification, which can be referenced at the following URL: <ulink url="
+"\"http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec\"> "
+"http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec</ulink>."
+msgstr ""
+
+#: C/gdm.xml:1999(para)
+msgid ""
+"By default, GDM will install desktop files in the <filename>&lt;share&gt;/"
+"xsessions</filename> directory. GDM will search the following directories in "
+"this order to find desktop files: <filename>&lt;etc&gt;/X11/sessions/</"
+"filename>, <filename>&lt;dmconfdir&gt;/Sessions</filename>, <filename>&lt;"
+"share&gt;/xsessions</filename>, and <filename>&lt;share&gt;/gdm/"
+"BuiltInSessions</filename>. By default the <filename>&lt;dmconfdir&gt;</"
+"filename> is set to <filename>&lt;etc&gt;/dm/</filename> unless GDM is "
+"configured to use a different directory via the \"--with-dmconfdir\" option."
+msgstr ""
+
+#: C/gdm.xml:2012(para)
+msgid ""
+"A session can be disabled by editing the desktop file and adding a line as "
+"follows: <filename>Hidden=true</filename>."
+msgstr ""
+
+#: C/gdm.xml:2017(para)
+msgid ""
+"GDM desktop files support a GDM-specific extension, a key named \"X-GDM-"
+"BypassXsession\". If the key is not specified in a desktop file, the value "
+"defaults to \"false\". If this key is specified to be \"true\" in a desktop "
+"file, then GDM will launch the program specified by the desktop file \"Exec"
+"\" key directly when starting the user session. It will not run the program "
+"via the <filename>&lt;etc&gt;/gdm/Xsession</filename> script, which is the "
+"normal behavior. Since bypassing the <filename>&lt;etc&gt;/gdm/Xsession</"
+"filename> script avoids setting up the user session with the normal system "
+"and user settings, sessions started this way can be useful for debugging "
+"problems in the system or user scripts that might be preventing a user from "
+"being able to start a session."
+msgstr ""
+
+#: C/gdm.xml:2036(title)
+msgid "GDM User Session and Language Configuration"
+msgstr "Sesión de usuario de GDM e preferencias de idioma"
+
+#: C/gdm.xml:2037(para)
+msgid ""
+"The user's default session and language choices are stored in the "
+"<filename>~/.dmrc</filename> file. When a user logs in for the first time, "
+"this file is created with the user's initial choices. The user can change "
+"these default values by simply changing to a different value when logging "
+"in. GDM will remember this change for subsequent logins."
+msgstr ""
+
+#: C/gdm.xml:2045(para)
+msgid ""
+"The <filename>~/.dmrc</filename> file is in the standard <filename>INI</"
+"filename> format. It has one section called <filename>[Desktop]</filename> "
+"which has two keys: <filename>Session</filename> and <filename>Language</"
+"filename>."
+msgstr ""
+
+#: C/gdm.xml:2052(para)
+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. 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 ""
+
+#: C/gdm.xml:2061(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop]\n"
+"Session=gnome\n"
+"Language=cs_CZ.UTF-8\n"
+msgstr ""
+"\n"
+"[Desktop]\n"
+"Session=gnome\n"
+"Language=gl_ES.UTF-8\n"
+
+#: C/gdm.xml:2073(title)
+msgid "GDM Commands"
+msgstr "Ordes de GDM"
+
+#: C/gdm.xml:2076(title)
+msgid "GDM Root User Commands"
+msgstr "Ordes do administrador de GDM"
+
+#: C/gdm.xml:2078(para)
+msgid ""
+"The GDM package provides the following commands in <filename>sbindir</"
+"filename> intended to be run by the root user:"
+msgstr ""
+
+#: C/gdm.xml:2084(title) C/gdm.xml:2099(title)
+msgid ""
+"<command>gdm</command> and <command>gdm-binary</command> Command Line Options"
+msgstr ""
+
+#: C/gdm.xml:2087(para)
+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>&lt;etc&gt;/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. The <command>gdm-binary</command> is the "
+"actual GDM daemon."
+msgstr ""
+
+#: C/gdm.xml:2103(term)
+msgid "-?, --help"
+msgstr "-?, --help"
+
+#: C/gdm.xml:2105(para)
+msgid "Gives a brief overview of the command line options."
+msgstr ""
+
+#: C/gdm.xml:2112(term)
+msgid "--fatal-warnings"
+msgstr "--fatal-warnings"
+
+#: C/gdm.xml:2114(para)
+msgid "Make all warnings cause GDM to exit."
+msgstr ""
+
+#: C/gdm.xml:2121(term)
+msgid "--timed-exit"
+msgstr "--timed-exit"
+
+#: C/gdm.xml:2123(para)
+msgid "Exit after 30 seconds. Useful for debugging."
+msgstr ""
+
+#: C/gdm.xml:2130(term)
+msgid "--version"
+msgstr "--version"
+
+#: C/gdm.xml:2132(para)
+msgid "Print the version of the GDM daemon."
+msgstr ""
+
+#: C/gdm.xml:2141(title)
+msgid "<command>gdm-restart</command> Command Line Options"
+msgstr "Opcións de liña de ordes de <command>gdm-restart</command>"
+
+#: C/gdm.xml:2143(para)
+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 ""
+
+#: C/gdm.xml:2151(title)
+msgid "<command>gdm-safe-restart</command> Command Line Options"
+msgstr "Opcións de liña de ordes de <command>gdm-safe-restart</command>"
+
+#: C/gdm.xml:2153(para)
+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 e reinicia GDM enviando ao «daemon» "
+"GDM un sinal USR1. GDM reiniciarase tan pronto como todos os usuarios saian."
+
+#: C/gdm.xml:2161(title)
+msgid "<command>gdm-stop</command> Command Line Options"
+msgstr "Opcións da liña de ordes de <command>gdm-stop</command>"
+
+#: C/gdm.xml:2163(para)
+msgid ""
+"<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM "
+"signal."
+msgstr ""
+"<command>gdm-stop</command> para GDM enviando ao «daemon» GDM un sinal TERM."
+
+#: C/gdm.xml:2174(title)
+msgid "Troubleshooting"
+msgstr "Resolución de problemas"
+
+#. <para>
+#.       TODO - any other tips we should add?  Might be useful to highlight any
+#.              common D-Bus configuration issues?
+#. </para>
+#: C/gdm.xml:2182(para)
+msgid ""
+"This section discusses helpful tips for getting GDM working. In general, if "
+"you have a problem using GDM, you can submit a bug or send an email to the "
+"gdm-list mailing list. Information about how to do this is in the "
+"Introduction section of the document."
+msgstr ""
+
+#: C/gdm.xml:2189(para)
+msgid ""
+"If GDM is failing to work properly, it is always a good idea to include "
+"debug information. To enable debugging, set the debug/Enable key to \"true\" "
+"in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file and restart "
+"GDM. Then use GDM to the point where it fails, and debug output will be sent "
+"to the system log file (<filename>&lt;var&gt;/log/messages</filename> or "
+"<filename>&lt;var&gt;/adm/messages</filename> depending on your Operating "
+"System). If you share this output with the GDM community via a bug report or "
+"email, please only include the GDM related debug information and not the "
+"entire file since it can be large. If you do not see any GDM syslog output, "
+"you may need to configure syslog (refer to the <ulink type=\"help\" url="
+"\"man:syslog\">syslog</ulink> man page)."
+msgstr ""
+
+#: C/gdm.xml:2205(title)
+msgid "GDM Will Not Start"
+msgstr "GDM non se inicia"
+
+#: C/gdm.xml:2207(para)
+msgid ""
+"There are a many problems that can cause GDM to fail to start, but this "
+"section will discuss a few common problems and how to approach tracking down "
+"a problem with GDM starting. Some problems will cause GDM to respond with an "
+"error message or dialog when it tries to start, but it can be difficult to "
+"track down problems when GDM fails silently."
+msgstr ""
+
+#: C/gdm.xml:2216(para)
+msgid ""
+"First make sure that the Xserver is configured properly. The GDM "
+"configuration file contains a command in the [server-Standard] section that "
+"is used for starting the Xserver. Verify that this command works on your "
+"system. Running this command from the console should start the Xserver. If "
+"it fails, then the problem is likely with your Xserver configuration. Refer "
+"to your Xserver error log for an idea of what the problem may be. The "
+"problem may also be that your Xserver requires different command-line "
+"options. If so, then modify the Xserver command in the GDM configuration "
+"file so that it is correct for your system."
+msgstr ""
+
+#: C/gdm.xml:2229(para)
+msgid ""
+"Also make sure that the <filename>/tmp</filename> directory has reasonable "
+"ownership and permissions, and that the machine's file system is not full. "
+"These problems will cause GDM to fail to start."
+msgstr ""
+
+#: C/gdm.xml:2240(title)
+msgid "License"
+msgstr "Licenza"
+
+#: C/gdm.xml:2241(para)
+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 ""
+
+#: C/gdm.xml:2249(para)
+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 ""
+
+#: C/gdm.xml:2255(para)
+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>51 Franklin Street, Fifth Floor</"
+"street><city>Boston</city>, <state>MA</state><postcode>02110-1301</"
+"postcode><country>USA</country></address>"
+msgstr ""
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
+#: C/gdm.xml:0(None)
+msgid "translator-credits"
+msgstr "Fran Dieguez <frandieguez@gnome.org>, 2012."
diff --git a/docs/id/id.po b/docs/id/id.po
new file mode 100644
index 0000000..9b20cad
--- /dev/null
+++ b/docs/id/id.po
@@ -0,0 +1,3501 @@
+# Indonesian translation of gdm manual
+# Copyright (C) 2010 THE gdm manual'S COPYRIGHT HOLDER
+# This file is distributed under the same license as the gdm package.
+# Andika Triwidada <andika@gmail.com>, 2010, 2011, 2012.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: gdm master\n"
+"POT-Creation-Date: 2012-09-04 21:13+0000\n"
+"PO-Revision-Date: 2012-09-15 18:56+0700\n"
+"Last-Translator: Andika Triwidada <andika@gmail.com>\n"
+"Language-Team: GNOME Indonesian Translation Team <gnome@i15n.org>\n"
+"Language: id_ID\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+"X-Poedit-Basepath: .\n"
+"X-Generator: Poedit 1.5.3\n"
+"X-Poedit-SearchPath-0: /S/gnome/gdm/docs\n"
+
+#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
+#| msgid "translator-credits"
+msgid "translator-credits"
+msgstr "Andika Triwidada <andika@gmail.com>, 2010, 2011, 2012."
+
+#: C/index.docbook:13(articleinfo/title)
+msgid "GNOME Display Manager Reference Manual"
+msgstr "Manual Rujukan Manajer Tampilan GNOME"
+
+#: C/index.docbook:16(revhistory/revision)
+msgid "<revnumber>0.0</revnumber> <date>2008-09</date>"
+msgstr "<revnumber>0.0</revnumber> <date>2008-09</date>"
+
+#: C/index.docbook:23(abstract/para)
+msgid "GDM is the GNOME Display Manager, a graphical login program."
+msgstr "GDM adalah Manajer Tampilan GNOME, suatu program log masuk grafis."
+
+#: C/index.docbook:29(authorgroup/author)
+msgid ""
+"<firstname>Martin</firstname><othername>K.</othername> <surname>Petersen</"
+"surname> <affiliation> <address><email>mkp@mkp.net</email></address> </"
+"affiliation>"
+msgstr ""
+"<firstname>Martin</firstname><othername>K.</othername> <surname>Petersen</"
+"surname> <affiliation> <address><email>mkp@mkp.net</email></address> </"
+"affiliation>"
+
+#: C/index.docbook:36(authorgroup/author)
+msgid ""
+"<firstname>George</firstname><surname>Lebl</surname> <affiliation> "
+"<address><email>jirka@5z.com</email></address> </affiliation>"
+msgstr ""
+"<firstname>George</firstname><surname>Lebl</surname> <affiliation> "
+"<address><email>jirka@5z.com</email></address> </affiliation>"
+
+#: C/index.docbook:42(authorgroup/author)
+msgid ""
+"<firstname>Jon</firstname><surname>McCann</surname> <affiliation> "
+"<address><email>mccann@jhu.edu</email></address> </affiliation>"
+msgstr ""
+"<firstname>Jon</firstname><surname>McCann</surname> <affiliation> "
+"<address><email>mccann@jhu.edu</email></address> </affiliation>"
+
+#: C/index.docbook:48(authorgroup/author)
+msgid ""
+"<firstname>Ray</firstname><surname>Strode</surname> <affiliation> "
+"<address><email>rstrode@redhat.com</email></address> </affiliation>"
+msgstr ""
+"<firstname>Ray</firstname><surname>Strode</surname> <affiliation> "
+"<address><email>rstrode@redhat.com</email></address> </affiliation>"
+
+#: C/index.docbook:54(authorgroup/author)
+msgid ""
+"<firstname>Brian</firstname><surname>Cameron</surname> <affiliation> "
+"<address><email>Brian.Cameron@Oracle.COM</email></address> </affiliation>"
+msgstr ""
+"<firstname>Brian</firstname><surname>Cameron</surname> <affiliation> "
+"<address><email>Brian.Cameron@Oracle.COM</email></address> </affiliation>"
+
+#: C/index.docbook:61(articleinfo/copyright)
+msgid "<year>1998</year> <year>1999</year> <holder>Martin K. Petersen</holder>"
+msgstr ""
+"<year>1998</year> <year>1999</year> <holder>Martin K. Petersen</holder>"
+
+#: C/index.docbook:66(articleinfo/copyright)
+msgid ""
+"<year>2001</year> <year>2003</year> <year>2004</year> <holder>George Lebl</"
+"holder>"
+msgstr ""
+"<year>2001</year> <year>2003</year> <year>2004</year> <holder>George Lebl</"
+"holder>"
+
+#: C/index.docbook:72(articleinfo/copyright)
+msgid ""
+"<year>2003</year> <year>2007</year> <year>2008</year> <holder>Red Hat, Inc.</"
+"holder>"
+msgstr ""
+"<year>2003</year> <year>2007</year> <year>2008</year> <holder>Red Hat, Inc.</"
+"holder>"
+
+#: C/index.docbook:78(articleinfo/copyright)
+#| msgid "Oracle and/or its affiliates. All rights reserved."
+msgid ""
+"<year>2003</year> <year>2011</year> <holder>Oracle and/or its affiliates. "
+"All rights reserved.</holder>"
+msgstr ""
+"<year>2003</year> <year>2011</year> <holder>Oracle dan/atau afiliasinya. "
+"Semua hak dipertahankan.</holder>"
+
+#: C/index.docbook:2(legalnotice/para)
+msgid ""
+"Permission is granted to copy, distribute and/or modify this document under "
+"the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any "
+"later version published by the Free Software Foundation with no Invariant "
+"Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy "
+"of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or "
+"in the file COPYING-DOCS distributed with this manual."
+msgstr ""
+"Hak diberikan untuk menyalin, mendistribusikan, dan/atau mengubah dokumen "
+"ini di bawah persyaratan GNU Free Documentation License (GFDL, Lisensi "
+"Dokumentasi Bebas GNU), Versi 1.1 atau sebarang versi setelahnya yang "
+"dipublikasikan oleh Free Software Foundation tanpa Invariant Section, tanpa "
+"Front-Cover Texts, dan tanpa Back-Cover Texts. Anda dapat menemukan salinan "
+"dari GFDL pada <ulink type=\"help\" url=\"ghelp:fdl\">taut</ulink> ini atau "
+"di dalam berkas COPYING-DOCS yang didistribusikan bersama panduan ini."
+
+#: C/index.docbook:12(legalnotice/para) C/legal.xml:12(legalnotice/para)
+msgid ""
+"This manual is part of a collection of GNOME manuals distributed under the "
+"GFDL. If you want to distribute this manual separately from the collection, "
+"you can do so by adding a copy of the license to the manual, as described in "
+"section 6 of the license."
+msgstr ""
+"Manual ini adalah bagian dari suatu koleksi manual GNOME yang disebarkan di "
+"bawah GDFL. Bila Anda ingin menyebarkan manual ini secara terpisah dari "
+"koleksi, Anda dapat melakukannya dengan menambahkan salinan lisensi ke "
+"manual, sebagaimana dijelaskan di bagian 6 dari lisensi."
+
+#: C/index.docbook:19(legalnotice/para) C/legal.xml:19(legalnotice/para)
+msgid ""
+"Many of the names used by companies to distinguish their products and "
+"services are claimed as trademarks. Where those names appear in any GNOME "
+"documentation, and the members of the GNOME Documentation Project are made "
+"aware of those trademarks, then the names are in capital letters or initial "
+"capital letters."
+msgstr ""
+"Banyak nama yang dipakai oleh perusahaan-perusahaan untuk membedakan produk "
+"dan layanan mereka diklaim sebagai merek dagang. Ketika nama-nama tersebut "
+"muncul di dalam sebarang dokumentasi GNOME, and anggota Projek Dokumentasi "
+"GNOME disadarkan atas merek dagang tersebut, maka nama-nama akan ditulis "
+"dalam huruf besar atau huruf awal huruf besar."
+
+#: C/index.docbook:35(listitem/para) C/legal.xml:35(listitem/para)
+msgid ""
+"DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, "
+"EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT "
+"THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS "
+"MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE "
+"RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR "
+"MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR "
+"MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL "
+"WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY "
+"SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN "
+"ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION "
+"OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND"
+msgstr ""
+"DOKUMEN DISEDIAKAN DALAM BENTUK \"APA ADANYA\", TANPA JAMINAN APAPUN, YANG "
+"DINYATAKAN MAUPUN TERSIRAT, TERMASUK, TANPA PEMBATASAN, JAMINAN BAHWA "
+"DOKUMEN ATAU VERSI YANG DIMODIFIKASI DARI DOKUMEN BEBAS DARI KERUSAKAN YANG "
+"DAPAT DIPERJUALBELIKAN, COCOK UNTUK KEPERLUAN TERTENTU ATAU TAK MELANGGAR. "
+"SEMUA RESIKO ATAS KUALITAS, KETEPATAN, DAN KINERJA DOKUMEN ATAU VERSI YANG "
+"DIMODIFIKASI ADA PADA ANDA. BILA SEBARANG DOKUMEN ATAU VERSI YANG "
+"DIMODIFIKASI DARI DOKUMEN TERBUKTI RUSAK DALAM HAL APAPUN, ANDA (BUKAN "
+"PENULIS AWAL, PENGARANG, ATAU SEBARANG PENYUMBANG) MENANGGUNG BIAYA UNTUK "
+"PELAYANAN, PERBAIKAN, ATAU KOREKSI YANG DIPERLUKAN. DISKLAIMER JAMINAN INI "
+"MENJADI BAGIAN ESENSIAL DARI LISENSI INI. TIDAK ADA PEMAKAIAN SEBARANG "
+"DOKUMEN ATAU VERSI YANG DIMODIFIKASI DARI DOKUMEN YANG DIIJINKAN KECUALI DI "
+"BAWAH DISKLAIMER INI, DAN"
+
+#: C/index.docbook:55(listitem/para) C/legal.xml:55(listitem/para)
+msgid ""
+"UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING "
+"NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY "
+"CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE "
+"DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON "
+"FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF "
+"ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, "
+"WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES "
+"OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED "
+"VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE "
+"POSSIBILITY OF SUCH DAMAGES."
+msgstr ""
+"TIDAK DI BAWAH KEADAAN APAPUN DAN TIDAK DI BAWAH TEORI HUKUM, APAKAH TORT "
+"(TERMASUK KETIDAKPEDULIAN), KONTRAK, ATAU APAPUN, DIMANA PENGARANG, PENULIS "
+"AWAL, SEBARANG PENYUMBANG, ATAU SEBARANG DISTRIBUTOR DOKUMEN ATAU VERSI YANG "
+"DIMODIFIKASI DARI DOKUMEN, ATAU SEBARANG SUPPLIER DARI SEBARANG PIHAK, "
+"BERTANGGUNG JAWAB ATAS SEBARANG ORANG BAGI SEBARANG KERUSAKAN LANGSUNG, TAK "
+"LANGSUNG, KHUSUS, INSIDENTAL, ATAU KONSEKUENSIAL DARI APAPUN TERMASUK, TANPA "
+"PEMBATASAN, KERUSAKAN ATAS HILANGNYA GOODWILL, BERHENTINYA PEKERJAAN, "
+"KEGAGALAN KOMPUTER, ATAU MALFUNGSI, ATAU SEBARANG DAN SEMUA KERUSAKAN LAIN "
+"ATAU KEHILANGAN YANG TIMBUL KARENA ATAU TERKAIT DENGAN PENGGUNAAN DOKUMEN "
+"DAN VERSI YANG DIMODIFIKASI DARI DOKUMEN, BAHKAN BILA PIHAK TERSEBUT "
+"MESTINYA TELAH DIBERITAHU TENTANG KEMUNGKINAN KERUSAKAN TERSEBUT."
+
+#: C/index.docbook:28(legalnotice/para) C/legal.xml:28(legalnotice/para)
+#| msgid ""
+#| "DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE "
+#| "TERMS OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER "
+#| "UNDERSTANDING THAT: <placeholder-1/>"
+msgid ""
+"DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS "
+"OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: "
+"<_:orderedlist-1/>"
+msgstr ""
+"DOKUMEN DAN VERSI YANG DOKUMEN YANG DIMODIFIKASI DISEDIAKAN DI BAWAH "
+"PERSYARATAN LISENSI GNU FREE DOCUMENTATION DENGAN PENGERTIAN LEBIH LANJUT "
+"BAHWA: <_:orderedlist-1/>"
+
+#: C/index.docbook:86(articleinfo/releaseinfo) C/index.docbook:97(sect1/para)
+msgid ""
+"This manual describes version 2.26.0 of the GNOME Display Manager. It was "
+"last updated on 02/10/2009."
+msgstr ""
+"Manual ini menjelaskan Manajer Tampilan GNOME versi 2.26.0. Terakhir "
+"diperbarui pada 02/10/2009."
+
+#: C/index.docbook:95(sect1/title)
+msgid "Terms and Conventions Used in This Manual"
+msgstr "Istilah dan Konvensi yang Dipakai di Manual Ini"
+
+#: C/index.docbook:102(sect1/para)
+msgid ""
+"Chooser - A program used to select a remote host for managing a display "
+"remotely on the attached display (<command>gdm-host-chooser</command>)."
+msgstr ""
+"Chooser/Pemilih - Suatu program yang dipakai untuk memilih suatu host jauh "
+"untuk mengelola tampilan dari jauh pada tampilan yang tersambung "
+"(<command>gdm-host-chooser</command>)."
+
+#: C/index.docbook:107(sect1/para)
+msgid ""
+"FreeDesktop - The organization providing desktop standards, such as the "
+"Desktop Entry Specification used by GDM. <ulink type=\"http\" url=\"http://"
+"www.freedesktop.org/\"> http://www.freedesktop.org</ulink>."
+msgstr ""
+"FreeDesktop - Organisasi yang menyediakan standar desktop, seperti misalnya "
+"Spesifikasi Entri Desktop yang dipakai oleh GDM. <ulink type=\"http\" url="
+"\"http://www.freedesktop.org/\"> http://www.freedesktop.org</ulink>."
+
+#: C/index.docbook:113(sect1/para)
+msgid ""
+"GDM - GNOME Display Manager. Used to describe the software package as a "
+"whole."
+msgstr ""
+"GDM - Manajer Tampilan GNOME. Dipakai untuk menjelaskan paket perangkat "
+"lunak secara utuh."
+
+#: C/index.docbook:118(sect1/para)
+msgid ""
+"Greeter - The graphical login window (<command>gdm-simple-greeter</command>)."
+msgstr ""
+"Greeter/Penyapa - Jendela log masuk grafis (<command>gdm-simple-greeter</"
+"command>)."
+
+#: C/index.docbook:122(sect1/para)
+msgid "PAM - Pluggable Authentication Mechanism"
+msgstr "PAM - Pluggable Authentication Mechanism"
+
+#: C/index.docbook:126(sect1/para)
+msgid "XDMCP - X Display Manage Protocol"
+msgstr "XDMCP - X Display Manage Protocol"
+
+#: C/index.docbook:130(sect1/para)
+msgid ""
+"Xserver - An implementation of the X Window System. For example the Xorg "
+"Xserver provided by the X.org Foundation <ulink type=\"http\" url=\"http://"
+"www.x.org/\">http://www.x.org</ulink>."
+msgstr ""
+"Xserver - Suatu implementasi Sistem X Window. Misalnya Xserver Xorg yang "
+"disediakan oleh X.org Foundation <ulink type=\"http\" url=\"http://www.x.org/"
+"\">http://www.x.org</ulink>."
+
+#: C/index.docbook:136(sect1/para)
+msgid ""
+"Paths that start with a word in angle brackets are relative to the "
+"installation prefix. I.e. <filename>&lt;share&gt;/pixmaps/</filename> refers "
+"to <filename>/usr/share/pixmaps</filename> if GDM was configured with "
+"<command>--prefix=/usr</command>."
+msgstr ""
+"Path yang diawali dengan suatu kata yang diapit oleh tanda lebih dari dan "
+"kurang dari, posisinya relatif terhadap prefiks instalasi. Artinya "
+"<filename>&lt;share&gt;/pixmaps/</filename> mengacu ke <filename>/usr/share/"
+"pixmaps</filename> bila GDM ditata dengan <command>--prefix=/usr</command>."
+
+#: C/index.docbook:147(sect1/title)
+msgid "Overview"
+msgstr "Ringkasan"
+
+#: C/index.docbook:150(sect2/title)
+msgid "Introduction"
+msgstr "Perkenalan"
+
+#: C/index.docbook:152(sect2/para)
+msgid ""
+"The GNOME Display Manager (GDM) is a display manager that implements all "
+"significant features required for managing attached and remote displays. GDM "
+"was written from scratch and does not contain any XDM or X Consortium code."
+msgstr ""
+"Manajer Tampilan GNOME (GNOME Display Manager, GDM) adalah manajer tampilan "
+"yang mengimplementasikan semua fitur signifikan yang diperlukan untuk "
+"mengelola tampilan yang tersambung langsung dan jarak jauh. GDM ditulis dari "
+"awal dan tidak memuat sebarang kode XDM atau X Consortium."
+
+#: C/index.docbook:159(sect2/para)
+msgid ""
+"Note that GDM is configurable, and many configuration settings have an "
+"impact on security. Issues to be aware of are highlighted in this document."
+msgstr ""
+"Catat bahwa GDM dapat dikonfigurasi, dan banyak tatanan konfigurasi memiliki "
+"dampak keamanan. Masalah-masalah yang mesti diwaspadai disorot pada dokumen "
+"ini."
+
+#: C/index.docbook:165(sect2/para)
+msgid ""
+"Please note that some Operating Systems configure GDM to behave differently "
+"than the default values as described in this document. If GDM does not seem "
+"to behave as documented, then check to see if any related configuration may "
+"be different than described here."
+msgstr ""
+"Mohon dicatat bahwa beberap Sistem Operasi menata GDM untuk berperilaku "
+"berbeda dengan nilai bawaan sebagaimana dijelaskan dalam dokumen ini. Bila "
+"GDM sepertinya tidak berperilaku seperti yang didokumentasikan, maka "
+"periksalah bila ada konfigurasi terkait yang mungkin berbeda dengan yang "
+"dijelaskan disini."
+
+#: C/index.docbook:172(sect2/para)
+msgid ""
+"For further information about GDM, refer to the project website at <ulink "
+"type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> http://www.gnome."
+"org/projects/gdm</ulink> and the project Wiki <ulink type=\"http\" url="
+"\"http://live.gnome.org/GDM\"> http://live.gnome.org/GDM</ulink>."
+msgstr ""
+"Untuk informasi lebih lanjut tentang GDM, silakan mengacu ke situs web "
+"projek di <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> "
+"http://www.gnome.org/projects/gdm</ulink> dan Wiki projek <ulink type=\"http"
+"\" url=\"http://live.gnome.org/GDM\"> http://live.gnome.org/GDM</ulink>."
+
+#: C/index.docbook:180(sect2/para)
+msgid ""
+"For discussion or queries about GDM, refer to the <address><email>gdm-"
+"list@gnome.org</email></address> mail list. This list is archived, and is a "
+"good resource to check to seek answers to common questions. This list is "
+"archived at <ulink type=\"http\" url=\"http://mail.gnome.org/archives/gdm-"
+"list/\"> http://mail.gnome.org/archives/gdm-list/</ulink> and has a search "
+"facility to look for messages with keywords."
+msgstr ""
+"Untuk diskusi atau pertanyaan tentang GDM, silakan mengacu ke milis "
+"<address><email>gdm-list@gnome.org</email></address>. List ini diarsipkan, "
+"dan merupakan sumber daya yang bagus untuk memeriksa dan mencari jawaban "
+"atas pertanyaan umum. List ini diarsipkan di <ulink type=\"http\" url="
+"\"http://mail.gnome.org/archives/gdm-list/\"> http://mail.gnome.org/archives/"
+"gdm-list/</ulink> dan memiliki fasilitas pencarian untuk mencari pesan "
+"dengan kata kunci."
+
+#: C/index.docbook:190(sect2/para)
+msgid ""
+"Please submit any bug reports or enhancement requests to the \"gdm\" "
+"category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\"> http://"
+"bugzilla.gnome.org</ulink>."
+msgstr ""
+"Mohon kirim laporan kutu atau permintaan perbaikan ke kategori \"gdm\" pada "
+"<ulink type=\"http\" url=\"http://bugzilla.gnome.org/\"> http://bugzilla."
+"gnome.org</ulink>."
+
+#: C/index.docbook:199(sect2/title)
+msgid "Interface Stability"
+msgstr "Stabilitas Antar Muka"
+
+#: C/index.docbook:201(sect2/para)
+msgid ""
+"GDM 2.20 and earlier supported stable configuration interfaces. However, the "
+"codebase was completely rewritten for GDM 2.22, and is not completely "
+"backward compatible with older releases. This is in part because things work "
+"differently, so some options just don't make sense, in part because some "
+"options never made sense, and in part because some functionality has not "
+"been reimplemented yet."
+msgstr ""
+"GDM 2.20 dan sebelumnya mendukung antar muka konfigurasi stabil. Namun, "
+"codebase-nya ditulis ulang secara lengkap bagi GDM 2.22, dan tak sepenuhnya "
+"kompatibel ke belakang dengan rilis-rilis yang lebih lama. Hal ini sebagian "
+"karena berbagai hal bekerja secara berbeda, sehingga beberapa opsi jadi tak "
+"masuk akal, sebagian lagi karena sebagian opsi tak pernah masuk akal, dan "
+"sebagian karena beberapa fungsionalitas belum diimplementasi ulang."
+
+#: C/index.docbook:210(sect2/para)
+msgid ""
+"Interfaces which continue to be supported in a stable fashion include the "
+"Init, PreSession, PostSession, PostLogin, and Xsession scripts. Some daemon "
+"configuration options in the <filename>&lt;etc&gt;/gdm/custom.conf</"
+"filename> file continue to be supported. Also, the <filename>~/.dmrc</"
+"filename>, and face browser image locations are still supported."
+msgstr ""
+"Antarmuka yang didukung terus secara stabil termasuk skrip Xsession, Init, "
+"PreSession, PostSession, dan PostLogin. Beberapa opsi konfigurasi daemon "
+"dalam berkas <filename>&lt;etc&gt;/gdm/custom.conf</filename> didukung "
+"terus. <filename>~/.dmrc</filename> dan lokasi gambar peramban muka juga "
+"masih didukung."
+
+#: C/index.docbook:219(sect2/para)
+msgid ""
+"GDM 2.20 and earlier supported the ability to manage multiple displays with "
+"separate graphics cards, such as used in terminal server environments, login "
+"in a window via a program like Xnest or Xephyr, the gdmsetup program, XML-"
+"based greeter themes, and the ability to run the XDMCP chooser from the "
+"login screen. These features were not added back during the 2.22 rewrite."
+msgstr ""
+"GDM 2.20 dan sebelumnya mendukung kemampuan pengelolaan tampilan berganda "
+"dengan kartu grafis yang terpisah seperti yang dipakai pada lingkungan "
+"server terminal, log masuk ke jendela melalui program seperti Xnest atau "
+"Xephyr, program gdmsetup, tema penyapa berbasis XML, dan kemampuan "
+"menjalankan pemilih XDMCP dari layar log masuk. Fitur-fitur tersebut tak "
+"ditambahkan kembali selama penulisan ulang 2.22."
+
+#: C/index.docbook:231(sect2/title)
+msgid "Functional Description"
+msgstr "Penjelasan Fungsional"
+
+#: C/index.docbook:242(sect2/para)
+msgid ""
+"GDM is responsible for managing displays on the system. This includes "
+"authenticating users, starting the user session, and terminating the user "
+"session. GDM is configurable and the ways it can be configured are described "
+"in the \"Configuring GDM\" section of this document. GDM is also accessible "
+"for users with disabilities."
+msgstr ""
+"GDM bertanggung jawab mengelola tampilan pada sistem. Ini termasuk "
+"mengotentikasi pengguna, memulai sesi pengguna, dan mengakhiri sesi "
+"pengguna. GDM dapat ditata dan berbagai cara penataannya diuraikan dalam "
+"bagian \"Menata GDM\" dari dokumen ini. GDM juga membantu pengguna cacat."
+
+#: C/index.docbook:250(sect2/para)
+msgid ""
+"GDM provides the ability to manage the main console display, and displays "
+"launched via VT. It is integrated with other programs, such as the Fast User "
+"Switch Applet (FUSA) and gnome-screensaver to manage multiple displays on "
+"the console via the Xserver Virtual Terminal (VT) interface. It also can "
+"manage XDMCP displays."
+msgstr ""
+"GDM menyediakan kemampuan mengelola tampilan konsol utama, dan tampilan yang "
+"diluncurkan melalui VT. Ini terpadu dengan program lain, seperti Fast User "
+"Switch Applet (FUSA, aplet berganti pengguna secara cepat) dan gnome-"
+"screensaver untuk mengelola tampilan berganda pada konsol melalui antar muka "
+"Xserver Virtual Terminal (VT). Ini juga dapat mengelola tampilan XDMCP."
+
+#: C/index.docbook:258(sect2/para)
+msgid ""
+"Regardless of the display type, GDM will do the following when it manages "
+"the display. It will start an Xserver process, then run the <filename>Init</"
+"filename> script as the root user, and start the greeter program on the "
+"display."
+msgstr ""
+"Tanpa peduli jenis tampilan, GDM akan melakukan hal berikut ketika mengelola "
+"tampilan. Dia akan memulai proses Xserver, lalu menjalankan skrip "
+"<filename>Init</filename> sebagai pengguna root, dan mengawali program "
+"penyapa pada tampilan."
+
+#: C/index.docbook:265(sect2/para)
+#| msgid ""
+#| "The greeter program is run as the unprivileged \"gdm\" user/group. This "
+#| "user and group are described in the \"Security\" section of this "
+#| "document. The main functions of the greeter program are to provide a "
+#| "mechanism for selecting an account for log in and to drive the dialogue "
+#| "between the user and system when authenticating that account. The "
+#| "authentication process is driven by Pluggable Authentication Modules "
+#| "(PAM). The PAM modules determine what prompts (if any) are shown to the "
+#| "user to authenticate. On the average system, the greeter program will "
+#| "request a username and password for authentication. However some systems "
+#| "may be configured to use supplemental mechanisms such as a fingerprint or "
+#| "SmartCard readers. GDM can be configured to support these alternatives in "
+#| "parallel with greeter login extensions and the <command>--enable-split-"
+#| "authentication</command><filename>./configure</filename> option, or one "
+#| "at a time via system PAM configuration."
+msgid ""
+"The greeter program is run as the unprivileged \"gdm\" user/group. This user "
+"and group are described in the \"Security\" section of this document. The "
+"main functions of the greeter program are to provide a mechanism for "
+"selecting an account for log in and to drive the dialogue between the user "
+"and system when authenticating that account. The authentication process is "
+"driven by Pluggable Authentication Modules (PAM). The PAM modules determine "
+"what prompts (if any) are shown to the user to authenticate. On the average "
+"system, the greeter program will request a username and password for "
+"authentication. However some systems may be configured to use supplemental "
+"mechanisms such as a fingerprint or SmartCard readers. GDM can be configured "
+"to support these alternatives in parallel with greeter login extensions and "
+"the <command>--enable-split-authentication</command> <filename>./configure</"
+"filename> option, or one at a time via system PAM configuration."
+msgstr ""
+"Program penyapa (greeter) dijalankan sebagai pengguna/grup biasa \"gdm\". "
+"Pengguna dan grup ini dijelaskan dalam bagian \"Keamanan\" dari dokumen ini. "
+"Fungsi utama program penyapa adalah untuk menyediakan mekanisme memilih akun "
+"untuk log masuk dan untuk mendorong dialog antara pengguna dan sistem ketika "
+"mengotentikasi akun tersebut. Proses otentikasi ini didorong oleh Pluggable "
+"Authentication Modules (PAM). Modul PAM menentukan sapaan apa (bila ada) "
+"yang ditampilkan ke pengguna untuk mengotentikasi. Pada sistem umum, program "
+"penyapa akan meminta nama pengguna dan sandi untuk otentikasi. Namun "
+"beberapa sistem mungkin ditata untuk memakai mekanisme pelengkap seperti "
+"sidik jari atau pembaca SmartCard. GDM dapat ditata untuk mendukung "
+"alternatif tersebut secara paralel dengan ekstensi log masuk penyapa dan "
+"opsi <command>--enable-split-authentication</command> <filename>./configure</"
+"filename>, atau satu setiap saat melalui konfigurasi PAM sistem."
+
+#: C/index.docbook:284(sect2/para)
+msgid ""
+"The smartcard extension can be enabled or disabled via the <filename>org."
+"gnome.display-manager.extensions.smartcard.active</filename> gsettings key."
+msgstr ""
+"Ekstensi smartcard dapat diaktifkan atau dimatikan melalui kunci gsettings "
+"<filename>org.gnome.display-manager.extensions.smartcard.active</filename>."
+
+#: C/index.docbook:290(sect2/para)
+msgid ""
+"Likewise, the fingerprint extension can be enabled or disabled via the "
+"<filename>org.gnome.display-manager.extensions.fingerprint.active</filename> "
+"gsettings key."
+msgstr ""
+"Serupa dengan itu, ekstensi sidik jari dapat diaktifkan atau dimatikan "
+"melalui kunci gsettings <filename>org.gnome.display-manager.extensions."
+"fingerprint.active</filename>."
+
+#: C/index.docbook:296(sect2/para)
+msgid ""
+"GDM and PAM can be configured to not require any input, which will cause GDM "
+"to automatically log in and simply start a session, which can be useful for "
+"some environments, such as single user systems or kiosks."
+msgstr ""
+"GDM dan PAM dapat ditata untuk tidak memerlukan masukan, yang akan "
+"menyebabkan GDM otomatis log masuk dan memulai suatu sesi, yang dapat "
+"berguna bagi beberapa lingkungan, seperti sistem pengguna tunggal atau kios."
+
+#: C/index.docbook:303(sect2/para)
+msgid ""
+"In addition to authentication, the greeter program allows the user to select "
+"which session to start and which language to use. Sessions are defined by "
+"files that end in the .desktop suffix and more information about these files "
+"can be found in the \"GDM User Session and Language Configuration\" section "
+"of this document. By default, GDM is configured to display a face browser so "
+"the user can select their user account by clicking on an image instead of "
+"having to type their username. GDM keeps track of the user's default session "
+"and language in the user's <filename>~/.dmrc</filename> and will use these "
+"defaults if the user did not pick a session or language in the login GUI."
+msgstr ""
+"Selain otentikasi, program penyapa mengijinkan pengguna memilih sesi mana "
+"yang dimulai dan bahasa mana yang dipakai. Sesi didefinisikan oleh berkas "
+"yang memiliki akhiran .desktop dan informasi lebih lanjut tentang berkas ini "
+"dapat ditemukan dalam bagian \"Konfigurasi Bahasa dan Sesi Pengguna GDM\" "
+"dari dokumen ini. Secara bawaan, GDM ditata untuk menampilkan peramban wajah "
+"sehingga pengguna dapat memilih akunnya dengan mengklik pada suatu gambar "
+"daripada mesti mengetikkan nama penggunanya. GDM mencatat sesi dan bahasa "
+"baku pengguna dalam <filename>~/.dmrc</filename> milik pengguna dan akan "
+"memakai baku ini bila pengguna tak memilih sesi atau bahasa dalam GUI log "
+"masuk."
+
+#: C/index.docbook:316(sect2/para)
+msgid ""
+"After authenticating a user, the daemon runs the <filename>PostLogin</"
+"filename> script as root, then runs the <filename>PreSession</filename> "
+"script as root. After running these scripts, the user session is started. "
+"When the user exits their session, the <filename>PostSession</filename> "
+"script is run as root. These scripts are provided as hooks for distributions "
+"and end-users to customize how sessions are managed. For example, using "
+"these hooks you could set up a machine which creates the user's $HOME "
+"directory on the fly, and erases it on logout. The difference between the "
+"<filename>PostLogin</filename> and <filename>PreSession</filename> scripts "
+"is that <filename>PostLogin</filename> is run before the pam_open_session "
+"call so is the right place to do anything which should be run before the "
+"user session is initialized. The <filename>PreSession</filename> script is "
+"called after session initialization."
+msgstr ""
+"Setelah mengotentikasi pengguna, daemon menjalankan skrip "
+"<filename>PostLogin</filename> sebagai root, lalu menjalankan skrip "
+"<filename>PreSession</filename> sebagai root. Setelah menjalankan skrip "
+"tersebut, sesi pengguna dimulai. Ketika pengguna keluar dari sesinya, skrip "
+"<filename>PostSession</filename> dijalankan sebagai root. Skrip-skrip "
+"tersebut disediakan sebagai kaitan bagi distribusi dan pengguna akhir untuk "
+"menggubah bagaimana sesi dikelola. Sebagai contoh, memakai kait tersebut "
+"Anda dapat menyiapkan suatu mesin yang membuat direktori $HOME milik "
+"pengguna sambil jalan, dan menghapusnya saat log keluar. Perbedaan antara "
+"skrip <filename>PostLogin</filename> dan <filename>PreSession</filename> "
+"adalah bahwa <filename>PostLogin</filename> dijalankan sebelum pemanggilan "
+"pam_open_session sehingga merupakan tempat yang tepat untuk melakukan apapun "
+"yang mesti dijalankan  sebelum sesi pengguna diinisialisasi. Skrip "
+"<filename>PreSession</filename> dipanggil setelah inisialisasi sesi."
+
+#: C/index.docbook:336(sect2/title)
+msgid "Greeter Panel"
+msgstr "Panel Penyapa"
+
+#: C/index.docbook:337(sect2/para)
+msgid ""
+"The GDM greeter program displays a panel docked at the bottom of the screen "
+"which provides additional functionality. When a user is selected, the panel "
+"allows the user to select which session, language, and keyboard layout to "
+"use after logging in. The keyboard layout selector also changes the keyboard "
+"layout used when typing your password. The panel also contains an area for "
+"login services to leave status icons. Some example status icons include a "
+"battery icon for current battery usage, and an icon for enabling "
+"accessibility features. The greeter program also provides buttons which "
+"allow the user to shutdown or restart the system. It is possible to "
+"configure GDM to not provide the shutdown and restart buttons, if desired. "
+"GDM can also be configured via PolicyKit (or via RBAC on Oracle Solaris) to "
+"require the user have appropriate authorization before accepting the "
+"shutdown or restart request."
+msgstr ""
+"Program penyapa GDM menampilkan suatu panel yang dilabuhkan di dasar layar "
+"yang menyediakan fungsionalitas tambahan. Ketika seorang pengguna dipilih, "
+"panel mengijinkan pengguna memilih sesi, bahasa, dan tata letak papan tik "
+"mana yang dipakai setelah log masuk. Pemilih tata letak papan tik juga "
+"mengubah tata letak papan tik yang dipakai ketika mengetikkan sandi Anda. "
+"Panel juga memuat wilayah bagi layanan log masuk untuk menampilkan ikon "
+"status. Beberapa contoh ikon status termasuk ikon baterai untuk pemakaian "
+"baterai sekarang, dan ikon untuk mengaktifkan fitur-fitur aksesibilitas. "
+"Program penyapa juga menyediakan tombol-tombol yang memungkinkan pengguna "
+"mematikan atau memulai ulang sistem. Mungkin juga untuk menata GDM agar "
+"tidak menyediakan tombol matikan dan mulai ulang bila diinginkan. GDM juga "
+"dapat ditata melalui PolicyKit (atau melalui RBAC pada Oracle Solaris) untuk "
+"menuntut pengguna agar memiliki otorisasi yang sesuai sebelum menerima "
+"permintaan mematikan atau memulai ulang."
+
+#: C/index.docbook:354(sect2/para)
+msgid ""
+"Note that keyboard layout features are only available on systems that "
+"support libxklavier."
+msgstr ""
+"Perhatikan bahwa fitur tata letak papan tik hanya tersedia pada sistem yang "
+"mendukung libxklavier."
+
+#: C/index.docbook:361(sect2/title)
+msgid "Accessibility"
+msgstr "Aksesibilitas"
+
+#: C/index.docbook:363(sect2/para)
+msgid ""
+"GDM supports \"Accessible Login\", allowing users to log into their desktop "
+"session even if they cannot easily use the screen, mouse, or keyboard in the "
+"usual way. Accessible Technology (AT) features such as an on-screen "
+"keyboard, screen reader, screen magnifier, and Xserver AccessX keyboard "
+"accessibility are available. It is also possible to enable large text or "
+"high contrast icons and controls, if needed. Refer to the \"Accessibility "
+"Configuration\" section of the document for more information how various "
+"accessibility features can be configured."
+msgstr ""
+"GDM mendukung \"Log Masuk Aksesibel\", yang memungkinkan pengguna log masuk "
+"ke sesi desktop mereka walaupun mereka tak dapat dengan mudah menggunakan "
+"layar, tetikus, atau papan tik secara biasa. Tersedia fitur-fitur Teknologi "
+"Aksesibilitas seperti papan tik pada layar, pembaca layar, pembesar layar, "
+"dan aksesibilitas papan tik Xserver AccessX. Juga dimungkinkan untuk "
+"mengaktifkan teks besar atau ikon dan kendali-kendali kontras tinggi, bila "
+"diperlukan. Lihat bagian \"Konfigurasi Aksesibilitas\" dari dokumen untuk "
+"informasi lebih lanjut tentang bagaimana berbagai fitur aksesibilitas dapat "
+"ditata."
+
+#: C/index.docbook:375(sect2/para)
+msgid ""
+"On some Operating Systems, it is necessary to make sure that the GDM user is "
+"a member of the \"audio\" group for AT programs that require audio output "
+"(such as text-to-speech) to be functional."
+msgstr ""
+"Pada beberapa Sistem Operasi, perlu dipastikan bahwa pengguna GDM adalah "
+"anggota dari grup \"audio\" agar program AT yang memerlukan keluaran audio "
+"(seperti misalnya teks-ke-suara) berfungsi."
+
+#: C/index.docbook:383(sect2/title)
+msgid "The GDM Face Browser"
+msgstr "Peramban Wajah GDM"
+
+#: C/index.docbook:385(sect2/para)
+msgid ""
+"The Face Browser is the interface which allows users to select their "
+"username by clicking on an image. This feature can be enabled or disabled "
+"via the /apps/gdm/simple-greeter/disable_user_list GConf key and is on by "
+"default. When disabled, users must type their complete username by hand. "
+"When enabled, it displays all local users which are available for login on "
+"the system (all user accounts defined in the /etc/passwd file that have a "
+"valid shell and sufficiently high UID) and remote users that have recently "
+"logged in. The face browser in GDM 2.20 and earlier would attempt to display "
+"all remote users, which caused performance problems in large, enterprise "
+"deployments."
+msgstr ""
+"Peramban Wajah adalah antar muka yang memungkinkan pengguna memilih nama "
+"dengan mengklik gambar. Fitur ini dapat diaktifkan atau dimatikan melalui "
+"kunci GConf /apps/gdm/simple-greeter/disable_user_list dan bawaannya aktif. "
+"Ketika dimatikan, pengguna mesti mengetikkan nama penggunanya secara "
+"lengkap. Ketika diaktifkan, ini menampilkan semua pengguna lokal yang dapat "
+"log masuk pada sistem (semua akun pengguna yang didefinisikan di dalam "
+"berkas /etc/passwd yang memiliki shell yang valid dan UID cukup tinggi) dan "
+"pengguna jauh yang baru-baru ini log masuk. Peramban wajah dalam GDM 2.20 "
+"dan sebelumnya akan mencoba menampilkan semua pengguna jauh, yang akan "
+"menyebabkan masalah kinerja pada pemasangan di enterprise yang besar."
+
+#: C/index.docbook:399(sect2/para)
+msgid ""
+"The Face Browser is configured to display the users who log in most "
+"frequently at the top of the list. This helps to ensure that users who log "
+"in frequently can quickly find their login image."
+msgstr ""
+"Peramban Wajah ditata untuk menampilkan pengguna yang paling sering log "
+"masuk di puncak daftar. Ini membantu memastikan bahwa pengguna yang sering "
+"log masuk dapat menemukan gambar log masuk mereka secara cepat."
+
+#: C/index.docbook:405(sect2/para)
+msgid ""
+"The Face Browser supports \"type-ahead search\" which dynamically moves the "
+"face selection as the user types to the corresponding username in the list. "
+"This means that a user with a long username will only have to type the first "
+"few characters of the username before the correct item in the list gets "
+"selected."
+msgstr ""
+"Peramban Wajah mendukung \"pencarian type-ahead\" yang secara dinamis "
+"memindah pemilihan wajah ketika pengguna mengetikkan ke nama pengguna yang "
+"berkaitan dalam daftar. Ini berarti bahwa pengguna dengan nama pengguna yang "
+"panjang hanya perlu mengetikkan beberapa karakter pertama dari nama pengguna "
+"sebelum butir yang benar dalam daftar menjadi terpilih."
+
+#: C/index.docbook:413(sect2/para)
+msgid ""
+"The icons used by GDM can be installed globally by the sysadmin or can be "
+"located in the user's home directories. If installed globally they should be "
+"in the <filename>&lt;share&gt;/pixmaps/faces/</filename> directory and the "
+"filename should be the name of the user. Face image files should be a "
+"standard image that GTK+ can read, such as PNG or JPEG. Face icons placed in "
+"the global face directory must be readable to the GDM user."
+msgstr ""
+"Ikon yang dipakai oleh GDM dapat dipasang secara global oleh sysadmin atau "
+"dapat ditempatkan pada direktori rumah pengguna. Bila dipasang secara global "
+"mereka mesti ada di direktori <filename>&lt;share&gt;/pixmaps/faces/</"
+"filename> dan nama berkas mesti merupakan nama pengguna. Berkas gambar wajah "
+"mesti merupakan gambar standar yang dapat dibaca oleh GTK+, seperti misalnya "
+"PNG atau JPEG. Ikon wajah yang ditempatkan di direktori wajah global mesti "
+"dapat dibaca oleh pengguna GDM."
+
+#: C/index.docbook:429(sect2/para)
+msgid ""
+"If there is no global icon for the user, GDM will look in the user's $HOME "
+"directory for the image file. GDM will first look for the user's face image "
+"in <filename>~/.face</filename>. If not found, it will try <filename>~/.face."
+"icon</filename>. If still not found, it will use the value defined for "
+"\"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file."
+msgstr ""
+"Bila tak ada ikon global bagi pengguna, GDM akan mencari berkas gambar dalam "
+"direktori $HOME pengguna. Pertama kali GDM akan mencari gambar wajah "
+"pengguna dalam <filename>~/.face</filename>. Bila tak ditemukan, akan dicoba "
+"<filename>~/.face.icon</filename>. Bila masih tak ditemukan, akan dipakai "
+"nilai yang didefinisikan bagi \"face/picture=\" dalam berkas <filename>~/."
+"gnome2/gdm</filename>."
+
+#: C/index.docbook:438(sect2/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 "
+"fallback to a generic face image."
+msgstr ""
+"Bila seorang pengguna tak memiliki gambar wajah, GDM akan memakai ikon "
+"\"stock_person\" yang didefinisikan dalam tema GTK+ kini. Bila gambar itu "
+"tak didefinisikan, maka akan kembali ke gambar wajah generik."
+
+#: C/index.docbook:444(sect2/para)
+msgid ""
+"Please note that loading and scaling face icons located in remote user home "
+"directories can be a very time-consuming task. Since it not practical to "
+"load images over NIS or NFS, GDM does not attempt to load face images from "
+"remote home directories."
+msgstr ""
+"Perhatikan bahwa memuat dan menskalakan ikon wajah yang terletak di "
+"direktori rumah pengguna jauh bisa merupakan tugas yang sangat menghabiskan "
+"waktu. Karena tak praktis untuk memuat gambar lewat NIS atau NFS, GDM tak "
+"mencoba memuat gambar wajah dari direktori rumah jauh."
+
+#: C/index.docbook:451(sect2/para)
+msgid ""
+"When the browser is turned on, valid usernames on the computer are exposed "
+"for everyone to see. If XDMCP is enabled, then the usernames are exposed to "
+"remote users. This, of course, limits security somewhat since a malicious "
+"user does not need to guess valid usernames. In some very restrictive "
+"environments the face browser may not be appropriate."
+msgstr ""
+"Ketika peramban dinyalakan, nama pengguna yang valid pada komputer "
+"dipaparkan untuk dilihat oleh semua orang. Bila XDMCP diaktifkan, maka nama "
+"pengguna dipaparkan ke pengguna jauh. Ini tentu saja membatasi keamanan "
+"karena pengguna yang berniat jahat tak perlu lagi menebak nama pengguna yang "
+"valid. Dalam beberapa lingkungan yang sangat terbatas, peramban wajah "
+"mungkin tidak pada tempatnya."
+
+#: C/index.docbook:463(sect2/title)
+msgid "XDMCP"
+msgstr "XDMCP"
+
+#: C/index.docbook:472(sect2/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 "
+"turned off, but can be enabled if desired. If GDM is built with TCP Wrapper "
+"support, then the daemon will only grant access to hosts specified in the "
+"GDM service section in the TCP Wrappers configuration file."
+msgstr ""
+"Daemon GDM dapat ditata untuk mendengarkan dan mengelola permintaan X "
+"Display Manager Protocol (XDMCP) dari tampilan jauh. Secara baku dukungan "
+"XDMCP dimatikan, tapi dapat dinyalakan bila dikehendaki. Bila GDM dibangun "
+"dengan dukungan TCP Wrapper, maka daemon hanya akan memberikan akses ke host "
+"yang dinyatakan pada bagian layanan GDM dalam berkas konfigurasi TCP Wrapper."
+
+#: C/index.docbook:481(sect2/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 "
+"timeouts, etc. can be fine tuned. The default configuration should work "
+"reasonably on most systems."
+msgstr ""
+"GDM menyertakan beberapa penangkal yang membuatnya lebih kebal terhadap "
+"serangan denial of service pada layanan XDMCP. Banyak parameter protokol, "
+"tenggang waktu jabat tangan, dsb. dapat ditala secara halus. Konfigurasi "
+"bawaan mestinya berjalan dengan cukup baik pada kebanyakan sistem."
+
+#: C/index.docbook:488(sect2/para)
+msgid ""
+"GDM by default listens for XDMCP requests on the normal UDP port used for "
+"XDMCP, port 177, and will respond to QUERY and BROADCAST_QUERY requests by "
+"sending a WILLING packet to the originator."
+msgstr ""
+"Secara baku GDM mendengarkan permintaan XDMCP pada port UDP normal yang "
+"dipakai oleh XDMCP, port 177, dan akan menjawab permintaan QUERY dan "
+"BROADCAST_QUERY dengan mengirim paket WILLING ke peminta."
+
+#: C/index.docbook:494(sect2/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 "
+"forward subsequent requests to the chosen manager. GDM also supports an "
+"extension to the protocol which will make it forget the redirection once the "
+"user's connection succeeds. This extension is only supported if both daemons "
+"are GDM. It is transparent and will be ignored by XDM or other daemons that "
+"implement XDMCP."
+msgstr ""
+"GDM juga dapat ditata untuk menjawab permintaan INDIRECT dan menyajikan "
+"suatu pemilih host ke tampilan jauh. GDM akan mengingat pilihan pengguna dan "
+"meneruskan permintaan seterusnya ke pengelola yang dipilih. GDM juga "
+"mendukung ekstensi ke protokol yang membuatnya melupakan pengalihan sekali "
+"koneksi pengguna sukses. Ekstensi ini hanya didukung bila kedua daemon "
+"adalah GDM. Ini transparan dan akan diabaikan oleh XDM atau daemon lain yang "
+"mengimplementasikan XDMCP."
+
+#: C/index.docbook:504(sect2/para)
+msgid ""
+"If XDMCP seems to not be working, make sure that all machines are specified "
+"in <filename>/etc/hosts</filename>."
+msgstr ""
+"Bila XDMCP sepertinya tak bekerja, pastikan bahwa semua mesin dinyatakan "
+"dalam <filename>/etc/hosts</filename>."
+
+#: C/index.docbook:509(sect2/para)
+msgid ""
+"Refer to the \"Security\" section for information about security concerns "
+"when using XDMCP."
+msgstr ""
+"Lihat ke bagian \"Keamanan\" untuk informasi tentang aspek-aspek keamanan "
+"ketika memakai XDMCP."
+
+#: C/index.docbook:516(sect2/title)
+msgid "Logging"
+msgstr "Log"
+
+#: C/index.docbook:518(sect2/para)
+msgid ""
+"GDM uses syslog to log errors and status. It can also log debugging "
+"information, which can be useful for tracking down problems if GDM is not "
+"working properly. Debug output can be enabled by setting the debug/Enable "
+"key to \"true\" in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file."
+msgstr ""
+"GDM memakai syslog untuk mencatat galat dan status. Itu juga dapat mencatat "
+"informasi pengawakutuan, yang dapat berguna untuk menelusuri masalah bila "
+"GDM tak bekerja dengan baik. Keluaran awakutu dapat diaktifkan dengan menata "
+"kunci debug/Enable ke \"true\" dalam berkas <filename>&lt;etc&gt;/gdm/custom."
+"conf</filename>."
+
+#: C/index.docbook:526(sect2/para)
+msgid ""
+"Output from the various Xservers is stored in the GDM log directory, which "
+"is normally <filename>&lt;var&gt;/log/gdm/</filename>. Any Xserver messages "
+"are saved to a file associated with the display value, <filename>&lt;"
+"display&gt;.log</filename>."
+msgstr ""
+"Keluaran dari berbagai Xserver disimpan di dalam direktori log GDM, yang "
+"biasanya <filename>&lt;var&gt;/log/gdm/</filename>. Sebarang pesan Xserver "
+"disimpan ke berkas yang dikaitkan dengan nilai tampilan, <filename>&lt;"
+"display&gt;.log</filename>."
+
+#: C/index.docbook:533(sect2/para)
+msgid ""
+"The session output is piped through the GDM daemon to the <filename>~/."
+"xsession-errors</filename> file. The file is overwritten on each login, so "
+"logging out and logging back into the same user via GDM will cause any "
+"messages from the previous session to be lost."
+msgstr ""
+"Keluaran sesi disalurkan melalui daemon GDM ke berkas <filename>~/.xsession-"
+"errors</filename>. Berkas ditimpa setiap kali log masuk, sehingga log keluar "
+"dan masuk lagi ke pengguna yang sama melalui GDM akan menyebabkan sebarang "
+"pesan dari sesi sebelumnya hilang."
+
+#: C/index.docbook:540(sect2/para)
+msgid ""
+"Note that if GDM can not create this file for some reason, then a fallback "
+"file will be created named <filename>~/.xsession-errors.XXXXXXXX</filename> "
+"where the <filename>XXXXXXXX</filename> are some random characters."
+msgstr ""
+"Catat bahwa bila GDM tak bisa membuat berkas ini karena beberapa alasan, "
+"maka berkas cadangan akan dibuat dengan nama <filename>~/.xsession-errors."
+"XXXXXXXX</filename> dimana <filename>XXXXXXXX</filename> adalah beberapa "
+"karakter acak."
+
+#: C/index.docbook:548(sect2/title)
+msgid "Fast User Switching"
+msgstr "Pindah Pengguna Dengan Cepat"
+
+#: C/index.docbook:550(sect2/para)
+msgid ""
+"GDM allows multiple users to be logged in at the same time. After one user "
+"is logged in, additional users can log in via the User Switcher on the GNOME "
+"Panel, or from the \"Switch User\" button in Lock Screen dialog of GNOME "
+"Screensaver. The active session can be changed back and forth using the same "
+"mechanism. Note that some distributions may not add the User Switcher to the "
+"default panel configuration. It can be added using the panel context menu."
+msgstr ""
+"GDM mengijinkan beberapa pengguna log masuk bersamaan. Setelah salah satu "
+"pengguna log masuk, pengguna lain dapat log masuk melalui Penukar Pengguna "
+"pada Panel GNOME, atau dari tombol \"Ganti Pengguna\" pada dialog Kunci "
+"Layar dari Screensaver GNOME. Sesi aktif dapat ditukar bolak balik memakai "
+"mekanisme yang sama. Perhatikan bahwa beberapa distribusi mungkin tidak "
+"menambahkan Penukar Pengguna ke konfigurasi panel bawaan. Itu dapat "
+"ditambahkan memakai menu konteks panel."
+
+#: C/index.docbook:559(sect2/para)
+msgid ""
+"Note this feature is available on systems that support Virtual Terminals. "
+"This feature will not function if Virtual Terminals is not available."
+msgstr ""
+"Catat bahwa fitur ini tersedia pada sistem yang mendukung Terminal Virtual. "
+"Fitur ini tak akan berfungsi bila Terminal Virtual tak tersedia."
+
+#: C/index.docbook:570(sect1/title)
+msgid "Security"
+msgstr "Keamanan"
+
+#: C/index.docbook:573(sect2/title)
+msgid "The GDM User And Group"
+msgstr "Grup dan Pengguna GDM"
+
+#: C/index.docbook:575(sect2/para)
+msgid ""
+"For security reasons a dedicated user and group id are recommended for "
+"proper operation. This user and group are normally \"gdm\" on most systems, "
+"but can be configured to any user or group. All GDM GUI programs are run as "
+"this user, so that the programs which interact with the user are run in a "
+"sandbox. This user and group should have limited privilege."
+msgstr ""
+"Untuk alasan keamanan, id pengguna dan grup yang terdedikasi disarankan "
+"untuk operasi yang benar. Pengguna dan grup ini biasanya \"gdm\" pada "
+"kebanyakan sistem, tapi dapat ditata ke sebarang pengguna atau grup. Semua "
+"program GUI GDM dijalankan sebagai pengguna ini, sehingga program yang "
+"berinteraksi dengan pengguna dijalankan dalam suatu kotak pasir. Pengguna "
+"dan grup ini mesti memiliki hak terbatas."
+
+#: C/index.docbook:584(sect2/para)
+msgid ""
+"The only special privilege the \"gdm\" user requires is the ability to read "
+"and write Xauth files to the <filename>&lt;var&gt;/run/gdm</filename> "
+"directory. The <filename>&lt;var&gt;/run/gdm</filename> directory should "
+"have root:gdm ownership and 1777 permissions."
+msgstr ""
+"Satu-satunya hak khusus yang diperlukan oleh pengguna \"gdm\" adalah "
+"kemampuan membaca dan menulis berkas Xauth ke direktori <filename>&lt;"
+"var&gt;/run/gdm</filename> directory. Direktori <filename>&lt;var&gt;/run/"
+"gdm</filename> mesti dimiliki oleh root:gdm dan hak 1777."
+
+#: C/index.docbook:592(sect2/para)
+msgid ""
+"You should not, under any circumstances, configure the GDM user/group to a "
+"user which a user could easily gain access to, such as the user "
+"<filename>nobody</filename>. Any user who gains access to an Xauth key can "
+"snoop on and control running GUI programs running in the associated session "
+"or perform a denial-of-service attack on it. It is important to ensure that "
+"the system is configured properly so that only the \"gdm\" user has access "
+"to these files and that it is not easy to login to this account. For "
+"example, the account should be setup to not have a password or allow non-"
+"root users to login to the account."
+msgstr ""
+"Anda jangan, dalam keadaan apapun, menata pengguna/grup GDM ke sesuatu yang "
+"dapat diakses dengan mudah oleh pengguna lain, seperti misalnya pengguna "
+"<filename>nobody</filename>. Sebarang pengguna yang mendapat akses ke kunci "
+"Xauth dapat menyadap dan mengendalikan program GUI yang berjalan pada sesi "
+"terkait atau melakukan serangan denial-of-service padanya. Penting untuk "
+"memastikan bahwa sistem ditata secara benar sehingga hanya pengguna \"gdm\" "
+"punya akses ke berkas tersebut dan tak mudah untuk log masuk ke akun ini. "
+"Sebagai contoh, akun mesti disiapkan untuk tak memiliki sandi atau "
+"mengijinkan pengguna bukan root untuk log masuk ke akun."
+
+#: C/index.docbook:605(sect2/para)
+msgid ""
+"The GDM greeter configuration is stored in GConf. To allow the GDM user to "
+"be able to write configuration, it is necessary for the \"gdm\" user to have "
+"a writable $HOME directory. Users may configure the default GConf "
+"configuration as desired to avoid the need to provide the \"gdm\" user with "
+"a writable $HOME directory. However, some features of GDM may be disabled if "
+"it is unable to write state information to GConf configuration."
+msgstr ""
+"Konfigurasi penyapa GDM disimpan di dalam GConf. Untuk mengijinkan pengguna "
+"GDM menulis konfigurasi, pengguna \"gdm\" perlu memiliki direktori $HOME "
+"yang dapat ditulisi. Pengguna dapat menata konfigurasi bawaan GConf sesuai "
+"keinginan untuk menghindari perlunya menyediakan pengguna \"gdm\" dengan "
+"direktori $HOME yang dapat ditulisi. Namun beberapa fitur GDM mungkin mati "
+"bila tak bisa menulis informasi keadaan ke konfigurasi GConf."
+
+#: C/index.docbook:617(sect2/title)
+msgid "PAM"
+msgstr "PAM"
+
+#: C/index.docbook:619(sect2/para)
+msgid ""
+"GDM uses PAM for login authentication. PAM stands for Pluggable "
+"Authentication Module, and is used by most programs that request "
+"authentication on your computer. It allows the administrator to configure "
+"specific authentication behavior for different login programs (such as ssh, "
+"login GUI, screensaver, etc.)"
+msgstr ""
+"GDM memakai PAM untuk otentikasi log masuk. PAM kependekan dari Pluggable "
+"Authentication Module (modul otentikasi yang dapat ditempelkan), dan dipakai "
+"oleh kebanyakan program yang meminta otentikasi pada komputer Anda. Itu "
+"mengijinkan administrator untuk menata perilaku otentikasi spesifik bagi "
+"program log masuk yang berbeda (seperti misalnya ssh, log masuk GUI, "
+"screensaver, dsb.)"
+
+#: C/index.docbook:627(sect2/para)
+msgid ""
+"PAM is complicated and highly configurable, and this documentation does not "
+"intend to explain this in detail. Instead, it is intended to give an "
+"overview of how PAM configuration relates with GDM, how PAM is commonly "
+"configured with GDM, and known issues. It is expected that a person needing "
+"to do PAM configuration would need to do further reading of PAM "
+"documentation to understand how to configure PAM and to understand terms "
+"used in this section."
+msgstr ""
+"PAM itu rumit dan dapat ditata dalam sangat banyak cara, dan dokumentasi ini "
+"bukan bertujuan untuk menjelaskan hal ini secara rinci. Alih-alih, ini "
+"ditujukan untuk memberi ringkasan tentang bagaimana konfigurasi PAM "
+"berhubungan dengan GDM, bagaimana PAM umumnya ditata dengan GDM, dan masalah-"
+"masalah yang telah diketahui. Diharapkan bahwa orang yang perlu melakukan "
+"konfigurasi PAM akan membaca lebih jauh dokumentasi PAM untuk memahami "
+"bagaimana menata PAM dan memahami istilah-istilah yang dipakai pada bagian "
+"ini."
+
+#: C/index.docbook:637(sect2/para)
+msgid ""
+"PAM configuration has different, but similar, interfaces on different "
+"Operating Systems, so check the <ulink type=\"help\" url=\"man:pam.d\">pam."
+"d</ulink> or <ulink type=\"help\" url=\"man:pam.conf\">pam.conf</ulink> man "
+"page for details. Be sure you read the PAM documentation and are comfortable "
+"with the security implications of any changes you intend to make to your "
+"configuration."
+msgstr ""
+"Konfigurasi PAM memiliki antar muka yang berbeda namun mirip pada Sistem "
+"Operasi yang berbeda, sehingga periksalah halaman man <ulink type=\"help\" "
+"url=\"man:pam.d\">pam.d</ulink> atau <ulink type=\"help\" url=\"man:pam.conf"
+"\">pam.conf</ulink> untuk rinciannya. Pastikan bahwa Anda membaca "
+"dokumentasi PAM dan merasa nyaman dengan implikasi keamanan dari perubahan "
+"apapun yang hendak Anda lakukan pada konfigurasi Anda."
+
+#: C/index.docbook:647(sect2/para)
+msgid ""
+"Note that, by default, GDM uses the \"gdm\" PAM service name for normal "
+"login and the \"gdm-autologin\" PAM service name for automatic login. These "
+"services may not be defined in your pam.d or pam.conf configured file. If "
+"there is no entry, then GDM will use the default PAM behavior. On most "
+"systems this should work fine. However, the automatic login feature may not "
+"work if the gdm-autologin service is not defined."
+msgstr ""
+"Perhatikan bahwa, secara baku, GDM memakai nama layanan PAM \"gdm\" untuk "
+"log masuk normal dan nama layanan PAM \"gdm-autologin\" untuk log masuk "
+"otomatis. Layanan-layanan ini mungkin tak didefinisikan dalam berkas "
+"konfigurasi pam.d atau pam.conf Anda. Bila tak ada entri, maka GDM akan "
+"memakai perilaku PAM bawaan. Pada kebanyakan sistem ini mestinya berjalan "
+"baik. Namun, fitur log masuk otomatis mungkin tak bekerja bila layanan gdm-"
+"autologin tak terdefinisi."
+
+#: C/index.docbook:657(sect2/para)
+msgid ""
+"The <filename>PostLogin</filename> script is run before pam_open_session is "
+"called, and the <filename>PreSession</filename> script is called after. This "
+"allows the system administrator to add any scripting to the login process "
+"either before or after PAM initializes the session."
+msgstr ""
+"Skrip <filename>PostLogin</filename> dijalankan sebelum pam_open_session "
+"dipanggil, dan skrip <filename>PreSession</filename> dipanggil setelahnya. "
+"Ini memungkinkan administrator sistem untuk menambahkan sebarang penskripan "
+"ke proses log masuk sebelum atau setelah PAM menginisialisasi sesi."
+
+#: C/index.docbook:665(sect2/para)
+msgid ""
+"If you wish to make GDM work with other types of authentication mechanisms "
+"(such as a fingerprint or SmartCard reader), then you should implement this "
+"by using a PAM service module for the desired authentication type rather "
+"than by trying to modify the GDM code directly. Refer to the PAM "
+"documentation on your system. How to do this is frequently discussed on the "
+"<address><email>gdm-list@gnome.org</email></address> mail list, so you can "
+"refer to the list archives for more information."
+msgstr ""
+"Bila Anda hendak membuat GDM bekerja dengan mekanisme otentikasi jenis lain "
+"(seperti misalnya sidik jari atau pembaca SmartCard), maka Anda mesti "
+"mengimplementasikan ini memakai modul layanan PAM bagi jenis otentikasi yang "
+"diinginkan daripada mencoba mengubah kode GDM secara langsung. Lihatlah "
+"dokumentasi PAM pada sistem Anda. Bagaimana melakukan hal ini sering "
+"didiskusikan di milis <address><email>gdm-list@gnome.org</email></address>, "
+"sehingga Anda dapat mengacu ke arsip milis untuk informasi lebih lanjut."
+
+#: C/index.docbook:676(sect2/para)
+msgid ""
+"PAM does have some limitations regarding being able to work with multiple "
+"types of authentication at the same time, like supporting the ability to "
+"accept either SmartCard and the ability to type the username and password "
+"into the login program. There are techniques that are used to make this "
+"work, and it is best to research how this problem is commonly solved when "
+"setting up such a configuration."
+msgstr ""
+"PAM memiliki beberapa keterbatasan dalam kemampuan bekerja dengan banyak "
+"tipe otentikasi pada saat yang sama, seperti mendukung kemampuan menerima "
+"SmartCard dan kemampuan mengetikkan nama pengguna serta sandi ke dalam "
+"program log masuk. Ada teknik-teknik yang dipakai untuk membuat ini bekerja, "
+"dan yang terbaik adalah meneliti bagaimana masalah ini secara umum "
+"dipecahkan ketika menyiapkan konfigurasi seperti itu."
+
+#: C/index.docbook:685(sect2/para)
+msgid ""
+"If automatic login does not work on a system, check to see if the \"gdm-"
+"autologin\" PAM stack is defined in the PAM configuration. For this to work, "
+"it is necessary to use a PAM module that simply does no authentication, or "
+"which simply returns PAM_SUCCESS from all of its public interfaces. Assuming "
+"your system has a pam_allow.so PAM module which does this, a PAM "
+"configuration to enable \"gdm-autologin\" would look like this:"
+msgstr ""
+"Bila log masuk otomatis tak bekerja pada suatu sistem, periksa apakah stack "
+"PAM \"gdm-autologin\" didefinisikan di dalam konfigurasi PAM. Agar ini "
+"bekerja, perlu memakai modul PAM yang tak melakukan otentikasi, atau yang "
+"sekedar mengembalikan PAM_SUCCESS dari semua antar muka publiknya. Dengan "
+"asumsi bahwa sistem Anda memiliki modul PAM pam_allow.so yang melakukan hal "
+"ini, konfigurasi PAM yang mengaktifkan \"gdm-autologin\" akan terlihat "
+"seperti ini:"
+
+#: C/index.docbook:695(sect2/screen)
+#, no-wrap
+msgid ""
+"\n"
+"       gdm-autologin auth  required    pam_unix_cred.so.1\n"
+"       gdm-autologin auth  sufficient  pam_allow.so.1\n"
+"       gdm-autologin account  sufficient  pam_allow.so.1\n"
+"       gdm-autologin session  sufficient  pam_allow.so.1\n"
+"       gdm-autologin password  sufficient  pam_allow.so.1\n"
+msgstr ""
+"\n"
+"       gdm-autologin auth  required    pam_unix_cred.so.1\n"
+"       gdm-autologin auth  sufficient  pam_allow.so.1\n"
+"       gdm-autologin account  sufficient  pam_allow.so.1\n"
+"       gdm-autologin session  sufficient  pam_allow.so.1\n"
+"       gdm-autologin password  sufficient  pam_allow.so.1\n"
+
+#: C/index.docbook:703(sect2/para)
+msgid ""
+"The above setup will cause no lastlog entry to be generated. If a lastlog "
+"entry is desired, then use the following for the session:"
+msgstr ""
+"Penataan di atas akan menyebabkan tiadanya entri lastlog. Bila suatu entri "
+"lastlog dikehendaki, maka gunakan yang berikut bagi sesi:"
+
+#: C/index.docbook:708(sect2/screen)
+#, no-wrap
+msgid ""
+"\n"
+"       gdm-autologin session required pam_unix_session.so.1\n"
+msgstr ""
+"\n"
+"       gdm-autologin session required pam_unix_session.so.1\n"
+
+#: C/index.docbook:712(sect2/para)
+msgid ""
+"If the computer is used by several people, which makes automatic login "
+"unsuitable, you may want to allow some users to log in without entering "
+"their password. This feature can be enabled as a per-user option in the "
+"users-admin tool from the gnome-system-tools; it is achieved by checking "
+"that the user is member a Unix group called \"nopasswdlogin\" before asking "
+"for a password. For this to work, the PAM configuration file for the \"gdm\" "
+"service must include a line such as:"
+msgstr ""
+"Bila komputer dipakai oleh beberapa orang, yang membuat log masuk otomatis "
+"tidak cocok, Anda mungkin hendak mengijinkan beberapa pengguna untuk log "
+"masuk tanpa mengetikkan sandi. Fitur ini dapat diaktifkan sebagai opsi per "
+"pengguna dalam perkakas users-admin dari gnome-system-tools; ini dicapai "
+"dengan memeriksa apakah pengguna tersebut anggota dari grup Unix bernama "
+"\"nopasswdlogin\" sebelum menanyakan sandi. Agar ini bekerja, berkas "
+"konfigurasi PAM bagi layanan \"gdm\" mesti memuat suatu baris seperti:"
+
+#: C/index.docbook:723(sect2/screen)
+#, no-wrap
+msgid ""
+"\n"
+"      gdm auth  sufficient  pam_succeed_if.so  user ingroup nopasswdlogin\n"
+msgstr ""
+"\n"
+"      gdm auth  sufficient  pam_succeed_if.so  user ingroup nopasswdlogin\n"
+
+#: C/index.docbook:730(sect2/title)
+msgid "utmp and wtmp"
+msgstr "utmp dan wtmp"
+
+#: C/index.docbook:732(sect2/para)
+msgid ""
+"GDM generates utmp and wtmp User Accounting Database entries upon session "
+"login and logout. The utmp database contains user access and accounting "
+"information that is accessed by commands such as <command>finger</command>, "
+"<command>last</command>, <command>login</command>, and <command>who</"
+"command>. The wtmp database contains the history of user access and "
+"accounting information for the utmp database. Refer to the <ulink type=\"help"
+"\" url=\"man:utmp\">utmp</ulink> and <ulink type=\"help\" url=\"man:wtmp"
+"\">wtmp</ulink> man pages on your system for more information."
+msgstr ""
+"GDM menjangkitkan entri Basis Data Akunting Pengguna utmp dan wtmp saat log "
+"masuk dan log keluar sesi. Basis data utmp memuat informasi akunting dan "
+"akses pengguna yang diakses oleh perintah seperti <command>finger</command>, "
+"<command>last</command>, <command>login</command>, dan <command>who</"
+"command>. Basis data wtmp memuat riwayat informasi akunting dan akses "
+"pengguna bagi basis data utmp. Lihatlah halaman man <ulink type=\"help\" url="
+"\"man:utmp\">utmp</ulink> dan <ulink type=\"help\" url=\"man:wtmp\">wtmp</"
+"ulink> pada sistem Anda untuk informasi lebih jauh."
+
+#: C/index.docbook:747(sect2/title)
+msgid "Xserver Authentication Scheme"
+msgstr "Skema Otentikasi Xserver"
+
+#: C/index.docbook:749(sect2/para)
+msgid ""
+"Xserver authorization files are stored in a newly created subdirectory of "
+"<filename>&lt;var&gt;/run/gdm</filename> at start up. These files are used "
+"to store and share a \"password\" between X clients and the Xserver. This "
+"\"password\" is unique for each session logged in, so users from one session "
+"can't snoop on users from another."
+msgstr ""
+"Berkas otorisasi Xserver disimpan dalam subdirektori <filename>&lt;var&gt;/"
+"run/gdm</filename> yang baru dibuat saat awal mula. Berkas-berkas ini "
+"dipakai untuk menyimpan dan berbagi \"sandi\" antara klien X dan Xserver. "
+"\"Sandi\" ini unik bagi setiap sesi log masuk, sehingga pengguna dari sesi "
+"satu tak bisa menyadap pengguna sesi lain."
+
+#: C/index.docbook:757(sect2/para)
+msgid ""
+"GDM only supports the MIT-MAGIC-COOKIE-1 Xserver 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 Xserver 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. In most cases, ssh -Y should be preferred over GDM's XDMCP features."
+msgstr ""
+"GDM hanya mendukung skema otentikasi Xserver MIT-MAGIC-COOKIE-1. Secara "
+"normal hanya sedikit keuntungan yang didapat dari skema lain, dan tak ada "
+"upaya untuk mengimplementasi mereka sejauh ini. Sangat berhati-hatilah untuk "
+"memakai XDMCP karena cookie otentikasi Xserver disalurkan lewat jaringan "
+"sebagai teks polos. Bila penyadapan mungkin, maka penyerang cukup sekedar "
+"menyadap sandi otentikasi saat Anda log masuk, tak peduli skema otentikasi "
+"yang dipakai. Bila penyadapan dimungkinkan dan tak diharapkan, maka Anda "
+"mesti memakai ssh untuk membungkus koneksi X daripada memakai XDMCP. Anda "
+"dapat menganggap XDMCP sebagai telnet mode grafis, yang memiliki masalah "
+"keamanan sama. Dalam kebanyakan kasus, ssh -Y mesti lebih disukai daripada "
+"fitur XDMCP GDM."
+
+#: C/index.docbook:774(sect2/title)
+msgid "XDMCP Security"
+msgstr "Keamanan XDMCP"
+
+#: C/index.docbook:776(sect2/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 ""
+"Walaupun tampilan Anda dilindungi oleh cookies, XEvents dan juga ketikan "
+"saat memasukkan sandi masih akan dilewatkan jaringan dalam bentuk teks "
+"polos. Sangat mudah untuk menangkap itu."
+
+#: C/index.docbook:782(sect2/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. This type of set up should never use an unmanaged hub or "
+"other sniffable network."
+msgstr ""
+"XDMCP terutama berguna untuk menjalankan thin client seperti di lab "
+"terminal. Thin client itu hanya akan perlu jaringan untuk mengakses server, "
+"sehingga kebijakan keamanan terbaik adalah untuk menempatkan thin client "
+"tersebut pada jaringan terpisah yang tak dapat diakses oleh dunia luar, dan "
+"hanya dapat menyambung ke server. Satu-satunya titik yang perlu akses keluar "
+"adalah server. Jenis penyiapan ini tak boleh memakai unmanaged hub atau "
+"jaringa lain yang dapat disadap."
+
+#: C/index.docbook:795(sect2/title)
+msgid "XDMCP Access Control"
+msgstr "Kendali Akses XDMCP"
+
+#: C/index.docbook:797(sect2/para)
+msgid ""
+"XDMCP access control is done using TCP wrappers. It is possible to compile "
+"GDM without TCP wrapper support, so this feature may not be supported on "
+"some Operating Systems."
+msgstr ""
+"Kendali akses XDMCP dilakukan memakai TCP wrappers. Memang mungkin untuk "
+"mengompail GDM tanpa dukungan TCP wrappers, sehingga fitur ini mungkin tak "
+"didukung pada beberapa Sistem Operasi."
+
+#: C/index.docbook:803(sect2/para)
+msgid ""
+"You should use the daemon name <command>gdm</command> in the <filename>&lt;"
+"etc&gt;/hosts.allow</filename> and <filename>&lt;etc&gt;/hosts.deny</"
+"filename> files. For example to deny computers from <filename>.evil.domain</"
+"filename> from logging in, then add"
+msgstr ""
+"Anda mesti memakai nama deamon <command>gdm</command> dalam berkas "
+"<filename>&lt;etc&gt;/hosts.allow</filename> dan <filename>&lt;etc&gt;/hosts."
+"deny</filename>. Sebagai contoh untuk menolak komputer dari <filename>.evil."
+"domain</filename> yang berusaha log masuk, maka tambahkan"
+
+#: C/index.docbook:810(sect2/screen)
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .evil.domain\n"
+msgstr ""
+"\n"
+"gdm: .evil.domain\n"
+
+#: C/index.docbook:813(sect2/para)
+msgid ""
+"to <filename>&lt;etc&gt;/hosts.deny</filename>. You may also need to add"
+msgstr ""
+"ke <filename>&lt;etc&gt;/hosts.deny</filename>. Anda mungkin juga perlu "
+"menambah"
+
+#: C/index.docbook:817(sect2/screen)
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .your.domain\n"
+msgstr ""
+"\n"
+"gdm: .your.domain\n"
+
+#: C/index.docbook:820(sect2/para)
+msgid ""
+"to your <filename>&lt;etc&gt;/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 ""
+"ke <filename>&lt;etc&gt;/hosts.allow</filename> bila biasanya Anda menolak "
+"semua layanan dari semua host. Lihat halaman man <ulink type=\"help\" url="
+"\"man:hosts.allow\">hosts.allow(5)</ulink> untuk rinciannya."
+
+#: C/index.docbook:829(sect2/title)
+msgid "Firewall Security"
+msgstr "Keamanan Firewall"
+
+#: C/index.docbook:831(sect2/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 really needed. GDM guards "
+"against 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 do a "
+"denial of service attack via XDMCP than attacking a webserver."
+msgstr ""
+"Walaupun GDM mencoba untuk mengakali penyerang potensial yang mencoba "
+"mengambil keuntungan dari XDMCP, masih disarankan bagi Anda untuk memblokir "
+"port XDMCP (biasanya UDP port 177) pada firewall Anda kecuali bila memang "
+"diperlukan. GDM menjaga dari serangan denial of service, tapi protokol X "
+"masih tak aman secara inheren dan mestinya hanya dipakai dalam suatu "
+"lingkungan yang terkendali. Setiap koneksi remote juga menghabiskan banyak "
+"sumber daya, sehingga jauh lebih mudah melakukan serangan denial of service "
+"melalui XDMCP daripada menyerang suatu server web."
+
+#: C/index.docbook:842(sect2/para)
+msgid ""
+"It is also wise to block all of the Xserver ports. These are TCP ports 6000+ "
+"(one for each display number) on your firewall. Note that GDM will use "
+"display numbers 20 and higher for flexible on-demand servers."
+msgstr ""
+"Juga bijaksana untuk memblokir semua port Xserver. Ini adalah port TCP 6000+ "
+"(satu bagi setiap nomor tampilan) pada firewall Anda. Perhatikan bahwa GDM "
+"akan memakai tampilan nomor 20 dan yang lebih tinggi bagi server on-demand "
+"yang fleksibel."
+
+#: C/index.docbook:849(sect2/para)
+msgid ""
+"X is not a very safe protocol when using it over the Internet, and XDMCP is "
+"even less safe."
+msgstr ""
+"X bukan protokol yang aman ketika dipakai di Internet, dan XDMCP bahkan "
+"lebih tidak aman lagi."
+
+#: C/index.docbook:856(sect2/title)
+msgid "PolicyKit"
+msgstr "PolicyKit"
+
+#: C/index.docbook:864(sect2/para)
+msgid ""
+"GDM may be configured to use PolicyKit to allow the system administrator to "
+"control whether the login screen should provide the shutdown and restart "
+"buttons on the greeter screen."
+msgstr ""
+"GDM dapat ditata untuk memakai PolicyKit yang mengijinkan administrator "
+"sistem mengendalikan apakah layar log masuk mesti menyediakan tombol matikan "
+"dan mulai ulang pada layar penyapa."
+
+#: C/index.docbook:870(sect2/para)
+msgid ""
+"These buttons are controlled by the <filename>org.freedesktop.consolekit."
+"system.stop-multiple-users</filename> and <filename>org.freedesktop."
+"consolekit.system.restart-multiple-users</filename> actions respectively. "
+"Policy for these actions can be set up using the polkit-gnome-authorization "
+"tool, or the polkit-auth command line program."
+msgstr ""
+"Tombol-tombol ini masing-masing dikendalikan oleh aksi filename>org."
+"freedesktop.consolekit.system.stop-multiple-users</filename> dan "
+"<filename>org.freedesktop.consolekit.system.restart-multiple-users</"
+"filename>. Kebijakan bagi aksi-aksi ini dapat disiapkan memakai perkakas "
+"polkit-gnome-authorization, atau program baris perintah polkit-auth."
+
+#: C/index.docbook:882(sect2/title)
+msgid "RBAC (Role Based Access Control)"
+msgstr "RBAC (Role Based Access Control)"
+
+#: C/index.docbook:884(sect2/para)
+msgid ""
+"GDM may be configured to use RBAC instead of PolicyKit. In this case the "
+"RBAC configuration is used to control whether the login screen should "
+"provide the shutdown and restart buttons on the greeter screen."
+msgstr ""
+"GDM dapat ditata untuk memakai RBAC sebagai pengganti PolicyKit. Dalam hal "
+"ini konfigurasi RBAC dipakai untuk mengendalikan apakah layar log masuk "
+"mesti menyediakan tombol matikan dan mulai ulang pada layar penyapa."
+
+#: C/index.docbook:890(sect2/para)
+msgid ""
+"For example, on Oracle Solaris, the \"solaris.system.shutdown\" "
+"authorization is used to control this. Simply modify the <filename>/etc/"
+"user_attr</filename> file so that the \"gdm\" user has this authorization."
+msgstr ""
+"Sebagai contoh, pada Oracle Solaris, otorisasi \"solaris.system.shutdown\" "
+"dipakai untuk mengendalikan ini. Cukup ubah berkas <filename>/etc/user_attr</"
+"filename> sehingga pengguna \"gdm\" memiliki otorisasi ini."
+
+#: C/index.docbook:903(sect1/title)
+msgid "Support for ConsoleKit"
+msgstr "Dukungan untuk ConsoleKit"
+
+#: C/index.docbook:914(sect1/para)
+msgid ""
+"GDM includes support for publishing user login information with the user and "
+"login session accounting framework known as ConsoleKit. ConsoleKit is able "
+"to keep track of all the users currently logged in. In this respect, it can "
+"be used as a replacement for the utmp or utmpx files that are available on "
+"most Unix-like Operating Systems."
+msgstr ""
+"GDM menyertakan dukungan bagi pengumuman informasi log masuk pengguna dengan "
+"framework akunting sesi log masuk dan pengguna yang dikenal sebagai "
+"ConsoleKit. ConsoleKit dapat mencatat semua pengguna yang kini log masuk, "
+"sehingga dapat dipakai sebagai pengganti berkas utmp atau utmpx yang "
+"tersedia pada kebanyakan Sistem Operasi mirip Unix."
+
+#: C/index.docbook:922(sect1/para)
+msgid ""
+"When GDM is about to create a new login process for a user it will call a "
+"privileged method of ConsoleKit in order to open a new session for this "
+"user. At this time GDM also provides ConsoleKit with information about this "
+"user session such as: the user ID, the X11 Display name that will be "
+"associated with the session, the host-name from which the session originates "
+"(useful in the case of an XDMCP session), whether or not this session is "
+"attached, etc. As the entity that initiates the user process, GDM is in a "
+"unique position to know about the user session and to be trusted to provide "
+"these bits of information. The use of this privileged method is restricted "
+"by the use of the D-Bus system message bus security policy."
+msgstr ""
+"Ketika GDM akan membuat proses log masuk baru bagi seorang pengguna, ia akan "
+"memanggil metoda dengan hak khusus dari ConsoleKit untuk membuka sesi baru "
+"bagi pengguna ini. Pada saat ini GDM juga menyediakan informasi untuk "
+"ConsoleKit tentang sesi pengguna ini seperti: ID pengguna, Nama tampilan X11 "
+"yang akan dikaitkan dengan sesi ini, nama host tempat sesi berasal (berguna "
+"pada kasus sesi XDMCP), apakah sesi ini dicantol atau tidak, dsb. Sebagai "
+"entitas yang mengawali proses pengguna, GDM berada pada posisi yang unik "
+"untuk mengetahui tentang sesi pengguna dan untuk dipercaya menyediakan "
+"kepingan informasi ini. Penggunaan metode dengan hak khusus ini dibatasi "
+"oleh pemakaian kebijakan keamanan bus pesan sistem D-BUS."
+
+#: C/index.docbook:936(sect1/para)
+msgid ""
+"In case a user with an existing session has authenticated at GDM and "
+"requests to resume that existing session, GDM calls a privileged method of "
+"ConsoleKit to unlock that session. The exact details of what happens when "
+"the session receives this unlock signal are undefined and session-specific. "
+"However, most sessions will unlock a screensaver in response."
+msgstr ""
+"Bila penguna dengan sesi yang telah ada telah diotentikasi pada GDM dan "
+"meminta melanjutkan sesi tersebut, GDM memanggil suatu metoda dengan hak "
+"khusus dari ConsoleKit untuk membuka kunci sesi tersebut. Rincian tepatnya "
+"dari apa yang terjadi ketika sesi menerima sinyal buka kunci ini tak "
+"terdefinisi dan spesifik sesi. Namun kebanyakan sesi akan membuka kunci "
+"screensaver sebagai respon."
+
+#: C/index.docbook:945(sect1/para)
+msgid ""
+"When the user chooses to log out, or if GDM or the session quit unexpectedly "
+"the user session will be unregistered from ConsoleKit."
+msgstr ""
+"Ketika pengguna memilih untuk log keluar, atau bila GDM atau sesi keluar tak "
+"disangka-sangka, sesi pengguna akan dikeluarkan dari daftar ConsoleKit."
+
+#: C/index.docbook:954(sect1/title)
+msgid "Configuration"
+msgstr "Konfigurasi"
+
+#: C/index.docbook:956(sect1/para)
+msgid ""
+"GDM has a number of configuration interfaces. These include scripting "
+"integration points, daemon configuration, greeter configuration, general "
+"session settings, integration with gnome-settings-daemon configuration, and "
+"session configuration. These types of integration are described in detail "
+"below."
+msgstr ""
+"GDM memiliki sejumlah antar muka konfigurasi. Ini termasuk titik integrasi "
+"skrip, konfigurasi daemon, konfigurasi penyapa, pengaturan sesi umum, "
+"integrasi dengan konfigurasi gnome-settings-daemon, dan konfigurasi sesi. "
+"Integrasi tipe ini diuraikan secara rinci di bawah."
+
+#: C/index.docbook:965(sect2/title)
+msgid "Scripting Integration Points"
+msgstr "Titik Integrasi Skrip"
+
+#: C/index.docbook:967(sect2/para)
+msgid ""
+"The GDM script integration points can be found in the <filename>&lt;etc&gt;/"
+"gdm/</filename> directory:"
+msgstr ""
+"Titik integrasi skrip GDM dapat ditemukan dalam direktori <filename>&lt;"
+"etc&gt;/gdm/</filename>:"
+
+#: C/index.docbook:972(sect2/screen)
+#, no-wrap
+msgid ""
+"\n"
+"Xsession\n"
+"Init/\n"
+"PostLogin/\n"
+"PreSession/\n"
+"PostSession/\n"
+msgstr ""
+"\n"
+"Xsession\n"
+"Init/\n"
+"PostLogin/\n"
+"PreSession/\n"
+"PostSession/\n"
+
+#: C/index.docbook:980(sect2/para)
+msgid ""
+"The <filename>Init</filename>, <filename>PostLogin</filename>, "
+"<filename>PreSession</filename>, and <filename>PostSession</filename> "
+"scripts all work as described below."
+msgstr ""
+"Skrip <filename>Init</filename>, <filename>PostLogin</filename>, "
+"<filename>PreSession</filename>, dan <filename>PostSession</filename> semua "
+"bekerja seperti dijelaskan di bawah."
+
+#: C/index.docbook:986(sect2/para)
+msgid ""
+"For each type of script, the default one which will be executed is called "
+"\"Default\" and is stored in a directory associated with the script type. So "
+"the default <filename>Init</filename> script is <filename>&lt;etc&gt;/gdm/"
+"Init/Default</filename>. A per-display script can be provided, and if it "
+"exists it will be run instead of the default script. Such scripts are stored "
+"in the same directory as the default script and have the same name as the "
+"Xserver DISPLAY value for that display. For example, if the <filename>&lt;"
+"Init&gt;/:0</filename> script exists, it will be run for DISPLAY \":0\"."
+msgstr ""
+"Untuk setiap jenis skirp, secara baku yang akan dieksekusi dinamai \"Default"
+"\" dan disimpan dalam suatu direktori yang berkaitan dengan tipe skrip. Maka "
+"skrip <filename>Init</filename> baku adalah <filename>&lt;etc&gt;/gdm/Init/"
+"Default</filename>. Suatu skrip per tampilan dapat disediakan, dan bila ada "
+"akan dijalankan sebagai pengganti skrip bawaan. Skrip demikian disimpan di "
+"dalam direktori yang sama dengan skrip bawaan dan memiliki nama yang sama "
+"dengan nilai DISPLAY Xserver bagi tampilan tersebut. Sebagai contoh, bila "
+"skrip <filename>&lt;Init&gt;/:0</filename> ada, itu akan dijalankan bagi "
+"DISPLAY \":0\"."
+
+#: C/index.docbook:998(sect2/para)
+msgid ""
+"All of these scripts are run with root privilege and return 0 if run "
+"successfully, and a non-zero return code if there was any failure that "
+"should cause the login session to be aborted. Also note that GDM will block "
+"until the scripts finish, so if any of these scripts hang, this will cause "
+"the login process to also hang."
+msgstr ""
+"Semua skrip ini dijalankan dengan privilese root dan mengembalikan 0 bila "
+"dijalankan dengan sukses, dan kode kembalian bukan nol bila ada kegagalan "
+"yang mesti menyebabkan sesi login digugurkan. Perhatikan juga bahwa GDM akan "
+"memblok sampai skrip selesai, sehingga bila salah satu skrip ini hang, ini "
+"akan menyebabkan proses log masuk juga hang."
+
+#: C/index.docbook:1006(sect2/para)
+msgid ""
+"When the Xserver for the login GUI has been successfully started, but before "
+"the login GUI is actually displayed, GDM will run the <filename>Init</"
+"filename> script. This script is useful for starting programs that should be "
+"run while the login screen is showing, or for doing any special "
+"initialization if required."
+msgstr ""
+"Ketika Xserver sebagai GUI log masuk telah sukses dimulai, tapi sebelum GUI "
+"log masuk benar-benar ditampilkan, GDM akan menjalankan skrip "
+"<filename>Init</filename>. Skrip ini berguna untuk memulai program yang "
+"mesti dijalankan ketika layar log masuk tampil, atau untuk melakukan "
+"inisialisasi khusus apapun bila diperlukan."
+
+#: C/index.docbook:1014(sect2/para)
+msgid ""
+"After the user has been successfully authenticated GDM will run the "
+"<filename>PostLogin</filename> script. This is done before any session setup "
+"has been done, including before the pam_open_session call. This script is "
+"useful for doing any session initialization that needs to happen before the "
+"session starts. For example, you might setup the user's $HOME directory if "
+"needed."
+msgstr ""
+"Setelah pengguna sukses terotentikasi GDM akan menjalankan skrip "
+"<filename>PostLogin</filename>. Ini dilakukan sebelum penyiapan sesi manapun "
+"dilakukan, termasuk sebelum pemanggilan pam_open_session. Skrip ini berguna "
+"untuk melakukan inisialisasi sesi apapun yang perlu terjadi sebelum sesi "
+"mulai. Sebagai contoh, Anda mungkin perlu menyiapkan direktori $HOME "
+"pengguna bila diperlukan."
+
+#: C/index.docbook:1023(sect2/para)
+msgid ""
+"After the user session has been initialized, GDM will run the "
+"<filename>PreSession</filename> script. This script is useful for doing any "
+"session initialization that needs to happen after the session has been "
+"initialized. It can be used for session management or accounting, for "
+"example."
+msgstr ""
+"Setelah sesi pengguna diinisialisasi, GDM akan menjalankan skrip "
+"<filename>PreSession</filename>. Skrip ini berguna untuk melakukan sebarang "
+"inisialisasi sesi yang perlu terjadi setelah sesi diinisialisasi. Ini dapat "
+"dipakai untuk manajemen sesi atau akunting, misalnya."
+
+#: C/index.docbook:1031(sect2/para)
+msgid ""
+"When a user terminates their session, GDM will run the "
+"<filename>PostSession</filename> script. Note that the Xserver will have "
+"been stopped by the time this script is run, so it should not be accessed."
+msgstr ""
+"Ketika seorang pengguna mengakhiri sesinya, GDM akan menjalankan skrip "
+"<filename>PostSession</filename>. Perhatikan bahwa Xserver bakal telah "
+"berhenti saat skrip ini dijalankan, sehingga itu tak boleh diakses."
+
+#: C/index.docbook:1038(sect2/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 ""
+"Perhatikan bahwa skrip <filename>PostSession</filename> akan dijalankan "
+"bahkan ketika tampilan gagal merespon karena galat I/O atau yang serupa. "
+"Jadi tak ada jaminan bahwa aplikasi X akan bekerja selama eksekusi skrip."
+
+#: C/index.docbook:1045(sect2/para)
+msgid ""
+"All of the above scripts will set the <filename>$RUNNING_UNDER_GDM</"
+"filename> environment variable to <filename>yes</filename>. If the scripts "
+"are also shared with other display managers, this allows you to identify "
+"when GDM is calling these scripts, so you can run specific code when GDM is "
+"used."
+msgstr ""
+"Semua skrip di atas akan menata variabel lingkungan <filename>"
+"$RUNNING_UNDER_GDM</filename> ke <filename>yes</filename>. Bila skrip juga "
+"dipakai bersama dengan manajer tampilan lain, ini memungkinkan Anda "
+"mengidentifikasi ketika GDM sedang memanggil skrip ini, sehingga Anda dapat "
+"menjalankan kode khusus ketika GDM sedang dipakai."
+
+#: C/index.docbook:1055(sect2/title)
+msgid "Autostart Configuration"
+msgstr "Konfigurasi Autostart"
+
+#: C/index.docbook:1057(sect2/para)
+msgid ""
+"The <filename>&lt;share&gt;/gdm/autostart/LoginWindow</filename> directory "
+"contains files in the format specified by the \"FreeDesktop.org Desktop "
+"Application Autostart Specification\". Standard features in the "
+"specification may be used to specify programs that should auto-restart or "
+"only be launched if a GConf configuration value is set, etc."
+msgstr ""
+"Direktori <filename>&lt;share&gt;/gdm/autostart/LoginWindow</filename> "
+"memuat berkas dalam format yang dinyatakan oleh \"FreeDesktop.org Desktop "
+"Application Autostart Specification\". Fitur standar dalam spesifikasi itu "
+"boleh dipakai untuk menyatakan program yang mesti dijalankan ulang secara "
+"otomatis atau hanya diluncurkan bila suatu nilai konfigurasi GConf ditata, "
+"dsb."
+
+#: C/index.docbook:1066(sect2/para)
+msgid ""
+"Any <filename>.desktop</filename> files in this directory will cause the "
+"associated program to automatically start with the login GUI greeter. By "
+"default, GDM is shipped with files which will autostart the gdm-simple-"
+"greeter login GUI greeter itself, the gnome-power-manager application, the "
+"gnome-settings-daemon, and the metacity window manager. These programs are "
+"needed for the greeter program to work. In addition, desktop files are "
+"provided for starting various AT programs if the configuration values "
+"specified in the Accessibility Configuration section below are set."
+msgstr ""
+"Berkas <filename>.desktop</filename> apapun dalam direktori ini akan "
+"menyebabkan program yang terkait dijalankan secara otomatis dengan penyapa "
+"GUI log masuk. Secara baku, GDM dilengkapi dengan berkas yang akan otomatis "
+"menjalankan penyapa GUI log masuk gdm-simple-greeter, aplikasi gnome-power-"
+"manager, gnome-settings-daemon, dan manajer jendela metacity. Program-"
+"program ini diperlukan agar program penyapa dapat bekerja. Sebagai tambahan, "
+"berkas desktop disediakan untuk menjalankan berbagai program AT bila nilai "
+"konfigurasi yang dinyatakan dalam bagian Konfigurasi Aksesabilitas di bawah "
+"ditata."
+
+#: C/index.docbook:1080(sect2/title)
+msgid "Xsession Script"
+msgstr "Skrip Xsession"
+
+#: C/index.docbook:1082(sect2/para)
+msgid ""
+"There is also an <filename>Xsession</filename> script located at "
+"<filename>&lt;etc&gt;/gdm/Xsession</filename> which is called between the "
+"<filename>PreSession</filename> and the <filename>PostSession</filename> "
+"scripts. This script does not support per-display like the other scripts. "
+"This script is used for actually starting the user session. This script is "
+"run as the user, and it will run whatever session was specified by the "
+"Desktop session file the user selected to start."
+msgstr ""
+"Ada juga skrip <filename>Xsession</filename> yang terletak di <filename>&lt;"
+"etc&gt;/gdm/Xsession</filename> yang dipanggil antara skrip "
+"<filename>PreSession</filename> dan <filename>PostSession</filename>. Skrip "
+"ini tak mendukung per-tampilan seperti skrip lain. Skrip ini dipakai untuk "
+"benar-benar memulai sesi pengguna. Skrip ini dijalankan sebagai pengguna, "
+"dan akan menjalankan sesi apapun yang dinyatakan oleh berkas sesi Desktop "
+"yang dipilih pengguna untuk dimulai."
+
+#: C/index.docbook:1095(sect2/title)
+msgid "Daemon Configuration"
+msgstr "Konfigurasi Daemon"
+
+#: C/index.docbook:1097(sect2/para)
+msgid ""
+"The GDM daemon is configured using the <filename>&lt;etc&gt;/gdm/custom."
+"conf</filename> file. Default values are stored in GConf in the "
+"<filename>gdm.schemas</filename> file. It is recommended that end-users "
+"modify the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file because the "
+"schemas file may be overwritten when the user updates their system to have a "
+"newer version of GDM."
+msgstr ""
+"Daemon GDM dikonfigurasi memakai berkas <filename>&lt;etc&gt;/gdm/custom."
+"conf</filename>. Nilai baku disimpan di GConf dalam berkas <filename>gdm."
+"schemas</filename>. Disarankan bahwa pengguna akhir mengubah berkas "
+"<filename>&lt;etc&gt;/gdm/custom.conf</filename> karena berkas skema mungkin "
+"tertimpa ketika pengguna memutakhirkan sistem mereka untuk mendapatkan versi "
+"GDM yang lebih baru."
+
+#: C/index.docbook:1107(sect2/para)
+msgid ""
+"Note that older versions of GDM supported additional configuration options "
+"which are no longer supported in the latest versions of GDM."
+msgstr ""
+"Perhatikan bahwa GDM versi lebih lama mendukung opsi konfigurasi tambahan "
+"yang tak didukung lagi pada versi GDM terakhir."
+
+#: C/index.docbook:1112(sect2/para)
+msgid ""
+"The <filename>&lt;etc&gt;/gdm/custom.conf</filename> file is in the "
+"<filename>keyfile</filename> format. Keywords in brackets define group "
+"sections, strings before an equal sign (=) are keys and the data after equal "
+"sign represents their value. Empty lines or lines starting with the hash "
+"mark (#) are ignored."
+msgstr ""
+"Berkas <filename>&lt;etc&gt;/gdm/custom.conf</filename> berformat "
+"<filename>keyfile</filename>. Kata kunci dalam kurung siku mendefinisikan "
+"bagian grup, string sebelum tanda sama dengan adalah kunci dan data setelah "
+"tanda sama dengan mewakili nilai mereka. Baris kosong atau baris yang "
+"diawali dengan tanda pagar (#) diabaikan."
+
+#: C/index.docbook:1120(sect2/para)
+msgid ""
+"The file <filename>&lt;etc&gt;/gdm/custom.conf</filename> supports the "
+"\"[daemon]\", \"[security]\", and \"[xdmcp]\" group sections. Within each "
+"group, there are particular key/value pairs that can be specified to modify "
+"how GDM behaves. For example, to enable timed login and specify the timed "
+"login user to be a user named \"you\", you would modify the file so it "
+"contains the following lines:"
+msgstr ""
+"Berkas <filename>&lt;etc&gt;/gdm/custom.conf</filename> mendukung bagian "
+"grup \"[daemon]\", \"[security]\", dan \"[xdmcp]\". Dalam setiap grup, ada "
+"pasangan kunci/nilai tertentu yang dapat dinyatakan untuk mengubah bagaimana "
+"GDM bertingkahlaku. Sebagai contoh, untuk mengaktifkan log masuk dengan "
+"tenggang waktu dan menyatakan bahwa pengguna yang log masuknya diberi "
+"tenggang waktu adalah pengguna bernama \"you\", Anda perlu mengubah berkas "
+"sehingga memuat baris-baris berikut:"
+
+#: C/index.docbook:1130(sect2/screen)
+#, no-wrap
+msgid ""
+"\n"
+"[daemon]\n"
+"TimedLoginEnable=true\n"
+"TimedLogin=you\n"
+msgstr ""
+"\n"
+"[daemon]\n"
+"TimedLoginEnable=true\n"
+"TimedLogin=you\n"
+
+#: C/index.docbook:1136(sect2/para)
+msgid "A full list of supported configuration keys follow:"
+msgstr ""
+"Daftar lengkap dari kunci konfigurasi yang didukung adalah sebagai berikut:"
+
+#: C/index.docbook:1141(sect3/title)
+msgid "[chooser]"
+msgstr "[chooser]"
+
+#: C/index.docbook:1145(varlistentry/term)
+msgid "Multicast"
+msgstr "Multicast"
+
+#: C/index.docbook:1147(listitem/synopsis)
+#, no-wrap
+msgid "Multicast=false"
+msgstr "Multicast=false"
+
+#: C/index.docbook:1148(listitem/para)
+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."
+msgstr ""
+"Bila true dan IPv6 diaktifkan, chooser akan mengirim suatu query multicast "
+"ke jaringan lokal dan mengumpulkan jawaban dari host yang telah bergabung ke "
+"grup multicast."
+
+#: C/index.docbook:1157(varlistentry/term)
+msgid "MulticastAddr"
+msgstr "MulticastAddr"
+
+#: C/index.docbook:1159(listitem/synopsis)
+#, no-wrap
+msgid "MulticastAddr=ff02::1"
+msgstr "MulticastAddr=ff02::1"
+
+#: C/index.docbook:1160(listitem/para)
+msgid "This is the Link-local multicast address."
+msgstr "Ini adalaha alamat multicast Link-local."
+
+#: C/index.docbook:1169(sect3/title)
+msgid "[daemon]"
+msgstr "[daemon]"
+
+#: C/index.docbook:1172(varlistentry/term)
+msgid "TimedLoginEnable"
+msgstr "TimedLoginEnable"
+
+#: C/index.docbook:1174(listitem/synopsis)
+#, no-wrap
+msgid "TimedLoginEnable=false"
+msgstr "TimedLoginEnable=false"
+
+#: C/index.docbook:1175(listitem/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. Refer to the \"Security-&gt;PAM\" section of the manual for "
+"more information, or for help if this feature does not seem to work."
+msgstr ""
+"Bila pengguna yang diberikan dalam <filename>TimedLogin</filename> mesti log "
+"masuk setelah sekian detik (diatur dengan <filename>TimedLoginDelay</"
+"filename> tanpa aktivitas pada layar log masuk. Ini berguna bagi terminal "
+"akses publik atau bahkan penggunaan di rumah. Bila pengguna memakai papan "
+"tik atau meramban menu, tenggang waktu akan direset ke "
+"<filename>TimedLoginDelay</filename> atau 30 detik, manapun yang lebih "
+"tinggi. Bila pengguna tak memasukkan nama tapi hanya menekan tombol ENTER "
+"ketika program log masuk meminta nama pengguna, maka GDM akan menganggap "
+"bahwa pengguna ingin log masuk seketika sebagai pengguna yang dikenai "
+"tenggang waktu. Perhatikan bahwa sandi tak akan diminta bagi pengguna ini "
+"sehingga Anda mesti berhati-hati, walaupun bilan menggunakan PAM ini dapat "
+"diatur untuk meminta masukan sandi sebelum mengijinkan log masuk. Lihatlah "
+"bagian \"Keamanan-&gt;PAM\" dari manual untuk informasi lebih jauh, atau "
+"untuk bantuan bila fitur ini sepertinya tak bekerja."
+
+#: C/index.docbook:1197(varlistentry/term)
+msgid "TimedLogin"
+msgstr "TimedLogin"
+
+#: C/index.docbook:1199(listitem/synopsis)
+#, no-wrap
+msgid "TimedLogin="
+msgstr "TimedLogin="
+
+#: C/index.docbook:1200(listitem/para)
+msgid ""
+"This is the user that should be logged in after a specified number of "
+"seconds of inactivity."
+msgstr ""
+"Ini adalah pengguna yang mesti dilogmasukkan setelah sekian detik tanpa "
+"aktivitas seperti yang dinyatakan."
+
+#: C/index.docbook:1204(listitem/para) C/index.docbook:1248(listitem/para)
+msgid ""
+"If the value ends with a vertical bar | (the pipe symbol), then GDM will "
+"execute the program specified and use whatever value is returned on standard "
+"out from the program as the user. The program is run with the DISPLAY "
+"environment variable set so that it is possible to specify the user in a per-"
+"display fashion. For example if the value is \"/usr/bin/getloginuser|\", "
+"then the program \"/usr/bin/getloginuser\" will be run to get the user value."
+msgstr ""
+"Bila nilai diakhiri dengan batang vertikal (simbol pipa), maka GDM akan "
+"menjalankan program yang dinyatakan dan memakai nilai apapun yang "
+"dikembalikan pada standard out dari program sebagai pengguna. Program "
+"dijalankan dengan variabel lingkungan DISPLAY ditata sehingga mungkin untuk "
+"menyatakan pengguna dengan cara  per-tampilan. Sebagai contoh bila nilainya "
+"adalah \"/usr/bin/getloginuser|\", maka program \"/usr/bin/getloginuser\" "
+"akan dijalankan untuk mendapat nilai pengguna."
+
+#: C/index.docbook:1218(varlistentry/term)
+msgid "TimedLoginDelay"
+msgstr "TimedLoginDelay"
+
+#: C/index.docbook:1220(listitem/synopsis)
+#, no-wrap
+msgid "TimedLoginDelay=30"
+msgstr "TimedLoginDelay=30"
+
+#: C/index.docbook:1221(listitem/para)
+msgid ""
+"Delay in seconds before the <filename>TimedLogin</filename> user will be "
+"logged in."
+msgstr ""
+"Tundaan dalam detik sebelum pengguna <filename>TimedLogin</filename> akan "
+"dilogmasukkan."
+
+#: C/index.docbook:1229(varlistentry/term)
+msgid "AutomaticLoginEnable"
+msgstr "AutomaticLoginEnable"
+
+#: C/index.docbook:1231(listitem/synopsis)
+#, no-wrap
+msgid "AutomaticLoginEnable=false"
+msgstr "AutomaticLoginEnable=false"
+
+#: C/index.docbook:1232(listitem/para)
+msgid ""
+"If true, the user given in <filename>AutomaticLogin</filename> should be "
+"logged in immediately. This feature is like timed login with a delay of 0 "
+"seconds."
+msgstr ""
+"Bila berisi true, pengguna yang diberikan dalam <filename>AutomaticLogin</"
+"filename> mesti dilogmasukkan seketika. Fitur ini seperti log masuk dengan "
+"tenggang waktu 0 detik."
+
+#: C/index.docbook:1241(varlistentry/term)
+msgid "AutomaticLogin"
+msgstr "AutomaticLogin"
+
+#: C/index.docbook:1243(listitem/synopsis)
+#, no-wrap
+msgid "AutomaticLogin="
+msgstr "AutomaticLogin="
+
+#: C/index.docbook:1244(listitem/para)
+msgid ""
+"This is the user that should be logged in immediately if "
+"<filename>AutomaticLoginEnable</filename> is true."
+msgstr ""
+"Ini adalah pengguna yang mesti seketika log masuk bila "
+"<filename>AutomaticLoginEnable</filename> berisi true."
+
+#: C/index.docbook:1262(varlistentry/term)
+msgid "User"
+msgstr "User"
+
+#: C/index.docbook:1264(listitem/synopsis)
+#, no-wrap
+msgid "User=gdm"
+msgstr "User=gdm"
+
+#: C/index.docbook:1265(listitem/para)
+msgid ""
+"The username under which the greeter and other GUI programs are run. Refer "
+"to the <filename>Group</filename> configuration key and to the \"Security-"
+"&gt;GDM User And Group\" section of this document for more information."
+msgstr ""
+"Nama pengguna yang menjalankan penyapa dan program GUI lainnya. Lihat kunci "
+"konfigurasi <filename>Group</filename> dan bagian \"Keamanan-&gt;Pengguna "
+"Dan Grup GDM\" dari dokumentasi ini untuk informasi lebih lanjut."
+
+#: C/index.docbook:1275(varlistentry/term)
+msgid "Group"
+msgstr "Group"
+
+#: C/index.docbook:1277(listitem/synopsis)
+#, no-wrap
+msgid "Group=gdm"
+msgstr "Group=gdm"
+
+#: C/index.docbook:1278(listitem/para)
+msgid ""
+"The group name under which the greeter and other GUI programs are run. Refer "
+"to the <filename>User</filename> configuration key and to the \"Security-&gt;"
+"GDM User And Group\" section of this document for more information."
+msgstr ""
+"Nama grup yang menjalankan penyapa dan program GUI lainnya. Lihat kunci "
+"konfigurasi <filename>Group</filename> dan bagian \"Keamanan-&gt;Pengguna "
+"Dan Grup GDM\" dari dokumentasi ini untuk informasi lebih lanjut."
+
+#: C/index.docbook:1290(sect3/title)
+msgid "Debug Options"
+msgstr "Opsi Debug"
+
+#: C/index.docbook:1293(variablelist/title)
+msgid "[debug]"
+msgstr "[debug]"
+
+#: C/index.docbook:1296(varlistentry/term)
+#: C/index.docbook:1427(varlistentry/term)
+msgid "Enable"
+msgstr "Enable"
+
+#: C/index.docbook:1298(listitem/synopsis)
+#: C/index.docbook:1429(listitem/synopsis)
+#, no-wrap
+msgid "Enable=false"
+msgstr "Enable=false"
+
+#: C/index.docbook:1299(listitem/para)
+msgid ""
+"To enable debugging, set the debug/Enable key to \"true\" in the "
+"<filename>&lt;etc&gt;/gdm/custom.conf</filename> file and restart GDM. Then "
+"debug output will be sent to the system log file (<filename>&lt;var&gt;/log/"
+"messages</filename> or <filename>&lt;var&gt;/adm/messages</filename> "
+"depending on your Operating System)."
+msgstr ""
+"Untuk memungkinkan pengawakutuan, atur kunci debug/Enable ke \"true\" dalam "
+"berkas <filename>&lt;etc&gt;/gdm/custom.conf</filename> dan mulai ulang GDM. "
+"Maka keluaran pengawakutuan akan kemudian dikirim ke  berkas log sistem "
+"(<filename>&lt;var&gt;/log/messages</filename> atau <filename>&lt;var&gt;/"
+"adm/messages</filename> bergantung kepada Sistem Operasi Anda)."
+
+#: C/index.docbook:1314(sect3/title)
+msgid "Greeter Options"
+msgstr "Opsi Greeter"
+
+#: C/index.docbook:1317(variablelist/title)
+msgid "[greeter]"
+msgstr "[greeter]"
+
+#: C/index.docbook:1320(varlistentry/term)
+msgid "IncludeAll"
+msgstr "IncludeAll"
+
+#: C/index.docbook:1322(listitem/synopsis)
+#, no-wrap
+msgid "IncludeAll=true"
+msgstr "IncludeAll=true"
+
+#: C/index.docbook:1323(listitem/para)
+msgid ""
+"If true, then the face browser will show all users on the local machine. If "
+"false, the face browser will only show users who have recently logged in."
+msgstr ""
+"Bila berisi true, maka peramban wajah akan menampilkan semua pengguna pada "
+"mesin lokal. Bila berisi false, maka peramban wajah hanya akan menampilkan "
+"pengguna yang baru-baru ini log masuk."
+
+#: C/index.docbook:1329(listitem/para)
+msgid ""
+"When this key is true, GDM will call fgetpwent() to get a list of local "
+"users on the system. Any users with a user id less than 500 (or 100 if "
+"running on Oracle Solaris) are filtered out. The Face Browser also will "
+"display any users that have previously logged in on the system (for example "
+"NIS/LDAP users). It gets this list via calling the <command>ck-history</"
+"command> ConsoleKit interface. It will also filter out any users which do "
+"not have a valid shell (valid shells are any shell that getusershell() "
+"returns - /sbin/nologin or /bin/false are considered invalid shells even if "
+"getusershell() returns them)."
+msgstr ""
+"Bila kunci ini berisi true, GDM akan memanggil fgetpwent() untuk memperoleh "
+"daftar pengguna lokal pada sistem. Sebarang pengguna dengan id pengguna "
+"kurang dari 500 (atau 100 bila menjalankan Oracle Solaris) tak akan lolos "
+"saringan. Peramban Wajah juga akan menampilkan sebarang pengguna yang "
+"sebelumnya log masuk ke sistem (sebagai contoh pengguna NIS/LDAP). Daftar "
+"ini didapat dari pemanggilan antar muka ConsoleKit <command>ck-history</"
+"command>. Ini juga akan menyingkirkan pengguna yang tak memiliki shell yang "
+"valid (shell valid adalah sebarang shell yang dikembalikan oleh getusershell"
+"() - /sbin/nologin atau /bin/false dianggap sebagai shell yang tak valid "
+"walaupun getusershell() mengembalikan mereka)."
+
+#: C/index.docbook:1343(listitem/para)
+msgid ""
+"If false, then GDM more simply only displays users that have previously "
+"logged in on the system (local or NIS/LDAP users) by calling the <command>ck-"
+"history</command> ConsoleKit interface."
+msgstr ""
+"Bila berisi false, maka GDM hanya sekedar menampilkan pengguna yang "
+"sebelumnya pernah log masuk ke sistem (pengguna lokal atau NIS/LDAP) dengan "
+"memanggil antar muka ConsoleKit <command>ck-history</command>."
+
+#: C/index.docbook:1352(varlistentry/term)
+msgid "Include"
+msgstr "Include"
+
+#: C/index.docbook:1354(listitem/synopsis)
+#, no-wrap
+msgid "Include="
+msgstr "Include="
+
+#: C/index.docbook:1355(listitem/para)
+msgid ""
+"Set to a list of users to always include in the Face Browser. This value is "
+"set to a list of users separated by commas. By default, the value is empty."
+msgstr ""
+"Diisi dengan daftar pengguna yang selalu disertakan dalam Peramban Wajah. "
+"Nilai ini diisi dengan daftar pengguna yang dipisah dengan koma. Nilai "
+"bawaan adalah kosong."
+
+#: C/index.docbook:1364(varlistentry/term)
+msgid "Exclude"
+msgstr "Exclude"
+
+#: C/index.docbook:1366(listitem/synopsis)
+#, no-wrap
+msgid "Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap"
+msgstr "Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap"
+
+#: C/index.docbook:1367(listitem/para)
+msgid ""
+"Set to a list of users to always exclude in the Face Browser. This value is "
+"set to a list of users separated by commas. Note that the setting in the "
+"<filename>custom.conf</filename> overrides the default value, so if you wish "
+"to add additional users to the list, then you need to set the value to the "
+"default value with additional users appended to the list."
+msgstr ""
+"Diisi dengan daftar pengguna yang selalu tidak disertakan dalam Peramban "
+"Wajah. Nilai ini diisi dengan daftar pengguna yang dipisah dengan koma. "
+"Perhatikan bahwa pengaturan dalam <filename>custom.conf</filename> menimpa "
+"nilai bawaan, sehingga ketika Anda hendak menambahkan pengguna ke daftar, "
+"maka Anda perlu menata nilai ke nilai bawaan dengan pengguna tambahan "
+"ditambahkan ke daftar."
+
+#: C/index.docbook:1381(sect3/title)
+msgid "Security Options"
+msgstr "Opsi Keamanan"
+
+#: C/index.docbook:1384(variablelist/title)
+msgid "[security]"
+msgstr "[security]"
+
+#: C/index.docbook:1387(varlistentry/term)
+msgid "DisallowTCP"
+msgstr "DisallowTCP"
+
+#: C/index.docbook:1389(listitem/synopsis)
+#, no-wrap
+msgid "DisallowTCP=true"
+msgstr "DisallowTCP=true"
+
+#: C/index.docbook:1390(listitem/para)
+msgid ""
+"If true, then always append <filename>-nolisten tcp</filename> to the "
+"command line when starting attached Xservers, thus disallowing TCP "
+"connection. This is a more secure configuration if you are not using remote "
+"connections."
+msgstr ""
+"Bila berisi true, maka selalu menambahkan <filename>-nolisten tcp</filename> "
+"ke baris perintah ketika memulai Xserver yang dicantol, sehingga melarang "
+"koneksi TCP. Ini konfigurasi yang lebih aman bila Anda tak memakai koneksi "
+"jauh."
+
+#: C/index.docbook:1402(sect3/title)
+msgid "XDCMP Support"
+msgstr "Dukungan XDMCP"
+
+#: C/index.docbook:1405(variablelist/title)
+msgid "[xdmcp]"
+msgstr "[xdmcp]"
+
+#: C/index.docbook:1408(varlistentry/term)
+msgid "DisplaysPerHost"
+msgstr "DisplaysPerHost"
+
+#: C/index.docbook:1410(listitem/synopsis)
+#, no-wrap
+msgid "DisplaysPerHost=1"
+msgstr "DisplaysPerHost=1"
+
+#: C/index.docbook:1411(listitem/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 this "
+"value."
+msgstr ""
+"Untuk mencegah penyerang memenuhi antrian yang tertunda, GDM hanya "
+"akanmengijinkan satu koneksi bagi setiap komputer jauh. Bila Anda ingin "
+"menyediakanlayanan tampilan ke komputer yang memiliki lebih dari satu layar, "
+"Anda mesti menaikkan nilai ini."
+
+#: C/index.docbook:1418(listitem/para)
+msgid ""
+"Note that the number of attached DISPLAYS allowed is not limited. Only "
+"remote connections via XDMCP are limited by this configuration option."
+msgstr ""
+"Perhatikan bahwa cacah DISPLAY tercantol yang diijinkan tak dibatasi. Hanya "
+"koneksi jauh melalui XDMCP yang dibatasi oleh opsi konfigurasi ini."
+
+#: C/index.docbook:1430(listitem/para)
+msgid ""
+"Setting this to true enables XDMCP support allowing remote displays/X "
+"terminals to be managed by GDM."
+msgstr ""
+"Menata ini ke true memungkinkan dukungan XDMCP yang mengijinkan tampilan "
+"jauh/terminal X dikelola oleh GDM."
+
+#: C/index.docbook:1435(listitem/para)
+msgid ""
+"<filename>gdm</filename> listens for requests on UDP port 177. See the Port "
+"option for more information."
+msgstr ""
+"<filename>gdm</filename> mendengarkan permintaan pada UDP port 177. Lihat "
+"opsi Port untuk informasi lebih jauh."
+
+#: C/index.docbook:1440(listitem/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 ""
+"Bila GDM dikompail untuk mendukungnya, akses dari tampilan jauh dapat "
+"dikendalikan memakai pustaka TCP Wrapper. Nama layanan adalah <filename>gdm</"
+"filename>"
+
+#: C/index.docbook:1448(para/screen)
+#, no-wrap
+#| msgid ""
+#| "\n"
+#| "gdm: .your.domain\n"
+msgid ""
+"\n"
+"gdm:.my.domain\n"
+msgstr ""
+"\n"
+"gdm:.my.domain\n"
+
+#: C/index.docbook:1446(listitem/para)
+#| msgid ""
+#| "You should add <screen>\n"
+#| "gdm:.my.domain\n"
+#| "</screen> to your <filename>&lt;etc&gt;/hosts.allow</filename>, depending "
+#| "on your TCP Wrappers configuration. See the <ulink type=\"help\" url="
+#| "\"man:hosts.allow\">hosts.allow</ulink> man page for details."
+msgid ""
+"You should add <_:screen-1/> to your <filename>&lt;etc&gt;/hosts.allow</"
+"filename>, depending on your TCP Wrappers configuration. See the <ulink type="
+"\"help\" url=\"man:hosts.allow\">hosts.allow</ulink> man page for details."
+msgstr ""
+"Ada mesti menambah <_:screen-1/> ke <filename>&lt;etc&gt;/hosts.allow</"
+"filename> Anda, bergantung kepada konfigurasi TCP Wrapper Anda. Lihat "
+"halaman man <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow</ulink> "
+"untuk rinciannya."
+
+#: C/index.docbook:1457(listitem/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 ""
+"Mohon diperhatikan bahwa XDMCP bukan protokol yang aman dan ide yang bagus "
+"untuk memblokir UDP port 177 pada firewall Anda kecuali Anda memang "
+"memerlukannya."
+
+#: C/index.docbook:1466(varlistentry/term)
+msgid "HonorIndirect"
+msgstr "HonorIndirect"
+
+#: C/index.docbook:1468(listitem/synopsis)
+#, no-wrap
+msgid "HonorIndirect=true"
+msgstr "HonorIndirect=true"
+
+#: C/index.docbook:1469(listitem/para)
+msgid ""
+"Enables XDMCP INDIRECT choosing (i.e. remote execution of "
+"<filename>gdmchooser</filename>) for X-terminals which do not supply their "
+"own display browser."
+msgstr ""
+"Fungsikan pemilihan XDMCP INDIRECT (yaitu eksekusi jauh dari "
+"<filename>gdmchooser</filename>) bagi X-terminal yang tak menyediakan "
+"peramban tampilannya sendiri."
+
+#: C/index.docbook:1478(varlistentry/term)
+msgid "MaxPending"
+msgstr "MaxPending"
+
+#: C/index.docbook:1480(listitem/synopsis)
+#, no-wrap
+msgid "MaxPending=4"
+msgstr "MaxPending=4"
+
+#: C/index.docbook:1481(listitem/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 ""
+"Untuk menghindari serangan penyangkalan layanan, GDM memiliki antrian "
+"sambungan yang tertunda berukuran tetap. Hanya MaxPending tampilan yang "
+"dapat dimulai pada saat yang sama."
+
+#: C/index.docbook:1487(listitem/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 ""
+"Mohon dicatat bahwa parameter ini tak membatasi cacah tampilan jauh yang "
+"dapat dikelola. Ini hanya membatasi cacah tampilan yang mengawali koneksi "
+"secara simultan."
+
+#: C/index.docbook:1496(varlistentry/term)
+msgid "MaxSessions"
+msgstr "MaxSessions"
+
+#: C/index.docbook:1498(listitem/synopsis)
+#, no-wrap
+msgid "MaxSessions=16"
+msgstr "MaxSessions=16"
+
+#: C/index.docbook:1499(listitem/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 ""
+"Menentukan cacah maksimum dari koneksi tampilan jauh yang akan dikelola "
+"secara simultan. Yaitu cacah total tampilan jauh yang dapat memakai host "
+"Anda."
+
+#: C/index.docbook:1508(varlistentry/term)
+msgid "MaxWait"
+msgstr "MaxWait"
+
+#: C/index.docbook:1510(listitem/synopsis)
+#, no-wrap
+msgid "MaxWait=30"
+msgstr "MaxWait=30"
+
+#: C/index.docbook:1511(listitem/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 ""
+"Ketika GDM siap untuk mengelola suatu tampilan, suatu paket ACCEPT dikirim "
+"kepadanya, yang memuat id sesi unik yang akan dipakai dalam percakapan XDMCP "
+"di masa mendatang."
+
+#: C/index.docbook:1517(listitem/para)
+msgid ""
+"GDM will then place the session id in the pending queue waiting for the "
+"display to respond with a MANAGE request."
+msgstr ""
+"GDM lalu akan menempatkan id sesi ke dalam antrian tertunda yang menunggu "
+"tampilan merespon dengan permintaan MANAGE."
+
+#: C/index.docbook:1522(listitem/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 ""
+"Bila tak ada respon yang diterima dalam MaxWait detik, GDM akan menyatakan "
+"bahwa tampilan mati dan menghapusnya dari antrian tertunda, membebaskan slot "
+"bagi tampilan lain."
+
+#: C/index.docbook:1531(varlistentry/term)
+msgid "MaxWaitIndirect"
+msgstr "MaxWaitIndirect"
+
+#: C/index.docbook:1533(listitem/synopsis)
+#, no-wrap
+msgid "MaxWaitIndirect=30"
+msgstr "MaxWaitIndirect=30"
+
+#: C/index.docbook:1534(listitem/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 ""
+"Parameter MaxWaitIndirect menentukan berapa detik maksimum antara waktu "
+"ketika pengguna memilih suatu host dan query tak langsung kelanjutannya "
+"dimana pengguna tersambung ke host. Ketika tenggang waktu dilampaui, "
+"informasi tentang host yang dipilih dilupakan dan slot tak langsung "
+"dibebaskan bagi tampilan lain. Informasi mungkin dilupakan lebih awal bila "
+"ada lebih banyak host mencoba mengirim query tak langsung daripada "
+"<filename>MaxPendingIndirect</filename>."
+
+#: C/index.docbook:1548(varlistentry/term)
+msgid "PingIntervalSeconds"
+msgstr "PingIntervalSeconds"
+
+#: C/index.docbook:1550(listitem/synopsis)
+#, no-wrap
+msgid "PingIntervalSeconds=60"
+msgstr "PingIntervalSeconds=60"
+
+#: C/index.docbook:1551(listitem/para)
+msgid ""
+"If the Xserver does not respond in the specified number of seconds, then the "
+"connection is stopped and the session ended. When this happens the slave "
+"daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied "
+"this setting by 2, so it may be necessary to increase the timeout if "
+"upgrading from GDM 2.20 and earlier to a newer version."
+msgstr ""
+"Bila Xserver tak merespon dalam sekian detik yang dinyatakan, maka koneksi "
+"dihentikan dan sesi diakhiri. Ketika ini terjadi daemon slave mati dengan "
+"sinyal ALARM. Perhatikan bahwa GDM 2.20 dan sebelumnya mengalikan 2 "
+"pengaturan ini, sehingga mungkin perlu menaikkan tenggang waktu bila "
+"meningkatkan dari GDM 2.20 dan sebelumnya ke versi yang lebih baru."
+
+#: C/index.docbook:1560(listitem/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 than 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 ""
+"Perhatikan bahwa GDM di masa lalu biasa memiliki kunci konfigurasi "
+"<filename>PingInterval</filename> dalam satuan menit. Untuk kebanyakan "
+"tujuan Anda akan menginginkan pengaturan ini agar kurang dari satu meni. "
+"Namun karena dalam kebanyakan kasus dimana XDMCP akan dipakai (seperti pada "
+"lab terminal), lag lebih dari sekitar 15 detik sesungguhnya berarti bahwa "
+"terminal dimatikan atau dimulai ulang dan Anda ingin mengakhiri sesi "
+"tersebut."
+
+#: C/index.docbook:1573(varlistentry/term)
+msgid "Port"
+msgstr "Port"
+
+#: C/index.docbook:1575(listitem/synopsis)
+#, no-wrap
+msgid "Port=177"
+msgstr "Port=177"
+
+#: C/index.docbook:1576(listitem/para)
+msgid ""
+"The UDP port number <filename>gdm</filename> should listen to for XDMCP "
+"requests. Do not change this unless you know what you are doing."
+msgstr ""
+"Nomor port UDP yang mesti didengar oleh <filename>gdm</filename> bagi "
+"permintaan XDMCP. Jangan mengubah ini kecuali Anda tahu apa yang Anda "
+"lakukan."
+
+#: C/index.docbook:1585(varlistentry/term)
+msgid "Willing"
+msgstr "Willing"
+
+#: C/index.docbook:1587(listitem/synopsis)
+#, no-wrap
+msgid "Willing=&lt;etc&gt;/gdm/Xwilling"
+msgstr "Willing=&lt;etc&gt;/gdm/Xwilling"
+
+#: C/index.docbook:1588(listitem/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 does not 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 ""
+"Ketika mesin mengirim balik paket WILLING setelah QUERY, dia mengirim string "
+"yang memberikan status terkini dari server ini. Pesan baku adalah ID sistem, "
+"tapi mungkin untuk membuat skrip yang menampilkan pesan ubahan. Bila skrip "
+"ini tak ada atau kunci ini kosong maka pesan baku yang dikirim. Bila skrip "
+"ini sukses dan menghasilkan suatu keluaran, baris pertama keluaran yang akan "
+"dikirim (dan hanya baris pertama). Itu dijalankan paling sering sekali dalam "
+"3 detik untuk mencegah kemungkinan denial of service dengan membanjiri mesin "
+"dengan paket QUERY."
+
+#: C/index.docbook:1607(sect2/title)
+msgid "Simple Greeter Configuration"
+msgstr "Konfigurasi Penyapa Sederhana"
+
+#: C/index.docbook:1609(sect2/para)
+msgid ""
+"The GDM default greeter is called the simple Greeter and is configured via "
+"GConf. Default values are stored in GConf in the <filename>gdm-simple-"
+"greeter.schemas</filename> file. These defaults can be overridden if the "
+"\"gdm\" user has a writable $HOME directory to store GConf settings. These "
+"values can be edited using the <command>gconftool-2</command> or "
+"<command>gconf-editor</command> programs. The following configuration "
+"options are supported:"
+msgstr ""
+"Penyapa bawaan GDM dinamai Simple Greeter dan ditata melalui GConf. Nilai "
+"bawaan disimpan dalam GConf pada berkas <filename>gdm-simple-greeter."
+"schemas</filename>. Nilai bawaan ini dapat ditimpa bila pengguna \"gdm\" "
+"memiliki direktori $HOME yang dapat ditulisi untuk menyimpan tatanan GConf. "
+"Nilai-nilai ini dapat disunting memakai program <command>gconftool-2</"
+"command> atau <command>gconf-editor</command>. Opsi konfigurasi berikut "
+"didukung:"
+
+#: C/index.docbook:1620(variablelist/title)
+msgid "Greeter Configuration Keys"
+msgstr "Kunci Konfigurasi Penyapa"
+
+#: C/index.docbook:1623(varlistentry/term)
+msgid "/apps/gdm/simple-greeter/banner_message_enable"
+msgstr "/apps/gdm/simple-greeter/banner_message_enable"
+
+#: C/index.docbook:1625(listitem/synopsis)
+#: C/index.docbook:1646(listitem/synopsis)
+#: C/index.docbook:1657(listitem/synopsis)
+#: C/index.docbook:1722(listitem/synopsis)
+#: C/index.docbook:1787(listitem/synopsis)
+#: C/index.docbook:1798(listitem/synopsis)
+#: C/index.docbook:1809(listitem/synopsis)
+#: C/index.docbook:1820(listitem/synopsis)
+#, no-wrap
+msgid "false (boolean)"
+msgstr "false (boolean)"
+
+#: C/index.docbook:1626(listitem/para)
+msgid "Controls whether the banner message text is displayed."
+msgstr "Mengendalikan apakah teks pesan banner ditampilkan."
+
+#: C/index.docbook:1633(varlistentry/term)
+msgid "/apps/gdm/simple-greeter/banner_message_text"
+msgstr "/apps/gdm/simple-greeter/banner_message_text"
+
+#: C/index.docbook:1635(listitem/synopsis)
+#, no-wrap
+msgid "NULL (string)"
+msgstr "NULL (string)"
+
+#: C/index.docbook:1636(listitem/para)
+msgid "Specifies the text banner message to show on the greeter window."
+msgstr "Menyatakan pesan banner teks untuk ditampilkan pada jendela penyapa."
+
+#: C/index.docbook:1644(varlistentry/term)
+msgid "/apps/gdm/simple-greeter/disable_restart_buttons"
+msgstr "/apps/gdm/simple-greeter/disable_restart_buttons"
+
+#: C/index.docbook:1647(listitem/para)
+msgid "Controls whether to show the restart buttons in the login window."
+msgstr ""
+"Mengendalikan apakah menampilkan tombol hidupkan ulang komputer pada jendela "
+"log masuk."
+
+#: C/index.docbook:1655(varlistentry/term)
+msgid "/apps/gdm/simple-greeter/disable_user_list"
+msgstr "/apps/gdm/simple-greeter/disable_user_list"
+
+#: C/index.docbook:1658(listitem/para)
+msgid ""
+"If true, then the face browser with known users is not shown in the login "
+"window."
+msgstr ""
+"Bila true, maka peramban wajah dengan pengguna yang dikenal tak ditampilkan "
+"di jendela log masuk."
+
+#: C/index.docbook:1666(varlistentry/term)
+msgid "/apps/gdm/simple-greeter/logo_icon_name"
+msgstr "/apps/gdm/simple-greeter/logo_icon_name"
+
+#: C/index.docbook:1668(listitem/synopsis)
+#, no-wrap
+msgid "computer (string)"
+msgstr "komputer (string)"
+
+#: C/index.docbook:1669(listitem/para)
+msgid "Set to the themed icon name to use for the greeter logo."
+msgstr "Tata ke nama ikon ditemakan untuk dipakai bagi logo penyapa."
+
+#: C/index.docbook:1676(varlistentry/term)
+msgid "/apps/gdm/simple-greeter/recent-languages"
+msgstr "/apps/gdm/simple-greeter/recent-languages"
+
+#: C/index.docbook:1678(listitem/synopsis)
+#: C/index.docbook:1700(listitem/synopsis)
+#, no-wrap
+msgid "[] (string list)"
+msgstr "[] (daftar string)"
+
+#: C/index.docbook:1679(listitem/para)
+msgid ""
+"Set to a list of languages to be shown by default in the login window. "
+"Default value is \"[]\". With the default setting only the system default "
+"language is shown and the option \"Other...\" which pops-up a dialog box "
+"showing a full list of available languages which the user can select."
+msgstr ""
+"Tata ke daftar bahasa yang akan ditampilkan secara baku dalam jendela log "
+"masuk. Nilai baku adalah \"[]\". Dengan tatanan bawaan hanya bahasa bawaan "
+"sistem yang ditampilkan dan opsi \"Lainnya...\" yang memunculkan suatu kotak "
+"dialog yang menampilkan daftar lengkap bahasa yang tersedia tempat pengguna "
+"dapat memilih."
+
+#: C/index.docbook:1687(listitem/para)
+msgid ""
+"Users are not intended to change this setting by hand. Instead GDM keeps "
+"track of any languages selected in this configuration key, and will show "
+"them in the language combo box along with the \"Other...\" choice. This way, "
+"commonly selected languages are easier to select."
+msgstr ""
+"Pengguna tak diharapkan mengubah pengaturan ini secara manual. Sebagai "
+"gantinya, GDM melacak sebarang bahasa yang dipilih dalam kunci konfigurasi "
+"ini, dan akan menampilkan mereka dalam kotak kombo bahasa bersama dengan "
+"pilihan \"Lainnya...\". Dengan cara ini, bahasa yang umum dipilih akan lebih "
+"mudah dipilih."
+
+#: C/index.docbook:1698(varlistentry/term)
+msgid "/apps/gdm/simple-greeter/recent-layouts"
+msgstr "/apps/gdm/simple-greeter/recent-layouts"
+
+#: C/index.docbook:1701(listitem/para)
+msgid ""
+"Set to a list of keyboard layouts to be shown by default in the login panel. "
+"Default value is \"[]\". With the default setting only the system default "
+"keyboard layout is shown and the option \"Other...\" which pops-up a dialog "
+"box showing a full list of available keyboard layouts which the user can "
+"select."
+msgstr ""
+"Ditata ke daftar tata letak papan tik yang secara baku akan ditampilkan pada "
+"panel log masuk. Nilai bawaan adalah \"[]\". Dengan pengaturan baku hanya "
+"tata letak papan tik bawaan sistem yang ditampilkan dan opsi \"Lainnya...\" "
+"yang memunculkan kotak dialog yang menunjukkan daftar lengkap tata letak "
+"papan tik yang tersedia yang dapat dipilih oleh pengguna."
+
+#: C/index.docbook:1709(listitem/para)
+msgid ""
+"Users are not intended to change this setting by hand. Instead GDM keeps "
+"track of any keyboard layouts selected in this configuration key, and will "
+"show them in the keyboard layout combo box along with the \"Other...\" "
+"choice. This way, commonly selected keyboard layouts are easier to select."
+msgstr ""
+"Pengguna tak diharapkan mengubah pengaturan ini secara manual. Sebagai "
+"gantinya, GDM melacak sebarang tata letak papan tik yang dipilih dalam kunci "
+"konfigurasi ini, dan akan menampilkan mereka dalam kotak kombo tata letak "
+"papan tik bersama dengan pilihan \"Lainnya...\". Dengan cara ini, tata letak "
+"papan tik yang umum dipilih akan lebih mudah dipilih."
+
+#: C/index.docbook:1720(varlistentry/term)
+msgid "/apps/gdm/simple-greeter/wm_use_compiz"
+msgstr "/apps/gdm/simple-greeter/wm_use_compiz"
+
+#: C/index.docbook:1723(listitem/para)
+msgid ""
+"Controls whether compiz is used as the window manager instead of metacity."
+msgstr ""
+"Mengendalikan apakah compiz dipakai sebagai manajer jendela menggantikan "
+"metacity."
+
+#: C/index.docbook:1733(sect2/title)
+msgid "Accessibility Configuration"
+msgstr "Konfigurasi Aksesibilitas"
+
+#: C/index.docbook:1735(sect2/para)
+msgid ""
+"This section describes the accessibility configuration options available in "
+"GDM."
+msgstr ""
+"Seksi ini menjelaskan opsi konfigurasi aksesibilitas yang tersedia dalam GDM."
+
+#: C/index.docbook:1741(sect3/title)
+msgid "GDM Accessibility Dialog And GConf Keys"
+msgstr "Dialog Aksesibilitas GDM Dan Kunci GConf"
+
+#: C/index.docbook:1743(sect3/para)
+msgid ""
+"The GDM greeter panel at the login screen displays an accessibility icon. "
+"Clicking on that icon opens the GDM Accessibility Dialog. In the GDM "
+"Accessibility Dialog, there is a list of checkboxes, so the user can enable "
+"or disable the associated assistive tools."
+msgstr ""
+"Panel penyapa GDM pada layar log masuk menampilkan ikon aksesibilitas. Bila "
+"ikon tersebut diklik akan membuka Dialog Aksesibilitas GDM. Dalam Dialog "
+"Aksesibilitas GDM, ada daftar kotak contreng, sehingga pengguna dapat "
+"mengaktifkan atau menonaktifkan perkakas bantu yang terkait."
+
+#: C/index.docbook:1750(sect3/para)
+msgid ""
+"The checkboxes that correspond to the on-screen keyboard, screen magnifier "
+"and screen reader assistive tools act on the three GConf keys that are "
+"described in the next section of this document. By enabling or disabling "
+"these checkboxes, the associated GConf key is set to \"true\" or \"false\". "
+"When the GConf key is set to true, the assistive tools linked to this GConf "
+"key are launched. When the GConf key is set to \"false\", any running "
+"assistive tool linked to this GConf key are terminated. These GConf keys are "
+"not automatically reset to a default state after the user has logged in. "
+"Consequently, the assistive tools that were running during the last GDM "
+"login session will automatically be launched at the next GDM login session."
+msgstr ""
+"Kotak contreng yang terkait dengan perkakas bantu papan tik pada layar, "
+"pembesar layar, dan pembaca layar beraksi pada tiga kunci GConf yang "
+"diuraikan pada seksi selanjutnya dari dokumen ini. Dengan mengaktifkan atau "
+"mematikan kotak-kotak contreng ini, kunci GConf yang terkait akan ditata ke "
+"\"true\" atau \"false\". Ketika kunci GConf diisi dengan true, perkakas "
+"bantu yang terkait ke kunci GConf ini diluncurkan. Ketika kunci GConf diisi "
+"dengan \"false\", perkakas bantu terkait kunci GConf ini diakhiri bila "
+"berjalan. Kunci-kunci GConf ini tak direset ke keadaan bawaan secara "
+"otomatis setelah pengguna log masuk. Konsekuensinya, perkakas bantu yang "
+"berjalan selama sesi log masuk terakhir akan otomatis diluncurkan pada sesi "
+"log masuk selanjutnya."
+
+#: C/index.docbook:1764(sect3/para)
+msgid ""
+"The other checkboxes in the GDM Accessibility Dialog do not have "
+"corresponding GConf keys because no additional program is launched to "
+"provide the accessibility features that they offer. These other options "
+"correspond to accessibility features that are provided by the Xserver, which "
+"is always running during the GDM session."
+msgstr ""
+"Kotak contreng lain dalam Dialog Aksesibilitas GDM tak memiliki kunci GConf "
+"yang berkaitan karena tak ada program tambahan yang diluncurkan untuk "
+"menyediakan fitur aksesibilitas yang mereka tawarkan. Ops lain ini berkaitan "
+"dengan fitur aksesibilitas yang disediakan oleh Xserver, yang selalu "
+"berjalan selama sesi GDM."
+
+#: C/index.docbook:1774(sect3/title)
+msgid "Accessibility GConf Keys"
+msgstr "Kunci GConf Aksesibilitas"
+
+#: C/index.docbook:1776(sect3/para)
+msgid ""
+"GDM offers the following GConf keys to control its accessibility features:"
+msgstr ""
+"GDM menawarkan kunci GConf berikut untuk mengendalikan fitur "
+"aksesibilitasnya:"
+
+#: C/index.docbook:1782(variablelist/title)
+msgid "GDM Configuration Keys"
+msgstr "Kunci Konfigurasi GDM"
+
+#: C/index.docbook:1785(varlistentry/term)
+msgid "/desktop/gnome/interface/accessibility"
+msgstr "/desktop/gnome/interface/accessibility"
+
+#: C/index.docbook:1788(listitem/para)
+msgid ""
+"Controls whether the Accessibility infrastructure will be started with the "
+"GDM GUI. This is needed for many accessibility technology programs to work."
+msgstr ""
+"Mengendalikan apakah infrastruktur Aksesibilitas akan dimulai dengan GUI "
+"GDM. Ini diperlukan oleh banyak program teknologi aksesibilitas agar bekerja."
+
+#: C/index.docbook:1796(varlistentry/term)
+msgid "/desktop/gnome/applications/at/screen_magnifier_enabled"
+msgstr "/desktop/gnome/applications/at/screen_magnifier_enabled"
+
+#: C/index.docbook:1799(listitem/para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is a screen magnifier application."
+msgstr ""
+"Bila ditata, alat asistif yang dikaitkan ke kunci GConf ini akan dimulai "
+"dengan program GUI GDM. Secara baku ini adalah aplikasi pembesaran layar."
+
+#: C/index.docbook:1807(varlistentry/term)
+msgid "/desktop/gnome/applications/at/screen_keyboard_enabled"
+msgstr "/desktop/gnome/applications/at/screen_keyboard_enabled"
+
+#: C/index.docbook:1810(listitem/para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is an on-screen keyboard "
+"application."
+msgstr ""
+"Bila ditata, alat asistif yang dikaitkan ke kunci GConf ini akan dimulai "
+"dengan program GUI GDM. Secara baku ini adalah aplikasi papan tik di layar."
+
+#: C/index.docbook:1818(varlistentry/term)
+msgid "/desktop/gnome/applications/at/screen_reader_enabled"
+msgstr "/desktop/gnome/applications/at/screen_reader_enabled"
+
+#: C/index.docbook:1821(listitem/para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is a screen reader application."
+msgstr ""
+"Bila ditata, alat asistif yang dikaitkan ke kunci GConf ini akan dimulai "
+"dengan program GUI GDM. Secara baku ini adalah aplikasi pembaca layar."
+
+#: C/index.docbook:1832(sect3/title)
+msgid "Linking GConf Keys to Accessbility Tools"
+msgstr "Mengaitkan Kunci GConf ke Alat Aksesibilitas"
+
+#: C/index.docbook:1834(sect3/para)
+msgid ""
+"For the screen_magnifier_enabled, the screen_keyboard_enabled, and the "
+"screen_reader_enabled GConf keys, the assistive tool which gets launched "
+"depends on the desktop files located in the GDM autostart directory as "
+"described in the \"Autostart Configuration\" section of this manual. Any "
+"desktop file in the GDM autostart directory can be linked to these GConf key "
+"via specifying that GConf key in the AutostartCondition value in the desktop "
+"file. So the exact AutostartCondition line in the desktop file could be one "
+"of the following:"
+msgstr ""
+"Untuk kunci GConf screen_magnifier_enabled, screen_keyboard_enabled, dan "
+"screen_reader_enabled, perkakas asistif yang diluncurkan bergantung kepada "
+"berkas desktop yang terletak di direktori autostart GDM sebagaimana "
+"diuraikan dalam bagian \"Konfigurasi Mulai Otomatis\" dari manual ini. "
+"Sebarang berkas desktop dalam direktori autostart GDM dapat ditautkan ke "
+"kunci GConf ini dengan menyatakan kunci GConf itu dalam nilai "
+"AutostartCondition pada berkas desktop. Maka baris AutostartCondition dalam "
+"berkas desktop secara persis bisa salah satu dari berikut:"
+
+#: C/index.docbook:1846(sect3/screen)
+#, no-wrap
+msgid ""
+"\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled\n"
+msgstr ""
+"\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled\n"
+
+#: C/index.docbook:1852(sect3/para)
+msgid ""
+"When an accessibility key is true, then any program which is linked to that "
+"key in a GDM autostart desktop file will be launched (unless the Hidden key "
+"is set to true in that desktop file). A single GConf key can even start "
+"multiple assistive tools if there are multiple desktop files with this "
+"AutostartCondition in the GDM autostart directory."
+msgstr ""
+"Ketika suatu kunci aksesibilitas berisi true, maka sebarang program yang "
+"ditautkan ke kunci tersebut dalam suatu berkas desktop autostart GDM akan "
+"diluncurkan (kecuali kunci Tersembunyi diisi true dalam berkas desktop "
+"tersebut). Suatu kunci GConf tunggal bahkan dapat memulai beberapa perkakas "
+"asistif bila ada beberapa berkas desktop dengan AutostartCondition ini dalam "
+"direktori autostart GDM."
+
+#: C/index.docbook:1862(sect3/title)
+msgid "Example Of Modifying Accessibility Tool Configuration"
+msgstr "Contoh Pengubahan Konfigurasi Alat Aksesibilitas"
+
+#: C/index.docbook:1864(sect3/para)
+msgid ""
+"For example, if GNOME is distributed with GOK as the default on-screen "
+"keyboard, then this could be replaced with a different program if desired. "
+"To replace GOK with the on-screen keyboard application \"onboard\" and "
+"additionally activate the assistive tool \"mousetweaks\" for dwelling "
+"support, then the following configuration is needed."
+msgstr ""
+"Sebagai contoh, bila GNOME didistribusikan dengan GOK sebagai papan tik pada "
+"layar bawaan, maka ini dapat digantikan dengan program lain bila "
+"dikehendaki. Untuk mengganti GOK dengan aplikasi papan tik pada layar "
+"\"onboard\" dan sebagai tambah mengaktifkan perkakas asistif \"mousetweaks\" "
+"untuk dukungan dwelling, maka konfigurasi berikut diperlukan."
+
+#: C/index.docbook:1872(sect3/para)
+msgid ""
+"Create a desktop file for onboard and a second one for mousetweaks; for "
+"example, onboard.desktop and mousetweaks.desktop. These files must be placed "
+"in the GDM autostart directory and be in the format as explained in the "
+"\"Autostart Configuration\" section of this document."
+msgstr ""
+"Buatlah suatu berkas desktop bagi onboard dan yang kedua bagi mousetweaks; "
+"sebagai contoh, onboard.desktop dan mousetweaks.desktop. Berkas-berkas ini "
+"mesti ditempatkan dalam direktori autostart GDM dan dalam format yang "
+"diterangkan dalam bagian \"Konfigurasi Mulai Otomatis\" dari dokumen ini."
+
+#: C/index.docbook:1880(sect3/para)
+msgid "The following is an example <filename>onboard.desktop</filename> file:"
+msgstr "Berikut ini adalah contoh berkas <filename>onboard.desktop</filename>:"
+
+#: C/index.docbook:1884(sect3/screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Onboard Onscreen Keyboard\n"
+"Comment=Use an on-screen keyboard\n"
+"TryExec=onboard\n"
+"Exec=onboard --size 500x180 -x 20 -y 10\n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+msgstr ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Onboard Onscreen Keyboard\n"
+"Comment=Use an on-screen keyboard\n"
+"TryExec=onboard\n"
+"Exec=onboard --size 500x180 -x 20 -y 10\n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+
+#: C/index.docbook:1898(sect3/para)
+msgid ""
+"The following is an example <filename>mousetweaks.desktop</filename> file:"
+msgstr ""
+"Berikut ini adalah contoh berkas <filename>mousetweaks.desktop</filename>:"
+
+#: C/index.docbook:1903(sect3/screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Software Mouse-Clicks\n"
+"Comment=Perform clicks by dwelling with the pointer\n"
+"TryExec=mousetweaks\n"
+"Exec=mousetweaks --enable-dwell -m window -c -x 20 -y 240 \n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+msgstr ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Software Mouse-Clicks\n"
+"Comment=Perform clicks by dwelling with the pointer\n"
+"TryExec=mousetweaks\n"
+"Exec=mousetweaks --enable-dwell -m window -c -x 20 -y 240 \n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+
+#: C/index.docbook:1917(sect3/para)
+msgid ""
+"Note the line with the AutostartCondition that links both desktop files to "
+"the GConf key for the on-screen keyboard."
+msgstr ""
+"Perhatikan baris dengan AutostartCondition yang menautkan kedua berkas "
+"desktop ke kunci GConf bagi papan tik pada layar."
+
+#: C/index.docbook:1922(sect3/para)
+msgid ""
+"To disable GOK from starting, the desktop file for the GOK on-screen "
+"keyboard must be removed or deactivated. Otherwise onboard and GOK would "
+"simultaneously be started. This can be done by removing the gok.desktop file "
+"from the GDM autostart directory, or by adding the \"Hidden=true\" key "
+"setting to the gok.desktop file."
+msgstr ""
+"Untuk mencegah GOK dimulai, berkas desktop bagi papan tik pada layar GOK "
+"mesti dihapus atau dimatikan. Bila tidak maka onboard dan GOK akan dimulai "
+"secara simultan. Ini dapat dilakukan dengan menghapus berkas gok.desktop "
+"dari direktori mulai-sendiri GDM atau dengan menambahkan pengaturan kunci "
+"\"Hidden=true\" ke berkas gok.desktop."
+
+#: C/index.docbook:1930(sect3/para)
+msgid ""
+"After making these changes, GOK will no longer be started when the user "
+"activates the on-screen keyboard in the GDM session; but onboard and "
+"mousetweaks will instead be launched."
+msgstr ""
+"Setelah membuat perubahan ini, GOK tak akan lagi dimulai ketika pengguna "
+"mengaktifkan papan tik pada layar dalam sesi GDM, tapi sebagai gantinya yang "
+"akan diluncurkan adalah onboard dan mousetweaks."
+
+#: C/index.docbook:1939(sect2/title)
+msgid "General Session Settings"
+msgstr "Tatanan Sesi Umum"
+
+#: C/index.docbook:1948(sect2/para)
+msgid ""
+"The GDM Greeter uses some of the same framework that your desktop session "
+"will use. And so, it is influenced by a number of the same GConf settings. "
+"For each of these settings the Greeter will use the default value unless it "
+"is specifically overridden by a) GDM's installed mandatory policy b) system "
+"mandatory policy. GDM installs its own mandatory policy to lock down some "
+"settings for security."
+msgstr ""
+"Penyapa GDM memakai beberapa dari framework yang sama dengan yang akan "
+"dipakai oleh sesi desktop Anda. Maka itu dipengaruhi oleh sejumlah "
+"pengaturan GConf yang sama. Bagi setiap pengaturan ini Penyapa akan memakai "
+"nilai bawaan kecuali ditimpa secara spesifik oleh a) kebijakan wajib "
+"terpasang GDM b) kebijakan wajib sistem. GDM memasang kebijakan wajibnya "
+"sendiri untuk mengunci beberapa pengaturan demi keamanan."
+
+#: C/index.docbook:1959(sect2/title)
+msgid "GNOME Settings Daemon"
+msgstr "Daemon Penataan GNOME"
+
+#: C/index.docbook:1972(sect2/para)
+msgid ""
+"GDM enables the following gnome-settings-daemon plugins: a11y-keyboard, "
+"background, sound, xsettings."
+msgstr ""
+"GDM mengaktifkan plugin gnome-settings-daemon berikut: a11y-keyboard, "
+"background, sound, xsettings."
+
+#: C/index.docbook:1977(sect2/para)
+msgid ""
+"These are responsible for things like the background image, font and theme "
+"settings, sound events, etc."
+msgstr ""
+"Ini bertanggungjawab bagi hal-hal seperti gambar latar, pengaturan fonta dan "
+"tema, kejadian-kejadian bersuara, dsb."
+
+#: C/index.docbook:1982(sect2/para)
+msgid ""
+"Plugins can also be disabled using GConf. For example, if you want to "
+"disable the sound plugin then unset the following key: <filename>/apps/gdm/"
+"simple-greeter/settings-manager-plugins/sound/active</filename>."
+msgstr ""
+"Plugin juga dapat dinonaktifkan memakai GConf. Sebagai contoh, bila Anda "
+"ingin mematikan plugin suara maka hapuskan tatanan kunci berikut: <filename>/"
+"apps/gdm/simple-greeter/settings-manager-plugins/sound/active</filename>."
+
+#: C/index.docbook:1990(sect2/title)
+msgid "GDM Session Configuration"
+msgstr "Konfigurasi Sesi GDM"
+
+#: C/index.docbook:1992(sect2/para)
+msgid ""
+"GDM sessions are specified using the FreeDesktop.org Desktop Entry "
+"Specification, which can be referenced at the following URL: <ulink url="
+"\"http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec\"> "
+"http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec</ulink>."
+msgstr ""
+"Sesi GDM dinyatakan memakai Spesifikasi Entri Desktop FreeDesktop.org, yang "
+"dapat dirujuk pada URL berikut: <ulink url=\"http://www.freedesktop.org/wiki/"
+"Specifications/desktop-entry-spec\"> http://www.freedesktop.org/wiki/"
+"Specifications/desktop-entry-spec</ulink>."
+
+#: C/index.docbook:1999(sect2/para)
+msgid ""
+"By default, GDM will install desktop files in the <filename>&lt;share&gt;/"
+"xsessions</filename> directory. GDM will search the following directories in "
+"this order to find desktop files: <filename>&lt;etc&gt;/X11/sessions/</"
+"filename>, <filename>&lt;dmconfdir&gt;/Sessions</filename>, <filename>&lt;"
+"share&gt;/xsessions</filename>, and <filename>&lt;share&gt;/gdm/"
+"BuiltInSessions</filename>. By default the <filename>&lt;dmconfdir&gt;</"
+"filename> is set to <filename>&lt;etc&gt;/dm/</filename> unless GDM is "
+"configured to use a different directory via the \"--with-dmconfdir\" option."
+msgstr ""
+"Secara baku, GDM akan memasang berkas desktop dalam direktori <filename>&lt;"
+"share&gt;/xsessions</filename>. GDM akan mencari dalam direktori berikut, "
+"sesuai urutan, untuk mencari berkas desktop: <filename>&lt;etc&gt;/X11/"
+"sessions/</filename>, <filename>&lt;dmconfdir&gt;/Sessions</filename>, "
+"<filename>&lt;share&gt;/xsessions</filename>, dan <filename>&lt;share&gt;/"
+"gdm/BuiltInSessions</filename>. Secara baku <filename>&lt;dmconfdir&gt;</"
+"filename> ditata ke <filename>&lt;etc&gt;/dm/</filename> kecuali GDM ditata "
+"untuk memakai direktori lain melalui opsi \"--with-dmconfdir\"."
+
+#: C/index.docbook:2012(sect2/para)
+msgid ""
+"A session can be disabled by editing the desktop file and adding a line as "
+"follows: <filename>Hidden=true</filename>."
+msgstr ""
+"Suatu sesi dapat dimatikan dengan menyunting berkas desktop dan menambahkan "
+"baris berikut: <filename>Hidden=true</filename>."
+
+#: C/index.docbook:2017(sect2/para)
+msgid ""
+"GDM desktop files support a GDM-specific extension, a key named \"X-GDM-"
+"BypassXsession\". If the key is not specified in a desktop file, the value "
+"defaults to \"false\". If this key is specified to be \"true\" in a desktop "
+"file, then GDM will launch the program specified by the desktop file \"Exec"
+"\" key directly when starting the user session. It will not run the program "
+"via the <filename>&lt;etc&gt;/gdm/Xsession</filename> script, which is the "
+"normal behavior. Since bypassing the <filename>&lt;etc&gt;/gdm/Xsession</"
+"filename> script avoids setting up the user session with the normal system "
+"and user settings, sessions started this way can be useful for debugging "
+"problems in the system or user scripts that might be preventing a user from "
+"being able to start a session."
+msgstr ""
+"Berkas desktop GDM mendukung ekstensi spesifik GDM, suatu kunci bernama \"X-"
+"GDM-BypassXsession\". Bila kunci itu tak dinyatakan dalam suatu berkas "
+"desktop, nilai bawaannya adalah \"false\". Bila kunci ini dinyatakan dengan "
+"nilai \"true\" dalam suatu berkas desktop, maka GDM akan meluncurkan program "
+"yang dinyatakan oleh kunci \"Exec\" berkas desktop secara langsung ketika "
+"mengawali sesi pengguna. Itu tidak akan menjalankan program melalui skrip "
+"<filename>&lt;etc&gt;/gdm/Xsession</filename>, yang merupakan perilaku "
+"normal. Karena mem-bypass skrip <filename>&lt;etc&gt;/gdm/Xsession</"
+"filename> menghindari menyiapkan sesi pengguna dengan pengaturan pengguna "
+"dan sistem normal, sesi yang dimulai dengan cara ini dapat berguna untuk "
+"mengawakutu masalah dalam skrip pengguna atau sistem yang mungkin mencegah "
+"seorang pengguna untuk mengawali suatu sesi."
+
+#: C/index.docbook:2036(sect2/title)
+msgid "GDM User Session and Language Configuration"
+msgstr "Konfigurasi Bahasa dan Sesi Pengguna GDM "
+
+#: C/index.docbook:2037(sect2/para)
+msgid ""
+"The user's default session and language choices are stored in the "
+"<filename>~/.dmrc</filename> file. When a user logs in for the first time, "
+"this file is created with the user's initial choices. The user can change "
+"these default values by simply changing to a different value when logging "
+"in. GDM will remember this change for subsequent logins."
+msgstr ""
+"Pilihan bahasa dan sesi baku pengguna disimpan di dalam berkas <filename>~/."
+"dmrc</filename>. Ketika pengguna log masuk untuk pertama kali, berkas ini "
+"dibuat dan diisi dengan pilihan awal pengguna. Pengguna dapat mengubah nilai "
+"bawaan ini hanya dengan mengubah ke nilai yang berbeda ketika sedang log "
+"masuk. GDM akan mengingat perubahan ini untuk log masuk seterusnya."
+
+#: C/index.docbook:2045(sect2/para)
+msgid ""
+"The <filename>~/.dmrc</filename> file is in the standard <filename>INI</"
+"filename> format. It has one section called <filename>[Desktop]</filename> "
+"which has two keys: <filename>Session</filename> and <filename>Language</"
+"filename>."
+msgstr ""
+"Berkas <filename>~/.dmrc</filename> memakai standar format <filename>INI</"
+"filename>. Dia memiliki satu bagian bernama <filename>[Desktop]</filename> "
+"yang memiliki dua kunci: <filename>Session</filename> dan "
+"<filename>Language</filename>."
+
+#: C/index.docbook:2052(sect2/para)
+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. 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 ""
+"Kunci <filename>Session</filename> menyatakan nama basis dari berkas "
+"<filename>.desktop</filename> sesi yang biasanya ingin dipakai oleh pengguna "
+"tanpa ekstensi <filename>.desktop</filename>. Kunci <filename>Language</"
+"filename> menyatakan bahasa bawaan yang ingin dipakai oleh pengguna. Bila "
+"salah satu kunci tersebut hilang, akan dipakai bawaan sistem. Berkas "
+"biasanya nampak sebagai berikut:"
+
+#: C/index.docbook:2061(sect2/screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop]\n"
+"Session=gnome\n"
+"Language=cs_CZ.UTF-8\n"
+msgstr ""
+"\n"
+"[Desktop]\n"
+"Session=gnome\n"
+"Language=id_ID.UTF-8\n"
+
+#: C/index.docbook:2073(sect1/title)
+msgid "GDM Commands"
+msgstr "Perintah GDM"
+
+#: C/index.docbook:2076(sect2/title)
+msgid "GDM Root User Commands"
+msgstr "Perintah Pengguna Root GDM"
+
+#: C/index.docbook:2078(sect2/para)
+msgid ""
+"The GDM package provides the following commands in <filename>sbindir</"
+"filename> intended to be run by the root user:"
+msgstr ""
+"Paket GDM menyediakan perintah berikut di <filename>sbindir</filename> yang "
+"dimaksudkan untuk dijalankan oleh pengguna root:"
+
+#: C/index.docbook:2084(sect3/title) C/index.docbook:2099(variablelist/title)
+msgid ""
+"<command>gdm</command> and <command>gdm-binary</command> Command Line Options"
+msgstr ""
+"Opsi Perintah Baris <command>gdm</command> dan <command>gdm-binary</command>"
+
+#: C/index.docbook:2087(sect3/para)
+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>&lt;etc&gt;/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. The <command>gdm-binary</command> is the "
+"actual GDM daemon."
+msgstr ""
+"Perintah <command>gdm</command> sebenarnya hanya suatu skrip yang "
+"menjalankan <command>gdm-binary</command>, meneruskan semua opsi. Sebelum "
+"meluncurkan <command>gdm-binary</command>, skrip pembungkus gdm akan men-"
+"source berkas <filename>&lt;etc&gt;/profile</filename> untuk menata variabel "
+"lingkungan sistem standar. Agar dapat mendukung internasionalisasi secara "
+"lebih baik, itu juga akan menata variabel lingkungan LC_MESSAGES ke LANG "
+"bila LC_MESSAGES maupun LC_ALL tak diisi. <command>gdm-binary</command> "
+"adalah daemon GDM yang sebenarnya."
+
+#: C/index.docbook:2103(varlistentry/term)
+msgid "-?, --help"
+msgstr "-?, --help"
+
+#: C/index.docbook:2105(listitem/para)
+msgid "Gives a brief overview of the command line options."
+msgstr "Memberi kilasan singkat atas opsi perintah baris."
+
+#: C/index.docbook:2112(varlistentry/term)
+msgid "--fatal-warnings"
+msgstr "--fatal-warnings"
+
+#: C/index.docbook:2114(listitem/para)
+msgid "Make all warnings cause GDM to exit."
+msgstr "Buat semua peringatan menyebabkan GDM keluar."
+
+#: C/index.docbook:2121(varlistentry/term)
+msgid "--timed-exit"
+msgstr "--timed-exit"
+
+#: C/index.docbook:2123(listitem/para)
+msgid "Exit after 30 seconds. Useful for debugging."
+msgstr "Keluar setelah 30 detik. Berguna untuk pengawakutuan."
+
+#: C/index.docbook:2130(varlistentry/term)
+msgid "--version"
+msgstr "--version"
+
+#: C/index.docbook:2132(listitem/para)
+msgid "Print the version of the GDM daemon."
+msgstr "Cetak versi daemon GDM."
+
+#: C/index.docbook:2141(sect3/title)
+msgid "<command>gdm-restart</command> Command Line Options"
+msgstr "Opsi Perintah Baris <command>gdm-restart</command>"
+
+#: C/index.docbook:2143(sect3/para)
+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> menghentikan dan memulai ulang GDM dengan "
+"mengirim sinyal HUP ke daemon GDM. Perintah ini akan seketika menghentikan "
+"semua sesi dan melog keluar pengguna yang sedang log masuk dengan GDM."
+
+#: C/index.docbook:2151(sect3/title)
+msgid "<command>gdm-safe-restart</command> Command Line Options"
+msgstr "Opsi Perintah Baris <command>gdm-safe-restart</command>"
+
+#: C/index.docbook:2153(sect3/para)
+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> menghentikan dan memulai ulang GDM "
+"dengan mengirim sinyal USR1 ke daemon GDM. GDM akan direstart segera setelah "
+"semua pengguna log keluar."
+
+#: C/index.docbook:2161(sect3/title)
+msgid "<command>gdm-stop</command> Command Line Options"
+msgstr "Opsi Perintah Baris <command>gdm-stop</command>"
+
+#: C/index.docbook:2163(sect3/para)
+msgid ""
+"<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM "
+"signal."
+msgstr ""
+"<command>gdm-stop</command> menghentikan GDM dengan cara mengirim sinyal "
+"TERM ke daemon GDM."
+
+#: C/index.docbook:2174(sect1/title)
+msgid "Troubleshooting"
+msgstr "Penanganan Masalah"
+
+#: C/index.docbook:2182(sect1/para)
+msgid ""
+"This section discusses helpful tips for getting GDM working. In general, if "
+"you have a problem using GDM, you can submit a bug or send an email to the "
+"gdm-list mailing list. Information about how to do this is in the "
+"Introduction section of the document."
+msgstr ""
+"Bagian ini membahas petunjuk-petunjuk yang berguna agar GDM dapat berjalan. "
+"Secara umum, bila Anda menemui masalah saat memakai GDM, Anda dapat mengirim "
+"kutu atau surel ke milis gdm-list. Informasi tentang bagaimana melakukan ini "
+"ada pada bagian pengantar dokumen ini."
+
+#: C/index.docbook:2189(sect1/para)
+msgid ""
+"If GDM is failing to work properly, it is always a good idea to include "
+"debug information. To enable debugging, set the debug/Enable key to \"true\" "
+"in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file and restart "
+"GDM. Then use GDM to the point where it fails, and debug output will be sent "
+"to the system log file (<filename>&lt;var&gt;/log/messages</filename> or "
+"<filename>&lt;var&gt;/adm/messages</filename> depending on your Operating "
+"System). If you share this output with the GDM community via a bug report or "
+"email, please only include the GDM related debug information and not the "
+"entire file since it can be large. If you do not see any GDM syslog output, "
+"you may need to configure syslog (refer to the <ulink type=\"help\" url="
+"\"man:syslog\">syslog</ulink> man page)."
+msgstr ""
+"Bila GDM gagal bekerja dengan benar, sangat baik untuk menyertakan informasi "
+"awakutu. Untuk mengaktifkan pengawakutuan, tata kunci debug/Enable ke \"true"
+"\" di berkas <filename>&lt;etc&gt;/gdm/custom.conf</filename> dan mulai "
+"ulang GDM. Lalu gunakan GDM sampai titik kegagalan, dan keluaran awakutu "
+"akan dikirim ke berkas log sistem (<filename>&lt;var&gt;/log/messages</"
+"filename> atau <filename>&lt;var&gt;/adm/messages</filename> bergantung "
+"kepada Sistem Operasi Anda). Bila Anda berbagi keluaran ini dengan komunitas "
+"GDM melalui laporan kutu atau surel, mohon hanya sertakan informasi awakutu "
+"yang terkait GDM dan bukan seluruh berkas karena itu bisa jadi besar. Bila "
+"Anda tidak melihat keluaran syslog GDM apapun, mungkin Anda perlu menata "
+"ulang syslog (lihat halaman man <ulink type=\"help\" url=\"man:syslog"
+"\">syslog</ulink>)."
+
+#: C/index.docbook:2205(sect2/title)
+msgid "GDM Will Not Start"
+msgstr "GDM Tidak Akan Dimulai"
+
+#: C/index.docbook:2207(sect2/para)
+msgid ""
+"There are a many problems that can cause GDM to fail to start, but this "
+"section will discuss a few common problems and how to approach tracking down "
+"a problem with GDM starting. Some problems will cause GDM to respond with an "
+"error message or dialog when it tries to start, but it can be difficult to "
+"track down problems when GDM fails silently."
+msgstr ""
+"Banyak masalah yang dapat menyebabkan GDM gagal berjalan, tapi bagian ini "
+"akan membahas beberapa masalah umum dan bagaimana melacak suatu masalah "
+"memulai GDM. Beberapa masalah akan menyebabkan GDM merespon dengan pesan "
+"galat atau dialog ketika ia mencoba memulai, tapi bisa menjadi sulit melacak "
+"masalah ketika GDM gagal diam-diam."
+
+#: C/index.docbook:2216(sect2/para)
+msgid ""
+"First make sure that the Xserver is configured properly. The GDM "
+"configuration file contains a command in the [server-Standard] section that "
+"is used for starting the Xserver. Verify that this command works on your "
+"system. Running this command from the console should start the Xserver. If "
+"it fails, then the problem is likely with your Xserver configuration. Refer "
+"to your Xserver error log for an idea of what the problem may be. The "
+"problem may also be that your Xserver requires different command-line "
+"options. If so, then modify the Xserver command in the GDM configuration "
+"file so that it is correct for your system."
+msgstr ""
+"Pertama pastikan bahwa Xserver ditata dengan benar. Berkas konfigurasi GDM "
+"memuat suatu perintah di bagian [server-Standard] yang dipakai untuk memulai "
+"Xserver. Periksa bahwa perintah ini bekerja baik pada sistem Anda. "
+"Menjalankan perintah ini dari konsol mestinya memulai Xserver. Bila gagal, "
+"maka masalahnya boleh jadi pada konfigurasi Xserver Anda. Lihat log galat "
+"Xserver Anda untuk ide apa kemungkinan masalahnya. Masalah mungkin juga "
+"karena bahwa Xserver Anda memerlukan opsi perintah baris yang berbeda. Bila "
+"begitu, maka ubahlah perintah Xserver di berkas konfigurasi GDM sehingga "
+"tepat bagi sistem Anda."
+
+#: C/index.docbook:2229(sect2/para)
+msgid ""
+"Also make sure that the <filename>/tmp</filename> directory has reasonable "
+"ownership and permissions, and that the machine's file system is not full. "
+"These problems will cause GDM to fail to start."
+msgstr ""
+"Pastikan juga bahwa direktori <filename>/tmp</filename> memiliki kepemilikan "
+"dan ijin yang memadai, dan sistem berkas mesin tak penuh. Masalah-masalah "
+"ini akan menyebabkan GDM gagal dijalankan."
+
+#: C/index.docbook:2240(sect1/title)
+msgid "License"
+msgstr "Lisensi"
+
+#: C/index.docbook:2241(sect1/para)
+#| 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."
+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 ""
+"Program ini adalah perangkat lunak bebas; Anda dapat menyebarluaskannya dan/"
+"atau mengubahnya di bawah syarat <ulink type=\"help\" url=\"gnome-help:gpl"
+"\"> <citetitle>GNU General Public License</citetitle></ulink> sebagaimana "
+"dipublikasikan oleh Free Software Foundation; baik versi 2 dari Lisensi, "
+"atau (terserah pilihan Anda) versi setelahnya."
+
+#: C/index.docbook:2249(sect1/para)
+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 ""
+"Program ini didistribusikan dengan harapan akan berguna, tetapi TANPA ADANYA "
+"JAMINAN; termasuk tanpa jaminan KETERDAGANGAN atau KECOCOKAN UNTUK TUJUAN "
+"TERTENTU. Lihat <citetitle>GNU General Public License</citetitle> untuk "
+"rincian lebih lanjut."
+
+#: C/index.docbook:2263(para/address)
+#, no-wrap
+msgid ""
+"\n"
+"      Free Software Foundation, Inc.\n"
+"      <street>51 Franklin Street, Fifth Floor</street>\n"
+"      <city>Boston</city>, <state>MA</state> <postcode>02110-1301</postcode>\n"
+"      <country>USA</country>\n"
+"      "
+msgstr ""
+"\n"
+"      Free Software Foundation, Inc.\n"
+"      <street>51 Franklin Street, Fifth Floor</street>\n"
+"      <city>Boston</city>, <state>MA</state> <postcode>02110-1301</postcode>\n"
+"      <country>USA</country>\n"
+"      "
+
+#: C/index.docbook:2255(sect1/para)
+#| 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>51 Franklin Street, "
+#| "Fifth Floor</street><city>Boston</city>, <state>MA</"
+#| "state><postcode>02110-1301</postcode><country>USA</country></address>"
+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-1/>"
+msgstr ""
+"Suatu salinan dari <citetitle>GNU General Public License</citetitle> "
+"disertakan sebagai lampiran dari <citetitle>Panduan Pengguna GNOME</"
+"citetitle>. Anda juga dapat memperoleh salinan dari <citetitle>GNU General "
+"Public License</citetitle> dari Free Software Foundation dengan mengunjungi "
+"ulink type=\"http\" url=\"http://www.fsf.org\">laman Web mereka</ulink> atau "
+"dengan mengirim surat ke <_:address-1/>"
+
+#: C/legal.xml:9(para/ulink)
+msgid "link"
+msgstr "taut"
+
+#: C/legal.xml:2(legalnotice/para)
+#| msgid ""
+#| "Permission is granted to copy, distribute and/or modify this document "
+#| "under the terms of the GNU Free Documentation License (GFDL), Version 1.1 "
+#| "or any later version published by the Free Software Foundation with no "
+#| "Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You "
+#| "can find a copy of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl"
+#| "\">link</ulink> or in the file COPYING-DOCS distributed with this manual."
+msgid ""
+"Permission is granted to copy, distribute and/or modify this document under "
+"the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any "
+"later version published by the Free Software Foundation with no Invariant "
+"Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy "
+"of the GFDL at this <_:ulink-1/> or in the file COPYING-DOCS distributed "
+"with this manual."
+msgstr ""
+"Hak diberikan untuk menyalin, mendistribusikan, dan/atau mengubah dokumen "
+"ini di bawah persyaratan GNU Free Documentation License (GFDL, Lisensi "
+"Dokumentasi Bebas GNU), Versi 1.1 atau sebarang versi setelahnya yang "
+"dipublikasikan oleh Free Software Foundation tanpa Invariant Section, tanpa "
+"Front-Cover Texts, dan tanpa Back-Cover Texts. Anda dapat menemukan salinan "
+"dari GFDL pada <_:ulink-1/> ini atau di dalam berkas COPYING-DOCS yang "
+"didistribusikan bersama panduan ini."
diff --git a/docs/sl/sl.po b/docs/sl/sl.po
new file mode 100644
index 0000000..1bd858c
--- /dev/null
+++ b/docs/sl/sl.po
@@ -0,0 +1,1656 @@
+# Slovenian translation for gdm.
+# Copyright (C) 2010 gdm's COPYRIGHT HOLDER
+# This file is distributed under the same license as the gdm package.
+#
+# Ime Priimek <email>, leto
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: gdm help master\n"
+"POT-Creation-Date: 2010-10-16 18:19+0000\n"
+"PO-Revision-Date: 2010-10-17 21:12+0100\n"
+"Last-Translator: Matej Urbančič <mateju@svn.gnome.org>\n"
+"Language-Team: Slovenian GNOME Translation Team <gnome-si@googlegroups.com>\n"
+"Language: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=4; plural=(n%100==1 ? 1 : n%100==2 ? 2 : n%100==3 || n%100==4 ? 3 : 0);\n"
+"X-Poedit-Country: SLOVENIA\n"
+"X-Poedit-Language: Slovenian\n"
+"X-Poedit-SourceCharset: utf-8\n"
+
+#: C/gdm.xml:13(title)
+msgid "GNOME Display Manager Reference Manual"
+msgstr ""
+
+#: C/gdm.xml:17(revnumber)
+msgid "0.0"
+msgstr "0.0"
+
+#: C/gdm.xml:18(date)
+msgid "2008-09"
+msgstr "2008-09"
+
+#: C/gdm.xml:23(para)
+msgid "GDM is the GNOME Display Manager, a graphical login program."
+msgstr ""
+
+#: C/gdm.xml:30(firstname)
+msgid "Martin"
+msgstr "Martin"
+
+#: C/gdm.xml:30(othername)
+msgid "K."
+msgstr "K."
+
+#: C/gdm.xml:31(surname)
+msgid "Petersen"
+msgstr "Petersen"
+
+#: C/gdm.xml:33(email)
+msgid "mkp@mkp.net"
+msgstr "mkp@mkp.net"
+
+#: C/gdm.xml:37(firstname)
+msgid "George"
+msgstr "George"
+
+#: C/gdm.xml:37(surname)
+msgid "Lebl"
+msgstr "Lebl"
+
+#: C/gdm.xml:39(email)
+msgid "jirka@5z.com"
+msgstr "jirka@5z.com"
+
+#: C/gdm.xml:43(firstname)
+msgid "Jon"
+msgstr "Jon"
+
+#: C/gdm.xml:43(surname)
+msgid "McCann"
+msgstr "McCann"
+
+#: C/gdm.xml:45(email)
+msgid "mccann@jhu.edu"
+msgstr "mccann@jhu.edu"
+
+#: C/gdm.xml:49(firstname)
+msgid "Ray"
+msgstr "Ray"
+
+#: C/gdm.xml:49(surname)
+msgid "Strode"
+msgstr "Strode"
+
+#: C/gdm.xml:51(email)
+msgid "rstrode@redhat.com"
+msgstr "rstrode@redhat.com"
+
+#: C/gdm.xml:55(firstname)
+msgid "Brian"
+msgstr "Brian"
+
+#: C/gdm.xml:55(surname)
+msgid "Cameron"
+msgstr "Cameron"
+
+#: C/gdm.xml:57(email)
+msgid "Brian.Cameron@Sun.COM"
+msgstr "brian.cameron@sun.com"
+
+#: C/gdm.xml:62(year)
+msgid "1998"
+msgstr "1998"
+
+#: C/gdm.xml:63(year)
+msgid "1999"
+msgstr "1999"
+
+#: C/gdm.xml:64(holder)
+msgid "Martin K. Petersen"
+msgstr "Martin K. Petersen"
+
+#: C/gdm.xml:67(year)
+msgid "2001"
+msgstr "2001"
+
+#: C/gdm.xml:68(year)
+#: C/gdm.xml:73(year)
+#: C/gdm.xml:79(year)
+msgid "2003"
+msgstr "2003"
+
+#: C/gdm.xml:69(year)
+#: C/gdm.xml:80(year)
+msgid "2004"
+msgstr "2004"
+
+#: C/gdm.xml:70(holder)
+msgid "George Lebl"
+msgstr "George Lebl"
+
+#: C/gdm.xml:74(year)
+#: C/gdm.xml:83(year)
+msgid "2007"
+msgstr "2007"
+
+#: C/gdm.xml:75(year)
+#: C/gdm.xml:84(year)
+msgid "2008"
+msgstr "2008"
+
+#: C/gdm.xml:76(holder)
+msgid "Red Hat, Inc."
+msgstr "Red Hat, Inc."
+
+#: C/gdm.xml:81(year)
+msgid "2005"
+msgstr "2005"
+
+#: C/gdm.xml:82(year)
+msgid "2006"
+msgstr "2006"
+
+#: C/gdm.xml:85(holder)
+msgid "Sun Microsystems, Inc."
+msgstr "Sun Microsystems, Inc."
+
+#: C/gdm.xml:2(para)
+msgid "Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or in the file COPYING-DOCS distributed with this manual."
+msgstr ""
+
+#: C/gdm.xml:12(para)
+msgid "This manual is part of a collection of GNOME manuals distributed under the GFDL. If you want to distribute this manual separately from the collection, you can do so by adding a copy of the license to the manual, as described in section 6 of the license."
+msgstr ""
+
+#: C/gdm.xml:19(para)
+msgid "Many of the names used by companies to distinguish their products and services are claimed as trademarks. Where those names appear in any GNOME documentation, and the members of the GNOME Documentation Project are made aware of those trademarks, then the names are in capital letters or initial capital letters."
+msgstr ""
+
+#: C/gdm.xml:35(para)
+msgid "DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND"
+msgstr ""
+
+#: C/gdm.xml:55(para)
+msgid "UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES."
+msgstr ""
+
+#: C/gdm.xml:28(para)
+msgid "DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: <placeholder-1/>"
+msgstr ""
+
+#: C/gdm.xml:90(releaseinfo)
+#: C/gdm.xml:101(para)
+msgid "This manual describes version 2.26.0 of the GNOME Display Manager. It was last updated on 02/10/2009."
+msgstr ""
+
+#: C/gdm.xml:99(title)
+msgid "Terms and Conventions Used in This Manual"
+msgstr ""
+
+#: C/gdm.xml:106(para)
+msgid "Chooser - A program used to select a remote host for managing a display remotely on the attached display (<command>gdm-host-chooser</command>)."
+msgstr ""
+
+#: C/gdm.xml:111(para)
+msgid "FreeDesktop - The organization providing desktop standards, such as the Desktop Entry Specification used by GDM. <ulink type=\"http\" url=\"http://www.freedesktop.org/\"> http://www.freedesktop.org</ulink>."
+msgstr ""
+
+#: C/gdm.xml:117(para)
+msgid "GDM - GNOME Display Manager. Used to describe the software package as a whole."
+msgstr ""
+
+#: C/gdm.xml:122(para)
+msgid "Greeter - The graphical login window (<command>gdm-simple-greeter</command>)."
+msgstr ""
+
+#: C/gdm.xml:126(para)
+msgid "PAM - Pluggable Authentication Mechanism"
+msgstr ""
+
+#: C/gdm.xml:130(para)
+msgid "XDMCP - X Display Manage Protocol"
+msgstr ""
+
+#: C/gdm.xml:134(para)
+msgid "Xserver - An implementation of the X Window System. For example the Xorg Xserver provided by the X.org Foundation <ulink type=\"http\" url=\"http://www.x.org/\">http://www.x.org</ulink>."
+msgstr ""
+
+#: C/gdm.xml:140(para)
+msgid "Paths that start with a word in angle brackets are relative to the installation prefix. I.e. <filename>&lt;share&gt;/pixmaps/</filename> refers to <filename>/usr/share/pixmaps</filename> if GDM was configured with <command>--prefix=/usr</command>."
+msgstr ""
+
+#: C/gdm.xml:151(title)
+msgid "Overview"
+msgstr "Pregled"
+
+#: C/gdm.xml:154(title)
+msgid "Introduction"
+msgstr "Uvod"
+
+#: C/gdm.xml:156(para)
+msgid "The GNOME Display Manager (GDM) is a display manager that implements all significant features required for managing attached and remote displays. GDM was written from scratch and does not contain any XDM or X Consortium code."
+msgstr ""
+
+#: C/gdm.xml:163(para)
+msgid "Note that GDM is configurable, and many configuration settings have an impact on security. Issues to be aware of are highlighted in this document."
+msgstr ""
+
+#: C/gdm.xml:169(para)
+msgid "Please note that some Operating Systems configure GDM to behave differently than the default values as described in this document. If GDM does not seem to behave as documented, then check to see if any related configuration may be different than described here."
+msgstr ""
+
+#: C/gdm.xml:176(para)
+msgid "For further information about GDM, refer to the project website at <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> http://www.gnome.org/projects/gdm</ulink> and the project Wiki <ulink type=\"http\" url=\"http://live.gnome.org/GDM\"> http://live.gnome.org/GDM</ulink>."
+msgstr ""
+
+#: C/gdm.xml:184(para)
+msgid "For discussion or queries about GDM, refer to the <address><email>gdm-list@gnome.org</email></address> mail list. This list is archived, and is a good resource to check to seek answers to common questions. This list is archived at <ulink type=\"http\" url=\"http://mail.gnome.org/archives/gdm-list/\"> http://mail.gnome.org/archives/gdm-list/</ulink> and has a search facility to look for messages with keywords."
+msgstr ""
+
+#: C/gdm.xml:194(para)
+msgid "Please submit any bug reports or enhancement requests to the \"gdm\" category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\"> http://bugzilla.gnome.org</ulink>."
+msgstr ""
+
+#: C/gdm.xml:203(title)
+msgid "Interface Stability"
+msgstr ""
+
+#: C/gdm.xml:205(para)
+msgid "GDM 2.20 and earlier supported stable configuration interfaces. However, the codebase was completely rewritten for GDM 2.22, and is not completely backward compatible with older releases. This is in part because things work differently, so some options just don't make sense, in part because some options never made sense, and in part because some functionality has not been reimplemented yet."
+msgstr ""
+
+#: C/gdm.xml:214(para)
+msgid "Interfaces which continue to be supported in a stable fashion include the Init, PreSession, PostSession, PostLogin, and Xsession scripts. Some daemon configuration options in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file continue to be supported. Also, the <filename>~/.dmrc</filename>, and face browser image locations are still supported."
+msgstr ""
+
+#: C/gdm.xml:223(para)
+msgid "GDM 2.20 and earlier supported the ability to manage multiple displays with separate graphics cards, such as used in terminal server environments, login in a window via a program like Xnest or Xephyr, the gdmsetup program, XML-based greeter themes, and the ability to run the XDMCP chooser from the login screen. These features were not added back during the 2.22 rewrite."
+msgstr ""
+
+#: C/gdm.xml:235(title)
+msgid "Functional Description"
+msgstr ""
+
+#. <para>
+#.         TODO - Would be good to discuss D-Bus, perhaps the new GObject model,
+#.                and to explain the reasons why the rewrite made GDM better.
+#.                From a high-level overview perspective, rather than the
+#.                technical aspects.
+#. </para>
+#: C/gdm.xml:246(para)
+msgid "GDM is responsible for managing displays on the system. This includes authenticating users, starting the user session, and terminating the user session. GDM is configurable and the ways it can be configured are described in the \"Configuring GDM\" section of this document. GDM is also accessible for users with disabilities."
+msgstr ""
+
+#: C/gdm.xml:254(para)
+msgid "GDM provides the ability to manage the main console display, and displays launched via VT. It is integrated with other programs, such as the Fast User Switch Applet (FUSA) and gnome-screensaver to manage multiple displays on the console via the Xserver Virtual Terminal (VT) interface. It also can manage XDMCP displays."
+msgstr ""
+
+#: C/gdm.xml:262(para)
+msgid "Regardless of the display type, GDM will do the following when it manages the display. It will start an Xserver process, then run the <filename>Init</filename> script as the root user, and start the greeter program on the display."
+msgstr ""
+
+#: C/gdm.xml:269(para)
+msgid "The greeter program is run as the unprivileged \"gdm\" user/group. This user and group are described in the \"Security\" section of this document. The main function of the greeter program is to authenticate the user. The authentication process is driven by Pluggable Authentication Modules (PAM). The PAM modules determine what prompts (if any) are shown to the user to authenticate. On the average system, the greeter program will request a username and password for authentication. However some systems may be configured to use alternative mechanisms such as a fingerprint or SmartCard reader. GDM and PAM can be configured to not require any input, which will cause GDM to automatically log in and simply start a session, which can be useful for some environments, such as for kiosks."
+msgstr ""
+
+#: C/gdm.xml:285(para)
+msgid "In addition to authentication, the greeter program allows the user to select which session to start and which language to use. Sessions are defined by files that end in the .desktop suffix and more information about these files can be found in the \"GDM User Session and Language Configuration\" section of this document. By default, GDM is configured to display a face browser so the user can select their user account by clicking on an image instead of having to type their username. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI."
+msgstr ""
+
+#: C/gdm.xml:298(para)
+msgid "After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, then runs the <filename>PreSession</filename> script as root. After running these scripts, the user session is started. When the user exits their session, the <filename>PostSession</filename> script is run as root. These scripts are provided as hooks for distributions and end-users to customize how sessions are managed. For example, using these hooks you could set up a machine which creates the user's $HOME directory on the fly, and erases it on logout. The difference between the <filename>PostLogin</filename> and <filename>PreSession</filename> scripts is that <filename>PostLogin</filename> is run before the pam_open_session call so is the right place to do anything which should be run before the user session is initialized. The <filename>PreSession</filename> script is called after session initialization."
+msgstr ""
+
+#: C/gdm.xml:318(title)
+msgid "Greeter Panel"
+msgstr ""
+
+#: C/gdm.xml:319(para)
+msgid "The GDM greeter program displays a panel docked at the bottom of the screen which provides additional functionality. When a user is selected, the panel allows the user to select which session, language, and keyboard layout to use after logging in. The keyboard layout selector also changes the keyboard layout used when typing your password. The panel also contains an area for login services to leave status icons. Some example status icons include a battery icon for current battery usage, and an icon for enabling accessibility features. The greeter program also provides buttons which allow the user to shutdown or restart the system. It is possible to configure GDM to not provide the shutdown and restart buttons, if desired. GDM can also be configured via PolicyKit (or via RBAC on Solaris) to require the user have appropriate authorization before accepting the shutdown or restart request."
+msgstr ""
+
+#: C/gdm.xml:336(para)
+msgid "Note that keyboard layout features are only available on systems that support libxklavier."
+msgstr ""
+
+#: C/gdm.xml:343(title)
+msgid "Accessibility"
+msgstr ""
+
+#: C/gdm.xml:345(para)
+msgid "GDM supports \"Accessible Login\", allowing users to log into their desktop session even if they cannot easily use the screen, mouse, or keyboard in the usual way. Accessible Technology (AT) features such as an on-screen keyboard, screen reader, screen magnifier, and Xserver AccessX keyboard accessibility are available. It is also possible to enable large text or high contrast icons and controls, if needed. Refer to the \"Accessibility Configuration\" section of the document for more information how various accessibility features can be configured."
+msgstr ""
+
+#: C/gdm.xml:357(para)
+msgid "On some Operating Systems, it is necessary to make sure that the GDM user is a member of the \"audio\" group for AT programs that require audio output (such as text-to-speech) to be functional."
+msgstr ""
+
+#: C/gdm.xml:365(title)
+msgid "The GDM Face Browser"
+msgstr ""
+
+#: C/gdm.xml:367(para)
+msgid "The Face Browser is the interface which allows users to select their username by clicking on an image. This feature can be enabled or disabled via the /apps/gdm/simple-greeter/disable_user_list GConf key and is on by default. When disabled, users must type their complete username by hand. When enabled, it displays all local users which are available for login on the system (all user accounts defined in the /etc/passwd file that have a valid shell and sufficiently high UID) and remote users that have recently logged in. The face browser in GDM 2.20 and earlier would attempt to display all remote users, which caused performance problems in large, enterprise deployments."
+msgstr ""
+
+#: C/gdm.xml:381(para)
+msgid "The Face Browser is configured to display the users who log in most frequently at the top of the list. This helps to ensure that users who log in frequently can quickly find their login image."
+msgstr ""
+
+#: C/gdm.xml:387(para)
+msgid "The Face Browser supports \"type-ahead search\" which dynamically moves the face selection as the user types to the corresponding username in the list. This means that a user with a long username will only have to type the first few characters of the username before the correct item in the list gets selected."
+msgstr ""
+
+#: C/gdm.xml:395(para)
+msgid "The icons used by GDM can be installed globally by the sysadmin or can be located in the user's home directories. If installed globally they should be in the <filename>&lt;share&gt;/pixmaps/faces/</filename> directory and the filename should be the name of the user. Face image files should be a standard image that GTK+ can read, such as PNG or JPEG. Face icons placed in the global face directory must be readable to the GDM user."
+msgstr ""
+
+#. <para>
+#.         TODO - In the old GDM the ~/gnome2/gdm file is used, but the new code
+#.                seems to use ~/.gnome/gdm.  Error?
+#. </para>
+#: C/gdm.xml:411(para)
+msgid "If there is no global icon for the user, GDM will look in the user's $HOME directory for the image file. GDM will first look for the user's face image in <filename>~/.face</filename>. If not found, it will try <filename>~/.face.icon</filename>. If still not found, it will use the value defined for \"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file."
+msgstr ""
+
+#: C/gdm.xml:420(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 fallback to a generic face image."
+msgstr ""
+
+#: C/gdm.xml:426(para)
+msgid "Please note that loading and scaling face icons located in remote user home directories can be a very time-consuming task. Since it not practical to load images over NIS or NFS, GDM does not attempt to load face images from remote home directories."
+msgstr ""
+
+#: C/gdm.xml:433(para)
+msgid "When the browser is turned on, valid usernames on the computer are exposed for everyone to see. If XDMCP is enabled, then the usernames are exposed to remote users. This, of course, limits security somewhat since a malicious user does not need to guess valid usernames. In some very restrictive environments the face browser may not be appropriate."
+msgstr ""
+
+#: C/gdm.xml:445(title)
+msgid "XDMCP"
+msgstr "XDMCP"
+
+#. <para>
+#.         TODO - What XDMCP features actually work?   I know that the
+#.                chooser is missing.
+#. </para>
+#: C/gdm.xml:454(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 turned off, but can be enabled if desired. If GDM is built with TCP Wrapper support, then the daemon will only grant access to hosts specified in the GDM service section in the TCP Wrappers configuration file."
+msgstr ""
+
+#: C/gdm.xml:463(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 timeouts, etc. can be fine tuned. The default configuration should work reasonably on most systems."
+msgstr ""
+
+#: C/gdm.xml:470(para)
+msgid "GDM by default listens for XDMCP requests on the normal UDP port used for XDMCP, port 177, and will respond to QUERY and BROADCAST_QUERY requests by sending a WILLING packet to the originator."
+msgstr ""
+
+#: C/gdm.xml:476(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 forward subsequent requests to the chosen manager. GDM also supports an extension to the protocol which will make it forget the redirection once the user's connection succeeds. This extension is only supported if both daemons are GDM. It is transparent and will be ignored by XDM or other daemons that implement XDMCP."
+msgstr ""
+
+#: C/gdm.xml:486(para)
+msgid "If XDMCP seems to not be working, make sure that all machines are specified in <filename>/etc/hosts</filename>."
+msgstr ""
+
+#: C/gdm.xml:491(para)
+msgid "Refer to the \"Security\" section for information about security concerns when using XDMCP."
+msgstr ""
+
+#: C/gdm.xml:498(title)
+msgid "Logging"
+msgstr ""
+
+#: C/gdm.xml:500(para)
+msgid "GDM uses syslog to log errors and status. It can also log debugging information, which can be useful for tracking down problems if GDM is not working properly. Debug output can be enabled by setting the debug/Enable key to \"true\" in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file."
+msgstr ""
+
+#: C/gdm.xml:508(para)
+msgid "Output from the various Xservers is stored in the GDM log directory, which is normally <filename>&lt;var&gt;/log/gdm/</filename>. Any Xserver messages are saved to a file associated with the display value, <filename>&lt;display&gt;.log</filename>."
+msgstr ""
+
+#: C/gdm.xml:515(para)
+msgid "The session output is piped through the GDM daemon to the <filename>~/.xsession-errors</filename> file. The file is overwritten on each login, so logging out and logging back into the same user via GDM will cause any messages from the previous session to be lost."
+msgstr ""
+
+#: C/gdm.xml:522(para)
+msgid "Note that if GDM can not create this file for some reason, then a fallback file will be created named <filename>~/.xsession-errors.XXXXXXXX</filename> where the <filename>XXXXXXXX</filename> are some random characters."
+msgstr ""
+
+#: C/gdm.xml:530(title)
+msgid "Fast User Switching"
+msgstr ""
+
+#: C/gdm.xml:532(para)
+msgid "GDM allows multiple users to be logged in at the same time. After one user is logged in, additional users can log in via the User Switcher on the GNOME Panel, or from the \"Switch User\" button in Lock Screen dialog of GNOME Screensaver. The active session can be changed back and forth using the same mechanism. Note that some distributions may not add the User Switcher to the default panel configuration. It can be added using the panel context menu."
+msgstr ""
+
+#: C/gdm.xml:541(para)
+msgid "Note this feature is available on systems that support Virtual Terminals. This feature will not function if Virtual Terminals is not available."
+msgstr ""
+
+#: C/gdm.xml:552(title)
+msgid "Security"
+msgstr "Varnost"
+
+#: C/gdm.xml:555(title)
+msgid "The GDM User And Group"
+msgstr ""
+
+#: C/gdm.xml:557(para)
+msgid "For security reasons a dedicated user and group id are recommended for proper operation. This user and group are normally \"gdm\" on most systems, but can be configured to any user or group. All GDM GUI programs are run as this user, so that the programs which interact with the user are run in a sandbox. This user and group should have limited privilege."
+msgstr ""
+
+#: C/gdm.xml:566(para)
+msgid "The only special privilege the \"gdm\" user requires is the ability to read and write Xauth files to the <filename>&lt;var&gt;/run/gdm</filename> directory. The <filename>&lt;var&gt;/run/gdm</filename> directory should have root:gdm ownership and 1777 permissions."
+msgstr ""
+
+#: C/gdm.xml:574(para)
+msgid "You should not, under any circumstances, configure the GDM user/group to a user which a user could easily gain access to, such as the user <filename>nobody</filename>. Any user who gains access to an Xauth key can snoop on and control running GUI programs running in the associated session or perform a denial-of-service attack on it. It is important to ensure that the system is configured properly so that only the \"gdm\" user has access to these files and that it is not easy to login to this account. For example, the account should be setup to not have a password or allow non-root users to login to the account."
+msgstr ""
+
+#: C/gdm.xml:587(para)
+msgid "The GDM greeter configuration is stored in GConf. To allow the GDM user to be able to write configuration, it is necessary for the \"gdm\" user to have a writable $HOME directory. Users may configure the default GConf configuration as desired to avoid the need to provide the \"gdm\" user with a writable $HOME directory. However, some features of GDM may be disabled if it is unable to write state information to GConf configuration."
+msgstr ""
+
+#: C/gdm.xml:599(title)
+msgid "PAM"
+msgstr "PAM"
+
+#: C/gdm.xml:601(para)
+msgid "GDM uses PAM for login authentication. PAM stands for Pluggable Authentication Module, and is used by most programs that request authentication on your computer. It allows the administrator to configure specific authentication behavior for different login programs (such as ssh, login GUI, screensaver, etc.)"
+msgstr ""
+
+#: C/gdm.xml:609(para)
+msgid "PAM is complicated and highly configurable, and this documentation does not intend to explain this in detail. Instead, it is intended to give an overview of how PAM configuration relates with GDM, how PAM is commonly configured with GDM, and known issues. It is expected that a person needing to do PAM configuration would need to do further reading of PAM documentation to understand how to configure PAM and to understand terms used in this section."
+msgstr ""
+
+#: C/gdm.xml:619(para)
+msgid "PAM configuration has different, but similar, interfaces on different Operating Systems, so check the <ulink type=\"help\" url=\"man:pam.d\">pam.d</ulink> or <ulink type=\"help\" url=\"man:pam.conf\">pam.conf</ulink> man page for details. Be sure you read the PAM documentation and are comfortable with the security implications of any changes you intend to make to your configuration."
+msgstr ""
+
+#: C/gdm.xml:629(para)
+msgid "Note that, by default, GDM uses the \"gdm\" PAM service name for normal login and the \"gdm-autologin\" PAM service name for automatic login. These services may not be defined in your pam.d or pam.conf configured file. If there is no entry, then GDM will use the default PAM behavior. On most systems this should work fine. However, the automatic login feature may not work if the gdm-autologin service is not defined."
+msgstr ""
+
+#: C/gdm.xml:639(para)
+msgid "The <filename>PostLogin</filename> script is run before pam_open_session is called, and the <filename>PreSession</filename> script is called after. This allows the system administrator to add any scripting to the login process either before or after PAM initializes the session."
+msgstr ""
+
+#: C/gdm.xml:647(para)
+msgid "If you wish to make GDM work with other types of authentication mechanisms (such as a fingerprint or SmartCard reader), then you should implement this by using a PAM service module for the desired authentication type rather than by trying to modify the GDM code directly. Refer to the PAM documentation on your system. How to do this is frequently discussed on the <address><email>gdm-list@gnome.org</email></address> mail list, so you can refer to the list archives for more information."
+msgstr ""
+
+#: C/gdm.xml:658(para)
+msgid "PAM does have some limitations regarding being able to work with multiple types of authentication at the same time, like supporting the ability to accept either SmartCard and the ability to type the username and password into the login program. There are techniques that are used to make this work, and it is best to research how this problem is commonly solved when setting up such a configuration."
+msgstr ""
+
+#: C/gdm.xml:667(para)
+msgid "If automatic login does not work on a system, check to see if the \"gdm-autologin\" PAM stack is defined in the PAM configuration. For this to work, it is necessary to use a PAM module that simply does no authentication, or which simply returns PAM_SUCCESS from all of its public interfaces. Assuming your system has a pam_allow.so PAM module which does this, a PAM configuration to enable \"gdm-autologin\" would look like this:"
+msgstr ""
+
+#: C/gdm.xml:677(screen)
+#, no-wrap
+msgid ""
+"\n"
+"       gdm-autologin auth  required    pam_unix_cred.so.1\n"
+"       gdm-autologin auth  sufficient  pam_allow.so.1\n"
+"       gdm-autologin account  sufficient  pam_allow.so.1\n"
+"       gdm-autologin session  sufficient  pam_allow.so.1\n"
+"       gdm-autologin password  sufficient  pam_allow.so.1\n"
+msgstr ""
+
+#: C/gdm.xml:685(para)
+msgid "The above setup will cause no lastlog entry to be generated. If a lastlog entry is desired, then use the following for the session:"
+msgstr ""
+
+#: C/gdm.xml:690(screen)
+#, no-wrap
+msgid ""
+"\n"
+"       gdm-autologin session required pam_unix_session.so.1\n"
+msgstr ""
+
+#: C/gdm.xml:694(para)
+msgid "If the computer is used by several people, which makes automatic login unsuitable, you may want to allow some users to log in without entering their password. This feature can be enabled as a per-user option in the users-admin tool from the gnome-system-tools; it is achieved by checking that the user is member a Unix group called \"nopasswdlogin\" before asking for a password. For this to work, the PAM configuration file for the \"gdm\" service must include a line such as:"
+msgstr ""
+
+#: C/gdm.xml:705(screen)
+#, no-wrap
+msgid ""
+"\n"
+"      gdm auth  sufficient  pam_succeed_if.so  user ingroup nopasswdlogin\n"
+msgstr ""
+
+#: C/gdm.xml:712(title)
+msgid "utmp and wtmp"
+msgstr ""
+
+#: C/gdm.xml:714(para)
+msgid "GDM generates utmp and wtmp User Accounting Database entries upon session login and logout. The utmp database contains user access and accounting information that is accessed by commands such as <command>finger</command>, <command>last</command>, <command>login</command>, and <command>who</command>. The wtmp database contains the history of user access and accounting information for the utmp database. Refer to the <ulink type=\"help\" url=\"man:utmp\">utmp</ulink> and <ulink type=\"help\" url=\"man:wtmp\">wtmp</ulink> man pages on your system for more information."
+msgstr ""
+
+#: C/gdm.xml:729(title)
+msgid "Xserver Authentication Scheme"
+msgstr ""
+
+#: C/gdm.xml:731(para)
+msgid "Xserver authorization files are stored in a newly created subdirectory of <filename>&lt;var&gt;/run/gdm</filename> at start up. These files are used to store and share a \"password\" between X clients and the Xserver. This \"password\" is unique for each session logged in, so users from one session can't snoop on users from another."
+msgstr ""
+
+#: C/gdm.xml:739(para)
+msgid "GDM only supports the MIT-MAGIC-COOKIE-1 Xserver 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 Xserver 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. In most cases, ssh -Y should be preferred over GDM's XDMCP features."
+msgstr ""
+
+#: C/gdm.xml:756(title)
+msgid "XDMCP Security"
+msgstr ""
+
+#: C/gdm.xml:758(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:764(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. This type of set up should never use an unmanaged hub or other sniffable network."
+msgstr ""
+
+#: C/gdm.xml:777(title)
+msgid "XDMCP Access Control"
+msgstr ""
+
+#: C/gdm.xml:779(para)
+msgid "XDMCP access control is done using TCP wrappers. It is possible to compile GDM without TCP wrapper support, so this feature may not be supported on some Operating Systems."
+msgstr ""
+
+#: C/gdm.xml:785(para)
+msgid "You should use the daemon name <command>gdm</command> in the <filename>&lt;etc&gt;/hosts.allow</filename> and <filename>&lt;etc&gt;/hosts.deny</filename> files. For example to deny computers from <filename>.evil.domain</filename> from logging in, then add"
+msgstr ""
+
+#: C/gdm.xml:792(screen)
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .evil.domain\n"
+msgstr ""
+
+#: C/gdm.xml:795(para)
+msgid "to <filename>&lt;etc&gt;/hosts.deny</filename>. You may also need to add"
+msgstr ""
+
+#: C/gdm.xml:799(screen)
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .your.domain\n"
+msgstr ""
+
+#: C/gdm.xml:802(para)
+msgid "to your <filename>&lt;etc&gt;/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 ""
+
+#: C/gdm.xml:811(title)
+msgid "Firewall Security"
+msgstr ""
+
+#: C/gdm.xml:813(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 really needed. GDM guards against 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 do a denial of service attack via XDMCP than attacking a webserver."
+msgstr ""
+
+#: C/gdm.xml:824(para)
+msgid "It is also wise to block all of the Xserver ports. These are TCP ports 6000+ (one for each display number) on your firewall. Note that GDM will use display numbers 20 and higher for flexible on-demand servers."
+msgstr ""
+
+#: C/gdm.xml:831(para)
+msgid "X is not a very safe protocol when using it over the Internet, and XDMCP is even less safe."
+msgstr ""
+
+#: C/gdm.xml:838(title)
+msgid "PolicyKit"
+msgstr ""
+
+#. <para>
+#.         TODO - Should we say more?
+#. </para>
+#: C/gdm.xml:846(para)
+msgid "GDM may be configured to use PolicyKit to allow the system administrator to control whether the login screen should provide the shutdown and restart buttons on the greeter screen."
+msgstr ""
+
+#: C/gdm.xml:852(para)
+msgid "These buttons are controlled by the <filename>org.freedesktop.consolekit.system.stop-multiple-users</filename> and <filename>org.freedesktop.consolekit.system.restart-multiple-users</filename> actions respectively. Policy for these actions can be set up using the polkit-gnome-authorization tool, or the polkit-auth command line program."
+msgstr ""
+
+#: C/gdm.xml:864(title)
+msgid "RBAC (Role Based Access Control)"
+msgstr ""
+
+#: C/gdm.xml:866(para)
+msgid "GDM may be configured to use RBAC instead of PolicyKit. In this case the RBAC configuration is used to control whether the login screen should provide the shutdown and restart buttons on the greeter screen."
+msgstr ""
+
+#: C/gdm.xml:872(para)
+msgid "For example, on Solaris, the \"solaris.system.shutdown\" authorization is used to control this. Simply modify the <filename>/etc/user_attr</filename> file so that the \"gdm\" user has this authorization."
+msgstr ""
+
+#: C/gdm.xml:885(title)
+msgid "Support for ConsoleKit"
+msgstr ""
+
+#. <para>
+#.     TODO - Should we update these docs?  Probably should mention any
+#.            configuration that users may want to do for using it with GDM?
+#.            If so, perhaps this section should be moved to a subsection of
+#.            the "Configure" section?
+#. </para>
+#: C/gdm.xml:896(para)
+msgid "GDM includes support for publishing user login information with the user and login session accounting framework known as ConsoleKit. ConsoleKit is able to keep track of all the users currently logged in. In this respect, it can be used as a replacement for the utmp or utmpx files that are available on most Unix-like Operating Systems."
+msgstr ""
+
+#: C/gdm.xml:904(para)
+msgid "When GDM is about to create a new login process for a user it will call a privileged method of ConsoleKit in order to open a new session for this user. At this time GDM also provides ConsoleKit with information about this user session such as: the user ID, the X11 Display name that will be associated with the session, the host-name from which the session originates (useful in the case of an XDMCP session), whether or not this session is attached, etc. As the entity that initiates the user process, GDM is in a unique position to know about the user session and to be trusted to provide these bits of information. The use of this privileged method is restricted by the use of the D-Bus system message bus security policy."
+msgstr ""
+
+#: C/gdm.xml:918(para)
+msgid "In case a user with an existing session has authenticated at GDM and requests to resume that existing session, GDM calls a privileged method of ConsoleKit to unlock that session. The exact details of what happens when the session receives this unlock signal are undefined and session-specific. However, most sessions will unlock a screensaver in response."
+msgstr ""
+
+#: C/gdm.xml:927(para)
+msgid "When the user chooses to log out, or if GDM or the session quit unexpectedly the user session will be unregistered from ConsoleKit."
+msgstr ""
+
+#: C/gdm.xml:936(title)
+msgid "Configuration"
+msgstr ""
+
+#: C/gdm.xml:938(para)
+msgid "GDM has a number of configuration interfaces. These include scripting integration points, daemon configuration, greeter configuration, general session settings, integration with gnome-settings-daemon configuration, and session configuration. These types of integration are described in detail below."
+msgstr ""
+
+#: C/gdm.xml:947(title)
+msgid "Scripting Integration Points"
+msgstr ""
+
+#: C/gdm.xml:949(para)
+msgid "The GDM script integration points can be found in the <filename>&lt;etc&gt;/gdm/</filename> directory:"
+msgstr ""
+
+#: C/gdm.xml:954(screen)
+#, no-wrap
+msgid ""
+"\n"
+"Xsession\n"
+"Init/\n"
+"PostLogin/\n"
+"PreSession/\n"
+"PostSession/\n"
+msgstr ""
+
+#: C/gdm.xml:962(para)
+msgid "The <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename>, and <filename>PostSession</filename> scripts all work as described below."
+msgstr ""
+
+#: C/gdm.xml:968(para)
+msgid "For each type of script, the default one which will be executed is called \"Default\" and is stored in a directory associated with the script type. So the default <filename>Init</filename> script is <filename>&lt;etc&gt;/gdm/Init/Default</filename>. A per-display script can be provided, and if it exists it will be run instead of the default script. Such scripts are stored in the same directory as the default script and have the same name as the Xserver DISPLAY value for that display. For example, if the <filename>&lt;Init&gt;/:0</filename> script exists, it will be run for DISPLAY \":0\"."
+msgstr ""
+
+#: C/gdm.xml:980(para)
+msgid "All of these scripts are run with root privilege and return 0 if run successfully, and a non-zero return code if there was any failure that should cause the login session to be aborted. Also note that GDM will block until the scripts finish, so if any of these scripts hang, this will cause the login process to also hang."
+msgstr ""
+
+#: C/gdm.xml:988(para)
+msgid "When the Xserver for the login GUI has been successfully started, but before the login GUI is actually displayed, GDM will run the <filename>Init</filename> script. This script is useful for starting programs that should be run while the login screen is showing, or for doing any special initialization if required."
+msgstr ""
+
+#: C/gdm.xml:996(para)
+msgid "After the user has been successfully authenticated GDM will run the <filename>PostLogin</filename> script. This is done before any session setup has been done, including before the pam_open_session call. This script is useful for doing any session initialization that needs to happen before the session starts. For example, you might setup the user's $HOME directory if needed."
+msgstr ""
+
+#: C/gdm.xml:1005(para)
+msgid "After the user session has been initialized, GDM will run the <filename>PreSession</filename> script. This script is useful for doing any session initialization that needs to happen after the session has been initialized. It can be used for session management or accounting, for example."
+msgstr ""
+
+#: C/gdm.xml:1013(para)
+msgid "When a user terminates their session, GDM will run the <filename>PostSession</filename> script. Note that the Xserver will have been stopped by the time this script is run, so it should not be accessed."
+msgstr ""
+
+#: C/gdm.xml:1020(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 ""
+
+#: C/gdm.xml:1027(para)
+msgid "All of the above scripts will set the <filename>$RUNNING_UNDER_GDM</filename> environment variable to <filename>yes</filename>. If the scripts are also shared with other display managers, this allows you to identify when GDM is calling these scripts, so you can run specific code when GDM is used."
+msgstr ""
+
+#: C/gdm.xml:1037(title)
+msgid "Autostart Configuration"
+msgstr ""
+
+#: C/gdm.xml:1039(para)
+msgid "The <filename>&lt;share&gt;/gdm/autostart/LoginWindow</filename> directory contains files in the format specified by the \"FreeDesktop.org Desktop Application Autostart Specification\". Standard features in the specification may be used to specify programs that should auto-restart or only be launched if a GConf configuration value is set, etc."
+msgstr ""
+
+#: C/gdm.xml:1048(para)
+msgid "Any <filename>.desktop</filename> files in this directory will cause the associated program to automatically start with the login GUI greeter. By default, GDM is shipped with files which will autostart the gdm-simple-greeter login GUI greeter itself, the gnome-power-manager application, the gnome-settings-daemon, and the metacity window manager. These programs are needed for the greeter program to work. In addition, desktop files are provided for starting various AT programs if the configuration values specified in the Accessibility Configuration section below are set."
+msgstr ""
+
+#: C/gdm.xml:1062(title)
+msgid "Xsession Script"
+msgstr ""
+
+#: C/gdm.xml:1064(para)
+msgid "There is also an <filename>Xsession</filename> script located at <filename>&lt;etc&gt;/gdm/Xsession</filename> which is called between the <filename>PreSession</filename> and the <filename>PostSession</filename> scripts. This script does not support per-display like the other scripts. This script is used for actually starting the user session. This script is run as the user, and it will run whatever session was specified by the Desktop session file the user selected to start."
+msgstr ""
+
+#: C/gdm.xml:1077(title)
+msgid "Daemon Configuration"
+msgstr ""
+
+#: C/gdm.xml:1079(para)
+msgid "The GDM daemon is configured using the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file. Default values are stored in GConf in the <filename>gdm.schemas</filename> file. It is recommended that end-users modify the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file because the schemas file may be overwritten when the user updates their system to have a newer version of GDM."
+msgstr ""
+
+#: C/gdm.xml:1089(para)
+msgid "Note that older versions of GDM supported additional configuration options which are no longer supported in the latest versions of GDM."
+msgstr ""
+
+#: C/gdm.xml:1094(para)
+msgid "The <filename>&lt;etc&gt;/gdm/custom.conf</filename> file is in the <filename>keyfile</filename> format. Keywords in brackets define group sections, strings before an equal sign (=) are keys and the data after equal sign represents their value. Empty lines or lines starting with the hash mark (#) are ignored."
+msgstr ""
+
+#: C/gdm.xml:1102(para)
+msgid "The file <filename>&lt;etc&gt;/gdm/custom.conf</filename> supports the \"[daemon]\", \"[security]\", and \"[xdmcp]\" group sections. Within each group, there are particular key/value pairs that can be specified to modify how GDM behaves. For example, to enable timed login and specify the timed login user to be a user named \"you\", you would modify the file so it contains the following lines:"
+msgstr ""
+
+#: C/gdm.xml:1112(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[daemon]\n"
+"TimedLoginEnable=true\n"
+"TimedLogin=you\n"
+msgstr ""
+
+#: C/gdm.xml:1118(para)
+msgid "A full list of supported configuration keys follow:"
+msgstr ""
+
+#: C/gdm.xml:1123(title)
+msgid "[chooser]"
+msgstr ""
+
+#: C/gdm.xml:1127(term)
+msgid "Multicast"
+msgstr ""
+
+#: C/gdm.xml:1129(synopsis)
+#, no-wrap
+msgid "Multicast=false"
+msgstr ""
+
+#: C/gdm.xml:1130(para)
+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."
+msgstr ""
+
+#: C/gdm.xml:1139(term)
+msgid "MulticastAddr"
+msgstr ""
+
+#: C/gdm.xml:1141(synopsis)
+#, no-wrap
+msgid "MulticastAddr=ff02::1"
+msgstr ""
+
+#: C/gdm.xml:1142(para)
+msgid "This is the Link-local multicast address."
+msgstr ""
+
+#: C/gdm.xml:1151(title)
+msgid "[daemon]"
+msgstr ""
+
+#: C/gdm.xml:1154(term)
+msgid "TimedLoginEnable"
+msgstr ""
+
+#: C/gdm.xml:1156(synopsis)
+#, no-wrap
+msgid "TimedLoginEnable=false"
+msgstr ""
+
+#: C/gdm.xml:1157(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. Refer to the \"Security-&gt;PAM\" section of the manual for more information, or for help if this feature does not seem to work."
+msgstr ""
+
+#: C/gdm.xml:1179(term)
+msgid "TimedLogin"
+msgstr ""
+
+#: C/gdm.xml:1181(synopsis)
+#, no-wrap
+msgid "TimedLogin="
+msgstr ""
+
+#: C/gdm.xml:1182(para)
+msgid "This is the user that should be logged in after a specified number of seconds of inactivity."
+msgstr ""
+
+#: C/gdm.xml:1186(para)
+#: C/gdm.xml:1230(para)
+msgid "If the value ends with a vertical bar | (the pipe symbol), then GDM will execute the program specified and use whatever value is returned on standard out from the program as the user. The program is run with the DISPLAY environment variable set so that it is possible to specify the user in a per-display fashion. For example if the value is \"/usr/bin/getloginuser|\", then the program \"/usr/bin/getloginuser\" will be run to get the user value."
+msgstr ""
+
+#: C/gdm.xml:1200(term)
+msgid "TimedLoginDelay"
+msgstr ""
+
+#: C/gdm.xml:1202(synopsis)
+#, no-wrap
+msgid "TimedLoginDelay=30"
+msgstr ""
+
+#: C/gdm.xml:1203(para)
+msgid "Delay in seconds before the <filename>TimedLogin</filename> user will be logged in."
+msgstr ""
+
+#: C/gdm.xml:1211(term)
+msgid "AutomaticLoginEnable"
+msgstr ""
+
+#: C/gdm.xml:1213(synopsis)
+#, no-wrap
+msgid "AutomaticLoginEnable=false"
+msgstr ""
+
+#: C/gdm.xml:1214(para)
+msgid "If true, the user given in <filename>AutomaticLogin</filename> should be logged in immediately. This feature is like timed login with a delay of 0 seconds."
+msgstr ""
+
+#: C/gdm.xml:1223(term)
+msgid "AutomaticLogin"
+msgstr ""
+
+#: C/gdm.xml:1225(synopsis)
+#, no-wrap
+msgid "AutomaticLogin="
+msgstr ""
+
+#: C/gdm.xml:1226(para)
+msgid "This is the user that should be logged in immediately if <filename>AutomaticLoginEnable</filename> is true."
+msgstr ""
+
+#: C/gdm.xml:1244(term)
+msgid "User"
+msgstr "Uporabnik"
+
+#: C/gdm.xml:1246(synopsis)
+#, no-wrap
+msgid "User=gdm"
+msgstr ""
+
+#: C/gdm.xml:1247(para)
+msgid "The username under which the greeter and other GUI programs are run. Refer to the <filename>Group</filename> configuration key and to the \"Security-&gt;GDM User And Group\" section of this document for more information."
+msgstr ""
+
+#: C/gdm.xml:1257(term)
+msgid "Group"
+msgstr "Skupina"
+
+#: C/gdm.xml:1259(synopsis)
+#, no-wrap
+msgid "Group=gdm"
+msgstr ""
+
+#: C/gdm.xml:1260(para)
+msgid "The group name under which the greeter and other GUI programs are run. Refer to the <filename>User</filename> configuration key and to the \"Security-&gt;GDM User And Group\" section of this document for more information."
+msgstr ""
+
+#: C/gdm.xml:1272(title)
+msgid "Debug Options"
+msgstr ""
+
+#: C/gdm.xml:1275(title)
+msgid "[debug]"
+msgstr ""
+
+#: C/gdm.xml:1278(term)
+#: C/gdm.xml:1408(term)
+msgid "Enable"
+msgstr ""
+
+#: C/gdm.xml:1280(synopsis)
+#: C/gdm.xml:1410(synopsis)
+#, no-wrap
+msgid "Enable=false"
+msgstr ""
+
+#: C/gdm.xml:1281(para)
+msgid "To enable debugging, set the debug/Enable key to \"true\" in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file and restart GDM. Then debug output will be sent to the system log file (<filename>&lt;var&gt;/log/messages</filename> or <filename>&lt;var&gt;/adm/messages</filename> depending on your Operating System)."
+msgstr ""
+
+#: C/gdm.xml:1296(title)
+msgid "Greeter Options"
+msgstr ""
+
+#: C/gdm.xml:1299(title)
+msgid "[greeter]"
+msgstr ""
+
+#: C/gdm.xml:1302(term)
+msgid "IncludeAll"
+msgstr ""
+
+#: C/gdm.xml:1304(synopsis)
+#, no-wrap
+msgid "IncludeAll=true"
+msgstr ""
+
+#: C/gdm.xml:1305(para)
+msgid "If true, then the face browser will show all users on the local machine. If false, the face browser will only show users who have recently logged in."
+msgstr ""
+
+#: C/gdm.xml:1311(para)
+msgid "When this key is true, GDM will call fgetpwent() to get a list of local users on the system. Any users with a user id less than 500 (or 100 if running on Solaris) are filtered out. The Face Browser also will display any users that have previously logged in on the system (for example NIS/LDAP users). It gets this list via calling the <command>ck-history</command> ConsoleKit interface. It will also filter out any users which do not have a valid shell (valid shells are any shell that getusershell() returns - /sbin/nologin or /bin/false are considered invalid shells even if getusershell() returns them)."
+msgstr ""
+
+#: C/gdm.xml:1324(para)
+msgid "If false, then GDM more simply only displays users that have previously logged in on the system (local or NIS/LDAP users) by calling the <command>ck-history</command> ConsoleKit interface."
+msgstr ""
+
+#: C/gdm.xml:1333(term)
+msgid "Include"
+msgstr ""
+
+#: C/gdm.xml:1335(synopsis)
+#, no-wrap
+msgid "Include="
+msgstr ""
+
+#: C/gdm.xml:1336(para)
+msgid "Set to a list of users to always include in the Face Browser. This value is set to a list of users separated by commas. By default, the value is empty."
+msgstr ""
+
+#: C/gdm.xml:1345(term)
+msgid "Exclude"
+msgstr ""
+
+#: C/gdm.xml:1347(synopsis)
+#, no-wrap
+msgid "Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap"
+msgstr ""
+
+#: C/gdm.xml:1348(para)
+msgid "Set to a list of users to always exclude in the Face Browser. This value is set to a list of users separated by commas. Note that the setting in the <filename>custom.conf</filename> overrides the default value, so if you wish to add additional users to the list, then you need to set the value to the default value with additional users appended to the list."
+msgstr ""
+
+#: C/gdm.xml:1362(title)
+msgid "Security Options"
+msgstr ""
+
+#: C/gdm.xml:1365(title)
+msgid "[security]"
+msgstr ""
+
+#: C/gdm.xml:1368(term)
+msgid "DisallowTCP"
+msgstr ""
+
+#: C/gdm.xml:1370(synopsis)
+#, no-wrap
+msgid "DisallowTCP=true"
+msgstr ""
+
+#: C/gdm.xml:1371(para)
+msgid "If true, then always append <filename>-nolisten tcp</filename> to the command line when starting attached Xservers, thus disallowing TCP connection. This is a more secure configuration if you are not using remote connections."
+msgstr ""
+
+#: C/gdm.xml:1383(title)
+msgid "XDCMP Support"
+msgstr ""
+
+#: C/gdm.xml:1386(title)
+msgid "[xdmcp]"
+msgstr ""
+
+#: C/gdm.xml:1389(term)
+msgid "DisplaysPerHost"
+msgstr ""
+
+#: C/gdm.xml:1391(synopsis)
+#, no-wrap
+msgid "DisplaysPerHost=1"
+msgstr ""
+
+#: C/gdm.xml:1392(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 this value."
+msgstr ""
+
+#: C/gdm.xml:1399(para)
+msgid "Note that the number of attached DISPLAYS allowed is not limited. Only remote connections via XDMCP are limited by this configuration option."
+msgstr ""
+
+#: C/gdm.xml:1411(para)
+msgid "Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM."
+msgstr ""
+
+#: C/gdm.xml:1416(para)
+msgid "<filename>gdm</filename> listens for requests on UDP port 177. See the Port option for more information."
+msgstr ""
+
+#: C/gdm.xml:1421(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 ""
+
+#: C/gdm.xml:1427(para)
+msgid ""
+"You should add <screen>\n"
+"gdm:.my.domain\n"
+"</screen> to your <filename>&lt;etc&gt;/hosts.allow</filename>, depending on your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow</ulink> man page for details."
+msgstr ""
+
+#: C/gdm.xml:1438(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 ""
+
+#: C/gdm.xml:1447(term)
+msgid "HonorIndirect"
+msgstr ""
+
+#: C/gdm.xml:1449(synopsis)
+#, no-wrap
+msgid "HonorIndirect=true"
+msgstr ""
+
+#: C/gdm.xml:1450(para)
+msgid "Enables XDMCP INDIRECT choosing (i.e. remote execution of <filename>gdmchooser</filename>) for X-terminals which do not supply their own display browser."
+msgstr ""
+
+#: C/gdm.xml:1459(term)
+msgid "MaxPending"
+msgstr ""
+
+#: C/gdm.xml:1461(synopsis)
+#, no-wrap
+msgid "MaxPending=4"
+msgstr ""
+
+#: C/gdm.xml:1462(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:1468(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:1477(term)
+msgid "MaxSessions"
+msgstr ""
+
+#: C/gdm.xml:1479(synopsis)
+#, no-wrap
+msgid "MaxSessions=16"
+msgstr ""
+
+#: C/gdm.xml:1480(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:1489(term)
+msgid "MaxWait"
+msgstr ""
+
+#: C/gdm.xml:1491(synopsis)
+#, no-wrap
+msgid "MaxWait=30"
+msgstr ""
+
+#: C/gdm.xml:1492(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:1498(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:1503(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:1512(term)
+msgid "MaxWaitIndirect"
+msgstr ""
+
+#: C/gdm.xml:1514(synopsis)
+#, no-wrap
+msgid "MaxWaitIndirect=30"
+msgstr ""
+
+#: C/gdm.xml:1515(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 ""
+
+#: C/gdm.xml:1529(term)
+msgid "PingIntervalSeconds"
+msgstr ""
+
+#: C/gdm.xml:1531(synopsis)
+#, no-wrap
+msgid "PingIntervalSeconds=60"
+msgstr ""
+
+#: C/gdm.xml:1532(para)
+msgid "If the Xserver does not respond in the specified number of seconds, then the connection is stopped and the session ended. When this happens the slave daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied this setting by 2, so it may be necessary to increase the timeout if upgrading from GDM 2.20 and earlier to a newer version."
+msgstr ""
+
+#: C/gdm.xml:1541(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 than 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 ""
+
+#: C/gdm.xml:1554(term)
+msgid "Port"
+msgstr ""
+
+#: C/gdm.xml:1556(synopsis)
+#, no-wrap
+msgid "Port=177"
+msgstr ""
+
+#: C/gdm.xml:1557(para)
+msgid "The UDP port number <filename>gdm</filename> should listen to for XDMCP requests. Do not change this unless you know what you are doing."
+msgstr ""
+
+#: C/gdm.xml:1566(term)
+msgid "Willing"
+msgstr ""
+
+#: C/gdm.xml:1568(synopsis)
+#, no-wrap
+msgid "Willing=&lt;etc&gt;/gdm/Xwilling"
+msgstr ""
+
+#: C/gdm.xml:1569(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 does not 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 ""
+
+#: C/gdm.xml:1588(title)
+msgid "Simple Greeter Configuration"
+msgstr ""
+
+#: C/gdm.xml:1590(para)
+msgid "The GDM default greeter is called the simple Greeter and is configured via GConf. Default values are stored in GConf in the <filename>gdm-simple-greeter.schemas</filename> file. These defaults can be overridden if the \"gdm\" user has a writable $HOME directory to store GConf settings. These values can be edited using the <command>gconftool-2</command> or <command>gconf-editor</command> programs. The following configuration options are supported:"
+msgstr ""
+
+#: C/gdm.xml:1601(title)
+msgid "Greeter Configuration Keys"
+msgstr ""
+
+#: C/gdm.xml:1604(term)
+msgid "/apps/gdm/simple-greeter/banner_message_enable"
+msgstr ""
+
+#: C/gdm.xml:1606(synopsis)
+#: C/gdm.xml:1627(synopsis)
+#: C/gdm.xml:1638(synopsis)
+#: C/gdm.xml:1703(synopsis)
+#: C/gdm.xml:1768(synopsis)
+#: C/gdm.xml:1779(synopsis)
+#: C/gdm.xml:1790(synopsis)
+#: C/gdm.xml:1801(synopsis)
+#, no-wrap
+msgid "false (boolean)"
+msgstr ""
+
+#: C/gdm.xml:1607(para)
+msgid "Controls whether the banner message text is displayed."
+msgstr ""
+
+#: C/gdm.xml:1614(term)
+msgid "/apps/gdm/simple-greeter/banner_message_text"
+msgstr ""
+
+#: C/gdm.xml:1616(synopsis)
+#, no-wrap
+msgid "NULL (string)"
+msgstr ""
+
+#: C/gdm.xml:1617(para)
+msgid "Specifies the text banner message to show on the greeter window."
+msgstr ""
+
+#: C/gdm.xml:1625(term)
+msgid "/apps/gdm/simple-greeter/disable_restart_buttons"
+msgstr ""
+
+#: C/gdm.xml:1628(para)
+msgid "Controls whether to show the restart buttons in the login window."
+msgstr ""
+
+#: C/gdm.xml:1636(term)
+msgid "/apps/gdm/simple-greeter/disable_user_list"
+msgstr ""
+
+#: C/gdm.xml:1639(para)
+msgid "If true, then the face browser with known users is not shown in the login window."
+msgstr ""
+
+#: C/gdm.xml:1647(term)
+msgid "/apps/gdm/simple-greeter/logo_icon_name"
+msgstr ""
+
+#: C/gdm.xml:1649(synopsis)
+#, no-wrap
+msgid "computer (string)"
+msgstr ""
+
+#: C/gdm.xml:1650(para)
+msgid "Set to the themed icon name to use for the greeter logo."
+msgstr ""
+
+#: C/gdm.xml:1657(term)
+msgid "/apps/gdm/simple-greeter/recent-languages"
+msgstr ""
+
+#: C/gdm.xml:1659(synopsis)
+#: C/gdm.xml:1681(synopsis)
+#, no-wrap
+msgid "[] (string list)"
+msgstr ""
+
+#: C/gdm.xml:1660(para)
+msgid "Set to a list of languages to be shown by default in the login window. Default value is \"[]\". With the default setting only the system default language is shown and the option \"Other...\" which pops-up a dialog box showing a full list of available languages which the user can select."
+msgstr ""
+
+#: C/gdm.xml:1668(para)
+msgid "Users are not intended to change this setting by hand. Instead GDM keeps track of any languages selected in this configuration key, and will show them in the language combo box along with the \"Other...\" choice. This way, commonly selected languages are easier to select."
+msgstr ""
+
+#: C/gdm.xml:1679(term)
+msgid "/apps/gdm/simple-greeter/recent-layouts"
+msgstr ""
+
+#: C/gdm.xml:1682(para)
+msgid "Set to a list of keyboard layouts to be shown by default in the login panel. Default value is \"[]\". With the default setting only the system default keyboard layout is shown and the option \"Other...\" which pops-up a dialog box showing a full list of available keyboard layouts which the user can select."
+msgstr ""
+
+#: C/gdm.xml:1690(para)
+msgid "Users are not intended to change this setting by hand. Instead GDM keeps track of any keyboard layouts selected in this configuration key, and will show them in the keyboard layout combo box along with the \"Other...\" choice. This way, commonly selected keyboard layouts are easier to select."
+msgstr ""
+
+#: C/gdm.xml:1701(term)
+msgid "/apps/gdm/simple-greeter/wm_use_compiz"
+msgstr ""
+
+#: C/gdm.xml:1704(para)
+msgid "Controls whether compiz is used as the window manager instead of metacity."
+msgstr ""
+
+#: C/gdm.xml:1714(title)
+msgid "Accessibility Configuration"
+msgstr ""
+
+#: C/gdm.xml:1716(para)
+msgid "This section describes the accessibility configuration options available in GDM."
+msgstr ""
+
+#: C/gdm.xml:1722(title)
+msgid "GDM Accessibility Dialog And GConf Keys"
+msgstr ""
+
+#: C/gdm.xml:1724(para)
+msgid "The GDM greeter panel at the login screen displays an accessibility icon. Clicking on that icon opens the GDM Accessibility Dialog. In the GDM Accessibility Dialog, there is a list of checkboxes, so the user can enable or disable the associated assistive tools."
+msgstr ""
+
+#: C/gdm.xml:1731(para)
+msgid "The checkboxes that correspond to the on-screen keyboard, screen magnifier and screen reader assistive tools act on the three GConf keys that are described in the next section of this document. By enabling or disabling these checkboxes, the associated GConf key is set to \"true\" or \"false\". When the GConf key is set to true, the assistive tools linked to this GConf key are launched. When the GConf key is set to \"false\", any running assistive tool linked to this GConf key are terminated. These GConf keys are not automatically reset to a default state after the user has logged in. Consequently, the assistive tools that were running during the last GDM login session will automatically be launched at the next GDM login session."
+msgstr ""
+
+#: C/gdm.xml:1745(para)
+msgid "The other checkboxes in the GDM Accessibility Dialog do not have corresponding GConf keys because no additional program is launched to provide the accessibility features that they offer. These other options correspond to accessibility features that are provided by the Xserver, which is always running during the GDM session."
+msgstr ""
+
+#: C/gdm.xml:1755(title)
+msgid "Accessibility GConf Keys"
+msgstr ""
+
+#: C/gdm.xml:1757(para)
+msgid "GDM offers the following GConf keys to control its accessibility features:"
+msgstr ""
+
+#: C/gdm.xml:1763(title)
+msgid "GDM Configuration Keys"
+msgstr ""
+
+#: C/gdm.xml:1766(term)
+msgid "/desktop/gnome/interface/accessibility"
+msgstr ""
+
+#: C/gdm.xml:1769(para)
+msgid "Controls whether the Accessibility infrastructure will be started with the GDM GUI. This is needed for many accessibility technology programs to work."
+msgstr ""
+
+#: C/gdm.xml:1777(term)
+msgid "/desktop/gnome/applications/at/screen_magnifier_enabled"
+msgstr ""
+
+#: C/gdm.xml:1780(para)
+msgid "If set, then the assistive tools linked to this GConf key will be started with the GDM GUI program. By default this is a screen magnifier application."
+msgstr ""
+
+#: C/gdm.xml:1788(term)
+msgid "/desktop/gnome/applications/at/screen_keyboard_enabled"
+msgstr ""
+
+#: C/gdm.xml:1791(para)
+msgid "If set, then the assistive tools linked to this GConf key will be started with the GDM GUI program. By default this is an on-screen keyboard application."
+msgstr ""
+
+#: C/gdm.xml:1799(term)
+msgid "/desktop/gnome/applications/at/screen_reader_enabled"
+msgstr ""
+
+#: C/gdm.xml:1802(para)
+msgid "If set, then the assistive tools linked to this GConf key will be started with the GDM GUI program. By default this is a screen reader application."
+msgstr ""
+
+#: C/gdm.xml:1813(title)
+msgid "Linking GConf Keys to Accessbility Tools"
+msgstr ""
+
+#: C/gdm.xml:1815(para)
+msgid "For the screen_magnifier_enabled, the screen_keyboard_enabled, and the screen_reader_enabled GConf keys, the assistive tool which gets launched depends on the desktop files located in the GDM autostart directory as described in the \"Autostart Configuration\" section of this manual. Any desktop file in the GDM autostart directory can be linked to these GConf key via specifying that GConf key in the AutostartCondition value in the desktop file. So the exact AutostartCondition line in the desktop file could be one of the following:"
+msgstr ""
+
+#: C/gdm.xml:1827(screen)
+#, no-wrap
+msgid ""
+"\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled\n"
+msgstr ""
+
+#: C/gdm.xml:1833(para)
+msgid "When an accessibility key is true, then any program which is linked to that key in a GDM autostart desktop file will be launched (unless the Hidden key is set to true in that desktop file). A single GConf key can even start multiple assistive tools if there are multiple desktop files with this AutostartCondition in the GDM autostart directory."
+msgstr ""
+
+#: C/gdm.xml:1843(title)
+msgid "Example Of Modifying Accessibility Tool Configuration"
+msgstr ""
+
+#: C/gdm.xml:1845(para)
+msgid "For example, if GNOME is distributed with GOK as the default on-screen keyboard, then this could be replaced with a different program if desired. To replace GOK with the on-screen keyboard application \"onboard\" and additionally activate the assistive tool \"mousetweaks\" for dwelling support, then the following configuration is needed."
+msgstr ""
+
+#: C/gdm.xml:1853(para)
+msgid "Create a desktop file for onboard and a second one for mousetweaks; for example, onboard.desktop and mousetweaks.desktop. These files must be placed in the GDM autostart directory and be in the format as explained in the \"Autostart Configuration\" section of this document."
+msgstr ""
+
+#: C/gdm.xml:1861(para)
+msgid "The following is an example <filename>onboard.desktop</filename> file:"
+msgstr ""
+
+#: C/gdm.xml:1865(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Onboard Onscreen Keyboard\n"
+"Comment=Use an on-screen keyboard\n"
+"TryExec=onboard\n"
+"Exec=onboard --size 500x180 -x 20 -y 10\n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+msgstr ""
+
+#: C/gdm.xml:1879(para)
+msgid "The following is an example <filename>mousetweaks.desktop</filename> file:"
+msgstr ""
+
+#: C/gdm.xml:1884(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Software Mouse-Clicks\n"
+"Comment=Perform clicks by dwelling with the pointer\n"
+"TryExec=mousetweaks\n"
+"Exec=mousetweaks --enable-dwell -m window -c -x 20 -y 240 \n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+msgstr ""
+
+#: C/gdm.xml:1898(para)
+msgid "Note the line with the AutostartCondition that links both desktop files to the GConf key for the on-screen keyboard."
+msgstr ""
+
+#: C/gdm.xml:1903(para)
+msgid "To disable GOK from starting, the desktop file for the GOK on-screen keyboard must be removed or deactivated. Otherwise onboard and GOK would simultaneously be started. This can be done by removing the gok.desktop file from the GDM autostart directory, or by adding the \"Hidden=true\" key setting to the gok.desktop file."
+msgstr ""
+
+#: C/gdm.xml:1911(para)
+msgid "After making these changes, GOK will no longer be started when the user activates the on-screen keyboard in the GDM session; but onboard and mousetweaks will instead be launched."
+msgstr ""
+
+#: C/gdm.xml:1920(title)
+msgid "General Session Settings"
+msgstr ""
+
+#. <para>
+#.           TODO - I think this section should be expanded upon.  What specific
+#.                  keys are of interest, or would some users be likely to want
+#.                  to configure?  Also, would be good to be more specific about
+#.                  how lock down management is handled.
+#. </para>
+#: C/gdm.xml:1929(para)
+msgid "The GDM Greeter uses some of the same framework that your desktop session will use. And so, it is influenced by a number of the same GConf settings. For each of these settings the Greeter will use the default value unless it is specifically overridden by a) GDM's installed mandatory policy b) system mandatory policy. GDM installs its own mandatory policy to lock down some settings for security."
+msgstr ""
+
+#: C/gdm.xml:1940(title)
+msgid "GNOME Settings Daemon"
+msgstr ""
+
+#. <para>
+#.           TODO - I think this section should be expanded upon.  What specific
+#.                  keys are of interest, or would some users be likely to want
+#.                  to configure?  Also, would be good to give a more complete
+#.                  list of plugins that users might want to consider disabling.
+#.                  Also, shouldn't we list the sound/active key in the Greeter
+#.                  configuration setting?  Oddly I do not find this key used
+#.                  in anything but the chooser in SVN.
+#. </para>
+#: C/gdm.xml:1953(para)
+msgid "GDM enables the following gnome-settings-daemon plugins: a11y-keyboard, background, sound, xsettings."
+msgstr ""
+
+#: C/gdm.xml:1958(para)
+msgid "These are responsible for things like the background image, font and theme settings, sound events, etc."
+msgstr ""
+
+#: C/gdm.xml:1963(para)
+msgid "Plugins can also be disabled using GConf. For example, if you want to disable the sound plugin then unset the following key: <filename>/apps/gdm/simple-greeter/settings-manager-plugins/sound/active</filename>."
+msgstr ""
+
+#: C/gdm.xml:1971(title)
+msgid "GDM Session Configuration"
+msgstr ""
+
+#: C/gdm.xml:1973(para)
+msgid "GDM sessions are specified using the FreeDesktop.org Desktop Entry Specification, which can be referenced at the following URL: <ulink url=\"http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec\"> http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec</ulink>."
+msgstr ""
+
+#: C/gdm.xml:1980(para)
+msgid "By default, GDM will install desktop files in the <filename>&lt;share&gt;/xsessions</filename> directory. GDM will search the following directories in this order to find desktop files: <filename>&lt;etc&gt;/X11/sessions/</filename>, <filename>&lt;dmconfdir&gt;/Sessions</filename>, <filename>&lt;share&gt;/xsessions</filename>, and <filename>&lt;share&gt;/gdm/BuiltInSessions</filename>. By default the <filename>&lt;dmconfdir&gt;</filename> is set to <filename>&lt;etc&gt;/dm/</filename> unless GDM is configured to use a different directory via the \"--with-dmconfdir\" option."
+msgstr ""
+
+#: C/gdm.xml:1993(para)
+msgid "A session can be disabled by editing the desktop file and adding a line as follows: <filename>Hidden=true</filename>."
+msgstr ""
+
+#: C/gdm.xml:1998(para)
+msgid "GDM desktop files support a GDM-specific extension, a key named \"X-GDM-BypassXsession\". If the key is not specified in a desktop file, the value defaults to \"false\". If this key is specified to be \"true\" in a desktop file, then GDM will launch the program specified by the desktop file \"Exec\" key directly when starting the user session. It will not run the program via the <filename>&lt;etc&gt;/gdm/Xsession</filename> script, which is the normal behavior. Since bypassing the <filename>&lt;etc&gt;/gdm/Xsession</filename> script avoids setting up the user session with the normal system and user settings, sessions started this way can be useful for debugging problems in the system or user scripts that might be preventing a user from being able to start a session."
+msgstr ""
+
+#: C/gdm.xml:2017(title)
+msgid "GDM User Session and Language Configuration"
+msgstr ""
+
+#: C/gdm.xml:2018(para)
+msgid "The user's default session and language choices are stored in the <filename>~/.dmrc</filename> file. When a user logs in for the first time, this file is created with the user's initial choices. The user can change these default values by simply changing to a different value when logging in. GDM will remember this change for subsequent logins."
+msgstr ""
+
+#: C/gdm.xml:2026(para)
+msgid "The <filename>~/.dmrc</filename> file is in the standard <filename>INI</filename> format. It has one section called <filename>[Desktop]</filename> which has two keys: <filename>Session</filename> and <filename>Language</filename>."
+msgstr ""
+
+#: C/gdm.xml:2033(para)
+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. 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 ""
+
+#: C/gdm.xml:2042(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop]\n"
+"Session=gnome\n"
+"Language=cs_CZ.UTF-8\n"
+msgstr ""
+
+#: C/gdm.xml:2054(title)
+msgid "GDM Commands"
+msgstr ""
+
+#: C/gdm.xml:2057(title)
+msgid "GDM Root User Commands"
+msgstr ""
+
+#: C/gdm.xml:2059(para)
+msgid "The GDM package provides the following commands in <filename>sbindir</filename> intended to be run by the root user:"
+msgstr ""
+
+#: C/gdm.xml:2065(title)
+#: C/gdm.xml:2080(title)
+msgid "<command>gdm</command> and <command>gdm-binary</command> Command Line Options"
+msgstr ""
+
+#: C/gdm.xml:2068(para)
+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>&lt;etc&gt;/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. The <command>gdm-binary</command> is the actual GDM daemon."
+msgstr ""
+
+#: C/gdm.xml:2084(term)
+msgid "-?, --help"
+msgstr ""
+
+#: C/gdm.xml:2086(para)
+msgid "Gives a brief overview of the command line options."
+msgstr ""
+
+#: C/gdm.xml:2093(term)
+msgid "--fatal-warnings"
+msgstr ""
+
+#: C/gdm.xml:2095(para)
+msgid "Make all warnings cause GDM to exit."
+msgstr ""
+
+#: C/gdm.xml:2102(term)
+msgid "--timed-exit"
+msgstr ""
+
+#: C/gdm.xml:2104(para)
+msgid "Exit after 30 seconds. Useful for debugging."
+msgstr ""
+
+#: C/gdm.xml:2111(term)
+msgid "--version"
+msgstr ""
+
+#: C/gdm.xml:2113(para)
+msgid "Print the version of the GDM daemon."
+msgstr ""
+
+#: C/gdm.xml:2122(title)
+msgid "<command>gdm-restart</command> Command Line Options"
+msgstr ""
+
+#: C/gdm.xml:2124(para)
+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 ""
+
+#: C/gdm.xml:2132(title)
+msgid "<command>gdm-safe-restart</command> Command Line Options"
+msgstr ""
+
+#: C/gdm.xml:2134(para)
+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 ""
+
+#: C/gdm.xml:2142(title)
+msgid "<command>gdm-stop</command> Command Line Options"
+msgstr ""
+
+#: C/gdm.xml:2144(para)
+msgid "<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM signal."
+msgstr ""
+
+#: C/gdm.xml:2155(title)
+msgid "Troubleshooting"
+msgstr ""
+
+#. <para>
+#.       TODO - any other tips we should add?  Might be useful to highlight any
+#.              common D-Bus configuration issues?
+#. </para>
+#: C/gdm.xml:2163(para)
+msgid "This section discusses helpful tips for getting GDM working. In general, if you have a problem using GDM, you can submit a bug or send an email to the gdm-list mailing list. Information about how to do this is in the Introduction section of the document."
+msgstr ""
+
+#: C/gdm.xml:2170(para)
+msgid "If GDM is failing to work properly, it is always a good idea to include debug information. To enable debugging, set the debug/Enable key to \"true\" in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file and restart GDM. Then use GDM to the point where it fails, and debug output will be sent to the system log file (<filename>&lt;var&gt;/log/messages</filename> or <filename>&lt;var&gt;/adm/messages</filename> depending on your Operating System). If you share this output with the GDM community via a bug report or email, please only include the GDM related debug information and not the entire file since it can be large. If you do not see any GDM syslog output, you may need to configure syslog (refer to the <ulink type=\"help\" url=\"man:syslog\">syslog</ulink> man page)."
+msgstr ""
+
+#: C/gdm.xml:2186(title)
+msgid "GDM Will Not Start"
+msgstr ""
+
+#: C/gdm.xml:2188(para)
+msgid "There are a many problems that can cause GDM to fail to start, but this section will discuss a few common problems and how to approach tracking down a problem with GDM starting. Some problems will cause GDM to respond with an error message or dialog when it tries to start, but it can be difficult to track down problems when GDM fails silently."
+msgstr ""
+
+#: C/gdm.xml:2197(para)
+msgid "First make sure that the Xserver is configured properly. The GDM configuration file contains a command in the [server-Standard] section that is used for starting the Xserver. Verify that this command works on your system. Running this command from the console should start the Xserver. If it fails, then the problem is likely with your Xserver configuration. Refer to your Xserver error log for an idea of what the problem may be. The problem may also be that your Xserver requires different command-line options. If so, then modify the Xserver command in the GDM configuration file so that it is correct for your system."
+msgstr ""
+
+#: C/gdm.xml:2210(para)
+msgid "Also make sure that the <filename>/tmp</filename> directory has reasonable ownership and permissions, and that the machine's file system is not full. These problems will cause GDM to fail to start."
+msgstr ""
+
+#: C/gdm.xml:2221(title)
+msgid "License"
+msgstr "Dovoljenje"
+
+#: C/gdm.xml:2222(para)
+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 ""
+
+#: C/gdm.xml:2230(para)
+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 ""
+
+#: C/gdm.xml:2236(para)
+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>51 Franklin Street, Fifth Floor</street><city>Boston</city>, <state>MA</state><postcode>02110-1301</postcode><country>USA</country></address>"
+msgstr ""
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
+#: C/gdm.xml:0(None)
+msgid "translator-credits"
+msgstr ""
+
diff --git a/docs/te/te.po b/docs/te/te.po
new file mode 100644
index 0000000..f46acaf
--- /dev/null
+++ b/docs/te/te.po
@@ -0,0 +1,2514 @@
+# Telugu translation for gdm.
+# Copyright (C) 2011, 2012 Swecha Telugu Localisation Team <localization@swecha.net>
+# This file is distributed under the same license as the gdm package.
+# Bhuvan Krishna <bhuvan@swecha.net>, 2012.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: gdm master\n"
+"POT-Creation-Date: 2012-03-25 07:01+0000\n"
+"PO-Revision-Date: 2012-03-25 16:12+0530\n"
+"Last-Translator: Bhuvan Krishna <bhuvan@swecha.net>\n"
+"Language-Team: Telugu <indlinux-telugu@lists.sourceforge.net>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n!=1);\n"
+
+#: C/gdm.xml:13(title)
+msgid "GNOME Display Manager Reference Manual"
+msgstr ""
+
+#: C/gdm.xml:17(revnumber)
+msgid "0.0"
+msgstr "0.0"
+
+#: C/gdm.xml:18(date)
+msgid "2008-09"
+msgstr "2008-09"
+
+#: C/gdm.xml:23(para)
+msgid "GDM is the GNOME Display Manager, a graphical login program."
+msgstr ""
+
+#: C/gdm.xml:30(firstname)
+msgid "Martin"
+msgstr ""
+
+#: C/gdm.xml:30(othername)
+msgid "K."
+msgstr ""
+
+#: C/gdm.xml:31(surname)
+msgid "Petersen"
+msgstr ""
+
+#: C/gdm.xml:33(email)
+msgid "mkp@mkp.net"
+msgstr "mkp@mkp.net"
+
+#: C/gdm.xml:37(firstname)
+msgid "George"
+msgstr ""
+
+#: C/gdm.xml:37(surname)
+msgid "Lebl"
+msgstr ""
+
+#: C/gdm.xml:39(email)
+msgid "jirka@5z.com"
+msgstr "jirka@5z.com"
+
+#: C/gdm.xml:43(firstname)
+msgid "Jon"
+msgstr ""
+
+#: C/gdm.xml:43(surname)
+msgid "McCann"
+msgstr ""
+
+#: C/gdm.xml:45(email)
+msgid "mccann@jhu.edu"
+msgstr "mccann@jhu.edu"
+
+#: C/gdm.xml:49(firstname)
+msgid "Ray"
+msgstr ""
+
+#: C/gdm.xml:49(surname)
+msgid "Strode"
+msgstr ""
+
+#: C/gdm.xml:51(email)
+msgid "rstrode@redhat.com"
+msgstr "rstrode@redhat.com"
+
+#: C/gdm.xml:55(firstname)
+msgid "Brian"
+msgstr ""
+
+#: C/gdm.xml:55(surname)
+msgid "Cameron"
+msgstr ""
+
+#: C/gdm.xml:57(email)
+msgid "Brian.Cameron@Oracle.COM"
+msgstr ""
+
+#: C/gdm.xml:62(year)
+msgid "1998"
+msgstr "1998"
+
+#: C/gdm.xml:63(year)
+msgid "1999"
+msgstr "1999"
+
+#: C/gdm.xml:64(holder)
+msgid "Martin K. Petersen"
+msgstr ""
+
+#: C/gdm.xml:67(year)
+msgid "2001"
+msgstr "2001"
+
+#: C/gdm.xml:68(year) C/gdm.xml:73(year) C/gdm.xml:79(year)
+msgid "2003"
+msgstr "2003"
+
+#: C/gdm.xml:69(year)
+msgid "2004"
+msgstr "2004"
+
+#: C/gdm.xml:70(holder)
+msgid "George Lebl"
+msgstr ""
+
+#: C/gdm.xml:74(year)
+msgid "2007"
+msgstr "2007"
+
+#: C/gdm.xml:75(year)
+msgid "2008"
+msgstr "2008"
+
+#: C/gdm.xml:76(holder)
+msgid "Red Hat, Inc."
+msgstr "రెడ్ హ్యాట్, ఇంక్."
+
+#: C/gdm.xml:80(year)
+msgid "2011"
+msgstr "2011"
+
+#: C/gdm.xml:81(holder)
+msgid "Oracle and/or its affiliates. All rights reserved."
+msgstr ""
+
+#: C/gdm.xml:2(para)
+msgid ""
+"Permission is granted to copy, distribute and/or modify this document under "
+"the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any "
+"later version published by the Free Software Foundation with no Invariant "
+"Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy "
+"of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or "
+"in the file COPYING-DOCS distributed with this manual."
+msgstr ""
+
+#: C/gdm.xml:12(para)
+msgid ""
+"This manual is part of a collection of GNOME manuals distributed under the "
+"GFDL. If you want to distribute this manual separately from the collection, "
+"you can do so by adding a copy of the license to the manual, as described in "
+"section 6 of the license."
+msgstr ""
+
+#: C/gdm.xml:19(para)
+msgid ""
+"Many of the names used by companies to distinguish their products and "
+"services are claimed as trademarks. Where those names appear in any GNOME "
+"documentation, and the members of the GNOME Documentation Project are made "
+"aware of those trademarks, then the names are in capital letters or initial "
+"capital letters."
+msgstr ""
+
+#: C/gdm.xml:35(para)
+msgid ""
+"DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, "
+"EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT "
+"THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS "
+"MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE "
+"RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR "
+"MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR "
+"MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL "
+"WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY "
+"SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN "
+"ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION "
+"OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND"
+msgstr ""
+
+#: C/gdm.xml:55(para)
+msgid ""
+"UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING "
+"NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY "
+"CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE "
+"DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON "
+"FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF "
+"ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, "
+"WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES "
+"OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED "
+"VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE "
+"POSSIBILITY OF SUCH DAMAGES."
+msgstr ""
+
+#: C/gdm.xml:28(para)
+msgid ""
+"DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS "
+"OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: "
+"<placeholder-1/>"
+msgstr ""
+
+#: C/gdm.xml:86(releaseinfo) C/gdm.xml:97(para)
+msgid ""
+"This manual describes version 2.26.0 of the GNOME Display Manager. It was "
+"last updated on 02/10/2009."
+msgstr ""
+
+#: C/gdm.xml:95(title)
+msgid "Terms and Conventions Used in This Manual"
+msgstr ""
+
+#: C/gdm.xml:102(para)
+msgid ""
+"Chooser - A program used to select a remote host for managing a display "
+"remotely on the attached display (<command>gdm-host-chooser</command>)."
+msgstr ""
+
+#: C/gdm.xml:107(para)
+msgid ""
+"FreeDesktop - The organization providing desktop standards, such as the "
+"Desktop Entry Specification used by GDM. <ulink type=\"http\" url=\"http://"
+"www.freedesktop.org/\"> http://www.freedesktop.org</ulink>."
+msgstr ""
+
+#: C/gdm.xml:113(para)
+msgid ""
+"GDM - GNOME Display Manager. Used to describe the software package as a "
+"whole."
+msgstr ""
+
+#: C/gdm.xml:118(para)
+msgid ""
+"Greeter - The graphical login window (<command>gdm-simple-greeter</command>)."
+msgstr ""
+
+#: C/gdm.xml:122(para)
+msgid "PAM - Pluggable Authentication Mechanism"
+msgstr ""
+
+#: C/gdm.xml:126(para)
+msgid "XDMCP - X Display Manage Protocol"
+msgstr ""
+
+#: C/gdm.xml:130(para)
+msgid ""
+"Xserver - An implementation of the X Window System. For example the Xorg "
+"Xserver provided by the X.org Foundation <ulink type=\"http\" url=\"http://"
+"www.x.org/\">http://www.x.org</ulink>."
+msgstr ""
+
+#: C/gdm.xml:136(para)
+msgid ""
+"Paths that start with a word in angle brackets are relative to the "
+"installation prefix. I.e. <filename>&lt;share&gt;/pixmaps/</filename> refers "
+"to <filename>/usr/share/pixmaps</filename> if GDM was configured with "
+"<command>--prefix=/usr</command>."
+msgstr ""
+
+#: C/gdm.xml:147(title)
+msgid "Overview"
+msgstr "పర్యావలోకనం"
+
+#: C/gdm.xml:150(title)
+msgid "Introduction"
+msgstr "పరిచయం"
+
+#: C/gdm.xml:152(para)
+msgid ""
+"The GNOME Display Manager (GDM) is a display manager that implements all "
+"significant features required for managing attached and remote displays. GDM "
+"was written from scratch and does not contain any XDM or X Consortium code."
+msgstr ""
+
+#: C/gdm.xml:159(para)
+msgid ""
+"Note that GDM is configurable, and many configuration settings have an "
+"impact on security. Issues to be aware of are highlighted in this document."
+msgstr ""
+
+#: C/gdm.xml:165(para)
+msgid ""
+"Please note that some Operating Systems configure GDM to behave differently "
+"than the default values as described in this document. If GDM does not seem "
+"to behave as documented, then check to see if any related configuration may "
+"be different than described here."
+msgstr ""
+
+#: C/gdm.xml:172(para)
+msgid ""
+"For further information about GDM, refer to the project website at <ulink "
+"type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> http://www.gnome."
+"org/projects/gdm</ulink> and the project Wiki <ulink type=\"http\" url="
+"\"http://live.gnome.org/GDM\"> http://live.gnome.org/GDM</ulink>."
+msgstr ""
+
+#: C/gdm.xml:180(para)
+msgid ""
+"For discussion or queries about GDM, refer to the <address><email>gdm-"
+"list@gnome.org</email></address> mail list. This list is archived, and is a "
+"good resource to check to seek answers to common questions. This list is "
+"archived at <ulink type=\"http\" url=\"http://mail.gnome.org/archives/gdm-"
+"list/\"> http://mail.gnome.org/archives/gdm-list/</ulink> and has a search "
+"facility to look for messages with keywords."
+msgstr ""
+
+#: C/gdm.xml:190(para)
+msgid ""
+"Please submit any bug reports or enhancement requests to the \"gdm\" "
+"category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\"> http://"
+"bugzilla.gnome.org</ulink>."
+msgstr ""
+
+#: C/gdm.xml:199(title)
+msgid "Interface Stability"
+msgstr ""
+
+#: C/gdm.xml:201(para)
+msgid ""
+"GDM 2.20 and earlier supported stable configuration interfaces. However, the "
+"codebase was completely rewritten for GDM 2.22, and is not completely "
+"backward compatible with older releases. This is in part because things work "
+"differently, so some options just don't make sense, in part because some "
+"options never made sense, and in part because some functionality has not "
+"been reimplemented yet."
+msgstr ""
+
+#: C/gdm.xml:210(para)
+msgid ""
+"Interfaces which continue to be supported in a stable fashion include the "
+"Init, PreSession, PostSession, PostLogin, and Xsession scripts. Some daemon "
+"configuration options in the <filename>&lt;etc&gt;/gdm/custom.conf</"
+"filename> file continue to be supported. Also, the <filename>~/.dmrc</"
+"filename>, and face browser image locations are still supported."
+msgstr ""
+
+#: C/gdm.xml:219(para)
+msgid ""
+"GDM 2.20 and earlier supported the ability to manage multiple displays with "
+"separate graphics cards, such as used in terminal server environments, login "
+"in a window via a program like Xnest or Xephyr, the gdmsetup program, XML-"
+"based greeter themes, and the ability to run the XDMCP chooser from the "
+"login screen. These features were not added back during the 2.22 rewrite."
+msgstr ""
+
+#: C/gdm.xml:231(title)
+msgid "Functional Description"
+msgstr ""
+
+#. <para>
+#.         TODO - Would be good to discuss D-Bus, perhaps the new GObject model,
+#.                and to explain the reasons why the rewrite made GDM better.
+#.                From a high-level overview perspective, rather than the
+#.                technical aspects.
+#. </para>
+#: C/gdm.xml:242(para)
+msgid ""
+"GDM is responsible for managing displays on the system. This includes "
+"authenticating users, starting the user session, and terminating the user "
+"session. GDM is configurable and the ways it can be configured are described "
+"in the \"Configuring GDM\" section of this document. GDM is also accessible "
+"for users with disabilities."
+msgstr ""
+
+#: C/gdm.xml:250(para)
+msgid ""
+"GDM provides the ability to manage the main console display, and displays "
+"launched via VT. It is integrated with other programs, such as the Fast User "
+"Switch Applet (FUSA) and gnome-screensaver to manage multiple displays on "
+"the console via the Xserver Virtual Terminal (VT) interface. It also can "
+"manage XDMCP displays."
+msgstr ""
+
+#: C/gdm.xml:258(para)
+msgid ""
+"Regardless of the display type, GDM will do the following when it manages "
+"the display. It will start an Xserver process, then run the <filename>Init</"
+"filename> script as the root user, and start the greeter program on the "
+"display."
+msgstr ""
+
+#: C/gdm.xml:265(para)
+msgid ""
+"The greeter program is run as the unprivileged \"gdm\" user/group. This user "
+"and group are described in the \"Security\" section of this document. The "
+"main functions of the greeter program are to provide a mechanism for "
+"selecting an account for log in and to drive the dialogue between the user "
+"and system when authenticating that account. The authentication process is "
+"driven by Pluggable Authentication Modules (PAM). The PAM modules determine "
+"what prompts (if any) are shown to the user to authenticate. On the average "
+"system, the greeter program will request a username and password for "
+"authentication. However some systems may be configured to use supplemental "
+"mechanisms such as a fingerprint or SmartCard readers. GDM can be configured "
+"to support these alternatives in parallel with greeter login extensions and "
+"the <command>--enable-split-authentication</command><filename>./configure</"
+"filename> option, or one at a time via system PAM configuration."
+msgstr ""
+
+#: C/gdm.xml:284(para)
+msgid ""
+"The smartcard extension can be enabled or disabled via the <filename>org."
+"gnome.display-manager.extensions.smartcard.active</filename> gsettings key."
+msgstr ""
+
+#: C/gdm.xml:290(para)
+msgid ""
+"Likewise, the fingerprint extension can be enabled or disabled via the "
+"<filename>org.gnome.display-manager.extensions.fingerprint.active</filename> "
+"gsettings key."
+msgstr ""
+
+#: C/gdm.xml:296(para)
+msgid ""
+"GDM and PAM can be configured to not require any input, which will cause GDM "
+"to automatically log in and simply start a session, which can be useful for "
+"some environments, such as single user systems or kiosks."
+msgstr ""
+
+#: C/gdm.xml:303(para)
+msgid ""
+"In addition to authentication, the greeter program allows the user to select "
+"which session to start and which language to use. Sessions are defined by "
+"files that end in the .desktop suffix and more information about these files "
+"can be found in the \"GDM User Session and Language Configuration\" section "
+"of this document. By default, GDM is configured to display a face browser so "
+"the user can select their user account by clicking on an image instead of "
+"having to type their username. GDM keeps track of the user's default session "
+"and language in the user's <filename>~/.dmrc</filename> and will use these "
+"defaults if the user did not pick a session or language in the login GUI."
+msgstr ""
+
+#: C/gdm.xml:316(para)
+msgid ""
+"After authenticating a user, the daemon runs the <filename>PostLogin</"
+"filename> script as root, then runs the <filename>PreSession</filename> "
+"script as root. After running these scripts, the user session is started. "
+"When the user exits their session, the <filename>PostSession</filename> "
+"script is run as root. These scripts are provided as hooks for distributions "
+"and end-users to customize how sessions are managed. For example, using "
+"these hooks you could set up a machine which creates the user's $HOME "
+"directory on the fly, and erases it on logout. The difference between the "
+"<filename>PostLogin</filename> and <filename>PreSession</filename> scripts "
+"is that <filename>PostLogin</filename> is run before the pam_open_session "
+"call so is the right place to do anything which should be run before the "
+"user session is initialized. The <filename>PreSession</filename> script is "
+"called after session initialization."
+msgstr ""
+
+#: C/gdm.xml:336(title)
+msgid "Greeter Panel"
+msgstr ""
+
+#: C/gdm.xml:337(para)
+msgid ""
+"The GDM greeter program displays a panel docked at the bottom of the screen "
+"which provides additional functionality. When a user is selected, the panel "
+"allows the user to select which session, language, and keyboard layout to "
+"use after logging in. The keyboard layout selector also changes the keyboard "
+"layout used when typing your password. The panel also contains an area for "
+"login services to leave status icons. Some example status icons include a "
+"battery icon for current battery usage, and an icon for enabling "
+"accessibility features. The greeter program also provides buttons which "
+"allow the user to shutdown or restart the system. It is possible to "
+"configure GDM to not provide the shutdown and restart buttons, if desired. "
+"GDM can also be configured via PolicyKit (or via RBAC on Oracle Solaris) to "
+"require the user have appropriate authorization before accepting the "
+"shutdown or restart request."
+msgstr ""
+
+#: C/gdm.xml:354(para)
+msgid ""
+"Note that keyboard layout features are only available on systems that "
+"support libxklavier."
+msgstr ""
+
+#: C/gdm.xml:361(title)
+msgid "Accessibility"
+msgstr ""
+
+#: C/gdm.xml:363(para)
+msgid ""
+"GDM supports \"Accessible Login\", allowing users to log into their desktop "
+"session even if they cannot easily use the screen, mouse, or keyboard in the "
+"usual way. Accessible Technology (AT) features such as an on-screen "
+"keyboard, screen reader, screen magnifier, and Xserver AccessX keyboard "
+"accessibility are available. It is also possible to enable large text or "
+"high contrast icons and controls, if needed. Refer to the \"Accessibility "
+"Configuration\" section of the document for more information how various "
+"accessibility features can be configured."
+msgstr ""
+
+#: C/gdm.xml:375(para)
+msgid ""
+"On some Operating Systems, it is necessary to make sure that the GDM user is "
+"a member of the \"audio\" group for AT programs that require audio output "
+"(such as text-to-speech) to be functional."
+msgstr ""
+
+#: C/gdm.xml:383(title)
+msgid "The GDM Face Browser"
+msgstr ""
+
+#: C/gdm.xml:385(para)
+msgid ""
+"The Face Browser is the interface which allows users to select their "
+"username by clicking on an image. This feature can be enabled or disabled "
+"via the /apps/gdm/simple-greeter/disable_user_list GConf key and is on by "
+"default. When disabled, users must type their complete username by hand. "
+"When enabled, it displays all local users which are available for login on "
+"the system (all user accounts defined in the /etc/passwd file that have a "
+"valid shell and sufficiently high UID) and remote users that have recently "
+"logged in. The face browser in GDM 2.20 and earlier would attempt to display "
+"all remote users, which caused performance problems in large, enterprise "
+"deployments."
+msgstr ""
+
+#: C/gdm.xml:399(para)
+msgid ""
+"The Face Browser is configured to display the users who log in most "
+"frequently at the top of the list. This helps to ensure that users who log "
+"in frequently can quickly find their login image."
+msgstr ""
+
+#: C/gdm.xml:405(para)
+msgid ""
+"The Face Browser supports \"type-ahead search\" which dynamically moves the "
+"face selection as the user types to the corresponding username in the list. "
+"This means that a user with a long username will only have to type the first "
+"few characters of the username before the correct item in the list gets "
+"selected."
+msgstr ""
+
+#: C/gdm.xml:413(para)
+msgid ""
+"The icons used by GDM can be installed globally by the sysadmin or can be "
+"located in the user's home directories. If installed globally they should be "
+"in the <filename>&lt;share&gt;/pixmaps/faces/</filename> directory and the "
+"filename should be the name of the user. Face image files should be a "
+"standard image that GTK+ can read, such as PNG or JPEG. Face icons placed in "
+"the global face directory must be readable to the GDM user."
+msgstr ""
+
+#. <para>
+#.         TODO - In the old GDM the ~/gnome2/gdm file is used, but the new code
+#.                seems to use ~/.gnome/gdm.  Error?
+#. </para>
+#: C/gdm.xml:429(para)
+msgid ""
+"If there is no global icon for the user, GDM will look in the user's $HOME "
+"directory for the image file. GDM will first look for the user's face image "
+"in <filename>~/.face</filename>. If not found, it will try <filename>~/.face."
+"icon</filename>. If still not found, it will use the value defined for "
+"\"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file."
+msgstr ""
+
+#: C/gdm.xml:438(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 "
+"fallback to a generic face image."
+msgstr ""
+
+#: C/gdm.xml:444(para)
+msgid ""
+"Please note that loading and scaling face icons located in remote user home "
+"directories can be a very time-consuming task. Since it not practical to "
+"load images over NIS or NFS, GDM does not attempt to load face images from "
+"remote home directories."
+msgstr ""
+
+#: C/gdm.xml:451(para)
+msgid ""
+"When the browser is turned on, valid usernames on the computer are exposed "
+"for everyone to see. If XDMCP is enabled, then the usernames are exposed to "
+"remote users. This, of course, limits security somewhat since a malicious "
+"user does not need to guess valid usernames. In some very restrictive "
+"environments the face browser may not be appropriate."
+msgstr ""
+
+#: C/gdm.xml:463(title)
+msgid "XDMCP"
+msgstr "XDMCP"
+
+#. <para>
+#.         TODO - What XDMCP features actually work?   I know that the
+#.                chooser is missing.
+#. </para>
+#: C/gdm.xml:472(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 "
+"turned off, but can be enabled if desired. If GDM is built with TCP Wrapper "
+"support, then the daemon will only grant access to hosts specified in the "
+"GDM service section in the TCP Wrappers configuration file."
+msgstr ""
+
+#: C/gdm.xml:481(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 "
+"timeouts, etc. can be fine tuned. The default configuration should work "
+"reasonably on most systems."
+msgstr ""
+
+#: C/gdm.xml:488(para)
+msgid ""
+"GDM by default listens for XDMCP requests on the normal UDP port used for "
+"XDMCP, port 177, and will respond to QUERY and BROADCAST_QUERY requests by "
+"sending a WILLING packet to the originator."
+msgstr ""
+
+#: C/gdm.xml:494(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 "
+"forward subsequent requests to the chosen manager. GDM also supports an "
+"extension to the protocol which will make it forget the redirection once the "
+"user's connection succeeds. This extension is only supported if both daemons "
+"are GDM. It is transparent and will be ignored by XDM or other daemons that "
+"implement XDMCP."
+msgstr ""
+
+#: C/gdm.xml:504(para)
+msgid ""
+"If XDMCP seems to not be working, make sure that all machines are specified "
+"in <filename>/etc/hosts</filename>."
+msgstr ""
+
+#: C/gdm.xml:509(para)
+msgid ""
+"Refer to the \"Security\" section for information about security concerns "
+"when using XDMCP."
+msgstr ""
+
+#: C/gdm.xml:516(title)
+msgid "Logging"
+msgstr "నమోదుపరుచు"
+
+#: C/gdm.xml:518(para)
+msgid ""
+"GDM uses syslog to log errors and status. It can also log debugging "
+"information, which can be useful for tracking down problems if GDM is not "
+"working properly. Debug output can be enabled by setting the debug/Enable "
+"key to \"true\" in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file."
+msgstr ""
+
+#: C/gdm.xml:526(para)
+msgid ""
+"Output from the various Xservers is stored in the GDM log directory, which "
+"is normally <filename>&lt;var&gt;/log/gdm/</filename>. Any Xserver messages "
+"are saved to a file associated with the display value, <filename>&lt;"
+"display&gt;.log</filename>."
+msgstr ""
+
+#: C/gdm.xml:533(para)
+msgid ""
+"The session output is piped through the GDM daemon to the <filename>~/."
+"xsession-errors</filename> file. The file is overwritten on each login, so "
+"logging out and logging back into the same user via GDM will cause any "
+"messages from the previous session to be lost."
+msgstr ""
+
+#: C/gdm.xml:540(para)
+msgid ""
+"Note that if GDM can not create this file for some reason, then a fallback "
+"file will be created named <filename>~/.xsession-errors.XXXXXXXX</filename> "
+"where the <filename>XXXXXXXX</filename> are some random characters."
+msgstr ""
+
+#: C/gdm.xml:548(title)
+msgid "Fast User Switching"
+msgstr ""
+
+#: C/gdm.xml:550(para)
+msgid ""
+"GDM allows multiple users to be logged in at the same time. After one user "
+"is logged in, additional users can log in via the User Switcher on the GNOME "
+"Panel, or from the \"Switch User\" button in Lock Screen dialog of GNOME "
+"Screensaver. The active session can be changed back and forth using the same "
+"mechanism. Note that some distributions may not add the User Switcher to the "
+"default panel configuration. It can be added using the panel context menu."
+msgstr ""
+
+#: C/gdm.xml:559(para)
+msgid ""
+"Note this feature is available on systems that support Virtual Terminals. "
+"This feature will not function if Virtual Terminals is not available."
+msgstr ""
+
+#: C/gdm.xml:570(title)
+msgid "Security"
+msgstr "రక్షణ"
+
+#: C/gdm.xml:573(title)
+msgid "The GDM User And Group"
+msgstr ""
+
+#: C/gdm.xml:575(para)
+msgid ""
+"For security reasons a dedicated user and group id are recommended for "
+"proper operation. This user and group are normally \"gdm\" on most systems, "
+"but can be configured to any user or group. All GDM GUI programs are run as "
+"this user, so that the programs which interact with the user are run in a "
+"sandbox. This user and group should have limited privilege."
+msgstr ""
+
+#: C/gdm.xml:584(para)
+msgid ""
+"The only special privilege the \"gdm\" user requires is the ability to read "
+"and write Xauth files to the <filename>&lt;var&gt;/run/gdm</filename> "
+"directory. The <filename>&lt;var&gt;/run/gdm</filename> directory should "
+"have root:gdm ownership and 1777 permissions."
+msgstr ""
+
+#: C/gdm.xml:592(para)
+msgid ""
+"You should not, under any circumstances, configure the GDM user/group to a "
+"user which a user could easily gain access to, such as the user "
+"<filename>nobody</filename>. Any user who gains access to an Xauth key can "
+"snoop on and control running GUI programs running in the associated session "
+"or perform a denial-of-service attack on it. It is important to ensure that "
+"the system is configured properly so that only the \"gdm\" user has access "
+"to these files and that it is not easy to login to this account. For "
+"example, the account should be setup to not have a password or allow non-"
+"root users to login to the account."
+msgstr ""
+
+#: C/gdm.xml:605(para)
+msgid ""
+"The GDM greeter configuration is stored in GConf. To allow the GDM user to "
+"be able to write configuration, it is necessary for the \"gdm\" user to have "
+"a writable $HOME directory. Users may configure the default GConf "
+"configuration as desired to avoid the need to provide the \"gdm\" user with "
+"a writable $HOME directory. However, some features of GDM may be disabled if "
+"it is unable to write state information to GConf configuration."
+msgstr ""
+
+#: C/gdm.xml:617(title)
+msgid "PAM"
+msgstr "PAM"
+
+#: C/gdm.xml:619(para)
+msgid ""
+"GDM uses PAM for login authentication. PAM stands for Pluggable "
+"Authentication Module, and is used by most programs that request "
+"authentication on your computer. It allows the administrator to configure "
+"specific authentication behavior for different login programs (such as ssh, "
+"login GUI, screensaver, etc.)"
+msgstr ""
+
+#: C/gdm.xml:627(para)
+msgid ""
+"PAM is complicated and highly configurable, and this documentation does not "
+"intend to explain this in detail. Instead, it is intended to give an "
+"overview of how PAM configuration relates with GDM, how PAM is commonly "
+"configured with GDM, and known issues. It is expected that a person needing "
+"to do PAM configuration would need to do further reading of PAM "
+"documentation to understand how to configure PAM and to understand terms "
+"used in this section."
+msgstr ""
+
+#: C/gdm.xml:637(para)
+msgid ""
+"PAM configuration has different, but similar, interfaces on different "
+"Operating Systems, so check the <ulink type=\"help\" url=\"man:pam.d\">pam."
+"d</ulink> or <ulink type=\"help\" url=\"man:pam.conf\">pam.conf</ulink> man "
+"page for details. Be sure you read the PAM documentation and are comfortable "
+"with the security implications of any changes you intend to make to your "
+"configuration."
+msgstr ""
+
+#: C/gdm.xml:647(para)
+msgid ""
+"Note that, by default, GDM uses the \"gdm\" PAM service name for normal "
+"login and the \"gdm-autologin\" PAM service name for automatic login. These "
+"services may not be defined in your pam.d or pam.conf configured file. If "
+"there is no entry, then GDM will use the default PAM behavior. On most "
+"systems this should work fine. However, the automatic login feature may not "
+"work if the gdm-autologin service is not defined."
+msgstr ""
+
+#: C/gdm.xml:657(para)
+msgid ""
+"The <filename>PostLogin</filename> script is run before pam_open_session is "
+"called, and the <filename>PreSession</filename> script is called after. This "
+"allows the system administrator to add any scripting to the login process "
+"either before or after PAM initializes the session."
+msgstr ""
+
+#: C/gdm.xml:665(para)
+msgid ""
+"If you wish to make GDM work with other types of authentication mechanisms "
+"(such as a fingerprint or SmartCard reader), then you should implement this "
+"by using a PAM service module for the desired authentication type rather "
+"than by trying to modify the GDM code directly. Refer to the PAM "
+"documentation on your system. How to do this is frequently discussed on the "
+"<address><email>gdm-list@gnome.org</email></address> mail list, so you can "
+"refer to the list archives for more information."
+msgstr ""
+
+#: C/gdm.xml:676(para)
+msgid ""
+"PAM does have some limitations regarding being able to work with multiple "
+"types of authentication at the same time, like supporting the ability to "
+"accept either SmartCard and the ability to type the username and password "
+"into the login program. There are techniques that are used to make this "
+"work, and it is best to research how this problem is commonly solved when "
+"setting up such a configuration."
+msgstr ""
+
+#: C/gdm.xml:685(para)
+msgid ""
+"If automatic login does not work on a system, check to see if the \"gdm-"
+"autologin\" PAM stack is defined in the PAM configuration. For this to work, "
+"it is necessary to use a PAM module that simply does no authentication, or "
+"which simply returns PAM_SUCCESS from all of its public interfaces. Assuming "
+"your system has a pam_allow.so PAM module which does this, a PAM "
+"configuration to enable \"gdm-autologin\" would look like this:"
+msgstr ""
+
+#: C/gdm.xml:695(screen)
+#, no-wrap
+msgid ""
+"\n"
+"       gdm-autologin auth  required    pam_unix_cred.so.1\n"
+"       gdm-autologin auth  sufficient  pam_allow.so.1\n"
+"       gdm-autologin account  sufficient  pam_allow.so.1\n"
+"       gdm-autologin session  sufficient  pam_allow.so.1\n"
+"       gdm-autologin password  sufficient  pam_allow.so.1\n"
+msgstr ""
+"\n"
+"       gdm-autologin auth  required    pam_unix_cred.so.1\n"
+"       gdm-autologin auth  sufficient  pam_allow.so.1\n"
+"       gdm-autologin account  sufficient  pam_allow.so.1\n"
+"       gdm-autologin session  sufficient  pam_allow.so.1\n"
+"       gdm-autologin password  sufficient  pam_allow.so.1\n"
+
+#: C/gdm.xml:703(para)
+msgid ""
+"The above setup will cause no lastlog entry to be generated. If a lastlog "
+"entry is desired, then use the following for the session:"
+msgstr ""
+
+#: C/gdm.xml:708(screen)
+#, no-wrap
+msgid ""
+"\n"
+"       gdm-autologin session required pam_unix_session.so.1\n"
+msgstr ""
+
+#: C/gdm.xml:712(para)
+msgid ""
+"If the computer is used by several people, which makes automatic login "
+"unsuitable, you may want to allow some users to log in without entering "
+"their password. This feature can be enabled as a per-user option in the "
+"users-admin tool from the gnome-system-tools; it is achieved by checking "
+"that the user is member a Unix group called \"nopasswdlogin\" before asking "
+"for a password. For this to work, the PAM configuration file for the \"gdm\" "
+"service must include a line such as:"
+msgstr ""
+
+#: C/gdm.xml:723(screen)
+#, no-wrap
+msgid ""
+"\n"
+"      gdm auth  sufficient  pam_succeed_if.so  user ingroup nopasswdlogin\n"
+msgstr ""
+
+#: C/gdm.xml:730(title)
+msgid "utmp and wtmp"
+msgstr ""
+
+#: C/gdm.xml:732(para)
+msgid ""
+"GDM generates utmp and wtmp User Accounting Database entries upon session "
+"login and logout. The utmp database contains user access and accounting "
+"information that is accessed by commands such as <command>finger</command>, "
+"<command>last</command>, <command>login</command>, and <command>who</"
+"command>. The wtmp database contains the history of user access and "
+"accounting information for the utmp database. Refer to the <ulink type=\"help"
+"\" url=\"man:utmp\">utmp</ulink> and <ulink type=\"help\" url=\"man:wtmp"
+"\">wtmp</ulink> man pages on your system for more information."
+msgstr ""
+
+#: C/gdm.xml:747(title)
+msgid "Xserver Authentication Scheme"
+msgstr ""
+
+#: C/gdm.xml:749(para)
+msgid ""
+"Xserver authorization files are stored in a newly created subdirectory of "
+"<filename>&lt;var&gt;/run/gdm</filename> at start up. These files are used "
+"to store and share a \"password\" between X clients and the Xserver. This "
+"\"password\" is unique for each session logged in, so users from one session "
+"can't snoop on users from another."
+msgstr ""
+
+#: C/gdm.xml:757(para)
+msgid ""
+"GDM only supports the MIT-MAGIC-COOKIE-1 Xserver 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 Xserver 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. In most cases, ssh -Y should be preferred over GDM's XDMCP features."
+msgstr ""
+
+#: C/gdm.xml:774(title)
+msgid "XDMCP Security"
+msgstr ""
+
+#: C/gdm.xml:776(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:782(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. This type of set up should never use an unmanaged hub or "
+"other sniffable network."
+msgstr ""
+
+#: C/gdm.xml:795(title)
+msgid "XDMCP Access Control"
+msgstr ""
+
+#: C/gdm.xml:797(para)
+msgid ""
+"XDMCP access control is done using TCP wrappers. It is possible to compile "
+"GDM without TCP wrapper support, so this feature may not be supported on "
+"some Operating Systems."
+msgstr ""
+
+#: C/gdm.xml:803(para)
+msgid ""
+"You should use the daemon name <command>gdm</command> in the <filename>&lt;"
+"etc&gt;/hosts.allow</filename> and <filename>&lt;etc&gt;/hosts.deny</"
+"filename> files. For example to deny computers from <filename>.evil.domain</"
+"filename> from logging in, then add"
+msgstr ""
+
+#: C/gdm.xml:810(screen)
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .evil.domain\n"
+msgstr ""
+
+#: C/gdm.xml:813(para)
+msgid ""
+"to <filename>&lt;etc&gt;/hosts.deny</filename>. You may also need to add"
+msgstr ""
+
+#: C/gdm.xml:817(screen)
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .your.domain\n"
+msgstr ""
+
+#: C/gdm.xml:820(para)
+msgid ""
+"to your <filename>&lt;etc&gt;/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 ""
+
+#: C/gdm.xml:829(title)
+msgid "Firewall Security"
+msgstr ""
+
+#: C/gdm.xml:831(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 really needed. GDM guards "
+"against 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 do a "
+"denial of service attack via XDMCP than attacking a webserver."
+msgstr ""
+
+#: C/gdm.xml:842(para)
+msgid ""
+"It is also wise to block all of the Xserver ports. These are TCP ports 6000+ "
+"(one for each display number) on your firewall. Note that GDM will use "
+"display numbers 20 and higher for flexible on-demand servers."
+msgstr ""
+
+#: C/gdm.xml:849(para)
+msgid ""
+"X is not a very safe protocol when using it over the Internet, and XDMCP is "
+"even less safe."
+msgstr ""
+
+#: C/gdm.xml:856(title)
+msgid "PolicyKit"
+msgstr ""
+
+#. <para>
+#.         TODO - Should we say more?
+#. </para>
+#: C/gdm.xml:864(para)
+msgid ""
+"GDM may be configured to use PolicyKit to allow the system administrator to "
+"control whether the login screen should provide the shutdown and restart "
+"buttons on the greeter screen."
+msgstr ""
+
+#: C/gdm.xml:870(para)
+msgid ""
+"These buttons are controlled by the <filename>org.freedesktop.consolekit."
+"system.stop-multiple-users</filename> and <filename>org.freedesktop."
+"consolekit.system.restart-multiple-users</filename> actions respectively. "
+"Policy for these actions can be set up using the polkit-gnome-authorization "
+"tool, or the polkit-auth command line program."
+msgstr ""
+
+#: C/gdm.xml:882(title)
+msgid "RBAC (Role Based Access Control)"
+msgstr ""
+
+#: C/gdm.xml:884(para)
+msgid ""
+"GDM may be configured to use RBAC instead of PolicyKit. In this case the "
+"RBAC configuration is used to control whether the login screen should "
+"provide the shutdown and restart buttons on the greeter screen."
+msgstr ""
+
+#: C/gdm.xml:890(para)
+msgid ""
+"For example, on Oracle Solaris, the \"solaris.system.shutdown\" "
+"authorization is used to control this. Simply modify the <filename>/etc/"
+"user_attr</filename> file so that the \"gdm\" user has this authorization."
+msgstr ""
+
+#: C/gdm.xml:903(title)
+msgid "Support for ConsoleKit"
+msgstr ""
+
+#. <para>
+#.     TODO - Should we update these docs?  Probably should mention any 
+#.            configuration that users may want to do for using it with GDM?
+#.            If so, perhaps this section should be moved to a subsection of
+#.            the "Configure" section?
+#. </para>
+#: C/gdm.xml:914(para)
+msgid ""
+"GDM includes support for publishing user login information with the user and "
+"login session accounting framework known as ConsoleKit. ConsoleKit is able "
+"to keep track of all the users currently logged in. In this respect, it can "
+"be used as a replacement for the utmp or utmpx files that are available on "
+"most Unix-like Operating Systems."
+msgstr ""
+
+#: C/gdm.xml:922(para)
+msgid ""
+"When GDM is about to create a new login process for a user it will call a "
+"privileged method of ConsoleKit in order to open a new session for this "
+"user. At this time GDM also provides ConsoleKit with information about this "
+"user session such as: the user ID, the X11 Display name that will be "
+"associated with the session, the host-name from which the session originates "
+"(useful in the case of an XDMCP session), whether or not this session is "
+"attached, etc. As the entity that initiates the user process, GDM is in a "
+"unique position to know about the user session and to be trusted to provide "
+"these bits of information. The use of this privileged method is restricted "
+"by the use of the D-Bus system message bus security policy."
+msgstr ""
+
+#: C/gdm.xml:936(para)
+msgid ""
+"In case a user with an existing session has authenticated at GDM and "
+"requests to resume that existing session, GDM calls a privileged method of "
+"ConsoleKit to unlock that session. The exact details of what happens when "
+"the session receives this unlock signal are undefined and session-specific. "
+"However, most sessions will unlock a screensaver in response."
+msgstr ""
+
+#: C/gdm.xml:945(para)
+msgid ""
+"When the user chooses to log out, or if GDM or the session quit unexpectedly "
+"the user session will be unregistered from ConsoleKit."
+msgstr ""
+
+#: C/gdm.xml:954(title)
+msgid "Configuration"
+msgstr ""
+
+#: C/gdm.xml:956(para)
+msgid ""
+"GDM has a number of configuration interfaces. These include scripting "
+"integration points, daemon configuration, greeter configuration, general "
+"session settings, integration with gnome-settings-daemon configuration, and "
+"session configuration. These types of integration are described in detail "
+"below."
+msgstr ""
+
+#: C/gdm.xml:965(title)
+msgid "Scripting Integration Points"
+msgstr ""
+
+#: C/gdm.xml:967(para)
+msgid ""
+"The GDM script integration points can be found in the <filename>&lt;etc&gt;/"
+"gdm/</filename> directory:"
+msgstr ""
+
+#: C/gdm.xml:972(screen)
+#, no-wrap
+msgid ""
+"\n"
+"Xsession\n"
+"Init/\n"
+"PostLogin/\n"
+"PreSession/\n"
+"PostSession/\n"
+msgstr ""
+
+#: C/gdm.xml:980(para)
+msgid ""
+"The <filename>Init</filename>, <filename>PostLogin</filename>, "
+"<filename>PreSession</filename>, and <filename>PostSession</filename> "
+"scripts all work as described below."
+msgstr ""
+
+#: C/gdm.xml:986(para)
+msgid ""
+"For each type of script, the default one which will be executed is called "
+"\"Default\" and is stored in a directory associated with the script type. So "
+"the default <filename>Init</filename> script is <filename>&lt;etc&gt;/gdm/"
+"Init/Default</filename>. A per-display script can be provided, and if it "
+"exists it will be run instead of the default script. Such scripts are stored "
+"in the same directory as the default script and have the same name as the "
+"Xserver DISPLAY value for that display. For example, if the <filename>&lt;"
+"Init&gt;/:0</filename> script exists, it will be run for DISPLAY \":0\"."
+msgstr ""
+
+#: C/gdm.xml:998(para)
+msgid ""
+"All of these scripts are run with root privilege and return 0 if run "
+"successfully, and a non-zero return code if there was any failure that "
+"should cause the login session to be aborted. Also note that GDM will block "
+"until the scripts finish, so if any of these scripts hang, this will cause "
+"the login process to also hang."
+msgstr ""
+
+#: C/gdm.xml:1006(para)
+msgid ""
+"When the Xserver for the login GUI has been successfully started, but before "
+"the login GUI is actually displayed, GDM will run the <filename>Init</"
+"filename> script. This script is useful for starting programs that should be "
+"run while the login screen is showing, or for doing any special "
+"initialization if required."
+msgstr ""
+
+#: C/gdm.xml:1014(para)
+msgid ""
+"After the user has been successfully authenticated GDM will run the "
+"<filename>PostLogin</filename> script. This is done before any session setup "
+"has been done, including before the pam_open_session call. This script is "
+"useful for doing any session initialization that needs to happen before the "
+"session starts. For example, you might setup the user's $HOME directory if "
+"needed."
+msgstr ""
+
+#: C/gdm.xml:1023(para)
+msgid ""
+"After the user session has been initialized, GDM will run the "
+"<filename>PreSession</filename> script. This script is useful for doing any "
+"session initialization that needs to happen after the session has been "
+"initialized. It can be used for session management or accounting, for "
+"example."
+msgstr ""
+
+#: C/gdm.xml:1031(para)
+msgid ""
+"When a user terminates their session, GDM will run the "
+"<filename>PostSession</filename> script. Note that the Xserver will have "
+"been stopped by the time this script is run, so it should not be accessed."
+msgstr ""
+
+#: C/gdm.xml:1038(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 ""
+
+#: C/gdm.xml:1045(para)
+msgid ""
+"All of the above scripts will set the <filename>$RUNNING_UNDER_GDM</"
+"filename> environment variable to <filename>yes</filename>. If the scripts "
+"are also shared with other display managers, this allows you to identify "
+"when GDM is calling these scripts, so you can run specific code when GDM is "
+"used."
+msgstr ""
+
+#: C/gdm.xml:1055(title)
+msgid "Autostart Configuration"
+msgstr ""
+
+#: C/gdm.xml:1057(para)
+msgid ""
+"The <filename>&lt;share&gt;/gdm/autostart/LoginWindow</filename> directory "
+"contains files in the format specified by the \"FreeDesktop.org Desktop "
+"Application Autostart Specification\". Standard features in the "
+"specification may be used to specify programs that should auto-restart or "
+"only be launched if a GConf configuration value is set, etc."
+msgstr ""
+
+#: C/gdm.xml:1066(para)
+msgid ""
+"Any <filename>.desktop</filename> files in this directory will cause the "
+"associated program to automatically start with the login GUI greeter. By "
+"default, GDM is shipped with files which will autostart the gdm-simple-"
+"greeter login GUI greeter itself, the gnome-power-manager application, the "
+"gnome-settings-daemon, and the metacity window manager. These programs are "
+"needed for the greeter program to work. In addition, desktop files are "
+"provided for starting various AT programs if the configuration values "
+"specified in the Accessibility Configuration section below are set."
+msgstr ""
+
+#: C/gdm.xml:1080(title)
+msgid "Xsession Script"
+msgstr ""
+
+#: C/gdm.xml:1082(para)
+msgid ""
+"There is also an <filename>Xsession</filename> script located at "
+"<filename>&lt;etc&gt;/gdm/Xsession</filename> which is called between the "
+"<filename>PreSession</filename> and the <filename>PostSession</filename> "
+"scripts. This script does not support per-display like the other scripts. "
+"This script is used for actually starting the user session. This script is "
+"run as the user, and it will run whatever session was specified by the "
+"Desktop session file the user selected to start."
+msgstr ""
+
+#: C/gdm.xml:1095(title)
+msgid "Daemon Configuration"
+msgstr ""
+
+#: C/gdm.xml:1097(para)
+msgid ""
+"The GDM daemon is configured using the <filename>&lt;etc&gt;/gdm/custom."
+"conf</filename> file. Default values are stored in GConf in the "
+"<filename>gdm.schemas</filename> file. It is recommended that end-users "
+"modify the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file because the "
+"schemas file may be overwritten when the user updates their system to have a "
+"newer version of GDM."
+msgstr ""
+
+#: C/gdm.xml:1107(para)
+msgid ""
+"Note that older versions of GDM supported additional configuration options "
+"which are no longer supported in the latest versions of GDM."
+msgstr ""
+
+#: C/gdm.xml:1112(para)
+msgid ""
+"The <filename>&lt;etc&gt;/gdm/custom.conf</filename> file is in the "
+"<filename>keyfile</filename> format. Keywords in brackets define group "
+"sections, strings before an equal sign (=) are keys and the data after equal "
+"sign represents their value. Empty lines or lines starting with the hash "
+"mark (#) are ignored."
+msgstr ""
+
+#: C/gdm.xml:1120(para)
+msgid ""
+"The file <filename>&lt;etc&gt;/gdm/custom.conf</filename> supports the "
+"\"[daemon]\", \"[security]\", and \"[xdmcp]\" group sections. Within each "
+"group, there are particular key/value pairs that can be specified to modify "
+"how GDM behaves. For example, to enable timed login and specify the timed "
+"login user to be a user named \"you\", you would modify the file so it "
+"contains the following lines:"
+msgstr ""
+
+#: C/gdm.xml:1130(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[daemon]\n"
+"TimedLoginEnable=true\n"
+"TimedLogin=you\n"
+msgstr ""
+
+#: C/gdm.xml:1136(para)
+msgid "A full list of supported configuration keys follow:"
+msgstr ""
+
+#: C/gdm.xml:1141(title)
+msgid "[chooser]"
+msgstr ""
+
+#: C/gdm.xml:1145(term)
+msgid "Multicast"
+msgstr ""
+
+#: C/gdm.xml:1147(synopsis)
+#, no-wrap
+msgid "Multicast=false"
+msgstr ""
+
+#: C/gdm.xml:1148(para)
+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."
+msgstr ""
+
+#: C/gdm.xml:1157(term)
+msgid "MulticastAddr"
+msgstr ""
+
+#: C/gdm.xml:1159(synopsis)
+#, no-wrap
+msgid "MulticastAddr=ff02::1"
+msgstr ""
+
+#: C/gdm.xml:1160(para)
+msgid "This is the Link-local multicast address."
+msgstr ""
+
+#: C/gdm.xml:1169(title)
+msgid "[daemon]"
+msgstr ""
+
+#: C/gdm.xml:1172(term)
+msgid "TimedLoginEnable"
+msgstr ""
+
+#: C/gdm.xml:1174(synopsis)
+#, no-wrap
+msgid "TimedLoginEnable=false"
+msgstr ""
+
+#: C/gdm.xml:1175(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. Refer to the \"Security-&gt;PAM\" section of the manual for "
+"more information, or for help if this feature does not seem to work."
+msgstr ""
+
+#: C/gdm.xml:1197(term)
+msgid "TimedLogin"
+msgstr ""
+
+#: C/gdm.xml:1199(synopsis)
+#, no-wrap
+msgid "TimedLogin="
+msgstr ""
+
+#: C/gdm.xml:1200(para)
+msgid ""
+"This is the user that should be logged in after a specified number of "
+"seconds of inactivity."
+msgstr ""
+
+#: C/gdm.xml:1204(para) C/gdm.xml:1248(para)
+msgid ""
+"If the value ends with a vertical bar | (the pipe symbol), then GDM will "
+"execute the program specified and use whatever value is returned on standard "
+"out from the program as the user. The program is run with the DISPLAY "
+"environment variable set so that it is possible to specify the user in a per-"
+"display fashion. For example if the value is \"/usr/bin/getloginuser|\", "
+"then the program \"/usr/bin/getloginuser\" will be run to get the user value."
+msgstr ""
+
+#: C/gdm.xml:1218(term)
+msgid "TimedLoginDelay"
+msgstr ""
+
+#: C/gdm.xml:1220(synopsis)
+#, no-wrap
+msgid "TimedLoginDelay=30"
+msgstr ""
+
+#: C/gdm.xml:1221(para)
+msgid ""
+"Delay in seconds before the <filename>TimedLogin</filename> user will be "
+"logged in."
+msgstr ""
+
+#: C/gdm.xml:1229(term)
+msgid "AutomaticLoginEnable"
+msgstr ""
+
+#: C/gdm.xml:1231(synopsis)
+#, no-wrap
+msgid "AutomaticLoginEnable=false"
+msgstr ""
+
+#: C/gdm.xml:1232(para)
+msgid ""
+"If true, the user given in <filename>AutomaticLogin</filename> should be "
+"logged in immediately. This feature is like timed login with a delay of 0 "
+"seconds."
+msgstr ""
+
+#: C/gdm.xml:1241(term)
+msgid "AutomaticLogin"
+msgstr ""
+
+#: C/gdm.xml:1243(synopsis)
+#, no-wrap
+msgid "AutomaticLogin="
+msgstr ""
+
+#: C/gdm.xml:1244(para)
+msgid ""
+"This is the user that should be logged in immediately if "
+"<filename>AutomaticLoginEnable</filename> is true."
+msgstr ""
+
+#: C/gdm.xml:1262(term)
+msgid "User"
+msgstr ""
+
+#: C/gdm.xml:1264(synopsis)
+#, no-wrap
+msgid "User=gdm"
+msgstr ""
+
+#: C/gdm.xml:1265(para)
+msgid ""
+"The username under which the greeter and other GUI programs are run. Refer "
+"to the <filename>Group</filename> configuration key and to the \"Security-"
+"&gt;GDM User And Group\" section of this document for more information."
+msgstr ""
+
+#: C/gdm.xml:1275(term)
+msgid "Group"
+msgstr ""
+
+#: C/gdm.xml:1277(synopsis)
+#, no-wrap
+msgid "Group=gdm"
+msgstr ""
+
+#: C/gdm.xml:1278(para)
+msgid ""
+"The group name under which the greeter and other GUI programs are run. Refer "
+"to the <filename>User</filename> configuration key and to the \"Security-&gt;"
+"GDM User And Group\" section of this document for more information."
+msgstr ""
+
+#: C/gdm.xml:1290(title)
+msgid "Debug Options"
+msgstr ""
+
+#: C/gdm.xml:1293(title)
+msgid "[debug]"
+msgstr ""
+
+#: C/gdm.xml:1296(term) C/gdm.xml:1427(term)
+msgid "Enable"
+msgstr ""
+
+#: C/gdm.xml:1298(synopsis) C/gdm.xml:1429(synopsis)
+#, no-wrap
+msgid "Enable=false"
+msgstr ""
+
+#: C/gdm.xml:1299(para)
+msgid ""
+"To enable debugging, set the debug/Enable key to \"true\" in the "
+"<filename>&lt;etc&gt;/gdm/custom.conf</filename> file and restart GDM. Then "
+"debug output will be sent to the system log file (<filename>&lt;var&gt;/log/"
+"messages</filename> or <filename>&lt;var&gt;/adm/messages</filename> "
+"depending on your Operating System)."
+msgstr ""
+
+#: C/gdm.xml:1314(title)
+msgid "Greeter Options"
+msgstr ""
+
+#: C/gdm.xml:1317(title)
+msgid "[greeter]"
+msgstr ""
+
+#: C/gdm.xml:1320(term)
+msgid "IncludeAll"
+msgstr ""
+
+#: C/gdm.xml:1322(synopsis)
+#, no-wrap
+msgid "IncludeAll=true"
+msgstr ""
+
+#: C/gdm.xml:1323(para)
+msgid ""
+"If true, then the face browser will show all users on the local machine. If "
+"false, the face browser will only show users who have recently logged in."
+msgstr ""
+
+#: C/gdm.xml:1329(para)
+msgid ""
+"When this key is true, GDM will call fgetpwent() to get a list of local "
+"users on the system. Any users with a user id less than 500 (or 100 if "
+"running on Oracle Solaris) are filtered out. The Face Browser also will "
+"display any users that have previously logged in on the system (for example "
+"NIS/LDAP users). It gets this list via calling the <command>ck-history</"
+"command> ConsoleKit interface. It will also filter out any users which do "
+"not have a valid shell (valid shells are any shell that getusershell() "
+"returns - /sbin/nologin or /bin/false are considered invalid shells even if "
+"getusershell() returns them)."
+msgstr ""
+
+#: C/gdm.xml:1343(para)
+msgid ""
+"If false, then GDM more simply only displays users that have previously "
+"logged in on the system (local or NIS/LDAP users) by calling the <command>ck-"
+"history</command> ConsoleKit interface."
+msgstr ""
+
+#: C/gdm.xml:1352(term)
+msgid "Include"
+msgstr ""
+
+#: C/gdm.xml:1354(synopsis)
+#, no-wrap
+msgid "Include="
+msgstr ""
+
+#: C/gdm.xml:1355(para)
+msgid ""
+"Set to a list of users to always include in the Face Browser. This value is "
+"set to a list of users separated by commas. By default, the value is empty."
+msgstr ""
+
+#: C/gdm.xml:1364(term)
+msgid "Exclude"
+msgstr ""
+
+#: C/gdm.xml:1366(synopsis)
+#, no-wrap
+msgid "Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap"
+msgstr ""
+
+#: C/gdm.xml:1367(para)
+msgid ""
+"Set to a list of users to always exclude in the Face Browser. This value is "
+"set to a list of users separated by commas. Note that the setting in the "
+"<filename>custom.conf</filename> overrides the default value, so if you wish "
+"to add additional users to the list, then you need to set the value to the "
+"default value with additional users appended to the list."
+msgstr ""
+
+#: C/gdm.xml:1381(title)
+msgid "Security Options"
+msgstr ""
+
+#: C/gdm.xml:1384(title)
+msgid "[security]"
+msgstr ""
+
+#: C/gdm.xml:1387(term)
+msgid "DisallowTCP"
+msgstr ""
+
+#: C/gdm.xml:1389(synopsis)
+#, no-wrap
+msgid "DisallowTCP=true"
+msgstr ""
+
+#: C/gdm.xml:1390(para)
+msgid ""
+"If true, then always append <filename>-nolisten tcp</filename> to the "
+"command line when starting attached Xservers, thus disallowing TCP "
+"connection. This is a more secure configuration if you are not using remote "
+"connections."
+msgstr ""
+
+#: C/gdm.xml:1402(title)
+msgid "XDCMP Support"
+msgstr ""
+
+#: C/gdm.xml:1405(title)
+msgid "[xdmcp]"
+msgstr ""
+
+#: C/gdm.xml:1408(term)
+msgid "DisplaysPerHost"
+msgstr ""
+
+#: C/gdm.xml:1410(synopsis)
+#, no-wrap
+msgid "DisplaysPerHost=1"
+msgstr ""
+
+#: C/gdm.xml:1411(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 this "
+"value."
+msgstr ""
+
+#: C/gdm.xml:1418(para)
+msgid ""
+"Note that the number of attached DISPLAYS allowed is not limited. Only "
+"remote connections via XDMCP are limited by this configuration option."
+msgstr ""
+
+#: C/gdm.xml:1430(para)
+msgid ""
+"Setting this to true enables XDMCP support allowing remote displays/X "
+"terminals to be managed by GDM."
+msgstr ""
+
+#: C/gdm.xml:1435(para)
+msgid ""
+"<filename>gdm</filename> listens for requests on UDP port 177. See the Port "
+"option for more information."
+msgstr ""
+
+#: C/gdm.xml:1440(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 ""
+
+#: C/gdm.xml:1446(para)
+msgid ""
+"You should add <screen>\n"
+"gdm:.my.domain\n"
+"</screen> to your <filename>&lt;etc&gt;/hosts.allow</filename>, depending on "
+"your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:"
+"hosts.allow\">hosts.allow</ulink> man page for details."
+msgstr ""
+
+#: C/gdm.xml:1457(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 ""
+
+#: C/gdm.xml:1466(term)
+msgid "HonorIndirect"
+msgstr ""
+
+#: C/gdm.xml:1468(synopsis)
+#, no-wrap
+msgid "HonorIndirect=true"
+msgstr ""
+
+#: C/gdm.xml:1469(para)
+msgid ""
+"Enables XDMCP INDIRECT choosing (i.e. remote execution of "
+"<filename>gdmchooser</filename>) for X-terminals which do not supply their "
+"own display browser."
+msgstr ""
+
+#: C/gdm.xml:1478(term)
+msgid "MaxPending"
+msgstr ""
+
+#: C/gdm.xml:1480(synopsis)
+#, no-wrap
+msgid "MaxPending=4"
+msgstr ""
+
+#: C/gdm.xml:1481(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:1487(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:1496(term)
+msgid "MaxSessions"
+msgstr ""
+
+#: C/gdm.xml:1498(synopsis)
+#, no-wrap
+msgid "MaxSessions=16"
+msgstr ""
+
+#: C/gdm.xml:1499(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:1508(term)
+msgid "MaxWait"
+msgstr ""
+
+#: C/gdm.xml:1510(synopsis)
+#, no-wrap
+msgid "MaxWait=30"
+msgstr ""
+
+#: C/gdm.xml:1511(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:1517(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:1522(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:1531(term)
+msgid "MaxWaitIndirect"
+msgstr ""
+
+#: C/gdm.xml:1533(synopsis)
+#, no-wrap
+msgid "MaxWaitIndirect=30"
+msgstr ""
+
+#: C/gdm.xml:1534(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 ""
+
+#: C/gdm.xml:1548(term)
+msgid "PingIntervalSeconds"
+msgstr ""
+
+#: C/gdm.xml:1550(synopsis)
+#, no-wrap
+msgid "PingIntervalSeconds=60"
+msgstr ""
+
+#: C/gdm.xml:1551(para)
+msgid ""
+"If the Xserver does not respond in the specified number of seconds, then the "
+"connection is stopped and the session ended. When this happens the slave "
+"daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied "
+"this setting by 2, so it may be necessary to increase the timeout if "
+"upgrading from GDM 2.20 and earlier to a newer version."
+msgstr ""
+
+#: C/gdm.xml:1560(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 than 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 ""
+
+#: C/gdm.xml:1573(term)
+msgid "Port"
+msgstr ""
+
+#: C/gdm.xml:1575(synopsis)
+#, no-wrap
+msgid "Port=177"
+msgstr ""
+
+#: C/gdm.xml:1576(para)
+msgid ""
+"The UDP port number <filename>gdm</filename> should listen to for XDMCP "
+"requests. Do not change this unless you know what you are doing."
+msgstr ""
+
+#: C/gdm.xml:1585(term)
+msgid "Willing"
+msgstr ""
+
+#: C/gdm.xml:1587(synopsis)
+#, no-wrap
+msgid "Willing=&lt;etc&gt;/gdm/Xwilling"
+msgstr ""
+
+#: C/gdm.xml:1588(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 does not 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 ""
+
+#: C/gdm.xml:1607(title)
+msgid "Simple Greeter Configuration"
+msgstr ""
+
+#: C/gdm.xml:1609(para)
+msgid ""
+"The GDM default greeter is called the simple Greeter and is configured via "
+"GConf. Default values are stored in GConf in the <filename>gdm-simple-"
+"greeter.schemas</filename> file. These defaults can be overridden if the "
+"\"gdm\" user has a writable $HOME directory to store GConf settings. These "
+"values can be edited using the <command>gconftool-2</command> or "
+"<command>gconf-editor</command> programs. The following configuration "
+"options are supported:"
+msgstr ""
+
+#: C/gdm.xml:1620(title)
+msgid "Greeter Configuration Keys"
+msgstr ""
+
+#: C/gdm.xml:1623(term)
+msgid "/apps/gdm/simple-greeter/banner_message_enable"
+msgstr ""
+
+#: C/gdm.xml:1625(synopsis) C/gdm.xml:1646(synopsis) C/gdm.xml:1657(synopsis)
+#: C/gdm.xml:1722(synopsis) C/gdm.xml:1787(synopsis) C/gdm.xml:1798(synopsis)
+#: C/gdm.xml:1809(synopsis) C/gdm.xml:1820(synopsis)
+#, no-wrap
+msgid "false (boolean)"
+msgstr ""
+
+#: C/gdm.xml:1626(para)
+msgid "Controls whether the banner message text is displayed."
+msgstr ""
+
+#: C/gdm.xml:1633(term)
+msgid "/apps/gdm/simple-greeter/banner_message_text"
+msgstr ""
+
+#: C/gdm.xml:1635(synopsis)
+#, no-wrap
+msgid "NULL (string)"
+msgstr ""
+
+#: C/gdm.xml:1636(para)
+msgid "Specifies the text banner message to show on the greeter window."
+msgstr ""
+
+#: C/gdm.xml:1644(term)
+msgid "/apps/gdm/simple-greeter/disable_restart_buttons"
+msgstr ""
+
+#: C/gdm.xml:1647(para)
+msgid "Controls whether to show the restart buttons in the login window."
+msgstr ""
+
+#: C/gdm.xml:1655(term)
+msgid "/apps/gdm/simple-greeter/disable_user_list"
+msgstr ""
+
+#: C/gdm.xml:1658(para)
+msgid ""
+"If true, then the face browser with known users is not shown in the login "
+"window."
+msgstr ""
+
+#: C/gdm.xml:1666(term)
+msgid "/apps/gdm/simple-greeter/logo_icon_name"
+msgstr ""
+
+#: C/gdm.xml:1668(synopsis)
+#, no-wrap
+msgid "computer (string)"
+msgstr ""
+
+#: C/gdm.xml:1669(para)
+msgid "Set to the themed icon name to use for the greeter logo."
+msgstr ""
+
+#: C/gdm.xml:1676(term)
+msgid "/apps/gdm/simple-greeter/recent-languages"
+msgstr ""
+
+#: C/gdm.xml:1678(synopsis) C/gdm.xml:1700(synopsis)
+#, no-wrap
+msgid "[] (string list)"
+msgstr ""
+
+#: C/gdm.xml:1679(para)
+msgid ""
+"Set to a list of languages to be shown by default in the login window. "
+"Default value is \"[]\". With the default setting only the system default "
+"language is shown and the option \"Other...\" which pops-up a dialog box "
+"showing a full list of available languages which the user can select."
+msgstr ""
+
+#: C/gdm.xml:1687(para)
+msgid ""
+"Users are not intended to change this setting by hand. Instead GDM keeps "
+"track of any languages selected in this configuration key, and will show "
+"them in the language combo box along with the \"Other...\" choice. This way, "
+"commonly selected languages are easier to select."
+msgstr ""
+
+#: C/gdm.xml:1698(term)
+msgid "/apps/gdm/simple-greeter/recent-layouts"
+msgstr ""
+
+#: C/gdm.xml:1701(para)
+msgid ""
+"Set to a list of keyboard layouts to be shown by default in the login panel. "
+"Default value is \"[]\". With the default setting only the system default "
+"keyboard layout is shown and the option \"Other...\" which pops-up a dialog "
+"box showing a full list of available keyboard layouts which the user can "
+"select."
+msgstr ""
+
+#: C/gdm.xml:1709(para)
+msgid ""
+"Users are not intended to change this setting by hand. Instead GDM keeps "
+"track of any keyboard layouts selected in this configuration key, and will "
+"show them in the keyboard layout combo box along with the \"Other...\" "
+"choice. This way, commonly selected keyboard layouts are easier to select."
+msgstr ""
+
+#: C/gdm.xml:1720(term)
+msgid "/apps/gdm/simple-greeter/wm_use_compiz"
+msgstr ""
+
+#: C/gdm.xml:1723(para)
+msgid ""
+"Controls whether compiz is used as the window manager instead of metacity."
+msgstr ""
+
+#: C/gdm.xml:1733(title)
+msgid "Accessibility Configuration"
+msgstr ""
+
+#: C/gdm.xml:1735(para)
+msgid ""
+"This section describes the accessibility configuration options available in "
+"GDM."
+msgstr ""
+
+#: C/gdm.xml:1741(title)
+msgid "GDM Accessibility Dialog And GConf Keys"
+msgstr ""
+
+#: C/gdm.xml:1743(para)
+msgid ""
+"The GDM greeter panel at the login screen displays an accessibility icon. "
+"Clicking on that icon opens the GDM Accessibility Dialog. In the GDM "
+"Accessibility Dialog, there is a list of checkboxes, so the user can enable "
+"or disable the associated assistive tools."
+msgstr ""
+
+#: C/gdm.xml:1750(para)
+msgid ""
+"The checkboxes that correspond to the on-screen keyboard, screen magnifier "
+"and screen reader assistive tools act on the three GConf keys that are "
+"described in the next section of this document. By enabling or disabling "
+"these checkboxes, the associated GConf key is set to \"true\" or \"false\". "
+"When the GConf key is set to true, the assistive tools linked to this GConf "
+"key are launched. When the GConf key is set to \"false\", any running "
+"assistive tool linked to this GConf key are terminated. These GConf keys are "
+"not automatically reset to a default state after the user has logged in. "
+"Consequently, the assistive tools that were running during the last GDM "
+"login session will automatically be launched at the next GDM login session."
+msgstr ""
+
+#: C/gdm.xml:1764(para)
+msgid ""
+"The other checkboxes in the GDM Accessibility Dialog do not have "
+"corresponding GConf keys because no additional program is launched to "
+"provide the accessibility features that they offer. These other options "
+"correspond to accessibility features that are provided by the Xserver, which "
+"is always running during the GDM session."
+msgstr ""
+
+#: C/gdm.xml:1774(title)
+msgid "Accessibility GConf Keys"
+msgstr ""
+
+#: C/gdm.xml:1776(para)
+msgid ""
+"GDM offers the following GConf keys to control its accessibility features:"
+msgstr ""
+
+#: C/gdm.xml:1782(title)
+msgid "GDM Configuration Keys"
+msgstr ""
+
+#: C/gdm.xml:1785(term)
+msgid "/desktop/gnome/interface/accessibility"
+msgstr ""
+
+#: C/gdm.xml:1788(para)
+msgid ""
+"Controls whether the Accessibility infrastructure will be started with the "
+"GDM GUI. This is needed for many accessibility technology programs to work."
+msgstr ""
+
+#: C/gdm.xml:1796(term)
+msgid "/desktop/gnome/applications/at/screen_magnifier_enabled"
+msgstr ""
+
+#: C/gdm.xml:1799(para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is a screen magnifier application."
+msgstr ""
+
+#: C/gdm.xml:1807(term)
+msgid "/desktop/gnome/applications/at/screen_keyboard_enabled"
+msgstr ""
+
+#: C/gdm.xml:1810(para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is an on-screen keyboard "
+"application."
+msgstr ""
+
+#: C/gdm.xml:1818(term)
+msgid "/desktop/gnome/applications/at/screen_reader_enabled"
+msgstr ""
+
+#: C/gdm.xml:1821(para)
+msgid ""
+"If set, then the assistive tools linked to this GConf key will be started "
+"with the GDM GUI program. By default this is a screen reader application."
+msgstr ""
+
+#: C/gdm.xml:1832(title)
+msgid "Linking GConf Keys to Accessbility Tools"
+msgstr ""
+
+#: C/gdm.xml:1834(para)
+msgid ""
+"For the screen_magnifier_enabled, the screen_keyboard_enabled, and the "
+"screen_reader_enabled GConf keys, the assistive tool which gets launched "
+"depends on the desktop files located in the GDM autostart directory as "
+"described in the \"Autostart Configuration\" section of this manual. Any "
+"desktop file in the GDM autostart directory can be linked to these GConf key "
+"via specifying that GConf key in the AutostartCondition value in the desktop "
+"file. So the exact AutostartCondition line in the desktop file could be one "
+"of the following:"
+msgstr ""
+
+#: C/gdm.xml:1846(screen)
+#, no-wrap
+msgid ""
+"\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled\n"
+msgstr ""
+
+#: C/gdm.xml:1852(para)
+msgid ""
+"When an accessibility key is true, then any program which is linked to that "
+"key in a GDM autostart desktop file will be launched (unless the Hidden key "
+"is set to true in that desktop file). A single GConf key can even start "
+"multiple assistive tools if there are multiple desktop files with this "
+"AutostartCondition in the GDM autostart directory."
+msgstr ""
+
+#: C/gdm.xml:1862(title)
+msgid "Example Of Modifying Accessibility Tool Configuration"
+msgstr ""
+
+#: C/gdm.xml:1864(para)
+msgid ""
+"For example, if GNOME is distributed with GOK as the default on-screen "
+"keyboard, then this could be replaced with a different program if desired. "
+"To replace GOK with the on-screen keyboard application \"onboard\" and "
+"additionally activate the assistive tool \"mousetweaks\" for dwelling "
+"support, then the following configuration is needed."
+msgstr ""
+
+#: C/gdm.xml:1872(para)
+msgid ""
+"Create a desktop file for onboard and a second one for mousetweaks; for "
+"example, onboard.desktop and mousetweaks.desktop. These files must be placed "
+"in the GDM autostart directory and be in the format as explained in the "
+"\"Autostart Configuration\" section of this document."
+msgstr ""
+
+#: C/gdm.xml:1880(para)
+msgid "The following is an example <filename>onboard.desktop</filename> file:"
+msgstr ""
+
+#: C/gdm.xml:1884(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Onboard Onscreen Keyboard\n"
+"Comment=Use an on-screen keyboard\n"
+"TryExec=onboard\n"
+"Exec=onboard --size 500x180 -x 20 -y 10\n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+msgstr ""
+
+#: C/gdm.xml:1898(para)
+msgid ""
+"The following is an example <filename>mousetweaks.desktop</filename> file:"
+msgstr ""
+
+#: C/gdm.xml:1903(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop Entry]\n"
+"Encoding=UTF-8\n"
+"Name=Software Mouse-Clicks\n"
+"Comment=Perform clicks by dwelling with the pointer\n"
+"TryExec=mousetweaks\n"
+"Exec=mousetweaks --enable-dwell -m window -c -x 20 -y 240 \n"
+"Terminal=false\n"
+"Type=Application\n"
+"StartupNotify=true\n"
+"Categories=GNOME;GTK;Accessibility;\n"
+"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"
+msgstr ""
+
+#: C/gdm.xml:1917(para)
+msgid ""
+"Note the line with the AutostartCondition that links both desktop files to "
+"the GConf key for the on-screen keyboard."
+msgstr ""
+
+#: C/gdm.xml:1922(para)
+msgid ""
+"To disable GOK from starting, the desktop file for the GOK on-screen "
+"keyboard must be removed or deactivated. Otherwise onboard and GOK would "
+"simultaneously be started. This can be done by removing the gok.desktop file "
+"from the GDM autostart directory, or by adding the \"Hidden=true\" key "
+"setting to the gok.desktop file."
+msgstr ""
+
+#: C/gdm.xml:1930(para)
+msgid ""
+"After making these changes, GOK will no longer be started when the user "
+"activates the on-screen keyboard in the GDM session; but onboard and "
+"mousetweaks will instead be launched."
+msgstr ""
+
+#: C/gdm.xml:1939(title)
+msgid "General Session Settings"
+msgstr ""
+
+#. <para>
+#.           TODO - I think this section should be expanded upon.  What specific
+#.                  keys are of interest, or would some users be likely to want
+#.                  to configure?  Also, would be good to be more specific about
+#.                  how lock down management is handled.
+#. </para>
+#: C/gdm.xml:1948(para)
+msgid ""
+"The GDM Greeter uses some of the same framework that your desktop session "
+"will use. And so, it is influenced by a number of the same GConf settings. "
+"For each of these settings the Greeter will use the default value unless it "
+"is specifically overridden by a) GDM's installed mandatory policy b) system "
+"mandatory policy. GDM installs its own mandatory policy to lock down some "
+"settings for security."
+msgstr ""
+
+#: C/gdm.xml:1959(title)
+msgid "GNOME Settings Daemon"
+msgstr ""
+
+#. <para>
+#.           TODO - I think this section should be expanded upon.  What specific
+#.                  keys are of interest, or would some users be likely to want
+#.                  to configure?  Also, would be good to give a more complete
+#.                  list of plugins that users might want to consider disabling.
+#.                  Also, shouldn't we list the sound/active key in the Greeter
+#.                  configuration setting?  Oddly I do not find this key used
+#.                  in anything but the chooser in SVN.
+#. </para>
+#: C/gdm.xml:1972(para)
+msgid ""
+"GDM enables the following gnome-settings-daemon plugins: a11y-keyboard, "
+"background, sound, xsettings."
+msgstr ""
+
+#: C/gdm.xml:1977(para)
+msgid ""
+"These are responsible for things like the background image, font and theme "
+"settings, sound events, etc."
+msgstr ""
+
+#: C/gdm.xml:1982(para)
+msgid ""
+"Plugins can also be disabled using GConf. For example, if you want to "
+"disable the sound plugin then unset the following key: <filename>/apps/gdm/"
+"simple-greeter/settings-manager-plugins/sound/active</filename>."
+msgstr ""
+
+#: C/gdm.xml:1990(title)
+msgid "GDM Session Configuration"
+msgstr ""
+
+#: C/gdm.xml:1992(para)
+msgid ""
+"GDM sessions are specified using the FreeDesktop.org Desktop Entry "
+"Specification, which can be referenced at the following URL: <ulink url="
+"\"http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec\"> "
+"http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec</ulink>."
+msgstr ""
+
+#: C/gdm.xml:1999(para)
+msgid ""
+"By default, GDM will install desktop files in the <filename>&lt;share&gt;/"
+"xsessions</filename> directory. GDM will search the following directories in "
+"this order to find desktop files: <filename>&lt;etc&gt;/X11/sessions/</"
+"filename>, <filename>&lt;dmconfdir&gt;/Sessions</filename>, <filename>&lt;"
+"share&gt;/xsessions</filename>, and <filename>&lt;share&gt;/gdm/"
+"BuiltInSessions</filename>. By default the <filename>&lt;dmconfdir&gt;</"
+"filename> is set to <filename>&lt;etc&gt;/dm/</filename> unless GDM is "
+"configured to use a different directory via the \"--with-dmconfdir\" option."
+msgstr ""
+
+#: C/gdm.xml:2012(para)
+msgid ""
+"A session can be disabled by editing the desktop file and adding a line as "
+"follows: <filename>Hidden=true</filename>."
+msgstr ""
+
+#: C/gdm.xml:2017(para)
+msgid ""
+"GDM desktop files support a GDM-specific extension, a key named \"X-GDM-"
+"BypassXsession\". If the key is not specified in a desktop file, the value "
+"defaults to \"false\". If this key is specified to be \"true\" in a desktop "
+"file, then GDM will launch the program specified by the desktop file \"Exec"
+"\" key directly when starting the user session. It will not run the program "
+"via the <filename>&lt;etc&gt;/gdm/Xsession</filename> script, which is the "
+"normal behavior. Since bypassing the <filename>&lt;etc&gt;/gdm/Xsession</"
+"filename> script avoids setting up the user session with the normal system "
+"and user settings, sessions started this way can be useful for debugging "
+"problems in the system or user scripts that might be preventing a user from "
+"being able to start a session."
+msgstr ""
+
+#: C/gdm.xml:2036(title)
+msgid "GDM User Session and Language Configuration"
+msgstr ""
+
+#: C/gdm.xml:2037(para)
+msgid ""
+"The user's default session and language choices are stored in the "
+"<filename>~/.dmrc</filename> file. When a user logs in for the first time, "
+"this file is created with the user's initial choices. The user can change "
+"these default values by simply changing to a different value when logging "
+"in. GDM will remember this change for subsequent logins."
+msgstr ""
+
+#: C/gdm.xml:2045(para)
+msgid ""
+"The <filename>~/.dmrc</filename> file is in the standard <filename>INI</"
+"filename> format. It has one section called <filename>[Desktop]</filename> "
+"which has two keys: <filename>Session</filename> and <filename>Language</"
+"filename>."
+msgstr ""
+
+#: C/gdm.xml:2052(para)
+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. 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 ""
+
+#: C/gdm.xml:2061(screen)
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop]\n"
+"Session=gnome\n"
+"Language=cs_CZ.UTF-8\n"
+msgstr ""
+
+#: C/gdm.xml:2073(title)
+msgid "GDM Commands"
+msgstr ""
+
+#: C/gdm.xml:2076(title)
+msgid "GDM Root User Commands"
+msgstr ""
+
+#: C/gdm.xml:2078(para)
+msgid ""
+"The GDM package provides the following commands in <filename>sbindir</"
+"filename> intended to be run by the root user:"
+msgstr ""
+
+#: C/gdm.xml:2084(title) C/gdm.xml:2099(title)
+msgid ""
+"<command>gdm</command> and <command>gdm-binary</command> Command Line Options"
+msgstr ""
+
+#: C/gdm.xml:2087(para)
+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>&lt;etc&gt;/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. The <command>gdm-binary</command> is the "
+"actual GDM daemon."
+msgstr ""
+
+#: C/gdm.xml:2103(term)
+msgid "-?, --help"
+msgstr ""
+
+#: C/gdm.xml:2105(para)
+msgid "Gives a brief overview of the command line options."
+msgstr ""
+
+#: C/gdm.xml:2112(term)
+msgid "--fatal-warnings"
+msgstr ""
+
+#: C/gdm.xml:2114(para)
+msgid "Make all warnings cause GDM to exit."
+msgstr ""
+
+#: C/gdm.xml:2121(term)
+msgid "--timed-exit"
+msgstr ""
+
+#: C/gdm.xml:2123(para)
+msgid "Exit after 30 seconds. Useful for debugging."
+msgstr ""
+
+#: C/gdm.xml:2130(term)
+msgid "--version"
+msgstr ""
+
+#: C/gdm.xml:2132(para)
+msgid "Print the version of the GDM daemon."
+msgstr ""
+
+#: C/gdm.xml:2141(title)
+msgid "<command>gdm-restart</command> Command Line Options"
+msgstr ""
+
+#: C/gdm.xml:2143(para)
+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 ""
+
+#: C/gdm.xml:2151(title)
+msgid "<command>gdm-safe-restart</command> Command Line Options"
+msgstr ""
+
+#: C/gdm.xml:2153(para)
+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 ""
+
+#: C/gdm.xml:2161(title)
+msgid "<command>gdm-stop</command> Command Line Options"
+msgstr ""
+
+#: C/gdm.xml:2163(para)
+msgid ""
+"<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM "
+"signal."
+msgstr ""
+
+#: C/gdm.xml:2174(title)
+msgid "Troubleshooting"
+msgstr ""
+
+#. <para>
+#.       TODO - any other tips we should add?  Might be useful to highlight any
+#.              common D-Bus configuration issues?
+#. </para>
+#: C/gdm.xml:2182(para)
+msgid ""
+"This section discusses helpful tips for getting GDM working. In general, if "
+"you have a problem using GDM, you can submit a bug or send an email to the "
+"gdm-list mailing list. Information about how to do this is in the "
+"Introduction section of the document."
+msgstr ""
+
+#: C/gdm.xml:2189(para)
+msgid ""
+"If GDM is failing to work properly, it is always a good idea to include "
+"debug information. To enable debugging, set the debug/Enable key to \"true\" "
+"in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file and restart "
+"GDM. Then use GDM to the point where it fails, and debug output will be sent "
+"to the system log file (<filename>&lt;var&gt;/log/messages</filename> or "
+"<filename>&lt;var&gt;/adm/messages</filename> depending on your Operating "
+"System). If you share this output with the GDM community via a bug report or "
+"email, please only include the GDM related debug information and not the "
+"entire file since it can be large. If you do not see any GDM syslog output, "
+"you may need to configure syslog (refer to the <ulink type=\"help\" url="
+"\"man:syslog\">syslog</ulink> man page)."
+msgstr ""
+
+#: C/gdm.xml:2205(title)
+msgid "GDM Will Not Start"
+msgstr ""
+
+#: C/gdm.xml:2207(para)
+msgid ""
+"There are a many problems that can cause GDM to fail to start, but this "
+"section will discuss a few common problems and how to approach tracking down "
+"a problem with GDM starting. Some problems will cause GDM to respond with an "
+"error message or dialog when it tries to start, but it can be difficult to "
+"track down problems when GDM fails silently."
+msgstr ""
+
+#: C/gdm.xml:2216(para)
+msgid ""
+"First make sure that the Xserver is configured properly. The GDM "
+"configuration file contains a command in the [server-Standard] section that "
+"is used for starting the Xserver. Verify that this command works on your "
+"system. Running this command from the console should start the Xserver. If "
+"it fails, then the problem is likely with your Xserver configuration. Refer "
+"to your Xserver error log for an idea of what the problem may be. The "
+"problem may also be that your Xserver requires different command-line "
+"options. If so, then modify the Xserver command in the GDM configuration "
+"file so that it is correct for your system."
+msgstr ""
+
+#: C/gdm.xml:2229(para)
+msgid ""
+"Also make sure that the <filename>/tmp</filename> directory has reasonable "
+"ownership and permissions, and that the machine's file system is not full. "
+"These problems will cause GDM to fail to start."
+msgstr ""
+
+#: C/gdm.xml:2240(title)
+msgid "License"
+msgstr ""
+
+#: C/gdm.xml:2241(para)
+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 ""
+
+#: C/gdm.xml:2249(para)
+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 ""
+
+#: C/gdm.xml:2255(para)
+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>51 Franklin Street, Fifth Floor</"
+"street><city>Boston</city>, <state>MA</state><postcode>02110-1301</"
+"postcode><country>USA</country></address>"
+msgstr ""
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
+#: C/gdm.xml:0(None)
+msgid "translator-credits"
+msgstr ""
