msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: 2008-09-07 03:19+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: C/legal.xml:2(para) C/gdm.xml:2(para) msgid "Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy of the GFDL at this link or in the file COPYING-DOCS distributed with this manual." msgstr "" #: C/legal.xml:12(para) C/gdm.xml:12(para) msgid "This manual is part of a collection of GNOME manuals distributed under the GFDL. If you want to distribute this manual separately from the collection, you can do so by adding a copy of the license to the manual, as described in section 6 of the license." msgstr "" #: C/legal.xml:19(para) C/gdm.xml:19(para) msgid "Many of the names used by companies to distinguish their products and services are claimed as trademarks. Where those names appear in any GNOME documentation, and the members of the GNOME Documentation Project are made aware of those trademarks, then the names are in capital letters or initial capital letters." msgstr "" #: C/legal.xml:35(para) C/gdm.xml:35(para) msgid "DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND" msgstr "" #: C/legal.xml:55(para) C/gdm.xml:55(para) msgid "UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES." msgstr "" #: C/legal.xml:28(para) C/gdm.xml:28(para) msgid "DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: " msgstr "" #: C/gdm.xml:11(title) msgid "Gnome Display Manager Reference Manual" msgstr "" #: C/gdm.xml:15(revnumber) msgid "0.0" msgstr "" #: C/gdm.xml:16(date) msgid "2007-01" msgstr "" #: C/gdm.xml:21(para) msgid "GDM is the GNOME Display Manager, a graphical login program." msgstr "" #: C/gdm.xml:28(firstname) msgid "Martin" msgstr "" #: C/gdm.xml:28(othername) msgid "K." msgstr "" #: C/gdm.xml:29(surname) msgid "Petersen" msgstr "" #: C/gdm.xml:31(email) msgid "mkp@mkp.net" msgstr "" #: C/gdm.xml:35(firstname) msgid "George" msgstr "" #: C/gdm.xml:35(surname) msgid "Lebl" msgstr "" #: C/gdm.xml:37(email) msgid "jirka@5z.com" msgstr "" #: C/gdm.xml:41(firstname) msgid "Brian" msgstr "" #: C/gdm.xml:41(surname) msgid "Cameron" msgstr "" #: C/gdm.xml:43(email) msgid "Brian.Cameron@Sun.COM" msgstr "" #: C/gdm.xml:47(firstname) msgid "Bill" msgstr "" #: C/gdm.xml:47(surname) msgid "Haneman" msgstr "" #: C/gdm.xml:49(email) msgid "Bill.Haneman@Sun.COM" msgstr "" #: C/gdm.xml:54(year) msgid "1998" msgstr "" #: C/gdm.xml:54(year) msgid "1999" msgstr "" #: C/gdm.xml:54(holder) msgid "Martin K. Petersen" msgstr "" #: C/gdm.xml:57(year) msgid "2001" msgstr "" #: C/gdm.xml:57(year) C/gdm.xml:61(year) C/gdm.xml:64(year) msgid "2003" msgstr "" #: C/gdm.xml:57(year) C/gdm.xml:64(year) msgid "2004" msgstr "" #: C/gdm.xml:58(holder) msgid "George Lebl" msgstr "" #: C/gdm.xml:61(holder) msgid "Red Hat, Inc." msgstr "" #: C/gdm.xml:64(holder) msgid "Sun Microsystems, Inc." msgstr "" #: C/gdm.xml:69(releaseinfo) C/gdm.xml:78(para) msgid "This manual describes version 2.18.0 of the GNOME Display Manager. It was last updated on 03/12/2007." msgstr "" #: C/gdm.xml:76(title) msgid "Terms and Conventions Used in This Manual" msgstr "" #: C/gdm.xml:83(para) msgid "Chooser - A program used to select a remote host for managing a display remotely on the local display (gdmchooser)." msgstr "" #: C/gdm.xml:88(para) msgid "Configurator - The configuration application (gdmsetup)." msgstr "" #: C/gdm.xml:93(para) msgid "GDM - Gnome Display Manager. Used to describe the software package as a whole. Sometimes also referred to as GDM2." msgstr "" #: C/gdm.xml:98(para) msgid "gdm - The Gnome Display Manager daemon (gdm)." msgstr "" #: C/gdm.xml:102(para) msgid "Greeter - The graphical login window (gdmlogin or gdmgreeter)." msgstr "" #: C/gdm.xml:107(para) msgid "GTK+ Greeter - The standard login window (gdmlogin)." msgstr "" #: C/gdm.xml:111(para) msgid "PAM - Pluggable Authentication Mechanism" msgstr "" #: C/gdm.xml:115(para) msgid "Themed Greeter - The themable login window ( gdmgreeter)." msgstr "" #: C/gdm.xml:120(para) msgid "XDMCP - X Display Manage Protocol" msgstr "" #: C/gdm.xml:124(para) msgid "Paths that start with a word in angle brackets are relative to the installation prefix. I.e. <share>/pixmaps/ refers to <share>/pixmaps if GDM was configured with --prefix=/usr. Normally also note that GDM is installed with --sysconfigdir=<etc>/X11, meaning any path to which we refer to as <etc>/gdm/PreSession usually means <etc/X11>/gdm/PreSession. Note that for interoperability it is recommended that you use a --prefix of /usr and a --sysconfdir of <etc>/X11." msgstr "" #: C/gdm.xml:140(title) msgid "Overview" msgstr "" #: C/gdm.xml:143(title) msgid "Introduction" msgstr "" #: C/gdm.xml:147(para) msgid "The Gnome Display Manager (GDM) is a display manager that implements all significant features required for managing local and remote displays. GDM was written from scratch and does not contain any XDM / X Consortium code." msgstr "" #: C/gdm.xml:154(para) msgid "For further information about GDM, see the the GDM project website. Please submit any bug reports or enhancement requests to the \"gdm\" category in bugzilla.gnome.org. You can also send a message to the
gdm-list@gnome.org
mail list to discuss any issues or concerns with the GDM program." msgstr "" #: C/gdm.xml:167(title) msgid "Interface Stability" msgstr "" #: C/gdm.xml:171(para) msgid "The key/value pairs defined in the GDM configuration files and the location of these files are considered \"stable\" interfaces and should only change in ways that are backwards compatible. Note that this includes functionality like the GDM scripts (Init, PreSession, PostSession, PostLogin, XKeepsCrashing, etc.); directory locations (ServAuthDir, PidFile, etc.), system applications (SoundProgram), etc. Some configuration values depend on OS interfaces may need to be modified to work on a given OS. Typical examples are HaltCommand, RebootCommand, CustomCommands, SuspendCommand, StandardXServer, Xnest, SoundProgram, and the \"command\" value for each \"server-foo\"." msgstr "" #: C/gdm.xml:185(para) msgid "Note: distributions often change the default values of keys to support their platform. Command-line interfaces for GDM programs installed to <bin> and <sbin> are considered stable. Refer to your distribution documentation to see if there are any distribution-specific changes to these GDM interfaces and what support exists for them." msgstr "" #: C/gdm.xml:194(para) msgid "As of the GDM 2.15 development series, some one-dash arguments are no longer supported. This includes the \"-xdmaddress\", \"-clientaddress\", and \"-connectionType\" arguments used by gdmchooser. These arguments have been changed to now use two dashes." msgstr "" #: C/gdm.xml:202(para) msgid "If issues are discovered that break compatibility, please file a bug with an \"urgent\" priority." msgstr "" #: C/gdm.xml:209(title) msgid "The GDM Daemon" msgstr "" #: C/gdm.xml:211(para) msgid "The GDM daemon is responsible for managing displays on the system. This includes authenticating users, starting the user session, and terminating the user session. GDM is configurable and the ways it can be configured are described in the \"Configuring GDM\" section of this document. The Init, PostLogin, PreSession, and PostSession scripts discussed below are discussed in this \"Configuring GDM section\"." msgstr "" #: C/gdm.xml:222(para) msgid "The GDM daemon supports a UNIX domain socket protocol which can be used to control aspects of its behavior and to query information. This protocol is described in the \"Controlling GDM\" section of this document." msgstr "" #: C/gdm.xml:229(para) msgid "GDM can be asked to manage a display a number of ways. Local displays are always managed when GDM starts and will be restarted when a user's session is finished. Displays can be requested via XDMCP, flexible displays can be requested by running the gdmflexiserver command. Displays that are started on request are not restarted on session exit. GDM also provides the gdmdynamic command to allow easier management of displays on a multi-user server. These display types are discussed further in the next section." msgstr "" #: C/gdm.xml:241(para) msgid "When the GDM daemon is asked to manage a display, it will fork an X server process, then run the Init script as the root user, and start the login GUI dialog as a slave process on the display. GDM can be configured to use either gdmgreeter (the default) or gdmlogin as the GUI dialog program. The gdmlogin program supports accessibility while the gdmgreeter program supports greater themeability. The GUI dialog is run as the unpriviledged \"gdm\" user/group which is described in the \"Security\" section below. The GUI dialog communicates with the daemon via a sockets protocol and via standard input/output. The slave, for example passes the username and password information to the GDM daemon via standard input/output so the daemon can handle the actual authentication." msgstr "" #: C/gdm.xml:258(para) msgid "The login GUI dialog screen allows the user to select which session they wish to start and which language they wish to use. Sessions are defined by files that end in the .desktop extension and more information about these files can be found in the \"Configuration\" section. The user enters their name and password and if these successfully authenticate, GDM will start the requested session for the user. It is possible to configure GDM to avoid the authentication process by turning on the Automatic or Timed Login features in the GDM configuration. The login GUI can also be configured to provide additional features to the user, such as the Face Browser; the ability to halt, restart, or suspend the system; and/or edit the login configuration (after entering the root password)." msgstr "" #: C/gdm.xml:273(para) msgid "GDM, by default, will use Pluggable Authentication Modules (PAM) for authentication, but can also support regular crypt and shadow passwords on legacy systems. After authenticating a user, the daemon runs the PostLogin script as root, and forks a slave process to start the requested session. This slave process runs the PreSession script as root, sets up the user's environment, and starts the requested session. GDM keeps track of the user's default session and language in the user's ~/.dmrc and will use these defaults if the user did not pick a session or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN interface after user authentication to tell the X server to be restarted as the user instead of as root for added security. When the user's session exits, the GDM daemon will run the PostSession script as root." msgstr "" #: C/gdm.xml:290(para) msgid "Note that, by default, GDM uses the \"gdm\" service name for normal login and the \"gdm-autologin\" service name for automatic login. The PamStack configuration option can be used to specify a different service name. For example, if \"foo\" is specified, then GDM will use the \"foo\" service name for normal login and \"foo-autologin\" for automatic login." msgstr "" #: C/gdm.xml:300(para) msgid "For those looking at the code, the gdm_verify_user function in daemon/verify-pam.c is used for normal login and the gdm_verify_setup_user function is used for automatic login." msgstr "" #: C/gdm.xml:308(title) msgid "Different Display Types" msgstr "" #: C/gdm.xml:310(para) msgid "GDM supports three different display types: static (local) displays, flexible (on-demand) displays, and XDMCP (remote) displays. The \"X Server Definitions\" and the \"Local Static X Display Configuration\" subsections of the \"Configuration\" section explains how these various types of displays are defined in the GDM configuration file." msgstr "" #: C/gdm.xml:319(para) msgid "Local static displays are always started by the daemon, and when they die or are killed, they are restarted. GDM can run as many of these as needed. GDM can also manage displays on which it does not manage a GUI login, thus GDM can be used for supporting X terminals." msgstr "" #: C/gdm.xml:326(para) msgid "Flexible, or on demand displays, are started via the socket protocol with the gdmflexiserver command. This feature is only available to users logged in on the console and will display a new login screen. If a flexible display has previously been started on the console, running gdmflexiserver again will display a menu allowing users to switch back to a previous session or start a new flexible session. The gdmflexiserver locks the current session before starting a new flexible display, so the user's password must be entered before returning to an existing session. The gdmflexiserver command can also be used to launch nested Xnest display. These are launched in a window in the user's current session. Nested displays can be started even if not logged into the console and are started by running the gdmflexiserver -n command. Flexible displays are not restarted when the user session ends. Flexible displays require virtual terminal (VT) support in the kernel, and will not be available if not supported (such as on Solaris). Nested displays require that the X server supports Xnest." msgstr "" #: C/gdm.xml:347(para) msgid "The last display type is the XDMCP remote displays which are described in the next section. Remote hosts can connect to GDM and present the login screen if this is enabled. Some things are different for remote sessions. For example, the Actions menu which allows you to shut down, restart, suspend, or configure GDM are not shown." msgstr "" #: C/gdm.xml:355(para) msgid "Displays started via the gdmdynamic command are treated as local displays, so they are restarted automatically on when the session exits. This command is intended to more effectively manage the displays on a multi-user server (many displays connected to a single server)." msgstr "" #: C/gdm.xml:365(title) msgid "XDMCP" msgstr "" #: C/gdm.xml:369(para) msgid "The GDM daemon can be configured to listen for and manage X Display Manage Protocol (XDMCP) requests from remote displays. By default XDMCP support is turned off, but can be enabled if desired. If GDM is built with TCP Wrapper support, then the daemon will only grant access to hosts specified in the GDM service section in the TCP Wrappers configuration file." msgstr "" #: C/gdm.xml:378(para) msgid "GDM includes several measures making it more resistant to denial of service attacks on the XDMCP service. A lot of the protocol parameters, handshaking timeouts etc. can be fine tuned. The defaults should work for most systems, however. Do not change them unless you know what you are doing." msgstr "" #: C/gdm.xml:386(para) msgid "GDM listens to UDP port 177 and will respond to QUERY and BROADCAST_QUERY requests by sending a WILLING packet to the originator." msgstr "" #: C/gdm.xml:391(para) msgid "GDM can also be configured to honor INDIRECT queries and present a host chooser to the remote display. GDM will remember the user's choice and forward subsequent requests to the chosen manager. GDM also supports an extension to the protocol which will make it forget the redirection once the user's connection succeeds. This extension is only supported if both daemons are GDM. It is transparent and will be ignored by XDM or other daemons that implement XDMCP." msgstr "" #: C/gdm.xml:401(para) msgid "Refer to the \"Security\" section for information about security concerns when using XDMCP." msgstr "" #: C/gdm.xml:408(title) msgid "Securing Remote Connection Through SSH" msgstr "" #: C/gdm.xml:411(para) msgid "As explained in the \"Security\" section, XDMCP does not use any kind of encryption and as such is inherently insecure. As XDMCP uses UDP as a network transport layer, it is not possible to simply secure it through an SSH tunnel." msgstr "" #: C/gdm.xml:418(para) msgid "To remedy this problem, gdm can be configured at compilation-time with the option --enable-secureremote, in which case gdm proposes as a built-in session a session called \"Secure Remote Connection\". Starting such a session allows the user to enter the name or the address of the host on which to connect; provided the said host runs an SSH server, the user then gets connected to the server on which the default X session is started and displayed on the local host." msgstr "" #: C/gdm.xml:428(para) msgid "Using this session allows a much more secure network connection and only necessitates to have an SSH server running on the remote host." msgstr "" #: C/gdm.xml:435(title) msgid "The GTK+ Greeter" msgstr "" #: C/gdm.xml:437(para) msgid "The GTK+ Greeter is the default graphical user interface that is presented to the user. The greeter contains a menu at the top, an optional face browser, an optional logo and a text entry widget. This greeter has full accessibility support, and should be used by users with accessibility needs." msgstr "" #: C/gdm.xml:445(para) msgid "The text entry field is used for entering logins, passwords, passphrases etc. gdmlogin is controlled by the underlying daemon and is basically stateless. The daemon controls the greeter through a simple protocol where it can ask the greeter for a text string with echo turned on or off. Similarly, the daemon can change the label above the text entry widget to correspond to the value the authentication system wants the user to enter." msgstr "" #: C/gdm.xml:455(para) msgid "The menu bar in the top of the greeter enables the user to select the requested session type/desktop environment, select an appropriate locale/language, halt/restart/suspend the computer, configure GDM (given the user knows the root password), change the GTK+ theme, or start an XDMCP chooser." msgstr "" #: C/gdm.xml:463(para) msgid "The greeter can optionally display a logo in the login window. The image must be in a format readable to the gdk-pixbuf library (GIF, JPG, PNG, TIFF, XPM and possibly others), and it must be readable to the GDM user. See the Logo option in the reference section below for details." msgstr "" #: C/gdm.xml:473(title) msgid "The Themed Greeter" msgstr "" #: C/gdm.xml:475(para) msgid "The Themed Greeter is a greeter interface that takes up the whole screen and is very themable. Themes can be selected and new themes can be installed by the configuration application or by setting the GraphicalTheme configuration key. The Themed Greeter is much like the GTK+ Greeter in that it is controlled by the underlying daemon, is stateless, and is controlled by the daemon using the same simple protocol." msgstr "" #: C/gdm.xml:485(para) msgid "The look and feel of this greeter is really controlled by the theme and so the user interface elements that are present may be different. The only thing that must always be present is the text entry field as described above in the GTK+ Greeter. The theme can include buttons that allow the user to select an appropriate locale/language, halt/restart/suspend the computer, configure GDM (given the user knows the root password), or start an XDMCP chooser." msgstr "" #: C/gdm.xml:495(para) msgid "You can always get a menu of available actions by pressing the F10 key. This can be useful if the theme doesn't provide certain buttons when you wish to do some action allowed by the GDM configuration." msgstr "" #: C/gdm.xml:503(title) msgid "The GDM Face Browser" msgstr "" #: C/gdm.xml:505(para) msgid "GDM supports a face browser which will display a list of users who can login and an icon for each user. This feature can be used with the GTK+ Greeter if the Browser configuration option is set to \"true\". This feature can be used with the Themed Greeter if using a GDM theme which includes a \"userlist\" item type is defined, such as \"happygnome-list\"" msgstr "" #: C/gdm.xml:515(para) msgid "By default, the face browser is disabled since revealing usernames on the login screen is not appropriate on many systems for security reasons. Also GDM requires some setup to specify which users should be visible. Setup can be done on the \"Users\" tab in gdmsetup. This feature is most practical to use on a system with a smaller number of users." msgstr "" #: C/gdm.xml:524(para) msgid "The icons used by GDM can be installed globally by the sysadmin or can be located in the users' home directories. If installed globally they should be in the <share>/pixmaps/faces/ directory (though this can be configured with the GlobalFaceDir configuration option) and the filename should be the name of the user, optionally with a .png appended. Face icons placed in the global face directory must be readable to the GDM user. However, the daemon, proxies user pictures to the greeter and thus those do not have be be readable by the \"gdm\" user, but root." msgstr "" #: C/gdm.xml:537(para) msgid "Users may run the gdmphotosetup command to configure the image to use for their userid. This program properly scales the file down if it is larger than the MaxIconWidth or MaxIconHeight configuration options and places the icon in a file called ~/.face. Although gdmphotosetup scales user images automatically, this does not guarantee that user images are properly scaled since a user may create their ~/.face file by hand." msgstr "" #: C/gdm.xml:549(para) msgid "GDM will first look for the user's face image in ~/.face. If not found, it will try ~/.face.icon. If still not found, it will use the value defined for \"face/picture=\" in the ~/.gnome2/gdm file. Lastly, it will try ~/.gnome2/photo and ~/.gnome/photo which are deprecated and supported for backwards compatibility." msgstr "" #: C/gdm.xml:560(para) msgid "If a user has no defined face image, GDM will use the \"stock_person\" icon defined in the current GTK+ theme. If no such image is defined, it will fallback to the image specified in the DefaultFace configuration option, normally <share>/pixmaps/nobody.png." msgstr "" #: C/gdm.xml:568(para) msgid "Please note that loading and scaling face icons located in user home directories can be a very time-consuming task. Since it not practical to load images over NIS or NFS, GDM does not attempt to load face images from remote home directories. Furthermore, GDM will give up loading face images after 5 seconds of activity and will only display the users whose pictures it has gotten so far. The Include configuration option can be used to specify a set of users who should appear on the face browser. As long as the users to include is of a reasonable size, there should not be a problem with GDM being unable to access the face images. To work around such problems, it is recommended to place face images in the directory specified by the GlobalFaceDir configuration option." msgstr "" #: C/gdm.xml:584(para) msgid "To control the users who get displayed in the face browser, there are a number of configuration options that can be used. If the IncludeAll option is set to true, then the password file will be scanned and all users will be displayed. If IncludeAll option is set to false, then the Include option should contain a list of users separated by commas. Only the users specified will be displayed. Any user listed in the Exclude option and users whose UID's is lower than MinimalUID will be filtered out regardless of the IncludeAll setting. IncludeAll is not recommended for systems where the passwords are loaded over a network (such as when NIS is used), since it can be very slow to load more than a small number of users over the network.." msgstr "" #: C/gdm.xml:601(para) msgid "When the browser is turned on, valid usernames on the computer are inherently exposed to a potential intruder. This may be a bad idea if you do not know who can get to a login screen. This is especially true if you run XDMCP (turned off by default)." msgstr "" #: C/gdm.xml:610(title) msgid "Logging" msgstr "" #: C/gdm.xml:612(para) msgid "GDM itself will use syslog to log errors or status. It can also log debugging information, which can be useful for tracking down problems if GDM is not working properly. This can be enabled in the configuration file." msgstr "" #: C/gdm.xml:619(para) msgid "Output from the various X servers is stored in the GDM log directory, which is configurable, but is usually <var>/log/gdm/. The output from the session can be found in a file called <display>.log. Four older files are also stored with .1 through .4 appended. These will be rotated as new sessions on that display are started. You can use these logs to view what the X server said when it started up." msgstr "" #: C/gdm.xml:631(para) msgid "The output from the user session is redirected to ~/.xsession-errors before even the PreSession script is started. So it is not really necessary to redirect this again in the session setup script. As is usually done. If the user session lasted less then 10 seconds, GDM assumes that the session crashed and allows the user to view this file in a dialog before returning to the login screen. This way the user can view the session errors from the last session and correct the problem this way." msgstr "" #: C/gdm.xml:643(para) msgid "You can suppress the 10 second warning by returning code 66 from the Xsessionscript or from your session binary (the default Xsession script propagates those codes back). This is useful if you have some sort of special logins for which it is not an error to return less then 10 seconds later, or if you setup the session to already display some error message and the GDM message would be confusing and redundant." msgstr "" #: C/gdm.xml:653(para) msgid "The session output is piped through the GDM daemon and so the ~/.xsession-errors file is capped at about 200 kilobytes by GDM to prevent a possible denial of service attack on the session. An app could perhaps on reading some wrong data print out warnings or errors on the stderr or stdout. This could perhaps fill up the user's home directory who would then have to log out and log back in to clear this. This could be especially nasty if quotas are set. GDM also correctly traps the XFSZ signal and stops writing the file, which would lead to killed sessions if the file was redirected in the old fashioned way from the script." msgstr "" #: C/gdm.xml:666(para) msgid "Note that some distributors seem to override the ~/.xsession-errors redirection and do it themselves in their own Xsession script (set by the BaseXsession configuration key) which means that GDM will not be able to trap the output and cap this file. You also lose output from the PreSession script which can make debugging things harder to figure out as perhaps useful output of what is wrong will not be printed out. See the description of the BaseXsession configuration key for more information, especially on how to handle multiple display managers using the same script." msgstr "" #: C/gdm.xml:680(para) msgid "Note that if the session is a failsafe session, or if GDM can't open this file for some reason, then a fallback file will be created in the /tmp directory named /tmp/xses-<user>.XXXXXX where the XXXXXX are some random characters." msgstr "" #: C/gdm.xml:688(para) msgid "If you run a system with quotas set, it would be good to delete the ~/.xsession-errors in the PostSession script. Such that this log file doesn't unnecessarily stay around." msgstr "" #: C/gdm.xml:697(title) msgid "Accessing Files" msgstr "" #: C/gdm.xml:699(para) msgid "In general GDM is very reluctant regarding reading/writing of user files (such as the ~/.dmrc, ~/.face, ~/.xsession-errors, and ~/.Xauthority files). For instance it refuses to access anything but regular files. Links, sockets and devices are ignored. The value of the RelaxPermissions parameter determines whether GDM should accept files writable by the user's group or others. These are ignored by default." msgstr "" #: C/gdm.xml:711(para) msgid "All operations on user files are done with the effective user id of the user. If the sanity check fails on the user's .Xauthority file, a fallback cookie is created in the directory specified by the UserAuthFBDir configuration setting (/tmp by default)." msgstr "" #: C/gdm.xml:719(para) msgid "Finally, the sysadmin can specify the maximum file size GDM should accept, and, if the face browser is enabled, a tunable maximum icon size is also enforced. On large systems it is still advised to turn off the face browser for performance reasons. Looking up icons in home directories, scaling and rendering face icons can take a long time." msgstr "" #: C/gdm.xml:730(title) msgid "GDM Performance" msgstr "" #: C/gdm.xml:732(para) msgid "To speed performance it is possible to build GDM so that it will preload libraries when GDM first displays a greeter program. This has been shown to speed first time login since these libraries can be loaded into memory while the user types in their username and password." msgstr "" #: C/gdm.xml:740(para) msgid "To use this feature, configure GDM with the --with-prefetch option. This will cause GDM to install the gdmprefetch program to the libexecdir directory, install the gdmprefetchlist to the <etc>/gdm directory, and set the PreFetchProgram configuration variable so that the gdmprefetch program is called with the default gdmprefetchlist file. The default gdmprefetchlist file was optimized for a GNOME desktop running on Solaris, so may need fine-tuning on other systems. Alternative prefetchlist files can be contributed to the \"gdm\" category in bugzilla.gnome.org, so that they can be included in future GDM releases." msgstr "" #: C/gdm.xml:761(title) msgid "Security" msgstr "" #: C/gdm.xml:764(title) msgid "PAM" msgstr "" #: C/gdm.xml:768(para) msgid "GDM uses PAM for login authentication, though if your machine does not support PAM you can build GDM to work with the password database and the crypt library function." msgstr "" #: C/gdm.xml:774(para) msgid "PAM stands for Pluggable Authentication Module, and is used by most programs that request authentication on your computer. It allows the administrator to configure different authentication behavior for different programs." msgstr "" #: C/gdm.xml:781(para) msgid "Some GDM features (like turning on automatic login) may require that you update your PAM configuration. PAM configuration has different, but similar, interfaces on different operating systems, so check your pam.d or pam.conf man page for details. Be sure that you read the PAM documentation (e.g. pam.d/pam.conf man page) and are comfortable with the security implications of any changes you intend to make to your configuration." msgstr "" #: C/gdm.xml:791(para) msgid "If there is no entry for GDM in your system's PAM configuration file, then features like automatic login may not work. Not having an entry will cause GDM to use default behavior, conservative settings are recommended and probably shipped with your distribution." msgstr "" #: C/gdm.xml:798(para) msgid "If you wish to make GDM work with other types of authentication mechanisms (such as a SmartCard), 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. This issue has been discussed on the
gdm-list@gnome.org
mail list, so you can refer to the list archives for more information." msgstr "" #: C/gdm.xml:810(title) msgid "The GDM User" msgstr "" #: C/gdm.xml:812(para) msgid "For security reasons a dedicated user and group id are required for proper operation! The need to be able to write Xauth files is why user \"nobody\" is not appropriate for gdm." msgstr "" #: C/gdm.xml:818(para) msgid "The GDM daemon normally runs as root, as does the slave. However GDM should also have a dedicated user id and a group id which it uses for its graphical interfaces such as gdmgreeter and gdmlogin. These are configured via the User and Group configuration options in the GDM configuration files. The user and group should be created before running \"make install\". By default GDM assumes the user and the group are called \"gdm\"." msgstr "" #: C/gdm.xml:829(para) msgid "This userid is used to run the GDM GUI programs required for login. All functionality that requires root authority is done by the GDM daemon process. This design ensures that if the GUI programs are somehow exploited, only the dedicated user privileges are available." msgstr "" #: C/gdm.xml:836(para) msgid "It should however be noted that the GDM user and group have some privileges that make them somewhat dangerous. For one, they have access to the X server authorization directory. It must be able to read and write Xauth keys to <var>/lib/gdm. This directory should have root:gdm ownership and 1770 permissions. Running \"make install\" will set this directory to these values. The GDM daemon process will reset this directory to proper ownership/permissions if it is somehow not set properly." msgstr "" #: C/gdm.xml:847(para) msgid "The danger is that someone who gains the GDM user/group privileges can then connect to any session. So you should not, under any circumstances, make this some user/group which may be easy to get access to, such as the user nobody. Users who gain access to the \"gdm\" user could also modify the Xauth keys causing Denial-Of-Service attacks. Also if a person gains the ability to run programs as the user \"gdm\", it would be possible to snoop on running GDM processes, including usernames and passwords as they are being typed in." msgstr "" #: C/gdm.xml:859(para) msgid "Distributions and system administrators using GDM are expected to setup the dedicated user properly. It is recommended that this userid be configured to disallow login and to not have a default shell. Distributions and system administrators should set up the filesystem to ensure that the GDM user does not have read or write access to sensitive files." msgstr "" #: C/gdm.xml:870(title) msgid "X Server Authentication Scheme" msgstr "" #: C/gdm.xml:872(para) msgid "The X server authorization directory (the ServAuthDir) is used for a host of random internal data in addition to the X server authorization files, and the naming is really a relic of history. GDM daemon enforces this directory to be owned by root.gdm with the permissions of 1770. This way, only root and the GDM group have write access to this directory, but the GDM group cannot remove the root owned files from this directory, such as the X server authorization files." msgstr "" #: C/gdm.xml:884(para) msgid "GDM by default doesn't trust the X server authorization directory and treats it in the same way as the temporary directory with respect to creating files. This way someone breaking the GDM user cannot mount attacks by creating links in this directory. Similarly the X server log directory is treated safely, but that directory should really be owned and writable only by root." msgstr "" #: C/gdm.xml:893(para) msgid "GDM only supports the MIT-MAGIC-COOKIE-1 X server authentication scheme. Normally little is gained from the other schemes, and no effort has been made to implement them so far. Be especially careful about using XDMCP because the X server authentication cookie goes over the wire as clear text. If snooping is possible, then an attacker could simply snoop your authentication password as you log in, regardless of the authentication scheme being used. If snooping is possible and undesirable, then you should use ssh for tunneling an X connection rather then using XDMCP. You could think of XDMCP as a sort of graphical telnet, having the same security issues." msgstr "" #: C/gdm.xml:906(para) msgid "On the upside, GDM's random number generation is very conservative and GDM goes to extraordinary measures to truly get a 128 bit random number, using hardware random number generators (if available), plus the current time (in microsecond precision), a 20 byte array of pseudorandom numbers, process pid's, and other random information (possibly using /dev/audio or /dev/mem if hardware random generators are not available) to create a large buffer and then run MD5 digest on this. Obviously, all this work is wasted if you send this cookie over an open network or store it on an NFS directory (see UserAuthDir configuration key). So be careful about where you use remote X display." msgstr "" #: C/gdm.xml:923(title) msgid "Firewall Security" msgstr "" #: C/gdm.xml:925(para) msgid "Even though GDM tries to outsmart potential attackers trying to take advantage of XDMCP, it is still advised that you block the XDMCP port (normally UDP port 177) on your firewall unless you really need it. GDM guards against DoS (Denial of Service) attacks, but the X protocol is still inherently insecure and should only be used in controlled environments. Also each remote connection takes up lots of resources, so it is much easier to DoS via XDMCP then a webserver." msgstr "" #: C/gdm.xml:935(para) msgid "It is also wise to block all of the X Server ports. These are TCP ports 6000 + the display number of course) on your firewall. Note that GDM will use display numbers 20 and higher for flexible on-demand servers." msgstr "" #: C/gdm.xml:942(para) msgid "X is not a very safe protocol for leaving on the net, and XDMCP is even less safe." msgstr "" #: C/gdm.xml:949(title) msgid "GDM Security With NFS" msgstr "" #: C/gdm.xml:951(para) msgid "Note that NFS traffic really goes \"over the wire\" and thus can be snooped. When accessing the user's X authorization file (~/.Xauthority), GDM will try to open the file for reading as root. If it fails, GDM will conclude that it is on an NFS mount and it will automatically use UserAuthFBDir, which by default is set to /tmp. This behavior can be changed by setting the NeverPlaceCookiesOnNFS in the [security] section to false." msgstr "" #: C/gdm.xml:965(title) msgid "XDMCP Security" msgstr "" #: C/gdm.xml:967(para) msgid "Even though your display is protected by cookies, XEvents and thus keystrokes typed when entering passwords will still go over the wire in clear text. It is trivial to capture these." msgstr "" #: C/gdm.xml:973(para) msgid "XDMCP is primarily useful for running thin clients such as in terminal labs. Those thin clients will only ever need the network to access the server, and so it seems like the best security policy to have those thin clients on a separate network that cannot be accessed by the outside world, and can only connect to the server. The only point from which you need to access outside is the server." msgstr "" #: C/gdm.xml:982(para) msgid "The above sections \"X Server Authentication Scheme\" and \"Firewall Security\" also contain important information about using XDMCP securely. The next section also discusses how to set up XDMCP access control." msgstr "" #: C/gdm.xml:989(para) msgid "To workaround the inherent insecurity of XDMCP, gdm proposes a default built-in session that uses SSH to encrypt the remote connection. See the section \"Securing remote connection through SSH\" above." msgstr "" #: C/gdm.xml:997(title) msgid "XDMCP Access Control" msgstr "" #: C/gdm.xml:999(para) msgid "XDMCP access control is done using TCP wrappers. It is possible to compile GDM without TCP wrappers however, so you should test your configuration and verify that they work." msgstr "" #: C/gdm.xml:1005(para) msgid "You should use the daemon name gdm in the <etc>/hosts.allow and <etc>/hosts.deny files. For example to deny computers from .evil.domain from logging in, then add" msgstr "" #: C/gdm.xml:1012(screen) #, no-wrap msgid "\ngdm: .evil.domain\n" msgstr "" #: C/gdm.xml:1015(para) msgid "to <etc>/hosts.deny. You may also need to add" msgstr "" #: C/gdm.xml:1019(screen) #, no-wrap msgid "\ngdm: .your.domain\n" msgstr "" #: C/gdm.xml:1022(para) msgid "to your <etc>/hosts.allow if you normally disallow all services from all hosts. See the hosts.allow(5) man page for details." msgstr "" #: C/gdm.xml:1032(title) msgid "Support for ConsoleKit" msgstr "" #: C/gdm.xml:1034(para) msgid "GDM includes support for publishing user login information with the user and login session accounting framework known as ConsoleKit. ConsoleKit is able to keep track of all the users currently logged in. In this respect, it can be used as a replacement for the utmp or utmpx files that are available on most Unix-like operating systems." msgstr "" #: C/gdm.xml:1041(para) msgid "When GDM is about to create a new login process for a user it will call a privileged method of ConsoleKit in order to open a new session for this user. At this time GDM also provides ConsoleKit with information about this user session such as: the user ID, the X11 Display name that will be associated with the session, the host-name from which the session originates (useful in the case of an XDMCP session), whether or not this session is local, etc. As the entity that initiates the user process, GDM is in a unique position know and to be trusted to provide these bits of information about the user session. The use of this privileged method is restricted by the use of D-Bus system message bus security policy." msgstr "" #: C/gdm.xml:1052(para) msgid "In the case where a user with an existing session and 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 is undefined and session-specific. However, most sessions will unlock a screensaver in response." msgstr "" #: C/gdm.xml:1059(para) msgid "When the user chooses to log out, or if GDM or the session quit unexpectedly the user session will be unregistered from ConsoleKit." msgstr "" #: C/gdm.xml:1064(para) msgid "If support for ConsoleKit is not desired it can be disabled at build time using the --with-console-kit=no option when running configure." msgstr "" #: C/gdm.xml:1072(title) msgid "Using gdmsetup To Configure GDM" msgstr "" #: C/gdm.xml:1074(para) msgid "The gdmsetup application can be used to configure GDM. If you believe running root-owned GUI's causes security risk, then you would want to always edit the files by hand and not use gdmsetup. Editing the files by hand is explained in the \"Configuration\" section of this document. Note that gdmsetup does not support changing of all configuration variables, so it may be necessary to edit the files by hand for some configurations." msgstr "" #: C/gdm.xml:1085(para) msgid "The gdmsetup program has five tabs: Local, Remote, Accessibility, Security, and Users, described below. In parenthesis is information about which GDM configuration key is affected by each GUI choice. Refer to the \"Configuration\" section of this manual and the comments in the <share>/gdm/defaults.conf file for additional details about each key." msgstr "" #: C/gdm.xml:1095(title) msgid "Local Tab" msgstr "" #: C/gdm.xml:1097(para) msgid "The Local tab is used for controlling the appearance of GDM for local/static displays (non-XDMCP remote connections). The choices available in this tab depend on the setting of the \"Style\" combobox. This combobox is used to determine whether the \"Plain\" or \"Themed\" greeter GUI is used. The differences between these greeter programs are explained in the \"Overview\" section of this document." msgstr "" #: C/gdm.xml:1107(para) msgid "If the \"Style\" choice is \"Plain\", then GDM will use the gdmlogin program as the GUI (daemon/Greeter). When this choice is selected, gdmsetup allows the user to select whether the background is an image or solid color (greeter/BackgroundType). If image is selected, there is a file selection button to pick the image file (greeter/BackgroundImage) and a checkbox to scale the image to fit the screen (greeter/BackgroundImageScaleToFit). If solid color is selected, there is a button available to allow the color selection (greeter/BackgroundColor). Also, the user may select the logo image that appears in gdmlogin (greeter/Logo)." msgstr "" #: C/gdm.xml:1121(para) msgid "If the \"Style\" choice is \"Plain with face browser\", then the gdmlogin program is used as the GUI (daemon/Greeter) and the face browser is turned on (greeter/Browser). The Face Browser is explained in the Overview section. Otherwise, the choices are the same as when the \"Style\" choice is \"Plain\". Additional setup in the Users tab may be necessary to choose which users appear in the Face Browser." msgstr "" #: C/gdm.xml:1131(para) msgid "If the \"Style\" choice is \"Themed\", then the gdmgreeter program is used as the GUI (daemon/Greeter). When this choice is selected, gdmsetup allows the user to select the theme to be used (greeter/GraphicalTheme). Note that the checkbox to the left of the theme's name must be checked for a theme to be selected. Clicking on the theme, but not selecting the checkbox will highlight the theme and the \"Remove\" button can be used to delete the theme. Information about the theme's author and copyright are shown for the highlighted theme. The \"Add\" button can be used to add new themes to the system. To turn on the Face Browser, a theme which includes a Face Browser must be selected, such as happygnome-list. The \"Background color\" displayed when GDM starts (and if the theme has transparent elements) can also be selected (greeter/GraphicalThemedColor). The \"Theme\" combo box may be set to \"Random from selected\" if you want a random theme to be used for each login (greeter/GraphicalThemeRand and greeter/GraphicalThemes). To use random themes, select each theme that you wish to be used. By default this combobox is set to \"Selected only\", so that only a single theme can be selected and be used." msgstr "" #: C/gdm.xml:1155(para) msgid "Regardless of the \"Style\" choice, the user may also select whether the Actions menu is visible (greeter/SystemMenu), whether the Actions menu includes the choice to start gdmsetup (greeter/ConfigAvailable), and whether the Action menu includes the choice to start gdmchooser to run a remote XDMCP login session (greeter/ChooserButton). Note that the root password must be entered to start gdmsetup from the login screen if it is enabled. Also the Welcome message displayed for local sessions may be selected (greeter/DefaultWelcome and greeter/Welcome). The Welcome message can contain the character sequences described in the \"Text Node\" section of the \"Themed Greeter\" section of this manual." msgstr "" #: C/gdm.xml:1172(title) msgid "Remote Tab" msgstr "" #: C/gdm.xml:1174(para) msgid "The Remote tab controls the appearance of the GDM for users logging in via XDMCP. By default XDMCP is disabled, and users should be comfortable with the XDMCP-related sections of the Security section of this document before enabling it. This tab includes a \"Style\" combobox which can be used to turn on XDMCP and control the appearance of GDM for remote users (gui/RemoteGreeter and xdmcp/Enable). This combobox may be set to \"Remote login disabled\" or \"Same as Local\". If the Local tab is set to \"Plain\" or \"Plain with Face Browser\", then the user may also select \"Themed\". If the Local tab is set to \"Themed\", then the user may also select \"Plain\" or \"Plain with face browser\". It is recommended that the \"Plain\" GUI be used for remote connections since it is more lightweight and tends to have better performance across a network." msgstr "" #: C/gdm.xml:1192(para) msgid "If Remote login is enabled, then the user can specify the remote Welcome Message to be displayed (greeter/DefaultRemoteWelcome and greeter/RemoteWelcome). This welcome message is separate from the Local welcome message and can have a different value. The Welcome message can contain the character sequences described in the \"Text Node\" section of the \"Themed Greeter\" section of this manual." msgstr "" #: C/gdm.xml:1202(para) msgid "If the \"Style\" choice is \"Same as Local\" and the local selection is \"Plain\" or \"Plain with face browser\", then the user may select whether background images should be displayed for remote logins (greeter/BackgroundRemoteOnlyColor)." msgstr "" #: C/gdm.xml:1210(para) msgid "If the \"Style\" choice is enabled and set to a different value than the Local tab, then the user has the same configuration choices as found on the Local tab except that the System Menu choices are not available since this is never available for remote logins for security purposes." msgstr "" #: C/gdm.xml:1218(para) msgid "If Remote login is enabled, there is a \"Configure XDMCP\" button which displays a dialog allowing the user to set XDMCP configuration, including whether indirect requests are honored (xdmcp/HonorIndirect), UDP port (xdmcp/Port), maximum pending requests (xdmcp/MaxPending), maximum pending indirect requests (xmdcp/MaxPendingIndirect), maximum remote sessions (xdmcp/MaxSessions), maximum wait time (xdmcp/MaxWait), maximum indirect wait time (xdmcp/MaxWaitIndirect), displays per host (xdmcp/DisplaysPerHost), and ping interval (xdmcp/PingIntervalSeconds). The default settings are standard settings and should only be changed by someone who understands the ramifications of the change." msgstr "" #: C/gdm.xml:1234(title) msgid "Accessibility Tab" msgstr "" #: C/gdm.xml:1236(para) msgid "The Accessibility tab is used to turn on Accessibility features in GDM. \"Enable accessible login\" (daemon/AddGtkModules and daemon/GtkModulesList) turns on GDM's gesture listeners which are explained in the \"Accessibility\" section of this document. There is also a checkbox to allow users to change the theme when using the Plain greeter (gui/AllowGtkThemeChange). This feature allows GDM users to switch the theme to the HighContrast or LowContrast themes if needed. The user may also select whether GDM should play a sound when the login screen is ready, when login is successful and when login has failed. File chooser buttons are used to select the sound file to be played, and the \"Play\" button can be used to sample the sound." msgstr "" #: C/gdm.xml:1253(title) msgid "Security Tab" msgstr "" #: C/gdm.xml:1255(para) msgid "The Security tab allows the user to turn on Automatic and Timed login, which user is logged in via an automatic or timed login, and the timed login delay (daemon/AutomaticLoginEnable, daemon/AutomaticLogin, daemon/TimedLoginEnable, daemon/TimedLogin, and daemon/TimedLoginDelay). If automatic login is turned on, then the specified user will immediately log in on reboot without GDM asking for username/password. If the user logs out of their session, GDM will start and ask for username and password to log back in. If TimedLogin is turned on, then GDM will log in to the specified user after a specified number of seconds. The user may enable Timed Login for remote (XDMCP) connections by checking the \"Allow remote timed logins\" checkbox." msgstr "" #: C/gdm.xml:1270(para) msgid "On this tab, the user may select whether the system administrator user can log in, and whether the system administrator user can log in via remote (XDMCP) connections (security/AllowRoot and security/AllowRemoteRoot). The user may turn on GDM debug (debug/Enable) which causes debug messages to be sent to the system log. Debug should only be used when diagnosing a problem and not be left on when not needed. The \"Deny TCP connections to Xserver\" choice will disable X forwarding if selected (security/DisallowTCP). A login retry delay (security/RetryDelay) can be set to cause GDM to wait a number of seconds after a failed login." msgstr "" #: C/gdm.xml:1283(para) msgid "The \"Configure X Server\" button can be used to specify how GDM manages each display. The \"Servers\" combobox shows what server definitions are available (Standard, Terminal, and Chooser by default). Refer to the \"X Server Definitions\" section of the \"Configuration\" section for more information about how to create new Server Definitions." msgstr "" #: C/gdm.xml:1292(para) msgid "For any server type, the user may modify the \"Server Name\" (server/name), the \"Command\" (server/command) to be used to launch the Xserver, whether the server type will \"Launch\" (server/chooser) the greeter or chooser GUI after starting the Xserver, whether GDM handles this type (normally only set to false when logging into a Terminal session type), and whether the session type supports \"Flexible\" (server/flexible) sessions." msgstr "" #: C/gdm.xml:1302(para) msgid "The \"Servers To Start\" section shows what server type is displayed for each display on the machine. Users may click on the \"Add/Modify\" button to add a new display to the list or to modify a selected display. This simply corresponds each physical display with the Server Definition to be used for managing that display. The \"Remove\" button may be used to remove a display from the list." msgstr "" #: C/gdm.xml:1314(title) msgid "Users Tab" msgstr "" #: C/gdm.xml:1316(para) msgid "The Users tab controls which users appear in the Face Browser. If the \"Include all users from /etc/password\" checkbox is selected, then all users (with a userid above greeter/MinimalUID and not in the Exclude list) are displayed. If this checkbox is not selected, then users must be added to the \"Include\" list. Users in the \"Exclude\" list are never displayed. The \"Add\" and \"Remove\" buttons are used to add a new user to the list or remove a selected user from the list. The \"Apply User Changes\" button must be pressed after the \"Include\" and \"Exclude\" lists have been modified. The left and right arrow buttons between the \"Include\" and \"Exclude\" lists can be used to move a selected user from one list to the other." msgstr "" #: C/gdm.xml:1334(title) msgid "Configuration" msgstr "" #: C/gdm.xml:1336(para) msgid "GDM has powerful configuration management. System configuration is stored in <share>/gdm/defaults.conf and the intention is that this file can be stored on a shared filesystem so that sysadmins can have a single file to modify to control configuration for multiple machines. Also GDM distributions may patch this file on update to improve usability, improve security, etc. Configuration may be customized for a specific machine by editing the <etc>/gdm/custom.conf file to include an override for a specific key. Those parameters in the \"gui\", \"greeter\" sections, and the security/PamStack key may be customized per-display by specifying them in a file named <etc>/gdm/custom.conf<display num>. For example, configuration overrides for display \":103\" would be stored in the file <etc>/gdm/custom.conf:0. Per-display configuration is supported in GDM 2.14.6 and later." msgstr "" #: C/gdm.xml:1354(para) msgid "The gdmsetup is a GUI program you can use to edit the GDM configuration. This program may also be launched directly from the login screen if the greeter/ConfigAvailable key is set to \"true\" Not all keys in the GDM configuration file are supported in the GUI, so you may need to edit the configuration files by hand to edit these keys. If you believe running root-owned GUI's causes security risk, then you would want to always edit the files by hand. This program does not support setting per-display configuration, so per-display configuration files must be set up by hand." msgstr "" #: C/gdm.xml:1366(para) msgid "Distributions should edit the <share>/gdm/defaults.conf file to establish the default values so these are preserved as defaults and not modified by users modifying their personal configuration file <etc>/gdm/custom.conf." msgstr "" #: C/gdm.xml:1374(para) msgid "If you want to change configuration by hand, edit the <etc>/gdm/custom.conf file and make sure the keyname=value pair you want is included in the appropriate section. For example, to change the \"Greeter\" key in the \"daemon\" section, make sure the daemon section of the <etc>/gdm/custom.conf file has the value like in this example." msgstr "" #: C/gdm.xml:1384(screen) #, no-wrap msgid "\n[daemon]\nGreeter=/usr/lib/gdmgreeter\n" msgstr "" #: C/gdm.xml:1389(para) msgid "The configuration files (especially the <share>/gdm/defaults.conf and <etc>/gdm/custom.conf files) contain useful comments and examples, so read them for more information about changing your configuration. GDM considers lines that start with the \"#\" character a comment, and these lines will be ignored by GDM. Some keys in the <share>/gdm/defaults.conf are commented out while others are set. Commented out values show the default value." msgstr "" #: C/gdm.xml:1401(para) msgid "The <share>/gdm/defaults.conf file contains the default configuration choices for GDM, and should not be modified by the user. The <etc>/gdm/custom.conf file is where users may specify their custom configuration choices. Configuration options specified in the <etc>/gdm/custom.conf file override the values in the main <share>/gdm/defaults.conf file. Running the gdmsetup command will cause the <etc>/gdm/custom.conf to be modified with the user's configuration choices and will cause any running GDM GUI programs to automatically update. Previous to version 2.13.0.4 GDM only supported the <etc>/gdm/gdm.conf file, so if using an older version of GDM just edit that file directly." msgstr "" #: C/gdm.xml:1417(para) msgid "The location of the configuration files may be controlled via the --with-defaults-conf and --with-custom-conf configuration options. The GDM daemon --config option may also be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used." msgstr "" #: C/gdm.xml:1426(para) msgid "<share>/gdm/factory-defaults.conf is the configuration file as shipped with the daemon. This can be useful for to see if the <share>/gdm/defaults.conf file has been changed." msgstr "" #: C/gdm.xml:1433(para) msgid "The other GDM configuration files are located, by default, in the <etc>/gdm/ folder or its subdirectories. However, the location of all configuration files are defined in the GDM configuration files, so the sysadmin may choose to locate these files in any location." msgstr "" #: C/gdm.xml:1441(para) msgid "This is a listing of the config directory contents:" msgstr "" #: C/gdm.xml:1445(screen) #, no-wrap msgid "\nlocale.alias\nXsession\nXKeepsCrashing\nmodules/\nInit/\nPostLogin/\nPreSession/\nPostSession/\n" msgstr "" #: C/gdm.xml:1456(para) msgid "locale.alias is a file which looks much like the system locale alias but in fact it is not the same. These are the languages that are available on your system. All the languages are still tested to see if they actually exist before presenting them to the user." msgstr "" #: C/gdm.xml:1464(para) msgid "Xsession is a script which sets up a user session and then executes the user's choice of session. Note that the session script is typically started via the desktop file associated with the session the user has picked. Some sessions may start the user's session via a different mechanism than the Xsession script, so please check the appropriate desktop before assuming a session startup issue is being caused by this file." msgstr "" #: C/gdm.xml:1475(para) msgid "XKeepsCrashing is a script which gets run when the X server keeps crashing and we cannot recover. The shipped default script will work with most Linux distributions and can run the X configuration application provided the person on the console knows the root password." msgstr "" #: C/gdm.xml:1483(para) msgid "Accessibility modules are configured in the modules/ subdirectory, and are a separate topic. Read the default files provided, they have adequate documentation. Again normally the default install is given in the files with factory in their name, and those files are not read, they are just there for you so you can always revert to default config." msgstr "" #: C/gdm.xml:1492(para) msgid "Files describing available GDM session follow the freedesktop.org desktop file specification and are .desktop-style files are installed to <etc>/X11/sessions/. This directory is also read by the KDE desktop manager (KDM) for common configuration. Next the directory <share>/gdm/BuiltInSessions/ is read for GDM specific built-in sessions (KDM hardcodes these at time of this writing). Lastly the default setup will also read <share>/xsessions/ (which should be <share>/xsessions/ if you really wish to cooperate with KDM) where desktop packages can install their session files. The directories under the <etc> should be reserved for configuration. The desktop file specification approach makes it easy for package management systems to install window managers and different session types without requiring the sysadmin to edit files. See the SessionDesktopDir configuration key for changing the paths. It used to be that GDM stored its built in sessions in <etc>/dm/Sessions/ but this is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the <etc>/dm/Sessions/ was being read." msgstr "" #: C/gdm.xml:1515(para) msgid "A session can be disabled (if it was installed in <share>/xsessions/) by adding an identically named .desktop to one of the directories earlier in the path (likely <etc>/X11/sessions) and using Hidden=true in that file." msgstr "" #: C/gdm.xml:1524(title) msgid "The Script Directories" msgstr "" #: C/gdm.xml:1526(para) msgid "In this section we will explain the Init, PostLogin, PreSession and PostSession directories as they are very similar." msgstr "" #: C/gdm.xml:1532(para) msgid "When the X server has been successfully started, GDM will try to run the script called Init/<displayname>. I.e. Init/:0 for the first local display. If this file is not found, GDM will attempt to to run Init/<hostname>. I.e. Init/somehost. If this still is not found, GDM will try Init/XDMCP for all XDMCP logins or Init/Flexi for all on demand flexible displays. If none of the above were found, GDM will run Init/Default. The script will be run as root and GDM blocks until it terminates. Use the Init/* script for applications that are supposed to run alongside with the GDM login window. xconsole for instance. Commands to set the background etc. go in this file too." msgstr "" #: C/gdm.xml:1550(para) msgid "It is up to the sysadmin to decide whether clients started by the Init script should be killed before starting the user session. This is controlled with the KillInitClients configuration option." msgstr "" #: C/gdm.xml:1557(para) msgid "When the user has been successfully authenticated GDM tries the scripts in the PostLogin directory in the same manner as for the Init directory. This is done before any session setup is done, and so this would be the script where you might setup the home directory if you need to (though you should use the pam_mount module if you can for this). You have the $USER and $DISPLAY environment variables set for this script, and again it is run as root. The script should return 0 on success as otherwise the user won't be logged in. This is not true for failsafe session however." msgstr "" #: C/gdm.xml:1571(para) msgid "After the user session has been setup from the GDM side of things, GDM will run the scripts in the PreSession directory, again in the same manner as the Init directory. Use this script for local session management or accounting stuff. The $USER environment variable contains the login of the authenticated user and $DISPLAY is set to the current display. The script should return 0 on success. Any other value will cause GDM to terminate the current login process. This is not true for failsafe sessions however. Also $X_SERVERS environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." msgstr "" #: C/gdm.xml:1586(para) msgid "After this the base Xsession script is run with the selected session executable as the first argument. This is run as the user, and really this is the user session. The available session executables are taken from the Exec= line in the .desktop files in the path specified by SessionDesktopDir. Usually this path is <etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/xsessions/. The first found file is used. The user either picks from these sessions or GDM will look inside the file ~/.dmrc for the stored preference." msgstr "" #: C/gdm.xml:1599(para) msgid "This script should really load the user's profile and generally do all the voodoo that is needed to launch a session. Since many systems reset the language selections done by GDM, GDM will also set the $GDM_LANG variable to the selected language. You can use this to reset the language environmental variables after you run the user's profile. If the user elected to use the system language, then $GDM_LANG is not set." msgstr "" #: C/gdm.xml:1609(para) msgid "When the user terminates his session, the PostSession script will be run. Again operation is similar to Init, PostLogin and PreSession. Again the script will be run with root privileges, the slave daemon will block and the $USER environment variable will contain the name of the user who just logged out and $DISPLAY will be set to the display the user used, however note that the X server for this display may already be dead and so you shouldn't try to access it. Also $X_SERVERS environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." msgstr "" #: C/gdm.xml:1624(para) msgid "Note that the PostSession script will be run even when the display fails to respond due to an I/O error or similar. Thus, there is no guarantee that X applications will work during script execution." msgstr "" #: C/gdm.xml:1631(para) msgid "Except for the Xsession script all of these scripts will also have the environment variable $RUNNING_UNDER_GDM set to yes, so that you could perhaps use similar scripts for different display managers. The Xsession will always have the $GDMSESSION set to the basename of the session that the user chose to run without the .desktop extension. In addition $DESKTOP_SESSION is also set to the same value and in fact this will also be set by KDM in future versions." msgstr "" #: C/gdm.xml:1645(para) msgid "Neither of the Init, PostLogin, PreSession or PostSession scripts are necessary and can be left out. The Xsession script is however required as well as at least one session .desktop file." msgstr "" #: C/gdm.xml:1655(title) msgid "The Configuration Files - defaults.conf and custom.conf" msgstr "" #: C/gdm.xml:1658(para) msgid "GDM uses two configuration files: <share>/gdm/defaults.conf and <etc>/gdm/custom.conf. The <share>/gdm/defaults.conf file contains the default configuration choices for GDM, and should not be modified by the user. The <etc>/gdm/custom.conf file is where users may specify their custom configuration choices. Configuration options specified in the <etc>/gdm/custom.conf file override the values in the <share>/gdm/defaults.conf file. If a configuration option is not defined in either file, GDM will default to the value described in the comments in the <share>/gdm/defaults.conf file." msgstr "" #: C/gdm.xml:1674(para) msgid "Running the gdmsetup command will cause the <etc>/gdm/custom.conf to be modified with the user's configuration choices." msgstr "" #: C/gdm.xml:1680(para) msgid "Previous to GDM 2.13.0.4 only the <etc>/gdm/gdm.conf existed. If upgrading to the new version of GDM, install will check to see if your <etc>/gdm/gdm.conf file is different than your <etc>/gdm/factory-gdm.conf file. If so, your <etc>/gdm/gdm.conf file will be automatically copied to <etc>/gdm/custom.conf to preserve any configuration changes." msgstr "" #: C/gdm.xml:1692(para) msgid "The location of the configuration files may be controlled via the --with-defaults-conf and --with-custom-conf configuration options. The GDM daemon --config option may instead be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used." msgstr "" #: C/gdm.xml:1701(para) msgid "Both configuration files are divided into sections each containing variables that define the behavior for a specific part of the GDM suite. Refer to the comments in the <share>/gdm/defaults.conf file for additional information about each configuration setting." msgstr "" #: C/gdm.xml:1709(para) msgid "The <share>/gdm/defaults.conf and <etc>/gdm/custom.conf files follow the standard .ini style configuration file syntax. Keywords in brackets define sections, strings before an equal sign (=) are variables and the data after equal sign represents their value. Empty lines or lines starting with the hash mark (#) are ignored. The graphical configurator will try to preserve both comments (lines with a hash mark) and the overall structure of the file so you can intermix using the GUI or hand editing the configuration file." msgstr "" #: C/gdm.xml:1722(title) msgid "Daemon Configuration" msgstr "" #: C/gdm.xml:1725(title) msgid "[daemon]" msgstr "" #: C/gdm.xml:1728(term) msgid "AddGtkModules" msgstr "" #: C/gdm.xml:1730(synopsis) #, no-wrap msgid "AddGtkModules=false" msgstr "" #: C/gdm.xml:1731(para) msgid "If true, then enables gdmgreeter or gdmlogin to be launched with additional Gtk+ modules. This is useful when extra features are required such as accessible login. Note that only \"trusted\" modules should be used to minimize security issues." msgstr "" #: C/gdm.xml:1738(para) msgid "If true, then the registry daemon at-spi-registryd will be launched by gdmgreeter or gdmlogin starting with version GDM 2.17." msgstr "" #: C/gdm.xml:1744(para) msgid "Usually this is used for accessibility modules. The modules which are loaded are specified with the GtkModulesList key." msgstr "" #: C/gdm.xml:1753(term) msgid "AlwaysRestartServer" msgstr "" #: C/gdm.xml:1755(synopsis) #, no-wrap msgid "AlwaysRestartServer=false" msgstr "" #: C/gdm.xml:1756(para) msgid "If true, then gdm never tries to reuse existing X servers by reinitializing them. It will just kill the existing X server and start over. Normally, just reinitializing is a nicer way to go but if the X server memory usage keeps growing this may be a safer option. On Solaris, this value is always true, and this configuration setting is ignored." msgstr "" #: C/gdm.xml:1768(term) msgid "AlwaysLoginCurrentSession" msgstr "" #: C/gdm.xml:1770(synopsis) #, no-wrap msgid "AlwaysLoginCurrentSession=true" msgstr "" #: C/gdm.xml:1771(para) msgid "If true, then when the user logs in and already has an existing session, then they are connected to that session rather than starting a new session. This only works for sessions running on VTs (Virtual Terminals) started with gdmflexiserver, and not with XDMCP. Note that VTs are not supported on all operating systems." msgstr "" #: C/gdm.xml:1783(term) msgid "AutomaticLoginEnable" msgstr "" #: C/gdm.xml:1785(synopsis) #, no-wrap msgid "AutomaticLoginEnable=false" msgstr "" #: C/gdm.xml:1786(para) msgid "If the user given in AutomaticLogin should be logged in upon first bootup. No password will be asked. This is useful for single user workstations where local console security is not an issue. Also could be useful for public terminals, although there see TimedLogin." msgstr "" #: C/gdm.xml:1797(term) msgid "AutomaticLogin" msgstr "" #: C/gdm.xml:1799(synopsis) #, no-wrap msgid "AutomaticLogin=" msgstr "" #: C/gdm.xml:1800(para) msgid "This user should be automatically logged in on first bootup. AutomaticLoginEnable must be true and this must be a valid user for this to happen. \"root\" can never be autologged in however and gdm will just refuse to do it even if you set it up." msgstr "" #: C/gdm.xml:1808(para) msgid "The following control chars are recognized within the specified name:" msgstr "" #: C/gdm.xml:1813(para) C/gdm.xml:3821(para) msgid "%%— the `%' character" msgstr "" #: C/gdm.xml:1817(para) msgid "%d — display's name" msgstr "" #: C/gdm.xml:1821(para) msgid "%h — display's hostname" msgstr "" #: C/gdm.xml:1825(para) msgid "Alternatively, the name may end with a vertical bar |, the pipe symbol. The name is then used as a application to execute which returns the desired username on standard output. If an empty or otherwise invalid username is returned, automatic login is not performed. This feature is typically used when several remote displays are used as internet kiosks, with a specific user to automatically login for each display." msgstr "" #: C/gdm.xml:1838(term) msgid "BaseXsession" msgstr "" #: C/gdm.xml:1840(synopsis) #, no-wrap msgid "BaseXsession=<etc>/gdm/Xsession" msgstr "" #: C/gdm.xml:1841(para) msgid "This is the base X session file. When a user logs in, this script will be run with the selected session as the first argument. The selected session will be the Exec= from the .desktop file of the session." msgstr "" #: C/gdm.xml:1849(para) msgid "If you wish to use the same script for several different display managers, and wish to have some of the script run only for GDM, then you can check the presence of the GDMSESSION environmental variable. This will always be set to the basename of .desktop (without the extension) file that is being used for this session, and will only be set for GDM sessions. Previously some scripts were checking for GDM_LANG, but that is only set when the user picks a non-system default language." msgstr "" #: C/gdm.xml:1862(para) msgid "This script should take care of doing the \"login\" for the user and so it should source the <etc>/profile and friends. The standard script shipped with GDM sources the files in this order: <etc>/profile then ~/.profile then <etc>/xprofile and finally ~/.xprofile. Note that different distributions may change this however. Sometimes users personal setup will be in ~/.bash_profile, however broken that is." msgstr "" #: C/gdm.xml:1879(term) msgid "Chooser" msgstr "" #: C/gdm.xml:1881(synopsis) #, no-wrap msgid "Chooser=<bin>/gdmchooser" msgstr "" #: C/gdm.xml:1882(para) msgid "Full path and name of the chooser executable followed by optional arguments." msgstr "" #: C/gdm.xml:1890(term) msgid "Configurator" msgstr "" #: C/gdm.xml:1892(synopsis) #, no-wrap msgid "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" msgstr "" #: C/gdm.xml:1893(para) msgid "The pathname to the configurator binary. If the greeter ConfigAvailable option is set to true then run this binary when somebody chooses Configuration from the Actions menu. Of course GDM will first ask for root password however. And it will never allow this to happen from a remote display." msgstr "" #: C/gdm.xml:1905(term) msgid "ConsoleCannotHandle" msgstr "" #: C/gdm.xml:1907(synopsis) #, no-wrap msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" msgstr "" #: C/gdm.xml:1908(para) msgid "These are the languages that the console cannot handle because of font issues. Here we mean the text console, not X. This is only used when there are errors to report and we cannot start X." msgstr "" #: C/gdm.xml:1918(term) msgid "ConsoleNotify" msgstr "" #: C/gdm.xml:1920(synopsis) #, no-wrap msgid "ConsoleNotify=true" msgstr "" #: C/gdm.xml:1921(para) msgid "If false, gdm will not display a message dialog on the console when an error happens." msgstr "" #: C/gdm.xml:1929(term) msgid "DefaultPath" msgstr "" #: C/gdm.xml:1931(synopsis) #, no-wrap msgid "DefaultPath=defaultpath (value set by configure)" msgstr "" #: C/gdm.xml:1932(para) msgid "Specifies the path which will be set in the user's session. This value will be overridden with the value from /etc/default/login if it contains \"ROOT=<pathname>\". If the /etc/default/login file exists, but contains no value for ROOT, the value as defined in the GDM configuration will be be used." msgstr "" #: C/gdm.xml:1945(term) msgid "DefaultSession" msgstr "" #: C/gdm.xml:1947(synopsis) #, no-wrap msgid "DefaultSession=gnome.desktop" msgstr "" #: C/gdm.xml:1948(para) msgid "The session that is used by default if the user does not have a saved preference and has picked 'Last' from the list of sessions. Note that 'Last' need not be displayed, see the ShowLastSession key." msgstr "" #: C/gdm.xml:1959(term) msgid "DisplayInitDir" msgstr "" #: C/gdm.xml:1961(synopsis) #, no-wrap msgid "DisplayInitDir=<etc>/gdm/Init" msgstr "" #: C/gdm.xml:1962(para) msgid "Directory containing the display init scripts. See the ``The Script Directories'' section for more info." msgstr "" #: C/gdm.xml:1970(term) msgid "DisplayLastLogin" msgstr "" #: C/gdm.xml:1972(synopsis) #, no-wrap msgid "DisplayLastLogin=true" msgstr "" #: C/gdm.xml:1973(para) msgid "If true then the last login information is printed to the user before being prompted for password. While this gives away some info on what users are on a system, it on the other hand should give the user an idea of when they logged in and if it doesn't seem kosher to them, they can just abort the login and contact the sysadmin (avoids running malicious startup scripts). This was added in version 2.5.90.0." msgstr "" #: C/gdm.xml:1982(para) msgid "This is for making GDM conformant to CSC-STD-002-85, although that is purely theoretical now. Someone should read that spec and ensure that this actually conforms (in addition to other places in GDM). See http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html for more info." msgstr "" #: C/gdm.xml:1994(term) msgid "DoubleLoginWarning" msgstr "" #: C/gdm.xml:1996(synopsis) #, no-wrap msgid "DoubleLoginWarning=true" msgstr "" #: C/gdm.xml:1997(para) msgid "If true, GDM will warn the user if they are already logged in on another virtual terminal. On systems where GDM supports checking the X virtual terminals, GDM will let the user switch to the previous login virtual terminal instead of logging in." msgstr "" #: C/gdm.xml:2007(term) msgid "DynamicXServers" msgstr "" #: C/gdm.xml:2009(synopsis) #, no-wrap msgid "DynamicXServers=false" msgstr "" #: C/gdm.xml:2010(para) msgid "If true, the GDM daemon will honor requests to manage displays via the /tmp/.gdm_socket socket connection. Displays can be created, started, and deleted with the appropriate commands. The gdmdynamic command is a convenient method to send these messages." msgstr "" #: C/gdm.xml:2022(term) msgid "FailsafeXServer" msgstr "" #: C/gdm.xml:2024(synopsis) #, no-wrap msgid "FailsafeXServer=" msgstr "" #: C/gdm.xml:2025(para) msgid "An X command line in case we can't start the normal X server. should probably be some sort of a script that runs an appropriate low resolution X server that will just work. This is tried before the XKeepsCrashing script is run." msgstr "" #: C/gdm.xml:2036(term) msgid "FirstVT" msgstr "" #: C/gdm.xml:2038(synopsis) #, no-wrap msgid "FirstVT=7" msgstr "" #: C/gdm.xml:2039(para) msgid "On systems where GDM supports automatic VT (virtual terminal) allocation, this is the first vt to try. Usually standard text logins are run on the lower vts. See also VTAllocation." msgstr "" #: C/gdm.xml:2049(term) msgid "FlexibleXServers" msgstr "" #: C/gdm.xml:2051(synopsis) #, no-wrap msgid "FlexibleXServers=5" msgstr "" #: C/gdm.xml:2052(para) msgid "The maximum number of allowed flexible displays. These are displays that can be run using the /tmp/.gdm_socket socket connection. This is used for both full flexible displays and for Xnest displays." msgstr "" #: C/gdm.xml:2063(term) msgid "FlexiReapDelayMinutes" msgstr "" #: C/gdm.xml:2065(synopsis) #, no-wrap msgid "FlexiReapDelayMinutes=5" msgstr "" #: C/gdm.xml:2066(para) msgid "After how many minutes of inactivity at the login screen should a flexi display be reaped. This is only in effect before a user logs in. Also it does not affect the Xnest flexiservers. To turn off this behavior set this value to 0. This was added in version 2.5.90.0." msgstr "" #: C/gdm.xml:2077(term) msgid "Greeter" msgstr "" #: C/gdm.xml:2079(synopsis) #, no-wrap msgid "Greeter=<bin>/gdmlogin" msgstr "" #: C/gdm.xml:2080(para) msgid "Full path and name of the greeter executable followed by optional arguments. This is the greeter used for all displays except for the XDMCP remote displays. See also RemoteGreeter" msgstr "" #: C/gdm.xml:2090(term) msgid "Group" msgstr "" #: C/gdm.xml:2092(synopsis) #, no-wrap msgid "Group=gdm" msgstr "" #: C/gdm.xml:2093(para) msgid "The group name under which gdmlogin, gdmgreeter, gdmchooser and the internal failsafe GTK+ dialogs are run. Also see User. This user will have access to all the X authorization files, and perhaps to other internal GDM data and it should not therefore be a user such as nobody, but rather a dedicated user. The ServAuthDir is owned by this group. The ownership and permissions of ServAuthDir should be root.gdm and 1770." msgstr "" #: C/gdm.xml:2110(term) msgid "GtkModulesList" msgstr "" #: C/gdm.xml:2112(synopsis) #, no-wrap msgid "GtkModulesList=module-1:module-2:..." msgstr "" #: C/gdm.xml:2113(para) msgid "A colon separated list of Gtk+ modules that gdmgreeter or gdmlogin will be invoked with if AddGtkModules is true. The format is the same as the standard Gtk+ module interface." msgstr "" #: C/gdm.xml:2124(term) msgid "HaltCommand" msgstr "" #: C/gdm.xml:2126(synopsis) #, no-wrap msgid "HaltCommand=<sbin>/shutdown -h now" msgstr "" #: C/gdm.xml:2127(para) msgid "Full path and arguments to command to be executed when user selects \"Shut Down\" from the Actions menu. This can be a ';' separated list of commands to try. If a value is missing, the shut down command is not available. Note that the default for this value is not empty, so to disable \"Shut Down\" it must be set to an empty value." msgstr "" #: C/gdm.xml:2140(term) msgid "KillInitClients" msgstr "" #: C/gdm.xml:2142(synopsis) #, no-wrap msgid "KillInitClients=true" msgstr "" #: C/gdm.xml:2143(para) msgid "Determines whether GDM should kill X clients started by the init scripts when the user logs in." msgstr "" #: C/gdm.xml:2151(term) msgid "LogDir" msgstr "" #: C/gdm.xml:2153(synopsis) #, no-wrap msgid "LogDir=<var>/log/gdm" msgstr "" #: C/gdm.xml:2154(para) msgid "Directory containing the log files for the individual displays. By default this is the same as the ServAuthDir." msgstr "" #: C/gdm.xml:2162(term) msgid "PidFile" msgstr "" #: C/gdm.xml:2164(synopsis) #, no-wrap msgid "PidFile=<var>/run/gdm.pid" msgstr "" #: C/gdm.xml:2165(para) msgid "Name of the file containing the gdm process id." msgstr "" #: C/gdm.xml:2173(term) msgid "PreFetchProgram" msgstr "" #: C/gdm.xml:2175(synopsis) #, no-wrap msgid "PreFetchProgram=command" msgstr "" #: C/gdm.xml:2176(para) msgid "Program to be run by the GDM greeter/login program when the initial screen is displayed. The purpose is to provide a hook where files which will be used after login can be preloaded to speed performance for the user. The program will be called once only, the first time a greeter is displayed. The gdmprefetch command may be used. This utility will load any libraries passed in on the command line, or if the argument starts with a \"@\" character, it will process the file assuming it is an ASCII file containing a list of libraries, one per line, and load each library in the file." msgstr "" #: C/gdm.xml:2192(term) msgid "PostLoginScriptDir" msgstr "" #: C/gdm.xml:2194(synopsis) #, no-wrap msgid "PostLoginScriptDir=<etc>/gdm/PostLogin" msgstr "" #: C/gdm.xml:2195(para) msgid "Directory containing the scripts run right after the user logs in, but before any session setup is done. See the ``The Script Directories'' section for more info." msgstr "" #: C/gdm.xml:2204(term) msgid "PostSessionScriptDir" msgstr "" #: C/gdm.xml:2206(synopsis) #, no-wrap msgid "PostSessionScriptDir=<etc>/gdm/PostSession" msgstr "" #: C/gdm.xml:2207(para) msgid "Directory containing the scripts run after the user logs out. See the ``The Script Directories'' section for more info." msgstr "" #: C/gdm.xml:2215(term) msgid "PreSessionScriptDir" msgstr "" #: C/gdm.xml:2217(synopsis) #, no-wrap msgid "PreSessionScriptDir=<etc>/gdm/PreSession" msgstr "" #: C/gdm.xml:2218(para) msgid "Directory containing the scripts run before the user logs in. See the ``The Script Directories'' section for more info." msgstr "" #: C/gdm.xml:2226(term) msgid "RebootCommand" msgstr "" #: C/gdm.xml:2228(synopsis) #, no-wrap msgid "RebootCommand=<sbin>/shutdown -r now" msgstr "" #: C/gdm.xml:2229(para) msgid "Full path and optional arguments to the command to be executed when user selects Restart from the Actions menu. This can be a ';' separated list of commands to try. If missing, the restart command is not available. Note that the default for this value is not empty so to disable restart you must set this explicitly to an empty value." msgstr "" #: C/gdm.xml:2241(term) msgid "RemoteGreeter" msgstr "" #: C/gdm.xml:2243(synopsis) #, no-wrap msgid "RemoteGreeter=<bin>/gdmlogin" msgstr "" #: C/gdm.xml:2244(para) msgid "Full path and name of the greeter executable followed by optional arguments. This is used for all remote XDMCP sessions. It is useful to have the less graphically demanding greeter here if you use the Themed Greeter for your main greeter. See also the Greeter key." msgstr "" #: C/gdm.xml:2255(term) msgid "RootPath" msgstr "" #: C/gdm.xml:2257(synopsis) #, no-wrap msgid "RootPath=defaultpath (value set by configure)" msgstr "" #: C/gdm.xml:2258(para) msgid "Specifies the path which will be set in the root's session and the {Init,PostLogin,PreSession,PostSession} scripts executed by GDM. This value will be overridden with the value from /etc/default/login if it contains \"SUROOT=<pathname>\". If the /etc/default/login file exists, but contains no value for SUROOT, the value as defined in the GDM configuration will be used." msgstr "" #: C/gdm.xml:2272(term) msgid "ServAuthDir" msgstr "" #: C/gdm.xml:2274(synopsis) #, no-wrap msgid "ServAuthDir=<var>/gdm" msgstr "" #: C/gdm.xml:2275(para) msgid "Directory containing the X authentication files for the individual displays. Should be owned by root.gdm with permissions 1770, where gdm is the GDM group as defined by the Group option. That is should be owned by root, with gdm group having full write permissions and the directory should be sticky and others should have no permission to the directory. This way the GDM user can't remove files owned by root in that directory, while still being able to write its own files there. GDM will attempt to change permissions for you when it's first run if the permissions are not the above. This directory is also used for other private files that the daemon needs to store. Other users should not have any way to get into this directory and read/change it's contents. Anybody who can read this directory can connect to any display on this computer." msgstr "" #: C/gdm.xml:2297(term) msgid "SessionDesktopDir" msgstr "" #: C/gdm.xml:2299(synopsis) #, no-wrap msgid "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" msgstr "" #: C/gdm.xml:2300(para) msgid "Directory containing the .desktop files which are the available sessions on the system. Since 2.4.4.2 this is treated like a PATH type variable and the first file found is used." msgstr "" #: C/gdm.xml:2310(term) msgid "SoundProgram" msgstr "" #: C/gdm.xml:2312(filename) msgid "<bin>/play" msgstr "" #: C/gdm.xml:2312(filename) msgid "<bin>/audioplay" msgstr "" #: C/gdm.xml:2312(synopsis) #, no-wrap msgid "SoundProgram= (or on Solaris)" msgstr "" #: C/gdm.xml:2313(para) msgid "Application to use when playing a sound. Currently used for playing the login sound, see the SoundOnLoginFile key. Supported since 2.5.90.0." msgstr "" #: C/gdm.xml:2323(term) msgid "StandardXServer" msgstr "" #: C/gdm.xml:2325(synopsis) #, no-wrap msgid "StandardXServer=/dir/to/X (value assigned by configuration file)" msgstr "" #: C/gdm.xml:2326(para) msgid "Full path and arguments to the standard X server command. This is used when gdm cannot find any other definition, and it's used as the default and failsafe fallback in a number of places. This should be able to run some sort of X server." msgstr "" #: C/gdm.xml:2337(term) msgid "SuspendCommand" msgstr "" #: C/gdm.xml:2339(synopsis) #, no-wrap msgid "SuspendCommand=" msgstr "" #: C/gdm.xml:2340(para) msgid "Full path and arguments to command to be executed when user selects Suspend from the Actions menu. If empty there is no such menu item. Note that the default for this value is not empty so to disable suspend you must set this explicitly to an empty value." msgstr "" #: C/gdm.xml:2351(term) msgid "TimedLoginEnable" msgstr "" #: C/gdm.xml:2353(synopsis) #, no-wrap msgid "TimedLoginEnable=false" msgstr "" #: C/gdm.xml:2354(para) msgid "If the user given in TimedLogin should be logged in after a number of seconds (set with TimedLoginDelay) of inactivity on the login screen. This is useful for public access terminals or perhaps even home use. If the user uses the keyboard or browses the menus, the timeout will be reset to TimedLoginDelay or 30 seconds, whichever is higher. If the user does not enter a username but just hits the ENTER key while the login program is requesting the username, then GDM will assume the user wants to login immediately as the timed user. Note that no password will be asked for this user so you should be careful, although if using PAM it can be configured to require password entry before allowing login." msgstr "" #: C/gdm.xml:2374(term) msgid "TimedLogin" msgstr "" #: C/gdm.xml:2376(synopsis) #, no-wrap msgid "TimedLogin=" msgstr "" #: C/gdm.xml:2377(para) msgid "This is the user that should be logged in after a specified number of seconds of inactivity. This can never be \"root\" and gdm will refuse to log in root this way. The same features as for AutomaticLogin are supported. The same control chars and piping to a application are supported." msgstr "" #: C/gdm.xml:2389(term) msgid "TimedLoginDelay" msgstr "" #: C/gdm.xml:2391(synopsis) #, no-wrap msgid "TimedLoginDelay=30" msgstr "" #: C/gdm.xml:2392(para) msgid "Delay in seconds before the TimedLogin user will be logged in. It must be greater then or equal to 10." msgstr "" #: C/gdm.xml:2400(term) msgid "User" msgstr "" #: C/gdm.xml:2402(synopsis) #, no-wrap msgid "User=gdm" msgstr "" #: C/gdm.xml:2403(para) msgid "The username under which gdmlogin, gdmgreeter, gdmchooser and the internal failsafe GTK+ dialogs are run. Also see Group. This user will have access to all the X authorization files, and perhaps to other internal GDM data and it should not therefore be a user such as nobody, but rather a dedicated user." msgstr "" #: C/gdm.xml:2417(term) msgid "UserAuthDir" msgstr "" #: C/gdm.xml:2419(synopsis) #, no-wrap msgid "UserAuthDir=" msgstr "" #: C/gdm.xml:2420(para) msgid "The directory where user's .Xauthority file should be saved. When nothing is specified the user's home directory is used. This is tilde expanded so you can set it to things like: ~/authdir/." msgstr "" #: C/gdm.xml:2427(para) msgid "If you do not use the tilde expansion, then the filename created will be random, like in UserAuthFBDir. This way many users can have the same authentication directory. For example you might want to set this to /tmp when user has the home directory on NFS, since you really don't want cookie files to go over the wire. The users should really have write privileges to this directory, and this directory should really be sticky and all that, just like the /tmp directory." msgstr "" #: C/gdm.xml:2440(para) msgid "Normally if this is the user's home directory GDM will still refuse to put cookies there if it thinks it is NFS (by testing root-squashing). This can be changed by setting NeverPlaceCookiesOnNFS in the [security] section to false." msgstr "" #: C/gdm.xml:2451(term) msgid "UserAuthFBDir" msgstr "" #: C/gdm.xml:2453(synopsis) #, no-wrap msgid "UserAuthFBDir=/tmp" msgstr "" #: C/gdm.xml:2454(para) msgid "If GDM fails to update the user's .Xauthority file a fallback cookie is created in this directory." msgstr "" #: C/gdm.xml:2463(term) msgid "UserAuthFile" msgstr "" #: C/gdm.xml:2465(synopsis) #, no-wrap msgid "UserAuthFile=.Xauthority" msgstr "" #: C/gdm.xml:2466(para) msgid "Name of the file used for storing user cookies." msgstr "" #: C/gdm.xml:2473(term) msgid "VTAllocation" msgstr "" #: C/gdm.xml:2475(synopsis) #, no-wrap msgid "VTAllocation=true" msgstr "" #: C/gdm.xml:2476(para) msgid "On systems where GDM supports automatic VT (virtual terminal) allocation (currently Linux and FreeBSD only), you can have GDM automatically append the vt argument to the X server executable. This way races that come up from each X server managing it's own vt allocation can be avoided. See also FirstVT." msgstr "" #: C/gdm.xml:2488(term) msgid "XKeepsCrashing" msgstr "" #: C/gdm.xml:2490(synopsis) #, no-wrap msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" msgstr "" #: C/gdm.xml:2491(para) msgid "A script to run in case X keeps crashing. This is for running An X configuration or whatever else to make the X configuration work. See the script that came with the distribution for an example. The distributed XKeepsCrashing script is tested on Red Hat, but may work elsewhere. Your system integrator should make sure this script is up to date for your particular system." msgstr "" #: C/gdm.xml:2500(para) msgid "In case FailsafeXServer is setup, that will be tried first. and this only used as a backup if even that X server keeps crashing." msgstr "" #: C/gdm.xml:2509(term) msgid "Xnest" msgstr "" #: C/gdm.xml:2511(synopsis) #, no-wrap msgid "Xnest=<bin>/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)" msgstr "" #: C/gdm.xml:2512(para) msgid "The full path and arguments to the Xnest command. This is used for the flexible Xnest displays. This way the user can start new login screens in a nested window. Of course you must have the Xnest display from your X server packages installed for this to work." msgstr "" #: C/gdm.xml:2525(title) msgid "Security Options" msgstr "" #: C/gdm.xml:2528(title) msgid "[security]" msgstr "" #: C/gdm.xml:2531(term) msgid "AllowRoot" msgstr "" #: C/gdm.xml:2533(synopsis) #, no-wrap msgid "AllowRoot=true" msgstr "" #: C/gdm.xml:2534(para) msgid "Allow root (privileged user) to log in through GDM. Set this to false if you want to disallow such logins." msgstr "" #: C/gdm.xml:2538(para) msgid "On systems that support PAM, this parameter is not as useful as you can use PAM to do the same thing, and in fact do even more. However it is still followed, so you should probably leave it true for PAM systems." msgstr "" #: C/gdm.xml:2548(term) msgid "AllowRemoteRoot" msgstr "" #: C/gdm.xml:2550(synopsis) #, no-wrap msgid "AllowRemoteRoot=false" msgstr "" #: C/gdm.xml:2551(para) msgid "Allow root (privileged user) to log in remotely through GDM. This value should be set to true to allow such logins. Remote logins are any logins that come in through the XDMCP." msgstr "" #: C/gdm.xml:2556(para) msgid "On systems that support PAM, this parameter is not as useful since you can use PAM to do the same thing, and do even more." msgstr "" #: C/gdm.xml:2561(para) msgid "This value will be overridden and set to false if the /etc/default/login file exists and contains \"CONSOLE=/dev/login\", and set to true if the /etc/default/login file exists and contains any other value or no value for CONSOLE." msgstr "" #: C/gdm.xml:2572(term) msgid "AllowRemoteAutoLogin" msgstr "" #: C/gdm.xml:2574(synopsis) #, no-wrap msgid "AllowRemoteAutoLogin=false" msgstr "" #: C/gdm.xml:2575(para) msgid "Allow the timed login to work remotely. That is, remote connections through XDMCP will be allowed to log into the \"TimedLogin\" user by letting the login window time out, just like the local user on the first console." msgstr "" #: C/gdm.xml:2581(para) msgid "Note that this can make a system quite insecure, and thus is off by default." msgstr "" #: C/gdm.xml:2589(term) msgid "CheckDirOwner" msgstr "" #: C/gdm.xml:2591(synopsis) #, no-wrap msgid "CheckDirOwner=true" msgstr "" #: C/gdm.xml:2592(para) msgid "By default GDM checks the ownership of the home directories before writing to them, this prevents security issues in case of bad setup. However in some instances home directories will be owned by a different user and in this case it is necessary to turn this option on. You will also most likely have to turn the RelaxPermissions key to at least value 1 since in such a scenario home directories are likely to be group writable. Supported since 2.6.0.4." msgstr "" #: C/gdm.xml:2606(term) msgid "SupportAutomount" msgstr "" #: C/gdm.xml:2608(synopsis) #, no-wrap msgid "SupportAutomount=false" msgstr "" #: C/gdm.xml:2609(para) msgid "By default GDM checks the ownership of the home directories before writing to them, this prevents security issues in case of bad setup. However, when home directories are managed by automounter, they are often not mounted before they are accessed. This option works around subtleties of Linux automounter." msgstr "" #: C/gdm.xml:2621(term) msgid "DisallowTCP" msgstr "" #: C/gdm.xml:2623(synopsis) #, no-wrap msgid "DisallowTCP=true" msgstr "" #: C/gdm.xml:2624(para) msgid "If true, then always append -nolisten tcp to the command line of local X servers, thus disallowing TCP connection. This is useful if you do not care for allowing remote connections, since the X protocol could really be potentially a security hazard to leave open, even though no known security problems exist." msgstr "" #: C/gdm.xml:2637(term) msgid "NeverPlaceCookiesOnNFS" msgstr "" #: C/gdm.xml:2639(synopsis) #, no-wrap msgid "NeverPlaceCookiesOnNFS=true" msgstr "" #: C/gdm.xml:2640(para) msgid "Normally if this is true (which is by default), GDM will not place cookies into the user's home directory if this directory is on NFS. Well, GDM will consider any filesystem with root-squashing an NFS filesystem. Sometimes however the remote file system can have root squashing and be safe (perhaps by using encryption). In this case set this to 'false'. Note that this option appeared in version 2.4.4.4 and is ignored in previous versions." msgstr "" #: C/gdm.xml:2654(term) msgid "PasswordRequired" msgstr "" #: C/gdm.xml:2656(synopsis) #, no-wrap msgid "PasswordRequired=false" msgstr "" #: C/gdm.xml:2657(para) msgid "If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be passed as a flag to pam_authenticate and pam_acct_mgmt, disallowing NULL password. This setting will only take effect if PAM is being used by GDM. This value will be overridden with the value from /etc/default/login if it contains \"PASSREQ=[YES|NO]\". If the /etc/default/login file exists, but contains no value for PASSREQ, the value as defined in the GDM configuration will be used." msgstr "" #: C/gdm.xml:2673(term) msgid "RelaxPermissions" msgstr "" #: C/gdm.xml:2675(synopsis) #, no-wrap msgid "RelaxPermissions=0" msgstr "" #: C/gdm.xml:2676(para) msgid "By default GDM ignores files and directories writable to other users than the owner." msgstr "" #: C/gdm.xml:2681(para) msgid "Changing the value of RelaxPermissions makes it possible to alter this behavior:" msgstr "" #: C/gdm.xml:2686(para) msgid "0 - Paranoia option. Only accepts user owned files and directories." msgstr "" #: C/gdm.xml:2690(para) msgid "1 - Allow group writable files and directories." msgstr "" #: C/gdm.xml:2693(para) msgid "2 - Allow world writable files and directories." msgstr "" #: C/gdm.xml:2700(term) msgid "RetryDelay" msgstr "" #: C/gdm.xml:2702(synopsis) #, no-wrap msgid "RetryDelay=1" msgstr "" #: C/gdm.xml:2703(para) msgid "The number of seconds GDM should wait before reactivating the entry field after a failed login." msgstr "" #: C/gdm.xml:2711(term) msgid "UserMaxFile" msgstr "" #: C/gdm.xml:2713(synopsis) #, no-wrap msgid "UserMaxFile=65536" msgstr "" #: C/gdm.xml:2714(para) msgid "GDM will refuse to read/write files bigger than this number (specified in bytes)." msgstr "" #: C/gdm.xml:2719(para) msgid "In addition to the size check GDM is extremely picky about accessing files in user directories. It will not follow symlinks and can optionally refuse to read files and directories writable by other than the owner. See the RelaxPermissions option for more info." msgstr "" #: C/gdm.xml:2732(title) msgid "XDCMP Support" msgstr "" #: C/gdm.xml:2735(title) msgid "[xdmcp]" msgstr "" #: C/gdm.xml:2738(term) msgid "DisplaysPerHost" msgstr "" #: C/gdm.xml:2740(synopsis) #, no-wrap msgid "DisplaysPerHost=1" msgstr "" #: C/gdm.xml:2741(para) msgid "To prevent attackers from filling up the pending queue, GDM will only allow one connection for each remote computer. If you want to provide display services to computers with more than one screen, you should increase the DisplaysPerHost value accordingly." msgstr "" #: C/gdm.xml:2749(para) msgid "Note that the number of connections from the local computer is unlimited. Only remote connections are limited by this number." msgstr "" #: C/gdm.xml:2757(term) C/gdm.xml:4004(term) msgid "Enable" msgstr "" #: C/gdm.xml:2759(synopsis) C/gdm.xml:4006(synopsis) #, no-wrap msgid "Enable=false" msgstr "" #: C/gdm.xml:2760(para) msgid "Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM." msgstr "" #: C/gdm.xml:2765(para) msgid "gdm listens for requests on UDP port 177. See the Port option for more information." msgstr "" #: C/gdm.xml:2770(para) msgid "If GDM is compiled to support it, access from remote displays can be controlled using the TCP Wrappers library. The service name is gdm" msgstr "" #: C/gdm.xml:2776(para) msgid "You should add \ngdm:.my.domain\n to your <etc>/hosts.allow, depending on your TCP Wrappers configuration. See the hosts.allow(5) man page for details." msgstr "" #: C/gdm.xml:2787(para) msgid "Please note that XDMCP is not a particularly secure protocol and that it is a good idea to block UDP port 177 on your firewall unless you really need it." msgstr "" #: C/gdm.xml:2796(term) msgid "EnableProxy" msgstr "" #: C/gdm.xml:2798(synopsis) #, no-wrap msgid "EnableProxy=false" msgstr "" #: C/gdm.xml:2799(para) msgid "Setting this to true enables support for running XDMCP sessions on a local proxy X server. This may improve the performance of XDMCP sessions, especially on high latency networks, as many X protocol operations can be completed without going over the network." msgstr "" #: C/gdm.xml:2806(para) msgid "Note, however, that this mode will significantly increase the burden on the machine hosting the XDMCP sessions" msgstr "" #: C/gdm.xml:2810(para) msgid "See the FlexiProxy and FlexiProxyDisconnect options for further details on how to configure support for this feature." msgstr "" #: C/gdm.xml:2819(term) msgid "HonorIndirect" msgstr "" #: C/gdm.xml:2821(synopsis) #, no-wrap msgid "HonorIndirect=true" msgstr "" #: C/gdm.xml:2822(para) msgid "Enables XDMCP INDIRECT choosing (i.e. remote execution of gdmchooser) for X-terminals which don't supply their own display browser." msgstr "" #: C/gdm.xml:2831(term) msgid "MaxPending" msgstr "" #: C/gdm.xml:2833(synopsis) #, no-wrap msgid "MaxPending=4" msgstr "" #: C/gdm.xml:2834(para) msgid "To avoid denial of service attacks, GDM has fixed size queue of pending connections. Only MaxPending displays can start at the same time." msgstr "" #: C/gdm.xml:2840(para) msgid "Please note that this parameter does *not* limit the number of remote displays which can be managed. It only limits the number of displays initiating a connection simultaneously." msgstr "" #: C/gdm.xml:2849(term) msgid "MaxPendingIndirect" msgstr "" #: C/gdm.xml:2851(synopsis) #, no-wrap msgid "MaxPendingIndirect=4" msgstr "" #: C/gdm.xml:2852(para) msgid "GDM will only provide MaxPendingIndirect displays with host choosers simultaneously. If more queries from different hosts come in, the oldest ones will be forgotten." msgstr "" #: C/gdm.xml:2862(term) msgid "MaxSessions" msgstr "" #: C/gdm.xml:2864(synopsis) #, no-wrap msgid "MaxSessions=16" msgstr "" #: C/gdm.xml:2865(para) msgid "Determines the maximum number of remote display connections which will be managed simultaneously. I.e. the total number of remote displays that can use your host." msgstr "" #: C/gdm.xml:2874(term) msgid "MaxWait" msgstr "" #: C/gdm.xml:2876(synopsis) #, no-wrap msgid "MaxWait=30" msgstr "" #: C/gdm.xml:2877(para) msgid "When GDM is ready to manage a display an ACCEPT packet is sent to it containing a unique session id which will be used in future XDMCP conversations." msgstr "" #: C/gdm.xml:2883(para) msgid "GDM will then place the session id in the pending queue waiting for the display to respond with a MANAGE request." msgstr "" #: C/gdm.xml:2888(para) msgid "If no response is received within MaxWait seconds, GDM will declare the display dead and erase it from the pending queue freeing up the slot for other displays." msgstr "" #: C/gdm.xml:2897(term) msgid "MaxWaitIndirect" msgstr "" #: C/gdm.xml:2899(synopsis) #, no-wrap msgid "MaxWaitIndirect=30" msgstr "" #: C/gdm.xml:2900(para) msgid "The MaxWaitIndirect parameter determines the maximum number of seconds between the time where a user chooses a host and the subsequent indirect query where the user is connected to the host. When the timeout is exceeded, the information about the chosen host is forgotten and the indirect slot freed up for other displays. The information may be forgotten earlier if there are more hosts trying to send indirect queries then MaxPendingIndirect." msgstr "" #: C/gdm.xml:2914(term) msgid "Port" msgstr "" #: C/gdm.xml:2916(synopsis) #, no-wrap msgid "Port=177" msgstr "" #: C/gdm.xml:2917(para) msgid "The UDP port number gdm should listen to for XDMCP requests. Don't change this unless you know what you are doing." msgstr "" #: C/gdm.xml:2926(term) msgid "PingIntervalSeconds" msgstr "" #: C/gdm.xml:2928(synopsis) #, no-wrap msgid "PingIntervalSeconds=15" msgstr "" #: C/gdm.xml:2929(para) msgid "Interval in which to ping the X server in seconds. If the X server doesn't return before the next time we ping it, the connection is stopped and the session ended. This is a combination of the XDM PingInterval and PingTimeout, but in seconds." msgstr "" #: C/gdm.xml:2937(para) msgid "Note that GDM in the past used to have a PingInterval configuration key which was also in minutes. For most purposes you'd want this setting to be lower then one minute however since in most cases where XDMCP would be used (such as terminal labs), a lag of more than 15 or so seconds would really mean that the terminal was turned off or restarted and you would want to end the session." msgstr "" #: C/gdm.xml:2950(term) msgid "ProxyReconnect" msgstr "" #: C/gdm.xml:2952(synopsis) #, no-wrap msgid "FlexiProxyReconnect=" msgstr "" #: C/gdm.xml:2953(para) msgid "Setting this option enables experimental support for session migration with XDMCP sessions. This enables users to disconnect from their session and later reconnect to that same session, possibly from a different terminal." msgstr "" #: C/gdm.xml:2959(para) msgid "In order to use this feature, you must have a nested X server available which supports disconnecting from its parent X server and reconnecting to another X server. Currently, the Distributed Multihead X (DMX) server supports this feature to some extent and other projects like NoMachine NX are busy implementing it." msgstr "" #: C/gdm.xml:2966(para) msgid "This option should be set to the path of a command which will handle reconnecting the XDMCP proxy to another backend display. A sample implementation for use with DMX is supplied." msgstr "" #: C/gdm.xml:2975(term) msgid "ProxyXServer" msgstr "" #: C/gdm.xml:2977(synopsis) #, no-wrap msgid "ProxyXServer=" msgstr "" #: C/gdm.xml:2978(para) msgid "The X server command line for a XDMCP proxy. Any nested X server like Xnest, Xephr or Xdmx should work fairly well." msgstr "" #: C/gdm.xml:2986(term) msgid "Willing" msgstr "" #: C/gdm.xml:2988(synopsis) #, no-wrap msgid "Willing=<etc>/gdm/Xwilling" msgstr "" #: C/gdm.xml:2989(para) msgid "When the machine sends a WILLING packet back after a QUERY it sends a string that gives the current status of this server. The default message is the system ID, but it is possible to create a script that displays customized message. If this script doesn't exist or this key is empty the default message is sent. If this script succeeds and produces some output, the first line of it's output is sent (and only the first line). It runs at most once every 3 seconds to prevent possible denial of service by flooding the machine with QUERY packets." msgstr "" #: C/gdm.xml:3007(title) msgid "Common GUI Configuration Options" msgstr "" #: C/gdm.xml:3010(title) msgid "[gui]" msgstr "" #: C/gdm.xml:3013(term) msgid "AllowGtkThemeChange" msgstr "" #: C/gdm.xml:3015(synopsis) #, no-wrap msgid "AllowGtkThemeChange=true" msgstr "" #: C/gdm.xml:3016(para) msgid "If to allow changing the GTK+ (widget) theme from the greeter. Currently this only affects the standard greeter as the graphical greeter does not yet have this ability. The theme will stay in effect on this display until changed and will affect all the other windows that are put up by GDM. Supported since 2.5.90.2." msgstr "" #: C/gdm.xml:3028(term) msgid "GtkRC" msgstr "" #: C/gdm.xml:3030(synopsis) #, no-wrap msgid "GtkRC=" msgstr "" #: C/gdm.xml:3031(para) msgid "Path to a gtkrc to read when GDM puts up a window. You should really now use the GtkTheme key for just setting a theme." msgstr "" #: C/gdm.xml:3040(term) msgid "GtkTheme" msgstr "" #: C/gdm.xml:3042(synopsis) #, no-wrap msgid "GtkTheme=Default" msgstr "" #: C/gdm.xml:3043(para) msgid "A name of an installed theme to use by default. It will be used in the greeter, chooser and all other GUI windows put up by GDM. Supported since 2.5.90.2." msgstr "" #: C/gdm.xml:3052(term) msgid "GtkThemesToAllow" msgstr "" #: C/gdm.xml:3054(synopsis) #, no-wrap msgid "GtkThemesToAllow=all" msgstr "" #: C/gdm.xml:3055(para) msgid "Comma separated list of themes to allow. These must be the names of the themes installed in the standard locations for GTK+ themes. You can also specify 'all' to allow all installed themes. This is related to the AllowGtkThemeChange key. Supported since 2.5.90.2." msgstr "" #: C/gdm.xml:3067(term) msgid "MaxIconWidth" msgstr "" #: C/gdm.xml:3069(synopsis) #, no-wrap msgid "MaxIconWidth=128" msgstr "" #: C/gdm.xml:3070(para) msgid "Specifies the maximum icon width (in pixels) that the face browser will display. Icons larger than this will be scaled. This also affects icons in the XDMCP chooser." msgstr "" #: C/gdm.xml:3079(term) msgid "MaxIconHeight" msgstr "" #: C/gdm.xml:3081(synopsis) #, no-wrap msgid "MaxIconHeight=128" msgstr "" #: C/gdm.xml:3082(para) msgid "Specifies the maximum icon height (in pixels) that the face browser will display. Icons larger than this will be scaled. This also affects icons in the XDMCP chooser." msgstr "" #: C/gdm.xml:3093(title) msgid "Greeter Configuration" msgstr "" #: C/gdm.xml:3096(title) msgid "[greeter]" msgstr "" #: C/gdm.xml:3099(term) msgid "BackgroundColor" msgstr "" #: C/gdm.xml:3101(synopsis) #, no-wrap msgid "BackgroundColor=#76848F" msgstr "" #: C/gdm.xml:3102(para) msgid "If the BackgroundType is 2, use this color in the background of the greeter. Also use it as the back of transparent images set on the background and if the BackgroundRemoteOnlyColor is set and this is a remote display. This only affects the GTK+ Greeter." msgstr "" #: C/gdm.xml:3113(term) msgid "BackgroundProgramInitialDelay" msgstr "" #: C/gdm.xml:3115(synopsis) #, no-wrap msgid "BackgroundProgramInitialDelay=30" msgstr "" #: C/gdm.xml:3116(para) msgid "The background application will be started after at least that many seconds of inactivity." msgstr "" #: C/gdm.xml:3124(term) msgid "RestartBackgroundProgram" msgstr "" #: C/gdm.xml:3126(synopsis) #, no-wrap msgid "RestartBackgroundProgram=true" msgstr "" #: C/gdm.xml:3127(para) msgid "If set the background application will be restarted when it has exited, after the delay described below has elapsed. This option can be useful when you wish to run a screen saver application when no user is using the computer." msgstr "" #: C/gdm.xml:3137(term) msgid "BackgroundProgramRestartDelay" msgstr "" #: C/gdm.xml:3139(synopsis) #, no-wrap msgid "BackgroundProgramRestartDelay=30" msgstr "" #: C/gdm.xml:3140(para) msgid "The background application will be restarted after at least that many seconds of inactivity." msgstr "" #: C/gdm.xml:3148(term) msgid "BackgroundImage" msgstr "" #: C/gdm.xml:3150(synopsis) #, no-wrap msgid "BackgroundImage=somefile.png" msgstr "" #: C/gdm.xml:3151(para) msgid "If the BackgroundType is 1, then display this file as the background in the greeter. This only affects the GTK+ Greeter." msgstr "" #: C/gdm.xml:3160(term) msgid "BackgroundProgram" msgstr "" #: C/gdm.xml:3162(synopsis) #, no-wrap msgid "BackgroundProgram=<bin>/xeyes" msgstr "" #: C/gdm.xml:3163(para) msgid "If set this command will be run in the background while the login window is being displayed. Note that not all applications will run this way, since GDM does not usually have a home directory. You could set up home directory for the GDM user if you wish to run applications which require it. This only affects the GTK+ Greeter." msgstr "" #: C/gdm.xml:3175(term) msgid "BackgroundRemoteOnlyColor" msgstr "" #: C/gdm.xml:3177(synopsis) #, no-wrap msgid "BackgroundRemoteOnlyColor=true" msgstr "" #: C/gdm.xml:3178(para) msgid "On remote displays only set the color background. This is to make network load lighter. The BackgroundProgram is also not run. This only affects the GTK+ Greeter." msgstr "" #: C/gdm.xml:3188(term) msgid "BackgroundScaleToFit" msgstr "" #: C/gdm.xml:3190(synopsis) #, no-wrap msgid "BackgroundScaleToFit=true" msgstr "" #: C/gdm.xml:3191(para) msgid "Scale background image to fit the screen. This only affects the GTK+ Greeter." msgstr "" #: C/gdm.xml:3199(term) msgid "BackgroundType" msgstr "" #: C/gdm.xml:3201(synopsis) #, no-wrap msgid "BackgroundType=2" msgstr "" #: C/gdm.xml:3202(para) msgid "The type of background to set. 0 is none, 1 is image and color, 2 is color and 3 is image. This only affects the GTK+ Greeter." msgstr "" #: C/gdm.xml:3210(term) msgid "Browser" msgstr "" #: C/gdm.xml:3212(synopsis) #, no-wrap msgid "Browser=true" msgstr "" #: C/gdm.xml:3213(para) msgid "Set to true to enable the face browser. See the ``The GTK+ Greeter'' section for more information on the face browser. This option only works for the GTK+ Greeter. For the Themed Greeter, the face browser is enabled by choosing a theme which includes a face browser" msgstr "" #: C/gdm.xml:3224(term) msgid "ChooserButton" msgstr "" #: C/gdm.xml:3226(synopsis) #, no-wrap msgid "ChooserButton=true" msgstr "" #: C/gdm.xml:3227(para) msgid "If true, add a chooser button to the Actions menu that will restart the current X server with a chooser. XDMCP does not need to be enabled on the local computer for this to work." msgstr "" #: C/gdm.xml:3236(term) msgid "ConfigAvailable" msgstr "" #: C/gdm.xml:3238(synopsis) #, no-wrap msgid "ConfigAvailable=false" msgstr "" #: C/gdm.xml:3239(para) msgid "If true, allows the configurator to be run from the greeter. Note that the user will need to type in the root password before the configurator will be started. This is set to false by default for additional security. See the Configurator option in the daemon section." msgstr "" #: C/gdm.xml:3251(term) msgid "DefaultFace" msgstr "" #: C/gdm.xml:3253(synopsis) #, no-wrap msgid "DefaultFace=<share>/pixmaps/nophoto.png" msgstr "" #: C/gdm.xml:3254(para) msgid "If a user has no defined face image, GDM will use the \"stock_person\" icon defined in the current GTK+ theme. If no such image is defined, the image specified by DefaultFace will be used. The image must be in a gdk-pixbuf supported format and the file must be readable to the GDM user." msgstr "" #: C/gdm.xml:3266(term) msgid "Include" msgstr "" #: C/gdm.xml:3268(synopsis) #, no-wrap msgid "Include=" msgstr "" #: C/gdm.xml:3269(para) msgid "Comma separated list of users to be included in the face browser and in the gdmsetup selection list for Automatic/Timed login. See also Exclude, IncludeAll, and MinimalUID." msgstr "" #: C/gdm.xml:3281(term) msgid "Exclude" msgstr "" #: C/gdm.xml:3283(synopsis) #, no-wrap msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." msgstr "" #: C/gdm.xml:3284(para) msgid "Comma separated list of users to be excluded from the face browser and from the gdmsetup selection list for Automatic/Timed login. Excluded users will still be able to log in, but will have to type their username. See also Include, IncludeAll, and MinimalUID." msgstr "" #: C/gdm.xml:3297(term) msgid "IncludeAll" msgstr "" #: C/gdm.xml:3299(synopsis) #, no-wrap msgid "IncludeAll=false" msgstr "" #: C/gdm.xml:3300(para) msgid "By default, an empty include list means display no users. By setting IncludeAll to true, the password file will be scanned and all users will be displayed aside from users excluded via the Exclude setting and user ID's less than MinimalUID. Scanning the password file can be slow on systems with large numbers of users and this feature should not be used in such environments. See also Include, Exclude, and MinimalUID." msgstr "" #: C/gdm.xml:3316(term) msgid "GlobalFaceDir" msgstr "" #: C/gdm.xml:3318(synopsis) #, no-wrap msgid "GlobalFaceDir=<share>/pixmaps/faces/" msgstr "" #: C/gdm.xml:3319(para) msgid "Systemwide directory for face files. The sysadmin can place icons for users here without touching their homedirs. Faces are named after their users' logins." msgstr "" #: C/gdm.xml:3325(para) msgid "I.e. <GlobalFaceDir>/johndoe would contain the face icon for the user ``johndoe''. No image format extension should be specified." msgstr "" #: C/gdm.xml:3331(para) msgid "The face images must be stored in gdk-pixbuf supported formats and they must be readable for the GDM user." msgstr "" #: C/gdm.xml:3336(para) msgid "A user's own icon file will always take precedence over the sysadmin provided one." msgstr "" #: C/gdm.xml:3344(term) msgid "GraphicalTheme" msgstr "" #: C/gdm.xml:3346(synopsis) #, no-wrap msgid "GraphicalTheme=circles" msgstr "" #: C/gdm.xml:3347(para) msgid "The graphical theme that the Themed Greeter should use. it should refer to a directory in the theme directory set by GraphicalThemeDir." msgstr "" #: C/gdm.xml:3356(term) msgid "GraphicalThemes" msgstr "" #: C/gdm.xml:3358(synopsis) #, no-wrap msgid "GraphicalThemes=circles" msgstr "" #: C/gdm.xml:3359(para) msgid "The graphical themes that the Themed Greeter should use is the Mode is set on Random Themes. This is a \"/:\" delimited list. It should refer to a directory in the theme directory set by GraphicalThemeDir. This is only used if GraphicalThemeRand is set to true." msgstr "" #: C/gdm.xml:3371(term) msgid "GraphicalThemeRand" msgstr "" #: C/gdm.xml:3373(synopsis) #, no-wrap msgid "GraphicalThemeRand=false" msgstr "" #: C/gdm.xml:3374(para) msgid "Whether the graphica