Adding upstream version 43.0.upstream/43.0upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 2455 insertions, 0 deletions

diff --git a/docs/nl/nl.po b/docs/nl/nl.po
new file mode 100644
index 0000000..35da334
--- /dev/null
+++ b/docs/nl/nl.po
@@ -0,0 +1,2455 @@
+# Dutch translation for gdm.
+# Copyright (C) 2022 gdm's COPYRIGHT HOLDER
+# This file is distributed under the same license as the gdm package.
+# Nathan Follens <nfollens@gnome.org>, 2022.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: gdm main\n"
+"POT-Creation-Date: 2022-03-30 16:33+0000\n"
+"PO-Revision-Date: 2022-06-30 23:48+0200\n"
+"Last-Translator: Nathan Follens <nfollens@gnome.org>\n"
+"Language-Team: Dutch <gnome-nl-list@gnome.org>\n"
+"Language: nl\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"
+"X-Generator: Poedit 3.1\n"
+
+#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
+msgctxt "_"
+msgid "translator-credits"
+msgstr "Nathan Follens <nfollens@gnome.org>, 2022."
+
+#. (itstool) path: articleinfo/title
+#: C/index.docbook:13
+msgid "GNOME Display Manager Reference Manual"
+msgstr ""
+
+#. (itstool) path: revhistory/revision
+#: C/index.docbook:16
+msgid "<revnumber>0.0</revnumber> <date>2008-09</date>"
+msgstr "<revnumber>0.0</revnumber> <date>2008-09</date>"
+
+#. (itstool) path: abstract/para
+#: C/index.docbook:23
+msgid "GDM is the GNOME Display Manager, a graphical login program."
+msgstr ""
+
+#. (itstool) path: authorgroup/author
+#: C/index.docbook:29
+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>"
+
+#. (itstool) path: authorgroup/author
+#: C/index.docbook:36
+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>"
+
+#. (itstool) path: authorgroup/author
+#: C/index.docbook:42
+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>"
+
+#. (itstool) path: authorgroup/author
+#: C/index.docbook:48
+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>"
+
+#. (itstool) path: authorgroup/author
+#: C/index.docbook:54
+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>"
+
+#. (itstool) path: articleinfo/copyright
+#: C/index.docbook:61
+msgid "<year>1998</year> <year>1999</year> <holder>Martin K. Petersen</holder>"
+msgstr "<year>1998</year> <year>1999</year> <holder>Martin K. Petersen</holder>"
+
+#. (itstool) path: articleinfo/copyright
+#: C/index.docbook:66
+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>"
+
+#. (itstool) path: articleinfo/copyright
+#: C/index.docbook:72
+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>"
+
+#. (itstool) path: articleinfo/copyright
+#: C/index.docbook:78
+msgid "<year>2003</year> <year>2011</year> <holder>Oracle and/or its affiliates. All rights reserved.</holder>"
+msgstr ""
+
+#. (itstool) path: legalnotice/para
+#: C/index.docbook:2
+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 ""
+
+#. (itstool) path: legalnotice/para
+#: C/index.docbook:12 C/legal.xml:12
+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 ""
+
+#. (itstool) path: legalnotice/para
+#: C/index.docbook:19 C/legal.xml:19
+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 ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:35 C/legal.xml:35
+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 ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:55 C/legal.xml:55
+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 ""
+
+#. (itstool) path: legalnotice/para
+#: C/index.docbook:28 C/legal.xml:28
+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 ""
+
+#. (itstool) path: articleinfo/releaseinfo
+#. (itstool) path: sect1/para
+#: C/index.docbook:86 C/index.docbook:97
+msgid "This manual describes version 2.26.0 of the GNOME Display Manager. It was last updated on 02/10/2009."
+msgstr ""
+
+#. (itstool) path: sect1/title
+#: C/index.docbook:95
+msgid "Terms and Conventions Used in This Manual"
+msgstr "Begrippen en conventies die in deze handleiding gebruikt worden"
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:102
+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 ""
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:107
+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 ""
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:113
+msgid "GDM - GNOME Display Manager. Used to describe the software package as a whole."
+msgstr ""
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:118
+msgid "Greeter - The graphical login window (provided by <command>gnome-shell</command>)."
+msgstr ""
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:122
+msgid "PAM - Pluggable Authentication Mechanism"
+msgstr ""
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:126
+msgid "XDMCP - X Display Manage Protocol"
+msgstr "XDMCP - X Display Manage Protocol"
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:130
+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 ""
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:136
+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 ""
+
+#. (itstool) path: sect1/title
+#: C/index.docbook:147
+msgid "Overview"
+msgstr "Overzicht"
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:150
+msgid "Introduction"
+msgstr "Inleiding"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:152
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:159
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:165
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:172
+msgid ""
+"For further information about GDM, refer to the project website at <ulink type=\"http\" url=\"http://wiki.gnome.org/Projects/GDM/\"> "
+"http://wiki.gnome.org/Projects/GDM</ulink>."
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:178
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:188
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:197
+msgid "Interface Stability"
+msgstr "Interfacestabiliteit"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:199
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:208
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:217
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:229
+msgid "Functional Description"
+msgstr "Functiebeschrijving"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:240
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:248
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:256
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:263
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:282
+msgid ""
+"The smartcard extension can be enabled or disabled via the <filename>org.gnome.display-manager.extensions.smartcard.active</filename> "
+"gsettings key."
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:288
+msgid ""
+"Likewise, the fingerprint extension can be enabled or disabled via the <filename>org.gnome.display-manager.extensions.fingerprint."
+"active</filename> gsettings key."
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:294
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:301
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:314
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:334
+msgid "Greeter Panel"
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:335
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:352
+msgid "Note that keyboard layout features are only available on systems that support libxklavier."
+msgstr ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:359
+msgid "Accessibility"
+msgstr "Toegankelijkheid"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:361
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:373
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:381
+msgid "The GDM Face Browser"
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:383
+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 org.gnome.login-screen disable-user-list GSettings 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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:397
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:403
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:411
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:427
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:436
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:442
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:449
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:461
+msgid "XDMCP"
+msgstr "XDMCP"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:470
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:479
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:486
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:492
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:502
+msgid "If XDMCP seems to not be working, make sure that all machines are specified in <filename>/etc/hosts</filename>."
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:507
+msgid "Refer to the \"Security\" section for information about security concerns when using XDMCP."
+msgstr ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:514
+msgid "Logging"
+msgstr "Loggen"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:516
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:524
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:531
+msgid ""
+"The session output is piped through the GDM daemon to the <filename>~/<replaceable>$XDG_CACHE_HOME</replaceable>/gdm/session.log</"
+"filename> file which usually expands to <filename>~/.cache/gdm/session.log</filename>. 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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:540
+msgid ""
+"Note that if GDM can not create this file for some reason, then a fallback file will be created named <filename>~/<replaceable>"
+"$XDG_CACHE_HOME</replaceable>/gdm/session.log.XXXXXXXX</filename> where the <filename>XXXXXXXX</filename> are some random characters."
+msgstr ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:548
+msgid "Fast User Switching"
+msgstr "Snel wisselen tussen gebruikers"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:550
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:559
+msgid ""
+"Note this feature is available on systems that support Virtual Terminals. This feature will not function if Virtual Terminals is not "
+"available."
+msgstr ""
+
+#. (itstool) path: sect1/title
+#: C/index.docbook:570
+msgid "Security"
+msgstr "Beveiliging"
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:573
+msgid "The GDM User And Group"
+msgstr "De GDM-gebruiker en -groep"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:575
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:584
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:592
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:605
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:617
+msgid "PAM"
+msgstr "PAM"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:619
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:627
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:637
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:647
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:657
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:665
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:676
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:685
+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 ""
+
+#. (itstool) path: sect2/screen
+#: C/index.docbook:695
+#, 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"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:703
+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 ""
+
+#. (itstool) path: sect2/screen
+#: C/index.docbook:708
+#, 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"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:712
+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 ""
+
+#. (itstool) path: sect2/screen
+#: C/index.docbook:723
+#, 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"
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:730
+msgid "utmp and wtmp"
+msgstr "utmp en wtmp"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:732
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:747
+msgid "Xserver Authentication Scheme"
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:749
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:757
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:774
+msgid "XDMCP Security"
+msgstr "XDMCP-beveiliging"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:776
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:782
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:795
+msgid "XDMCP Access Control"
+msgstr "XDMCP-toegangsbeheer"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:797
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:803
+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 ""
+
+#. (itstool) path: sect2/screen
+#: C/index.docbook:810
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .evil.domain\n"
+msgstr ""
+"\n"
+"gdm: .kwaadaardig.domein\n"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:813
+msgid "to <filename>&lt;etc&gt;/hosts.deny</filename>. You may also need to add"
+msgstr ""
+
+#. (itstool) path: sect2/screen
+#: C/index.docbook:817
+#, no-wrap
+msgid ""
+"\n"
+"gdm: .your.domain\n"
+msgstr ""
+"\n"
+"gdm: .uw.domein\n"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:820
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:829
+msgid "Firewall Security"
+msgstr "Firewallbeveiliging"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:831
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:842
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:849
+msgid "X is not a very safe protocol when using it over the Internet, and XDMCP is even less safe."
+msgstr ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:856
+msgid "PolicyKit"
+msgstr "PolicyKit"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:864
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:870
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:882
+msgid "RBAC (Role Based Access Control)"
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:884
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:890
+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 ""
+
+#. (itstool) path: sect1/title
+#: C/index.docbook:903
+msgid "Support for ConsoleKit"
+msgstr "Ondersteuning voor ConsoleKit"
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:914
+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 ""
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:922
+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 ""
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:936
+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 ""
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:945
+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 ""
+
+#. (itstool) path: sect1/title
+#: C/index.docbook:954
+msgid "Configuration"
+msgstr "Configuratie"
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:956
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:965
+msgid "Scripting Integration Points"
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:967
+msgid "The GDM script integration points can be found in the <filename>&lt;etc&gt;/gdm/</filename> directory:"
+msgstr ""
+
+#. (itstool) path: sect2/screen
+#: C/index.docbook:972
+#, 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"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:980
+msgid ""
+"The <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename>, and <filename>PostSession</filename> "
+"scripts all work as described below."
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:986
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:998
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1006
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1014
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1023
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1031
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1038
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1045
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:1055
+msgid "Autostart Configuration"
+msgstr "Autostartconfiguratie"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1057
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1066
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:1080
+msgid "Xsession Script"
+msgstr "Xsession-script"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1082
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:1095
+msgid "Daemon Configuration"
+msgstr "Daemonconfiguratie"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1097
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1107
+msgid ""
+"Note that older versions of GDM supported additional configuration options which are no longer supported in the latest versions of GDM."
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1112
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1120
+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 ""
+
+#. (itstool) path: sect2/screen
+#: C/index.docbook:1130
+#, no-wrap
+msgid ""
+"\n"
+"[daemon]\n"
+"TimedLoginEnable=true\n"
+"TimedLogin=you\n"
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1136
+msgid "A full list of supported configuration keys follow:"
+msgstr ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:1141
+msgid "[chooser]"
+msgstr "[chooser]"
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1145
+msgid "Multicast"
+msgstr "Multicast"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1147
+#, no-wrap
+msgid "Multicast=false"
+msgstr "Multicast=false"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1148
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1157
+msgid "MulticastAddr"
+msgstr "MulticastAddr"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1159
+#, no-wrap
+msgid "MulticastAddr=ff02::1"
+msgstr "MulticastAddr=ff02::1"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1160
+msgid "This is the Link-local multicast address."
+msgstr ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:1169
+msgid "[daemon]"
+msgstr "[daemon]"
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1172
+msgid "TimedLoginEnable"
+msgstr "TimedLoginEnable"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1174
+#, no-wrap
+msgid "TimedLoginEnable=false"
+msgstr "TimedLoginEnable=false"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1175
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1197
+msgid "TimedLogin"
+msgstr "TimedLogin"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1199
+#, no-wrap
+msgid "TimedLogin="
+msgstr "TimedLogin="
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1200
+msgid "This is the user that should be logged in after a specified number of seconds of inactivity."
+msgstr ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1204 C/index.docbook:1248
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1218
+msgid "TimedLoginDelay"
+msgstr "TimedLoginDelay"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1220
+#, no-wrap
+msgid "TimedLoginDelay=30"
+msgstr "TimedLoginDelay=30"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1221
+msgid "Delay in seconds before the <filename>TimedLogin</filename> user will be logged in."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1229
+msgid "AutomaticLoginEnable"
+msgstr "AutomaticLoginEnable"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1231
+#, no-wrap
+msgid "AutomaticLoginEnable=false"
+msgstr "AutomaticLoginEnable=false"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1232
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1241
+msgid "AutomaticLogin"
+msgstr "AutomaticLogin"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1243
+#, no-wrap
+msgid "AutomaticLogin="
+msgstr "AutomaticLogin="
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1244
+msgid "This is the user that should be logged in immediately if <filename>AutomaticLoginEnable</filename> is true."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1262
+msgid "User"
+msgstr "User"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1264
+#, no-wrap
+msgid "User=gdm"
+msgstr "User=gdm"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1265
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1275
+msgid "Group"
+msgstr "Group"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1277
+#, no-wrap
+msgid "Group=gdm"
+msgstr "Group=gdm"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1278
+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 ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:1290
+msgid "Debug Options"
+msgstr "Debugopties"
+
+#. (itstool) path: variablelist/title
+#: C/index.docbook:1293
+msgid "[debug]"
+msgstr "[debug]"
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1296 C/index.docbook:1427
+msgid "Enable"
+msgstr "Enable"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1298 C/index.docbook:1429
+#, no-wrap
+msgid "Enable=false"
+msgstr "Enable=false"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1299
+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 ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:1314
+msgid "Greeter Options"
+msgstr ""
+
+#. (itstool) path: variablelist/title
+#: C/index.docbook:1317
+msgid "[greeter]"
+msgstr "[greeter]"
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1320
+msgid "IncludeAll"
+msgstr "IncludeAll"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1322
+#, no-wrap
+msgid "IncludeAll=true"
+msgstr "IncludeAll=true"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1323
+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 ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1329
+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 ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1343
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1352
+msgid "Include"
+msgstr "Include"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1354
+#, no-wrap
+msgid "Include="
+msgstr "Include="
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1355
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1364
+msgid "Exclude"
+msgstr "Exclude"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1366
+#, 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"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1367
+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 ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:1381
+msgid "Security Options"
+msgstr "Beveiligingsopties"
+
+#. (itstool) path: variablelist/title
+#: C/index.docbook:1384
+msgid "[security]"
+msgstr "[security]"
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1387
+msgid "DisallowTCP"
+msgstr "DisallowTCP"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1389
+#, no-wrap
+msgid "DisallowTCP=true"
+msgstr "DisallowTCP=true"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1390
+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 ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:1402
+msgid "XDCMP Support"
+msgstr "XDCMP-ondersteuning"
+
+#. (itstool) path: variablelist/title
+#: C/index.docbook:1405
+msgid "[xdmcp]"
+msgstr "[xdmcp]"
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1408
+msgid "DisplaysPerHost"
+msgstr "DisplaysPerHost"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1410
+#, no-wrap
+msgid "DisplaysPerHost=1"
+msgstr "DisplaysPerHost=1"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1411
+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 ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1418
+msgid ""
+"Note that the number of attached DISPLAYS allowed is not limited. Only remote connections via XDMCP are limited by this configuration "
+"option."
+msgstr ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1430
+msgid "Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM."
+msgstr ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1435
+msgid "<filename>gdm</filename> listens for requests on UDP port 177. See the Port option for more information."
+msgstr ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1440
+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 ""
+
+#. (itstool) path: para/screen
+#: C/index.docbook:1448
+#, no-wrap
+msgid ""
+"\n"
+"gdm:.my.domain\n"
+msgstr ""
+"\n"
+"gdm:.mijn.domein\n"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1446
+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 ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1457
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1466
+msgid "HonorIndirect"
+msgstr "HonorIndirect"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1468
+#, no-wrap
+msgid "HonorIndirect=true"
+msgstr "HonorIndirect=true"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1469
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1478
+msgid "MaxPending"
+msgstr "MaxPending"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1480
+#, no-wrap
+msgid "MaxPending=4"
+msgstr "MaxPending=4"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1481
+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 ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1487
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1496
+msgid "MaxSessions"
+msgstr "MaxSessions"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1498
+#, no-wrap
+msgid "MaxSessions=16"
+msgstr "MaxSessions=16"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1499
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1508
+msgid "MaxWait"
+msgstr "MaxWait"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1510
+#, no-wrap
+msgid "MaxWait=30"
+msgstr "MaxWait=30"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1511
+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 ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1517
+msgid "GDM will then place the session id in the pending queue waiting for the display to respond with a MANAGE request."
+msgstr ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1522
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1531
+msgid "MaxWaitIndirect"
+msgstr "MaxWaitIndirect"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1533
+#, no-wrap
+msgid "MaxWaitIndirect=30"
+msgstr "MaxWaitIndirect=30"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1534
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1548
+msgid "PingIntervalSeconds"
+msgstr "PingIntervalSeconds"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1550
+#, no-wrap
+msgid "PingIntervalSeconds=60"
+msgstr "PingIntervalSeconds=60"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1551
+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 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 ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1560
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1573
+msgid "Port"
+msgstr "Port"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1575
+#, no-wrap
+msgid "Port=177"
+msgstr "Port=177"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1576
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1585
+msgid "Willing"
+msgstr "Willing"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1587
+#, no-wrap
+msgid "Willing=&lt;etc&gt;/gdm/Xwilling"
+msgstr "Willing=&lt;etc&gt;/gdm/Xwilling"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1588
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:1607
+msgid "Simple Greeter Configuration"
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1609
+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 ""
+
+#. (itstool) path: variablelist/title
+#: C/index.docbook:1620
+msgid "Greeter Configuration Keys"
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1623
+msgid "/apps/gdm/simple-greeter/banner_message_enable"
+msgstr "/apps/gdm/simple-greeter/banner_message_enable"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1625 C/index.docbook:1646 C/index.docbook:1657 C/index.docbook:1722 C/index.docbook:1787 C/index.docbook:1798
+#: C/index.docbook:1809 C/index.docbook:1820
+#, no-wrap
+msgid "false (boolean)"
+msgstr "false (boolean)"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1626
+msgid "Controls whether the banner message text is displayed."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1633
+msgid "/apps/gdm/simple-greeter/banner_message_text"
+msgstr "/apps/gdm/simple-greeter/banner_message_text"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1635
+#, no-wrap
+msgid "NULL (string)"
+msgstr "NULL (string)"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1636
+msgid "Specifies the text banner message to show on the greeter window."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1644
+msgid "/apps/gdm/simple-greeter/disable_restart_buttons"
+msgstr "/apps/gdm/simple-greeter/disable_restart_buttons"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1647
+msgid "Controls whether to show the restart buttons in the login window."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1655
+msgid "/apps/gdm/simple-greeter/disable_user_list"
+msgstr "/apps/gdm/simple-greeter/disable_user_list"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1658
+msgid "If true, then the face browser with known users is not shown in the login window."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1666
+msgid "/apps/gdm/simple-greeter/logo_icon_name"
+msgstr "/apps/gdm/simple-greeter/logo_icon_name"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1668
+#, no-wrap
+msgid "computer (string)"
+msgstr "computer (string)"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1669
+msgid "Set to the themed icon name to use for the greeter logo."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1676
+msgid "/apps/gdm/simple-greeter/recent-languages"
+msgstr "/apps/gdm/simple-greeter/recent-languages"
+
+#. (itstool) path: listitem/synopsis
+#: C/index.docbook:1678 C/index.docbook:1700
+#, no-wrap
+msgid "[] (string list)"
+msgstr "[] (string list)"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1679
+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 ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1687
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1698
+msgid "/apps/gdm/simple-greeter/recent-layouts"
+msgstr "/apps/gdm/simple-greeter/recent-layouts"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1701
+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 ""
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1709
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1720
+msgid "/apps/gdm/simple-greeter/wm_use_compiz"
+msgstr "/apps/gdm/simple-greeter/wm_use_compiz"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1723
+msgid "Controls whether compiz is used as the window manager instead of metacity."
+msgstr ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:1733
+msgid "Accessibility Configuration"
+msgstr "Toegankelijkheidsconfiguratie"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1735
+msgid "This section describes the accessibility configuration options available in GDM."
+msgstr ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:1741
+msgid "GDM Accessibility Dialog And GConf Keys"
+msgstr ""
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1743
+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 ""
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1750
+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 ""
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1764
+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 ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:1774
+msgid "Accessibility GConf Keys"
+msgstr "GConf-sleutels voor toegankelijkheid"
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1776
+msgid "GDM offers the following GConf keys to control its accessibility features:"
+msgstr "GDM biedt de volgende GConf-sleutels om zijn toegankelijkheidsfuncties te besturen:"
+
+#. (itstool) path: variablelist/title
+#: C/index.docbook:1782
+msgid "GDM Configuration Keys"
+msgstr "GDM-configuratiesleutels"
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1785
+msgid "/desktop/gnome/interface/accessibility"
+msgstr "/desktop/gnome/interface/accessibility"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1788
+msgid ""
+"Controls whether the Accessibility infrastructure will be started with the GDM GUI. This is needed for many accessibility technology "
+"programs to work."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1796
+msgid "/desktop/gnome/applications/at/screen_magnifier_enabled"
+msgstr "/desktop/gnome/applications/at/screen_magnifier_enabled"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1799
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1807
+msgid "/desktop/gnome/applications/at/screen_keyboard_enabled"
+msgstr "/desktop/gnome/applications/at/screen_keyboard_enabled"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1810
+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 ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:1818
+msgid "/desktop/gnome/applications/at/screen_reader_enabled"
+msgstr "/desktop/gnome/applications/at/screen_reader_enabled"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:1821
+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 ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:1832
+msgid "Linking GConf Keys to Accessibility Tools"
+msgstr "GConf-sleutels koppelen aan toegankelijkheidshulpmiddelen"
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1834
+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 ""
+
+#. (itstool) path: sect3/screen
+#: C/index.docbook:1846
+#, 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"
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1852
+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 ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:1862
+msgid "Example Of Modifying Accessibility Tool Configuration"
+msgstr "Voorbeeld van aangepaste toegankelijkheidshulpmiddelconfiguratie"
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1864
+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 ""
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1872
+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 ""
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1880
+msgid "The following is an example <filename>onboard.desktop</filename> file:"
+msgstr "Het volgende is een voorbeeld van een <filename>onboard.desktop</filename>-bestand:"
+
+#. (itstool) path: sect3/screen
+#: C/index.docbook:1884
+#, 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=Schermtoetsenbord\n"
+"Comment=Gebruik een schermtoetsenbord\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"
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1898
+msgid "The following is an example <filename>mousetweaks.desktop</filename> file:"
+msgstr "Het volgende is een voorbeeld van een <filename>mousetweaks.desktop</filename>-bestand:"
+
+#. (itstool) path: sect3/screen
+#: C/index.docbook:1903
+#, 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 ""
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1917
+msgid "Note the line with the AutostartCondition that links both desktop files to the GConf key for the on-screen keyboard."
+msgstr ""
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1922
+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 ""
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:1930
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:1939
+msgid "General Session Settings"
+msgstr "Algemene sessieinstellingen"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1948
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:1959
+msgid "GNOME Settings Daemon"
+msgstr "Gnome Settings Daemon"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1972
+msgid "GDM enables the following gnome-settings-daemon plugins: a11y-keyboard, background, sound, xsettings."
+msgstr "GDM schakelt de volgende gnome-settings-daemon-plug-ins in: a11y-keyboard, background, sound, xsettings."
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1977
+msgid "These are responsible for things like the background image, font and theme settings, sound events, etc."
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1982
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:1990
+msgid "GDM Session Configuration"
+msgstr "GDM-sessieconfiguratie"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1992
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:1999
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:2012
+msgid "A session can be disabled by editing the desktop file and adding a line as follows: <filename>Hidden=true</filename>."
+msgstr ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:2017
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:2036
+msgid "GDM User Session and Language Configuration"
+msgstr "GDM-gebruikersessie- en taalconfiguratie"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:2037
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:2045
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:2052
+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 ""
+
+#. (itstool) path: sect2/screen
+#: C/index.docbook:2061
+#, no-wrap
+msgid ""
+"\n"
+"[Desktop]\n"
+"Session=gnome\n"
+"Language=cs_CZ.UTF-8\n"
+msgstr ""
+
+#. (itstool) path: sect1/title
+#: C/index.docbook:2073
+msgid "GDM Commands"
+msgstr "GDM-opdrachten"
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:2076
+msgid "GDM Root User Commands"
+msgstr "GDM-rootgebruikersopdrachten"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:2078
+msgid "The GDM package provides the following commands in <filename>sbindir</filename> intended to be run by the root user:"
+msgstr ""
+
+#. (itstool) path: sect3/title
+#. (itstool) path: variablelist/title
+#: C/index.docbook:2084 C/index.docbook:2092
+msgid "<command>gdm</command> Command Line Options"
+msgstr "Opdrachtregelopties voor <command>gdm</command>"
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:2086
+msgid "<command>gdm</command> is the main daemon which sets up graphical login environment and starts necessary helpers."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:2095
+msgid "-?, --help"
+msgstr "-?, --help"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:2097
+msgid "Gives a brief overview of the command line options."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:2104
+msgid "--fatal-warnings"
+msgstr "--fatal-warnings"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:2106
+msgid "Make all warnings cause GDM to exit."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:2113
+msgid "--timed-exit"
+msgstr "--timed-exit"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:2115
+msgid "Exit after 30 seconds. Useful for debugging."
+msgstr ""
+
+#. (itstool) path: varlistentry/term
+#: C/index.docbook:2122
+msgid "--version"
+msgstr "--version"
+
+#. (itstool) path: listitem/para
+#: C/index.docbook:2124
+msgid "Print the version of the GDM daemon."
+msgstr ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:2133
+msgid "<command>gdm-restart</command> Command Line Options"
+msgstr "Opdrachtregelopties voor <command>gdm-restart</command>"
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:2135
+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 ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:2143
+msgid "<command>gdm-safe-restart</command> Command Line Options"
+msgstr "Opdrachtregelopties voor <command>gdm-safe-restart</command>"
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:2145
+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 ""
+
+#. (itstool) path: sect3/title
+#: C/index.docbook:2153
+msgid "<command>gdm-stop</command> Command Line Options"
+msgstr "Opdrachtregelopties voor <command>gdm-stop</command>"
+
+#. (itstool) path: sect3/para
+#: C/index.docbook:2155
+msgid "<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM signal."
+msgstr ""
+
+#. (itstool) path: sect1/title
+#: C/index.docbook:2166
+msgid "Troubleshooting"
+msgstr "Probleemoplossing"
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:2174
+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 ""
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:2181
+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 ""
+
+#. (itstool) path: sect2/title
+#: C/index.docbook:2197
+msgid "GDM Will Not Start"
+msgstr "GDM start niet"
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:2199
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:2208
+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 ""
+
+#. (itstool) path: sect2/para
+#: C/index.docbook:2221
+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 ""
+
+#. (itstool) path: sect1/title
+#: C/index.docbook:2232
+msgid "License"
+msgstr "Licentie"
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:2233
+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 ""
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:2241
+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 ""
+
+#. (itstool) path: para/address
+#: C/index.docbook:2255
+#, 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"
+"      "
+
+#. (itstool) path: sect1/para
+#: C/index.docbook:2247
+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 ""
+
+#. (itstool) path: para/ulink
+#: C/legal.xml:9
+msgid "link"
+msgstr "verwijzing"
+
+#. (itstool) path: legalnotice/para
+#: C/legal.xml:2
+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 ""