# Telugu translation for gdm. # Copyright (C) 2011, 2012 Swecha Telugu Localisation Team # This file is distributed under the same license as the gdm package. # Bhuvan Krishna , 2012. # msgid "" msgstr "" "Project-Id-Version: gdm master\n" "POT-Creation-Date: 2012-03-25 07:01+0000\n" "PO-Revision-Date: 2012-03-25 16:12+0530\n" "Last-Translator: Bhuvan Krishna \n" "Language-Team: Telugu \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n!=1);\n" #: C/gdm.xml:13(title) msgid "GNOME Display Manager Reference Manual" msgstr "" #: C/gdm.xml:17(revnumber) msgid "0.0" msgstr "0.0" #: C/gdm.xml:18(date) msgid "2008-09" msgstr "2008-09" #: C/gdm.xml:23(para) msgid "GDM is the GNOME Display Manager, a graphical login program." msgstr "" #: C/gdm.xml:30(firstname) msgid "Martin" msgstr "" #: C/gdm.xml:30(othername) msgid "K." msgstr "" #: C/gdm.xml:31(surname) msgid "Petersen" msgstr "" #: C/gdm.xml:33(email) msgid "mkp@mkp.net" msgstr "mkp@mkp.net" #: C/gdm.xml:37(firstname) msgid "George" msgstr "" #: C/gdm.xml:37(surname) msgid "Lebl" msgstr "" #: C/gdm.xml:39(email) msgid "jirka@5z.com" msgstr "jirka@5z.com" #: C/gdm.xml:43(firstname) msgid "Jon" msgstr "" #: C/gdm.xml:43(surname) msgid "McCann" msgstr "" #: C/gdm.xml:45(email) msgid "mccann@jhu.edu" msgstr "mccann@jhu.edu" #: C/gdm.xml:49(firstname) msgid "Ray" msgstr "" #: C/gdm.xml:49(surname) msgid "Strode" msgstr "" #: C/gdm.xml:51(email) msgid "rstrode@redhat.com" msgstr "rstrode@redhat.com" #: C/gdm.xml:55(firstname) msgid "Brian" msgstr "" #: C/gdm.xml:55(surname) msgid "Cameron" msgstr "" #: C/gdm.xml:57(email) msgid "Brian.Cameron@Oracle.COM" msgstr "" #: C/gdm.xml:62(year) msgid "1998" msgstr "1998" #: C/gdm.xml:63(year) msgid "1999" msgstr "1999" #: C/gdm.xml:64(holder) msgid "Martin K. Petersen" msgstr "" #: C/gdm.xml:67(year) msgid "2001" msgstr "2001" #: C/gdm.xml:68(year) C/gdm.xml:73(year) C/gdm.xml:79(year) msgid "2003" msgstr "2003" #: C/gdm.xml:69(year) msgid "2004" msgstr "2004" #: C/gdm.xml:70(holder) msgid "George Lebl" msgstr "" #: C/gdm.xml:74(year) msgid "2007" msgstr "2007" #: C/gdm.xml:75(year) msgid "2008" msgstr "2008" #: C/gdm.xml:76(holder) msgid "Red Hat, Inc." msgstr "రెడ్ హ్యాట్, ఇంక్." #: C/gdm.xml:80(year) msgid "2011" msgstr "2011" #: C/gdm.xml:81(holder) msgid "Oracle and/or its affiliates. All rights reserved." msgstr "" #: C/gdm.xml:2(para) msgid "" "Permission is granted to copy, distribute and/or modify this document under " "the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any " "later version published by the Free Software Foundation with no Invariant " "Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy " "of the GFDL at this link or " "in the file COPYING-DOCS distributed with this manual." msgstr "" #: C/gdm.xml:12(para) msgid "" "This manual is part of a collection of GNOME manuals distributed under the " "GFDL. If you want to distribute this manual separately from the collection, " "you can do so by adding a copy of the license to the manual, as described in " "section 6 of the license." msgstr "" #: C/gdm.xml:19(para) msgid "" "Many of the names used by companies to distinguish their products and " "services are claimed as trademarks. Where those names appear in any GNOME " "documentation, and the members of the GNOME Documentation Project are made " "aware of those trademarks, then the names are in capital letters or initial " "capital letters." msgstr "" #: C/gdm.xml:35(para) msgid "" "DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, " "EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT " "THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS " "MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE " "RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR " "MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR " "MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL " "WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY " "SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN " "ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION " "OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND" msgstr "" #: C/gdm.xml:55(para) msgid "" "UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING " "NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY " "CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE " "DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON " "FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF " "ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, " "WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES " "OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED " "VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE " "POSSIBILITY OF SUCH DAMAGES." msgstr "" #: C/gdm.xml:28(para) msgid "" "DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS " "OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: " "" msgstr "" #: C/gdm.xml:86(releaseinfo) C/gdm.xml:97(para) msgid "" "This manual describes version 2.26.0 of the GNOME Display Manager. It was " "last updated on 02/10/2009." msgstr "" #: C/gdm.xml:95(title) msgid "Terms and Conventions Used in This Manual" msgstr "" #: C/gdm.xml:102(para) msgid "" "Chooser - A program used to select a remote host for managing a display " "remotely on the attached display (gdm-host-chooser)." msgstr "" #: C/gdm.xml:107(para) msgid "" "FreeDesktop - The organization providing desktop standards, such as the " "Desktop Entry Specification used by GDM. http://www.freedesktop.org." msgstr "" #: C/gdm.xml:113(para) msgid "" "GDM - GNOME Display Manager. Used to describe the software package as a " "whole." msgstr "" #: C/gdm.xml:118(para) msgid "" "Greeter - The graphical login window (gdm-simple-greeter)." msgstr "" #: C/gdm.xml:122(para) msgid "PAM - Pluggable Authentication Mechanism" msgstr "" #: C/gdm.xml:126(para) msgid "XDMCP - X Display Manage Protocol" msgstr "" #: C/gdm.xml:130(para) msgid "" "Xserver - An implementation of the X Window System. For example the Xorg " "Xserver provided by the X.org Foundation http://www.x.org." msgstr "" #: C/gdm.xml:136(para) msgid "" "Paths that start with a word in angle brackets are relative to the " "installation prefix. I.e. <share>/pixmaps/ refers " "to /usr/share/pixmaps if GDM was configured with " "--prefix=/usr." msgstr "" #: C/gdm.xml:147(title) msgid "Overview" msgstr "పర్యావలోకనం" #: C/gdm.xml:150(title) msgid "Introduction" msgstr "పరిచయం" #: C/gdm.xml:152(para) msgid "" "The GNOME Display Manager (GDM) is a display manager that implements all " "significant features required for managing attached and remote displays. GDM " "was written from scratch and does not contain any XDM or X Consortium code." msgstr "" #: C/gdm.xml:159(para) msgid "" "Note that GDM is configurable, and many configuration settings have an " "impact on security. Issues to be aware of are highlighted in this document." msgstr "" #: C/gdm.xml:165(para) msgid "" "Please note that some Operating Systems configure GDM to behave differently " "than the default values as described in this document. If GDM does not seem " "to behave as documented, then check to see if any related configuration may " "be different than described here." msgstr "" #: C/gdm.xml:172(para) msgid "" "For further information about GDM, refer to the project website at http://www.gnome." "org/projects/gdm and the project Wiki http://live.gnome.org/GDM." msgstr "" #: C/gdm.xml:180(para) msgid "" "For discussion or queries about GDM, refer to the
gdm-" "list@gnome.org
mail list. This list is archived, and is a " "good resource to check to seek answers to common questions. This list is " "archived at http://mail.gnome.org/archives/gdm-list/ and has a search " "facility to look for messages with keywords." msgstr "" #: C/gdm.xml:190(para) msgid "" "Please submit any bug reports or enhancement requests to the \"gdm\" " "category in http://" "bugzilla.gnome.org." msgstr "" #: C/gdm.xml:199(title) msgid "Interface Stability" msgstr "" #: C/gdm.xml:201(para) msgid "" "GDM 2.20 and earlier supported stable configuration interfaces. However, the " "codebase was completely rewritten for GDM 2.22, and is not completely " "backward compatible with older releases. This is in part because things work " "differently, so some options just don't make sense, in part because some " "options never made sense, and in part because some functionality has not " "been reimplemented yet." msgstr "" #: C/gdm.xml:210(para) msgid "" "Interfaces which continue to be supported in a stable fashion include the " "Init, PreSession, PostSession, PostLogin, and Xsession scripts. Some daemon " "configuration options in the <etc>/gdm/custom.conf file continue to be supported. Also, the ~/.dmrc, and face browser image locations are still supported." msgstr "" #: C/gdm.xml:219(para) msgid "" "GDM 2.20 and earlier supported the ability to manage multiple displays with " "separate graphics cards, such as used in terminal server environments, login " "in a window via a program like Xnest or Xephyr, the gdmsetup program, XML-" "based greeter themes, and the ability to run the XDMCP chooser from the " "login screen. These features were not added back during the 2.22 rewrite." msgstr "" #: C/gdm.xml:231(title) msgid "Functional Description" msgstr "" #. #. TODO - Would be good to discuss D-Bus, perhaps the new GObject model, #. and to explain the reasons why the rewrite made GDM better. #. From a high-level overview perspective, rather than the #. technical aspects. #. #: C/gdm.xml:242(para) msgid "" "GDM is responsible for managing displays on the system. This includes " "authenticating users, starting the user session, and terminating the user " "session. GDM is configurable and the ways it can be configured are described " "in the \"Configuring GDM\" section of this document. GDM is also accessible " "for users with disabilities." msgstr "" #: C/gdm.xml:250(para) msgid "" "GDM provides the ability to manage the main console display, and displays " "launched via VT. It is integrated with other programs, such as the Fast User " "Switch Applet (FUSA) and gnome-screensaver to manage multiple displays on " "the console via the Xserver Virtual Terminal (VT) interface. It also can " "manage XDMCP displays." msgstr "" #: C/gdm.xml:258(para) msgid "" "Regardless of the display type, GDM will do the following when it manages " "the display. It will start an Xserver process, then run the Init script as the root user, and start the greeter program on the " "display." msgstr "" #: C/gdm.xml:265(para) msgid "" "The greeter program is run as the unprivileged \"gdm\" user/group. This user " "and group are described in the \"Security\" section of this document. The " "main functions of the greeter program are to provide a mechanism for " "selecting an account for log in and to drive the dialogue between the user " "and system when authenticating that account. The authentication process is " "driven by Pluggable Authentication Modules (PAM). The PAM modules determine " "what prompts (if any) are shown to the user to authenticate. On the average " "system, the greeter program will request a username and password for " "authentication. However some systems may be configured to use supplemental " "mechanisms such as a fingerprint or SmartCard readers. GDM can be configured " "to support these alternatives in parallel with greeter login extensions and " "the --enable-split-authentication./configure option, or one at a time via system PAM configuration." msgstr "" #: C/gdm.xml:284(para) msgid "" "The smartcard extension can be enabled or disabled via the org." "gnome.display-manager.extensions.smartcard.active gsettings key." msgstr "" #: C/gdm.xml:290(para) msgid "" "Likewise, the fingerprint extension can be enabled or disabled via the " "org.gnome.display-manager.extensions.fingerprint.active " "gsettings key." msgstr "" #: C/gdm.xml:296(para) msgid "" "GDM and PAM can be configured to not require any input, which will cause GDM " "to automatically log in and simply start a session, which can be useful for " "some environments, such as single user systems or kiosks." msgstr "" #: C/gdm.xml:303(para) msgid "" "In addition to authentication, the greeter program allows the user to select " "which session to start and which language to use. Sessions are defined by " "files that end in the .desktop suffix and more information about these files " "can be found in the \"GDM User Session and Language Configuration\" section " "of this document. By default, GDM is configured to display a face browser so " "the user can select their user account by clicking on an image instead of " "having to type their username. GDM keeps track of the user's default session " "and language in the user's ~/.dmrc and will use these " "defaults if the user did not pick a session or language in the login GUI." msgstr "" #: C/gdm.xml:316(para) msgid "" "After authenticating a user, the daemon runs the PostLogin script as root, then runs the PreSession " "script as root. After running these scripts, the user session is started. " "When the user exits their session, the PostSession " "script is run as root. These scripts are provided as hooks for distributions " "and end-users to customize how sessions are managed. For example, using " "these hooks you could set up a machine which creates the user's $HOME " "directory on the fly, and erases it on logout. The difference between the " "PostLogin and PreSession scripts " "is that PostLogin is run before the pam_open_session " "call so is the right place to do anything which should be run before the " "user session is initialized. The PreSession script is " "called after session initialization." msgstr "" #: C/gdm.xml:336(title) msgid "Greeter Panel" msgstr "" #: C/gdm.xml:337(para) msgid "" "The GDM greeter program displays a panel docked at the bottom of the screen " "which provides additional functionality. When a user is selected, the panel " "allows the user to select which session, language, and keyboard layout to " "use after logging in. The keyboard layout selector also changes the keyboard " "layout used when typing your password. The panel also contains an area for " "login services to leave status icons. Some example status icons include a " "battery icon for current battery usage, and an icon for enabling " "accessibility features. The greeter program also provides buttons which " "allow the user to shutdown or restart the system. It is possible to " "configure GDM to not provide the shutdown and restart buttons, if desired. " "GDM can also be configured via PolicyKit (or via RBAC on Oracle Solaris) to " "require the user have appropriate authorization before accepting the " "shutdown or restart request." msgstr "" #: C/gdm.xml:354(para) msgid "" "Note that keyboard layout features are only available on systems that " "support libxklavier." msgstr "" #: C/gdm.xml:361(title) msgid "Accessibility" msgstr "" #: C/gdm.xml:363(para) msgid "" "GDM supports \"Accessible Login\", allowing users to log into their desktop " "session even if they cannot easily use the screen, mouse, or keyboard in the " "usual way. Accessible Technology (AT) features such as an on-screen " "keyboard, screen reader, screen magnifier, and Xserver AccessX keyboard " "accessibility are available. It is also possible to enable large text or " "high contrast icons and controls, if needed. Refer to the \"Accessibility " "Configuration\" section of the document for more information how various " "accessibility features can be configured." msgstr "" #: C/gdm.xml:375(para) msgid "" "On some Operating Systems, it is necessary to make sure that the GDM user is " "a member of the \"audio\" group for AT programs that require audio output " "(such as text-to-speech) to be functional." msgstr "" #: C/gdm.xml:383(title) msgid "The GDM Face Browser" msgstr "" #: C/gdm.xml:385(para) msgid "" "The Face Browser is the interface which allows users to select their " "username by clicking on an image. This feature can be enabled or disabled " "via the /apps/gdm/simple-greeter/disable_user_list GConf key and is on by " "default. When disabled, users must type their complete username by hand. " "When enabled, it displays all local users which are available for login on " "the system (all user accounts defined in the /etc/passwd file that have a " "valid shell and sufficiently high UID) and remote users that have recently " "logged in. The face browser in GDM 2.20 and earlier would attempt to display " "all remote users, which caused performance problems in large, enterprise " "deployments." msgstr "" #: C/gdm.xml:399(para) msgid "" "The Face Browser is configured to display the users who log in most " "frequently at the top of the list. This helps to ensure that users who log " "in frequently can quickly find their login image." msgstr "" #: C/gdm.xml:405(para) msgid "" "The Face Browser supports \"type-ahead search\" which dynamically moves the " "face selection as the user types to the corresponding username in the list. " "This means that a user with a long username will only have to type the first " "few characters of the username before the correct item in the list gets " "selected." msgstr "" #: C/gdm.xml:413(para) msgid "" "The icons used by GDM can be installed globally by the sysadmin or can be " "located in the user's home directories. If installed globally they should be " "in the <share>/pixmaps/faces/ directory and the " "filename should be the name of the user. Face image files should be a " "standard image that GTK+ can read, such as PNG or JPEG. Face icons placed in " "the global face directory must be readable to the GDM user." msgstr "" #. #. TODO - In the old GDM the ~/gnome2/gdm file is used, but the new code #. seems to use ~/.gnome/gdm. Error? #. #: C/gdm.xml:429(para) msgid "" "If there is no global icon for the user, GDM will look in the user's $HOME " "directory for the image file. GDM will first look for the user's face image " "in ~/.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." msgstr "" #: C/gdm.xml:438(para) msgid "" "If a user has no defined face image, GDM will use the \"stock_person\" icon " "defined in the current GTK+ theme. If no such image is defined, it will " "fallback to a generic face image." msgstr "" #: C/gdm.xml:444(para) msgid "" "Please note that loading and scaling face icons located in remote user home " "directories can be a very time-consuming task. Since it not practical to " "load images over NIS or NFS, GDM does not attempt to load face images from " "remote home directories." msgstr "" #: C/gdm.xml:451(para) msgid "" "When the browser is turned on, valid usernames on the computer are exposed " "for everyone to see. If XDMCP is enabled, then the usernames are exposed to " "remote users. This, of course, limits security somewhat since a malicious " "user does not need to guess valid usernames. In some very restrictive " "environments the face browser may not be appropriate." msgstr "" #: C/gdm.xml:463(title) msgid "XDMCP" msgstr "XDMCP" #. #. TODO - What XDMCP features actually work? I know that the #. chooser is missing. #. #: C/gdm.xml:472(para) msgid "" "The GDM daemon can be configured to listen for and manage X Display Manage " "Protocol (XDMCP) requests from remote displays. By default XDMCP support is " "turned off, but can be enabled if desired. If GDM is built with TCP Wrapper " "support, then the daemon will only grant access to hosts specified in the " "GDM service section in the TCP Wrappers configuration file." msgstr "" #: C/gdm.xml:481(para) msgid "" "GDM includes several measures making it more resistant to denial of service " "attacks on the XDMCP service. A lot of the protocol parameters, handshaking " "timeouts, etc. can be fine tuned. The default configuration should work " "reasonably on most systems." msgstr "" #: C/gdm.xml:488(para) msgid "" "GDM by default listens for XDMCP requests on the normal UDP port used for " "XDMCP, port 177, and will respond to QUERY and BROADCAST_QUERY requests by " "sending a WILLING packet to the originator." msgstr "" #: C/gdm.xml:494(para) msgid "" "GDM can also be configured to honor INDIRECT queries and present a host " "chooser to the remote display. GDM will remember the user's choice and " "forward subsequent requests to the chosen manager. GDM also supports an " "extension to the protocol which will make it forget the redirection once the " "user's connection succeeds. This extension is only supported if both daemons " "are GDM. It is transparent and will be ignored by XDM or other daemons that " "implement XDMCP." msgstr "" #: C/gdm.xml:504(para) msgid "" "If XDMCP seems to not be working, make sure that all machines are specified " "in /etc/hosts." msgstr "" #: C/gdm.xml:509(para) msgid "" "Refer to the \"Security\" section for information about security concerns " "when using XDMCP." msgstr "" #: C/gdm.xml:516(title) msgid "Logging" msgstr "నమోదుపరుచు" #: C/gdm.xml:518(para) msgid "" "GDM uses syslog to log errors and status. It can also log debugging " "information, which can be useful for tracking down problems if GDM is not " "working properly. Debug output can be enabled by setting the debug/Enable " "key to \"true\" in the <etc>/gdm/custom.conf file." msgstr "" #: C/gdm.xml:526(para) msgid "" "Output from the various Xservers is stored in the GDM log directory, which " "is normally <var>/log/gdm/. Any Xserver messages " "are saved to a file associated with the display value, <" "display>.log." msgstr "" #: C/gdm.xml:533(para) msgid "" "The session output is piped through the GDM daemon to the ~/." "xsession-errors file. The file is overwritten on each login, so " "logging out and logging back into the same user via GDM will cause any " "messages from the previous session to be lost." msgstr "" #: C/gdm.xml:540(para) msgid "" "Note that if GDM can not create this file for some reason, then a fallback " "file will be created named ~/.xsession-errors.XXXXXXXX " "where the XXXXXXXX are some random characters." msgstr "" #: C/gdm.xml:548(title) msgid "Fast User Switching" msgstr "" #: C/gdm.xml:550(para) msgid "" "GDM allows multiple users to be logged in at the same time. After one user " "is logged in, additional users can log in via the User Switcher on the GNOME " "Panel, or from the \"Switch User\" button in Lock Screen dialog of GNOME " "Screensaver. The active session can be changed back and forth using the same " "mechanism. Note that some distributions may not add the User Switcher to the " "default panel configuration. It can be added using the panel context menu." msgstr "" #: C/gdm.xml:559(para) msgid "" "Note this feature is available on systems that support Virtual Terminals. " "This feature will not function if Virtual Terminals is not available." msgstr "" #: C/gdm.xml:570(title) msgid "Security" msgstr "రక్షణ" #: C/gdm.xml:573(title) msgid "The GDM User And Group" msgstr "" #: C/gdm.xml:575(para) msgid "" "For security reasons a dedicated user and group id are recommended for " "proper operation. This user and group are normally \"gdm\" on most systems, " "but can be configured to any user or group. All GDM GUI programs are run as " "this user, so that the programs which interact with the user are run in a " "sandbox. This user and group should have limited privilege." msgstr "" #: C/gdm.xml:584(para) msgid "" "The only special privilege the \"gdm\" user requires is the ability to read " "and write Xauth files to the <var>/run/gdm " "directory. The <var>/run/gdm directory should " "have root:gdm ownership and 1777 permissions." msgstr "" #: C/gdm.xml:592(para) msgid "" "You should not, under any circumstances, configure the GDM user/group to a " "user which a user could easily gain access to, such as the user " "nobody. Any user who gains access to an Xauth key can " "snoop on and control running GUI programs running in the associated session " "or perform a denial-of-service attack on it. It is important to ensure that " "the system is configured properly so that only the \"gdm\" user has access " "to these files and that it is not easy to login to this account. For " "example, the account should be setup to not have a password or allow non-" "root users to login to the account." msgstr "" #: C/gdm.xml:605(para) msgid "" "The GDM greeter configuration is stored in GConf. To allow the GDM user to " "be able to write configuration, it is necessary for the \"gdm\" user to have " "a writable $HOME directory. Users may configure the default GConf " "configuration as desired to avoid the need to provide the \"gdm\" user with " "a writable $HOME directory. However, some features of GDM may be disabled if " "it is unable to write state information to GConf configuration." msgstr "" #: C/gdm.xml:617(title) msgid "PAM" msgstr "PAM" #: C/gdm.xml:619(para) msgid "" "GDM uses PAM for login authentication. PAM stands for Pluggable " "Authentication Module, and is used by most programs that request " "authentication on your computer. It allows the administrator to configure " "specific authentication behavior for different login programs (such as ssh, " "login GUI, screensaver, etc.)" msgstr "" #: C/gdm.xml:627(para) msgid "" "PAM is complicated and highly configurable, and this documentation does not " "intend to explain this in detail. Instead, it is intended to give an " "overview of how PAM configuration relates with GDM, how PAM is commonly " "configured with GDM, and known issues. It is expected that a person needing " "to do PAM configuration would need to do further reading of PAM " "documentation to understand how to configure PAM and to understand terms " "used in this section." msgstr "" #: C/gdm.xml:637(para) msgid "" "PAM configuration has different, but similar, interfaces on different " "Operating Systems, so check the pam." "d or pam.conf man " "page for details. Be sure you read the PAM documentation and are comfortable " "with the security implications of any changes you intend to make to your " "configuration." msgstr "" #: C/gdm.xml:647(para) msgid "" "Note that, by default, GDM uses the \"gdm\" PAM service name for normal " "login and the \"gdm-autologin\" PAM service name for automatic login. These " "services may not be defined in your pam.d or pam.conf configured file. If " "there is no entry, then GDM will use the default PAM behavior. On most " "systems this should work fine. However, the automatic login feature may not " "work if the gdm-autologin service is not defined." msgstr "" #: C/gdm.xml:657(para) msgid "" "The PostLogin script is run before pam_open_session is " "called, and the PreSession script is called after. This " "allows the system administrator to add any scripting to the login process " "either before or after PAM initializes the session." msgstr "" #: C/gdm.xml:665(para) msgid "" "If you wish to make GDM work with other types of authentication mechanisms " "(such as a fingerprint or SmartCard reader), then you should implement this " "by using a PAM service module for the desired authentication type rather " "than by trying to modify the GDM code directly. Refer to the PAM " "documentation on your system. How to do this is frequently discussed on the " "
gdm-list@gnome.org
mail list, so you can " "refer to the list archives for more information." msgstr "" #: C/gdm.xml:676(para) msgid "" "PAM does have some limitations regarding being able to work with multiple " "types of authentication at the same time, like supporting the ability to " "accept either SmartCard and the ability to type the username and password " "into the login program. There are techniques that are used to make this " "work, and it is best to research how this problem is commonly solved when " "setting up such a configuration." msgstr "" #: C/gdm.xml:685(para) msgid "" "If automatic login does not work on a system, check to see if the \"gdm-" "autologin\" PAM stack is defined in the PAM configuration. For this to work, " "it is necessary to use a PAM module that simply does no authentication, or " "which simply returns PAM_SUCCESS from all of its public interfaces. Assuming " "your system has a pam_allow.so PAM module which does this, a PAM " "configuration to enable \"gdm-autologin\" would look like this:" msgstr "" #: C/gdm.xml:695(screen) #, no-wrap msgid "" "\n" " gdm-autologin auth required pam_unix_cred.so.1\n" " gdm-autologin auth sufficient pam_allow.so.1\n" " gdm-autologin account sufficient pam_allow.so.1\n" " gdm-autologin session sufficient pam_allow.so.1\n" " gdm-autologin password sufficient pam_allow.so.1\n" msgstr "" "\n" " gdm-autologin auth required pam_unix_cred.so.1\n" " gdm-autologin auth sufficient pam_allow.so.1\n" " gdm-autologin account sufficient pam_allow.so.1\n" " gdm-autologin session sufficient pam_allow.so.1\n" " gdm-autologin password sufficient pam_allow.so.1\n" #: C/gdm.xml:703(para) msgid "" "The above setup will cause no lastlog entry to be generated. If a lastlog " "entry is desired, then use the following for the session:" msgstr "" #: C/gdm.xml:708(screen) #, no-wrap msgid "" "\n" " gdm-autologin session required pam_unix_session.so.1\n" msgstr "" #: C/gdm.xml:712(para) msgid "" "If the computer is used by several people, which makes automatic login " "unsuitable, you may want to allow some users to log in without entering " "their password. This feature can be enabled as a per-user option in the " "users-admin tool from the gnome-system-tools; it is achieved by checking " "that the user is member a Unix group called \"nopasswdlogin\" before asking " "for a password. For this to work, the PAM configuration file for the \"gdm\" " "service must include a line such as:" msgstr "" #: C/gdm.xml:723(screen) #, no-wrap msgid "" "\n" " gdm auth sufficient pam_succeed_if.so user ingroup nopasswdlogin\n" msgstr "" #: C/gdm.xml:730(title) msgid "utmp and wtmp" msgstr "" #: C/gdm.xml:732(para) msgid "" "GDM generates utmp and wtmp User Accounting Database entries upon session " "login and logout. The utmp database contains user access and accounting " "information that is accessed by commands such as finger, " "last, login, and who. The wtmp database contains the history of user access and " "accounting information for the utmp database. Refer to the utmp and wtmp man pages on your system for more information." msgstr "" #: C/gdm.xml:747(title) msgid "Xserver Authentication Scheme" msgstr "" #: C/gdm.xml:749(para) msgid "" "Xserver authorization files are stored in a newly created subdirectory of " "<var>/run/gdm at start up. These files are used " "to store and share a \"password\" between X clients and the Xserver. This " "\"password\" is unique for each session logged in, so users from one session " "can't snoop on users from another." msgstr "" #: C/gdm.xml:757(para) msgid "" "GDM only supports the MIT-MAGIC-COOKIE-1 Xserver authentication scheme. " "Normally little is gained from the other schemes, and no effort has been " "made to implement them so far. Be especially careful about using XDMCP " "because the Xserver authentication cookie goes over the wire as clear text. " "If snooping is possible, then an attacker could simply snoop your " "authentication password as you log in, regardless of the authentication " "scheme being used. If snooping is possible and undesirable, then you should " "use ssh for tunneling an X connection rather then using XDMCP. You could " "think of XDMCP as a sort of graphical telnet, having the same security " "issues. In most cases, ssh -Y should be preferred over GDM's XDMCP features." msgstr "" #: C/gdm.xml:774(title) msgid "XDMCP Security" msgstr "" #: C/gdm.xml:776(para) msgid "" "Even though your display is protected by cookies, XEvents and thus " "keystrokes typed when entering passwords will still go over the wire in " "clear text. It is trivial to capture these." msgstr "" #: C/gdm.xml:782(para) msgid "" "XDMCP is primarily useful for running thin clients such as in terminal labs. " "Those thin clients will only ever need the network to access the server, and " "so it seems like the best security policy to have those thin clients on a " "separate network that cannot be accessed by the outside world, and can only " "connect to the server. The only point from which you need to access outside " "is the server. This type of set up should never use an unmanaged hub or " "other sniffable network." msgstr "" #: C/gdm.xml:795(title) msgid "XDMCP Access Control" msgstr "" #: C/gdm.xml:797(para) msgid "" "XDMCP access control is done using TCP wrappers. It is possible to compile " "GDM without TCP wrapper support, so this feature may not be supported on " "some Operating Systems." msgstr "" #: C/gdm.xml:803(para) msgid "" "You should use the daemon name 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:810(screen) #, no-wrap msgid "" "\n" "gdm: .evil.domain\n" msgstr "" #: C/gdm.xml:813(para) msgid "" "to <etc>/hosts.deny. You may also need to add" msgstr "" #: C/gdm.xml:817(screen) #, no-wrap msgid "" "\n" "gdm: .your.domain\n" msgstr "" #: C/gdm.xml:820(para) msgid "" "to your <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:829(title) msgid "Firewall Security" msgstr "" #: C/gdm.xml:831(para) msgid "" "Even though GDM tries to outsmart potential attackers trying to take " "advantage of XDMCP, it is still advised that you block the XDMCP port " "(normally UDP port 177) on your firewall unless really needed. GDM guards " "against denial of service attacks, but the X protocol is still inherently " "insecure and should only be used in controlled environments. Also each " "remote connection takes up lots of resources, so it is much easier to do a " "denial of service attack via XDMCP than attacking a webserver." msgstr "" #: C/gdm.xml:842(para) msgid "" "It is also wise to block all of the Xserver ports. These are TCP ports 6000+ " "(one for each display number) on your firewall. Note that GDM will use " "display numbers 20 and higher for flexible on-demand servers." msgstr "" #: C/gdm.xml:849(para) msgid "" "X is not a very safe protocol when using it over the Internet, and XDMCP is " "even less safe." msgstr "" #: C/gdm.xml:856(title) msgid "PolicyKit" msgstr "" #. #. TODO - Should we say more? #. #: C/gdm.xml:864(para) msgid "" "GDM may be configured to use PolicyKit to allow the system administrator to " "control whether the login screen should provide the shutdown and restart " "buttons on the greeter screen." msgstr "" #: C/gdm.xml:870(para) msgid "" "These buttons are controlled by the org.freedesktop.consolekit." "system.stop-multiple-users and org.freedesktop." "consolekit.system.restart-multiple-users actions respectively. " "Policy for these actions can be set up using the polkit-gnome-authorization " "tool, or the polkit-auth command line program." msgstr "" #: C/gdm.xml:882(title) msgid "RBAC (Role Based Access Control)" msgstr "" #: C/gdm.xml:884(para) msgid "" "GDM may be configured to use RBAC instead of PolicyKit. In this case the " "RBAC configuration is used to control whether the login screen should " "provide the shutdown and restart buttons on the greeter screen." msgstr "" #: C/gdm.xml:890(para) msgid "" "For example, on Oracle Solaris, the \"solaris.system.shutdown\" " "authorization is used to control this. Simply modify the /etc/" "user_attr file so that the \"gdm\" user has this authorization." msgstr "" #: C/gdm.xml:903(title) msgid "Support for ConsoleKit" msgstr "" #. #. TODO - Should we update these docs? Probably should mention any #. configuration that users may want to do for using it with GDM? #. If so, perhaps this section should be moved to a subsection of #. the "Configure" section? #. #: C/gdm.xml:914(para) msgid "" "GDM includes support for publishing user login information with the user and " "login session accounting framework known as ConsoleKit. ConsoleKit is able " "to keep track of all the users currently logged in. In this respect, it can " "be used as a replacement for the utmp or utmpx files that are available on " "most Unix-like Operating Systems." msgstr "" #: C/gdm.xml:922(para) msgid "" "When GDM is about to create a new login process for a user it will call a " "privileged method of ConsoleKit in order to open a new session for this " "user. At this time GDM also provides ConsoleKit with information about this " "user session such as: the user ID, the X11 Display name that will be " "associated with the session, the host-name from which the session originates " "(useful in the case of an XDMCP session), whether or not this session is " "attached, etc. As the entity that initiates the user process, GDM is in a " "unique position to know about the user session and to be trusted to provide " "these bits of information. The use of this privileged method is restricted " "by the use of the D-Bus system message bus security policy." msgstr "" #: C/gdm.xml:936(para) msgid "" "In case a user with an existing session has authenticated at GDM and " "requests to resume that existing session, GDM calls a privileged method of " "ConsoleKit to unlock that session. The exact details of what happens when " "the session receives this unlock signal are undefined and session-specific. " "However, most sessions will unlock a screensaver in response." msgstr "" #: C/gdm.xml:945(para) msgid "" "When the user chooses to log out, or if GDM or the session quit unexpectedly " "the user session will be unregistered from ConsoleKit." msgstr "" #: C/gdm.xml:954(title) msgid "Configuration" msgstr "" #: C/gdm.xml:956(para) msgid "" "GDM has a number of configuration interfaces. These include scripting " "integration points, daemon configuration, greeter configuration, general " "session settings, integration with gnome-settings-daemon configuration, and " "session configuration. These types of integration are described in detail " "below." msgstr "" #: C/gdm.xml:965(title) msgid "Scripting Integration Points" msgstr "" #: C/gdm.xml:967(para) msgid "" "The GDM script integration points can be found in the <etc>/" "gdm/ directory:" msgstr "" #: C/gdm.xml:972(screen) #, no-wrap msgid "" "\n" "Xsession\n" "Init/\n" "PostLogin/\n" "PreSession/\n" "PostSession/\n" msgstr "" #: C/gdm.xml:980(para) msgid "" "The Init, PostLogin, " "PreSession, and PostSession " "scripts all work as described below." msgstr "" #: C/gdm.xml:986(para) msgid "" "For each type of script, the default one which will be executed is called " "\"Default\" and is stored in a directory associated with the script type. So " "the default Init script is <etc>/gdm/" "Init/Default. A per-display script can be provided, and if it " "exists it will be run instead of the default script. Such scripts are stored " "in the same directory as the default script and have the same name as the " "Xserver DISPLAY value for that display. For example, if the <" "Init>/:0 script exists, it will be run for DISPLAY \":0\"." msgstr "" #: C/gdm.xml:998(para) msgid "" "All of these scripts are run with root privilege and return 0 if run " "successfully, and a non-zero return code if there was any failure that " "should cause the login session to be aborted. Also note that GDM will block " "until the scripts finish, so if any of these scripts hang, this will cause " "the login process to also hang." msgstr "" #: C/gdm.xml:1006(para) msgid "" "When the Xserver for the login GUI has been successfully started, but before " "the login GUI is actually displayed, GDM will run the Init script. This script is useful for starting programs that should be " "run while the login screen is showing, or for doing any special " "initialization if required." msgstr "" #: C/gdm.xml:1014(para) msgid "" "After the user has been successfully authenticated GDM will run the " "PostLogin script. This is done before any session setup " "has been done, including before the pam_open_session call. This script is " "useful for doing any session initialization that needs to happen before the " "session starts. For example, you might setup the user's $HOME directory if " "needed." msgstr "" #: C/gdm.xml:1023(para) msgid "" "After the user session has been initialized, GDM will run the " "PreSession script. This script is useful for doing any " "session initialization that needs to happen after the session has been " "initialized. It can be used for session management or accounting, for " "example." msgstr "" #: C/gdm.xml:1031(para) msgid "" "When a user terminates their session, GDM will run the " "PostSession script. Note that the Xserver will have " "been stopped by the time this script is run, so it should not be accessed." msgstr "" #: C/gdm.xml:1038(para) msgid "" "Note that the 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:1045(para) msgid "" "All of the above scripts will set the $RUNNING_UNDER_GDM environment variable to yes. If the scripts " "are also shared with other display managers, this allows you to identify " "when GDM is calling these scripts, so you can run specific code when GDM is " "used." msgstr "" #: C/gdm.xml:1055(title) msgid "Autostart Configuration" msgstr "" #: C/gdm.xml:1057(para) msgid "" "The <share>/gdm/autostart/LoginWindow directory " "contains files in the format specified by the \"FreeDesktop.org Desktop " "Application Autostart Specification\". Standard features in the " "specification may be used to specify programs that should auto-restart or " "only be launched if a GConf configuration value is set, etc." msgstr "" #: C/gdm.xml:1066(para) msgid "" "Any .desktop files in this directory will cause the " "associated program to automatically start with the login GUI greeter. By " "default, GDM is shipped with files which will autostart the gdm-simple-" "greeter login GUI greeter itself, the gnome-power-manager application, the " "gnome-settings-daemon, and the metacity window manager. These programs are " "needed for the greeter program to work. In addition, desktop files are " "provided for starting various AT programs if the configuration values " "specified in the Accessibility Configuration section below are set." msgstr "" #: C/gdm.xml:1080(title) msgid "Xsession Script" msgstr "" #: C/gdm.xml:1082(para) msgid "" "There is also an Xsession script located at " "<etc>/gdm/Xsession which is called between the " "PreSession and the PostSession " "scripts. This script does not support per-display like the other scripts. " "This script is used for actually starting the user session. This script is " "run as the user, and it will run whatever session was specified by the " "Desktop session file the user selected to start." msgstr "" #: C/gdm.xml:1095(title) msgid "Daemon Configuration" msgstr "" #: C/gdm.xml:1097(para) msgid "" "The GDM daemon is configured using the <etc>/gdm/custom." "conf file. Default values are stored in GConf in the " "gdm.schemas file. It is recommended that end-users " "modify the <etc>/gdm/custom.conf file because the " "schemas file may be overwritten when the user updates their system to have a " "newer version of GDM." msgstr "" #: C/gdm.xml:1107(para) msgid "" "Note that older versions of GDM supported additional configuration options " "which are no longer supported in the latest versions of GDM." msgstr "" #: C/gdm.xml:1112(para) msgid "" "The <etc>/gdm/custom.conf file is in the " "keyfile format. Keywords in brackets define group " "sections, strings before an equal sign (=) are keys and the data after equal " "sign represents their value. Empty lines or lines starting with the hash " "mark (#) are ignored." msgstr "" #: C/gdm.xml:1120(para) msgid "" "The file <etc>/gdm/custom.conf supports the " "\"[daemon]\", \"[security]\", and \"[xdmcp]\" group sections. Within each " "group, there are particular key/value pairs that can be specified to modify " "how GDM behaves. For example, to enable timed login and specify the timed " "login user to be a user named \"you\", you would modify the file so it " "contains the following lines:" msgstr "" #: C/gdm.xml:1130(screen) #, no-wrap msgid "" "\n" "[daemon]\n" "TimedLoginEnable=true\n" "TimedLogin=you\n" msgstr "" #: C/gdm.xml:1136(para) msgid "A full list of supported configuration keys follow:" msgstr "" #: C/gdm.xml:1141(title) msgid "[chooser]" msgstr "" #: C/gdm.xml:1145(term) msgid "Multicast" msgstr "" #: C/gdm.xml:1147(synopsis) #, no-wrap msgid "Multicast=false" msgstr "" #: C/gdm.xml:1148(para) msgid "" "If true and IPv6 is enabled, the chooser will send a multicast query to the " "local network and collect responses from the hosts who have joined multicast " "group." msgstr "" #: C/gdm.xml:1157(term) msgid "MulticastAddr" msgstr "" #: C/gdm.xml:1159(synopsis) #, no-wrap msgid "MulticastAddr=ff02::1" msgstr "" #: C/gdm.xml:1160(para) msgid "This is the Link-local multicast address." msgstr "" #: C/gdm.xml:1169(title) msgid "[daemon]" msgstr "" #: C/gdm.xml:1172(term) msgid "TimedLoginEnable" msgstr "" #: C/gdm.xml:1174(synopsis) #, no-wrap msgid "TimedLoginEnable=false" msgstr "" #: C/gdm.xml:1175(para) msgid "" "If the user given in 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. Refer to the \"Security->PAM\" section of the manual for " "more information, or for help if this feature does not seem to work." msgstr "" #: C/gdm.xml:1197(term) msgid "TimedLogin" msgstr "" #: C/gdm.xml:1199(synopsis) #, no-wrap msgid "TimedLogin=" msgstr "" #: C/gdm.xml:1200(para) msgid "" "This is the user that should be logged in after a specified number of " "seconds of inactivity." msgstr "" #: C/gdm.xml:1204(para) C/gdm.xml:1248(para) msgid "" "If the value ends with a vertical bar | (the pipe symbol), then GDM will " "execute the program specified and use whatever value is returned on standard " "out from the program as the user. The program is run with the DISPLAY " "environment variable set so that it is possible to specify the user in a per-" "display fashion. For example if the value is \"/usr/bin/getloginuser|\", " "then the program \"/usr/bin/getloginuser\" will be run to get the user value." msgstr "" #: C/gdm.xml:1218(term) msgid "TimedLoginDelay" msgstr "" #: C/gdm.xml:1220(synopsis) #, no-wrap msgid "TimedLoginDelay=30" msgstr "" #: C/gdm.xml:1221(para) msgid "" "Delay in seconds before the TimedLogin user will be " "logged in." msgstr "" #: C/gdm.xml:1229(term) msgid "AutomaticLoginEnable" msgstr "" #: C/gdm.xml:1231(synopsis) #, no-wrap msgid "AutomaticLoginEnable=false" msgstr "" #: C/gdm.xml:1232(para) msgid "" "If true, the user given in AutomaticLogin should be " "logged in immediately. This feature is like timed login with a delay of 0 " "seconds." msgstr "" #: C/gdm.xml:1241(term) msgid "AutomaticLogin" msgstr "" #: C/gdm.xml:1243(synopsis) #, no-wrap msgid "AutomaticLogin=" msgstr "" #: C/gdm.xml:1244(para) msgid "" "This is the user that should be logged in immediately if " "AutomaticLoginEnable is true." msgstr "" #: C/gdm.xml:1262(term) msgid "User" msgstr "" #: C/gdm.xml:1264(synopsis) #, no-wrap msgid "User=gdm" msgstr "" #: C/gdm.xml:1265(para) msgid "" "The username under which the greeter and other GUI programs are run. Refer " "to the Group configuration key and to the \"Security-" ">GDM User And Group\" section of this document for more information." msgstr "" #: C/gdm.xml:1275(term) msgid "Group" msgstr "" #: C/gdm.xml:1277(synopsis) #, no-wrap msgid "Group=gdm" msgstr "" #: C/gdm.xml:1278(para) msgid "" "The group name under which the greeter and other GUI programs are run. Refer " "to the User configuration key and to the \"Security->" "GDM User And Group\" section of this document for more information." msgstr "" #: C/gdm.xml:1290(title) msgid "Debug Options" msgstr "" #: C/gdm.xml:1293(title) msgid "[debug]" msgstr "" #: C/gdm.xml:1296(term) C/gdm.xml:1427(term) msgid "Enable" msgstr "" #: C/gdm.xml:1298(synopsis) C/gdm.xml:1429(synopsis) #, no-wrap msgid "Enable=false" msgstr "" #: C/gdm.xml:1299(para) msgid "" "To enable debugging, set the debug/Enable key to \"true\" in the " "<etc>/gdm/custom.conf file and restart GDM. Then " "debug output will be sent to the system log file (<var>/log/" "messages or <var>/adm/messages " "depending on your Operating System)." msgstr "" #: C/gdm.xml:1314(title) msgid "Greeter Options" msgstr "" #: C/gdm.xml:1317(title) msgid "[greeter]" msgstr "" #: C/gdm.xml:1320(term) msgid "IncludeAll" msgstr "" #: C/gdm.xml:1322(synopsis) #, no-wrap msgid "IncludeAll=true" msgstr "" #: C/gdm.xml:1323(para) msgid "" "If true, then the face browser will show all users on the local machine. If " "false, the face browser will only show users who have recently logged in." msgstr "" #: C/gdm.xml:1329(para) msgid "" "When this key is true, GDM will call fgetpwent() to get a list of local " "users on the system. Any users with a user id less than 500 (or 100 if " "running on Oracle Solaris) are filtered out. The Face Browser also will " "display any users that have previously logged in on the system (for example " "NIS/LDAP users). It gets this list via calling the ck-history ConsoleKit interface. It will also filter out any users which do " "not have a valid shell (valid shells are any shell that getusershell() " "returns - /sbin/nologin or /bin/false are considered invalid shells even if " "getusershell() returns them)." msgstr "" #: C/gdm.xml:1343(para) msgid "" "If false, then GDM more simply only displays users that have previously " "logged in on the system (local or NIS/LDAP users) by calling the ck-" "history ConsoleKit interface." msgstr "" #: C/gdm.xml:1352(term) msgid "Include" msgstr "" #: C/gdm.xml:1354(synopsis) #, no-wrap msgid "Include=" msgstr "" #: C/gdm.xml:1355(para) msgid "" "Set to a list of users to always include in the Face Browser. This value is " "set to a list of users separated by commas. By default, the value is empty." msgstr "" #: C/gdm.xml:1364(term) msgid "Exclude" msgstr "" #: C/gdm.xml:1366(synopsis) #, no-wrap msgid "Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap" msgstr "" #: C/gdm.xml:1367(para) msgid "" "Set to a list of users to always exclude in the Face Browser. This value is " "set to a list of users separated by commas. Note that the setting in the " "custom.conf overrides the default value, so if you wish " "to add additional users to the list, then you need to set the value to the " "default value with additional users appended to the list." msgstr "" #: C/gdm.xml:1381(title) msgid "Security Options" msgstr "" #: C/gdm.xml:1384(title) msgid "[security]" msgstr "" #: C/gdm.xml:1387(term) msgid "DisallowTCP" msgstr "" #: C/gdm.xml:1389(synopsis) #, no-wrap msgid "DisallowTCP=true" msgstr "" #: C/gdm.xml:1390(para) msgid "" "If true, then always append -nolisten tcp to the " "command line when starting attached Xservers, thus disallowing TCP " "connection. This is a more secure configuration if you are not using remote " "connections." msgstr "" #: C/gdm.xml:1402(title) msgid "XDCMP Support" msgstr "" #: C/gdm.xml:1405(title) msgid "[xdmcp]" msgstr "" #: C/gdm.xml:1408(term) msgid "DisplaysPerHost" msgstr "" #: C/gdm.xml:1410(synopsis) #, no-wrap msgid "DisplaysPerHost=1" msgstr "" #: C/gdm.xml:1411(para) msgid "" "To prevent attackers from filling up the pending queue, GDM will only allow " "one connection for each remote computer. If you want to provide display " "services to computers with more than one screen, you should increase this " "value." msgstr "" #: C/gdm.xml:1418(para) msgid "" "Note that the number of attached DISPLAYS allowed is not limited. Only " "remote connections via XDMCP are limited by this configuration option." msgstr "" #: C/gdm.xml:1430(para) msgid "" "Setting this to true enables XDMCP support allowing remote displays/X " "terminals to be managed by GDM." msgstr "" #: C/gdm.xml:1435(para) msgid "" "gdm listens for requests on UDP port 177. See the Port " "option for more information." msgstr "" #: C/gdm.xml:1440(para) msgid "" "If GDM is compiled to support it, access from remote displays can be " "controlled using the TCP Wrappers library. The service name is " "gdm" msgstr "" #: C/gdm.xml:1446(para) msgid "" "You should add \n" "gdm:.my.domain\n" " to your <etc>/hosts.allow, depending on " "your TCP Wrappers configuration. See the hosts.allow man page for details." msgstr "" #: C/gdm.xml:1457(para) msgid "" "Please note that XDMCP is not a particularly secure protocol and that it is " "a good idea to block UDP port 177 on your firewall unless you really need it." msgstr "" #: C/gdm.xml:1466(term) msgid "HonorIndirect" msgstr "" #: C/gdm.xml:1468(synopsis) #, no-wrap msgid "HonorIndirect=true" msgstr "" #: C/gdm.xml:1469(para) msgid "" "Enables XDMCP INDIRECT choosing (i.e. remote execution of " "gdmchooser) for X-terminals which do not supply their " "own display browser." msgstr "" #: C/gdm.xml:1478(term) msgid "MaxPending" msgstr "" #: C/gdm.xml:1480(synopsis) #, no-wrap msgid "MaxPending=4" msgstr "" #: C/gdm.xml:1481(para) msgid "" "To avoid denial of service attacks, GDM has fixed size queue of pending " "connections. Only MaxPending displays can start at the same time." msgstr "" #: C/gdm.xml:1487(para) msgid "" "Please note that this parameter does not limit the number of remote displays " "which can be managed. It only limits the number of displays initiating a " "connection simultaneously." msgstr "" #: C/gdm.xml:1496(term) msgid "MaxSessions" msgstr "" #: C/gdm.xml:1498(synopsis) #, no-wrap msgid "MaxSessions=16" msgstr "" #: C/gdm.xml:1499(para) msgid "" "Determines the maximum number of remote display connections which will be " "managed simultaneously. I.e. the total number of remote displays that can " "use your host." msgstr "" #: C/gdm.xml:1508(term) msgid "MaxWait" msgstr "" #: C/gdm.xml:1510(synopsis) #, no-wrap msgid "MaxWait=30" msgstr "" #: C/gdm.xml:1511(para) msgid "" "When GDM is ready to manage a display an ACCEPT packet is sent to it " "containing a unique session id which will be used in future XDMCP " "conversations." msgstr "" #: C/gdm.xml:1517(para) msgid "" "GDM will then place the session id in the pending queue waiting for the " "display to respond with a MANAGE request." msgstr "" #: C/gdm.xml:1522(para) msgid "" "If no response is received within MaxWait seconds, GDM will declare the " "display dead and erase it from the pending queue freeing up the slot for " "other displays." msgstr "" #: C/gdm.xml:1531(term) msgid "MaxWaitIndirect" msgstr "" #: C/gdm.xml:1533(synopsis) #, no-wrap msgid "MaxWaitIndirect=30" msgstr "" #: C/gdm.xml:1534(para) msgid "" "The MaxWaitIndirect parameter determines the maximum number of seconds " "between the time where a user chooses a host and the subsequent indirect " "query where the user is connected to the host. When the timeout is exceeded, " "the information about the chosen host is forgotten and the indirect slot " "freed up for other displays. The information may be forgotten earlier if " "there are more hosts trying to send indirect queries then " "MaxPendingIndirect." msgstr "" #: C/gdm.xml:1548(term) msgid "PingIntervalSeconds" msgstr "" #: C/gdm.xml:1550(synopsis) #, no-wrap msgid "PingIntervalSeconds=60" msgstr "" #: C/gdm.xml:1560(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 than one minute. However since in most cases where " "XDMCP would be used (such as terminal labs), a lag of more than 15 or so " "seconds would really mean that the terminal was turned off or restarted and " "you would want to end the session." msgstr "" #: C/gdm.xml:1573(term) msgid "Port" msgstr "" #: C/gdm.xml:1575(synopsis) #, no-wrap msgid "Port=177" msgstr "" #: C/gdm.xml:1576(para) msgid "" "The UDP port number gdm should listen to for XDMCP " "requests. Do not change this unless you know what you are doing." msgstr "" #: C/gdm.xml:1585(term) msgid "Willing" msgstr "" #: C/gdm.xml:1587(synopsis) #, no-wrap msgid "Willing=<etc>/gdm/Xwilling" msgstr "" #: C/gdm.xml:1588(para) msgid "" "When the machine sends a WILLING packet back after a QUERY it sends a string " "that gives the current status of this server. The default message is the " "system ID, but it is possible to create a script that displays customized " "message. If this script does not exist or this key is empty the default " "message is sent. If this script succeeds and produces some output, the first " "line of it's output is sent (and only the first line). It runs at most once " "every 3 seconds to prevent possible denial of service by flooding the " "machine with QUERY packets." msgstr "" #: C/gdm.xml:1607(title) msgid "Simple Greeter Configuration" msgstr "" #: C/gdm.xml:1609(para) msgid "" "The GDM default greeter is called the simple Greeter and is configured via " "GConf. Default values are stored in GConf in the gdm-simple-" "greeter.schemas file. These defaults can be overridden if the " "\"gdm\" user has a writable $HOME directory to store GConf settings. These " "values can be edited using the gconftool-2 or " "gconf-editor programs. The following configuration " "options are supported:" msgstr "" #: C/gdm.xml:1620(title) msgid "Greeter Configuration Keys" msgstr "" #: C/gdm.xml:1623(term) msgid "/apps/gdm/simple-greeter/banner_message_enable" msgstr "" #: C/gdm.xml:1625(synopsis) C/gdm.xml:1646(synopsis) C/gdm.xml:1657(synopsis) #: C/gdm.xml:1722(synopsis) C/gdm.xml:1787(synopsis) C/gdm.xml:1798(synopsis) #: C/gdm.xml:1809(synopsis) C/gdm.xml:1820(synopsis) #, no-wrap msgid "false (boolean)" msgstr "" #: C/gdm.xml:1626(para) msgid "Controls whether the banner message text is displayed." msgstr "" #: C/gdm.xml:1633(term) msgid "/apps/gdm/simple-greeter/banner_message_text" msgstr "" #: C/gdm.xml:1635(synopsis) #, no-wrap msgid "NULL (string)" msgstr "" #: C/gdm.xml:1636(para) msgid "Specifies the text banner message to show on the greeter window." msgstr "" #: C/gdm.xml:1644(term) msgid "/apps/gdm/simple-greeter/disable_restart_buttons" msgstr "" #: C/gdm.xml:1647(para) msgid "Controls whether to show the restart buttons in the login window." msgstr "" #: C/gdm.xml:1655(term) msgid "/apps/gdm/simple-greeter/disable_user_list" msgstr "" #: C/gdm.xml:1658(para) msgid "" "If true, then the face browser with known users is not shown in the login " "window." msgstr "" #: C/gdm.xml:1666(term) msgid "/apps/gdm/simple-greeter/logo_icon_name" msgstr "" #: C/gdm.xml:1668(synopsis) #, no-wrap msgid "computer (string)" msgstr "" #: C/gdm.xml:1669(para) msgid "Set to the themed icon name to use for the greeter logo." msgstr "" #: C/gdm.xml:1676(term) msgid "/apps/gdm/simple-greeter/recent-languages" msgstr "" #: C/gdm.xml:1678(synopsis) C/gdm.xml:1700(synopsis) #, no-wrap msgid "[] (string list)" msgstr "" #: C/gdm.xml:1679(para) msgid "" "Set to a list of languages to be shown by default in the login window. " "Default value is \"[]\". With the default setting only the system default " "language is shown and the option \"Other...\" which pops-up a dialog box " "showing a full list of available languages which the user can select." msgstr "" #: C/gdm.xml:1687(para) msgid "" "Users are not intended to change this setting by hand. Instead GDM keeps " "track of any languages selected in this configuration key, and will show " "them in the language combo box along with the \"Other...\" choice. This way, " "commonly selected languages are easier to select." msgstr "" #: C/gdm.xml:1698(term) msgid "/apps/gdm/simple-greeter/recent-layouts" msgstr "" #: C/gdm.xml:1701(para) msgid "" "Set to a list of keyboard layouts to be shown by default in the login panel. " "Default value is \"[]\". With the default setting only the system default " "keyboard layout is shown and the option \"Other...\" which pops-up a dialog " "box showing a full list of available keyboard layouts which the user can " "select." msgstr "" #: C/gdm.xml:1709(para) msgid "" "Users are not intended to change this setting by hand. Instead GDM keeps " "track of any keyboard layouts selected in this configuration key, and will " "show them in the keyboard layout combo box along with the \"Other...\" " "choice. This way, commonly selected keyboard layouts are easier to select." msgstr "" #: C/gdm.xml:1720(term) msgid "/apps/gdm/simple-greeter/wm_use_compiz" msgstr "" #: C/gdm.xml:1723(para) msgid "" "Controls whether compiz is used as the window manager instead of metacity." msgstr "" #: C/gdm.xml:1733(title) msgid "Accessibility Configuration" msgstr "" #: C/gdm.xml:1735(para) msgid "" "This section describes the accessibility configuration options available in " "GDM." msgstr "" #: C/gdm.xml:1741(title) msgid "GDM Accessibility Dialog And GConf Keys" msgstr "" #: C/gdm.xml:1743(para) msgid "" "The GDM greeter panel at the login screen displays an accessibility icon. " "Clicking on that icon opens the GDM Accessibility Dialog. In the GDM " "Accessibility Dialog, there is a list of checkboxes, so the user can enable " "or disable the associated assistive tools." msgstr "" #: C/gdm.xml:1750(para) msgid "" "The checkboxes that correspond to the on-screen keyboard, screen magnifier " "and screen reader assistive tools act on the three GConf keys that are " "described in the next section of this document. By enabling or disabling " "these checkboxes, the associated GConf key is set to \"true\" or \"false\". " "When the GConf key is set to true, the assistive tools linked to this GConf " "key are launched. When the GConf key is set to \"false\", any running " "assistive tool linked to this GConf key are terminated. These GConf keys are " "not automatically reset to a default state after the user has logged in. " "Consequently, the assistive tools that were running during the last GDM " "login session will automatically be launched at the next GDM login session." msgstr "" #: C/gdm.xml:1764(para) msgid "" "The other checkboxes in the GDM Accessibility Dialog do not have " "corresponding GConf keys because no additional program is launched to " "provide the accessibility features that they offer. These other options " "correspond to accessibility features that are provided by the Xserver, which " "is always running during the GDM session." msgstr "" #: C/gdm.xml:1774(title) msgid "Accessibility GConf Keys" msgstr "" #: C/gdm.xml:1776(para) msgid "" "GDM offers the following GConf keys to control its accessibility features:" msgstr "" #: C/gdm.xml:1782(title) msgid "GDM Configuration Keys" msgstr "" #: C/gdm.xml:1785(term) msgid "/desktop/gnome/interface/accessibility" msgstr "" #: C/gdm.xml:1788(para) msgid "" "Controls whether the Accessibility infrastructure will be started with the " "GDM GUI. This is needed for many accessibility technology programs to work." msgstr "" #: C/gdm.xml:1796(term) msgid "/desktop/gnome/applications/at/screen_magnifier_enabled" msgstr "" #: C/gdm.xml:1799(para) msgid "" "If set, then the assistive tools linked to this GConf key will be started " "with the GDM GUI program. By default this is a screen magnifier application." msgstr "" #: C/gdm.xml:1807(term) msgid "/desktop/gnome/applications/at/screen_keyboard_enabled" msgstr "" #: C/gdm.xml:1810(para) msgid "" "If set, then the assistive tools linked to this GConf key will be started " "with the GDM GUI program. By default this is an on-screen keyboard " "application." msgstr "" #: C/gdm.xml:1818(term) msgid "/desktop/gnome/applications/at/screen_reader_enabled" msgstr "" #: C/gdm.xml:1821(para) msgid "" "If set, then the assistive tools linked to this GConf key will be started " "with the GDM GUI program. By default this is a screen reader application." msgstr "" #: C/gdm.xml:1832(title) msgid "Linking GConf Keys to Accessbility Tools" msgstr "" #: C/gdm.xml:1834(para) msgid "" "For the screen_magnifier_enabled, the screen_keyboard_enabled, and the " "screen_reader_enabled GConf keys, the assistive tool which gets launched " "depends on the desktop files located in the GDM autostart directory as " "described in the \"Autostart Configuration\" section of this manual. Any " "desktop file in the GDM autostart directory can be linked to these GConf key " "via specifying that GConf key in the AutostartCondition value in the desktop " "file. So the exact AutostartCondition line in the desktop file could be one " "of the following:" msgstr "" #: C/gdm.xml:1846(screen) #, no-wrap msgid "" "\n" "AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n" "AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled\n" "AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled\n" msgstr "" #: C/gdm.xml:1852(para) msgid "" "When an accessibility key is true, then any program which is linked to that " "key in a GDM autostart desktop file will be launched (unless the Hidden key " "is set to true in that desktop file). A single GConf key can even start " "multiple assistive tools if there are multiple desktop files with this " "AutostartCondition in the GDM autostart directory." msgstr "" #: C/gdm.xml:1862(title) msgid "Example Of Modifying Accessibility Tool Configuration" msgstr "" #: C/gdm.xml:1864(para) msgid "" "For example, if GNOME is distributed with GOK as the default on-screen " "keyboard, then this could be replaced with a different program if desired. " "To replace GOK with the on-screen keyboard application \"onboard\" and " "additionally activate the assistive tool \"mousetweaks\" for dwelling " "support, then the following configuration is needed." msgstr "" #: C/gdm.xml:1872(para) msgid "" "Create a desktop file for onboard and a second one for mousetweaks; for " "example, onboard.desktop and mousetweaks.desktop. These files must be placed " "in the GDM autostart directory and be in the format as explained in the " "\"Autostart Configuration\" section of this document." msgstr "" #: C/gdm.xml:1880(para) msgid "The following is an example onboard.desktop file:" msgstr "" #: C/gdm.xml:1884(screen) #, no-wrap msgid "" "\n" "[Desktop Entry]\n" "Encoding=UTF-8\n" "Name=Onboard Onscreen Keyboard\n" "Comment=Use an on-screen keyboard\n" "TryExec=onboard\n" "Exec=onboard --size 500x180 -x 20 -y 10\n" "Terminal=false\n" "Type=Application\n" "StartupNotify=true\n" "Categories=GNOME;GTK;Accessibility;\n" "AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n" msgstr "" #: C/gdm.xml:1898(para) msgid "" "The following is an example mousetweaks.desktop file:" msgstr "" #: C/gdm.xml:1903(screen) #, no-wrap msgid "" "\n" "[Desktop Entry]\n" "Encoding=UTF-8\n" "Name=Software Mouse-Clicks\n" "Comment=Perform clicks by dwelling with the pointer\n" "TryExec=mousetweaks\n" "Exec=mousetweaks --enable-dwell -m window -c -x 20 -y 240 \n" "Terminal=false\n" "Type=Application\n" "StartupNotify=true\n" "Categories=GNOME;GTK;Accessibility;\n" "AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n" msgstr "" #: C/gdm.xml:1917(para) msgid "" "Note the line with the AutostartCondition that links both desktop files to " "the GConf key for the on-screen keyboard." msgstr "" #: C/gdm.xml:1922(para) msgid "" "To disable GOK from starting, the desktop file for the GOK on-screen " "keyboard must be removed or deactivated. Otherwise onboard and GOK would " "simultaneously be started. This can be done by removing the gok.desktop file " "from the GDM autostart directory, or by adding the \"Hidden=true\" key " "setting to the gok.desktop file." msgstr "" #: C/gdm.xml:1930(para) msgid "" "After making these changes, GOK will no longer be started when the user " "activates the on-screen keyboard in the GDM session; but onboard and " "mousetweaks will instead be launched." msgstr "" #: C/gdm.xml:1939(title) msgid "General Session Settings" msgstr "" #. #. TODO - I think this section should be expanded upon. What specific #. keys are of interest, or would some users be likely to want #. to configure? Also, would be good to be more specific about #. how lock down management is handled. #. #: C/gdm.xml:1948(para) msgid "" "The GDM Greeter uses some of the same framework that your desktop session " "will use. And so, it is influenced by a number of the same GConf settings. " "For each of these settings the Greeter will use the default value unless it " "is specifically overridden by a) GDM's installed mandatory policy b) system " "mandatory policy. GDM installs its own mandatory policy to lock down some " "settings for security." msgstr "" #: C/gdm.xml:1959(title) msgid "GNOME Settings Daemon" msgstr "" #. #. TODO - I think this section should be expanded upon. What specific #. keys are of interest, or would some users be likely to want #. to configure? Also, would be good to give a more complete #. list of plugins that users might want to consider disabling. #. Also, shouldn't we list the sound/active key in the Greeter #. configuration setting? Oddly I do not find this key used #. in anything but the chooser in SVN. #. #: C/gdm.xml:1972(para) msgid "" "GDM enables the following gnome-settings-daemon plugins: a11y-keyboard, " "background, sound, xsettings." msgstr "" #: C/gdm.xml:1977(para) msgid "" "These are responsible for things like the background image, font and theme " "settings, sound events, etc." msgstr "" #: C/gdm.xml:1982(para) msgid "" "Plugins can also be disabled using GConf. For example, if you want to " "disable the sound plugin then unset the following key: /apps/gdm/" "simple-greeter/settings-manager-plugins/sound/active." msgstr "" #: C/gdm.xml:1990(title) msgid "GDM Session Configuration" msgstr "" #: C/gdm.xml:1992(para) msgid "" "GDM sessions are specified using the FreeDesktop.org Desktop Entry " "Specification, which can be referenced at the following URL: " "http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec." msgstr "" #: C/gdm.xml:1999(para) msgid "" "By default, GDM will install desktop files in the <share>/" "xsessions directory. GDM will search the following directories in " "this order to find desktop files: <etc>/X11/sessions/, <dmconfdir>/Sessions, <" "share>/xsessions, and <share>/gdm/" "BuiltInSessions. By default the <dmconfdir> is set to <etc>/dm/ unless GDM is " "configured to use a different directory via the \"--with-dmconfdir\" option." msgstr "" #: C/gdm.xml:2012(para) msgid "" "A session can be disabled by editing the desktop file and adding a line as " "follows: Hidden=true." msgstr "" #: C/gdm.xml:2017(para) msgid "" "GDM desktop files support a GDM-specific extension, a key named \"X-GDM-" "BypassXsession\". If the key is not specified in a desktop file, the value " "defaults to \"false\". If this key is specified to be \"true\" in a desktop " "file, then GDM will launch the program specified by the desktop file \"Exec" "\" key directly when starting the user session. It will not run the program " "via the <etc>/gdm/Xsession script, which is the " "normal behavior. Since bypassing the <etc>/gdm/Xsession script avoids setting up the user session with the normal system " "and user settings, sessions started this way can be useful for debugging " "problems in the system or user scripts that might be preventing a user from " "being able to start a session." msgstr "" #: C/gdm.xml:2036(title) msgid "GDM User Session and Language Configuration" msgstr "" #: C/gdm.xml:2037(para) msgid "" "The user's default session and language choices are stored in the " "~/.dmrc file. When a user logs in for the first time, " "this file is created with the user's initial choices. The user can change " "these default values by simply changing to a different value when logging " "in. GDM will remember this change for subsequent logins." msgstr "" #: C/gdm.xml:2045(para) msgid "" "The ~/.dmrc file is in the standard INI format. It has one section called [Desktop] " "which has two keys: Session and Language." msgstr "" #: C/gdm.xml:2052(para) msgid "" "The Session key specifies the basename of the session " ".desktop file that the user wishes to normally use " "without the .desktop extension. The Language key specifies the language that the user wishes to use by default. " "If either of these keys is missing, the system default is used. The file " "would normally look as follows:" msgstr "" #: C/gdm.xml:2061(screen) #, no-wrap msgid "" "\n" "[Desktop]\n" "Session=gnome\n" "Language=cs_CZ.UTF-8\n" msgstr "" #: C/gdm.xml:2073(title) msgid "GDM Commands" msgstr "" #: C/gdm.xml:2076(title) msgid "GDM Root User Commands" msgstr "" #: C/gdm.xml:2078(para) msgid "" "The GDM package provides the following commands in sbindir intended to be run by the root user:" msgstr "" #: C/gdm.xml:2084(title) C/gdm.xml:2099(title) msgid "" "gdm and gdm-binary Command Line Options" msgstr "" #: C/gdm.xml:2087(para) msgid "" "The gdm command is really just a script which runs the " "gdm-binary, passing along any options. Before launching " "gdm-binary, the gdm wrapper script will source the " "<etc>/profile file to set the standard system " "environment variables. In order to better support internationalization, it " "will also set the LC_MESSAGES environment variable to LANG if neither " "LC_MESSAGES or LC_ALL are set. The gdm-binary is the " "actual GDM daemon." msgstr "" #: C/gdm.xml:2103(term) msgid "-?, --help" msgstr "" #: C/gdm.xml:2105(para) msgid "Gives a brief overview of the command line options." msgstr "" #: C/gdm.xml:2112(term) msgid "--fatal-warnings" msgstr "" #: C/gdm.xml:2114(para) msgid "Make all warnings cause GDM to exit." msgstr "" #: C/gdm.xml:2121(term) msgid "--timed-exit" msgstr "" #: C/gdm.xml:2123(para) msgid "Exit after 30 seconds. Useful for debugging." msgstr "" #: C/gdm.xml:2130(term) msgid "--version" msgstr "" #: C/gdm.xml:2132(para) msgid "Print the version of the GDM daemon." msgstr "" #: C/gdm.xml:2141(title) msgid "gdm-restart Command Line Options" msgstr "" #: C/gdm.xml:2143(para) msgid "" "gdm-restart stops and restarts GDM by sending the GDM " "daemon a HUP signal. This command will immediately terminate all sessions " "and log out users currently logged in with GDM." msgstr "" #: C/gdm.xml:2151(title) msgid "gdm-safe-restart Command Line Options" msgstr "" #: C/gdm.xml:2153(para) msgid "" "gdm-safe-restart stops and restarts GDM by sending the " "GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out." msgstr "" #: C/gdm.xml:2161(title) msgid "gdm-stop Command Line Options" msgstr "" #: C/gdm.xml:2163(para) msgid "" "gdm-stop stops GDM by sending the GDM daemon a TERM " "signal." msgstr "" #: C/gdm.xml:2174(title) msgid "Troubleshooting" msgstr "" #. #. TODO - any other tips we should add? Might be useful to highlight any #. common D-Bus configuration issues? #. #: C/gdm.xml:2182(para) msgid "" "This section discusses helpful tips for getting GDM working. In general, if " "you have a problem using GDM, you can submit a bug or send an email to the " "gdm-list mailing list. Information about how to do this is in the " "Introduction section of the document." msgstr "" #: C/gdm.xml:2189(para) msgid "" "If GDM is failing to work properly, it is always a good idea to include " "debug information. To enable debugging, set the debug/Enable key to \"true\" " "in the <etc>/gdm/custom.conf file and restart " "GDM. Then use GDM to the point where it fails, and debug output will be sent " "to the system log file (<var>/log/messages or " "<var>/adm/messages depending on your Operating " "System). If you share this output with the GDM community via a bug report or " "email, please only include the GDM related debug information and not the " "entire file since it can be large. If you do not see any GDM syslog output, " "you may need to configure syslog (refer to the syslog man page)." msgstr "" #: C/gdm.xml:2205(title) msgid "GDM Will Not Start" msgstr "" #: C/gdm.xml:2207(para) msgid "" "There are a many problems that can cause GDM to fail to start, but this " "section will discuss a few common problems and how to approach tracking down " "a problem with GDM starting. Some problems will cause GDM to respond with an " "error message or dialog when it tries to start, but it can be difficult to " "track down problems when GDM fails silently." msgstr "" #: C/gdm.xml:2216(para) msgid "" "First make sure that the Xserver is configured properly. The GDM " "configuration file contains a command in the [server-Standard] section that " "is used for starting the Xserver. Verify that this command works on your " "system. Running this command from the console should start the Xserver. If " "it fails, then the problem is likely with your Xserver configuration. Refer " "to your Xserver error log for an idea of what the problem may be. The " "problem may also be that your Xserver requires different command-line " "options. If so, then modify the Xserver command in the GDM configuration " "file so that it is correct for your system." msgstr "" #: C/gdm.xml:2229(para) msgid "" "Also make sure that the /tmp directory has reasonable " "ownership and permissions, and that the machine's file system is not full. " "These problems will cause GDM to fail to start." msgstr "" #: C/gdm.xml:2240(title) msgid "License" msgstr "" #: C/gdm.xml:2241(para) msgid "" "This program is free software; you can redistribute it and/or modify it " "under the terms of the GNU General Public License as published by " "the Free Software Foundation; either version 2 of the License, or (at your " "option) any later version." msgstr "" #: C/gdm.xml:2249(para) msgid "" "This program is distributed in the hope that it will be useful, but WITHOUT " "ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or " "FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public " "License for more details." msgstr "" #: C/gdm.xml:2255(para) msgid "" "A copy of the GNU General Public License is included " "as an appendix to the GNOME Users Guide. You may also " "obtain a copy of the GNU General Public License from " "the Free Software Foundation by visiting their Web site or by writing to
Free " "Software Foundation, Inc. 51 Franklin Street, Fifth FloorBoston, MA02110-1301USA
" msgstr "" #. Put one translator per line, in the form of NAME , YEAR1, YEAR2 #: C/gdm.xml:0(None) msgid "translator-credits" msgstr ""