# Occitan translation of gdm2 documentation. # Copyright (C) 2006-2007 Free Software Foundation, Inc. # This file is distributed under the same license as the gdm documentation package. # # Yannig MARCHEGAY (yannig@marchegay.org) - 2006-2007 # msgid "" msgstr "" "Project-Id-Version: gdm2 doc fr\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2007-06-09 17:20+0200\n" "PO-Revision-Date: 2007-08-21 21:38+0200\n" "Last-Translator: Yannig Marchegay (Kokoyaya) \n" "Language-Team: Occitan (post 1500) \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);" #: ../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:13(title) msgid "Gnome Display Manager Reference Manual" msgstr "" #: ../C/gdm.xml:17(revnumber) msgid "0.0" msgstr "" #: ../C/gdm.xml:18(date) msgid "2007-01" msgstr "" #: ../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 "" #: ../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 "" #: ../C/gdm.xml:43(firstname) msgid "Brian" msgstr "" #: ../C/gdm.xml:43(surname) msgid "Cameron" msgstr "" #: ../C/gdm.xml:45(email) msgid "Brian.Cameron@Sun.COM" msgstr "" #: ../C/gdm.xml:49(firstname) msgid "Bill" msgstr "" #: ../C/gdm.xml:49(surname) msgid "Haneman" msgstr "" #: ../C/gdm.xml:51(email) msgid "Bill.Haneman@Sun.COM" msgstr "" #: ../C/gdm.xml:56(year) msgid "1998" msgstr "1998" #: ../C/gdm.xml:56(year) msgid "1999" msgstr "1999" #: ../C/gdm.xml:56(holder) msgid "Martin K. Petersen" msgstr "" #: ../C/gdm.xml:59(year) msgid "2001" msgstr "2001" #: ../C/gdm.xml:59(year) ../C/gdm.xml:63(year) ../C/gdm.xml:66(year) msgid "2003" msgstr "2003" #: ../C/gdm.xml:59(year) ../C/gdm.xml:66(year) msgid "2004" msgstr "2004" #: ../C/gdm.xml:60(holder) msgid "George Lebl" msgstr "" #: ../C/gdm.xml:63(holder) msgid "Red Hat, Inc." msgstr "" #: ../C/gdm.xml:66(holder) msgid "Sun Microsystems, Inc." msgstr "" #: ../C/gdm.xml:71(releaseinfo) ../C/gdm.xml:80(para) msgid "" "This manual describes version 2.19.2 of the GNOME Display Manager. It was " "last updated on 06/04/2007." msgstr "" #: ../C/gdm.xml:78(title) msgid "Terms and Conventions Used in This Manual" msgstr "" #: ../C/gdm.xml:85(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:90(para) msgid "Configurator - The configuration application (gdmsetup)." msgstr "" #: ../C/gdm.xml:95(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:100(para) msgid "gdm - The Gnome Display Manager daemon (gdm)." msgstr "" #: ../C/gdm.xml:104(para) msgid "" "Greeter - The graphical login window (gdmlogin or " "gdmgreeter)." msgstr "" #: ../C/gdm.xml:109(para) msgid "GTK+ Greeter - The standard login window (gdmlogin)." msgstr "" #: ../C/gdm.xml:113(para) msgid "PAM - Pluggable Authentication Mechanism" msgstr "" #: ../C/gdm.xml:117(para) msgid "Themed Greeter - The themable login window ( gdmgreeter)." msgstr "" #: ../C/gdm.xml:122(para) msgid "XDMCP - X Display Manage Protocol" msgstr "" #: ../C/gdm.xml:126(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:142(title) msgid "Overview" msgstr "" #: ../C/gdm.xml:145(title) msgid "Introduction" msgstr "" #: ../C/gdm.xml:149(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:156(para) msgid "" "Note that GDM is highly configurable, and many configuration settings can " "affect security. Issues to be aware of are highlighted in this document and " "in the GDM Configuration files." msgstr "" #: ../C/gdm.xml:162(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:175(title) msgid "Interface Stability" msgstr "" #: ../C/gdm.xml:179(para) msgid "" "The key/value pairs defined in the GDM configuration files and the location " "of these files are considered \"stable\" interfaces 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, 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:193(para) msgid "" "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:201(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:209(para) msgid "" "If issues are discovered that break compatibility, please file a bug with an " "\"urgent\" priority." msgstr "" #: ../C/gdm.xml:216(title) msgid "The GDM Daemon" msgstr "" #: ../C/gdm.xml:218(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:229(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:236(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:265(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:297(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:307(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:315(title) msgid "Different Display Types" msgstr "" #: ../C/gdm.xml:317(para) msgid "" "GDM supports three different display types: static (local) displays, " "flexible (on-demand) displays, and XDMCP (remote) displays. The \"X Server " "Definitions\" subsection of the \"Configuration\" section explains how the X " "server is configured for different displays." msgstr "" #: ../C/gdm.xml:325(para) msgid "" "Static (local) 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. The \"Local Static X Display " "Configuration\" subsection of the \"Configuration\" section describes how " "Static (local) displays are defined." msgstr "" #: ../C/gdm.xml:335(para) msgid "" "Flexible, or on demand displays are only available to users logged in on the " "console. Starting a flexible display will lock the current user session and " "will show a new login screen over the current running session. If at least " "one flexible display is already running, and the user requests another, then " "a dialog will display showing existing flexible displays. The user can " "choose to switch back to a previous display or start a new flexible display. " "If the user switches back to a previous display, they will need to enter the " "password in the lock screen program to return to their session. The GDM " "configuration file specifies the maximum number of flexible displays allowed " "on the system." msgstr "" #: ../C/gdm.xml:349(para) msgid "" "Flexible displays may be started by running the gdmflexiserver command, or via calling the GDM socket protocol directly. Some lock " "screen programs provide a button to start a new flexible session. This " "allows a user to start a new session even if the screen was left locked. The " "GNOME Fast User Switch applet also uses the socket protocol to provide an " "applet interface on the GNOME panel for managing user displays quickly. " "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)." msgstr "" #: ../C/gdm.xml:362(para) msgid "" "The FlexibleXServers, FirstVT=7, " "VTAllocation, and FlexiReapDelayMinutes configuration settings are used to configure how flexible displays " "operate." msgstr "" #: ../C/gdm.xml:369(para) msgid "" "Nested displays are available to users even if not logged in on the console. " "Nested displays launch a login screen in a window in the user's current " "session. This can be useful if the user has more than one account on a " "machine and wishes to login to the other account without disrupting their " "current session. Nested displays may be started by running the " "gdmflexiserver -n command or via calling the GDM socket " "protocol directly. Nested displays require that the X server supports a " "nested X server command like Xnest or Xephyr. The Xnest " "configuration option is used to configure how nested displays operate" msgstr "" #: ../C/gdm.xml:382(para) msgid "" "The gdmdynamic is similar to gdmflexiserver in the sense that it allows the user to manage displays " "dynamically. However displays started with gdmdynamic are " "treated as local displays, so they are restarted automatically when the " "session exits. This command is intended to be used in multi-user server " "environments (many displays connected to a single server). In other words, " "this command allows the displays to be managed without hardcoding the " "display information in the \"Local Static X Display Configuration\" section " "of the configuration file. This is useful to support the ability of adding " "new displays to the server without needing to restart GDM, for example." msgstr "" #: ../C/gdm.xml:397(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:408(title) msgid "XDMCP" msgstr "" #: ../C/gdm.xml:412(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:421(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:429(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:434(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:444(para) msgid "" "If XDMCP seems to not be working, make sure that all machines are specified " "in /etc/hosts." msgstr "" #: ../C/gdm.xml:449(para) msgid "" "Refer to the \"Security\" section for information about security concerns " "when using XDMCP." msgstr "" #: ../C/gdm.xml:456(title) msgid "Securing Remote Connection Through SSH" msgstr "" #: ../C/gdm.xml:459(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:466(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:476(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:483(title) msgid "The GTK+ Greeter" msgstr "" #: ../C/gdm.xml:485(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:493(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:503(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:511(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:521(title) msgid "The Themed Greeter" msgstr "" #: ../C/gdm.xml:523(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:533(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:543(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:551(title) msgid "The GDM Face Browser" msgstr "" #: ../C/gdm.xml:553(para) msgid "" "GDM supports a face browser which will display a list of users who can login " "and an icon for each user. Starting with version 2.18.1 the " "Browser configuration option must be set to \"true\" " "for this function to be available. In previous versions it was only required " "when using the GTK+ Greeter. When using the Themed Greeter, the Face Browser " "is only available if the GDM theme includes a \"userlist\" item type." msgstr "" #: ../C/gdm.xml:563(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:572(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:585(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:597(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:608(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:616(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:632(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:649(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:658(title) msgid "Logging" msgstr "" #: ../C/gdm.xml:660(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:667(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:679(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:691(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:701(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 application " "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 " "making it necessary to log out and back into their session 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:714(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:728(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:736(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:745(title) msgid "Accessing Files" msgstr "" #: ../C/gdm.xml:747(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:759(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:767(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:778(title) msgid "GDM Performance" msgstr "" #: ../C/gdm.xml:780(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:788(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:809(title) msgid "Security" msgstr "" #: ../C/gdm.xml:812(title) msgid "PAM" msgstr "" #: ../C/gdm.xml:816(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:822(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:829(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:839(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:846(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:856(para) msgid "" "For example, an effective way to implement such an exotic authentication " "mechanism would be to have a daemon running on the server listening to the " "authentication device (e.g. USB key, fingerprint reader, etc.). When the " "device announces that it has received input, then the daemon can set the " "PamStack configuration value using per-display " "configuration, and restart the greeter with the PAM stack that works with " "this device. This avoids needing to hack the display manager code directly " "to support the feature." msgstr "" #: ../C/gdm.xml:871(title) msgid "The GDM User" msgstr "" #: ../C/gdm.xml:873(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:890(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:897(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:908(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:920(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:931(title) msgid "X Server Authentication Scheme" msgstr "" #: ../C/gdm.xml:933(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:945(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:954(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:967(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:984(title) msgid "Firewall Security" msgstr "" #: ../C/gdm.xml:986(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:996(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:1003(para) msgid "" "X is not a very safe protocol for leaving on the net, and XDMCP is even less " "safe." msgstr "" #: ../C/gdm.xml:1010(title) msgid "GDM Security With NFS" msgstr "" #: ../C/gdm.xml:1012(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:1026(title) msgid "XDMCP Security" msgstr "" #: ../C/gdm.xml:1028(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:1034(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:1043(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:1050(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:1058(title) msgid "XDMCP Access Control" msgstr "" #: ../C/gdm.xml:1060(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:1066(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:1073(screen) #, no-wrap msgid "" "\n" "gdm: .evil.domain\n" msgstr "" #: ../C/gdm.xml:1076(para) msgid "to <etc>/hosts.deny. You may also need to add" msgstr "" #: ../C/gdm.xml:1080(screen) #, no-wrap msgid "" "\n" "gdm: .your.domain\n" msgstr "" #: ../C/gdm.xml:1083(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:1092(title) msgid "RBAC (Role Based Access Control)" msgstr "" #: ../C/gdm.xml:1094(para) msgid "" "If GDM is compiled with RBAC support, then the " "RBACSystemCommandKeys configuration option can be used " "to specify the RBAC key to be used to determine if the user has authority to " "use commands. This is supported for the Shutdown, Reboot, Suspend, and " "Custom Commands that appear in the GDM greeter and via the " "gdmflexiserver QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, " "and SET_SAFE_LOGOUT_ACTION commands. The greeter will only display the " "option if the gdm user (specified by the User " "configuration option) has permission via RBAC. Users will only be able to " "use the gdmflexiserver commands if the user has " "permission via RBAC." msgstr "" #: ../C/gdm.xml:1112(title) msgid "Support for ConsoleKit" msgstr "" #: ../C/gdm.xml:1114(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:1122(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:1135(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:1144(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:1149(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:1158(title) msgid "Using gdmsetup To Configure GDM" msgstr "" #: ../C/gdm.xml:1160(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:1171(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 GDM System Defaults Configuration File for additional " "details about each key." msgstr "" #: ../C/gdm.xml:1181(title) msgid "Local Tab" msgstr "" #: ../C/gdm.xml:1183(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:1193(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:1207(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:1217(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. Information about " "the theme's author and copyright are shown for the highlighted theme. The " "\"Remove\" button can be used to delete the highlighted theme. The \"Add\" " "button can be used to add new themes to the system. For a new theme to be " "added it must be in tar or compressed tar format. The \"Background color\" " "displayed when GDM starts (and if the theme has transparent elements) can be " "selected (greeter/GraphicalThemedColor). The \"Theme\" combo box may be set " "to \"Random from selected\" to display a random theme for each login " "(greeter/GraphicalThemeRand and greeter/GraphicalThemes). To use random " "themes, select each theme that you wish to be displayed. By default this " "combobox is set to \"Selected only\", so that only a single theme may be " "selected and be used." msgstr "" #: ../C/gdm.xml:1239(para) msgid "" "If the \"Style\" choice is \"Themed with face browser\", then the " "gdmgreeter program is used as the GUI (daemon/Greeter) " "and the face browser is turned on (greeter/Browser) if supported by the " "theme. The Face Browser is explained in the Overview section. Otherwise, the " "choices are the same as when the \"Style\" choice is \"Themed\". Additional " "setup in the Users tab may be necessary to choose which users appear in the " "Face Browser." msgstr "" #: ../C/gdm.xml:1250(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:1267(title) msgid "Remote Tab" msgstr "" #: ../C/gdm.xml:1269(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). The user may specify to use either the same " "greeter as used on the Local tab, or the other Greeter program. If the Face " "Browser setting is true on the Local tab, then it will also be true for the " "Remote tab. If the Face Browser setting is false on the Local tab, then it " "will also be false for the Remote tab. 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:1286(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:1296(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:1304(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:1312(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:1328(title) msgid "Accessibility Tab" msgstr "" #: ../C/gdm.xml:1330(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:1347(title) msgid "Security Tab" msgstr "" #: ../C/gdm.xml:1349(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 into 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:1364(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 X server\" " "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:1377(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:1386(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 X server, whether " "the server type will \"Launch\" (server/chooser) the greeter or chooser GUI " "after starting the X server, 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:1396(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:1408(title) msgid "Users Tab" msgstr "" #: ../C/gdm.xml:1410(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:1428(title) msgid "Configuration" msgstr "" #: ../C/gdm.xml:1430(para) msgid "" "GDM has powerful configuration management. System default configuration is " "stored in the GDM System Defaults Configuration File and user changes to the " "default configuration are stored in the GDM Custom Configuration File. This " "allows sysadmins to store the GDM System Defaults Configuration File on a " "shared filesystem, so a single file can be used to control configuration for " "multiple machines. GDM also supports per-display configuration for GUI-" "related keys." msgstr "" #: ../C/gdm.xml:1440(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:1452(para) msgid "" "Aside from the GDM System Defaults Configuration File, the other GDM " "configuration files are located, by default, in the <etc>/" "gdm/ folder or its subdirectories. Note that the location of many " "configuration files are defined in the GDM configuration files, so check the " "GDM System Defaults Configuration File and the GDM Custom Configuration File " "if the files are not in the locations specified in this document." msgstr "" #: ../C/gdm.xml:1462(para) msgid "Listing of the config directory contents:" msgstr "" #: ../C/gdm.xml:1466(screen) #, no-wrap msgid "" "\n" "custom.conf\n" "locale.alias\n" "Xsession\n" "XKeepsCrashing\n" "modules/\n" "Init/\n" "PostLogin/\n" "PreSession/\n" "PostSession/\n" msgstr "" #: ../C/gdm.xml:1478(para) msgid "" "locale.alias is a file which looks much like the system " "locale alias but, in fact, is not the same. This is a list of all languages " "that may be on your system. All languages are checked to see if they exist " "before displaying them in the Language Selection dialog in the login GUI. " "Only those that exist are displayed." msgstr "" #: ../C/gdm.xml:1486(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:1497(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:1505(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:1514(para) msgid "" "Files describing available GDM session follow the freedesktop.org desktop " "file specification. The .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:1537(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:1545(para) msgid "" "GDM uses the optional key X-Gdm-XserverArgs in session " "files to specify additional arguments to be passed to the X server. For " "example, the entry X-Gdm-XserverArgs=-depth 16 will " "start the X server with a color depth of 16 bits. Any such additional " "arguments are ignored when using a Nested display (when GDM is launched in a " "window)." msgstr "" #: ../C/gdm.xml:1556(title) msgid "The Script Directories" msgstr "" #: ../C/gdm.xml:1558(para) msgid "" "In this section we will explain the Init, " "PostLogin, PreSession and " "PostSession directories as they are very similar." msgstr "" #: ../C/gdm.xml:1564(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:1582(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:1589(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:1603(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:1618(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:1631(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:1656(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:1663(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:1677(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:1687(title) msgid "" "The Configuration Files - GDM System Defaults Configuration File and GDM " "Custom Configuraiton File" msgstr "" #: ../C/gdm.xml:1690(para) msgid "" "GDM uses two configuration files: the GDM System Defaults Configuration File " "(<share>/gdm/defaults.conf) and the GDM Custom " "Configuration File (<etc>/gdm/custom.conf). The " "GDM System Defaults File contains the default configuration choices for GDM, " "and should not be modified by the user. The GDM Custom Configuration File is " "where users may specify their custom configuration choices. If a " "configuration option is not defined in either file, GDM will default to the " "value described in the comments in the GDM System Defaults Configuration " "File." msgstr "" #: ../C/gdm.xml:1703(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 GDM System Defaults Configuration File for additional " "information about each configuration setting." msgstr "" #: ../C/gdm.xml:1710(para) msgid "" "GDM also supports per-display configuration for parameters in the \"gui\", " "\"greeter\" sections of the configuration file Also the security/PamStack " "key may be customized per-display. Per-display configuration is specified by " "creating a file named <etc>/gdm/custom.conf<display " "num>. In this file the section and keys to use on this display " "can be specified. 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:1723(para) msgid "" "To change configuration by hand, edit the GDM Custom Configuration File or " "per-display configuration file and make sure the keyname=value pair you want " "is included in the appropriate section. For example, to change the value for " "the \"Greeter\" key in the \"daemon\" section, make sure the daemon section " "of the GDM Custom Configuration File or per-display configuration file " "includes the \"[daemon]\" section followed by the key and value change " "desired. As in this example:" msgstr "" #: ../C/gdm.xml:1734(screen) #, no-wrap msgid "" "\n" "[daemon]\n" "Greeter=/usr/lib/gdmgreeter\n" msgstr "" #: ../C/gdm.xml:1739(para) msgid "" "The gdmsetup command can be used to modify the GDM Custom " "Configuration File. Note the gdmsetup is intended to be " "run as root, so users who feel it is insecure to run GUI programs as root " "should edit the configuration files by hand." msgstr "" #: ../C/gdm.xml:1746(para) msgid "" "The GDM daemon --config argument may instead be used to " "specify a different configuration file location. The GDM daemon must be " "restarted to change the configuration file being used. Also when building " "GDM, the location of the configuration files may be specified via the " "--with-defaults-conf and --with-custom-conf configuration options." msgstr "" #: ../C/gdm.xml:1755(para) msgid "" "Previous to GDM 2.13.0.4 only the <etc>/gdm/gdm.conf existed. For best backwards compatibility, this file will be used " "instead of the GDM Custom Configuration File if it exists on your system. If " "upgrading to the new version of GDM, \"make install\" will check to see if " "the <etc>/gdm/gdm.conf file is different than the " "<etc>/gdm/factory-gdm.conf file. If so, the " "<etc>/gdm/gdm.conf file will be automatically " "copied to <etc>/gdm/custom.conf to preserve any " "configuration changes." msgstr "" #: ../C/gdm.xml:1769(para) msgid "" "Distributions should edit the GDM System Defaults Configuration File to " "establish default configuration values, so that they are preserved as " "defaults and not modified by users modifying the GDM Custom Configuration " "File. Note that distributions may modify the GDM System Defaults " "Configuration File on update to improve usability, security, etc. So any " "changes made to this file may be lost." msgstr "" #: ../C/gdm.xml:1778(para) msgid "" "The GDM System Defaults Configuration File and the GDM Custom Configuration " "File 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:1790(para) msgid "The following configuration keys are supported in GDM:" msgstr "" #: ../C/gdm.xml:1795(title) msgid "Daemon Configuration" msgstr "" #: ../C/gdm.xml:1798(title) msgid "[daemon]" msgstr "" #: ../C/gdm.xml:1801(term) msgid "AddGtkModules" msgstr "" #: ../C/gdm.xml:1803(synopsis) #, no-wrap msgid "AddGtkModules=false" msgstr "" #: ../C/gdm.xml:1804(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:1811(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:1817(para) msgid "" "Usually this is used for accessibility modules. The modules which are loaded " "are specified with the GtkModulesList key." msgstr "" #: ../C/gdm.xml:1826(term) msgid "AllowLogoutActions" msgstr "" #: ../C/gdm.xml:1828(synopsis) #, no-wrap msgid "AllowLogoutActions=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD" msgstr "" #: ../C/gdm.xml:1829(para) msgid "" "Specify which actions are supported by the QUERY_LOGOUT_ACTION, " "SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION gdmflexiserver commands. Valid values are HALT, REBOOT, SHUTDOWN, SUSPEND, and " "CUSTOM_CMD and these should be separated by semicolons. This allows certain " "options to be disabled if desired. Refer to the related " "SystemCommandsInMenu and " "RBACSystemCommandKeys configuration options." msgstr "" #: ../C/gdm.xml:1844(term) msgid "AlwaysLoginCurrentSession" msgstr "" #: ../C/gdm.xml:1846(synopsis) #, no-wrap msgid "AlwaysLoginCurrentSession=true" msgstr "" #: ../C/gdm.xml:1847(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:1859(term) msgid "AutomaticLoginEnable" msgstr "" #: ../C/gdm.xml:1861(synopsis) #, no-wrap msgid "AutomaticLoginEnable=false" msgstr "" #: ../C/gdm.xml:1862(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:1873(term) msgid "AutomaticLogin" msgstr "" #: ../C/gdm.xml:1875(synopsis) #, no-wrap msgid "AutomaticLogin=" msgstr "" #: ../C/gdm.xml:1876(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:1884(para) msgid "The following control chars are recognized within the specified name:" msgstr "" #: ../C/gdm.xml:1889(para) ../C/gdm.xml:3957(para) msgid "%% — the `%' character" msgstr "" #: ../C/gdm.xml:1893(para) msgid "%d — display's name" msgstr "" #: ../C/gdm.xml:1897(para) msgid "%h — display's hostname" msgstr "" #: ../C/gdm.xml:1901(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:1914(term) msgid "BaseXsession" msgstr "" #: ../C/gdm.xml:1916(synopsis) #, no-wrap msgid "BaseXsession=<etc>/gdm/Xsession" msgstr "" #: ../C/gdm.xml:1917(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:1925(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:1938(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:1955(term) msgid "Chooser" msgstr "" #: ../C/gdm.xml:1957(synopsis) #, no-wrap msgid "Chooser=<bin>/gdmchooser" msgstr "" #: ../C/gdm.xml:1958(para) msgid "Full path and name of the chooser executable followed by optional arguments." msgstr "" #: ../C/gdm.xml:1966(term) msgid "Configurator" msgstr "" #: ../C/gdm.xml:1968(synopsis) #, no-wrap msgid "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" msgstr "" #: ../C/gdm.xml:1969(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:1981(term) msgid "ConsoleCannotHandle" msgstr "" #: ../C/gdm.xml:1983(synopsis) #, no-wrap msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" msgstr "" #: ../C/gdm.xml:1984(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:1994(term) msgid "ConsoleNotify" msgstr "" #: ../C/gdm.xml:1996(synopsis) #, no-wrap msgid "ConsoleNotify=true" msgstr "" #: ../C/gdm.xml:1997(para) msgid "" "If false, gdm will not display a message dialog on the console when an error " "happens." msgstr "" #: ../C/gdm.xml:2005(term) msgid "DefaultPath" msgstr "" #: ../C/gdm.xml:2007(synopsis) #, no-wrap msgid "DefaultPath=defaultpath (value set by configure)" msgstr "" #: ../C/gdm.xml:2008(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:2021(term) msgid "DefaultSession" msgstr "" #: ../C/gdm.xml:2023(synopsis) #, no-wrap msgid "DefaultSession=gnome.desktop" msgstr "" #: ../C/gdm.xml:2024(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:2035(term) msgid "DisplayInitDir" msgstr "" #: ../C/gdm.xml:2037(synopsis) #, no-wrap msgid "DisplayInitDir=<etc>/gdm/Init" msgstr "" #: ../C/gdm.xml:2038(para) msgid "" "Directory containing the display init scripts. See the ``The Script " "Directories'' section for more info." msgstr "" #: ../C/gdm.xml:2046(term) msgid "DisplayLastLogin" msgstr "" #: ../C/gdm.xml:2048(synopsis) #, no-wrap msgid "DisplayLastLogin=true" msgstr "" #: ../C/gdm.xml:2049(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:2058(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:2070(term) msgid "DoubleLoginWarning" msgstr "" #: ../C/gdm.xml:2072(synopsis) #, no-wrap msgid "DoubleLoginWarning=true" msgstr "" #: ../C/gdm.xml:2073(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:2083(term) msgid "DynamicXServers" msgstr "" #: ../C/gdm.xml:2085(synopsis) #, no-wrap msgid "DynamicXServers=false" msgstr "" #: ../C/gdm.xml:2086(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:2098(term) msgid "FailsafeXServer" msgstr "" #: ../C/gdm.xml:2100(synopsis) #, no-wrap msgid "FailsafeXServer=" msgstr "" #: ../C/gdm.xml:2101(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:2112(term) msgid "FirstVT" msgstr "" #: ../C/gdm.xml:2114(synopsis) #, no-wrap msgid "FirstVT=7" msgstr "" #: ../C/gdm.xml:2115(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:2125(term) msgid "FlexibleXServers" msgstr "" #: ../C/gdm.xml:2127(synopsis) #, no-wrap msgid "FlexibleXServers=5" msgstr "" #: ../C/gdm.xml:2128(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 nested displays (refer " "to the Xnest configuration option)." msgstr "" #: ../C/gdm.xml:2140(term) msgid "FlexiReapDelayMinutes" msgstr "" #: ../C/gdm.xml:2142(synopsis) #, no-wrap msgid "FlexiReapDelayMinutes=5" msgstr "" #: ../C/gdm.xml:2143(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 nested displays (refer to the Xnest " "configuration option). To turn off this behavior set this value to 0. This " "was added in version 2.5.90.0." msgstr "" #: ../C/gdm.xml:2155(term) msgid "Greeter" msgstr "" #: ../C/gdm.xml:2157(synopsis) #, no-wrap msgid "Greeter=<bin>/gdmlogin" msgstr "" #: ../C/gdm.xml:2158(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:2168(term) msgid "Group" msgstr "" #: ../C/gdm.xml:2170(synopsis) #, no-wrap msgid "Group=gdm" msgstr "" #: ../C/gdm.xml:2171(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:2188(term) msgid "GtkModulesList" msgstr "" #: ../C/gdm.xml:2190(synopsis) #, no-wrap msgid "GtkModulesList=module-1:module-2:..." msgstr "" #: ../C/gdm.xml:2191(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:2202(term) msgid "HaltCommand" msgstr "" #: ../C/gdm.xml:2204(synopsis) #, no-wrap msgid "HaltCommand=<sbin>/shutdown -h now" msgstr "" #: ../C/gdm.xml:2205(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:2218(term) msgid "KillInitClients" msgstr "" #: ../C/gdm.xml:2220(synopsis) #, no-wrap msgid "KillInitClients=true" msgstr "" #: ../C/gdm.xml:2221(para) msgid "" "Determines whether GDM should kill X clients started by the init scripts " "when the user logs in." msgstr "" #: ../C/gdm.xml:2229(term) msgid "LogDir" msgstr "" #: ../C/gdm.xml:2231(synopsis) #, no-wrap msgid "LogDir=<var>/log/gdm" msgstr "" #: ../C/gdm.xml:2232(para) msgid "" "Directory containing the log files for the individual displays. By default " "this is the same as the ServAuthDir." msgstr "" #: ../C/gdm.xml:2240(term) msgid "PreFetchProgram" msgstr "" #: ../C/gdm.xml:2242(synopsis) #, no-wrap msgid "PreFetchProgram=command" msgstr "" #: ../C/gdm.xml:2243(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:2259(term) msgid "PostLoginScriptDir" msgstr "" #: ../C/gdm.xml:2261(synopsis) #, no-wrap msgid "PostLoginScriptDir=<etc>/gdm/PostLogin" msgstr "" #: ../C/gdm.xml:2262(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:2271(term) msgid "PostSessionScriptDir" msgstr "" #: ../C/gdm.xml:2273(synopsis) #, no-wrap msgid "PostSessionScriptDir=<etc>/gdm/PostSession" msgstr "" #: ../C/gdm.xml:2274(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:2282(term) msgid "PreSessionScriptDir" msgstr "" #: ../C/gdm.xml:2284(synopsis) #, no-wrap msgid "PreSessionScriptDir=<etc>/gdm/PreSession" msgstr "" #: ../C/gdm.xml:2285(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:2293(term) ../C/gdm.xml:2295(synopsis) msgid "RBACSystemCommandKeys" msgstr "" #: ../C/gdm.xml:2296(para) msgid "" "Support RBAC (Role Based Access Control) for system commands (Shutdown, " "Reboot, Suspend, etc.). This feature is only functional if GDM is compiled " "with RBAC support. Specify the RBAC key used to determine if the user has " "permission to use the action via the QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, " "and SET_SAFE_LOGOUT_ACTION gdmflexiserver commands. Valid " "actions are HALT, REBOOT, SUSPEND, and CUSTOM_CMD. The greeter will only " "display the command if the gdm user (User configuration " "key) has RBAC permissions to use the action. RBAC keys for multiple actions " "can be specified by separating them with semicolons. The format for each is " "\"Action:RBAC key\". If an action is not specified, it is assumed that all " "users have permission to use this action. For example, a valid value for " "this configuration option would be \"HALT:key.for.halt;REBOOT:key.for.reboot" "\". Refer to the related AllowLogoutActions and " "SystemCommandsInMenu configuration options." msgstr "" #: ../C/gdm.xml:2320(term) msgid "RebootCommand" msgstr "" #: ../C/gdm.xml:2322(synopsis) #, no-wrap msgid "RebootCommand=<sbin>/shutdown -r now" msgstr "" #: ../C/gdm.xml:2323(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:2335(term) msgid "RemoteGreeter" msgstr "" #: ../C/gdm.xml:2337(synopsis) #, no-wrap msgid "RemoteGreeter=<bin>/gdmlogin" msgstr "" #: ../C/gdm.xml:2338(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:2349(term) msgid "RootPath" msgstr "" #: ../C/gdm.xml:2351(synopsis) #, no-wrap msgid "RootPath=defaultpath (value set by configure)" msgstr "" #: ../C/gdm.xml:2352(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:2366(term) msgid "ServAuthDir" msgstr "" #: ../C/gdm.xml:2368(synopsis) #, no-wrap msgid "ServAuthDir=<var>/gdm" msgstr "" #: ../C/gdm.xml:2369(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:2391(term) msgid "SessionDesktopDir" msgstr "" #: ../C/gdm.xml:2393(synopsis) #, no-wrap msgid "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" msgstr "" #: ../C/gdm.xml:2394(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:2404(term) msgid "SoundProgram" msgstr "" #: ../C/gdm.xml:2406(filename) msgid "<bin>/play" msgstr "" #: ../C/gdm.xml:2406(filename) msgid "<bin>/audioplay" msgstr "" #: ../C/gdm.xml:2406(synopsis) #, no-wrap msgid "SoundProgram= (or on Solaris)" msgstr "" #: ../C/gdm.xml:2407(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:2417(term) msgid "StandardXServer" msgstr "" #: ../C/gdm.xml:2419(synopsis) #, no-wrap msgid "StandardXServer=/dir/to/X (value assigned by configuration file)" msgstr "" #: ../C/gdm.xml:2420(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:2431(term) msgid "SuspendCommand" msgstr "" #: ../C/gdm.xml:2433(synopsis) #, no-wrap msgid "SuspendCommand=" msgstr "" #: ../C/gdm.xml:2434(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:2445(term) msgid "SystemCommandsInMenu" msgstr "" #: ../C/gdm.xml:2447(synopsis) #, no-wrap msgid "SuspendCommand=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD" msgstr "" #: ../C/gdm.xml:2448(para) msgid "" "Specify which system commands are available in the greeter menu. Valid " "values are HALT, REBOOT, SHUTDOWN, SUSPEND, and CUSTOM_CMD and these should " "be separated by semicolons. This can be useful if you want to disable some " "options in the menu, but still have them available to authenticated users " "via the SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION gdmflexiserver commands. For example, the GNOME panel uses these commands to " "provide Shutdown, Reboot, and Suspend in the application menu. Therefore if " "you turn off these options in the greeter, these options can still be " "available to users who have authenticated via the GNOME panel. Refer to the " "related AllowLogoutActions and " "RBACSystemCommandKeys configuration options." msgstr "" #: ../C/gdm.xml:2469(term) msgid "TimedLoginEnable" msgstr "" #: ../C/gdm.xml:2471(synopsis) #, no-wrap msgid "TimedLoginEnable=false" msgstr "" #: ../C/gdm.xml:2472(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:2492(term) msgid "TimedLogin" msgstr "" #: ../C/gdm.xml:2494(synopsis) #, no-wrap msgid "TimedLogin=" msgstr "" #: ../C/gdm.xml:2495(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:2507(term) msgid "TimedLoginDelay" msgstr "" #: ../C/gdm.xml:2509(synopsis) #, no-wrap msgid "TimedLoginDelay=30" msgstr "" #: ../C/gdm.xml:2510(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:2518(term) msgid "User" msgstr "" #: ../C/gdm.xml:2520(synopsis) #, no-wrap msgid "User=gdm" msgstr "" #: ../C/gdm.xml:2521(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:2535(term) msgid "UserAuthDir" msgstr "" #: ../C/gdm.xml:2537(synopsis) #, no-wrap msgid "UserAuthDir=" msgstr "" #: ../C/gdm.xml:2538(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:2545(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:2558(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:2569(term) msgid "UserAuthFBDir" msgstr "" #: ../C/gdm.xml:2571(synopsis) #, no-wrap msgid "UserAuthFBDir=/tmp" msgstr "" #: ../C/gdm.xml:2572(para) msgid "" "If GDM fails to update the user's .Xauthority file a " "fallback cookie is created in this directory." msgstr "" #: ../C/gdm.xml:2581(term) msgid "UserAuthFile" msgstr "" #: ../C/gdm.xml:2583(synopsis) #, no-wrap msgid "UserAuthFile=.Xauthority" msgstr "" #: ../C/gdm.xml:2584(para) msgid "Name of the file used for storing user cookies." msgstr "" #: ../C/gdm.xml:2591(term) msgid "VTAllocation" msgstr "" #: ../C/gdm.xml:2593(synopsis) #, no-wrap msgid "VTAllocation=true" msgstr "" #: ../C/gdm.xml:2594(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:2606(term) msgid "XKeepsCrashing" msgstr "" #: ../C/gdm.xml:2608(synopsis) #, no-wrap msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" msgstr "" #: ../C/gdm.xml:2609(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:2618(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:2627(term) msgid "Xnest" msgstr "" #: ../C/gdm.xml:2629(synopsis) #, no-wrap msgid "Xnest=<bin>/X11/Xephyr -audit 0" msgstr "" #: ../C/gdm.xml:2630(para) msgid "" "The full path and arguments to the nested X server command, which can be " "Xephyr, Xnest, or similar program. This command is used for starting nested " "displays allowing the user to start new login screens in a nested window. " "Xephyr is recommended since it works best and better supports modern X " "server extensions. Therefore GDM will set the default configuration to use " "Xephyr if available. If Xephyr is not available, then Xnest will be used if " "it is available." msgstr "" #: ../C/gdm.xml:2644(term) msgid "XnestUnscaledFontPath" msgstr "" #: ../C/gdm.xml:2646(synopsis) #, no-wrap msgid "XnestUnscaledFontPath=true" msgstr "" #: ../C/gdm.xml:2647(para) msgid "" "Set to true if the nested X server command program supports the \":unscaled" "\" suffix in the FontPath (passed to nested X server command via the -fp " "argument). Some Xnest (e.g. Xsun Xnest) programs do not, and it is necessary " "to set this to false for such nested X server commands to work with GDM. " "Refer to the Xnest configuration option." msgstr "" #: ../C/gdm.xml:2661(title) msgid "Security Options" msgstr "" #: ../C/gdm.xml:2664(title) msgid "[security]" msgstr "" #: ../C/gdm.xml:2667(term) msgid "AllowRoot" msgstr "" #: ../C/gdm.xml:2669(synopsis) #, no-wrap msgid "AllowRoot=true" msgstr "" #: ../C/gdm.xml:2670(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:2674(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:2684(term) msgid "AllowRemoteRoot" msgstr "" #: ../C/gdm.xml:2686(synopsis) #, no-wrap msgid "AllowRemoteRoot=false" msgstr "" #: ../C/gdm.xml:2687(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:2692(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:2697(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:2708(term) msgid "AllowRemoteAutoLogin" msgstr "" #: ../C/gdm.xml:2710(synopsis) #, no-wrap msgid "AllowRemoteAutoLogin=false" msgstr "" #: ../C/gdm.xml:2711(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:2717(para) msgid "Note that this can make a system quite insecure, and thus is off by default." msgstr "" #: ../C/gdm.xml:2725(term) msgid "CheckDirOwner" msgstr "" #: ../C/gdm.xml:2727(synopsis) #, no-wrap msgid "CheckDirOwner=true" msgstr "" #: ../C/gdm.xml:2728(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:2742(term) msgid "SupportAutomount" msgstr "" #: ../C/gdm.xml:2744(synopsis) #, no-wrap msgid "SupportAutomount=false" msgstr "" #: ../C/gdm.xml:2745(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:2757(term) msgid "DisallowTCP" msgstr "" #: ../C/gdm.xml:2759(synopsis) #, no-wrap msgid "DisallowTCP=true" msgstr "" #: ../C/gdm.xml:2760(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:2773(term) msgid "NeverPlaceCookiesOnNFS" msgstr "" #: ../C/gdm.xml:2775(synopsis) #, no-wrap msgid "NeverPlaceCookiesOnNFS=true" msgstr "" #: ../C/gdm.xml:2776(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:2790(term) msgid "PasswordRequired" msgstr "" #: ../C/gdm.xml:2792(synopsis) #, no-wrap msgid "PasswordRequired=false" msgstr "" #: ../C/gdm.xml:2793(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:2809(term) msgid "RelaxPermissions" msgstr "" #: ../C/gdm.xml:2811(synopsis) #, no-wrap msgid "RelaxPermissions=0" msgstr "" #: ../C/gdm.xml:2812(para) msgid "" "By default GDM ignores files and directories writable to other users than " "the owner." msgstr "" #: ../C/gdm.xml:2817(para) msgid "" "Changing the value of RelaxPermissions makes it possible to alter this " "behavior:" msgstr "" #: ../C/gdm.xml:2822(para) msgid "0 - Paranoia option. Only accepts user owned files and directories." msgstr "" #: ../C/gdm.xml:2826(para) msgid "1 - Allow group writable files and directories." msgstr "" #: ../C/gdm.xml:2829(para) msgid "2 - Allow world writable files and directories." msgstr "" #: ../C/gdm.xml:2836(term) msgid "RetryDelay" msgstr "" #: ../C/gdm.xml:2838(synopsis) #, no-wrap msgid "RetryDelay=1" msgstr "" #: ../C/gdm.xml:2839(para) msgid "" "The number of seconds GDM should wait before reactivating the entry field " "after a failed login." msgstr "" #: ../C/gdm.xml:2847(term) msgid "UserMaxFile" msgstr "" #: ../C/gdm.xml:2849(synopsis) #, no-wrap msgid "UserMaxFile=65536" msgstr "" #: ../C/gdm.xml:2850(para) msgid "" "GDM will refuse to read/write files bigger than this number (specified in " "bytes)." msgstr "" #: ../C/gdm.xml:2855(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:2868(title) msgid "XDCMP Support" msgstr "" #: ../C/gdm.xml:2871(title) msgid "[xdmcp]" msgstr "" #: ../C/gdm.xml:2874(term) msgid "DisplaysPerHost" msgstr "" #: ../C/gdm.xml:2876(synopsis) #, no-wrap msgid "DisplaysPerHost=1" msgstr "" #: ../C/gdm.xml:2877(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:2885(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:2893(term) ../C/gdm.xml:4140(term) msgid "Enable" msgstr "" #: ../C/gdm.xml:2895(synopsis) ../C/gdm.xml:4142(synopsis) #, no-wrap msgid "Enable=false" msgstr "" #: ../C/gdm.xml:2896(para) msgid "" "Setting this to true enables XDMCP support allowing remote displays/X " "terminals to be managed by GDM." msgstr "" #: ../C/gdm.xml:2901(para) msgid "" "gdm listens for requests on UDP port 177. See the Port " "option for more information." msgstr "" #: ../C/gdm.xml:2906(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:2912(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(5) man page for details." msgstr "" #: ../C/gdm.xml:2923(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:2932(term) msgid "EnableProxy" msgstr "" #: ../C/gdm.xml:2934(synopsis) #, no-wrap msgid "EnableProxy=false" msgstr "" #: ../C/gdm.xml:2935(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:2942(para) msgid "" "Note, however, that this mode will significantly increase the burden on the " "machine hosting the XDMCP sessions" msgstr "" #: ../C/gdm.xml:2946(para) msgid "" "See the FlexiProxy and FlexiProxyDisconnect options for further details on how to configure support for this " "feature." msgstr "" #: ../C/gdm.xml:2955(term) msgid "HonorIndirect" msgstr "" #: ../C/gdm.xml:2957(synopsis) #, no-wrap msgid "HonorIndirect=true" msgstr "" #: ../C/gdm.xml:2958(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:2967(term) msgid "MaxPending" msgstr "" #: ../C/gdm.xml:2969(synopsis) #, no-wrap msgid "MaxPending=4" msgstr "" #: ../C/gdm.xml:2970(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:2976(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:2985(term) msgid "MaxPendingIndirect" msgstr "" #: ../C/gdm.xml:2987(synopsis) #, no-wrap msgid "MaxPendingIndirect=4" msgstr "" #: ../C/gdm.xml:2988(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:2998(term) msgid "MaxSessions" msgstr "" #: ../C/gdm.xml:3000(synopsis) #, no-wrap msgid "MaxSessions=16" msgstr "" #: ../C/gdm.xml:3001(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:3010(term) msgid "MaxWait" msgstr "" #: ../C/gdm.xml:3012(synopsis) #, no-wrap msgid "MaxWait=30" msgstr "" #: ../C/gdm.xml:3013(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:3019(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:3024(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:3033(term) msgid "MaxWaitIndirect" msgstr "" #: ../C/gdm.xml:3035(synopsis) #, no-wrap msgid "MaxWaitIndirect=30" msgstr "" #: ../C/gdm.xml:3036(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:3050(term) msgid "Port" msgstr "" #: ../C/gdm.xml:3052(synopsis) #, no-wrap msgid "Port=177" msgstr "" #: ../C/gdm.xml:3053(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:3062(term) msgid "PingIntervalSeconds" msgstr "" #: ../C/gdm.xml:3064(synopsis) #, no-wrap msgid "PingIntervalSeconds=15" msgstr "" #: ../C/gdm.xml:3065(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:3073(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:3086(term) msgid "ProxyReconnect" msgstr "" #: ../C/gdm.xml:3088(synopsis) #, no-wrap msgid "FlexiProxyReconnect=" msgstr "" #: ../C/gdm.xml:3089(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:3095(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:3102(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:3111(term) msgid "ProxyXServer" msgstr "" #: ../C/gdm.xml:3113(synopsis) #, no-wrap msgid "ProxyXServer=" msgstr "" #: ../C/gdm.xml:3114(para) msgid "" "The X server command line for a XDMCP proxy. Any nested X server like Xnest, " "Xephyr or Xdmx should work fairly well." msgstr "" #: ../C/gdm.xml:3122(term) msgid "Willing" msgstr "" #: ../C/gdm.xml:3124(synopsis) #, no-wrap msgid "Willing=<etc>/gdm/Xwilling" msgstr "" #: ../C/gdm.xml:3125(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:3143(title) msgid "Common GUI Configuration Options" msgstr "" #: ../C/gdm.xml:3146(title) msgid "[gui]" msgstr "" #: ../C/gdm.xml:3149(term) msgid "AllowGtkThemeChange" msgstr "" #: ../C/gdm.xml:3151(synopsis) #, no-wrap msgid "AllowGtkThemeChange=true" msgstr "" #: ../C/gdm.xml:3152(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:3164(term) msgid "GtkRC" msgstr "" #: ../C/gdm.xml:3166(synopsis) #, no-wrap msgid "GtkRC=" msgstr "" #: ../C/gdm.xml:3167(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:3176(term) msgid "GtkTheme" msgstr "" #: ../C/gdm.xml:3178(synopsis) #, no-wrap msgid "GtkTheme=Default" msgstr "" #: ../C/gdm.xml:3179(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:3188(term) msgid "GtkThemesToAllow" msgstr "" #: ../C/gdm.xml:3190(synopsis) #, no-wrap msgid "GtkThemesToAllow=all" msgstr "" #: ../C/gdm.xml:3191(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:3203(term) msgid "MaxIconWidth" msgstr "" #: ../C/gdm.xml:3205(synopsis) #, no-wrap msgid "MaxIconWidth=128" msgstr "" #: ../C/gdm.xml:3206(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:3215(term) msgid "MaxIconHeight" msgstr "" #: ../C/gdm.xml:3217(synopsis) #, no-wrap msgid "MaxIconHeight=128" msgstr "" #: ../C/gdm.xml:3218(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:3229(title) msgid "Greeter Configuration" msgstr "" #: ../C/gdm.xml:3232(title) msgid "[greeter]" msgstr "" #: ../C/gdm.xml:3235(term) msgid "BackgroundColor" msgstr "" #: ../C/gdm.xml:3237(synopsis) #, no-wrap msgid "BackgroundColor=#76848F" msgstr "" #: ../C/gdm.xml:3238(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:3249(term) msgid "BackgroundProgramInitialDelay" msgstr "" #: ../C/gdm.xml:3251(synopsis) #, no-wrap msgid "BackgroundProgramInitialDelay=30" msgstr "" #: ../C/gdm.xml:3252(para) msgid "" "The background application will be started after at least that many seconds " "of inactivity." msgstr "" #: ../C/gdm.xml:3260(term) msgid "RestartBackgroundProgram" msgstr "" #: ../C/gdm.xml:3262(synopsis) #, no-wrap msgid "RestartBackgroundProgram=true" msgstr "" #: ../C/gdm.xml:3263(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:3273(term) msgid "BackgroundProgramRestartDelay" msgstr "" #: ../C/gdm.xml:3275(synopsis) #, no-wrap msgid "BackgroundProgramRestartDelay=30" msgstr "" #: ../C/gdm.xml:3276(para) msgid "" "The background application will be restarted after at least that many " "seconds of inactivity." msgstr "" #: ../C/gdm.xml:3284(term) msgid "BackgroundImage" msgstr "" #: ../C/gdm.xml:3286(synopsis) #, no-wrap msgid "BackgroundImage=somefile.png" msgstr "" #: ../C/gdm.xml:3287(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:3296(term) msgid "BackgroundProgram" msgstr "" #: ../C/gdm.xml:3298(synopsis) #, no-wrap msgid "BackgroundProgram=<bin>/xeyes" msgstr "" #: ../C/gdm.xml:3299(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:3311(term) msgid "BackgroundRemoteOnlyColor" msgstr "" #: ../C/gdm.xml:3313(synopsis) #, no-wrap msgid "BackgroundRemoteOnlyColor=true" msgstr "" #: ../C/gdm.xml:3314(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:3324(term) msgid "BackgroundScaleToFit" msgstr "" #: ../C/gdm.xml:3326(synopsis) #, no-wrap msgid "BackgroundScaleToFit=true" msgstr "" #: ../C/gdm.xml:3327(para) msgid "Scale background image to fit the screen. This only affects the GTK+ Greeter." msgstr "" #: ../C/gdm.xml:3335(term) msgid "BackgroundType" msgstr "" #: ../C/gdm.xml:3337(synopsis) #, no-wrap msgid "BackgroundType=2" msgstr "" #: ../C/gdm.xml:3338(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:3346(term) msgid "Browser" msgstr "" #: ../C/gdm.xml:3348(synopsis) #, no-wrap msgid "Browser=true" msgstr "" #: ../C/gdm.xml:3349(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:3360(term) msgid "ChooserButton" msgstr "" #: ../C/gdm.xml:3362(synopsis) #, no-wrap msgid "ChooserButton=true" msgstr "" #: ../C/gdm.xml:3363(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:3372(term) msgid "ConfigAvailable" msgstr "" #: ../C/gdm.xml:3374(synopsis) #, no-wrap msgid "ConfigAvailable=false" msgstr "" #: ../C/gdm.xml:3375(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:3387(term) msgid "DefaultFace" msgstr "" #: ../C/gdm.xml:3389(synopsis) #, no-wrap msgid "DefaultFace=<share>/pixmaps/nophoto.png" msgstr "" #: ../C/gdm.xml:3390(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:3402(term) msgid "Include" msgstr "" #: ../C/gdm.xml:3404(synopsis) #, no-wrap msgid "Include=" msgstr "" #: ../C/gdm.xml:3405(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:3417(term) msgid "Exclude" msgstr "" #: ../C/gdm.xml:3419(synopsis) #, no-wrap msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." msgstr "" #: ../C/gdm.xml:3420(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:3433(term) msgid "IncludeAll" msgstr "" #: ../C/gdm.xml:3435(synopsis) #, no-wrap msgid "IncludeAll=false" msgstr "" #: ../C/gdm.xml:3436(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:3452(term) msgid "GlobalFaceDir" msgstr "" #: ../C/gdm.xml:3454(synopsis) #, no-wrap msgid "GlobalFaceDir=<share>/pixmaps/faces/" msgstr "" #: ../C/gdm.xml:3455(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:3461(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:3467(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:3472(para) msgid "" "A user's own icon file will always take precedence over the sysadmin " "provided one." msgstr "" #: ../C/gdm.xml:3480(term) msgid "GraphicalTheme" msgstr "" #: ../C/gdm.xml:3482(synopsis) #, no-wrap msgid "GraphicalTheme=circles" msgstr "" #: ../C/gdm.xml:3483(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:3492(term) msgid "GraphicalThemes" msgstr "" #: ../C/gdm.xml:3494(synopsis) #, no-wrap msgid "GraphicalThemes=circles" msgstr "" #: ../C/gdm.xml:3495(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:3507(term) msgid "GraphicalThemeRand" msgstr "" #: ../C/gdm.xml:3509(synopsis) #, no-wrap msgid "GraphicalThemeRand=false" msgstr "" #: ../C/gdm.xml:3510(para) msgid "" "Whether the graphical greeter will use Only One Theme or Random Theme mode. " "Only One Theme mode uses themes listed by GraphicalTheme, Random Themes mode uses themes listed by " "GraphicalThemes. A value of false sets greeter to use " "Only One Theme mode, a value of true sets the greeter to use Random Theme " "mode." msgstr "" #: ../C/gdm.xml:3522(term) msgid "GraphicalThemeDir" msgstr "" #: ../C/gdm.xml:3524(synopsis) #, no-wrap msgid "GraphicalThemeDir=<share>/gdm/themes/" msgstr "" #: ../C/gdm.xml:3525(para) msgid "The directory where themes for the Themed Greeter are installed." msgstr "" #: ../C/gdm.xml:3533(term) msgid "GraphicalThemedColor" msgstr "" #: ../C/gdm.xml:3535(synopsis) #, no-wrap msgid "GraphicalThemedColor=#76848F" msgstr "" #: ../C/gdm.xml:3536(para) msgid "" "Use this color in the background of the Themed Greeter. This only affects " "the Themed Greeter." msgstr "" #: ../C/gdm.xml:3544(term) msgid "InfoMsgFile" msgstr "" #: ../C/gdm.xml:3546(synopsis) #, no-wrap msgid "InfoMsgFile=/path/to/infofile" msgstr "" #: ../C/gdm.xml:3547(para) msgid "" "If present and /path/to/infofile specifies an existing and readable text " "file (e.g. <etc>/infomsg.txt) the contents of the file will be " "displayed in a modal dialog box before the user is allowed to login. This " "works both with the standard and the themable greeters." msgstr "" #: ../C/gdm.xml:3558(term) msgid "InfoMsgFont" msgstr "" #: ../C/gdm.xml:3560(synopsis) #, no-wrap msgid "InfoMsgFont=fontspec" msgstr "" #: ../C/gdm.xml:3561(para) msgid "" "If present and InfoMsgFile (see above) is used, this specifies the font to " "use when displaying the contents of the InfoMsgFile text file. For example " "fontspec could be Sans 24 to get a sans serif font of size 24 points. This " "works both with the standard and the themable greeters." msgstr "" #: ../C/gdm.xml:3573(term) msgid "LocaleFile" msgstr "" #: ../C/gdm.xml:3575(synopsis) #, no-wrap msgid "LocaleFile=<etc>/gdm/locale.alias" msgstr "" #: ../C/gdm.xml:3576(para) msgid "" "File in format similar to the GNU locale format with entries for all " "supported languages on the system. The format is described above or in a " "comment inside that file." msgstr "" #: ../C/gdm.xml:3585(term) msgid "LockPosition" msgstr "" #: ../C/gdm.xml:3587(synopsis) #, no-wrap msgid "LockPosition=true" msgstr "" #: ../C/gdm.xml:3588(para) msgid "" "If true the position of the login window of the GTK+ Greeter cannot be " "changed even if the title bar is turned on." msgstr "" #: ../C/gdm.xml:3596(term) msgid "Logo" msgstr "" #: ../C/gdm.xml:3598(synopsis) #, no-wrap msgid "Logo=<share>/pixmaps/gnome-logo-large.png" msgstr "" #: ../C/gdm.xml:3599(para) msgid "" "Image file to display in the logo box. The file must be in a gdk-pixbuf " "supported format and it must be readable by the GDM user. If no file is " "specified the logo feature is disabled. This only affects the GTK+ Greeter." msgstr "" #: ../C/gdm.xml:3610(term) msgid "ChooserButtonLogo" msgstr "" #: ../C/gdm.xml:3612(synopsis) #, no-wrap msgid "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" msgstr "" #: ../C/gdm.xml:3613(para) msgid "" "Image file to display in the file chooser button in gdmsetup. This key is modified by gdmsetup and should not " "be manually modified by the user. This only affects the Login Window " "Preferences (gdmsetup)." msgstr "" #: ../C/gdm.xml:3624(term) msgid "MinimalUID" msgstr "" #: ../C/gdm.xml:3626(synopsis) #, no-wrap msgid "MinimalUID=100" msgstr "" #: ../C/gdm.xml:3627(para) msgid "" "The minimal UID that GDM should consider a user. All users with a lower UID " "will be excluded from the face browser. See also Include, Exclude, and IncludeAll." msgstr "" #: ../C/gdm.xml:3638(term) msgid "PositionX" msgstr "" #: ../C/gdm.xml:3640(synopsis) #, no-wrap msgid "PositionX=200" msgstr "" #: ../C/gdm.xml:3641(para) msgid "The horizontal position of the login window of the GTK+ Greeter." msgstr "" #: ../C/gdm.xml:3649(term) msgid "PositionY" msgstr "" #: ../C/gdm.xml:3651(synopsis) #, no-wrap msgid "PositionY=100" msgstr "" #: ../C/gdm.xml:3652(para) msgid "The vertical position of the login window of the GTK+ Greeter." msgstr "" #: ../C/gdm.xml:3660(term) msgid "Quiver" msgstr "" #: ../C/gdm.xml:3662(synopsis) #, no-wrap msgid "Quiver=true" msgstr "" #: ../C/gdm.xml:3663(para) msgid "" "Controls whether gdmlogin should shake the display when " "an incorrect username/password is entered. This only affects the GTK+ " "Greeter." msgstr "" #: ../C/gdm.xml:3673(term) msgid "DefaultRemoteWelcome" msgstr "" #: ../C/gdm.xml:3675(synopsis) #, no-wrap msgid "DefaultRemoteWelcome=true" msgstr "" #: ../C/gdm.xml:3676(para) msgid "" "If set to true, the value \"Welcome to %n\" is used for the " "RemoteWelcome. This value is translated into the " "appropriate language for the user. If set to false, the " "RemoteWelcome setting is used. This string can use the " "same special character sequences as explained in the \"Text Node\" section " "of the \"Themed Greeter\" chapter. This explains the meaning of \"%n\"." msgstr "" #: ../C/gdm.xml:3690(term) msgid "RemoteWelcome" msgstr "" #: ../C/gdm.xml:3692(synopsis) #, no-wrap msgid "RemoteWelcome=Welcome to %n" msgstr "" #: ../C/gdm.xml:3693(para) msgid "" "Controls which text to display next to the logo image in the greeter for " "remote XDMCP sessions. The same expansion is done here as in the " "Welcome string. This string can use the same special " "character sequences as explained in the \"Text Node\" section of the " "\"Themed Greeter\" chapter. chapter." msgstr "" #: ../C/gdm.xml:3706(term) msgid "RunBackgroundProgramAlways" msgstr "" #: ../C/gdm.xml:3708(synopsis) #, no-wrap msgid "RunBackgroundProgramAlways=false" msgstr "" #: ../C/gdm.xml:3709(para) msgid "" "If this is true then the background application is run always, otherwise it " "is only run when the BackgroundType is 0 (None) This " "only affects the GTK+ Greeter." msgstr "" #: ../C/gdm.xml:3719(term) msgid "SetPosition" msgstr "" #: ../C/gdm.xml:3721(synopsis) #, no-wrap msgid "SetPosition=true" msgstr "" #: ../C/gdm.xml:3722(para) msgid "" "If true the position of the login window of the GTK+ Greeter is determined " "by PositionX / PositionY." msgstr "" #: ../C/gdm.xml:3731(term) msgid "ShowGnomeFailsafeSession" msgstr "" #: ../C/gdm.xml:3733(synopsis) #, no-wrap msgid "ShowGnomeFailsafeSession=true" msgstr "" #: ../C/gdm.xml:3734(para) msgid "Should the greeter show the Gnome Failsafe session in th sessions list." msgstr "" #: ../C/gdm.xml:3742(term) msgid "ShowLastSession" msgstr "" #: ../C/gdm.xml:3744(synopsis) #, no-wrap msgid "ShowLastSession=true" msgstr "" #: ../C/gdm.xml:3745(para) msgid "" "Should the greeter show the 'Last' session in the session list. If this is " "off, then GDM is in the so called 'switchdesk' mode which for example Red " "Hat uses. That is, the users can't pick the last session and will just then " "get the default session (see DefaultSession) unless " "then pick something else for this session only. So if this is off, this " "really circumvents saving of the last session." msgstr "" #: ../C/gdm.xml:3758(term) msgid "ShowXtermFailsafeSession" msgstr "" #: ../C/gdm.xml:3760(synopsis) #, no-wrap msgid "ShowXtermFailsafeSession=true" msgstr "" #: ../C/gdm.xml:3761(para) msgid "Should the greeter show the Xterm Failsafe session in the sessions list." msgstr "" #: ../C/gdm.xml:3769(term) msgid "SoundOnLogin" msgstr "" #: ../C/gdm.xml:3771(synopsis) #, no-wrap msgid "SoundOnLogin=true" msgstr "" #: ../C/gdm.xml:3772(para) msgid "" "If true, the greeter will play a sound or beep when it is ready for a login. " "See also the SoundOnLoginFile key. Supported since " "2.5.90.0." msgstr "" #: ../C/gdm.xml:3782(term) msgid "SoundOnLoginSuccess" msgstr "" #: ../C/gdm.xml:3784(synopsis) #, no-wrap msgid "SoundOnLoginSuccess=true" msgstr "" #: ../C/gdm.xml:3785(para) msgid "" "If true, the greeter will play a sound after a successful login attempt. See " "also the SoundOnLoginSuccessFile key." msgstr "" #: ../C/gdm.xml:3794(term) msgid "SoundOnLoginFailure" msgstr "" #: ../C/gdm.xml:3796(synopsis) #, no-wrap msgid "SoundOnLoginFailure=true" msgstr "" #: ../C/gdm.xml:3797(para) msgid "" "If true, the greeter will play a sound after a failed login attempt. See " "also the SoundOnLoginFailureFile key." msgstr "" #: ../C/gdm.xml:3806(term) msgid "SoundOnLoginFile" msgstr "" #: ../C/gdm.xml:3808(synopsis) #, no-wrap msgid "SoundOnLoginFile=/path/to/sound.wav" msgstr "" #: ../C/gdm.xml:3809(para) msgid "" "The file that will be played using the specified sound application (by " "default that is /usr/bin/play) instead of a beep when " "the greeter is ready for a login. See also the SoundOnLogin key and the SoundProgram key. Supported since " "2.5.90.0." msgstr "" #: ../C/gdm.xml:3822(term) msgid "SoundOnLoginSuccessFile" msgstr "" #: ../C/gdm.xml:3824(synopsis) #, no-wrap msgid "SoundOnLoginSuccessFile=/path/to/sound.wav" msgstr "" #: ../C/gdm.xml:3825(para) msgid "" "The file that will be played using the specified sound application (by " "default that is /usr/bin/play) after a successful login " "attempt. See also the SoundOnLoginSuccess key and the " "SoundProgram key." msgstr "" #: ../C/gdm.xml:3836(term) msgid "SoundOnLoginFailureFile" msgstr "" #: ../C/gdm.xml:3838(synopsis) #, no-wrap msgid "SoundOnLoginFailureFile=/path/to/sound.wav" msgstr "" #: ../C/gdm.xml:3839(para) msgid "" "The file that will be played using the specified sound application (by " "default that is /usr/bin/play) after a failed login " "attempt. See also the SoundOnLoginFailure key and the " "SoundProgram key." msgstr "" #: ../C/gdm.xml:3850(term) msgid "SystemMenu" msgstr "" #: ../C/gdm.xml:3852(synopsis) #, no-wrap msgid "SystemMenu=true" msgstr "" #: ../C/gdm.xml:3853(para) msgid "" "Turns the Actions menu (which used to be called System menu) on or off. If " "this is off then one of the actions will be available anywhere. These " "actions include Shutdown, Restart, Configure, XDMCP chooser and such. All of " "those can however be turned off individually. Shutdown, Restart and Suspend " "can be turned off by just setting the corresponding keys to empty. Note that " "the actions menu is only shown on local logins as it would not be safe or " "even desirable on remote logins, so you don't have to worry about remote " "users having any sort of console privileges." msgstr "" #: ../C/gdm.xml:3866(para) msgid "" "Note that if this is off none of the actions will be available even if a " "theme for a graphical greeter mistakenly shows them. Also note that " "sometimes a graphical theme may not show all the available actions as " "buttons and you may have to press F10 to see the menu." msgstr "" #: ../C/gdm.xml:3877(term) msgid "TitleBar" msgstr "" #: ../C/gdm.xml:3879(synopsis) #, no-wrap msgid "TitleBar=true" msgstr "" #: ../C/gdm.xml:3880(para) msgid "Display the title bar in the greeter. This only affects the GTK+ Greeter." msgstr "" #: ../C/gdm.xml:3888(term) msgid "Use24Clock" msgstr "" #: ../C/gdm.xml:3890(synopsis) #, no-wrap msgid "Use24Clock=auto" msgstr "" #: ../C/gdm.xml:3891(para) msgid "" "Select the use of 24 hour clock. Some locales do not support 12 hour format " "(like Finnish, that is fi_FI), and in those locales " "this setting has no effect at all." msgstr "" #: ../C/gdm.xml:3897(para) msgid "" "Possible values are \"auto\" (default), \"true\", and \"false\". If this is " "set to \"auto\" or left empty, then time format is chosen from locale " "settings. Locale settings are based on the language in use, thus it is " "changed by setting environment variables LANGUAGE (GNU extension), LANG, " "LC_MESSAGES or LC_ALL in the GDM's runtime environment. Priorities between " "the mentioned environment variables can be found from your system's C " "library manual." msgstr "" #: ../C/gdm.xml:3912(term) msgid "UseCirclesInEntry" msgstr "" #: ../C/gdm.xml:3914(synopsis) #, no-wrap msgid "UseCirclesInEntry=false" msgstr "" #: ../C/gdm.xml:3915(para) msgid "" "Use circles instead of asterisks in the password entry. This may not work " "with all fonts however." msgstr "" #: ../C/gdm.xml:3923(term) msgid "UseInvisibleInEntry" msgstr "" #: ../C/gdm.xml:3925(synopsis) #, no-wrap msgid "UseInvisibleInEntry=false" msgstr "" #: ../C/gdm.xml:3926(para) msgid "" "Do not show any visual feedback is the password entry. This is the standard " "in console and xdm. Settings this option discards the " "UseCirclesInEntry option." msgstr "" #: ../C/gdm.xml:3936(term) msgid "DefaultWelcome" msgstr "" #: ../C/gdm.xml:3938(synopsis) #, no-wrap msgid "DefaultWelcome=true" msgstr "" #: ../C/gdm.xml:3939(para) msgid "" "If set to true, the value \"Welcome\" is used for the Welcome. This value is translated into the appropriate language for the " "user. If set to false, the Welcome setting is used." msgstr "" #: ../C/gdm.xml:3949(term) msgid "Welcome" msgstr "" #: ../C/gdm.xml:3951(synopsis) #, no-wrap msgid "Welcome=Welcome" msgstr "" #: ../C/gdm.xml:3952(para) msgid "" "Controls which text to display next to the logo image in the standard " "greeter. The following control chars are supported:" msgstr "" #: ../C/gdm.xml:3961(para) msgid "%d — display's hostname" msgstr "" #: ../C/gdm.xml:3965(para) msgid "%h — Fully qualified hostname" msgstr "" #: ../C/gdm.xml:3969(para) msgid "%m — machine (processor type)" msgstr "" #: ../C/gdm.xml:3973(para) msgid "%n — Nodename (i.e. hostname without .domain)" msgstr "" #: ../C/gdm.xml:3977(para) msgid "%r — release (OS version)" msgstr "" #: ../C/gdm.xml:3981(para) msgid "%s — sysname (i.e. OS)" msgstr "" #: ../C/gdm.xml:3985(para) msgid "" "This string is only used for local logins. For remote XDMCP logins we use " "RemoteWelcome." msgstr "" #: ../C/gdm.xml:3990(para) msgid "" "In the Themed Greeter the location of this text depends on the theme. Unless " "the theme uses the stock welcome string somewhere this string will not be " "displayed at all." msgstr "" #: ../C/gdm.xml:4000(term) msgid "XineramaScreen" msgstr "" #: ../C/gdm.xml:4002(synopsis) #, no-wrap msgid "XineramaScreen=0" msgstr "" #: ../C/gdm.xml:4003(para) msgid "" "If the Xinerama extension is active the login window will be centered on " "this physical screen (use 0 for the first screen, 1 for the second...)." msgstr "" #: ../C/gdm.xml:4014(title) msgid "XDCMP Chooser Options" msgstr "" #: ../C/gdm.xml:4017(title) msgid "[chooser]" msgstr "" #: ../C/gdm.xml:4020(term) msgid "AllowAdd" msgstr "" #: ../C/gdm.xml:4022(synopsis) #, no-wrap msgid "AllowAdd=true" msgstr "" #: ../C/gdm.xml:4023(para) msgid "" "If true, allow the user to add arbitrary hosts to the chooser. This way the " "user could connect to any host that responds to XDMCP queries from the " "chooser." msgstr "" #: ../C/gdm.xml:4032(term) msgid "Broadcast" msgstr "" #: ../C/gdm.xml:4034(synopsis) #, no-wrap msgid "Broadcast=true" msgstr "" #: ../C/gdm.xml:4035(para) msgid "" "If true, the chooser will broadcast a query to the local network and collect " "responses. This way the chooser will always show all available managers on " "the network. If you need to add some hosts not local to this network, or if " "you don't want to use a broadcast, you can list them explicitly in the " "Hosts key." msgstr "" #: ../C/gdm.xml:4047(term) msgid "Multicast" msgstr "" #: ../C/gdm.xml:4049(synopsis) #, no-wrap msgid "Multicast=true" msgstr "" #: ../C/gdm.xml:4050(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. If you don't want to send a multicast, you can specify IPv6 address " "in the Hosts key. The host will respond if it is " "listening to XDMCP requests and IPv6 is enabled there." msgstr "" #: ../C/gdm.xml:4062(term) msgid "MulticastAddr" msgstr "" #: ../C/gdm.xml:4064(synopsis) #, no-wrap msgid "MulticastAddr=ff02::1" msgstr "" #: ../C/gdm.xml:4065(para) msgid "This is the Link-local Multicast address and is hardcoded here." msgstr "" #: ../C/gdm.xml:4072(term) msgid "DefaultHostImage" msgstr "" #: ../C/gdm.xml:4074(synopsis) #, no-wrap msgid "DefaultHostImage=<share>/pixmaps/nohost.png" msgstr "" #: ../C/gdm.xml:4075(para) msgid "" "File name for the default host icon. This image will be displayed if no icon " "is specified for a given host. The file must be in a gdk-pixbuf supported " "format and it must be readable for the GDM user." msgstr "" #: ../C/gdm.xml:4085(term) msgid "HostImageDir" msgstr "" #: ../C/gdm.xml:4087(synopsis) #, no-wrap msgid "HostImageDir=<share>/hosts" msgstr "" #: ../C/gdm.xml:4088(para) msgid "" "Repository for host icon files. The sysadmin can place icons for remote " "hosts here and they will appear in gdmchooser." msgstr "" #: ../C/gdm.xml:4094(para) msgid "" "The file name must match the fully qualified name (FQDN) for the host. The " "icons must be stored in gdk-pixbuf supported formats and they must be " "readable to the GDM user." msgstr "" #: ../C/gdm.xml:4104(term) msgid "Hosts" msgstr "" #: ../C/gdm.xml:4106(synopsis) #, no-wrap msgid "Hosts=host1,host2" msgstr "" #: ../C/gdm.xml:4107(para) msgid "" "The hosts which should be listed in the chooser. The chooser will only list " "them if they respond. This is done in addition to broadcast (if " "Broadcast is set), so you need not list hosts on the " "local network. This is useful if your networking setup doesn't allow all " "hosts to be reachable by a broadcast packet." msgstr "" #: ../C/gdm.xml:4119(term) msgid "ScanTime" msgstr "" #: ../C/gdm.xml:4121(synopsis) #, no-wrap msgid "ScanTime=4" msgstr "" #: ../C/gdm.xml:4122(para) msgid "" "Specifies how many seconds the chooser should wait for replies to its " "BROADCAST_QUERY. Really this is only the time in which we expect a reply. We " "will still add hosts to the list even if they reply after this time." msgstr "" #: ../C/gdm.xml:4134(title) msgid "Debug Configuration" msgstr "" #: ../C/gdm.xml:4137(title) msgid "[debug]" msgstr "" #: ../C/gdm.xml:4143(para) msgid "" "Setting to true sends debug ouput to the syslog. This can be useful for " "tracking down problems with GDM. This output tends to be verbose so should " "not be turned on for general use." msgstr "" #: ../C/gdm.xml:4153(term) msgid "Gestures" msgstr "" #: ../C/gdm.xml:4155(synopsis) #, no-wrap msgid "Gestures=false" msgstr "" #: ../C/gdm.xml:4156(para) msgid "" "Setting to true sends debug ouput concerning the accessibility gesture " "listeners to the syslog. This can be useful for tracking down problems with " "them not working properly. This output tends to be verbose so should not be " "turned on for general use." msgstr "" #: ../C/gdm.xml:4169(title) msgid "Custom Commands" msgstr "" #: ../C/gdm.xml:4171(para) msgid "" "You can create up to 10 different commands. Gaps between command numbers are " "allowed and their relative positioning within the section and with respect " "to each other is not important as long as they conform to the permitted " "range of [0-9]." msgstr "" #: ../C/gdm.xml:4180(title) msgid "[customcommand]" msgstr "" #: ../C/gdm.xml:4183(term) msgid "CustomCommand[0-9]" msgstr "" #: ../C/gdm.xml:4185(synopsis) #, no-wrap msgid "CustomCommand[0-9]=" msgstr "" #: ../C/gdm.xml:4186(para) msgid "" "Full path and arguments to command to be executed when user selects " "n-th \"Custom Command\" from the Actions menu. This can " "be a ';' separated list of commands to try. If the value is empty or " "missing, then the custom command is not available. By default this value is " "not enabled, so to enable \"Custom Command\" it must be set to a nonempty " "value. [0-9] represents the CustomCommand suffix and " "can be an integer between 0 and 9." msgstr "" #: ../C/gdm.xml:4201(term) msgid "CustomCommandIsPersistent[0-9]" msgstr "" #: ../C/gdm.xml:4203(synopsis) #, no-wrap msgid "CustomCommandIsPersistent[0-9]=" msgstr "" #: ../C/gdm.xml:4204(para) msgid "" "Specifies if n-th \"Custom Command\" will appear " "outside the login manager, for example on the desktop through the Log Out/" "Shut Down dialogs. If not specified the default value is \"false\". This " "option is only valid if corresponding CustomCommand is " "defined. [0-9] represents CustomCommand suffix and can " "be an integer between 0 and 9." msgstr "" #: ../C/gdm.xml:4218(term) msgid "CustomCommandLabel[0-9]" msgstr "" #: ../C/gdm.xml:4220(synopsis) #, no-wrap msgid "CustomCommandLabel[0-9]=" msgstr "" #: ../C/gdm.xml:4221(para) msgid "" "Specifies the stock label that will be displayed on the n-th \"Custom Command\" buttons and menu items. If not specified the " "default value is \"Custom_[0-9]\". This option is only valid if " "corresponding CustomCommand is defined. [0-9] " "represents CustomCommand suffix and can be an integer " "between 0 and 9. This option can't contain any semicolon characters (i.e. \";" "\")." msgstr "" #: ../C/gdm.xml:4235(term) msgid "CustomCommandLRLabel[0-9]" msgstr "" #: ../C/gdm.xml:4237(synopsis) #, no-wrap msgid "CustomCommandLRLabel[0-9]=" msgstr "" #: ../C/gdm.xml:4238(para) msgid "" "Specifies the stock label that will be displayed on the n-th \"Custom Command\" list items and radio buttons. If not specified " "the default value is \"Execute custom command _[0-9]\". This option is only " "valid if corresponding CustomCommand is defined. [0-9] " "represents CustomCommand suffix and can be an integer " "between 0 and 9." msgstr "" #: ../C/gdm.xml:4252(term) msgid "CustomCommandNoRestart[0-9]" msgstr "" #: ../C/gdm.xml:4254(synopsis) #, no-wrap msgid "CustomCommandNoRestart[0-9]=" msgstr "" #: ../C/gdm.xml:4255(para) msgid "" "Specifies if gdm will be stopped/restarted once n-th " "\"Custom Command\" has been executed. If not specified the default value is " "\"false\". This option is only valid if corresponding " "CustomCommand is defined. [0-9] represents " "CustomCommand suffix and can be an integer between 0 " "and 9. In addition when corresponding CustomCommandIsPersistent is set to true, setting CustomCommandNoRestart to false will place " "corresponding CustomCommand in the Shut Down dialog set " "of actions, setting it to true will place corresponding " "CustomCommand in the Log Out dialog set of actions." msgstr "" #: ../C/gdm.xml:4275(term) msgid "CustomCommandText[0-9]" msgstr "" #: ../C/gdm.xml:4277(synopsis) #, no-wrap msgid "CustomCommandText[0-9]=" msgstr "" #: ../C/gdm.xml:4278(para) msgid "" "Specifies the message that will be displayed on the warning dialog box once " "n-th \"Custom Command\" button/menu item/radio button/" "list item has been activated. If not specified the default value is \"Are " "you sure?\". This option is only valid if corresponding " "CustomCommand is defined. [0-9] represents " "CustomCommand suffix and can be an integer between 0 " "and 9." msgstr "" #: ../C/gdm.xml:4292(term) msgid "CustomCommandTooltip[0-9]" msgstr "" #: ../C/gdm.xml:4294(synopsis) #, no-wrap msgid "CustomCommandTooltip[0-9]=" msgstr "" #: ../C/gdm.xml:4295(para) msgid "" "Specifies the message that will be displayed on tooltips for n-th \"Custom Command\" entries. If not specified the default value is " "\"Execute custom command [0-9]\". This option is only valid if corresponding " "CustomCommand is defined. [0-9] represents " "CustomCommand suffix and can be an integer between 0 " "and 9." msgstr "" #: ../C/gdm.xml:4310(title) msgid "X Server Definitions" msgstr "" #: ../C/gdm.xml:4312(para) msgid "" "To set up X servers, you need to provide GDM with information about the " "installed X servers. You can have as many different definitions as you wish, " "each identified with a unique name. The name Standard " "is required. If you do not specify this server, GDM will assume default " "values for a 'Standard' server and the path given by daemon/" "StandardXServer. Standard is used as the " "default, in situations when no other server has been defined." msgstr "" #: ../C/gdm.xml:4323(para) msgid "" "Servers are defined by sections named server- followed " "by the identifier of this server. This should be a simple ASCII string with " "no spaces. The GUI configuration program allows users to edit the servers " "defined in the GDM configuration files but currently does not allow adding " "or deleting entries. Like normal configuration options, server- sections in the GDM Custom Configuration File override values in " "the GDM System Defaults Configuration File. In other words, if a " "server-Standard section is defined in the GDM Custom " "Configuration File, then that will be used and the section in the GDM System " "Defaults Configuration File will be ignored." msgstr "" #: ../C/gdm.xml:4338(title) msgid "[server-Standard]" msgstr "" #: ../C/gdm.xml:4341(term) msgid "name" msgstr "" #: ../C/gdm.xml:4343(synopsis) #, no-wrap msgid "name=Standard server" msgstr "" #: ../C/gdm.xml:4344(para) msgid "The name that will be displayed to the user." msgstr "" #: ../C/gdm.xml:4351(term) msgid "command" msgstr "" #: ../C/gdm.xml:4353(synopsis) #, no-wrap msgid "command=/path/to/X" msgstr "" #: ../C/gdm.xml:4354(para) msgid "" "The command to execute, with full path to the binary of the X server, and " "any extra arguments needed." msgstr "" #: ../C/gdm.xml:4362(term) msgid "flexible" msgstr "" #: ../C/gdm.xml:4364(synopsis) #, no-wrap msgid "flexible=true" msgstr "" #: ../C/gdm.xml:4365(para) msgid "" "Indicates if this server is available as a choice when a user wishes to run " "a flexible, on demand server." msgstr "" #: ../C/gdm.xml:4373(term) msgid "handled" msgstr "" #: ../C/gdm.xml:4375(synopsis) #, no-wrap msgid "handled=true" msgstr "" #: ../C/gdm.xml:4392(term) msgid "chooser" msgstr "" #: ../C/gdm.xml:4394(synopsis) #, no-wrap msgid "chooser=false" msgstr "" #: ../C/gdm.xml:4395(para) msgid "" "Indicates that GDM should instead of a login window run a chooser on this " "window and allow the user to choose which server to log into." msgstr "" #: ../C/gdm.xml:4406(title) msgid "Local Static X Display Configuration" msgstr "" #: ../C/gdm.xml:4408(para) msgid "" "The static display configuration specifies what displays should be always " "managed by GDM. GDM will restart the X server on the display if it dies, for " "example. There may be as many static displays that are managed as you wish, " "although typically each display is associated with a real display. For " "example, if a machine has two displays (say display \":0\" and display \":1" "\"), then this section can be used to specify that a separate login screen " "be managed for each screen. Each key in the [servers] " "section corresponds to the display number to be managed. Normally there is " "only one key, which is the key 0, which corresponds to " "the display :0." msgstr "" #: ../C/gdm.xml:4423(para) msgid "" "The GUI configuration program allows users to edit the static display " "configuration defined in the GDM configuration files and allows the user to " "add or delete entries. Like normal configuration options, the " "[servers] section in the GDM Custom Configuration File overrides " "values in the GDM System Defaults Configuration File." msgstr "" #: ../C/gdm.xml:4433(title) msgid "[servers]" msgstr "" #: ../C/gdm.xml:4436(term) msgid "<display number>" msgstr "" #: ../C/gdm.xml:4438(synopsis) #, no-wrap msgid "0=Standard" msgstr "" #: ../C/gdm.xml:4439(para) msgid "" "Control section for local displays. Each line indicates the local display " "number and the command that needs to be run to start the X server(s)." msgstr "" #: ../C/gdm.xml:4445(para) msgid "" "The command can either be a path to an X executable, or a name of one of the " "server definitions. This can be followed by some arguments that should be " "passed to the X server when executed. The gdm daemon doesn't enforce the " "numbers to be in order or for them to be \"packed\". They keyword \"inactive" "\" can be used instead of a command to specify that the display should be " "not managed. This can be used in the GDM Custom Configuration File to turn " "off a display that is defined in the GDM System Defaults Configuration File." msgstr "" #: ../C/gdm.xml:4458(para) msgid "" "GDM will splice \"-auth <ServAuthDir>/:n.Xauth :n" "\", where n is the display number. Inside the command line before all other " "arguments before running the X server." msgstr "" #: ../C/gdm.xml:4465(para) msgid "" "On some systems it is necessary for GDM to know on which virtual consoles to " "run the X server. In this case, (if running XFree86) add \"vt7\" to the " "command line, for example, to run on virtual console 7. However on Linux and " "FreeBSD this is normally done automatically if the VTAllocation key is set." msgstr "" #: ../C/gdm.xml:4474(para) msgid "" "Normally you do not need to add a -nolisten tcp flag as " "this is added automatically for local X servers when the " "DisallowTCP option is set." msgstr "" #: ../C/gdm.xml:4484(term) msgid "priority" msgstr "" #: ../C/gdm.xml:4486(synopsis) #, no-wrap msgid "priority=0" msgstr "" #: ../C/gdm.xml:4487(para) msgid "" "Indicates that the X server should be started at a different process " "priority. Values can be any integer value accepted by the setpriority C " "library function (normally between -20 and 20) with 0 being the default. For " "highly interactive applications, -5 yields good responsiveness. The default " "value is 0 and the setpriority function is not called if the value is 0." msgstr "" #: ../C/gdm.xml:4503(title) msgid "Per User Configuration" msgstr "" #: ../C/gdm.xml:4505(para) msgid "" "There are some per user configuration settings that control how GDM behaves. " "GDM is picky about the file ownership and permissions of the user files it " "will access, and will ignore files if they are not owned by the user or " "files that have group/world write permission. It will also ignore the user " "if the user's $HOME directory is not owned by the user or if the user's " "$HOME directory has group/world write permission. files must also be smaller " "than the UserMaxFile value as defined in the GDM " "configuration. If it seems that GDM is not properly accessing user " "configuration settings, the problem is most likely caused by one of these " "checks failing." msgstr "" #: ../C/gdm.xml:4519(para) msgid "" "First there is the ~/.dmrc file. In theory this file " "should be shared between GDM and KDM, so users only have to configure things " "once. This is a standard .ini style configuration file. " "It has one section called [Desktop] which has two keys: " "Session and Language." msgstr "" #: ../C/gdm.xml:4528(para) msgid "" "The Session key specifies the basename of the session " ".desktop file that the user wishes to normally use " "(without the .desktop extension, in other words). The " "Language key specifies the language that the user " "wishes to use by default. If either of these keys is missing, the system " "default is used. The file would normally look as follows:" msgstr "" #: ../C/gdm.xml:4538(screen) #, no-wrap msgid "" "\n" "[Desktop]\n" "Session=gnome\n" "Language=cs_CZ.UTF-8\n" msgstr "" #: ../C/gdm.xml:4544(para) msgid "" "Normally GDM will write this file when the user logs in for the first time, " "and rewrite it if the user chooses to change their default values on a " "subsequent login." msgstr "" #: ../C/gdm.xml:4550(para) msgid "" "If the GDM Face Browser is turned on, then the file $HOME/.face is accessed. This file should be a standard image that GTK+ can " "read, such as PNG or JPEG. It also must be smaller than the " "MaxIconWidth and MaxIconHeight " "values defined in the GDM configuration or it will be ignored. Users can run " "the gdmphotosetup program to specify a face image and it " "will copy the file to the $HOME/.face location and " "scale it so its longest dimension is not larger than the " "MaxIconWidth or MaxIconHeight " "values. gdmphotosetup takes care to not change the aspect " "ratio of the image." msgstr "" #: ../C/gdm.xml:4565(para) msgid "" "Face images can also be placed in the global face directory, which is " "specified by the GlobalFaceDir configuration option " "( normally <share>/pixmaps/faces/) and the " "filename should be the name of the user, optionally with a .png, .jpg, etc. appended." msgstr "" #: ../C/gdm.xml:4576(title) msgid "Controlling GDM" msgstr "" #: ../C/gdm.xml:4578(para) msgid "" "You can control GDM behavior during runtime in several different ways. You " "can either run certain commands, or you can talk to GDM using either a unix " "socket protocol, or a FIFO protocol." msgstr "" #: ../C/gdm.xml:4585(title) msgid "Commands" msgstr "" #: ../C/gdm.xml:4587(para) msgid "" "To stop GDM, you can either send the TERM signal to the main daemon or run " "the gdm-stop command which is in the <" "sbin>/ directory. To restart GDM, you can either send the HUP " "signal to the main daemon or run the gdm-restart command " "which is also in the <sbin>/ directory. To " "restart GDM but only after all the users have logged out, you can either " "send the USR1 signal to the main daemon or run the gdm-safe-" "restart command which is in the <sbin>/ " "directory as well." msgstr "" #: ../C/gdm.xml:4600(para) msgid "" "The gdmflexiserver command can be used to start new " "flexible (on demand) displays if your system supports virtual terminals. " "This command will normally lock the current session with a screensaver so " "that the user can safely walk away from the computer and let someone else " "log in. If more that two flexible displays have started " "gdmflexiserver will display a pop-up dialog allowing the " "user to select which session to continue. The user will normally have to " "enter a password to return to the session. On session exit the system will " "return to the previous virtual terminal. Run gdmflexiserver --help to get a listing of possible options." msgstr "" #: ../C/gdm.xml:4616(title) msgid "The FIFO protocol" msgstr "" #: ../C/gdm.xml:4618(para) msgid "" "GDM also provides a FIFO called .gdmfifo in the " "ServAuthDir directory (usually <var>/" "gdm/.gdmfifo). You must be root to use this protocol, and it is " "mostly used for internal GDM chatter. It is a very simple protocol where you " "just echo a command on a single line to this file. It can be used to tell " "GDM things such as restart, suspend the computer, or restart all X servers " "next time it has a chance (which would be useful from an X configuration " "application)." msgstr "" #: ../C/gdm.xml:4641(title) msgid "Socket Protocol" msgstr "" #: ../C/gdm.xml:4643(para) msgid "" "GDM provides a unix domain socket for communication at /tmp/." "gdm_socket. Using this you can check if GDM is running, the " "version of the daemon, the current displays that are running and who is " "logged in on them, and if GDM supports it on your operating system, also the " "virtual terminals of all the console logins. The gdmflexiserver command uses this protocol, for example, to launch flexible (on-" "demand) displays." msgstr "" #: ../C/gdm.xml:4653(para) msgid "gdmflexiserver accepts the following commands with the --command option:" msgstr "" #: ../C/gdm.xml:4658(screen) #, no-wrap msgid "" "\n" "ADD_DYNAMIC_DISPLAY\n" "ALL_SERVERS\n" "ATTACHED_SERVERS\n" "AUTH_LOCAL\n" "CLOSE\n" "FLEXI_XNEST\n" "FLEXI_XNEST_USER\n" "FLEXI_XSERVER\n" "FLEXI_XSERVER_USER\n" "GET_CONFIG\n" "GET_CONFIG_FILE\n" "GET_CUSTOM_CONFIG_FILE\n" "GET_SERVER_LIST\n" "GET_SERVER_DETAILS\n" "GREETERPIDS\n" "QUERY_LOGOUT_ACTION\n" "QUERY_CUSTOM_CMD_LABELS\n" "QUERY_CUSTOM_CMD_NO_RESTART_STATUS\n" "QUERY_VT\n" "RELEASE_DYNAMIC_DISPLAYS\n" "REMOVE_DYNAMIC_DISPLAY\n" "SERVER_BUSY\n" "SET_LOGOUT_ACTION\n" "SET_SAFE_LOGOUT_ACTION\n" "SET_VT\n" "UPDATE_CONFIG\n" "VERSION\n" msgstr "" #: ../C/gdm.xml:4688(para) msgid "" "These are described in detail below, including required arguments, response " "format, and return codes." msgstr "" #: ../C/gdm.xml:4694(title) msgid "ADD_DYNAMIC_DISPLAY" msgstr "" #: ../C/gdm.xml:4695(screen) #, no-wrap msgid "" "\n" "ADD_DYNAMIC_DISPLAY: Create a new server definition that will\n" " run on the specified display leaving, it\n" " in DISPLAY_CONFIG state.\n" "Supported since: 2.8.0.0\n" "Arguments: <display to run on>=<server>\n" " Where <server> is either a configuration named in the\n" " GDM configuration or a literal command name.\n" "Answers:\n" " OK <display>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 2 = Existing display\n" " 3 = No server string\n" " 4 = Display startup failure\n" " 100 = Not authenticated\n" " 200 = Dynamic Displays not allowed\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:4717(title) msgid "ALL_SERVERS" msgstr "" #: ../C/gdm.xml:4718(screen) #, no-wrap msgid "" "\n" "ALL_SERVERS: List all displays, including console, remote, xnest.\n" " This can, for example, be useful to figure out if\n" " the display you are on is managed by the gdm daemon,\n" " by seeing if it is in the list. It is also somewhat\n" " like the 'w' command but for graphical sessions.\n" "Supported since: 2.4.2.96\n" "Arguments: None\n" "Answers:\n" " OK <server>;<server>;...\n" "\n" " <server> is <display>,<logged in user>\n" "\n" " <logged in user> can be empty in case no one logged in yet\n" "\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:4741(title) msgid "ATTACHED_SERVERS" msgstr "" #: ../C/gdm.xml:4742(screen) #, no-wrap msgid "" "\n" "ATTACHED_SERVERS: List all attached displays. Doesn't list XDMCP\n" " and xnest non-attached displays.\n" "Note: This command used to be named CONSOLE_SERVERS,\n" " which is still recognized for backwards\n" " compatibility. The optional pattern argument\n" " is supported as of version 2.8.0.0.\n" "Supported since: 2.2.4.0\n" "Arguments: <pattern> (optional)\n" " With no argument, all attached displays are returned. The optional\n" " <pattern> is a string that may contain glob characters '*', '?', and\n" " '[]'. Only displays that match the pattern will be returned.\n" "Answers:\n" " OK <server>;<server>;...\n" "\n" " <server> is <display>,<logged in user>,<vt or xnest\n" " display>\n" "\n" " <logged in user> can be empty in case no one logged\n" " in yet, and <vt> can be -1 if it's not known or not\n" " supported (on non-Linux for example). If the display is an\n" " xnest display and is a console one (that is, it is an xnest\n" " inside another console display) it is listed and instead of\n" " vt, it lists the parent display in standard form.\n" "\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:4775(title) msgid "AUTH_LOCAL" msgstr "" #: ../C/gdm.xml:4776(screen) #, no-wrap msgid "" "\n" "AUTH_LOCAL: Setup this connection as authenticated for\n" " FLEXI_SERVER. Because all full blown\n" " (non-nested) displays can be started only from\n" " users logged in locally, and here GDM assumes\n" " only users logged in from GDM. They must pass\n" " the xauth MIT-MAGIC-COOKIE-1 that they were passed\n" " before the connection is authenticated.\n" "Note: The AUTH LOCAL command requires the\n" " --authenticate option, although only\n" " FLEXI XSERVER uses this currently.\n" "Note: Since 2.6.0.6 you can also use a global\n" " <ServAuthDir>/.cookie, which works for all\n" " authentication except for SET_LOGOUT_ACTION and\n" " QUERY_LOGOUT_ACTION and SET_SAFE_LOGOUT_ACTION\n" " which require a logged in display.\n" "Supported since: 2.2.4.0\n" "Arguments: <xauth cookie>\n" " <xauth cookie> is in hex form with no 0x prefix\n" "Answers:\n" " OK\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 100 = Not authenticated\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:4806(title) msgid "CLOSE" msgstr "" #: ../C/gdm.xml:4807(screen) #, no-wrap msgid "" "\n" "CLOSE: Close sockets connection\n" "Supported since: 2.2.4.0\n" "Arguments: None\n" "Answers: None\n" msgstr "" #: ../C/gdm.xml:4816(title) msgid "FLEXI_XNEST" msgstr "" #: ../C/gdm.xml:4817(screen) #, no-wrap msgid "" "\n" "FLEXI_XNEXT: Start a new flexible nested display.\n" "Note: Supported on older version from 2.2.4.0, later\n" " 2.2.4.2, but since 2.3.90.4 you must supply 4\n" " arguments or ERROR 100 will be returned. This\n" " will start the nested X server command using\n" " the XAUTHORITY file supplied and as the uid\n" " same as the owner of that file (and same as\n" " you supply). You must also supply the cookie as\n" " the third argument for this display, to prove\n" " that you indeed are this user. Also this file\n" " must be readable ONLY by this user, that is\n" " have a mode of 0600. If this all is not met,\n" " ERROR 100 is returned.\n" "Note: The cookie should be the MIT-MAGIC-COOKIE-1,\n" " the first one GDM can find in the XAUTHORITY\n" " file for this display. If that's not what you\n" " use you should generate one first. The cookie\n" " should be in hex form.\n" "Supported since: 2.3.90.4\n" "Arguments: <display to run on> <uid of requesting user>\n" " <xauth cookie for the display> <xauth file>\n" "Answers:\n" " OK <display>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 1 = No more flexi servers\n" " 2 = Startup errors\n" " 3 = X failed\n" " 4 = X too busy\n" " 5 = Xnest can't connect\n" " 6 = No server binary\n" " 100 = Not authenticated\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:4856(title) msgid "FLEXI_XNEST_USER" msgstr "" #: ../C/gdm.xml:4857(screen) #, no-wrap msgid "" "\n" "FLEXI_XNEST_USER: Start a new flexible nested display and\n" " initialize the greeter with the given username.\n" "Note: This is a variant of the FLEXI_XNEST command.\n" "Note: The cookie should be the MIT-MAGIC-COOKIE-1,\n" " the first one GDM can find in the XAUTHORITY\n" " file for this display. If that's not what you\n" " use you should generate one first. The cookie\n" " should be in hex form.\n" "Supported since: 2.17.7\n" "Arguments: <username> <display to run on> <uid of requesting\n" " user> <xauth cookie for the display> <xauth file>\n" "Answers:\n" " OK <display>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 1 = No more flexi servers\n" " 2 = Startup errors\n" " 3 = X failed\n" " 4 = X too busy\n" " 5 = Xnest can't connect\n" " 6 = No server binary\n" " 100 = Not authenticated\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:4886(title) msgid "FLEXI_XSERVER" msgstr "" #: ../C/gdm.xml:4887(screen) #, no-wrap msgid "" "\n" "FLEXI_XSERVER: Start a new X flexible display. Only supported on\n" " connection that passed AUTH_LOCAL\n" "Supported since: 2.2.4.0\n" "Arguments: <xserver type>\n" " If no arguments, starts the standard X server\n" "Answers:\n" " OK <display>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 1 = No more flexi servers\n" " 2 = Startup errors\n" " 3 = X failed\n" " 4 = X too busy\n" " 6 = No server binary\n" " 100 = Not authenticated\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:4909(title) msgid "FLEXI_XSERVER_USER" msgstr "" #: ../C/gdm.xml:4910(screen) #, no-wrap msgid "" "\n" "FLEXI_XSERVER_USER: Start a new X flexible display and initialize the\n" " greeter with the given username. Only supported on\n" " connection that passed AUTH_LOCAL\n" "Supported since: 2.17.7 \n" "Arguments: <username> <xserver type>\n" " If no server type specified, starts the standard X server\n" "Answers:\n" " OK <display>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 1 = No more flexi servers\n" " 2 = Startup errors\n" " 3 = X failed\n" " 4 = X too busy\n" " 6 = No server binary\n" " 100 = Not authenticated\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:4933(title) msgid "GET_CONFIG" msgstr "" #: ../C/gdm.xml:4934(screen) #, no-wrap msgid "" "\n" "GET_CONFIG: Get configuration value for key. Useful so\n" " that other applications can request configuration\n" " information from GDM. Any key defined as GDM_KEY_*\n" " in gdm-daemon-config-keys.h is supported. Starting with version\n" " 2.13.0.2, translated keys (such as\n" " \"greeter/GdmWelcome[cs]\" are supported via GET_CONFIG.\n" " Also starting with version 2.13.0.2 it is no longer necessary to\n" " include the default value (i.e. you can use key\n" " \"greeter/IncludeAll\" instead of having to use\n" " \"greeter/IncludeAll=false\". \n" "Supported since: 2.6.0.9\n" "Arguments: <key>\n" "Answers:\n" " OK <value>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 50 = Unsupported key\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:4958(title) msgid "GET_CONFIG_FILE" msgstr "" #: ../C/gdm.xml:4959(screen) #, no-wrap msgid "" "\n" "GET_CONFIG_FILE: Get config file location being used by\n" " the daemon. If the GDM daemon was started\n" " with the --config option, it will return\n" " the value passed in via the argument.\n" "Supported since: 2.8.0.2\n" "Arguments: None\n" "Answers:\n" " OK <full path to GDM configuration file>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:4976(title) msgid "GET_CUSTOM_CONFIG_FILE" msgstr "" #: ../C/gdm.xml:4977(screen) #, no-wrap msgid "" "\n" "GET_CUSTOM_CONFIG_FILE: Get custom config file location being\n" " used by the daemon.\n" "Supported since: 2.14.0.0\n" "Arguments: None\n" "Answers:\n" " OK <full path to GDM custom configuration file>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 1 = File not found\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:4993(title) msgid "GET_SERVER_DETAILS" msgstr "" #: ../C/gdm.xml:4994(screen) #, no-wrap msgid "" "\n" "GET_SERVER_DETAILS: Get detail information for a specific server.\n" "Supported since: 2.13.0.4\n" "Arguments: <server> <key>\n" " Key values include:\n" " NAME - Returns the server name\n" " COMMAND - Returns the server command\n" " FLEXIBLE - Returns \"true\" if flexible, \"false\"\n" " otherwise\n" " CHOOSABLE - Returns \"true\" if choosable, \"false\"\n" " otherwise\n" " HANDLED - Returns \"true\" if handled, \"false\"\n" " otherwise\n" " CHOOSER - Returns \"true\" if chooser, \"false\"\n" " otherwise\n" " PRIORITY - Returns process priority\n" "Answers:\n" " OK <value>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 1 = Server not found\n" " 2 = Key not valid\n" " 50 = Unsupported key\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5023(title) msgid "GET_SERVER_LIST" msgstr "" #: ../C/gdm.xml:5024(screen) #, no-wrap msgid "" "\n" "GET_SERVER_LIST: Get a list of the server sections from\n" " the configuration file.\n" "Supported since: 2.13.0.4\n" "Arguments: None\n" "Answers:\n" " OK <value>;<value>;...\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 1 = No servers found\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5040(title) msgid "GREETERPIDS" msgstr "" #: ../C/gdm.xml:5041(screen) #, no-wrap msgid "" "\n" "GREETERPIDS: List all greeter pids so that one can send HUP\n" " to them for config rereading. Of course one\n" " must be root to do that.\n" "Supported since: 2.3.90.2\n" "Arguments: None\n" "Answers:\n" " OK <pid>;<pid>;...\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5057(title) msgid "QUERY_LOGOUT_ACTION" msgstr "" #: ../C/gdm.xml:5058(screen) #, no-wrap msgid "" "\n" "QUERY_LOGOUT_ACTION: Query which logout actions are possible\n" " Only supported on connections that passed\n" " AUTH_LOCAL.\n" "Supported since: 2.5.90.0\n" "Answers:\n" " OK <action>;<action>;...\n" " Where action is one of HALT, REBOOT, SUSPEND or CUSTOM_CMD[0-9].\n" " An empty list can also be returned if no action is possible.\n" " A '!' is appended to an action if it was already set with\n" " SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION. Note that\n" " SET_LOGOUT_ACTION has precedence over\n" " SET_SAFE_LOGOUT_ACTION.\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 100 = Not authenticated\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5080(title) msgid "QUERY_CUSTOM_CMD_LABELS" msgstr "" #: ../C/gdm.xml:5081(screen) #, no-wrap msgid "" "\n" " QUERY_CUSTOM_CMD_LABELS: Query labels belonging to exported custom\n" " commands Only supported on connections that\n" " passed AUTH_LOCAL.\n" " Supported since: 2.5.90.0\n" " Answers:\n" " OK <label1>;<label2>;...\n" " Where labelX is one of the labels belonging to CUSTOM_CMDX\n" " (where X in [0,GDM_CUSTOM_COMMAND_MAX)). An empty list can\n" " also be returned if none of the custom commands are exported\n" " outside login manager (no CustomCommandIsPersistent options\n" " are set to true). \n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 100 = Not authenticated\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5102(title) msgid "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" msgstr "" #: ../C/gdm.xml:5103(screen) #, no-wrap msgid "" "\n" "QUERY_CUSTOM_CMD_NO_RESTART_STATUS: Query NoRestart config options\n" " for each of custom commands Only\n" " supported on connections that\n" " passed AUTH_LOCAL.\n" "Supported since: 2.5.90.0\n" "Answers:\n" " OK <status>\n" " Where each bit of the status represents NoRestart value for\n" " each of the custom commands.\n" " bit on (1): NoRestart = true, \n" " bit off (0): NoRestart = false.\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 100 = Not authenticated\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5124(title) msgid "QUERY_VT" msgstr "" #: ../C/gdm.xml:5125(screen) #, no-wrap msgid "" "\n" "QUERY_VT: Ask the daemon about which VT we are currently on.\n" " This is useful for logins which don't own\n" " /dev/console but are still console logins. Only\n" " supported on Linux currently, other places will\n" " just get ERROR 8. This is also the way to query\n" " if VT support is available in the daemon in the\n" " first place. Only supported on connections that\n" " passed AUTH_LOCAL.\n" "Supported since: 2.5.90.0\n" "Arguments: None\n" "Answers:\n" " OK <vt number>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 8 = Virtual terminals not supported\n" " 100 = Not authenticated\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5148(title) msgid "RELEASE_DYNAMIC_DISPLAYS" msgstr "" #: ../C/gdm.xml:5149(screen) #, no-wrap msgid "" "\n" "RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in \n" " DISPLAY_CONFIG state\n" "Supported since: 2.8.0.0\n" "Arguments: <display to release>\n" "Answers:\n" " OK <display>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 1 = Bad display number\n" " 100 = Not authenticated\n" " 200 = Dynamic Displays not allowed\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5166(title) msgid "REMOVE_DYNAMIC_DISPLAY" msgstr "" #: ../C/gdm.xml:5167(screen) #, no-wrap msgid "" "\n" "REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server\n" " and purging the display configuration\n" "Supported since: 2.8.0.0\n" "Arguments: <display to remove>\n" "Answers:\n" " OK <display>\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 1 = Bad display number\n" " 100 = Not authenticated\n" " 200 = Dynamic Displays not allowed\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5184(title) msgid "SERVER_BUSY" msgstr "" #: ../C/gdm.xml:5202(title) msgid "SET_LOGOUT_ACTION" msgstr "" #: ../C/gdm.xml:5226(title) msgid "SET_SAFE_LOGOUT_ACTION" msgstr "" #: ../C/gdm.xml:5227(screen) #, no-wrap msgid "" "\n" "SET_SAFE_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend\n" " after everybody logs out. If only one\n" " person logs out, then this is obviously\n" " the same as the SET_LOGOUT_ACTION. Note\n" " that SET_LOGOUT_ACTION has precedence\n" " over SET_SAFE_LOGOUT_ACTION if it is set\n" " to something other then NONE. If no one\n" " is logged in, then the action takes effect\n" " effect immediately. Only supported on\n" " connections that passed AUTH_LOCAL.\n" "Supported since: 2.5.90.0\n" "Arguments: <action>\n" " NONE Set exit action to 'none'\n" " HALT Set exit action to 'halt'\n" " REBOOT Set exit action to 'reboot'\n" " SUSPEND Set exit action to 'suspend'\n" " CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]'\n" "Answers:\n" " OK\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 7 = Unknown logout action, or not available\n" " 100 = Not authenticated\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5257(title) msgid "SET_VT" msgstr "" #: ../C/gdm.xml:5258(screen) #, no-wrap msgid "" "\n" "SET_VT: Change to the specified virtual terminal.\n" " This is useful for logins which don't own /dev/console\n" " but are still console logins. Only supported on Linux\n" " currently, other places will just get ERROR 8.\n" " Only supported on connections that passed AUTH_LOCAL.\n" "Supported since: 2.5.90.0\n" "Arguments: <vt>\n" "Answers:\n" " OK\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 8 = Virtual terminals not supported\n" " 9 = Invalid virtual terminal number\n" " 100 = Not authenticated\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5279(title) msgid "UPDATE_CONFIG" msgstr "" #: ../C/gdm.xml:5280(screen) #, no-wrap msgid "" "\n" "UPDATE_CONFIG: Tell the daemon to re-read a key from the \n" " GDM configuration file. Any user can request\n" " that values are re-read but the daemon will\n" " only do so if the file has been modified\n" " since GDM first read the file. Only users\n" " who can change the GDM configuration file\n" " (normally writable only by the root user) can\n" " actually modify the GDM configuration. This\n" " command is useful to cause the GDM to update\n" " itself to recognize a change made to the GDM\n" " configuration file by the root user.\n" "\n" " Starting with version 2.13.0.0, all GDM keys are\n" " supported except for the following:\n" "\n" " daemon/PidFile\n" " daemon/ConsoleNotify\n" " daemon/User\n" " daemon/Group\n" " daemon/LogDir\n" " daemon/ServAuthDir\n" " daemon/UserAuthDir\n" " daemon/UserAuthFile\n" " daemon/UserAuthFBDir\n" "\n" " GDM also supports the following Psuedokeys:\n" "\n" " xdmcp/PARAMETERS (2.3.90.2) updates the following:\n" " xdmcp/MaxPending\n" " xdmcp/MaxSessions\n" " xdmcp/MaxWait\n" " xdmcp/DisplaysPerHost\n" " xdmcp/HonorIndirect\n" " xdmcp/MaxPendingIndirect\n" " xdmcp/MaxWaitIndirect\n" " xdmcp/PingIntervalSeconds (only affects new connections)\n" "\n" " xservers/PARAMETERS (2.13.0.4) updates the following:\n" " all [server-foo] sections.\n" "\n" " Supported keys for previous versions of GDM:\n" "\n" " security/AllowRoot (2.3.90.2)\n" " security/AllowRemoteRoot (2.3.90.2)\n" " security/AllowRemoteAutoLogin (2.3.90.2)\n" " security/RetryDelay (2.3.90.2)\n" " security/DisallowTCP (2.4.2.0)\n" " daemon/Greeter (2.3.90.2)\n" " daemon/RemoteGreeter (2.3.90.2)\n" " xdmcp/Enable (2.3.90.2)\n" " xdmcp/Port (2.3.90.2)\n" " daemon/TimedLogin (2.3.90.3)\n" " daemon/TimedLoginEnable (2.3.90.3)\n" " daemon/TimedLoginDelay (2.3.90.3)\n" " greeter/SystemMenu (2.3.90.3)\n" " greeter/ConfigAvailable (2.3.90.3)\n" " greeter/ChooserButton (2.4.2.0)\n" " greeter/SoundOnLoginFile (2.5.90.0)\n" " daemon/AddGtkModules (2.5.90.0)\n" " daemon/GtkModulesList (2.5.90.0)\n" "Supported since: 2.3.90.2\n" "Arguments: <key>\n" " <key> is just the base part of the key such as\n" " \"security/AllowRemoteRoot\"\n" "Answers:\n" " OK\n" " ERROR <err number> <english error description>\n" " 0 = Not implemented\n" " 50 = Unsupported key\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5356(title) msgid "VERSION" msgstr "" #: ../C/gdm.xml:5357(screen) #, no-wrap msgid "" "\n" "VERSION: Query GDM version\n" "Supported since: 2.2.4.0\n" "Arguments: None\n" "Answers:\n" " GDM <gdm version>\n" " ERROR <err number> <english error description>\n" " 200 = Too many messages\n" " 999 = Unknown error\n" msgstr "" #: ../C/gdm.xml:5374(title) msgid "GDM Commands" msgstr "" #: ../C/gdm.xml:5377(title) msgid "GDM User Commands" msgstr "" #: ../C/gdm.xml:5379(para) msgid "" "The GDM package provides the following different commands in " "bindir intended to be used by the end-user:" msgstr "" #: ../C/gdm.xml:5385(title) msgid "" "gdmXnestchooser and gdmXnest Command " "Line Options" msgstr "" #: ../C/gdm.xml:5388(para) msgid "" "The gdmXnestchooser command automatically gets the " "correct display number, sets up access, and runs the nested X server command " "with the \"-indirect localhost\" argument. This provides an XDMCP chooser " "program. You can also supply as an argument the hostname whose chooser " "should be displayed, so gdmXnestchooser somehost will run " "the XDMCP chooser from host somehost inside a nested X " "server session. You can make this command do a direct query instead by " "passing the -d option as well. In addition to the " "following options, this command also supports standard GNOME options." msgstr "" #: ../C/gdm.xml:5403(title) msgid "gdmXnestchooser Command Line Options" msgstr "" #: ../C/gdm.xml:5406(term) msgid "-x, --xnest=STRING" msgstr "" #: ../C/gdm.xml:5408(para) msgid "" "Nested X server command line, default is defined by the Xnest configuration option." msgstr "" #: ../C/gdm.xml:5416(term) msgid "-o, --xnest-extra-options=OPTIONS" msgstr "" #: ../C/gdm.xml:5418(para) msgid "Extra options for nested X server, default is no options." msgstr "" #: ../C/gdm.xml:5425(term) msgid "-n, --no-query" msgstr "" #: ../C/gdm.xml:5427(para) msgid "Just run nested X server, no query (no chooser)" msgstr "" #: ../C/gdm.xml:5434(term) msgid "-d, --direct" msgstr "" #: ../C/gdm.xml:5436(para) msgid "Do direct query instead of indirect (chooser)" msgstr "" #: ../C/gdm.xml:5443(term) msgid "-B, --broadcast" msgstr "" #: ../C/gdm.xml:5445(para) msgid "Run broadcast instead of indirect (chooser)" msgstr "" #: ../C/gdm.xml:5452(term) msgid "-b, --background" msgstr "" #: ../C/gdm.xml:5454(para) msgid "Run in background" msgstr "" #: ../C/gdm.xml:5461(term) msgid "--no-gdm-check" msgstr "" #: ../C/gdm.xml:5463(para) msgid "Don't check for running GDM" msgstr "" #: ../C/gdm.xml:5472(title) ../C/gdm.xml:5515(title) msgid "gdmflexichooser Command Line Options" msgstr "" #: ../C/gdm.xml:5474(para) msgid "" "The gdmflexiserver command provides three features. It " "can be used to run flexible (on demand) X displays, to run a flexible " "display via nested X server, and to send commands to the GDM daemon process." msgstr "" #: ../C/gdm.xml:5481(para) msgid "" "Starting a flexible X display will normally lock the current session with a " "screensaver and will redisplay the GDM login screen so a second user can log " "in. This feature is only available on systems that support virtual terminals " "and have them enabled. This feature is useful if you are logged in as user " "A, and user B wants to log in quickly but user A does not wish to log out. " "The X server takes care of the virtual terminal switching so it works " "transparently. If there is more than one running display defined with " "flexible=true, then the user is shown a dialog that displays the currently " "running sessions. The user can then pick which session to continue and will " "normally have to enter the password to unlock the screen." msgstr "" #: ../C/gdm.xml:5495(para) msgid "" "Nested displays works on systems that do not support virtual terminals. This " "option starts a flexible display in a window in the current session. This " "does not lock the current session, so is not as secure as a flexible server " "started via virtual terminals." msgstr "" #: ../C/gdm.xml:5502(para) msgid "" "The gdmflexiserver --command option provides a way to " "send commands to the GDM daemon and can be used to debug problems or to " "change the GDM configuration." msgstr "" #: ../C/gdm.xml:5508(para) msgid "" "In addition to the following options, gdmflexiserver also " "supports standard GNOME options." msgstr "" #: ../C/gdm.xml:5518(term) msgid "-c, --command=COMMAND" msgstr "" #: ../C/gdm.xml:5520(para) msgid "Send the specified protocol command to GDM" msgstr "" #: ../C/gdm.xml:5527(term) msgid "-n, --xnest" msgstr "" #: ../C/gdm.xml:5529(para) msgid "Start a flexible X display in Nested mode" msgstr "" #: ../C/gdm.xml:5536(term) msgid "-l, --no-lock" msgstr "" #: ../C/gdm.xml:5538(para) msgid "Do not lock current screen" msgstr "" #: ../C/gdm.xml:5545(term) msgid "-d, --debug" msgstr "" #: ../C/gdm.xml:5547(para) msgid "" "Turns on debugging output which gets sent to syslog. Same as turning on " "debug in the configuration file." msgstr "" #: ../C/gdm.xml:5555(term) msgid "-a, --authenticate" msgstr "" #: ../C/gdm.xml:5557(para) msgid "Authenticate before running --command" msgstr "" #: ../C/gdm.xml:5564(term) msgid "-s, --startnew" msgstr "" #: ../C/gdm.xml:5566(para) msgid "" "Starts a new flexible display without displaying a dialog asking the user if " "they wish to continue any existing sessions." msgstr "" #: ../C/gdm.xml:5577(title) ../C/gdm.xml:5604(title) msgid "gdmdynamic Command Line Options" msgstr "" #: ../C/gdm.xml:5579(para) msgid "" "gdmdynamic allows the management of displays in a dynamic " "fashion. It is typically used in environments where it is not possible to " "list the possible displays in the GDM configuration files. The " "gdmdynamic command can be used to create a new display on " "a particular display number, run all newly created displays, or remove a " "display. The gdmdynamic command can also be used to list " "all attached displays or only those attached displays that match a pattern. " "The -a option is used to add a display, the -r option is used to run (or " "release) a display, the -d option is used to delete a display, and the -l " "option lists existing displays. Only one of these four options can be " "specified at a time, so in the life cycle of a particular display, the " "command will be run once to add, again to release (run) the display, and " "finally to delete when the session is to be terminated." msgstr "" #: ../C/gdm.xml:5596(para) msgid "" "This program is designed to manage multiple simultaneous requests and tries " "to avoid flooding the daemon with requests. If the sockets connection is " "busy, it will sleep and retry a certain number of times that can be tuned " "with the -s and -t options." msgstr "" #: ../C/gdm.xml:5607(term) msgid "-a display=server" msgstr "" #: ../C/gdm.xml:5609(para) msgid "" "Add a new display configuration, leaving it in the DISPLAY_CONFIG state. For " "example, \"-a 2=StandardServerTwo\"\"-a 3=/usr/" "X11R6/bin/X -dev /dev/fb2\"" msgstr "" #: ../C/gdm.xml:5615(para) msgid "" "The display will not actually be started until the display is released by " "calling gdmdynamic again with the -r option." msgstr "" #: ../C/gdm.xml:5623(term) msgid "-r" msgstr "" #: ../C/gdm.xml:5625(para) msgid "Release (run) all displays waiting in the DISPLAY_CONFIG state." msgstr "" #: ../C/gdm.xml:5632(term) msgid "-d display" msgstr "" #: ../C/gdm.xml:5634(para) msgid "" "Delete a display, killing the X server and purging the display " "configuration. For example, \"-d 3\"." msgstr "" #: ../C/gdm.xml:5642(term) msgid "-l [pattern]" msgstr "" #: ../C/gdm.xml:5644(para) msgid "" "List displays via the ATTACHED_SERVERS gdmflexiserver " "command. Without a pattern lists all attached displays. With a pattern will " "match using glob characters '*', '?', and '[]'. For example: \"-l " "Standard*\"\"-l *Xorg*\"" msgstr "" #: ../C/gdm.xml:5655(term) msgid "-v" msgstr "" #: ../C/gdm.xml:5657(para) msgid "Verbose mode. Prints diagnostic messages. to GDM." msgstr "" #: ../C/gdm.xml:5665(term) msgid "-b" msgstr "" #: ../C/gdm.xml:5667(para) msgid "Background mode. Fork child to do the work and return immediately." msgstr "" #: ../C/gdm.xml:5674(term) msgid "-t RETRY" msgstr "" #: ../C/gdm.xml:5676(para) msgid "" "If the daemon socket is busy, gdmdynamic will retry to " "open the connection the specified RETRY number of times. Default value is 15." msgstr "" #: ../C/gdm.xml:5685(term) msgid "-s SLEEP" msgstr "" #: ../C/gdm.xml:5687(para) msgid "" "If the daemon socket is busy, gdmdynamic will sleep an " "amount of time between retries. A random number of seconds 0-5 is added to " "the SLEEP value to help ensure that multiple calls to gdmdynamic do not all " "try to restart at the same time. A SLEEP value of zero causes the sleep time " "to be 1 second. Default value is 8 seconds." msgstr "" #: ../C/gdm.xml:5702(title) msgid "gdmphotosetup Command Line Options" msgstr "" #: ../C/gdm.xml:5704(para) msgid "" "Allows the user to select an image that will be used as the user's photo by " "GDM's face browser, if enabled by GDM. The selected file is stored as " "~/.face. This command accepts standard GNOME options." msgstr "" #: ../C/gdm.xml:5713(title) msgid "gdmthemetester Command Line Options" msgstr "" #: ../C/gdm.xml:5715(para) msgid "" "gdmthemetester takes two parameters. The first parameter " "specifies the environment and the second parameter specifies the path name " "or the name of a theme to view. This is a tool for viewing a theme outside " "of GDM. It is useful for testing or viewing themes. gdmthemetester requires that the system support gdmXnest. Note " "that themes can display differently depending on the theme's \"Show mode\". " "gdmthemetester allows viewing the themes in different " "modes via the environment option. Valid environment values and their " "meanings follow: \n" "console - In console mode.\n" "console-timed - In console non-flexi mode.\n" "flexi - In flexi mode.\n" "xdmcp - In remote (XDMCP) mode.\n" "remote-flexi - In remote (XDMCP) & flexi mode.\n" "" msgstr "" #: ../C/gdm.xml:5741(title) msgid "GDM Root User Commands" msgstr "" #: ../C/gdm.xml:5743(para) msgid "" "The GDM package provides the following different commands in " "sbindir intended to be used by the root user:" msgstr "" #: ../C/gdm.xml:5749(title) ../C/gdm.xml:5765(title) msgid "gdm and gdm-binary Command Line Options" msgstr "" #: ../C/gdm.xml:5752(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. If you really need to set some additional " "environment before launching GDM, you can do so in this script." msgstr "" #: ../C/gdm.xml:5769(term) msgid "--help" msgstr "" #: ../C/gdm.xml:5771(para) msgid "Gives a brief overview of the command line options." msgstr "" #: ../C/gdm.xml:5778(term) msgid "--nodaemon" msgstr "" #: ../C/gdm.xml:5780(para) msgid "" "If this option is specified, then GDM does not fork into the background when " "run. You can also use a single-dash version, \"-nodaemon\" for compatibility " "with other display managers." msgstr "" #: ../C/gdm.xml:5790(term) msgid "--no-console" msgstr "" #: ../C/gdm.xml:5792(para) msgid "" "Tell the daemon that it should not run anything on the console. This means " "that none of the local servers from the [servers] " "section will be run, and the console will not be used for communicating " "errors to the user. An empty [servers] section " "automatically implies this option." msgstr "" #: ../C/gdm.xml:5804(term) msgid "--config=CONFIGFILE" msgstr "" #: ../C/gdm.xml:5806(para) msgid "Specify an alternative configuration file." msgstr "" #: ../C/gdm.xml:5813(term) msgid "--preserve-ld-vars" msgstr "" #: ../C/gdm.xml:5815(para) msgid "" "When clearing the environment internally, preserve all variables starting " "with LD_. This is mostly for debugging purposes." msgstr "" #: ../C/gdm.xml:5823(term) msgid "--version" msgstr "" #: ../C/gdm.xml:5825(para) msgid "Print the version of the GDM daemon." msgstr "" #: ../C/gdm.xml:5832(term) msgid "--wait-for-go" msgstr "" #: ../C/gdm.xml:5834(para) msgid "" "If started with this option, gdm will init, but only start the first local " "display and then wait for a GO message in the fifo protocol. No greeter will " "be shown until the GO message is sent. Also flexiserver requests will be " "denied and XDMCP will not be started until GO is given. This is useful for " "initialization scripts which wish to start X early, but where you don't yet " "want the user to start logging in. So the script would send the GO to the " "fifo once it is ready and GDM will then continue. This functionality was " "added in version 2.5.90.0." msgstr "" #: ../C/gdm.xml:5852(title) msgid "gdmsetup Command Line Options" msgstr "" #: ../C/gdm.xml:5854(para) msgid "" "gdmsetup runs a graphical application for modifying the " "GDM configuration file. Normally on systems that support the PAM userhelper, " "this is setup such that when you run gdmsetup as an " "ordinary user, it will first ask you for your root password before starting. " "Otherwise, this application may only be run as root. This application " "supports standard GNOME options." msgstr "" #: ../C/gdm.xml:5866(title) msgid "gdm-restart Command Line Options" msgstr "" #: ../C/gdm.xml:5868(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:5876(title) msgid "gdm-safe-restart Command Line Options" msgstr "" #: ../C/gdm.xml:5878(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:5886(title) msgid "gdm-stop Command Line Options" msgstr "" #: ../C/gdm.xml:5888(para) msgid "" "gdm-stop stops GDM by sending the GDM daemon a TERM " "signal." msgstr "" #: ../C/gdm.xml:5896(title) msgid "GDM Internal Commands" msgstr "" #: ../C/gdm.xml:5898(para) msgid "" "The GDM package provides the following different commands in " "libexecdir intended to be used by the gdm daemon " "process." msgstr "" #: ../C/gdm.xml:5905(title) msgid "" "gdmchooser and gdmlogin Command Line " "Options" msgstr "" #: ../C/gdm.xml:5908(para) msgid "" "The gdmgreeter and gdmlogin are two " "different login applications, either can be used by GDM. " "gdmgreeter is themeable with GDM themes while " "gdmlogin is themable with GTK+ themes. These applications " "are normally executed by the GDM daemon. Both commands support standard " "GNOME options." msgstr "" #: ../C/gdm.xml:5919(title) ../C/gdm.xml:5929(title) msgid "gdmchooser Command Line Options" msgstr "" #: ../C/gdm.xml:5921(para) msgid "" "The gdmchooser is the XDMCP chooser application. The " "gdmchooser is normally executed by the GDM daemon. It " "supports the following options for XDM compatibility. This command supports " "standard GNOME options." msgstr "" #: ../C/gdm.xml:5932(term) msgid "--xdmaddress=SOCKET" msgstr "" #: ../C/gdm.xml:5934(para) msgid "Socket for XDM communication." msgstr "" #: ../C/gdm.xml:5941(term) msgid "--clientaddress=ADDRESS" msgstr "" #: ../C/gdm.xml:5943(para) msgid "" "Client address to return in response to XDM. This option is for running " "gdmchooser with XDM, and is not used within GDM." msgstr "" #: ../C/gdm.xml:5951(term) msgid "--connectionType=TYPE" msgstr "" #: ../C/gdm.xml:5953(para) msgid "" "Connection type to return in response to XDM. This option is for running " "gdmchooser with XDM, and is not used within GDM." msgstr "" #: ../C/gdm.xml:5963(command) msgid "gdm-ssh-session" msgstr "" #: ../C/gdm.xml:5965(para) msgid "" "The gdm-ssh-session is normally executed by the GDM " "daemon when starting a secure remote connection through ssh. It does not " "take any options." msgstr "" #: ../C/gdm.xml:5977(title) msgid "Themed Greeter" msgstr "" #: ../C/gdm.xml:5979(para) msgid "" "This section describes the creation of themes for the Themed Greeter. For " "examples including screenshots, see the standard installed themes and the " "themes from the theme website." msgstr "" #: ../C/gdm.xml:5988(title) msgid "Theme Overview" msgstr "" #: ../C/gdm.xml:5990(para) msgid "" "GDM Themes can be created by creating an XML file that follows the " "specification in gui/greeter/greeter.dtd. Theme files are stored in the " "directory <share>/gdm/themes/<theme_name>. " "Usually this would be under /usr/share. The theme " "directory should contain a file called GdmGreeterTheme.desktop which has similar format to other .desktop files and looks like:" msgstr "" #: ../C/gdm.xml:6001(screen) #, no-wrap msgid "" "\n" "[GdmGreeterTheme]\n" "Encoding=UTF-8\n" "Greeter=circles.xml\n" "Name=Circles\n" "Description=Theme with blue circles\n" "Author=Bond, James Bond\n" "Copyright=(c) 2002 Bond, James Bond\n" "Screenshot=screenshot.png\n" msgstr "" #: ../C/gdm.xml:6012(para) msgid "" "The Name, Description, Author and Copyright fields can be translated just " "like the other .desktopfiles. All the files that are " "mentioned should be in the theme directory itself. The Screenshot field " "points to a file which should be a 200x150 screenshot of the theme in action " "(it is OK not to have one, but it makes it nicer for user). The Greeter " "field points to an XML file that contains the description of the theme. The " "description will be given later." msgstr "" #: ../C/gdm.xml:6022(para) msgid "" "Once you have theme ready and installed you can test it with the installed " "gdmthemetester script. This script assumes that the X " "server supports a nested server command. This command takes two arguments, " "first the environment that should be used. This is one of console, console-" "timed, flexi, remote-flexi, xdmcp. Where console is a standard console " "login, console-timed is a console login with a timed login going on, flexi " "is for any local flexible display, remote-flexi is for flexi displays that " "are not local (such as an Xnest flexiserver run from a remote display) and " "xdmcp is for remote XDMCP connections. The second argument is the theme " "name. So for example to test how things look in the XDMCP mode with the " "circles theme you would run:" msgstr "" #: ../C/gdm.xml:6038(command) msgid "gdmthemetester xdmcp circles" msgstr "" #: ../C/gdm.xml:6041(para) msgid "" "Be sure to test all the environments with your theme, and make sure to test " "how the caps lock warning looks by pressing caps lock. This is also a good " "way to take screenshots, just take a screenshot of the nested display " "window. This can be done in GNOME by focusing the nested login window and " "pressing Alt-PrintScreen." msgstr "" #: ../C/gdm.xml:6049(para) msgid "" "Once you have all this done, then make a tarball that contains the directory " "name (so that you could just untar it in the <share>/gdm/" "themes directory). And this is the tarball you distribute and " "people can install from the graphical configuration application. You can do " "this with the commands: \n" "cd <share>/gdm/themes\n" "tar czvf <theme_name>.tar.gz <theme_name>/\n" "" msgstr "" #: ../C/gdm.xml:6063(title) msgid "Detailed Description of Theme XML format" msgstr "" #: ../C/gdm.xml:6066(title) msgid "greeter tag" msgstr "" #: ../C/gdm.xml:6068(para) msgid "" "The GDM theme format is specified in XML format contained within a <" "greeter> tag. You may specify a GTK+ theme to be used with this theme by " "using the gtk-theme element in the greeter tag as in the following example." msgstr "" #: ../C/gdm.xml:6075(screen) #, no-wrap msgid "" "\n" "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" "<!DOCTYPE greeter SYSTEM \"greeter.dtd\">\n" "<greeter gtk-theme=\"Crux\">\n" "[...]\n" "</greeter>\n" msgstr "" #: ../C/gdm.xml:6083(para) msgid "" "Contained within the greeter tag can be the nodes described in the next " "sections of this document. Some of these nodes are containers (box nodes, " "rect item nodes) which can be used to organize how to display the nodes that " "the user sees and interacts with (such as button, pixmap and entry item " "nodes)." msgstr "" #: ../C/gdm.xml:6093(title) msgid "Box Nodes" msgstr "" #: ../C/gdm.xml:6095(para) msgid "" "Box nodes are container nodes for item nodes. Box nodes are specified as " "follows: \n" "<box orientation=\"alignment\" min-width=\"num\"\n" "xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" "homogeneous=\"bool\">\n" " Where \"num\" means number and bool means either \"true\" or " "\"false\" The alignment value can be either \"horizontal\" or \"vertical\". " "If you leave any property off it will default to zero or \"false\" in case " "of \"homogeneous\" and \"vertical\" for the orientation." msgstr "" #: ../C/gdm.xml:6111(para) msgid "" "If the box is homogeneous then the children are allocated equal amount of " "space." msgstr "" #: ../C/gdm.xml:6116(para) msgid "" "The \"min-width\" must be specified in pixels. Obviously there is also a " "corresponding \"min-height\" property as well." msgstr "" #: ../C/gdm.xml:6124(title) msgid "Fixed Nodes" msgstr "" #: ../C/gdm.xml:6126(para) msgid "" "Fixed is a container that has its children scattered about laid out with " "precise coordinates. The size of this container is the biggest rectangle " "that contains all the children. Fixed has no extra properties and so you " "just use: \n" "<fixed>\n" " Then you put other items with proper position nodes inside this." msgstr "" #: ../C/gdm.xml:6137(para) msgid "The \"toplevel\" node is really just like a fixed node." msgstr "" #: ../C/gdm.xml:6143(title) msgid "Item Nodes" msgstr "" #: ../C/gdm.xml:6145(para) msgid "" "A GDM Theme is created by specifying a hierarchy of item and box nodes. Item " "nodes can have the following value for \"type\":" msgstr "" #: ../C/gdm.xml:6153(term) msgid "button" msgstr "" #: ../C/gdm.xml:6155(para) msgid "" "A button field. This field uses a GTK+ button. It is also possible to make a " "\"rect\" item act like a button by setting its button element to true. " "However it is better to use GTK+ buttons in GDM themes since these are " "accessible to users with disabilities. Also, GTK+ buttons can be themed. " "This feature is supported in GDM 2.14.6 and later." msgstr "" #: ../C/gdm.xml:6167(term) msgid "entry" msgstr "" #: ../C/gdm.xml:6169(para) msgid "Text entry field." msgstr "" #: ../C/gdm.xml:6176(term) msgid "label" msgstr "" #: ../C/gdm.xml:6178(para) msgid "A text label. Must have a \"text\" node to specify the text." msgstr "" #: ../C/gdm.xml:6186(term) msgid "list" msgstr "" #: ../C/gdm.xml:6188(para) msgid "" "A face browser widget. Only useful if the face browser is enabled via the " "configuration." msgstr "" #: ../C/gdm.xml:6196(term) msgid "pixmap" msgstr "" #: ../C/gdm.xml:6198(para) msgid "" "An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, " "etc...)" msgstr "" #: ../C/gdm.xml:6206(term) msgid "rect" msgstr "" #: ../C/gdm.xml:6208(para) msgid "Rectangle." msgstr "" #: ../C/gdm.xml:6215(term) msgid "svg" msgstr "" #: ../C/gdm.xml:6217(para) msgid "Scaled Vector Graphic image." msgstr "" #: ../C/gdm.xml:6224(para) msgid "" "For example: \n" "<item type=\"label\">\n" " Items can specify ID values which gives them a specific look and " "feel or formatting. Furthermore you can customize the login process by " "adding custom widgets with custom id's for some items (currently only the " "list item)" msgstr "" #: ../C/gdm.xml:6235(para) msgid "Entry items can have id values as follows:" msgstr "" #: ../C/gdm.xml:6241(term) msgid "user-pw-entry" msgstr "" #: ../C/gdm.xml:6243(para) msgid "" "Entry field for userid and password entry. This is the field used for " "responses for the PAM/GDM questions (Username, Password, etc..)." msgstr "" #: ../C/gdm.xml:6252(para) msgid "" "List items by default display as lists, but the combo=\"true\" attribute can " "be used to specify combo box style (combo style supported since GDM 2.16.2). " "Some predefined lists may be included in a theme by using the following id " "values. Customized lists may also be defined, which are explained below." msgstr "" #: ../C/gdm.xml:6262(term) msgid "session" msgstr "" #: ../C/gdm.xml:6264(para) msgid "" "A list of available sessions, which allows the user to pick the session to " "use. Supported since GDM 2.16.2." msgstr "" #: ../C/gdm.xml:6274(term) msgid "language" msgstr "" #: ../C/gdm.xml:6276(para) msgid "" "A list of available languages, which allows the user to pick the language to " "use. Supported since GDM 2.16.2." msgstr "" #: ../C/gdm.xml:6286(term) msgid "userlist" msgstr "" #: ../C/gdm.xml:6288(para) msgid "" "A Face Browser list, so that users can pick their username by clicking on " "this instead of typing. This obviously exposes the usernames to viewers of " "the login screen, and is not recommended for users who feel that this " "reduces security. The face browser does not support combo box style." msgstr "" #: ../C/gdm.xml:6301(term) msgid "userlist-rect" msgstr "" #: ../C/gdm.xml:6303(para) msgid "" "This id can be specified for the <rect> object containing the userlist " "and if the userlist is empty then this rectangle will not be shown. This " "allows the theme to define something like an area with a different color and/" "or alpha to surround the userlist, but only if there are users to display. " "Supported since 2.16.2." msgstr "" #: ../C/gdm.xml:6315(para) msgid "" "Furthermore, you can have an arbitrary id (I'd recommend starting the id " "with 'custom' not to conflict with future additions to this spec) and ask " "extra information of the user. See the section 'Custom Widgetry'" msgstr "" #: ../C/gdm.xml:6322(para) msgid "Label items can have id values as follows:" msgstr "" #: ../C/gdm.xml:6328(term) msgid "clock" msgstr "" #: ../C/gdm.xml:6330(para) msgid "Label that displays the date and time." msgstr "" #: ../C/gdm.xml:6337(term) msgid "pam-prompt" msgstr "" #: ../C/gdm.xml:6339(para) msgid "" "Label that displays the PAM prompt. This is the prompt that PAM uses to ask " "for username, password, etc..." msgstr "" #: ../C/gdm.xml:6347(term) msgid "pam-error" msgstr "" #: ../C/gdm.xml:6349(para) msgid "Label that displayst PAM/GDM error messages. Such as when user can't log in." msgstr "" #: ../C/gdm.xml:6357(term) msgid "pam-error-logo" msgstr "" #: ../C/gdm.xml:6359(para) msgid "" "An image that will be displayed only when a pam-error message is being " "displayed. This is useful for displaying an \"Attention\" icon, for example. " "This feature is supported in GDM 2.14.6 and later." msgstr "" #: ../C/gdm.xml:6369(term) msgid "pam-message" msgstr "" #: ../C/gdm.xml:6371(para) msgid "" "Label that displays the PAM message. These are messages that PAM/GDM gives " "about state of the account, help about the prompts and other information." msgstr "" #: ../C/gdm.xml:6380(term) msgid "timed-label" msgstr "" #: ../C/gdm.xml:6382(para) msgid "Label that displays timed login information." msgstr "" #: ../C/gdm.xml:6389(para) msgid "Rectangles can have id values as follows:" msgstr "" #: ../C/gdm.xml:6395(term) msgid "caps-lock-warning" msgstr "" #: ../C/gdm.xml:6397(para) msgid "" "Displays an icon that shows if the CAPS LOCK key is depressed. This " "rectangle will be hidden/shown appropriately" msgstr "" #: ../C/gdm.xml:6406(para) msgid "" "If an item is of type rect, the item can be a button. Buttons must also " "include a \"button\" value as follows: \n" "<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n" "" msgstr "" #: ../C/gdm.xml:6414(para) msgid "Possible values for button ids are as follows." msgstr "" #: ../C/gdm.xml:6420(term) msgid "chooser_button" msgstr "" #: ../C/gdm.xml:6422(para) msgid "Runs the XDMCP chooser." msgstr "" #: ../C/gdm.xml:6429(term) msgid "config_button" msgstr "" #: ../C/gdm.xml:6431(para) msgid "Runs the GDM configuration application." msgstr "" #: ../C/gdm.xml:6438(term) msgid "custom_cmd_button[0-9]" msgstr "" #: ../C/gdm.xml:6440(para) msgid "Runs the n-th custom command." msgstr "" #: ../C/gdm.xml:6447(term) msgid "disconnect_button" msgstr "" #: ../C/gdm.xml:6449(para) msgid "Disconnect from remote session." msgstr "" #: ../C/gdm.xml:6456(term) msgid "language_button" msgstr "" #: ../C/gdm.xml:6458(para) msgid "Displays the language selection dialog." msgstr "" #: ../C/gdm.xml:6465(term) msgid "halt_button" msgstr "" #: ../C/gdm.xml:6467(para) msgid "Halt (shuts down) the system." msgstr "" #: ../C/gdm.xml:6474(term) msgid "reboot_button" msgstr "" #: ../C/gdm.xml:6476(para) msgid "Restart the system." msgstr "" #: ../C/gdm.xml:6483(term) msgid "session_button" msgstr "" #: ../C/gdm.xml:6485(para) msgid "List and select from available sessions." msgstr "" #: ../C/gdm.xml:6492(term) msgid "suspend_button" msgstr "" #: ../C/gdm.xml:6494(para) msgid "Suspend the system." msgstr "" #: ../C/gdm.xml:6501(term) msgid "system_button" msgstr "" #: ../C/gdm.xml:6503(para) msgid "" "Perform halt/restart/suspend/etc. options (if allowed by GDM configuration). " "Also allows user to run configurator if user enters root password (again if " "allowed by GDM configuration). This is usually now labeled Actions, and " "referred to as the Actions menu." msgstr "" #: ../C/gdm.xml:6514(para) msgid "" "By default, the GDM login screen will disappear after authentication. This " "can result in flicker between the login screen and the session. The " "\"background\" property allows users to specify what elements of the theme " "are the background image. When used, this will cause GDM to remove all non-" "background items from the display and render the remaining \"background\" " "items to the root window. This can be used to create a smooth transition " "between the login screen and the session. For example, if the GDM theme and " "the session use the same background, then this will make the background " "apear seamless." msgstr "" #: ../C/gdm.xml:6527(para) msgid "" "Item nodes may specify a \"background\" property which can be set to \"true" "\" or \"false\" (not setting this property is equivalent to \"false\"), as " "follows:" msgstr "" #: ../C/gdm.xml:6533(screen) #, no-wrap msgid "" "\n" "<item type=\"rect\" background=\"true\">\n" " <normal file=\"background.svg\"/>\n" " <pos x=\"0\" y=\"0\" width=\"100%\" height=\"-75\"/>\n" "</item>\n" msgstr "" #: ../C/gdm.xml:6540(para) msgid "" "If no item node has \"background\" property set, then the background is not " "modified when greeter exits." msgstr "" #: ../C/gdm.xml:6545(para) msgid "" "To use a different background for login transition than the one used for " "login, the theme should specify two item nodes (which could contain pixmaps " "or svg images, for example). The item which corresponds to the greeter " "background should not have the \"background\" property while the item which " "corresponds to the transition background should have the \"background\" " "property. For instance :" msgstr "" #: ../C/gdm.xml:6554(screen) #, no-wrap msgid "" "\n" "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" "<!DOCTYPE greeter SYSTEM \"greeter.dtd\">\n" " <greeter>\n" "\n" " <item type=\"rect\" background=\"true\">\n" " <normal file=\"background_for_login.svg\"/>\n" " <pos x=\"0\" y=\"0\" width=\"100%\" height=\"100%\"/>\n" " </item>\n" " <item type=\"rect\">\n" " <normal file=\"background_for_greeter.svg\"/>\n" " <pos x=\"0\" y=\"0\" width=\"100%\" height=\"100%\"/>\n" " </item>\n" "[...]\n" "</greeter>\n" msgstr "" #: ../C/gdm.xml:6573(title) msgid "Position Node" msgstr "" #: ../C/gdm.xml:6575(para) msgid "" "Each item can specify its position and size via the \"pos\" node. For " "example: \n" "<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" "" msgstr "" #: ../C/gdm.xml:6583(para) msgid "" "Both position and size can be given in percent and it will be taken as the " "percentage of the size of the current container. For toplevel items it's the " "percentage of the whole screen." msgstr "" #: ../C/gdm.xml:6589(para) msgid "" "For x and y, you can also specify a negative position which means position " "from the right or bottom edge. But this only applies with absolute " "coordinates. With percentage you can specify negative position and it will " "be still from the same edge." msgstr "" #: ../C/gdm.xml:6596(para) msgid "" "The position also specifies the anchor of the item, this can be \"n\" \"ne\" " "\"e\" \"se\" \"s\" \"sw\" \"w\" and \"nw\" or \"center\" which stand for the " "different edges/corners or \"center\" for center. For example: \n" "<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/>\n" "" msgstr "" #: ../C/gdm.xml:6607(para) msgid "" "If the item contains a box, you can specify width and height to be \"box\" " "to mean that they are supposed to be the width and height of the box, that " "is the items in the box plus the padding." msgstr "" #: ../C/gdm.xml:6613(para) msgid "" "If the item contains an SVG image, you can specify width and height to be " "\"scale\" to mean that the SVG image should be scaled to fit the requested " "area." msgstr "" #: ../C/gdm.xml:6619(para) msgid "" "You can also specify an \"expand\" property to either be \"true\" or false. " "If true then the child will be expanded in the box as much as possible (that " "is it will be given more space if available)." msgstr "" #: ../C/gdm.xml:6626(para) msgid "" "There are two extra properties you can specify (as of 2.4.4.3) for labels " "(and labels only). The first is \"max-width\" which will specify the maximum " "width of the label in pixels. And the second is \"max-screen-percent-width\" " "which specifies the maximum percentage of the screen width that the label " "can occupy. By default no label will occupy more then 90% of the screen by " "width. An example may be: \n" "<item type=\"label\">\n" "<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" "" msgstr "" #: ../C/gdm.xml:6642(title) msgid "Show Node" msgstr "" #: ../C/gdm.xml:6644(para) msgid "" "Some items may only display in certain modes, like when doing a remote " "display. Multiple values can be specified and must be separated with commas. " "The following values are possible:" msgstr "" #: ../C/gdm.xml:6650(para) msgid "console - In console mode." msgstr "" #: ../C/gdm.xml:6653(para) msgid "console-fixed - In console non-flexi mode." msgstr "" #: ../C/gdm.xml:6656(para) msgid "console-flexi - In console & flexi mode." msgstr "" #: ../C/gdm.xml:6659(para) msgid "flexi - In flexi mode." msgstr "" #: ../C/gdm.xml:6662(para) msgid "remote - In remote mode." msgstr "" #: ../C/gdm.xml:6665(para) msgid "remote-flexi - In remote & flexi mode." msgstr "" #: ../C/gdm.xml:6669(para) msgid "" "For example: \n" "<show modes=\"flexi,remote\"/>\n" "" msgstr "" #: ../C/gdm.xml:6676(para) msgid "" "You can also specify the \"type\" value to indicate that certain items " "should only be displayed if the type is true. Valid values include the " "following:" msgstr "" #: ../C/gdm.xml:6682(para) msgid "" "chooser, if ChooserButton is set to \"true\" in the GDM " "configuration." msgstr "" #: ../C/gdm.xml:6686(para) msgid "" "config, if ConfigAvailable is set to \"true\" in the " "GDM configuration." msgstr "" #: ../C/gdm.xml:6690(para) msgid "" "custom_cmd[0-9], if n-th " "CustomCommand is specified in the GDM configuration." msgstr "" #: ../C/gdm.xml:6694(para) msgid "" "halt, if HaltDaemon is specified in the GDM " "configuration." msgstr "" #: ../C/gdm.xml:6698(para) msgid "" "reboot, if RebootCommand is specified in the GDM " "configuration." msgstr "" #: ../C/gdm.xml:6702(para) msgid "" "suspend, if SuspendCommand is specified in the GDM " "configuration." msgstr "" #: ../C/gdm.xml:6706(para) msgid "" "system, if SystemMenu is specified in the GDM " "configuration." msgstr "" #: ../C/gdm.xml:6710(para) msgid "" "timed, if TimedLoginEnabled is set to \"true\" in the " "GDM configuration." msgstr "" #: ../C/gdm.xml:6715(para) msgid "" "For example: \n" "<show modes=\"console\" type=\"system\"/>\n" "" msgstr "" #: ../C/gdm.xml:6722(para) msgid "" "Alternatively, you can specify a \"min-screen-width\" or \"min-screen-height" "\" value to indicate that certain items should only be displayed if the " "screen resolution is the at least the given required size." msgstr "" #: ../C/gdm.xml:6729(para) msgid "" "For example: \n" "<show min-screen-height=\"768\"/>\n" "" msgstr "" #: ../C/gdm.xml:6736(para) msgid "" "Note that if SystemMenu is off then the halt, restart, suspend, chooser and " "config choices will not be shown, so this is a global toggle for them all. " "See some of the standard themes for how the show modes are used." msgstr "" #: ../C/gdm.xml:6745(title) msgid "Normal/Active/Prelight Nodes" msgstr "" #: ../C/gdm.xml:6747(para) msgid "" "Depending on the item type (except for userlist - refer to Color node " "below), it can specify its color, font, or image via the following tags:" msgstr "" #: ../C/gdm.xml:6753(para) msgid "normal - normal state." msgstr "" #: ../C/gdm.xml:6756(para) msgid "active - when the item has active focus." msgstr "" #: ../C/gdm.xml:6759(para) msgid "prelight - when the mouse is hovering over the item." msgstr "" #: ../C/gdm.xml:6764(para) msgid "" "When item is \"rect\" (alpha can be omitted and defaults to 0.0): \n" "<normal color=\"#ffffff\" alpha=\"0.0\">\n" "" msgstr "" #: ../C/gdm.xml:6772(para) msgid "" "When item is \"label\" \n" "<normal color=\"#ffffff\" font=\"Sans 14\"/>\n" "" msgstr "" #: ../C/gdm.xml:6779(para) msgid "" "When the item type is \"pixmap\" or \"SVG\", then the normal, active, and " "prelight tags specify the images to use as follows: \n" "<normal file=\"picture.png\" tint=\"#dddddd\"/>\n" "" msgstr "" #: ../C/gdm.xml:6788(para) msgid "" "Note that relative pathnames are assumed to be in the same directory as the " "theme .xml file in <share>/gdm/themes/" "<theme_name>." msgstr "" #: ../C/gdm.xml:6794(para) msgid "" "Note that alternative image file can be specified using the altfile[n] " "property. GDM will use the last valid image filename specified. For example: " "\n" "<normal file=\"picture.png\" altfile1=\"distribution-blah-image.png\" " "altfile2=\"distribution-foo-image.png\"/>\n" " If distribution-foo-image.png is a valid " "image filename it will be used. Otherwise distribution-blah-image.png will " "be used if valid. This feature supported since 2.16.3." msgstr "" #: ../C/gdm.xml:6809(title) msgid "Face Browser Icon/Label Color Nodes" msgstr "" #: ../C/gdm.xml:6811(para) msgid "" "If the item type is of userlist, then the background color for the icon and " "label can be set separately via the the following tag:" msgstr "" #: ../C/gdm.xml:6817(screen) #, no-wrap msgid "" "\n" "<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" msgstr "" #: ../C/gdm.xml:6824(title) msgid "Text Node" msgstr "" #: ../C/gdm.xml:6826(para) msgid "" "Text tags are used by labels. They can be used to display localized text as " "follows (if the \"xml:lang\" attribute is omitted, the C locale is assumed): " "\n" "<text xml:lang=\"fr\">Option</text>\n" "" msgstr "" #: ../C/gdm.xml:6835(para) msgid "" "You can include pango markup in the text nodes for labels, however you must " "encode it. So for example to have the label of \"foo<sup>bar</" "sup>\", you must type: \n" "<text>\"foo<sup>bar</sup>\"</text>\n" "" msgstr "" #: ../C/gdm.xml:6844(para) msgid "" "Text nodes can contain the following special character sequences which will " "be translated as follows:" msgstr "" #: ../C/gdm.xml:6849(para) msgid "%% - A literal % character" msgstr "" #: ../C/gdm.xml:6852(para) msgid "" "%c - Clock time. Only labels with the \"clock\" id will update automatically " "every second. Other labels will contain a static timestamp." msgstr "" #: ../C/gdm.xml:6857(para) msgid "%d - Display name (DISPLAY environment variable)" msgstr "" #: ../C/gdm.xml:6860(para) msgid "%h - Hostname (gethostname output)" msgstr "" #: ../C/gdm.xml:6863(para) msgid "%m - Machine name (uname.machine output)" msgstr "" #: ../C/gdm.xml:6866(para) msgid "%n - Node name (uname.nodename output)" msgstr "" #: ../C/gdm.xml:6869(para) msgid "%o - Domain name (getdomainname output)" msgstr "" #: ../C/gdm.xml:6872(para) msgid "%r - Release name (uname.release output)" msgstr "" #: ../C/gdm.xml:6875(para) msgid "%s - System name (uname.sysname output)" msgstr "" #: ../C/gdm.xml:6878(para) msgid "" "%t - Current timed delay value from configuration file (0 if off) followed " "by the word \"seconds\" if value is greater than 1 or the word \"second\" if " "the value is 1. This character sequence is intended to be only used " "internally to display the \"timed-label\" message, which is automatically " "updated every second." msgstr "" #: ../C/gdm.xml:6886(para) msgid "" "%u - Timed username value from configuration file (empty if off) This " "character sequence is intended to be only used internally to display the " "\"timed-label\" message, which is automatically updated every second." msgstr "" #: ../C/gdm.xml:6892(para) msgid "\\n - Carriage return" msgstr "" #: ../C/gdm.xml:6895(para) msgid "" "_ - An underscore causes the following character to be underlined. If it " "precedes a % character sequence, the string that replaces the character " "sequence is underlined." msgstr "" #: ../C/gdm.xml:6903(title) msgid "Stock node" msgstr "" #: ../C/gdm.xml:6905(para) msgid "" "Certain common localized labels can be specified via the stock tags. The " "\"text\" tag is ignored if the \"stock\" tag is used. You should really use " "the stock labels rather then just putting all the translations into the " "themes. This gives faster load times and likely better translations. The " "following values are valid:" msgstr "" #: ../C/gdm.xml:6914(para) msgid "cancel, _(\"_Cancel\"" msgstr "" #: ../C/gdm.xml:6917(para) msgid "caps-lock-warning, _(\"Caps Lock is on.\"" msgstr "" #: ../C/gdm.xml:6921(para) msgid "chooser, _(\"Remote Login via _XDMCP\"" msgstr "" #: ../C/gdm.xml:6924(para) msgid "config, _(\"_Configure\"" msgstr "" #: ../C/gdm.xml:6927(para) msgid "custom_cmd[0-9], getting label from config file" msgstr "" #: ../C/gdm.xml:6930(para) msgid "disconnect, _(\"D_isconnect\"" msgstr "" #: ../C/gdm.xml:6933(para) msgid "halt, _(\"Shut _Down\"" msgstr "" #: ../C/gdm.xml:6936(para) msgid "language, _(\"_Language\"" msgstr "" #: ../C/gdm.xml:6939(para) msgid "ok, _(\"_OK\"" msgstr "" #: ../C/gdm.xml:6942(para) msgid "options, _(\"_Options\"" msgstr "" #: ../C/gdm.xml:6945(para) msgid "quit, _(\"_Quit\"" msgstr "" #: ../C/gdm.xml:6948(para) msgid "reboot, _(\"_Restart\"" msgstr "" #: ../C/gdm.xml:6951(para) msgid "session, _(\"_Session\"" msgstr "" #: ../C/gdm.xml:6954(para) msgid "startagain, _(\"_Start Again\"" msgstr "" #: ../C/gdm.xml:6957(para) msgid "suspend, _(\"Sus_pend\"" msgstr "" #: ../C/gdm.xml:6960(para) msgid "system, _(\"_Actions\" (Formerly \"S_ystem\"" msgstr "" #: ../C/gdm.xml:6964(para) msgid "timed-label, _(\"User %u will login in %t\"" msgstr "" #: ../C/gdm.xml:6968(para) msgid "username-label, _(\"Username:\"" msgstr "" #: ../C/gdm.xml:6971(para) msgid "welcome-label, _(\"Welcome to %n\"" msgstr "" #: ../C/gdm.xml:6975(para) msgid "" "For example: \n" "<stock type=\"welcome-label\">\n" "" msgstr "" #: ../C/gdm.xml:6984(title) msgid "Custom Widgetry" msgstr "" #: ../C/gdm.xml:6986(para) msgid "" "Currently there is one item which is customizable and this is the list item. " "If you need to ask the user extra things, such as to pick from a list of " "places to log into, or set of custom login sessions you can setup the list " "item and add listitem children that describe the choices. Each listitem must " "have an id and a text child. The choice will be recorded in the file " "<ServAuthDir>/<display>.GreeterInfo as " "<list id>=<listitem id>." msgstr "" #: ../C/gdm.xml:6997(para) msgid "" "For example suppose we are on display :0, ServAuthDir " "is <var>/lib/gdm and we have the following in the " "theme:" msgstr "" #: ../C/gdm.xml:7004(screen) #, no-wrap msgid "" "\n" "<item type=\"list\" id=\"custom-config\">\n" "<pos anchor=\"nw\" x=\"1\" y=\"1\" height=\"200\" width=\"100\">\n" "<listitem id=\"foo\">\n" "<text>Foo</text>\n" "</listitem>\n" "<listitem id=\"bar\">\n" "<text>Bar</text>\n" "</listitem>\n" "</item>\n" msgstr "" #: ../C/gdm.xml:7016(para) msgid "" "Then if the user chooses 'Foo' then <var>/lib/gdm/:0." "GreeterInfo will contain: \n" "custom-config=foo\n" "" msgstr "" #: ../C/gdm.xml:7028(title) msgid "Accessibility" msgstr "" #: ../C/gdm.xml:7029(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) programs such as GOK (on-screen keyboard) and orca (magnifier and " "text-to-speech) are supported. The \"GTK+ Greeter\" best supports " "accessibility, so it is recommended for accessibility support. The \"Themed " "Greeter\" supports some accessibility features and may be usable by some " "users. But some AT programs, such as GOK, do not yet work " "with the \"Themed Greeter\"." msgstr "" #: ../C/gdm.xml:7042(para) msgid "" "Accessibility is enabled by specifying the \"GTK+ Greeter\" in the \"Local\" " "tab for the console display and specifying the \"GTK+ Greeter\" in the " "\"Remote\" tab for remote displays. Or you can modify the Greeter and RemoteGreeter configuration options by " "hand to be /usr/lib/gdmlogin." msgstr "" #: ../C/gdm.xml:7051(para) msgid "" "The GDM greeter programs support the ability to launch AT's at login time " "via configurable \"gestures\". These gestures can be defined to be standard " "keyboard hotkeys, switch device event, or mouse motion events. When using " "the \"GTK+ Greeter\", the user may also change the visual appearance of the " "login UI. For example, to use a higher-contrast color scheme for better " "visibility." msgstr "" #: ../C/gdm.xml:7060(para) msgid "" "Note that gdmsetup does not yet work with accessibility, " "so that users who require AT programs should only configure GDM by editing " "the ASCII files directly." msgstr "" #: ../C/gdm.xml:7067(title) msgid "Accessibility Configuration" msgstr "" #: ../C/gdm.xml:7069(para) msgid "" "In order to enable Accessible Login, the system administrator must make some " "changes to the default login configuration by manually modifying three human-" "readable configuration files, stored in the GDM Custom Configuration File, " "AccessKeyMouseEvents File, and AccessDwellMouseEvents File. The " "AccessKeyMouseEvents and AccessDwellMouseEvents contain reasonable default " "gestures for launching GOK and orca, " "but some users may require these gestures to be configured to best meet " "their needs. For example, shorter or longer duration for holding down a " "button or hotkey might make the login experience more usable for some users. " "Also, additional AT programs may be added to the configuration file if " "needed." msgstr "" #: ../C/gdm.xml:7085(title) msgid "Accessibile Theming" msgstr "" #: ../C/gdm.xml:7087(para) msgid "" "If using the \"GTK+ Greeter\" users can easily switch the color and contrast " "scheme of the dialog. To do this, ensure the AllowGtkThemeChange parameter in the GDM configuration is set to \"true\". This should " "be the default value. When true, the \"Standard Greeter\" contains a menu " "allowing the user to change to a different GTK+ theme. The " "GtkThemesToAllow configuration choice can also be used " "to limit the choices available as desired. For example:" msgstr "" #: ../C/gdm.xml:7099(screen) #, no-wrap msgid "" "\n" "GtkThemesToAllow=HighContrast,HighContrastInverse\n" msgstr "" #: ../C/gdm.xml:7103(para) msgid "" "If using the \"Themed Greeter\" there may be suitable GDM themes available " "that provide needed color and contrast schemes, but these are not yet " "shipped with the GDM program. Some distributions may ship such themes. There " "is not yet any mechanism to switch between themes in the \"Themed Greeter\", " "so if an accessible theme is required by one user, then all users would need " "to use the same theme." msgstr "" #: ../C/gdm.xml:7115(title) msgid "AT Program Support" msgstr "" #: ../C/gdm.xml:7117(para) msgid "" "To enable user to launch AT such as the GOK or " "orca, the AddGtkModules parameter in " "the GDM configuration must be set to \"true\". Also the " "GtkModulesList parameter must be uncommented and set as " "follows:" msgstr "" #: ../C/gdm.xml:7126(screen) #, no-wrap msgid "" "\n" "GtkModulesList=gail:atk-bridge:/usr/lib/gtk-2.0/modules/libdwellmouselistener:/usr/lib/gtk-2.0/modules/libkeymouselistener\n" msgstr "" #: ../C/gdm.xml:7130(para) msgid "" "This causes all GDM GUI programs to be run with the appropriate GTK modules " "for launching AT programs. The use of assistive technologies and the atk-" "bridge module requires the registry daemon, at-spi-registryd, to be running. This is handled by the GDM GUI starting with " "version 2.17." msgstr "" #: ../C/gdm.xml:7138(para) msgid "" "System administrators may wish to load only the minimum subset of these " "modules which is required to support their user base. The " "\"libkeymouselistener\" provides hotkey and switch gesture support while the " "\"libdwellmouselistener\" provides mouse motion gesture support. If your " "user base only requires one or the other, it is only necessary to include " "the gesture listener that is needed. Also, some AT programs may not require " "gail or atk-bridge. If you find the AT programs you need works fine without " "including these, then they may be omitted. Note that some AT programs work " "with a reduced feature set if gail and/or atk-bridge are not present. " "However, for general accessibility use, including all four is suitable." msgstr "" #: ../C/gdm.xml:7153(para) msgid "" "Once \"keymouselistener\" and/or \"dwellmouselistener\" have been added to " "the AddGtkModules loaded by GDM, then you may need to " "modiify the gesture configurations to meet your user's needs. Default " "gestures are provided for launching GOK and " "orca, but it is recommended to modify these gestures so " "they work best for your user base. These gesture associations are contained " "in files AccessKeyMouseEvents and " "AccessDwellMouseEvents, respectively. Both files are " "located in the <etc>/gdm/modules directory. The " "gesture configuration format is described in the comment section of the two " "configuration files." msgstr "" #: ../C/gdm.xml:7170(para) msgid "" "The AccessKeyMouseEvents file controls the keymouselistener Gesture Listener " "and is used to define key-press, mouse button, or XInput device sequences " "that can be used to launch applications needed for accessibility. In order " "to reduce the likelihood of unintentional launch, these \"gestures\" may be " "associated with multiple switch presses and/or minimum durations. Note that " "the XKB extension is needed for key gestures to work, so you may need to add " "+xkb to your X server command line for gestures to work properly. The X " "server command line is specified in the GDM configuration file in the " "\"server-foo\" sections." msgstr "" #: ../C/gdm.xml:7184(para) msgid "" "The DwellKeyMouseEvents file controls the dwellmouselistner and supports " "gestures that involve the motion of a pointing device such as the system " "mouse of an alternative pointing device such as a head pointer or trackball " "may also be defined. Motion gestures are defined as \"crossing events\" into " "and out of the login dialog window. If the \"dwellmouselistener\" gesture " "listener is loaded, then alternative pointing devices are temporarily " "\"latched\" to the core pointer, such that motion from alternative devices " "results in movement of the onscreen pointer. All gestures are specified by " "the same syntax; that is, there is no distinction between a \"core mouse\" " "gesture and motion from an alternate input device." msgstr "" #: ../C/gdm.xml:7200(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:7207(para) msgid "" "Currently GDM does not remember what accessible technology programs have " "been started when switching applications. So if the user switches between " "the login program and the chooser, for example, then it is necessary for the " "user to redo the gesture. Users may need to also set up their default " "session so that the assistive technologies required are started " "automatically (or have appropriate key-bindings defined to start them) after " "the user session has started." msgstr "" #: ../C/gdm.xml:7220(title) msgid "AT Troubleshooting" msgstr "" #: ../C/gdm.xml:7222(para) msgid "" "There are some common issues that cause users to have problems getting the " "gesture listeners to work. It is recommended that people use GDM version " "2.18.0 or later for best results." msgstr "" #: ../C/gdm.xml:7228(para) msgid "" "Some older X servers have a bug which causes detectable autorepeat to fail " "when XEVIE is enabled (which happens when atk-bridge is included as a GTK " "Module). This bug causes key gestures with a duration greater than 0 to " "always fail. A workaround is to simply redefine all key gestures so they " "have zero length duration, or upgrade your X server." msgstr "" #: ../C/gdm.xml:7237(para) msgid "" "Some versions of GOK and orca will not " "launch unless the \"gdm\" user has a writable home directory. This has been " "fixed in GNOME 2.18, but if using an older version of GNOME, then making " "sure that the GDM user has a writable home directory should make these " "programs functional." msgstr "" #: ../C/gdm.xml:7246(para) msgid "" "If you see an hourglass cursor when you complete a gesture but the program " "does not start, then this indicates that the gesture was received, but that " "there was a problem starting the program. Most likely the issue may be the " "lack of a writable gdm home directory." msgstr "" #: ../C/gdm.xml:7254(para) msgid "" "Also note that some input devices require X server configuration before GDM " "will recognize them." msgstr "" #: ../C/gdm.xml:7261(title) msgid "Accessibility Login Sound Configuration" msgstr "" #: ../C/gdm.xml:7263(para) msgid "" "By default, GDM requires a media application such as \"play\" to be present " "to play sounds for successful or failed login. GDM defaults the location of " "this application to <bin>/play (or <" "bin>/audioplay on Solaris. This can be changed via the " "SoundProgram GDM configuration option. Typically most " "text-to-speech programs (such as orca) use a separate " "mechanism to play audio, so this configuration setting is not needed for " "them to work." msgstr "" #: ../C/gdm.xml:7281(title) msgid "Solaris Specific Features" msgstr "" #: ../C/gdm.xml:7284(title) msgid "Using GDM on Solaris" msgstr "" #: ../C/gdm.xml:7286(para) msgid "" "GDM is not yet the default login program on Solaris. If you wish to switch " "to using GDM, then you need to turn off CDE login and start the GDM service. " "Note that turning off or disabiling CDE login will cause any running " "sessions to immediately exit, and any unsaved data will be lost. Only run " "these commands if you are sure there is no unsaved data in your running " "sessions. It would be best to run these commands from console login, or a " "Failsafe Terminal rather than from a running GUI session. The first step is " "to run the following command to see if CDE login is running as an SMF " "service." msgstr "" #: ../C/gdm.xml:7299(screen) #, no-wrap msgid "" "\n" "svcs cde-login\n" msgstr "" #: ../C/gdm.xml:7303(para) msgid "" "If the svcs command responds that this service is " "enabled, then run this command to disable CDE login:" msgstr "" #: ../C/gdm.xml:7308(screen) #, no-wrap msgid "" "\n" "svcadm disable cde-login\n" msgstr "" #: ../C/gdm.xml:7312(para) msgid "" "If the svcs command responds that this pattern doesn't " "match any instances, then run these commands to stop CDE login:" msgstr "" #: ../C/gdm.xml:7318(screen) #, no-wrap msgid "" "\n" "/usr/dt/config/dtconfig -d\n" "Either reboot, or kill any running dtlogin processes.\n" msgstr "" #: ../C/gdm.xml:7323(para) msgid "" "At this point you will be presented with a console login. Login as root, and " "run the following command. If on Solaris 10 the servicename is \"gdm2-login" "\", if on Solaris Nevada the servicename is \"gdm\"." msgstr "" #: ../C/gdm.xml:7330(screen) #, no-wrap msgid "" "\n" "svcadm enable servicename\n" msgstr "" #: ../C/gdm.xml:7336(title) msgid "Solaris Configuration" msgstr "" #: ../C/gdm.xml:7337(para) msgid "" "On Solaris, the following configuration is recommended. This turns on IPv6 " "and also turns on PreFetch for performance benefit. \n" "./autogen.sh --prefix=/usr --sysconfdir=/etc/X11 --localstatedir=/var\n" " --libexecdir=/usr/lib --enable-ipv6=yes --with-at-bindir=/usr/sfw/bin\n" " --with-prefetch --with-post-path=/usr/openwin/bin --with-pam-prefix=/etc\n" " --with-lang-file=/etc/default/init\n" "" msgstr "" #: ../C/gdm.xml:7350(para) msgid "" "Configuring GDM with the \"--with-post-path=/usr/openwin/bin\" on Solaris is " "recommended for accessing X server programs." msgstr "" #: ../C/gdm.xml:7358(title) msgid "Solaris /etc/logindevperm" msgstr "" #: ../C/gdm.xml:7359(para) msgid "" "GDM supports /etc/logindevperm, but only on Solaris 10 and higher. Refer to " "the logindevperm.4 man page for more information." msgstr "" #: ../C/gdm.xml:7365(para) msgid "" "To make /etc/logindevperm functionality work on Solaris 9 or earlier you " "would have to hack the GDM PreSession and PostSession script to chmod the " "device permissions directly. In other words, if /etc/logindevperm had a " "listing like this:" msgstr "" #: ../C/gdm.xml:7372(screen) #, no-wrap msgid "" "\n" "/dev/console 0600 /dev/sound/* # audio devices\n" msgstr "" #: ../C/gdm.xml:7376(para) msgid "" "Then the PreSession script would need to be modified to chown /dev/console " "to the user:group who is logging into the console and ensure whatever " "permissions is specified in /etc/logindevperm (0600 for the line above). " "Then in the PostSession script chmod the device back to root:root and ensure " "0600 this time (do not use the value in the /etc/logindevperm file). Linux " "uses a different mechanism for managing device permissions, so this extra " "scripting is not needed." msgstr "" #: ../C/gdm.xml:7389(title) msgid "Solaris Automatic Login" msgstr "" #: ../C/gdm.xml:7390(para) msgid "" "Automatic login does not work on Solaris 10 and earlier because PAM is not " "configured to support this feature by default. Automatic login is a GDM " "feature that is not enabled by default, so you would only notice this " "problem if you try to make use of it. Turning this feature on causes your " "computer to login to a specified username on startup without asking for " "username and password. This is an insecure way to set up your computer." msgstr "" #: ../C/gdm.xml:7401(para) msgid "" "If using Solaris 10 or lower, then you need to compile the pam_allow.c code " "provided with the GDM release and install it to /usr/lib/security (or " "provide the full path in /etc/pam.conf) and ensure it is owned by uid 0 and " "not group or world writable." msgstr "" #: ../C/gdm.xml:7408(para) msgid "" "The following are reasonable pam.conf values for turning on automatic login " "in GDM. Make sure to read the PAM documentation (e.g. pam.d/pam.conf man " "page) and be comfortable with the security implications of any changes you " "intend to make to your configuration." msgstr "" #: ../C/gdm.xml:7416(screen) #, no-wrap msgid "" "\n" " gdm-autologin auth required pam_unix_cred.so.1\n" " gdm-autologin auth sufficient pam_allow.so.1\n" " gdm-autologin account sufficient pam_allow.so.1\n" " gdm-autologin session sufficient pam_allow.so.1\n" " gdm-autologin password sufficient pam_allow.so.1\n" msgstr "" #: ../C/gdm.xml:7424(para) msgid "" "The above setup will cause no lastlog entry to be generated. If a lastlog " "entry is desired, then use the following for session:" msgstr "" #: ../C/gdm.xml:7429(screen) #, no-wrap msgid "" "\n" " gdm-autologin session required pam_unix_session.so.1\n" msgstr "" #: ../C/gdm.xml:7435(title) msgid "Solaris RBAC support for Shutdown, Reboot, and Suspend" msgstr "" #: ../C/gdm.xml:7437(para) msgid "" "Starting with GDM 2.19, GDM supports RBAC (Role Based Access Control) for " "enabling the system commands (Shutdown, Reboot, Suspend, etc.) that appear " "in the greeter system menu and via the gdmflexiserver " "QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION commands." msgstr "" #: ../C/gdm.xml:7446(para) msgid "" "On Solaris GDM has the following value specified for the " "RBACSystemCommandKeys configuration option." msgstr "" #: ../C/gdm.xml:7452(screen) #, no-wrap msgid "" "\n" "HALT:solaris.system.shutdown;REBOOT:solaris.system.shutdown\n" msgstr "" #: ../C/gdm.xml:7456(para) msgid "" "This will cause the SHUTDOWN and REBOOT features to only be enabled for " "users who have RBAC authority. In other words, those users who have the " "\"solaris.system.shutdown\" authorization name specified. The GDM greeter " "will only display these options if the gdm user (specified in the " "User configuration option, \"gdm\" by default) has such " "RBAC permissions." msgstr "" #: ../C/gdm.xml:7466(para) msgid "" "Therefore, add the \"solaris.system.shutdown\" authorization name to the " "/etc/user_attr for all users who should have authority " "to shutdown and reboot the system. If you want these options to appear in " "the greeter program, also add this authorization name to the gdm user. If " "you don't want to use RBAC, then you may unset the " "RBACSystemCommandKeys GDM configuration key, and this " "will make the system commands available for all users. Refer to the " "user_attr man page for more information about setting " "RBAC privileges." msgstr "" #: ../C/gdm.xml:7480(para) msgid "" "Note that on Solaris there are two programs that can be used to shutdown the " "system. These are GDM and gnome-sys-suspend. " "gnome-sys-suspend is a GUI front-end for the sys-" "suspend." msgstr "" #: ../C/gdm.xml:7488(para) msgid "" "If GDM is being used as the login program and the user has RBAC permissions " "to shutdown the machine (or RBAC support is disabled in GDM), then the GNOME " "panel \"Shut Down..\" option will use GDM to shutdown, reboot, and suspend " "the machine. This is a bit nicer than using gnome-sys-suspend since GDM will wait until the user session has finished (including " "running the PostSession script, etc.) before running the shutdown/reboot/" "suspend command. Also the gnome-sys-suspend command is " "less functional since it does not support a reboot option, only shutdown and " "suspend." msgstr "" #: ../C/gdm.xml:7503(para) msgid "" "If GDM is not being used to manage shutdown, reboot, and suspend; then the " "GNOME panel uses gnome-sys-suspend when you select the " "\"Shut Down...\" option from the application menu. If the pop-up that " "appears when you select this only shows the suspend and shutdown options, " "then you are likely using gnome-sys-suspend. If you are " "using this, then refer to the sys-suspend man page for " "information about how to configure it. Or consider using GDM and configuring " "it to provide these options." msgstr "" #: ../C/gdm.xml:7519(title) msgid "Other Solaris Features" msgstr "" #: ../C/gdm.xml:7520(para) msgid "GDM supports a few features specific to Solaris, as follows:" msgstr "" #: ../C/gdm.xml:7524(para) msgid "" "GDM supports Solaris Auditing if running on Solaris 10 or higher. GDM should " "not be used if auditing is needed and running Solaris 9 or older." msgstr "" #: ../C/gdm.xml:7530(para) msgid "" "GDM supports a security feature which causes the X server to run as the user " "instead of as the root user. GDM must be using PAM for this feature to be " "enabled, which is the normal case for Solaris. This second feature has the " "side-effect of causing the X server to always restart between sessions, " "which disables the AlwaysRestartServer configuration option." msgstr "" #: ../C/gdm.xml:7539(para) msgid "" "Solaris supports the /etc/default/login interface, " "which affects the DefaultPath, RootPath, PasswordRequired, and " "AllowRemoteRoot options as described in the " "\"Configuration\" section." msgstr "" #: ../C/gdm.xml:7551(title) msgid "Example Configurations" msgstr "" #: ../C/gdm.xml:7553(para) msgid "" "This section has some example configurations that are useful for various " "setups." msgstr "" #: ../C/gdm.xml:7559(title) msgid "Terminal Lab With One Server" msgstr "" #: ../C/gdm.xml:7561(para) msgid "" "Suppose you want to make a lab full of X terminals that all connect to one " "server machine. So let's call one X terminal xterminal " "and let's call the server machine appserver. You " "install GDM on both." msgstr "" #: ../C/gdm.xml:7568(para) msgid "" "On appserver you enable XDMCP, so you have \n" "[xdmcp]\n" "Enable=true\n" " If you want no local screens here, you can then make the " "[servers] section empty." msgstr "" #: ../C/gdm.xml:7578(para) msgid "" "On the xterminal you disable XDMCP (you don't want " "anyone to connect to the xterminal really). You will add a server type " "perhaps called Terminal as follows: \n" "[server-Terminal]\n" "name=Terminal server\n" "command=/path/to/X -terminate\n" "flexible=false\n" "handled=false\n" " This definition should in fact be included in the standard " "configuration file. Notice that we made the handled key " "false since we don't want GDM to handle this server localy. Also note that " "we have not yet added the -query argument, you can add " "that here, or in the [servers] section. We'll define " "our local servers as follows: \n" "[servers]\n" "0=Terminal -query appserver\n" " This will run a direct XDMCP query to the server named " "appserver." msgstr "" #: ../C/gdm.xml:7606(title) msgid "Terminal Lab With Two Or More Servers" msgstr "" #: ../C/gdm.xml:7608(para) msgid "" "Suppose you want to make a lab full of X terminals that all connect to some " "choice of servers. For now let's make it appserverone " "and appservertwo. Again we'll call our example X " "terminal server xterminal. The setup on both servers is " "the same as with the case of one server in the previous section. You do not " "need to explicitly enable indirect queries on the server since we'll run the " "choosers locally on the X terminals." msgstr "" #: ../C/gdm.xml:7619(para) msgid "" "So on the xterminal you again disable XDMCP. You will " "add a server type perhaps called Chooser as follows: " "\n" "[server-Chooser]\n" "name=Chooser server\n" "command=/path/to/X\n" "flexible=false\n" "chooser=true\n" " And again this definition should in fact be included in the " "standard configuration file. Notice that we made the chooser key true here. This will run the XDMCP chooser for this server, " "and when the user chooses a host GDM will run a query for that host. Then we " "will define our local servers as follows: \n" "[servers]\n" "0=Chooser\n" "" msgstr "" #: ../C/gdm.xml:7642(para) msgid "" "The XDMCP chooser on the X terminal will normally give a broadcast query to " "see which servers exist on the network. If the two servers are not reachable " "by a broadcast query, you must add them by hand to the configuration file. " "So in the [chooser] section you would have: \n" "Hosts=appserverone,appservertwo\n" " and any other servers you wish the users to be able to connect to." msgstr "" #: ../C/gdm.xml:7654(para) msgid "" "Sometimes you may want to run the chooser on the server side however. Then " "what you want to do is to run a configuration similar to the previous " "section about the one server configuration with XDMCP indirect queries " "enabled on appserver and on the X terminals you'd have " "\n" "[servers]\n" "0=Terminal -indirect appserver\n" " This way for example you only have to maintain one " "Hosts entry. However as a disadvantage then, the " "appserver must then always be available. So it's not " "good for situations where you want to have several servers and not all of " "them have to be on all the time. You could also have one of the X terminals " "handle indirect XDMCP queries and serve up the chooser to the other X " "terminals." msgstr "" #: ../C/gdm.xml:7675(title) msgid "Defining Custom Commands" msgstr "" #: ../C/gdm.xml:7677(para) msgid "" "Suppose you want to add a custom command to the GDM menu that will give you " "the opportunity to boot into other operating system such as Windoze. Just " "add the following options into the [customcommand] " "section of the GDM configuration file. \n" " [customcommand]\n" " CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze\n" " CustomCommandLabel0=_Windoze\n" " CustomCommandLRLabel0=Reboot into _Windoze\n" " CustomCommandText0=Are you sure you want to restart the computer " "into Windoze?\n" " CustomCommandTooltip0=Restarts the computer into Windoze\n" " CustomCommandIsPersistent0=true\n" " CustomCommand0 specifies two commands separated by a " "semicolon: /sbin/rebootwindoze and /usr/local/" "sbin/rebootwindoze. GDM will use the first valid command in the " "list. This allows different commands for different operating systems to be " "included." msgstr "" #: ../C/gdm.xml:7700(para) msgid "" "Note, that besides being able to customise this option to reboot into " "different operating systems you can also use it to define your own custom " "behaviours that you wish to run from the GDM menu. Suppose you want to give " "users the opportunity to run system update scripts from the login screen. " "Add the following options into the [customcommand] " "section of your GDM configuration file. \n" " [customcommand]\n" " CustomCommand0=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" " CustomCommandLabel0=_Update Me\n" " CustomCommandLRLabel0=Update the system\n" " CustomCommandText0=Are you sure you want to update the system " "software?\n" " CustomCommandTooltip0=Updates the system\n" " CustomCommandNoRestart0=true\n" " " msgstr "" #: ../C/gdm.xml:7720(para) msgid "" "Both custom commands could be defined as follows. \n" " [customcommand]\n" " CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze\n" " CustomCommandLabel0=_Windoze\n" " CustomCommandLRLabel0=Reboot into _Windoze\n" " CustomCommandText0=Are you sure you want to restart the computer " "into Windoze?\n" " CustomCommandTooltip0=Restarts the computer into Windoze\n" " CustomCommandIsPersistent0=true\n" " \n" " CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" " CustomCommandLabel1=_Update Me\n" " CustomCommandLRLabel1=Update the system\n" " CustomCommandText1=Are you sure you want to update the system " "software?\n" " CustomCommandTooltip1=Updates the system\n" " CustomCommandNoRestart1=true\n" " " msgstr "" #: ../C/gdm.xml:7741(para) msgid "" "There can be up to 10 custom commands numbered 0-9. \n" " [customcommand]\n" " CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze\n" " CustomCommandLabel0=_Windoze\n" " CustomCommandLRLabel0=Reboot into _Windoze\n" " CustomCommandText0=Are you sure you want to restart the computer " "into Windoze?\n" " CustomCommandTooltip0=Restarts the computer into Windoze\n" " CustomCommandIsPersistent0=true\n" " \n" " CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" " CustomCommandLabel1=_Update Me\n" " CustomCommandLRLabel1=Update the system\n" " CustomCommandText1=Are you sure you want to update the system " "software?\n" " CustomCommandTooltip1=Updates the system\n" " CustomCommandNoRestart1=true\n" " \n" " CustomCommand3=/sbin/do_something\n" " .\n" " .\n" " .\n" " \n" " CustomCommand4=/sbin/do_something_else\n" " .\n" " .\n" " .\n" " " msgstr "" #: ../C/gdm.xml:7775(title) msgid "Troubleshooting" msgstr "" #: ../C/gdm.xml:7777(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 to the \"gdm\" category " "in bugzilla.gnome." "org or send an email to the
gdm-list@gnome.org
mail list." msgstr "" #: ../C/gdm.xml:7787(para) msgid "" "If GDM is failing to work properly, it is always a good idea to include " "debug information. Use the gdmsetup command to turn on " "debug (\"Enable debug messages to system log\" checkbox in the \"Security\" " "tab), then use GDM to the point where it fails, and include the GDM output " "sent to your system log (<var>/log/messages or " "<var>/adm/messages depending on your operating " "system). Since the system log can be large, please only include the GDM " "debug information and do not sent the entire file. If you do not see any GDM " "syslog output, you may need to configure syslog (see syslog.3c man page)." msgstr "" #: ../C/gdm.xml:7801(para) msgid "" "You should not leave debug on after collecting data. It will clutter your " "syslog and slow system performance." msgstr "" #: ../C/gdm.xml:7807(title) msgid "GDM Will Not Start" msgstr "" #: ../C/gdm.xml:7809(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:7818(para) msgid "" "First make sure that the X server is configured properly. The GDM " "configuration file contains a command in the [server-Standard] section that " "is used for starting the X server. Verify that this command works on your " "system. Running this command from the console should start the X server. If " "it fails, then the problem is likely with your X server configuration. Refer " "to your X server error log for an idea of what the problem may be. The " "problem may also be that your X server requires different command-line " "options. If so, then modify the X server command in the GDM configuration " "file so that it is correct for your system." msgstr "" #: ../C/gdm.xml:7831(para) msgid "" "Another common problem is that the GDM greeter program is having trouble " "starting. This can happen, for example, if GDM cannot find a needed library " "or other resource. Try starting the X server and a terminal program, set the " "shell environment variable DOING_GDM_DEVELOPMENT=1 and run <" "lib>/gdmlogin or <lib>/gdmgreeter. Any " "error messages echoed to the terminal will likely highlight the problem. " "Also, turning on debug and checking the output sent to the system log will " "often highlight the problem." msgstr "" #: ../C/gdm.xml:7844(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:7852(title) msgid "GDM Will Not Access User Settings" msgstr "" #: ../C/gdm.xml:7854(para) msgid "" "GDM saves user settings, such as your default session and default language, " "in the ~/.dmrc. Other files, such as the user's " "~/.Xauthority file will also affect login. GDM, by " "default, is strict about how it tries to access files in the user's home " "directory, and will ignore the file if they do not conform to certain rules. " "You can use the RelaxPermissions configuration option " "to make GDM less strict about how it accesses files in the user's home " "directory, or correct the permissions issues that cause GDM to ignore the " "file. This is discussed in detail described in the \"File Access\" section " "of the \"Overview\"." msgstr "" #: ../C/gdm.xml:7873(title) msgid "License" msgstr "" #: ../C/gdm.xml:7874(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:7882(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:7888(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 ""