diff options
Diffstat (limited to 'docs')
42 files changed, 0 insertions, 65150 deletions
diff --git a/docs/.cvsignore b/docs/.cvsignore deleted file mode 100644 index 83e56ef0..00000000 --- a/docs/.cvsignore +++ /dev/null @@ -1,3 +0,0 @@ -Makefile.in -Makefile -*.omf diff --git a/docs/C/.cvsignore b/docs/C/.cvsignore deleted file mode 100644 index ab4d4d42..00000000 --- a/docs/C/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -Makefile -Makefile.in -*.out -omf_timestamp diff --git a/docs/C/gdm.xml b/docs/C/gdm.xml deleted file mode 100644 index ffdddac7..00000000 --- a/docs/C/gdm.xml +++ /dev/null @@ -1,7909 +0,0 @@ -<?xml version="1.0"?> -<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" - "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ - <!ENTITY legal SYSTEM "legal.xml"> - <!ENTITY version "2.21.0"> - <!ENTITY date "09/17/2007"> - <!ENTITY mdash "—"> - <!ENTITY percnt "%"> -]> - -<article id="index" lang="en"> - <articleinfo> - <title>Gnome Display Manager Reference Manual</title> - - <revhistory> - <revision> - <revnumber>0.0</revnumber> - <date>2007-01</date> - </revision> - </revhistory> - - <abstract role="description"> - <para> - GDM is the GNOME Display Manager, a graphical login program. - </para> - </abstract> - - <authorgroup> - <author> - <firstname>Martin</firstname><othername>K.</othername> - <surname>Petersen</surname> - <affiliation> - <address><email>mkp@mkp.net</email></address> - </affiliation> - </author> - <author> - <firstname>George</firstname><surname>Lebl</surname> - <affiliation> - <address><email>jirka@5z.com</email></address> - </affiliation> - </author> - <author role="maintainer"> - <firstname>Brian</firstname><surname>Cameron</surname> - <affiliation> - <address><email>Brian.Cameron@Sun.COM</email></address> - </affiliation> - </author> - <author> - <firstname>Bill</firstname><surname>Haneman</surname> - <affiliation> - <address><email>Bill.Haneman@Sun.COM</email></address> - </affiliation> - </author> - </authorgroup> - <copyright> - <year>1998</year><year>1999</year><holder>Martin K. Petersen</holder> - </copyright> - <copyright> - <year>2001</year><year>2003</year><year>2004</year> - <holder>George Lebl</holder> - </copyright> - <copyright> - <year>2003</year> <holder>Red Hat, Inc.</holder> - </copyright> - <copyright> - <year>2003</year><year>2004</year><holder>Sun Microsystems, Inc.</holder> - </copyright> - - &legal; - - <releaseinfo> - This manual describes version &version; of the GNOME Display Manager. - It was last updated on &date;. - </releaseinfo> - </articleinfo> - - <sect1 id="preface"> - <title>Terms and Conventions Used in This Manual</title> - - <para> - This manual describes version &version; of the GNOME Display Manager. - It was last updated on &date;. - </para> - - <para> - Chooser - A program used to select a remote host for managing a - display remotely on the attached display (<command>gdmchooser</command>). - </para> - - <para> - Configurator - The configuration application - (<command>gdmsetup</command>). - </para> - - <para> - GDM - Gnome Display Manager. Used to describe the software package as a - whole. Sometimes also referred to as GDM2. - </para> - - <para> - gdm - The Gnome Display Manager daemon (<command>gdm</command>). - </para> - - <para> - Greeter - The graphical login window (<command>gdmlogin</command> or - <command>gdmgreeter</command>). - </para> - - <para> - GTK+ Greeter - The standard login window (<command>gdmlogin</command>). - </para> - - <para> - PAM - Pluggable Authentication Mechanism - </para> - - <para> - Themed Greeter - The themable login window ( - <command>gdmgreeter</command>). - </para> - - <para> - XDMCP - X Display Manage Protocol - </para> - - <para> - Paths that start with a word in angle brackets are relative to the - installation prefix. I.e. <filename><share>/pixmaps/</filename> - refers to <filename><share>/pixmaps</filename> if GDM was configured - with <command>--prefix=/usr</command>. Normally also note that - GDM is installed with <command>--sysconfigdir=<etc>/X11</command>, - meaning any path to which we refer to as - <filename><etc>/gdm/PreSession</filename> usually means - <filename><etc/X11>/gdm/PreSession</filename>. Note that for - interoperability it is recommended that you use a --prefix of - <filename>/usr</filename> and a --sysconfdir of - <filename><etc>/X11</filename>. - </para> - </sect1> - - <sect1 id="overview"> - <title>Overview</title> - - <sect2 id="introduction"> - <title> - Introduction - </title> - - <para> - The Gnome Display Manager (GDM) is a display manager that - implements all significant features required for managing - attached and remote displays. GDM was written from scratch and - does not contain any XDM / X Consortium code. - </para> - - <para> - 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. - </para> - - <para> - For further information about GDM, see the - <ulink type="http" url="http://www.gnome.org/projects/gdm/"> - the GDM project website</ulink>. Please submit any bug reports or - enhancement requests to the "gdm" category in - <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink>. - You can also send a message to the - <address><email>gdm-list@gnome.org</email></address> mail list to - discuss any issues or concerns with the GDM program. - </para> - </sect2> - - <sect2 id="stability"> - <title> - Interface Stability - </title> - - <para> - 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 - <filename>server-foo</filename>. - </para> - - <para> - Command-line interfaces for GDM programs installed to - <filename><bin></filename> and <filename><sbin></filename> - 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. - </para> - - <para> - 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 <command>gdmchooser</command>. These arguments have been - changed to now use two dashes. - </para> - - <para> - If issues are discovered that break compatibility, please file a bug - with an "urgent" priority. - </para> - </sect2> - - <sect2 id="daemonov"> - <title>The GDM Daemon</title> - - <para> - 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 <filename>Init</filename>, - <filename>PostLogin</filename>, <filename>PreSession</filename>, - and <filename>PostSession</filename> scripts discussed below are - discussed in this "Configuring GDM section". - </para> - - <para> - 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. - </para> - - <para> - GDM can be asked to manage a display a number of ways. Attached - displays are always managed when GDM starts and will be restarted when - a user's session is finished. Remote displays can be requested via - XDMCP, flexible displays via the <command>gdmflexiserver</command> - command, and dynamic displays via the <command>gdmdynamic</command> - command. Displays that are started on request are not restarted on - session exit. - </para> - - <para> - When the GDM daemon is asked to manage a display, it will fork an - X server process, then run the <filename>Init</filename> script as the - root user, and start the login GUI dialog as a slave process on the - display. GDM can be configured to use either - <command>gdmgreeter</command> (the default) or - <command>gdmlogin</command> as the GUI dialog program. The - <command>gdmlogin</command> program supports accessibility while the - <command>gdmgreeter</command> program supports greater themeability. - The GUI dialog is run as the unpriviledged "gdm" user/group - which is described in the "Security" section below. The GUI - dialog communicates with the daemon via a sockets protocol and via - standard input/output. The slave, for example passes the username and - password information to the GDM daemon via standard input/output so - the daemon can handle the actual authentication. - </para> - - <para> - 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). - </para> - - <para> - GDM, by default, will use Pluggable Authentication Modules (PAM) for - authentication, but can also support regular crypt and shadow passwords - on legacy systems. After authenticating a user, the daemon runs the - <filename>PostLogin</filename> script as root, and forks a slave - process to start the requested session. This slave process runs the - <filename>PreSession</filename> script as root, sets up the user's - environment, and starts the requested session. GDM keeps track of the - user's default session and language in the user's - <filename>~/.dmrc</filename> and will use these defaults if the user - did not pick a session or language in the login GUI. On Solaris, GDM - (since version 2.8.0.3) uses the SDTLOGIN interface after user - authentication to tell the X server to be restarted as the user instead - of as root for added security. When the user's session exits, the GDM - daemon will run the <filename>PostSession</filename> script as root. - </para> - - <para> - Note that, by default, GDM uses the "gdm" service name for - normal login and the "gdm-autologin" service name for - automatic login. The <filename>PamStack</filename> 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. - </para> - - <para> - For those looking at the code, the gdm_verify_user function in - <filename>daemon/verify-pam.c</filename> is used for normal login - and the gdm_verify_setup_user function is used for automatic login. - </para> - </sect2> - - <sect2 id="displaytypes"> - <title>Different Display Types</title> - - <para> - GDM supports three different display types: attached displays, - flexible displays, and XDMCP remote displays. The - "X Server Definitions" subsection of the - "Configuration" section explains how the X server is - configured for different displays. - </para> - - <para> - Attached (also known as local or static) displays are always started by - the daemon, and when they die or are killed, they are restarted. GDM - can run as many of these as needed. GDM can also manage displays on - which it does not manage a GUI login, thus GDM can be used for - supporting X terminals. The "Attached DISPLAY Configuration" - subsection of the "Configuration" section describes how - attached displays are defined. - </para> - - <para> - Flexible (also known as on-demand) displays are only available to users - logged 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. - </para> - - <para> - Flexible displays may be started by running the - <command>gdmflexiserver</command> 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). - </para> - - <para> - The <filename>FlexibleXServers</filename>, - <filename>FirstVT=7</filename>, <filename>VTAllocation</filename>, - and <filename>FlexiReapDelayMinutes</filename> configuration settings - are used to configure how flexible displays operate. - </para> - - <para> - 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 <command>gdmflexiserver -n</command> - 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 <filename>Xnest</filename> configuration - option is used to configure how nested displays are started. - </para> - - <para> - The <command>gdmdynamic</command> is similar to - <command>gdmflexiserver</command> in the sense that it allows the - user to manage displays dynamically. However displays started with - <command>gdmdynamic</command> are treated as attached 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 "Attached 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. - </para> - - <para> - 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. - </para> - - </sect2> - - <sect2 id="xdmcp"> - <title> - XDMCP - </title> - - <para> - The GDM daemon can be configured to listen for and manage X Display - Manage Protocol (XDMCP) requests from remote displays. By default - XDMCP support is turned off, but can be enabled if desired. If GDM is - built with TCP Wrapper support, then the daemon will only grant access - to hosts specified in the GDM service section in the TCP Wrappers - configuration file. - </para> - - <para> - GDM includes several measures making it more resistant to denial of - service attacks on the XDMCP service. A lot of the protocol - parameters, handshaking timeouts etc. can be fine tuned. The defaults - should work for most systems, however. Do not change them unless you - know what you are doing. - </para> - - <para> - GDM listens to UDP port 177 and will respond to QUERY and - BROADCAST_QUERY requests by sending a WILLING packet to the originator. - </para> - - <para> - GDM can also be configured to honor INDIRECT queries and present a - host chooser to the remote display. GDM will remember the user's - choice and forward subsequent requests to the chosen manager. GDM - also supports an extension to the protocol which will make it forget - the redirection once the user's connection succeeds. This extension - is only supported if both daemons are GDM. It is transparent and - will be ignored by XDM or other daemons that implement XDMCP. - </para> - - <para> - If XDMCP seems to not be working, make sure that all machines are - specified in <filename>/etc/hosts</filename>. - </para> - - <para> - Refer to the "Security" section for information about - security concerns when using XDMCP. - </para> - </sect2> - - <sect2 id="secureremote"> - <title> - Securing Remote Connection Through SSH - </title> - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - Using this session allows a much more secure network connection and - only necessitates to have an SSH server running on the remote host. - </para> - </sect2> - - <sect2 id="gtkgreeter"> - <title>The GTK+ Greeter</title> - - <para> - 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. - </para> - - <para> - The text entry field is used for entering logins, passwords, - passphrases etc. <command>gdmlogin</command> 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. - </para> - - <para> - 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. - </para> - - <para> - 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 <filename>Logo</filename> option in the - reference section below for details. - </para> - </sect2> - - <sect2 id="themedgreeter"> - <title>The Themed Greeter</title> - - <para> - 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 - <filename>GraphicalTheme</filename> 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - </sect2> - - <sect2 id="facebrowser"> - <title>The GDM Face Browser</title> - - <para> - 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 <filename>Browser</filename> 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. - </para> - - <para> - 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 - <command>gdmsetup</command>. This feature is most practical to use - on a system with a smaller number of users. - </para> - - <para> - 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 <filename><share>/pixmaps/faces/</filename> - directory (though this can be configured with the - <filename>GlobalFaceDir</filename> configuration option) and the - filename should be the name of the user, optionally with a - <filename>.png</filename> 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. - </para> - - <para> - Users may run the <command>gdmphotosetup</command> command to - configure the image to use for their userid. This program properly - scales the file down if it is larger than the - <filename>MaxIconWidth</filename> or - <filename>MaxIconHeight</filename> configuration options and places the - icon in a file called <filename>~/.face</filename>. Although - <command>gdmphotosetup</command> scales user images automatically, - this does not guarantee that user images are properly scaled since - a user may create their <filename>~/.face</filename> file by hand. - </para> - - <para> - GDM will first look for the user's face image in - <filename>~/.face</filename>. If not found, it will try - <filename>~/.face.icon</filename>. If still not found, it will - use the value defined for "face/picture=" in the - <filename>~/.gnome2/gdm</filename> file. Lastly, it will try - <filename>~/.gnome2/photo</filename> and - <filename>~/.gnome/photo</filename> which are deprecated and - supported for backwards compatibility. - </para> - - <para> - If a user has no defined face image, GDM will use the - "stock_person" icon defined in the current GTK+ theme. If no - such image is defined, it will fallback to the image specified in the - <filename>DefaultFace</filename> configuration option, normally - <filename><share>/pixmaps/nobody.png</filename>. - </para> - - <para> - 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 - <filename>Include</filename> 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 <filename>GlobalFaceDir</filename> - configuration option. - </para> - - <para> - To control the users who get displayed in the face browser, there are - a number of configuration options that can be used. If the - <filename>IncludeAll</filename> option is set to true, then the - password file will be scanned and all users will be displayed. If - <filename>IncludeAll</filename> option is set to false, then the - <filename>Include</filename> option should contain a list of users - separated by commas. Only the users specified will be displayed. - Any user listed in the <filename>Exclude</filename> option and users - whose UID's is lower than <filename>MinimalUID</filename> will be - filtered out regardless of the <filename>IncludeAll</filename> - setting. <filename>IncludeAll</filename> 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.. - </para> - - <para> - 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). - </para> - </sect2> - - <sect2 id="logging"> - <title>Logging</title> - - <para> - 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. - </para> - - <para> - Output from the various X servers is stored in the GDM log directory, - which is configurable, but is usually - <filename><var>/log/gdm/</filename>. The output from the - session can be found in a file called - <filename><display>.log</filename>. Four older files are also - stored with <filename>.1</filename> through - <filename>.4</filename> 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. - </para> - - <para> - The output from the user session is redirected to - <filename>~/.xsession-errors</filename> - before even the <filename>PreSession</filename> 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. - </para> - - <para> - You can suppress the 10 second warning by returning code 66 from the - <filename>Xsession</filename>script or from your session binary (the - default <filename>Xsession</filename> 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. - </para> - - <para> - The session output is piped through the GDM daemon and so the - <filename>~/.xsession-errors</filename> 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. - </para> - - <para> - Note that some distributors seem to override the - <filename>~/.xsession-errors</filename> redirection and do it - themselves in their own Xsession script (set by the - <filename>BaseXsession</filename> configuration key) which means that - GDM will not be able to trap the output and cap this file. You also - lose output from the <filename>PreSession</filename> 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 - <filename>BaseXsession</filename> configuration key for more - information, especially on how to handle multiple display managers - using the same script. - </para> - - <para> - 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 - <filename>/tmp</filename> directory named - <filename>/tmp/xses-<user>.XXXXXX</filename> where the - <filename>XXXXXX</filename> are some random characters. - </para> - - <para> - If you run a system with quotas set, it would be good to delete the - <filename>~/.xsession-errors</filename> in the - <filename>PostSession</filename> script. Such that this log file - doesn't unnecessarily stay around. - </para> - </sect2> - - <sect2 id="fileaccess"> - <title>Accessing Files</title> - - <para> - In general GDM is very reluctant regarding reading/writing of user - files (such as the <filename>~/.dmrc</filename>, - <filename>~/.face</filename>, - <filename>~/.xsession-errors</filename>, and - <filename>~/.Xauthority</filename> files). For instance it refuses to - access anything but regular files. Links, sockets and devices are - ignored. The value of the <filename>RelaxPermissions</filename> - parameter determines whether GDM should accept files writable by the - user's group or others. These are ignored by default. - </para> - - <para> - All operations on user files are done with the effective user id of the - user. If the sanity check fails on the user's - <filename>.Xauthority</filename> file, a fallback cookie is created in - the directory specified by the <filename>UserAuthFBDir</filename> - configuration setting (<filename>/tmp</filename> by default). - </para> - - <para> - 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. - </para> - </sect2> - - <sect2 id="performance"> - <title>GDM Performance</title> - - <para> - 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. - </para> - - <para> - To use this feature, configure GDM with the - <command>--with-prefetch</command> option. This will cause GDM to - install the <command>gdmprefetch</command> program to the - <filename>libexecdir</filename> directory, install the - <filename>gdmprefetchlist</filename> to the - <filename><etc>/gdm</filename> directory, and set the - <filename>PreFetchProgram</filename> configuration variable so that the - <command>gdmprefetch</command> program is called with the default - <filename>gdmprefetchlist</filename> file. The default - <filename>gdmprefetchlist</filename> 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 - <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink>, - so that they can be included in future GDM releases. - </para> - </sect2> - </sect1> - - <sect1 id="security"> - <title>Security</title> - - <sect2 id="PAM"> - <title> - PAM - </title> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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 - <address><email>gdm-list@gnome.org</email></address> mail list, - so you can refer to the list archives for more information. - </para> - - <para> - 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 <filename>PamStack</filename> 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. - </para> - </sect2> - - <sect2 id="utmpwtmp"> - <title> - utmp/wtmp - </title> - - <para> - GDM generates utmp and wtmp User Accounting Database entries upon - session login and logout. The utmp database contains user access - and accounting information that is accessed by commands such as - <command>finger</command>, <command>last</command>, - <command>login</command>, and <command>who</command>. The wtmp - database contains the history of user access and accounting - information for the utmp database. - </para> - - <para> - GDM 2.18 and earlier would run the X server <command>sessreg</command> - program from the default GDM <command>PreSession</command> and - <command>PostSession</command> scripts. Starting with GDM 2.20, GDM - interacts with the UTMP and WTMP databases directly and supports the - following configuration options. - </para> - - <para> - When doing utmp processing, GDM supports configurability on how the - ut_line value is set. Programs that access the database assume that - this value is an actual device, so GDM will set the device as follows. - If the display is attached and has an associated Virtual Terminal (VT) - device, then this device will be used. Otherwise, if an attached - display in the <command>[servers]</command> specifies a device name, - then this value will be used. Otherwise attached displays will default - to the <filename>UtmpLineAttached</filename> value in the GDM - configuration. Remote displays will default to the - <filename>UtmpLineRemote</filename> value in the GDM configuration. - Device values must begin with "/dev/". - </para> - - <para> - GDM also supports the <filename>UtmpPseudoDevice</filename> - configuration option. If this configuration setting is true, then GDM - will ensure that the specified device exists and will create a pseudo - device if the device does not exist. A pseudo device is a symlink to - <filename>/dev/null</filename>. If - <filename>UtmpPseudoDevice</filename> is true, and the device does - already exist, GDM checks to see if the device is a symlink to - <filename>/dev/null</filename>. If so, then GDM will update the access - time of the symlink. This ensures that programs that check the access - time of the device will get a reasonable value for the last time the - device was accessed. If the <filename>UtmpPseudoDevice</filename> - configuration option is false, then GDM will only set the ut_line - value as specified regardless of whether the device exists or not. - </para> - </sect2> - - <sect2 id="gdmuser"> - <title>The GDM User</title> - - <para> - 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. - </para> - - <para> - The GDM daemon normally runs as root, as does the slave. However GDM - should also have a dedicated user id and a group id which it uses for - its graphical interfaces such as <command>gdmgreeter</command> and - <command>gdmlogin</command>. These are configured via the - <filename>User</filename> and <filename>Group</filename> - configuration options in the GDM configuration files. The user and - group should be created before running "make install". By - default GDM assumes the user and the group are called "gdm". - </para> - - <para> - 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. - </para> - - <para> - 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 <filename><var>/lib/gdm</filename>. - 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. - </para> - - <para> - 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 <filename>nobody</filename>. 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. - </para> - - <para> - 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. - </para> - </sect2> - - <sect2 id="xauth"> - <title>X Server Authentication Scheme</title> - - <para> - The X server authorization directory (the - <filename>ServAuthDir</filename>) 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 <filename>root.gdm</filename> 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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 <filename>/dev/audio</filename> or - <filename>/dev/mem</filename> 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 - <filename>UserAuthDir</filename> configuration key). So be careful - about where you use remote X display. - </para> - </sect2> - - <sect2 id="firewall"> - <title>Firewall Security</title> - - <para> - Even though GDM tries to outsmart potential attackers trying to take - advantage of XDMCP, it is still advised that you block the XDMCP port - (normally UDP port 177) on your firewall unless 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. - </para> - - <para> - 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. - </para> - - <para> - X is not a very safe protocol for leaving on the net, and XDMCP is - even less safe. - </para> - </sect2> - - <sect2 id="nfssecurity"> - <title>GDM Security With NFS</title> - - <para> - Note that NFS traffic really goes "over the wire" and thus - can be snooped. When accessing the user's X authorization file - (<filename>~/.Xauthority</filename>), 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 - <filename>UserAuthFBDir</filename>, which by default is set to - <filename>/tmp</filename>. This behavior can be changed by setting the - <filename>NeverPlaceCookiesOnNFS</filename> in the - <filename>[security]</filename> section to false. - </para> - </sect2> - - <sect2 id="xdmcpsecurity"> - <title>XDMCP Security</title> - - <para> - Even though your display is protected by cookies, XEvents and thus - keystrokes typed when entering passwords will still go over the wire in - clear text. It is trivial to capture these. - </para> - - <para> - XDMCP is primarily useful for running thin clients such as in terminal - labs. Those thin clients will only ever need the network to access - the server, and so it seems like the best security policy to have - those thin clients on a separate network that cannot be accessed by - the outside world, and can only connect to the server. The only point - from which you need to access outside is the server. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - </sect2> - - <sect2 id="xdmcpaccess"> - <title>XDMCP Access Control</title> - - <para> - XDMCP access control is done using TCP wrappers. It is possible to - compile GDM without TCP wrappers however, so you should test your - configuration and verify that they work. - </para> - - <para> - You should use the daemon name <command>gdm</command> in the - <filename><etc>/hosts.allow</filename> and - <filename><etc>/hosts.deny</filename> files. For example to - deny computers from <filename>.evil.domain</filename> from logging in, - then add - </para> -<screen> -gdm: .evil.domain -</screen> - <para> - to <filename><etc>/hosts.deny</filename>. You may also need - to add - </para> -<screen> -gdm: .your.domain -</screen> - <para> - to your <filename><etc>/hosts.allow</filename> if you normally - disallow all services from all hosts. See the - <ulink type="help" url="man:hosts.allow">hosts.allow(5)</ulink> man - page for details. - </para> - </sect2> - - <sect2 id="rbac"> - <title>RBAC (Role Based Access Control)</title> - - <para> - If GDM is compiled with RBAC support, then the - <filename>RBACSystemCommandKeys</filename> 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 <command>gdmflexiserver</command> 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 - <filename>User</filename> configuration option) has permission - via RBAC. Users will only be able to use the - <command>gdmflexiserver</command> commands if the user has - permission via RBAC. - </para> - </sect2> - </sect1> - - <sect1 id="consolekit"> - <title>Support for ConsoleKit</title> - - <para> - GDM includes support for publishing user login information with the user - and login session accounting framework known as ConsoleKit. ConsoleKit - is able to keep track of all the users currently logged in. In this - respect, it can be used as a replacement for the utmp or utmpx files that - are available on most Unix-like operating systems. - </para> - - <para> - When GDM is about to create a new login process for a user it will call - a privileged method of ConsoleKit in order to open a new session for this - user. At this time GDM also provides ConsoleKit with information about - this user session such as: the user ID, the X11 Display name that will be - associated with the session, the host-name from which the session - originates (useful in the case of an XDMCP session), whether or not this - session is attached, etc. As the entity that initiates the user process, - GDM is in a unique position 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. - </para> - - <para> - 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. - </para> - - <para> - When the user chooses to log out, or if GDM or the session quit - unexpectedly the user session will be unregistered from ConsoleKit. - </para> - - <para> - If support for ConsoleKit is not desired it can be disabled at build - time using the "--with-console-kit=no" option when running - configure. - </para> - - </sect1> - - <sect1 id="gdmsetupusage"> - <title>Using gdmsetup To Configure GDM</title> - - <para> - The <command>gdmsetup</command> 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 - <command>gdmsetup</command>. Editing the files by hand is explained in - the "Configuration" section of this document. Note that - <command>gdmsetup</command> does not support changing of all - configuration variables, so it may be necessary to edit the files by - hand for some configurations. - </para> - - <para> - The <command>gdmsetup</command> 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. - </para> - - <sect2 id="gdmsetuplocaltab"> - <title>Local Tab</title> - - <para> - The Local tab is used for controlling the appearance of GDM for - attached (also known as local or static) displays. Attached displays - are non-XDMCP remote connections, for example. 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. - </para> - - <para> - If the "Style" choice is "Plain", then GDM will - use the <command>gdmlogin</command> program as the GUI - (daemon/Greeter). When this choice is selected, - <command>gdmsetup</command> 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). - </para> - - <para> - If the "Style" choice is "Plain with face browser", - then the <command>gdmlogin</command> 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. - </para> - - <para> - If the "Style" choice is "Themed", then the - <command>gdmgreeter</command> program is used as the GUI - (daemon/Greeter). When this choice is selected, - <command>gdmsetup</command> 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. - </para> - - <para> - If the "Style" choice is "Themed with face - browser", then the <command>gdmgreeter</command> 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. - </para> - - <para> - 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 <command>gdmsetup</command> - (greeter/ConfigAvailable), and whether the Action menu includes the - choice to start <command>gdmchooser</command> to run a remote XDMCP - login session (greeter/ChooserButton). The welcome message for - attached DISPLAYS may be specified (greeter/DefaultWelcome and - greeter/Welcome). The welcome message may contain the character - sequences described in the "Text Node" subsection of the - "Themed Greeter" section of this manual. These character - sequences allow the welcome message to contain things like the display - or host name. - </para> - </sect2> - - <sect2 id="gdmsetupremotetab"> - <title>Remote Tab</title> - - <para> - 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. - </para> - - <para> - If Remote login is enabled, then the welcome message for - remote DISPLAYs may be specified (greeter/DefaultRemoteWelcome and - greeter/RemoteWelcome). This welcome message is separate from the - one shown for attached displays defined in the Local tab and can have - a different value. The welcome message may contain the character - sequences described in the "Text Node" subsection of the - "Themed Greeter" section of this manual. These character - sequences allow the welcome message to contain things like the - display or host name. - </para> - - <para> - 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). - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - </sect2> - - <sect2 id="gdmsetupaccessibilitytab"> - <title>Accessibility Tab</title> - - <para> - 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. - </para> - </sect2> - - <sect2 id="gdmsetupsecuritytab"> - <title>Security Tab</title> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - </sect2> - - <sect2 id="gdmsetupuserstab"> - <title>Users Tab</title> - - <para> - 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. - </para> - </sect2> - </sect1> - - <sect1 id="configuration"> - <title>Configuration</title> - - <para> - 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. - </para> - - <para> - The <command>gdmsetup</command> 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. - </para> - - <para> - Aside from the GDM System Defaults Configuration File, the other GDM - configuration files are located, by default, in the - <filename><etc>/gdm/</filename> 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. - </para> - - <para> - Listing of the config directory contents: - </para> - -<screen> -custom.conf -locale.alias -Xsession -XKeepsCrashing -modules/ -Init/ -PostLogin/ -PreSession/ -PostSession/ -</screen> - - <para> - <filename>locale.alias</filename> 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. - </para> - - <para> - <filename>Xsession</filename> 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 <filename>desktop</filename> - file associated with the session the user has picked. Some - sessions may start the user's session via a different mechanism than - the <filename>Xsession</filename> script, so please check the - appropriate <filename>desktop</filename> before assuming a session - startup issue is being caused by this file. - </para> - - <para> - <filename>XKeepsCrashing</filename> 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. - </para> - - <para> - Accessibility modules are configured in the <filename>modules/</filename> - 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 <filename>factory</filename> in their name, - and those files are not read, they are just there for you so you can - always revert to default config. - </para> - - <para> - Files describing available GDM session follow the freedesktop.org - desktop file specification. The <filename>.desktop</filename>-style - files are installed to <filename><etc>/X11/sessions/</filename>. - This directory is also read by the KDE desktop manager (KDM) for common - configuration. Next the directory - <filename><share>/gdm/BuiltInSessions/</filename> is read for - GDM specific built-in sessions (KDM hardcodes these at time of - this writing). Lastly the default setup will also read - <filename><share>/xsessions/</filename> (which should be - <filename><share>/xsessions/</filename> if you really wish to - cooperate with KDM) where desktop packages can install their session - files. The directories under the <filename><etc></filename> 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 <filename>SessionDesktopDir</filename> configuration key for - changing the paths. It used to be that GDM stored its built in - sessions in <filename><etc>/dm/Sessions/</filename> but this is - deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the - <filename><etc>/dm/Sessions/</filename> was being read. - </para> - - <para> - A session can be disabled (if it was installed in - <filename><share>/xsessions/</filename>) by adding an identically - named <filename>.desktop</filename> to one of the directories earlier in - the path (likely <filename><etc>/X11/sessions</filename>) and using - <filename>Hidden=true</filename> in that file. - </para> - - <para> - GDM uses the optional key <filename>X-Gdm-XserverArgs</filename> in - session files to specify additional arguments to be passed to the - X server. For example, the entry - <filename>X-Gdm-XserverArgs=-depth 16</filename> 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). - </para> - - <sect2 id="scriptdirs"> - <title>The Script Directories</title> - - <para> - In this section we will explain the <filename>Init</filename>, - <filename>PostLogin</filename>, <filename>PreSession</filename> and - <filename>PostSession</filename> directories as they are very similar. - </para> - - <para> - When the X server has been successfully started, GDM will try to run - the script called <filename>Init/<displayname></filename>. I.e. - <filename>Init/:0</filename> for the first attached display. If this - file is not found, GDM will attempt to to run - <filename>Init/<hostname></filename>. I.e. - <filename>Init/somehost</filename>. - If this still is not found, GDM will try - <filename>Init/XDMCP</filename> for all XDMCP logins or - <filename>Init/Flexi</filename> for all on demand flexible - displays. If none of the above were found, GDM will run - <filename>Init/Default</filename>. The script will be run as root and - GDM blocks until it terminates. Use the <filename>Init/*</filename> - 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. - </para> - - <para> - 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 <filename>KillInitClients</filename> configuration - option. - </para> - - <para> - When the user has been successfully authenticated GDM tries the - scripts in the <filename>PostLogin</filename> directory in the same - manner as for the <filename>Init</filename> 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 <filename>pam_mount</filename> module if you can for this). - You have the <filename>$USER</filename> and - <filename>$DISPLAY</filename> 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. - </para> - - <para> - After the user session has been setup from the GDM side of things, GDM - will run the scripts in the <filename>PreSession</filename> directory, - again in the same manner as the <filename>Init</filename> directory. - This script can be used for session management or accounting, for - example. The <filename>$USER</filename> environment variable contains - the login of the authenticated user and <filename>$DISPLAY</filename> - 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 - <filename>$X_SERVERS</filename> environmental variable is set and this - points to a fake generated X servers file for use with the sessreg - accounting application. - </para> - - <para> - After this the base <filename>Xsession</filename> 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 <filename>Exec=</filename> line in the - <filename>.desktop</filename> files in the path specified by - <filename>SessionDesktopDir</filename>. Usually this path is - <filename><etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/xsessions/</filename>. - The first found file is used. The user either picks from these - sessions or GDM will look inside the file <filename>~/.dmrc</filename> - for the stored preference. - </para> - - <para> - 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 - <filename>$GDM_LANG</filename> 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 <filename>$GDM_LANG</filename> is not set. - </para> - - <para> - When the user terminates his session, the - <filename>PostSession</filename> script will be run. Again operation - is similar to <filename>Init</filename>, <filename>PostLogin</filename> - and <filename>PreSession</filename>. Again the script will be run with - root privileges, the slave daemon will block and the - <filename>$USER</filename> environment variable will contain the name - of the user who just logged out and <filename>$DISPLAY</filename> will - be set to the display the user used, however note that the X server for - this display may already be dead and so you shouldn't try to access it. - Also <filename>$X_SERVERS</filename> environmental variable is set and - this points to a fake generated X servers file for use with the sessreg - accounting application. - </para> - - <para> - Note that the <filename>PostSession</filename> script will be run - even when the display fails to respond due to an I/O error or - similar. Thus, there is no guarantee that X applications will work - during script execution. - </para> - - <para> - Except for the <filename>Xsession</filename> script all of these - scripts will also have the environment variable - <filename>$RUNNING_UNDER_GDM</filename> set to - <filename>yes</filename>, so that you could perhaps use similar - scripts for different display managers. The - <filename>Xsession</filename> will always have the - <filename>$GDMSESSION</filename> set to the basename of the - session that the user chose to run without the - <filename>.desktop</filename> extension. In addition - <filename>$DESKTOP_SESSION</filename> is also set to the same value - and in fact this will also be set by KDM in future versions. - </para> - - <para> - Neither of the <filename>Init</filename>, - <filename>PostLogin</filename>, <filename>PreSession</filename> or - <filename>PostSession</filename> scripts are necessary and can be left - out. The <filename>Xsession</filename> script is however required as - well as at least one session <filename>.desktop</filename> file. - </para> - </sect2> - - <sect2 id="configfile"> - <title>The Configuration Files - GDM System Defaults Configuration File - and GDM Custom Configuraiton File</title> - - <para> - GDM uses two configuration files: the GDM System Defaults Configuration - File (<filename><share>/gdm/defaults.conf</filename>) and the - GDM Custom Configuration File - (<filename><etc>/gdm/custom.conf</filename>). 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. - </para> - - <para> - 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. - </para> - - <para> - 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 - <filename><etc>/gdm/custom.conf<display num></filename>. - 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 - <filename><etc>/gdm/custom.conf:0</filename>. Per-display - configuration is supported in GDM 2.14.6 and later. - </para> - - <para> - 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: - </para> - -<screen> -[daemon] -Greeter=/usr/lib/gdmgreeter -</screen> - - <para> - The <command>gdmsetup</command> command can be used to modify the GDM - Custom Configuration File. Note the <command>gdmsetup</command> 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. - </para> - - <para> - The GDM daemon <command>--config</command> 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 <command>--with-defaults-conf</command> and - <command>--with-custom-conf</command> configuration options. - </para> - - <para> - Previous to GDM 2.13.0.4 only the - <filename><etc>/gdm/gdm.conf</filename> 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 <filename><etc>/gdm/gdm.conf</filename> file is different - than the <filename><etc>/gdm/factory-gdm.conf</filename> file. - If so, the <filename><etc>/gdm/gdm.conf</filename> file will be - automatically copied to - <filename><etc>/gdm/custom.conf</filename> to preserve any - configuration changes. - </para> - - <para> - 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. - </para> - - <para> - The GDM System Defaults Configuration File and the GDM Custom - Configuration File follow the standard <filename>.ini</filename> 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. - </para> - - <para> - The following configuration keys are supported in GDM: - </para> - - <sect3 id="daemonsection"> - <title>Daemon Configuration</title> - - <variablelist> - <title>[daemon]</title> - - <varlistentry> - <term>AddGtkModules</term> - <listitem> - <synopsis>AddGtkModules=false</synopsis> - <para> - If true, then enables <command>gdmgreeter</command> or - <command>gdmlogin</command> 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. - </para> - <para> - If true, then the registry daemon - <command>at-spi-registryd</command> - will be launched by <command>gdmgreeter</command> or - <command>gdmlogin</command> starting with version GDM 2.17. - </para> - <para> - Usually this is used for accessibility modules. The modules - which are loaded are specified with the - <filename>GtkModulesList</filename> key. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AllowLogoutActions</term> - <listitem> - <synopsis>AllowLogoutActions=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD</synopsis> - <para> - Specify which actions are supported by the QUERY_LOGOUT_ACTION, - SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION - <command>gdmflexiserver</command> 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 - <filename>SystemCommandsInMenu</filename> and - <filename>RBACSystemCommandKeys</filename> configuration - options. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AlwaysLoginCurrentSession</term> - <listitem> - <synopsis>AlwaysLoginCurrentSession=true</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AutomaticLoginEnable</term> - <listitem> - <synopsis>AutomaticLoginEnable=false</synopsis> - <para> - 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 console security is not an - issue and also could be useful for public terminals. Refer - also to <filename>TimedLogin</filename>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AutomaticLogin</term> - <listitem> - <synopsis>AutomaticLogin=</synopsis> - <para> - 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. - </para> - - <para> - The following control chars are recognized within the - specified name: - </para> - - <para> - %% — the `%' character - </para> - - <para> - %d — display's name - </para> - - <para> - %h — display's hostname - </para> - - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BaseXsession</term> - <listitem> - <synopsis>BaseXsession=<etc>/gdm/Xsession</synopsis> - <para> - 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 - <filename>Exec=</filename> from the - <filename>.desktop</filename> file of the session. - </para> - - <para> - 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 - <filename>GDMSESSION</filename> environmental variable. This - will always be set to the basename of - <filename>.desktop</filename> (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 - <filename>GDM_LANG</filename>, but that is only set when the - user picks a non-system default language. - </para> - - <para> - This script should take care of doing the "login" for - the user and so it should source the - <filename><etc>/profile</filename> and friends. The - standard script shipped with GDM sources the files in this - order: <filename><etc>/profile</filename> then - <filename>~/.profile</filename> then - <filename><etc>/xprofile</filename> and finally - <filename>~/.xprofile</filename>. Note that different - distributions may change this however. Sometimes users - personal setup will be in <filename>~/.bash_profile</filename>, - however broken that is. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Chooser</term> - <listitem> - <synopsis>Chooser=<bin>/gdmchooser</synopsis> - <para> - Full path and name of the chooser executable followed by - optional arguments. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Configurator</term> - <listitem> - <synopsis>Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog</synopsis> - <para> - The pathname to the configurator binary. If the greeter - <filename>ConfigAvailable</filename> 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ConsoleCannotHandle</term> - <listitem> - <synopsis>ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ConsoleNotify</term> - <listitem> - <synopsis>ConsoleNotify=true</synopsis> - <para> - If false, gdm will not display a message dialog on the - console when an error happens. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultPath</term> - <listitem> - <synopsis>DefaultPath=defaultpath (value set by configure)</synopsis> - <para> - Specifies the path which will be set in the user's session. - This value will be overridden with the value from - <filename>/etc/default/login</filename> if it contains - "ROOT=<pathname>". If the - <filename>/etc/default/login</filename> file exists, but - contains no value for ROOT, the value as defined in the GDM - configuration will be be used. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultSession</term> - <listitem> - <synopsis>DefaultSession=gnome.desktop</synopsis> - <para> - 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 <filename>ShowLastSession</filename> key. - </para> - </listitem> - </varlistentry> - - - <varlistentry> - <term>DisplayInitDir</term> - <listitem> - <synopsis>DisplayInitDir=<etc>/gdm/Init</synopsis> - <para> - Directory containing the display init scripts. See the - ``The Script Directories'' section for more info. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DisplayLastLogin</term> - <listitem> - <synopsis>DisplayLastLogin=true</synopsis> - <para> - 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. - </para> - <para> - 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 - <filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> - for more info. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DoubleLoginWarning</term> - <listitem> - <synopsis>DoubleLoginWarning=true</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DynamicXServers</term> - <listitem> - <synopsis>DynamicXServers=false</synopsis> - <para> - If true, the GDM daemon will honor requests to manage - displays via the <filename>/tmp/.gdm_socket</filename> - socket connection. Displays can be created, started, - and deleted with the appropriate commands. The - <filename>gdmdynamic</filename> command is a convenient - method to send these messages. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>FailsafeXServer</term> - <listitem> - <synopsis>FailsafeXServer=</synopsis> - <para> - 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 <filename>XKeepsCrashing</filename> - script is run. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>FirstVT</term> - <listitem> - <synopsis>FirstVT=7</synopsis> - <para> - 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 - <filename>VTAllocation</filename>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>FlexibleXServers</term> - <listitem> - <synopsis>FlexibleXServers=5</synopsis> - <para> - The maximum number of allowed flexible displays. These are - displays that can be run using the - <filename>/tmp/.gdm_socket</filename> socket connection. - This is used for both full flexible displays and for nested - displays (refer to the <filename>Xnest</filename> configuration - option). - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>FlexiReapDelayMinutes</term> - <listitem> - <synopsis>FlexiReapDelayMinutes=5</synopsis> - <para> - 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 <filename>Xnest</filename> configuration - option). To turn off this behavior set this value to 0. This - was added in version 2.5.90.0. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Greeter</term> - <listitem> - <synopsis>Greeter=<bin>/gdmlogin</synopsis> - <para> - 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 - <filename>RemoteGreeter</filename> - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Group</term> - <listitem> - <synopsis>Group=gdm</synopsis> - <para> - The group name under which <command>gdmlogin</command>, - <command>gdmgreeter</command>, - <command>gdmchooser</command> and the internal - failsafe GTK+ dialogs are run. Also see - <filename>User</filename>. 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 <filename>ServAuthDir</filename> - is owned by this group. The ownership and permissions of - <filename>ServAuthDir</filename> should be - <filename>root.gdm</filename> and 1770. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GtkModulesList</term> - <listitem> - <synopsis>GtkModulesList=module-1:module-2:...</synopsis> - <para> - A colon separated list of Gtk+ modules that - <command>gdmgreeter</command> or <command>gdmlogin</command> - will be invoked with if <filename>AddGtkModules</filename> is - true. The format is the same as the standard Gtk+ module - interface. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>HaltCommand</term> - <listitem> - <synopsis>HaltCommand=<sbin>/shutdown -h now</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>KillInitClients</term> - <listitem> - <synopsis>KillInitClients=true</synopsis> - <para> - Determines whether GDM should kill X clients started by the - init scripts when the user logs in. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>LogDir</term> - <listitem> - <synopsis>LogDir=<var>/log/gdm</synopsis> - <para> - Directory containing the log files for the individual displays. - By default this is the same as the ServAuthDir. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PreFetchProgram</term> - <listitem> - <synopsis>PreFetchProgram=command</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PostLoginScriptDir</term> - <listitem> - <synopsis>PostLoginScriptDir=<etc>/gdm/PostLogin</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PostSessionScriptDir</term> - <listitem> - <synopsis>PostSessionScriptDir=<etc>/gdm/PostSession</synopsis> - <para> - Directory containing the scripts run after the user logs out. - See the ``The Script Directories'' section for more info. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PreSessionScriptDir</term> - <listitem> - <synopsis>PreSessionScriptDir=<etc>/gdm/PreSession</synopsis> - <para> - Directory containing the scripts run before the user logs in. - See the ``The Script Directories'' section for more info. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RBACSystemCommandKeys</term> - <listitem> - <synopsis>RBACSystemCommandKeys</synopsis> - <para> - 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 <command>gdmflexiserver</command> - commands. Valid actions are HALT, REBOOT, SUSPEND, and - CUSTOM_CMD. The greeter will only display the command if the - gdm user (<filename>User</filename> 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 <filename>AllowLogoutActions</filename> and - <filename>SystemCommandsInMenu</filename> configuration - options. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>RebootCommand</term> - <listitem> - <synopsis>RebootCommand=<sbin>/shutdown -r now</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RemoteGreeter</term> - <listitem> - <synopsis>RemoteGreeter=<bin>/gdmlogin</synopsis> - <para> - 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 <filename>Greeter</filename> key. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RootPath</term> - <listitem> - <synopsis>RootPath=defaultpath (value set by configure)</synopsis> - <para> - 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 <filename>/etc/default/login</filename> if it - contains "SUROOT=<pathname>". If the - <filename>/etc/default/login</filename> file exists, but - contains no value for SUROOT, the value as defined in the GDM - configuration will be used. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ServAuthDir</term> - <listitem> - <synopsis>ServAuthDir=<var>/gdm</synopsis> - <para> - Directory containing the X authentication files for the - individual displays. Should be owned by - <filename>root.gdm</filename> with permissions 1770, where - <filename>gdm</filename> is the GDM group as defined by the - <filename>Group</filename> option. That is should be owned by - root, with <filename>gdm</filename> 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SessionDesktopDir</term> - <listitem> - <synopsis>SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/</synopsis> - <para> - Directory containing the <filename>.desktop</filename> 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SoundProgram</term> - <listitem> - <synopsis>SoundProgram=<filename><bin>/play</filename> (or <filename><bin>/audioplay</filename> on Solaris)</synopsis> - <para> - Application to use when playing a sound. Currently used for - playing the login sound, see the - <filename>SoundOnLoginFile</filename> key. Supported since - 2.5.90.0. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>StandardXServer</term> - <listitem> - <synopsis>StandardXServer=/dir/to/X (value assigned by configuration file)</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SuspendCommand</term> - <listitem> - <synopsis>SuspendCommand=</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SystemCommandsInMenu</term> - <listitem> - <synopsis>SuspendCommand=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD</synopsis> - <para> - 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 - <command>gdmflexiserver</command> 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 - <filename>AllowLogoutActions</filename> and - <filename>RBACSystemCommandKeys</filename> configuration - options. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>TimedLoginEnable</term> - <listitem> - <synopsis>TimedLoginEnable=false</synopsis> - <para> - If the user given in <filename>TimedLogin</filename> should be - logged in after a number of seconds (set with - <filename>TimedLoginDelay</filename>) of inactivity on the - login screen. This is useful for public access terminals or - perhaps even home use. If the user uses the keyboard or - browses the menus, the timeout will be reset to - <filename>TimedLoginDelay</filename> or 30 seconds, whichever - is higher. If the user does not enter a username but just - hits the ENTER key while the login program is requesting the - username, then GDM will assume the user wants to login - immediately as the timed user. Note that no password will be - asked for this user so you should be careful, although if using - PAM it can be configured to require password entry before - allowing login. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>TimedLogin</term> - <listitem> - <synopsis>TimedLogin=</synopsis> - <para> - This is the user that should be logged in after a specified - number of seconds of inactivity. This can never be - "root" and gdm will refuse to log in root this way. - The same features as for <filename>AutomaticLogin</filename> - are supported. The same control chars and piping to a - application are supported. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>TimedLoginDelay</term> - <listitem> - <synopsis>TimedLoginDelay=30</synopsis> - <para> - Delay in seconds before the <filename>TimedLogin</filename> - user will be logged in. It must be greater then or equal to 10. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>User</term> - <listitem> - <synopsis>User=gdm</synopsis> - <para> - The username under which <command>gdmlogin</command>, - <command>gdmgreeter</command>, - <command>gdmchooser</command> and the internal - failsafe GTK+ dialogs are run. Also see - <filename>Group</filename>. 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>UserAuthDir</term> - <listitem> - <synopsis>UserAuthDir=</synopsis> - <para> - The directory where user's <filename>.Xauthority</filename> - 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: <filename>~/authdir/</filename>. - </para> - - <para> - If you do not use the tilde expansion, then the filename - created will be random, like in - <filename>UserAuthFBDir</filename>. This way many users can - have the same authentication directory. For example you might - want to set this to <filename>/tmp</filename> 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 <filename>/tmp</filename> - directory. - </para> - - <para> - 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 - <filename>NeverPlaceCookiesOnNFS</filename> in the - <filename>[security]</filename> section to false. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>UserAuthFBDir</term> - <listitem> - <synopsis>UserAuthFBDir=/tmp</synopsis> - <para> - If GDM fails to update the user's - <filename>.Xauthority</filename> file a fallback cookie is - created in this directory. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>UserAuthFile</term> - <listitem> - <synopsis>UserAuthFile=.Xauthority</synopsis> - <para> - Name of the file used for storing user cookies. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>VTAllocation</term> - <listitem> - <synopsis>VTAllocation=true</synopsis> - <para> - 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 - <filename>FirstVT</filename>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>XKeepsCrashing</term> - <listitem> - <synopsis>XKeepsCrashing=<etc>/gdm/XKeepsCrashing</synopsis> - <para> - 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 <filename>XKeepsCrashing</filename> - 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. - </para> - <para> - In case <filename>FailsafeXServer</filename> is setup, that - will be tried first. and this only used as a backup if even - that X server keeps crashing. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Xnest</term> - <listitem> - <synopsis>Xnest=<bin>/X11/Xephyr -audit 0</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>XnestUnscaledFontPath</term> - <listitem> - <synopsis>XnestUnscaledFontPath=true</synopsis> - <para> - 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 - <filename>Xnest</filename> configuration option. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="securitysection"> - <title>Security Options</title> - - <variablelist> - <title>[security]</title> - - <varlistentry> - <term>AllowRoot</term> - <listitem> - <synopsis>AllowRoot=true</synopsis> - <para> - Allow root (privileged user) to log in through GDM. Set this - to false if you want to disallow such logins. - </para> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AllowRemoteRoot</term> - <listitem> - <synopsis>AllowRemoteRoot=false</synopsis> - <para> - 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. - </para> - <para> - 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. - </para> - <para> - This value will be overridden and set to false if the - <filename>/etc/default/login</filename> file exists and - contains "CONSOLE=/dev/login", and set to true if the - <filename>/etc/default/login</filename> file exists and - contains any other value or no value for CONSOLE. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>AllowRemoteAutoLogin</term> - <listitem> - <synopsis>AllowRemoteAutoLogin=false</synopsis> - <para> - Allow the timed login feature to work for remote displays. - In other words, remote connections via XDMCP will be allowed to - log into the "TimedLogin" user after the delay - defined by <filename>TimedLoginDelay</filename>. - </para> - <para> - Note that this can make a system quite insecure, and thus is - off by default. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>CheckDirOwner</term> - <listitem> - <synopsis>CheckDirOwner=true</synopsis> - <para> - 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 <filename>RelaxPermissions</filename> 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SupportAutomount</term> - <listitem> - <synopsis>SupportAutomount=false</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DisallowTCP</term> - <listitem> - <synopsis>DisallowTCP=true</synopsis> - <para> - If true, then always append <filename>-nolisten tcp</filename> - to the command line when starting attached X servers, thus - disallowing TCP connection. This is a more secure - configuration if not using remote connections. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>NeverPlaceCookiesOnNFS</term> - <listitem> - <synopsis>NeverPlaceCookiesOnNFS=true</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PasswordRequired</term> - <listitem> - <synopsis>PasswordRequired=false</synopsis> - <para> - 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 - <filename>/etc/default/login</filename> if it contains - "PASSREQ=[YES|NO]". If the - <filename>/etc/default/login</filename> file exists, but - contains no value for PASSREQ, the value as defined in the GDM - configuration will be used. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RelaxPermissions</term> - <listitem> - <synopsis>RelaxPermissions=0</synopsis> - <para> - By default GDM ignores files and directories writable to - other users than the owner. - </para> - - <para> - Changing the value of RelaxPermissions makes it possible to - alter this behavior: - </para> - - <para> - 0 - Paranoia option. Only accepts user owned files and - directories. - </para> - <para> - 1 - Allow group writable files and directories. - </para> - <para> - 2 - Allow world writable files and directories. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RetryDelay</term> - <listitem> - <synopsis>RetryDelay=1</synopsis> - <para> - The number of seconds GDM should wait before reactivating the - entry field after a failed login. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>UserMaxFile</term> - <listitem> - <synopsis>UserMaxFile=65536</synopsis> - <para> - GDM will refuse to read/write files bigger than this number - (specified in bytes). - </para> - - <para> - 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 - <filename>RelaxPermissions</filename> option for more info. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>UtmpLineAttached</term> - <listitem> - <synopsis>UtmpLineAttached=/dev/console (or /dev/dtlocal on Solaris)</synopsis> - <para> - When doing Utmp processing for attached displays, GDM sets the - ut_line to the device associated with the Virtual Terminal (VT) - if it is being used. Otherwise, it will use the value - specified with the display in the - <filename>[servers]</filename> section if a value is provided. - If not, then the default value specified in UtmpLineAttached is - used for attached displays. The value can contain - "%d" which is translated to the DISPLAY value or - "%h" which is translated to the hostname. This value - must begin with <filename>/dev/</filename>. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>UtmpLineRemote</term> - <listitem> - <synopsis>UtmpLineRemote= (or /dev/dtremote on Solaris)</synopsis> - <para> - When doing Utmp processing, GDM sets the ut_line to this value - for remote displays. The value can contain "%d" - which is translated to the DISPLAY value or "%h" - which is translated to the hostname. This value must begin - with <filename>/dev/</filename>. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>UtmpPseudoDevice</term> - <listitem> - <synopsis>PseudoDevice=false (or true on Solaris)</synopsis> - <para> - If the device associated with a display does not exist, then - GDM will create a symlink to <filename>/dev/null</filename>, or - touch it if it is a symlink to <filename>/dev/null</filename>. - Some programs such as <command>last</command>, - <command>finger</command>, or <command>who</command> access the - utmp database and may assume that the device points to an - actual file. Creating such symlinks ensures that such programs - work properly. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="xdmcpsection"> - <title>XDCMP Support</title> - - <variablelist> - <title>[xdmcp]</title> - - <varlistentry> - <term>DisplaysPerHost</term> - <listitem> - <synopsis>DisplaysPerHost=1</synopsis> - <para> - To prevent attackers from filling up the pending queue, GDM - will only allow one connection for each remote computer. If - you want to provide display services to computers with more - than one screen, you should increase the - <filename>DisplaysPerHost</filename> value accordingly. - </para> - - <para> - Note that the number of attached DISPLAYS allowed is not - limited. Only remote connections via XDMCP are limited by - this configuration option. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Enable</term> - <listitem> - <synopsis>Enable=false</synopsis> - <para> - Setting this to true enables XDMCP support allowing remote - displays/X terminals to be managed by GDM. - </para> - - <para> - <filename>gdm</filename> listens for requests on UDP port 177. - See the Port option for more information. - </para> - - <para> - If GDM is compiled to support it, access from remote displays - can be controlled using the TCP Wrappers library. The service - name is <filename>gdm</filename> - </para> - - <para> - You should add -<screen> -gdm:.my.domain -</screen> - to your <filename><etc>/hosts.allow</filename>, depending - on your TCP Wrappers configuration. See the - <ulink type="help" url="man:hosts.allow">hosts.allow(5)</ulink> - man page for details. - </para> - - <para> - Please note that XDMCP is not a particularly secure protocol - and that it is a good idea to block UDP port 177 on your - firewall unless you really need it. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>EnableProxy</term> - <listitem> - <synopsis>EnableProxy=false</synopsis> - <para> - 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. - </para> - <para> - Note, however, that this mode will significantly increase the - burden on the machine hosting the XDMCP sessions - </para> - <para> - See the <filename>FlexiProxy</filename> and - <filename>FlexiProxyDisconnect</filename> options for further - details on how to configure support for this feature. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>HonorIndirect</term> - <listitem> - <synopsis>HonorIndirect=true</synopsis> - <para> - Enables XDMCP INDIRECT choosing (i.e. remote execution of - <filename>gdmchooser</filename>) for X-terminals which don't - supply their own display browser. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxPending</term> - <listitem> - <synopsis>MaxPending=4</synopsis> - <para> - To avoid denial of service attacks, GDM has fixed size queue - of pending connections. Only MaxPending displays can start at - the same time. - </para> - - <para> - Please note that this parameter does *not* limit the number of - remote displays which can be managed. It only limits the number - of displays initiating a connection simultaneously. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxPendingIndirect</term> - <listitem> - <synopsis>MaxPendingIndirect=4</synopsis> - <para> - GDM will only provide <filename>MaxPendingIndirect</filename> - displays with host choosers simultaneously. If more queries - from different hosts come in, the oldest ones will be - forgotten. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxSessions</term> - <listitem> - <synopsis>MaxSessions=16</synopsis> - <para> - Determines the maximum number of remote display connections - which will be managed simultaneously. I.e. the total number of - remote displays that can use your host. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxWait</term> - <listitem> - <synopsis>MaxWait=30</synopsis> - <para> - When GDM is ready to manage a display an ACCEPT packet is sent - to it containing a unique session id which will be used in - future XDMCP conversations. - </para> - - <para> - GDM will then place the session id in the pending queue - waiting for the display to respond with a MANAGE request. - </para> - - <para> - If no response is received within MaxWait seconds, GDM will - declare the display dead and erase it from the pending queue - freeing up the slot for other displays. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxWaitIndirect</term> - <listitem> - <synopsis>MaxWaitIndirect=30</synopsis> - <para> - The MaxWaitIndirect parameter determines the maximum number of - seconds between the time where a user chooses a host and the - subsequent indirect query where the user is connected to the - host. When the timeout is exceeded, the information about the - chosen host is forgotten and the indirect slot freed up for - other displays. The information may be forgotten earlier if - there are more hosts trying to send indirect queries then - <filename>MaxPendingIndirect</filename>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Port</term> - <listitem> - <synopsis>Port=177</synopsis> - <para> - The UDP port number <filename>gdm</filename> should listen to - for XDMCP requests. Don't change this unless you know what - you are doing. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PingIntervalSeconds</term> - <listitem> - <synopsis>PingIntervalSeconds=15</synopsis> - <para> - 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. - </para> - - <para> - Note that GDM in the past used to have a - <filename>PingInterval</filename> configuration key which was - also in minutes. For most purposes you'd want this setting - to be lower 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ProxyReconnect</term> - <listitem> - <synopsis>FlexiProxyReconnect=</synopsis> - <para> - 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. - </para> - <para> - 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. - </para> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ProxyXServer</term> - <listitem> - <synopsis>ProxyXServer=</synopsis> - <para> - The X server command line for a XDMCP proxy. Any nested X - server like Xnest, Xephyr or Xdmx should work fairly well. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Willing</term> - <listitem> - <synopsis>Willing=<etc>/gdm/Xwilling</synopsis> - <para> - When the machine sends a WILLING packet back after a QUERY it - sends a string that gives the current status of this server. - The default message is the system ID, but it is possible to - create a script that displays customized message. If this - script 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. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="commonguioptions"> - <title>Common GUI Configuration Options</title> - - <variablelist> - <title>[gui]</title> - - <varlistentry> - <term>AllowGtkThemeChange</term> - <listitem> - <synopsis>AllowGtkThemeChange=true</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GtkRC</term> - <listitem> - <synopsis>GtkRC=</synopsis> - <para> - Path to a <filename>gtkrc</filename> to read when GDM puts up - a window. You should really now use the - <filename>GtkTheme</filename> key for just setting a theme. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GtkTheme</term> - <listitem> - <synopsis>GtkTheme=Default</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GtkThemesToAllow</term> - <listitem> - <synopsis>GtkThemesToAllow=all</synopsis> - <para> - 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 - <filename>AllowGtkThemeChange</filename> key. Supported since - 2.5.90.2. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxIconWidth</term> - <listitem> - <synopsis>MaxIconWidth=128</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MaxIconHeight</term> - <listitem> - <synopsis>MaxIconHeight=128</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="greetersection"> - <title>Greeter Configuration</title> - - <variablelist> - <title>[greeter]</title> - - <varlistentry> - <term>BackgroundColor</term> - <listitem> - <synopsis>BackgroundColor=#76848F</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundProgramInitialDelay</term> - <listitem> - <synopsis>BackgroundProgramInitialDelay=30</synopsis> - <para> - The background application will be started after at least that - many seconds of inactivity. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RestartBackgroundProgram</term> - <listitem> - <synopsis>RestartBackgroundProgram=true</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundProgramRestartDelay</term> - <listitem> - <synopsis>BackgroundProgramRestartDelay=30</synopsis> - <para> - The background application will be restarted after at least that - many seconds of inactivity. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundImage</term> - <listitem> - <synopsis>BackgroundImage=somefile.png</synopsis> - <para> - If the BackgroundType is 1, then display this file as the - background in the greeter. This only affects the GTK+ - Greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundProgram</term> - <listitem> - <synopsis>BackgroundProgram=<bin>/xeyes</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundRemoteOnlyColor</term> - <listitem> - <synopsis>BackgroundRemoteOnlyColor=true</synopsis> - <para> - On remote displays only set the color background. This is to - make network load lighter. The - <filename>BackgroundProgram</filename> is also not run. This - only affects the GTK+ Greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundScaleToFit</term> - <listitem> - <synopsis>BackgroundScaleToFit=true</synopsis> - <para> - Scale background image to fit the screen. This only affects - the GTK+ Greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>BackgroundType</term> - <listitem> - <synopsis>BackgroundType=2</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Browser</term> - <listitem> - <synopsis>Browser=true</synopsis> - <para> - 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 - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ChooserButton</term> - <listitem> - <synopsis>ChooserButton=true</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ConfigAvailable</term> - <listitem> - <synopsis>ConfigAvailable=false</synopsis> - <para> - 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 - <filename>Configurator</filename> option in the daemon - section. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultFace</term> - <listitem> - <synopsis>DefaultFace=<share>/pixmaps/nophoto.png</synopsis> - <para> - If a user has no defined face image, GDM will use the - "stock_person" icon defined in the current GTK+ - theme. If no such image is defined, the image specified by - <filename>DefaultFace</filename> will be used. The image must - be in a gdk-pixbuf supported format and the file must be - readable to the GDM user. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Include</term> - <listitem> - <synopsis>Include=</synopsis> - <para> - Comma separated list of users to be included in the face - browser and in the <command>gdmsetup</command> selection list - for Automatic/Timed login. - See also <filename>Exclude</filename>, - <filename>IncludeAll</filename>, and - <filename>MinimalUID</filename>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Exclude</term> - <listitem> - <synopsis>Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,...</synopsis> - <para> - Comma separated list of users to be excluded from the face - browser and from the <command>gdmsetup</command> selection list - for Automatic/Timed login. Excluded users will still be able to - log in, but will have to type their username. - See also <filename>Include</filename>, - <filename>IncludeAll</filename>, and - <filename>MinimalUID</filename>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>IncludeAll</term> - <listitem> - <synopsis>IncludeAll=false</synopsis> - <para> - 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 <filename>Include</filename>, - <filename>Exclude</filename>, and - <filename>MinimalUID</filename>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GlobalFaceDir</term> - <listitem> - <synopsis>GlobalFaceDir=<share>/pixmaps/faces/</synopsis> - <para> - Systemwide directory for face files. The sysadmin can place - icons for users here without touching their homedirs. Faces are - named after their users' logins. - </para> - - <para> - I.e. <filename><GlobalFaceDir>/johndoe</filename> would - contain the face icon for the user ``johndoe''. No image format - extension should be specified. - </para> - - <para> - The face images must be stored in gdk-pixbuf supported formats - and they must be readable for the GDM user. - </para> - - <para> - A user's own icon file will always take precedence over the - sysadmin provided one. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GraphicalTheme</term> - <listitem> - <synopsis>GraphicalTheme=circles</synopsis> - <para> - The graphical theme that the Themed Greeter should use. it - should refer to a directory in the theme directory set by - <filename>GraphicalThemeDir</filename>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GraphicalThemes</term> - <listitem> - <synopsis>GraphicalThemes=circles</synopsis> - <para> - 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 <filename>GraphicalThemeDir</filename>. This - is only used if <filename>GraphicalThemeRand</filename> is set - to true. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GraphicalThemeRand</term> - <listitem> - <synopsis>GraphicalThemeRand=false</synopsis> - <para> - Whether the graphical greeter will use Only One Theme or Random - Theme mode. Only One Theme mode uses themes listed by - <filename>GraphicalTheme</filename>, Random Themes mode uses - themes listed by <filename>GraphicalThemes</filename>. A value - of false sets greeter to use Only One Theme mode, a value of - true sets the greeter to use Random Theme mode. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GraphicalThemeDir</term> - <listitem> - <synopsis>GraphicalThemeDir=<share>/gdm/themes/</synopsis> - <para> - The directory where themes for the Themed Greeter are - installed. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>GraphicalThemedColor</term> - <listitem> - <synopsis>GraphicalThemedColor=#76848F</synopsis> - <para> - Use this color in the background of the Themed Greeter. - This only affects the Themed Greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>InfoMsgFile</term> - <listitem> - <synopsis>InfoMsgFile=/path/to/infofile</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>InfoMsgFont</term> - <listitem> - <synopsis>InfoMsgFont=fontspec</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - - <varlistentry> - <term>LocaleFile</term> - <listitem> - <synopsis>LocaleFile=<etc>/gdm/locale.alias</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>LockPosition</term> - <listitem> - <synopsis>LockPosition=true</synopsis> - <para> - If true the position of the login window of the GTK+ - Greeter cannot be changed even if the title bar is turned on. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Logo</term> - <listitem> - <synopsis>Logo=<share>/pixmaps/gnome-logo-large.png</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ChooserButtonLogo</term> - <listitem> - <synopsis>ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png</synopsis> - <para> - Image file to display in the file chooser button in - <command>gdmsetup</command>. This key is modified by - <command>gdmsetup</command> and should not be manually - modified by the user. This only affects the Login Window - Preferences (<command>gdmsetup</command>). - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MinimalUID</term> - <listitem> - <synopsis>MinimalUID=100</synopsis> - <para> - The minimal UID that GDM should consider a user. All - users with a lower UID will be excluded from the face browser. - See also <filename>Include</filename>, - <filename>Exclude</filename>, and - <filename>IncludeAll</filename>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PositionX</term> - <listitem> - <synopsis>PositionX=200</synopsis> - <para> - The horizontal position of the login window of the GTK+ - Greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>PositionY</term> - <listitem> - <synopsis>PositionY=100</synopsis> - <para> - The vertical position of the login window of the GTK+ - Greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Quiver</term> - <listitem> - <synopsis>Quiver=true</synopsis> - <para> - Controls whether <command>gdmlogin</command> should - shake the display when an incorrect username/password is - entered. - This only affects the GTK+ Greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultRemoteWelcome</term> - <listitem> - <synopsis>DefaultRemoteWelcome=true</synopsis> - <para> - If set to true, the value "Welcome to %n" is used for - the <filename>RemoteWelcome</filename>. This value is - translated into the appropriate language for the user. If set - to false, the <filename>RemoteWelcome</filename> 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". - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RemoteWelcome</term> - <listitem> - <synopsis>RemoteWelcome=Welcome to %n</synopsis> - <para> - 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 <filename>Welcome</filename> string. - This string can use the same special character sequences as - explained in the "Text Node" section of the - "Themed Greeter" chapter. - chapter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RunBackgroundProgramAlways</term> - <listitem> - <synopsis>RunBackgroundProgramAlways=false</synopsis> - <para> - If this is true then the background application is run always, - otherwise it is only run when the - <filename>BackgroundType</filename> is 0 (None) - This only affects the GTK+ Greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SetPosition</term> - <listitem> - <synopsis>SetPosition=true</synopsis> - <para> - If true the position of the login window of the GTK+ Greeter - is determined by <filename>PositionX</filename> - / <filename>PositionY</filename>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ShowGnomeFailsafeSession</term> - <listitem> - <synopsis>ShowGnomeFailsafeSession=true</synopsis> - <para> - Should the greeter show the Gnome Failsafe session in th - sessions list. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ShowLastSession</term> - <listitem> - <synopsis>ShowLastSession=true</synopsis> - <para> - 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 <filename>DefaultSession</filename>) unless then pick - something else for this session only. So if this is off, this - really circumvents saving of the last session. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ShowXtermFailsafeSession</term> - <listitem> - <synopsis>ShowXtermFailsafeSession=true</synopsis> - <para> - Should the greeter show the Xterm Failsafe session in the - sessions list. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SoundOnLogin</term> - <listitem> - <synopsis>SoundOnLogin=true</synopsis> - <para> - If true, the greeter will play a sound or beep when it is - ready for a login. See also the - <filename>SoundOnLoginFile</filename> key. - Supported since 2.5.90.0. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SoundOnLoginSuccess</term> - <listitem> - <synopsis>SoundOnLoginSuccess=true</synopsis> - <para> - If true, the greeter will play a sound after a successful login - attempt. See also the - <filename>SoundOnLoginSuccessFile</filename> key. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SoundOnLoginFailure</term> - <listitem> - <synopsis>SoundOnLoginFailure=true</synopsis> - <para> - If true, the greeter will play a sound after a failed login - attempt. See also the - <filename>SoundOnLoginFailureFile</filename> key. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SoundOnLoginFile</term> - <listitem> - <synopsis>SoundOnLoginFile=/path/to/sound.wav</synopsis> - <para> - The file that will be played using the specified sound - application (by default that is - <filename>/usr/bin/play</filename>) instead of a beep when the - greeter is ready for a login. See also the - <filename>SoundOnLogin</filename> key and the - <filename>SoundProgram</filename> key. Supported since - 2.5.90.0. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SoundOnLoginSuccessFile</term> - <listitem> - <synopsis>SoundOnLoginSuccessFile=/path/to/sound.wav</synopsis> - <para> - The file that will be played using the specified sound - application (by default that is - <filename>/usr/bin/play</filename>) after a successful login - attempt. See also the <filename>SoundOnLoginSuccess</filename> - key and the <filename>SoundProgram</filename> key. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SoundOnLoginFailureFile</term> - <listitem> - <synopsis>SoundOnLoginFailureFile=/path/to/sound.wav</synopsis> - <para> - The file that will be played using the specified sound - application (by default that is - <filename>/usr/bin/play</filename>) after a failed login - attempt. See also the <filename>SoundOnLoginFailure</filename> - key and the <filename>SoundProgram</filename> key. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>SystemMenu</term> - <listitem> - <synopsis>SystemMenu=true</synopsis> - <para> - 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 attached displays. - It would not be safe or even desirable on remote logins, so you - do not have to worry about remote users having these privileges. - </para> - - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>TitleBar</term> - <listitem> - <synopsis>TitleBar=true</synopsis> - <para> - Display the title bar in the greeter. - This only affects the GTK+ Greeter. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Use24Clock</term> - <listitem> - <synopsis>Use24Clock=auto</synopsis> - <para> - Select the use of 24 hour clock. Some locales do not - support 12 hour format (like Finnish, that is - <filename>fi_FI</filename>), and in those locales this - setting has no effect at all. - </para> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>UseCirclesInEntry</term> - <listitem> - <synopsis>UseCirclesInEntry=false</synopsis> - <para> - Use circles instead of asterisks in the password entry. - This may not work with all fonts however. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>UseInvisibleInEntry</term> - <listitem> - <synopsis>UseInvisibleInEntry=false</synopsis> - <para> - Do not show any visual feedback is the password entry. - This is the standard in console and xdm. Settings this - option discards the <filename>UseCirclesInEntry</filename> - option. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultWelcome</term> - <listitem> - <synopsis>DefaultWelcome=true</synopsis> - <para> - If set to true, the value "Welcome" is used for the - <filename>Welcome</filename>. This value is translated - into the appropriate language for the user. If set to - false, the <filename>Welcome</filename> setting is used. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Welcome</term> - <listitem> - <synopsis>Welcome=Welcome</synopsis> - <para> - Controls which text to display next to the logo image in the - standard greeter. The following control chars are supported: - </para> - - <para> - %% — the `%' character - </para> - - <para> - %d — display's hostname - </para> - - <para> - %h — Fully qualified hostname - </para> - - <para> - %m — machine (processor type) - </para> - - <para> - %n — Nodename (i.e. hostname without .domain) - </para> - - <para> - %r — release (OS version) - </para> - - <para> - %s — sysname (i.e. OS) - </para> - - <para> - This string is only used for attached displays. For remote - XDMCP displays we use <filename>RemoteWelcome</filename>. - </para> - - <para> - 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. - </para> - - </listitem> - </varlistentry> - - <varlistentry> - <term>XineramaScreen</term> - <listitem> - <synopsis>XineramaScreen=0</synopsis> - <para> - 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...). - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="choosersection"> - <title>XDCMP Chooser Options</title> - - <variablelist> - <title>[chooser]</title> - - <varlistentry> - <term>AllowAdd</term> - <listitem> - <synopsis>AllowAdd=true</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Broadcast</term> - <listitem> - <synopsis>Broadcast=true</synopsis> - <para> - 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 <filename>Hosts</filename> key. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Multicast</term> - <listitem> - <synopsis>Multicast=true</synopsis> - <para> - If true and IPv6 is enabled, the chooser will send a multicast - query to the local network and collect responses from the hosts - who have joined multicast group. If you don't want to send a - multicast, you can specify IPv6 address in the <filename>Hosts - </filename> key. The host will respond if it is listening to - XDMCP requests and IPv6 is enabled there. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MulticastAddr</term> - <listitem> - <synopsis>MulticastAddr=ff02::1</synopsis> - <para> - This is the Link-local Multicast address and is hardcoded here. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>DefaultHostImage</term> - <listitem> - <synopsis>DefaultHostImage=<share>/pixmaps/nohost.png</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>HostImageDir</term> - <listitem> - <synopsis>HostImageDir=<share>/hosts</synopsis> - <para> - Repository for host icon files. The sysadmin can place icons - for remote hosts here and they will appear in - <filename>gdmchooser</filename>. - </para> - - <para> - 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. - </para> - - </listitem> - </varlistentry> - - <varlistentry> - <term>Hosts</term> - <listitem> - <synopsis>Hosts=host1,host2</synopsis> - <para> - 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 <filename>Broadcast</filename> 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>ScanTime</term> - <listitem> - <synopsis>ScanTime=4</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="debugsection"> - <title>Debug Configuration</title> - - <variablelist> - <title>[debug]</title> - - <varlistentry> - <term>Enable</term> - <listitem> - <synopsis>Enable=false</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Gestures</term> - <listitem> - <synopsis>Gestures=false</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="customcmdsection"> - <title>Custom Commands</title> - - <para> - 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]. - - </para> - - <variablelist> - <title>[customcommand]</title> - - <varlistentry> - <term>CustomCommand[0-9]</term> - <listitem> - <synopsis>CustomCommand[0-9]=</synopsis> - <para> - Full path and arguments to command to be executed when user - selects <filename>n-th</filename> "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 - <filename>CustomCommand</filename> suffix and can be an - integer between 0 and 9. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>CustomCommandIsPersistent[0-9]</term> - <listitem> - <synopsis>CustomCommandIsPersistent[0-9]=</synopsis> - <para> - Specifies if <filename>n-th</filename> "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 - <filename>CustomCommand</filename> is defined. [0-9] represents - <filename>CustomCommand</filename> suffix and can be an integer - between 0 and 9. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>CustomCommandLabel[0-9]</term> - <listitem> - <synopsis>CustomCommandLabel[0-9]=</synopsis> - <para> - Specifies the stock label that will be displayed on the - <filename>n-th</filename> "Custom Command" - buttons and menu items. If not specified the default value is - "Custom_[0-9]". This option is only valid if - corresponding <filename>CustomCommand</filename> is defined. - [0-9] represents <filename>CustomCommand</filename> suffix - and can be an integer between 0 and 9. This option can't contain - any semicolon characters (i.e. ";"). - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>CustomCommandLRLabel[0-9]</term> - <listitem> - <synopsis>CustomCommandLRLabel[0-9]=</synopsis> - <para> - Specifies the stock label that will be displayed on the - <filename>n-th</filename> "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 - <filename>CustomCommand</filename> is defined. [0-9] - represents <filename>CustomCommand</filename> suffix and - can be an integer between 0 and 9. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>CustomCommandNoRestart[0-9]</term> - <listitem> - <synopsis>CustomCommandNoRestart[0-9]=</synopsis> - <para> - Specifies if gdm will be stopped/restarted once - <filename>n-th</filename> "Custom Command" - has been executed. If not specified the default value is - "false". This option is only valid if corresponding - <filename>CustomCommand</filename> is defined. [0-9] - represents <filename>CustomCommand</filename> suffix and - can be an integer between 0 and 9. In addition when - corresponding <filename>CustomCommandIsPersistent</filename> - is set to true, setting CustomCommandNoRestart to false will - place corresponding <filename>CustomCommand</filename> in the - Shut Down dialog set of actions, setting it to true will place - corresponding - <filename>CustomCommand</filename> in the Log Out dialog set of - actions. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>CustomCommandText[0-9]</term> - <listitem> - <synopsis>CustomCommandText[0-9]=</synopsis> - <para> - Specifies the message that will be displayed on the warning - dialog box once <filename>n-th</filename> - "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 <filename>CustomCommand</filename> is defined. - [0-9] represents <filename>CustomCommand</filename> suffix and - can be an integer between 0 and 9. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>CustomCommandTooltip[0-9]</term> - <listitem> - <synopsis>CustomCommandTooltip[0-9]=</synopsis> - <para> - Specifies the message that will be displayed on tooltips for - <filename>n-th</filename> "Custom Command" - entries. If not specified the default value is "Execute - custom command [0-9]". This option is only valid if - corresponding <filename>CustomCommand</filename> is defined. - [0-9] represents <filename>CustomCommand</filename> suffix and - can be an integer between 0 and 9. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="xserverdefs"> - <title>X Server Definitions</title> - - <para> - GDM needs to be provided with information about each X servers that - will be used. You can have as many different definitions as you wish, - each identified with a unique name. The name - <filename>Standard</filename> is required. If you do not specify - this server, GDM will assume default values for a 'Standard' server - and the path given by <filename>daemon/StandardXServer</filename>. - <filename>Standard</filename> is used as the default, - in situations when no other server has been defined. - </para> - - <para> - Servers are defined by sections named <filename>server-</filename> - 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, <filename>server-</filename> - sections in the <filename><etc>/gdm/custom.conf</filename> - file override values in the - <filename><share>/gdm/defaults.conf</filename> file. In other - words, if a <filename>server-Standard</filename> section is defined - in <filename><etc>/gdm/custom.conf</filename>, then that - will be used and the section in the - <filename><share>/gdm/defaults.conf</filename> file will be - ignored. - </para> - - <variablelist> - <title>[server-Standard]</title> - - <varlistentry> - <term>name</term> - <listitem> - <synopsis>name=Standard server</synopsis> - <para> - The name that will be displayed to the user. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>command</term> - <listitem> - <synopsis>command=/path/to/X</synopsis> - <para> - The command to execute, with full path to the binary of the X - server, and any extra arguments needed. Normally it is not - necessary to add a <filename>-nolisten tcp</filename> argument - since the addition of this argument is controlled by the - <filename>DisallowTCP</filename> GDM configuration option. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>flexible</term> - <listitem> - <synopsis>flexible=true</synopsis> - <para> - Indicates if this server is available as a choice when a - user wishes to run a flexible, on demand server. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>handled</term> - <listitem> - <synopsis>handled=true</synopsis> - <para> - Indicates that GDM should run the login window on this server - and allow a user to log in. If set to false, then GDM will - just run this server and wait for it to terminate. This can be - useful to run an X terminal using GDM. When this is done you - should normally also add <filename>-terminate</filename> to the - command line of the server to make the server terminate after - each session. Otherwise the control of the slave will never - come back to GDM and, for example, soft restarts won't work. - This is because GDM assumes there is a login in progress for - the entire time this server is active. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>chooser</term> - <listitem> - <synopsis>chooser=false</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>priority</term> - <listitem> - <synopsis>priority=0</synopsis> - <para> - 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. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="attacheddisplayconfig"> - <title>Attached DISPLAY Configuration</title> - - <para> - The attached (also known as local or 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 attached displays that are managed as you wish. - Typically each display is associated with a real display. On a - typical single-display machine this section would only contain one - key <filename>0</filename> that corresponds to DISPLAY - <filename>:0</filename>. - </para> - - <para> - The GUI configuration program allows users to edit the attached - display configuration defined in the GDM configuration files - and allows the user to add or delete entries. Like normal - configuration options, the <filename>[servers]</filename> - section in the <filename><etc>/gdm/custom.conf</filename> - file overrides values in the - <filename><share>/gdm/defaults.conf</filename> file. - </para> - - <variablelist> - <title>[servers]</title> - - <varlistentry> - <term><display number></term> - <listitem> - <synopsis>0=Standard [device=/dev/foo]</synopsis> - - <para> - The key cooresponds to the DISPLAY to be managed, so that - key <filename>0</filename> cooresponds to DISPLAY - <filename>:0</filename>. On a multi-display machine you - can configure GDM to manage a login program on other displays - by adding additional keys. For example, adding key - <filename>1</filename> would cause GDM to manage DISPLAY - <filename>:1</filename>. - </para> - - <para> - The first word of the value corresponds to a X server - definition in the "X Server Definitions" section - of the configuration file. For example, the following entry - means that DISPLAY <filename>:0</filename> will start an X - server as defined in the - <filename>[server-Standard]</filename> section: - </para> - -<screen> -[servers] -0=Standard -</screen> - - <para> - The first word of the value can also be set to the string - "inactive" to indicate that this DISPLAY should not - be 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. - </para> - - <para> - The optional device argument is used to specify the device that - is associated with the DISPLAY. When using Virtual Terminals - (VT), this value is ignored and GDM will use the correct - device name associated with the VT. If not using VT, then GDM - will use the value specified by this optional argument. If - the device argument is not defined, then GDM will use the - default setting for attached displays defined in the - <filename>UtmpLineAttached</filename> configuration section. - For the main display (typically DISPLAY - <filename>:0</filename>), <filename>/dev/console</filename> is - a reasonable value. For other displays it is probably best - to not include this argument unless you know the specific - device associated with the DISPLAY. The device value can - contain "%d" which is translated to the DISPLAY value - or "%h" which is translated to the hostname. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - </sect2> - - <sect2 id="userconfig"> - <title>Per User Configuration</title> - - <para> - 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 - <filename>UserMaxFile</filename> 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. - </para> - - <para> - First there is the <filename>~/.dmrc</filename> file. In - theory this file should be shared between GDM and KDM, so users only - have to configure things once. This is a standard - <filename>.ini</filename> style configuration file. It has one section - called <filename>[Desktop]</filename> which has two keys: - <filename>Session</filename> and <filename>Language</filename>. - </para> - - <para> - The <filename>Session</filename> key specifies the basename of the - session <filename>.desktop</filename> file that the user wishes to - normally use (without the <filename>.desktop</filename> extension, in - other words). The <filename>Language</filename> key specifies the - language that the user wishes to use by default. If either of these - keys is missing, the system default is used. The file would normally - look as follows: - </para> - -<screen> -[Desktop] -Session=gnome -Language=cs_CZ.UTF-8 -</screen> - - <para> - 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. - </para> - - <para> - If the GDM Face Browser is turned on, then the file - <filename>$HOME/.face</filename> 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 <filename>MaxIconWidth</filename> and - <filename>MaxIconHeight</filename> values defined in the GDM - configuration or it will be ignored. Users can run the - <command>gdmphotosetup</command> program to specify a face image - and it will copy the file to the <filename>$HOME/.face</filename> - location and scale it so its longest dimension is not larger than the - <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> - values. <command>gdmphotosetup</command> takes care to not change - the aspect ratio of the image. - </para> - - <para> - Face images can also be placed in the global face directory, which is - specified by the <filename>GlobalFaceDir</filename> configuration - option ( normally <filename><share>/pixmaps/faces/</filename>) - and the filename should be the name of the user, optionally with a - <filename>.png</filename>, <filename>.jpg</filename>, etc. appended. - </para> - </sect2> - </sect1> - - <sect1 id="controlling"> - <title>Controlling GDM</title> - - <para> - 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. - </para> - - <sect2 id="commands"> - <title>Commands</title> - - <para> - To stop GDM, you can either send the TERM signal to the main daemon or - run the <command>gdm-stop</command> command which is in the - <filename><sbin>/</filename> directory. To restart GDM, you can - either send the HUP signal to the main daemon or run the - <command>gdm-restart</command> command which is also in the - <filename><sbin>/</filename> 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 - <command>gdm-safe-restart</command> command which is in the - <filename><sbin>/</filename> directory as well. - </para> - - <para> - The <command>gdmflexiserver</command> 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 <command>gdmflexiserver</command> 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 - <command>gdmflexiserver --help</command> to get a listing of possible - options. - </para> - </sect2> - - <sect2 id="fifoprot"> - <title>The FIFO protocol</title> - - <para> - GDM also provides a FIFO called <filename>.gdmfifo</filename> in the - <filename>ServAuthDir</filename> directory - (usually <filename><var>/gdm/.gdmfifo</filename>). 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). - </para> - - <para> - Full and up to date documentation of the commands and their use is - contained in the GDM source tree in the file - <filename>daemon/gdm.h</filename>. Look for the defines starting with - <filename>GDM_SOP_</filename>. The commands which require the - pid of the slave as an argument are the ones that are really used for - internal communication of the slave with the master and should not be - used. - </para> - </sect2> - - <sect2 id="socketprot"> - <title>Socket Protocol</title> - - <para> - GDM provides a unix domain socket for communication at - <filename>/tmp/.gdm_socket</filename>. 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 <command>gdmflexiserver</command> command uses this - protocol, for example, to launch flexible (on-demand) displays. - </para> - - <para> - gdmflexiserver accepts the following commands with the --command - option: - </para> - -<screen> -ADD_DYNAMIC_DISPLAY -ALL_SERVERS -ATTACHED_SERVERS -AUTH_LOCAL -CLOSE -FLEXI_XNEST -FLEXI_XNEST_USER -FLEXI_XSERVER -FLEXI_XSERVER_USER -GET_CONFIG -GET_CONFIG_FILE -GET_CUSTOM_CONFIG_FILE -GET_SERVER_LIST -GET_SERVER_DETAILS -GREETERPIDS -QUERY_LOGOUT_ACTION -QUERY_CUSTOM_CMD_LABELS -QUERY_CUSTOM_CMD_NO_RESTART_STATUS -QUERY_VT -RELEASE_DYNAMIC_DISPLAYS -REMOVE_DYNAMIC_DISPLAY -SERVER_BUSY -SET_LOGOUT_ACTION -SET_SAFE_LOGOUT_ACTION -SET_VT -UPDATE_CONFIG -VERSION -</screen> - - <para> - These are described in detail below, including required arguments, - response format, and return codes. - </para> - - <sect3 id="adddynamic"> - <title>ADD_DYNAMIC_DISPLAY</title> -<screen> -ADD_DYNAMIC_DISPLAY: Create a new server definition that will - run on the specified display leaving, it - in DISPLAY_CONFIG state. -Supported since: 2.8.0.0 -Arguments: <display to run on>=<server> - Where <server> is either a configuration named in the - GDM configuration or a literal command name. -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 2 = Existing display - 3 = No server string - 4 = Display startup failure - 100 = Not authenticated - 200 = Dynamic Displays not allowed - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="allservers"> - <title>ALL_SERVERS</title> -<screen> -ALL_SERVERS: List all displays, including console, remote, xnest. - This can, for example, be useful to figure out if - the display you are on is managed by the gdm daemon, - by seeing if it is in the list. It is also somewhat - like the 'w' command but for graphical sessions. -Supported since: 2.4.2.96 -Arguments: None -Answers: - OK <server>;<server>;... - - <server> is <display>,<logged in user> - - <logged in user> can be empty in case no one logged in yet - - ERROR <err number> <english error description> - 0 = Not implemented - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="attachedservers"> - <title>ATTACHED_SERVERS</title> -<screen> -ATTACHED_SERVERS: List all attached displays. Doesn't list XDMCP - and xnest non-attached displays. -Note: This command used to be named CONSOLE_SERVERS, - which is still recognized for backwards - compatibility. The optional pattern argument - is supported as of version 2.8.0.0. -Supported since: 2.2.4.0 -Arguments: <pattern> (optional) - With no argument, all attached displays are returned. The optional - <pattern> is a string that may contain glob characters '*', '?', and - '[]'. Only displays that match the pattern will be returned. -Answers: - OK <server>;<server>;... - - <server> is <display>,<logged in user>,<vt or xnest - display> - - <logged in user> can be empty in case no one logged - in yet, and <vt> can be -1 if it's not known or not - supported (on non-Linux for example). If the display is an - xnest display and is a console one (that is, it is an xnest - inside another console display) it is listed and instead of - vt, it lists the parent display in standard form. - - ERROR <err number> <english error description> - 0 = Not implemented - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="authlocal"> - <title>AUTH_LOCAL</title> -<screen> -AUTH_LOCAL: Setup this connection as authenticated for - FLEXI_SERVER. Because all full blown - (non-nested) displays can be started only from - users logged into attached displays, and here GDM - assumes only users logged in from GDM. They must - pass the xauth MIT-MAGIC-COOKIE-1 that they were - passed before the connection is authenticated. -Note: The AUTH LOCAL command requires the - --authenticate option, although only - FLEXI XSERVER uses this currently. -Note: Since 2.6.0.6 you can also use a global - <ServAuthDir>/.cookie, which works for all - authentication except for SET_LOGOUT_ACTION and - QUERY_LOGOUT_ACTION and SET_SAFE_LOGOUT_ACTION - which require a logged in display. -Supported since: 2.2.4.0 -Arguments: <xauth cookie> - <xauth cookie> is in hex form with no 0x prefix -Answers: - OK - ERROR <err number> <english error description> - 0 = Not implemented - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="close"> - <title>CLOSE</title> -<screen> -CLOSE: Close sockets connection -Supported since: 2.2.4.0 -Arguments: None -Answers: None -</screen> - </sect3> - - <sect3 id="flexixnest"> - <title>FLEXI_XNEST</title> -<screen> -FLEXI_XNEXT: Start a new flexible nested display. -Note: Supported on older version from 2.2.4.0, later - 2.2.4.2, but since 2.3.90.4 you must supply 4 - arguments or ERROR 100 will be returned. This - will start the nested X server command using - the XAUTHORITY file supplied and as the uid - same as the owner of that file (and same as - you supply). You must also supply the cookie as - the third argument for this display, to prove - that you indeed are this user. Also this file - must be readable ONLY by this user, that is - have a mode of 0600. If this all is not met, - ERROR 100 is returned. -Note: The cookie should be the MIT-MAGIC-COOKIE-1, - the first one GDM can find in the XAUTHORITY - file for this display. If that's not what you - use you should generate one first. The cookie - should be in hex form. -Supported since: 2.3.90.4 -Arguments: <display to run on> <uid of requesting user> - <xauth cookie for the display> <xauth file> -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = No more flexi servers - 2 = Startup errors - 3 = X failed - 4 = X too busy - 5 = Xnest can't connect - 6 = No server binary - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="flexixnestuser"> - <title>FLEXI_XNEST_USER</title> -<screen> -FLEXI_XNEST_USER: Start a new flexible nested display and - initialize the greeter with the given username. -Note: This is a variant of the FLEXI_XNEST command. -Note: The cookie should be the MIT-MAGIC-COOKIE-1, - the first one GDM can find in the XAUTHORITY - file for this display. If that's not what you - use you should generate one first. The cookie - should be in hex form. -Supported since: 2.17.7 -Arguments: <username> <display to run on> <uid of requesting - user> <xauth cookie for the display> <xauth file> -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = No more flexi servers - 2 = Startup errors - 3 = X failed - 4 = X too busy - 5 = Xnest can't connect - 6 = No server binary - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="flexixserver"> - <title>FLEXI_XSERVER</title> -<screen> -FLEXI_XSERVER: Start a new X flexible display. Only supported on - connection that passed AUTH_LOCAL -Supported since: 2.2.4.0 -Arguments: <xserver type> - If no arguments, starts the standard X server -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = No more flexi servers - 2 = Startup errors - 3 = X failed - 4 = X too busy - 6 = No server binary - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="flexixserveruser"> - <title>FLEXI_XSERVER_USER</title> -<screen> -FLEXI_XSERVER_USER: Start a new X flexible display and initialize the - greeter with the given username. Only supported on - connection that passed AUTH_LOCAL -Supported since: 2.17.7 -Arguments: <username> <xserver type> - If no server type specified, starts the standard X server -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = No more flexi servers - 2 = Startup errors - 3 = X failed - 4 = X too busy - 6 = No server binary - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="getconfig"> - <title>GET_CONFIG</title> -<screen> -GET_CONFIG: Get configuration value for key. Useful so - that other applications can request configuration - information from GDM. Any key defined as GDM_KEY_* - in gdm-daemon-config-keys.h is supported. Starting with version - 2.13.0.2, translated keys (such as - "greeter/GdmWelcome[cs]" are supported via GET_CONFIG. - Also starting with version 2.13.0.2 it is no longer necessary to - include the default value (i.e. you can use key - "greeter/IncludeAll" instead of having to use - "greeter/IncludeAll=false". -Supported since: 2.6.0.9 -Arguments: <key> -Answers: - OK <value> - ERROR <err number> <english error description> - 0 = Not implemented - 50 = Unsupported key - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="getconfigfile"> - <title>GET_CONFIG_FILE</title> -<screen> -GET_CONFIG_FILE: Get config file location being used by - the daemon. If the GDM daemon was started - with the --config option, it will return - the value passed in via the argument. -Supported since: 2.8.0.2 -Arguments: None -Answers: - OK <full path to GDM configuration file> - ERROR <err number> <english error description> - 0 = Not implemented - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="getcustomconfigfile"> - <title>GET_CUSTOM_CONFIG_FILE</title> -<screen> -GET_CUSTOM_CONFIG_FILE: Get custom config file location being - used by the daemon. -Supported since: 2.14.0.0 -Arguments: None -Answers: - OK <full path to GDM custom configuration file> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = File not found - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="getserverdetails"> - <title>GET_SERVER_DETAILS</title> -<screen> -GET_SERVER_DETAILS: Get detail information for a specific server. -Supported since: 2.13.0.4 -Arguments: <server> <key> - Key values include: - NAME - Returns the server name - COMMAND - Returns the server command - FLEXIBLE - Returns "true" if flexible, "false" - otherwise - CHOOSABLE - Returns "true" if choosable, "false" - otherwise - HANDLED - Returns "true" if handled, "false" - otherwise - CHOOSER - Returns "true" if chooser, "false" - otherwise - PRIORITY - Returns process priority -Answers: - OK <value> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = Server not found - 2 = Key not valid - 50 = Unsupported key - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="getserverlist"> - <title>GET_SERVER_LIST</title> -<screen> -GET_SERVER_LIST: Get a list of the server sections from - the configuration file. -Supported since: 2.13.0.4 -Arguments: None -Answers: - OK <value>;<value>;... - ERROR <err number> <english error description> - 0 = Not implemented - 1 = No servers found - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="greeterpids"> - <title>GREETERPIDS</title> -<screen> -GREETERPIDS: List all greeter pids so that one can send HUP - to them for config rereading. Of course one - must be root to do that. -Supported since: 2.3.90.2 -Arguments: None -Answers: - OK <pid>;<pid>;... - ERROR <err number> <english error description> - 0 = Not implemented - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="querylogoutaction"> - <title>QUERY_LOGOUT_ACTION</title> -<screen> -QUERY_LOGOUT_ACTION: Query which logout actions are possible - Only supported on connections that passed - AUTH_LOCAL. -Supported since: 2.5.90.0 -Answers: - OK <action>;<action>;... - Where action is one of HALT, REBOOT, SUSPEND or CUSTOM_CMD[0-9]. - An empty list can also be returned if no action is possible. - A '!' is appended to an action if it was already set with - SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION. Note that - SET_LOGOUT_ACTION has precedence over - SET_SAFE_LOGOUT_ACTION. - ERROR <err number> <english error description> - 0 = Not implemented - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="querycustomcmdlabels"> - <title>QUERY_CUSTOM_CMD_LABELS</title> -<screen> - QUERY_CUSTOM_CMD_LABELS: Query labels belonging to exported custom - commands Only supported on connections that - passed AUTH_LOCAL. - Supported since: 2.5.90.0 - Answers: - OK <label1>;<label2>;... - Where labelX is one of the labels belonging to CUSTOM_CMDX - (where X in [0,GDM_CUSTOM_COMMAND_MAX)). An empty list can - also be returned if none of the custom commands are exported - outside login manager (no CustomCommandIsPersistent options - are set to true). - ERROR <err number> <english error description> - 0 = Not implemented - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="querycustomcmdnorestartstatus"> - <title>QUERY_CUSTOM_CMD_NO_RESTART_STATUS</title> -<screen> -QUERY_CUSTOM_CMD_NO_RESTART_STATUS: Query NoRestart config options - for each of custom commands Only - supported on connections that - passed AUTH_LOCAL. -Supported since: 2.5.90.0 -Answers: - OK <status> - Where each bit of the status represents NoRestart value for - each of the custom commands. - bit on (1): NoRestart = true, - bit off (0): NoRestart = false. - ERROR <err number> <english error description> - 0 = Not implemented - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="queryvt"> - <title>QUERY_VT</title> -<screen> -QUERY_VT: Ask the daemon about which VT we are currently on. - This is useful for logins which don't own - /dev/console but are still console logins. Only - supported on Linux currently, other places will - just get ERROR 8. This is also the way to query - if VT support is available in the daemon in the - first place. Only supported on connections that - passed AUTH_LOCAL. -Supported since: 2.5.90.0 -Arguments: None -Answers: - OK <vt number> - ERROR <err number> <english error description> - 0 = Not implemented - 8 = Virtual terminals not supported - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="releasedynamic"> - <title>RELEASE_DYNAMIC_DISPLAYS</title> -<screen> -RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in - DISPLAY_CONFIG state -Supported since: 2.8.0.0 -Arguments: <display to release> -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = Bad display number - 100 = Not authenticated - 200 = Dynamic Displays not allowed - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="removedynamic"> - <title>REMOVE_DYNAMIC_DISPLAY</title> -<screen> -REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server - and purging the display configuration -Supported since: 2.8.0.0 -Arguments: <display to remove> -Answers: - OK <display> - ERROR <err number> <english error description> - 0 = Not implemented - 1 = Bad display number - 100 = Not authenticated - 200 = Dynamic Displays not allowed - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="serverbusy"> - <title>SERVER_BUSY</title> -<screen> -SERVER_BUSY: Returns true if half or more of the daemon's sockets - are busy, false otherwise. Used by slave programs - which want to ensure they do not overwhelm the - sever. -Supported since: 2.13.0.8 -Arguments: None -Answers: - OK <value> - ERROR <err number> <english error description> - 0 = Not implemented - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="setlogoutaction"> - <title>SET_LOGOUT_ACTION</title> -<screen> -SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after - slave process exits. Only supported on - connections that passed AUTH_LOCAL. -Supported since: 2.5.90.0 -Arguments: <action> - NONE Set exit action to 'none' - HALT Set exit action to 'halt' - REBOOT Set exit action to 'reboot' - SUSPEND Set exit action to 'suspend' - CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]' -Answers: - OK - ERROR <err number> <english error description> - 0 = Not implemented - 7 = Unknown logout action, or not available - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="setsafelogoutaction"> - <title>SET_SAFE_LOGOUT_ACTION</title> -<screen> -SET_SAFE_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend - after everybody logs out. If only one - person logs out, then this is obviously - the same as the SET_LOGOUT_ACTION. Note - that SET_LOGOUT_ACTION has precedence - over SET_SAFE_LOGOUT_ACTION if it is set - to something other then NONE. If no one - is logged in, then the action takes effect - effect immediately. Only supported on - connections that passed AUTH_LOCAL. -Supported since: 2.5.90.0 -Arguments: <action> - NONE Set exit action to 'none' - HALT Set exit action to 'halt' - REBOOT Set exit action to 'reboot' - SUSPEND Set exit action to 'suspend' - CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]' -Answers: - OK - ERROR <err number> <english error description> - 0 = Not implemented - 7 = Unknown logout action, or not available - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="setvt"> - <title>SET_VT</title> -<screen> -SET_VT: Change to the specified virtual terminal. - This is useful for logins which don't own /dev/console - but are still console logins. Only supported on Linux - currently, other places will just get ERROR 8. - Only supported on connections that passed AUTH_LOCAL. -Supported since: 2.5.90.0 -Arguments: <vt> -Answers: - OK - ERROR <err number> <english error description> - 0 = Not implemented - 8 = Virtual terminals not supported - 9 = Invalid virtual terminal number - 100 = Not authenticated - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="updateconfig"> - <title>UPDATE_CONFIG</title> -<screen> -UPDATE_CONFIG: Tell the daemon to re-read a key from the - GDM configuration file. Any user can request - that values are re-read but the daemon will - only do so if the file has been modified - since GDM first read the file. Only users - who can change the GDM configuration file - (normally writable only by the root user) can - actually modify the GDM configuration. This - command is useful to cause the GDM to update - itself to recognize a change made to the GDM - configuration file by the root user. - - Starting with version 2.13.0.0, all GDM keys are - supported except for the following: - - daemon/PidFile - daemon/ConsoleNotify - daemon/User - daemon/Group - daemon/LogDir - daemon/ServAuthDir - daemon/UserAuthDir - daemon/UserAuthFile - daemon/UserAuthFBDir - - GDM also supports the following Psuedokeys: - - xdmcp/PARAMETERS (2.3.90.2) updates the following: - xdmcp/MaxPending - xdmcp/MaxSessions - xdmcp/MaxWait - xdmcp/DisplaysPerHost - xdmcp/HonorIndirect - xdmcp/MaxPendingIndirect - xdmcp/MaxWaitIndirect - xdmcp/PingIntervalSeconds (only affects new connections) - - xservers/PARAMETERS (2.13.0.4) updates the following: - all [server-foo] sections. - - Supported keys for previous versions of GDM: - - security/AllowRoot (2.3.90.2) - security/AllowRemoteRoot (2.3.90.2) - security/AllowRemoteAutoLogin (2.3.90.2) - security/RetryDelay (2.3.90.2) - security/DisallowTCP (2.4.2.0) - daemon/Greeter (2.3.90.2) - daemon/RemoteGreeter (2.3.90.2) - xdmcp/Enable (2.3.90.2) - xdmcp/Port (2.3.90.2) - daemon/TimedLogin (2.3.90.3) - daemon/TimedLoginEnable (2.3.90.3) - daemon/TimedLoginDelay (2.3.90.3) - greeter/SystemMenu (2.3.90.3) - greeter/ConfigAvailable (2.3.90.3) - greeter/ChooserButton (2.4.2.0) - greeter/SoundOnLoginFile (2.5.90.0) - daemon/AddGtkModules (2.5.90.0) - daemon/GtkModulesList (2.5.90.0) -Supported since: 2.3.90.2 -Arguments: <key> - <key> is just the base part of the key such as - "security/AllowRemoteRoot" -Answers: - OK - ERROR <err number> <english error description> - 0 = Not implemented - 50 = Unsupported key - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - - <sect3 id="queryversion"> - <title>VERSION</title> -<screen> -VERSION: Query GDM version -Supported since: 2.2.4.0 -Arguments: None -Answers: - GDM <gdm version> - ERROR <err number> <english error description> - 200 = Too many messages - 999 = Unknown error -</screen> - </sect3> - </sect2> - </sect1> - - <!-- ============= GDM Commands ============================= --> - - <sect1 id="binaries"> - <title>GDM Commands</title> - - <sect2 id="bindir_binaries"> - <title>GDM User Commands</title> - - <para> - The GDM package provides the following different commands in - <filename>bindir</filename> intended to be used by the end-user: - </para> - - <sect3 id="gdmxnestchoosercommandline"> - <title><command>gdmXnestchooser</command> and - <command>gdmXnest</command> Command Line Options</title> - - <para> - The <command>gdmXnestchooser</command> 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 - <command>gdmXnestchooser somehost</command> will run the XDMCP - chooser from host <command>somehost</command> inside a nested - X server session. You can make this command do a direct query - instead by passing the <command>-d</command> option as well. In - addition to the following options, this command also supports - standard GNOME options. - </para> - - <variablelist> - <title><command>gdmXnestchooser</command> Command Line Options</title> - - <varlistentry> - <term>-x, --xnest=STRING</term> - <listitem> - <para> - Nested X server command line, default is defined by the - <filename>Xnest</filename> configuration option. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-o, --xnest-extra-options=OPTIONS</term> - <listitem> - <para> - Extra options for nested X server, default is no options. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-n, --no-query</term> - <listitem> - <para> - Just run nested X server, no query (no chooser) - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-d, --direct</term> - <listitem> - <para> - Do direct query instead of indirect (chooser) - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-B, --broadcast</term> - <listitem> - <para> - Run broadcast instead of indirect (chooser) - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-b, --background</term> - <listitem> - <para> - Run in background - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>--no-gdm-check</term> - <listitem> - <para> - Don't check for running GDM - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="gdmflexichoosercommandline"> - <title><command>gdmflexichooser</command> Command Line Options</title> - - <para> - The <command>gdmflexiserver</command> 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - The <command>gdmflexiserver --command</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. - </para> - - <para> - In addition to the following options, - <command>gdmflexiserver</command> also supports standard GNOME - options. - </para> - - <variablelist> - <title><command>gdmflexichooser</command> Command Line Options</title> - - <varlistentry> - <term>-c, --command=COMMAND</term> - <listitem> - <para> - Send the specified protocol command to GDM - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-n, --xnest</term> - <listitem> - <para> - Start a flexible X display in Nested mode - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-l, --no-lock</term> - <listitem> - <para> - Do not lock current screen - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-d, --debug</term> - <listitem> - <para> - Turns on debugging output which gets sent to syslog. Same as - turning on debug in the configuration file. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-a, --authenticate</term> - <listitem> - <para> - Authenticate before running --command - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-s, --startnew</term> - <listitem> - <para> - Starts a new flexible display without displaying a dialog - asking the user if they wish to continue any existing - sessions. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="gdmdynamiccommandline"> - <title><command>gdmdynamic</command> Command Line Options</title> - - <para> - <command>gdmdynamic</command> 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 <command>gdmdynamic</command> command can be used to create a new - display on a particular display number, run all newly created displays, - or remove a display. The <command>gdmdynamic</command> 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. - </para> - - <para> - 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. - </para> - - <variablelist> - <title><command>gdmdynamic</command> Command Line Options</title> - - <varlistentry> - <term>-a display=server</term> - <listitem> - <para> - Add a new display configuration, leaving it in the DISPLAY_CONFIG - state. For example, - <command>"-a 2=StandardServerTwo"</command> - <command>"-a 3=/usr/X11R6/bin/X -dev /dev/fb2"</command> - </para> - <para> - The display will not actually be started until the display is released - by calling <command>gdmdynamic</command> again with the -r option. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-r</term> - <listitem> - <para> - Release (run) all displays waiting in the DISPLAY_CONFIG state. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-d display</term> - <listitem> - <para> - Delete a display, killing the X server and purging the - display configuration. For example, "-d 3". - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-l [pattern]</term> - <listitem> - <para> - List displays via the ATTACHED_SERVERS - <command>gdmflexiserver</command> command. Without a pattern - lists all attached displays. With a pattern will match using - glob characters '*', '?', and '[]'. For example: - <command>"-l Standard*"</command> - <command>"-l *Xorg*"</command> - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-v</term> - <listitem> - <para> - Verbose mode. Prints diagnostic messages. - to GDM. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-b</term> - <listitem> - <para> - Background mode. Fork child to do the work and return immediately. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-t RETRY</term> - <listitem> - <para> - If the daemon socket is busy, <command>gdmdynamic</command> will - retry to open the connection the specified RETRY number of times. - Default value is 15. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>-s SLEEP</term> - <listitem> - <para> - If the daemon socket is busy, <command>gdmdynamic</command> 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. - </para> - </listitem> - </varlistentry> - - </variablelist> - </sect3> - - <sect3 id="gdmphotosetupcommandline"> - <title><command>gdmphotosetup</command> Command Line Options</title> - - <para> - 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 <filename>~/.face</filename>. This command accepts - standard GNOME options. - </para> - </sect3> - - <sect3 id="gdmthemetestercommandline"> - <title><command>gdmthemetester</command> Command Line Options</title> - - <para> - <command>gdmthemetester</command> 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. <command>gdmthemetester</command> requires - that the system support <command>gdmXnest</command>. - - Note that themes can display differently depending on the theme's - "Show mode". <command>gdmthemetester</command> allows - viewing the themes in different modes via the environment option. - Valid environment values and their meanings follow: - -<screen> -console - In console mode. -console-timed - In console non-flexi mode. -flexi - In flexi mode. -xdmcp - In remote (XDMCP) mode. -remote-flexi - In remote (XDMCP) & flexi mode. -</screen> - </para> - </sect3> - </sect2> - - <sect2 id="sbindir_binaries"> - <title>GDM Root User Commands</title> - - <para> - The GDM package provides the following different commands in - <filename>sbindir</filename> intended to be used by the root user: - </para> - - <sect3 id="gdmcommandline"> - <title><command>gdm</command> and <command>gdm-binary</command> - Command Line Options</title> - - <para> - The <command>gdm</command> command is really just a script which - runs the <command>gdm-binary</command>, passing along any options. - Before launching <command>gdm-binary</command>, the gdm wrapper script - will source the <filename><etc>/profile</filename> file to set - the standard system environment variables. In order to better support - internationalization, it will also set the LC_MESSAGES environment - variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you - really need to set some additional environment before launching GDM, - you can do so in this script. - </para> - - <variablelist> - <title><command>gdm</command> and <command>gdm-binary</command> - Command Line Options</title> - - <varlistentry> - <term>--help</term> - <listitem> - <para> - Gives a brief overview of the command line options. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>--nodaemon</term> - <listitem> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>--no-console</term> - <listitem> - <para> - Tell the daemon that it should not run anything on the console. - This means that none of the attached servers from the - <filename>[servers]</filename> section will be started, and the - console will not be used for communicating errors to the user. - An empty <filename>[servers]</filename> section automatically - implies this option. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>--config=CONFIGFILE</term> - <listitem> - <para> - Specify an alternative configuration file. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>--preserve-ld-vars</term> - <listitem> - <para> - When clearing the environment internally, preserve all variables - starting with LD_. This is mostly for debugging purposes. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>--version</term> - <listitem> - <para> - Print the version of the GDM daemon. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>--wait-for-go</term> - <listitem> - <para> - If started with this option, gdm will init, but only start the - first attached 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. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="gdmsetupcommandline"> - <title><command>gdmsetup</command> Command Line Options</title> - - <para> - <command>gdmsetup</command> 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 - <command>gdmsetup</command> 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. - </para> - </sect3> - - <sect3 id="gdmrestartcommandline"> - <title><command>gdm-restart</command> Command Line Options</title> - - <para> - <command>gdm-restart</command> stops and restarts GDM by sending - the GDM daemon a HUP signal. This command will immediately terminate - all sessions and log out users currently logged in with GDM. - </para> - </sect3> - - <sect3 id="gdmsaferestartcommandline"> - <title><command>gdm-safe-restart</command> Command Line Options</title> - - <para> - <command>gdm-safe-restart</command> stops and restarts GDM by - sending the GDM daemon a USR1 signal. GDM will be restarted as soon - as all users log out. - </para> - </sect3> - - <sect3 id="gdmstopcommandline"> - <title><command>gdm-stop</command> Command Line Options</title> - - <para> - <command>gdm-stop</command> stops GDM by sending the GDM daemon - a TERM signal. - </para> - </sect3> - </sect2> - - <sect2 id="libexecdir_binaries"> - <title>GDM Internal Commands</title> - - <para> - The GDM package provides the following different commands in - <filename>libexecdir</filename> intended to be used by the gdm - daemon process. - </para> - - <sect3 id="gdmgreeterlogincommandline"> - <title><command>gdmchooser</command> and <command>gdmlogin</command> - Command Line Options</title> - - <para> - The <command>gdmgreeter</command> and <command>gdmlogin</command> - are two different login applications, either can be used by GDM. - <command>gdmgreeter</command> is themeable with GDM themes while - <command>gdmlogin</command> is themable with GTK+ themes. These - applications are normally executed by the GDM daemon. Both commands - support standard GNOME options. - </para> - </sect3> - - <sect3 id="gdmchoosercommandline"> - <title><command>gdmchooser</command> Command Line Options</title> - - <para> - The <command>gdmchooser</command> is the XDMCP chooser application. - The <command>gdmchooser</command> is normally executed by the GDM - daemon. It supports the following options for XDM compatibility. - This command supports standard GNOME options. - </para> - - <variablelist> - <title><command>gdmchooser</command> Command Line Options</title> - - <varlistentry> - <term>--xdmaddress=SOCKET</term> - <listitem> - <para> - Socket for XDM communication. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>--clientaddress=ADDRESS</term> - <listitem> - <para> - Client address to return in response to XDM. This option is for - running gdmchooser with XDM, and is not used within GDM. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>--connectionType=TYPE</term> - <listitem> - <para> - Connection type to return in response to XDM. This option is for - running gdmchooser with XDM, and is not used within GDM. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect3> - - <sect3 id="gdm-ssh-session"> - <title><command>gdm-ssh-session</command></title> - - <para> - The <command>gdm-ssh-session</command> is normally executed by the - GDM daemon when starting a secure remote connection through ssh. - It does not take any options. - </para> - </sect3> - </sect2> - </sect1> - - <!-- ============= Theme manual ============================= --> - - <sect1 id="thememanual"> - <title>Themed Greeter</title> - - <para> - This section describes the creation of themes for the Themed - Greeter. For examples including screenshots, see the standard installed - themes and the themes from - <ulink type="http" url="http://art.gnome.org/themes/gdm_greeter/"> - the theme website</ulink>. - </para> - - <sect2 id="themeover"> - <title>Theme Overview</title> - - <para> - 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 - <filename><share>/gdm/themes/<theme_name></filename>. - Usually this would be under <filename>/usr/share</filename>. The theme - directory should contain a file called - <filename>GdmGreeterTheme.desktop</filename> which has similar format - to other .desktop files and looks like: - </para> - -<screen> -[GdmGreeterTheme] -Encoding=UTF-8 -Greeter=circles.xml -Name=Circles -Description=Theme with blue circles -Author=Bond, James Bond -Copyright=(c) 2002 Bond, James Bond -Screenshot=screenshot.png -</screen> - - <para> - The Name, Description, Author and Copyright fields can be translated - just like the other <filename>.desktop</filename>files. 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. - </para> - - <para> - Once a theme is installed, it can be tested with the - <command>gdmthemetester</command> program. This program assumes that - the X server supports a nested server command. This command takes two - arguments, first the environment that should be used. The environment - can be one of the following values: console, console-timed, flexi, - remote-flexi, or xdmcp. The "console" option tests the - theme as it would be shown on an attached display. The - "console-timed" option tests the theme as it would be shown - on an attached display with timed login enabled. The "flexi" - option tests the theme as it would be shown on an attached flexible - display (such as started via Xnest). Finally, the "xdmcp" - option tests the theme as it would be shown for remote XDMCP - displays. The second argument is the theme name. For example, to - test how the circles theme would look in XDMP remote display mode, - you would run the following command: - </para> - -<screen> -<command>gdmthemetester xdmcp circles</command> -</screen> - - <para> - When developing a theme, make sure to test all the environments, and - make sure to test how the caps lock warning looks by pressing the caps - lock key. Running <command>gdmthemetester</command> is also a good way - to take screenshots of GDM themes. Simply take a screenshot of the - theme running in the nested display window. This can be done in GNOME - by focusing the nested login window and pressing Alt-PrintScreen. - </para> - - <para> - Once a theme has been fully tested, then make a tarball that contains - the directory as it would be insatlled to the - <filename><share>/gdm/themes</filename> directory. This is - the standard format for distributing GDM themes. - </para> - </sect2> - - <sect2 id="descofthemeformat"> - <title>Detailed Description of Theme XML format</title> - - <sect3 id="greetertag"> - <title>greeter tag</title> - - <para> - 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. - </para> - -<screen> -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE greeter SYSTEM "greeter.dtd"> -<greeter gtk-theme="Crux"> -[...] -</greeter> -</screen> - - <para> - 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). - </para> - </sect3> - - <sect3 id="boxnodes"> - <title>Box Nodes</title> - - <para> - Box nodes are container nodes for item nodes. Box nodes are - specified as follows: -<screen> -<box orientation="alignment" min-width="num" -xpadding="num" ypadding="num" spacing="num" -homogeneous="bool"> -</screen> - 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. - </para> - - <para> - If the box is homogeneous then the children are allocated equal - amount of space. - </para> - - <para> - The "min-width" must be specified in pixels. Obviously - there is also a corresponding "min-height" property as - well. - </para> - </sect3> - - <sect3 id="fixednodes"> - <title>Fixed Nodes</title> - - <para> - 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: -<screen> -<fixed> -</screen> - Then you put other items with proper position nodes inside this. - </para> - - <para> - The "toplevel" node is really just like a fixed node. - </para> - </sect3> - - <sect3 id="itemnodes"> - <title>Item Nodes</title> - - <para> - A GDM Theme is created by specifying a hierarchy of item and box - nodes. Item nodes can have the following value for - "type": - </para> - - <variablelist> - <varlistentry> - <term>button</term> - <listitem> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>entry</term> - <listitem> - <para> - Text entry field. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>label</term> - <listitem> - <para> - A text label. Must have a "text" node to specify the - text. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>list</term> - <listitem> - <para> - A face browser widget. Only useful if the face browser is - enabled via the configuration. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>pixmap</term> - <listitem> - <para> - An pixmap image in a format that gdk-pixbuf supports like - PNG, JPEG, Tiff, etc...) - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>rect</term> - <listitem> - <para> - Rectangle. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>svg</term> - <listitem> - <para> - Scaled Vector Graphic image. - </para> - </listitem> - </varlistentry> - </variablelist> - - <para> - For example: -<screen> -<item type="label"> -</screen> - 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) - </para> - - <para> - Entry items can have id values as follows: - </para> - - <variablelist> - <varlistentry> - <term>user-pw-entry</term> - <listitem> - <para> - Entry field for userid and password entry. This is the field - used for responses for the PAM/GDM questions (Username, - Password, etc..). - </para> - </listitem> - </varlistentry> - </variablelist> - - <para> - 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. - </para> - - <variablelist> - <varlistentry> - <term>session</term> - <listitem> - <para> - A list of available sessions, which allows the user to pick - the session to use. Supported since GDM 2.16.2. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist> - <varlistentry> - <term>language</term> - <listitem> - <para> - A list of available languages, which allows the user to pick - the language to use. Supported since GDM 2.16.2. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist> - <varlistentry> - <term>userlist</term> - <listitem> - <para> - 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. - </para> - </listitem> - </varlistentry> - </variablelist> - - <variablelist> - <varlistentry> - <term>userlist-rect</term> - <listitem> - <para> - 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. - </para> - </listitem> - </varlistentry> - </variablelist> - - <para> - 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' - </para> - - <para> - Label items can have id values as follows: - </para> - - <variablelist> - <varlistentry> - <term>clock</term> - <listitem> - <para> - Label that displays the date and time. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>pam-prompt</term> - <listitem> - <para> - Label that displays the PAM prompt. This is the prompt that PAM - uses to ask for username, password, etc... - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>pam-error</term> - <listitem> - <para> - Label that displayst PAM/GDM error messages. Such as when user - can't log in. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>pam-error-logo</term> - <listitem> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>pam-message</term> - <listitem> - <para> - 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. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>timed-label</term> - <listitem> - <para> - Label that displays timed login information. - </para> - </listitem> - </varlistentry> - </variablelist> - - <para> - Rectangles can have id values as follows: - </para> - - <variablelist> - <varlistentry> - <term>caps-lock-warning</term> - <listitem> - <para> - Displays an icon that shows if the - CAPS LOCK key is depressed. This rectangle - will be hidden/shown appropriately - </para> - </listitem> - </varlistentry> - </variablelist> - - <para> - If an item is of type rect, the item can be a button. Buttons - must also include a "button" value as follows: -<screen> -<item type="rect" id="disconnect_button" button="true">. -</screen> - </para> - - <para> - Possible values for button ids are as follows. - </para> - - <variablelist> - <varlistentry> - <term>chooser_button</term> - <listitem> - <para> - Runs the XDMCP chooser. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>config_button</term> - <listitem> - <para> - Runs the GDM configuration application. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>custom_cmd_button[0-9]</term> - <listitem> - <para> - Runs the <filename>n-th</filename> custom command. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>disconnect_button</term> - <listitem> - <para> - Disconnect from remote session. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>language_button</term> - <listitem> - <para> - Displays the language selection dialog. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>halt_button</term> - <listitem> - <para> - Halt (shuts down) the system. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>reboot_button</term> - <listitem> - <para> - Restart the system. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>session_button</term> - <listitem> - <para> - List and select from available sessions. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>suspend_button</term> - <listitem> - <para> - Suspend the system. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>system_button</term> - <listitem> - <para> - 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. - </para> - </listitem> - </varlistentry> - </variablelist> - - <para> - 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. - </para> - - <para> - 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: - </para> - -<screen> -<item type="rect" background="true"> - <normal file="background.svg"/> - <pos x="0" y="0" width="100%" height="-75"/> -</item> -</screen> - - <para> - If no item node has "background" property set, then the - background is not modified when greeter exits. - </para> - - <para> - 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 : - </para> -<screen> -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE greeter SYSTEM "greeter.dtd"> - <greeter> - - <item type="rect" background="true"> - <normal file="background_for_login.svg"/> - <pos x="0" y="0" width="100%" height="100%"/> - </item> - <item type="rect"> - <normal file="background_for_greeter.svg"/> - <pos x="0" y="0" width="100%" height="100%"/> - </item> -[...] -</greeter> -</screen> - </sect3> - - <sect3 id="positionnodes"> - <title>Position Node</title> - - <para> - Each item can specify its position and size via the "pos" - node. For example: -<screen> -<pos x="0" y="4" width="100%" height="100%"/> -</screen> - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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: -<screen> -<pos x="10%" y="50%" anchor="w" width="80%" height="95"/> -</screen> - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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). - </para> - - <para> - 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: -<screen> -<item type="label"> -<pos x="10%" max-screen-percent-width="50%"/> -</screen> - </para> - </sect3> - - <sect3 id="shownodes"> - <title>Show Node</title> - - <para> - 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: - </para> - - <para> - <filename>console</filename> - In console mode. - </para> - <para> - <filename>console-fixed</filename> - In console non-flexi mode. - </para> - <para> - <filename>console-flexi</filename> - In console & flexi mode. - </para> - <para> - <filename>flexi</filename> - In flexi mode. - </para> - <para> - <filename>remote</filename> - In remote mode. - </para> - <para> - <filename>remote-flexi</filename> - In remote & flexi mode. - </para> - - <para> - For example: -<screen> -<show modes="flexi,remote"/> -</screen> - </para> - - <para> - 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: - </para> - - <para> - <filename>chooser</filename>, if ChooserButton is set to - "true" in the GDM configuration. - </para> - <para> - <filename>config</filename>, if ConfigAvailable is set to - "true" in the GDM configuration. - </para> - <para> - <filename>custom_cmd[0-9]</filename>, if <filename>n-th</filename> - CustomCommand is specified in the GDM configuration. - </para> - <para> - <filename>halt</filename>, if HaltDaemon is specified in - the GDM configuration. - </para> - <para> - <filename>reboot</filename>, if RebootCommand is specified in - the GDM configuration. - </para> - <para> - <filename>suspend</filename>, if SuspendCommand is specified in - the GDM configuration. - </para> - <para> - <filename>system</filename>, if SystemMenu is specified in - the GDM configuration. - </para> - <para> - <filename>timed</filename>, if TimedLoginEnabled is set to - "true" in the GDM configuration. - </para> - - <para> - For example: -<screen> -<show modes="console" type="system"/> -</screen> - </para> - - <para> - 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. - </para> - - <para> - For example: -<screen> -<show min-screen-height="768"/> -</screen> - </para> - - <para> - 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. - </para> - </sect3> - - <sect3 id="noractprenodes"> - <title>Normal/Active/Prelight Nodes</title> - - <para> - 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: - </para> - - <para> - <filename>normal</filename> - normal state. - </para> - <para> - <filename>active</filename> - when the item has active focus. - </para> - <para> - <filename>prelight</filename> - when the mouse is hovering over the - item. - </para> - - <para> - When item is "rect" (alpha can be omitted and defaults to - 0.0): -<screen> -<normal color="#ffffff" alpha="0.0"> -</screen> - </para> - - <para> - When item is "label" -<screen> -<normal color="#ffffff" font="Sans 14"/> -</screen> - </para> - - <para> - When the item type is "pixmap" or "SVG", then the - normal, active, and prelight tags specify the images to use as - follows: -<screen> -<normal file="picture.png" tint="#dddddd"/> -</screen> - </para> - - <para> - Note that relative pathnames are assumed to be in the same - directory as the theme <filename>.xml</filename> file in - <filename><share>/gdm/themes/<theme_name></filename>. - </para> - - <para> - Note that alternative image file can be specified using the altfile[n] - property. GDM will use the last valid image filename specified. - For example: -<screen> -<normal file="picture.png" altfile1="distribution-blah-image.png" altfile2="distribution-foo-image.png"/> -</screen> - If <filename>distribution-foo-image.png</filename> 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. - </para> - - </sect3> - - <sect3 id="listcoloronodes"> - <title>Face Browser Icon/Label Color Nodes</title> - - <para> - 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: - </para> - - <para> -<screen> -<color iconcolor="#dddddd" labelcolor="#ffffff"/> -</screen> - </para> - </sect3> - - <sect3 id="textnodes"> - <title>Text Node</title> - - <para> - 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): -<screen> -<text xml:lang="fr">Option</text> -</screen> - </para> - - <para> - 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: -<screen> -<text>"foo<sup>bar</sup>"</text> -</screen> - </para> - - <para> - Text nodes can contain the following special character sequences - which will be translated as follows: - </para> - - <para> - %% - A literal % character - </para> - <para> - %c - Clock time. Only labels with the "clock" id will - update automatically every second. Other labels will contain a - static timestamp. - </para> - <para> - %d - Display name (DISPLAY environment variable) - </para> - <para> - %h - Hostname (gethostname output) - </para> - <para> - %m - Machine name (uname.machine output) - </para> - <para> - %n - Node name (uname.nodename output) - </para> - <para> - %o - Domain name (getdomainname output) - </para> - <para> - %r - Release name (uname.release output) - </para> - <para> - %s - System name (uname.sysname output) - </para> - <para> - %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. - </para> - <para> - %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. - </para> - <para> - \n - Carriage return - </para> - <para> - _ - An underscore causes the following character to be underlined. - If it precedes a % character sequence, the string that replaces the - character sequence is underlined. - </para> - </sect3> - - <sect3 id="stocklabels"> - <title>Stock node</title> - - <para> - 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: - </para> - - <para> - <filename>cancel</filename>, _("_Cancel" - </para> - <para> - <filename>caps-lock-warning</filename>, - _("Caps Lock is on." - </para> - <para> - <filename>chooser</filename>, _("Remote Login via _XDMCP" - </para> - <para> - <filename>config</filename>, _("_Configure" - </para> - <para> - <filename>custom_cmd[0-9]</filename>, getting label from config file - </para> - <para> - <filename>disconnect</filename>, _("D_isconnect" - </para> - <para> - <filename>halt</filename>, _("Shut _Down" - </para> - <para> - <filename>language</filename>, _("_Language" - </para> - <para> - <filename>ok</filename>, _("_OK" - </para> - <para> - <filename>options</filename>, _("_Options" - </para> - <para> - <filename>quit</filename>, _("_Quit" - </para> - <para> - <filename>reboot</filename>, _("_Restart" - </para> - <para> - <filename>session</filename>, _("_Session" - </para> - <para> - <filename>startagain</filename>, _("_Start Again" - </para> - <para> - <filename>suspend</filename>, _("Sus_pend" - </para> - <para> - <filename>system</filename>, _("_Actions" - (Formerly "S_ystem" - </para> - <para> - <filename>timed-label</filename>, - _("User %u will login in %t" - </para> - <para> - <filename>username-label</filename>, _("Username:" - </para> - <para> - <filename>welcome-label</filename>, _("Welcome to %n" - </para> - - <para> - For example: -<screen> -<stock type="welcome-label"> -</screen> - </para> - </sect3> - - <sect3 id="customwidgetry"> - <title>Custom Widgetry</title> - - <para> - 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 - <filename><ServAuthDir>/<display>.GreeterInfo</filename> - as <filename><list id>=<listitem id></filename>. - </para> - - <para> - For example suppose we are on display :0, - <filename>ServAuthDir</filename> is - <filename><var>/lib/gdm</filename> and we have the following in the - theme: - </para> - -<screen> -<item type="list" id="custom-config"> -<pos anchor="nw" x="1" y="1" height="200" width="100"> -<listitem id="foo"> -<text>Foo</text> -</listitem> -<listitem id="bar"> -<text>Bar</text> -</listitem> -</item> -</screen> - - <para> - Then if the user chooses 'Foo' then - <filename><var>/lib/gdm/:0.GreeterInfo</filename> will contain: -<screen> -custom-config=foo -</screen> - </para> - </sect3> - </sect2> - </sect1> - - <sect1 id="accessibility"> - <title>Accessibility</title> - <para> - GDM supports "Accessible Login", allowing users to log into - their desktop session even if they cannot easily use the screen, mouse, - or keyboard in the usual way. Accessible Technology (AT) programs - such as <command>GOK</command> (on-screen keyboard) and - <command>orca</command> (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 <command>GOK</command>, do not yet work - with the "Themed Greeter". - </para> - - <para> - 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 <filename>Greeter</filename> - and <filename>RemoteGreeter</filename> configuration options by hand - to be <command>/usr/lib/gdmlogin</command>. - </para> - - <para> - 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. - </para> - - <para> - Note that <command>gdmsetup</command> does not yet work with - accessibility, so that users who require AT programs should only - configure GDM by editing the ASCII files directly. - </para> - - <sect2 id="accessibilityconfig"> - <title>Accessibility Configuration</title> - - <para> - 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 <command>GOK</command> and <command>orca</command>, 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. - </para> - - <sect3 id="accessibilitytheming"> - <title>Accessibile Theming</title> - - <para> - If using the "GTK+ Greeter" users can easily - switch the color and contrast scheme of the dialog. To do this, - ensure the <filename>AllowGtkThemeChange</filename> 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 <filename>GtkThemesToAllow</filename> - configuration choice can also be used to limit the choices - available as desired. For example: - </para> - -<screen> -GtkThemesToAllow=HighContrast,HighContrastInverse -</screen> - - <para> - 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. - </para> - </sect3> - - <sect3 id="accessibilityatprograms"> - <title>AT Program Support</title> - - <para> - To enable user to launch AT such as the <command>GOK</command> - or <command>orca</command>, the - <filename>AddGtkModules</filename> parameter in the GDM - configuration must be set to "true". - Also the <filename>GtkModulesList</filename> parameter must be - uncommented and set as follows: - </para> - -<screen> -GtkModulesList=gail:atk-bridge:/usr/lib/gtk-2.0/modules/libdwellmouselistener:/usr/lib/gtk-2.0/modules/libkeymouselistener -</screen> - - <para> - 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, <command>at-spi-registryd</command>, to be running. - This is handled by the GDM GUI starting with version 2.17. - </para> - - <para> - 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. - </para> - - <para> - Once "keymouselistener" and/or - "dwellmouselistener" have been added to the - <filename>AddGtkModules</filename> loaded by GDM, then you may - need to modiify the gesture configurations to meet your user's - needs. Default gestures are provided for launching - <command>GOK</command> and <command>orca</command>, but it is - recommended to modify these gestures so they work best for your - user base. These gesture associations are contained in files - <filename>AccessKeyMouseEvents</filename> and - <filename>AccessDwellMouseEvents</filename>, respectively. Both - files are located in the - <filename><etc>/gdm/modules</filename> directory. The - gesture configuration format is described in the comment section - of the two configuration files. - </para> - - <para> - 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 - <filename>server-foo</filename> sections. - </para> - - <para> - 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. - </para> - - <para> - On some operating systems, it is necessary to make sure that the - GDM user is a member of the "audio" group for AT - programs that require audio output (such as text-to-speech) to - be functional. - </para> - - <para> - 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. - </para> - </sect3> - - <sect3 id="accessibilitytroubleshooting"> - <title>AT Troubleshooting</title> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - Some versions of <command>GOK</command> and - <command>orca</command> 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. - </para> - - <para> - 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. - </para> - - <para> - Also note that some input devices require X server configuration - before GDM will recognize them. - </para> - </sect3> - - <sect3 id="accessibilitysound"> - <title>Accessibility Login Sound Configuration</title> - - <para> - 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 - <filename><bin>/play</filename> (or - <filename><bin>/audioplay</filename> on Solaris. This can - be changed via the <filename>SoundProgram</filename> GDM - configuration option. Typically most text-to-speech programs - (such as <command>orca</command>) use a separate mechanism to - play audio, so this configuration setting is not needed for - them to work. - </para> - </sect3> - </sect2> - </sect1> - - <sect1 id="solaris"> - <title>Solaris Specific Features</title> - - <sect2 id="solarisusing"> - <title>Using GDM on Solaris</title> - - <para> - 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. - </para> - -<screen> -svcs cde-login -</screen> - - <para> - If the <command>svcs</command> command responds that this - service is enabled, then run this command to disable CDE login: - </para> - -<screen> -svcadm disable cde-login -</screen> - - <para> - If the <command>svcs</command> command responds that this pattern - doesn't match any instances, then run these commands to stop - CDE login: - </para> - -<screen> -/usr/dt/config/dtconfig -d -Either reboot, or kill any running dtlogin processes. -</screen> - - <para> - 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". - </para> - -<screen> -svcadm enable servicename -</screen> - </sect2> - - <sect2 id="solarisconfiguration"> - <title>Solaris Configuration</title> - <para> - On Solaris, the following configuration is recommended. - This turns on IPv6 and also turns on PreFetch for - performance benefit. - -<screen> -./autogen.sh --prefix=/usr --sysconfdir=/etc/X11 --localstatedir=/var - --libexecdir=/usr/lib --enable-ipv6=yes --with-at-bindir=/usr/sfw/bin - --with-prefetch --with-post-path=/usr/openwin/bin --with-pam-prefix=/etc - --with-lang-file=/etc/default/init -</screen> - </para> - - <para> - Configuring GDM with the - "--with-post-path=/usr/openwin/bin" on Solaris is - recommended for accessing X server programs. - </para> - </sect2> - - <sect2 id="solarislogindevperm"> - <title>Solaris /etc/logindevperm</title> - <para> - GDM supports /etc/logindevperm, but only on Solaris 10 and - higher. Refer to the logindevperm.4 man page for more - information. - </para> - - <para> - 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: - </para> - -<screen> -/dev/console 0600 /dev/sound/* # audio devices -</screen> - - <para> - 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. - </para> - </sect2> - - <sect2 id="solarisautomaticlogin"> - <title>Solaris Automatic Login</title> - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - -<screen> - gdm-autologin auth required pam_unix_cred.so.1 - gdm-autologin auth sufficient pam_allow.so.1 - gdm-autologin account sufficient pam_allow.so.1 - gdm-autologin session sufficient pam_allow.so.1 - gdm-autologin password sufficient pam_allow.so.1 -</screen> - - <para> - The above setup will cause no lastlog entry to be generated. If - a lastlog entry is desired, then use the following for session: - </para> - -<screen> - gdm-autologin session required pam_unix_session.so.1 -</screen> - </sect2> - - <sect2 id="solarisrbac"> - <title>Solaris RBAC support for Shutdown, Reboot, and Suspend</title> - - <para> - 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 <command>gdmflexiserver</command> - QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and - SET_SAFE_LOGOUT_ACTION commands. - </para> - - <para> - On Solaris GDM has the following value specified for the - <filename>RBACSystemCommandKeys</filename> configuration - option. - </para> - -<screen> -HALT:solaris.system.shutdown;REBOOT:solaris.system.shutdown -</screen> - - <para> - 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 - <filename>User</filename> configuration option, "gdm" by - default) has such RBAC permissions. - </para> - - <para> - Therefore, add the "solaris.system.shutdown" - authorization name to the <filename>/etc/user_attr</filename> - 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 <filename>RBACSystemCommandKeys</filename> GDM - configuration key, and this will make the system commands - available for all users. Refer to the - <filename>user_attr</filename> man page for more information - about setting RBAC privileges. - </para> - - <para> - Note that on Solaris there are two programs that can be used - to shutdown the system. These are GDM and - <command>gnome-sys-suspend</command>. - <command>gnome-sys-suspend</command> is a GUI front-end for - the <command>sys-suspend</command>. - </para> - - <para> - 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 - <command>gnome-sys-suspend</command> 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 - <command>gnome-sys-suspend</command> command is less functional - since it does not support a reboot option, only shutdown and - suspend. - </para> - - <para> - If GDM is not being used to manage shutdown, reboot, and - suspend; then the GNOME panel uses - <command>gnome-sys-suspend</command> 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 <command>gnome-sys-suspend</command>. If - you are using this, then refer to the - <command>sys-suspend</command> man page for information - about how to configure it. Or consider using GDM and - configuring it to provide these options. - </para> - </sect2> - - <sect2 id="solarisother"> - <title>Other Solaris Features</title> - <para> - GDM supports a few features specific to Solaris, as follows: - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - Solaris supports the <filename>/etc/default/login</filename> - interface, which affects the <filename>DefaultPath</filename>, - <filename>RootPath</filename>, - <filename>PasswordRequired</filename>, and - <filename>AllowRemoteRoot</filename> options as described in the - "Configuration" section. - </para> - </sect2> - </sect1> - - <sect1 id="exampleconf"> - <title>Example Configurations</title> - - <sect2 id="customcommand"> - <title>Defining Custom Commands</title> - - <para> - 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 - <filename>[customcommand]</filename> section of the GDM configuration - file. - - <screen> - [customcommand] - CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze - CustomCommandLabel0=_Windoze - CustomCommandLRLabel0=Reboot into _Windoze - CustomCommandText0=Are you sure you want to restart the computer into Windoze? - CustomCommandTooltip0=Restarts the computer into Windoze - CustomCommandIsPersistent0=true - </screen> - - CustomCommand0 specifies two commands separated by a semicolon: - <filename>/sbin/rebootwindoze</filename> and - <filename>/usr/local/sbin/rebootwindoze</filename>. GDM will use - the first valid command in the list. This allows different - commands for different operating systems to be included. - </para> - <para> - 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 - <filename>[customcommand]</filename> section of your GDM configuration - file. - - <screen> - [customcommand] - CustomCommand0=/sbin/updatesystem;/usr/local/sbin/updatesystem - CustomCommandLabel0=_Update Me - CustomCommandLRLabel0=Update the system - CustomCommandText0=Are you sure you want to update the system software? - CustomCommandTooltip0=Updates the system - CustomCommandNoRestart0=true - </screen> - </para> - - <para> - Both custom commands could be defined as follows. - - <screen> - [customcommand] - CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze - CustomCommandLabel0=_Windoze - CustomCommandLRLabel0=Reboot into _Windoze - CustomCommandText0=Are you sure you want to restart the computer into Windoze? - CustomCommandTooltip0=Restarts the computer into Windoze - CustomCommandIsPersistent0=true - - CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem - CustomCommandLabel1=_Update Me - CustomCommandLRLabel1=Update the system - CustomCommandText1=Are you sure you want to update the system software? - CustomCommandTooltip1=Updates the system - CustomCommandNoRestart1=true - </screen> - </para> - - <para> - There can be up to 10 custom commands numbered 0-9. - - <screen> - [customcommand] - CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze - CustomCommandLabel0=_Windoze - CustomCommandLRLabel0=Reboot into _Windoze - CustomCommandText0=Are you sure you want to restart the computer into Windoze? - CustomCommandTooltip0=Restarts the computer into Windoze - CustomCommandIsPersistent0=true - - CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem - CustomCommandLabel1=_Update Me - CustomCommandLRLabel1=Update the system - CustomCommandText1=Are you sure you want to update the system software? - CustomCommandTooltip1=Updates the system - CustomCommandNoRestart1=true - - CustomCommand3=/sbin/do_something - . - . - . - - CustomCommand4=/sbin/do_something_else - . - . - . - </screen> - </para> - </sect2> - </sect1> - - <sect1 id="troubleshooting"> - <title>Troubleshooting</title> - - <para> - 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 - <ulink type="http" - url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink> - or send an email to the - <address><email>gdm-list@gnome.org</email></address> mail list. - </para> - - <para> - If GDM is failing to work properly, it is always a good idea to include - debug information. Use the <command>gdmsetup</command> 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 - (<filename><var>/log/messages</filename> or - <filename><var>/adm/messages</filename> 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). - </para> - - <para> - You should not leave debug on after collecting data. It will clutter your - syslog and slow system performance. - </para> - - <sect2 id="wontstart"> - <title>GDM Will Not Start</title> - - <para> - There are a many problems that can cause GDM to fail to start, but - this section will discuss a few common problems and how to approach - tracking down a problem with GDM starting. Some problems will - cause GDM to respond with an error message or dialog when it tries - to start, but it can be difficult to track down problems when GDM - fails silently. - </para> - - <para> - First make sure that the 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. - </para> - - <para> - 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 - <command><lib>/gdmlogin</command> - or <command><lib>/gdmgreeter</command>. 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. - </para> - - <para> - Also make sure that the <filename>/tmp</filename> directory has - reasonable ownership and permissions, and that the machine's file - system is not full. These problems will cause GDM to fail to start. - </para> - </sect2> - - <sect2 id="notaccessfile"> - <title>GDM Will Not Access User Settings</title> - - <para> - GDM saves user settings, such as your default session and default - language, in the <filename>~/.dmrc</filename>. Other files, such - as the user's <filename>~/.Xauthority</filename> 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 - <filename>RelaxPermissions</filename> 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". - </para> - </sect2> - </sect1> - - <!-- ============= Application License ============================= --> - - <sect1 id="license"> - <title>License</title> - <para> - This program is free software; you can redistribute it and/or - modify it under the terms of the <ulink type="help" url="gnome-help:gpl"> - <citetitle>GNU General Public License</citetitle></ulink> as - published by the Free Software Foundation; - either version 2 of the License, or (at your option) any later - version. - </para> - <para> - This program is distributed in the hope that it will be useful, but - WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - <citetitle>GNU General Public License</citetitle> for more details. - </para> - <para> - A copy of the <citetitle>GNU General Public License</citetitle> is - included as an appendix to the <citetitle>GNOME Users - Guide</citetitle>. You may also obtain a copy of the - <citetitle>GNU General Public License</citetitle> from the Free - Software Foundation by visiting <ulink type="http" - url="http://www.fsf.org">their Web site</ulink> or by writing to - <address> - Free Software Foundation, Inc. - <street>51 Franklin Street, Fifth Floor</street> - <city>Boston</city>, <state>MA</state> <postcode>02110-1301</postcode> - <country>USA</country> - </address> - </para> - </sect1> -</article> - -<!-- Keep this comment at the end of the file -Local variables: -mode: sgml -sgml-omittag:t -sgml-shorttag:t -sgml-minimize-attributes:nil -sgml-always-quote-attributes:t -sgml-indent-step:2 -sgml-indent-data:t -sgml-parent-document:nil -sgml-exposed-tags:nil -sgml-local-catalogs:nil -sgml-local-ecat-files:nil -End: ---> diff --git a/docs/C/legal.xml b/docs/C/legal.xml deleted file mode 100644 index ac97e1de..00000000 --- a/docs/C/legal.xml +++ /dev/null @@ -1,76 +0,0 @@ - <legalnotice id="legalnotice"> - <para> - Permission is granted to copy, distribute and/or modify this - document under the terms of the GNU Free Documentation - License (GFDL), Version 1.1 or any later version published - by the Free Software Foundation with no Invariant Sections, - no Front-Cover Texts, and no Back-Cover Texts. You can find - a copy of the GFDL at this <ulink type="help" - url="ghelp:fdl">link</ulink> or in the file COPYING-DOCS - distributed with this manual. - </para> - <para> 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. - </para> - - <para> - 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. - </para> - - <para> - DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED - UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE - WITH THE FURTHER UNDERSTANDING THAT: - - <orderedlist> - <listitem> - <para>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 - </para> - </listitem> - <listitem> - <para>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. - </para> - </listitem> - </orderedlist> - </para> - </legalnotice> - diff --git a/docs/C/make-and-upload.sh b/docs/C/make-and-upload.sh deleted file mode 100755 index 9c0bd29b..00000000 --- a/docs/C/make-and-upload.sh +++ /dev/null @@ -1,20 +0,0 @@ -# This script is for George only, so recognize my machine :) -if [ ! -d /home/jirka/ -o ! -d /home/devgnome/ ]; then - echo "Only George wants to run this script (it's for updating the gdm webpage)" - exit -fi - -echo rm -f *.html *.pdf -rm -f *.html *.pdf - -echo docbook2html gdm.xml -docbook2html gdm.xml - -echo docbook2pdf gdm.xml -docbook2pdf gdm.xml - -echo scp *.html zinc.5z.com:/home/www/html/jirka/gdm-documentation/ -scp *.html zinc.5z.com:/home/www/html/jirka/gdm-documentation/ - -echo scp gdm.pdf zinc.5z.com:/home/www/html/jirka/gdm-reference.pdf -scp gdm.pdf zinc.5z.com:/home/www/html/jirka/gdm-reference.pdf diff --git a/docs/ChangeLog b/docs/ChangeLog deleted file mode 100644 index b5e2abe9..00000000 --- a/docs/ChangeLog +++ /dev/null @@ -1,1341 +0,0 @@ -2007-09-17 Jorge Gonzalez <jorgegonz@svn.gnome.org> - - * es/es.po: Updated Spanish translation - -2009-09-17 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Update to 2.21.0 release version. - -2009-09-17 Brian Cameron <brian.cameron@sun.com> - - * Release 2.20.0: - * C/gdm.xml: Updated to new release version - -2007-09-13 Jorge Gonzalez <jorgegonz@svn.gnome.org> - - * es/es.po: Updated Spanish translation - -2007-09-02 Jorge Gonzalez <jorgegonz@svn.gnome.org> - - * es/es.po: Updated Spanish translation - -2007-08-30 Jorge Gonzalez <jorgegonz@svn.gnome.org> - - * es/es.po: Updated Spanish translation - -2007-08-27 Claude Paroz <claude@2xlibre.net> - - * fr/fr.po: Updated French translation. - -2007-07-27 Brian Cameron <brian.cameron@sun.com> - - * Release 2.19.7: - * C/gdm.xml: Updated to new release version - -2007-07-29 Jorge Gonzalez <jorgegonz@svn.gnome.org> - - * es/es.po: Updated Spanish translation - -2007-07-09 Brian Cameron <brian.cameron@sun.com> - - * Release 2.19.4: - * C/gdm.xml: Updated to new release version - -2007-07-02 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add docs for new UtmpLocalLine, UtmpRemoteLine, - UtmpPseudoDevice, and the new device optional argument in the - [servers] section. Also add new section about how GDM supports - utmp/wtmp processing. Remove examples that show the [servers] - section supporting commands which GDM does not support. Now more - consistantly use the word attached display instead of local or - static displays. Rewrite the Configuration of [servers] and - [server-foo] sections so they are more clear. - -2007-06-18 Brian Cameron <brian.cameron@sun.com> - - * en_GB/en_GB.po, es/es.po, ko/ko.po, sv/sv.po, uk/uk.po: I - accidently commited broken versions of these files. Reverting - to the older version before I committed the broken ones. - * fr/fr.po: Added template since file was missing. - -2007-06-12 Claude Paroz <claude@2xlibre.net> - - * Makefile.am: DOC_LINGUAS should only include gnome-doc-utils enabled - languages. Corrected DOC_ENTITIES and DOC_INCLUDES. - -2007-06-09 Claude Paroz <claude@2xlibre.net> - - * fr/figures: - * fr/.cvsignore: - * fr/gdm-fr.omf: Not used any more. Deleted. - * fr/fr.po: New French translation. - -2007-06-09 Claude Paroz <claude@2xlibre.net> - - * C/gdm.xml: Typo corrections and updated FSF address. - -2007-06-06 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Fix stock label information in the docs so it is - accurate. Fixes bug #445291. Patch by Claude Paroz - <claude@2xlibre.net>. - -2007-06-06 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Fix description of gdmchooser options to remove - double wording. - -2007-06-04 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: While reviewing bug #440498, I updated the - docs that explain the new background property so it makes - more sense. - -2007-06-04 Brian Cameron <brian.cameron@sun.com> - - * Release 2.19.2 - * C/gdm.xml: Rewrote the "gdmdynamic Command Line Options" - section to fix a problem with xml2po crashing while trying to - process the file. This problem was caused because some of the - <varlistentry> items did not have values for the <term> tag, - which seemed to make xml2po unhappy. Rewording this section - avoids this problem. Updated to the new release version. - -2007-05-14 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add mdash and percnt entities so that make - stops complaining. Probably a better way to do this since these - should be defined elsewhere, but this seems to work okay. Fix - "e; typo, changing to ". - * C/Makefile.am: Clean up a bit. - -2007-05-14 Brian Cameron <brian.cameron@sun.com> - - * */Makefile.am: Delete these files. They aren't needed. - Update to no longer use the deprecated xmldocs.make and omf.make. - Now gnome-doc-utils.make handles everything. - * Makefile.am: No longer go into SUBDIRS. Instead all all - languages to DOC_LINGUAS. Add gdm.xml to DOC_ENTITIES. This - should fix bug #431168. - -2007-05-14 Brian Cameron <brian.cameron@sun.com> - - * Release 2.19.1: - * C/gdm.xml: Updated to new release version - -2007-05-08 Brian Cameron <brian.cameron@sun.com> - - * gdm.1: Now refer to full documentation in - "Applications / System Tools" section rather than - "GNOME / System". Fixes bug #436807. Patch by - Lo\357c Minier <lool+gnome@via.ecp.fr> - -2007-05-04 Frederic Crozat <fcrozat@mandriva.com> - - * C/gdm.xml: Update background property documentation. - -2007-05-01 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add information about the new X-Gdm-XserverArgs key in the - GDM desktop files. This implements enhancement request #326771. - -2007-05-01 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Improve docs for new "background" feature. - -2007-04-28 Changwoo Ryu <cwryu@debian.org> - - * Makefile.am (SUBDIRS): Removed "ko". - (DOC_LINGUAS): Added "ko". - * ko/*: Migrated to gnome-doc-utils. - -2007-04-21 Jorge Gonzalez <jorgegonz@svn.gnome.org> - - * es/es.po: Updated Spanish translation by Lucas Vieites - -2007-04-19 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add information about new configuration options: - SystemCommandsInMenu, AllowLogoutAction, and RBACSystemCommandKeys. - Add RBAC section to the Security section. - -2007-04-05 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Improved docs some more. Lukasz did not update - all the places where the Face Browser change needed to be - mentioned. - -2007-04-05 Lukasz Zalewski <lukas@dcs.qmul.ac.uk> - - * C/gdm.xml: Added a "Themed with face browser" option to the - Local/Remote Style ComboBox and updated the documentation. Fixes - bug #423300 - -2007-04-02 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add comment about XDMCP troubleshooting. - -2007-03-26 William Jon McCann <mccann@jhu.edu> - - * C/gdm.xml: Update docs for last commit. - -2007-03-23 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: A little more information added to Solaris - and Accessibility sections. - -2007-03-23 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Update Accessibility and Solaris sections - of the manual. The Accessibility section was badly out of - date, and some new information needed to be added (like - that you don't need to create a writable gdm home directory - starting with GNOME 2.18). - -2007-03-23 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add new XnestUnscaledFontPath key to docs. Fix - Configuration section to refer to the configuration file by name - rather than repeating the full path over and over. Now that we - support Xephyr, change docs to refer to "nested Xserver" or "nested - display" rathar than referring to this feature as "Xnest". Added - some docs to the PAM section. Other cleanup of wording. - -2007-03-20 Brian Cameron <brian.cameron@sun.com> - - * es/gdm.xml, uk/gdm.xml: Remove generated files. - -2007-03-20 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add min-screen-height tag to parser so that certain - elements in the theme will only display if the screen is large - enough. Patch by Ray Strode. <rstrode@redhat.com>. Enhancement - #420610. - -2007-03-12 Brian Cameron <brian.cameron@sun.com> - - * Release 2.18.0: - * C/gdm.xml: Update version number. - -2007-03-11 Daniel Nylander <po@danielnylander.se> - - * sv/sv.po: Updated Swedish translation. - -2007-02-26 Brian Cameron <brian.cameron@sun.com> - - * Release 2.17.8 - * en_GB/Makefile.am: Add needed Makefile.am. - * Makefile.am: Remove en_GB from SUBDIRS so it does not build since - needed omf file is not present. - -2007-02-16 David Lodge <dave@cirt.net> - - * en_GB/en_GB.po: Added English (British) translation - * Makefile.am: Added en_GB - -2007-02-12 Brian Cameron <brian.cameron@sun.com> - - * Release 2.17.7 - * C/gdm.xml: Update version number. - -2007-02-09 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add sockets command to start login procedure, to be used - by gnome-screensaver and Fast User Switch applet. Fixes enhancement - request #335786. Patch by Matthias Clasen <mclasen@redhat.com>. - -2007-02-02 Daniel Nylander <po@danielnylander.se> - - * sv/sv.po: Updated Swedish translation. - -2007-01-26 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Fix tags. - -2007-01-24 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Some improvements to the PAM documentation. Suggestions - by Gary Winiger <Gary.Winiger@sun.com>. - -2006-12-29 Brian Cameron <Brian.Cameron@sun.com> - - * C/gdm.xml: Add revnumber and date to GDM docs. Patch by Paul - <ephraim_owns@hotmail.com>. Helps to fix bug #389931. - -2006-12-13 Brian Cameron <brian.cameron@sun.com> - - * Release 2.17.4: - * C/gdm.xml: Update version number. - -2006-12-12 Francisco Javier F. Serrador <serrador@openshine.com> - - * es/es.po: Updated Spanish translation. - -2006-12-04 Brian Cameron <brian.cameron@sun.com> - - * Release 2.17.3: - * C/gdm.xml: Update version number. - -2006-11-06 Brian Cameron <brian.cameron@sun.com> - - * Release 2.17.2: - * C/gdm.xml: Update version number. - -2006-11-01 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Mention that altfile feature is supported - since 2.16.3. - -2006-10-31 William Jon McCann <mccann@jhu.edu> - - * C/gdm.xml: - Add ConsoleKit support. Fixes #365375. - -2006-10-30 Brian Cameron <brian.cameron@sun.com> - - * Release 2.17.1: - * C/gdm.xml: Fix docs. - -2006-10-30 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add information about userlist-rect id. - -2006-10-30 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add new QUERY_CUSTOM_CMD_LABELS - and QUERY_CUSTOM_CMD_NO_RESTART_STATUS commands and the - new CustomCommandIsPersistent[0-9] - -2006-10-26 Erwann Chenede - <erwann.chenede@sun.com> - - * docs/C/gdm.xml: added documentation for the new alstfile[n] - alternate image file property. - -2006-10-23 Brian Cameron <brian.cameron@sun.com> - - * docs/C/gdm.xml: Corrections to spelling and grammar mistakes. - Patch by Malcolm Parsons <malcolm.parsons@gmail.com>. Also - updated docs for list combo style to indicate this feature is - supported in GDM 2.18 and later. - -2006-10-20 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml Add "combo" style lists and now support "language" and - "session" style lists which can be used directly in the - gdmgreeter theme rather than having to use the session/language - pop-ups. - -2006-10-16 Brian Cameron <brian.cameron@sun.com> - - * Release 2.17.0: - * C/gdm.xml: Update version number. - -2006-10-04 Ariel Rios <ariel@gnu.org> - - Fixes bug #345434. - * C/gdm.xml: Add documentation to indicate that the GUI will now - launch the at-spi-registryd if GTK_ADD_MODULES is set to true. - -2006-09-25 Francisco Javier F. Serrador <serrador@openshine.com> - - * es/es.po: Updated Spanish translation. - -2006-09-22 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Now gdm.conf has SupportAutomount option which, when - turned on, changes the way that GDM accessess the user's $HOME/.dmrc - file so that automounted $HOME directories can be configured to work - even with the automounter is not started with the --ghost option. - This feature is off by default. This addresses RFE bug #356869. - Patch by Jerzy Borkowski <jubork@ncac.torun.pl>. - -2006-09-11 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Make gdmdynamic section a bit more clear. - -2006-09-04 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml, es/gdm.xml, uk/gdm.xml: Accidently putback docs fix after - freeze. Backing out. - -2006-08-15 Francisco Javier F. Serrador <serrador@openshine.com> - - * es/es.po: Updated Spanish translation. - -2006-07-27 Francisco Javier F. Serrador <serrador@openshine.com> - - * es/es.po: Updated Spanish translation. - -2006-07-26 Francisco Javier F. Serrador <serrador@openshine.com> - - * es/es.po: Updated Spanish translation. - -2006-07-24 Brian Cameron <brian.cameron@sun.com> - - * Makefile.am: Removing sv since it does not build properly. Running - autogen.sh complains that Makefile.am doesn't exist, and adding one - based on the others seems to cause a build problem also. - -2006-07-23 Daniel Nylander <po@danielnylander.se> - - * sv/sv.po: Added Swedish translation. - * sv/*.xml: Removed obsolete files. - * Makefile.am: Added sv to DOC_LINGUAS. - -2006-07-02 Francisco Javier F. Serrador <serrador@cvs.gnome.org> - - * es.po: Updated Spanish translation. - -2006-06-23 Francisco Javier F. Serrador <serrador@openshine.com> - - * es/es.po: Updated Spanish translation. - -2006-05-24 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Put back support for -nodaemon argument, lost in the - 2006-05-12 patch by Christian Kirbach. This fixes bug #324831. - Patch provided by Ray Strode <rstrode@redhat.com>. - -2006-05-12 Christian Kirbach <Christian.Kirbach@siemens.com> - - * C/gdm.xml: -nodaemon command line option has become --nodaemon. - GDM User Commands section has been rewritten accordingly. Also the - interface stability sections reflects the new changes. - -2006-05-12 Brian Cameron <brian.cameron@sun.com> - - * Release 2.15.1: - * C/gdm.xml: Updated to reflect which interfaces are supported - starting with 2.14.6. - -2006-04-27 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Updated to add new "Using gdmsetup" section and other - corrections. - -2006-04-26 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add docs for new features and the gtk-theme greeter - element feature added in 2.12 but after string-freeze, so docs - could not be updated then. - -2006-04-26 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Updated docs to reflect new per-display config. - -2006-04-25 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml. Add units information to TimedLoginDelay. Fixes bug - #334531. Improved PAM documentation based on input from Gary Winger - <Gary.Winiger@sun.com>. Added info about GET_CUSTOM_CONFIG_FILE. - Added docs for AlwaysLoginCurrentSession which I noticed were - missing. - -2006-04-05 Brian Cameron <brian.cameron@sun.com> - - * es/.cvsignore, uk/.cvsignore: Update .cvsignore files to include - generated files not currently listed. - -2006-03-28 Julio M. Merino Vidal <jmmv@NetBSD.org> - - * C/gdm.xml: Fixes bug #336364. - -2006-03-20 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Updated version to 2.14 in docs. - -2006-03-03 Maxim Dziumanenko <mvd@mylinux.ua> - - * Makefile.am: Add uk to DOC_LINGUAS. - -2006-02-28 Brian Cameron <brian.cameron@sun.com> - - * Release 2.13.0.9: - * Makefile.am: Remove "uk" since there is no such subdir yet. - -2006-02-20 Maxim Dziumanenko <mvd@mylinux.ua> - - * uk/*, Makefile.am: Add Ukrainian translation of the manual. - -2006-02-13 Brian Cameron <brian.cameron@sun.com> - - * Release 2.13.0.8: - * C/gdm.xml: Update docs so that the change from --with-configdir - to --with-defaults-conf and renaming of default and custom config - file is documented. - -2006-02-13 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Change --with-configdir to --with-defaults-conf and make - it work so that the gdm.conf and gdm.conf-custom file can be - installed to different subdirectories. Fixes bug #330905. Patch - provided by Ray Strode. - -2006-02-13 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Last minute updates before string freeze. - -2006-02-10 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Few more updates worth adding. - -2006-02-10 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Updated docs with a bunch of information from the README - and README.install file that really belonged in the docs. - -2006-02-09 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Cleaned up section that explains sockets commands so that - they are in alphabetical order, added info about SERVER_BUSY and new - gdmdynamic -s and -t options. - -2006-02-02 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add comment to docs that +xkb is needed as an Xserver - argument for the keyboard gestures to work. - -2006-01-30 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Change section name for "Security" to "security" so the - generated html file has a more consistant name with the other html - files. - -2006-01-30 Brian Cameron <brian.cameron@sun.com> - - * Release 2.13.0.7: - * C/gdm.xml: Updated version/date. - * Makefile.am: Adding es back to SUBDIRS. - * es/Makefile.am: Adding file. - -2006-01-30 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Added new "options_button" which pops up the F10 menu. - Modified themes to now use the new options button for a cleaner - one-button look. Patch provied by Sebastien Bacher - <seb128@debian.org>. Modifications to existing themes made by - myself. Also modified string "Remote login via XDMCP" to "Remote - Login via XDMCP". - -2006-01-27 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Change "XDMCP Chooser" to "Remote login via XDMCP". - Fixing bug #328857. - -2006-01-23 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add Troubleshooting section. - -2006-01-20 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Better scrollkeeper/yelp description for GDM. Fixes - bug #327796. Patch by Alessandro Ferrucci <a24@umbc.edu>. - -2006-01-19 Brian Cameron <brian.cameron@sun.com> - - * Release 2.13.0.6: - * docs/C/gdm.xml: Updated version/date. - -2006-01-17 Brian Cameron <brian.cameron@sun.com> - - * docs/C/gdm.xml: Added docs for "secure remote" feature. Patch - provided by Dominique Hazael-Massieux. - -2006-01-15 Brian Cameron <brian.cameron@sun.com> - - * Release 2.13.0.5: - * docs/C/gdm.xml: Updated version/date. - -2006-01-13 Brian Cameron <brian.cameron@sun.com> - - Enhancement patch provided by Dominique Hazael-Massieux - <dominique.hazael-massieux@centraliens.net> - - * C/gdm.xml: Add support for --enable-secureremote - -2006-01-11 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Change the "Please make sure the Caps Lock key is not - enabled." message to the more informational "Caps Lock is on.". - Some users may want to use Caps Lock when logging in. - -2006-01-11 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Use "Shut Down" instead of "Shut down" or "shut down". - -2006-01-11 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Rename "shutdown" to "shut down" or "halt" and rename - "capslock" to "Caps Lock" since these are the recommended wordings - suggested by Calum Benson. Also corrected a few errors in the stock - labels. - -2006-01-04 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Added "Performance" section to discuss the - --with-prefetch option. - -2006-01-04 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Fix Prefetch command so that there is a needed "@" before - the argument to gdmprefetch. Padraig O'Briain pointed out this - oversight. Made docs a bit more clear to highlight the usage of - this "@" character. - -2006-01-03 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Rewrote the Introduction section so it is more clear, - made improvements to the Accessibility section, and fixed a number - of formatting issues. Now a separate Security section. Updated - docs to reflect PreFetchProgram change. - -2006-01-02 Brian Cameron <brian.cameron@sun.com> - - * Release 2.13.0.4: - * C/gdm.xml: Updated version/date. - -2005-12-24 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Now mention that if the user hits just ENTER when - TimedLoginEnable is on, that GDM will just login immediately as the - timed user. This is how GDM has always behaved, just was not - documented. - -2005-12-24 Brian Cameron <brian.cameron@sun.com> - - Happy holidays. Some bug fixes. - - * C/gdm.xml: Document how character sequences work with text labels - and Welcome/RemoteWelcome messages. - -2005-12-21 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Updated docs with information about the new priority - [server-foo] configuration option. - -2005-12-21 Brian Cameron <brian.cameron@sun.com> - - Patch by Padraig O'Briain <Padraig.OBriain@sun.com>, modified by myself - so it also works with gdmlogin and not just gdmgreeter. Also I - integrated his gdmprefetch.c utility into the configure/Makefile system - with the --with-prefetch option. - - * C/gdm.xml: Add docs for new PostDisplayProgram key. - -2005-12-21 Brian Cameron <brian.cameron@sun.com> - - Refer to main ChangeLog for more information about the GDM - configuration redesign. - - * C/gdm.xml: Updated docs with info about how configuration works now. - Now sockets protocol info is the same in this document and - daemon/gdm.h - -2005-12-12 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add docs for new GET_SERVER_LIST and GET_SERVER_DETAILS - sockets commands. - -2005-12-12 Brian Cameron <brian.cameron@sun.com> - - * Release 2.13.0.3: - * C/gdm.xml: Updated version/date. - -2005-11-28 Brian Cameron <brian.cameron@sun.com> - - * Release 2.13.0.2: - * C/gdm.xml: Updated version/date and added new info about GET_CONFIG - command. - -2005-11-14 Brian Cameron <Brian.Cameron@sun.com> - - * Release 2.13.0.1: - * C/gdm.xml: Updated version/date. - -2005-11-03 Dennis Cranston <dennis_cranston@yahoo.com> - - * C/gdm.xml: Fixes bug #314685. - -2005-10-26 Brian Cameron <Brian.Cameron@sun.com> - - * C/gdm.xml: Updated to include more workaround info for - accessibility. - -2005-10-06 Brian Cameron <Brian.Cameron@sun.com> - - * C/gdm.xml: Add some information about using GlobalFaceDir when home - directories are mounted via NFS/NIS, etc. - -2005-09-14 Brian Cameron <Brian.Cameron@sun.com> - - * C/gdm.xml: Docs had very little information about debug, so added - some. - -2005-08-22 Tommi Vainikainen <thv@iki.fi> - - * C/gdm.xml, gdm.1: Fixed address of the web site. - -2005-08-15 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Updated Face Browser docs to better explain how things - work now that bug #310906 has been fixed, and to clarify that the - Face Browser can be used with the Themed Greeter. - -2005-08-15 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Updated links to point to the new - http://www.gnome.org/projects/gdm/ for the project page. Updated - Commands section of the docs so they look better. Fixed - art.gnome.org link. - -2005-08-11 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Updated gdmflexiserver docs so they are more clear and - added info about the SDTLOGIN mechanism. Add info about new - gdmflexiserver --startnew (or -s) option. - -2005-08-03 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Made XML conformant. - -2005-08-03 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Discuss support for /etc/default/login. - -2005-08-02 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Updated docs. - -2005-07-31 Tommi Vainikainen <thv@iki.fi> - - * C/gdm.xml: This is now valid Docbook XML. - - * *: Migrated to gnome-doc-utils. - -2005-07-31 Tommi Vainikainen <thv@iki.fi> - - * ChangeLog: Started new ChangeLog similar to po/ChangeLog after - gnome-doc-utils migration. This file has older entries because - they were ported over on 2007-06-03. - -2005-07-26 Tommi Vainikainen <thv@iki.fi> - - * C/gdm.xml: Documented new default "auto" option for Use24Clock, - which selects 24 hour time format by locale (translation). Fixes - bug #145549. - -2005-07-22 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: GDM configuration enhancements. - -2005-07-19 Tommi Vainikainen <thv@iki.fi> - - * C/gdm.xml: Cleanup terminology, and fix many strings. See bug - #310453. Also fixes bug #308287. List of the most important string - changes: - machine -> computer - program -> application or command - superuser -> root - gdm, Gdm -> GDM - See the Language chapter in GNOME HIG for more information. - -2005-06-30 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Corrected grammar. Thanks to Martin Petersen for - noticing this. - -2005-06-17 Julio M. Merino Vidal <jmmv84@gmail.com> - - * C/gdm.xml: Fix duplicate entity ID so that the document validates - correctly. Fixes bug #308048. - -2005-05-17 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Added support for dynamic Xservers. Fixes enhancement - request #168219. Patch provided by Bob Terek <Robert.Terek@sun.com>. - -2005-05-03 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Now support random theme. Fixes #302354. Patch by - Andrew Case. - -2005-04-25 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Now support background programs that are started after a - timedelay and can be restarted after a delay. Useful for running a - screensaver at login time. Fixes bug #301528. Patch provided by - Laurent Birtz. - -2005-04-22 Mark McLoughlin <mark@skynet.ie> - - Add the ability to make GDM spawn XDMCP sessions on a local - X proxy server. Experimental support for disconnect/reconnect - or "session migration" is also implemented using DMX. - More details in bug #301602. - - * C/gdm.xml: document new config keys. - -2005-04-19 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Now support ratio scaling of SVG images. Docs were not - provided with the patch so I added some. Fixes bug 159524. Patch - provided by Vincent Untz <vincent@vuntz.net>. Also fixed spelling. - * C/gdm.xml: Fixed bug 300138 by providing better sound docs in the - a11y section. Fixes bug #300138. Patch provided by Andrew Case. - -2005-04-18 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add login success/failure sounds. Patch provided by - Andrew Case. Refer to bug #300136. - -2005-04-15 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Add docs for DefaultWelcome and DefaultRemoteWelcome - keys and the ability to allow theming of background colors in - the Face Browser. - -2005-03-23 Brian Cameron <Brian.Cameron@sun.com> - - * C/gdm.xml: Add face browser tab for configuring the face browser - with the Exclude options and the new Include and IncludeAll - configuration options. - -Fri Mar 18 21:45:0000 2005 Brian Cameron <Brian.Cameron@Sun.Com> - - * C/gdm.xml: Added OK button to greeter so GDM now properly follows - the Sun HCI recommendations. Fixes bug #98470. - -Thu Mar 17 2:06:00 2005 Brian Cameron <Brian.Cameron@Sun.Com> - - * C/gdm.xml: Made face browser much less braindead. The facebrowser - is no longer insensitive when entering the password so you can - change the selected user without having to enter an invalid - password. Also added a cancel button which allows user to reselect - a different username without having to enter an invalid password. - Removed the stupid double-click requirement to select a user with - the face browser. Now just clicking on a user takes you to password - entry. Clicking the cancel button unselects all users in the face - browser and takes the user back to the Username prompt. - -Mon Mar 14 12:10:00 2005 Brian Cameron <Brian.Cameron@Sun.Com> - - * C/gdm.xml: Added Include and IncludeAll gdm config options to - better control what users are displayed in the face browser. - -Thu Mar 10 17:50:00 2005 Brian Cameron <Brian.Cameron@Sun.Com> - - * C/gdm.xml: Document the face that the default face directory is - changed to EXPANDED_DATADIR/pixmaps/faces since putting the faces - subdirectory in pixmaps simply makes more sense. Also document - changes to the way GDM files are installed. Now all programs - intended to be run by root are in EXPANDED_SBINDIR - (gdm/gdm-binary/gdmsetup), all programs that are not intended to be - run by end-users are in EXPANDED_LIBEXEC - (gdmchooser/gdmgreeter/gdmlogin). Removed gdmconfig wrapper script - and gdmXnest symlink since they only server to clutter the - filesystem. - -Mon Feb 14 16:42:00 2005 Brian Cameron <Brian.Cameron@Sun.Com> - - * C/gdm.xml: Fixes bug #151018. Add configuration option to disallow - visible feedback in password entry. Patch provided by John - Martinsson. - -Thu Aug 26 15:55:00 2004 Brian Cameron <brian.cameron@sun.com> - - * C/gdm.xml: Updated docs to include gdmflexiserver command options, - arguments for all GDM programs aside from gdm-binary (which was - already there), added accessibility section, and cleaned up the XML - so it is more readible. Also added a comment that gdmlogin now lets - you change the theme from the menu. - -Wed Jul 14 09:37:25 2004 George Lebl <jirka@5z.com> - - * C/gdm.xml: Document the new CheckDirOwner key to fix systems - which have non-user-owned home dirs. - -Tue Jul 13 10:27:35 2004 George Lebl <jirka@5z.com> - - * C/gdm.xml: Add mention that VTAllocation now works on FreeBSD as - well. - -Wed May 26 18:23:14 2004 George Lebl <jirka@5z.com> - - * C/gdm.xml: Add a daemon/ConsoleCannotHandle key which lists - languages which should not be used on the console because they - will not work. Uses "C" locale strings instead then. Should - "fix" #135387, but I suppose there's no clean way to do this, - just let the distributors ship proper config files and have them - test it (yeah right). I've tested the current set on RH9 and I - listed all of the ones that didn't work. - -Fri Apr 16 16:02:53 2004 George Lebl <jirka@5z.com> - - * C/gdm.xml: update version information, no changes. I should have - done this before the release. - -Mon Mar 15 10:22:30 2004 George Lebl <jirka@5z.com> - - * Release 2.6.0.0 - * Makefile.am: fix build - -2004-03-15 Glynn Foster <glynn.foster@sun.com> - - * Makefile.am: Add localized docs to build. - * *: Add de, es, fr, it, ja, ko, sv, zh_CN, zh_HK and zh_TW - all from the Sun translation team. - -Thu Feb 12 11:49:20 2004 George Lebl <jirka@5z.com> - - * C/gdm.xml, config/gdm.conf.in: Adding the GtkTheme, - AllowGtkThemeChange and GtkThemesToAllow keys - -Tue Jan 06 17:06:42 2004 George Lebl <jirka@5z.com> - - * C/gdm.xml: update for DisplayLastLogin - -Tue Dec 30 15:34:59 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: Update docs for the accessibility/sound stuff - -Mon Dec 29 16:52:32 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: set version to 2.5.90.0 since it's really for GNOME 2.5 - not 2.4 - -Fri Dec 12 17:56:58 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: Add a GO fifo SOP command and a --wait-for-go command - line option. This is intended to allow an initialization script to - start X early and have that be the GDM display, but not allow users - to log in until it's ready. - -Fri Dec 12 17:14:41 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: There's now the ability to reap flexiservers that are - inactive for a period of time. The default time is 5 minutes. - -Wed Dec 10 13:08:13 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: Move the built in sessions to a more appropriate place - (datadir). Apply a patch from Anton Altaparmakov to add an optional - info message to the greeters. Fixes #125219 - -Wed Dec 10 2003 Archana Shah <archana.shah@wipro.com> - - * C/gdm.xml: Add documentation for Multicast and Multicast_Addr. - -Mon Oct 06 15:02:19 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: add info about NeverPlaceCookiesOnNFS - -Wed Sep 24 13:21:43 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: update the docs a bit - -Mon Sep 22 15:01:41 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: update a bit. - -Fri Sep 19 13:41:37 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: Update the session docs to reflect reality, - plus some other minor cleanup - -Thu Sep 18 13:53:37 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: update for the SessionDesktopDir path stuff - -Fri Sep 12 14:49:30 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: update - -Tue Aug 26 18:06:51 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: minor update - -Tue Aug 26 17:58:46 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: lots of updates, stylistic and fixing - errors, also add ShowLastSession. - -Mon Aug 25 16:27:09 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: update - -Mon Aug 25 11:13:08 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: update the SystemMenu (Actions menu) key description. - -Mon Aug 25 10:47:30 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: updates relating to the ~/.xsession-errors stuff and how - to handle the Xsession file. - -Thu Aug 21 14:35:25 2003 George Lebl <jirka@5z.com> - - * Makefile.am, gdm.1: add a very simple man page - -Wed Aug 20 12:13:04 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: minor updates - -Mon Aug 18 11:02:38 2003 George Lebl <jirka@5z.com> - - To prevent a possible DoS attack where an app might spit out - too many warnings on stdout/stderr and thus fill up the users - home dir (or when an app is buggy), the output of the session - no longer goes directly into .xsession-errors but in fact - through an internal pipe. This way we can just cap the file - at some size (currently 80*2500 bytes, which should be long - enough for actual use in debugging but it's short enough to - prevent a DoS attack) - - * C/gdm.xml: note about the above - -Fri Aug 15 12:36:30 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: added more notes on the MIT-MAGIC-COOKIE-1 authorization - scheme - -Thu Aug 14 17:50:30 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: Update docs for UserAuthDir and add a note about using - this with NFS mounted home directories. - -Mon Aug 11 09:38:08 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: whack a doubled paragraph. - -Fri Aug 08 17:20:59 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: fill in missing info in the theme manual - -Thu Aug 07 17:59:25 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: add more comments on security of XDMCP, fixup the screen - sections a bit, whack SessionMaxFile entry - -Wed Aug 06 17:40:27 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: more notes on security of XDMCP and using - MIT-MAGIC-COOKIE-1 added, plus a section on the TCP Wrappers, - though it kind of sucks. - -Wed Aug 06 12:05:52 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: update version number - -Wed Aug 06 11:39:37 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: some fixes from my mailspool from like a year ago, plus - added section about terminal lab example setups. - -Thu Jul 31 15:26:41 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: add the release info as the first paragraph of the - preface so that it appears in the HTML and PDF versions - -Thu Jul 31 13:50:38 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: fix closing tag - -Mon Jul 28 16:28:28 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: fix doc of the gdm User/Group and add a section on this - to the Overview. - -Fri Jul 25 16:31:24 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: add documentation of command line options - -Thu Jul 24 16:41:25 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: update the version information on top - -Thu Jul 24 16:40:07 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: fixed the art.gnome.org link added a link to the GDM - website, ran through a spellchecker, whacked the last vestiges of - iconification feature mentions and added MinimalUID mention next to - Exclude in the overview. - -Thu Jul 24 14:58:23 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: update the PostLogin behaviour and the permissions on the - ServAuthDir - -Wed Jul 23 15:13:33 2003 George Lebl <jirka@5z.com> - - * Release 2.4.2.98 - * Makefile.am: fix for distcheck - -Mon Jul 21 15:36:48 2003 George Lebl <jirka@5z.com> - - * GdmGreeterThemeManual.txt: removed since this is now in the XML - documentation - -Mon Jul 21 13:45:31 2003 George Lebl <jirka@5z.com> - - * C/gdm-C.omf: add. I forgot to add this to CVS :) - -Sun Jul 20 14:34:42 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: remove the documentation for the Icon key, and add a - better blurb in the [servers] description. - -Sun Jul 20 12:36:06 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: update - -Sun Jul 20 08:59:19 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: fix docbook errors - -Sat Jul 19 16:40:55 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml: update the way the years in the copyright are done - -Sat Jul 19 16:33:19 2003 George Lebl <jirka@5z.com> - - * C/gdm.xml, C/Makefile.am, Makefile.am: Update the documentation a - lot and install the docs. Yay! We have actual documentation now!!! - -Sat Jul 19 16:33:19 2003 George Lebl <jirka@5z.com> - - * C/gdmconfig/*, C/gdm.sgml, C/gdm-manual.txt: Remove everything here - as it was old and unused and outdated. - -Tue Jul 15 15:54:14 2003 George Lebl <jirka@5z.com> - - * GdmGreeterThemeManual.txt: Update the theme manual adding the - userlist and whacking pam-warning which does not exist and other - minor fixes and additions. - -Thu Jun 26 12:01:55 2003 George Lebl <jirka@5z.com> - - * Makefile.am: Actually include the docs dir in the tarball and redo - the .96 release (doh!) - -Wed Jun 11 16:04:02 2003 George Lebl <jirka@5z.com> - - * Makefile.am: Actually include the theme document, DUH! - -Fri Jun 06 19:07:22 2003 George Lebl <jirka@5z.com> - - * GdmGreeterThemeManual.txt: Update a bit on theme creation and the - .desktop file and add notes about gdmthemetester - -Wed Jun 04 Brian Cameron <Brian.Cameron@Sun.COM> - - * GdmGreeterThemeManual.txt: Added theme docs. - -Tue May 13 17:00:16 2003 George Lebl <jirka@5z.com> - - * C/gdm.(xml|sgml): PingInterval is now in seconds. It really makes - no sense in minutes, I mean who wants to use a connection which - hangs for several minutes, that makes no sense. This fixes a whole - bunch of bugs, among others #103266 - -2003-04-10 Niall Power <Niall.Power@Sun.COM> - - * C/gdm.xml: Add support for launching gdmlogin/gdmgreeter with a - configurable list of gtk modules. Needed for accessibility. Adds - two new options to gdm.conf: "AddGtkModules" (boolean) and - "GtkModulesList" (string). - -Thu Apr 25 17:20:52 2002 George Lebl <jirka@5z.com> - - * Makefile.am: Do not build gdmconfig docs. - -Mon Dec 10 08:23:00 2001 Trevor Curtis <tcurtis@somaradio.ca> - - * C/gdm.xml: Updated the doc to use the FDL, and cleaned up a few - things. - -Fri Dec 7 23:02:12 2001 Trevor Curtis <tcurtis@somaradio.ca> - - * C/gdmconfig/C/gdm.xml: Removed Tim Jansen from documentation at his - request. - -Fri Dec 7 06:33:13 2001 Trevor Curtis <tcurtis@soamradio.ca> - - * C/gdmconfig/C/gdm.xml: Created xml version of gdmconfig - documentation. - -Fri Dec 7 05:05:26 2001 Trevor Curtis <tcurtis@somaradio.ca> - - * C/gdm.xml: Created xml version of GDM documentation. - -Wed Oct 24 17:57:03 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: Remove the XKeepsCrashingConfigurators option. - -Wed Oct 24 01:22:41 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: Remove documentation of the VerboseAuth option. - -Sat Oct 20 12:03:14 2001 George Lebl <jirka@5z.com> - - * C/Makefile.am: DESTDIR added patch by: frodol@dds.nl (Frodo - Looijaard) - -Tue Sep 11 02:34:47 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: Apply and finish a patch from Terje Rosten - <terjeros@phys.ntnu.no> to add an option to force 24 hour clock on - the greeter - -Tue Sep 4 18:52:10 2001 Trevor Curtis <tcurtis@somaradio.ca> - - * gdmconfig/C/figures/GDM_xserv_setup.png,GDM_xdmcp.png: Updated the - above screenshots to reflect recent changes. - -Sat Sep 01 14:53:22 2001 George Lebl <jirka@5z.com> - - * gdmconfig/C/gdmconfig.sgml: Updated trevors email. - -Sat Sep 01 00:47:36 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: a small update - -Fri Aug 31 20:22:33 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: Update for all the server def stuff. - -Fri Aug 31 18:21:46 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: update - -Fri Aug 31 18:12:05 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: Document some of the new configuration keys. Not - everything is documented yet. - -Fri Aug 24 19:32:42 2001 George Lebl <jirka@5z.com> - - * sgmldocs.make: update to newest from gnome-core - -Fri Aug 17 14:47:08 2001 George Lebl <jirka@5z.com> - - * C/Makefile.am: fix rules since the .sgml file changed - -2001-08-14 Kjartan Maraas <kmaraas@gnome.org> - - * C/gdm.sgml: Fix sgml up a bit. - * gdmconfig/C/gdmconfig.sgml: Fix up here too. - -Thu Jun 28 18:48:56 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: add docs for the above two keys - -Tue Jun 26 23:00:04 2001 Trevor Curtis <trevor.curtis@home.com> - - * gdmconfig/C: added sections for Miscellaneous, and Login Sessions. - Updated XServer-Setup section. - * gdmconfig/C/figures/*: updated GDM_xserv_setup.png, and - GDM_login_sessions.png. Added GDM_expert_misc.png - -Sun Jun 24 14:55:29 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: Add daemon/AlwaysRestartServer option. - -Fri Jun 22 19:13:05 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: fix indirect wait entry, add entries for the showingl - of different built in sessions (failsafes, chooser) - -Thu May 24 12:55:05 2001 George Lebl <jirka@5z.com> - - * Makefile.am, sgmldocs.make, gdmconfig/C/Makefile.am: Set up the - documentation/omf build stuff. - - * gdmconfig/C/gdmconfig.sgml: fix version to say 2.2.2 and this is - part of the GDM package not the Gnome-Core package :) - -Wed May 23 23:31:00 2001 Trevor Curtis <trevor.curtis@home.com> - - * gdmconfig/C/gdmconfig.sgml: Added the expert and system - descriptions. - - * gdmconfig/C/figures: Was created to put the screenshots in for the - gdmconfig doc. - - * gdmconfig/C/figures/*: added the following png's; - GDM_auto_login.png, GDM_background.png, GDM_chooser.png, - GDM_enviro.png, GDM_face_brow.png, GDM_full.png, - GDM_login_appear.png, GDM_login_behav.png, GDM_login_sessions.png, - GDM_menubar.png, GDM_misc.png, GDM_paths.png, GDM_security.png, - GDM_xdmcp.png, GDM_xserv_setup.png - -Fri May 18 04:17:00 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: Add a config option for a failsafe X server which is - empty by default - -Fri May 18 00:16:58 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: update for the XKeepsCrashing stuff - -Mon May 14 22:20:09 2001 George Lebl <jirka@5z.com> - - * C/Makefile.am: install the index.html file correctly on make install. - For those weirdos like me that run out of CVS - -Mon May 14 21:52:53 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: Add proper copyrights/authors for me and Tim Jensen and - update the configuration section with all the new keys. - -Thu Apr 19 17:32:36 2001 George Lebl <jirka@5z.com> - - * C/gdm.sgml: Update the VerboseAuth and AllowRoot sections to - reflect what actually happens nowdays. - -Sun Mar 4 16:13:55 2001 Lee Mallabone <lee0@callnetuk.com> - - * gdmconfig/*: Added initial directory structure/files for the - gdmconfig user guide. Not installed yet. - - * gdmconfig/C/gdmconfig.sgml: Initial gdmconfig user guide content - from Trevor Curtis <trevor.curtis@home.com>. - -Mon Feb 19 21:37:07 2001 George Lebl <jirka@5z.com> - - Patch from Tim Jansen <tim@tjansen.de> - - * C/gdm.sgml: Fixed docs in terms of true/false vs. 1/0 and add new - values. - -2000-12-12 Mathieu Lacage <mathieu@eazel.com> - - Make it: 1) compile 2) pass make distcheck. - * C/Makefile.am: remove images. - * C/gdm.sgml: fix sgml. - -1999-09-27 <mkp@mkp.net> - - * C/gdm.sgml: Lots of updates. - -1999-08-18 <mkp@mkp.net> - - * C/gdm.sgml: More documentation work. - -1999-08-16 <mkp@mkp.net> - - * C/gdm.sgml: SGML-ified manual. Only bare bones so far. - -1999-08-15 <mkp@mkp.net> - - * gdm-manual.txt: Updated for v2 config file syntax. - -1999-05-14 Jacob Berkman <jberk+@cmu.edu> - - * gdm-manual.txt: Added entry for %m - -1998-12-01 Martin Kasper Petersen <mkp@mkp.net> - - * gdm-manual.txt: Crude manual draft. - - diff --git a/docs/Makefile.am b/docs/Makefile.am deleted file mode 100644 index f86894f4..00000000 --- a/docs/Makefile.am +++ /dev/null @@ -1,11 +0,0 @@ -include $(top_srcdir)/gnome-doc-utils.make -dist-hook: doc-dist-hook - -DOC_MODULE = gdm -DOC_ENTITIES = legal.xml -DOC_INCLUDES = -DOC_LINGUAS = en_GB es fr ko oc sv uk -# de it ja zh_CN zh_HK zh_TW need to be transitioned to gnome-doc-utils - -man_MANS = gdm.1 -EXTRA_DIST = gdm.1 diff --git a/docs/de/.cvsignore b/docs/de/.cvsignore deleted file mode 100644 index ab4d4d42..00000000 --- a/docs/de/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -Makefile -Makefile.in -*.out -omf_timestamp diff --git a/docs/de/figures/gdm_window.png b/docs/de/figures/gdm_window.png Binary files differdeleted file mode 100644 index bd1e10ab..00000000 --- a/docs/de/figures/gdm_window.png +++ /dev/null diff --git a/docs/de/gdm-de.omf b/docs/de/gdm-de.omf deleted file mode 100644 index f84357d7..00000000 --- a/docs/de/gdm-de.omf +++ /dev/null @@ -1,18 +0,0 @@ -<?xml version="1.0" encoding="UTF8"?> <omf> - <resource> - <creator>docs@gnome.org (GDP) </creator> - <maintainer>docs@gnome.org (GDP) </maintainer> - <title>Einrichtung des Anmeldebildschirms Handbuch V2.0.1 </title> - <date>2004-01-19 </date> - <version identifier="2.0.1" date="2004-01-19" description="Neu erstellt für Quicksilver, Programmversion 2.4.2.101"/> - <subject category="GNOME|Applications|System Tools"/> - - <description>Benutzerhandbuch für die Anwendung "Einrichtung des Anmeldebildschirms" </description> - <type>user's guide </type> - <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/> - <identifier url="gdm.xml"/> - <language code="de"/> - <relation seriesid="be6a0524-46d3-11d8-983d-e135363498a8"/> - <rights type="GNU FDL" license.version="1.1" holder="Sun Microsystems"/> - </resource> -</omf> diff --git a/docs/en_GB/en_GB.po b/docs/en_GB/en_GB.po deleted file mode 100644 index e6cb1d75..00000000 --- a/docs/en_GB/en_GB.po +++ /dev/null @@ -1,6599 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: gdm2\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2007-02-16 07:18+0100\n" -"PO-Revision-Date: 2007-02-16 23:29-0000\n" -"Last-Translator: David Lodge <dave@cirt.net>\n" -"Language-Team: en_GB <en@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: C/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 <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or in the file COPYING-DOCS distributed with this manual." -msgstr "Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation Licence (GFDL), Version 1.1 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or in the file COPYING-DOCS distributed with this manual." - -#: 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 "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 licence to the manual, as described in section 6 of the licence." - -#: 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 "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." - -#: 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 "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 LICENCE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS AUTHORISED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND" - -#: 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 "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." - -#: 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: <placeholder-1/>" -msgstr "DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENCE WITH THE FURTHER UNDERSTANDING THAT: <placeholder-1/>" - -#: C/gdm.xml:11(title) -msgid "Gnome Display Manager Reference Manual" -msgstr "Gnome Display Manager Reference Manual" - -#: C/gdm.xml:15(revnumber) -msgid "0.0" -msgstr "0.0" - -#: C/gdm.xml:16(date) -msgid "2007-01" -msgstr "2007-01" - -#: C/gdm.xml:21(para) -msgid "GDM is the GNOME Display Manager, a graphical login program." -msgstr "GDM is the GNOME Display Manager, a graphical login program." - -#: C/gdm.xml:28(firstname) -msgid "Martin" -msgstr "Martin" - -#: C/gdm.xml:28(othername) -msgid "K." -msgstr "K." - -#: C/gdm.xml:29(surname) -msgid "Petersen" -msgstr "Petersen" - -#: C/gdm.xml:31(email) -msgid "mkp@mkp.net" -msgstr "mkp@mkp.net" - -#: C/gdm.xml:35(firstname) -msgid "George" -msgstr "George" - -#: C/gdm.xml:35(surname) -msgid "Lebl" -msgstr "Lebl" - -#: C/gdm.xml:37(email) -msgid "jirka@5z.com" -msgstr "jirka@5z.com" - -#: C/gdm.xml:41(firstname) -msgid "Brian" -msgstr "Brian" - -#: C/gdm.xml:41(surname) -msgid "Cameron" -msgstr "Cameron" - -#: C/gdm.xml:43(email) -msgid "Brian.Cameron@Sun.COM" -msgstr "Brian.Cameron@Sun.COM" - -#: C/gdm.xml:47(firstname) -msgid "Bill" -msgstr "Bill" - -#: C/gdm.xml:47(surname) -msgid "Haneman" -msgstr "Haneman" - -#: C/gdm.xml:49(email) -msgid "Bill.Haneman@Sun.COM" -msgstr "Bill.Haneman@Sun.COM" - -#: C/gdm.xml:54(year) -msgid "1998" -msgstr "1998" - -#: C/gdm.xml:54(year) -msgid "1999" -msgstr "1999" - -#: C/gdm.xml:54(holder) -msgid "Martin K. Petersen" -msgstr "Martin K. Petersen" - -#: C/gdm.xml:57(year) -msgid "2001" -msgstr "2001" - -#: C/gdm.xml:57(year) -#: C/gdm.xml:61(year) -#: C/gdm.xml:64(year) -msgid "2003" -msgstr "2003" - -#: C/gdm.xml:57(year) -#: C/gdm.xml:64(year) -msgid "2004" -msgstr "2004" - -#: C/gdm.xml:58(holder) -msgid "George Lebl" -msgstr "George Lebl" - -#: C/gdm.xml:61(holder) -msgid "Red Hat, Inc." -msgstr "Red Hat, Inc." - -#: C/gdm.xml:64(holder) -msgid "Sun Microsystems, Inc." -msgstr "Sun Microsystems, Inc." - -#: C/gdm.xml:69(releaseinfo) -#: C/gdm.xml:78(para) -msgid "This manual describes version 2.17.7 of the GNOME Display Manager. It was last updated on 02/12/2007." -msgstr "This manual describes version 2.17.7 of the GNOME Display Manager. It was last updated on the 12th February 2007." - -#: C/gdm.xml:76(title) -msgid "Terms and Conventions Used in This Manual" -msgstr "Terms and Conventions Used in This Manual" - -#: C/gdm.xml:83(para) -msgid "Chooser - A program used to select a remote host for managing a display remotely on the local display (<command>gdmchooser</command>)." -msgstr "Chooser - A program used to select a remote host for managing a display remotely on the local display (<command>gdmchooser</command>)." - -#: C/gdm.xml:88(para) -msgid "Configurator - The configuration application (<command>gdmsetup</command>)." -msgstr "Configurator - The configuration application (<command>gdmsetup</command>)." - -#: C/gdm.xml:93(para) -msgid "GDM - Gnome Display Manager. Used to describe the software package as a whole. Sometimes also referred to as GDM2." -msgstr "GDM - Gnome Display Manager. Used to describe the software package as a whole. Sometimes also referred to as GDM2." - -#: C/gdm.xml:98(para) -msgid "gdm - The Gnome Display Manager daemon (<command>gdm</command>)." -msgstr "gdm - The Gnome Display Manager daemon (<command>gdm</command>)." - -#: C/gdm.xml:102(para) -msgid "Greeter - The graphical login window (<command>gdmlogin</command> or <command>gdmgreeter</command>)." -msgstr "Greeter - The graphical login window (<command>gdmlogin</command> or <command>gdmgreeter</command>)." - -#: C/gdm.xml:107(para) -msgid "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)." -msgstr "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)." - -#: C/gdm.xml:111(para) -msgid "PAM - Pluggable Authentication Mechanism" -msgstr "PAM - Pluggable Authentication Mechanism" - -#: C/gdm.xml:115(para) -msgid "Themed Greeter - The themable login window ( <command>gdmgreeter</command>)." -msgstr "Themed Greeter - The themable login window ( <command>gdmgreeter</command>)." - -#: C/gdm.xml:120(para) -msgid "XDMCP - X Display Manage Protocol" -msgstr "XDMCP - X Display Manage Protocol" - -#: C/gdm.xml:124(para) -msgid "Paths that start with a word in angle brackets are relative to the installation prefix. I.e. <filename><share>/pixmaps/</filename> refers to <filename><share>/pixmaps</filename> if GDM was configured with <command>--prefix=/usr</command>. Normally also note that GDM is installed with <command>--sysconfigdir=<etc>/X11</command>, meaning any path to which we refer to as <filename><etc>/gdm/PreSession</filename> usually means <filename><etc/X11>/gdm/PreSession</filename>. Note that for interoperability it is recommended that you use a --prefix of <filename>/usr</filename> and a --sysconfdir of <filename><etc>/X11</filename>." -msgstr "Paths that start with a word in angle brackets are relative to the installation prefix. I.e. <filename><share>/pixmaps/</filename> refers to <filename><share>/pixmaps</filename> if GDM was configured with <command>--prefix=/usr</command>. Normally also note that GDM is installed with <command>--sysconfigdir=<etc>/X11</command>, meaning any path to which we refer to as <filename><etc>/gdm/PreSession</filename> usually means <filename><etc/X11>/gdm/PreSession</filename>. Note that for interoperability it is recommended that you use a --prefix of <filename>/usr</filename> and a --sysconfdir of <filename><etc>/X11</filename>." - -#: C/gdm.xml:140(title) -msgid "Overview" -msgstr "Overview" - -#: C/gdm.xml:143(title) -msgid "Introduction" -msgstr "Introduction" - -#: C/gdm.xml:147(para) -msgid "The Gnome Display Manager (GDM) is a display manager that implements all significant features required for managing local and remote displays. GDM was written from scratch and does not contain any XDM / X Consortium code." -msgstr "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." - -#: C/gdm.xml:154(para) -msgid "For further information about GDM, see the <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. Please submit any bug reports or enhancement requests to the \"gdm\" category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>. You can also send a message to the <address><email>gdm-list@gnome.org</email></address> mail list to discuss any issues or concerns with the GDM program." -msgstr "For further information about GDM, see the <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. Please submit any bug reports or enhancement requests to the \"gdm\" category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>. You can also send a message to the <address><email>gdm-list@gnome.org</email></address> mail list to discuss any issues or concerns with the GDM program." - -#: C/gdm.xml:167(title) -msgid "Interface Stability" -msgstr "Interface Stability" - -#: C/gdm.xml:171(para) -msgid "The key/value pairs defined in the GDM configuration files and the location of these files are considered \"stable\" interfaces and should only change in ways that are backwards compatible. Note that this includes functionality like the GDM scripts (Init, PreSession, PostSession, PostLogin, XKeepsCrashing, etc.); directory locations (ServAuthDir, PidFile, etc.), system applications (SoundProgram), etc. Some configuration values depend on OS interfaces may need to be modified to work on a given OS. Typical examples are HaltCommand, RebootCommand, CustomCommands, SuspendCommand, StandardXServer, Xnest, SoundProgram, and the \"command\" value for each \"server-foo\"." -msgstr "The key/value pairs defined in the GDM configuration files and the location of these files are considered \"stable\" interfaces and should only change in ways that are backwards compatible. Note that this includes functionality like the GDM scripts (Init, PreSession, PostSession, PostLogin, XKeepsCrashing, etc.); directory locations (ServAuthDir, PidFile, etc.); system applications (SoundProgram); etc. Some configuration values depend on OS interfaces may need to be modified to work on a given OS. Typical examples are HaltCommand, RebootCommand, CustomCommands, SuspendCommand, StandardXServer, Xnest, SoundProgram and the \"command\" value for each \"server-foo\"." - -#: C/gdm.xml:185(para) -msgid "Note: distributions often change the default values of keys to support their platform. Command-line interfaces for GDM programs installed to <filename><bin></filename> and <filename><sbin></filename> 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 "Note: distributions often change the default values of keys to support their platform. Command-line interfaces for GDM programs installed to <filename><bin></filename> and <filename><sbin></filename> 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." - -#: C/gdm.xml:194(para) -msgid "As of the GDM 2.15 development series, some one-dash arguments are no longer supported. This includes the \"-xdmaddress\", \"-clientaddress\", and \"-connectionType\" arguments used by <command>gdmchooser</command>. These arguments have been changed to now use two dashes." -msgstr "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 <command>gdmchooser</command>. These arguments have been changed to use two dashes." - -#: C/gdm.xml:202(para) -msgid "If issues are discovered that break compatibility, please file a bug with an \"urgent\" priority." -msgstr "If issues are discovered that break compatibility, please file a bug with an \"urgent\" priority." - -#: C/gdm.xml:209(title) -msgid "The GDM Daemon" -msgstr "The GDM Daemon" - -#: C/gdm.xml:211(para) -msgid "The GDM daemon is responsible for managing displays on the system. This includes authenticating users, starting the user session, and terminating the user session. GDM is configurable and the ways it can be configured are described in the \"Configuring GDM\" section of this document. The <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename>, and <filename>PostSession</filename> scripts discussed below are discussed in this \"Configuring GDM section\"." -msgstr "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; the ways it may be configured are described in the \"Configuring GDM\" section of this document. The <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> and <filename>PostSession</filename> scripts discussed below are discussed in this \"Configuring GDM section\"." - -#: C/gdm.xml:222(para) -msgid "The GDM daemon supports a UNIX domain socket protocol which can be used to control aspects of its behavior and to query information. This protocol is described in the \"Controlling GDM\" section of this document." -msgstr "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." - -#: C/gdm.xml:229(para) -msgid "GDM can be asked to manage a display a number of ways. Local displays are always managed when GDM starts and will be restarted when a user's session is finished. Displays can be requested via XDMCP, flexible displays can be requested by running the <command>gdmflexiserver</command> command. Displays that are started on request are not restarted on session exit. GDM also provides the <command>gdmdynamic</command> command to allow easier management of displays on a multi-user server. These display types are discussed further in the next section." -msgstr "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 <command>gdmflexiserver</command> command. Displays that are started on request are not restarted on session exit. GDM also provides the <command>gdmdynamic</command> command to allow easier management of displays on a multi-user server. These display types are discussed further in the next section." - -#: C/gdm.xml:241(para) -msgid "When the GDM daemon is asked to manage a display, it will fork an X server process, then run the <filename>Init</filename> script as the root user, and start the login GUI dialog as a slave process on the display. GDM can be configured to use either <command>gdmgreeter</command> (the default) or <command>gdmlogin</command> as the GUI dialog program. The <command>gdmlogin</command> program supports accessibility while the <command>gdmgreeter</command> program supports greater themeability. The GUI dialog is run as the unpriviledged \"gdm\" user/group which is described in the \"Security\" section below. The GUI dialog communicates with the daemon via a sockets protocol and via standard input/output. The slave, for example passes the username and password information to the GDM daemon via standard input/output so the daemon can handle the actual authentication." -msgstr "When the GDM daemon is asked to manage a display, it will fork an X server process, then run the <filename>Init</filename> script as the root user, and start the login GUI dialogue as a slave process on the display. GDM can be configured to use either <command>gdmgreeter</command> (the default) or <command>gdmlogin</command> as the GUI dialogue program. The <command>gdmlogin</command> program supports accessibility while the <command>gdmgreeter</command> program supports greater themeability. The GUI dialogue is run as the unprivileged \"gdm\" user/group which is described in the \"Security\" section below. The GUI dialogue communicates with the daemon via a sockets protocol and via standard input/output. The slave, for example passes the username and password information to the GDM daemon via standard input/output so the daemon can handle the actual authentication." - -#: C/gdm.xml:258(para) -msgid "The login GUI dialog screen allows the user to select which session they wish to start and which language they wish to use. Sessions are defined by files that end in the .desktop extension and more information about these files can be found in the \"Configuration\" section. The user enters their name and password and if these successfully authenticate, GDM will start the requested session for the user. It is possible to configure GDM to avoid the authentication process by turning on the Automatic or Timed Login features in the GDM configuration. The login GUI can also be configured to provide additional features to the user, such as the Face Browser; the ability to halt, restart, or suspend the system; and/or edit the login configuration (after entering the root password)." -msgstr "The login GUI dialogue 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)." - -#: C/gdm.xml:273(para) -msgid "GDM, by default, will use Pluggable Authentication Modules (PAM) for authentication, but can also support regular crypt and shadow passwords on legacy systems. After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, and forks a slave process to start the requested session. This slave process runs the <filename>PreSession</filename> script as root, sets up the user's environment, and starts the requested session. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN interface after user authentication to tell the X server to be restarted as the user instead of as root for added security. When the user's session exits, the GDM daemon will run the <filename>PostSession</filename> script as root." -msgstr "GDM, by default, will use Pluggable Authentication Modules (PAM) for authentication, but can also support regular crypt and shadow passwords on legacy systems. After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, and forks a slave process to start the requested session. This slave process runs the <filename>PreSession</filename> script as root, sets up the user's environment, and starts the requested session. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN interface after user authentication to tell the X server to be restarted as the user instead of as root for added security. When the user's session exits, the GDM daemon will run the <filename>PostSession</filename> script as root." - -#: C/gdm.xml:290(para) -msgid "Note that, by default, GDM uses the \"gdm\" service name for normal login and the \"gdm-autologin\" service name for automatic login. The <filename>PamStack</filename> 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 "Note that, by default, GDM uses the \"gdm\" service name for normal login and the \"gdm-autologin\" service name for automatic login. The <filename>PamStack</filename> 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." - -#: C/gdm.xml:300(para) -msgid "For those looking at the code, the gdm_verify_user function in <filename>daemon/verify-pam.c</filename> is used for normal login and the gdm_verify_setup_user function is used for automatic login." -msgstr "For those looking at the code, the gdm_verify_user function in <filename>daemon/verify-pam.c</filename> is used for normal login and the gdm_verify_setup_user function is used for automatic login." - -#: C/gdm.xml:308(title) -msgid "Different Display Types" -msgstr "Different Display Types" - -#: C/gdm.xml:310(para) -msgid "GDM supports three different display types: static (local) displays, flexible (on-demand) displays, and XDMCP (remote) displays. The \"X Server Definitions\" and the \"Local Static X Display Configuration\" subsections of the \"Configuration\" section explains how these various types of displays are defined in the GDM configuration file." -msgstr "GDM supports three different display types: static (local) displays, flexible (on-demand) displays, and XDMCP (remote) displays. The \"X Server Definitions\" and the \"Local Static X Display Configuration\" subsections of the \"Configuration\" section explains how these various types of displays are defined in the GDM configuration file." - -#: C/gdm.xml:319(para) -msgid "Local static displays are always started by the daemon, and when they die or are killed, they are restarted. GDM can run as many of these as needed. GDM can also manage displays on which it does not manage a GUI login, thus GDM can be used for supporting X terminals." -msgstr "Local static displays are always started by the daemon, and when they die or are killed, they are restarted. GDM can run as many of these as needed. GDM can also manage displays on which it does not manage a GUI login, thus GDM can be used for supporting X terminals." - -#: C/gdm.xml:326(para) -msgid "Flexible, or on demand displays, are started via the socket protocol with the <command>gdmflexiserver</command> command. This feature is only available to users logged in on the console and will display a new login screen. If a flexible display has previously been started on the console, running <command>gdmflexiserver</command> again will display a menu allowing users to switch back to a previous session or start a new flexible session. The <command>gdmflexiserver</command> locks the current session before starting a new flexible display, so the user's password must be entered before returning to an existing session. The <command>gdmflexiserver</command> command can also be used to launch nested <command>Xnest</command> display. These are launched in a window in the user's current session. Nested displays can be started even if not logged into the console and are started by running the <command>gdmflexiserver -n</command> command. Flexible displays are not restarted when the user session ends. Flexible displays require virtual terminal (VT) support in the kernel, and will not be available if not supported (such as on Solaris). Nested displays require that the X server supports Xnest." -msgstr "Flexible, or on demand displays, are started via the socket protocol with the <command>gdmflexiserver</command> command. This feature is only available to users logged in on the console and will display a new login screen. If a flexible display has previously been started on the console, running <command>gdmflexiserver</command> again will display a menu allowing users to switch back to a previous session or start a new flexible session. The <command>gdmflexiserver</command> locks the current session before starting a new flexible display, so the user's password must be entered before returning to an existing session. The <command>gdmflexiserver</command> command can also be used to launch nested <command>Xnest</command> display. These are launched in a window in the user's current session. Nested displays can be started even if not logged into the console and are started by running the <command>gdmflexiserver -n</command> command. Flexible displays are not restarted when the user session ends. Flexible displays require virtual terminal (VT) support in the kernel, and will not be available if not supported (such as on Solaris). Nested displays require that the X server supports Xnest." - -#: C/gdm.xml:347(para) -msgid "The last display type is the XDMCP remote displays which are described in the next section. Remote hosts can connect to GDM and present the login screen if this is enabled. Some things are different for remote sessions. For example, the Actions menu which allows you to shut down, restart, suspend, or configure GDM are not shown." -msgstr "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." - -#: C/gdm.xml:355(para) -msgid "Displays started via the <command>gdmdynamic</command> command are treated as local displays, so they are restarted automatically on when the session exits. This command is intended to more effectively manage the displays on a multi-user server (many displays connected to a single server)." -msgstr "Displays started via the <command>gdmdynamic</command> command are treated as local displays, so they are restarted automatically on when the session exits. This command is intended to more effectively manage the displays on a multi-user server (many displays connected to a single server)." - -#: C/gdm.xml:365(title) -msgid "XDMCP" -msgstr "XDMCP" - -#: C/gdm.xml:369(para) -msgid "The GDM daemon can be configured to listen for and manage X Display Manage Protocol (XDMCP) requests from remote displays. By default XDMCP support is turned off, but can be enabled if desired. If GDM is built with TCP Wrapper support, then the daemon will only grant access to hosts specified in the GDM service section in the TCP Wrappers configuration file." -msgstr "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." - -#: C/gdm.xml:378(para) -msgid "GDM includes several measures making it more resistant to denial of service attacks on the XDMCP service. A lot of the protocol parameters, handshaking timeouts etc. can be fine tuned. The defaults should work for most systems, however. Do not change them unless you know what you are doing." -msgstr "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." - -#: C/gdm.xml:386(para) -msgid "GDM listens to UDP port 177 and will respond to QUERY and BROADCAST_QUERY requests by sending a WILLING packet to the originator." -msgstr "GDM listens to UDP port 177 and will respond to QUERY and BROADCAST_QUERY requests by sending a WILLING packet to the originator." - -#: C/gdm.xml:391(para) -msgid "GDM can also be configured to honor INDIRECT queries and present a host chooser to the remote display. GDM will remember the user's choice and forward subsequent requests to the chosen manager. GDM also supports an extension to the protocol which will make it forget the redirection once the user's connection succeeds. This extension is only supported if both daemons are GDM. It is transparent and will be ignored by XDM or other daemons that implement XDMCP." -msgstr "GDM can also be configured to honour 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." - -#: C/gdm.xml:401(para) -msgid "Refer to the \"Security\" section for information about security concerns when using XDMCP." -msgstr "Refer to the \"Security\" section for information about security concerns when using XDMCP." - -#: C/gdm.xml:408(title) -msgid "Securing Remote Connection Through SSH" -msgstr "Securing Remote Connection Through SSH" - -#: C/gdm.xml:411(para) -msgid "As explained in the \"Security\" section, XDMCP does not use any kind of encryption and as such is inherently insecure. As XDMCP uses UDP as a network transport layer, it is not possible to simply secure it through an SSH tunnel." -msgstr "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." - -#: C/gdm.xml:418(para) -msgid "To remedy this problem, gdm can be configured at compilation-time with the option --enable-secureremote, in which case gdm proposes as a built-in session a session called \"Secure Remote Connection\". Starting such a session allows the user to enter the name or the address of the host on which to connect; provided the said host runs an SSH server, the user then gets connected to the server on which the default X session is started and displayed on the local host." -msgstr "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 is then connected to the server on which the default X session is started and displayed on the local host." - -#: C/gdm.xml:428(para) -msgid "Using this session allows a much more secure network connection and only necessitates to have an SSH server running on the remote host." -msgstr "Using this session allows a much more secure network connection and only necessitates to have an SSH server running on the remote host." - -#: C/gdm.xml:435(title) -msgid "The GTK+ Greeter" -msgstr "The GTK+ Greeter" - -#: C/gdm.xml:437(para) -msgid "The GTK+ Greeter is the default graphical user interface that is presented to the user. The greeter contains a menu at the top, an optional face browser, an optional logo and a text entry widget. This greeter has full accessibility support, and should be used by users with accessibility needs." -msgstr "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." - -#: C/gdm.xml:445(para) -msgid "The text entry field is used for entering logins, passwords, passphrases etc. <command>gdmlogin</command> 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 "The text entry field is used for entering logins, passwords, passphrases etc. <command>gdmlogin</command> 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." - -#: C/gdm.xml:455(para) -msgid "The menu bar in the top of the greeter enables the user to select the requested session type/desktop environment, select an appropriate locale/language, halt/restart/suspend the computer, configure GDM (given the user knows the root password), change the GTK+ theme, or start an XDMCP chooser." -msgstr "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." - -#: C/gdm.xml:463(para) -msgid "The greeter can optionally display a logo in the login window. The image must be in a format readable to the gdk-pixbuf library (GIF, JPG, PNG, TIFF, XPM and possibly others), and it must be readable to the GDM user. See the <filename>Logo</filename> option in the reference section below for details." -msgstr "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 <filename>Logo</filename> option in the reference section below for details." - -#: C/gdm.xml:473(title) -msgid "The Themed Greeter" -msgstr "The Themed Greeter" - -#: C/gdm.xml:475(para) -msgid "The Themed Greeter is a greeter interface that takes up the whole screen and is very themable. Themes can be selected and new themes can be installed by the configuration application or by setting the <filename>GraphicalTheme</filename> 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 "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 <filename>GraphicalTheme</filename> 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." - -#: C/gdm.xml:485(para) -msgid "The look and feel of this greeter is really controlled by the theme and so the user interface elements that are present may be different. The only thing that must always be present is the text entry field as described above in the GTK+ Greeter. The theme can include buttons that allow the user to select an appropriate locale/language, halt/restart/suspend the computer, configure GDM (given the user knows the root password), or start an XDMCP chooser." -msgstr "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." - -#: C/gdm.xml:495(para) -msgid "You can always get a menu of available actions by pressing the F10 key. This can be useful if the theme doesn't provide certain buttons when you wish to do some action allowed by the GDM configuration." -msgstr "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." - -#: C/gdm.xml:503(title) -msgid "The GDM Face Browser" -msgstr "The GDM Face Browser" - -#: C/gdm.xml:505(para) -msgid "GDM supports a face browser which will display a list of users who can login and an icon for each user. This feature can be used with the GTK+ Greeter if the <filename>Browser</filename> configuration option is set to \"true\". This feature can be used with the Themed Greeter if using a GDM theme which includes a \"userlist\" item type is defined, such as \"happygnome-list\"" -msgstr "GDM supports a face browser which will display a list of users who can login and an icon for each user. This feature can be used with the GTK+ Greeter if the <filename>Browser</filename> configuration option is set to \"true\". This feature can be used with the Themed Greeter if using a GDM theme which includes a \"userlist\" item type is defined, such as \"happygnome-list\"" - -#: C/gdm.xml:515(para) -msgid "By default, the face browser is disabled since revealing usernames on the login screen is not appropriate on many systems for security reasons. Also GDM requires some setup to specify which users should be visible. Setup can be done on the \"Users\" tab in <command>gdmsetup</command>. This feature is most practical to use on a system with a smaller number of users." -msgstr "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 <command>gdmsetup</command>. This feature is most practical to use on a system with a smaller number of users." - -#: C/gdm.xml:524(para) -msgid "The icons used by GDM can be installed globally by the sysadmin or can be located in the users' home directories. If installed globally they should be in the <filename><share>/pixmaps/faces/</filename> directory (though this can be configured with the <filename>GlobalFaceDir</filename> configuration option) and the filename should be the name of the user, optionally with a <filename>.png</filename> 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 "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 <filename><share>/pixmaps/faces/</filename> directory (though this can be configured with the <filename>GlobalFaceDir</filename> configuration option) and the filename should be the name of the user, optionally with a <filename>.png</filename> 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." - -#: C/gdm.xml:537(para) -msgid "Users may run the <command>gdmphotosetup</command> command to configure the image to use for their userid. This program properly scales the file down if it is larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> configuration options and places the icon in a file called <filename>~/.face</filename>. Although <command>gdmphotosetup</command> scales user images automatically, this does not guarantee that user images are properly scaled since a user may create their <filename>~/.face</filename> file by hand." -msgstr "Users may run the <command>gdmphotosetup</command> command to configure the image to use for their userid. This program properly scales the file down if it is larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> configuration options and places the icon in a file called <filename>~/.face</filename>. Although <command>gdmphotosetup</command> scales user images automatically, this does not guarantee that user images are properly scaled since a user may create their <filename>~/.face</filename> file by hand." - -#: C/gdm.xml:549(para) -msgid "GDM will first look for the user's face image in <filename>~/.face</filename>. If not found, it will try <filename>~/.face.icon</filename>. If still not found, it will use the value defined for \"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file. Lastly, it will try <filename>~/.gnome2/photo</filename> and <filename>~/.gnome/photo</filename> which are deprecated and supported for backwards compatibility." -msgstr "GDM will first look for the user's face image in <filename>~/.face</filename>. If not found, it will try <filename>~/.face.icon</filename>. If still not found, it will use the value defined for \"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file. Lastly, it will try <filename>~/.gnome2/photo</filename> and <filename>~/.gnome/photo</filename> which are deprecated and supported for backwards compatibility." - -#: C/gdm.xml:560(para) -msgid "If a user has no defined face image, GDM will use the \"stock_person\" icon defined in the current GTK+ theme. If no such image is defined, it will fallback to the image specified in the <filename>DefaultFace</filename> configuration option, normally <filename><share>/pixmaps/nobody.png</filename>." -msgstr "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 <filename>DefaultFace</filename> configuration option, normally <filename><share>/pixmaps/nobody.png</filename>." - -#: C/gdm.xml:568(para) -msgid "Please note that loading and scaling face icons located in user home directories can be a very time-consuming task. Since it not practical to load images over NIS or NFS, GDM does not attempt to load face images from remote home directories. Furthermore, GDM will give up loading face images after 5 seconds of activity and will only display the users whose pictures it has gotten so far. The <filename>Include</filename> 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 <filename>GlobalFaceDir</filename> configuration option." -msgstr "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 <filename>Include</filename> 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 <filename>GlobalFaceDir</filename> configuration option." - -#: C/gdm.xml:584(para) -msgid "To control the users who get displayed in the face browser, there are a number of configuration options that can be used. If the <filename>IncludeAll</filename> option is set to true, then the password file will be scanned and all users will be displayed. If <filename>IncludeAll</filename> option is set to false, then the <filename>Include</filename> option should contain a list of users separated by commas. Only the users specified will be displayed. Any user listed in the <filename>Exclude</filename> option and users whose UID's is lower than <filename>MinimalUID</filename> will be filtered out regardless of the <filename>IncludeAll</filename> setting. <filename>IncludeAll</filename> 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 "To control the users who get displayed in the face browser, there are a number of configuration options that can be used. If the <filename>IncludeAll</filename> option is set to true, then the password file will be scanned and all users will be displayed. If <filename>IncludeAll</filename> option is set to false, then the <filename>Include</filename> option should contain a list of users separated by commas. Only the users specified will be displayed. Any user listed in the <filename>Exclude</filename> option and users whose UID's is lower than <filename>MinimalUID</filename> will be filtered out regardless of the <filename>IncludeAll</filename> setting. <filename>IncludeAll</filename> 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.." - -#: C/gdm.xml:601(para) -msgid "When the browser is turned on, valid usernames on the computer are inherently exposed to a potential intruder. This may be a bad idea if you do not know who can get to a login screen. This is especially true if you run XDMCP (turned off by default)." -msgstr "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)." - -#: C/gdm.xml:610(title) -msgid "Logging" -msgstr "Logging" - -#: C/gdm.xml:612(para) -msgid "GDM itself will use syslog to log errors or status. It can also log debugging information, which can be useful for tracking down problems if GDM is not working properly. This can be enabled in the configuration file." -msgstr "GDM 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." - -#: C/gdm.xml:619(para) -msgid "Output from the various X servers is stored in the GDM log directory, which is configurable, but is usually <filename><var>/log/gdm/</filename>. The output from the session can be found in a file called <filename><display>.log</filename>. Four older files are also stored with <filename>.1</filename> through <filename>.4</filename> 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 "Output from the various X servers is stored in the GDM log directory, which is configurable, but is usually <filename><var>/log/gdm/</filename>. The output from the session can be found in a file called <filename><display>.log</filename>. Four older files are also stored with <filename>.1</filename> through <filename>.4</filename> 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." - -#: C/gdm.xml:631(para) -msgid "The output from the user session is redirected to <filename>~/.xsession-errors</filename> before even the <filename>PreSession</filename> 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 "The output from the user session is redirected to <filename>~/.xsession-errors</filename> before even the <filename>PreSession</filename> 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 dialogue 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." - -#: C/gdm.xml:643(para) -msgid "You can suppress the 10 second warning by returning code 66 from the <filename>Xsession</filename>script or from your session binary (the default <filename>Xsession</filename> 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 "You can suppress the 10 second warning by returning code 66 from the <filename>Xsession</filename>script or from your session binary (the default <filename>Xsession</filename> 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." - -#: C/gdm.xml:653(para) -msgid "The session output is piped through the GDM daemon and so the <filename>~/.xsession-errors</filename> file is capped at about 200 kilobytes by GDM to prevent a possible denial of service attack on the session. An app could perhaps on reading some wrong data print out warnings or errors on the stderr or stdout. This could perhaps fill up the user's home directory who would then have to log out and log back in to clear this. This could be especially nasty if quotas are set. GDM also correctly traps the XFSZ signal and stops writing the file, which would lead to killed sessions if the file was redirected in the old fashioned way from the script." -msgstr "The session output is piped through the GDM daemon and so the <filename>~/.xsession-errors</filename> file is capped at about 200 kilobytes by GDM to prevent a possible denial of service attack on the session. An app could, perhaps on reading some wrong data, print out warnings or errors on stderr or stdout. This could fill up the user's home directory, who would then have to log out and log back in to clear this. This could be especially nasty if quotas are set. GDM also correctly traps the XFSZ signal and stops writing the file, which would lead to killed sessions if the file was redirected in the old fashioned way from the script." - -#: C/gdm.xml:666(para) -msgid "Note that some distributors seem to override the <filename>~/.xsession-errors</filename> redirection and do it themselves in their own Xsession script (set by the <filename>BaseXsession</filename> configuration key) which means that GDM will not be able to trap the output and cap this file. You also lose output from the <filename>PreSession</filename> 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 <filename>BaseXsession</filename> configuration key for more information, especially on how to handle multiple display managers using the same script." -msgstr "Note that some distributors seem to override the <filename>~/.xsession-errors</filename> redirection and do it themselves in their own Xsession script (set by the <filename>BaseXsession</filename> configuration key) which means that GDM will not be able to trap the output and cap this file. You also lose output from the <filename>PreSession</filename> 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 <filename>BaseXsession</filename> configuration key for more information, especially on how to handle multiple display managers using the same script." - -#: C/gdm.xml:680(para) -msgid "Note that if the session is a failsafe session, or if GDM can't open this file for some reason, then a fallback file will be created in the <filename>/tmp</filename> directory named <filename>/tmp/xses-<user>.XXXXXX</filename> where the <filename>XXXXXX</filename> are some random characters." -msgstr "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 <filename>/tmp</filename> directory named <filename>/tmp/xses-<user>.XXXXXX</filename> where the <filename>XXXXXX</filename> are some random characters." - -#: C/gdm.xml:688(para) -msgid "If you run a system with quotas set, it would be good to delete the <filename>~/.xsession-errors</filename> in the <filename>PostSession</filename> script. Such that this log file doesn't unnecessarily stay around." -msgstr "If you run a system with quotas set, it would be a good idea to delete the <filename>~/.xsession-errors</filename> in the <filename>PostSession</filename> script. So that this log file doesn't take up unnecessarily disk space." - -#: C/gdm.xml:697(title) -msgid "Accessing Files" -msgstr "Accessing Files" - -#: C/gdm.xml:699(para) -msgid "In general GDM is very reluctant regarding reading/writing of user files (such as the <filename>~/.dmrc</filename>, <filename>~/.face</filename>, <filename>~/.xsession-errors</filename>, and <filename>~/.Xauthority</filename> files). For instance it refuses to access anything but regular files. Links, sockets and devices are ignored. The value of the <filename>RelaxPermissions</filename> parameter determines whether GDM should accept files writable by the user's group or others. These are ignored by default." -msgstr "In general GDM is very reluctant regarding reading/writing of user files (such as the <filename>~/.dmrc</filename>, <filename>~/.face</filename>, <filename>~/.xsession-errors</filename>, and <filename>~/.Xauthority</filename> files). For instance it refuses to access anything but regular files. Links, sockets and devices are ignored. The value of the <filename>RelaxPermissions</filename> parameter determines whether GDM should accept files writable by the user's group or others. These are ignored by default." - -#: C/gdm.xml:711(para) -msgid "All operations on user files are done with the effective user id of the user. If the sanity check fails on the user's <filename>.Xauthority</filename> file, a fallback cookie is created in the directory specified by the <filename>UserAuthFBDir</filename> configuration setting (<filename>/tmp</filename> by default)." -msgstr "All operations on user files are done with the effective user id of the user. If the sanity check fails on the user's <filename>.Xauthority</filename> file, a fallback cookie is created in the directory specified by the <filename>UserAuthFBDir</filename> configuration setting (<filename>/tmp</filename> by default)." - -#: C/gdm.xml:719(para) -msgid "Finally, the sysadmin can specify the maximum file size GDM should accept, and, if the face browser is enabled, a tunable maximum icon size is also enforced. On large systems it is still advised to turn off the face browser for performance reasons. Looking up icons in home directories, scaling and rendering face icons can take a long time." -msgstr "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." - -#: C/gdm.xml:730(title) -msgid "GDM Performance" -msgstr "GDM Performance" - -#: C/gdm.xml:732(para) -msgid "To speed performance it is possible to build GDM so that it will preload libraries when GDM first displays a greeter program. This has been shown to speed first time login since these libraries can be loaded into memory while the user types in their username and password." -msgstr "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." - -#: C/gdm.xml:740(para) -msgid "To use this feature, configure GDM with the <command>--with-prefetch</command> option. This will cause GDM to install the <command>gdmprefetch</command> program to the <filename>libexecdir</filename> directory, install the <filename>gdmprefetchlist</filename> to the <filename><etc>/gdm</filename> directory, and set the <filename>PreFetchProgram</filename> configuration variable so that the <command>gdmprefetch</command> program is called with the default <filename>gdmprefetchlist</filename> file. The default <filename>gdmprefetchlist</filename> 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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>, so that they can be included in future GDM releases." -msgstr "To use this feature, configure GDM with the <command>--with-prefetch</command> option. This will cause GDM to install the <command>gdmprefetch</command> program to the <filename>libexecdir</filename> directory, install the <filename>gdmprefetchlist</filename> to the <filename><etc>/gdm</filename> directory, and set the <filename>PreFetchProgram</filename> configuration variable so that the <command>gdmprefetch</command> program is called with the default <filename>gdmprefetchlist</filename> file. The default <filename>gdmprefetchlist</filename> file was optimised 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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>, so that they can be included in future GDM releases." - -#: C/gdm.xml:761(title) -msgid "Security" -msgstr "Security" - -#: C/gdm.xml:764(title) -msgid "PAM" -msgstr "PAM" - -#: C/gdm.xml:768(para) -msgid "GDM uses PAM for login authentication, though if your machine does not support PAM you can build GDM to work with the password database and the crypt library function." -msgstr "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." - -#: C/gdm.xml:774(para) -msgid "PAM stands for Pluggable Authentication Module, and is used by most programs that request authentication on your computer. It allows the administrator to configure different authentication behavior for different programs." -msgstr "PAM stands for Pluggable Authentication Modules, and is used by most programs that request authentication on your computer. It allows the administrator to configure different authentication behaviours for different programs." - -#: C/gdm.xml:781(para) -msgid "Some GDM features (like turning on automatic login) may require that you update your PAM configuration. PAM configuration has different, but similar, interfaces on different operating systems, so check your pam.d or pam.conf man page for details. Be sure that you read the PAM documentation (e.g. pam.d/pam.conf man page) and are comfortable with the security implications of any changes you intend to make to your configuration." -msgstr "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." - -#: C/gdm.xml:791(para) -msgid "If there is no entry for GDM in your system's PAM configuration file, then features like automatic login may not work. Not having an entry will cause GDM to use default behavior, conservative settings are recommended and probably shipped with your distribution." -msgstr "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." - -#: C/gdm.xml:798(para) -msgid "If you wish to make GDM work with other types of authentication mechanisms (such as a SmartCard), then you should implement this by using a PAM service module for the desired authentication type rather than by trying to modify the GDM code directly. Refer to the PAM documentation on your system. This issue has been discussed on the <address><email>gdm-list@gnome.org</email></address> mail list, so you can refer to the list archives for more information." -msgstr "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 <address><email>gdm-list@gnome.org</email></address> mail list, so you can refer to the list archives for more information." - -#: C/gdm.xml:810(title) -msgid "The GDM User" -msgstr "The GDM User" - -#: C/gdm.xml:812(para) -msgid "For security reasons a dedicated user and group id are required for proper operation! The need to be able to write Xauth files is why user \"nobody\" is not appropriate for gdm." -msgstr "For security reasons a dedicated user and group id are required for proper operation. The user \"nobody\" is not appropiate for gdm as the user needs to be able to write Xauth files." - -#: C/gdm.xml:818(para) -msgid "The GDM daemon normally runs as root, as does the slave. However GDM should also have a dedicated user id and a group id which it uses for its graphical interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</command>. These are configured via the <filename>User</filename> and <filename>Group</filename> configuration options in the GDM configuration files. The user and group should be created before running \"make install\". By default GDM assumes the user and the group are called \"gdm\"." -msgstr "The GDM daemon normally runs as root, as does the slave. However GDM should also have a dedicated user id and a group id which it uses for its graphical interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</command>. These are configured via the <filename>User</filename> and <filename>Group</filename> configuration options in the GDM configuration files. The user and group should be created before running \"make install\". By default GDM assumes the user and the group are called \"gdm\"." - -#: C/gdm.xml:829(para) -msgid "This userid is used to run the GDM GUI programs required for login. All functionality that requires root authority is done by the GDM daemon process. This design ensures that if the GUI programs are somehow exploited, only the dedicated user privileges are available." -msgstr "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." - -#: C/gdm.xml:836(para) -msgid "It should however be noted that the GDM user and group have some privileges that make them somewhat dangerous. For one, they have access to the X server authorization directory. It must be able to read and write Xauth keys to <filename><var>/lib/gdm</filename>. 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 "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 authorisation directory. It must be able to read and write Xauth keys to <filename><var>/lib/gdm</filename>. 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." - -#: C/gdm.xml:847(para) -msgid "The danger is that someone who gains the GDM user/group privileges can then connect to any session. So you should not, under any circumstances, make this some user/group which may be easy to get access to, such as the user <filename>nobody</filename>. 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 "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 a user/group which may be easily accessed, such as the <filename>nobody</filename> user. Users who gain access to the \"gdm\" user could also modify the Xauth keys causing Denial-Of-Service attacks. 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." - -#: C/gdm.xml:859(para) -msgid "Distributions and system administrators using GDM are expected to setup the dedicated user properly. It is recommended that this userid be configured to disallow login and to not have a default shell. Distributions and system administrators should set up the filesystem to ensure that the GDM user does not have read or write access to sensitive files." -msgstr "Distributions and system administrators using GDM are expected to set up the dedicated user properly. It is recommended that this userid be configured to not have a default shell or be allowed to login. 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." - -#: C/gdm.xml:870(title) -msgid "X Server Authentication Scheme" -msgstr "X Server Authentication Scheme" - -#: C/gdm.xml:872(para) -msgid "The X server authorization directory (the <filename>ServAuthDir</filename>) 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 <filename>root.gdm</filename> 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 "The X server authorisation directory (the <filename>ServAuthDir</filename>) is used, for legacy reasons, for a host of random internal data in addition to the X server authorisation files. GDM daemon enforces this directory to be owned by <filename>root:gdm</filename> 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 authorisation files." - -#: C/gdm.xml:884(para) -msgid "GDM by default doesn't trust the X server authorization directory and treats it in the same way as the temporary directory with respect to creating files. This way someone breaking the GDM user cannot mount attacks by creating links in this directory. Similarly the X server log directory is treated safely, but that directory should really be owned and writable only by root." -msgstr "GDM, by default, doesn't trust the X server authorisation directory and treats it in the same way as the temporary directory with respect to creating files. This way the daemon cannot be attacked by creating links in this directory. Similarly the X server log directory is treated safely, but that directory should be owned and writable only by root." - -#: C/gdm.xml:893(para) -msgid "GDM only supports the MIT-MAGIC-COOKIE-1 X server authentication scheme. Normally little is gained from the other schemes, and no effort has been made to implement them so far. Be especially careful about using XDMCP because the X server authentication cookie goes over the wire as clear text. If snooping is possible, then an attacker could simply snoop your authentication password as you log in, regardless of the authentication scheme being used. If snooping is possible and undesirable, then you should use ssh for tunneling an X connection rather then using XDMCP. You could think of XDMCP as a sort of graphical telnet, having the same security issues." -msgstr "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 in clear text. If snooping is possible, then an attacker could simply snoop your authentication cookie 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." - -#: C/gdm.xml:906(para) -msgid "On the upside, GDM's random number generation is very conservative and GDM goes to extraordinary measures to truly get a 128 bit random number, using hardware random number generators (if available), plus the current time (in microsecond precision), a 20 byte array of pseudorandom numbers, process pid's, and other random information (possibly using <filename>/dev/audio</filename> or <filename>/dev/mem</filename> 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 <filename>UserAuthDir</filename> configuration key). So be careful about where you use remote X display." -msgstr "On the upside, GDM's random number generation is very conservative and GDM goes to extraordinary measures to get get a truly random 128 bit number, using hardware random number generators (if available), the current time (in microseconds), a 20 byte array of pseudo-random numbers, process pids and other random information (possibly using <filename>/dev/audio</filename> or <filename>/dev/mem</filename> if hardware random generators are not available) to create a large buffer and then runs an 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 the <filename>UserAuthDir</filename> configuration key). So be careful about where you use remote X display." - -#: C/gdm.xml:923(title) -msgid "Firewall Security" -msgstr "Firewall Security" - -#: C/gdm.xml:925(para) -msgid "Even though GDM tries to outsmart potential attackers trying to take advantage of XDMCP, it is still advised that you block the XDMCP port (normally UDP port 177) on your firewall unless you really need it. GDM guards against DoS (Denial of Service) attacks, but the X protocol is still inherently insecure and should only be used in controlled environments. Also each remote connection takes up lots of resources, so it is much easier to DoS via XDMCP then a webserver." -msgstr "Even though GDM tries to outsmart potential attackers trying to take advantage of XDMCP, it is advised that you block the XDMCP port (normally UDP port 177) on your firewall. GDM guards against DoS (Denial of Service) attacks, but the X protocol is still inherently insecure and should only be used in controlled environments. This risk is increased as each remote connection takes up lots of resources, making it much easier to perform a DoS via XDMCP." - -#: C/gdm.xml:935(para) -msgid "It is also wise to block all of the X Server ports. These are TCP ports 6000 + the display number of course) on your firewall. Note that GDM will use display numbers 20 and higher for flexible on-demand servers." -msgstr "It is also wise to block all of the X Server ports. These are the TCP ports 6000 + the display number of course. Note that GDM will use display numbers 20 and higher for flexible on-demand servers." - -#: C/gdm.xml:942(para) -msgid "X is not a very safe protocol for leaving on the net, and XDMCP is even less safe." -msgstr "Both X and XDMCP are not safe protocols for public access." - -#: C/gdm.xml:949(title) -msgid "GDM Security With NFS" -msgstr "GDM Security With NFS" - -#: C/gdm.xml:951(para) -msgid "Note that NFS traffic really goes \"over the wire\" and thus can be snooped. When accessing the user's X authorization file (<filename>~/.Xauthority</filename>), 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 <filename>UserAuthFBDir</filename>, which by default is set to <filename>/tmp</filename>. This behavior can be changed by setting the <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false." -msgstr "Note that NFS traffic really goes \"over the wire\" and can be snooped. When accessing the user's X authorisation file (<filename>~/.Xauthority</filename>), 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 <filename>UserAuthFBDir</filename>, which by default is set to <filename>/tmp</filename>. This behaviour can be changed by setting the <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false." - -#: C/gdm.xml:965(title) -msgid "XDMCP Security" -msgstr "XDMCP Security" - -#: C/gdm.xml:967(para) -msgid "Even though your display is protected by cookies, XEvents and thus keystrokes typed when entering passwords will still go over the wire in clear text. It is trivial to capture these." -msgstr "Even though your display is protected by cookies, XEvents and keystrokes typed when entering passwords will still go over the network in clear text. It is trivial to capture these." - -#: C/gdm.xml:973(para) -msgid "XDMCP is primarily useful for running thin clients such as in terminal labs. Those thin clients will only ever need the network to access the server, and so it seems like the best security policy to have those thin clients on a separate network that cannot be accessed by the outside world, and can only connect to the server. The only point from which you need to access outside is the server." -msgstr "XDMCP is primarily useful for running thin clients, such as in terminal labs. These thin clients will only ever need the network to access the server, 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." - -#: C/gdm.xml:982(para) -msgid "The above sections \"X Server Authentication Scheme\" and \"Firewall Security\" also contain important information about using XDMCP securely. The next section also discusses how to set up XDMCP access control." -msgstr "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." - -#: C/gdm.xml:989(para) -msgid "To workaround the inherent insecurity of XDMCP, gdm proposes a default built-in session that uses SSH to encrypt the remote connection. See the section \"Securing remote connection through SSH\" above." -msgstr "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." - -#: C/gdm.xml:997(title) -msgid "XDMCP Access Control" -msgstr "XDMCP Access Control" - -#: C/gdm.xml:999(para) -msgid "XDMCP access control is done using TCP wrappers. It is possible to compile GDM without TCP wrappers however, so you should test your configuration and verify that they work." -msgstr "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." - -#: C/gdm.xml:1005(para) -msgid "You should use the daemon name <command>gdm</command> in the <filename><etc>/hosts.allow</filename> and <filename><etc>/hosts.deny</filename> files. For example to deny computers from <filename>.evil.domain</filename> from logging in, then add" -msgstr "You should use the daemon name <command>gdm</command> in the <filename><etc>/hosts.allow</filename> and <filename><etc>/hosts.deny</filename> files. For example, to deny computers from <filename>.evil.domain</filename> from logging in, then add" - -#: C/gdm.xml:1012(screen) -#, no-wrap -msgid "" -"\n" -"gdm: .evil.domain\n" -msgstr "" -"\n" -"gdm: .evil.domain\n" - -#: C/gdm.xml:1015(para) -msgid "to <filename><etc>/hosts.deny</filename>. You may also need to add" -msgstr "to <filename><etc>/hosts.deny</filename>. You may also need to add" - -#: C/gdm.xml:1019(screen) -#, no-wrap -msgid "" -"\n" -"gdm: .your.domain\n" -msgstr "" -"\n" -"gdm: .your.domain\n" - -#: C/gdm.xml:1022(para) -msgid "to your <filename><etc>/hosts.allow</filename> if you normally disallow all services from all hosts. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "to your <filename><etc>/hosts.allow</filename> if you normally disallow all services from all hosts. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details." - -#: C/gdm.xml:1032(title) -msgid "Support for ConsoleKit" -msgstr "Support for ConsoleKit" - -#: C/gdm.xml:1034(para) -msgid "GDM includes support for publishing user login information with the user and login session accounting framework known as ConsoleKit. ConsoleKit is able to keep track of all the users currently logged in. In this respect, it can be used as a replacement for the utmp or utmpx files that are available on most Unix-like operating systems." -msgstr "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." - -#: C/gdm.xml:1041(para) -msgid "When GDM is about to create a new login process for a user it will call a privileged method of ConsoleKit in order to open a new session for this user. At this time GDM also provides ConsoleKit with information about this user session such as: the user ID, the X11 Display name that will be associated with the session, the host-name from which the session originates (useful in the case of an XDMCP session), whether or not this session is local, etc. As the entity that initiates the user process, GDM is in a unique position know and to be trusted to provide these bits of information about the user session. The use of this privileged method is restricted by the use of D-Bus system message bus security policy." -msgstr "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." - -#: C/gdm.xml:1052(para) -msgid "In the case where a user with an existing session and has authenticated at GDM and requests to resume that existing session GDM calls a privileged method of ConsoleKit to unlock that session. The exact details of what happens when the session receives this unlock signal is undefined and session-specific. However, most sessions will unlock a screensaver in response." -msgstr "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." - -#: C/gdm.xml:1059(para) -msgid "When the user chooses to log out, or if GDM or the session quit unexpectedly the user session will be unregistered from ConsoleKit." -msgstr "When the user chooses to log out, or if GDM or the session quit unexpectedly the user session will be unregistered from ConsoleKit." - -#: C/gdm.xml:1064(para) -msgid "If support for ConsoleKit is not desired it can be disabled at build time using the --with-console-kit=no option when running configure." -msgstr "If support for ConsoleKit is not desired it can be disabled at build time using the --with-console-kit=no option when running configure." - -#: C/gdm.xml:1072(title) -msgid "Using gdmsetup To Configure GDM" -msgstr "Using gdmsetup To Configure GDM" - -#: C/gdm.xml:1074(para) -msgid "The <command>gdmsetup</command> 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 <command>gdmsetup</command>. Editing the files by hand is explained in the \"Configuration\" section of this document. Note that <command>gdmsetup</command> does not support changing of all configuration variables, so it may be necessary to edit the files by hand for some configurations." -msgstr "The <command>gdmsetup</command> application can be used to configure GDM. If you believe running root-owned GUIs causes a security risk, then you would want to always edit the files by hand and not use <command>gdmsetup</command>. Editing the files by hand is explained in the \"Configuration\" section of this document. Note that <command>gdmsetup</command> does not support changing of all configuration variables, so it may be necessary to edit the files by hand for some configurations." - -#: C/gdm.xml:1085(para) -msgid "The <command>gdmsetup</command> program has five tabs: Local, Remote, Accessibility, Security, and Users, described below. In parenthesis is information about which GDM configuration key is affected by each GUI choice. Refer to the \"Configuration\" section of this manual and the comments in the <share>/gdm/defaults.conf file for additional details about each key." -msgstr "The <command>gdmsetup</command> program has five tabs: Local, Remote, Accessibility, Security, and Users, described below. In parenthesis is information about which GDM configuration key is affected by each GUI choice. Refer to the \"Configuration\" section of this manual and the comments in the <share>/gdm/defaults.conf file for additional details about each key." - -#: C/gdm.xml:1095(title) -msgid "Local Tab" -msgstr "Local Tab" - -#: C/gdm.xml:1097(para) -msgid "The Local tab is used for controlling the appearance of GDM for local/static displays (non-XDMCP remote connections). The choices available in this tab depend on the setting of the \"Style\" combobox. This combobox is used to determine whether the \"Plain\" or \"Themed\" greeter GUI is used. The differences between these greeter programs are explained in the \"Overview\" section of this document." -msgstr "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." - -#: C/gdm.xml:1107(para) -msgid "If the \"Style\" choice is \"Plain\", then GDM will use the <command>gdmlogin</command> program as the GUI (daemon/Greeter). When this choice is selected, <command>gdmsetup</command> 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 "If the \"Style\" choice is \"Plain\", then GDM will use the <command>gdmlogin</command> program as the GUI (daemon/Greeter). When this choice is selected, <command>gdmsetup</command> allows the user to select whether the background is an image or solid colour (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 colour is selected, there is a button available to allow the colour selection (greeter/BackgroundColor). Also, the user may select the logo image that appears in gdmlogin (greeter/Logo)." - -#: C/gdm.xml:1121(para) -msgid "If the \"Style\" choice is \"Plain with face browser\", then the <command>gdmlogin</command> 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 "If the \"Style\" choice is \"Plain with face browser\", then the <command>gdmlogin</command> 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." - -#: C/gdm.xml:1131(para) -msgid "If the \"Style\" choice is \"Themed\", then the <command>gdmgreeter</command> program is used as the GUI (daemon/Greeter). When this choice is selected, <command>gdmsetup</command> allows the user to select the theme to be used (greeter/GraphicalTheme). Note that the checkbox to the left of the theme's name must be checked for a theme to be selected. Clicking on the theme, but not selecting the checkbox will highlight the theme and the \"Remove\" button can be used to delete the theme. Information about the theme's author and copyright are shown for the highlighted theme. The \"Add\" button can be used to add new themes to the system. To turn on the Face Browser, a theme which includes a Face Browser must be selected, such as happygnome-list. The \"Background color\" displayed when GDM starts (and if the theme has transparent elements) can also be selected (greeter/GraphicalThemedColor). The \"Theme\" combo box may be set to \"Random from selected\" if you want a random theme to be used for each login (greeter/GraphicalThemeRand and greeter/GraphicalThemes). To use random themes, select each theme that you wish to be used. By default this combobox is set to \"Selected only\", so that only a single theme can be selected and be used." -msgstr "If the \"Style\" choice is \"Themed\", then the <command>gdmgreeter</command> program is used as the GUI (daemon/Greeter). When this choice is selected, <command>gdmsetup</command> allows the user to select the theme to be used (greeter/GraphicalTheme). Note that the checkbox to the left of the theme's name must be checked for a theme to be selected. Clicking on the theme, but not selecting the checkbox will highlight the theme and the \"Remove\" button can be used to delete the theme. Information about the theme's author and copyright are shown for the highlighted theme. The \"Add\" button can be used to add new themes to the system. To turn on the Face Browser, a theme which includes a Face Browser must be selected, such as happygnome-list. The \"Background colocr\" displayed when GDM starts (and if the theme has transparent elements) can also be selected (greeter/GraphicalThemedColor). The \"Theme\" combo box may be set to \"Random from selected\" if you want a random theme to be used for each login (greeter/GraphicalThemeRand and greeter/GraphicalThemes). To use random themes, select each theme that you wish to be used. By default this combobox is set to \"Selected only\", so that only a single theme can be selected and be used." - -#: C/gdm.xml:1155(para) -msgid "Regardless of the \"Style\" choice, the user may also select whether the Actions menu is visible (greeter/SystemMenu), whether the Actions menu includes the choice to start <command>gdmsetup</command> (greeter/ConfigAvailable), and whether the Action menu includes the choice to start <command>gdmchooser</command> to run a remote XDMCP login session (greeter/ChooserButton). Note that the root password must be entered to start <command>gdmsetup</command> 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 "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 <command>gdmsetup</command> (greeter/ConfigAvailable), and whether the Action menu includes the choice to start <command>gdmchooser</command> to run a remote XDMCP login session (greeter/ChooserButton). Note that the root password must be entered to start <command>gdmsetup</command> 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." - -#: C/gdm.xml:1172(title) -msgid "Remote Tab" -msgstr "Remote Tab" - -#: C/gdm.xml:1174(para) -msgid "The Remote tab controls the appearance of the GDM for users logging in via XDMCP. By default XDMCP is disabled, and users should be comfortable with the XDMCP-related sections of the Security section of this document before enabling it. This tab includes a \"Style\" combobox which can be used to turn on XDMCP and control the appearance of GDM for remote users (gui/RemoteGreeter and xdmcp/Enable). This combobox may be set to \"Remote login disabled\" or \"Same as Local\". If the Local tab is set to \"Plain\" or \"Plain with Face Browser\", then the user may also select \"Themed\". If the Local tab is set to \"Themed\", then the user may also select \"Plain\" or \"Plain with face browser\". It is recommended that the \"Plain\" GUI be used for remote connections since it is more lightweight and tends to have better performance across a network." -msgstr "The Remote tab controls the appearance of the GDM for users logging in via XDMCP. By default XDMCP is disabled, and users should be comfortable with the XDMCP-related sections of the Security section of this document before enabling it. This tab includes a \"Style\" combobox which can be used to turn on XDMCP and control the appearance of GDM for remote users (gui/RemoteGreeter and xdmcp/Enable). This combobox may be set to \"Remote login disabled\" or \"Same as Local\". If the Local tab is set to \"Plain\" or \"Plain with Face Browser\", then the user may also select \"Themed\". If the Local tab is set to \"Themed\", then the user may also select \"Plain\" or \"Plain with face browser\". It is recommended that the \"Plain\" GUI be used for remote connections since it is more lightweight and tends to have better performance across a network." - -#: C/gdm.xml:1192(para) -msgid "If Remote login is enabled, then the user can specify the remote Welcome Message to be displayed (greeter/DefaultRemoteWelcome and greeter/RemoteWelcome). This welcome message is separate from the Local welcome message and can have a different value. The Welcome message can contain the character sequences described in the \"Text Node\" section of the \"Themed Greeter\" section of this manual." -msgstr "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." - -#: C/gdm.xml:1202(para) -msgid "If the \"Style\" choice is \"Same as Local\" and the local selection is \"Plain\" or \"Plain with face browser\", then the user may select whether background images should be displayed for remote logins (greeter/BackgroundRemoteOnlyColor)." -msgstr "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)." - -#: C/gdm.xml:1210(para) -msgid "If the \"Style\" choice is enabled and set to a different value than the Local tab, then the user has the same configuration choices as found on the Local tab except that the System Menu choices are not available since this is never available for remote logins for security purposes." -msgstr "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." - -#: C/gdm.xml:1218(para) -msgid "If Remote login is enabled, there is a \"Configure XDMCP\" button which displays a dialog allowing the user to set XDMCP configuration, including whether indirect requests are honored (xdmcp/HonorIndirect), UDP port (xdmcp/Port), maximum pending requests (xdmcp/MaxPending), maximum pending indirect requests (xmdcp/MaxPendingIndirect), maximum remote sessions (xdmcp/MaxSessions), maximum wait time (xdmcp/MaxWait), maximum indirect wait time (xdmcp/MaxWaitIndirect), displays per host (xdmcp/DisplaysPerHost), and ping interval (xdmcp/PingIntervalSeconds). The default settings are standard settings and should only be changed by someone who understands the ramifications of the change." -msgstr "If remote login is enabled, there is a \"Configure XDMCP\" button which displays a dialogue allowing the user to set up XDMCP configuration, including whether indirect requests are honoured (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." - -#: C/gdm.xml:1234(title) -msgid "Accessibility Tab" -msgstr "Accessibility Tab" - -#: C/gdm.xml:1236(para) -msgid "The Accessibility tab is used to turn on Accessibility features in GDM. \"Enable accessible login\" (daemon/AddGtkModules and daemon/GtkModulesList) turns on GDM's gesture listeners which are explained in the \"Accessibility\" section of this document. There is also a checkbox to allow users to change the theme when using the Plain greeter (gui/AllowGtkThemeChange). This feature allows GDM users to switch the theme to the HighContrast or LowContrast themes if needed. The user may also select whether GDM should play a sound when the login screen is ready, when login is successful and when login has failed. File chooser buttons are used to select the sound file to be played, and the \"Play\" button can be used to sample the sound." -msgstr "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." - -#: C/gdm.xml:1253(title) -msgid "Security Tab" -msgstr "Security Tab" - -#: C/gdm.xml:1255(para) -msgid "The Security tab allows the user to turn on Automatic and Timed login, which user is logged in via an automatic or timed login, and the timed login delay (daemon/AutomaticLoginEnable, daemon/AutomaticLogin, daemon/TimedLoginEnable, daemon/TimedLogin, and daemon/TimedLoginDelay). If automatic login is turned on, then the specified user will immediately log in on reboot without GDM asking for username/password. If the user logs out of their session, GDM will start and ask for username and password to log back in. If TimedLogin is turned on, then GDM will log in to the specified user after a specified number of seconds. The user may enable Timed Login for remote (XDMCP) connections by checking the \"Allow remote timed logins\" checkbox." -msgstr "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 a username and password. If the user logs out of their session, GDM will start and ask for username and password to log back in. If TimedLogin is turned on, then GDM will log in to the specified user after a specified number of seconds. The user may enable Timed Login for remote (XDMCP) connections by checking the \"Allow remote timed logins\" checkbox." - -#: C/gdm.xml:1270(para) -msgid "On this tab, the user may select whether the system administrator user can log in, and whether the system administrator user can log in via remote (XDMCP) connections (security/AllowRoot and security/AllowRemoteRoot). The user may turn on GDM debug (debug/Enable) which causes debug messages to be sent to the system log. Debug should only be used when diagnosing a problem and not be left on when not needed. The \"Deny TCP connections to Xserver\" choice will disable X forwarding if selected (security/DisallowTCP). A login retry delay (security/RetryDelay) can be set to cause GDM to wait a number of seconds after a failed login." -msgstr "On this tab, the user may select whether the system administrator user can log in, and whether the system administrator user can log in via remote (XDMCP) connections (security/AllowRoot and security/AllowRemoteRoot). The user may turn on GDM debug (debug/Enable) which causes debug messages to be sent to the system log. Debug should only be used when diagnosing a problem and not be left on when not needed. The \"Deny TCP connections to Xserver\" choice will disable X forwarding if selected (security/DisallowTCP). A login retry delay (security/RetryDelay) can be set to cause GDM to wait a number of seconds after a failed login." - -#: C/gdm.xml:1283(para) -msgid "The \"Configure X Server\" button can be used to specify how GDM manages each display. The \"Servers\" combobox shows what server definitions are available (Standard, Terminal, and Chooser by default). Refer to the \"X Server Definitions\" section of the \"Configuration\" section for more information about how to create new Server Definitions." -msgstr "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." - -#: C/gdm.xml:1292(para) -msgid "For any server type, the user may modify the \"Server Name\" (server/name), the \"Command\" (server/command) to be used to launch the Xserver, whether the server type will \"Launch\" (server/chooser) the greeter or chooser GUI after starting the Xserver, whether GDM handles this type (normally only set to false when logging into a Terminal session type), and whether the session type supports \"Flexible\" (server/flexible) sessions." -msgstr "For any server type, the user may modify the \"Server Name\" (server/name), the \"Command\" (server/command) to be used to launch the Xserver, whether the server type will \"Launch\" (server/chooser) the greeter or chooser GUI after starting the Xserver, whether GDM handles this type (normally only set to false when logging into a Terminal session type), and whether the session type supports \"Flexible\" (server/flexible) sessions." - -#: C/gdm.xml:1302(para) -msgid "The \"Servers To Start\" section shows what server type is displayed for each display on the machine. Users may click on the \"Add/Modify\" button to add a new display to the list or to modify a selected display. This simply corresponds each physical display with the Server Definition to be used for managing that display. The \"Remove\" button may be used to remove a display from the list." -msgstr "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." - -#: C/gdm.xml:1314(title) -msgid "Users Tab" -msgstr "Users Tab" - -#: C/gdm.xml:1316(para) -msgid "The Users tab controls which users appear in the Face Browser. If the \"Include all users from /etc/password\" checkbox is selected, then all users (with a userid above greeter/MinimalUID and not in the Exclude list) are displayed. If this checkbox is not selected, then users must be added to the \"Include\" list. Users in the \"Exclude\" list are never displayed. The \"Add\" and \"Remove\" buttons are used to add a new user to the list or remove a selected user from the list. The \"Apply User Changes\" button must be pressed after the \"Include\" and \"Exclude\" lists have been modified. The left and right arrow buttons between the \"Include\" and \"Exclude\" lists can be used to move a selected user from one list to the other." -msgstr "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." - -#: C/gdm.xml:1334(title) -msgid "Configuration" -msgstr "Configuration" - -#: C/gdm.xml:1336(para) -msgid "GDM has powerful configuration management. System configuration is stored in <filename><share>/gdm/defaults.conf</filename> and the intention is that this file can be stored on a shared filesystem so that sysadmins can have a single file to modify to control configuration for multiple machines. Also GDM distributions may patch this file on update to improve usability, improve security, etc. Configuration may be customized for a specific machine by editing the <filename><etc>/gdm/custom.conf</filename> file to include an override for a specific key. Those parameters in the \"gui\", \"greeter\" sections, and the security/PamStack key may be customized per-display by specifying them in a file named <filename><etc>/gdm/custom.conf<display num></filename>. For example, configuration overrides for display \":103\" would be stored in the file <filename><etc>/gdm/custom.conf:0</filename>. Per-display configuration is supported in GDM 2.14.6 and later." -msgstr "GDM has powerful configuration management. System configuration is stored in <filename><share>/gdm/defaults.conf</filename> and the intention is that this file can be stored on a shared filesystem so that sysadmins can have a single file to modify to control configuration for multiple machines. Also GDM distributions may patch this file on update to improve usability, improve security, etc. Configuration may be customised for a specific machine by editing the <filename><etc>/gdm/custom.conf</filename> file to include an override for a specific key. Those parameters in the \"gui\", \"greeter\" sections, and the security/PamStack key may be customised per-display by specifying them in a file named <filename><etc>/gdm/custom.conf<display num></filename>. For example, configuration overrides for display \":103\" would be stored in the file <filename><etc>/gdm/custom.conf:0</filename>. Per-display configuration is supported in GDM 2.14.6 and later." - -#: C/gdm.xml:1354(para) -msgid "The <command>gdmsetup</command> 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 "The <command>gdmsetup</command> 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." - -#: C/gdm.xml:1366(para) -msgid "Distributions should edit the <filename><share>/gdm/defaults.conf</filename> file to establish the default values so these are preserved as defaults and not modified by users modifying their personal configuration file <filename><etc>/gdm/custom.conf</filename>." -msgstr "Distributions should edit the <filename><share>/gdm/defaults.conf</filename> file to establish the default values so these are preserved as defaults and not modified by users modifying their personal configuration file <filename><etc>/gdm/custom.conf</filename>." - -#: C/gdm.xml:1374(para) -msgid "If you want to change configuration by hand, edit the <filename><etc>/gdm/custom.conf</filename> file and make sure the keyname=value pair you want is included in the appropriate section. For example, to change the \"Greeter\" key in the \"daemon\" section, make sure the daemon section of the <filename><etc>/gdm/custom.conf</filename> file has the value like in this example." -msgstr "If you want to change configuration by hand, edit the <filename><etc>/gdm/custom.conf</filename> file and make sure the keyname=value pair you want is included in the appropriate section. For example, to change the \"Greeter\" key in the \"daemon\" section, make sure the daemon section of the <filename><etc>/gdm/custom.conf</filename> file has the value like in this example." - -#: C/gdm.xml:1384(screen) -#, no-wrap -msgid "" -"\n" -"[daemon]\n" -"Greeter=/usr/lib/gdmgreeter\n" -msgstr "" -"\n" -"[daemon]\n" -"Greeter=/usr/lib/gdmgreeter\n" - -#: C/gdm.xml:1389(para) -msgid "The configuration files (especially the <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename> files) contain useful comments and examples, so read them for more information about changing your configuration. GDM considers lines that start with the \"#\" character a comment, and these lines will be ignored by GDM. Some keys in the <filename><share>/gdm/defaults.conf</filename> are commented out while others are set. Commented out values show the default value." -msgstr "The configuration files (especially the <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename> files) contain useful comments and examples, so read them for more information about changing your configuration. GDM considers lines that start with the \"#\" character a comment, and these lines will be ignored by GDM. Some keys in the <filename><share>/gdm/defaults.conf</filename> are commented out while others are set. Commented out values show the default value." - -#: C/gdm.xml:1401(para) -msgid "The <filename><share>/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename><etc>/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename><etc>/gdm/custom.conf</filename> file override the values in the main <filename><share>/gdm/defaults.conf</filename> file. Running the <command>gdmsetup</command> command will cause the <filename><etc>/gdm/custom.conf</filename> to be modified with the user's configuration choices and will cause any running GDM GUI programs to automatically update. Previous to version 2.13.0.4 GDM only supported the <filename><etc>/gdm/gdm.conf</filename> file, so if using an older version of GDM just edit that file directly." -msgstr "The <filename><share>/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename><etc>/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename><etc>/gdm/custom.conf</filename> file override the values in the main <filename><share>/gdm/defaults.conf</filename> file. Running the <command>gdmsetup</command> command will cause the <filename><etc>/gdm/custom.conf</filename> to be modified with the user's configuration choices and will cause any running GDM GUI programs to automatically update. Previous to version 2.13.0.4 GDM only supported the <filename><etc>/gdm/gdm.conf</filename> file, so if using an older version of GDM just edit that file directly." - -#: C/gdm.xml:1417(para) -msgid "The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may also be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used." -msgstr "The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may also be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used." - -#: C/gdm.xml:1426(para) -msgid "<filename><share>/gdm/factory-defaults.conf</filename> is the configuration file as shipped with the daemon. This can be useful for to see if the <filename><share>/gdm/defaults.conf</filename> file has been changed." -msgstr "<filename><share>/gdm/factory-defaults.conf</filename> is the configuration file as shipped with the daemon. This can be useful for to see if the <filename><share>/gdm/defaults.conf</filename> file has been changed." - -#: C/gdm.xml:1433(para) -msgid "The other GDM configuration files are located, by default, in the <filename><etc>/gdm/</filename> folder or its subdirectories. However, the location of all configuration files are defined in the GDM configuration files, so the sysadmin may choose to locate these files in any location." -msgstr "The other GDM configuration files are located, by default, in the <filename><etc>/gdm/</filename> folder or its subdirectories. However, the location of all configuration files are defined in the GDM configuration files, so the sysadmin may choose to locate these files in any location." - -#: C/gdm.xml:1441(para) -msgid "This is a listing of the config directory contents:" -msgstr "This is a listing of the config directory contents:" - -#: C/gdm.xml:1445(screen) -#, no-wrap -msgid "" -"\n" -"locale.alias\n" -"Xsession\n" -"XKeepsCrashing\n" -"modules/\n" -"Init/\n" -"PostLogin/\n" -"PreSession/\n" -"PostSession/\n" -msgstr "" -"\n" -"locale.alias\n" -"Xsession\n" -"XKeepsCrashing\n" -"modules/\n" -"Init/\n" -"PostLogin/\n" -"PreSession/\n" -"PostSession/\n" - -#: C/gdm.xml:1456(para) -msgid "<filename>locale.alias</filename> is a file which looks much like the system locale alias but in fact it is not the same. These are the languages that are available on your system. All the languages are still tested to see if they actually exist before presenting them to the user." -msgstr "<filename>locale.alias</filename> is a file which looks much like the system locale alias but in fact it is not the same. These are the languages that are available on your system. All the languages are still tested to see if they actually exist before presenting them to the user." - -#: C/gdm.xml:1464(para) -msgid "<filename>Xsession</filename> 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 <filename>desktop</filename> file associated with the session the user has picked. Some sessions may start the user's session via a different mechanism than the <filename>Xsession</filename> script, so please check the appropriate <filename>desktop</filename> before assuming a session startup issue is being caused by this file." -msgstr "<filename>Xsession</filename> 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 <filename>desktop</filename> file associated with the session the user has picked. Some sessions may start the user's session via a different mechanism than the <filename>Xsession</filename> script, so please check the appropriate <filename>desktop</filename> before assuming a session startup issue is being caused by this file." - -#: C/gdm.xml:1475(para) -msgid "<filename>XKeepsCrashing</filename> 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 "<filename>XKeepsCrashing</filename> 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." - -#: C/gdm.xml:1483(para) -msgid "Accessibility modules are configured in the <filename>modules/</filename> 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 <filename>factory</filename> in their name, and those files are not read, they are just there for you so you can always revert to default config." -msgstr "Accessibility modules are configured in the <filename>modules/</filename> 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 <filename>factory</filename> in their name, and those files are not read, they are just there for you so you can always revert to default config." - -#: C/gdm.xml:1492(para) -msgid "Files describing available GDM session follow the freedesktop.org desktop file specification and are <filename>.desktop</filename>-style files are installed to <filename><etc>/X11/sessions/</filename>. This directory is also read by the KDE desktop manager (KDM) for common configuration. Next the directory <filename><share>/gdm/BuiltInSessions/</filename> is read for GDM specific built-in sessions (KDM hardcodes these at time of this writing). Lastly the default setup will also read <filename><share>/xsessions/</filename> (which should be <filename><share>/xsessions/</filename> if you really wish to cooperate with KDM) where desktop packages can install their session files. The directories under the <filename><etc></filename> 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 <filename>SessionDesktopDir</filename> configuration key for changing the paths. It used to be that GDM stored its built in sessions in <filename><etc>/dm/Sessions/</filename> but this is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the <filename><etc>/dm/Sessions/</filename> was being read." -msgstr "Files describing available GDM session follow the freedesktop.org desktop file specification and are <filename>.desktop</filename>-style files are installed to <filename><etc>/X11/sessions/</filename>. This directory is also read by the KDE desktop manager (KDM) for common configuration. Next the directory <filename><share>/gdm/BuiltInSessions/</filename> is read for GDM specific built-in sessions (KDM hardcodes these at time of this writing). Lastly the default setup will also read <filename><share>/xsessions/</filename> (which should be <filename><share>/xsessions/</filename> if you really wish to cooperate with KDM) where desktop packages can install their session files. The directories under the <filename><etc></filename> 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 <filename>SessionDesktopDir</filename> configuration key for changing the paths. It used to be that GDM stored its built in sessions in <filename><etc>/dm/Sessions/</filename> but this is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the <filename><etc>/dm/Sessions/</filename> was being read." - -#: C/gdm.xml:1515(para) -msgid "A session can be disabled (if it was installed in <filename><share>/xsessions/</filename>) by adding an identically named <filename>.desktop</filename> to one of the directories earlier in the path (likely <filename><etc>/X11/sessions</filename>) and using <filename>Hidden=true</filename> in that file." -msgstr "A session can be disabled (if it was installed in <filename><share>/xsessions/</filename>) by adding an identically named <filename>.desktop</filename> to one of the directories earlier in the path (likely <filename><etc>/X11/sessions</filename>) and using <filename>Hidden=true</filename> in that file." - -#: C/gdm.xml:1524(title) -msgid "The Script Directories" -msgstr "The Script Directories" - -#: C/gdm.xml:1526(para) -msgid "In this section we will explain the <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> and <filename>PostSession</filename> directories as they are very similar." -msgstr "In this section we will explain the <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> and <filename>PostSession</filename> directories as they are very similar." - -#: C/gdm.xml:1532(para) -msgid "When the X server has been successfully started, GDM will try to run the script called <filename>Init/<displayname></filename>. I.e. <filename>Init/:0</filename> for the first local display. If this file is not found, GDM will attempt to to run <filename>Init/<hostname></filename>. I.e. <filename>Init/somehost</filename>. If this still is not found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins or <filename>Init/Flexi</filename> for all on demand flexible displays. If none of the above were found, GDM will run <filename>Init/Default</filename>. The script will be run as root and GDM blocks until it terminates. Use the <filename>Init/*</filename> 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 "When the X server has been successfully started, GDM will try to run the script called <filename>Init/<displayname></filename>. I.e. <filename>Init/:0</filename> for the first local display. If this file is not found, GDM will attempt to to run <filename>Init/<hostname></filename>. I.e. <filename>Init/somehost</filename>. If this still is not found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins or <filename>Init/Flexi</filename> for all on demand flexible displays. If none of the above were found, GDM will run <filename>Init/Default</filename>. The script will be run as root and GDM blocks until it terminates. Use the <filename>Init/*</filename> 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." - -#: C/gdm.xml:1550(para) -msgid "It is up to the sysadmin to decide whether clients started by the Init script should be killed before starting the user session. This is controlled with the <filename>KillInitClients</filename> configuration option." -msgstr "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 <filename>KillInitClients</filename> configuration option." - -#: C/gdm.xml:1557(para) -msgid "When the user has been successfully authenticated GDM tries the scripts in the <filename>PostLogin</filename> directory in the same manner as for the <filename>Init</filename> 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 <filename>pam_mount</filename> module if you can for this). You have the <filename>$USER</filename> and <filename>$DISPLAY</filename> 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 "When the user has been successfully authenticated GDM tries the scripts in the <filename>PostLogin</filename> directory in the same manner as for the <filename>Init</filename> 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 <filename>pam_mount</filename> module if you can for this). You have the <filename>$USER</filename> and <filename>$DISPLAY</filename> 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." - -#: C/gdm.xml:1571(para) -msgid "After the user session has been setup from the GDM side of things, GDM will run the scripts in the <filename>PreSession</filename> directory, again in the same manner as the <filename>Init</filename> directory. Use this script for local session management or accounting stuff. The <filename>$USER</filename> environment variable contains the login of the authenticated user and <filename>$DISPLAY</filename> 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 <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." -msgstr "After the user session has been setup from the GDM side of things, GDM will run the scripts in the <filename>PreSession</filename> directory, again in the same manner as the <filename>Init</filename> directory. Use this script for local session management or accounting stuff. The <filename>$USER</filename> environment variable contains the login of the authenticated user and <filename>$DISPLAY</filename> 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 <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." - -#: C/gdm.xml:1586(para) -msgid "After this the base <filename>Xsession</filename> 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 <filename>Exec=</filename> line in the <filename>.desktop</filename> files in the path specified by <filename>SessionDesktopDir</filename>. Usually this path is <filename><etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/xsessions/</filename>. The first found file is used. The user either picks from these sessions or GDM will look inside the file <filename>~/.dmrc</filename> for the stored preference." -msgstr "After this the base <filename>Xsession</filename> 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 <filename>Exec=</filename> line in the <filename>.desktop</filename> files in the path specified by <filename>SessionDesktopDir</filename>. Usually this path is <filename><etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/xsessions/</filename>. The first found file is used. The user either picks from these sessions or GDM will look inside the file <filename>~/.dmrc</filename> for the stored preference." - -#: C/gdm.xml:1599(para) -msgid "This script should really load the user's profile and generally do all the voodoo that is needed to launch a session. Since many systems reset the language selections done by GDM, GDM will also set the <filename>$GDM_LANG</filename> 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 <filename>$GDM_LANG</filename> is not set." -msgstr "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 <filename>$GDM_LANG</filename> 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 <filename>$GDM_LANG</filename> is not set." - -#: C/gdm.xml:1609(para) -msgid "When the user terminates his session, the <filename>PostSession</filename> script will be run. Again operation is similar to <filename>Init</filename>, <filename>PostLogin</filename> and <filename>PreSession</filename>. Again the script will be run with root privileges, the slave daemon will block and the <filename>$USER</filename> environment variable will contain the name of the user who just logged out and <filename>$DISPLAY</filename> will be set to the display the user used, however note that the X server for this display may already be dead and so you shouldn't try to access it. Also <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." -msgstr "When the user terminates his session, the <filename>PostSession</filename> script will be run. Again operation is similar to <filename>Init</filename>, <filename>PostLogin</filename> and <filename>PreSession</filename>. Again the script will be run with root privileges, the slave daemon will block and the <filename>$USER</filename> environment variable will contain the name of the user who just logged out and <filename>$DISPLAY</filename> will be set to the display the user used, however note that the X server for this display may already be dead and so you shouldn't try to access it. Also <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." - -#: C/gdm.xml:1624(para) -msgid "Note that the <filename>PostSession</filename> script will be run even when the display fails to respond due to an I/O error or similar. Thus, there is no guarantee that X applications will work during script execution." -msgstr "Note that the <filename>PostSession</filename> script will be run even when the display fails to respond due to an I/O error or similar. Thus, there is no guarantee that X applications will work during script execution." - -#: C/gdm.xml:1631(para) -msgid "Except for the <filename>Xsession</filename> script all of these scripts will also have the environment variable <filename>$RUNNING_UNDER_GDM</filename> set to <filename>yes</filename>, so that you could perhaps use similar scripts for different display managers. The <filename>Xsession</filename> will always have the <filename>$GDMSESSION</filename> set to the basename of the session that the user chose to run without the <filename>.desktop</filename> extension. In addition <filename>$DESKTOP_SESSION</filename> is also set to the same value and in fact this will also be set by KDM in future versions." -msgstr "Except for the <filename>Xsession</filename> script all of these scripts will also have the environment variable <filename>$RUNNING_UNDER_GDM</filename> set to <filename>yes</filename>, so that you could perhaps use similar scripts for different display managers. The <filename>Xsession</filename> will always have the <filename>$GDMSESSION</filename> set to the basename of the session that the user chose to run without the <filename>.desktop</filename> extension. In addition <filename>$DESKTOP_SESSION</filename> is also set to the same value and in fact this will also be set by KDM in future versions." - -#: C/gdm.xml:1645(para) -msgid "Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> or <filename>PostSession</filename> scripts are necessary and can be left out. The <filename>Xsession</filename> script is however required as well as at least one session <filename>.desktop</filename> file." -msgstr "Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> or <filename>PostSession</filename> scripts are necessary and can be left out. The <filename>Xsession</filename> script is however required as well as at least one session <filename>.desktop</filename> file." - -#: C/gdm.xml:1655(title) -msgid "The Configuration Files - <filename>defaults.conf</filename> and <filename>custom.conf</filename>" -msgstr "The Configuration Files - <filename>defaults.conf</filename> and <filename>custom.conf</filename>" - -#: C/gdm.xml:1658(para) -msgid "GDM uses two configuration files: <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename>. The <filename><share>/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename><etc>/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename><etc>/gdm/custom.conf</filename> file override the values in the <filename><share>/gdm/defaults.conf</filename> file. If a configuration option is not defined in either file, GDM will default to the value described in the comments in the <filename><share>/gdm/defaults.conf</filename> file." -msgstr "GDM uses two configuration files: <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename>. The <filename><share>/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename><etc>/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename><etc>/gdm/custom.conf</filename> file override the values in the <filename><share>/gdm/defaults.conf</filename> file. If a configuration option is not defined in either file, GDM will default to the value described in the comments in the <filename><share>/gdm/defaults.conf</filename> file." - -#: C/gdm.xml:1674(para) -msgid "Running the <command>gdmsetup</command> command will cause the <filename><etc>/gdm/custom.conf</filename> to be modified with the user's configuration choices." -msgstr "Running the <command>gdmsetup</command> command will cause the <filename><etc>/gdm/custom.conf</filename> to be modified with the user's configuration choices." - -#: C/gdm.xml:1680(para) -msgid "Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</filename> existed. If upgrading to the new version of GDM, install will check to see if your <filename><etc>/gdm/gdm.conf</filename> file is different than your <filename><etc>/gdm/factory-gdm.conf</filename> file. If so, your <filename><etc>/gdm/gdm.conf</filename> file will be automatically copied to <filename><etc>/gdm/custom.conf</filename> to preserve any configuration changes." -msgstr "Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</filename> existed. If upgrading to the new version of GDM, install will check to see if your <filename><etc>/gdm/gdm.conf</filename> file is different than your <filename><etc>/gdm/factory-gdm.conf</filename> file. If so, your <filename><etc>/gdm/gdm.conf</filename> file will be automatically copied to <filename><etc>/gdm/custom.conf</filename> to preserve any configuration changes." - -#: C/gdm.xml:1692(para) -msgid "The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may instead be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used." -msgstr "The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may instead be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used." - -#: C/gdm.xml:1701(para) -msgid "Both configuration files are divided into sections each containing variables that define the behavior for a specific part of the GDM suite. Refer to the comments in the <filename><share>/gdm/defaults.conf</filename> file for additional information about each configuration setting." -msgstr "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 <filename><share>/gdm/defaults.conf</filename> file for additional information about each configuration setting." - -#: C/gdm.xml:1709(para) -msgid "The <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename> files follow the standard <filename>.ini</filename> 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 "The <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename> files follow the standard <filename>.ini</filename> 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." - -#: C/gdm.xml:1722(title) -msgid "Daemon Configuration" -msgstr "Daemon Configuration" - -#: C/gdm.xml:1725(title) -msgid "[daemon]" -msgstr "[daemon]" - -#: C/gdm.xml:1728(term) -msgid "AddGtkModules" -msgstr "AddGtkModules" - -#: C/gdm.xml:1730(synopsis) -#, no-wrap -msgid "AddGtkModules=false" -msgstr "AddGtkModules=false" - -#: C/gdm.xml:1731(para) -msgid "If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</command> 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 "If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</command> 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 minimise security issues." - -#: C/gdm.xml:1738(para) -msgid "If true, then the registry daemon <command>at-spi-registryd</command> will be launched by <command>gdmgreeter</command> or <command>gdmlogin</command> starting with version GDM 2.17." -msgstr "If true, then the registry daemon <command>at-spi-registryd</command> will be launched by <command>gdmgreeter</command> or <command>gdmlogin</command> starting with version GDM 2.17." - -#: C/gdm.xml:1744(para) -msgid "Usually this is used for accessibility modules. The modules which are loaded are specified with the <filename>GtkModulesList</filename> key." -msgstr "Usually this is used for accessibility modules. The modules which are loaded are specified with the <filename>GtkModulesList</filename> key." - -#: C/gdm.xml:1753(term) -msgid "AlwaysRestartServer" -msgstr "AlwaysRestartServer" - -#: C/gdm.xml:1755(synopsis) -#, no-wrap -msgid "AlwaysRestartServer=false" -msgstr "AlwaysRestartServer=false" - -#: C/gdm.xml:1756(para) -msgid "If true, then gdm never tries to reuse existing X servers by reinitializing them. It will just kill the existing X server and start over. Normally, just reinitializing is a nicer way to go but if the X server memory usage keeps growing this may be a safer option. On Solaris, this value is always true, and this configuration setting is ignored." -msgstr "If true, then gdm never tries to reuse existing X servers by reinitialising them. It will just kill the existing X server and start over. Normally, just reinitialising is a nicer way to go but if the X server memory usage keeps growing this may be a safer option. On Solaris, this value is always true, and this configuration setting is ignored." - -#: C/gdm.xml:1768(term) -msgid "AlwaysLoginCurrentSession" -msgstr "AlwaysLoginCurrentSession" - -#: C/gdm.xml:1770(synopsis) -#, no-wrap -msgid "AlwaysLoginCurrentSession=true" -msgstr "AlwaysLoginCurrentSession=true" - -#: C/gdm.xml:1771(para) -msgid "If true, then when the user logs in and already has an existing session, then they are connected to that session rather than starting a new session. This only works for sessions running on VTs (Virtual Terminals) started with gdmflexiserver, and not with XDMCP. Note that VTs are not supported on all operating systems." -msgstr "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." - -#: C/gdm.xml:1783(term) -msgid "AutomaticLoginEnable" -msgstr "AutomaticLoginEnable" - -#: C/gdm.xml:1785(synopsis) -#, no-wrap -msgid "AutomaticLoginEnable=false" -msgstr "AutomaticLoginEnable=false" - -#: C/gdm.xml:1786(para) -msgid "If the user given in AutomaticLogin should be logged in upon first bootup. No password will be asked. This is useful for single user workstations where local console security is not an issue. Also could be useful for public terminals, although there see <filename>TimedLogin</filename>." -msgstr "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 <filename>TimedLogin</filename>." - -#: C/gdm.xml:1797(term) -msgid "AutomaticLogin" -msgstr "AutomaticLogin" - -#: C/gdm.xml:1799(synopsis) -#, no-wrap -msgid "AutomaticLogin=" -msgstr "AutomaticLogin=" - -#: C/gdm.xml:1800(para) -msgid "This user should be automatically logged in on first bootup. AutomaticLoginEnable must be true and this must be a valid user for this to happen. \"root\" can never be autologged in however and gdm will just refuse to do it even if you set it up." -msgstr "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." - -#: C/gdm.xml:1808(para) -msgid "The following control chars are recognized within the specified name:" -msgstr "The following control chars are recognised within the specified name:" - -#: C/gdm.xml:1813(para) -#: C/gdm.xml:3821(para) -msgid "%%— the `%' character" -msgstr "%%— the `%' character" - -#: C/gdm.xml:1817(para) -msgid "%d — display's name" -msgstr "%d — display's name" - -#: C/gdm.xml:1821(para) -msgid "%h — display's hostname" -msgstr "%h — display's hostname" - -#: C/gdm.xml:1825(para) -msgid "Alternatively, the name may end with a vertical bar |, the pipe symbol. The name is then used as a application to execute which returns the desired username on standard output. If an empty or otherwise invalid username is returned, automatic login is not performed. This feature is typically used when several remote displays are used as internet kiosks, with a specific user to automatically login for each display." -msgstr "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." - -#: C/gdm.xml:1838(term) -msgid "BaseXsession" -msgstr "BaseXsession" - -#: C/gdm.xml:1840(synopsis) -#, no-wrap -msgid "BaseXsession=<etc>/gdm/Xsession" -msgstr "BaseXsession=<etc>/gdm/Xsession" - -#: C/gdm.xml:1841(para) -msgid "This is the base X session file. When a user logs in, this script will be run with the selected session as the first argument. The selected session will be the <filename>Exec=</filename> from the <filename>.desktop</filename> file of the session." -msgstr "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 <filename>Exec=</filename> from the <filename>.desktop</filename> file of the session." - -#: C/gdm.xml:1849(para) -msgid "If you wish to use the same script for several different display managers, and wish to have some of the script run only for GDM, then you can check the presence of the <filename>GDMSESSION</filename> environmental variable. This will always be set to the basename of <filename>.desktop</filename> (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 <filename>GDM_LANG</filename>, but that is only set when the user picks a non-system default language." -msgstr "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 <filename>GDMSESSION</filename> environmental variable. This will always be set to the basename of <filename>.desktop</filename> (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 <filename>GDM_LANG</filename>, but that is only set when the user picks a non-system default language." - -#: C/gdm.xml:1862(para) -msgid "This script should take care of doing the \"login\" for the user and so it should source the <filename><etc>/profile</filename> and friends. The standard script shipped with GDM sources the files in this order: <filename><etc>/profile</filename> then <filename>~/.profile</filename> then <filename><etc>/xprofile</filename> and finally <filename>~/.xprofile</filename>. Note that different distributions may change this however. Sometimes users personal setup will be in <filename>~/.bash_profile</filename>, however broken that is." -msgstr "This script should take care of doing the \"login\" for the user and so it should source the <filename><etc>/profile</filename> and friends. The standard script shipped with GDM sources the files in this order: <filename><etc>/profile</filename> then <filename>~/.profile</filename> then <filename><etc>/xprofile</filename> and finally <filename>~/.xprofile</filename>. Note that different distributions may change this however. Sometimes users personal setup will be in <filename>~/.bash_profile</filename>, however broken that is." - -#: C/gdm.xml:1879(term) -msgid "Chooser" -msgstr "Chooser" - -#: C/gdm.xml:1881(synopsis) -#, no-wrap -msgid "Chooser=<bin>/gdmchooser" -msgstr "Chooser=<bin>/gdmchooser" - -#: C/gdm.xml:1882(para) -msgid "Full path and name of the chooser executable followed by optional arguments." -msgstr "Full path and name of the chooser executable followed by optional arguments." - -#: C/gdm.xml:1890(term) -msgid "Configurator" -msgstr "Configurator" - -#: C/gdm.xml:1892(synopsis) -#, no-wrap -msgid "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" -msgstr "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" - -#: C/gdm.xml:1893(para) -msgid "The pathname to the configurator binary. If the greeter <filename>ConfigAvailable</filename> 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 "The pathname to the configurator binary. If the greeter <filename>ConfigAvailable</filename> option is set to true then run this binary when somebody chooses Configuration from the Actions menu. GDM will first ask for root password however. And it will never allow this to happen from a remote display." - -#: C/gdm.xml:1905(term) -msgid "ConsoleCannotHandle" -msgstr "ConsoleCannotHandle" - -#: C/gdm.xml:1907(synopsis) -#, no-wrap -msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" -msgstr "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" - -#: C/gdm.xml:1908(para) -msgid "These are the languages that the console cannot handle because of font issues. Here we mean the text console, not X. This is only used when there are errors to report and we cannot start X." -msgstr "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." - -#: C/gdm.xml:1918(term) -msgid "ConsoleNotify" -msgstr "ConsoleNotify" - -#: C/gdm.xml:1920(synopsis) -#, no-wrap -msgid "ConsoleNotify=true" -msgstr "ConsoleNotify=true" - -#: C/gdm.xml:1921(para) -msgid "If false, gdm will not display a message dialog on the console when an error happens." -msgstr "If false, gdm will not display a message dialogue on the console when an error happens." - -#: C/gdm.xml:1929(term) -msgid "DefaultPath" -msgstr "DefaultPath" - -#: C/gdm.xml:1931(synopsis) -#, no-wrap -msgid "DefaultPath=defaultpath (value set by configure)" -msgstr "DefaultPath=defaultpath (value set by configure)" - -#: C/gdm.xml:1932(para) -msgid "Specifies the path which will be set in the user's session. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains \"ROOT=<pathname>\". If the <filename>/etc/default/login</filename> file exists, but contains no value for ROOT, the value as defined in the GDM configuration will be be used." -msgstr "Specifies the path which will be set in the user's session. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains \"ROOT=<pathname>\". If the <filename>/etc/default/login</filename> file exists, but contains no value for ROOT, the value as defined in the GDM configuration will be be used." - -#: C/gdm.xml:1945(term) -msgid "DefaultSession" -msgstr "DefaultSession" - -#: C/gdm.xml:1947(synopsis) -#, no-wrap -msgid "DefaultSession=gnome.desktop" -msgstr "DefaultSession=gnome.desktop" - -#: C/gdm.xml:1948(para) -msgid "The session that is used by default if the user does not have a saved preference and has picked 'Last' from the list of sessions. Note that 'Last' need not be displayed, see the <filename>ShowLastSession</filename> key." -msgstr "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 <filename>ShowLastSession</filename> key." - -#: C/gdm.xml:1959(term) -msgid "DisplayInitDir" -msgstr "DisplayInitDir" - -#: C/gdm.xml:1961(synopsis) -#, no-wrap -msgid "DisplayInitDir=<etc>/gdm/Init" -msgstr "DisplayInitDir=<etc>/gdm/Init" - -#: C/gdm.xml:1962(para) -msgid "Directory containing the display init scripts. See the ``The Script Directories'' section for more info." -msgstr "Directory containing the display init scripts. See the ``The Script Directories'' section for more info." - -#: C/gdm.xml:1970(term) -msgid "DisplayLastLogin" -msgstr "DisplayLastLogin" - -#: C/gdm.xml:1972(synopsis) -#, no-wrap -msgid "DisplayLastLogin=true" -msgstr "DisplayLastLogin=true" - -#: C/gdm.xml:1973(para) -msgid "If true then the last login information is printed to the user before being prompted for password. While this gives away some info on what users are on a system, it on the other hand should give the user an idea of when they logged in and if it doesn't seem kosher to them, they can just abort the login and contact the sysadmin (avoids running malicious startup scripts). This was added in version 2.5.90.0." -msgstr "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." - -#: C/gdm.xml:1982(para) -msgid "This is for making GDM conformant to CSC-STD-002-85, although that is purely theoretical now. Someone should read that spec and ensure that this actually conforms (in addition to other places in GDM). See <filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> for more info." -msgstr "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 <filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> for more info." - -#: C/gdm.xml:1994(term) -msgid "DoubleLoginWarning" -msgstr "DoubleLoginWarning" - -#: C/gdm.xml:1996(synopsis) -#, no-wrap -msgid "DoubleLoginWarning=true" -msgstr "DoubleLoginWarning=true" - -#: C/gdm.xml:1997(para) -msgid "If true, GDM will warn the user if they are already logged in on another virtual terminal. On systems where GDM supports checking the X virtual terminals, GDM will let the user switch to the previous login virtual terminal instead of logging in." -msgstr "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." - -#: C/gdm.xml:2007(term) -msgid "DynamicXServers" -msgstr "DynamicXServers" - -#: C/gdm.xml:2009(synopsis) -#, no-wrap -msgid "DynamicXServers=false" -msgstr "DynamicXServers=false" - -#: C/gdm.xml:2010(para) -msgid "If true, the GDM daemon will honor requests to manage displays via the <filename>/tmp/.gdm_socket</filename> socket connection. Displays can be created, started, and deleted with the appropriate commands. The <filename>gdmdynamic</filename> command is a convenient method to send these messages." -msgstr "If true, the GDM daemon will honour requests to manage displays via the <filename>/tmp/.gdm_socket</filename> socket connection. Displays can be created, started, and deleted with the appropriate commands. The <filename>gdmdynamic</filename> command is a convenient method to send these messages." - -#: C/gdm.xml:2022(term) -msgid "FailsafeXServer" -msgstr "FailsafeXServer" - -#: C/gdm.xml:2024(synopsis) -#, no-wrap -msgid "FailsafeXServer=" -msgstr "FailsafeXServer=" - -#: C/gdm.xml:2025(para) -msgid "An X command line in case we can't start the normal X server. should probably be some sort of a script that runs an appropriate low resolution X server that will just work. This is tried before the <filename>XKeepsCrashing</filename> script is run." -msgstr "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 <filename>XKeepsCrashing</filename> script is run." - -#: C/gdm.xml:2036(term) -msgid "FirstVT" -msgstr "FirstVT" - -#: C/gdm.xml:2038(synopsis) -#, no-wrap -msgid "FirstVT=7" -msgstr "FirstVT=7" - -#: C/gdm.xml:2039(para) -msgid "On systems where GDM supports automatic VT (virtual terminal) allocation, this is the first vt to try. Usually standard text logins are run on the lower vts. See also <filename>VTAllocation</filename>." -msgstr "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 <filename>VTAllocation</filename>." - -#: C/gdm.xml:2049(term) -msgid "FlexibleXServers" -msgstr "FlexibleXServers" - -#: C/gdm.xml:2051(synopsis) -#, no-wrap -msgid "FlexibleXServers=5" -msgstr "FlexibleXServers=5" - -#: C/gdm.xml:2052(para) -msgid "The maximum number of allowed flexible displays. These are displays that can be run using the <filename>/tmp/.gdm_socket</filename> socket connection. This is used for both full flexible displays and for Xnest displays." -msgstr "The maximum number of allowed flexible displays. These are displays that can be run using the <filename>/tmp/.gdm_socket</filename> socket connection. This is used for both fully flexible displays and for Xnest displays." - -#: C/gdm.xml:2063(term) -msgid "FlexiReapDelayMinutes" -msgstr "FlexiReapDelayMinutes" - -#: C/gdm.xml:2065(synopsis) -#, no-wrap -msgid "FlexiReapDelayMinutes=5" -msgstr "FlexiReapDelayMinutes=5" - -#: C/gdm.xml:2066(para) -msgid "After how many minutes of inactivity at the login screen should a flexi display be reaped. This is only in effect before a user logs in. Also it does not affect the Xnest flexiservers. To turn off this behavior set this value to 0. This was added in version 2.5.90.0." -msgstr "After how many minutes of inactivity at the login screen should a flexi display be reaped. This is only in effect before a user logs in. Also it does not affect the Xnest flexiservers. To turn off this behavior set this value to 0. This was added in version 2.5.90.0." - -#: C/gdm.xml:2077(term) -msgid "Greeter" -msgstr "Greeter" - -#: C/gdm.xml:2079(synopsis) -#, no-wrap -msgid "Greeter=<bin>/gdmlogin" -msgstr "Greeter=<bin>/gdmlogin" - -#: C/gdm.xml:2080(para) -msgid "Full path and name of the greeter executable followed by optional arguments. This is the greeter used for all displays except for the XDMCP remote displays. See also <filename>RemoteGreeter</filename>" -msgstr "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 <filename>RemoteGreeter</filename>" - -#: C/gdm.xml:2090(term) -msgid "Group" -msgstr "Group" - -#: C/gdm.xml:2092(synopsis) -#, no-wrap -msgid "Group=gdm" -msgstr "Group=gdm" - -#: C/gdm.xml:2093(para) -msgid "The group name under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogs are run. Also see <filename>User</filename>. 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 <filename>ServAuthDir</filename> is owned by this group. The ownership and permissions of <filename>ServAuthDir</filename> should be <filename>root.gdm</filename> and 1770." -msgstr "The group name under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogues are run. Also see <filename>User</filename>. This user will have access to all the X authorisation files, and perhaps to other internal GDM data and it should not be a user such as nobody, but a dedicated user. The <filename>ServAuthDir</filename> is owned by this group. The ownership and permissions of <filename>ServAuthDir</filename> should be <filename>root:gdm</filename> and 1770." - -#: C/gdm.xml:2110(term) -msgid "GtkModulesList" -msgstr "GtkModulesList" - -#: C/gdm.xml:2112(synopsis) -#, no-wrap -msgid "GtkModulesList=module-1:module-2:..." -msgstr "GtkModulesList=module-1:module-2:..." - -#: C/gdm.xml:2113(para) -msgid "A colon separated list of Gtk+ modules that <command>gdmgreeter</command> or <command>gdmlogin</command> will be invoked with if <filename>AddGtkModules</filename> is true. The format is the same as the standard Gtk+ module interface." -msgstr "A colon separated list of Gtk+ modules that <command>gdmgreeter</command> or <command>gdmlogin</command> will be invoked with if <filename>AddGtkModules</filename> is true. The format is the same as the standard Gtk+ module interface." - -#: C/gdm.xml:2124(term) -msgid "HaltCommand" -msgstr "HaltCommand" - -#: C/gdm.xml:2126(synopsis) -#, no-wrap -msgid "HaltCommand=<sbin>/shutdown -h now" -msgstr "HaltCommand=<sbin>/shutdown -h now" - -#: C/gdm.xml:2127(para) -msgid "Full path and arguments to command to be executed when user selects \"Shut Down\" from the Actions menu. This can be a ';' separated list of commands to try. If a value is missing, the shut down command is not available. Note that the default for this value is not empty, so to disable \"Shut Down\" it must be set to an empty value." -msgstr "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." - -#: C/gdm.xml:2140(term) -msgid "KillInitClients" -msgstr "KillInitClients" - -#: C/gdm.xml:2142(synopsis) -#, no-wrap -msgid "KillInitClients=true" -msgstr "KillInitClients=true" - -#: C/gdm.xml:2143(para) -msgid "Determines whether GDM should kill X clients started by the init scripts when the user logs in." -msgstr "Determines whether GDM should kill X clients started by the init scripts when the user logs in." - -#: C/gdm.xml:2151(term) -msgid "LogDir" -msgstr "LogDir" - -#: C/gdm.xml:2153(synopsis) -#, no-wrap -msgid "LogDir=<var>/log/gdm" -msgstr "LogDir=<var>/log/gdm" - -#: C/gdm.xml:2154(para) -msgid "Directory containing the log files for the individual displays. By default this is the same as the ServAuthDir." -msgstr "Directory containing the log files for the individual displays. By default this is the same as the ServAuthDir." - -#: C/gdm.xml:2162(term) -msgid "PidFile" -msgstr "PidFile" - -#: C/gdm.xml:2164(synopsis) -#, no-wrap -msgid "PidFile=<var>/run/gdm.pid" -msgstr "PidFile=<var>/run/gdm.pid" - -#: C/gdm.xml:2165(para) -msgid "Name of the file containing the <filename>gdm</filename> process id." -msgstr "Name of the file containing the <filename>gdm</filename> process id." - -#: C/gdm.xml:2173(term) -msgid "PreFetchProgram" -msgstr "PreFetchProgram" - -#: C/gdm.xml:2175(synopsis) -#, no-wrap -msgid "PreFetchProgram=command" -msgstr "PreFetchProgram=command" - -#: C/gdm.xml:2176(para) -msgid "Program to be run by the GDM greeter/login program when the initial screen is displayed. The purpose is to provide a hook where files which will be used after login can be preloaded to speed performance for the user. The program will be called once only, the first time a greeter is displayed. The gdmprefetch command may be used. This utility will load any libraries passed in on the command line, or if the argument starts with a \"@\" character, it will process the file assuming it is an ASCII file containing a list of libraries, one per line, and load each library in the file." -msgstr "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." - -#: C/gdm.xml:2192(term) -msgid "PostLoginScriptDir" -msgstr "PostLoginScriptDir" - -#: C/gdm.xml:2194(synopsis) -#, no-wrap -msgid "PostLoginScriptDir=<etc>/gdm/PostLogin" -msgstr "PostLoginScriptDir=<etc>/gdm/PostLogin" - -#: C/gdm.xml:2195(para) -msgid "Directory containing the scripts run right after the user logs in, but before any session setup is done. See the ``The Script Directories'' section for more info." -msgstr "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." - -#: C/gdm.xml:2204(term) -msgid "PostSessionScriptDir" -msgstr "PostSessionScriptDir" - -#: C/gdm.xml:2206(synopsis) -#, no-wrap -msgid "PostSessionScriptDir=<etc>/gdm/PostSession" -msgstr "PostSessionScriptDir=<etc>/gdm/PostSession" - -#: C/gdm.xml:2207(para) -msgid "Directory containing the scripts run after the user logs out. See the ``The Script Directories'' section for more info." -msgstr "Directory containing the scripts run after the user logs out. See the ``The Script Directories'' section for more info." - -#: C/gdm.xml:2215(term) -msgid "PreSessionScriptDir" -msgstr "PreSessionScriptDir" - -#: C/gdm.xml:2217(synopsis) -#, no-wrap -msgid "PreSessionScriptDir=<etc>/gdm/PreSession" -msgstr "PreSessionScriptDir=<etc>/gdm/PreSession" - -#: C/gdm.xml:2218(para) -msgid "Directory containing the scripts run before the user logs in. See the ``The Script Directories'' section for more info." -msgstr "Directory containing the scripts run before the user logs in. See the ``The Script Directories'' section for more info." - -#: C/gdm.xml:2226(term) -msgid "RebootCommand" -msgstr "RebootCommand" - -#: C/gdm.xml:2228(synopsis) -#, no-wrap -msgid "RebootCommand=<sbin>/shutdown -r now" -msgstr "RebootCommand=<sbin>/shutdown -r now" - -#: C/gdm.xml:2229(para) -msgid "Full path and optional arguments to the command to be executed when user selects Restart from the Actions menu. This can be a ';' separated list of commands to try. If missing, the restart command is not available. Note that the default for this value is not empty so to disable restart you must set this explicitly to an empty value." -msgstr "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." - -#: C/gdm.xml:2241(term) -msgid "RemoteGreeter" -msgstr "RemoteGreeter" - -#: C/gdm.xml:2243(synopsis) -#, no-wrap -msgid "RemoteGreeter=<bin>/gdmlogin" -msgstr "RemoteGreeter=<bin>/gdmlogin" - -#: C/gdm.xml:2244(para) -msgid "Full path and name of the greeter executable followed by optional arguments. This is used for all remote XDMCP sessions. It is useful to have the less graphically demanding greeter here if you use the Themed Greeter for your main greeter. See also the <filename>Greeter</filename> key." -msgstr "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 <filename>Greeter</filename> key." - -#: C/gdm.xml:2255(term) -msgid "RootPath" -msgstr "RootPath" - -#: C/gdm.xml:2257(synopsis) -#, no-wrap -msgid "RootPath=defaultpath (value set by configure)" -msgstr "RootPath=defaultpath (value set by configure)" - -#: C/gdm.xml:2258(para) -msgid "Specifies the path which will be set in the root's session and the {Init,PostLogin,PreSession,PostSession} scripts executed by GDM. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains \"SUROOT=<pathname>\". If the <filename>/etc/default/login</filename> file exists, but contains no value for SUROOT, the value as defined in the GDM configuration will be used." -msgstr "Specifies the path which will be set in root's session and the {Init,PostLogin,PreSession,PostSession} scripts executed by GDM. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains \"SUROOT=<pathname>\". If the <filename>/etc/default/login</filename> file exists, but contains no value for SUROOT, the value as defined in the GDM configuration will be used." - -#: C/gdm.xml:2272(term) -msgid "ServAuthDir" -msgstr "ServAuthDir" - -#: C/gdm.xml:2274(synopsis) -#, no-wrap -msgid "ServAuthDir=<var>/gdm" -msgstr "ServAuthDir=<var>/gdm" - -#: C/gdm.xml:2275(para) -msgid "Directory containing the X authentication files for the individual displays. Should be owned by <filename>root.gdm</filename> with permissions 1770, where <filename>gdm</filename> is the GDM group as defined by the <filename>Group</filename> option. That is should be owned by root, with <filename>gdm</filename> 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 "Directory containing the X authentication files for the individual displays. Should be owned by <filename>root:gdm</filename> with permissions 1770, where <filename>gdm</filename> is the GDM group as defined by the <filename>Group</filename> option. That is should be owned by root, with <filename>gdm</filename> 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." - -#: C/gdm.xml:2297(term) -msgid "SessionDesktopDir" -msgstr "SessionDesktopDir" - -#: C/gdm.xml:2299(synopsis) -#, no-wrap -msgid "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" -msgstr "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" - -#: C/gdm.xml:2300(para) -msgid "Directory containing the <filename>.desktop</filename> 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 "Directory containing the <filename>.desktop</filename> 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." - -#: C/gdm.xml:2310(term) -msgid "SoundProgram" -msgstr "SoundProgram" - -#: C/gdm.xml:2312(filename) -msgid "<bin>/play" -msgstr "<bin>/play" - -#: C/gdm.xml:2312(filename) -msgid "<bin>/audioplay" -msgstr "<bin>/audioplay" - -#: C/gdm.xml:2312(synopsis) -#, no-wrap -msgid "SoundProgram=<placeholder-1/> (or <placeholder-2/> on Solaris)" -msgstr "SoundProgram=<placeholder-1/> (or <placeholder-2/> on Solaris)" - -#: C/gdm.xml:2313(para) -msgid "Application to use when playing a sound. Currently used for playing the login sound, see the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0." -msgstr "Application to use when playing a sound. Currently used for playing the login sound, see the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0." - -#: C/gdm.xml:2323(term) -msgid "StandardXServer" -msgstr "StandardXServer" - -#: C/gdm.xml:2325(synopsis) -#, no-wrap -msgid "StandardXServer=/dir/to/X (value assigned by configuration file)" -msgstr "StandardXServer=/dir/to/X (value assigned by configuration file)" - -#: C/gdm.xml:2326(para) -msgid "Full path and arguments to the standard X server command. This is used when gdm cannot find any other definition, and it's used as the default and failsafe fallback in a number of places. This should be able to run some sort of X server." -msgstr "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." - -#: C/gdm.xml:2337(term) -msgid "SuspendCommand" -msgstr "SuspendCommand" - -#: C/gdm.xml:2339(synopsis) -#, no-wrap -msgid "SuspendCommand=" -msgstr "SuspendCommand=" - -#: C/gdm.xml:2340(para) -msgid "Full path and arguments to command to be executed when user selects Suspend from the Actions menu. If empty there is no such menu item. Note that the default for this value is not empty so to disable suspend you must set this explicitly to an empty value." -msgstr "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." - -#: C/gdm.xml:2351(term) -msgid "TimedLoginEnable" -msgstr "TimedLoginEnable" - -#: C/gdm.xml:2353(synopsis) -#, no-wrap -msgid "TimedLoginEnable=false" -msgstr "TimedLoginEnable=false" - -#: C/gdm.xml:2354(para) -msgid "If the user given in <filename>TimedLogin</filename> should be logged in after a number of seconds (set with <filename>TimedLoginDelay</filename>) of inactivity on the login screen. This is useful for public access terminals or perhaps even home use. If the user uses the keyboard or browses the menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or 30 seconds, whichever is higher. If the user does not enter a username but just hits the ENTER key while the login program is requesting the username, then GDM will assume the user wants to login immediately as the timed user. Note that no password will be asked for this user so you should be careful, although if using PAM it can be configured to require password entry before allowing login." -msgstr "If the user given in <filename>TimedLogin</filename> should be logged in after a number of seconds (set with <filename>TimedLoginDelay</filename>) of inactivity on the login screen. This is useful for public access terminals or perhaps even home use. If the user uses the keyboard or browses the menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or 30 seconds, whichever is higher. If the user does not enter a username but just hits the ENTER key while the login program is requesting the username, then GDM will assume the user wants to login immediately as the timed user. Note that no password will be asked for this user so you should be careful, although if using PAM it can be configured to require password entry before allowing login." - -#: C/gdm.xml:2374(term) -msgid "TimedLogin" -msgstr "TimedLogin" - -#: C/gdm.xml:2376(synopsis) -#, no-wrap -msgid "TimedLogin=" -msgstr "TimedLogin=" - -#: C/gdm.xml:2377(para) -msgid "This is the user that should be logged in after a specified number of seconds of inactivity. This can never be \"root\" and gdm will refuse to log in root this way. The same features as for <filename>AutomaticLogin</filename> are supported. The same control chars and piping to a application are supported." -msgstr "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 <filename>AutomaticLogin</filename> are supported. The same control chars and piping to a application are supported." - -#: C/gdm.xml:2389(term) -msgid "TimedLoginDelay" -msgstr "TimedLoginDelay" - -#: C/gdm.xml:2391(synopsis) -#, no-wrap -msgid "TimedLoginDelay=30" -msgstr "TimedLoginDelay=30" - -#: C/gdm.xml:2392(para) -msgid "Delay in seconds before the <filename>TimedLogin</filename> user will be logged in. It must be greater then or equal to 10." -msgstr "Delay in seconds before the <filename>TimedLogin</filename> user will be logged in. It must be greater then or equal to 10." - -#: C/gdm.xml:2400(term) -msgid "User" -msgstr "User" - -#: C/gdm.xml:2402(synopsis) -#, no-wrap -msgid "User=gdm" -msgstr "User=gdm" - -#: C/gdm.xml:2403(para) -msgid "The username under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogs are run. Also see <filename>Group</filename>. 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 "The username under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogues are run. Also see <filename>Group</filename>. This user will have access to all the X authorisation files, and other internal GDM data; it should not be a user such as nobody, but a dedicated user." - -#: C/gdm.xml:2417(term) -msgid "UserAuthDir" -msgstr "UserAuthDir" - -#: C/gdm.xml:2419(synopsis) -#, no-wrap -msgid "UserAuthDir=" -msgstr "UserAuthDir=" - -#: C/gdm.xml:2420(para) -msgid "The directory where user's <filename>.Xauthority</filename> 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: <filename>~/authdir/</filename>." -msgstr "The directory where user's <filename>.Xauthority</filename> 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: <filename>~/authdir/</filename>." - -#: C/gdm.xml:2427(para) -msgid "If you do not use the tilde expansion, then the filename created will be random, like in <filename>UserAuthFBDir</filename>. This way many users can have the same authentication directory. For example you might want to set this to <filename>/tmp</filename> 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 <filename>/tmp</filename> directory." -msgstr "If you do not use the tilde expansion, then the filename created will be random, like in <filename>UserAuthFBDir</filename>. This way many users can have the same authentication directory. For example you might want to set this to <filename>/tmp</filename> 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 <filename>/tmp</filename> directory." - -#: C/gdm.xml:2440(para) -msgid "Normally if this is the user's home directory GDM will still refuse to put cookies there if it thinks it is NFS (by testing root-squashing). This can be changed by setting <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false." -msgstr "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 <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false." - -#: C/gdm.xml:2451(term) -msgid "UserAuthFBDir" -msgstr "UserAuthFBDir" - -#: C/gdm.xml:2453(synopsis) -#, no-wrap -msgid "UserAuthFBDir=/tmp" -msgstr "UserAuthFBDir=/tmp" - -#: C/gdm.xml:2454(para) -msgid "If GDM fails to update the user's <filename>.Xauthority</filename> file a fallback cookie is created in this directory." -msgstr "If GDM fails to update the user's <filename>.Xauthority</filename> file a fallback cookie is created in this directory." - -#: C/gdm.xml:2463(term) -msgid "UserAuthFile" -msgstr "UserAuthFile" - -#: C/gdm.xml:2465(synopsis) -#, no-wrap -msgid "UserAuthFile=.Xauthority" -msgstr "UserAuthFile=.Xauthority" - -#: C/gdm.xml:2466(para) -msgid "Name of the file used for storing user cookies." -msgstr "Name of the file used for storing user cookies." - -#: C/gdm.xml:2473(term) -msgid "VTAllocation" -msgstr "VTAllocation" - -#: C/gdm.xml:2475(synopsis) -#, no-wrap -msgid "VTAllocation=true" -msgstr "VTAllocation=true" - -#: C/gdm.xml:2476(para) -msgid "On systems where GDM supports automatic VT (virtual terminal) allocation (currently Linux and FreeBSD only), you can have GDM automatically append the vt argument to the X server executable. This way races that come up from each X server managing it's own vt allocation can be avoided. See also <filename>FirstVT</filename>." -msgstr "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 <filename>FirstVT</filename>." - -#: C/gdm.xml:2488(term) -msgid "XKeepsCrashing" -msgstr "XKeepsCrashing" - -#: C/gdm.xml:2490(synopsis) -#, no-wrap -msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" -msgstr "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" - -#: C/gdm.xml:2491(para) -msgid "A script to run in case X keeps crashing. This is for running An X configuration or whatever else to make the X configuration work. See the script that came with the distribution for an example. The distributed <filename>XKeepsCrashing</filename> 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 "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 <filename>XKeepsCrashing</filename> 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." - -#: C/gdm.xml:2500(para) -msgid "In case <filename>FailsafeXServer</filename> is setup, that will be tried first. and this only used as a backup if even that X server keeps crashing." -msgstr "In case <filename>FailsafeXServer</filename> is setup, that will be tried first. and this only used as a backup if even that X server keeps crashing." - -#: C/gdm.xml:2509(term) -msgid "Xnest" -msgstr "Xnest" - -#: C/gdm.xml:2511(synopsis) -#, no-wrap -msgid "Xnest=<bin>/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)" -msgstr "Xnest=<bin>/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)" - -#: C/gdm.xml:2512(para) -msgid "The full path and arguments to the Xnest command. This is used for the flexible Xnest displays. This way the user can start new login screens in a nested window. Of course you must have the Xnest display from your X server packages installed for this to work." -msgstr "The full path and arguments to the Xnest command. This is used for the flexible Xnest displays. This way the user can start new login screens in a nested window. Of course you must have the Xnest display from your X server packages installed for this to work." - -#: C/gdm.xml:2525(title) -msgid "Security Options" -msgstr "Security Options" - -#: C/gdm.xml:2528(title) -msgid "[security]" -msgstr "[security]" - -#: C/gdm.xml:2531(term) -msgid "AllowRoot" -msgstr "AllowRoot" - -#: C/gdm.xml:2533(synopsis) -#, no-wrap -msgid "AllowRoot=true" -msgstr "AllowRoot=true" - -#: C/gdm.xml:2534(para) -msgid "Allow root (privileged user) to log in through GDM. Set this to false if you want to disallow such logins." -msgstr "Allow root (privileged user) to log in through GDM. Set this to false if you want to disallow such logins." - -#: C/gdm.xml:2538(para) -msgid "On systems that support PAM, this parameter is not as useful as you can use PAM to do the same thing, and in fact do even more. However it is still followed, so you should probably leave it true for PAM systems." -msgstr "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." - -#: C/gdm.xml:2548(term) -msgid "AllowRemoteRoot" -msgstr "AllowRemoteRoot" - -#: C/gdm.xml:2550(synopsis) -#, no-wrap -msgid "AllowRemoteRoot=false" -msgstr "AllowRemoteRoot=false" - -#: C/gdm.xml:2551(para) -msgid "Allow root (privileged user) to log in remotely through GDM. This value should be set to true to allow such logins. Remote logins are any logins that come in through the XDMCP." -msgstr "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." - -#: C/gdm.xml:2556(para) -msgid "On systems that support PAM, this parameter is not as useful since you can use PAM to do the same thing, and do even more." -msgstr "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." - -#: C/gdm.xml:2561(para) -msgid "This value will be overridden and set to false if the <filename>/etc/default/login</filename> file exists and contains \"CONSOLE=/dev/login\", and set to true if the <filename>/etc/default/login</filename> file exists and contains any other value or no value for CONSOLE." -msgstr "This value will be overridden and set to false if the <filename>/etc/default/login</filename> file exists and contains \"CONSOLE=/dev/login\", and set to true if the <filename>/etc/default/login</filename> file exists and contains any other value or no value for CONSOLE." - -#: C/gdm.xml:2572(term) -msgid "AllowRemoteAutoLogin" -msgstr "AllowRemoteAutoLogin" - -#: C/gdm.xml:2574(synopsis) -#, no-wrap -msgid "AllowRemoteAutoLogin=false" -msgstr "AllowRemoteAutoLogin=false" - -#: C/gdm.xml:2575(para) -msgid "Allow the timed login to work remotely. That is, remote connections through XDMCP will be allowed to log into the \"TimedLogin\" user by letting the login window time out, just like the local user on the first console." -msgstr "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." - -#: C/gdm.xml:2581(para) -msgid "Note that this can make a system quite insecure, and thus is off by default." -msgstr "Note that this can make a system quite insecure, and thus is off by default." - -#: C/gdm.xml:2589(term) -msgid "CheckDirOwner" -msgstr "CheckDirOwner" - -#: C/gdm.xml:2591(synopsis) -#, no-wrap -msgid "CheckDirOwner=true" -msgstr "CheckDirOwner=true" - -#: C/gdm.xml:2592(para) -msgid "By default GDM checks the ownership of the home directories before writing to them, this prevents security issues in case of bad setup. However in some instances home directories will be owned by a different user and in this case it is necessary to turn this option on. You will also most likely have to turn the <filename>RelaxPermissions</filename> 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 "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 <filename>RelaxPermissions</filename> 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." - -#: C/gdm.xml:2606(term) -msgid "SupportAutomount" -msgstr "SupportAutomount" - -#: C/gdm.xml:2608(synopsis) -#, no-wrap -msgid "SupportAutomount=false" -msgstr "SupportAutomount=false" - -#: C/gdm.xml:2609(para) -msgid "By default GDM checks the ownership of the home directories before writing to them, this prevents security issues in case of bad setup. However, when home directories are managed by automounter, they are often not mounted before they are accessed. This option works around subtleties of Linux automounter." -msgstr "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." - -#: C/gdm.xml:2621(term) -msgid "DisallowTCP" -msgstr "DisallowTCP" - -#: C/gdm.xml:2623(synopsis) -#, no-wrap -msgid "DisallowTCP=true" -msgstr "DisallowTCP=true" - -#: C/gdm.xml:2624(para) -msgid "If true, then always append <filename>-nolisten tcp</filename> 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 "If true, then always append <filename>-nolisten tcp</filename> 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." - -#: C/gdm.xml:2637(term) -msgid "NeverPlaceCookiesOnNFS" -msgstr "NeverPlaceCookiesOnNFS" - -#: C/gdm.xml:2639(synopsis) -#, no-wrap -msgid "NeverPlaceCookiesOnNFS=true" -msgstr "NeverPlaceCookiesOnNFS=true" - -#: C/gdm.xml:2640(para) -msgid "Normally if this is true (which is by default), GDM will not place cookies into the user's home directory if this directory is on NFS. Well, GDM will consider any filesystem with root-squashing an NFS filesystem. Sometimes however the remote file system can have root squashing and be safe (perhaps by using encryption). In this case set this to 'false'. Note that this option appeared in version 2.4.4.4 and is ignored in previous versions." -msgstr "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. 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." - -#: C/gdm.xml:2654(term) -msgid "PasswordRequired" -msgstr "PasswordRequired" - -#: C/gdm.xml:2656(synopsis) -#, no-wrap -msgid "PasswordRequired=false" -msgstr "PasswordRequired=false" - -#: C/gdm.xml:2657(para) -msgid "If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be passed as a flag to pam_authenticate and pam_acct_mgmt, disallowing NULL password. This setting will only take effect if PAM is being used by GDM. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains \"PASSREQ=[YES|NO]\". If the <filename>/etc/default/login</filename> file exists, but contains no value for PASSREQ, the value as defined in the GDM configuration will be used." -msgstr "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 <filename>/etc/default/login</filename> if it contains \"PASSREQ=[YES|NO]\". If the <filename>/etc/default/login</filename> file exists, but contains no value for PASSREQ, the value as defined in the GDM configuration will be used." - -#: C/gdm.xml:2673(term) -msgid "RelaxPermissions" -msgstr "RelaxPermissions" - -#: C/gdm.xml:2675(synopsis) -#, no-wrap -msgid "RelaxPermissions=0" -msgstr "RelaxPermissions=0" - -#: C/gdm.xml:2676(para) -msgid "By default GDM ignores files and directories writable to other users than the owner." -msgstr "By default GDM ignores files and directories writable to other users than the owner." - -#: C/gdm.xml:2681(para) -msgid "Changing the value of RelaxPermissions makes it possible to alter this behavior:" -msgstr "Changing the value of RelaxPermissions makes it possible to alter this behavior:" - -#: C/gdm.xml:2686(para) -msgid "0 - Paranoia option. Only accepts user owned files and directories." -msgstr "0 - Paranoia option. Only accepts user owned files and directories." - -#: C/gdm.xml:2690(para) -msgid "1 - Allow group writable files and directories." -msgstr "1 - Allow group writable files and directories." - -#: C/gdm.xml:2693(para) -msgid "2 - Allow world writable files and directories." -msgstr "2 - Allow world writable files and directories." - -#: C/gdm.xml:2700(term) -msgid "RetryDelay" -msgstr "RetryDelay" - -#: C/gdm.xml:2702(synopsis) -#, no-wrap -msgid "RetryDelay=1" -msgstr "RetryDelay=1" - -#: C/gdm.xml:2703(para) -msgid "The number of seconds GDM should wait before reactivating the entry field after a failed login." -msgstr "The number of seconds GDM should wait before reactivating the entry field after a failed login." - -#: C/gdm.xml:2711(term) -msgid "UserMaxFile" -msgstr "UserMaxFile" - -#: C/gdm.xml:2713(synopsis) -#, no-wrap -msgid "UserMaxFile=65536" -msgstr "UserMaxFile=65536" - -#: C/gdm.xml:2714(para) -msgid "GDM will refuse to read/write files bigger than this number (specified in bytes)." -msgstr "GDM will refuse to read/write files bigger than this number (specified in bytes)." - -#: C/gdm.xml:2719(para) -msgid "In addition to the size check GDM is extremely picky about accessing files in user directories. It will not follow symlinks and can optionally refuse to read files and directories writable by other than the owner. See the <filename>RelaxPermissions</filename> option for more info." -msgstr "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 <filename>RelaxPermissions</filename> option for more info." - -#: C/gdm.xml:2732(title) -msgid "XDCMP Support" -msgstr "XDCMP Support" - -#: C/gdm.xml:2735(title) -msgid "[xdmcp]" -msgstr "[xdmcp]" - -#: C/gdm.xml:2738(term) -msgid "DisplaysPerHost" -msgstr "DisplaysPerHost" - -#: C/gdm.xml:2740(synopsis) -#, no-wrap -msgid "DisplaysPerHost=1" -msgstr "DisplaysPerHost=1" - -#: C/gdm.xml:2741(para) -msgid "To prevent attackers from filling up the pending queue, GDM will only allow one connection for each remote computer. If you want to provide display services to computers with more than one screen, you should increase the <filename>DisplaysPerHost</filename> value accordingly." -msgstr "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 <filename>DisplaysPerHost</filename> value accordingly." - -#: C/gdm.xml:2749(para) -msgid "Note that the number of connections from the local computer is unlimited. Only remote connections are limited by this number." -msgstr "Note that the number of connections from the local computer is unlimited. Only remote connections are limited by this number." - -#: C/gdm.xml:2757(term) -#: C/gdm.xml:4004(term) -msgid "Enable" -msgstr "Enable" - -#: C/gdm.xml:2759(synopsis) -#: C/gdm.xml:4006(synopsis) -#, no-wrap -msgid "Enable=false" -msgstr "Enable=false" - -#: C/gdm.xml:2760(para) -msgid "Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM." -msgstr "Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM." - -#: C/gdm.xml:2765(para) -msgid "<filename>gdm</filename> listens for requests on UDP port 177. See the Port option for more information." -msgstr "<filename>gdm</filename> listens for requests on UDP port 177. See the Port option for more information." - -#: C/gdm.xml:2770(para) -msgid "If GDM is compiled to support it, access from remote displays can be controlled using the TCP Wrappers library. The service name is <filename>gdm</filename>" -msgstr "If GDM is compiled to support it, access from remote displays can be controlled using the TCP Wrappers library. The service name is <filename>gdm</filename>" - -#: C/gdm.xml:2776(para) -msgid "" -"You should add <screen>\n" -"gdm:.my.domain\n" -"</screen> to your <filename><etc>/hosts.allow</filename>, depending on your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" -"You should add <screen>\n" -"gdm:.my.domain\n" -"</screen> to your <filename><etc>/hosts.allow</filename>, depending on your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details." - -#: C/gdm.xml:2787(para) -msgid "Please note that XDMCP is not a particularly secure protocol and that it is a good idea to block UDP port 177 on your firewall unless you really need it." -msgstr "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." - -#: C/gdm.xml:2796(term) -msgid "EnableProxy" -msgstr "EnableProxy" - -#: C/gdm.xml:2798(synopsis) -#, no-wrap -msgid "EnableProxy=false" -msgstr "EnableProxy=false" - -#: C/gdm.xml:2799(para) -msgid "Setting this to true enables support for running XDMCP sessions on a local proxy X server. This may improve the performance of XDMCP sessions, especially on high latency networks, as many X protocol operations can be completed without going over the network." -msgstr "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." - -#: C/gdm.xml:2806(para) -msgid "Note, however, that this mode will significantly increase the burden on the machine hosting the XDMCP sessions" -msgstr "Note, however, that this mode will significantly increase the burden on the machine hosting the XDMCP sessions" - -#: C/gdm.xml:2810(para) -msgid "See the <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</filename> options for further details on how to configure support for this feature." -msgstr "See the <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</filename> options for further details on how to configure support for this feature." - -#: C/gdm.xml:2819(term) -msgid "HonorIndirect" -msgstr "HonorIndirect" - -#: C/gdm.xml:2821(synopsis) -#, no-wrap -msgid "HonorIndirect=true" -msgstr "HonorIndirect=true" - -#: C/gdm.xml:2822(para) -msgid "Enables XDMCP INDIRECT choosing (i.e. remote execution of <filename>gdmchooser</filename>) for X-terminals which don't supply their own display browser." -msgstr "Enables XDMCP INDIRECT choosing (i.e. remote execution of <filename>gdmchooser</filename>) for X-terminals which don't supply their own display browser." - -#: C/gdm.xml:2831(term) -msgid "MaxPending" -msgstr "MaxPending" - -#: C/gdm.xml:2833(synopsis) -#, no-wrap -msgid "MaxPending=4" -msgstr "MaxPending=4" - -#: C/gdm.xml:2834(para) -msgid "To avoid denial of service attacks, GDM has fixed size queue of pending connections. Only MaxPending displays can start at the same time." -msgstr "To avoid denial of service attacks, GDM has fixed size queue of pending connections. Only MaxPending displays can start at the same time." - -#: C/gdm.xml:2840(para) -msgid "Please note that this parameter does *not* limit the number of remote displays which can be managed. It only limits the number of displays initiating a connection simultaneously." -msgstr "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." - -#: C/gdm.xml:2849(term) -msgid "MaxPendingIndirect" -msgstr "MaxPendingIndirect" - -#: C/gdm.xml:2851(synopsis) -#, no-wrap -msgid "MaxPendingIndirect=4" -msgstr "MaxPendingIndirect=4" - -#: C/gdm.xml:2852(para) -msgid "GDM will only provide <filename>MaxPendingIndirect</filename> displays with host choosers simultaneously. If more queries from different hosts come in, the oldest ones will be forgotten." -msgstr "GDM will only provide <filename>MaxPendingIndirect</filename> displays with host choosers simultaneously. If more queries from different hosts come in, the oldest ones will be forgotten." - -#: C/gdm.xml:2862(term) -msgid "MaxSessions" -msgstr "MaxSessions" - -#: C/gdm.xml:2864(synopsis) -#, no-wrap -msgid "MaxSessions=16" -msgstr "MaxSessions=16" - -#: C/gdm.xml:2865(para) -msgid "Determines the maximum number of remote display connections which will be managed simultaneously. I.e. the total number of remote displays that can use your host." -msgstr "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." - -#: C/gdm.xml:2874(term) -msgid "MaxWait" -msgstr "MaxWait" - -#: C/gdm.xml:2876(synopsis) -#, no-wrap -msgid "MaxWait=30" -msgstr "MaxWait=30" - -#: C/gdm.xml:2877(para) -msgid "When GDM is ready to manage a display an ACCEPT packet is sent to it containing a unique session id which will be used in future XDMCP conversations." -msgstr "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." - -#: C/gdm.xml:2883(para) -msgid "GDM will then place the session id in the pending queue waiting for the display to respond with a MANAGE request." -msgstr "GDM will then place the session id in the pending queue waiting for the display to respond with a MANAGE request." - -#: C/gdm.xml:2888(para) -msgid "If no response is received within MaxWait seconds, GDM will declare the display dead and erase it from the pending queue freeing up the slot for other displays." -msgstr "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." - -#: C/gdm.xml:2897(term) -msgid "MaxWaitIndirect" -msgstr "MaxWaitIndirect" - -#: C/gdm.xml:2899(synopsis) -#, no-wrap -msgid "MaxWaitIndirect=30" -msgstr "MaxWaitIndirect=30" - -#: C/gdm.xml:2900(para) -msgid "The MaxWaitIndirect parameter determines the maximum number of seconds between the time where a user chooses a host and the subsequent indirect query where the user is connected to the host. When the timeout is exceeded, the information about the chosen host is forgotten and the indirect slot freed up for other displays. The information may be forgotten earlier if there are more hosts trying to send indirect queries then <filename>MaxPendingIndirect</filename>." -msgstr "The MaxWaitIndirect parameter determines the maximum number of seconds between the time where a user chooses a host and the subsequent indirect query where the user is connected to the host. When the timeout is exceeded, the information about the chosen host is forgotten and the indirect slot freed up for other displays. The information may be forgotten earlier if there are more hosts trying to send indirect queries then <filename>MaxPendingIndirect</filename>." - -#: C/gdm.xml:2914(term) -msgid "Port" -msgstr "Port" - -#: C/gdm.xml:2916(synopsis) -#, no-wrap -msgid "Port=177" -msgstr "Port=177" - -#: C/gdm.xml:2917(para) -msgid "The UDP port number <filename>gdm</filename> should listen to for XDMCP requests. Don't change this unless you know what you are doing." -msgstr "The UDP port number <filename>gdm</filename> should listen to for XDMCP requests. Don't change this unless you know what you are doing." - -#: C/gdm.xml:2926(term) -msgid "PingIntervalSeconds" -msgstr "PingIntervalSeconds" - -#: C/gdm.xml:2928(synopsis) -#, no-wrap -msgid "PingIntervalSeconds=15" -msgstr "PingIntervalSeconds=15" - -#: C/gdm.xml:2929(para) -msgid "Interval in which to ping the X server in seconds. If the X server doesn't return before the next time we ping it, the connection is stopped and the session ended. This is a combination of the XDM PingInterval and PingTimeout, but in seconds." -msgstr "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." - -#: C/gdm.xml:2937(para) -msgid "Note that GDM in the past used to have a <filename>PingInterval</filename> configuration key which was also in minutes. For most purposes you'd want this setting to be lower 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 "Note that GDM in the past used to have a <filename>PingInterval</filename> configuration key which was also in minutes. For most purposes you'd want this setting to be lower 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." - -#: C/gdm.xml:2950(term) -msgid "ProxyReconnect" -msgstr "ProxyReconnect" - -#: C/gdm.xml:2952(synopsis) -#, no-wrap -msgid "FlexiProxyReconnect=" -msgstr "FlexiProxyReconnect=" - -#: C/gdm.xml:2953(para) -msgid "Setting this option enables experimental support for session migration with XDMCP sessions. This enables users to disconnect from their session and later reconnect to that same session, possibly from a different terminal." -msgstr "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." - -#: C/gdm.xml:2959(para) -msgid "In order to use this feature, you must have a nested X server available which supports disconnecting from its parent X server and reconnecting to another X server. Currently, the Distributed Multihead X (DMX) server supports this feature to some extent and other projects like NoMachine NX are busy implementing it." -msgstr "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." - -#: C/gdm.xml:2966(para) -msgid "This option should be set to the path of a command which will handle reconnecting the XDMCP proxy to another backend display. A sample implementation for use with DMX is supplied." -msgstr "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." - -#: C/gdm.xml:2975(term) -msgid "ProxyXServer" -msgstr "ProxyXServer" - -#: C/gdm.xml:2977(synopsis) -#, no-wrap -msgid "ProxyXServer=" -msgstr "ProxyXServer=" - -#: C/gdm.xml:2978(para) -msgid "The X server command line for a XDMCP proxy. Any nested X server like Xnest, Xephr or Xdmx should work fairly well." -msgstr "The X server command line for a XDMCP proxy. Any nested X server like Xnest, Xephr or Xdmx should work fairly well." - -#: C/gdm.xml:2986(term) -msgid "Willing" -msgstr "Willing" - -#: C/gdm.xml:2988(synopsis) -#, no-wrap -msgid "Willing=<etc>/gdm/Xwilling" -msgstr "Willing=<etc>/gdm/Xwilling" - -#: C/gdm.xml:2989(para) -msgid "When the machine sends a WILLING packet back after a QUERY it sends a string that gives the current status of this server. The default message is the system ID, but it is possible to create a script that displays customized message. If this script doesn't exist or this key is empty the default message is sent. If this script succeeds and produces some output, the first line of it's output is sent (and only the first line). It runs at most once every 3 seconds to prevent possible denial of service by flooding the machine with QUERY packets." -msgstr "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 customised 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." - -#: C/gdm.xml:3007(title) -msgid "Common GUI Configuration Options" -msgstr "Common GUI Configuration Options" - -#: C/gdm.xml:3010(title) -msgid "[gui]" -msgstr "[gui]" - -#: C/gdm.xml:3013(term) -msgid "AllowGtkThemeChange" -msgstr "AllowGtkThemeChange" - -#: C/gdm.xml:3015(synopsis) -#, no-wrap -msgid "AllowGtkThemeChange=true" -msgstr "AllowGtkThemeChange=true" - -#: C/gdm.xml:3016(para) -msgid "If to allow changing the GTK+ (widget) theme from the greeter. Currently this only affects the standard greeter as the graphical greeter does not yet have this ability. The theme will stay in effect on this display until changed and will affect all the other windows that are put up by GDM. Supported since 2.5.90.2." -msgstr "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." - -#: C/gdm.xml:3028(term) -msgid "GtkRC" -msgstr "GtkRC" - -#: C/gdm.xml:3030(synopsis) -#, no-wrap -msgid "GtkRC=" -msgstr "GtkRC=" - -#: C/gdm.xml:3031(para) -msgid "Path to a <filename>gtkrc</filename> to read when GDM puts up a window. You should really now use the <filename>GtkTheme</filename> key for just setting a theme." -msgstr "Path to a <filename>gtkrc</filename> to read when GDM puts up a window. You should really now use the <filename>GtkTheme</filename> key for just setting a theme." - -#: C/gdm.xml:3040(term) -msgid "GtkTheme" -msgstr "GtkTheme" - -#: C/gdm.xml:3042(synopsis) -#, no-wrap -msgid "GtkTheme=Default" -msgstr "GtkTheme=Default" - -#: C/gdm.xml:3043(para) -msgid "A name of an installed theme to use by default. It will be used in the greeter, chooser and all other GUI windows put up by GDM. Supported since 2.5.90.2." -msgstr "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." - -#: C/gdm.xml:3052(term) -msgid "GtkThemesToAllow" -msgstr "GtkThemesToAllow" - -#: C/gdm.xml:3054(synopsis) -#, no-wrap -msgid "GtkThemesToAllow=all" -msgstr "GtkThemesToAllow=all" - -#: C/gdm.xml:3055(para) -msgid "Comma separated list of themes to allow. These must be the names of the themes installed in the standard locations for GTK+ themes. You can also specify 'all' to allow all installed themes. This is related to the <filename>AllowGtkThemeChange</filename> key. Supported since 2.5.90.2." -msgstr "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 <filename>AllowGtkThemeChange</filename> key. Supported since 2.5.90.2." - -#: C/gdm.xml:3067(term) -msgid "MaxIconWidth" -msgstr "MaxIconWidth" - -#: C/gdm.xml:3069(synopsis) -#, no-wrap -msgid "MaxIconWidth=128" -msgstr "MaxIconWidth=128" - -#: C/gdm.xml:3070(para) -msgid "Specifies the maximum icon width (in pixels) that the face browser will display. Icons larger than this will be scaled. This also affects icons in the XDMCP chooser." -msgstr "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." - -#: C/gdm.xml:3079(term) -msgid "MaxIconHeight" -msgstr "MaxIconHeight" - -#: C/gdm.xml:3081(synopsis) -#, no-wrap -msgid "MaxIconHeight=128" -msgstr "MaxIconHeight=128" - -#: C/gdm.xml:3082(para) -msgid "Specifies the maximum icon height (in pixels) that the face browser will display. Icons larger than this will be scaled. This also affects icons in the XDMCP chooser." -msgstr "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." - -#: C/gdm.xml:3093(title) -msgid "Greeter Configuration" -msgstr "Greeter Configuration" - -#: C/gdm.xml:3096(title) -msgid "[greeter]" -msgstr "[greeter]" - -#: C/gdm.xml:3099(term) -msgid "BackgroundColor" -msgstr "BackgroundColor" - -#: C/gdm.xml:3101(synopsis) -#, no-wrap -msgid "BackgroundColor=#76848F" -msgstr "BackgroundColor=#76848F" - -#: C/gdm.xml:3102(para) -msgid "If the BackgroundType is 2, use this color in the background of the greeter. Also use it as the back of transparent images set on the background and if the BackgroundRemoteOnlyColor is set and this is a remote display. This only affects the GTK+ Greeter." -msgstr "If the BackgroundType is 2, use this colour 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." - -#: C/gdm.xml:3113(term) -msgid "BackgroundProgramInitialDelay" -msgstr "BackgroundProgramInitialDelay" - -#: C/gdm.xml:3115(synopsis) -#, no-wrap -msgid "BackgroundProgramInitialDelay=30" -msgstr "BackgroundProgramInitialDelay=30" - -#: C/gdm.xml:3116(para) -msgid "The background application will be started after at least that many seconds of inactivity." -msgstr "The background application will be started after at least that many seconds of inactivity." - -#: C/gdm.xml:3124(term) -msgid "RestartBackgroundProgram" -msgstr "RestartBackgroundProgram" - -#: C/gdm.xml:3126(synopsis) -#, no-wrap -msgid "RestartBackgroundProgram=true" -msgstr "RestartBackgroundProgram=true" - -#: C/gdm.xml:3127(para) -msgid "If set the background application will be restarted when it has exited, after the delay described below has elapsed. This option can be useful when you wish to run a screen saver application when no user is using the computer." -msgstr "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." - -#: C/gdm.xml:3137(term) -msgid "BackgroundProgramRestartDelay" -msgstr "BackgroundProgramRestartDelay" - -#: C/gdm.xml:3139(synopsis) -#, no-wrap -msgid "BackgroundProgramRestartDelay=30" -msgstr "BackgroundProgramRestartDelay=30" - -#: C/gdm.xml:3140(para) -msgid "The background application will be restarted after at least that many seconds of inactivity." -msgstr "The background application will be restarted after at least that many seconds of inactivity." - -#: C/gdm.xml:3148(term) -msgid "BackgroundImage" -msgstr "BackgroundImage" - -#: C/gdm.xml:3150(synopsis) -#, no-wrap -msgid "BackgroundImage=somefile.png" -msgstr "BackgroundImage=somefile.png" - -#: C/gdm.xml:3151(para) -msgid "If the BackgroundType is 1, then display this file as the background in the greeter. This only affects the GTK+ Greeter." -msgstr "If the BackgroundType is 1, then display this file as the background in the greeter. This only affects the GTK+ Greeter." - -#: C/gdm.xml:3160(term) -msgid "BackgroundProgram" -msgstr "BackgroundProgram" - -#: C/gdm.xml:3162(synopsis) -#, no-wrap -msgid "BackgroundProgram=<bin>/xeyes" -msgstr "BackgroundProgram=<bin>/xeyes" - -#: C/gdm.xml:3163(para) -msgid "If set this command will be run in the background while the login window is being displayed. Note that not all applications will run this way, since GDM does not usually have a home directory. You could set up home directory for the GDM user if you wish to run applications which require it. This only affects the GTK+ Greeter." -msgstr "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." - -#: C/gdm.xml:3175(term) -msgid "BackgroundRemoteOnlyColor" -msgstr "BackgroundRemoteOnlyColor" - -#: C/gdm.xml:3177(synopsis) -#, no-wrap -msgid "BackgroundRemoteOnlyColor=true" -msgstr "BackgroundRemoteOnlyColor=true" - -#: C/gdm.xml:3178(para) -msgid "On remote displays only set the color background. This is to make network load lighter. The <filename>BackgroundProgram</filename> is also not run. This only affects the GTK+ Greeter." -msgstr "On remote displays only set the colour background. This is to make network load lighter. The <filename>BackgroundProgram</filename> is also not run. This only affects the GTK+ Greeter." - -#: C/gdm.xml:3188(term) -msgid "BackgroundScaleToFit" -msgstr "BackgroundScaleToFit" - -#: C/gdm.xml:3190(synopsis) -#, no-wrap -msgid "BackgroundScaleToFit=true" -msgstr "BackgroundScaleToFit=true" - -#: C/gdm.xml:3191(para) -msgid "Scale background image to fit the screen. This only affects the GTK+ Greeter." -msgstr "Scale background image to fit the screen. This only affects the GTK+ Greeter." - -#: C/gdm.xml:3199(term) -msgid "BackgroundType" -msgstr "BackgroundType" - -#: C/gdm.xml:3201(synopsis) -#, no-wrap -msgid "BackgroundType=2" -msgstr "BackgroundType=2" - -#: C/gdm.xml:3202(para) -msgid "The type of background to set. 0 is none, 1 is image and color, 2 is color and 3 is image. This only affects the GTK+ Greeter." -msgstr "The type of background to set. 0 is none, 1 is image and colour, 2 is colour and 3 is image. This only affects the GTK+ Greeter." - -#: C/gdm.xml:3210(term) -msgid "Browser" -msgstr "Browser" - -#: C/gdm.xml:3212(synopsis) -#, no-wrap -msgid "Browser=true" -msgstr "Browser=true" - -#: C/gdm.xml:3213(para) -msgid "Set to true to enable the face browser. See the ``The GTK+ Greeter'' section for more information on the face browser. This option only works for the GTK+ Greeter. For the Themed Greeter, the face browser is enabled by choosing a theme which includes a face browser" -msgstr "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" - -#: C/gdm.xml:3224(term) -msgid "ChooserButton" -msgstr "ChooserButton" - -#: C/gdm.xml:3226(synopsis) -#, no-wrap -msgid "ChooserButton=true" -msgstr "ChooserButton=true" - -#: C/gdm.xml:3227(para) -msgid "If true, add a chooser button to the Actions menu that will restart the current X server with a chooser. XDMCP does not need to be enabled on the local computer for this to work." -msgstr "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." - -#: C/gdm.xml:3236(term) -msgid "ConfigAvailable" -msgstr "ConfigAvailable" - -#: C/gdm.xml:3238(synopsis) -#, no-wrap -msgid "ConfigAvailable=false" -msgstr "ConfigAvailable=false" - -#: C/gdm.xml:3239(para) -msgid "If true, allows the configurator to be run from the greeter. Note that the user will need to type in the root password before the configurator will be started. This is set to false by default for additional security. See the <filename>Configurator</filename> option in the daemon section." -msgstr "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 <filename>Configurator</filename> option in the daemon section." - -#: C/gdm.xml:3251(term) -msgid "DefaultFace" -msgstr "DefaultFace" - -#: C/gdm.xml:3253(synopsis) -#, no-wrap -msgid "DefaultFace=<share>/pixmaps/nophoto.png" -msgstr "DefaultFace=<share>/pixmaps/nophoto.png" - -#: C/gdm.xml:3254(para) -msgid "If a user has no defined face image, GDM will use the \"stock_person\" icon defined in the current GTK+ theme. If no such image is defined, the image specified by <filename>DefaultFace</filename> will be used. The image must be in a gdk-pixbuf supported format and the file must be readable to the GDM user." -msgstr "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 <filename>DefaultFace</filename> will be used. The image must be in a gdk-pixbuf supported format and the file must be readable to the GDM user." - -#: C/gdm.xml:3266(term) -msgid "Include" -msgstr "Include" - -#: C/gdm.xml:3268(synopsis) -#, no-wrap -msgid "Include=" -msgstr "Include=" - -#: C/gdm.xml:3269(para) -msgid "Comma separated list of users to be included in the face browser and in the <command>gdmsetup</command> selection list for Automatic/Timed login. See also <filename>Exclude</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." -msgstr "Comma separated list of users to be included in the face browser and in the <command>gdmsetup</command> selection list for Automatic/Timed login. See also <filename>Exclude</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." - -#: C/gdm.xml:3281(term) -msgid "Exclude" -msgstr "Exclude" - -#: C/gdm.xml:3283(synopsis) -#, no-wrap -msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." -msgstr "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." - -#: C/gdm.xml:3284(para) -msgid "Comma separated list of users to be excluded from the face browser and from the <command>gdmsetup</command> selection list for Automatic/Timed login. Excluded users will still be able to log in, but will have to type their username. See also <filename>Include</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." -msgstr "Comma separated list of users to be excluded from the face browser and from the <command>gdmsetup</command> selection list for Automatic/Timed login. Excluded users will still be able to log in, but will have to type their username. See also <filename>Include</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." - -#: C/gdm.xml:3297(term) -msgid "IncludeAll" -msgstr "IncludeAll" - -#: C/gdm.xml:3299(synopsis) -#, no-wrap -msgid "IncludeAll=false" -msgstr "IncludeAll=false" - -#: C/gdm.xml:3300(para) -msgid "By default, an empty include list means display no users. By setting IncludeAll to true, the password file will be scanned and all users will be displayed aside from users excluded via the Exclude setting and user ID's less than MinimalUID. Scanning the password file can be slow on systems with large numbers of users and this feature should not be used in such environments. See also <filename>Include</filename>, <filename>Exclude</filename>, and <filename>MinimalUID</filename>." -msgstr "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 <filename>Include</filename>, <filename>Exclude</filename>, and <filename>MinimalUID</filename>." - -#: C/gdm.xml:3316(term) -msgid "GlobalFaceDir" -msgstr "GlobalFaceDir" - -#: C/gdm.xml:3318(synopsis) -#, no-wrap -msgid "GlobalFaceDir=<share>/pixmaps/faces/" -msgstr "GlobalFaceDir=<share>/pixmaps/faces/" - -#: C/gdm.xml:3319(para) -msgid "Systemwide directory for face files. The sysadmin can place icons for users here without touching their homedirs. Faces are named after their users' logins." -msgstr "Systemwide directory for face files. The sysadmin can place icons for users here without touching their homedirs. Faces are named after their users' logins." - -#: C/gdm.xml:3325(para) -msgid "I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the face icon for the user ``johndoe''. No image format extension should be specified." -msgstr "I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the face icon for the user ``johndoe''. No image format extension should be specified." - -#: C/gdm.xml:3331(para) -msgid "The face images must be stored in gdk-pixbuf supported formats and they must be readable for the GDM user." -msgstr "The face images must be stored in gdk-pixbuf supported formats and they must be readable for the GDM user." - -#: C/gdm.xml:3336(para) -msgid "A user's own icon file will always take precedence over the sysadmin provided one." -msgstr "A user's own icon file will always take precedence over the sysadmin provided one." - -#: C/gdm.xml:3344(term) -msgid "GraphicalTheme" -msgstr "GraphicalTheme" - -#: C/gdm.xml:3346(synopsis) -#, no-wrap -msgid "GraphicalTheme=circles" -msgstr "GraphicalTheme=circles" - -#: C/gdm.xml:3347(para) -msgid "The graphical theme that the Themed Greeter should use. it should refer to a directory in the theme directory set by <filename>GraphicalThemeDir</filename>." -msgstr "The graphical theme that the Themed Greeter should use. it should refer to a directory in the theme directory set by <filename>GraphicalThemeDir</filename>." - -#: C/gdm.xml:3356(term) -msgid "GraphicalThemes" -msgstr "GraphicalThemes" - -#: C/gdm.xml:3358(synopsis) -#, no-wrap -msgid "GraphicalThemes=circles" -msgstr "GraphicalThemes=circles" - -#: C/gdm.xml:3359(para) -msgid "The graphical themes that the Themed Greeter should use is the Mode is set on Random Themes. This is a \"/:\" delimited list. It should refer to a directory in the theme directory set by <filename>GraphicalThemeDir</filename>. This is only used if <filename>GraphicalThemeRand</filename> is set to true." -msgstr "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 <filename>GraphicalThemeDir</filename>. This is only used if <filename>GraphicalThemeRand</filename> is set to true." - -#: C/gdm.xml:3371(term) -msgid "GraphicalThemeRand" -msgstr "GraphicalThemeRand" - -#: C/gdm.xml:3373(synopsis) -#, no-wrap -msgid "GraphicalThemeRand=false" -msgstr "GraphicalThemeRand=false" - -#: C/gdm.xml:3374(para) -msgid "Whether the graphical greeter will use Only One Theme or Random Theme mode. Only One Theme mode uses themes listed by <filename>GraphicalTheme</filename>, Random Themes mode uses themes listed by <filename>GraphicalThemes</filename>. 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 "Whether the graphical greeter will use Only One Theme or Random Theme mode. Only One Theme mode uses themes listed by <filename>GraphicalTheme</filename>, Random Themes mode uses themes listed by <filename>GraphicalThemes</filename>. A value of false sets greeter to use Only One Theme mode, a value of true sets the greeter to use Random Theme mode." - -#: C/gdm.xml:3386(term) -msgid "GraphicalThemeDir" -msgstr "GraphicalThemeDir" - -#: C/gdm.xml:3388(synopsis) -#, no-wrap -msgid "GraphicalThemeDir=<share>/gdm/themes/" -msgstr "GraphicalThemeDir=<share>/gdm/themes/" - -#: C/gdm.xml:3389(para) -msgid "The directory where themes for the Themed Greeter are installed." -msgstr "The directory where themes for the Themed Greeter are installed." - -#: C/gdm.xml:3397(term) -msgid "GraphicalThemedColor" -msgstr "GraphicalThemedColor" - -#: C/gdm.xml:3399(synopsis) -#, no-wrap -msgid "GraphicalThemedColor=#76848F" -msgstr "GraphicalThemedColor=#76848F" - -#: C/gdm.xml:3400(para) -msgid "Use this color in the background of the Themed Greeter. This only affects the Themed Greeter." -msgstr "Use this colour in the background of the Themed Greeter. This only affects the Themed Greeter." - -#: C/gdm.xml:3408(term) -msgid "InfoMsgFile" -msgstr "InfoMsgFile" - -#: C/gdm.xml:3410(synopsis) -#, no-wrap -msgid "InfoMsgFile=/path/to/infofile" -msgstr "InfoMsgFile=/path/to/infofile" - -#: C/gdm.xml:3411(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 "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 dialogue box before the user is allowed to login. This works both with the standard and the themable greeters." - -#: C/gdm.xml:3422(term) -msgid "InfoMsgFont" -msgstr "InfoMsgFont" - -#: C/gdm.xml:3424(synopsis) -#, no-wrap -msgid "InfoMsgFont=fontspec" -msgstr "InfoMsgFont=fontspec" - -#: C/gdm.xml:3425(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 "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." - -#: C/gdm.xml:3437(term) -msgid "LocaleFile" -msgstr "LocaleFile" - -#: C/gdm.xml:3439(synopsis) -#, no-wrap -msgid "LocaleFile=<etc>/gdm/locale.alias" -msgstr "LocaleFile=<etc>/gdm/locale.alias" - -#: C/gdm.xml:3440(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 "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." - -#: C/gdm.xml:3449(term) -msgid "LockPosition" -msgstr "LockPosition" - -#: C/gdm.xml:3451(synopsis) -#, no-wrap -msgid "LockPosition=true" -msgstr "LockPosition=true" - -#: C/gdm.xml:3452(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 "If true the position of the login window of the GTK+ Greeter cannot be changed even if the title bar is turned on." - -#: C/gdm.xml:3460(term) -msgid "Logo" -msgstr "Logo" - -#: C/gdm.xml:3462(synopsis) -#, no-wrap -msgid "Logo=<share>/pixmaps/gnome-logo-large.png" -msgstr "Logo=<share>/pixmaps/gnome-logo-large.png" - -#: C/gdm.xml:3463(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 "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." - -#: C/gdm.xml:3474(term) -msgid "ChooserButtonLogo" -msgstr "ChooserButtonLogo" - -#: C/gdm.xml:3476(synopsis) -#, no-wrap -msgid "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" -msgstr "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" - -#: C/gdm.xml:3477(para) -msgid "Image file to display in the file chooser button in <command>gdmsetup</command>. This key is modified by <command>gdmsetup</command> and should not be manually modified by the user. This only affects the Login Window Preferences (<command>gdmsetup</command>)." -msgstr "Image file to display in the file chooser button in <command>gdmsetup</command>. This key is modified by <command>gdmsetup</command> and should not be manually modified by the user. This only affects the login window preferences (<command>gdmsetup</command>)." - -#: C/gdm.xml:3488(term) -msgid "MinimalUID" -msgstr "MinimalUID" - -#: C/gdm.xml:3490(synopsis) -#, no-wrap -msgid "MinimalUID=100" -msgstr "MinimalUID=100" - -#: C/gdm.xml:3491(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 <filename>Include</filename>, <filename>Exclude</filename>, and <filename>IncludeAll</filename>." -msgstr "The minimal UID that GDM should consider a user. All users with a lower UID will be excluded from the face browser. See also <filename>Include</filename>, <filename>Exclude</filename>, and <filename>IncludeAll</filename>." - -#: C/gdm.xml:3502(term) -msgid "PositionX" -msgstr "PositionX" - -#: C/gdm.xml:3504(synopsis) -#, no-wrap -msgid "PositionX=200" -msgstr "PositionX=200" - -#: C/gdm.xml:3505(para) -msgid "The horizontal position of the login window of the GTK+ Greeter." -msgstr "The horizontal position of the login window of the GTK+ Greeter." - -#: C/gdm.xml:3513(term) -msgid "PositionY" -msgstr "PositionY" - -#: C/gdm.xml:3515(synopsis) -#, no-wrap -msgid "PositionY=100" -msgstr "PositionY=100" - -#: C/gdm.xml:3516(para) -msgid "The vertical position of the login window of the GTK+ Greeter." -msgstr "The vertical position of the login window of the GTK+ Greeter." - -#: C/gdm.xml:3524(term) -msgid "Quiver" -msgstr "Quiver" - -#: C/gdm.xml:3526(synopsis) -#, no-wrap -msgid "Quiver=true" -msgstr "Quiver=true" - -#: C/gdm.xml:3527(para) -msgid "Controls whether <command>gdmlogin</command> should shake the display when an incorrect username/password is entered. This only affects the GTK+ Greeter." -msgstr "Controls whether <command>gdmlogin</command> should shake the display when an incorrect username/password is entered. This only affects the GTK+ Greeter." - -#: C/gdm.xml:3537(term) -msgid "DefaultRemoteWelcome" -msgstr "DefaultRemoteWelcome" - -#: C/gdm.xml:3539(synopsis) -#, no-wrap -msgid "DefaultRemoteWelcome=true" -msgstr "DefaultRemoteWelcome=true" - -#: C/gdm.xml:3540(para) -msgid "If set to true, the value \"Welcome to %n\" is used for the <filename>RemoteWelcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>RemoteWelcome</filename> 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 "If set to true, the value \"Welcome to %n\" is used for the <filename>RemoteWelcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>RemoteWelcome</filename> 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\"." - -#: C/gdm.xml:3554(term) -msgid "RemoteWelcome" -msgstr "RemoteWelcome" - -#: C/gdm.xml:3556(synopsis) -#, no-wrap -msgid "RemoteWelcome=Welcome to %n" -msgstr "RemoteWelcome=Welcome to %n" - -#: C/gdm.xml:3557(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 <filename>Welcome</filename> string. This string can use the same special character sequences as explained in the \"Text Node\" section of the \"Themed Greeter\" chapter. chapter." -msgstr "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 <filename>Welcome</filename> string. This string can use the same special character sequences as explained in the \"Text Node\" section of the \"Themed Greeter\" chapter. chapter." - -#: C/gdm.xml:3570(term) -msgid "RunBackgroundProgramAlways" -msgstr "RunBackgroundProgramAlways" - -#: C/gdm.xml:3572(synopsis) -#, no-wrap -msgid "RunBackgroundProgramAlways=false" -msgstr "RunBackgroundProgramAlways=false" - -#: C/gdm.xml:3573(para) -msgid "If this is true then the background application is run always, otherwise it is only run when the <filename>BackgroundType</filename> is 0 (None) This only affects the GTK+ Greeter." -msgstr "If this is true then the background application is run always, otherwise it is only run when the <filename>BackgroundType</filename> is 0 (None) This only affects the GTK+ Greeter." - -#: C/gdm.xml:3583(term) -msgid "SetPosition" -msgstr "SetPosition" - -#: C/gdm.xml:3585(synopsis) -#, no-wrap -msgid "SetPosition=true" -msgstr "SetPosition=true" - -#: C/gdm.xml:3586(para) -msgid "If true the position of the login window of the GTK+ Greeter is determined by <filename>PositionX</filename> / <filename>PositionY</filename>." -msgstr "If true the position of the login window of the GTK+ Greeter is determined by <filename>PositionX</filename> / <filename>PositionY</filename>." - -#: C/gdm.xml:3595(term) -msgid "ShowGnomeFailsafeSession" -msgstr "ShowGnomeFailsafeSession" - -#: C/gdm.xml:3597(synopsis) -#, no-wrap -msgid "ShowGnomeFailsafeSession=true" -msgstr "ShowGnomeFailsafeSession=true" - -#: C/gdm.xml:3598(para) -msgid "Should the greeter show the Gnome Failsafe session in th sessions list." -msgstr "Should the greeter show the Gnome Failsafe session in th sessions list." - -#: C/gdm.xml:3606(term) -msgid "ShowLastSession" -msgstr "ShowLastSession" - -#: C/gdm.xml:3608(synopsis) -#, no-wrap -msgid "ShowLastSession=true" -msgstr "ShowLastSession=true" - -#: C/gdm.xml:3609(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 <filename>DefaultSession</filename>) unless then pick something else for this session only. So if this is off, this really circumvents saving of the last session." -msgstr "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 <filename>DefaultSession</filename>) unless then pick something else for this session only. So if this is off, this really circumvents saving of the last session." - -#: C/gdm.xml:3622(term) -msgid "ShowXtermFailsafeSession" -msgstr "ShowXtermFailsafeSession" - -#: C/gdm.xml:3624(synopsis) -#, no-wrap -msgid "ShowXtermFailsafeSession=true" -msgstr "ShowXtermFailsafeSession=true" - -#: C/gdm.xml:3625(para) -msgid "Should the greeter show the Xterm Failsafe session in the sessions list." -msgstr "Should the greeter show the Xterm Failsafe session in the sessions list." - -#: C/gdm.xml:3633(term) -msgid "SoundOnLogin" -msgstr "SoundOnLogin" - -#: C/gdm.xml:3635(synopsis) -#, no-wrap -msgid "SoundOnLogin=true" -msgstr "SoundOnLogin=true" - -#: C/gdm.xml:3636(para) -msgid "If true, the greeter will play a sound or beep when it is ready for a login. See also the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0." -msgstr "If true, the greeter will play a sound or beep when it is ready for a login. See also the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0." - -#: C/gdm.xml:3646(term) -msgid "SoundOnLoginSuccess" -msgstr "SoundOnLoginSuccess" - -#: C/gdm.xml:3648(synopsis) -#, no-wrap -msgid "SoundOnLoginSuccess=true" -msgstr "SoundOnLoginSuccess=true" - -#: C/gdm.xml:3649(para) -msgid "If true, the greeter will play a sound after a successful login attempt. See also the <filename>SoundOnLoginSuccessFile</filename> key." -msgstr "If true, the greeter will play a sound after a successful login attempt. See also the <filename>SoundOnLoginSuccessFile</filename> key." - -#: C/gdm.xml:3658(term) -msgid "SoundOnLoginFailure" -msgstr "SoundOnLoginFailure" - -#: C/gdm.xml:3660(synopsis) -#, no-wrap -msgid "SoundOnLoginFailure=true" -msgstr "SoundOnLoginFailure=true" - -#: C/gdm.xml:3661(para) -msgid "If true, the greeter will play a sound after a failed login attempt. See also the <filename>SoundOnLoginFailureFile</filename> key." -msgstr "If true, the greeter will play a sound after a failed login attempt. See also the <filename>SoundOnLoginFailureFile</filename> key." - -#: C/gdm.xml:3670(term) -msgid "SoundOnLoginFile" -msgstr "SoundOnLoginFile" - -#: C/gdm.xml:3672(synopsis) -#, no-wrap -msgid "SoundOnLoginFile=/path/to/sound.wav" -msgstr "SoundOnLoginFile=/path/to/sound.wav" - -#: C/gdm.xml:3673(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) instead of a beep when the greeter is ready for a login. See also the <filename>SoundOnLogin</filename> key and the <filename>SoundProgram</filename> key. Supported since 2.5.90.0." -msgstr "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) instead of a beep when the greeter is ready for a login. See also the <filename>SoundOnLogin</filename> key and the <filename>SoundProgram</filename> key. Supported since 2.5.90.0." - -#: C/gdm.xml:3686(term) -msgid "SoundOnLoginSuccessFile" -msgstr "SoundOnLoginSuccessFile" - -#: C/gdm.xml:3688(synopsis) -#, no-wrap -msgid "SoundOnLoginSuccessFile=/path/to/sound.wav" -msgstr "SoundOnLoginSuccessFile=/path/to/sound.wav" - -#: C/gdm.xml:3689(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a successful login attempt. See also the <filename>SoundOnLoginSuccess</filename> key and the <filename>SoundProgram</filename> key." -msgstr "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a successful login attempt. See also the <filename>SoundOnLoginSuccess</filename> key and the <filename>SoundProgram</filename> key." - -#: C/gdm.xml:3700(term) -msgid "SoundOnLoginFailureFile" -msgstr "SoundOnLoginFailureFile" - -#: C/gdm.xml:3702(synopsis) -#, no-wrap -msgid "SoundOnLoginFailureFile=/path/to/sound.wav" -msgstr "SoundOnLoginFailureFile=/path/to/sound.wav" - -#: C/gdm.xml:3703(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a failed login attempt. See also the <filename>SoundOnLoginFailure</filename> key and the <filename>SoundProgram</filename> key." -msgstr "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a failed login attempt. See also the <filename>SoundOnLoginFailure</filename> key and the <filename>SoundProgram</filename> key." - -#: C/gdm.xml:3714(term) -msgid "SystemMenu" -msgstr "SystemMenu" - -#: C/gdm.xml:3716(synopsis) -#, no-wrap -msgid "SystemMenu=true" -msgstr "SystemMenu=true" - -#: C/gdm.xml:3717(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 "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 etc. All of those can 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." - -#: C/gdm.xml:3730(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 "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." - -#: C/gdm.xml:3741(term) -msgid "TitleBar" -msgstr "TitleBar" - -#: C/gdm.xml:3743(synopsis) -#, no-wrap -msgid "TitleBar=true" -msgstr "TitleBar=true" - -#: C/gdm.xml:3744(para) -msgid "Display the title bar in the greeter. This only affects the GTK+ Greeter." -msgstr "Display the title bar in the greeter. This only affects the GTK+ Greeter." - -#: C/gdm.xml:3752(term) -msgid "Use24Clock" -msgstr "Use24Clock" - -#: C/gdm.xml:3754(synopsis) -#, no-wrap -msgid "Use24Clock=auto" -msgstr "Use24Clock=auto" - -#: C/gdm.xml:3755(para) -msgid "Select the use of 24 hour clock. Some locales do not support 12 hour format (like Finnish, that is <filename>fi_FI</filename>), and in those locales this setting has no effect at all." -msgstr "Select the use of 24 hour clock. Some locales do not support 12 hour format (like Finnish, that is <filename>fi_FI</filename>), and in those locales this setting has no effect at all." - -#: C/gdm.xml:3761(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 "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." - -#: C/gdm.xml:3776(term) -msgid "UseCirclesInEntry" -msgstr "UseCirclesInEntry" - -#: C/gdm.xml:3778(synopsis) -#, no-wrap -msgid "UseCirclesInEntry=false" -msgstr "UseCirclesInEntry=false" - -#: C/gdm.xml:3779(para) -msgid "Use circles instead of asterisks in the password entry. This may not work with all fonts however." -msgstr "Use circles instead of asterisks in the password entry. This may not work with all fonts however." - -#: C/gdm.xml:3787(term) -msgid "UseInvisibleInEntry" -msgstr "UseInvisibleInEntry" - -#: C/gdm.xml:3789(synopsis) -#, no-wrap -msgid "UseInvisibleInEntry=false" -msgstr "UseInvisibleInEntry=false" - -#: C/gdm.xml:3790(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 <filename>UseCirclesInEntry</filename> option." -msgstr "Do not show any visual feedback is the password entry. This is the standard in console and xdm. Settings this option discards the <filename>UseCirclesInEntry</filename> option." - -#: C/gdm.xml:3800(term) -msgid "DefaultWelcome" -msgstr "DefaultWelcome" - -#: C/gdm.xml:3802(synopsis) -#, no-wrap -msgid "DefaultWelcome=true" -msgstr "DefaultWelcome=true" - -#: C/gdm.xml:3803(para) -msgid "If set to true, the value \"Welcome\" is used for the <filename>Welcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>Welcome</filename> setting is used." -msgstr "If set to true, the value \"Welcome\" is used for the <filename>Welcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>Welcome</filename> setting is used." - -#: C/gdm.xml:3813(term) -msgid "Welcome" -msgstr "Welcome" - -#: C/gdm.xml:3815(synopsis) -#, no-wrap -msgid "Welcome=Welcome" -msgstr "Welcome=Welcome" - -#: C/gdm.xml:3816(para) -msgid "Controls which text to display next to the logo image in the standard greeter. The following control chars are supported:" -msgstr "Controls which text to display next to the logo image in the standard greeter. The following control chars are supported:" - -#: C/gdm.xml:3825(para) -msgid "%d — display's hostname" -msgstr "%d — display's hostname" - -#: C/gdm.xml:3829(para) -msgid "%h — Fully qualified hostname" -msgstr "%h — Fully qualified hostname" - -#: C/gdm.xml:3833(para) -msgid "%m — machine (processor type)" -msgstr "%m — machine (processor type)" - -#: C/gdm.xml:3837(para) -msgid "%n — Nodename (i.e. hostname without .domain)" -msgstr "%n — Nodename (i.e. hostname without .domain)" - -#: C/gdm.xml:3841(para) -msgid "%r — release (OS version)" -msgstr "%r — release (OS version)" - -#: C/gdm.xml:3845(para) -msgid "%s — sysname (i.e. OS)" -msgstr "%s — sysname (i.e. OS)" - -#: C/gdm.xml:3849(para) -msgid "This string is only used for local logins. For remote XDMCP logins we use <filename>RemoteWelcome</filename>." -msgstr "This string is only used for local logins. For remote XDMCP logins we use <filename>RemoteWelcome</filename>." - -#: C/gdm.xml:3854(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 "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." - -#: C/gdm.xml:3864(term) -msgid "XineramaScreen" -msgstr "XineramaScreen" - -#: C/gdm.xml:3866(synopsis) -#, no-wrap -msgid "XineramaScreen=0" -msgstr "XineramaScreen=0" - -#: C/gdm.xml:3867(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 "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...)." - -#: C/gdm.xml:3878(title) -msgid "XDCMP Chooser Options" -msgstr "XDCMP Chooser Options" - -#: C/gdm.xml:3881(title) -msgid "[chooser]" -msgstr "[chooser]" - -#: C/gdm.xml:3884(term) -msgid "AllowAdd" -msgstr "AllowAdd" - -#: C/gdm.xml:3886(synopsis) -#, no-wrap -msgid "AllowAdd=true" -msgstr "AllowAdd=true" - -#: C/gdm.xml:3887(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 "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." - -#: C/gdm.xml:3896(term) -msgid "Broadcast" -msgstr "Broadcast" - -#: C/gdm.xml:3898(synopsis) -#, no-wrap -msgid "Broadcast=true" -msgstr "Broadcast=true" - -#: C/gdm.xml:3899(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 <filename>Hosts</filename> key." -msgstr "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 <filename>Hosts</filename> key." - -#: C/gdm.xml:3911(term) -msgid "Multicast" -msgstr "Multicast" - -#: C/gdm.xml:3913(synopsis) -#, no-wrap -msgid "Multicast=true" -msgstr "Multicast=true" - -#: C/gdm.xml:3914(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 <filename>Hosts </filename> key. The host will respond if it is listening to XDMCP requests and IPv6 is enabled there." -msgstr "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 <filename>Hosts </filename> key. The host will respond if it is listening to XDMCP requests and IPv6 is enabled there." - -#: C/gdm.xml:3926(term) -msgid "MulticastAddr" -msgstr "MulticastAddr" - -#: C/gdm.xml:3928(synopsis) -#, no-wrap -msgid "MulticastAddr=ff02::1" -msgstr "MulticastAddr=ff02::1" - -#: C/gdm.xml:3929(para) -msgid "This is the Link-local Multicast address and is hardcoded here." -msgstr "This is the Link-local Multicast address and is hardcoded here." - -#: C/gdm.xml:3936(term) -msgid "DefaultHostImage" -msgstr "DefaultHostImage" - -#: C/gdm.xml:3938(synopsis) -#, no-wrap -msgid "DefaultHostImage=<share>/pixmaps/nohost.png" -msgstr "DefaultHostImage=<share>/pixmaps/nohost.png" - -#: C/gdm.xml:3939(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 "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." - -#: C/gdm.xml:3949(term) -msgid "HostImageDir" -msgstr "HostImageDir" - -#: C/gdm.xml:3951(synopsis) -#, no-wrap -msgid "HostImageDir=<share>/hosts" -msgstr "HostImageDir=<share>/hosts" - -#: C/gdm.xml:3952(para) -msgid "Repository for host icon files. The sysadmin can place icons for remote hosts here and they will appear in <filename>gdmchooser</filename>." -msgstr "Repository for host icon files. The sysadmin can place icons for remote hosts here and they will appear in <filename>gdmchooser</filename>." - -#: C/gdm.xml:3958(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 "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." - -#: C/gdm.xml:3968(term) -msgid "Hosts" -msgstr "Hosts" - -#: C/gdm.xml:3970(synopsis) -#, no-wrap -msgid "Hosts=host1,host2" -msgstr "Hosts=host1,host2" - -#: C/gdm.xml:3971(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 <filename>Broadcast</filename> 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 "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 <filename>Broadcast</filename> 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." - -#: C/gdm.xml:3983(term) -msgid "ScanTime" -msgstr "ScanTime" - -#: C/gdm.xml:3985(synopsis) -#, no-wrap -msgid "ScanTime=4" -msgstr "ScanTime=4" - -#: C/gdm.xml:3986(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 "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." - -#: C/gdm.xml:3998(title) -msgid "Debug Configuration" -msgstr "Debug Configuration" - -#: C/gdm.xml:4001(title) -msgid "[debug]" -msgstr "[debug]" - -#: C/gdm.xml:4007(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 "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." - -#: C/gdm.xml:4017(term) -msgid "Gestures" -msgstr "Gestures" - -#: C/gdm.xml:4019(synopsis) -#, no-wrap -msgid "Gestures=false" -msgstr "Gestures=false" - -#: C/gdm.xml:4020(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 "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." - -#: C/gdm.xml:4033(title) -msgid "Custom Commands" -msgstr "Custom Commands" - -#: C/gdm.xml:4035(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 "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]." - -#: C/gdm.xml:4044(title) -msgid "[customcommand]" -msgstr "[customcommand]" - -#: C/gdm.xml:4047(term) -msgid "CustomCommand[0-9]" -msgstr "CustomCommand[0-9]" - -#: C/gdm.xml:4049(synopsis) -#, no-wrap -msgid "CustomCommand[0-9]=" -msgstr "CustomCommand[0-9]=" - -#: C/gdm.xml:4050(para) -msgid "Full path and arguments to command to be executed when user selects <filename>n-th</filename> \"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 <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "Full path and arguments to command to be executed when user selects the <filename>n-th</filename> \"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 <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." - -#: C/gdm.xml:4065(term) -msgid "CustomCommandIsPersistent[0-9]" -msgstr "CustomCommandIsPersistent[0-9]" - -#: C/gdm.xml:4067(synopsis) -#, no-wrap -msgid "CustomCommandIsPersistent[0-9]=" -msgstr "CustomCommandIsPersistent[0-9]=" - -#: C/gdm.xml:4068(para) -msgid "Specifies if <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "Specifies if the <filename>n-th</filename> \"Custom Command\" will appear outside the login manager, for example on the desktop through the Log Out/Shut Down dialogues. If not specified the default value is \"false\". This option is only valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." - -#: C/gdm.xml:4082(term) -msgid "CustomCommandLabel[0-9]" -msgstr "CustomCommandLabel[0-9]" - -#: C/gdm.xml:4084(synopsis) -#, no-wrap -msgid "CustomCommandLabel[0-9]=" -msgstr "CustomCommandLabel[0-9]=" - -#: C/gdm.xml:4085(para) -msgid "Specifies the stock label that will be displayed on the <filename>n-th</filename> \"Custom Command\" buttons and menu items. If not specified the default value is \"Custom_[0-9]\". This option is only valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9. This option can't contain any semicolon characters (i.e. \";\")." -msgstr "Specifies the stock label that will be displayed on the <filename>n-th</filename> \"Custom Command\" buttons and menu items. If not specified the default value is \"Custom_[0-9]\". This option is only valid if the corresponding <filename>CustomCommand</filename> is defined. [0-9] represents the <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9. This option can't contain any semicolon characters (i.e. \";\")." - -#: C/gdm.xml:4099(term) -msgid "CustomCommandLRLabel[0-9]" -msgstr "CustomCommandLRLabel[0-9]" - -#: C/gdm.xml:4101(synopsis) -#, no-wrap -msgid "CustomCommandLRLabel[0-9]=" -msgstr "CustomCommandLRLabel[0-9]=" - -#: C/gdm.xml:4102(para) -msgid "Specifies the stock label that will be displayed on the <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "Specifies the stock label that will be displayed on the <filename>n-th</filename> \"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 the corresponding <filename>CustomCommand</filename> is defined. [0-9] represents the <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." - -#: C/gdm.xml:4116(term) -msgid "CustomCommandNoRestart[0-9]" -msgstr "CustomCommandNoRestart[0-9]" - -#: C/gdm.xml:4118(synopsis) -#, no-wrap -msgid "CustomCommandNoRestart[0-9]=" -msgstr "CustomCommandNoRestart[0-9]=" - -#: C/gdm.xml:4119(para) -msgid "Specifies if gdm will be stopped/restarted once <filename>n-th</filename> \"Custom Command\" has been executed. If not specified the default value is \"false\". This option is only valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9. In addition when corresponding <filename>CustomCommandIsPersistent</filename> is set to true, setting CustomCommandNoRestart to false will place corresponding <filename>CustomCommand</filename> in the Shut Down dialog set of actions, setting it to true will place corresponding <filename>CustomCommand</filename> in the Log Out dialog set of actions." -msgstr "Specifies if gdm will be stopped/restarted once the <filename>n-th</filename> \"Custom Command\" has been executed. If not specified the default value is \"false\". This option is only valid if the corresponding <filename>CustomCommand</filename> is defined. [0-9] represents the <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9. When the corresponding <filename>CustomCommandIsPersistent</filename> is set to true, setting CustomCommandNoRestart to false will place the corresponding <filename>CustomCommand</filename> in the Shut Down dialogue set of actions. Setting it to true will place the corresponding <filename>CustomCommand</filename> in the Log Out dialogue set of actions." - -#: C/gdm.xml:4139(term) -msgid "CustomCommandText[0-9]" -msgstr "CustomCommandText[0-9]" - -#: C/gdm.xml:4141(synopsis) -#, no-wrap -msgid "CustomCommandText[0-9]=" -msgstr "CustomCommandText[0-9]=" - -#: C/gdm.xml:4142(para) -msgid "Specifies the message that will be displayed on the warning dialog box once <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "Specifies the message that will be displayed on the warning dialogue box once the <filename>n-th</filename> \"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 the corresponding <filename>CustomCommand</filename> is defined. [0-9] represents the <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." - -#: C/gdm.xml:4156(term) -msgid "CustomCommandTooltip[0-9]" -msgstr "CustomCommandTooltip[0-9]" - -#: C/gdm.xml:4158(synopsis) -#, no-wrap -msgid "CustomCommandTooltip[0-9]=" -msgstr "CustomCommandTooltip[0-9]=" - -#: C/gdm.xml:4159(para) -msgid "Specifies the message that will be displayed on tooltips for <filename>n-th</filename> \"Custom Command\" entries. If not specified the default value is \"Execute custom command [0-9]\". This option is only valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "Specifies the message that will be displayed on tooltips for <filename>n-th</filename> \"Custom Command\" entries. If not specified the default value is \"Execute custom command [0-9]\". This option is only valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." - -#: C/gdm.xml:4174(title) -msgid "X Server Definitions" -msgstr "X Server Definitions" - -#: C/gdm.xml:4176(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 <filename>Standard</filename> is required. If you do not specify this server, GDM will assume default values for a 'Standard' server and the path given by <filename>daemon/StandardXServer</filename>. <filename>Standard</filename> is used as the default, in situations when no other server has been defined." -msgstr "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 <filename>Standard</filename> is required. If you do not specify this server, GDM will assume default values for a 'Standard' server and the path given by <filename>daemon/StandardXServer</filename>. <filename>Standard</filename> is used as the default, in situations when no other server has been defined." - -#: C/gdm.xml:4187(para) -msgid "Servers are defined by sections named <filename>server-</filename> 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, <filename>server-</filename> sections in the <filename><etc>/gdm/custom.conf</filename> file override values in the <filename><share>/gdm/defaults.conf</filename> file. In other words, if a <filename>server-Standard</filename> section is defined in <filename><etc>/gdm/custom.conf</filename>, then that will be used and the section in the <filename><share>/gdm/defaults.conf</filename> file will be ignored." -msgstr "Servers are defined by sections named <filename>server-</filename> 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, <filename>server-</filename> sections in the <filename><etc>/gdm/custom.conf</filename> file override values in the <filename><share>/gdm/defaults.conf</filename> file. In other words, if a <filename>server-Standard</filename> section is defined in <filename><etc>/gdm/custom.conf</filename>, then that will be used and the section in the <filename><share>/gdm/defaults.conf</filename> file will be ignored." - -#: C/gdm.xml:4205(title) -msgid "[server-Standard]" -msgstr "[server-Standard]" - -#: C/gdm.xml:4208(term) -msgid "name" -msgstr "name" - -#: C/gdm.xml:4210(synopsis) -#, no-wrap -msgid "name=Standard server" -msgstr "name=Standard server" - -#: C/gdm.xml:4211(para) -msgid "The name that will be displayed to the user." -msgstr "The name that will be displayed to the user." - -#: C/gdm.xml:4218(term) -msgid "command" -msgstr "command" - -#: C/gdm.xml:4220(synopsis) -#, no-wrap -msgid "command=/path/to/X" -msgstr "command=/path/to/X" - -#: C/gdm.xml:4221(para) -msgid "The command to execute, with full path to the binary of the X server, and any extra arguments needed." -msgstr "The command to execute, with full path to the binary of the X server, and any extra arguments needed." - -#: C/gdm.xml:4229(term) -msgid "flexible" -msgstr "flexible" - -#: C/gdm.xml:4231(synopsis) -#, no-wrap -msgid "flexible=true" -msgstr "flexible=true" - -#: C/gdm.xml:4232(para) -msgid "Indicates if this server is available as a choice when a user wishes to run a flexible, on demand server." -msgstr "Indicates if this server is available as a choice when a user wishes to run a flexible, on demand server." - -#: C/gdm.xml:4240(term) -msgid "handled" -msgstr "handled" - -#: C/gdm.xml:4242(synopsis) -#, no-wrap -msgid "handled=true" -msgstr "handled=true" - -#: C/gdm.xml:4243(para) -msgid "Indicates that GDM should run the login window on this server and allow a user to log in. If set to false, then GDM will just run this server and wait for it to terminate. This can be useful to run an X terminal using GDM. When this is done you should normally also add <filename>-terminate</filename> to the command line of the server to make the server terminate after each session. Otherwise the control of the slave will never come back to GDM and, for example, soft restarts won't work. This is because GDM assumes there is a login in progress for the entire time this server is active." -msgstr "Indicates that GDM should run the login window on this server and allow a user to log in. If set to false, then GDM will just run this server and wait for it to terminate. This can be useful to run an X terminal using GDM. When this is done you should normally also add <filename>-terminate</filename> to the command line of the server to make the server terminate after each session. Otherwise the control of the slave will never come back to GDM and, for example, soft restarts won't work. This is because GDM assumes there is a login in progress for the entire time this server is active." - -#: C/gdm.xml:4259(term) -msgid "chooser" -msgstr "chooser" - -#: C/gdm.xml:4261(synopsis) -#, no-wrap -msgid "chooser=false" -msgstr "chooser=false" - -#: C/gdm.xml:4262(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 "Indicates that GDM should run a chooser on this window, instead of a login window, and allow the user to choose which server to log into." - -#: C/gdm.xml:4273(title) -msgid "Local Static X Display Configuration" -msgstr "Local Static X Display Configuration" - -#: C/gdm.xml:4275(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 <filename>[servers]</filename> section corresponds to the display number to be managed. Normally there is only one key, which is the key <filename>0</filename>, which corresponds to the display <filename>:0</filename>." -msgstr "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 <filename>[servers]</filename> section corresponds to the display number to be managed. Normally there is only one key, which is the key <filename>0</filename>, which corresponds to the display <filename>:0</filename>." - -#: C/gdm.xml:4290(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 <filename>[servers]</filename> section in the <filename><etc>/gdm/custom.conf</filename> file overrides values in the <filename><share>/gdm/defaults.conf</filename> file." -msgstr "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 <filename>[servers]</filename> section in the <filename><etc>/gdm/custom.conf</filename> file overrides values in the <filename><share>/gdm/defaults.conf</filename> file." - -#: C/gdm.xml:4301(title) -msgid "[servers]" -msgstr "[servers]" - -#: C/gdm.xml:4304(term) -msgid "<display number>" -msgstr "<display number>" - -#: C/gdm.xml:4306(synopsis) -#, no-wrap -msgid "0=Standard" -msgstr "0=Standard" - -#: C/gdm.xml:4307(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 "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)." - -#: C/gdm.xml:4313(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 <filename><etc>/gdm/custom.conf</filename> to turn off a display that is defined in the <filename><share>/gdm/defaults.conf</filename> file." -msgstr "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 <filename><etc>/gdm/custom.conf</filename> to turn off a display that is defined in the <filename><share>/gdm/defaults.conf</filename> file." - -#: C/gdm.xml:4327(para) -msgid "GDM will splice \"<filename>-auth <ServAuthDir>/:n.Xauth :n</filename>\", where n is the display number. Inside the command line before all other arguments before running the X server." -msgstr "GDM will splice \"<filename>-auth <ServAuthDir>/:n.Xauth :n</filename>\" (where n is the display number) inside the command line before all other arguments before running the X server." - -#: C/gdm.xml:4334(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 <filename>VTAllocation</filename> key is set." -msgstr "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 <filename>VTAllocation</filename> key is set." - -#: C/gdm.xml:4343(para) -msgid "Normally you do not need to add a <filename>-nolisten tcp</filename> flag as this is added automatically for local X servers when the <filename>DisallowTCP</filename> option is set." -msgstr "Normally you do not need to add a <filename>-nolisten tcp</filename> flag as this is added automatically for local X servers when the <filename>DisallowTCP</filename> option is set." - -#: C/gdm.xml:4353(term) -msgid "priority" -msgstr "priority" - -#: C/gdm.xml:4355(synopsis) -#, no-wrap -msgid "priority=0" -msgstr "priority=0" - -#: C/gdm.xml:4356(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 "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." - -#: C/gdm.xml:4372(title) -msgid "Per User Configuration" -msgstr "Per User Configuration" - -#: C/gdm.xml:4374(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 <filename>UserMaxFile</filename> 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 "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 permissions. 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 permissions. Files must also be smaller than the <filename>UserMaxFile</filename> value as defined in the GDM configuration. If GDM is not properly accessing user configuration settings, the problem is most likely caused by one of these checks failing." - -#: C/gdm.xml:4388(para) -msgid "First there is the <filename>~/.dmrc</filename> file. In theory this file should be shared between GDM and KDM, so users only have to configure things once. This is a standard <filename>.ini</filename> style configuration file. It has one section called <filename>[Desktop]</filename> which has two keys: <filename>Session</filename> and <filename>Language</filename>." -msgstr "First there is the <filename>~/.dmrc</filename> file. In theory this file should be shared between GDM and KDM, so users only have to configure things once. This is a standard <filename>.ini</filename> style configuration file. It has one section called <filename>[Desktop]</filename> which has two keys: <filename>Session</filename> and <filename>Language</filename>." - -#: C/gdm.xml:4397(para) -msgid "The <filename>Session</filename> key specifies the basename of the session <filename>.desktop</filename> file that the user wishes to normally use (without the <filename>.desktop</filename> extension, in other words). The <filename>Language</filename> key specifies the language that the user wishes to use by default. If either of these keys is missing, the system default is used. The file would normally look as follows:" -msgstr "The <filename>Session</filename> key specifies the basename of the session <filename>.desktop</filename> file that the user wishes to normally use (without the <filename>.desktop</filename> extension, in other words). The <filename>Language</filename> key specifies the language that the user wishes to use by default. If either of these keys is missing, the system default is used. The file would normally look as follows:" - -#: C/gdm.xml:4407(screen) -#, no-wrap -msgid "" -"\n" -"[Desktop]\n" -"Session=gnome\n" -"Language=cs_CZ.UTF-8\n" -msgstr "" -"\n" -"[Desktop]\n" -"Session=gnome\n" -"Language=cs_CZ.UTF-8\n" - -#: C/gdm.xml:4413(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 "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." - -#: C/gdm.xml:4419(para) -msgid "If the GDM Face Browser is turned, then the file <filename>$HOME/.face</filename> 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 <filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> values defined in the GDM configuration or it will be ignored. Users can run the <command>gdmphotosetup</command> program to specify a face image and it will copy the file to the <filename>$HOME/.face</filename> location and scale it so its longest dimension is not larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> values. <command>gdmphotosetup</command> takes care to not change the aspect ratio of the image." -msgstr "If the GDM Face Browser is enabled, then the file <filename>$HOME/.face</filename> is accessed. This file should be in a standard image format that GTK+ can read, such as PNG or JPEG. It also must be smaller than the <filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> values defined in the GDM configuration or it will be ignored. Users can run the <command>gdmphotosetup</command> program to specify a face image and it will copy the file to the <filename>$HOME/.face</filename> location and scale it so its longest dimension is not larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> values. <command>gdmphotosetup</command> takes care to not change the aspect ratio of the image." - -#: C/gdm.xml:4434(para) -msgid "Face images can also be placed in the global face directory, which is specified by the <filename>GlobalFaceDir</filename> configuration option ( normally <filename><share>/pixmaps/faces/</filename>) and the filename should be the name of the user, optionally with a <filename>.png</filename>, <filename>.jpg</filename>, etc. appended." -msgstr "Face images can also be placed in the global face directory, which is specified by the <filename>GlobalFaceDir</filename> configuration option ( normally <filename><share>/pixmaps/faces/</filename>) and the filename should be the name of the user, optionally with a <filename>.png</filename>, <filename>.jpg</filename>, etc. appended." - -#: C/gdm.xml:4445(title) -msgid "Controlling GDM" -msgstr "Controlling GDM" - -#: C/gdm.xml:4447(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 "You can control GDM behaviour during runtime in several different ways: you can run certain commands or you can talk to GDM using either a unix socket protocol or a FIFO protocol." - -#: C/gdm.xml:4454(title) -msgid "Commands" -msgstr "Commands" - -#: C/gdm.xml:4456(para) -msgid "To stop GDM, you can either send the TERM signal to the main daemon or run the <command>gdm-stop</command> command which is in the <filename><sbin>/</filename> directory. To restart GDM, you can either send the HUP signal to the main daemon or run the <command>gdm-restart</command> command which is also in the <filename><sbin>/</filename> 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 <command>gdm-safe-restart</command> command which is in the <filename><sbin>/</filename> directory as well." -msgstr "To stop GDM, you can either send the TERM signal to the main daemon or run the <command>gdm-stop</command> command which is in the <filename><sbin>/</filename> directory. To restart GDM, you can either send the HUP signal to the main daemon or run the <command>gdm-restart</command> command which is also in the <filename><sbin>/</filename> directory. To restart GDM only after all the users have logged out, you can either send the USR1 signal to the main daemon or run the <command>gdm-safe-restart</command> command which is in the <filename><sbin>/</filename> directory as well." - -#: C/gdm.xml:4469(para) -msgid "The <command>gdmflexiserver</command> 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 <command>gdmflexiserver</command> 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 <command>gdmflexiserver --help</command> to get a listing of possible options." -msgstr "The <command>gdmflexiserver</command> 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 been started <command>gdmflexiserver</command> will display a pop-up dialogue 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 <command>gdmflexiserver --help</command> to get a listing of possible options." - -#: C/gdm.xml:4485(title) -msgid "The FIFO protocol" -msgstr "The FIFO protocol" - -#: C/gdm.xml:4487(para) -msgid "GDM also provides a FIFO called <filename>.gdmfifo</filename> in the <filename>ServAuthDir</filename> directory (usually <filename><var>/gdm/.gdmfifo</filename>). 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 "GDM also provides a FIFO called <filename>.gdmfifo</filename> in the <filename>ServAuthDir</filename> directory (usually <filename><var>/gdm/.gdmfifo</filename>). 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)." - -#: C/gdm.xml:4498(para) -msgid "Full and up to date documentation of the commands and their use is contained in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look for the defines starting with <filename>GDM_SOP_</filename>. The commands which require the pid of the slave as an argument are the ones that are really used for internal communication of the slave with the master and should not be used." -msgstr "Full and up to date documentation of the commands and their use is contained in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look for the defines starting with <filename>GDM_SOP_</filename>. The commands which require the pid of the slave as an argument are the ones that are really used for internal communication of the slave with the master and should not be used." - -#: C/gdm.xml:4510(title) -msgid "Socket Protocol" -msgstr "Socket Protocol" - -#: C/gdm.xml:4512(para) -msgid "GDM provides a unix domain socket for communication at <filename>/tmp/.gdm_socket</filename>. 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 <command>gdmflexiserver</command> command uses this protocol, for example, to launch flexible (on-demand) displays." -msgstr "GDM provides a unix domain socket for communication at <filename>/tmp/.gdm_socket</filename>. 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 <command>gdmflexiserver</command> command uses this protocol, for example, to launch flexible (on-demand) displays." - -#: C/gdm.xml:4522(para) -msgid "gdmflexiserver accepts the following commands with the --command option:" -msgstr "gdmflexiserver accepts the following commands with the --command option:" - -#: C/gdm.xml:4527(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_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 "" -"\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_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" - -#: C/gdm.xml:4555(para) -msgid "These are described in detail below, including required arguments, response format, and return codes." -msgstr "These are described in detail below, including required arguments, response format, and return codes." - -#: C/gdm.xml:4561(title) -msgid "ADD_DYNAMIC_DISPLAY" -msgstr "ADD_DYNAMIC_DISPLAY" - -#: C/gdm.xml:4562(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 "" -"\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" - -#: C/gdm.xml:4584(title) -msgid "ALL_SERVERS" -msgstr "ALL_SERVERS" - -#: C/gdm.xml:4585(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 "" -"\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" - -#: C/gdm.xml:4608(title) -msgid "ATTACHED_SERVERS" -msgstr "ATTACHED_SERVERS" - -#: C/gdm.xml:4609(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 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 "" -"\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 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" - -#: C/gdm.xml:4641(title) -msgid "AUTH_LOCAL" -msgstr "AUTH_LOCAL" - -#: C/gdm.xml:4642(screen) -#, no-wrap -msgid "" -"\n" -"AUTH_LOCAL: Setup this connection as authenticated for\n" -" FLEXI_SERVER. Because all full blown (non-Xnest)\n" -" displays can be started only from users logged in\n" -" locally, and here GDM assumes only users logged\n" -" in from GDM. They must pass the xauth\n" -" MIT-MAGIC-COOKIE-1 that they were passed before\n" -" 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 "" -"\n" -"AUTH_LOCAL: Setup this connection as authenticated for\n" -" FLEXI_SERVER. Because all full blown (non-Xnest)\n" -" displays can be started only from users logged in\n" -" locally, and here GDM assumes only users logged\n" -" in from GDM. They must pass the xauth\n" -" MIT-MAGIC-COOKIE-1 that they were passed before\n" -" 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" - -#: C/gdm.xml:4672(title) -msgid "CLOSE" -msgstr "CLOSE" - -#: C/gdm.xml:4673(screen) -#, no-wrap -msgid "" -"\n" -"CLOSE: Close sockets connection\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers: None\n" -msgstr "" -"\n" -"CLOSE: Close sockets connection\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers: None\n" - -#: C/gdm.xml:4682(title) -msgid "FLEXI_XNEST" -msgstr "FLEXI_XNEST" - -#: C/gdm.xml:4683(screen) -#, no-wrap -msgid "" -"\n" -"FLEXI_XNEXT: Start a new flexible Xnest 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 Xnest using the XAUTHORITY file\n" -" supplied and as the uid same as the owner of\n" -" that file (and same as you supply). You must\n" -" also supply the cookie as the third argument\n" -" for this display, to prove that you indeed are\n" -" this user. Also this file must be readable\n" -" ONLY by this user, that is have a mode of 0600.\n" -" If this all is not met, 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 "" -"\n" -"FLEXI_XNEXT: Start a new flexible Xnest 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 Xnest using the XAUTHORITY file\n" -" supplied and as the uid same as the owner of\n" -" that file (and same as you supply). You must\n" -" also supply the cookie as the third argument\n" -" for this display, to prove that you indeed are\n" -" this user. Also this file must be readable\n" -" ONLY by this user, that is have a mode of 0600.\n" -" If this all is not met, 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" - -#: C/gdm.xml:4721(title) -msgid "FLEXI_XNEST_USER" -msgstr "FLEXI_XNEST_USER" - -#: C/gdm.xml:4722(screen) -#, no-wrap -msgid "" -"\n" -"FLEXI_XNEST_USER: Start a new flexible Xnest 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 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 "" -"\n" -"FLEXI_XNEST_USER: Start a new flexible Xnest 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 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" - -#: C/gdm.xml:4751(title) -msgid "FLEXI_XSERVER" -msgstr "FLEXI_XSERVER" - -#: C/gdm.xml:4752(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 "" -"\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" - -#: C/gdm.xml:4774(title) -msgid "FLEXI_XSERVER_USER" -msgstr "FLEXI_XSERVER_USER" - -#: C/gdm.xml:4775(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 "" -"\n" -"FLEXI_XSERVER_USER: Start a new X flexible display and initialise 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" - -#: C/gdm.xml:4798(title) -msgid "GET_CONFIG" -msgstr "GET_CONFIG" - -#: C/gdm.xml:4799(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.h is supported. Starting with version 2.13.0.2\n" -" translated keys (such as \"greeter/GdmWelcome[cs]\" are\n" -" supported via GET_CONFIG. Also starting with version\n" -" 2.13.0.2 it is no longer necessary to include the\n" -" default value (i.e. you can use key \"greeter/IncludeAll\"\n" -" instead of having to use \"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 "" -"\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.h is supported. Starting with version 2.13.0.2\n" -" translated keys (such as \"greeter/GdmWelcome[cs]\" are\n" -" supported via GET_CONFIG. Also starting with version\n" -" 2.13.0.2 it is no longer necessary to include the\n" -" default value (i.e. you can use key \"greeter/IncludeAll\"\n" -" instead of having to use \"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" - -#: C/gdm.xml:4822(title) -msgid "GET_CONFIG_FILE" -msgstr "GET_CONFIG_FILE" - -#: C/gdm.xml:4823(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 "" -"\n" -"GET_CONFIG_FILE: Get configuration 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" - -#: C/gdm.xml:4840(title) -msgid "GET_CUSTOM_CONFIG_FILE" -msgstr "GET_CUSTOM_CONFIG_FILE" - -#: C/gdm.xml:4841(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 "" -"\n" -"GET_CUSTOM_CONFIG_FILE: Get custom configuration 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" - -#: C/gdm.xml:4857(title) -msgid "GET_SERVER_DETAILS" -msgstr "GET_SERVER_DETAILS" - -#: C/gdm.xml:4858(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 "" -"\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" - -#: C/gdm.xml:4887(title) -msgid "GET_SERVER_LIST" -msgstr "GET_SERVER_LIST" - -#: C/gdm.xml:4888(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 "" -"\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" - -#: C/gdm.xml:4904(title) -msgid "GREETERPIDS" -msgstr "GREETERPIDS" - -#: C/gdm.xml:4905(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 "" -"\n" -"GREETERPIDS: List all greeter pids so that one can send HUP\n" -" to them for config re-reading. 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" - -#: C/gdm.xml:4921(title) -msgid "QUERY_LOGOUT_ACTION" -msgstr "QUERY_LOGOUT_ACTION" - -#: C/gdm.xml:4922(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 "" -"\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" - -#: C/gdm.xml:4944(title) -msgid "QUERY_CUSTOM_CMD_LABELS" -msgstr "QUERY_CUSTOM_CMD_LABELS" - -#: C/gdm.xml:4945(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 "" -"\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" - -#: C/gdm.xml:4966(title) -msgid "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" -msgstr "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" - -#: C/gdm.xml:4967(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 "" -"\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" - -#: C/gdm.xml:4988(title) -msgid "QUERY_VT" -msgstr "QUERY_VT" - -#: C/gdm.xml:4989(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 "" -"\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" - -#: C/gdm.xml:5012(title) -msgid "RELEASE_DYNAMIC_DISPLAYS" -msgstr "RELEASE_DYNAMIC_DISPLAYS" - -#: C/gdm.xml:5013(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 "" -"\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" - -#: C/gdm.xml:5030(title) -msgid "REMOVE_DYNAMIC_DISPLAY" -msgstr "REMOVE_DYNAMIC_DISPLAY" - -#: C/gdm.xml:5031(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 "" -"\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" - -#: C/gdm.xml:5048(title) -msgid "SERVER_BUSY" -msgstr "SERVER_BUSY" - -#: C/gdm.xml:5049(screen) -#, no-wrap -msgid "" -"\n" -"SERVER_BUSY: Returns true if half or more of the daemon's sockets\n" -" are busy, false otherwise. Used by slave programs\n" -" which want to ensure they do not overwhelm the \n" -" sever.\n" -"Supported since: 2.13.0.8\n" -"Arguments: None\n" -"Answers:\n" -" OK <value>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -msgstr "" -"\n" -"SERVER_BUSY: Returns true if half or more of the daemon's sockets\n" -" are busy, false otherwise. Used by slave programs\n" -" which want to ensure they do not overwhelm the \n" -" sever.\n" -"Supported since: 2.13.0.8\n" -"Arguments: None\n" -"Answers:\n" -" OK <value>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" - -#: C/gdm.xml:5066(title) -msgid "SET_LOGOUT_ACTION" -msgstr "SET_LOGOUT_ACTION" - -#: C/gdm.xml:5067(screen) -#, no-wrap -msgid "" -"\n" -"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -" slave process exits. 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 "" -"\n" -"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -" slave process exits. 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" - -#: C/gdm.xml:5090(title) -msgid "SET_SAFE_LOGOUT_ACTION" -msgstr "SET_SAFE_LOGOUT_ACTION" - -#: C/gdm.xml:5091(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 "" -"\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" - -#: C/gdm.xml:5121(title) -msgid "SET_VT" -msgstr "SET_VT" - -#: C/gdm.xml:5122(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 "" -"\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 currently supported\n" -" on Linux, other systems 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" - -#: C/gdm.xml:5143(title) -msgid "UPDATE_CONFIG" -msgstr "UPDATE_CONFIG" - -#: C/gdm.xml:5144(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 "" -"\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 recognise 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" - -#: C/gdm.xml:5220(title) -msgid "VERSION" -msgstr "VERSION" - -#: C/gdm.xml:5221(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 "" -"\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" - -#: C/gdm.xml:5238(title) -msgid "GDM Commands" -msgstr "GDM Commands" - -#: C/gdm.xml:5241(title) -msgid "GDM User Commands" -msgstr "GDM User Commands" - -#: C/gdm.xml:5243(para) -msgid "The GDM package provides the following different commands in <filename>bindir</filename> intended to be used by the end-user:" -msgstr "The GDM package provides the following different commands in <filename>bindir</filename> intended to be used by the end-user:" - -#: C/gdm.xml:5249(title) -msgid "<command>gdmXnestchooser</command> and <command>gdmXnest</command> Command Line Options" -msgstr "<command>gdmXnestchooser</command> and <command>gdmXnest</command> Command Line Options" - -#: C/gdm.xml:5252(para) -msgid "The <command>gdmXnestchooser</command> command automatically gets the correct display number, sets up access, and runs <command>Xnest</command> with -indirect localhost. This way you get an XDMCP chooser provided by your computer. You can also supply as an argument the hostname whose chooser should be displayed, so <command>gdmXnestchooser somehost</command> will run the XDMCP chooser from host <command>somehost</command> inside an Xnest session. You can make this command do a direct query instead by passing the <command>-d</command> option as well. In addition to the following options, this command also supports standard GNOME options." -msgstr "The <command>gdmXnestchooser</command> command automatically gets the correct display number, sets up access and runs <command>Xnest</command> with -indirect localhost. This way you get an XDMCP chooser provided by your computer. You can also supply as an argument the hostname whose chooser should be displayed, so <command>gdmXnestchooser somehost</command> will run the XDMCP chooser from host <command>somehost</command> inside an Xnest session. You can make this command do a direct query instead by passing the <command>-d</command> option as well. In addition to the following options, this command also supports standard GNOME options." - -#: C/gdm.xml:5267(title) -msgid "<command>gdmXnestchooser</command> Command Line Options" -msgstr "<command>gdmXnestchooser</command> Command Line Options" - -#: C/gdm.xml:5270(term) -msgid "-x, --xnest=STRING" -msgstr "-x, --xnest=STRING" - -#: C/gdm.xml:5272(para) -msgid "Xnest command line, default is \"Xnest\"" -msgstr "Xnest command line, default is \"Xnest\"" - -#: C/gdm.xml:5279(term) -msgid "-o, --xnest-extra-options=OPTIONS" -msgstr "-o, --xnest-extra-options=OPTIONS" - -#: C/gdm.xml:5281(para) -msgid "Extra options for Xnest, default is no options." -msgstr "Extra options for Xnest, default is no options." - -#: C/gdm.xml:5288(term) -msgid "-n, --no-query" -msgstr "-n, --no-query" - -#: C/gdm.xml:5290(para) -msgid "Just run Xnest, no query (no chooser)" -msgstr "Just run Xnest, no query (no chooser)" - -#: C/gdm.xml:5297(term) -msgid "-d, --direct" -msgstr "-d, --direct" - -#: C/gdm.xml:5299(para) -msgid "Do direct query instead of indirect (chooser)" -msgstr "Do direct query instead of indirect (chooser)" - -#: C/gdm.xml:5306(term) -msgid "-B, --broadcast" -msgstr "-B, --broadcast" - -#: C/gdm.xml:5308(para) -msgid "Run broadcast instead of indirect (chooser)" -msgstr "Run broadcast instead of indirect (chooser)" - -#: C/gdm.xml:5315(term) -msgid "-b, --background" -msgstr "-b, --background" - -#: C/gdm.xml:5317(para) -msgid "Run in background" -msgstr "Run in background" - -#: C/gdm.xml:5324(term) -msgid "--no-gdm-check" -msgstr "--no-gdm-check" - -#: C/gdm.xml:5326(para) -msgid "Don't check for running GDM" -msgstr "Don't check for running GDM" - -#: C/gdm.xml:5335(title) -#: C/gdm.xml:5379(title) -msgid "<command>gdmflexichooser</command> Command Line Options" -msgstr "<command>gdmflexichooser</command> Command Line Options" - -#: C/gdm.xml:5337(para) -msgid "The <command>gdmflexiserver</command> command provides three features. It can be used to run flexible (on demand) X displays, to run a flexible display via Xnest, and to send commands to the GDM daemon process." -msgstr "The <command>gdmflexiserver</command> command provides three features. It can be used to run flexible (on demand) X displays, to run a flexible display via Xnest, and to send commands to the GDM daemon process." - -#: C/gdm.xml:5344(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 "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 dialogue 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." - -#: C/gdm.xml:5358(para) -msgid "Flexible displays started via Xnest 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 "Flexible displays started via Xnest 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." - -#: C/gdm.xml:5366(para) -msgid "The <command>gdmflexiserver --command</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 "The <command>gdmflexiserver --command</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." - -#: C/gdm.xml:5372(para) -msgid "In addition to the following options, <command>gdmflexiserver</command> also supports standard GNOME options." -msgstr "In addition to the following options, <command>gdmflexiserver</command> also supports standard GNOME options." - -#: C/gdm.xml:5382(term) -msgid "-c, --command=COMMAND" -msgstr "-c, --command=COMMAND" - -#: C/gdm.xml:5384(para) -msgid "Send the specified protocol command to GDM" -msgstr "Send the specified protocol command to GDM" - -#: C/gdm.xml:5391(term) -msgid "-n, --xnest" -msgstr "-n, --xnest" - -#: C/gdm.xml:5393(para) -msgid "Start a flexible X display in Xnest mode" -msgstr "Start a flexible X display in Xnest mode" - -#: C/gdm.xml:5400(term) -msgid "-l, --no-lock" -msgstr "-l, --no-lock" - -#: C/gdm.xml:5402(para) -msgid "Do not lock current screen" -msgstr "Do not lock current screen" - -#: C/gdm.xml:5409(term) -msgid "-d, --debug" -msgstr "-d, --debug" - -#: C/gdm.xml:5411(para) -msgid "Turns on debugging output which gets sent to syslog. Same as turning on debug in the configuration file." -msgstr "Turns on debugging output which gets sent to syslog. Same as turning on debug in the configuration file." - -#: C/gdm.xml:5419(term) -msgid "-a, --authenticate" -msgstr "-a, --authenticate" - -#: C/gdm.xml:5421(para) -msgid "Authenticate before running --command" -msgstr "Authenticate before running --command" - -#: C/gdm.xml:5428(term) -msgid "-s, --startnew" -msgstr "-s, --startnew" - -#: C/gdm.xml:5430(para) -msgid "Starts a new flexible display without displaying a dialog asking the user if they wish to continue any existing sessions." -msgstr "Starts a new flexible display without displaying a dialogue asking the user if they wish to continue any existing sessions." - -#: C/gdm.xml:5441(title) -#: C/gdm.xml:5467(title) -msgid "<command>gdmdynamic</command> Command Line Options" -msgstr "<command>gdmdynamic</command> Command Line Options" - -#: C/gdm.xml:5443(para) -msgid "The <command>gdmdynamic</command> command which creates, runs, and removes displays (X servers) on demand." -msgstr "The <command>gdmdynamic</command> command which creates, runs, and removes displays (X servers) on demand." - -#: C/gdm.xml:5448(para) -msgid "<command>gdmdynamic</command> 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 <command>gdmdynamic</command> command can be used to create a new display on a particular display number, run all newly created displays, or remove a display. The <command>gdmdynamic</command> command can also be used to list all attached displays, or only attached displays that match a pattern." -msgstr "<command>gdmdynamic</command> 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 <command>gdmdynamic</command> command can be used to create a new display on a particular display number, run all newly created displays, or remove a display. The <command>gdmdynamic</command> command can also be used to list all attached displays, or only attached displays that match a pattern." - -#: C/gdm.xml:5459(para) -msgid "This program is designed to manage multiple simultaneous requests and works 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 "This program is designed to manage multiple simultaneous requests and works 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." - -#: C/gdm.xml:5472(emphasis) -msgid "One of the following options can be used per instance:" -msgstr "One of the following options can be used per instance:" - -#: C/gdm.xml:5479(term) -msgid "-a display=server" -msgstr "-a display=server" - -#: C/gdm.xml:5481(para) -msgid "Add a new display configuration, leaving it in the DISPLAY_CONFIG state. For example, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a 3=/usr/X11R6/bin/X -dev /dev/fb2\"</command>" -msgstr "Add a new display configuration, leaving it in the DISPLAY_CONFIG state. For example, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a 3=/usr/X11R6/bin/X -dev /dev/fb2\"</command>" - -#: C/gdm.xml:5487(para) -msgid "The display will not actually be started until the display is released by calling <command>gdmdynamic</command> again with the -r option." -msgstr "The display will not actually be started until the display is released by calling <command>gdmdynamic</command> again with the -r option." - -#: C/gdm.xml:5495(term) -msgid "-r" -msgstr "-r" - -#: C/gdm.xml:5497(para) -msgid "Release (run) all displays waiting in the DISPLAY_CONFIG state." -msgstr "Release (run) all displays waiting in the DISPLAY_CONFIG state." - -#: C/gdm.xml:5504(term) -msgid "-d display" -msgstr "-d display" - -#: C/gdm.xml:5506(para) -msgid "Delete a display, killing the X server and purging the display configuration. For example, \"-d 3\"." -msgstr "Delete a display, killing the X server and purging the display configuration. For example, \"-d 3\"." - -#: C/gdm.xml:5514(term) -msgid "-l [pattern]" -msgstr "-l [pattern]" - -#: C/gdm.xml:5516(para) -msgid "List displays via the ATTACHED_SERVERS <command>gdmflexiserver</command> command. Without a pattern lists all attached displays. With a pattern will match using glob characters '*', '?', and '[]'. For example: <command>\"-l Standard*\"</command><command>\"-l *Xorg*\"</command>" -msgstr "List displays via the ATTACHED_SERVERS <command>gdmflexiserver</command> command. Without a pattern lists all attached displays. With a pattern will match using glob characters '*', '?', and '[]'. For example: <command>\"-l Standard*\"</command><command>\"-l *Xorg*\"</command>" - -#: C/gdm.xml:5529(emphasis) -msgid "These options can be added to the above:" -msgstr "These options can be added to the above:" - -#: C/gdm.xml:5536(term) -msgid "-v" -msgstr "-v" - -#: C/gdm.xml:5538(para) -msgid "Verbose mode. Prinr diagnostic messages about each message sent to GDM." -msgstr "Verbose mode. Print diagnostic messages about each message sent to GDM." - -#: C/gdm.xml:5546(term) -msgid "-b" -msgstr "-b" - -#: C/gdm.xml:5548(para) -msgid "Background mode. Fork child to do the work and return immediately." -msgstr "Background mode. Fork child to do the work and return immediately." - -#: C/gdm.xml:5555(term) -msgid "-t RETRY" -msgstr "-t RETRY" - -#: C/gdm.xml:5557(para) -msgid "If the daemon socket is busy, <command>gdmdynamic</command> will retry to open the connection the specified RETRY number of times. Default value is 15." -msgstr "If the daemon socket is busy, <command>gdmdynamic</command> will retry to open the connection the specified RETRY number of times. The default value is 15." - -#: C/gdm.xml:5566(term) -msgid "-s SLEEP" -msgstr "-s SLEEP" - -#: C/gdm.xml:5568(para) -msgid "If the daemon socket is busy, <command>gdmdynamic</command> 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 "If the daemon socket is busy, <command>gdmdynamic</command> will sleep an amount of time between retries. A random number of seconds between 0 and 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. The default value is 8 seconds." - -#: C/gdm.xml:5583(title) -msgid "<command>gdmphotosetup</command> Command Line Options" -msgstr "<command>gdmphotosetup</command> Command Line Options" - -#: C/gdm.xml:5585(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 <filename>~/.face</filename>. This command accepts standard GNOME options." -msgstr "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 <filename>~/.face</filename>. This command accepts the standard GNOME options." - -#: C/gdm.xml:5594(title) -msgid "<command>gdmthemetester</command> Command Line Options" -msgstr "<command>gdmthemetester</command> Command Line Options" - -#: C/gdm.xml:5596(para) -msgid "" -"<command>gdmthemetester</command> 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. <command>gdmthemetester</command> requires that the system support <command>gdmXnest</command>. Note that themes can display differently depending on the theme's \"Show mode\". <command>gdmthemetester</command> allows viewing the themes in different modes via the environment option. Valid environment values and their meanings follow: <screen>\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" -"</screen>" -msgstr "" -"<command>gdmthemetester</command> 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. <command>gdmthemetester</command> requires that the system support <command>gdmXnest</command>. Note that themes can display differently depending on the theme's \"Show mode\". <command>gdmthemetester</command> allows viewing the themes in different modes via the environment option. Valid environment values and their meanings follow: <screen>\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" -"</screen>" - -#: C/gdm.xml:5622(title) -msgid "GDM Root User Commands" -msgstr "GDM Root User Commands" - -#: C/gdm.xml:5624(para) -msgid "The GDM package provides the following different commands in <filename>sbindir</filename> intended to be used by the root user:" -msgstr "The GDM package provides the following different commands in <filename>sbindir</filename> intended to be used by the root user:" - -#: C/gdm.xml:5630(title) -#: C/gdm.xml:5646(title) -msgid "<command>gdm</command> and <command>gdm-binary</command> Command Line Options" -msgstr "<command>gdm</command> and <command>gdm-binary</command> Command Line Options" - -#: C/gdm.xml:5633(para) -msgid "The <command>gdm</command> command is really just a script which runs the <command>gdm-binary</command>, passing along any options. Before launching <command>gdm-binary</command>, the gdm wrapper script will source the <filename><etc>/profile</filename> file to set the standard system environment variables. In order to better support internationalization, it will also set the LC_MESSAGES environment variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you really need to set some additional environment before launching GDM, you can do so in this script." -msgstr "The <command>gdm</command> command is a script which runs the <command>gdm-binary</command>, passing any options. Before launching <command>gdm-binary</command>, the gdm wrapper script will source the <filename><etc>/profile</filename> file to set the standard system environment variables. In order to better support internationalisation, it will also set the LC_MESSAGES environment variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you need to set some additional environment variables before launching GDM, you can do so in this script." - -#: C/gdm.xml:5650(term) -msgid "--help" -msgstr "--help" - -#: C/gdm.xml:5652(para) -msgid "Gives a brief overview of the command line options." -msgstr "Gives a brief overview of the command line options." - -#: C/gdm.xml:5659(term) -msgid "--nodaemon" -msgstr "--nodaemon" - -#: C/gdm.xml:5661(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 "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." - -#: C/gdm.xml:5671(term) -msgid "--no-console" -msgstr "--no-console" - -#: C/gdm.xml:5673(para) -msgid "Tell the daemon that it should not run anything on the console. This means that none of the local servers from the <filename>[servers]</filename> section will be run, and the console will not be used for communicating errors to the user. An empty <filename>[servers]</filename> section automatically implies this option." -msgstr "Tell the daemon that it should not run anything on the console. This means that none of the local servers from the <filename>[servers]</filename> section will be run, and the console will not be used for communicating errors to the user. An empty <filename>[servers]</filename> section automatically implies this option." - -#: C/gdm.xml:5685(term) -msgid "--config=CONFIGFILE" -msgstr "--config=CONFIGFILE" - -#: C/gdm.xml:5687(para) -msgid "Specify an alternative configuration file." -msgstr "Specify an alternative configuration file." - -#: C/gdm.xml:5694(term) -msgid "--preserve-ld-vars" -msgstr "--preserve-ld-vars" - -#: C/gdm.xml:5696(para) -msgid "When clearing the environment internally, preserve all variables starting with LD_. This is mostly for debugging purposes." -msgstr "When clearing the environment internally, preserve all variables starting with LD_. This is mostly for debugging purposes." - -#: C/gdm.xml:5704(term) -msgid "--version" -msgstr "--version" - -#: C/gdm.xml:5706(para) -msgid "Print the version of the GDM daemon." -msgstr "Print the version of the GDM daemon." - -#: C/gdm.xml:5713(term) -msgid "--wait-for-go" -msgstr "--wait-for-go" - -#: C/gdm.xml:5715(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 "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 initialisation 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." - -#: C/gdm.xml:5733(title) -msgid "<command>gdmsetup</command> Command Line Options" -msgstr "<command>gdmsetup</command> Command Line Options" - -#: C/gdm.xml:5735(para) -msgid "<command>gdmsetup</command> 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 <command>gdmsetup</command> 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 "<command>gdmsetup</command> runs a graphical application for modifying the GDM configuration file. Normally on systems that support the PAM user helper, this is set up such that when you run <command>gdmsetup</command> 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." - -#: C/gdm.xml:5747(title) -msgid "<command>gdm-restart</command> Command Line Options" -msgstr "<command>gdm-restart</command> Command Line Options" - -#: C/gdm.xml:5749(para) -msgid "<command>gdm-restart</command> stops and restarts GDM by sending the GDM daemon a HUP signal. This command will immediately terminate all sessions and log out users currently logged in with GDM." -msgstr "<command>gdm-restart</command> 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." - -#: C/gdm.xml:5757(title) -msgid "<command>gdm-safe-restart</command> Command Line Options" -msgstr "<command>gdm-safe-restart</command> Command Line Options" - -#: C/gdm.xml:5759(para) -msgid "<command>gdm-safe-restart</command> stops and restarts GDM by sending the GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out." -msgstr "<command>gdm-safe-restart</command> stops and restarts GDM by sending the GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out." - -#: C/gdm.xml:5767(title) -msgid "<command>gdm-stop</command> Command Line Options" -msgstr "<command>gdm-stop</command> Command Line Options" - -#: C/gdm.xml:5769(para) -msgid "<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM signal." -msgstr "<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM signal." - -#: C/gdm.xml:5777(title) -msgid "GDM Internal Commands" -msgstr "GDM Internal Commands" - -#: C/gdm.xml:5779(para) -msgid "The GDM package provides the following different commands in <filename>libexecdir</filename> intended to be used by the gdm daemon process." -msgstr "The GDM package provides the following different commands in <filename>libexecdir</filename> intended to be used by the gdm daemon process." - -#: C/gdm.xml:5786(title) -msgid "<command>gdmchooser</command> and <command>gdmlogin</command> Command Line Options" -msgstr "<command>gdmchooser</command> and <command>gdmlogin</command> Command Line Options" - -#: C/gdm.xml:5789(para) -msgid "The <command>gdmgreeter</command> and <command>gdmlogin</command> are two different login applications, either can be used by GDM. <command>gdmgreeter</command> is themeable with GDM themes while <command>gdmlogin</command> is themable with GTK+ themes. These applications are normally executed by the GDM daemon. Both commands support standard GNOME options." -msgstr "The <command>gdmgreeter</command> and <command>gdmlogin</command> are two different login applications, either can be used by GDM. <command>gdmgreeter</command> is themeable with GDM themes while <command>gdmlogin</command> is themable with GTK+ themes. These applications are normally executed by the GDM daemon. Both commands support standard GNOME options." - -#: C/gdm.xml:5800(title) -#: C/gdm.xml:5811(title) -msgid "<command>gdmchooser</command> Command Line Options" -msgstr "<command>gdmchooser</command> Command Line Options" - -#: C/gdm.xml:5802(para) -msgid "The <command>gdmchooser</command> is the XDMCP chooser application. The <command>gdmchooser</command> is normally executed by the GDM daemon. It supports the following options for XDM compatibility. This command supports standard GNOME options and is found in support standard GNOME options." -msgstr "The <command>gdmchooser</command> is the XDMCP chooser application. The <command>gdmchooser</command> is normally executed by the GDM daemon. It supports the following options for XDM compatibility. This command supports standard GNOME options and is found in support standard GNOME options." - -#: C/gdm.xml:5814(term) -msgid "--xdmaddress=SOCKET" -msgstr "--xdmaddress=SOCKET" - -#: C/gdm.xml:5816(para) -msgid "Socket for XDM communication." -msgstr "Socket for XDM communication." - -#: C/gdm.xml:5823(term) -msgid "--clientaddress=ADDRESS" -msgstr "--clientaddress=ADDRESS" - -#: C/gdm.xml:5825(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 "Client address to return in response to XDM. This option is for running gdmchooser with XDM, and is not used within GDM." - -#: C/gdm.xml:5833(term) -msgid "--connectionType=TYPE" -msgstr "--connectionType=TYPE" - -#: C/gdm.xml:5835(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 "Connection type to return in response to XDM. This option is for running gdmchooser with XDM, and is not used within GDM." - -#: C/gdm.xml:5845(command) -msgid "gdm-ssh-session" -msgstr "gdm-ssh-session" - -#: C/gdm.xml:5847(para) -msgid "The <command>gdm-ssh-session</command> is normally executed by the GDM daemon when starting a secure remote connection through ssh. It does not take any options." -msgstr "The <command>gdm-ssh-session</command> is normally executed by the GDM daemon when starting a secure remote connection through ssh. It does not take any options." - -#: C/gdm.xml:5859(title) -msgid "Themed Greeter" -msgstr "Themed Greeter" - -#: C/gdm.xml:5861(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 <ulink type=\"http\" url=\"http://art.gnome.org/themes/gdm_greeter/\"> the theme website</ulink>." -msgstr "This section describes the creation of themes for the Themed Greeter. For examples including screenshots, see the standard installed themes and the themes from <ulink type=\"http\" url=\"http://art.gnome.org/themes/gdm_greeter/\"> the theme website</ulink>." - -#: C/gdm.xml:5870(title) -msgid "Theme Overview" -msgstr "Theme Overview" - -#: C/gdm.xml:5872(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 <filename><share>/gdm/themes/<theme_name></filename>. Usually this would be under <filename>/usr/share</filename>. The theme directory should contain a file called <filename>GdmGreeterTheme.desktop</filename> which has similar format to other .desktop files and looks like:" -msgstr "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 <filename><share>/gdm/themes/<theme_name></filename>. Usually this would be under <filename>/usr/share</filename>. The theme directory should contain a file called <filename>GdmGreeterTheme.desktop</filename> which has similar format to other .desktop files and looks like:" - -#: C/gdm.xml:5883(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 "" -"\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" - -#: C/gdm.xml:5894(para) -msgid "The Name, Description, Author and Copyright fields can be translated just like the other <filename>.desktop</filename>files. 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 "The Name, Description, Author and Copyright fields can be translated just like the other <filename>.desktop</filename>files. 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." - -#: C/gdm.xml:5904(para) -msgid "Once you have theme ready and installed you can test it with the installed <command>gdmthemetester</command> script. This script assumes that the X server supports Xnest. 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 "Once you have theme ready and installed you can test it with the installed <command>gdmthemetester</command> script. This script assumes that the X server supports Xnest. 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:" - -#: C/gdm.xml:5919(command) -msgid "gdmthemetester xdmcp circles" -msgstr "gdmthemetester xdmcp circles" - -#: C/gdm.xml:5922(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 Xnest window. This can be done in GNOME by focusing the Xnest window and pressing Alt-PrintScreen." -msgstr "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 Xnest window. This can be done in GNOME by focusing the Xnest window and pressing Alt-PrintScreen." - -#: C/gdm.xml:5930(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 <filename><share>/gdm/themes</filename> directory). And this is the tarball you distribute and people can install from the graphical configuration application. You can do this with the commands: <screen>\n" -"cd <share>/gdm/themes\n" -"tar czvf <theme_name>.tar.gz <theme_name>/\n" -"</screen>" -msgstr "" -"Once you have all this done, then make a tarball that contains the directory name (so that you could just untar it in the <filename><share>/gdm/themes</filename> directory). And this is the tarball you distribute and people can install from the graphical configuration application. You can do this with the commands: <screen>\n" -"cd <share>/gdm/themes\n" -"tar czvf <theme_name>.tar.gz <theme_name>/\n" -"</screen>" - -#: C/gdm.xml:5944(title) -msgid "Detailed Description of Theme XML format" -msgstr "Detailed Description of Theme XML format" - -#: C/gdm.xml:5947(title) -msgid "greeter tag" -msgstr "greeter tag" - -#: C/gdm.xml:5949(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 "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." - -#: C/gdm.xml:5956(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 "" -"\n" -"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" -"<!DOCTYPE greeter SYSTEM \"greeter.dtd\">\n" -"<greeter gtk-theme=\"Crux\">\n" -"[...]\n" -"</greeter>\n" - -#: C/gdm.xml:5964(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 "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)." - -#: C/gdm.xml:5974(title) -msgid "Box Nodes" -msgstr "Box Nodes" - -#: C/gdm.xml:5976(para) -msgid "" -"Box nodes are container nodes for item nodes. Box nodes are specified as follows: <screen>\n" -"<box orientation=\"alignment\" min-width=\"num\"\n" -"xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -"homogeneous=\"bool\">\n" -"</screen> 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 "" -"Box nodes are container nodes for item nodes. Box nodes are specified as follows: <screen>\n" -"<box orientation=\"alignment\" min-width=\"num\"\n" -"xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -"homogeneous=\"bool\">\n" -"</screen> 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." - -#: C/gdm.xml:5992(para) -msgid "If the box is homogeneous then the children are allocated equal amount of space." -msgstr "If the box is homogeneous then the children are allocated equal amount of space." - -#: C/gdm.xml:5997(para) -msgid "The \"min-width\" must be specified in pixels. Obviously there is also a corresponding \"min-height\" property as well." -msgstr "The \"min-width\" must be specified in pixels. Obviously there is also a corresponding \"min-height\" property as well." - -#: C/gdm.xml:6005(title) -msgid "Fixed Nodes" -msgstr "Fixed Nodes" - -#: C/gdm.xml:6007(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: <screen>\n" -"<fixed>\n" -"</screen> Then you put other items with proper position nodes inside this." -msgstr "" -"Fixed is a container that has its children scattered about laid out with precise co-ordinates. The size of this container is the largest rectangle that contains all the children. Fixed has no extra properties and so you just use: <screen>\n" -"<fixed>\n" -"</screen> Then you put other items with proper position nodes inside this." - -#: C/gdm.xml:6018(para) -msgid "The \"toplevel\" node is really just like a fixed node." -msgstr "The \"toplevel\" node is really just like a fixed node." - -#: C/gdm.xml:6024(title) -msgid "Item Nodes" -msgstr "Item Nodes" - -#: C/gdm.xml:6026(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 "A GDM Theme is created by specifying a hierarchy of item and box nodes. Item nodes can have the following value for \"type\":" - -#: C/gdm.xml:6034(term) -msgid "button" -msgstr "button" - -#: C/gdm.xml:6036(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 "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." - -#: C/gdm.xml:6048(term) -msgid "entry" -msgstr "entry" - -#: C/gdm.xml:6050(para) -msgid "Text entry field." -msgstr "Text entry field." - -#: C/gdm.xml:6057(term) -msgid "label" -msgstr "label" - -#: C/gdm.xml:6059(para) -msgid "A text label. Must have a \"text\" node to specify the text." -msgstr "A text label. Must have a \"text\" node to specify the text." - -#: C/gdm.xml:6067(term) -msgid "list" -msgstr "list" - -#: C/gdm.xml:6069(para) -msgid "A face browser widget. Only useful if the face browser is enabled via the configuration." -msgstr "A face browser widget. Only useful if the face browser is enabled via the configuration." - -#: C/gdm.xml:6077(term) -msgid "pixmap" -msgstr "pixmap" - -#: C/gdm.xml:6079(para) -msgid "An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, etc...)" -msgstr "An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, etc...)" - -#: C/gdm.xml:6087(term) -msgid "rect" -msgstr "rect" - -#: C/gdm.xml:6089(para) -msgid "Rectangle." -msgstr "Rectangle." - -#: C/gdm.xml:6096(term) -msgid "svg" -msgstr "svg" - -#: C/gdm.xml:6098(para) -msgid "Scaled Vector Graphic image." -msgstr "Scaled Vector Graphic image." - -#: C/gdm.xml:6105(para) -msgid "" -"For example: <screen>\n" -"<item type=\"label\">\n" -"</screen> 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 "" -"For example: <screen>\n" -"<item type=\"label\">\n" -"</screen> Items can specify ID values which gives them a specific look and feel or formatting. Furthermore you can customise the login process by adding custom widgets with custom id's for some items (currently only the list item)" - -#: C/gdm.xml:6116(para) -msgid "Entry items can have id values as follows:" -msgstr "Entry items can have id values as follows:" - -#: C/gdm.xml:6122(term) -msgid "user-pw-entry" -msgstr "user-pw-entry" - -#: C/gdm.xml:6124(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 "Entry field for userid and password entry. This is the field used for responses for the PAM/GDM questions (Username, Password, etc..)." - -#: C/gdm.xml:6133(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 "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. Customised lists may also be defined, which are explained below." - -#: C/gdm.xml:6143(term) -msgid "session" -msgstr "session" - -#: C/gdm.xml:6145(para) -msgid "A list of available sessions, which allows the user to pick the session to use. Supported since GDM 2.16.2." -msgstr "A list of available sessions, which allows the user to pick the session to use. Supported since GDM 2.16.2." - -#: C/gdm.xml:6155(term) -msgid "language" -msgstr "language" - -#: C/gdm.xml:6157(para) -msgid "A list of available languages, which allows the user to pick the language to use. Supported since GDM 2.16.2." -msgstr "A list of available languages, which allows the user to pick the language to use. Supported since GDM 2.16.2." - -#: C/gdm.xml:6167(term) -msgid "userlist" -msgstr "userlist" - -#: C/gdm.xml:6169(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 "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." - -#: C/gdm.xml:6182(term) -msgid "userlist-rect" -msgstr "userlist-rect" - -#: C/gdm.xml:6184(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 "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 colour and/or alpha to surround the userlist, but only if there are users to display. Supported since 2.16.2." - -#: C/gdm.xml:6196(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 "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'" - -#: C/gdm.xml:6203(para) -msgid "Label items can have id values as follows:" -msgstr "Label items can have id values as follows:" - -#: C/gdm.xml:6209(term) -msgid "clock" -msgstr "clock" - -#: C/gdm.xml:6211(para) -msgid "Label that displays the date and time." -msgstr "Label that displays the date and time." - -#: C/gdm.xml:6218(term) -msgid "pam-prompt" -msgstr "pam-prompt" - -#: C/gdm.xml:6220(para) -msgid "Label that displays the PAM prompt. This is the prompt that PAM uses to ask for username, password, etc..." -msgstr "Label that displays the PAM prompt. This is the prompt that PAM uses to ask for username, password, etc..." - -#: C/gdm.xml:6228(term) -msgid "pam-error" -msgstr "pam-error" - -#: C/gdm.xml:6230(para) -msgid "Label that displayst PAM/GDM error messages. Such as when user can't log in." -msgstr "Label that displayst PAM/GDM error messages. Such as when user can't log in." - -#: C/gdm.xml:6238(term) -msgid "pam-error-logo" -msgstr "pam-error-logo" - -#: C/gdm.xml:6240(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 "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." - -#: C/gdm.xml:6250(term) -msgid "pam-message" -msgstr "pam-message" - -#: C/gdm.xml:6252(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 "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." - -#: C/gdm.xml:6261(term) -msgid "timed-label" -msgstr "timed-label" - -#: C/gdm.xml:6263(para) -msgid "Label that displays timed login information." -msgstr "Label that displays timed login information." - -#: C/gdm.xml:6270(para) -msgid "Rectangles can have id values as follows:" -msgstr "Rectangles can have id values as follows:" - -#: C/gdm.xml:6276(term) -msgid "caps-lock-warning" -msgstr "caps-lock-warning" - -#: C/gdm.xml:6278(para) -msgid "Displays an icon that shows if the CAPS LOCK key is depressed. This rectangle will be hidden/shown appropriately" -msgstr "Displays an icon that shows if the CAPS LOCK key is depressed. This rectangle will be hidden/shown appropriately" - -#: C/gdm.xml:6287(para) -msgid "" -"If an item is of type rect, the item can be a button. Buttons must also include a \"button\" value as follows: <screen>\n" -"<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n" -"</screen>" -msgstr "" -"If an item is of type rect, the item can be a button. Buttons must also include a \"button\" value as follows: <screen>\n" -"<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n" -"</screen>" - -#: C/gdm.xml:6295(para) -msgid "Possible values for button ids are as follows." -msgstr "Possible values for button ids are as follows." - -#: C/gdm.xml:6301(term) -msgid "chooser_button" -msgstr "chooser_button" - -#: C/gdm.xml:6303(para) -msgid "Runs the XDMCP chooser." -msgstr "Runs the XDMCP chooser." - -#: C/gdm.xml:6310(term) -msgid "config_button" -msgstr "config_button" - -#: C/gdm.xml:6312(para) -msgid "Runs the GDM configuration application." -msgstr "Runs the GDM configuration application." - -#: C/gdm.xml:6319(term) -msgid "custom_cmd_button[0-9]" -msgstr "custom_cmd_button[0-9]" - -#: C/gdm.xml:6321(para) -msgid "Runs the <filename>n-th</filename> custom command." -msgstr "Runs the <filename>n-th</filename> custom command." - -#: C/gdm.xml:6328(term) -msgid "disconnect_button" -msgstr "disconnect_button" - -#: C/gdm.xml:6330(para) -msgid "Disconnect from remote session." -msgstr "Disconnect from remote session." - -#: C/gdm.xml:6337(term) -msgid "language_button" -msgstr "language_button" - -#: C/gdm.xml:6339(para) -msgid "Displays the language selection dialog." -msgstr "Displays the language selection dialogue." - -#: C/gdm.xml:6346(term) -msgid "halt_button" -msgstr "halt_button" - -#: C/gdm.xml:6348(para) -msgid "Halt (shuts down) the system." -msgstr "Halt (shuts down) the system." - -#: C/gdm.xml:6355(term) -msgid "reboot_button" -msgstr "reboot_button" - -#: C/gdm.xml:6357(para) -msgid "Restart the system." -msgstr "Restart the system." - -#: C/gdm.xml:6364(term) -msgid "session_button" -msgstr "session_button" - -#: C/gdm.xml:6366(para) -msgid "List and select from available sessions." -msgstr "List and select from available sessions." - -#: C/gdm.xml:6373(term) -msgid "suspend_button" -msgstr "suspend_button" - -#: C/gdm.xml:6375(para) -msgid "Suspend the system." -msgstr "Suspend the system." - -#: C/gdm.xml:6382(term) -msgid "system_button" -msgstr "system_button" - -#: C/gdm.xml:6384(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 "Perform halt/restart/suspend/etc. options (if allowed by GDM configuration). Also allows the user to run configurator if the user enters the root password (if allowed by the GDM configuration). This is labelled Actions, and referred to as the Actions menu." - -#: C/gdm.xml:6397(title) -msgid "Position Node" -msgstr "Position Node" - -#: C/gdm.xml:6399(para) -msgid "" -"Each item can specify its position and size via the \"pos\" node. For example: <screen>\n" -"<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" -"</screen>" -msgstr "" -"Each item can specify its position and size via the \"pos\" node. For example: <screen>\n" -"<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" -"</screen>" - -#: C/gdm.xml:6407(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 "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." - -#: C/gdm.xml:6413(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 "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." - -#: C/gdm.xml:6420(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: <screen>\n" -"<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/>\n" -"</screen>" -msgstr "" -"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 centre. For example: <screen>\n" -"<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/>\n" -"</screen>" - -#: C/gdm.xml:6431(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 "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." - -#: C/gdm.xml:6437(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 "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." - -#: C/gdm.xml:6443(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 "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)." - -#: C/gdm.xml:6450(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: <screen>\n" -"<item type=\"label\">\n" -"<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -"</screen>" -msgstr "" -"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: <screen>\n" -"<item type=\"label\">\n" -"<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -"</screen>" - -#: C/gdm.xml:6466(title) -msgid "Show Node" -msgstr "Show Node" - -#: C/gdm.xml:6468(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 "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:" - -#: C/gdm.xml:6474(para) -msgid "<filename>console</filename> - In console mode." -msgstr "<filename>console</filename> - In console mode." - -#: C/gdm.xml:6477(para) -msgid "<filename>console-fixed</filename> - In console non-flexi mode." -msgstr "<filename>console-fixed</filename> - In console non-flexi mode." - -#: C/gdm.xml:6480(para) -msgid "<filename>console-flexi</filename> - In console & flexi mode." -msgstr "<filename>console-flexi</filename> - In console & flexi mode." - -#: C/gdm.xml:6483(para) -msgid "<filename>flexi</filename> - In flexi mode." -msgstr "<filename>flexi</filename> - In flexi mode." - -#: C/gdm.xml:6486(para) -msgid "<filename>remote</filename> - In remote mode." -msgstr "<filename>remote</filename> - In remote mode." - -#: C/gdm.xml:6489(para) -msgid "<filename>remote-flexi</filename> - In remote & flexi mode." -msgstr "<filename>remote-flexi</filename> - In remote & flexi mode." - -#: C/gdm.xml:6493(para) -msgid "" -"For example: <screen>\n" -"<show modes=\"flexi,remote\"/>\n" -"</screen>" -msgstr "" -"For example: <screen>\n" -"<show modes=\"flexi,remote\"/>\n" -"</screen>" - -#: C/gdm.xml:6500(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 "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:" - -#: C/gdm.xml:6506(para) -msgid "<filename>chooser</filename>, if ChooserButton is set to \"true\" in the GDM configuration." -msgstr "<filename>chooser</filename>, if ChooserButton is set to \"true\" in the GDM configuration." - -#: C/gdm.xml:6510(para) -msgid "<filename>config</filename>, if ConfigAvailable is set to \"true\" in the GDM configuration." -msgstr "<filename>config</filename>, if ConfigAvailable is set to \"true\" in the GDM configuration." - -#: C/gdm.xml:6514(para) -msgid "<filename>custom_cmd[0-9]</filename>, if <filename>n-th</filename> CustomCommand is specified in the GDM configuration." -msgstr "<filename>custom_cmd[0-9]</filename>, if <filename>n-th</filename> CustomCommand is specified in the GDM configuration." - -#: C/gdm.xml:6518(para) -msgid "<filename>halt</filename>, if HaltDaemon is specified in the GDM configuration." -msgstr "<filename>halt</filename>, if HaltDaemon is specified in the GDM configuration." - -#: C/gdm.xml:6522(para) -msgid "<filename>reboot</filename>, if RebootCommand is specified in the GDM configuration." -msgstr "<filename>reboot</filename>, if RebootCommand is specified in the GDM configuration." - -#: C/gdm.xml:6526(para) -msgid "<filename>suspend</filename>, if SuspendCommand is specified in the GDM configuration." -msgstr "<filename>suspend</filename>, if SuspendCommand is specified in the GDM configuration." - -#: C/gdm.xml:6530(para) -msgid "<filename>system</filename>, if SystemMenu is specified in the GDM configuration." -msgstr "<filename>system</filename>, if SystemMenu is specified in the GDM configuration." - -#: C/gdm.xml:6534(para) -msgid "<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in the GDM configuration." -msgstr "<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in the GDM configuration." - -#: C/gdm.xml:6539(para) -msgid "" -"For example: <screen>\n" -"<show modes=\"console\" type=\"system\"/>\n" -"</screen>" -msgstr "" -"For example: <screen>\n" -"<show modes=\"console\" type=\"system\"/>\n" -"</screen>" - -#: C/gdm.xml:6546(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 "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." - -#: C/gdm.xml:6555(title) -msgid "Normal/Active/Prelight Nodes" -msgstr "Normal/Active/Prelight Nodes" - -#: C/gdm.xml:6557(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 "Depending on the item type (except for userlist - refer to colour node below), it can specify its colour, font or image via the following tags:" - -#: C/gdm.xml:6563(para) -msgid "<filename>normal</filename> - normal state." -msgstr "<filename>normal</filename> - normal state." - -#: C/gdm.xml:6566(para) -msgid "<filename>active</filename> - when the item has active focus." -msgstr "<filename>active</filename> - when the item has active focus." - -#: C/gdm.xml:6569(para) -msgid "<filename>prelight</filename> - when the mouse is hovering over the item." -msgstr "<filename>prelight</filename> - when the mouse is hovering over the item." - -#: C/gdm.xml:6574(para) -msgid "" -"When item is \"rect\" (alpha can be omitted and defaults to 0.0): <screen>\n" -"<normal color=\"#ffffff\" alpha=\"0.0\">\n" -"</screen>" -msgstr "" -"When item is \"rect\" (alpha can be omitted and defaults to 0.0): <screen>\n" -"<normal colour=\"#ffffff\" alpha=\"0.0\">\n" -"</screen>" - -#: C/gdm.xml:6582(para) -msgid "" -"When item is \"label\" <screen>\n" -"<normal color=\"#ffffff\" font=\"Sans 14\"/>\n" -"</screen>" -msgstr "" -"When item is \"label\" <screen>\n" -"<normal colour=\"#ffffff\" font=\"Sans 14\"/>\n" -"</screen>" - -#: C/gdm.xml:6589(para) -msgid "" -"When the item type is \"pixmap\" or \"SVG\", then the normal, active, and prelight tags specify the images to use as follows: <screen>\n" -"<normal file=\"picture.png\" tint=\"#dddddd\"/>\n" -"</screen>" -msgstr "" -"When the item type is \"pixmap\" or \"SVG\", then the normal, active, and prelight tags specify the images to use as follows: <screen>\n" -"<normal file=\"picture.png\" tint=\"#dddddd\"/>\n" -"</screen>" - -#: C/gdm.xml:6598(para) -msgid "Note that relative pathnames are assumed to be in the same directory as the theme <filename>.xml</filename> file in <filename><share>/gdm/themes/<theme_name></filename>." -msgstr "Note that relative pathnames are assumed to be in the same directory as the theme <filename>.xml</filename> file in <filename><share>/gdm/themes/<theme_name></filename>." - -#: C/gdm.xml:6604(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: <screen>\n" -"<normal file=\"picture.png\" altfile1=\"distribution-blah-image.png\" altfile2=\"distribution-foo-image.png\"/>\n" -"</screen> If <filename>distribution-foo-image.png</filename> 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 "" -"Note that alternative image file can be specified using the altfile[n] property. GDM will use the last valid image filename specified. For example: <screen>\n" -"<normal file=\"picture.png\" altfile1=\"distribution-blah-image.png\" altfile2=\"distribution-foo-image.png\"/>\n" -"</screen> If <filename>distribution-foo-image.png</filename> 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." - -#: C/gdm.xml:6619(title) -msgid "Face Browser Icon/Label Color Nodes" -msgstr "Face Browser Icon/Label Colour Nodes" - -#: C/gdm.xml:6621(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 "If the item type is of userlist, then the background colour for the icon and label can be set separately via the the following tag:" - -#: C/gdm.xml:6627(screen) -#, no-wrap -msgid "" -"\n" -"<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" -msgstr "" -"\n" -"<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" - -#: C/gdm.xml:6634(title) -msgid "Text Node" -msgstr "Text Node" - -#: C/gdm.xml:6636(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): <screen>\n" -"<text xml:lang=\"fr\">Option</text>\n" -"</screen>" -msgstr "" -"Text tags are used by labels. They can be used to display localised text as follows (if the \"xml:lang\" attribute is omitted, the C locale is assumed): <screen>\n" -"<text xml:lang=\"fr\">Option</text>\n" -"</screen>" - -#: C/gdm.xml:6645(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: <screen>\n" -"<text>\"foo<sup>bar</sup>\"</text>\n" -"</screen>" -msgstr "" -"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: <screen>\n" -"<text>\"foo<sup>bar</sup>\"</text>\n" -"</screen>" - -#: C/gdm.xml:6654(para) -msgid "Text nodes can contain the following special character sequences which will be translated as follows:" -msgstr "Text nodes can contain the following special character sequences which will be translated as follows:" - -#: C/gdm.xml:6659(para) -msgid "%% - A literal % character" -msgstr "%% - A literal % character" - -#: C/gdm.xml:6662(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 - Clock time. Only labels with the \"clock\" id will update automatically every second. Other labels will contain a static timestamp." - -#: C/gdm.xml:6667(para) -msgid "%d - Display name (DISPLAY environment variable)" -msgstr "%d - Display name (DISPLAY environment variable)" - -#: C/gdm.xml:6670(para) -msgid "%h - Hostname (gethostname output)" -msgstr "%h - Hostname (gethostname output)" - -#: C/gdm.xml:6673(para) -msgid "%m - Machine name (uname.machine output)" -msgstr "%m - Machine name (uname.machine output)" - -#: C/gdm.xml:6676(para) -msgid "%n - Node name (uname.nodename output)" -msgstr "%n - Node name (uname.nodename output)" - -#: C/gdm.xml:6679(para) -msgid "%o - Domain name (getdomainname output)" -msgstr "%o - Domain name (getdomainname output)" - -#: C/gdm.xml:6682(para) -msgid "%r - Release name (uname.release output)" -msgstr "%r - Release name (uname.release output)" - -#: C/gdm.xml:6685(para) -msgid "%s - System name (uname.sysname output)" -msgstr "%s - System name (uname.sysname output)" - -#: C/gdm.xml:6688(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 "%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." - -#: C/gdm.xml:6696(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 "%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." - -#: C/gdm.xml:6702(para) -msgid "" -"\\n" -" - Carriage return" -msgstr "" -"\\n" -" - Carriage return" - -#: C/gdm.xml:6705(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 "_ - An underscore causes the following character to be underlined. If it precedes a % character sequence, the string that replaces the character sequence is underlined." - -#: C/gdm.xml:6713(title) -msgid "Stock" -msgstr "Stock" - -#: C/gdm.xml:6715(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 "Certain common localised 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:" - -#: C/gdm.xml:6724(para) -msgid "<filename>cancel</filename>, _(\"_Cancel\"" -msgstr "<filename>cancel</filename>, _(\"_Cancel\"" - -#: C/gdm.xml:6727(para) -msgid "<filename>caps-lock-warning</filename>, _(\"Caps Lock key is on.\"" -msgstr "<filename>caps-lock-warning</filename>, _(\"Caps Lock key is on.\"" - -#: C/gdm.xml:6731(para) -msgid "<filename>chooser</filename>, _(\"Remote Login via _XDMCP\"" -msgstr "<filename>chooser</filename>, _(\"Remote Login via _XDMCP\"" - -#: C/gdm.xml:6734(para) -msgid "<filename>config</filename>, _(\"_Configure\"" -msgstr "<filename>config</filename>, _(\"_Configure\"" - -#: C/gdm.xml:6737(para) -msgid "<filename>custom_cmd[0-9]</filename>, _(\"Custom_[0-9]\"" -msgstr "<filename>custom_cmd[0-9]</filename>, _(\"Custom_[0-9]\"" - -#: C/gdm.xml:6740(para) -msgid "<filename>disconnect</filename>, _(\"D_isconnect\"" -msgstr "<filename>disconnect</filename>, _(\"D_isconnect\"" - -#: C/gdm.xml:6743(para) -msgid "<filename>halt</filename>, _(\"Shut _Down\"" -msgstr "<filename>halt</filename>, _(\"Shut _Down\"" - -#: C/gdm.xml:6746(para) -msgid "<filename>language</filename>, _(\"_Language\"" -msgstr "<filename>language</filename>, _(\"_Language\"" - -#: C/gdm.xml:6749(para) -msgid "<filename>ok</filename>, _(\"_OK\"" -msgstr "<filename>ok</filename>, _(\"_OK\"" - -#: C/gdm.xml:6752(para) -msgid "<filename>quit</filename>, _(\"_Quit\"" -msgstr "<filename>quit</filename>, _(\"_Quit\"" - -#: C/gdm.xml:6755(para) -msgid "<filename>reboot</filename>, _(\"_Restart\"" -msgstr "<filename>reboot</filename>, _(\"_Restart\"" - -#: C/gdm.xml:6758(para) -msgid "<filename>session</filename>, _(\"_Session\"" -msgstr "<filename>session</filename>, _(\"_Session\"" - -#: C/gdm.xml:6761(para) -msgid "<filename>startover</filename>, _(\"_Start Over\"" -msgstr "<filename>startover</filename>, _(\"_Start Over\"" - -#: C/gdm.xml:6764(para) -msgid "<filename>suspend</filename>, _(\"Sus_pend\"" -msgstr "<filename>suspend</filename>, _(\"Sus_pend\"" - -#: C/gdm.xml:6767(para) -msgid "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\"" -msgstr "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\"" - -#: C/gdm.xml:6771(para) -msgid "<filename>timed-label</filename>, _(\"User %u will login in %t\"" -msgstr "<filename>timed-label</filename>, _(\"User %u will login in %t\"" - -#: C/gdm.xml:6775(para) -msgid "<filename>username-label</filename>, _(\"Username:\"" -msgstr "<filename>username-label</filename>, _(\"Username:\"" - -#: C/gdm.xml:6778(para) -msgid "<filename>welcome-label</filename>, _(\"Welcome to %n\"" -msgstr "<filename>welcome-label</filename>, _(\"Welcome to %n\"" - -#: C/gdm.xml:6782(para) -msgid "" -"For example: <screen>\n" -"<stock type=\"welcome-label\">\n" -"</screen>" -msgstr "" -"For example: <screen>\n" -"<stock type=\"welcome-label\">\n" -"</screen>" - -#: C/gdm.xml:6791(title) -msgid "Custom Widgetry" -msgstr "Custom Widgetry" - -#: C/gdm.xml:6793(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 <filename><ServAuthDir>/<display>.GreeterInfo</filename> as <filename><list id>=<listitem id></filename>." -msgstr "Currently there is one item which is customisable 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 set up the list item and add list item children that describe the choices. Each list item must have an id and a text child. The choice will be recorded in the file <filename><ServAuthDir>/<display>.GreeterInfo</filename> as <filename><list id>=<listitem id></filename>." - -#: C/gdm.xml:6804(para) -msgid "For example suppose we are on display :0, <filename>ServAuthDir</filename> is <filename><var>/lib/gdm</filename> and we have the following in the theme:" -msgstr "For example, suppose we are on display :0, <filename>ServAuthDir</filename> is <filename><var>/lib/gdm</filename> and we have the following in the theme:" - -#: C/gdm.xml:6811(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 "" -"\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" - -#: C/gdm.xml:6823(para) -msgid "" -"Then if the user chooses 'Foo' then <filename><var>/lib/gdm/:0.GreeterInfo</filename> will contain: <screen>\n" -"custom-config=foo\n" -"</screen>" -msgstr "" -"Then if the user chooses 'Foo' then <filename><var>/lib/gdm/:0.GreeterInfo</filename> will contain: <screen>\n" -"custom-config=foo\n" -"</screen>" - -#: C/gdm.xml:6835(title) -msgid "Accessibility" -msgstr "Accessibility" - -#: C/gdm.xml:6836(para) -msgid "GDM supports \"Accessible Login\" to allow users to log in to their desktop session even if they cannot easily use the screen, mouse, or keyboard in the usual way. Only the \"Standard Greeter\" supports accessibility, so use this login GUI for accessibility support. This is done by specifying the \"Standard Greeter\" in the \"Local\" tab for the console display and specifying the \"Standard Greeter\" in the \"Remote\" tab for remote displays. Or you can modify the <filename>Greeter</filename> configuration option by hand to be <command>gdmlogin</command>." -msgstr "GDM supports \"Accessible Login\" to allow users to log in to their desktop session even if they cannot easily use the screen, mouse or keyboard in the usual way. Only the \"Standard Greeter\" supports accessibility, so use this login GUI for accessibility support. This is done by specifying the \"Standard Greeter\" in the \"Local\" tab for the console display and specifying the \"Standard Greeter\" in the \"Remote\" tab for remote displays. Or you can modify the <filename>Greeter</filename> configuration option by hand to be <command>gdmlogin</command>." - -#: C/gdm.xml:6848(para) -msgid "The Standard Greeter supports the ability to launch assistive technologies at login time via configurable \"gestures\" from the standard keyboard, pointing device, or switch device attached to the USB or PS/2 mouse port. Also the user can change the visual appearance of the login UI before logging in, for instance to use a higher-contrast color scheme for better visibility." -msgstr "The Standard Greeter supports the ability to launch assistive technologies at login time via configurable \"gestures\" from the standard keyboard, pointing device or switch device attached to the USB or PS/2 mouse port. Also the user can change the visual appearance of the login user interface before logging in, for instance to use a higher-contrast colour scheme for better visibility." - -#: C/gdm.xml:6858(title) -msgid "Accessibility Configuration" -msgstr "Accessibility Configuration" - -#: C/gdm.xml:6859(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 configuration, AccessKeyMouseEvents and AccessDwellMouseEvents." -msgstr "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 configuration, AccessKeyMouseEvents and AccessDwellMouseEvents." - -#: C/gdm.xml:6867(para) -msgid "In order to allow users to change the color and contrast scheme of the login dialog, make sure the <filename>AllowThemeChange</filename> parameter in the GDM configuration is set to \"true\"." -msgstr "In order to allow users to change the colour and contrast scheme of the login dialogue, make sure the <filename>AllowThemeChange</filename> parameter in the GDM configuration is set to \"true\"." - -#: C/gdm.xml:6874(para) -msgid "To restrict user changes to the visual appearance to a subset of available themes, the <filename>GtkThemesToAllow</filename> parameter in the GDM configuration can be set to a list of acceptable themes separated by commas. For example:" -msgstr "To restrict user changes to the visual appearance to a subset of available themes, the <filename>GtkThemesToAllow</filename> parameter in the GDM configuration can be set to a list of acceptable themes separated by commas. For example:" - -#: C/gdm.xml:6881(screen) -#, no-wrap -msgid "" -"\n" -"GtkThemesToAllow=HighContrast,HighContrastInverse\n" -msgstr "" -"\n" -"GtkThemesToAllow=HighContrast,HighContrastInverse\n" - -#: C/gdm.xml:6885(para) -msgid "To enable the use of assistive technologies such as the Onscreen Keyboard, Screen Reader, or Magnifier, the <filename>AddGtkModules</filename> parameter in the GDM configuration must be uncommented and set to \"true\". Also the <filename>GtkModulesList</filename> parameter must be uncommented and set as follows:" -msgstr "To enable the use of assistive technologies such as the Onscreen Keyboard, Screen Reader, or Magnifier, the <filename>AddGtkModules</filename> parameter in the GDM configuration must be uncommented and set to \"true\". Also the <filename>GtkModulesList</filename> parameter must be uncommented and set as follows:" - -#: C/gdm.xml:6894(screen) -#, no-wrap -msgid "" -"\n" -"GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener\n" -msgstr "" -"\n" -"GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener\n" - -#: C/gdm.xml:6898(para) -msgid "The use of assistive technologies and the atk-bridge module requires the registry daemon, <command>at-spi-registryd</command>, to be running. This is handled by the GDM GUI starting with version 2.17." -msgstr "The use of assistive technologies and the atk-bridge module requires the registry daemon, <command>at-spi-registryd</command>, to be running. This is handled by the GDM GUI starting with version 2.17." - -#: C/gdm.xml:6905(para) -msgid "System administrators may wish to load only the minimum subset of these modules which is required to support their user base. Depending on the end-user needs, not all of the above GtkModules may need to be loaded. If your end-users need the integrated Screen Reader and Magnifier, you must include \"gail\" and \"atk-bridge\". If your end-users will be using a pointing device without buttons or switches, include \"dwellmouselistener\". If some of your users will use pointing devices with switches, alternative physical keyboards, or switch/button devices, include \"keymouselistener\". Including all four is suitable for most system configurations. The Onscreen Keyboard can operate without gail and atk-bridge, but with a reduced feature set; for optimum accessibility we recommend including both gail and atk-bridge." -msgstr "System administrators may wish to load only the minimum subset of these modules which is required to support their user base. Depending on the end-user needs, not all of the above GtkModules may need to be loaded. If your end-users need the integrated Screen Reader and Magnifier, you must include \"gail\" and \"atk-bridge\". If your end-users will be using a pointing device without buttons or switches, include \"dwellmouselistener\". If some of your users will use pointing devices with switches, alternative physical keyboards, or switch/button devices, include \"keymouselistener\". Including all four is suitable for most system configurations. The Onscreen Keyboard can operate without gail and atk-bridge, but with a reduced feature set; for optimum accessibility we recommend including both gail and atk-bridge." - -#: C/gdm.xml:6922(para) -msgid "Once \"keymouselistener\" and/or \"dwellmouselistener\" have been added to the GtkModules loaded by GDM, you can assign end-user actions with the launching of specific assistive technologies. These gesture associations are contained in files AccessKeyMouseEvents and AccessDwellMouseEvents, respectively. Both files are located in the <etc>/gdm/modules directory. The gesture format is described in the two configuration files." -msgstr "Once \"keymouselistener\" and/or \"dwellmouselistener\" have been added to the GtkModules loaded by GDM, you can assign end-user actions with the launching of specific assistive technologies. These gesture associations are contained in files AccessKeyMouseEvents and AccessDwellMouseEvents, respectively. Both files are located in the <etc>/gdm/modules directory. The gesture format is described in the two configuration files." - -#: C/gdm.xml:6933(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 Xserver command line for gestures to work properly." -msgstr "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 Xserver command line for gestures to work properly." - -#: C/gdm.xml:6945(para) -msgid "The DwellKeyMouseEvents file controls the dwellmouselistner and supports gestures that involve only 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. 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 "The DwellKeyMouseEvents file controls the dwellmouselistner and supports gestures that involve only 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. 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." - -#: C/gdm.xml:6955(para) -msgid "Motion gestures are defined as \"crossing events\" into and out of the login dialog window. If the \"dwellmouselistener\" GtkModule is loaded, alternative pointing devices are temporarily \"latched\" to the core pointer, such that motion from alternative devices results in movement of the onscreen pointer." -msgstr "Motion gestures are defined as \"crossing events\" into and out of the login dialogue window. If the \"dwellmouselistener\" GtkModule is loaded, alternative pointing devices are temporarily \"latched\" to the core pointer, such that motion from alternative devices results in movement of the on screen pointer." - -#: C/gdm.xml:6964(para) -msgid "In order to use text-to-speech services at login time (for instance, when using the Screen Reader in speech mode) on some operating systems, the GDM user must be made a member of the \"audio\" group" -msgstr "In order to use text-to-speech services at login time (for instance, when using the Screen Reader in speech mode) on some operating systems, the GDM user must be made a member of the \"audio\" group" - -#: C/gdm.xml:6971(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 "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." - -#: C/gdm.xml:6982(para) -msgid "There are some issues that cause users to have problems getting the gesture listeners to work. It is recommended that people use GDM version 2.8.0.5 or later for best results. Some 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. Some versions of GOK and gnopernicus will not launch unless the \"gdm\" user has a writable home directory. If you see an hourglass cursor when you complete a gesture but the program does not start, then you are likely having this problem. It should be considered a bug for AT programs to require having a writable home directory, so please file a bug with the AT program if you encounter this problem. Also note that some input devices require X server configuration before GDM will recognize them." -msgstr "There are some issues that cause users to have problems getting the gesture listeners to work. It is recommended that people use GDM version 2.8.0.5 or later for best results. Some 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. Some versions of GOK and gnopernicus will not launch unless the \"gdm\" user has a writable home directory. If you see an hourglass cursor when you complete a gesture but the program does not start, then you are likely having this problem. It should be considered a bug for AT programs to require having a writable home directory, so please file a bug with the AT program if you encounter this problem. Also note that some input devices require X server configuration before GDM will recognise them." - -#: C/gdm.xml:7003(title) -msgid "Accessibility Login Sound Configuration" -msgstr "Accessibility Login Sound Configuration" - -#: C/gdm.xml:7004(para) -msgid "By default, GDM requires a media application such as \"sox\" to be present to play sounds for successful or failed login. GDM defaults the location of this application to <filename><bin>/play</filename> (or <filename><bin>/audioplay</filename> on Solaris. This can be changed via the SoundProgram GDM configuration option. Typically most text-to-speech programs (such as ORCA or Gnopernicus) use a separate mechanism to play audio." -msgstr "By default, GDM requires a media application such as \"sox\" to be present to play sounds for successful or failed login. GDM defaults the location of this application to <filename><bin>/play</filename> (or <filename><bin>/audioplay</filename> on Solaris. This can be changed via the SoundProgram GDM configuration option. Typically most text-to-speech programs (such as ORCA or Gnopernicus) use a separate mechanism to play audio." - -#: C/gdm.xml:7019(title) -msgid "Solaris Specific Features" -msgstr "Solaris Specific Features" - -#: C/gdm.xml:7022(title) -msgid "Solaris Configuration" -msgstr "Solaris Configuration" - -#: C/gdm.xml:7023(para) -msgid "" -"On Solaris, the following configuration is recommended. This turns on IPv6 and also turns on PreFetch for performance benefit. <screen>\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\n" -"</screen>" -msgstr "" -"On Solaris, the following configuration is recommended. This turns on IPv6 and also turns on PreFetch for performance benefit. <screen>\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\n" -"</screen>" - -#: C/gdm.xml:7035(para) -msgid "Configuring GDM with the \"--with-post-path=/usr/openwin/bin\" on Solaris is recommended for access to programs like Xnest." -msgstr "Configuring GDM with the \"--with-post-path=/usr/openwin/bin\" on Solaris is recommended for access to programs like Xnest." - -#: C/gdm.xml:7043(title) -msgid "Solaris /etc/logindevperm" -msgstr "Solaris /etc/logindevperm" - -#: C/gdm.xml:7044(para) -msgid "GDM supports /etc/logindevperm, but only on Solaris 10 and higher. Refer to the logindevperm.4 man page for more information." -msgstr "GDM supports /etc/logindevperm, but only on Solaris 10 and higher. Refer to the logindevperm.4 man page for more information." - -#: C/gdm.xml:7049(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 "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:" - -#: C/gdm.xml:7056(screen) -#, no-wrap -msgid "" -"\n" -"/dev/console 0600 /dev/sound/* # audio devices\n" -msgstr "" -"\n" -"/dev/console 0600 /dev/sound/* # audio devices\n" - -#: C/gdm.xml:7060(para) -msgid "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 "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." - -#: C/gdm.xml:7073(title) -msgid "Solaris Automatic Login" -msgstr "Solaris Automatic Login" - -#: C/gdm.xml:7074(para) -msgid "Automatic login does not work on Solaris 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 "Automatic login does not work on Solaris 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 log in to a specified username on startup without asking for username and password. This is an insecure way to set up your computer." - -#: C/gdm.xml:7085(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 "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." - -#: C/gdm.xml:7093(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 "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." - -#: C/gdm.xml:7101(screen) -#, no-wrap -msgid "" -"\n" -" gdm-autologin auth required pam_unix_cred.so.1\n" -" gdm-autologin auth sufficient pam_allow.so.1\n" -" gdm-autologin account sufficient pam_allow.so.1\n" -" gdm-autologin session sufficient pam_allow.so.1\n" -" gdm-autologin password sufficient pam_allow.so.1\n" -msgstr "" -"\n" -" gdm-autologin auth required pam_unix_cred.so.1\n" -" gdm-autologin auth sufficient pam_allow.so.1\n" -" gdm-autologin account sufficient pam_allow.so.1\n" -" gdm-autologin session sufficient pam_allow.so.1\n" -" gdm-autologin password sufficient pam_allow.so.1\n" - -#: C/gdm.xml:7109(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 "The above setup will cause no lastlog entry to be generated. If a lastlog entry is desired, then use the following for session:" - -#: C/gdm.xml:7114(screen) -#, no-wrap -msgid "" -"\n" -" gdm-autologin session required pam_unix_session.so.1\n" -msgstr "" -"\n" -" gdm-autologin session required pam_unix_session.so.1\n" - -#: C/gdm.xml:7120(title) -msgid "Other Solaris Features" -msgstr "Other Solaris Features" - -#: C/gdm.xml:7121(para) -msgid "GDM supports a few features specific to Solaris, as follows:" -msgstr "GDM supports a few features specific to Solaris, as follows:" - -#: C/gdm.xml:7125(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 "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." - -#: C/gdm.xml:7131(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 "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." - -#: C/gdm.xml:7140(para) -msgid "Solaris supports the <filename>/etc/default/login</filename> interface, which affects the <filename>DefaultPath</filename>, <filename>RootPath</filename>, <filename>PasswordRequired</filename>, and <filename>AllowRemoteRoot</filename> options as described in the \"Configuration\" section." -msgstr "Solaris supports the <filename>/etc/default/login</filename> interface, which affects the <filename>DefaultPath</filename>, <filename>RootPath</filename>, <filename>PasswordRequired</filename>, and <filename>AllowRemoteRoot</filename> options as described in the \"Configuration\" section." - -#: C/gdm.xml:7152(title) -msgid "Example Configurations" -msgstr "Example Configurations" - -#: C/gdm.xml:7154(para) -msgid "This section has some example configurations that are useful for various setups." -msgstr "This section has some example configurations that are useful for various setups." - -#: C/gdm.xml:7160(title) -msgid "Terminal Lab With One Server" -msgstr "Terminal Lab With One Server" - -#: C/gdm.xml:7162(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 <filename>xterminal</filename> and let's call the server machine <filename>appserver</filename>. You install GDM on both." -msgstr "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 <filename>xterminal</filename> and let's call the server machine <filename>appserver</filename>. You install GDM on both." - -#: C/gdm.xml:7169(para) -msgid "" -"On <filename>appserver</filename> you enable XDMCP, so you have <screen>\n" -"[xdmcp]\n" -"Enable=true\n" -"</screen> If you want no local screens here, you can then make the <filename>[servers]</filename> section empty." -msgstr "" -"On <filename>appserver</filename> you enable XDMCP, so you have <screen>\n" -"[xdmcp]\n" -"Enable=true\n" -"</screen> If you want no local screens here, you can then make the <filename>[servers]</filename> section empty." - -#: C/gdm.xml:7179(para) -msgid "" -"On the <filename>xterminal</filename> you disable XDMCP (you don't want anyone to connect to the xterminal really). You will add a server type perhaps called <filename>Terminal</filename> as follows: <screen>\n" -"[server-Terminal]\n" -"name=Terminal server\n" -"command=/path/to/X -terminate\n" -"flexible=false\n" -"handled=false\n" -"</screen> This definition should in fact be included in the standard configuration file. Notice that we made the <filename>handled</filename> key false since we don't want GDM to handle this server localy. Also note that we have not yet added the <filename>-query</filename> argument, you can add that here, or in the <filename>[servers]</filename> section. We'll define our local servers as follows: <screen>\n" -"[servers]\n" -"0=Terminal -query appserver\n" -"</screen> This will run a direct XDMCP query to the server named <filename>appserver</filename>." -msgstr "" -"On the <filename>xterminal</filename> you disable XDMCP (you don't want anyone to connect to the xterminal really). You will add a server type perhaps called <filename>Terminal</filename> as follows: <screen>\n" -"[server-Terminal]\n" -"name=Terminal server\n" -"command=/path/to/X -terminate\n" -"flexible=false\n" -"handled=false\n" -"</screen> This definition should in fact be included in the standard configuration file. Notice that we made the <filename>handled</filename> key false since we don't want GDM to handle this server localy. Also note that we have not yet added the <filename>-query</filename> argument, you can add that here, or in the <filename>[servers]</filename> section. We'll define our local servers as follows: <screen>\n" -"[servers]\n" -"0=Terminal -query appserver\n" -"</screen> This will run a direct XDMCP query to the server named <filename>appserver</filename>." - -#: C/gdm.xml:7207(title) -msgid "Terminal Lab With Two Or More Servers" -msgstr "Terminal Lab With Two Or More Servers" - -#: C/gdm.xml:7209(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 <filename>appserverone</filename> and <filename>appservertwo</filename>. Again we'll call our example X terminal server <filename>xterminal</filename>. 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 "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 <filename>appserverone</filename> and <filename>appservertwo</filename>. Again we'll call our example X terminal server <filename>xterminal</filename>. 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." - -#: C/gdm.xml:7220(para) -msgid "" -"So on the <filename>xterminal</filename> you again disable XDMCP. You will add a server type perhaps called <filename>Chooser</filename> as follows: <screen>\n" -"[server-Chooser]\n" -"name=Chooser server\n" -"command=/path/to/X\n" -"flexible=false\n" -"chooser=true\n" -"</screen> And again this definition should in fact be included in the standard configuration file. Notice that we made the <filename>chooser</filename> 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: <screen>\n" -"[servers]\n" -"0=Chooser\n" -"</screen>" -msgstr "" -"So on the <filename>xterminal</filename> you again disable XDMCP. You will add a server type perhaps called <filename>Chooser</filename> as follows: <screen>\n" -"[server-Chooser]\n" -"name=Chooser server\n" -"command=/path/to/X\n" -"flexible=false\n" -"chooser=true\n" -"</screen> And again this definition should in fact be included in the standard configuration file. Notice that we made the <filename>chooser</filename> 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: <screen>\n" -"[servers]\n" -"0=Chooser\n" -"</screen>" - -#: C/gdm.xml:7243(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 <filename>[chooser]</filename> section you would have: <screen>\n" -"Hosts=appserverone,appservertwo\n" -"</screen> and any other servers you wish the users to be able to connect to." -msgstr "" -"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 <filename>[chooser]</filename> section you would have: <screen>\n" -"Hosts=appserverone,appservertwo\n" -"</screen> and any other servers you wish the users to be able to connect to." - -#: C/gdm.xml:7255(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 <filename>appserver</filename> and on the X terminals you'd have <screen>\n" -"[servers]\n" -"0=Terminal -indirect appserver\n" -"</screen> This way for example you only have to maintain one <filename>Hosts</filename> entry. However as a disadvantage then, the <filename>appserver</filename> 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 "" -"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 <filename>appserver</filename> and on the X terminals you'd have <screen>\n" -"[servers]\n" -"0=Terminal -indirect appserver\n" -"</screen> This way for example you only have to maintain one <filename>Hosts</filename> entry. However as a disadvantage then, the <filename>appserver</filename> 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." - -#: C/gdm.xml:7276(title) -msgid "Defining Custom Commands" -msgstr "Defining Custom Commands" - -#: C/gdm.xml:7278(para) -msgid "" -"Suppose you want to add a custom command to the GDM menu that will give you the oportunity to boot into other operating system such as Windoze. Jsut add the following options into the <filename>[customcommand]</filename> section of the GDM configuration file. <screen>\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" -" </screen> CustomCommand0 specifies two commands separated by a semicolon: <filename>/sbin/rebootwindoze</filename> and <filename>/usr/local/sbin/rebootwindoze</filename>. GDM will use the first valid command in the list. This allows different commands for different operating systems to be included." -msgstr "" -"Suppose you want to add a custom command to the GDM menu that will give you the oportunity to boot into another operating system such as Windoze. Just add the following options into the <filename>[customcommand]</filename> section of the GDM configuration file. <screen>\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" -" </screen> CustomCommand0 specifies two commands separated by a semicolon: <filename>/sbin/rebootwindoze</filename> and <filename>/usr/local/sbin/rebootwindoze</filename>. GDM will use the first valid command in the list. This allows different commands for different operating systems to be included." - -#: C/gdm.xml:7301(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 oportunity to run system update scripts from the login screen. Add the following options into the <filename>[customcommand]</filename> section of your GDM configuration file. <screen>\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" -" </screen>" -msgstr "" -"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 oportunity to run system update scripts from the login screen. Add the following options into the <filename>[customcommand]</filename> section of your GDM configuration file. <screen>\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" -" </screen>" - -#: C/gdm.xml:7321(para) -msgid "" -"Both custom commands could be defined as follows. <screen>\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" -" </screen>" -msgstr "" -"Both custom commands could be defined as follows. <screen>\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" -" </screen>" - -#: C/gdm.xml:7342(para) -msgid "" -"There can be up to 10 custom commands numbered 0-9. <screen>\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" -" </screen>" -msgstr "" -"There can be up to 10 custom commands numbered 0-9. <screen>\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" -" </screen>" - -#: C/gdm.xml:7376(title) -msgid "Troubleshooting" -msgstr "Troubleshooting" - -#: C/gdm.xml:7378(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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink> or send an email to the <address><email>gdm-list@gnome.org</email></address> mail list." -msgstr "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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink> or send an email to the <address><email>gdm-list@gnome.org</email></address> mail list." - -#: C/gdm.xml:7388(para) -msgid "If GDM is failing to work properly, it is always a good idea to include debug information. Use the <command>gdmsetup</command> 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 (<filename><var>/log/messages</filename> or <filename><var>/adm/messages</filename> 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 "If GDM is failing to work properly, it is always a good idea to include debug information. Use the <command>gdmsetup</command> command to turn on debugging (\"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 (<filename><var>/log/messages</filename> or <filename><var>/adm/messages</filename> 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)." - -#: C/gdm.xml:7402(para) -msgid "You should not leave debug on after collecting data. It will clutter your syslog and slow system performance." -msgstr "You should not leave debugging on after collecting data. It will clutter your syslog and slow system performance." - -#: C/gdm.xml:7408(title) -msgid "GDM Will Not Start" -msgstr "GDM Will Not Start" - -#: C/gdm.xml:7410(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 "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 dialogue when it tries to start, but it can be difficult to track down problems when GDM fails silently." - -#: C/gdm.xml:7419(para) -msgid "First make sure that the Xserver is configured properly. The GDM configuration file contains a command in the [server-Standard] section that is used for starting the Xserver. Verify that this command works on your system. Running this command from the console should start the Xserver. If it fails, then the problem is likely with your Xserver configuration. Refer to your Xserver error log for an idea of what the problem may be. The problem may also be that your Xserver requires different command-line options. If so, then modify the Xserver command in the GDM configuration file so that it is correct for your system." -msgstr "First make sure that the Xserver is configured properly. The GDM configuration file contains a command in the [server-Standard] section that is used for starting the Xserver. Verify that this command works on your system. Running this command from the console should start the Xserver. If it fails, then the problem is likely with your Xserver configuration. Refer to your Xserver error log for an idea of what the problem may be. The problem may also be that your Xserver requires different command-line options. If so, then modify the Xserver command in the GDM configuration file so that it is correct for your system." - -#: C/gdm.xml:7432(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 Xserver and a terminal program, set the shell environment variable DOING_GDM_DEVELOPMENT=1 and run <command><lib>/gdmlogin</command> or <command><lib>/gdmgreeter</command>. 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 "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 Xserver and a terminal program, set the shell environment variable DOING_GDM_DEVELOPMENT=1 and run <command><lib>/gdmlogin</command> or <command><lib>/gdmgreeter</command>. 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." - -#: C/gdm.xml:7445(para) -msgid "Also make sure that the <filename>/tmp</filename> directory has reasonable ownership and permissions, and that the machine's file system is not full. These problems will cause GDM to fail to start." -msgstr "Also make sure that the <filename>/tmp</filename> directory has reasonable ownership and permissions, and that the machine's file system is not full. These problems will cause GDM to fail to start." - -#: C/gdm.xml:7453(title) -msgid "GDM Will Not Access User Settings" -msgstr "GDM Will Not Access User Settings" - -#: C/gdm.xml:7455(para) -msgid "GDM saves user settings, such as your default session and default language, in the <filename>~/.dmrc</filename>. Other files, such as the user's <filename>~/.Xauthority</filename> 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 <filename>RelaxPermissions</filename> 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 "GDM saves user settings, such as your default session and default language, in the <filename>~/.dmrc</filename>. Other files, such as the user's <filename>~/.Xauthority</filename> 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 <filename>RelaxPermissions</filename> 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\"." - -#: C/gdm.xml:7474(title) -msgid "License" -msgstr "Licence" - -#: C/gdm.xml:7475(para) -msgid "This program is free software; you can redistribute it and/or modify it under the terms of the <ulink type=\"help\" url=\"gnome-help:gpl\"><citetitle>GNU General Public License</citetitle></ulink> as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version." -msgstr "This program is free software; you can redistribute it and/or modify it under the terms of the <ulink type=\"help\" url=\"gnome-help:gpl\"><citetitle>GNU General Public Licence</citetitle></ulink> as published by the Free Software Foundation; either version 2 of the Licence, or (at your option) any later version." - -#: C/gdm.xml:7483(para) -msgid "This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public License</citetitle> for more details." -msgstr "This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public Licence</citetitle> for more details." - -#: C/gdm.xml:7489(para) -msgid "A copy of the <citetitle>GNU General Public License</citetitle> is included as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also obtain a copy of the <citetitle>GNU General Public License</citetitle> from the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://www.fsf.org\">their Web site</ulink> or by writing to <address> Free Software Foundation, Inc. <street>59 Temple Place</street> - Suite 330 <city>Boston</city>, <state>MA</state><postcode>02111-1307</postcode><country>USA</country></address>" -msgstr "A copy of the <citetitle>GNU General Public Licence</citetitle> is included as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also obtain a copy of the <citetitle>GNU General Public Licence</citetitle> from the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://www.fsf.org\">their Web site</ulink> or by writing to <address> Free Software Foundation, Inc. <street>59 Temple Place</street> - Suite 330 <city>Boston</city>, <state>MA</state><postcode>02111-1307</postcode><country>USA</country></address>" - -#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2. -#: C/gdm.xml:0(None) -msgid "translator-credits" -msgstr "David Lodge <dave@cirt.net>, 2007" - diff --git a/docs/es/.cvsignore b/docs/es/.cvsignore deleted file mode 100644 index 611a1bf0..00000000 --- a/docs/es/.cvsignore +++ /dev/null @@ -1,5 +0,0 @@ -.xml2po.mo -Makefile -Makefile.in -*.out -omf_timestamp diff --git a/docs/es/es.po b/docs/es/es.po deleted file mode 100644 index 05f44b60..00000000 --- a/docs/es/es.po +++ /dev/null @@ -1,10984 +0,0 @@ -# translation of help.gnome-2-18.es.po to Español -# Francisco Javier F. Serrador <serrador@openshine.com>, 2003, 2007. -# Lucas Vieites <lucas@asixinformatica.com>, 2007. -# Jorge González <jorgegonz@svn.gnome.org>, 2007. -# translation of es.po to -msgid "" -msgstr "" -"Project-Id-Version: help.HEAD.es\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2007-09-18 15:23+0100\n" -"PO-Revision-Date: 2007-09-18 16:39+0200\n" -"Last-Translator: Jorge González <jorgegonz@svn.gnome.org>\n" -"Language-Team: Spanish <traductores@es.gnome.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"X-Generator: KBabel 1.11.4\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: C/gdm.xml:13(title) -msgid "Gnome Display Manager Reference Manual" -msgstr "Manual de referencia del Gestor de entrada de GNOME" - -#: C/gdm.xml:17(revnumber) -msgid "0.0" -msgstr "0.0" - -#: C/gdm.xml:18(date) -msgid "2007-01" -msgstr "2007-01" - -#: C/gdm.xml:23(para) -msgid "GDM is the GNOME Display Manager, a graphical login program." -msgstr "GDM es el Gestor de entrada de GNOME, un programa gráfico de entrada." - -#: C/gdm.xml:30(firstname) -msgid "Martin" -msgstr "Martin" - -#: C/gdm.xml:30(othername) -msgid "K." -msgstr "K." - -#: C/gdm.xml:31(surname) -msgid "Petersen" -msgstr "Petersen" - -#: C/gdm.xml:33(email) -msgid "mkp@mkp.net" -msgstr "mkp@mkp.net" - -#: C/gdm.xml:37(firstname) -msgid "George" -msgstr "George" - -#: C/gdm.xml:37(surname) -msgid "Lebl" -msgstr "Lebl" - -#: C/gdm.xml:39(email) -msgid "jirka@5z.com" -msgstr "jirka@5z.com" - -#: C/gdm.xml:43(firstname) -msgid "Brian" -msgstr "Brian" - -#: C/gdm.xml:43(surname) -msgid "Cameron" -msgstr "Cameron" - -#: C/gdm.xml:45(email) -msgid "Brian.Cameron@Sun.COM" -msgstr "Brian.Cameron@Sun.COM" - -#: C/gdm.xml:49(firstname) -msgid "Bill" -msgstr "Bill" - -#: C/gdm.xml:49(surname) -msgid "Haneman" -msgstr "Haneman" - -#: C/gdm.xml:51(email) -msgid "Bill.Haneman@Sun.COM" -msgstr "Bill.Haneman@Sun.COM" - -#: 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 "Martin K. Petersen" - -#: 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 "George Lebl" - -#: C/gdm.xml:63(holder) -msgid "Red Hat, Inc." -msgstr "Red Hat, Inc." - -#: C/gdm.xml:66(holder) -msgid "Sun Microsystems, Inc." -msgstr "Sun Microsystems, Inc." - -#: C/gdm.xml:2(para) -msgid "" -"Permission is granted to copy, distribute and/or modify this document under " -"the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any " -"later version published by the Free Software Foundation with no Invariant " -"Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy " -"of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or " -"in the file COPYING-DOCS distributed with this manual." -msgstr "" -"Se concede permiso para copiar, distribuir o modificar este documento según " -"las condiciones de la GNU Free Documentation License (GFDL), Versión 1.1 o " -"cualquier versión posterior publicada por la Free Software Foundation sin " -"Secciones invariantes, Textos de portada y Textos de contraportada. " -"Encontrará una copia de la GFDL en este <ulink type=\"help\" url=\"ghelp:fdl" -"\">enlace</ulink> o en el archivo COPYING-DOCS distribuido con este manual." - -#: C/gdm.xml:12(para) -msgid "" -"This manual is part of a collection of GNOME manuals distributed under the " -"GFDL. If you want to distribute this manual separately from the collection, " -"you can do so by adding a copy of the license to the manual, as described in " -"section 6 of the license." -msgstr "" -"Este manual forma parte de una colección de documentos de GNOME distribuidos " -"según la GFDL. Si desea distribuir este manual de forma independiente de la " -"colección, puede hacerlo agregando una copia de la licencia al documento, " -"según se describe en la sección 6 de la misma." - -#: 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 "" -"Muchos de los nombres utilizados por las empresas para distinguir sus " -"productos y servicios se consideran marcas comerciales. Cuando estos nombres " -"aparezcan en la documentación de GNOME, y siempre que se haya informado a " -"los miembros del Proyecto de documentación de GNOME de dichas marcas " -"comerciales, los nombres aparecerán en mayúsculas o con las iniciales en " -"mayúsculas." - -#: C/gdm.xml:35(para) -msgid "" -"DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, " -"EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT " -"THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS " -"MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE " -"RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR " -"MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR " -"MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL " -"WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY " -"SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN " -"ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION " -"OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND" -msgstr "" -"EL DOCUMENTO SE ENTREGA \"TAL CUAL\", SIN GARANTÍA DE NINGÚN TIPO, NI " -"EXPLÍCITA NI IMPLÍCITA INCLUYENDO, SIN LIMITACIÓN, GARANTÍA DE QUE EL " -"DOCUMENTO O VERSIÓN MODIFICADA DE ÉSTE CAREZCA DE DEFECTOS EN EL MOMENTO DE " -"SU VENTA, SEA ADECUADO A UN FIN CONCRETO O INCUMPLA ALGUNA NORMATIVA. TODO " -"EL RIESGO RELATIVO A LA CALIDAD, PRECISIÓN Y UTILIDAD DEL DOCUMENTO O SU " -"VERSIÓN MODIFICADA RECAE EN USTED. SI CUALQUIER DOCUMENTO O VERSIÓN " -"MODIFICADA DE AQUÉL RESULTARA DEFECTUOSO EN CUALQUIER ASPECTO, USTED (Y NO " -"EL REDACTOR INICIAL, AUTOR O AUTOR DE APORTACIONES) ASUMIRÁ LOS COSTES DE " -"TODA REPARACIÓN, MANTENIMIENTO O CORRECCIÓN NECESARIOS. ESTA EXENCIÓN DE " -"RESPONSABILIDAD SOBRE LA GARANTÍA ES UNA PARTE ESENCIAL DE ESTA LICENCIA. NO " -"SE AUTORIZA EL USO DE NINGÚN DOCUMENTO NI VERSIÓN MODIFICADA DE ÉSTE POR EL " -"PRESENTE, SALVO DENTRO DEL CUMPLIMIENTO DE LA EXENCIÓN DE RESPONSABILIDAD;Y" - -#: C/gdm.xml:55(para) -msgid "" -"UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING " -"NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY " -"CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE " -"DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON " -"FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF " -"ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, " -"WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES " -"OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED " -"VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE " -"POSSIBILITY OF SUCH DAMAGES." -msgstr "" -"EN NINGUNA CIRCUNSTANCIA NI BAJO NINGUNA TEORÍA LEGAL, SEA POR ERROR " -"(INCLUYENDO NEGLIGENCIA) CONTRATO O DOCUMENTO DE OTRO TIPO, EL AUTOR, EL " -"ESCRITOR INICIAL, EL AUTOR DE APORTACIONES NI NINGÚN DISTRIBUIDOR DEL " -"DOCUMENTO O VERSIÓN MODIFICADA DEL DOCUMENTO, NI NINGÚN PROVEEDOR DE NINGUNA " -"DE ESAS PARTES, SERÁ RESPONSABLE ANTE NINGUNA PERSONA POR NINGÚN DAÑO " -"DIRECTO, INDIRECTO, ESPECIAL, INCIDENTAL O DERIVADO DE NINGÚN TIPO, " -"INCLUYENDO, SIN LIMITACIÓN DAÑOS POR PÉRDIDA DE FONDO DE COMERCIO, PARO " -"TÉCNICO, FALLO INFORMÁTICO O AVERÍA O CUALQUIER OTRO POSIBLE DAÑO O AVERÍA " -"DERIVADO O RELACIONADO CON EL USO DEL DOCUMENTO O SUS VERSIONES MODIFICADAS, " -"AUNQUE DICHA PARTE HAYA SIDO INFORMADA DE LA POSIBILIDAD DE QUE SE " -"PRODUJESEN ESOS DAÑOS." - -#: C/gdm.xml:28(para) -msgid "" -"DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS " -"OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: " -"<placeholder-1/>" -msgstr "" -"ESTE DOCUMENTO Y LAS VERSIONES MODIFICADAS DEL MISMO SE OFRECEN SEGÚN LAS " -"CONDICIONES ESTABLECIDAS EN LA LICENCIA DE DOCUMENTACIÓN LIBRE DE GNU (GFDL) " -"Y TENIENDO EN CUENTA QUE: <placeholder-1/>" - -#: C/gdm.xml:71(releaseinfo) C/gdm.xml:80(para) -msgid "" -"This manual describes version 2.21.0 of the GNOME Display Manager. It was " -"last updated on 09/17/2007." -msgstr "" -"Este manual describe la versión 2.21.0 del Gestor de entrada de GNOME. Se " -"actualizó por última vez el 17 de septiembre de 2007." - -#: C/gdm.xml:78(title) -msgid "Terms and Conventions Used in This Manual" -msgstr "Términos y convenciones usados en este manual" - -#: C/gdm.xml:85(para) -msgid "" -"Chooser - A program used to select a remote host for managing a display " -"remotely on the attached display (<command>gdmchooser</command>)." -msgstr "" -"Selector: Un programa que se usa para seleccionar un equipo remoto para " -"gestionar una pantalla remotamente en la pantalla local " -"(<command>gdmchooser</command>)." - -#: C/gdm.xml:90(para) -msgid "Configurator - The configuration application (<command>gdmsetup</command>)." -msgstr "Configurador: La aplicación de configuración (<command>gdmsetup</command>)." - -#: 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 "" -"GDM: El gestor de entrada de GNOME. Se usa para describir el paquete de " -"software como un todo. Algunas veces también se refiere a él como GDM2." - -#: C/gdm.xml:100(para) -msgid "gdm - The Gnome Display Manager daemon (<command>gdm</command>)." -msgstr "gdm: El demonio del gestor de entrada (<command>gdm</command>)." - -#: C/gdm.xml:104(para) -msgid "" -"Greeter - The graphical login window (<command>gdmlogin</command> or " -"<command>gdmgreeter</command>)." -msgstr "" -"Interfaz de entrada: La ventana de entrada gráfica (<command>gdmlogin</" -"command> o <command>gdmgreeter</command>)." - -#: C/gdm.xml:109(para) -msgid "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)." -msgstr "" -"Interfaz de entrada GTK+: La ventana de entrada estándar " -"( <command>gdmlogin</command>)." - -#: C/gdm.xml:113(para) -msgid "PAM - Pluggable Authentication Mechanism" -msgstr "" -"PAM: Mecanismo de complementos de autenticación (Pluggable Authentication " -"Mechanism)" - -#: C/gdm.xml:117(para) -msgid "Themed Greeter - The themable login window ( <command>gdmgreeter</command>)." -msgstr "" -"Interfaz de entrada con temas: La ventana de entrada con temas " -"intercambiables ( <command>gdmgreeter</command>)." - -#: C/gdm.xml:122(para) -msgid "XDMCP - X Display Manage Protocol" -msgstr "XDMCP: Protocolo de gestión de pantallas X (X Display Manage Protocol)" - -#: C/gdm.xml:126(para) -msgid "" -"Paths that start with a word in angle brackets are relative to the " -"installation prefix. I.e. <filename><share>/pixmaps/</filename> refers " -"to <filename><share>/pixmaps</filename> if GDM was configured with " -"<command>--prefix=/usr</command>. Normally also note that GDM is installed " -"with <command>--sysconfigdir=<etc>/X11</command>, meaning any path to " -"which we refer to as <filename><etc>/gdm/PreSession</filename> usually " -"means <filename><etc/X11>/gdm/PreSession</filename>. Note that for " -"interoperability it is recommended that you use a --prefix of <filename>/" -"usr</filename> and a --sysconfdir of <filename><etc>/X11</filename>." -msgstr "" -"Las rutas que comienzan con una palabra entre los símbolos paréntesis " -"angulosos son relativas al prefijo de instalación. Ej: <filename><" -"share>/pixmaps/</filename> se refiere a <filename>/usr/share/pixmaps</" -"filename> si GDM se ha configurado con <command>--prefix=/usr</command>. " -"Normalmente también denota que GDM está instalado con <command>--" -"sysconfigdir=/etc/X11</command>, que quiere decir que cualquier ruta a la " -"que se refiera como <filename><etc>/gdm/PreSession</filename> " -"usualmente significa <filename><etc/X11>/gdm/PreSession</filename>. " -"Note que para interoperatibilidad se recomienda que use un prefijo de " -"<filename>/usr</filename> y un directorio de configuración del sistema (--" -"sysconfdir) <filename>/etc/X11</filename>." - -#: C/gdm.xml:142(title) -msgid "Overview" -msgstr "Vista general" - -#: C/gdm.xml:145(title) -msgid "Introduction" -msgstr "Introducción" - -#: C/gdm.xml:149(para) -msgid "" -"The Gnome Display Manager (GDM) is a display manager that implements all " -"significant features required for managing attached and remote displays. GDM " -"was written from scratch and does not contain any XDM / X Consortium code." -msgstr "" -"El Gestor de entrada de GNOME (GDM) es un gestor de entrada que implementa " -"todas las características significativas requeridas para gestionar pantallas " -"remotas y locales. GDM se ha escrito desde cero y no contiene nada de código " -"de XDM / X Consortium." - -#: 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 "" -"Note que el GDM es altamente configurable y muchos ajustes de configuración " -"pueden afectar a la seguridad. Los temas sobre los que debe prestar atención " -"están resaltados en este documento y en los archivos de configuración del " -"GDM." - -#: C/gdm.xml:162(para) -msgid "" -"For further information about GDM, see the <ulink type=\"http\" url=\"http://" -"www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. Please " -"submit any bug reports or enhancement requests to the \"gdm\" category in " -"<ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</" -"ulink>. You can also send a message to the <address><email>gdm-list@gnome." -"org</email></address> mail list to discuss any issues or concerns with the " -"GDM program." -msgstr "" -"Para más información acerca de GDM, vea <ulink type=\"http\" url=\"http://" -"www.gnome.org/projects/gdm/\"> el sitio web del proyecto GDM</ulink>. Por " -"favor envíe cualquier informe de fallos o peticiones de mejoras a la " -"categoría «gdm» en <ulink type=\"http\" url=\"http://bugzilla.gnome.org/" -"\">bugzilla.gnome.org</ulink>. También puede enviar un mensaje a la lista de " -"correo <address><email>gdm-list@gnome.org</email></address> para tratar " -"sobre cualquier problema o cuestión con el programa GDM." - -#: C/gdm.xml:175(title) -msgid "Interface Stability" -msgstr "Estabilidad de interfaces" - -#: 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 " -"<filename>server-foo</filename>." -msgstr "" -"Los valores de pares de clave/valor definidos en los archivos de " -"configuración de GDM y la ubicación de estos archivos se consideran " -"interfaces «estables» y deberían cambiar sólo de formas compatibles hacia " -"atrás. Note que esto incluye las funcionalidades como los scripts de GDM " -"(Init, PreSession, PostSession, PostLogin, XKeepsCrashing, etc), las " -"ubicaciones de directorios (ServAuthDir, etc), las aplicaciones del sistema " -"(SoundProgram), etc. Algunos valores de configuración dependen de interfaces " -"del SO y quizá necesiten modificarse para que funcionen en un determinado " -"SO. Los ejemplos típicos son HaltCommand, RebootCommand, CustomCommands, " -"SuspendCommand, StandardXServer, Xnest, SoundProgram, y el valor del valor " -"\"command\" para cada <filename>server-tal</filename>." - -#: C/gdm.xml:193(para) -msgid "" -"Command-line interfaces for GDM programs installed to <filename><bin></" -"filename> and <filename><sbin></filename> 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 "" -"Los interfaces de línea de comandos para los programas GDM instalados en " -"<filename><bin></filename> y <filename><sbin></filename> se " -"consideran estables. Refiérase a su documentación de la distribución para " -"ver si hay cualquier cambio específico de la distribución a estos interfaces " -"de GDM y qué soporte existe para ellos." - -#: 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 <command>gdmchooser</command>. These " -"arguments have been changed to now use two dashes." -msgstr "" -"En las series de desarrollo 2.15 los argumentos de un solo guión no están " -"soportados más. Esto incluye los argumentos \"-xdmaddress\", \"-clientaddress" -"\", y \"-connectionType\" usados por <command>gdmchooser</command>. Estos " -"argumentos se han cambiado para que ahora usen dos guiones. " - -#: C/gdm.xml:209(para) -msgid "" -"If issues are discovered that break compatibility, please file a bug with an " -"\"urgent\" priority." -msgstr "" -"Si se descubrieran problemas que rompiesen la compatibilidad, por favor " -"envíe un error con una prioridad «urgente»." - -#: C/gdm.xml:216(title) -msgid "The GDM Daemon" -msgstr "El demonio GDM" - -#: 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 " -"<filename>Init</filename>, <filename>PostLogin</filename>, " -"<filename>PreSession</filename>, and <filename>PostSession</filename> " -"scripts discussed below are discussed in this \"Configuring GDM section\"." -msgstr "" -"El demonio GDM es responsable de gestionar pantallas en el sistema. Esto " -"incluye la autenticación de usuarios, iniciar la sesión del usuario y " -"terminar la sesión del usuario. GDM es configurable y las formas en que " -"puede configurarse se describen en la sección «Configurar GDM» de este " -"documento. Los scripts <filename>Init</filename>, <filename>PostLogin</" -"filename>, <filename>PreSession</filename>, y <filename>PostSession</" -"filename> de los que se habla más abajo se tratan en esta sección " -"«Configurar GDM»." - -#: 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 "" -"El demonio de GDM soporta un protocolo de sockets de dominio UNIX que puede " -"usarse para controlar aspectos de su comportamiento y para solicitarle " -"información. Este protocolo se describe en la sección «Controlar GDM» de " -"este documento." - -#: C/gdm.xml:236(para) -msgid "" -"GDM can be asked to manage a display a number of ways. Attached displays are " -"always managed when GDM starts and will be restarted when a user's session " -"is finished. Remote displays can be requested via XDMCP, flexible displays " -"via the <command>gdmflexiserver</command> command, and dynamic displays via " -"the <command>gdmdynamic</command> command. Displays that are started on " -"request are not restarted on session exit." -msgstr "" -"A GDM se le puede pedir que gestione una pantalla de varias formas. Las " -"pantallas locales las gestiona siempre GDM cuando se inicia y serán " -"reiniciadas cuando la sesión de un usuario termine. Las pantallas pueden " -"pedirse además a través de XDMCP, se pueden pedir pantallas flexibles " -"ejecutando el comando <command>gdmflexiserver</command>. y pantallas bajo " -"demanda a través del comando <command>gdmdynamic</command>. Las pantallas " -"que se inician bajo demanda no se reinician al salir de la sesión." - -#: C/gdm.xml:246(para) -msgid "" -"When the GDM daemon is asked to manage a display, it will fork an X server " -"process, then run the <filename>Init</filename> script as the root user, and " -"start the login GUI dialog as a slave process on the display. GDM can be " -"configured to use either <command>gdmgreeter</command> (the default) or " -"<command>gdmlogin</command> as the GUI dialog program. The " -"<command>gdmlogin</command> program supports accessibility while the " -"<command>gdmgreeter</command> program supports greater themeability. The GUI " -"dialog is run as the unpriviledged \"gdm\" user/group which is described in " -"the \"Security\" section below. The GUI dialog communicates with the daemon " -"via a sockets protocol and via standard input/output. The slave, for example " -"passes the username and password information to the GDM daemon via standard " -"input/output so the daemon can handle the actual authentication." -msgstr "" -"Cuando se le pide al demonio GDM que gestione una pantalla, bifurcará un " -"proceso servidor de X, después ejecutará el script <filename>Init</filename> " -"como el usuario root, e iniciará el diálogo de entrada como un proceso " -"esclavo en la pantalla. GDM puede configurarse para usar o bien " -"<command>gdmgreeter</command> (predeterminado) o <command>gdmlogin</command> " -"como programa de IGU para la entrada. El programa <command>gdmlogin</" -"command> soporta accesibilidad mientras que el programa <command>gdmgreeter</" -"command> soporta mayor temabilidad. El diálogo de la IGU se ejecuta como el " -"usuario/grupo no privilegiado «gdm» que se describe en la sección " -"«Seguridad» abajo. El diálogo de la IGU se comunica con el demonio por medio " -"de un protocolo de sockets y por medio de la entrada/salida estándar. El " -"esclavo, por ejemplo pasa el nombre del usuario y la contraseña al demonio " -"GDM por medio de la entrada/salida estándar así que el demonio puede " -"manipular la autenticación actual." - -#: C/gdm.xml:263(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 "" -"La pantalla de la IGU de la entrada permite al usuario seleccionar qué " -"sesión quiere iniciar y qué idioma quiere usar. Las sesiones se definen por " -"archivos que terminan con la extensión .desktop y puede encontrar más " -"información sobre estos archivos en la sección de «Configuración». El " -"usuario introduce su nombre y contraseña y si éstos le autentican con éxito, " -"GDM iniciará la sesión solicitada para el usuario. Es posible configurar GDM " -"para evitar el proceso de autenticación activando las características de " -"Entrada automática o Entrada temporizada en la configuración de GDM. El IGU " -"de entrada puede configurarse además para para proporcionar características " -"adicionales al usuario, como un visor de rostros, la capacidad de detener, " -"reiniciar o suspender el sistema; y o editar la configuración de entrada " -"(tras introducir la contraseña de root)." - -#: C/gdm.xml:278(para) -msgid "" -"GDM, by default, will use Pluggable Authentication Modules (PAM) for " -"authentication, but can also support regular crypt and shadow passwords on " -"legacy systems. After authenticating a user, the daemon runs the " -"<filename>PostLogin</filename> script as root, and forks a slave process to " -"start the requested session. This slave process runs the " -"<filename>PreSession</filename> script as root, sets up the user's " -"environment, and starts the requested session. GDM keeps track of the user's " -"default session and language in the user's <filename>~/.dmrc</filename> and " -"will use these defaults if the user did not pick a session or language in " -"the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN " -"interface after user authentication to tell the X server to be restarted as " -"the user instead of as root for added security. When the user's session " -"exits, the GDM daemon will run the <filename>PostSession</filename> script " -"as root." -msgstr "" -"GDM, por omisión, usará Pluggable Authentication Modules (PAM) para " -"autenticar, pero puede usar además contraseñas crypt y shadow en sistemas " -"legados. Tras autenticar al usuario, el demonio ejecuta el script " -"<filename>PostLogin</filename> como root, y bifurca un proceso esclavo para " -"iniciar la sesión solicitada. Este proceso esclavo ejecuta el script de " -"<filename>PreSession</filename> como root, establece el entorno del usuario " -"e inicia la sesión solicitada. GDM conserva la sesión predeterminada del " -"usuario y el idioma en el archivo <filename>~/.dmrc</filename> del usuario y " -"usará estos predeterminados si el usuario no seleccionó una sesión o idioma " -"en la IGU de entrada. En Solaris, GDM (desde la versión 2.8.0.3) usa el " -"interfaz SDTLOGIN después de autenticar al usuario para decir al servidor X " -"que se reinicie como el usuario en vez de como root para mayor seguridad. " -"Cuando la sesión del usuario sale, el demonio de GDM ejecutará el script " -"<filename>PostSession</filename> como root." - -#: C/gdm.xml:295(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 " -"<filename>PamStack</filename> 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 "" -"Tenga en cuenta que, de modo predeterminado, GDM utiliza «gdm» como nombre " -"de servicio para un inicio de sesión normal y el nombre «gdm-autologin» para " -"el inicio de sesión automático. Puede utilizar la opción de configuración " -"<filename>PamStack</filename> para indicar un nombre distinto. Por ejemplo, " -"si indica «foo», GDM utilizará el nombre «foo» para el servicio de inicio de " -"sesión normal y «foo-autologin» para el inicio de sesión automático." - -#: C/gdm.xml:305(para) -msgid "" -"For those looking at the code, the gdm_verify_user function in " -"<filename>daemon/verify-pam.c</filename> is used for normal login and the " -"gdm_verify_setup_user function is used for automatic login." -msgstr "" -"Para aquellos que estén viendo el código, la función gdm_verify_user en " -"<filename>daemon/verify-pam.c</filename> se utiliza para el inicio de sesión " -"normal y la función gdm_verify_setup_user para el inicio de sesión " -"automático." - -#: C/gdm.xml:313(title) -msgid "Different Display Types" -msgstr "Tipos de pantalla diferentes" - -#: C/gdm.xml:315(para) -msgid "" -"GDM supports three different display types: attached displays, flexible " -"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 "" -"GDM soporta tres tipos de pantalla diferentes: pantallas locales, pantallas " -"flexibles (bajo demanda), y pantallas remotas XDMCP. Las subsección " -"«Definiciones del servidor X» de la sección «Configuración» explica cómo se " -"configura el servidor X para las diferentes pantallas." - -#: C/gdm.xml:323(para) -msgid "" -"Attached (also known as local or static) displays are always started by the " -"daemon, and when they die or are killed, they are restarted. GDM can run as " -"many of these as needed. GDM can also manage displays on which it does not " -"manage a GUI login, thus GDM can be used for supporting X terminals. The " -"\"Attached DISPLAY Configuration\" subsection of the \"Configuration\" " -"section describes how attached displays are defined." -msgstr "" -"Las pantallas locales (también conocidas como estáticas) siempre se inician " -"por el demonio, y cuando mueren o se las mata, se reinician. GDM puede " -"ejecutar tantas como se necesiten. GDM también puede gestionar pantallas en " -"las cuales no gestiona la entrada de la IGU él mismo, permitiendo usar GDM " -"para soportar terminales X. La subsección «Configuración de la pantalla " -"local» de la sección «Configuración» describe cómo se definen las pantallas " -"locales." - -#: C/gdm.xml:333(para) -msgid "" -"Flexible (also known as on-demand) displays are only available to users " -"logged 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:347(para) -msgid "" -"Flexible displays may be started by running the <command>gdmflexiserver</" -"command> 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:360(para) -msgid "" -"The <filename>FlexibleXServers</filename>, <filename>FirstVT=7</filename>, " -"<filename>VTAllocation</filename>, and <filename>FlexiReapDelayMinutes</" -"filename> configuration settings are used to configure how flexible displays " -"operate." -msgstr "" -"Los ajustes de configuración <filename>FlexibleXServers</filename>, " -"<filename>FirstVT=7</filename>, <filename>VTAllocation</filename>, y " -"<filename>FlexiReapDelayMinutes</filename> se usan para configurar cómo " -"operan las pantallas flexibles." - -#: C/gdm.xml:367(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 " -"<command>gdmflexiserver -n</command> 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 <filename>Xnest</filename> " -"configuration option is used to configure how nested displays are started." -msgstr "" - -#: C/gdm.xml:380(para) -msgid "" -"The <command>gdmdynamic</command> is similar to <command>gdmflexiserver</" -"command> in the sense that it allows the user to manage displays " -"dynamically. However displays started with <command>gdmdynamic</command> are " -"treated as attached 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 \"Attached 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:395(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 "" -"El último tipo es la pantalla remota XDMCP que se describe en la siguiente " -"sección. Los equipos remotos pueden conectarse a GDM y presentar la pantalla " -"de entrada si esto está activado. Algunas cosas son diferentes para las " -"sesiones remotas. Por ejemplo, el menú Acciones que permite apagar, " -"reiniciar o configurar GDM no se mostrará." - -#: C/gdm.xml:406(title) -msgid "XDMCP" -msgstr "XDMCP" - -#: C/gdm.xml:410(para) -msgid "" -"The GDM daemon can be configured to listen for and manage X Display Manage " -"Protocol (XDMCP) requests from remote displays. By default XDMCP support is " -"turned off, but can be enabled if desired. If GDM is built with TCP Wrapper " -"support, then the daemon will only grant access to hosts specified in the " -"GDM service section in the TCP Wrappers configuration file." -msgstr "" -"El demonio GDM puede configurase para escuchar y gestionar las solicitudes " -"del protocolo X Display Manage Protocol (XDMCP) de las pantallas remotas. " -"Por omisión el soporte para XDMCP está desactivado, pero puede activarse si " -"se desea. Si GDM está construido con soporte TCP Wrapper, entonces el " -"demonio sólo permitirá acceder a equipos remotos especificados en la sección " -"de servicio GDM en el archivo de configuración de TCP Wrappers." - -#: C/gdm.xml:419(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 "" -"GDM incluye varias medidas para hacerlo más resistente a ataques de " -"denegación de servicio en el servicio XDMCP. Muchos de los parámetros del " -"protocolo, tiempos de espera negociación, etc pueden ajustarse finamente. " -"Sin embargo la configuración de fábrica debería funcionar en la mayoría de " -"sistemas. No la cambie a menos que sepa lo que está haciendo." - -#: C/gdm.xml:427(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 "" -"GDM escucha en el puerto UDP 177 y responderá a las peticiones QUERY y " -"BROADCAST_QUERY enviando un paquete WILLING al originador." - -#: C/gdm.xml:432(para) -msgid "" -"GDM can also be configured to honor INDIRECT queries and present a host " -"chooser to the remote display. GDM will remember the user's choice and " -"forward subsequent requests to the chosen manager. GDM also supports an " -"extension to the protocol which will make it forget the redirection once the " -"user's connection succeeds. This extension is only supported if both daemons " -"are GDM. It is transparent and will be ignored by XDM or other daemons that " -"implement XDMCP." -msgstr "" -"GDM también puede configurarse para confiar en solicitudes INDIRECT y " -"presentar un selector de equipos al display remoto. GDM recordará la " -"selección del usuario y reenviará las peticiones subsiguiente al gestor " -"seleccionado. GDM también soporta una extensión al protocolo que hará que se " -"olvide de la redirección una vez que la conexión del usuario tiene éxito. " -"Esta extensión está soportada sólo si ambos demonios son GDM. Es " -"transparente y será ignorada por XDM u otros demonios que implementan XDMCP." - -#: C/gdm.xml:442(para) -msgid "" -"If XDMCP seems to not be working, make sure that all machines are specified " -"in <filename>/etc/hosts</filename>." -msgstr "" -"Si parece que XDMCP no funciona, asegúrese de que todas las máquinas están " -"especificadas en <filename>/etc/hosts</filename>." - -#: C/gdm.xml:447(para) -msgid "" -"Refer to the \"Security\" section for information about security concerns " -"when using XDMCP." -msgstr "" -"Refiérase a la sección «Seguridad» para información acerca de las " -"preocupaciones de seguridad al usar XDMCP." - -#: C/gdm.xml:454(title) -msgid "Securing Remote Connection Through SSH" -msgstr "Securización de la conexión remota a través de SSH" - -#: C/gdm.xml:457(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 "" -"Tal como se explica en la sección «Seguridad», XDMCP no usa ninguna clase de " -"encriptación y debido a esto es inherentemente inseguro. Como XDMCP usa UDP " -"como capa de transporte de red, no es posible simplemente securizarla por " -"medio de un túnel SSH." - -#: C/gdm.xml:464(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 "" -"Para remediar este problema, GDM puede configurarse durante la compilación " -"con la opción --enable-secureremote, con la cual GDM propone como una sesión " -"integrada una sesión llamada «Conexión remota segura». Iniciar dicha sesión " -"permite al usuario introducir el nombre o la dirección del equipo en el que " -"quiere conectarse, siempre que dicho equipo remoto ejecute un servidor SSH, " -"el usuario entonces obtiene una conexión al servidor en la cual la sesión X " -"predeterminada se inicia y muestra en el equipo remoto local." - -#: C/gdm.xml:474(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 "" -"Usar esta sesión permite una conexión de red mucho más segura y sólo " -"necesita tener un servidor SSH ejecutándose en el equipo remoto remoto." - -#: C/gdm.xml:481(title) -msgid "The GTK+ Greeter" -msgstr "El interfaz GTK+" - -#: C/gdm.xml:483(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 "" -"El interfaz GTK+ es el interfaz gráfico de usuario predeterminado que se " -"presenta al usuario. El interfaz contiene un menú en la parte superior, un " -"visor de rostros opcional, un logo opcional y un widget para entrada de " -"texto. Este interfaz tiene soporte de accesibilidad completo, y debería " -"usarse por los usuarios con necesidades de accesibilidad." - -#: C/gdm.xml:491(para) -msgid "" -"The text entry field is used for entering logins, passwords, passphrases " -"etc. <command>gdmlogin</command> 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 "" -"El campo de entrada de texto se usa para introducir nombres de usuario, " -"contraseñas, etc. <command>gdmlogin</command> está controlado por un demonio " -"por debajo que es básicamente sin estado. El demonio controla el interfaz a " -"través de un protocolo simple donde puede pedir al interfaz una cadena de " -"texto con eco activado o desactivado. Similarmente, el demonio puede cambiar " -"la etiqueta sobre la entrada de texto para corresponder con el valor que el " -"sistema de autenticación quiere que el usuario introduzca." - -#: C/gdm.xml:501(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 "" -"La barra del menú en la parte superior del interfaz de entrada permite al " -"usuario seleccionar el tipo sesión/entorno de escritorio solicitado, " -"seleccionar un idioma/configuración regional apropiada y opcionalmente " -"apagar/reiniciar/suspender el equipo, configurar GDM (siempre que el usuario " -"conozca la contraseña de administrador), cambiar el tema GTK+ o iniciar un " -"selector XDMCP." - -#: C/gdm.xml:509(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 " -"<filename>Logo</filename> option in the reference section below for details." -msgstr "" -"El interfaz de entrada puede mostrar opcionalmente un logotipo en la ventana " -"de entrada. La imagen debe estar en un formato legible por la biblioteca gdk-" -"pixbuf (GIF, JPG, PNG, TIFF, XPM y posiblemente otros), y debe tener permiso " -"de lectura para el usuario de GDM. Vea la opción <filename>Logo</filename> " -"en la sección de referencia inferior para los detalles." - -#: C/gdm.xml:519(title) -msgid "The Themed Greeter" -msgstr "El interfaz con temas" - -#: C/gdm.xml:521(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 <filename>GraphicalTheme</" -"filename> 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 "" -"El interfaz con temas es un interfaz que ocupa la pantalla completa y es muy " -"\"temable\". Los temas pueden seleccionarse e instalarse por medio de la " -"aplicación de configuración o estableciendo la clave de configuración " -"<filename>GraphicalTheme</filename>. El interfaz con temas se parece al " -"interfaz GTK+ en que está controlado por un demonio por debajo, no tiene " -"estados, y el demonio lo controla usando el mismo protocolo sencillo." - -#: C/gdm.xml:531(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 "" -"La apariencia de este interfaz está controlada realmente por el tema y así " -"los elementos del interfaz de usuario que están presentes pueden ser " -"diferentes. La única cosa que debe estar presente siempre es el campo de " -"entrada de texto tal como se describe arriba en el interfaz GTK+. El tema " -"puede incluir botones que permitan al usuario seleccionar la configuración " -"regional o idioma adecuado, detener/reiniciar/suspender el equipo, " -"configurar GDM (siempre que el usuario conozca la contraseña de root), o " -"iniciar un selector XDMCP." - -#: C/gdm.xml:541(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 "" -"Puede obtener siempre un menú de las acciones disponibles pulsando la tecla " -"F10. Esto puede ser útil si el tema no proporciona ciertos botones cuando " -"realmente quiere hacer alguna acción permitida por la configuración de GDM." - -#: C/gdm.xml:549(title) -msgid "The GDM Face Browser" -msgstr "El visor de rostros de GDM" - -#: C/gdm.xml:551(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 " -"<filename>Browser</filename> 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 "" -"GDM soporta un visor de rostros que mostrará una lista de usuarios que " -"pueden entrar y un icono para cada usuario. Disponible desde la versión " -"2.18.1, la opción de configuración <filename>Examinador</filename> debe " -"estar establecida a «true» para que pueda usarse. En versiones anteriores " -"sólo se requería al usar el tema GTK+ Greeter. Al usar el tema Greeter, el " -"visor de rostros sólo está disponible si el tema de GDM incluye un elemento " -"de tipo \"userlist\"." - -#: C/gdm.xml:561(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 <command>gdmsetup</command>. This feature is " -"most practical to use on a system with a smaller number of users." -msgstr "" -"Por omisión, el visor de rostros está desactivado debido a que revelar " -"nombres de usuario en la pantalla de entrada no es apropiado en muchos " -"sistemas por razones de seguridad. Además GDM requiere alguna configuración " -"para especificar qué usuarios deberían ser visibles. La configuración puede " -"hacerse en la solapa «Usuarios» en <command>gdmsetup</command>. Esta " -"característica es más práctica de usar en un sistema con un número pequeño " -"de usuarios." - -#: C/gdm.xml:570(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 <filename><share>/pixmaps/faces/</filename> directory (though " -"this can be configured with the <filename>GlobalFaceDir</filename> " -"configuration option) and the filename should be the name of the user, " -"optionally with a <filename>.png</filename> 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 "" -"Los iconos usados por GDM pueden instalarse globalmente por el administrador " -"del sistema o pueden colocarse en los directorios personales de los " -"usuarios. Si se instalan globalmente deberían estar en el directorio " -"<filename><share>/pixmaps/faces/</filename> (aunque esto puede " -"configurarse con la opción <filename>GlobalFaceDir</filename>) y el nombre " -"del archivo debería ser el nombre del usuario, opcionalmente con un " -"<filename>.png</filename> agregado. Los iconos de caras colocados en el " -"directorio global de caras deben ser legibles por el usuario de GDM. Sin " -"embargo, el demonio, proximiza las imágenes de los usuarios al interfaz y " -"debido a esto no tienen que ser legibles por el usuario «gdm» sino por el " -"root." - -#: C/gdm.xml:583(para) -msgid "" -"Users may run the <command>gdmphotosetup</command> command to configure the " -"image to use for their userid. This program properly scales the file down if " -"it is larger than the <filename>MaxIconWidth</filename> or " -"<filename>MaxIconHeight</filename> configuration options and places the icon " -"in a file called <filename>~/.face</filename>. Although " -"<command>gdmphotosetup</command> scales user images automatically, this does " -"not guarantee that user images are properly scaled since a user may create " -"their <filename>~/.face</filename> file by hand." -msgstr "" -"Los usuarios pueden ejecutar el comando <command>gdmphotosetup</command> " -"para configurar la imagen a usar para su id de usuario. Este programa escala " -"apropiadamente el archivo si es más grande que las opciones de " -"configuración <filename>MaxIconWidth</filename> o <filename>MaxIconHeight</" -"filename> y coloca al icono en un archivo llamado <filename>~/.face</" -"filename>. Aunque <command>gdmphotosetup</command> escala las imágenes del " -"usuario automáticamente, esto no garantiza que esas imágenes de usuario " -"estén escaladas de forma adecuada así que un usuario puede crear su archivo " -"<filename>~/.face</filename> a mano." - -#: C/gdm.xml:595(para) -msgid "" -"GDM will first look for the user's face image in <filename>~/.face</" -"filename>. If not found, it will try <filename>~/.face.icon</filename>. If " -"still not found, it will use the value defined for \"face/picture=\" in the " -"<filename>~/.gnome2/gdm</filename> file. Lastly, it will try <filename>~/." -"gnome2/photo</filename> and <filename>~/.gnome/photo</filename> which are " -"deprecated and supported for backwards compatibility." -msgstr "" -"GDM primero buscará la imagen de la cara del usuario en <filename>~/.face</" -"filename>. Si no la encuentra, intentará con <filename>~/.face.icon</" -"filename>. Si aún no la encuentra, usará el valor definido para \"face/" -"picture=\" en el archivo <filename>~/.gnome2/gdm</filename>. Por último " -"intentará con <filename>~/.gnome2/photo</filename> y <filename>~/.gnome/" -"photo</filename> los cuales están obsoletos y se soportan por compatibilidad " -"hacia atrás." - -#: C/gdm.xml:606(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 <filename>DefaultFace</filename> " -"configuration option, normally <filename><share>/pixmaps/nobody.png</" -"filename>." -msgstr "" -"Si un usuario no tiene una imagen de rostro definida, GDM usará el icono " -"\"stock_person\" definido en el tema GTK+ actual. Si dicha imagen no está " -"definida, entonces usará la imagen especificada en la opción de " -"configuración <filename>DefaultFace</filename> como resguardo, normalmente " -"<filename></share>/pixmaps/nobody.png</filename>." - -#: C/gdm.xml:614(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 <filename>Include</filename> 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 <filename>GlobalFaceDir</filename> configuration option." -msgstr "" -"Note que cargar y escalar los iconos de rostros situados en los directorios " -"personales de los usuarios puede ser una tarea que consuma mucho tiempo. " -"Debido a que no es práctico cargar imágenes sobre NIS o NFS, GDM no intenta " -"cargar imágenes de rostros desde directorios personales remotos. Además, GDM " -"parará de cargar imágenes de rostros después de 5 segundos de actividad y " -"sólo mostrará los usuarios cuyas imágenes haya obtenido hasta entonces. La " -"opción <filename>Include</filename> de <filename>gdm.conf</filename> puede " -"usarse para especificar un conjunto de usuarios que deberían aparecer en el " -"visor de rostros. Mientras los usuarios a incluir tengan un tamaño " -"razonable, no debería haber ningún problema con GDM siendo incapaz de " -"acceder a las imágenes de rostros. Para evitar estos problemas, se " -"recomienda situar las imágenes de rostros en el directorio especificado por " -"la opción de configuración <filename>GlobalFaceDir</filename>." - -#: C/gdm.xml:630(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 " -"<filename>IncludeAll</filename> option is set to true, then the password " -"file will be scanned and all users will be displayed. If " -"<filename>IncludeAll</filename> option is set to false, then the " -"<filename>Include</filename> option should contain a list of users separated " -"by commas. Only the users specified will be displayed. Any user listed in " -"the <filename>Exclude</filename> option and users whose UID's is lower than " -"<filename>MinimalUID</filename> will be filtered out regardless of the " -"<filename>IncludeAll</filename> setting. <filename>IncludeAll</filename> 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 "" -"Para controlar qué usuarios se muestran en el examinador de rostros, hay " -"varias opciones de configuración que pueden usarse. Si se establece a true " -"la opción <filename>IncludeAll</filename>, entonces se analizará el archivo " -"de contraseñas y se mostrarán todos los usuarios. Si la opción " -"<filename>IncludeAll</filename> se establece a falso, entonces la opción " -"<filename>Include</filename> debería contener una lista de usuarios separada " -"por comas. Sólo se mostrarán los usuarios especificados. Cualquier usuario " -"listado en la opción <filename>Exclude</filename> y los usuarios cuyo UID " -"sea inferior a <filename>MinimalUID</filename> se filtrarán con " -"independencia de lo que esté establecido en <filename>IncludeAll</filename>. " -"<filename>IncludeAll</filename> no está recomendado para sistemas donde las " -"contraseñas se carguen por medio de una red (como cuando se usa NIS), debido " -"a que puede ser muy lento cargar más de un pequeño número de usuarios sobre " -"la red." - -#: C/gdm.xml:647(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 "" -"Cuando el examinador está activado, los nombres de usuario válidos en el " -"equipo están expuestos inherentemente a un intruso potencial. Esto puede ser " -"una mala idea si no sabe quién puede acceder a una pantalla de entrada. Esto " -"es especialmente cierto si ejecuta XDMCP (desactivado por omisión)." - -#: C/gdm.xml:656(title) -msgid "Logging" -msgstr "Registro de actividad" - -#: C/gdm.xml:658(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 "" -"GDM por sí mismo usará syslog para registrar los errores o el estado. " -"También puede registrar información de depuración, que puede ser útil para " -"encontrar problemas si GDM no funciona apropiadamente. Esto puede activarse " -"en el archivo de configuración." - -#: C/gdm.xml:665(para) -msgid "" -"Output from the various X servers is stored in the GDM log directory, which " -"is configurable, but is usually <filename><var>/log/gdm/</filename>. " -"The output from the session can be found in a file called <filename><" -"display>.log</filename>. Four older files are also stored with " -"<filename>.1</filename> through <filename>.4</filename> 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 "" -"La salida de varios servidores X está almacenada en el directorio de " -"registros de GDM, el cual es configurable, pero normalmente es <filename>/" -"var/log/gdm/</filename>. La salida desde la sesión puede encontrarse en un " -"archivo llamado <filename><display>.log</filename>. Cuatro archivos " -"más antiguos se almacenan también con <filename>.1</filename> a " -"<filename>.4</filename> anexado. Éstos se rotarán a medida que se inicien " -"nuevas sesiones en esa pantalla. Puede usar estos registros para ver que " -"decía el servidor X cuando arrancaba." - -#: C/gdm.xml:677(para) -msgid "" -"The output from the user session is redirected to <filename>~/.xsession-" -"errors</filename> before even the <filename>PreSession</filename> 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 "" -"La salida de la sesión de usuario está redirigida a <filename>~/.xsession-" -"errors</filename> incluso antes de se inicie el script <filename>PreSession</" -"filename>. Así que no es realmente necesario redirigir esto otra vez en el " -"script de configuración de la sesión. Tal como se hace normalmente, si la " -"sesión del usuario duró menos de 10 segundos, GDM asume que la sesión " -"reventó y permite al usuario ver este archivo en un diálogo antes de volver " -"a la pantalla de entrada. De esta manera el usuario puede ver los errores de " -"la última sesión y corregir el problema." - -#: C/gdm.xml:689(para) -msgid "" -"You can suppress the 10 second warning by returning code 66 from the " -"<filename>Xsession</filename>script or from your session binary (the default " -"<filename>Xsession</filename> 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 "" -"Puede suprimir la advertencia de los 10 segundos devolviendo un código 66 " -"desde el script <filename>Xsession</filename> desde el binario de la sesión " -"(el script <filename>Xsession</filename> predeterminado propaga esos códigos " -"hacia atrás). Esto es útil si tiene alguna clase de inicios de sesión " -"especiales para los que no es un error retornar menos de esos 10 segundos " -"después, o si configura la sesión para mostrar algún mensaje de error y el " -"mensaje de GDM podría ser confuso y redundante." - -#: C/gdm.xml:699(para) -msgid "" -"The session output is piped through the GDM daemon and so the <filename>~/." -"xsession-errors</filename> 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 "" -"La salida de la sesión se encauza a través del demonio GDM y así el archivo " -"<filename>~/.xsession-errors</filename> está capado a cerca de 200 Kbytes " -"por GDM para prevenir una posible denegación de servicio en la sesión. Una " -"aplicación podría quizás leer algunos datos erróneos, imprimir advertencias " -"o errores en stderr o stdout. Esto podría quizás llenar el directorio " -"personal del usuario quien tendría que cerrar sesión e iniciar sesión de " -"nuevo para limpiar esto. Esto podría ser especialmente desagradable si hay " -"cuotas habilitadas. GDM además atrapa correctamente la señal XFSZ y para de " -"escribir el archivo, lo que podría conducir a sesiones matadas si el archivo " -"fue redirigido en la forma antigua desde el script." - -#: C/gdm.xml:712(para) -msgid "" -"Note that some distributors seem to override the <filename>~/.xsession-" -"errors</filename> redirection and do it themselves in their own Xsession " -"script (set by the <filename>BaseXsession</filename> configuration key) " -"which means that GDM will not be able to trap the output and cap this file. " -"You also lose output from the <filename>PreSession</filename> 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 " -"<filename>BaseXsession</filename> configuration key for more information, " -"especially on how to handle multiple display managers using the same script." -msgstr "" -"Note que algunos distribuidores parecen ignorar la redirección de " -"<filename>~/.xsession-errors</filename> y la hacen ellos mismos en su propio " -"script Xsession (establecido por la clave de configuración " -"<filename>BaseXsession</filename>) que significa que GDM no será capaz de " -"atrapar la salida y cubrir este archivo. Puede también perder datos de " -"salida del script <filename>PreSession</filename> lo que puede hacer la " -"depuración mucho más complicada ya que quizás la salida de lo que está " -"equivocado no se imprimirá. Vea la descripción de la clave de configuración " -"<filename>BaseXsession</filename> para más información, especialmente acerca " -"de cómo manejar múltiples gestores de entrada usando el mismo script." - -#: C/gdm.xml:726(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 <filename>/" -"tmp</filename> directory named <filename>/tmp/xses-<user>.XXXXXX</" -"filename> where the <filename>XXXXXX</filename> are some random characters." -msgstr "" -"Note que si la sesión es una sesión a prueba de fallos, o si GDM no puede " -"abrir este archivo por alguna razón, entonces se creará un archivo de apoyo " -"en el directorio <filename>/tmp</filename> llamado <filename>/tmp/xses-<" -"user>.XXXXXX</filename> donde <filename>XXXXXX</filename> son caracteres " -"aleatorios." - -#: C/gdm.xml:734(para) -msgid "" -"If you run a system with quotas set, it would be good to delete the " -"<filename>~/.xsession-errors</filename> in the <filename>PostSession</" -"filename> script. Such that this log file doesn't unnecessarily stay around." -msgstr "" -"Si ejecuta un sistema sin cuotas activadas, será bueno borrar el archivo " -"<filename>~/.xsession-errors</filename> en el script <filename>PostSession</" -"filename>. Así este archivo de registro no está por medio innecesariamente." - -#: C/gdm.xml:743(title) -msgid "Accessing Files" -msgstr "Acceder a archivos" - -#: C/gdm.xml:745(para) -msgid "" -"In general GDM is very reluctant regarding reading/writing of user files " -"(such as the <filename>~/.dmrc</filename>, <filename>~/.face</filename>, " -"<filename>~/.xsession-errors</filename>, and <filename>~/.Xauthority</" -"filename> files). For instance it refuses to access anything but regular " -"files. Links, sockets and devices are ignored. The value of the " -"<filename>RelaxPermissions</filename> parameter determines whether GDM " -"should accept files writable by the user's group or others. These are " -"ignored by default." -msgstr "" -"En general GDM es muy reluctante respecto a leer/escribir archivos del " -"usuario (como <filename>~/.dmrc</filename>, <filename>~/.face</filename>, " -"<filename>~/.xsession-errors</filename>, y <filename>~/.Xauthority</" -"filename>). Por ejemplo, se niega a acceder a cualquier cosa que no sean " -"archivos regulares. Los enlaces, sockets y dispositivos se ignoran. El valor " -"del parámetro <filename>RelaxPermissions</filename> determina si GDM debe " -"aceptar archivos escribibles por el grupo del usuario u otros. Éstos se " -"ignoran por omisión." - -#: C/gdm.xml:757(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 <filename>.Xauthority</" -"filename> file, a fallback cookie is created in the directory specified by " -"the <filename>UserAuthFBDir</filename> configuration setting (<filename>/" -"tmp</filename> by default)." -msgstr "" -"Todas las operaciones en los archivos de usuario se realizan con el id " -"efectivo del usuario. Si el control de sanidad falla en el archivo " -"<filename>.Xauthority</filename> del usuario, se crea una cookie de " -"resguardo en el directorio especificado por la opción de configuración " -"<filename>UserAuthFBDir</filename> (<filename>/tmp</filename> por omisión)." - -#: C/gdm.xml:765(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 "" -"Finalmente, el administrador del sistema puede especificar el tamaño máximo " -"del archivo que GDM debería aceptar y, en el caso de que el visor de rostros " -"esté activado, se fuerza un tamaño máximo del icono. En sistemas grandes se " -"avisa además que desactive el visor de rostros por razones de rendimiento. " -"Mirar iconos en directorios personales, escalarlos y renderizarlos puede " -"llevar mucho tiempo." - -#: C/gdm.xml:776(title) -msgid "GDM Performance" -msgstr "Rendimiento de GDM" - -#: C/gdm.xml:778(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 "" -"Para acelerar el rendimiento es posible construir GDM para que precargue las " -"bibliotecas cuando el GDM muestre un programa de entrada por primera vez. " -"Esto se ha mostrado para acelerar el primer inicio de sesión debido a que " -"estas bibliotecas pueden cargarse en memoria mientras el usuario teclea su " -"nombre y contraseña." - -#: C/gdm.xml:786(para) -msgid "" -"To use this feature, configure GDM with the <command>--with-prefetch</" -"command> option. This will cause GDM to install the <command>gdmprefetch</" -"command> program to the <filename>libexecdir</filename> directory, install " -"the <filename>gdmprefetchlist</filename> to the <filename><etc>/gdm</" -"filename> directory, and set the <filename>PreFetchProgram</filename> " -"configuration variable so that the <command>gdmprefetch</command> program is " -"called with the default <filename>gdmprefetchlist</filename> file. The " -"default <filename>gdmprefetchlist</filename> 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 " -"<ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</" -"ulink>, so that they can be included in future GDM releases." -msgstr "" -"Para usar esta característica, configure GDM con la opción <command>--with-" -"prefetch</command>. Esto causará que GDM instale el programa " -"<command>gdmprefetch</command> en el directorio <filename>libexecdir</" -"filename>, instale el <filename>gdmprefetchlist</filename> en el directorio " -"<filename><etc>/gdm</filename>, y establezca la variable de " -"configuración <filename>PreFetchProgram</filename> para que se llame al " -"programa <command>gdmprefetch</command> con el archivo predeterminado " -"<filename>gdmprefetchlist</filename>. El archivo predeterminado " -"<filename>gdmprefetchlist</filename> se optimizó para un escritorio GNOME " -"ejecutándose en Solaris, así que quizá necesite algo de ajuste fino en otros " -"sistemas. Pueden contribuirse archivos alternativos de prefetchlist en la " -"categoría «gdm» en <ulink type=\"http\" url=\"http://bugzilla.gnome.org/" -"\">bugzilla.gnome.org</ulink>, para que puedan ser incluidos en lanzamientos " -"futuros de GDM." - -#: C/gdm.xml:807(title) -msgid "Security" -msgstr "Seguridad" - -#: C/gdm.xml:810(title) -msgid "PAM" -msgstr "PAM" - -#: C/gdm.xml:814(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 "" -"GDM usa PAM para autenticación del usuario, aunque si su máquina no soporta " -"PAM puede compilar GDM para que funcione con la base de datos de contraseñas " -"y la biblioteca de funciones crypt." - -#: C/gdm.xml:820(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 "" -"PAM significa Pluggable Authentication Module, y se usa por la mayoría de " -"los programas que piden autenticación en su equipo. Permite al usuario " -"configurar diferentes comportamientos de autenticación para distintos " -"programas." - -#: C/gdm.xml:827(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 "" -"Algunas características de GDM (como activar la entrada automática) quizá " -"requieran que actualice su configuración PAM. PAM tiene interfaces " -"distintos, pero similares, en diferentes sistemas operativos, así que " -"compruebe su página man de pam.d o pam.conf para los detalles acerca de cómo " -"configurarlo. Asegúrese de leer la documentación de PAM (eg: página man de " -"pam.d/pam.conf) y tenga cuidado con las implicaciones de seguridad de " -"cualquier cambio que intente hacer a su configuración." - -#: C/gdm.xml:837(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 "" -"Si no hay ninguna entrada para GDM en su archivo de configuración de PAM, " -"entonces las características como la entrada automática quizá no funcionen. " -"No tener una entrada hará que GDM use el comportamiento predeterminado, se " -"recomiendan configuraciones conservadoras y probablemente sean los que se " -"entreguen con su distribución." - -#: C/gdm.xml:844(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 <address><email>gdm-list@gnome.org</email></" -"address> mail list, so you can refer to the list archives for more " -"information." -msgstr "" -"Si desea que GDM funciona con otros tipos de mecanismos de autenticación " -"(como una SmartCard), entonces debe implementar esto escribiendo un módulo " -"PAM en vez de intentando modificar el código de GDM directamente. Refiérase " -"a la documentación de PAM de su sistema. Esta cuestión se ha discutido en la " -"lista de correo <address><email>gdm-list@gnome.org</email></address>, así " -"que puede referirse a los archivadores de la lista para más información." - -#: C/gdm.xml:854(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 " -"<filename>PamStack</filename> 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:869(title) -msgid "utmp/wtmp" -msgstr "utmp/wtmp" - -#: C/gdm.xml:873(para) -msgid "" -"GDM generates utmp and wtmp User Accounting Database entries upon session " -"login and logout. The utmp database contains user access and accounting " -"information that is accessed by commands such as <command>finger</command>, " -"<command>last</command>, <command>login</command>, and <command>who</" -"command>. The wtmp database contains the history of user access and " -"accounting information for the utmp database." -msgstr "" - -#: C/gdm.xml:883(para) -msgid "" -"GDM 2.18 and earlier would run the X server <command>sessreg</command> " -"program from the default GDM <command>PreSession</command> and " -"<command>PostSession</command> scripts. Starting with GDM 2.20, GDM " -"interacts with the UTMP and WTMP databases directly and supports the " -"following configuration options." -msgstr "" -"Las versiones de GDM 2.18 y anteriores ejecutaban el programa " -"<command>sessreg</command> del servidor X desde los scripts predeterminados " -"<command>PreSession</command> y <command>PostSession</command>. Desde la " -"versión 2.20 de GDM, éste interactúa con las bases de datos UTMP y WTMP " -"directamente y soporta las siguientes opciones de configuración." - -#: C/gdm.xml:891(para) -msgid "" -"When doing utmp processing, GDM supports configurability on how the ut_line " -"value is set. Programs that access the database assume that this value is an " -"actual device, so GDM will set the device as follows. If the display is " -"attached and has an associated Virtual Terminal (VT) device, then this " -"device will be used. Otherwise, if an attached display in the <command>" -"[servers]</command> specifies a device name, then this value will be used. " -"Otherwise attached displays will default to the <filename>UtmpLineAttached</" -"filename> value in the GDM configuration. Remote displays will default to " -"the <filename>UtmpLineRemote</filename> value in the GDM configuration. " -"Device values must begin with \"/dev/\"." -msgstr "" - -#: C/gdm.xml:905(para) -msgid "" -"GDM also supports the <filename>UtmpPseudoDevice</filename> configuration " -"option. If this configuration setting is true, then GDM will ensure that the " -"specified device exists and will create a pseudo device if the device does " -"not exist. A pseudo device is a symlink to <filename>/dev/null</filename>. " -"If <filename>UtmpPseudoDevice</filename> is true, and the device does " -"already exist, GDM checks to see if the device is a symlink to <filename>/" -"dev/null</filename>. If so, then GDM will update the access time of the " -"symlink. This ensures that programs that check the access time of the device " -"will get a reasonable value for the last time the device was accessed. If " -"the <filename>UtmpPseudoDevice</filename> configuration option is false, " -"then GDM will only set the ut_line value as specified regardless of whether " -"the device exists or not." -msgstr "" - -#: C/gdm.xml:923(title) -msgid "The GDM User" -msgstr "El usuario GDM" - -#: C/gdm.xml:925(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 "" -"Por razones de seguridad se requieren un usuario y grupo dedicado para un " -"funcionamiento correcto. La necesidad de ser capaz de escribir archivos " -"Xauth es el porqué el usuario «nobody» no es apropiado para gdm." - -#: C/gdm.xml:931(para) -msgid "" -"The GDM daemon normally runs as root, as does the slave. However GDM should " -"also have a dedicated user id and a group id which it uses for its graphical " -"interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</" -"command>. These are configured via the <filename>User</filename> and " -"<filename>Group</filename> configuration options in the GDM configuration " -"files. The user and group should be created before running \"make install\". " -"By default GDM assumes the user and the group are called \"gdm\"." -msgstr "" -"El demonio GDM normalmente se ejecuta como root, y hace de esclavo. Sin " -"embargo GDM debería también tener un id de usuario y un id de grupo dedicado " -"que se usa para sus interfaces gráficas <command>gdmgreeter</command> y " -"<command>gdmlogin</command>. Éstos se configuran por medio de las opciones " -"de configuración <filename>User</filename> y <filename>Group</filename> en " -"los archivos de configuración de GDM. El usuario y grupo debería ser creado " -"antes de ejecutar «make install». Por omisión GDM asume que el usuario y el " -"grupo se llaman «gdm»." - -#: C/gdm.xml:942(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 "" -"Este id de usuario se usa para ejecutar los programas de la IGU de GDM " -"requeridos para la entrada. Toda la funcionalidad que requiere la " -"autorización de root la realiza el proceso del demonio GDM. Este diseño " -"asegura que si los programas de la IGU son comprometidos, sólo los " -"privilegios del usuario dedicado están disponibles." - -#: C/gdm.xml:949(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 " -"<filename><var>/lib/gdm</filename>. 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 "" -"Debería notarse sin embargo que el usuario y el grupo de GDM tienen algunos " -"privilegios que los hacen de alguna manera peligrosos. Por una parte tienen " -"acceso al directorio de autorización del servidor X. Debe ser capaz de leer " -"y escribir claves Xauth en <filename><var>/lib/gdm</filename>. Este " -"directorio debería tener como propietario root:gdm y permisos 1770. Ejecutar " -"«make install» establecerá este directorio a estos valores. El proceso del " -"demonio de GDM restablecerá este directorio a los permisos/propietario " -"adecuados si por cualquier circunstancia, no estuvieran establecidos de " -"forma correcta." - -#: C/gdm.xml:960(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 " -"<filename>nobody</filename>. 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 "" -"El peligro es que alguien que gane privilegios del usuario/grupo GDM puede " -"entonces conectarse a cualquier sesión. Así que no debería bajo ninguna " -"circunstancia, hacer esto a algún usuario/grupo que pueda ser fácil obtener " -"acceso, como el usuario <filename>nobody</filename>. Los usuarios que ganan " -"acceso al usuario «gdm» podrían también modificar las claves Xauth y " -"provocar ataques de denegación de servicio. También si una persona gana la " -"capacidad de ejecutar programas como el usuario «gdm», podría ser posible " -"espiar los procesos GDM en ejecución, incluyendo usuarios y contraseñas a " -"medida que se teclean." - -#: C/gdm.xml:972(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 "" -"Se espera que las distribuciones y los administradores de sistemas que usen " -"GDM configuren el usuario dedicado de forma apropiada. Se recomienda que " -"este id de usuario se configure para no permitirle iniciar sesión y no tener " -"un intérprete de comandos predeterminado. Las distribuciones y los " -"administradores del sistema deberían configurar el sistema de archivos para " -"asegurarse de que el usuario GDM no tenga permiso de lectura o escritura a " -"los archivos sensibles." - -#: C/gdm.xml:983(title) -msgid "X Server Authentication Scheme" -msgstr "Esquema de autenticación del servidor X" - -#: C/gdm.xml:985(para) -msgid "" -"The X server authorization directory (the <filename>ServAuthDir</filename>) " -"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 <filename>root.gdm</filename> 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 "" -"El directorio de autorización del servidor (el <filename>ServAuthDir</" -"filename>) se usa para albergar un conjunto de datos aleatorios internos " -"además de los archivos de autorización del servidor X, y el nombre es " -"realmente una reliquia de la historia. El demonio GDM fuerza que este " -"directorio tenga el propietario <filename>root.gdm</filename> con los " -"permisos 1770. De esta manera sólo root y el grupo de GDM tienen acceso de " -"escritura a este directorio, pero el grupo GDM no puede eliminar los " -"archivos que sean propiedad de root de este directorio, tales como los " -"archivos de autorización del servidor X." - -#: C/gdm.xml:997(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 "" -"GDM por omisión no confía en el directorio de autorización del servidor y lo " -"trata de la misma manera que el directorio temporal respecto a crear " -"archivos. De esta manera, alguien que rompa al usuario de GDM no puede " -"montar ataques creando enlaces en este directorio. Similarmente el " -"directorio de registros del servidor X se trata de forma segura, pero ese " -"directorio debería ser propiedad y escribible sólo por el usuario root." - -#: C/gdm.xml:1006(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 "" -"GDM sólo soporta el sistema de autenticación MIT-MAGIC-COOKIE-1. Normalmente " -"se gana poco de otros esquemas, no se ha hecho ningún esfuerzo en " -"implementarlos hasta ahora. Sea especialmente cuidadoso acerca de usar XDMCP " -"porque las cookies de autenticación van sobre el cable como texto en claro." -"Obviamente si el espionaje es posible, entonces el atacante podría tan sólo " -"espiar su contraseña de autenticación mientras usted inicia una sesion, con " -"independencia del esquema de autenticación que se esté usando. Si el " -"espionaje es posible y poco deseable, entonces tendrá que crear un túnel a " -"través de ssh para la conexión X en vez de usar XDMCP. Podría pensar en " -"XDMCP como una clase de telnet gráfico que tiene los mismos problemas de " -"seguridad." - -#: C/gdm.xml:1019(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 <filename>/dev/audio</" -"filename> or <filename>/dev/mem</filename> 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 <filename>UserAuthDir</" -"filename> configuration key). So be careful about where you use remote X " -"display." -msgstr "" -"En el lado superior, la generación de números aleatorios de GDM es muy " -"conservadora y GDM toma medidas extraordinarias para obtener un verdadero " -"número aleatorio de 128 bits, usando generadores de números aleatorios por " -"hardware si es posible, además de la hora actual (con precisión de " -"microsegundos), un array de 20 bytes de números pseudoaleatorios, pids de " -"procesos, además de otra información aleatoria (posiblemente usando " -"<filename>/dev/audio</filename> o <filename>/dev/mem</filename> si los " -"generadores aleatorios hardware no están disponibles) para crear un búfer " -"grande y después ejecutar un digest MD5 en él. Obviamente, todo este trabajo " -"se desperdicia si envía la cookie a través de una red abierta o la almacena " -"en un directorio NFS (vea la clave de configuración de " -"<filename>UserAuthDir</filename>). Así que sea cuidadoso acerca de dónde usa " -"su display X remoto." - -#: C/gdm.xml:1036(title) -msgid "Firewall Security" -msgstr "Seguridad con cortafuegos" - -#: C/gdm.xml:1038(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 "" -"Incluso aunque GDM intenta diferenciar inteligentemente a los atacantes " -"potenciales, se recomienda que bloquee el puerto XDMCP (normalmente el " -"puerto UDP 177) en su cortafuegos a no ser que realmente lo necesite. GDM se " -"protege contra ataques DoS, (Denial of Service) pero el protocolo X aún es " -"inherentemente inseguro y sólo debería usarse en entornos controlados. " -"Además cada conexión remota toma muchos recursos, así que es más fácil hacer " -"un DoS a un servidor XDMCP que a un servidor web." - -#: C/gdm.xml:1048(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 "" -"También es sabio bloquear todos los puertos del servidor X (puertos TCP 6000 " -"+ número de pantalla) en el cortafuegos. Note que GDM usará los números de " -"pantalla 20 y superiores para los servidores flexibles bajo demanda." - -#: C/gdm.xml:1055(para) -msgid "" -"X is not a very safe protocol for leaving on the net, and XDMCP is even less " -"safe." -msgstr "" -"X no es un protocolo muy seguro para dejarlo en la red, y XDMCP es incluso " -"menos seguro." - -#: C/gdm.xml:1062(title) -msgid "GDM Security With NFS" -msgstr "Seguridad de GDM con NFS" - -#: C/gdm.xml:1064(para) -msgid "" -"Note that NFS traffic really goes \"over the wire\" and thus can be snooped. " -"When accessing the user's X authorization file (<filename>~/.Xauthority</" -"filename>), 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 " -"<filename>UserAuthFBDir</filename>, which by default is set to <filename>/" -"tmp</filename>. This behavior can be changed by setting the " -"<filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</" -"filename> section to false." -msgstr "" -"Note que el tráfico NFS realmente va \"sobre el cable\" y puede verse. " -"Cuando se acceda al archivo de autorización X del usuario (<filename>~/." -"Xauthority</filename>), GDM intentará abrir el archivo para leerlo como " -"root. Si falla, GDM concluirá que se ha montado por NFS y usará " -"automáticamente <filename>UserAuthFBDir</filename>, que usualmente está en " -"<filename>/tmp</filename>. Este comportamiento puede cambiarse poniendo a " -"«false» <filename>NeverPlaceCookiesOnNFS</filename> en la sección <filename>" -"[security]</filename>." - -#: C/gdm.xml:1078(title) -msgid "XDMCP Security" -msgstr "Seguridad XDMCP" - -#: C/gdm.xml:1080(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 "" -"Incluso aunque su pantalla esté protegida por cookies, XEvents y las " -"pulsaciones de teclas que se introducen al escribir las contraseñas aún irán " -"sobre el cable en texto claro. Es trivial capturarlas." - -#: C/gdm.xml:1086(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 "" -"XDMCP es útil principalmente para ejecutar clientes ligeros como en " -"terminales de laboratorio. Dichos clientes ligeros sólo necesitarán la red " -"alguna vez para acceder al servidor, y así parece que la mejor política para " -"la seguridad es tener a esos clientes ligeros en una red separada que no " -"pueda accederse desde el mundo exterior, y sólo pueda conectarse al " -"servidor. El único punto desde el que necesita acceder desde fuera es el " -"servidor." - -#: C/gdm.xml:1095(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 "" -"Las secciones de arriba «Esquema de autenticación del servidor X» y " -"«Seguridad con cortafuegos» también contienen información importante acerca " -"de usuario XDMCP de forma segura. La siguiente sección también discute cómo " -"configurar el control de acceso de XDMCP." - -#: C/gdm.xml:1102(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 "" -"Para solucionar la seguridad inherente de XDMCP, gdm propone una sesión " -"predeterminada integrada que usa ssh para encriptar la conexión remota. Vea " -"la sección «Securizar una conexión remota con ssh» arriba." - -#: C/gdm.xml:1110(title) -msgid "XDMCP Access Control" -msgstr "Control de acceso XDMCP" - -#: C/gdm.xml:1112(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 "" -"El control de acceso XDMCP se realiza usando TCP wrappers. Es posible " -"compilar GDM sin TCP wrappers sin embargo, así que debería comprobar su " -"configuración y verificar que funciona." - -#: C/gdm.xml:1118(para) -msgid "" -"You should use the daemon name <command>gdm</command> in the <filename><" -"etc>/hosts.allow</filename> and <filename><etc>/hosts.deny</" -"filename> files. For example to deny computers from <filename>.evil.domain</" -"filename> from logging in, then add" -msgstr "" -"Debería usar el nombre del demonio <command>gdm</command> en el archivo " -"<filename><etc>/hosts.allow</filename> y en el archivo <filename><" -"etc>hosts.deny</filename>. Por ejemplo para denegar la entrada a equipos " -"de <filename>.evil.domain</filename> , añada" - -#: C/gdm.xml:1125(screen) -#, no-wrap -msgid "" -"\n" -"gdm: .evil.domain\n" -msgstr "" -"\n" -"gdm: .dominio.maligno\n" - -#: C/gdm.xml:1128(para) -msgid "to <filename><etc>/hosts.deny</filename>. You may also need to add" -msgstr "a <filename><etc>/hosts.deny</filename>. También necesitará añadir " - -#: C/gdm.xml:1132(screen) -#, no-wrap -msgid "" -"\n" -"gdm: .your.domain\n" -msgstr "" -"\n" -"gdm: .su.dominio\n" - -#: C/gdm.xml:1135(para) -msgid "" -"to your <filename><etc>/hosts.allow</filename> if you normally " -"disallow all services from all hosts. See the <ulink type=\"help\" url=\"man:" -"hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" -"a su <filename><etc>/hosts.allow</filename> si normalmente no permite " -"todos los servicios desde todos los equipos. Vea la página del manual <ulink " -"type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> para más " -"detalles." - -#: C/gdm.xml:1144(title) -msgid "RBAC (Role Based Access Control)" -msgstr "RBAC (Control de acceso basado en rol)" - -#: C/gdm.xml:1146(para) -msgid "" -"If GDM is compiled with RBAC support, then the " -"<filename>RBACSystemCommandKeys</filename> 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 " -"<command>gdmflexiserver</command> 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 <filename>User</filename> " -"configuration option) has permission via RBAC. Users will only be able to " -"use the <command>gdmflexiserver</command> commands if the user has " -"permission via RBAC." -msgstr "" - -#: C/gdm.xml:1164(title) -msgid "Support for ConsoleKit" -msgstr "Soporte para ConsoleKit" - -#: C/gdm.xml:1166(para) -msgid "" -"GDM includes support for publishing user login information with the user and " -"login session accounting framework known as ConsoleKit. ConsoleKit is able " -"to keep track of all the users currently logged in. In this respect, it can " -"be used as a replacement for the utmp or utmpx files that are available on " -"most Unix-like operating systems." -msgstr "" -"GDM incluye soporte para publicar la información de entrada del usuario con " -"el framework de contabilidad de usuarios y sesiones conocido como " -"COnsoleKit. ConsoleKit es capaz de hacer un seguimiento de todos los " -"usuarios actualmente reconocidos. En este respecto, puede usarse como un " -"reemplazo de los archivos utmp y utmpx que están disponibles en la mayoría " -"de los sistemas Unix." - -#: C/gdm.xml:1174(para) -msgid "" -"When GDM is about to create a new login process for a user it will call a " -"privileged method of ConsoleKit in order to open a new session for this " -"user. At this time GDM also provides ConsoleKit with information about this " -"user session such as: the user ID, the X11 Display name that will be " -"associated with the session, the host-name from which the session originates " -"(useful in the case of an XDMCP session), whether or not this session is " -"attached, etc. As the entity that initiates the user process, GDM is in a " -"unique position 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 "" -"Cuando GDM va a crear un proceso de entrada nuevo para un usuario llamará al " -"método privilegiado de ConsoleKit para abrir una sesión nueva para dicho " -"usuario. En este momento GDM también proporciona a ConsoleKit la información " -"acerca de esta sesión de usuario como: el ID de usuario, el nombre de la " -"pantalla X11 que se asociará con la sesión, el nombre de equipo desde el " -"cual se origina la sesión (útil en caso de una sesión XDMCP), si esta sesión " -"es o no es local, etc. Como la entidad que inicia el proceso de usuario, GDM " -"está en una posición única para conocer y confiar en proporcionar estos bits " -"de información acerca de la sesión de usuario. El uso de este método " -"privilegiado está restringido por el uso de una norma de seguridad del " -"sistema de bus de mensajes D-Bus." - -#: C/gdm.xml:1187(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 "" -"En caso donde un usuario con una sesión existente y que se haya autenticado " -"en GDM y pida continuar una sesión existente, GDM llama un proceso " -"privilegiado de ConsoleKit para desbloquear esa sesión. Los detalles exactos " -"de qué ocurre cuando la sesión recibe esta señal de desbloqueo están " -"indefinidos y son específicos de la sesión. Sin embargo la mayoría de las " -"sesiones desbloquearán un salvapantallas en respuesta." - -#: C/gdm.xml:1196(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 "" -"Cuando el usuario elige salir, o si GDM o la sesión terminan de forma " -"inesperada, la sesión de usuario se desregistra de ConsoleKit." - -#: C/gdm.xml:1201(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 "" -"Si no se desea el soporte para ConsoleKit se puede deshabilitar en tiempo de " -"compilación usando la opción \"--with-console-kit=no\" al ejecutar configure." - -#: C/gdm.xml:1210(title) -msgid "Using gdmsetup To Configure GDM" -msgstr "Uso de gdmsetup para configurar GDM" - -#: C/gdm.xml:1212(para) -msgid "" -"The <command>gdmsetup</command> 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 <command>gdmsetup</" -"command>. Editing the files by hand is explained in the \"Configuration\" " -"section of this document. Note that <command>gdmsetup</command> does not " -"support changing of all configuration variables, so it may be necessary to " -"edit the files by hand for some configurations." -msgstr "" -"La aplicación <command>gdmsetup</command> se puede usar para configurar GDM. " -"Si cree que ejecutar un IGU como root causa un riesgo de seguridad, entonces " -"quizá quiera editar siempre los archivos a mano y no usar <command>gdmsetup</" -"command>. Editar los archivos a mano se explica en la sección " -"«Configuración» de este documento. Note que <command>gdmsetup</command> no " -"soporta cambiar todas las variables de configuración, así que quizás sea " -"necesario editar los archivos a mano para algunas configuraciones." - -#: C/gdm.xml:1223(para) -msgid "" -"The <command>gdmsetup</command> 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 "" -"El programa <command>gdmsetup</command> tiene cinco solapas. Local, Remoto, " -"Accesibilidad, Seguridad y Usuarios, descritas abajo. Entre paréntesis está " -"la información acerca de qué clave de configuración de GDM está afectada por " -"cada selección de la IGU. Vea la sección «Configuración» de este manual y " -"los comentarios en el archivo de configuración predeterminada del sistema de " -"GDM para obtener detalles adicionales acerca de cada clave." - -#: C/gdm.xml:1233(title) -msgid "Local Tab" -msgstr "Solapa Local" - -#: C/gdm.xml:1235(para) -msgid "" -"The Local tab is used for controlling the appearance of GDM for attached " -"(also known as local or static) displays. Attached displays are non-XDMCP " -"remote connections, for example. 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 "" -"La solapa Local se usa para controlar la apariencia de GDM para las " -"pantallas locales (también conocidas como estáticas). Las pantallas locales " -"no son, por ejemplo, las conexiones remotas por XDMCP. Las opciones " -"disponibles en esta solapa dependen de lo que esté seleccionado en la caja " -"de combinación «Estilo». Esta caja de combinación se usa para determinar si " -"se usa la interfaz «Plano» o «Con tema». Las diferencias entre estos " -"programas de interfaz se explican en la sección «Vista general» de este " -"documento." - -#: C/gdm.xml:1246(para) -msgid "" -"If the \"Style\" choice is \"Plain\", then GDM will use the " -"<command>gdmlogin</command> program as the GUI (daemon/Greeter). When this " -"choice is selected, <command>gdmsetup</command> 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 "" -"Si la selección de «Estilo» es «Plano», entonces GDM usará el programa " -"<command>gdmlogin</command> como la IGU (daemon/Greeter). Cuando esta opción " -"está seleccionada, <command>gdmsetup</command> permite al usuario " -"seleccionar si el fondo es una imagen o color sólido (greeter/" -"BackGroundType). Si está seleccionado imagen, hay un botón de selección de " -"archivos para escoger el archivo de imagen (greeter/BackgroundImage) y una " -"casilla para escalar la imagen para que quepa en la pantalla (greeter/" -"BackgroundImageScaleToFit). Si se selecciona color sólido, hay un botón " -"disponible para permitir la selección del color (greeter/BackgroundColor). " -"Además, el usuario puede seleccionar la imagen del logo que aparece en " -"gdmlogin (greeter/Logo)." - -#: C/gdm.xml:1260(para) -msgid "" -"If the \"Style\" choice is \"Plain with face browser\", then the " -"<command>gdmlogin</command> 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 "" -"Si la elección de «Estilo» es «Plano con visor de rostros», entonces el " -"programa <command>gdmlogin</command> se usa como la IGU (daemon/Greeter) y " -"el visor de rostros se activa (greeter/Browser). El visor de rostros se " -"explica en la sección «Vista general». De todas formas, las elecciones son " -"las mismas que cuando la elección de «Estilo» es «Plana». Puede ser " -"necesaria la configuración adicional en la solapa Usuarios para elegir qué " -"usuarios aparecen en el Visor de rostros." - -#: C/gdm.xml:1270(para) -msgid "" -"If the \"Style\" choice is \"Themed\", then the <command>gdmgreeter</" -"command> program is used as the GUI (daemon/Greeter). When this choice is " -"selected, <command>gdmsetup</command> 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 "" -"Si la opción de «Estilo» es «Con temas», entonces se usa el programa " -"<command>gdmgreeter</command> como la IGU (daemon/Greeter). Cuando ésta " -"opción está seleccionada, <command>gdmsetup</command> permite al usuario " -"seleccionar el tema para que se use (greeter/GraphicalTheme). Note que la " -"casilla en la izquierda del nombre del tema debe marcarse para que ese tema " -"se pueda seleccionar. Se muestra información acerca del autor del tema y el " -"copyright para el tema seleccionado. Se puede usar el botón «Quitar» para " -"borrar el tema seleccionado. Se puede usar el botón «Añador» para añadir " -"nuevos temas al sistema. Para añadir un nuevo tema debe estar comprimido en " -"formato tar. El «Color de fondo» mostrado cuando se inicia GDM (y si el " -"tema tiene elementos transparentes) también se puede seleccionar (greeter/" -"GraphicalThemedColor). La caja combo «Tema» se puede establecer a «Aleatorio " -"de los seleccionados» para usar un tema aleatorio para cada entrada (greeter/" -"GraphicalThemeRand y greeter/GraphicalThemes). Para usar temas aleatorios, " -"seleccione cada tema que quiera usar. De forma predeterminada esta caja de " -"combinación está establecida a «Sólo seleccionados», para que sólo un único " -"tema pueda seleccionarse y ser usado." - -#: C/gdm.xml:1292(para) -msgid "" -"If the \"Style\" choice is \"Themed with face browser\", then the " -"<command>gdmgreeter</command> 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 "" -"Si la elección de «Estilo» es «Plano con visor de rostros», entonces el " -"programa <command>gdmlogin</command> se usa como la IGU (daemon/Greeter) y " -"el visor de rostros se activa (greeter/Browser) si está soportado por el " -"tema. El visor de rostros se explica en la sección Vista general. De otra " -"forma, las elecciones son las mismas que cuando la elección de «Estilo» es " -"«Con tema». Puede ser necesaria la configuración adicional en la solapa " -"Usuarios para elegir qué usuarios aparecen en el Visor de rostros." - -#: C/gdm.xml:1303(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 <command>gdmsetup</command> (greeter/" -"ConfigAvailable), and whether the Action menu includes the choice to start " -"<command>gdmchooser</command> to run a remote XDMCP login session (greeter/" -"ChooserButton). The welcome message for attached DISPLAYS may be specified " -"(greeter/DefaultWelcome and greeter/Welcome). The welcome message may " -"contain the character sequences described in the \"Text Node\" subsection of " -"the \"Themed Greeter\" section of this manual. These character sequences " -"allow the welcome message to contain things like the display or host name." -msgstr "" -"Independientemente de la elección de «Estilo», el usuario podría seleccionar " -"si el menú de acciones es visible (greeter/SystemMenu), o si el menú " -"Acciones incluye la elección para iniciar <command>gdmsetup</command> " -"(greeter/ConfigAvailable), y si el menú de Acciones incluye la opción para " -"hacer que <command>gdmchooser</command> ejecute una sesión de entrada remota " -"XDMCP (greeter/ChooseButton). El mensaje de bienvenida mostrado para las " -"sesiones locales se puede seleccionar (greeter/DefaultWelcome y greeter/" -"Welcome). El mensaje de Bienvenida puede contener las secuencias de " -"caracteres descritas en la subsección «Nodos de texto» de la sección de " -"«Interfaz de temas» de este manual. Estas secuencias de caracteres permiten " -"que los mensajes de bienvenida contengan elementos como el nombre del equipo." - -#: C/gdm.xml:1320(title) -msgid "Remote Tab" -msgstr "Solapa Remoto" - -#: C/gdm.xml:1322(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 "" -"La solapa Remoto controla la apariencia de GDM para los usuarios que accedan " -"a través de XDMCP. De forma predeterminada, XDMCP está desactivado y los " -"usuarios deberían entender las secciones relacionadas con XDMCP de la " -"sección de Seguridad de este documento antes de activarlo. Esta solapa " -"incluye una caja combinada «Estilo» que se puede usar para activar XDMCP y " -"controlar la apariencia de GDM para usuarios remotos (gui/RemoteGreeter y " -"xdmcp/Enable). El usuario puede especificar si quiere usar la misma " -"apariencia que e usa en la solapa Local, o el otro programa. Si en la solapa " -"Local está activado el Visor de rostros, entonces también estará activada " -"para la solapa Remoto. Si el Visor de rostros no está activado en la solapa " -"Local, entonces tampoco estará activado en la solapa Remoto. Se recomienda " -"que se use la IGU «Plano» para las conexiones remotas ya que es más ligero y " -"tiende a tener mejor rendimiento a través de la red." - -#: C/gdm.xml:1339(para) -msgid "" -"If Remote login is enabled, then the welcome message for remote DISPLAYs may " -"be specified (greeter/DefaultRemoteWelcome and greeter/RemoteWelcome). This " -"welcome message is separate from the one shown for attached displays defined " -"in the Local tab and can have a different value. The welcome message may " -"contain the character sequences described in the \"Text Node\" subsection of " -"the \"Themed Greeter\" section of this manual. These character sequences " -"allow the welcome message to contain things like the display or host name." -msgstr "" -"Si la entrada remota está activada, entonces el usuario puede especificar el " -"mensaje de bienvenida remoto que se mostrará (greeter/DefaultRemoteWelcome y " -"greeter/RemoteWelcome). Este mensaje de bienvenida está separado del mensaje " -"de bienvenida local definido en la solapa Local y puede tener un valor " -"diferente. El mensaje de bienvenida puede contener las secuencias de " -"caracteres descritas en la subección «Nodo de texto» de la sección «Interfaz " -"con temas» de este manual. Estas secuencias de caracteres permiten que los " -"mensajes de bienvenida contengan elementos como el nombre del equipo." - -#: C/gdm.xml:1351(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 "" -"Si la selección de «Estilo» es «La misma que local» y la selección local es " -"«Plano» o «Plano sin visor de rostros», entonces el usuario puede " -"seleccionar si las imágenes del fondo debe mostrarse para las entradas " -"remotas (greeter/BackgroundRemoteOnlyColor)." - -#: C/gdm.xml:1359(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 "" -"Si la selección «Estilo» está activada y establecida a un valor diferente " -"que la solapa «Local», entonces el usuario tiene las mismas selecciones de " -"configuración que las encontradas en la solapa Local, excepto que las del " -"Menú de Sistema, debido a que nunca están disponibles para las entradas " -"remotas por razones de seguridad." - -#: C/gdm.xml:1367(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 "" -"Si está activada la entrada remota, hay un botón «Configurar XDMCP» que " -"muestra un diálogo permitiendo al usuario establecer la configuración XDMCP, " -"incluyendo si se confían las peticiones indirectas (xdmcp/MaxPending), las " -"peticiones indirectas pendientes máximas (xmdcp/MaxPendingIndirect), las " -"sesiones remotas máximas (xdmcp/MaxSessions), tiempo máximo de espera " -"(xdmcp/MaxWait), tiempo máximo de espera para peticiones indirectas (xdmcp/" -"MaxWaitIndirect), pantallas por equipo remoto (xdmcp/DisplaysPerHost), e " -"intervalo de ping (xdmcp/PingIntervalSeconds). Los ajustes predeterminados " -"son ajustes estándar y sólo deberían cambiarse por alguien que entienda las " -"ramificaciones del cambio." - -#: C/gdm.xml:1383(title) -msgid "Accessibility Tab" -msgstr "Solapa Accesibilidad" - -#: C/gdm.xml:1385(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 "" -"La solapa de Accesibilidad se usa para activar las características de " -"Accesibilidad en GDM. «|Activar entrada accesible» (daemon/AddGtkModules y " -"daemon/GtkModulesList) activa los oyentes de gestos de GDM que se explican " -"en la sección «Accesibilidad» de este documento. Hay además una casilla para " -"permitir a los usuarios cambiar el tema al usar el interfaz «Plano» (gui/" -"AllowGtkThemeChange). Esta característica permite a los usuarios de GDM " -"cambiar el tema a temas de Alto Contraste o Bajo Contraste si fuera " -"necesario. El usuario podría seleccionar además si GDM debería reproducir un " -"sonido cuando la pantalla de entrada esté preparara, cuando la entrada tiene " -"éxito y cuando la entrada ha fallado. Los botones del selector de archivos " -"se usan para seleccionar el archivo de sonido a reproducir, y el botón " -"«Reproducir» se puede usar para obtener una muestra del sonido." - -#: C/gdm.xml:1402(title) -msgid "Security Tab" -msgstr "Solapa Seguridad" - -#: C/gdm.xml:1404(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 "" -"La solapa Seguridad permite al usuario activar la entrada automática y la " -"entrada temporizada, qué usuario entra por medio de una entrada automática o " -"temporizada, y el retardo de la entrada temporizada (daemon/" -"AutomaticLoginEnable, daemon/AutomaticLogin, daemon/TimedLoginEnable, daemon/" -"TimedLogin, y daemon/TimedLoginDelay). Si se activa la entrada automática, " -"entonces el usuario especificado entrará automáticamente al reiniciar sin " -"que GDM pida usuario y contraseña. Si el usuario sale de su sesión, GDM se " -"iniciará y pedirá un usuario y contraseña para volver a entrar. Si " -"TimedLogin está activado, entonces GDM iniciará sesión con el usuario " -"especificado tras un número especificado de segundos. El usuario podría " -"activar la entrada temporizada para las conexiones remotas (XDMCP) marcando " -"la casilla «Permitir entradas remotas temporizadas»." - -#: C/gdm.xml:1419(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 "" -"En esta solapa, el usuario puede seleccionar si el usuario administrador del " -"sistema puede entrar, y si el usuario administrador del sistema puede entrar " -"por medio de conexiones remotas (XDMCP) (security/AllowRoot y security/" -"AllowRemoteRoot). El usuario puede activar la depuración de GDM (debug/" -"Enable) lo cual causa que los mensajes de depuración se envíen al registro " -"del sistema. La depuración sólo debería usarse para diagnosticar un problema " -"y no debería dejarse activada cuando no se necesita. Si se selecciona la " -"opción «Denegar conexiones TCP al servidor X» desactivará el reenvío de X " -"(security/DisallowTCP). Se puede establecer un retardo de entrada (security/" -"RetryDelay) para hacer que GDM espere un número de segundos después de una " -"entrada fallida." - -#: C/gdm.xml:1432(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 "" -"El botón «Configurar servidor X» se puede usar para especificar como GDM " -"gestiona cada pantalla. La caja combo «Servidores» muestra qué definiciones " -"de servidor están disponibles (Estándar, Terminal, y Selector por omisión). " -"Vea la sección «Definiciones de servidor X» de la sección de «Configuración» " -"para más información acerca de cómo crear nuevas definiciones de servidores." - -#: C/gdm.xml:1441(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 "" -"Para cualquier tipo de servidor, el usuario podría modificar el «Nombre del " -"servidor» (server/name), el «Comando» (server/command) que se usa para " -"lanzar el servidor X, si el tipo de servidor lanzará la interfaz de entrada " -"o el de selección de equipo remoto (server/chooser) tras iniciar el servidor " -"X, si GDM manipulará este tipo (normalmente sólo se establece a «false» " -"cuando se entra en una sesión de tipo terminal), y si el tipo de sesión " -"soporta sesiones «Flexibles» (server/flexible)." - -#: C/gdm.xml:1451(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 "" -"La sección «Servidores que iniciar» muestra qué tipo de servidor se muestra " -"para cada pantalla en la máquina. Los usuarios podrían pulsar en el botón " -"«Añadir/Modificar) para añadir una pantalla nueva a la lista o para " -"modificar una pantalla seleccionada, Esto simplemente hace corresponder a " -"cada pantalla física con la definición del servidor que se usará para " -"gestionar esa pantalla. El botón «Quitar» se puede usar para quitar una " -"pantalla de la lista." - -#: C/gdm.xml:1463(title) -msgid "Users Tab" -msgstr "Solapa Usuarios" - -#: C/gdm.xml:1465(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 "" -"La solapa Usuarios controla qué usuarios aparecen en el Visor de Rostros. Si " -"la casilla «Incluir todos los usuarios de /etc/password» está seleccionada, " -"entonces todos los usuarios (con un id de usuario por encime de greeter/" -"MinimalUID y que no estén en la lista Excluir) se muestran. Si esta casilla " -"no está seleccionada, entonces los usuarios se deben añadir a la lista " -"«Incluir». Los usuarios en la lista «Excluir» nunca se muestran. Los botones " -"«Añadir» y «Quitar» se usan para añadir un usuario nuevo a la lista o quitar " -"un usuario seleccionado de la lista. El botón «Aplicar cambios de usuarios» " -"se debe pulsar tras modificar las listas «Incluir» y «Excluir». Los botones " -"de flechas de la izquierda y derecha se pueden usar para mover un usuario " -"seleccionado de una lista a otra." - -#: C/gdm.xml:1483(title) -msgid "Configuration" -msgstr "Configuración" - -#: C/gdm.xml:1485(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:1495(para) -msgid "" -"The <command>gdmsetup</command> 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 "" -"El comando <command>gdmsetup</command> es un programa IGU que puede usar " -"para editar la configuración de GDM. Este programa puede lanzarse " -"directamente desde la pantalla de entrada si la clave greeter/" -"ConfigAvailable está establecida a «true». El GUI no soporta todas las " -"claves de configuración de GDM, así que quizá tenga que editar los archivos " -"de configuración a mano para editar esas claves. Si crees que ejecutar un " -"GUI perteneciente al root es un riesgo de seguridad, entonces podría querer " -"editar siempre estos archivos a mano. Este programa no soporta establecer la " -"configuración por cada pantalla, así que los archivos de configuración por " -"cada pantalla deben configurarse a mano." - -#: C/gdm.xml:1507(para) -msgid "" -"Aside from the GDM System Defaults Configuration File, the other GDM " -"configuration files are located, by default, in the <filename><etc>/" -"gdm/</filename> 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 "" -"Además del archivo de configuración predeterminada del sistema de GDM, los " -"otros archivos de configuración de GDM, de forma predeterminada, están " -"ubicados en la carpeta <filename><etc>/gdm/</filename> o alguno de sus " -"subdirectorios. Note que la ubicación de muchos archivos de configuración " -"está definida en los archivos de configuración de GDM, así que compruebe el " -"archivo de configuración predeterminada del sistema de GDM y el archivo de " -"configuración personalizada de GDM si los archivos no se encuentran en las " -"ubicaciones especificadas en este documento." - -#: C/gdm.xml:1517(para) -msgid "Listing of the config directory contents:" -msgstr "Esta es una lista del contenido del directorio de configuración:" - -#: C/gdm.xml:1521(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 "" -"\n" -"custom.conf\n" -"locale.alias\n" -"Xsession\n" -"XKeepsCrashing\n" -"modules/\n" -"Init/\n" -"PostLogin/\n" -"PreSession/\n" -"PostSession/\n" - -#: C/gdm.xml:1533(para) -msgid "" -"<filename>locale.alias</filename> 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 "" -"<filename>locale.alias</filename> es un archivo que se parece mucho al " -"archivo de alias regionales del sistema pero no es el mismo. Éstos son los " -"idiomas que están disponibles en su sistema. Todos los idiomas además se " -"prueban para ver si actualmente existen antes de presentárselos al usuario " -"en el diálogo de selección de idioma, en la IGU de entrada. Sólo se muestran " -"aquellos que existen." - -#: C/gdm.xml:1541(para) -msgid "" -"<filename>Xsession</filename> 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 <filename>desktop</filename> file associated with " -"the session the user has picked. Some sessions may start the user's session " -"via a different mechanism than the <filename>Xsession</filename> script, so " -"please check the appropriate <filename>desktop</filename> before assuming a " -"session startup issue is being caused by this file." -msgstr "" -"<filename>Xsession</filename> es un script que configura una sesión de " -"usuario y después ejecuta la selección de sesión del usuario. Note que el " -"script de sesión se inicia típicamente por el archivo <filename>desktop</" -"filename> asociado con la sesión que el usuario a escogido. Algunas sesiones " -"quizá inicien la sesión del usuario por medio de un mecanismo diferente que " -"el script <filename>Xsession</filename> así que marque el <filename>desktop</" -"filename> apropiado antes de asumir que el problema de inicio está causado " -"por este archivo." - -#: C/gdm.xml:1552(para) -msgid "" -"<filename>XKeepsCrashing</filename> 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 "" -"<filename>XKeepsCrashing</filename> es un script que se ejecuta cuando el " -"servidor X continúa colgándose y no se puede recuperar. El script " -"predeterminado incluido funcionará con la mayoría de las distribuciones de " -"Linux y puede ejecutar la aplicación de configuración de X siempre que la " -"persona en la consola conozca la contraseña de root." - -#: C/gdm.xml:1560(para) -msgid "" -"Accessibility modules are configured in the <filename>modules/</filename> " -"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 <filename>factory</filename> in their name, and " -"those files are not read, they are just there for you so you can always " -"revert to default config." -msgstr "" -"Los módulos de accesibilidad se configuran en el subdirectorio " -"<filename>modules/</filename>, y son un tema aparte. Lea los archivos " -"predeterminados provistos, tienen documentación adecuada. De nuevo " -"normalmente la instalación predeterminada se da en archivos con " -"<filename>factory</filename> en su nombre, y dichos archivos no se leen, " -"están solo ahí para que usted pueda volver siempre a la configuración " -"predeterminada." - -#: C/gdm.xml:1569(para) -msgid "" -"Files describing available GDM session follow the freedesktop.org desktop " -"file specification. The <filename>.desktop</filename>-style files are " -"installed to <filename><etc>/X11/sessions/</filename>. This directory " -"is also read by the KDE desktop manager (KDM) for common configuration. Next " -"the directory <filename><share>/gdm/BuiltInSessions/</filename> is " -"read for GDM specific built-in sessions (KDM hardcodes these at time of this " -"writing). Lastly the default setup will also read <filename><share>/" -"xsessions/</filename> (which should be <filename><share>/xsessions/</" -"filename> if you really wish to cooperate with KDM) where desktop packages " -"can install their session files. The directories under the <filename><" -"etc></filename> 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 <filename>SessionDesktopDir</filename> " -"configuration key for changing the paths. It used to be that GDM stored its " -"built in sessions in <filename><etc>/dm/Sessions/</filename> but this " -"is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the " -"<filename><etc>/dm/Sessions/</filename> was being read." -msgstr "" -"Los archivos que describen las sesiones GDM disponibles siguen la " -"especificación de archivos <filename>.desktop</filename> de freedesktop.org " -"y se instalan en <filename><etc>/X11/sessions/</filename>. Este " -"directorio también lo lee el gestor de entrada de KDE (KDM) para una " -"configuración común. El siguiente directorio <filename><share>/gdm/" -"BuiltInSessions/</filename> se lee para las sesiones integradas específicas " -"de GDM (KDM las lleva en el propio código cuando se escribió este manual). " -"Por último la configuración predeterminada también lee <filename><" -"share>/xsessions/</filename> (que debería ser <filename>/usr/share/" -"xsessions/</filename> si realmente quiere cooperar con KDM) donde los " -"paquetes del escritorio pueden instalar sus propios archivos de sesión. Los " -"directorios bajo <filename><etc></filename> deberían reservarse para " -"la configuración. La aproximación de la especificación de archivos de " -"escritorio facilita la instalación de gestores de ventanas y diferentes " -"tipos de sesiones a los sistemas de gestión de paquetes, sin requerir que el " -"administrador del sistema edite los archivos. Vea la clave de configuración " -"<filename>SessionDesktopDir</filename> para cambiar las rutas. Solía ocurrir " -"que GDM almacenaba sus sesiones integradas en <filename><etc>/dm/" -"Sessions/</filename> pero esto está obsoleto desde2.5.90.0. Note que antes " -"de la versión 2.4.4.2 sólo se leía <filename><etc>/dm/Sessions/</" -"filename>." - -#: C/gdm.xml:1592(para) -msgid "" -"A session can be disabled (if it was installed in <filename><share>/" -"xsessions/</filename>) by adding an identically named <filename>.desktop</" -"filename> to one of the directories earlier in the path (likely " -"<filename><etc>/X11/sessions</filename>) and using " -"<filename>Hidden=true</filename> in that file." -msgstr "" -"Puede desactivarse una sesión (si fue instalada en <filename><share>" -"xsessions/</filename>) añadiendo un <filename>.desktop</filename> nombrado " -"idénticamente a uno de los directorios anteriores en la ruta (como " -"<filename><etc>/X11/sessions</filename>) y usando " -"<filename>Hidden=true</filename> en ese archivo." - -#: C/gdm.xml:1600(para) -msgid "" -"GDM uses the optional key <filename>X-Gdm-XserverArgs</filename> in session " -"files to specify additional arguments to be passed to the X server. For " -"example, the entry <filename>X-Gdm-XserverArgs=-depth 16</filename> 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:1611(title) -msgid "The Script Directories" -msgstr "Los directorio de scripts" - -#: C/gdm.xml:1613(para) -msgid "" -"In this section we will explain the <filename>Init</filename>, " -"<filename>PostLogin</filename>, <filename>PreSession</filename> and " -"<filename>PostSession</filename> directories as they are very similar." -msgstr "" -"En esta sección explicaremos los directorios <filename>Init</filename>, " -"<filename>PostLogin</filename>, <filename>PreSession</filename> y " -"<filename>PostSession</filename> ya que son muy similares." - -#: C/gdm.xml:1619(para) -msgid "" -"When the X server has been successfully started, GDM will try to run the " -"script called <filename>Init/<displayname></filename>. I.e. " -"<filename>Init/:0</filename> for the first attached display. If this file is " -"not found, GDM will attempt to to run <filename>Init/<hostname></" -"filename>. I.e. <filename>Init/somehost</filename>. If this still is not " -"found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins or " -"<filename>Init/Flexi</filename> for all on demand flexible displays. If none " -"of the above were found, GDM will run <filename>Init/Default</filename>. The " -"script will be run as root and GDM blocks until it terminates. Use the " -"<filename>Init/*</filename> 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 "" -"Cuando el servidor X se haya iniciado con éxito, GDM intentará ejecutar el " -"script llamado <filename>Init/<displayname></filename>. Ej: " -"<filename>Init/:0</filename> para la primera pantalla local. Si este archivo " -"no se encuentra, GDM intentará ejecutar <filename>Init/<hostname></" -"filename>. Ej: <filename>Init/somehost</filename>. Si esto aún no se " -"encuentra, GDM intentará <filename>Init/XDMCP</filename> para todas las " -"entradas XDMCP o <filename>Init/Flexi</filename> para todas las pantallas " -"bajo demanda. Si no se encuentra ninguno de los anteriores, GDM ejecutará " -"<filename>Init/Default</filename>. El script se ejecutará como root y GDM se " -"bloquea hasta que termina. Use el script <filename>Init/*</filename> para " -"las aplicaciones que se suponen que se ejecutan junto con la ventana de " -"entrada de GDM. xconsole por ejemplo. Los comandos para establecer el fondo " -"de pantalla, etc. también van en este archivo." - -#: C/gdm.xml:1637(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 <filename>KillInitClients</filename> configuration option." -msgstr "" -"Es responsabilidad del administrador de sistemas decidir si los clientes " -"iniciados por el script Init deben matarse antes de iniciar la sesión del " -"usuario. Esto se controla con la opción de configuración " -"<filename>KillInitClients</filename>" - -#: C/gdm.xml:1644(para) -msgid "" -"When the user has been successfully authenticated GDM tries the scripts in " -"the <filename>PostLogin</filename> directory in the same manner as for the " -"<filename>Init</filename> 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 <filename>pam_mount</" -"filename> module if you can for this). You have the <filename>$USER</" -"filename> and <filename>$DISPLAY</filename> 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 "" -"Cuando el usuario ha sido autenticado con éxito GDM intenta los scripts en " -"el directorio <filename>PostLogin</filename> de la misma manera que para el " -"directorio <filename>Init</filename>. Esto se hace antes de que cualquier " -"configuración de la sesión se realice, y así que este debería ser el script " -"donde quizá usted desee configurar el directorio personal si necesita " -"hacerlo (aunque debería usar el módulo <filename>pam_mount</filename> si " -"puede para esto). Tiene las variables de entorno <filename>$USER</filename> " -"y <filename>$DISPLAY</filename> establecidas para este script, y de nuevo se " -"ejecuta como root. El script debería devolver 0 si tiene éxito y de otra " -"manera el usuario no iniciará sesión. Sin embargo esto no es cierto para la " -"sesión a prueba de fallos." - -#: C/gdm.xml:1658(para) -msgid "" -"After the user session has been setup from the GDM side of things, GDM will " -"run the scripts in the <filename>PreSession</filename> directory, again in " -"the same manner as the <filename>Init</filename> directory. This script can " -"be used for session management or accounting, for example. The <filename>" -"$USER</filename> environment variable contains the login of the " -"authenticated user and <filename>$DISPLAY</filename> 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 <filename>$X_SERVERS</filename> environmental " -"variable is set and this points to a fake generated X servers file for use " -"with the sessreg accounting application." -msgstr "" -"Después de que la sesión del usuario haya sido configurada desde el lado de " -"las cosas de GDM, GDM ejecutará los scripts en el directorio de " -"<filename>PreSession</filename>, de nuevo de la misma manera que el " -"directorio <filename>Init</filename>. Use este script para la gestión de " -"sesión local o las cuentas de usuario. La variable de entorno <filename>" -"$USER</filename> contiene el nombre de inicio de sesión del usuario " -"autenticado y <filename>$DISPLAY</filename> está establecido a la pantalla " -"actual. El script debería devolver 0 si tiene éxito. Cualquier otro valor " -"hará que GDM termine el proceso actual de inicio de sesión. Esto sin embargo " -"no ocurre para la sesión a prueba de fallos. Además la variable de entorno " -"<filename>$X_SERVERS</filename> está establecida y ésta apunta a un archivo " -"falso de servidores X generados para usarla con la aplicación de gestión de " -"cuentas sessreg." - -#: C/gdm.xml:1673(para) -msgid "" -"After this the base <filename>Xsession</filename> 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 <filename>Exec=</filename> line in the <filename>.desktop</" -"filename> files in the path specified by <filename>SessionDesktopDir</" -"filename>. Usually this path is <filename><etc>/X11/sessions/:<" -"etc>/dm/Sessions:/usr/share/xsessions/</filename>. The first found file " -"is used. The user either picks from these sessions or GDM will look inside " -"the file <filename>~/.dmrc</filename> for the stored preference." -msgstr "" -"Después de esto se ejecuta el script <filename>Xsession</filename> base con " -"el ejecutable de la sesión seleccionada como primer argumento. Esto se " -"ejecuta como el usuario, y realmente esta es la sesión del usuario. Los " -"ejecutables de sesiones disponibles se toman de la línea <filename>Exec=</" -"filename> en los archivos <filename>.desktop</filename> de la ruta " -"especificada en <filename>SessionDesktopDir</filename>. Usualmente esta ruta " -"es <filename><etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/" -"xsessions/</filename>. Se usa el primer archivo encontrado. El usuario o " -"escoge de estas sesiones o GDM buscará dentro del archivo <filename>~/.dmrc</" -"filename> la preferencia almacenada." - -#: C/gdm.xml:1686(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 <filename>$GDM_LANG</" -"filename> 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 <filename>$GDM_LANG</filename> " -"is not set." -msgstr "" -"Este script debería cargar realmente el perfil de los usuarios y " -"generalmente hacer todo el vudú que se necesita para lanzar una sesión. " -"Debido a que muchos sistemas restablecen las selecciones de idioma " -"realizadas por GDM, GDM también establece la variable <filename>$GDM_LANG</" -"filename> al idioma seleccionado. Puede usar esto para restaurar las " -"variables de entorno de idiomas tras ejecutar el perfil del usuario. Si el " -"usuario eligió el idioma del sistema, entonces <filename>$GDM_LANG</" -"filename> no se establece." - -#: C/gdm.xml:1696(para) -msgid "" -"When the user terminates his session, the <filename>PostSession</filename> " -"script will be run. Again operation is similar to <filename>Init</filename>, " -"<filename>PostLogin</filename> and <filename>PreSession</filename>. Again " -"the script will be run with root privileges, the slave daemon will block and " -"the <filename>$USER</filename> environment variable will contain the name of " -"the user who just logged out and <filename>$DISPLAY</filename> will be set " -"to the display the user used, however note that the X server for this " -"display may already be dead and so you shouldn't try to access it. Also " -"<filename>$X_SERVERS</filename> environmental variable is set and this " -"points to a fake generated X servers file for use with the sessreg " -"accounting application." -msgstr "" -"Cuando el usuario termina su sesión, se ejecuta el script " -"<filename>PostSession</filename>. De nuevo la operación es similar a " -"<filename>Init</filename>, <filename>PostLogin</filename> y " -"<filename>PreSession</filename>. De nuevo el script se ejecuta con " -"privilegios de root, el demonio esclavo se bloqueará y la variable de " -"entorno <filename>$USER</filename> contendrá el nombre del usuario que acaba " -"de cerrar sesión y <filename>$DISPLAY</filename> se establecerá al " -"visualizador que el usuario usó, sin embargo note que el servidor X para " -"este visualizador quizá ya esté muerto y así que no debería intentar acceder " -"a él. Además la variable de entorno <filename>$X_SERVERS</filename> está " -"establecida y ésta apunta a un archivo generado falsificado de servidores X " -"para usar con la aplicación de contabilidad sessreg." - -#: C/gdm.xml:1711(para) -msgid "" -"Note that the <filename>PostSession</filename> script will be run even when " -"the display fails to respond due to an I/O error or similar. Thus, there is " -"no guarantee that X applications will work during script execution." -msgstr "" -"Note que el script de <filename>PostSession</filename> se ejecutará incluso " -"cuando el visualizador falle al responder debido a un error de E/S o " -"similar. Así que, no hay garantía de que funcionen las aplicaciones X " -"durante la ejecución del script." - -#: C/gdm.xml:1718(para) -msgid "" -"Except for the <filename>Xsession</filename> script all of these scripts " -"will also have the environment variable <filename>$RUNNING_UNDER_GDM</" -"filename> set to <filename>yes</filename>, so that you could perhaps use " -"similar scripts for different display managers. The <filename>Xsession</" -"filename> will always have the <filename>$GDMSESSION</filename> set to the " -"basename of the session that the user chose to run without the <filename>." -"desktop</filename> extension. In addition <filename>$DESKTOP_SESSION</" -"filename> is also set to the same value and in fact this will also be set by " -"KDM in future versions." -msgstr "" -"Excepto para el script <filename>Xsession</filename> todos estos scripts " -"también tendrán la variable de entorno <filename>$RUNNING_UNDER_GDM</" -"filename> establecida a <filename>yes</filename>, así que podría quizás usar " -"scripts similares para distintos gestores de entrada. <filename>Xsession</" -"filename> siempre tendrá <filename>$GDMSESSION</filename> establecido al " -"nombre base de la sesión que el usuario eligió ejecutar sin la extensión " -"<filename>.desktop</filename>. Además <filename>$DESKTOP_SESSION</filename> " -"también está establecida al mismo valor y de hecho esto también lo " -"establecerá KDM en versiones futuras." - -#: C/gdm.xml:1732(para) -msgid "" -"Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, " -"<filename>PreSession</filename> or <filename>PostSession</filename> scripts " -"are necessary and can be left out. The <filename>Xsession</filename> script " -"is however required as well as at least one session <filename>.desktop</" -"filename> file." -msgstr "" -"Ninguno de scripts <filename>Init</filename>, <filename>PostLogin</" -"filename>, <filename>PreSession</filename> o <filename>PostSession</" -"filename> son necesarios y se pueden dejar vacíos. El script " -"<filename>Xsession</filename> sin embargo es necesario así como al menos un " -"archivo de sesión <filename>.desktop</filename>." - -#: C/gdm.xml:1742(title) -msgid "" -"The Configuration Files - GDM System Defaults Configuration File and GDM " -"Custom Configuraiton File" -msgstr "" - -#: C/gdm.xml:1745(para) -msgid "" -"GDM uses two configuration files: the GDM System Defaults Configuration File " -"(<filename><share>/gdm/defaults.conf</filename>) and the GDM Custom " -"Configuration File (<filename><etc>/gdm/custom.conf</filename>). 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 "" -"GDM usa dos archivos de configuración: el archivo de configuración " -"predeterminada del sistema de GDM<filename><share>/gdm/defaults.conf</" -"filename> y el archivo de configuración personalizada de GDM <filename><" -"etc>/gdm/custom.conf</filename>. El archivo de configuración " -"predeterminada del sistema de GDM contiene las elecciones de configuración " -"predeterminadas para GDM, y no debería modificarse por el usuario. El " -"archivo de configuración personalizada de GDM es donde los usuarios pueden " -"especificar sus elecciones de configuración personales. Si una opción de " -"configuración no está definida en cualquier archivo, GDM usará el valor " -"predeterminado descrito en los comentarios en el archivo de configuración " -"predeterminada del sistema de GDM." - -#: C/gdm.xml:1758(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 "" -"Ambos archivos de configuración están divididos en secciones cada una " -"conteniendo variables que definen el comportamiento para una parte " -"específica de la suite GDM. Refiérase a los comentarios en el archivo de " -"configuración predeterminada del sistema de GDM para obtener información " -"adicional acerca de cada ajuste de configuración." - -#: C/gdm.xml:1765(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 <filename><etc>/gdm/custom.conf<display " -"num></filename>. 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 <filename><etc>/gdm/custom.conf:0</" -"filename>. Per-display configuration is supported in GDM 2.14.6 and later." -msgstr "" - -#: C/gdm.xml:1778(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 "" -"Para cambiar la configuración a mano, edite el archivo de configuración " -"personalizada de GDM o el archivo de configuración de cada pantalla y " -"asegúrese de que el par clave=valor que quiere está incluido en la sección " -"apropiada. Por ejemplo, para cambiar la clave \"Greeter\" en la sección " -"\"daemon\" asegúrese de que la sección daemon del archivo de configuración " -"personalizada de GDM o el archivo de configuración de cada pantalla incluye " -"la sección \"[daemon]\" seguida por la clave y el cambio de valor deseado. " -"Como en este ejemplo:" - -#: C/gdm.xml:1789(screen) -#, no-wrap -msgid "" -"\n" -"[daemon]\n" -"Greeter=/usr/lib/gdmgreeter\n" -msgstr "" -"\n" -"[daemon]\n" -"Greeter=/usr/lib/gdmgreeter\n" - -#: C/gdm.xml:1794(para) -msgid "" -"The <command>gdmsetup</command> command can be used to modify the GDM Custom " -"Configuration File. Note the <command>gdmsetup</command> 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:1801(para) -msgid "" -"The GDM daemon <command>--config</command> 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 " -"<command>--with-defaults-conf</command> and <command>--with-custom-conf</" -"command> configuration options." -msgstr "" - -#: C/gdm.xml:1810(para) -msgid "" -"Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</" -"filename> 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 <filename><etc>/gdm/gdm.conf</filename> file is different than the " -"<filename><etc>/gdm/factory-gdm.conf</filename> file. If so, the " -"<filename><etc>/gdm/gdm.conf</filename> file will be automatically " -"copied to <filename><etc>/gdm/custom.conf</filename> to preserve any " -"configuration changes." -msgstr "" -"Anterior a GDM 2.13.0.4 sólo existía el archivo <filename><etc>/gdm/" -"gdm.conf</filename>. Para una mejor compatibilidad hacia atrás, se usará " -"este archivo en lugar del archivo de configuración personalizado de GDM, si " -"es que existe en su sistema. Si actualiza a una versión nueva de GDM, la " -"instalación comprobará para ver si su archivo <filename><etc>/gdm/gdm." -"conf</filename> es diferente del archivo <filename><etc>/gdm/factory-" -"gdm.conf</filename> . Si lo es, se copiará automáticamente el archivo " -"<filename><etc>/gdm/gdm.conf</filename> a <filename><etc>/gdm/" -"custom.conf</filename> para preservar cualquier cambio de configuración." - -#: C/gdm.xml:1824(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:1833(para) -msgid "" -"The GDM System Defaults Configuration File and the GDM Custom Configuration " -"File follow the standard <filename>.ini</filename> 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 "" -"Los archivos de configuración predeterminada del sistema de GDM y el archivo " -"de configuración personalizada de GDM siguien el estilo de sintaxis estándar " -"del archivo de configuración <filename>.ini</filename>. Las palabras clave " -"entre corchetes definen secciones, las cadenas antes del signo igual (=) son " -"variables y los datos tras el signo igual representan su valor. Las líneas " -"en blanco o las líneas que empiezan con la almohadilla (#) se ignoran. El " -"configurador gráfico intentará preservar tanto los comentarios (líneas con " -"una almohadilla) como la estructura completa del archivo, así que puede " -"intercambiar usando el IGU o editando a mano el archivo de configuración." - -#: C/gdm.xml:1845(para) -msgid "The following configuration keys are supported in GDM:" -msgstr "Se soportan las siguientes claves de configuración en GDM:" - -#: C/gdm.xml:1850(title) -msgid "Daemon Configuration" -msgstr "Configuración del demonio" - -#: C/gdm.xml:1853(title) -msgid "[daemon]" -msgstr "[daemon]" - -#: C/gdm.xml:1856(term) -msgid "AddGtkModules" -msgstr "AddGtkModules" - -#: C/gdm.xml:1858(synopsis) -#, no-wrap -msgid "AddGtkModules=false" -msgstr "AddGtkModules=false" - -#: C/gdm.xml:1859(para) -msgid "" -"If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</" -"command> 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 "" -"Si es true, entonces activa <command>gdmgreeter</command> o " -"<command>gdmlogin</command> para que se lancen con módulos GTK+ adicionales. " -"esto es útil cuando se requieren características extra como un inicio sesión " -"accesible. Note que sólo deberían usarse los módulos «confiables» para " -"minimizar las cuestiones de seguridad." - -#: C/gdm.xml:1866(para) -msgid "" -"If true, then the registry daemon <command>at-spi-registryd</command> will " -"be launched by <command>gdmgreeter</command> or <command>gdmlogin</command> " -"starting with version GDM 2.17." -msgstr "" -"Si es true, entonces el demonio de registro <command>at-spi-registryd</" -"command> se lanzará por <command>gdmgreeter</command> o <command>gdmlogin</" -"command> iniciando con la versión GDM 2.17." - -#: C/gdm.xml:1872(para) -msgid "" -"Usually this is used for accessibility modules. The modules which are loaded " -"are specified with the <filename>GtkModulesList</filename> key." -msgstr "" -"Usualmente esto se usa para los módulos de accesibilidad. Los módulos que se " -"cargan se especifican con la clave <filename>GtkModulesList</filename>." - -#: C/gdm.xml:1881(term) -msgid "AllowLogoutActions" -msgstr "AllowLogoutActions" - -#: C/gdm.xml:1883(synopsis) -#, no-wrap -msgid "AllowLogoutActions=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD" -msgstr "AllowLogoutActions=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD" - -#: C/gdm.xml:1884(para) -msgid "" -"Specify which actions are supported by the QUERY_LOGOUT_ACTION, " -"SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</" -"command> 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 " -"<filename>SystemCommandsInMenu</filename> and " -"<filename>RBACSystemCommandKeys</filename> configuration options." -msgstr "" - -#: C/gdm.xml:1899(term) -msgid "AlwaysLoginCurrentSession" -msgstr "AlwaysLoginCurrentSession" - -#: C/gdm.xml:1901(synopsis) -#, no-wrap -msgid "AlwaysLoginCurrentSession=true" -msgstr "AlwaysLoginCurrentSession=true" - -#: C/gdm.xml:1902(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 "" -"Si es «true», cuando el usuario entra y ya tiene una sesión existente, " -"entonces se concecta a esa sesión en lugar de iniciar una sesión nueva. Esto " -"sólo funciona en sesiones que se ejecutan en VTs (Virtual Terminals) " -"iniciados con gdmflexiserver, y no con XDMCP. Note que los VTs no están " -"soportados en todos los sistemas operativos." - -#: C/gdm.xml:1914(term) -msgid "AutomaticLoginEnable" -msgstr "AutomaticLoginEnable" - -#: C/gdm.xml:1916(synopsis) -#, no-wrap -msgid "AutomaticLoginEnable=false" -msgstr "AutomaticLoginEnable=false" - -#: C/gdm.xml:1917(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 " -"console security is not an issue and also could be useful for public " -"terminals. Refer also to <filename>TimedLogin</filename>." -msgstr "" -"Si el usuario dado en AutomaticLogin debería entrar al primer arranque. No " -"se pedirá ninguna contraseña. Esto es útil para estaciones de trabajo de un " -"sólo usuario donde la seguridad de la consola local no es un problema y, " -"además, podría ser útil para terminales públicos. Referente también sobre " -"<filename>TimedLogin</filename>." - -#: C/gdm.xml:1928(term) -msgid "AutomaticLogin" -msgstr "AutomaticLogin" - -#: C/gdm.xml:1930(synopsis) -#, no-wrap -msgid "AutomaticLogin=" -msgstr "AutomaticLogin=" - -#: C/gdm.xml:1931(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 "" -"Este usuario debería iniciar sesión automáticamente al primer arranque. " -"AutomaticLoginEnable debe ser true y esto debe ser un usuario válido para " -"que esto ocurra. Sin embargo \"root\" nunca puede iniciar una sesión " -"automáticamente y gdm se negará a hacerlo incluso si lo configura." - -#: C/gdm.xml:1939(para) -msgid "The following control chars are recognized within the specified name:" -msgstr "" -"Se reconocen los siguientes caracteres de control dentro del nombre " -"especificado:" - -#: C/gdm.xml:1944(para) C/gdm.xml:4056(para) -msgid "%% — the `%' character" -msgstr "%% — Un carácter literal «%»" - -#: C/gdm.xml:1948(para) -msgid "%d — display's name" -msgstr "%d — nombre de la pantalla" - -#: C/gdm.xml:1952(para) -msgid "%h — display's hostname" -msgstr "%h — nombre de equipo de la pantalla" - -#: C/gdm.xml:1956(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 "" -"Alternativamente, el nombre podría terminar con una barra vertical |, el " -"símbolo de cauce. El nombre se usa entonces como una aplicación a ejecutar " -"que revuelve el nombre de usuario deseado en la salida estándar. Si se " -"devuelve un nombre de usuario vacío o inválido, no se realiza el inicio de " -"sesión automático. Esta característica se usa típicamente cuando se usan " -"varios visores remotos como kioscos de Internet, con un usuario específico " -"para iniciar sesión automáticamente en cada visualizador." - -#: C/gdm.xml:1969(term) -msgid "BaseXsession" -msgstr "BaseXsession" - -#: C/gdm.xml:1971(synopsis) -#, no-wrap -msgid "BaseXsession=<etc>/gdm/Xsession" -msgstr "BaseXsession=<etc>/gdm/Xsession" - -#: C/gdm.xml:1972(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 <filename>Exec=</filename> from the <filename>.desktop</" -"filename> file of the session." -msgstr "" -"Este es el archivo base X session. Cuando un usuario entra, este script se " -"ejecuta con la sesión seleccionada como primer argumento. La sesión " -"seleccionada será la indicada por <filename>Exec=</filename> en el archivo " -"de sesión <filename>.desktop</filename>." - -#: C/gdm.xml:1980(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 <filename>GDMSESSION</filename> environmental variable. This " -"will always be set to the basename of <filename>.desktop</filename> (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 " -"<filename>GDM_LANG</filename>, but that is only set when the user picks a " -"non-system default language." -msgstr "" -"Si quiere usar el mismo script para varios gestores de entrada diferentes, y " -"quiere tener algunos de los scripts para que sólo se ejecuten por GDM, " -"entonces puede comprobar por la presencia de la variable de entorno " -"<filename>GDMSESSION</filename>. Esto siempre será establecido al nombre " -"base del archivo <filename>.desktop</filename> (sin la extensión) que se " -"está usando en esta sesión, y sólo estará establecido para las sesiones GDM. " -"Anteriormente algunos scripts estaban comprobando <filename>GDM_LANG</" -"filename>, pero eso sólo se establece cuando el usuario escoge un idioma no " -"predeterminado del sistema." - -#: C/gdm.xml:1993(para) -msgid "" -"This script should take care of doing the \"login\" for the user and so it " -"should source the <filename><etc>/profile</filename> and friends. The " -"standard script shipped with GDM sources the files in this order: " -"<filename><etc>/profile</filename> then <filename>~/.profile</" -"filename> then <filename><etc>/xprofile</filename> and finally " -"<filename>~/.xprofile</filename>. Note that different distributions may " -"change this however. Sometimes users personal setup will be in <filename>~/." -"bash_profile</filename>, however broken that is." -msgstr "" -"Este script debería encargarse de hacer el login para el usuario y por lo " -"tanto debería incluir <filename><etc>/profile</filename> y demás. El " -"script estándar entregado con GDM incluye los archivos en este orden: " -"<filename><etc>/profile</filename> después <filename>~/.profile</" -"filename> después <filename><etc>/xprofile</filename> y " -"finalmente<filename>~/.xprofile</filename>. Note que las diferentes " -"distribuciones podrían cambiar esto. Algunas veces la configuración personal " -"del usuario estará en <filename>~/.bash_profile</filename>, por muy " -"defectuoso que esto sea." - -#: C/gdm.xml:2010(term) -msgid "Chooser" -msgstr "Selector" - -#: C/gdm.xml:2012(synopsis) -#, no-wrap -msgid "Chooser=<bin>/gdmchooser" -msgstr "Chooser=<bin>/gdmchooser" - -#: C/gdm.xml:2013(para) -msgid "Full path and name of the chooser executable followed by optional arguments." -msgstr "" -"Ruta completa y nombre del ejecutable del selector seguido de argumentos " -"opcionales." - -#: C/gdm.xml:2021(term) -msgid "Configurator" -msgstr "Configurator" - -#: C/gdm.xml:2023(synopsis) -#, no-wrap -msgid "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" -msgstr "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" - -#: C/gdm.xml:2024(para) -msgid "" -"The pathname to the configurator binary. If the greeter " -"<filename>ConfigAvailable</filename> 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 "" -"La ruta hacia el binario del configurador. Si la opción del interfaz " -"<filename>ConfigAvailable</filename> está puesta a «true» entonces se " -"ejecuta este binario cuando alguien elije Configuración desde el menú de " -"Acciones. Desde luego GDM pedirá primero la contraseña de root. Y nunca " -"permitirá que esto ocurra desde una pantalla remota." - -#: C/gdm.xml:2036(term) -msgid "ConsoleCannotHandle" -msgstr "ConsoleCannotHandle" - -#: C/gdm.xml:2038(synopsis) -#, no-wrap -msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" -msgstr "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" - -#: C/gdm.xml:2039(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 "" -"Éstos son los idiomas que la consola no puede manipular debido a cuestiones " -"de tipografía. Aquí queremos decir la consola de texto, no X. Esto sólo se " -"usa cuando hay errores que informar y no podemos iniciar X." - -#: C/gdm.xml:2049(term) -msgid "ConsoleNotify" -msgstr "ConsoleNotify" - -#: C/gdm.xml:2051(synopsis) -#, no-wrap -msgid "ConsoleNotify=true" -msgstr "ConsoleNotify=true" - -#: C/gdm.xml:2052(para) -msgid "" -"If false, gdm will not display a message dialog on the console when an error " -"happens." -msgstr "" -"Si es false, gdm no mostrará un diálogo de mensaje en la consola cuando " -"ocurra un error." - -#: C/gdm.xml:2060(term) -msgid "DefaultPath" -msgstr "DefaultPath" - -#: C/gdm.xml:2062(synopsis) -#, no-wrap -msgid "DefaultPath=defaultpath (value set by configure)" -msgstr "DefaultPath=defaultpath (valor establecido por la configuración)" - -#: C/gdm.xml:2063(para) -msgid "" -"Specifies the path which will be set in the user's session. This value will " -"be overridden with the value from <filename>/etc/default/login</filename> if " -"it contains \"ROOT=<pathname>\". If the <filename>/etc/default/login</" -"filename> file exists, but contains no value for ROOT, the value as defined " -"in the GDM configuration will be be used." -msgstr "" -"Especifica la ruta que debe establecerse en la sesión del usuario. Este " -"valor será sobreescrito por el valor de <filename>/etc/default/login</" -"filename> si contiene \"ROOT=<pathname>\". Si el archivo <filename>/" -"etc/default/login</filename> existe, pero no contiene ningún valor para " -"ROOT, se usará el el valor tal como esté definido en la configuración de GDM." - -#: C/gdm.xml:2076(term) -msgid "DefaultSession" -msgstr "DefaultSession" - -#: C/gdm.xml:2078(synopsis) -#, no-wrap -msgid "DefaultSession=gnome.desktop" -msgstr "DefaultSession=gnome.desktop" - -#: C/gdm.xml:2079(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 <filename>ShowLastSession</filename> key." -msgstr "" -"La sesión que se usará por omisión si el usuario no tiene una preferencia " -"guardada y ha escogido «Última» desde la lista de sesiones. Note que " -"«Última» no necesita mostrarse, vea la clave <filename>ShowLastSession</" -"filename>." - -#: C/gdm.xml:2090(term) -msgid "DisplayInitDir" -msgstr "DisplayInitDir" - -#: C/gdm.xml:2092(synopsis) -#, no-wrap -msgid "DisplayInitDir=<etc>/gdm/Init" -msgstr "DisplayInitDir=<etc>/gdm/Init" - -#: C/gdm.xml:2093(para) -msgid "" -"Directory containing the display init scripts. See the ``The Script " -"Directories'' section for more info." -msgstr "" -"Directorio que contiene los script de inicio de la pantalla. Vea la sección " -"«Los directorios de scripts» para más información." - -#: C/gdm.xml:2101(term) -msgid "DisplayLastLogin" -msgstr "DisplayLastLogin" - -#: C/gdm.xml:2103(synopsis) -#, no-wrap -msgid "DisplayLastLogin=true" -msgstr "DisplayLastLogin=true" - -#: C/gdm.xml:2104(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 "" -"Si es «true» entonces la última información de entrada se imprime para el " -"usuario antes de pedirle una contraseña. Mientras que esto revela algo de " -"información acerca de qué usuarios están en un sistema, por otra parte " -"debería dar al usuario una idea de cuando entró y si no parece cierta, " -"pueden entonces abortar la entrada y contactar con el administrador del " -"equipo (evitando ejecutar scripts de inicio maliciosos). Esto se añadió en " -"la versión 2.5.90.0" - -#: C/gdm.xml:2113(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 <filename>http://www." -"radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> for more " -"info." -msgstr "" -"Esto es para que GDM sea conforme a CSC-STD-002-85, aunque es puramente " -"teórico ahora. Alguien debería leer esa especificación y asegurarse de que " -"esto actualmente es conforme (en conjunto con otros lugares en GDM). Vea " -"<filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85." -"html</filename> para más información." - -#: C/gdm.xml:2125(term) -msgid "DoubleLoginWarning" -msgstr "DoubleLoginWarning" - -#: C/gdm.xml:2127(synopsis) -#, no-wrap -msgid "DoubleLoginWarning=true" -msgstr "DoubleLoginWarning=true" - -#: C/gdm.xml:2128(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 "" -"si es «true», GDM avisará al usuario si ya ha entrado en otro terminal " -"virtual. En sistemas donde GDM soporte comprobar los terminales virtuales X, " -"GDM permitirá al usuario cambiar al terminal de entrada anterior en lugar de " -"entrar." - -#: C/gdm.xml:2138(term) -msgid "DynamicXServers" -msgstr "DynamicXServers" - -#: C/gdm.xml:2140(synopsis) -#, no-wrap -msgid "DynamicXServers=false" -msgstr "DynamicXServers=false" - -#: C/gdm.xml:2141(para) -msgid "" -"If true, the GDM daemon will honor requests to manage displays via the " -"<filename>/tmp/.gdm_socket</filename> socket connection. Displays can be " -"created, started, and deleted with the appropriate commands. The " -"<filename>gdmdynamic</filename> command is a convenient method to send these " -"messages." -msgstr "" -"Si es «true», el demonio GDM confiará en las peticiones para gestionar " -"pantallas por medio de una conexión socket en <filename>/tmp/.gdm_socket</" -"filename>. Las pantallas se pueden crear, iniciar y borrar con los comandos " -"apropiados. El comando <filename>gdmdynamic</filename> es un método " -"conveniente para enviar estos mensajes." - -#: C/gdm.xml:2153(term) -msgid "FailsafeXServer" -msgstr "FailsafeXServer" - -#: C/gdm.xml:2155(synopsis) -#, no-wrap -msgid "FailsafeXServer=" -msgstr "FailsafeXServer=" - -#: C/gdm.xml:2156(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 " -"<filename>XKeepsCrashing</filename> script is run." -msgstr "" -"Una línea de comandos X en caso de que no podamos iniciar el servidor X " -"normal. Debería ser probablemente alguna clase de script que ejecute un " -"servidor X apropiado a baja resolución que funcione siempre. Esto se intenta " -"antes de que se ejecute el script <filename>XKeepsCrashing</filename>." - -#: C/gdm.xml:2167(term) -msgid "FirstVT" -msgstr "FirstVT" - -#: C/gdm.xml:2169(synopsis) -#, no-wrap -msgid "FirstVT=7" -msgstr "FirstVT=7" - -#: C/gdm.xml:2170(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 <filename>VTAllocation</filename>." -msgstr "" -"En sistemas donde GDM soporta la reserva automática de TV (Terminales " -"virtuales), este es el primer tv que probar. Usualmente los inicios de " -"sesión en entrada de texto se ejecutan en los tvs más bajos. Vea además " -"<filename>VTAllocation</filename>." - -#: C/gdm.xml:2180(term) -msgid "FlexibleXServers" -msgstr "FlexibleXServers" - -#: C/gdm.xml:2182(synopsis) -#, no-wrap -msgid "FlexibleXServers=5" -msgstr "FlexibleXServers=5" - -#: C/gdm.xml:2183(para) -msgid "" -"The maximum number of allowed flexible displays. These are displays that can " -"be run using the <filename>/tmp/.gdm_socket</filename> socket connection. " -"This is used for both full flexible displays and for nested displays (refer " -"to the <filename>Xnest</filename> configuration option)." -msgstr "" -"El número máximo de pantallas flexibles permitidas. Estas son pantallas que " -"pueden ejecutarse usando la conexión socket <filename>/tmp/.gdm_socket</" -"filename>. Esto se usa tanto para pantallas flexibles como para pantallas " -"anidadas (referente a la opción de configuración de <filename>Xnest</" -"filename>)." - -#: C/gdm.xml:2195(term) -msgid "FlexiReapDelayMinutes" -msgstr "FlexiReapDelayMinutes" - -#: C/gdm.xml:2197(synopsis) -#, no-wrap -msgid "FlexiReapDelayMinutes=5" -msgstr "FlexiReapDelayMinutes=5" - -#: C/gdm.xml:2198(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 <filename>Xnest</filename> " -"configuration option). To turn off this behavior set this value to 0. This " -"was added in version 2.5.90.0." -msgstr "" -"Después de cuantos minutos de inactividad en la pantalla de entrada debería " -"desconectarse la pantalla flexible. Esto sólo tiene efecto antes de que un " -"usuario inicie sesión. Tampoco afecta a los servidores anidados (referente a " -"la opción de configuración de <filename>Xnest</filename>). Para desactivar " -"este comportamiento establezca este valor a 0. Esto se añadió en la versión " -"2.5.90.0." - -#: C/gdm.xml:2210(term) -msgid "Greeter" -msgstr "Greeter" - -#: C/gdm.xml:2212(synopsis) -#, no-wrap -msgid "Greeter=<bin>/gdmlogin" -msgstr "Greeter=<bin>/gdmlogin" - -#: C/gdm.xml:2213(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 <filename>RemoteGreeter</filename>" -msgstr "" -"Ruta completa al nombre del ejecutable del interfaz de entrada seguido de " -"los argumentos opcionales. Este es el interfaz de entrada usado para todas " -"las pantallas excepto para las pantallas XDMCP remotas. Vea además " -"<filename>RemoteGreeter</filename>" - -#: C/gdm.xml:2223(term) -msgid "Group" -msgstr "Group" - -#: C/gdm.xml:2225(synopsis) -#, no-wrap -msgid "Group=gdm" -msgstr "Group=gdm" - -#: C/gdm.xml:2226(para) -msgid "" -"The group name under which <command>gdmlogin</command>, <command>gdmgreeter</" -"command>, <command>gdmchooser</command> and the internal failsafe GTK+ " -"dialogs are run. Also see <filename>User</filename>. 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 <filename>ServAuthDir</filename> is owned by this group. " -"The ownership and permissions of <filename>ServAuthDir</filename> should be " -"<filename>root.gdm</filename> and 1770." -msgstr "" -"El nombre del grupo bajo el cual <command>gdmlogin</command>, " -"<command>gdmgreeter</command>, <command>gdmchooser</command> y los diálogos " -"GTK+ internos en caso de fallo se ejecutan. Vea ademas <filename>User</" -"filename>. Este usuario tendrá acceso a todos los archivos de autorización " -"X, y quizás a otros datos internos de GDM y por lo tanto no debería usarlo " -"nadie. El <filename>ServAuthDir</filename> es propiedad de este grupo. La " -"propiedad y permisos de <filename>ServAuthDir</filename> deberia ser " -"<filename>root.gdm</filename> y 1770." - -#: C/gdm.xml:2243(term) -msgid "GtkModulesList" -msgstr "GtkModulesList" - -#: C/gdm.xml:2245(synopsis) -#, no-wrap -msgid "GtkModulesList=module-1:module-2:..." -msgstr "GtkModulesList=module-1:module-2:..." - -#: C/gdm.xml:2246(para) -msgid "" -"A colon separated list of Gtk+ modules that <command>gdmgreeter</command> or " -"<command>gdmlogin</command> will be invoked with if <filename>AddGtkModules</" -"filename> is true. The format is the same as the standard Gtk+ module " -"interface." -msgstr "" -"Una lista separada por dos puntos de módulos GTK+ que <command>gdmgreeter</" -"command> o <command>gdmlogin</command> invocar´an si " -"<filename>AddGtkModules</filename> está a true. El formato es el mismo que " -"el interfaz Gtk+ estándar." - -#: C/gdm.xml:2257(term) -msgid "HaltCommand" -msgstr "HaltCommand" - -#: C/gdm.xml:2259(synopsis) -#, no-wrap -msgid "HaltCommand=<sbin>/shutdown -h now" -msgstr "HaltCommand=<sbin>/shutdown -h now" - -#: C/gdm.xml:2260(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 "" -"ruta completa y argumentos al comando que ejecutar cuando el usuario " -"selecciona «Apagar» desde el menú Acciones. Esto puede ser una lista " -"separada por \";\" de comandos a intentar. Si falta un valor, el comando de " -"apagado no estará disponible. Note que lo predeterminado para este valor no " -"está vacío, así que para desactivar «Apagar» debe establecerse a un valor " -"vacío." - -#: C/gdm.xml:2273(term) -msgid "KillInitClients" -msgstr "KillInitClients" - -#: C/gdm.xml:2275(synopsis) -#, no-wrap -msgid "KillInitClients=true" -msgstr "KillInitClients=true" - -#: C/gdm.xml:2276(para) -msgid "" -"Determines whether GDM should kill X clients started by the init scripts " -"when the user logs in." -msgstr "" -"Determina si GDM sebe matar los clientes X iniciados por los scripts de " -"inicio cuando el usuario inicia sesión." - -#: C/gdm.xml:2284(term) -msgid "LogDir" -msgstr "Directorio de registro" - -#: C/gdm.xml:2286(synopsis) -#, no-wrap -msgid "LogDir=<var>/log/gdm" -msgstr "LogDir=<var>/log/gdm" - -#: C/gdm.xml:2287(para) -msgid "" -"Directory containing the log files for the individual displays. By default " -"this is the same as the ServAuthDir." -msgstr "" -"Directorio conteniendo los archivos de sucesos para las pantallas " -"individuales. Por omisión éste es el mismo que el de ServAuthDir." - -#: C/gdm.xml:2295(term) -msgid "PreFetchProgram" -msgstr "PreFetchProgram" - -#: C/gdm.xml:2297(synopsis) -#, no-wrap -msgid "PreFetchProgram=command" -msgstr "PreFetchProgram=command" - -#: C/gdm.xml:2298(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 "" -"Programa que se ejecutará por el programa de entrada/interfaz de GDM cuando " -"se muestre la pantalla inicial. El propósito es proporcionar un gancho donde " -"los archivos que se usarán tras la entrada puedan precargarse para mejorar " -"la velocidad para el usuario. El programa se llamará sólo una vez, la " -"primera vez que se muestre la interfaz de entrada. El comando gdmprefetch " -"será usado. Esta utilidad cargará cualquier biblioteca pasada en la línea de " -"comandos, o si el argumento empieza por un carácter «@», procesará el " -"archivo asumiendo que es un archivo ASCII conteniendo una lista de " -"bibliotecas, una por línea, y cargará cada biblioteca en el archivo." - -#: C/gdm.xml:2314(term) -msgid "PostLoginScriptDir" -msgstr "PostLoginScriptDir" - -#: C/gdm.xml:2316(synopsis) -#, no-wrap -msgid "PostLoginScriptDir=<etc>/gdm/PostLogin" -msgstr "PostLoginScriptDir=<etc>/gdm/PostLogin" - -#: C/gdm.xml:2317(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 "" -"Directorio que contiene los scripts ejecutados justo después de que el " -"usuario inicie sesión, pero antes de que se realice ninguna configuración de " -"sesión. Vea la sección ``Los directorios de Scripts'' para más información." - -#: C/gdm.xml:2326(term) -msgid "PostSessionScriptDir" -msgstr "PostSessionScriptDir" - -#: C/gdm.xml:2328(synopsis) -#, no-wrap -msgid "PostSessionScriptDir=<etc>/gdm/PostSession" -msgstr "PostSessionScriptDir=<etc>/gdm/PostSession" - -#: C/gdm.xml:2329(para) -msgid "" -"Directory containing the scripts run after the user logs out. See the ``The " -"Script Directories'' section for more info." -msgstr "" -"Directorio conteniendo los scripts ejecutados después de que el usuario " -"cierre la sesión. Vea la sección ``Los directorios de Scripts'' para más " -"información." - -#: C/gdm.xml:2337(term) -msgid "PreSessionScriptDir" -msgstr "PreSessionScriptDir" - -#: C/gdm.xml:2339(synopsis) -#, no-wrap -msgid "PreSessionScriptDir=<etc>/gdm/PreSession" -msgstr "PreSessionScriptDir=<etc>/gdm/PreSession" - -#: C/gdm.xml:2340(para) -msgid "" -"Directory containing the scripts run before the user logs in. See the ``The " -"Script Directories'' section for more info." -msgstr "" -"Directorio que contiene los scripts ejecutados antes de que el usuario " -"inicie sesión. Vea la sección ``Los directorios de Scripts'' para más " -"información." - -#: C/gdm.xml:2348(term) C/gdm.xml:2350(synopsis) -msgid "RBACSystemCommandKeys" -msgstr "RBACSystemCommandKeys" - -#: C/gdm.xml:2351(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 <command>gdmflexiserver</command> commands. Valid " -"actions are HALT, REBOOT, SUSPEND, and CUSTOM_CMD. The greeter will only " -"display the command if the gdm user (<filename>User</filename> 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 <filename>AllowLogoutActions</filename> and " -"<filename>SystemCommandsInMenu</filename> configuration options." -msgstr "" - -#: C/gdm.xml:2375(term) -msgid "RebootCommand" -msgstr "RebootCommand" - -#: C/gdm.xml:2377(synopsis) -#, no-wrap -msgid "RebootCommand=<sbin>/shutdown -r now" -msgstr "RebootCommand=<sbin>/shutdown -r now" - -#: C/gdm.xml:2378(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 "" -"Ruta completa y argumentos opcionales para el comando que ejecutar cuando el " -"usuario selecciona Reiniciar desde el menú de Acciones. Esto puede ser una " -"lista separada por «;» de comandos que probar. Si falta, el comandos de " -"reinicio no está disponible. Note que lo predeterminado para este valor es " -"no vacío así que para desactivar el reinicio debe establecerlo " -"explícitamente a un valor vacío." - -#: C/gdm.xml:2390(term) -msgid "RemoteGreeter" -msgstr "RemoteGreeter" - -#: C/gdm.xml:2392(synopsis) -#, no-wrap -msgid "RemoteGreeter=<bin>/gdmlogin" -msgstr "RemoteGreeter=<bin>/gdmlogin" - -#: C/gdm.xml:2393(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 <filename>Greeter</filename> key." -msgstr "" -"La ruta completa y el nombre del ejecutable del interfaz de entrada seguida " -"de argumentos opcionales. Esto se usa para todas las sesiones remotas XDMCP. " -"Es útil tener el interfaz de entrada que menos recursos gráficos demande si " -"usa el Interfaz con temas para su interfaz principal. Vea además la clave " -"<filename>Greeter</filename>." - -#: C/gdm.xml:2404(term) -msgid "RootPath" -msgstr "RootPath" - -#: C/gdm.xml:2406(synopsis) -#, no-wrap -msgid "RootPath=defaultpath (value set by configure)" -msgstr "RootPath=defaultpath (valor establecido por configure)" - -#: C/gdm.xml:2407(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 <filename>/etc/default/login</filename> if " -"it contains \"SUROOT=<pathname>\". If the <filename>/etc/default/" -"login</filename> file exists, but contains no value for SUROOT, the value as " -"defined in the GDM configuration will be used." -msgstr "" -"Especifica la ruta que se establecerá en la sesión del root y los scripts " -"{Init,PostLogin,PreSession,PostSession} ejecutados por GDM. Este valor podrá " -"ser sobrepasado con el valor de <filename>/etc/default/login</filename> si " -"contiene \"SUROOT=<pathname>\". Si el archivo <filename>/etc/default/" -"login</filename> existe, pero no contiene ningún valor para SUROOT, el valor " -"tal como se define en la configuración de GDM será el que se use." - -#: C/gdm.xml:2421(term) -msgid "ServAuthDir" -msgstr "ServAuthDir" - -#: C/gdm.xml:2423(synopsis) -#, no-wrap -msgid "ServAuthDir=<var>/gdm" -msgstr "ServAuthDir=<var>/gdm" - -#: C/gdm.xml:2424(para) -msgid "" -"Directory containing the X authentication files for the individual displays. " -"Should be owned by <filename>root.gdm</filename> with permissions 1770, " -"where <filename>gdm</filename> is the GDM group as defined by the " -"<filename>Group</filename> option. That is should be owned by root, with " -"<filename>gdm</filename> 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 "" -"Directorio que contiene los archivos de autenticación X para las pantallas " -"individuales. Debería ser propiedad de <filename>root.gdm</filename> con los " -"permisos 1770, donde <filename>gdm</filename> es el grupo GDM tal como se " -"define por la opción <filename>Group</filename> Esto es que debería ser " -"propiedad de root, con el grupo <filename>gdm</filename> teniendo permisos " -"de escritura completos y el directorio debería estar con el bit de " -"persistencia activado y otros no deberían tener permiso para el directorio. " -"De esta manera el usuario de GDM no puede borrar archivos que pertenezcan a " -"root en ese directorio, mientras que aún puede escribir sus propios archivos " -"allí. GDM intentará cambiar los permisos por el usuario cuando se ejecute " -"por primera vez si los permisos no son los de arriba. Este directorio " -"también se usa para otros archivos privados que el demonio necesite " -"almacenar Otros usuario no deberían tener ninguna forma de entrar a este " -"directorio y leer o cambiar su contenido. Cualquiera que pueda leer este " -"directorio puede conectarse a cualquier pantalla de este equipo." - -#: C/gdm.xml:2446(term) -msgid "SessionDesktopDir" -msgstr "SessionDesktopDir" - -#: C/gdm.xml:2448(synopsis) -#, no-wrap -msgid "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" -msgstr "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" - -#: C/gdm.xml:2449(para) -msgid "" -"Directory containing the <filename>.desktop</filename> 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 "" -"Directorio que contiene los archivos <filename>.desktop</filename> que son " -"las sesiones disponibles en el sistema. Desde 2.4.4.2 esto se trata como una " -"variable tipo PATH y se usa el primar archivo encontrado." - -#: C/gdm.xml:2459(term) -msgid "SoundProgram" -msgstr "SoundProgram" - -#: C/gdm.xml:2461(filename) -msgid "<bin>/play" -msgstr "<bin>/play" - -#: C/gdm.xml:2461(filename) -msgid "<bin>/audioplay" -msgstr "<bin>/audioplay" - -#: C/gdm.xml:2461(synopsis) -#, no-wrap -msgid "SoundProgram=<placeholder-1/> (or <placeholder-2/> on Solaris)" -msgstr "SoundProgram=<placeholder-1/> (o <placeholder-2/> en Solaris)" - -#: C/gdm.xml:2462(para) -msgid "" -"Application to use when playing a sound. Currently used for playing the " -"login sound, see the <filename>SoundOnLoginFile</filename> key. Supported " -"since 2.5.90.0." -msgstr "" -"La aplicación que se usará al reproducir un sonido. Actualmente se usa para " -"reproducir el sonido de inicio de sesión, vea la clave " -"<filename>SoundOnLoginFile</filename>. Soportado desde 2.5.90.0." - -#: C/gdm.xml:2472(term) -msgid "StandardXServer" -msgstr "StandardXServer" - -#: C/gdm.xml:2474(synopsis) -#, no-wrap -msgid "StandardXServer=/dir/to/X (value assigned by configuration file)" -msgstr "StandardXServer=/dir/to/X (valor asignado por el archivo de configuración)" - -#: C/gdm.xml:2475(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 "" -"Ruta completa y argumentos al comando del servidor X estándar. Esto de usa " -"cuando gdm no puede encontrar ninguna otra definición, y se usa como valor " -"predeterminado y valor para usar en caso de fallo en varios lugares. Esto " -"debería ser capaz de ejecutar alguna clase de servidor X." - -#: C/gdm.xml:2486(term) -msgid "SuspendCommand" -msgstr "SuspendCommand" - -#: C/gdm.xml:2488(synopsis) -#, no-wrap -msgid "SuspendCommand=" -msgstr "SuspendCommand=" - -#: C/gdm.xml:2489(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 "" -"Ruta completa y argumentos al comando que se ejecutará cuando el usuario " -"seleccione Suspender desde el menú Acciones. Si estuviera vacío no habrá ese " -"elemento del menú. Note que lo predeterminado para este valor es no vacío, " -"así que para desactivar la suspensión debe establecer esto explícitamente a " -"un valor vacío." - -#: C/gdm.xml:2500(term) -msgid "SystemCommandsInMenu" -msgstr "SystemCommandsInMenu" - -#: C/gdm.xml:2502(synopsis) -#, no-wrap -msgid "SuspendCommand=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD" -msgstr "SuspendCommand=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD" - -#: C/gdm.xml:2503(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 <command>gdmflexiserver</" -"command> 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 <filename>AllowLogoutActions</filename> and " -"<filename>RBACSystemCommandKeys</filename> configuration options." -msgstr "" - -#: C/gdm.xml:2524(term) -msgid "TimedLoginEnable" -msgstr "TimedLoginEnable" - -#: C/gdm.xml:2526(synopsis) -#, no-wrap -msgid "TimedLoginEnable=false" -msgstr "TimedLoginEnable=false" - -#: C/gdm.xml:2527(para) -msgid "" -"If the user given in <filename>TimedLogin</filename> should be logged in " -"after a number of seconds (set with <filename>TimedLoginDelay</filename>) of " -"inactivity on the login screen. This is useful for public access terminals " -"or perhaps even home use. If the user uses the keyboard or browses the " -"menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or " -"30 seconds, whichever is higher. If the user does not enter a username but " -"just hits the ENTER key while the login program is requesting the username, " -"then GDM will assume the user wants to login immediately as the timed user. " -"Note that no password will be asked for this user so you should be careful, " -"although if using PAM it can be configured to require password entry before " -"allowing login." -msgstr "" -"Si el usuario dado en <filename>TimedLogin</filename> debería abrir una " -"sesión después del número de segundos (establecidos en " -"<filename>TimedLoginDelay</filename>) de inactividad en la pantalla de " -"entrada. Esto es útil para terminales de acceso público o quizás incluso " -"para uso doméstico. Si el usuario usa el teclado o abre los menús, el " -"temporizador se restablecerá al valor <filename>TimedLoginDelay</filename> " -"o 30 segundos, lo que sea mayor. si el usuario no introduce un nombre de " -"usuario sino que tan sólo pulsa la tecla INTRO mientras que el programa de " -"entrada está pidiendo el nombre del usuario, entonces GDM asume que el " -"usuario quiere entrar inmediatamente como el usuario temporizado. Note que " -"si no se pedirá ninguna contraseña para este usuario así que debería ser " -"cuidadoso, aunque si usa PAM puede configurarlo para que requiera que " -"introduzca una contraseña antes de permitir la entrada." - -#: C/gdm.xml:2547(term) -msgid "TimedLogin" -msgstr "TimedLogin" - -#: C/gdm.xml:2549(synopsis) -#, no-wrap -msgid "TimedLogin=" -msgstr "TimedLogin=" - -#: C/gdm.xml:2550(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 <filename>AutomaticLogin</" -"filename> are supported. The same control chars and piping to a application " -"are supported." -msgstr "" -"Este es el usuario que debería iniciar sesión tras un número de segundos de " -"inactividad. Éste nunca puede ser «root» y gdm rechazará iniciar como root " -"de esta manera. Se soportan las mismas características que para " -"<filename>AutomaticLogin</filename>. Se soportan los mismos caracteres de " -"control y redirección a una aplicación." - -#: C/gdm.xml:2562(term) -msgid "TimedLoginDelay" -msgstr "TimedLoginDelay" - -#: C/gdm.xml:2564(synopsis) -#, no-wrap -msgid "TimedLoginDelay=30" -msgstr "TimedLoginDelay=30" - -#: C/gdm.xml:2565(para) -msgid "" -"Delay in seconds before the <filename>TimedLogin</filename> user will be " -"logged in. It must be greater then or equal to 10." -msgstr "" -"Retardo en segundos antes de que el usuario <filename>TimedLogin</filename> " -"entre en la sesión. Debe ser mayor o igual a 10." - -#: C/gdm.xml:2573(term) -msgid "User" -msgstr "User" - -#: C/gdm.xml:2575(synopsis) -#, no-wrap -msgid "User=gdm" -msgstr "User=gdm" - -#: C/gdm.xml:2576(para) -msgid "" -"The username under which <command>gdmlogin</command>, <command>gdmgreeter</" -"command>, <command>gdmchooser</command> and the internal failsafe GTK+ " -"dialogs are run. Also see <filename>Group</filename>. 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 "" -"El usuario bajo el cual <command>gdmlogin</command>, <command>gdmgreeter</" -"command>, <command>gdmchooser</command> y los diálos GTK+ internos a prueba " -"de fallos se ejecutan. Vea además <filename>Group</filename>. Este usuario " -"tendrá acceso a todos los archivos de autorización X, y quizás a otros datos " -"internos de GDM y por lo tanto no debería ser un usuario como nobody, sino " -"un usuario dedicado." - -#: C/gdm.xml:2590(term) -msgid "UserAuthDir" -msgstr "UserAuthDir" - -#: C/gdm.xml:2592(synopsis) -#, no-wrap -msgid "UserAuthDir=" -msgstr "UserAuthDir=" - -#: C/gdm.xml:2593(para) -msgid "" -"The directory where user's <filename>.Xauthority</filename> 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: <filename>~/authdir/</" -"filename>." -msgstr "" -"El directorio donde el archivo <filename>.Xauthority</filename> debería " -"guardarse. Cuando no se especifique nada se usará el directorio personal del " -"usuario. Éste es a lo que se expande la virgulilla así que puede " -"establecerlo a cosas como: <filename>~/authdir/</filename>." - -#: C/gdm.xml:2600(para) -msgid "" -"If you do not use the tilde expansion, then the filename created will be " -"random, like in <filename>UserAuthFBDir</filename>. This way many users can " -"have the same authentication directory. For example you might want to set " -"this to <filename>/tmp</filename> 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 <filename>/tmp</" -"filename> directory." -msgstr "" -"Si no usa la expansión de la virgulilla, entonces el nombre de archivo " -"creado será aleatorio, como en <filename>UserAuthFBDir</filename>. De esta " -"manera muchos usuarios pueden tener el mismo directorio de autenticación. " -"Por ejemplo quizá quiera establecer esto a <filename>/tmp</filename> cuando " -"tenga el directorio de personal en NFS, debido a que no desea que los " -"archivos de cookies vayan por el cable. Los usuarios deberían tener " -"privilegios de escritura en este directorio, y este directorio debería tener " -"el bit de persistencia activado y todo lo demás, igual que el directorio " -"<filename>/tmp</filename>." - -#: C/gdm.xml:2613(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 <filename>NeverPlaceCookiesOnNFS</filename> in the " -"<filename>[security]</filename> section to false." -msgstr "" -"Normalmente si este es el directorio personal del usuario GDM aún se negará " -"a poner cookies allí si piensa que es NFS (probando root-squashing). Esto " -"puede cambiarse estableciendo <filename>NeverPlaceCookiesOnNFS</filename> a " -"«false» en la sección <filename>[security]</filename>" - -#: C/gdm.xml:2624(term) -msgid "UserAuthFBDir" -msgstr "UserAuthFBDir" - -#: C/gdm.xml:2626(synopsis) -#, no-wrap -msgid "UserAuthFBDir=/tmp" -msgstr "UserAuthFBDir=/tmp" - -#: C/gdm.xml:2627(para) -msgid "" -"If GDM fails to update the user's <filename>.Xauthority</filename> file a " -"fallback cookie is created in this directory." -msgstr "" -"Si GDM falla al actualizar el archivo <filename>.Xauthority</filename> del " -"usuario se crea una cookie para casos de fallo en este directorio." - -#: C/gdm.xml:2636(term) -msgid "UserAuthFile" -msgstr "UserAuthFile" - -#: C/gdm.xml:2638(synopsis) -#, no-wrap -msgid "UserAuthFile=.Xauthority" -msgstr "UserAuthFile=.Xauthority" - -#: C/gdm.xml:2639(para) -msgid "Name of the file used for storing user cookies." -msgstr "Nombre del archivo usado para almacenar cookies del usuario." - -#: C/gdm.xml:2646(term) -msgid "VTAllocation" -msgstr "VTAllocation" - -#: C/gdm.xml:2648(synopsis) -#, no-wrap -msgid "VTAllocation=true" -msgstr "VTAllocation=true" - -#: C/gdm.xml:2649(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 " -"<filename>FirstVT</filename>." -msgstr "" -"En sistemas donde GDM soporta reserva de TV (terminales virtuales) " -"automáticos (actualmente Linux y FreeBSD sólo), puede hacer que GDM agregue " -"automáticamente el argumento del tv al ejecutable del servidor X. De esta " -"manera las carreras que surjan de cada servidor X gestionando su propia " -"reserva de tv se pueden evitar. Vea además <filename>FirstVT</filename>." - -#: C/gdm.xml:2661(term) -msgid "XKeepsCrashing" -msgstr "XKeepsCrashing" - -#: C/gdm.xml:2663(synopsis) -#, no-wrap -msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" -msgstr "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" - -#: C/gdm.xml:2664(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 " -"<filename>XKeepsCrashing</filename> 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 "" -"Un script para ejecutar en caso de que X no logre iniciarse. Esto es para " -"ejecutar una configuración de X o cualquier otra cosa para hacer que la " -"configuración de X funcione. Vea el script que vino con la distribución para " -"un ejemplo. El script <filename>XKeepsCrashing</filename> se prueba en Red " -"Hat, pero podría funcionar en cualquier otro lugar. Su integrador del " -"sistema debería asegurarse de que este script está actualizado para su " -"sistema particular." - -#: C/gdm.xml:2673(para) -msgid "" -"In case <filename>FailsafeXServer</filename> is setup, that will be tried " -"first. and this only used as a backup if even that X server keeps crashing." -msgstr "" -"En caso de que se configure <filename>FailsafeXServer</filename>, ése se " -"intentará primero, y éste sólo se usará como respaldo si incluso ese " -"servidor X sigue colgándose." - -#: C/gdm.xml:2682(term) -msgid "Xnest" -msgstr "Xnest" - -#: C/gdm.xml:2684(synopsis) -#, no-wrap -msgid "Xnest=<bin>/X11/Xephyr -audit 0" -msgstr "Xnest=<bin>/X11/Xephyr -audit 0" - -#: C/gdm.xml:2685(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:2699(term) -msgid "XnestUnscaledFontPath" -msgstr "XnestUnscaledFontPath" - -#: C/gdm.xml:2701(synopsis) -#, no-wrap -msgid "XnestUnscaledFontPath=true" -msgstr "XnestUnscaledFontPath=true" - -#: C/gdm.xml:2702(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 <filename>Xnest</filename> configuration option." -msgstr "" - -#: C/gdm.xml:2716(title) -msgid "Security Options" -msgstr "Opciones de seguridad" - -#: C/gdm.xml:2719(title) -msgid "[security]" -msgstr "[security]" - -#: C/gdm.xml:2722(term) -msgid "AllowRoot" -msgstr "AllowRoot" - -#: C/gdm.xml:2724(synopsis) -#, no-wrap -msgid "AllowRoot=true" -msgstr "AllowRoot=true" - -#: C/gdm.xml:2725(para) -msgid "" -"Allow root (privileged user) to log in through GDM. Set this to false if you " -"want to disallow such logins." -msgstr "" -"Permitir a root (usuario privilegiado) entrar a través de GDM. Establezca " -"esto a falso si no quiere permitir dichas entradas." - -#: C/gdm.xml:2729(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 "" -"En sistemas que soportan PAM, este parámetro no es tan útil ya que puede " -"usar PAM para hacer lo mismo, y de hecho para hacer más. Sin embargo todavía " -"se sigue, así que probablemente debería dejarlo a TRUE para los sistemas PAM." - -#: C/gdm.xml:2739(term) -msgid "AllowRemoteRoot" -msgstr "AllowRemoteRoot" - -#: C/gdm.xml:2741(synopsis) -#, no-wrap -msgid "AllowRemoteRoot=false" -msgstr "AllowRemoteRoot=false" - -#: C/gdm.xml:2742(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 "" -"Permitir al root (usuario privilegiado) entrar remotamente a través de GDM. " -"Este valor debería establecerse a true para permitir dichas entradas. Las " -"entradas remotas son cualquier entrada que provengan a través de XDMCP." - -#: C/gdm.xml:2747(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 "" -"En sistemas que soporten PAM, este parámetro no es tan útil debido a que " -"puede usar PAM para hacer lo mismo, e incluso más." - -#: C/gdm.xml:2752(para) -msgid "" -"This value will be overridden and set to false if the <filename>/etc/default/" -"login</filename> file exists and contains \"CONSOLE=/dev/login\", and set to " -"true if the <filename>/etc/default/login</filename> file exists and contains " -"any other value or no value for CONSOLE." -msgstr "" -"Este valor será sobrepasado y establecido a false si existe el archivo " -"<filename>/etc/default/login</filename> y contiene \"CONSOLE=/dev/login\", " -"y será establecido a true si el archivo <filename>/etc/default/login</" -"filename> existe y contine cualquier otro valor o ningún valor para CONSOLE." - -#: C/gdm.xml:2763(term) -msgid "AllowRemoteAutoLogin" -msgstr "AllowRemoteAutoLogin" - -#: C/gdm.xml:2765(synopsis) -#, no-wrap -msgid "AllowRemoteAutoLogin=false" -msgstr "AllowRemoteAutoLogin=false" - -#: C/gdm.xml:2766(para) -msgid "" -"Allow the timed login feature to work for remote displays. In other words, " -"remote connections via XDMCP will be allowed to log into the \"TimedLogin\" " -"user after the delay defined by <filename>TimedLoginDelay</filename>." -msgstr "" -"Permitir que la entrada temporizada funcione de forma remota. Esto es, que a " -"las conexiones remotas a través de XDMCP se les permita entrar con el " -"usuario «TimedLogin» después del retardo definido en " -"<filename>TimedLoginDelay</filename>." - -#: C/gdm.xml:2772(para) -msgid "Note that this can make a system quite insecure, and thus is off by default." -msgstr "" -"Note que esto puede hacer un sistema muy inseguro, y por eso está " -"desactivado por omisión." - -#: C/gdm.xml:2780(term) -msgid "CheckDirOwner" -msgstr "CheckDirOwner" - -#: C/gdm.xml:2782(synopsis) -#, no-wrap -msgid "CheckDirOwner=true" -msgstr "CheckDirOwner=true" - -#: C/gdm.xml:2783(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 <filename>RelaxPermissions</filename> 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 "" -"Por omisión GDM comprueba el propietario de los directorios personales antes " -"de escribir en ellos, esto previene problemas de seguridad en caso de una " -"configuración inadecuada. Sin embargo en algunos lugares los directorios " -"personales serán propiedad de un usuario diferente y en este caso es " -"necesario activar esta opción. Además tendrá que activar la clave " -"<filename>RelaxPermissions</filename> a almenos el valor 1 debido a que en " -"este escenario los directorios personales serán escribibles por el grupo. " -"Soportado desde 2.6.0.4." - -#: C/gdm.xml:2797(term) -msgid "SupportAutomount" -msgstr "SupportAutomount" - -#: C/gdm.xml:2799(synopsis) -#, no-wrap -msgid "SupportAutomount=false" -msgstr "SupportAutomount=false" - -#: C/gdm.xml:2800(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 "" -"Por omisión GDM comprueba la propiedad de los directorios personales antes " -"de escribir en ellos, esto previene problemas de seguridad en caso de una " -"configuración inadecuada. Sin embargo cuando los directorios personales " -"están gestionados por automounter, a menudo no están montados antes de " -"acceder a ellos. Esta opción soluciona algunas peculiaridades del " -"automontador de Linux." - -#: C/gdm.xml:2812(term) -msgid "DisallowTCP" -msgstr "DisallowTCP" - -#: C/gdm.xml:2814(synopsis) -#, no-wrap -msgid "DisallowTCP=true" -msgstr "DisallowTCP=true" - -#: C/gdm.xml:2815(para) -msgid "" -"If true, then always append <filename>-nolisten tcp</filename> to the " -"command line when starting attached X servers, thus disallowing TCP " -"connection. This is a more secure configuration if not using remote " -"connections." -msgstr "" -"Si es «true», entonces añadir siempre <filename>-nolisten tcp</filename> a " -"la línea de comandos de los servidores X locales, para de esta forma " -"deshabilitar las conexiones TCP. Esta configuración es más segura si no se " -"van a usar conexiones remotas." - -#: C/gdm.xml:2825(term) -msgid "NeverPlaceCookiesOnNFS" -msgstr "NeverPlaceCookiesOnNFS" - -#: C/gdm.xml:2827(synopsis) -#, no-wrap -msgid "NeverPlaceCookiesOnNFS=true" -msgstr "NeverPlaceCookiesOnNFS=true" - -#: C/gdm.xml:2828(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 "" -"Normalmente si esto es <literal>true</literal (lo cual es por omisión), GDM " -"no colocará cookies en los directorios personales de los usuarios si estos " -"directorios se encuentran en un volumen remoto NFS. Bien, GDM considerará " -"cualquier sistema con root-squashing un sistema NFS. Algunas veces sin " -"embargo el sistema de archivos remoto puede tener root squashing y ser " -"seguro (quizás usando encriptado). En este caso establezca esto a " -"<literal>false</literal>. Note que esta opción apareció en la versión " -"2.4.4.4 y se ignora en las versiones anteriores." - -#: C/gdm.xml:2842(term) -msgid "PasswordRequired" -msgstr "PasswordRequired" - -#: C/gdm.xml:2844(synopsis) -#, no-wrap -msgid "PasswordRequired=false" -msgstr "PasswordRequired=false" - -#: C/gdm.xml:2845(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 <filename>/etc/default/login</filename> if it " -"contains \"PASSREQ=[YES|NO]\". If the <filename>/etc/default/login</" -"filename> file exists, but contains no value for PASSREQ, the value as " -"defined in the GDM configuration will be used." -msgstr "" -"Si es <literal>true</literal>, esto hará que se pase " -"PAM_DISALLOW_NULL_AUTHTOK como una opción a pam_authenticate y " -"pam_acct_mgmt, no permitiendo una contraseña vacía. Este ajuste sólo tendrá " -"efecto si GDM está usando PAM. Este valor no se tendrá en cuanta si " -"<filename>/etc/default/login</filename> contiene \"PASSREQ=[YES|NO]\". Si " -"existe el archivo <filename>/etc/default/login</filename> pero no contiene " -"ningún valor para PASSREQ, se usará el valor tal como se defina en la " -"configuración de GDM." - -#: C/gdm.xml:2861(term) -msgid "RelaxPermissions" -msgstr "RelaxPermissions" - -#: C/gdm.xml:2863(synopsis) -#, no-wrap -msgid "RelaxPermissions=0" -msgstr "RelaxPermissions=0" - -#: C/gdm.xml:2864(para) -msgid "" -"By default GDM ignores files and directories writable to other users than " -"the owner." -msgstr "" -"Por omisión GDM ignora los archivos y directorios escribibles para otros " -"usuarios que no sean el propietario." - -#: C/gdm.xml:2869(para) -msgid "" -"Changing the value of RelaxPermissions makes it possible to alter this " -"behavior:" -msgstr "" -"Cambiar el valor de RelaxPermissions hace posible alterar este " -"comportamiento:" - -#: C/gdm.xml:2874(para) -msgid "0 - Paranoia option. Only accepts user owned files and directories." -msgstr "" -"0: Opción paranoia. Sólo acepta archivos y directorios que pertenezcan al " -"usuario." - -#: C/gdm.xml:2878(para) -msgid "1 - Allow group writable files and directories." -msgstr "1: Permitir archivos y directorios escribibles por el grupo." - -#: C/gdm.xml:2881(para) -msgid "2 - Allow world writable files and directories." -msgstr "2: Permitir archivos y directorios escribibles por todo el mundo." - -#: C/gdm.xml:2888(term) -msgid "RetryDelay" -msgstr "RetryDelay" - -#: C/gdm.xml:2890(synopsis) -#, no-wrap -msgid "RetryDelay=1" -msgstr "RetryDelay=1" - -#: C/gdm.xml:2891(para) -msgid "" -"The number of seconds GDM should wait before reactivating the entry field " -"after a failed login." -msgstr "" -"El número de segundos que GDM debería esperar antes de reactivar el campo de " -"la entrada después de una entrada fallida." - -#: C/gdm.xml:2899(term) -msgid "UserMaxFile" -msgstr "UserMaxFile" - -#: C/gdm.xml:2901(synopsis) -#, no-wrap -msgid "UserMaxFile=65536" -msgstr "UserMaxFile=65536" - -#: C/gdm.xml:2902(para) -msgid "" -"GDM will refuse to read/write files bigger than this number (specified in " -"bytes)." -msgstr "" -"GDM rehusará a leer/escribir archivos más grandes que este número " -"(especificado en bytes)." - -#: C/gdm.xml:2907(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 " -"<filename>RelaxPermissions</filename> option for more info." -msgstr "" -"Además de la comprobación del tamaño del archivo GDM es extremadamente " -"quisquilloso respecto a acceder a archivos en directorios de usuario. No " -"seguirá enlaces simbólicos y puede rehusar opcionalmente a leer archivos y " -"directorios escribibles por otros usuarios distintos del propietario. Vea la " -"opción <filename>RelaxPermissions</filename> para más información." - -#: C/gdm.xml:2917(term) -msgid "UtmpLineAttached" -msgstr "UtmpLineAttached" - -#: C/gdm.xml:2919(synopsis) -#, no-wrap -msgid "UtmpLineAttached=/dev/console (or /dev/dtlocal on Solaris)" -msgstr "UtmpLineAttached=/dev/console (o /dev/dtlocal en Solaris)" - -#: C/gdm.xml:2920(para) -msgid "" -"When doing Utmp processing for attached displays, GDM sets the ut_line to " -"the device associated with the Virtual Terminal (VT) if it is being used. " -"Otherwise, it will use the value specified with the display in the <filename>" -"[servers]</filename> section if a value is provided. If not, then the " -"default value specified in UtmpLineAttached is used for attached displays. " -"The value can contain \"%d\" which is translated to the DISPLAY value or \"%h" -"\" which is translated to the hostname. This value must begin with " -"<filename>/dev/</filename>." -msgstr "" - -#: C/gdm.xml:2935(term) -msgid "UtmpLineRemote" -msgstr "UtmpLineRemote" - -#: C/gdm.xml:2937(synopsis) -#, no-wrap -msgid "UtmpLineRemote= (or /dev/dtremote on Solaris)" -msgstr "UtmpLineRemote= (o /dev/dtremote en Solaris)" - -#: C/gdm.xml:2938(para) -msgid "" -"When doing Utmp processing, GDM sets the ut_line to this value for remote " -"displays. The value can contain \"%d\" which is translated to the DISPLAY " -"value or \"%h\" which is translated to the hostname. This value must begin " -"with <filename>/dev/</filename>." -msgstr "" - -#: C/gdm.xml:2948(term) -msgid "UtmpPseudoDevice" -msgstr "UtmpPseudoDevice" - -#: C/gdm.xml:2950(synopsis) -#, no-wrap -msgid "PseudoDevice=false (or true on Solaris)" -msgstr "PseudoDevice=false (o «true» en Solaris)" - -#: C/gdm.xml:2951(para) -msgid "" -"If the device associated with a display does not exist, then GDM will create " -"a symlink to <filename>/dev/null</filename>, or touch it if it is a symlink " -"to <filename>/dev/null</filename>. Some programs such as <command>last</" -"command>, <command>finger</command>, or <command>who</command> access the " -"utmp database and may assume that the device points to an actual file. " -"Creating such symlinks ensures that such programs work properly." -msgstr "" - -#: C/gdm.xml:2967(title) -msgid "XDCMP Support" -msgstr "Soporte XDMCP" - -#: C/gdm.xml:2970(title) -msgid "[xdmcp]" -msgstr "[xdmcp]" - -#: C/gdm.xml:2973(term) -msgid "DisplaysPerHost" -msgstr "DisplaysPerHost" - -#: C/gdm.xml:2975(synopsis) -#, no-wrap -msgid "DisplaysPerHost=1" -msgstr "DisplaysPerHost=1" - -#: C/gdm.xml:2976(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 " -"<filename>DisplaysPerHost</filename> value accordingly." -msgstr "" -"Para impedir que los atacantes llenen la cola de pendientes, GDM sólo " -"permite una conexión para cada equipo remoto. Si quiere proporcionar " -"servicios de pantalla a equipos con más de un monitor, debería incrementar " -"el valor <filename>DisplaysPerHost</filename>." - -#: C/gdm.xml:2984(para) -msgid "" -"Note that the number of attached DISPLAYS allowed is not limited. Only " -"remote connections via XDMCP are limited by this configuration option." -msgstr "" -"Note que el número de pantallas locales permitidas no está limitado. Sólolas " -"conexiones remotas a través de XDMCP están limitadas por esta opción de la " -"configuración." - -#: C/gdm.xml:2993(term) C/gdm.xml:4239(term) -msgid "Enable" -msgstr "Enable" - -#: C/gdm.xml:2995(synopsis) C/gdm.xml:4241(synopsis) -#, no-wrap -msgid "Enable=false" -msgstr "Enable=false" - -#: C/gdm.xml:2996(para) -msgid "" -"Setting this to true enables XDMCP support allowing remote displays/X " -"terminals to be managed by GDM." -msgstr "" -"Establecer esto a true activa el soporte XDMCP permitiento que las pantallas " -"X remotas o los terminales X se gestiones por medio de GDM." - -#: C/gdm.xml:3001(para) -msgid "" -"<filename>gdm</filename> listens for requests on UDP port 177. See the Port " -"option for more information." -msgstr "" -"<filename>gdm</filename> escucha peticiones en el puerto UDP 177. Vea la " -"opción Puerto para más información." - -#: C/gdm.xml:3006(para) -msgid "" -"If GDM is compiled to support it, access from remote displays can be " -"controlled using the TCP Wrappers library. The service name is " -"<filename>gdm</filename>" -msgstr "" -"Si GDM está compilado para soportarlo, el acceso desde las pantallas remotas " -"se puede controlar usando la biblioteca TCPWrappers. El nombre del servicio " -"es <filename>gdm</filename>" - -#: C/gdm.xml:3012(para) -msgid "" -"You should add <screen>\n" -"gdm:.my.domain\n" -"</screen> to your <filename><etc>/hosts.allow</filename>, depending on " -"your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:" -"hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" -"Debería añadir <screen>gdm:.mi.dominio</screen> a su <filename><etc>/" -"hosts.allow</filename>, dependiendo de su configuración de TCP Wrappers. Vea " -"la página del manual <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow" -"(5)</ulink> para más detalles." - -#: C/gdm.xml:3023(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 "" -"Note que XDMCP no es un protocolo particularmente seguro y que es una buena " -"idea bloquear el puerto UDP 177 en su cortafuegos a no ser que realmente lo " -"necesite." - -#: C/gdm.xml:3032(term) -msgid "EnableProxy" -msgstr "EnableProxy" - -#: C/gdm.xml:3034(synopsis) -#, no-wrap -msgid "EnableProxy=false" -msgstr "EnableProxy=false" - -#: C/gdm.xml:3035(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 "" -"Estableciendo esto a true se activa el soporte para ejecutar sesiones XDMCP " -"en un servidor proxy local de X. De esta forma se puede mejorar el " -"rendimiento de las sesiones XDMCP, especialmente en redes de alta latencia, " -"debido a que muchas opraciones del protocolo X se pueden completar sin ir " -"por la red." - -#: C/gdm.xml:3042(para) -msgid "" -"Note, however, that this mode will significantly increase the burden on the " -"machine hosting the XDMCP sessions" -msgstr "" -"Note, sin embargo que este modo incrementará significativamente la carga en " -"la máquina que hospede las sesiones XDMCP" - -#: C/gdm.xml:3046(para) -msgid "" -"See the <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</" -"filename> options for further details on how to configure support for this " -"feature." -msgstr "" -"Vea las opciones <filename>FlexiProxy</filename> y " -"<filename>FlexiProxyDisconnect</filename> para más detalles acerca de cómo " -"configurar el soporte para esta característica." - -#: C/gdm.xml:3055(term) -msgid "HonorIndirect" -msgstr "HonorIndirect" - -#: C/gdm.xml:3057(synopsis) -#, no-wrap -msgid "HonorIndirect=true" -msgstr "HonorIndirect=true" - -#: C/gdm.xml:3058(para) -msgid "" -"Enables XDMCP INDIRECT choosing (i.e. remote execution of " -"<filename>gdmchooser</filename>) for X-terminals which don't supply their " -"own display browser." -msgstr "" -"Activa la selección XDMCP INDIRECT (ejecución remota de " -"<filename>gdmchooser</filename>) para terminales X que no suministran su " -"proprio explorador de pantallas." - -#: C/gdm.xml:3067(term) -msgid "MaxPending" -msgstr "MaxPending" - -#: C/gdm.xml:3069(synopsis) -#, no-wrap -msgid "MaxPending=4" -msgstr "MaxPending=4" - -#: C/gdm.xml:3070(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 "" -"Para evitar ataques por denegación de servicio, GDM tiene una cola de tamaño " -"fijo de conexiones pendientes. Sólo pueden iniciarse a la vez MaxPending " -"pantallas." - -#: C/gdm.xml:3076(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 "" -"Note que este parámetro *no* liminta el número de pantallas remotas que se " -"puedan gestionar. Sólo limita el número de pantallas iniciando una conexión " -"simultáneamente." - -#: C/gdm.xml:3085(term) -msgid "MaxPendingIndirect" -msgstr "MaxPendingIndirect" - -#: C/gdm.xml:3087(synopsis) -#, no-wrap -msgid "MaxPendingIndirect=4" -msgstr "MaxPendingIndirect=4" - -#: C/gdm.xml:3088(para) -msgid "" -"GDM will only provide <filename>MaxPendingIndirect</filename> displays with " -"host choosers simultaneously. If more queries from different hosts come in, " -"the oldest ones will be forgotten." -msgstr "" -"GDM sólo proporciona <filename>MaxPendingIndirect</filename> pantallas con " -"selectores de host simultáneamente. Si entran más peticiones de diferentes " -"hosts, las más antiguas se descartarán." - -#: C/gdm.xml:3098(term) -msgid "MaxSessions" -msgstr "MaxSessions" - -#: C/gdm.xml:3100(synopsis) -#, no-wrap -msgid "MaxSessions=16" -msgstr "MaxSessions=16" - -#: C/gdm.xml:3101(para) -msgid "" -"Determines the maximum number of remote display connections which will be " -"managed simultaneously. I.e. the total number of remote displays that can " -"use your host." -msgstr "" -"Determina el número máximo de conexiones de pantallas remotas que serán " -"gestionadas simultáneamente. Ej: el número total de pantallas remotas que " -"puede usar su host." - -#: C/gdm.xml:3110(term) -msgid "MaxWait" -msgstr "MaxWait" - -#: C/gdm.xml:3112(synopsis) -#, no-wrap -msgid "MaxWait=30" -msgstr "MaxWait=30" - -#: C/gdm.xml:3113(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 "" -"Cuando GDM esté preparado para gestionar una pantalla se envía un paquete " -"ACCEPT a ella conteniendo un id único de sesión que será usado en las " -"conversaciones XDMCP futuras." - -#: C/gdm.xml:3119(para) -msgid "" -"GDM will then place the session id in the pending queue waiting for the " -"display to respond with a MANAGE request." -msgstr "" -"GDM entonces colocará el id de sesión en la cola de pendientes esperando a " -"que la pantalla responda con una petición MANAGE." - -#: C/gdm.xml:3124(para) -msgid "" -"If no response is received within MaxWait seconds, GDM will declare the " -"display dead and erase it from the pending queue freeing up the slot for " -"other displays." -msgstr "" -"Si no se recibe ninguna respuesta dentro de MaxWait segundos, GDM declarará " -"la pantalla muerta y la borrará de la cola pendiente liberando el espacio " -"para otras pantallas." - -#: C/gdm.xml:3133(term) -msgid "MaxWaitIndirect" -msgstr "MaxWaitIndirect" - -#: C/gdm.xml:3135(synopsis) -#, no-wrap -msgid "MaxWaitIndirect=30" -msgstr "MaxWaitIndirect=30" - -#: C/gdm.xml:3136(para) -msgid "" -"The MaxWaitIndirect parameter determines the maximum number of seconds " -"between the time where a user chooses a host and the subsequent indirect " -"query where the user is connected to the host. When the timeout is exceeded, " -"the information about the chosen host is forgotten and the indirect slot " -"freed up for other displays. The information may be forgotten earlier if " -"there are more hosts trying to send indirect queries then " -"<filename>MaxPendingIndirect</filename>." -msgstr "" -"El parámetro MaxWaitIndirect determina el número máximo de segundos entre el " -"tiempo donde un usuario elije un host y la subsiguiente petición indirecta " -"donde el usuario se conecta al host. Cuando se excede el tiempo establecido, " -"la información acerca del host elegido se olvida y el slot indirecto se " -"libera para otras pantallas. La información se puede olvidar antes si hay " -"más hosts intentando enviar solicitudes que <filename>MaxPendingIndirect</" -"filename>." - -#: C/gdm.xml:3150(term) -msgid "Port" -msgstr "Port" - -#: C/gdm.xml:3152(synopsis) -#, no-wrap -msgid "Port=177" -msgstr "Port=177" - -#: C/gdm.xml:3153(para) -msgid "" -"The UDP port number <filename>gdm</filename> should listen to for XDMCP " -"requests. Don't change this unless you know what you are doing." -msgstr "" -"El número de puerto UDP en el que <filename>gdm</filename> debería escuchar " -"las peticiones XDMCP. No cambie esto a no ser que sepa lo que está haciendo." - -#: C/gdm.xml:3162(term) -msgid "PingIntervalSeconds" -msgstr "PingIntervalSeconds" - -#: C/gdm.xml:3164(synopsis) -#, no-wrap -msgid "PingIntervalSeconds=15" -msgstr "PingIntervalSeconds=15" - -#: C/gdm.xml:3165(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 "" -"Intervalo en el que hacer ping al servidor X en segundos. Si el servidor X " -"no responde antes de la siguiente vez que lanzamos un ping a él, la conexión " -"se detiene y la sesión termina. Esta es una combinación de las opciones de " -"XDM PingInterval y PingTimeout, pero en segundos." - -#: C/gdm.xml:3173(para) -msgid "" -"Note that GDM in the past used to have a <filename>PingInterval</filename> " -"configuration key which was also in minutes. For most purposes you'd want " -"this setting to be lower 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 "" -"Note que GDM en el pasado usaba una clave de configuración " -"<filename>PingInterval</filename> estaba en minutos. Para la mayoría de los " -"propósitos querría que este ajuste fuera menor que un minuto, sin embargo en " -"la mayoría de casos donde se usaría XDMCP (como terminales de laboratorio), " -"un retraso de más de 15 segundos realmente significaría que el terminal se " -"ha apagado o reiniciado y usted querría terminar la sesión." - -#: C/gdm.xml:3186(term) -msgid "ProxyReconnect" -msgstr "ProxyReconnect" - -#: C/gdm.xml:3188(synopsis) -#, no-wrap -msgid "FlexiProxyReconnect=" -msgstr "FlexiProxyReconnect=" - -#: C/gdm.xml:3189(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 "" -"Establecer esta opción activa el soporte experimental para la migración de " -"sesión con sesiones XDMCP. Esto permite a los usuarios desconectarse de su " -"sesión y reconectarse más tarde a esa misma sesión, posiblemente desde un " -"terminal diferente." - -#: C/gdm.xml:3195(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 "" -"Para usar esta característica, debe tener un servidor X anidado disponible " -"que soporte desconectar de su servidor X padre y reconectar a otro servidor " -"X. Actualmente el servidor Distributed Multihead X (DMX) soporta esta " -"característica hasta cierto punto y otros proyectos como NoMachine NX lo " -"están implementándolo." - -#: C/gdm.xml:3202(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 "" -"Esta opción debería enviarse a la ruta de un comando que manejará la " -"reconexión del proxy XDMCD a otra pantalla de backend. Se suministra una " -"implementación de ejemplo para usar con DMX." - -#: C/gdm.xml:3211(term) -msgid "ProxyXServer" -msgstr "ProxyXServer" - -#: C/gdm.xml:3213(synopsis) -#, no-wrap -msgid "ProxyXServer=" -msgstr "ProxyXServer=" - -#: C/gdm.xml:3214(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 "" -"La línea de comandos del servidor X para un proxy XDMCP. Cualquier servidor " -"X anidado como Xnest, Xephyr o Xdmx debería funcionar bien." - -#: C/gdm.xml:3222(term) -msgid "Willing" -msgstr "Willing" - -#: C/gdm.xml:3224(synopsis) -#, no-wrap -msgid "Willing=<etc>/gdm/Xwilling" -msgstr "Willing=<etc>/gdm/Xwilling" - -#: C/gdm.xml:3225(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 "" -"Cuando la máquina devuelve un paquete WILLING tras un QUERY envía una cadena " -"que da el estado actual del servidor. El mensaje predeterminado es el ID de " -"sistema, pero es posible crear un script que muestre un mensaje " -"personalizado. Si este script no existe o esta clave está vacía se envía el " -"mensaje predeterminado. Si el script tiene éxito y produce alguna salida, se " -"envía la primera línea de la salida (y sólo la primera línea). Se ejecuta " -"como mucho una vez cada 3 segundos para impedir una posible denegación de " -"servicio inundando la máquina de paquetes QUERY." - -#: C/gdm.xml:3243(title) -msgid "Common GUI Configuration Options" -msgstr "Opciones comunes de configuración a través de la IGU" - -#: C/gdm.xml:3246(title) -msgid "[gui]" -msgstr "[gui]" - -#: C/gdm.xml:3249(term) -msgid "AllowGtkThemeChange" -msgstr "AllowGtkThemeChange" - -#: C/gdm.xml:3251(synopsis) -#, no-wrap -msgid "AllowGtkThemeChange=true" -msgstr "AllowGtkThemeChange=true" - -#: C/gdm.xml:3252(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 "" -"Si se quiere permitir cambiar el tema GTK+ (los widgets) desde el interfaz. " -"Actualmente esto sólo afecta al interfaz estándar debido a que el interfaz " -"gráfico no tiene esta capacidad. El tema tendrá efecto en esta pantalla " -"hasta que se cambie y afectará a todas las demás ventanas que sean " -"gestionadas por GDM. Soportado desde 2.5.90.2." - -#: C/gdm.xml:3264(term) -msgid "GtkRC" -msgstr "GtkRC" - -#: C/gdm.xml:3266(synopsis) -#, no-wrap -msgid "GtkRC=" -msgstr "GtkRC=" - -#: C/gdm.xml:3267(para) -msgid "" -"Path to a <filename>gtkrc</filename> to read when GDM puts up a window. You " -"should really now use the <filename>GtkTheme</filename> key for just setting " -"a theme." -msgstr "" -"Ruta al <filename>gtkrc</filename> para leer cuando GDM ponga una ventana. " -"Debería usar realmente la clave <filename>GtkTheme</filename> para " -"establecer un tema." - -#: C/gdm.xml:3276(term) -msgid "GtkTheme" -msgstr "GtkTheme" - -#: C/gdm.xml:3278(synopsis) -#, no-wrap -msgid "GtkTheme=Default" -msgstr "GtkTheme=Default" - -#: C/gdm.xml:3279(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 "" -"Un nombre de un tema instalado para usarlo por omisión. Se usará en la " -"interfaz, selector y toda ventana del GUI que salga de GDM. Soportado desde " -"2.5.90.2." - -#: C/gdm.xml:3288(term) -msgid "GtkThemesToAllow" -msgstr "GtkThemesToAllow" - -#: C/gdm.xml:3290(synopsis) -#, no-wrap -msgid "GtkThemesToAllow=all" -msgstr "GtkThemesToAllow=all" - -#: C/gdm.xml:3291(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 " -"<filename>AllowGtkThemeChange</filename> key. Supported since 2.5.90.2." -msgstr "" -"Lista separada por comas de temas permitidos. Éstos deben ser los nombres de " -"los temas instalados en los lugares estándar para temas GTK+. Puede además " -"especificar «all» para permitir todos los temas instalados. Esto está " -"relacionado con la clave <filename>AllowGtkThemeChange</filename>. Soportada " -"desde 2.5.90.2." - -#: C/gdm.xml:3303(term) -msgid "MaxIconWidth" -msgstr "MaxIconWidth" - -#: C/gdm.xml:3305(synopsis) -#, no-wrap -msgid "MaxIconWidth=128" -msgstr "MaxIconWidth=128" - -#: C/gdm.xml:3306(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 "" -"Especifica la anchura máxima del icono (en píxeles) que mostrará el visor de " -"rostros. Los iconos más grandes se escalarán. Esto también afecta a los " -"iconos en el selector XDMCP." - -#: C/gdm.xml:3315(term) -msgid "MaxIconHeight" -msgstr "MaxIconHeight" - -#: C/gdm.xml:3317(synopsis) -#, no-wrap -msgid "MaxIconHeight=128" -msgstr "MaxIconHeight=128" - -#: C/gdm.xml:3318(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 "" -"Especifica la altura máxima del icono (en píxeles) que mostrará el visor de " -"rostros. Los iconos más grandes se escalarán. Esto también afecta a los " -"iconos en el selector XDMCP." - -#: C/gdm.xml:3329(title) -msgid "Greeter Configuration" -msgstr "Configuración del interfaz" - -#: C/gdm.xml:3332(title) -msgid "[greeter]" -msgstr "[greeter]" - -#: C/gdm.xml:3335(term) -msgid "BackgroundColor" -msgstr "BackgroundColor" - -#: C/gdm.xml:3337(synopsis) -#, no-wrap -msgid "BackgroundColor=#76848F" -msgstr "BackgroundColor=#76848F" - -#: C/gdm.xml:3338(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 "" -"Si BackgroundType es 2, use este color en el fondo del interfaz. Además se " -"usará como el fondo de las imágenes transparentes y si " -"BackgroundRemoteOnlyColor está establecido y es una pantalla remota. Esto " -"sólo afecta al interfaz GTK+." - -#: C/gdm.xml:3349(term) -msgid "BackgroundProgramInitialDelay" -msgstr "BackgroundProgramInitialDelay" - -#: C/gdm.xml:3351(synopsis) -#, no-wrap -msgid "BackgroundProgramInitialDelay=30" -msgstr "BackgroundProgramInitialDelay=30" - -#: C/gdm.xml:3352(para) -msgid "" -"The background application will be started after at least that many seconds " -"of inactivity." -msgstr "" -"La aplicación de fondo será iniciada tras al menos estos segundos de " -"inactividad." - -#: C/gdm.xml:3360(term) -msgid "RestartBackgroundProgram" -msgstr "RestartBackgroundProgram" - -#: C/gdm.xml:3362(synopsis) -#, no-wrap -msgid "RestartBackgroundProgram=true" -msgstr "RestartBackgroundProgram=true" - -#: C/gdm.xml:3363(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 "" -"Si se establece la aplicación de fondo se reiniciará cuando haya salido, " -"después que el retardo descrito abajo haya pasado. Esta opción puede ser " -"útil cuando desee ejecutar un salvapantallas cuando no haya nadie usando el " -"equipo." - -#: C/gdm.xml:3373(term) -msgid "BackgroundProgramRestartDelay" -msgstr "BackgroundProgramRestartDelay" - -#: C/gdm.xml:3375(synopsis) -#, no-wrap -msgid "BackgroundProgramRestartDelay=30" -msgstr "BackgroundProgramRestartDelay=30" - -#: C/gdm.xml:3376(para) -msgid "" -"The background application will be restarted after at least that many " -"seconds of inactivity." -msgstr "" -"La aplicación de fondo será reiniciada tras al menos estos segundos de " -"inactividad." - -#: C/gdm.xml:3384(term) -msgid "BackgroundImage" -msgstr "BackgroundImage" - -#: C/gdm.xml:3386(synopsis) -#, no-wrap -msgid "BackgroundImage=somefile.png" -msgstr "BackgroundImage=somefile.png" - -#: C/gdm.xml:3387(para) -msgid "" -"If the BackgroundType is 1, then display this file as the background in the " -"greeter. This only affects the GTK+ Greeter." -msgstr "" -"Si BackgroundType es 1, entonces mostrar este archivo como fondo en el " -"interfaz. Esto sólo afecta al interfaz GTK+." - -#: C/gdm.xml:3396(term) -msgid "BackgroundProgram" -msgstr "BackgroundProgram" - -#: C/gdm.xml:3398(synopsis) -#, no-wrap -msgid "BackgroundProgram=<bin>/xeyes" -msgstr "BackgroundProgram=<bin>/xeyes" - -#: C/gdm.xml:3399(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 "" -"Si se establece, este comando se ejecutará en el fondo muentras la pantalla " -"de entrada se muestra. Note que no todas las aplicaciones ejecutarán de esta " -"manera, debido a que GDM no tiene un directorio personal usualmente. Podría " -"configurar el directorio personal del usuario GDM si quiere ejecutar " -"aplicaciones que lo requieren. Esto sólo afecta al interfaz GTK+." - -#: C/gdm.xml:3411(term) -msgid "BackgroundRemoteOnlyColor" -msgstr "BackgroundRemoteOnlyColor" - -#: C/gdm.xml:3413(synopsis) -#, no-wrap -msgid "BackgroundRemoteOnlyColor=true" -msgstr "BackgroundRemoteOnlyColor=true" - -#: C/gdm.xml:3414(para) -msgid "" -"On remote displays only set the color background. This is to make network " -"load lighter. The <filename>BackgroundProgram</filename> is also not run. " -"This only affects the GTK+ Greeter." -msgstr "" -"Establece el color de fondo sólo en las pantallas remotas. Esto es para " -"hacer la carga de red más ligera. El programa <filename>BackgroundProgram</" -"filename> tampoco se ejecuta. Esto sólo afecta al interfaz GTK+" - -#: C/gdm.xml:3424(term) -msgid "BackgroundScaleToFit" -msgstr "BackgroundScaleToFit" - -#: C/gdm.xml:3426(synopsis) -#, no-wrap -msgid "BackgroundScaleToFit=true" -msgstr "BackgroundScaleToFit=true" - -#: C/gdm.xml:3427(para) -msgid "Scale background image to fit the screen. This only affects the GTK+ Greeter." -msgstr "" -"Escalar la imagen del fondo para que quepa en la pantalla. Esto sólo afecta " -"al interfaz GTK+." - -#: C/gdm.xml:3435(term) -msgid "BackgroundType" -msgstr "BackgroundType" - -#: C/gdm.xml:3437(synopsis) -#, no-wrap -msgid "BackgroundType=2" -msgstr "BackgroundType=2" - -#: C/gdm.xml:3438(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 "" -"El tipo de fondo a establecer. 0 es ninguno, 1 es imagen y color, 2 es color " -"y 3 es imagen. Esto sólo afecta al interfaz GTK+." - -#: C/gdm.xml:3446(term) -msgid "Browser" -msgstr "Browser" - -#: C/gdm.xml:3448(synopsis) -#, no-wrap -msgid "Browser=true" -msgstr "Browser=true" - -#: C/gdm.xml:3449(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 "" -"Establézcalo a true para activar el visor de rostos. vea la sección «El " -"interfaz GTK+» para más información acerca del visor de rostros. Esta opción " -"sólo funciona para el interfaz GTK+. Para el interfaz con temas, el visor de " -"rostros se activa eligiendo un tema que incluya un visor de rostros." - -#: C/gdm.xml:3460(term) -msgid "ChooserButton" -msgstr "ChooserButton" - -#: C/gdm.xml:3462(synopsis) -#, no-wrap -msgid "ChooserButton=true" -msgstr "ChooserButton=true" - -#: C/gdm.xml:3463(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 "" -"Si es true, añadir un botón de selector al menú de Acciones que reiniciará " -"el servidor X actual con un selector. XDMCP no necesita estar activado en el " -"equipo local para que esto funcione." - -#: C/gdm.xml:3472(term) -msgid "ConfigAvailable" -msgstr "ConfigAvailable" - -#: C/gdm.xml:3474(synopsis) -#, no-wrap -msgid "ConfigAvailable=false" -msgstr "ConfigAvailable=false" - -#: C/gdm.xml:3475(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 " -"<filename>Configurator</filename> option in the daemon section." -msgstr "" -"Si es true, permite al configurador ejecutarse desde el interfaz. Note que " -"el usuario necesitará teclear la contraseña de root antes de que el " -"configurador se inicie. Establezca esto a falso por omisión para seguridad " -"adicional. Vea la opción <filename>Configurator</filename> en la sección del " -"demonio." - -#: C/gdm.xml:3487(term) -msgid "DefaultFace" -msgstr "DefaultFace" - -#: C/gdm.xml:3489(synopsis) -#, no-wrap -msgid "DefaultFace=<share>/pixmaps/nophoto.png" -msgstr "DefaultFace=<share>/pixmaps/nophoto.png" - -#: C/gdm.xml:3490(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 <filename>DefaultFace</filename> will be used. The image must " -"be in a gdk-pixbuf supported format and the file must be readable to the GDM " -"user." -msgstr "" -"Si un usuario no tiene una imagen de rostro definida, GDM usará el icono " -"\"stock_person\" definido en el tema GTK+ actual. Si dicha imagen no está " -"definida, entonces usará la imagen especificada en la opción de " -"configuración <filename>DefaultFace</filename>. La imagen debe estar en un " -"formato soportado por gdk-pixbuf y el archivo debe poderlo leer el usuario " -"de GDM." - -#: C/gdm.xml:3502(term) -msgid "Include" -msgstr "Include" - -#: C/gdm.xml:3504(synopsis) -#, no-wrap -msgid "Include=" -msgstr "Include=" - -#: C/gdm.xml:3505(para) -msgid "" -"Comma separated list of users to be included in the face browser and in the " -"<command>gdmsetup</command> selection list for Automatic/Timed login. See " -"also <filename>Exclude</filename>, <filename>IncludeAll</filename>, and " -"<filename>MinimalUID</filename>." -msgstr "" -"Lista separada por comas de usuarios que serán incluidos en el visor de " -"rostros y en la lista de selección de <command>gdmsetup</command> para el " -"inicio de sesión automático/temporizado. Vea además <filename>Exclude</" -"filename>, <filename>IncludeAll</filename>, y <filename>MinimalUID</" -"filename>." - -#: C/gdm.xml:3517(term) -msgid "Exclude" -msgstr "Exclude" - -#: C/gdm.xml:3519(synopsis) -#, no-wrap -msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." -msgstr "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." - -#: C/gdm.xml:3520(para) -msgid "" -"Comma separated list of users to be excluded from the face browser and from " -"the <command>gdmsetup</command> selection list for Automatic/Timed login. " -"Excluded users will still be able to log in, but will have to type their " -"username. See also <filename>Include</filename>, <filename>IncludeAll</" -"filename>, and <filename>MinimalUID</filename>." -msgstr "" -"Lista separada por comas de usuarios que serán excluidos en el visor de " -"rostros y en la lista de selección de <command>gdmsetup</command> para el " -"inicio de sesión automático/temporizado. Vea además <filename>Exclude</" -"filename>, <filename>IncludeAll</filename>, y <filename>MinimalUID</" -"filename>." - -#: C/gdm.xml:3533(term) -msgid "IncludeAll" -msgstr "IncludeAll" - -#: C/gdm.xml:3535(synopsis) -#, no-wrap -msgid "IncludeAll=false" -msgstr "IncludeAll=false" - -#: C/gdm.xml:3536(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 <filename>Include</filename>, <filename>Exclude</" -"filename>, and <filename>MinimalUID</filename>." -msgstr "" -"Por omisión, una lista de inclusión vacía significa no mostrar ningún " -"usuario. Estableciendo IncludeAll al valor «true», se inspeccionará el " -"archivo de contraseñas y todos los usuarios se mostrarán excepto los " -"usuarios excluidos por medio del ajuste de exclusión y los IDs de usuario " -"menores que MinimalUID. Examinar el archivo de contraseñas puede ser lento " -"en sistemas con gran número de usuarios y esta característica no se usará en " -"dichos entornos. Vea además <filename>Include</filename>, <filename>Exclude</" -"filename>, y <filename>MinimalUID</filename>." - -#: C/gdm.xml:3552(term) -msgid "GlobalFaceDir" -msgstr "GlobalFaceDir" - -#: C/gdm.xml:3554(synopsis) -#, no-wrap -msgid "GlobalFaceDir=<share>/pixmaps/faces/" -msgstr "GlobalFaceDir=<share>/pixmaps/faces/" - -#: C/gdm.xml:3555(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 "" -"Directorio para todo el sistema para los archivos de rostros. El " -"administrador del sistema puede colocar iconos para los usuarios aquí sin " -"tocar los directorios personales. Los rostros se llaman como los nombres de " -"sus usuarios." - -#: C/gdm.xml:3561(para) -msgid "" -"I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the " -"face icon for the user ``johndoe''. No image format extension should be " -"specified." -msgstr "" -"Ej <filename><GlobalFaceDir>/juansinnombre</filename> debería contener " -"el icono de rostro para el usuario «juansinnombre». No se debe especificar " -"ninguna extensión indicando el formato de la imagen." - -#: C/gdm.xml:3567(para) -msgid "" -"The face images must be stored in gdk-pixbuf supported formats and they must " -"be readable for the GDM user." -msgstr "" -"Las imágenes de los rostros deben almacenarse en un formato soportado por " -"gdk-pixbuf y deben tener permiso de lectura para el usuario GDM." - -#: C/gdm.xml:3572(para) -msgid "" -"A user's own icon file will always take precedence over the sysadmin " -"provided one." -msgstr "" -"Un archivo de icono de un usuario siempre toma precedencia sobre el " -"proporcionado por el administrador del sistema." - -#: C/gdm.xml:3580(term) -msgid "GraphicalTheme" -msgstr "GraphicalTheme" - -#: C/gdm.xml:3582(synopsis) -#, no-wrap -msgid "GraphicalTheme=circles" -msgstr "GraphicalTheme=circles" - -#: C/gdm.xml:3583(para) -msgid "" -"The graphical theme that the Themed Greeter should use. it should refer to a " -"directory in the theme directory set by <filename>GraphicalThemeDir</" -"filename>." -msgstr "" -"Los temas gráficos que el Interfaz de entrada con temas debería usar. " -"Debería referirse a un directorio en el directorio del tema designado por " -"<filename>GraphicalThemeDir</filename>. " - -#: C/gdm.xml:3592(term) -msgid "GraphicalThemes" -msgstr "GraphicalThemes" - -#: C/gdm.xml:3594(synopsis) -#, no-wrap -msgid "GraphicalThemes=circles" -msgstr "GraphicalThemes=circles" - -#: C/gdm.xml:3595(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 <filename>GraphicalThemeDir</" -"filename>. This is only used if <filename>GraphicalThemeRand</filename> is " -"set to true." -msgstr "" -"Los temas gráficos que el Interfaz de entrada debería usar si el modo está " -"puesto a Temas aleatorios. Esto es una lista delimitada por \"/:\" . " -"Debería referirse a un directorio en el directorio del tema designado por " -"<filename>GraphicalThemeDir</filename>. Esto se usa sólo si " -"<filename>GraphicalThemeRand</filename> está establecido a «true»." - -#: C/gdm.xml:3607(term) -msgid "GraphicalThemeRand" -msgstr "GraphicalThemeRand" - -#: C/gdm.xml:3609(synopsis) -#, no-wrap -msgid "GraphicalThemeRand=false" -msgstr "GraphicalThemeRand=false" - -#: C/gdm.xml:3610(para) -msgid "" -"Whether the graphical greeter will use Only One Theme or Random Theme mode. " -"Only One Theme mode uses themes listed by <filename>GraphicalTheme</" -"filename>, Random Themes mode uses themes listed by " -"<filename>GraphicalThemes</filename>. 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 "" -"Indica si el interfaz gráfico usará «Sólo un tema» o «Tema aleatorio». Sólo " -"el modo «Un tema» usa los temas listados en <filename>GraphicalTheme</" -"filename>, el modo «Temas aleatorios» usa los temas listados por " -"<filename>GraphicalThemes</filename>. Un valor de false establece el " -"interfaz para que use el modo «Sólo un tema», un valor de true establece al " -"interfaz para usar el modo «Tema aleatorio»." - -#: C/gdm.xml:3622(term) -msgid "GraphicalThemeDir" -msgstr "GraphicalThemeDir" - -#: C/gdm.xml:3624(synopsis) -#, no-wrap -msgid "GraphicalThemeDir=<share>/gdm/themes/" -msgstr "GraphicalThemeDir=<share>/gdm/themes/" - -#: C/gdm.xml:3625(para) -msgid "The directory where themes for the Themed Greeter are installed." -msgstr "El directorio donde se instalan los temas para el Interfaz de Temas." - -#: C/gdm.xml:3633(term) -msgid "GraphicalThemedColor" -msgstr "GraphicalThemedColor" - -#: C/gdm.xml:3635(synopsis) -#, no-wrap -msgid "GraphicalThemedColor=#76848F" -msgstr "GraphicalThemedColor=#76848F" - -#: C/gdm.xml:3636(para) -msgid "" -"Use this color in the background of the Themed Greeter. This only affects " -"the Themed Greeter." -msgstr "" -"Use este color en el fondo del Interfaz con Temas. Esto sólo afecta al " -"interfaz con temas." - -#: C/gdm.xml:3644(term) -msgid "InfoMsgFile" -msgstr "InfoMsgFile" - -#: C/gdm.xml:3646(synopsis) -#, no-wrap -msgid "InfoMsgFile=/path/to/infofile" -msgstr "InfoMsgFile=/path/to/infofile" - -#: C/gdm.xml:3647(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 "" -"Si está presente y la /ruta/al/archivo/info especifica un archivo de texto " -"existente y legible (ej: <etc>/infomsg.txt) el contenido del archivo " -"se mostrará en una caja de diálogo modal antes que al usuario se le permita " -"entrar. Esto funciona con los interfaces estándar y con temas." - -#: C/gdm.xml:3658(term) -msgid "InfoMsgFont" -msgstr "InfoMsgFont" - -#: C/gdm.xml:3660(synopsis) -#, no-wrap -msgid "InfoMsgFont=fontspec" -msgstr "InfoMsgFont=fontspec" - -#: C/gdm.xml:3661(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 "" -"Si está presente y InfoMsgFile (ver arriba) está en uso, esto especifica la " -"tipografía que usar cuando se muestra el contenido del archivo de texto " -"InfoMsgFile. Por ejemplo fontspec podría ser Sans 24 para obtener un tipo " -"sans serif de 24 puntos de tamaño. Esto funciona tanto para el interfaz " -"estándar como para los de temas." - -#: C/gdm.xml:3673(term) -msgid "LocaleFile" -msgstr "LocaleFile" - -#: C/gdm.xml:3675(synopsis) -#, no-wrap -msgid "LocaleFile=<etc>/gdm/locale.alias" -msgstr "LocaleFile=<etc>/gdm/locale.alias" - -#: C/gdm.xml:3676(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 "" -"Archivo en formato similar al formato de GNU locale con entradas para todos " -"los idiomas soportados en el sistema. El formato se describe encima o en un " -"comentario dentro de ese archivo." - -#: C/gdm.xml:3685(term) -msgid "LockPosition" -msgstr "LockPosition" - -#: C/gdm.xml:3687(synopsis) -#, no-wrap -msgid "LockPosition=true" -msgstr "LockPosition=true" - -#: C/gdm.xml:3688(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 "" -"Si es true, la posición de la ventana de entrada del interfaz de entrada GTK" -"+ no se puede cambiar incluso si la barra de título está activada." - -#: C/gdm.xml:3696(term) -msgid "Logo" -msgstr "Logo" - -#: C/gdm.xml:3698(synopsis) -#, no-wrap -msgid "Logo=<share>/pixmaps/gnome-logo-large.png" -msgstr "Logo=<share>/pixmaps/gnome-logo-large.png" - -#: C/gdm.xml:3699(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 "" -"El archivo de imagen que mostrar en la cada del logotipo. El archivo debe " -"estar en un formato soportado por gdk-pixbuf y debe ser legible por el " -"usuario GDM. Si no se especifica ningún archivo, la característica del " -"logotipo se desactiva. Esto sólo afecta al interfaz de entrada GTK+." - -#: C/gdm.xml:3710(term) -msgid "ChooserButtonLogo" -msgstr "ChooserButtonLogo" - -#: C/gdm.xml:3712(synopsis) -#, no-wrap -msgid "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" -msgstr "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" - -#: C/gdm.xml:3713(para) -msgid "" -"Image file to display in the file chooser button in <command>gdmsetup</" -"command>. This key is modified by <command>gdmsetup</command> and should not " -"be manually modified by the user. This only affects the Login Window " -"Preferences (<command>gdmsetup</command>)." -msgstr "" -"Archivo de imagen para mostrar en el botón del selector de archivos en " -"<command>gdmsetup</command>. Esta clave se modifica por <command>gdmsetup</" -"command> y no debería modificarse manualmente por el usuario. Esto sólo " -"afecta a las preferencias de la pantalla de entrada (<command>gdmsetup</" -"command>)." - -#: C/gdm.xml:3724(term) -msgid "MinimalUID" -msgstr "MinimalUID" - -#: C/gdm.xml:3726(synopsis) -#, no-wrap -msgid "MinimalUID=100" -msgstr "MinimalUID=100" - -#: C/gdm.xml:3727(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 <filename>Include</" -"filename>, <filename>Exclude</filename>, and <filename>IncludeAll</filename>." -msgstr "" -"El UID mínimo que GDM debería considerar un usuario. Todos los usuarios con " -"un UID inferior serán excluidos del visor de rostros. Vea además " -"<filename>Include</filename>, <filename>Exclude</filename>, y " -"<filename>IncludeAll</filename>." - -#: C/gdm.xml:3738(term) -msgid "PositionX" -msgstr "PositionX" - -#: C/gdm.xml:3740(synopsis) -#, no-wrap -msgid "PositionX=200" -msgstr "PositionX=200" - -#: C/gdm.xml:3741(para) -msgid "The horizontal position of the login window of the GTK+ Greeter." -msgstr "La posición horizontal de la ventana de entrada del interfaz GTK+." - -#: C/gdm.xml:3749(term) -msgid "PositionY" -msgstr "PositionY" - -#: C/gdm.xml:3751(synopsis) -#, no-wrap -msgid "PositionY=100" -msgstr "PositionY=100" - -#: C/gdm.xml:3752(para) -msgid "The vertical position of the login window of the GTK+ Greeter." -msgstr "La posición vertical de la ventana de entrada del interfaz GTK+." - -#: C/gdm.xml:3760(term) -msgid "Quiver" -msgstr "Quiver" - -#: C/gdm.xml:3762(synopsis) -#, no-wrap -msgid "Quiver=true" -msgstr "Quiver=true" - -#: C/gdm.xml:3763(para) -msgid "" -"Controls whether <command>gdmlogin</command> should shake the display when " -"an incorrect username/password is entered. This only affects the GTK+ " -"Greeter." -msgstr "" -"Controla si <command>gdmlogin</command> debe agitar la pantalla cuando se " -"introduce un usuario/contraseña incorrecto. Esto sólo afecta al interfaz GTK" -"+." - -#: C/gdm.xml:3773(term) -msgid "DefaultRemoteWelcome" -msgstr "DefaultRemoteWelcome" - -#: C/gdm.xml:3775(synopsis) -#, no-wrap -msgid "DefaultRemoteWelcome=true" -msgstr "DefaultRemoteWelcome=true" - -#: C/gdm.xml:3776(para) -msgid "" -"If set to true, the value \"Welcome to %n\" is used for the " -"<filename>RemoteWelcome</filename>. This value is translated into the " -"appropriate language for the user. If set to false, the " -"<filename>RemoteWelcome</filename> 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 "" -"Si está establecido a «true» el valor \"Welcome to %n\" se usa para " -"<filename>RemoteWelcome</filename>. Este valor se traduce al idioma " -"apropiado para el usuario. Si se establece a «false», se usa el ajuste " -"<filename>RemoteWelcome</filename>. Esta cadena puede usar las secuencias de " -"caracteres especiales tal como se explica en la sección \"Nodo de texto\" " -"del capítulo \"Interfaz con temas\". Esto explica el significado de \"%n\"." - -#: C/gdm.xml:3790(term) -msgid "RemoteWelcome" -msgstr "RemoteWelcome" - -#: C/gdm.xml:3792(synopsis) -#, no-wrap -msgid "RemoteWelcome=Welcome to %n" -msgstr "RemoteWelcome=Welcome to %n" - -#: C/gdm.xml:3793(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 " -"<filename>Welcome</filename> string. This string can use the same special " -"character sequences as explained in the \"Text Node\" section of the " -"\"Themed Greeter\" chapter. chapter." -msgstr "" -"Controla qué texto mostrar al lado de la imagen del logo en el interfaz para " -"las sesiones XDMCP remotas. Se realiza la misma expansión aquí como en la " -"cadena <filename>Welcome</filename>. Esta cadena puede usar las mismas " -"secuencias de caracteres especiales tal como se explica en la sección «Nodo " -"de Texto» del capítulo \"Interfaz con temas\"" - -#: C/gdm.xml:3806(term) -msgid "RunBackgroundProgramAlways" -msgstr "RunBackgroundProgramAlways" - -#: C/gdm.xml:3808(synopsis) -#, no-wrap -msgid "RunBackgroundProgramAlways=false" -msgstr "RunBackgroundProgramAlways=false" - -#: C/gdm.xml:3809(para) -msgid "" -"If this is true then the background application is run always, otherwise it " -"is only run when the <filename>BackgroundType</filename> is 0 (None) This " -"only affects the GTK+ Greeter." -msgstr "" -"Si esto es true entonces la aplicación de fondo se ejecuta siempre, en otro " -"caso sólo se ejecuta cuando <filename>BackgroundType</filename> es 0 " -"(Ninguno) Esto sólo afecta al interfaz GTK+" - -#: C/gdm.xml:3819(term) -msgid "SetPosition" -msgstr "SetPosition" - -#: C/gdm.xml:3821(synopsis) -#, no-wrap -msgid "SetPosition=true" -msgstr "SetPosition=true" - -#: C/gdm.xml:3822(para) -msgid "" -"If true the position of the login window of the GTK+ Greeter is determined " -"by <filename>PositionX</filename> / <filename>PositionY</filename>." -msgstr "" -"Si es true la posición de la ventana de entrada del interfaz GTK+ se " -"determina por PositionX</filename> / <filename>PositionY</filename>." - -#: C/gdm.xml:3831(term) -msgid "ShowGnomeFailsafeSession" -msgstr "ShowGNOMEFailsafeSession" - -#: C/gdm.xml:3833(synopsis) -#, no-wrap -msgid "ShowGnomeFailsafeSession=true" -msgstr "ShowGnomeFailsafeSession=true" - -#: C/gdm.xml:3834(para) -msgid "Should the greeter show the Gnome Failsafe session in th sessions list." -msgstr "" -"Indica si el interfaz muestra la sesión a prueba de fallos en la lista de " -"sesiones." - -#: C/gdm.xml:3842(term) -msgid "ShowLastSession" -msgstr "ShowLastSession" - -#: C/gdm.xml:3844(synopsis) -#, no-wrap -msgid "ShowLastSession=true" -msgstr "ShowLastSession=true" - -#: C/gdm.xml:3845(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 <filename>DefaultSession</filename>) unless " -"then pick something else for this session only. So if this is off, this " -"really circumvents saving of the last session." -msgstr "" -"Indica si el interfaz debe mostrar la última sesión en la lista de sesiones. " -"Si esto se desactiva, entonces GDM está en modo 'cambio de escritorio' que " -"es por ejemplo lo que usa Red Hat. Esto es, los usuarios no pueden escoger " -"la última sesión y obtienen entonces la sesión predeterminada (ver " -"<filename>DefaultSession</filename>) a no ser que escojan otra cosa distinta " -"para esta sesión únicamente. Así si esto está desactivado, esto realmente " -"evita guardar la última sesión." - -#: C/gdm.xml:3858(term) -msgid "ShowXtermFailsafeSession" -msgstr "ShowXtermFailsafeSession" - -#: C/gdm.xml:3860(synopsis) -#, no-wrap -msgid "ShowXtermFailsafeSession=true" -msgstr "ShowXtermFailsafeSession=true" - -#: C/gdm.xml:3861(para) -msgid "Should the greeter show the Xterm Failsafe session in the sessions list." -msgstr "" -"Indica si el interfaz debe mostrar la sesión a prueba de fallos Xterm en la " -"lista de sesiones." - -#: C/gdm.xml:3869(term) -msgid "SoundOnLogin" -msgstr "SoundOnLogin" - -#: C/gdm.xml:3871(synopsis) -#, no-wrap -msgid "SoundOnLogin=true" -msgstr "SoundOnLogin=true" - -#: C/gdm.xml:3872(para) -msgid "" -"If true, the greeter will play a sound or beep when it is ready for a login. " -"See also the <filename>SoundOnLoginFile</filename> key. Supported since " -"2.5.90.0." -msgstr "" -"Si es true, el interfaz reproducirá un sonido o pitará cuando esté listo " -"para una entrada. Vea además la clave <filename>SoundOnLoginFile</filename>. " -"Soportado desde 2.5.90.0." - -#: C/gdm.xml:3882(term) -msgid "SoundOnLoginSuccess" -msgstr "SoundOnLoginSuccess" - -#: C/gdm.xml:3884(synopsis) -#, no-wrap -msgid "SoundOnLoginSuccess=true" -msgstr "SoundOnLoginSuccess=true" - -#: C/gdm.xml:3885(para) -msgid "" -"If true, the greeter will play a sound after a successful login attempt. See " -"also the <filename>SoundOnLoginSuccessFile</filename> key." -msgstr "" -"Si es true, el interfaz reproducirá un sonido tras un intento de entrada " -"exitoso. Vea además la clave <filename>SoundOnLoginSuccessFile</filename>" - -#: C/gdm.xml:3894(term) -msgid "SoundOnLoginFailure" -msgstr "SoundOnLoginFailure" - -#: C/gdm.xml:3896(synopsis) -#, no-wrap -msgid "SoundOnLoginFailure=true" -msgstr "SoundOnLoginFailure=true" - -#: C/gdm.xml:3897(para) -msgid "" -"If true, the greeter will play a sound after a failed login attempt. See " -"also the <filename>SoundOnLoginFailureFile</filename> key." -msgstr "" -"Si es true, el interfaz reproducirá un sonido tras un intento de entrada " -"fallido. Vea además la clave <filename>SoundOnLoginFailureFile</filename>." - -#: C/gdm.xml:3906(term) -msgid "SoundOnLoginFile" -msgstr "SoundOnLoginFile" - -#: C/gdm.xml:3908(synopsis) -#, no-wrap -msgid "SoundOnLoginFile=/path/to/sound.wav" -msgstr "SoundOnLoginFile=/path/to/sound.wav" - -#: C/gdm.xml:3909(para) -msgid "" -"The file that will be played using the specified sound application (by " -"default that is <filename>/usr/bin/play</filename>) instead of a beep when " -"the greeter is ready for a login. See also the <filename>SoundOnLogin</" -"filename> key and the <filename>SoundProgram</filename> key. Supported since " -"2.5.90.0." -msgstr "" -"El archivo que se reproducirá usando la aplicación de sonido especificada " -"(por omisión esto es <filename>/usr/bin/play</filename>) en lugar de un " -"pitido cuando el interfaz esté preparado para una entrada. Vea además la " -"clave <filename>SoundOnLogin</filename> y la clave <filename>SoundProgram</" -"filename>. Soportado desde 2.5.90.0." - -#: C/gdm.xml:3922(term) -msgid "SoundOnLoginSuccessFile" -msgstr "SoundOnLoginSuccessFile" - -#: C/gdm.xml:3924(synopsis) -#, no-wrap -msgid "SoundOnLoginSuccessFile=/path/to/sound.wav" -msgstr "SoundOnLoginSuccessFile=/path/to/sound.wav" - -#: C/gdm.xml:3925(para) -msgid "" -"The file that will be played using the specified sound application (by " -"default that is <filename>/usr/bin/play</filename>) after a successful login " -"attempt. See also the <filename>SoundOnLoginSuccess</filename> key and the " -"<filename>SoundProgram</filename> key." -msgstr "" -"El archivo que se reproducirá usando la aplicación de sonido especificada " -"(por omisión es <filename>/usr/bin/play</filename>) tras una entrada " -"exitosa. Vea además las claves <filename>SoundOnLoginSuccess</filename> y " -"<filename>SoundProgram</filename>." - -#: C/gdm.xml:3936(term) -msgid "SoundOnLoginFailureFile" -msgstr "SoundOnLoginFailureFile" - -#: C/gdm.xml:3938(synopsis) -#, no-wrap -msgid "SoundOnLoginFailureFile=/path/to/sound.wav" -msgstr "SoundOnLoginFailureFile=/path/to/sound.wav" - -#: C/gdm.xml:3939(para) -msgid "" -"The file that will be played using the specified sound application (by " -"default that is <filename>/usr/bin/play</filename>) after a failed login " -"attempt. See also the <filename>SoundOnLoginFailure</filename> key and the " -"<filename>SoundProgram</filename> key." -msgstr "" -"El archivo que se reproducirá usando la aplicación de sonido especificada " -"(por omisión es <filename>/usr/bin/play</filename>) tras un intento fallido " -"de entrada. Vea además las claves <filename>SoundOnLoginFailure</filename> y " -"<filename>SoundProgram</filename>." - -#: C/gdm.xml:3950(term) -msgid "SystemMenu" -msgstr "SystemMenu" - -#: C/gdm.xml:3952(synopsis) -#, no-wrap -msgid "SystemMenu=true" -msgstr "SystemMenu=true" - -#: C/gdm.xml:3953(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 attached displays. It would not be safe or " -"even desirable on remote logins, so you do not have to worry about remote " -"users having these privileges." -msgstr "" -"Activa o desactiva el menú Acciones (que se llamaba antes menú Sistema). Si " -"esto está apagado entonces una de las acciones estará disponible en " -"cualquier lugar. Estas acciones incluyen Apagar, Reiniciar, Configurar, " -"selector XDMCP y demás. Todas aquellas sin embargo pueden desactivarse " -"individualmente. Apagar, Reiniciar y Suspender se pueden desactivar tan solo " -"estableciendo las claves correspondientes a un valor vacío. Note que el menú " -"de acciones sólo se muestra en pantallas locales. No sería seguro o incluso " -"deseable en las entradas remotoas, así que no tiene que preocuparse por si " -"los usuarios remotos tienen cualquier clase de esos privilegios." - -#: C/gdm.xml:3965(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 "" -"Note que si esto está desactivado ninguna de las acciones estará disponible " -"incluso si un tema para un interfaz gráfico las muestra por equivocación. " -"Además note que algunas veces un tema gráfico no podría mostrar todas las " -"acciones disponibles como botones y quizá deba pulsar F10 para ver el menú." - -#: C/gdm.xml:3976(term) -msgid "TitleBar" -msgstr "TitleBar" - -#: C/gdm.xml:3978(synopsis) -#, no-wrap -msgid "TitleBar=true" -msgstr "TitleBar=true" - -#: C/gdm.xml:3979(para) -msgid "Display the title bar in the greeter. This only affects the GTK+ Greeter." -msgstr "Muestra la barra de título en el interfaz. Esto sólo afecta al interfaz GTK+." - -#: C/gdm.xml:3987(term) -msgid "Use24Clock" -msgstr "Use24Clock" - -#: C/gdm.xml:3989(synopsis) -#, no-wrap -msgid "Use24Clock=auto" -msgstr "Use24Clock=auto" - -#: C/gdm.xml:3990(para) -msgid "" -"Select the use of 24 hour clock. Some locales do not support 12 hour format " -"(like Finnish, that is <filename>fi_FI</filename>), and in those locales " -"this setting has no effect at all." -msgstr "" -"Seleccione el uso de un reloj de 24 horas. Algunas configuraciones " -"regionales no soportan el formato de 12 horas (como Finlandés, que es " -"<filename>fi_FI</filename>) y en dichas configuraciones regionales este " -"ajuste no tiene ningún efecto." - -#: C/gdm.xml:3996(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 "" -"Los valores aceptados son: «auto» (predeterminado), «true» y «false». Si se " -"ajusta a «auto» o se deja vacío, el formato de la hora se tomará de los " -"ajuste de locale. Los ajustes de locale están basados en el idioma en uso, " -"por lo tanto se cambia mediante las variables LANGUAGE (extensión GNU), " -"LANG, LC_MESSAGES o LC_ALL en el entorno de ejecución de GDM. Podrá " -"encontrar información acerda de las prioridades entre las variables de " -"entorno indicadas en el manual de las bibliotecas de C de su sistema." - -#: C/gdm.xml:4011(term) -msgid "UseCirclesInEntry" -msgstr "UseCirclesInEntry" - -#: C/gdm.xml:4013(synopsis) -#, no-wrap -msgid "UseCirclesInEntry=false" -msgstr "UseCirclesInEntry=false" - -#: C/gdm.xml:4014(para) -msgid "" -"Use circles instead of asterisks in the password entry. This may not work " -"with all fonts however." -msgstr "" -"Usa círculos en lugar de asteriscos en la entrada de la contraseña. Esto " -"podría no funcionar con todas las tipografías sin embargo." - -#: C/gdm.xml:4022(term) -msgid "UseInvisibleInEntry" -msgstr "UseInvisibleInEntry" - -#: C/gdm.xml:4024(synopsis) -#, no-wrap -msgid "UseInvisibleInEntry=false" -msgstr "UseInvisibleInEntry=false" - -#: C/gdm.xml:4025(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 " -"<filename>UseCirclesInEntry</filename> option." -msgstr "" -"No muestra ningún retorno visual en la entrada de contraseñas. Esto es " -"estándar en la consola y xdm. Ajustar esta opción descarta la opción " -"<filename>UseCirclesInEntry</filename>." - -#: C/gdm.xml:4035(term) -msgid "DefaultWelcome" -msgstr "DefaultWelcome" - -#: C/gdm.xml:4037(synopsis) -#, no-wrap -msgid "DefaultWelcome=true" -msgstr "DefaultWelcome=true" - -#: C/gdm.xml:4038(para) -msgid "" -"If set to true, the value \"Welcome\" is used for the <filename>Welcome</" -"filename>. This value is translated into the appropriate language for the " -"user. If set to false, the <filename>Welcome</filename> setting is used." -msgstr "" -"Si está establecido a «true» el valor \"Welcome\" se usa para la " -"<filename>Welcome</filename>. Este valor está traducido en el idioma " -"apropiado para el usuario. Si se establece a «false», se usa el ajuste " -"<filename>Welcome</filename>." - -#: C/gdm.xml:4048(term) -msgid "Welcome" -msgstr "Welcome" - -#: C/gdm.xml:4050(synopsis) -#, no-wrap -msgid "Welcome=Welcome" -msgstr "Welcome=Welcome" - -#: C/gdm.xml:4051(para) -msgid "" -"Controls which text to display next to the logo image in the standard " -"greeter. The following control chars are supported:" -msgstr "" -"Controla qué texto se muestra junto a la imagen del logotipo en el interfaz " -"estándar. Están soportados los siguientes caracteres de control:" - -#: C/gdm.xml:4060(para) -msgid "%d — display's hostname" -msgstr "%d — nombre de equipo de la pantalla" - -#: C/gdm.xml:4064(para) -msgid "%h — Fully qualified hostname" -msgstr "%h — Nombre de equipo completamente cualificado" - -#: C/gdm.xml:4068(para) -msgid "%m — machine (processor type)" -msgstr "%m — máquina (tipo de procesador)" - -#: C/gdm.xml:4072(para) -msgid "%n — Nodename (i.e. hostname without .domain)" -msgstr "%n — Nombre de nodo (ej. nombre del host sin .dominio)" - -#: C/gdm.xml:4076(para) -msgid "%r — release (OS version)" -msgstr "%r — lanzamiento (versión del SO)" - -#: C/gdm.xml:4080(para) -msgid "%s — sysname (i.e. OS)" -msgstr "%s — nombre del sistema (ej. SO)" - -#: C/gdm.xml:4084(para) -msgid "" -"This string is only used for attached displays. For remote XDMCP displays we " -"use <filename>RemoteWelcome</filename>." -msgstr "" -"Esta cadena se usa sólo para la pantalla local. Para pantallas remotas XDMCP " -"se usa <filename>RemoteWelcome</filename>." - -#: C/gdm.xml:4089(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 "" -"En el interfaz con temas la ubicación de este texto depende del tema. A no " -"ser que el tema use la cadena de bienvenida predeterminada en algún lugar " -"esta cadena no se verá." - -#: C/gdm.xml:4099(term) -msgid "XineramaScreen" -msgstr "XineramaScreen" - -#: C/gdm.xml:4101(synopsis) -#, no-wrap -msgid "XineramaScreen=0" -msgstr "XineramaScreen=0" - -#: C/gdm.xml:4102(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 "" -"Si está activa la extensión Xinerama la ventana de inicio de sesión se " -"centrará en esta pantalla física (use 0 para la primera pantalla, 1 para la " -"segunda...)." - -#: C/gdm.xml:4113(title) -msgid "XDCMP Chooser Options" -msgstr "Opciones del selector XDCMP" - -#: C/gdm.xml:4116(title) -msgid "[chooser]" -msgstr "[chooser]" - -#: C/gdm.xml:4119(term) -msgid "AllowAdd" -msgstr "AllowAdd" - -#: C/gdm.xml:4121(synopsis) -#, no-wrap -msgid "AllowAdd=true" -msgstr "AllowAdd=true" - -#: C/gdm.xml:4122(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 "" -"Si es true, permite al usuario añadir hosts arbitrarios al selector. De esta " -"manera el usuario podría conectarse a cualquier host que responda a " -"peticiones XDMCP desde el selector." - -#: C/gdm.xml:4131(term) -msgid "Broadcast" -msgstr "Broadcast" - -#: C/gdm.xml:4133(synopsis) -#, no-wrap -msgid "Broadcast=true" -msgstr "Broadcast=true" - -#: C/gdm.xml:4134(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 " -"<filename>Hosts</filename> key." -msgstr "" -"Si es «true», el selector emitirá una petición a la red local y recogerá las " -"respuestas. De este modo el selector siempre mostrará todos los gestores " -"disponibles en la red. Si necesita añadir algún servidor que no sea local a " -"esta red, o si no desea utilizar «broadcast», puede añadirlo explícitamente " -"en la clave <filename>Hosts</filename>." - -#: C/gdm.xml:4146(term) -msgid "Multicast" -msgstr "Multicast" - -#: C/gdm.xml:4148(synopsis) -#, no-wrap -msgid "Multicast=true" -msgstr "Multicast=true" - -#: C/gdm.xml:4149(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 <filename>Hosts </filename> key. The host will respond if it is " -"listening to XDMCP requests and IPv6 is enabled there." -msgstr "" -"Si es «true» y está activado IPv6, el selector emitirá una petición " -"multicast a la red local y recogerá las respuestas de los servidores que se " -"hayan unido al grupo multicast. Si no desea emitir un multicast puede " -"indicar una dirección IPv6 en la clave <filename>Hosts</filename>. El " -"servidor responderá si está escuchando a las peticiones XDMCP y tiene " -"activado IPv6." - -#: C/gdm.xml:4161(term) -msgid "MulticastAddr" -msgstr "MulticastAddr" - -#: C/gdm.xml:4163(synopsis) -#, no-wrap -msgid "MulticastAddr=ff02::1" -msgstr "MulticastAddr=ff02::1" - -#: C/gdm.xml:4164(para) -msgid "This is the Link-local Multicast address and is hardcoded here." -msgstr "Esta es la dirección de enlace local multicast y está codificada aquí." - -#: C/gdm.xml:4171(term) -msgid "DefaultHostImage" -msgstr "DefaultHostImage" - -#: C/gdm.xml:4173(synopsis) -#, no-wrap -msgid "DefaultHostImage=<share>/pixmaps/nohost.png" -msgstr "DefaultHostImage=<share>/pixmaps/nohost.png" - -#: C/gdm.xml:4174(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 "" -"El nombre del archivo para el icono de host predeterminado. Esta imagen debe " -"mostrarse si no hay ningún icono especificado en un host dado. El archivo " -"debe estar en un formato soportado por gdk-pixbuf y deben tener permiso de " -"lectura para el usuario de GDM." - -#: C/gdm.xml:4184(term) -msgid "HostImageDir" -msgstr "HostImageDir" - -#: C/gdm.xml:4186(synopsis) -#, no-wrap -msgid "HostImageDir=<share>/hosts" -msgstr "HostImageDir=<share>/hosts" - -#: C/gdm.xml:4187(para) -msgid "" -"Repository for host icon files. The sysadmin can place icons for remote " -"hosts here and they will appear in <filename>gdmchooser</filename>." -msgstr "" -"Repositorio para archivos de iconos de host. El administrador del sistema " -"puede colocar iconos para los hosts remotos para que aparezcn en " -"<filename>gdmchooser</filename>." - -#: C/gdm.xml:4193(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 "" -"El nombre del archivo debe coincidir con el nombre completamente cualificado " -"(FQDN) para el host. Los iconos deben almacenarse en un formato soportado " -"por gdk-pixbuf y deben tener permiso de lectura para el usuario de GDM." - -#: C/gdm.xml:4203(term) -msgid "Hosts" -msgstr "Hosts" - -#: C/gdm.xml:4205(synopsis) -#, no-wrap -msgid "Hosts=host1,host2" -msgstr "Hosts=host1,host2" - -#: C/gdm.xml:4206(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 " -"<filename>Broadcast</filename> 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:4218(term) -msgid "ScanTime" -msgstr "ScanTime" - -#: C/gdm.xml:4220(synopsis) -#, no-wrap -msgid "ScanTime=4" -msgstr "ScanTime=4" - -#: C/gdm.xml:4221(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:4233(title) -msgid "Debug Configuration" -msgstr "Depurar configuración" - -#: C/gdm.xml:4236(title) -msgid "[debug]" -msgstr "[debug]" - -#: C/gdm.xml:4242(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 "" -"Establecer a verdadero envía la salida de depuración al syslog. Esto puede " -"ser útil para trazar problemas con GDM. Esta salida tiene a ser prolia así " -"que no se debería activar para uso general." - -#: C/gdm.xml:4252(term) -msgid "Gestures" -msgstr "Gestures" - -#: C/gdm.xml:4254(synopsis) -#, no-wrap -msgid "Gestures=false" -msgstr "Gestures=false" - -#: C/gdm.xml:4255(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 "" -"Establecer a verdadero envía la salida de depuración de los listeners de " -"gestos al syslog. Esto puede ser útil para trazar problemas con ellos cuando " -"no funcionan correctamente. Esta salida tiende a ser prolija así que no se " -"debería activar para uso general." - -#: C/gdm.xml:4268(title) -msgid "Custom Commands" -msgstr "Comandos personalizados" - -#: C/gdm.xml:4270(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:4279(title) -msgid "[customcommand]" -msgstr "[customcommand]" - -#: C/gdm.xml:4282(term) -msgid "CustomCommand[0-9]" -msgstr "CustomCommand[0-9]" - -#: C/gdm.xml:4284(synopsis) -#, no-wrap -msgid "CustomCommand[0-9]=" -msgstr "CustomCommand[0-9]=" - -#: C/gdm.xml:4285(para) -msgid "" -"Full path and arguments to command to be executed when user selects " -"<filename>n-th</filename> \"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 <filename>CustomCommand</filename> suffix and " -"can be an integer between 0 and 9." -msgstr "" -"Ruta completa y argumentos al comando que ejecutar cuando el usuario " -"selecciona <filename>n-th</filename> \"Comando personalizado\" en el menú " -"Acciones. Esto puede ser una lista separada por \";\" de comandos a " -"intentar. Si el valor está vacío o falta, entonces el comando personalizado " -"no estará disponible. Note que de forma predeterminada este valor no está " -"activado, así que para ctivar el \"Comando personalizado\" debe establecerlo " -"a un valor no vacío. [0-9] representa el sufijo de <filename>CustomCommand</" -"filename> y puede ser un entero entre 0 y 9." - -#: C/gdm.xml:4300(term) -msgid "CustomCommandIsPersistent[0-9]" -msgstr "CustomCommandIsPersistent[0-9]" - -#: C/gdm.xml:4302(synopsis) -#, no-wrap -msgid "CustomCommandIsPersistent[0-9]=" -msgstr "CustomCommandIsPersistent[0-9]=" - -#: C/gdm.xml:4303(para) -msgid "" -"Specifies if <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is " -"defined. [0-9] represents <filename>CustomCommand</filename> suffix and can " -"be an integer between 0 and 9." -msgstr "" -"Especifica si <filename>n-th</filename> \"Comando personalizado\" aparecerá " -"fuera del gestor de entrada, por ejemplo en el escritorio a trabés de los " -"diálogos de Salida/Apagado. Si no se especifica el valor predeterminado es " -"«false». Esta opción sólo es válida si el <filename>CustomCommand</filename> " -"correspondiente está definido. [0-9] representa el sufijo " -"<filename>CustomCommand</filename> y puede ser un entero entre 0 y 9." - -#: C/gdm.xml:4317(term) -msgid "CustomCommandLabel[0-9]" -msgstr "CustomCommandLabel[0-9]" - -#: C/gdm.xml:4319(synopsis) -#, no-wrap -msgid "CustomCommandLabel[0-9]=" -msgstr "CustomCommandLabel[0-9]=" - -#: C/gdm.xml:4320(para) -msgid "" -"Specifies the stock label that will be displayed on the <filename>n-th</" -"filename> \"Custom Command\" buttons and menu items. If not specified the " -"default value is \"Custom_[0-9]\". This option is only valid if " -"corresponding <filename>CustomCommand</filename> is defined. [0-9] " -"represents <filename>CustomCommand</filename> suffix and can be an integer " -"between 0 and 9. This option can't contain any semicolon characters (i.e. \";" -"\")." -msgstr "" -"Especifica la etiqueta de stock que se mostrará en los botones y menús " -"<filename>n-th</filename> del \"Comando personalizado\". Si no se especifica " -"el valor predeterminado, es \"Custom_[0-9\". Esta opción sólo es válida si " -"está definido al correspondiente <filename>CustomCommand</filename>. [0-9] " -"representa el sufijo del <filename>CustomCommand</filename> y puede ser un " -"entero entre 0 y 9. Esta opción no puede contener ningun carácter punto y " -"coma (\";\")." - -#: C/gdm.xml:4334(term) -msgid "CustomCommandLRLabel[0-9]" -msgstr "CustomCommandLRLabel[0-9]" - -#: C/gdm.xml:4336(synopsis) -#, no-wrap -msgid "CustomCommandLRLabel[0-9]=" -msgstr "CustomCommandLRLabel[0-9]=" - -#: C/gdm.xml:4337(para) -msgid "" -"Specifies the stock label that will be displayed on the <filename>n-th</" -"filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] " -"represents <filename>CustomCommand</filename> suffix and can be an integer " -"between 0 and 9." -msgstr "" - -#: C/gdm.xml:4351(term) -msgid "CustomCommandNoRestart[0-9]" -msgstr "CustomCommandNoRestart[0-9]" - -#: C/gdm.xml:4353(synopsis) -#, no-wrap -msgid "CustomCommandNoRestart[0-9]=" -msgstr "CustomCommandNoRestart[0-9]=" - -#: C/gdm.xml:4354(para) -msgid "" -"Specifies if gdm will be stopped/restarted once <filename>n-th</filename> " -"\"Custom Command\" has been executed. If not specified the default value is " -"\"false\". This option is only valid if corresponding " -"<filename>CustomCommand</filename> is defined. [0-9] represents " -"<filename>CustomCommand</filename> suffix and can be an integer between 0 " -"and 9. In addition when corresponding <filename>CustomCommandIsPersistent</" -"filename> is set to true, setting CustomCommandNoRestart to false will place " -"corresponding <filename>CustomCommand</filename> in the Shut Down dialog set " -"of actions, setting it to true will place corresponding " -"<filename>CustomCommand</filename> in the Log Out dialog set of actions." -msgstr "" - -#: C/gdm.xml:4374(term) -msgid "CustomCommandText[0-9]" -msgstr "CustomCommandText[0-9]" - -#: C/gdm.xml:4376(synopsis) -#, no-wrap -msgid "CustomCommandText[0-9]=" -msgstr "CustomCommandText[0-9]=" - -#: C/gdm.xml:4377(para) -msgid "" -"Specifies the message that will be displayed on the warning dialog box once " -"<filename>n-th</filename> \"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 " -"<filename>CustomCommand</filename> is defined. [0-9] represents " -"<filename>CustomCommand</filename> suffix and can be an integer between 0 " -"and 9." -msgstr "" - -#: C/gdm.xml:4391(term) -msgid "CustomCommandTooltip[0-9]" -msgstr "CustomCommandTooltip[0-9]" - -#: C/gdm.xml:4393(synopsis) -#, no-wrap -msgid "CustomCommandTooltip[0-9]=" -msgstr "CustomCommandTooltip[0-9]=" - -#: C/gdm.xml:4394(para) -msgid "" -"Specifies the message that will be displayed on tooltips for <filename>n-th</" -"filename> \"Custom Command\" entries. If not specified the default value is " -"\"Execute custom command [0-9]\". This option is only valid if corresponding " -"<filename>CustomCommand</filename> is defined. [0-9] represents " -"<filename>CustomCommand</filename> suffix and can be an integer between 0 " -"and 9." -msgstr "" - -#: C/gdm.xml:4409(title) -msgid "X Server Definitions" -msgstr "Definiciones del servidor X" - -#: C/gdm.xml:4411(para) -msgid "" -"GDM needs to be provided with information about each X servers that will be " -"used. You can have as many different definitions as you wish, each " -"identified with a unique name. The name <filename>Standard</filename> is " -"required. If you do not specify this server, GDM will assume default values " -"for a 'Standard' server and the path given by <filename>daemon/" -"StandardXServer</filename>. <filename>Standard</filename> is used as the " -"default, in situations when no other server has been defined." -msgstr "" - -#: C/gdm.xml:4422(para) -msgid "" -"Servers are defined by sections named <filename>server-</filename> 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, <filename>server-</" -"filename> sections in the <filename><etc>/gdm/custom.conf</filename> " -"file override values in the <filename><share>/gdm/defaults.conf</" -"filename> file. In other words, if a <filename>server-Standard</filename> " -"section is defined in <filename><etc>/gdm/custom.conf</filename>, then " -"that will be used and the section in the <filename><share>/gdm/" -"defaults.conf</filename> file will be ignored." -msgstr "" - -#: C/gdm.xml:4440(title) -msgid "[server-Standard]" -msgstr "[server-Standard]" - -#: C/gdm.xml:4443(term) -msgid "name" -msgstr "nombre" - -#: C/gdm.xml:4445(synopsis) -#, no-wrap -msgid "name=Standard server" -msgstr "name=Standard server" - -#: C/gdm.xml:4446(para) -msgid "The name that will be displayed to the user." -msgstr "El nombre que se mostrará al usuario." - -#: C/gdm.xml:4453(term) -msgid "command" -msgstr "command" - -#: C/gdm.xml:4455(synopsis) -#, no-wrap -msgid "command=/path/to/X" -msgstr "command=/path/to/X" - -#: C/gdm.xml:4456(para) -msgid "" -"The command to execute, with full path to the binary of the X server, and " -"any extra arguments needed. Normally it is not necessary to add a <filename>-" -"nolisten tcp</filename> argument since the addition of this argument is " -"controlled by the <filename>DisallowTCP</filename> GDM configuration option." -msgstr "" - -#: C/gdm.xml:4467(term) -msgid "flexible" -msgstr "flexible" - -#: C/gdm.xml:4469(synopsis) -#, no-wrap -msgid "flexible=true" -msgstr "flexible=true" - -#: C/gdm.xml:4470(para) -msgid "" -"Indicates if this server is available as a choice when a user wishes to run " -"a flexible, on demand server." -msgstr "" -"Indica si este servidor está disponible como una selección cuando un usuario " -"desea ejecutar un servidor flexible, bajo demanda." - -#: C/gdm.xml:4478(term) -msgid "handled" -msgstr "handled" - -#: C/gdm.xml:4480(synopsis) -#, no-wrap -msgid "handled=true" -msgstr "handled=true" - -#: C/gdm.xml:4481(para) -msgid "" -"Indicates that GDM should run the login window on this server and allow a " -"user to log in. If set to false, then GDM will just run this server and wait " -"for it to terminate. This can be useful to run an X terminal using GDM. When " -"this is done you should normally also add <filename>-terminate</filename> to " -"the command line of the server to make the server terminate after each " -"session. Otherwise the control of the slave will never come back to GDM and, " -"for example, soft restarts won't work. This is because GDM assumes there is " -"a login in progress for the entire time this server is active." -msgstr "" - -#: C/gdm.xml:4497(term) -msgid "chooser" -msgstr "chooser" - -#: C/gdm.xml:4499(synopsis) -#, no-wrap -msgid "chooser=false" -msgstr "chooser=false" - -#: C/gdm.xml:4500(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 "" -"Indica que GDM debería ejecutar en lugar de una ventana de entrada, un " -"selector en esta ventana y permitir al usuario elegir en qué servidor " -"iniciar sesión." - -#: C/gdm.xml:4509(term) -msgid "priority" -msgstr "priority" - -#: C/gdm.xml:4511(synopsis) -#, no-wrap -msgid "priority=0" -msgstr "priority=0" - -#: C/gdm.xml:4512(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 "" -"Indica que el servidor X debería ser iniciado en una prioridad de proceso " -"diferente. los valores pueden ser cualquier valor entero aceptado por la " -"función setpriority de la biblioteca de C. (normalmente entre -20 y 20) con " -"0 siendo el valor predeterminado. Para aplicaciones altamente interactivas, -" -"5 arroja buenas respuestas. El valor predeterminado es 0 y la función " -"setpriority no se llama si el valor es 0." - -#: C/gdm.xml:4527(title) -msgid "Attached DISPLAY Configuration" -msgstr "Configuración de la pantalla local" - -#: C/gdm.xml:4529(para) -msgid "" -"The attached (also known as local or 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 attached " -"displays that are managed as you wish. Typically each display is associated " -"with a real display. On a typical single-display machine this section would " -"only contain one key <filename>0</filename> that corresponds to DISPLAY " -"<filename>:0</filename>." -msgstr "" - -#: C/gdm.xml:4540(para) -msgid "" -"The GUI configuration program allows users to edit the attached display " -"configuration defined in the GDM configuration files and allows the user to " -"add or delete entries. Like normal configuration options, the <filename>" -"[servers]</filename> section in the <filename><etc>/gdm/custom.conf</" -"filename> file overrides values in the <filename><share>/gdm/defaults." -"conf</filename> file." -msgstr "" - -#: C/gdm.xml:4551(title) -msgid "[servers]" -msgstr "[servers]" - -#: C/gdm.xml:4554(term) -msgid "<display number>" -msgstr "<display number>" - -#: C/gdm.xml:4556(synopsis) -#, no-wrap -msgid "0=Standard [device=/dev/foo]" -msgstr "0=Standard [device=/dev/foo]" - -#: C/gdm.xml:4558(para) -msgid "" -"The key cooresponds to the DISPLAY to be managed, so that key <filename>0</" -"filename> cooresponds to DISPLAY <filename>:0</filename>. On a multi-display " -"machine you can configure GDM to manage a login program on other displays by " -"adding additional keys. For example, adding key <filename>1</filename> would " -"cause GDM to manage DISPLAY <filename>:1</filename>." -msgstr "" - -#: C/gdm.xml:4568(para) -msgid "" -"The first word of the value corresponds to a X server definition in the \"X " -"Server Definitions\" section of the configuration file. For example, the " -"following entry means that DISPLAY <filename>:0</filename> will start an X " -"server as defined in the <filename>[server-Standard]</filename> section:" -msgstr "" - -#: C/gdm.xml:4577(screen) -#, no-wrap -msgid "" -"\n" -"[servers]\n" -"0=Standard\n" -msgstr "" -"\n" -"[servers]\n" -"0=Standard\n" - -#: C/gdm.xml:4582(para) -msgid "" -"The first word of the value can also be set to the string \"inactive\" to " -"indicate that this DISPLAY should not be 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:4590(para) -msgid "" -"The optional device argument is used to specify the device that is " -"associated with the DISPLAY. When using Virtual Terminals (VT), this value " -"is ignored and GDM will use the correct device name associated with the VT. " -"If not using VT, then GDM will use the value specified by this optional " -"argument. If the device argument is not defined, then GDM will use the " -"default setting for attached displays defined in the " -"<filename>UtmpLineAttached</filename> configuration section. For the main " -"display (typically DISPLAY <filename>:0</filename>), <filename>/dev/console</" -"filename> is a reasonable value. For other displays it is probably best to " -"not include this argument unless you know the specific device associated " -"with the DISPLAY. The device value can contain \"%d\" which is translated to " -"the DISPLAY value or \"%h\" which is translated to the hostname." -msgstr "" - -#: C/gdm.xml:4614(title) -msgid "Per User Configuration" -msgstr "Configuración por usuario" - -#: C/gdm.xml:4616(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 <filename>UserMaxFile</filename> 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 "" -"Hay algunos ajustes de configuración por usuario que controlan cómo se " -"comporta GDM. GDM es bastante estricto con el propietario y los permisos de " -"los archivos de usuario a los que accede, e ignorará los archivos si no " -"pertenecen al usuario o tienen permiso de escritura para el grupo o para " -"todos. Ignorará el usuario si la carpeta personal del usuario ($HOME) no " -"pertenece al usuario o si la carpeta $HOME tiene permiso de escritura para " -"el grupo o para todos. Los archivos deben ser además más pequeños que el " -"valor <filename>UserMaxFile</filename> tal como se define en la " -"configuración de GDM. Si parece que GDM no está accediendo apropiadamente a " -"los ajustes de configuración del usuario, el problema se debe la mayoría de " -"las veces a que una de estas comprobaciones falla." - -#: C/gdm.xml:4630(para) -msgid "" -"First there is the <filename>~/.dmrc</filename> file. In theory this file " -"should be shared between GDM and KDM, so users only have to configure things " -"once. This is a standard <filename>.ini</filename> style configuration file. " -"It has one section called <filename>[Desktop]</filename> which has two keys: " -"<filename>Session</filename> and <filename>Language</filename>." -msgstr "" -"Primero está el archivo <filename>~/.dmrc</filename>. En teoría este archivo " -"debería ser compartido entre GDM y KDM, así que los usuarios sólo tienen que " -"configurar las cosas una vez. Esto es un archivo de configuración de estilo " -"<filename>.ini</filename> estándar. Tiene una sección llamada <filename>" -"[Desktop]</filename> que tiene dos claves: <filename>Session</filename> y " -"<filename>Language</filename>." - -#: C/gdm.xml:4639(para) -msgid "" -"The <filename>Session</filename> key specifies the basename of the session " -"<filename>.desktop</filename> file that the user wishes to normally use " -"(without the <filename>.desktop</filename> extension, in other words). The " -"<filename>Language</filename> key specifies the language that the user " -"wishes to use by default. If either of these keys is missing, the system " -"default is used. The file would normally look as follows:" -msgstr "" -"La clave <filename>Session</filename> especifica el nombre base del archivo " -"<filename>.desktop</filename> de sesión que el usuario quiere usar " -"normalmente (sin la extensión <filename>.desktop</filename>, en otras " -"palabras). La clave <filename>Language</filename> especifica el idioma que " -"el usuario quiere usar por omisión. Si cualquiera de estas dos claves falta, " -"se usa el predeterminado del sistema. El archivo normalmente tiene la " -"apariencia siguiente:" - -#: C/gdm.xml:4649(screen) -#, no-wrap -msgid "" -"\n" -"[Desktop]\n" -"Session=gnome\n" -"Language=cs_CZ.UTF-8\n" -msgstr "" -"\n" -"[Desktop]\n" -"Session=gnome\n" -"Language=es_ES.UTF-8\n" - -#: C/gdm.xml:4655(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 "" -"Normalmente GDM escribirá este archivo cuando el usuario entre por primera " -"vez, y lo reescribirá si el usuario escoge cambiar su valor predeterminado " -"en una entrada subsiguiente." - -#: C/gdm.xml:4661(para) -msgid "" -"If the GDM Face Browser is turned on, then the file <filename>$HOME/.face</" -"filename> 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 " -"<filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> " -"values defined in the GDM configuration or it will be ignored. Users can run " -"the <command>gdmphotosetup</command> program to specify a face image and it " -"will copy the file to the <filename>$HOME/.face</filename> location and " -"scale it so its longest dimension is not larger than the " -"<filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> " -"values. <command>gdmphotosetup</command> takes care to not change the aspect " -"ratio of the image." -msgstr "" -"Si está activado el visor de rostros, entonces se accede al archivo " -"<filename>$HOME/.face</filename>. Este archivo debería ser una imagen " -"estándar que GTK+ pueda leer, como PNG o JPEG. Además debería ser más " -"pequeña que los valores <filename>MaxIconWidth</filename> y " -"<filename>MaxIconHeight</filename> definidos en la configuración de GDM o " -"será ignorada. Los usuarios pueden ejecutar el comando " -"<command>gdmphotosetup</command> para especificar una imagen para el rostro " -"y se copiará el archivo al lugar <filename>$HOME/.face</filename> " -"escalándose para que su dimensión no sea mayor que los valores " -"<filename>MaxIconWidth</filename> o <filename>MaxIconHeight</filename>. " -"<command>gdmphotosetup</command> tiene cuidado de no cambiar las " -"proporciones de la imagen." - -#: C/gdm.xml:4676(para) -msgid "" -"Face images can also be placed in the global face directory, which is " -"specified by the <filename>GlobalFaceDir</filename> configuration option " -"( normally <filename><share>/pixmaps/faces/</filename>) and the " -"filename should be the name of the user, optionally with a <filename>.png</" -"filename>, <filename>.jpg</filename>, etc. appended." -msgstr "" -"Las imágenes de rostros pueden colocarse en el directorio global de rostros, " -"que se especifica por la opción de configuración <filename>GlobalFaceDir</" -"filename> (normalmente <filename><share>/pixmaps/faces/</filename>) y " -"el nombre del archivo debería ser el nombre del usuario, opcionalmente con " -"un <filename>.png</filename>, etc. agregado. " - -#: C/gdm.xml:4687(title) -msgid "Controlling GDM" -msgstr "Controlar GDM" - -#: C/gdm.xml:4689(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 "" -"Puede controlar el comportamiento de GDM durante la ejecución de varias " -"formas diferentes. Puede o ejecutar ciertos comandos, o puede hablar con GDM " -"usando un protocolo de sockets UNIX, o un protocolo FIFO." - -#: C/gdm.xml:4696(title) -msgid "Commands" -msgstr "Comandos" - -#: C/gdm.xml:4698(para) -msgid "" -"To stop GDM, you can either send the TERM signal to the main daemon or run " -"the <command>gdm-stop</command> command which is in the <filename><" -"sbin>/</filename> directory. To restart GDM, you can either send the HUP " -"signal to the main daemon or run the <command>gdm-restart</command> command " -"which is also in the <filename><sbin>/</filename> 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 <command>gdm-safe-" -"restart</command> command which is in the <filename><sbin>/</filename> " -"directory as well." -msgstr "" -"Para parar GDM, puede o bien enviar la señal TERM al demonio principal o " -"ejecutar el comando <command>gdm-stop</command> que está en el directorio " -"<filename>/sbin</filename>. Para reiniciar GDM, puede o bien enviar la señal " -"HUP al demonio principal o ejecutar el comando <command>gdm-restart</" -"command> que también está en el directorio <filename>/sbin</filename>. Para " -"reiniciar GDM paro sólo después de que todos los usuarios hayan salido de su " -"sesión puede o bien enviar la señal USR1 al demonio principal o ejecutar el " -"comando <command>gdm-safe-restart</command> que está en el directorio " -"<filename>/sbin</filename> también." - -#: C/gdm.xml:4711(para) -msgid "" -"The <command>gdmflexiserver</command> 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 " -"<command>gdmflexiserver</command> 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 <command>gdmflexiserver --help</" -"command> to get a listing of possible options." -msgstr "" -"El comando <command>gdmflexiserver</command> se puede usar para iniciar una " -"plantalla flexible (por demanda) si su sistema soporta terminales virtuales. " -"Este comando bloquea normalmente la sesión actual con un salvapantallas así " -"que el usuario puede ausentarse con seguridad del equipo y dejar a alguien " -"más entrar. Si se inician más de dos pantallas flexibles " -"<command>gdmflexiserver</command> mostrará un diálogo emergente permitiendo " -"al usuario sleccionar qué sesión continuar. Al salir de la sesión el sistema " -"retornará al terminal virtual anterior. Ejecute <command>gdmflexiserver --" -"help</command> para obtener un listado de opciones posibles." - -#: C/gdm.xml:4727(title) -msgid "The FIFO protocol" -msgstr "El protocolo FIFO" - -#: C/gdm.xml:4729(para) -msgid "" -"GDM also provides a FIFO called <filename>.gdmfifo</filename> in the " -"<filename>ServAuthDir</filename> directory (usually <filename><var>/" -"gdm/.gdmfifo</filename>). 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:4740(para) -msgid "" -"Full and up to date documentation of the commands and their use is contained " -"in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look " -"for the defines starting with <filename>GDM_SOP_</filename>. The commands " -"which require the pid of the slave as an argument are the ones that are " -"really used for internal communication of the slave with the master and " -"should not be used." -msgstr "" - -#: C/gdm.xml:4752(title) -msgid "Socket Protocol" -msgstr "El protocolo socket" - -#: C/gdm.xml:4754(para) -msgid "" -"GDM provides a unix domain socket for communication at <filename>/tmp/." -"gdm_socket</filename>. 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 <command>gdmflexiserver</" -"command> command uses this protocol, for example, to launch flexible (on-" -"demand) displays." -msgstr "" -"GDM proporciona un socket de dominio unix para comunicación en <filename>/" -"tmp/.gdm_socket</filename>. Usando éste puede comprobar si GDM se está " -"ejecutando, la versión del demonio, las pantallas actuales que se están " -"ejecutando y quién ha entrado en ellas, y si GDM soporta en su sistema " -"operativo, además los terminales virtuales de todas las entradas por " -"consola. El comando <command>gdmflexiserver</command> usa este protocole, " -"por ejemplo, para lanzar pantallas flexibles (por demanda)." - -#: C/gdm.xml:4764(para) -msgid "gdmflexiserver accepts the following commands with the --command option:" -msgstr "gdmflexiserver acepta los comandos siguientes con la opción --command:" - -#: C/gdm.xml:4769(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 "" -"\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" - -#: C/gdm.xml:4799(para) -msgid "" -"These are described in detail below, including required arguments, response " -"format, and return codes." -msgstr "" -"Estos se describen en detalle debajo, incluyendo los argumentos requeridos, " -"formato de respuesta, y códigos de retorno." - -#: C/gdm.xml:4805(title) -msgid "ADD_DYNAMIC_DISPLAY" -msgstr "ADD_DYNAMIC_DISPLAY" - -#: C/gdm.xml:4806(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 "" -"\n" -"ADD_DYNAMIC_DISPLAY: Crea una nueva definición de servidor que\n" -" se ejecutará en el visor especificado,\n" -" dejándolo en estado DISPLAY_CONFIG.\n" -"Suportado desde: 2.8.0.0\n" -"Argumentos: <visor en el que ejecutar>=<servidor>\n" -" Donde <servidor> es o una configuración nombrada en\n" -" la configuración de GDM o un nombre de comando literal.\n" -"Respuestas:\n" -" OK <visor>\n" -" ERROR <número de error> <descripción del error en inglés>\n" -" 0 = No implementado\n" -" 2 = Visor existente\n" -" 3 = Falta la cadena del servidor\n" -" 4 = Fallo al iniciar el visor\n" -" 100 = No autenticado\n" -" 200 = Visores dinámicos no permitidos\n" -" 999 = Error desconocido\n" - -#: C/gdm.xml:4828(title) -msgid "ALL_SERVERS" -msgstr "ALL_SERVERS" - -#: C/gdm.xml:4829(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:4852(title) -msgid "ATTACHED_SERVERS" -msgstr "ATTACHED_SERVERS" - -#: C/gdm.xml:4853(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:4886(title) -msgid "AUTH_LOCAL" -msgstr "AUTH_LOCAL" - -#: C/gdm.xml:4887(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 into attached displays, and here GDM\n" -" assumes only users logged in from GDM. They must\n" -" pass the xauth MIT-MAGIC-COOKIE-1 that they were\n" -" passed 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:4917(title) -msgid "CLOSE" -msgstr "CLOSE" - -#: C/gdm.xml:4918(screen) -#, no-wrap -msgid "" -"\n" -"CLOSE: Close sockets connection\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers: None\n" -msgstr "" -"\n" -"CLOSE: Cierra la conexión de sockets\n" -"Supportado desde: 2.2.4.0\n" -"Argumentos: Ninguno\n" -"Responde: Ninguno\n" - -#: C/gdm.xml:4927(title) -msgid "FLEXI_XNEST" -msgstr "FLEXI_XNEST" - -#: C/gdm.xml:4928(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:4967(title) -msgid "FLEXI_XNEST_USER" -msgstr "FLEXI_XNEST_USER" - -#: C/gdm.xml:4968(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 "" -"\n" -"FLEXI_XNEST_USER: Inicia una nueva pantalla flexible e inicializa\n" -" la interfaz de entrada con el usuario proporcionado.\n" -"Nota: Esta es una variante del comando FLEXI_XNETS.\n" -"Nota: La cookie debería ser MIT-MAGIC-COOKIE-1,\n" -" la primera que GDM puede encontrar en el archivo\n" -" XAUTHORITY para esta pantalla. Si eso no es lo que\n" -" usa, debería fenerar una primero. La cookie\n" -" debería estar en formato hexadecimal.\n" -"Suportado desde: 2.17.7 \n" -"Argumentos: <nombre de usuario> <pantalla en la que ejecutarse>\n" -"<uid del usuario que realizó la petición> <cookiexauth para la pantalla>\n" -"<archivo xauth>\n" -"Respuestas:\n" -" OK <pantalla>\n" -" ERROR <número de error> <descripción del error en inglés>\n" -" 0 = No implementado\n" -" 1 = No hay más servidores flexibles\n" -" 2 = Errores de inicio\n" -" 3 = Fallo en las X\n" -" 4 = X demasiado ocupadas\n" -" 5 = Xnest no se pudo conectar\n" -" 6 = No existe el binario del servidor\n" -" 100 = No autenticado\n" -" 200 = Demasiados mensajes\n" -" 999 = Error desconocido\n" - -#: C/gdm.xml:4997(title) -msgid "FLEXI_XSERVER" -msgstr "FLEXI_XSERVER" - -#: C/gdm.xml:4998(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:5020(title) -msgid "FLEXI_XSERVER_USER" -msgstr "FLEXI_XSERVER_USER" - -#: C/gdm.xml:5021(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 "" -"\n" -"FLEXI_XSERVER_USER: Inicia una nueva pantalla flexible e inicializa\n" -" la interfaz de entrada con el usuario proporcionado.\n" -" Sólo soportado para conexiones a través de AUTH_LOCAL\n" -"Suportado desde: 2.17.7 \n" -"Argumentos: <nombre de usuario>=<tipo de servidor x>\n" -" Si no se especifica un tipo de servidor, se iniciará el servidor X estándar\n" -"Respuestas:\n" -" OK <pantalla>\n" -" ERROR <número de error> <descripción del error en inglés>\n" -" 0 = No implementado\n" -" 1 = No hay más servidores flexibles\n" -" 2 = Errores de inicio\n" -" 3 = Fallo en las X\n" -" 4 = X demasiado ocupadas\n" -" 100 = No autenticado\n" -" 200 = Demasiados mensajes\n" -" 999 = Error desconocido\n" - -#: C/gdm.xml:5044(title) -msgid "GET_CONFIG" -msgstr "GET_CONFIG" - -#: C/gdm.xml:5045(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:5069(title) -msgid "GET_CONFIG_FILE" -msgstr "GET_CONFIG_FILE" - -#: C/gdm.xml:5070(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:5087(title) -msgid "GET_CUSTOM_CONFIG_FILE" -msgstr "GET_CUSTOM_CONFIG_FILE" - -#: C/gdm.xml:5088(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:5104(title) -msgid "GET_SERVER_DETAILS" -msgstr "GET_SERVER_DETAILS" - -#: C/gdm.xml:5105(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:5134(title) -msgid "GET_SERVER_LIST" -msgstr "GET_SERVER_LIST" - -#: C/gdm.xml:5135(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:5151(title) -msgid "GREETERPIDS" -msgstr "GREETERPIDS" - -#: C/gdm.xml:5152(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:5168(title) -msgid "QUERY_LOGOUT_ACTION" -msgstr "QUERY_LOGOUT_ACTION" - -#: C/gdm.xml:5169(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:5191(title) -msgid "QUERY_CUSTOM_CMD_LABELS" -msgstr "QUERY_CUSTOM_CMD_LABELS" - -#: C/gdm.xml:5192(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:5213(title) -msgid "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" -msgstr "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" - -#: C/gdm.xml:5214(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:5235(title) -msgid "QUERY_VT" -msgstr "QUERY_VT" - -#: C/gdm.xml:5236(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:5259(title) -msgid "RELEASE_DYNAMIC_DISPLAYS" -msgstr "RELEASE_DYNAMIC_DISPLAYS" - -#: C/gdm.xml:5260(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:5277(title) -msgid "REMOVE_DYNAMIC_DISPLAY" -msgstr "REMOVE_DYNAMIC_DISPLAY" - -#: C/gdm.xml:5278(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:5295(title) -msgid "SERVER_BUSY" -msgstr "SERVER_BUSY" - -#: C/gdm.xml:5296(screen) -#, no-wrap -msgid "" -"\n" -"SERVER_BUSY: Returns true if half or more of the daemon's sockets\n" -" are busy, false otherwise. Used by slave programs\n" -" which want to ensure they do not overwhelm the \n" -" sever.\n" -"Supported since: 2.13.0.8\n" -"Arguments: None\n" -"Answers:\n" -" OK <value>\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:5313(title) -msgid "SET_LOGOUT_ACTION" -msgstr "SET_LOGOUT_ACTION" - -#: C/gdm.xml:5314(screen) -#, no-wrap -msgid "" -"\n" -"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -" slave process exits. 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:5337(title) -msgid "SET_SAFE_LOGOUT_ACTION" -msgstr "SET_SAFE_LOGOUT_ACTION" - -#: C/gdm.xml:5338(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:5368(title) -msgid "SET_VT" -msgstr "SET_VT" - -#: C/gdm.xml:5369(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:5390(title) -msgid "UPDATE_CONFIG" -msgstr "UPDATE_CONFIG" - -#: C/gdm.xml:5391(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:5467(title) -msgid "VERSION" -msgstr "VERSION" - -#: C/gdm.xml:5468(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:5485(title) -msgid "GDM Commands" -msgstr "Comandos de GDM" - -#: C/gdm.xml:5488(title) -msgid "GDM User Commands" -msgstr "Comandos de usuario de GDM" - -#: C/gdm.xml:5490(para) -msgid "" -"The GDM package provides the following different commands in " -"<filename>bindir</filename> intended to be used by the end-user:" -msgstr "" -"El paquete GDM proporciona los siguiente comandos diferentes en " -"<filename>bindir</filename> con la intención de que sean usados por el " -"usuario final:" - -#: C/gdm.xml:5496(title) -msgid "" -"<command>gdmXnestchooser</command> and <command>gdmXnest</command> Command " -"Line Options" -msgstr "" -"Opciones de línea de comandos de <command>gdmXnestchooser</command> y " -"<command>gdmXnest</command>" - -#: C/gdm.xml:5499(para) -msgid "" -"The <command>gdmXnestchooser</command> 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 <command>gdmXnestchooser somehost</command> will run " -"the XDMCP chooser from host <command>somehost</command> inside a nested X " -"server session. You can make this command do a direct query instead by " -"passing the <command>-d</command> option as well. In addition to the " -"following options, this command also supports standard GNOME options." -msgstr "" - -#: C/gdm.xml:5514(title) -msgid "<command>gdmXnestchooser</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmXnestchooser</command>" - -#: C/gdm.xml:5517(term) -msgid "-x, --xnest=STRING" -msgstr "-x, --xnest=STRING" - -#: C/gdm.xml:5519(para) -msgid "" -"Nested X server command line, default is defined by the <filename>Xnest</" -"filename> configuration option." -msgstr "" - -#: C/gdm.xml:5527(term) -msgid "-o, --xnest-extra-options=OPTIONS" -msgstr "-o, --xnest-extra-options=OPCIONES" - -#: C/gdm.xml:5529(para) -msgid "Extra options for nested X server, default is no options." -msgstr "Opciones extra para el servidor X anidado, lo predeterminado es sin opciones." - -#: C/gdm.xml:5536(term) -msgid "-n, --no-query" -msgstr "-n, --no-query" - -#: C/gdm.xml:5538(para) -msgid "Just run nested X server, no query (no chooser)" -msgstr "Tan sólo ejecutar el servidor X anidado, sin consulta (sin selector)" - -#: C/gdm.xml:5545(term) -msgid "-d, --direct" -msgstr "-d, --direct" - -#: C/gdm.xml:5547(para) -msgid "Do direct query instead of indirect (chooser)" -msgstr "Hace una consulta directa en lugar de indirecta (selector)" - -#: C/gdm.xml:5554(term) -msgid "-B, --broadcast" -msgstr "-B, --broadcast" - -#: C/gdm.xml:5556(para) -msgid "Run broadcast instead of indirect (chooser)" -msgstr "Ejecutar en difusión en vez de indirecto (selector)" - -#: C/gdm.xml:5563(term) -msgid "-b, --background" -msgstr "-b, --background" - -#: C/gdm.xml:5565(para) -msgid "Run in background" -msgstr "Ejecutar en segundo plano" - -#: C/gdm.xml:5572(term) -msgid "--no-gdm-check" -msgstr "--no-gdm-check" - -#: C/gdm.xml:5574(para) -msgid "Don't check for running GDM" -msgstr "No comprueba si hay un GDM funcionando" - -#: C/gdm.xml:5583(title) C/gdm.xml:5626(title) -msgid "<command>gdmflexichooser</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmflexichooser</command>" - -#: C/gdm.xml:5585(para) -msgid "" -"The <command>gdmflexiserver</command> 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:5592(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:5606(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:5613(para) -msgid "" -"The <command>gdmflexiserver --command</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:5619(para) -msgid "" -"In addition to the following options, <command>gdmflexiserver</command> also " -"supports standard GNOME options." -msgstr "" -"Además de las siguientes opciones, <command>gdmflexiserver</command> también " -"soporta las opciones estándar de GNOME." - -#: C/gdm.xml:5629(term) -msgid "-c, --command=COMMAND" -msgstr "-c, --command=COMANDO" - -#: C/gdm.xml:5631(para) -msgid "Send the specified protocol command to GDM" -msgstr "Enviar el comando de protocolo especificado a GDM" - -#: C/gdm.xml:5638(term) -msgid "-n, --xnest" -msgstr "-n, --xnest" - -#: C/gdm.xml:5640(para) -msgid "Start a flexible X display in Nested mode" -msgstr "Inicia una pantalla flexible X en modo anidado" - -#: C/gdm.xml:5647(term) -msgid "-l, --no-lock" -msgstr "-l, --no-lock" - -#: C/gdm.xml:5649(para) -msgid "Do not lock current screen" -msgstr "No bloquear la pantalla actual" - -#: C/gdm.xml:5656(term) -msgid "-d, --debug" -msgstr "-d, --debug" - -#: C/gdm.xml:5658(para) -msgid "" -"Turns on debugging output which gets sent to syslog. Same as turning on " -"debug in the configuration file." -msgstr "" -"Activar salida de depuración para enviarla a syslog. Lo mismo que cuadno se " -"activa la depuración en el archivo de configuración." - -#: C/gdm.xml:5666(term) -msgid "-a, --authenticate" -msgstr "-a, --authenticate" - -#: C/gdm.xml:5668(para) -msgid "Authenticate before running --command" -msgstr "Autenticar antes de ejecutar --command" - -#: C/gdm.xml:5675(term) -msgid "-s, --startnew" -msgstr "-s, --startnew" - -#: C/gdm.xml:5677(para) -msgid "" -"Starts a new flexible display without displaying a dialog asking the user if " -"they wish to continue any existing sessions." -msgstr "" -"Inicia un servidor flexible nuevo sin mostrar un diálogo preguntando al " -"usuario si quiere continuar cualquier sesión existente." - -#: C/gdm.xml:5688(title) C/gdm.xml:5715(title) -msgid "<command>gdmdynamic</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmdynamic</command>" - -#: C/gdm.xml:5690(para) -msgid "" -"<command>gdmdynamic</command> 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 " -"<command>gdmdynamic</command> command can be used to create a new display on " -"a particular display number, run all newly created displays, or remove a " -"display. The <command>gdmdynamic</command> 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:5707(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:5718(term) -msgid "-a display=server" -msgstr "-a display=server" - -#: C/gdm.xml:5720(para) -msgid "" -"Add a new display configuration, leaving it in the DISPLAY_CONFIG state. For " -"example, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a 3=/usr/" -"X11R6/bin/X -dev /dev/fb2\"</command>" -msgstr "" - -#: C/gdm.xml:5726(para) -msgid "" -"The display will not actually be started until the display is released by " -"calling <command>gdmdynamic</command> again with the -r option." -msgstr "" - -#: C/gdm.xml:5734(term) -msgid "-r" -msgstr "-r" - -#: C/gdm.xml:5736(para) -msgid "Release (run) all displays waiting in the DISPLAY_CONFIG state." -msgstr "" - -#: C/gdm.xml:5743(term) -msgid "-d display" -msgstr "-d display" - -#: C/gdm.xml:5745(para) -msgid "" -"Delete a display, killing the X server and purging the display " -"configuration. For example, \"-d 3\"." -msgstr "" - -#: C/gdm.xml:5753(term) -msgid "-l [pattern]" -msgstr "-l [patrón]" - -#: C/gdm.xml:5755(para) -msgid "" -"List displays via the ATTACHED_SERVERS <command>gdmflexiserver</command> " -"command. Without a pattern lists all attached displays. With a pattern will " -"match using glob characters '*', '?', and '[]'. For example: <command>\"-l " -"Standard*\"</command><command>\"-l *Xorg*\"</command>" -msgstr "" - -#: C/gdm.xml:5767(term) -msgid "-v" -msgstr "-v" - -#: C/gdm.xml:5769(para) -msgid "Verbose mode. Prints diagnostic messages. to GDM." -msgstr "" - -#: C/gdm.xml:5777(term) -msgid "-b" -msgstr "-b" - -#: C/gdm.xml:5779(para) -msgid "Background mode. Fork child to do the work and return immediately." -msgstr "" -"Modo en segundo plano. Bifurcar un hijo para hacer el trabajo y volver " -"inmediatamente." - -#: C/gdm.xml:5786(term) -msgid "-t RETRY" -msgstr "-t RETRY" - -#: C/gdm.xml:5788(para) -msgid "" -"If the daemon socket is busy, <command>gdmdynamic</command> will retry to " -"open the connection the specified RETRY number of times. Default value is 15." -msgstr "" - -#: C/gdm.xml:5797(term) -msgid "-s SLEEP" -msgstr "-s SLEEP" - -#: C/gdm.xml:5799(para) -msgid "" -"If the daemon socket is busy, <command>gdmdynamic</command> 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:5814(title) -msgid "<command>gdmphotosetup</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmphotosetup</command>" - -#: C/gdm.xml:5816(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 " -"<filename>~/.face</filename>. This command accepts standard GNOME options." -msgstr "" - -#: C/gdm.xml:5825(title) -msgid "<command>gdmthemetester</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmthemetester</command>" - -#: C/gdm.xml:5827(para) -msgid "" -"<command>gdmthemetester</command> 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. <command>gdmthemetester</" -"command> requires that the system support <command>gdmXnest</command>. Note " -"that themes can display differently depending on the theme's \"Show mode\". " -"<command>gdmthemetester</command> allows viewing the themes in different " -"modes via the environment option. Valid environment values and their " -"meanings follow: <screen>\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" -"</screen>" -msgstr "" -"<command>gdmthemetester</command> toma dos parámetros . El primero " -"especifica el entorno y el segundo parámetro especifica el nombre de la ruta " -"o el nombre de un tema para ver. Esta es una herramienta para ver un tema " -"fuera de GDM. Es útil para probar o ver temas. <command>gdmthemetester</" -"command> requiere que el sistema soporte <command>gdmXnest</command>. Note " -"que los temas se pueden mostrar de forma diferente dependiendo del «modo de " -"visualización» del tema . <command>gdmthemetester</command> permite ver los " -"temas en diferentes modos por por medio de la opción de entorno. Los valores " -"de entorno y su significado siguen: <screen>\n" -"console - En modo consola.\n" -"console-timed - En modo consola no flexible.\n" -"flexi - En modo flexible.\n" -"xdmcp - En modo remoto (XDMCP).\n" -"remote-flexi - En modo remoto (XDMCP) y modo flexible.\n" -"</screen>" - -#: C/gdm.xml:5853(title) -msgid "GDM Root User Commands" -msgstr "Comandos del administrador de GDM" - -#: C/gdm.xml:5855(para) -msgid "" -"The GDM package provides the following different commands in " -"<filename>sbindir</filename> intended to be used by the root user:" -msgstr "" -"El paquete GDM proporciona los siguientes comandos diferentes en " -"<filename>sbindir</filename> con la intención de que los use el usario root:" - -#: C/gdm.xml:5861(title) C/gdm.xml:5877(title) -msgid "<command>gdm</command> and <command>gdm-binary</command> Command Line Options" -msgstr "" -"Opciones de línea de comandos de <command>gdm</command> y <command>gdm-" -"binary</command>" - -#: C/gdm.xml:5864(para) -msgid "" -"The <command>gdm</command> command is really just a script which runs the " -"<command>gdm-binary</command>, passing along any options. Before launching " -"<command>gdm-binary</command>, the gdm wrapper script will source the " -"<filename><etc>/profile</filename> file to set the standard system " -"environment variables. In order to better support internationalization, it " -"will also set the LC_MESSAGES environment variable to LANG if neither " -"LC_MESSAGES or LC_ALL are set. If you really need to set some additional " -"environment before launching GDM, you can do so in this script." -msgstr "" -"El comando <command>gdm</command> es realmente sólo un script que ejecuta el " -"<command>gdm-binary</command>, pasando cualquier opción. Anted de lanzar " -"<command>gdm-binary</command>, el script de envoltura de gdm incluirá el " -"archivo <filename><etc>/profile</filename> para establecer las " -"variables de entorno estándar. Para soportar mejor la internacionalización, " -"establecerá la variable de entorno LC_MESSAGES a LANG si cualquiera de " -"LC_MESSAGES o LC_ALL está establecida. Si realmente necesita establecer " -"algún entorno adicional antes de lanzar GDM, puede hacer eso en este script." - -#: C/gdm.xml:5881(term) -msgid "--help" -msgstr "--help" - -#: C/gdm.xml:5883(para) -msgid "Gives a brief overview of the command line options." -msgstr "Da un breve resumen de las opciones de línea de comandos." - -#: C/gdm.xml:5890(term) -msgid "--nodaemon" -msgstr "--nodaemon" - -#: C/gdm.xml:5892(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 "" -"Si se especifica esta opción, entonces GDM no se bifurca a un segundo plano " -"cuando se ejecuta. Note que ya no puede usar la opción de un guión simple \"-" -"nodaemon\" para compatibilidad con otros gestores de pantallas." - -#: C/gdm.xml:5902(term) -msgid "--no-console" -msgstr "--no-console" - -#: C/gdm.xml:5904(para) -msgid "" -"Tell the daemon that it should not run anything on the console. This means " -"that none of the attached servers from the <filename>[servers]</filename> " -"section will be started, and the console will not be used for communicating " -"errors to the user. An empty <filename>[servers]</filename> section " -"automatically implies this option." -msgstr "" -"Indica al demonio que no debería ejecutar nada en la consola. Esto significa " -"que ninguno de los servidores locales de la sección <filename>[servers]</" -"filename> se iniciará, y que la consola no se usará para comunicar errores " -"al usuario. Una sección <filename>[servers]</filename> vacía automáticamente " -"implica esta opción." - -#: C/gdm.xml:5916(term) -msgid "--config=CONFIGFILE" -msgstr "--config=CONFIGFILE" - -#: C/gdm.xml:5918(para) -msgid "Specify an alternative configuration file." -msgstr "Especificar un archivo de configuración alternativo." - -#: C/gdm.xml:5925(term) -msgid "--preserve-ld-vars" -msgstr "--preserve-ld-vars" - -#: C/gdm.xml:5927(para) -msgid "" -"When clearing the environment internally, preserve all variables starting " -"with LD_. This is mostly for debugging purposes." -msgstr "" -"Al limpiar internamente el entorno, preservar todas las variables empezando " -"con LD_. Esto es principalmente para propósitos de depuración." - -#: C/gdm.xml:5935(term) -msgid "--version" -msgstr "--version" - -#: C/gdm.xml:5937(para) -msgid "Print the version of the GDM daemon." -msgstr "Imprime la versión del demonio GDM." - -#: C/gdm.xml:5944(term) -msgid "--wait-for-go" -msgstr "--wait-for-go" - -#: C/gdm.xml:5946(para) -msgid "" -"If started with this option, gdm will init, but only start the first " -"attached 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:5964(title) -msgid "<command>gdmsetup</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmsetup</command>" - -#: C/gdm.xml:5966(para) -msgid "" -"<command>gdmsetup</command> 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 <command>gdmsetup</command> 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 "" -"<command>gdmsetup</command> ejecuta una aplicación gráfica para modificar el " -"archivo de configuración de GDM. Normalmente en sistemas que soportan el " -"ayudante de usuario PAM, esto es para configurar que cuando ejecute " -"<command>gdmsetup</command> como un usuario ordinario, le pida primero su " -"contraseña de root antes de inciar. De otro modo esta aplicación sólo podría " -"ser ejecutada como root. Esta aplicación soporta las opciones estándar de " -"GNOME." - -#: C/gdm.xml:5978(title) -msgid "<command>gdm-restart</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdm-restart</command>" - -#: C/gdm.xml:5980(para) -msgid "" -"<command>gdm-restart</command> stops and restarts GDM by sending the GDM " -"daemon a HUP signal. This command will immediately terminate all sessions " -"and log out users currently logged in with GDM." -msgstr "" -"<command>gdm-restart</command> para y reinicia GDM enviando al demonio de " -"GDM una señal HUP. Este comando inmediatamente terminará todas las sesiones " -"y echará fuera a los usuarios que hayan entrado con GDM." - -#: C/gdm.xml:5988(title) -msgid "<command>gdm-safe-restart</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdm-safe-restart</command>" - -#: C/gdm.xml:5990(para) -msgid "" -"<command>gdm-safe-restart</command> stops and restarts GDM by sending the " -"GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out." -msgstr "" -"<command>gdm-safe-restart</command> para y reinicia GDM enviando al demonio " -"GDM una señal USR1. GDM re reiniciará tan pronto como todos los usuarios " -"salgan." - -#: C/gdm.xml:5998(title) -msgid "<command>gdm-stop</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdm-stop</command>" - -#: C/gdm.xml:6000(para) -msgid "" -"<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM " -"signal." -msgstr "<command>gdm-stop</command> para GDM enviando al demonio GDM una señal TERM" - -#: C/gdm.xml:6008(title) -msgid "GDM Internal Commands" -msgstr "Comandos internos de GDM" - -#: C/gdm.xml:6010(para) -msgid "" -"The GDM package provides the following different commands in " -"<filename>libexecdir</filename> intended to be used by the gdm daemon " -"process." -msgstr "" -"El paquete de GDM proporciona los siguientes comandos en " -"<filename>libexecdir</filename> con intención de que sean usados por el " -"proceso del demonio gdm." - -#: C/gdm.xml:6017(title) -msgid "" -"<command>gdmchooser</command> and <command>gdmlogin</command> Command Line " -"Options" -msgstr "" -"Opciones de línea de comandos de <command>gdmchooser</command> y " -"<command>gdmlogin</command>" - -#: C/gdm.xml:6020(para) -msgid "" -"The <command>gdmgreeter</command> and <command>gdmlogin</command> are two " -"different login applications, either can be used by GDM. " -"<command>gdmgreeter</command> is themeable with GDM themes while " -"<command>gdmlogin</command> is themable with GTK+ themes. These applications " -"are normally executed by the GDM daemon. Both commands support standard " -"GNOME options." -msgstr "" - -#: C/gdm.xml:6031(title) C/gdm.xml:6041(title) -msgid "<command>gdmchooser</command> Command Line Options" -msgstr "Opciones de línea de comandos de <command>gdmchooser</command>" - -#: C/gdm.xml:6033(para) -msgid "" -"The <command>gdmchooser</command> is the XDMCP chooser application. The " -"<command>gdmchooser</command> is normally executed by the GDM daemon. It " -"supports the following options for XDM compatibility. This command supports " -"standard GNOME options." -msgstr "" -"<command>gdmchooser</command> es la aplicación selectora XDMCP. Normalmente " -"el demonio de GDM ejecuta <command>gdmchooser</command>. Soporta las " -"siguientes opciones para compatibilidad con XDM. Este comando soporta las " -"opciones estándar de GNOME." - -#: C/gdm.xml:6044(term) -msgid "--xdmaddress=SOCKET" -msgstr "--xdmaddress=SOCKET" - -#: C/gdm.xml:6046(para) -msgid "Socket for XDM communication." -msgstr "Socket para comunicación XDM." - -#: C/gdm.xml:6053(term) -msgid "--clientaddress=ADDRESS" -msgstr "--clientaddress=DIRECCIÓN" - -#: C/gdm.xml:6055(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:6063(term) -msgid "--connectionType=TYPE" -msgstr "--connectionType=TIPO" - -#: C/gdm.xml:6065(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 "" -"Tipo de conexión que devolver en respuesta a XDM. Esta opción es para " -"ejecutar gdmchooser con XDM, no se usa dentro de GDM." - -#: C/gdm.xml:6075(command) -msgid "gdm-ssh-session" -msgstr "gdm-ssh-session" - -#: C/gdm.xml:6077(para) -msgid "" -"The <command>gdm-ssh-session</command> is normally executed by the GDM " -"daemon when starting a secure remote connection through ssh. It does not " -"take any options." -msgstr "" -"Normalmente el demonio de GDM ejecuta <command>gdm-ssh-session</command> al " -"iniciar una conexión remota segura a través de SSH. No toma ninguna opción." - -#: C/gdm.xml:6089(title) -msgid "Themed Greeter" -msgstr "Interfaz con temas" - -#: C/gdm.xml:6091(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 <ulink type=\"http\" url=\"http://art.gnome.org/themes/" -"gdm_greeter/\"> the theme website</ulink>." -msgstr "" -"Esta sección describe la creación de temas para el Interfaz con temas. Para " -"los ejemplos incluidos en las capturas, vea los temas estándar instalados y " -"los temas del <ulink type=\"http\" url=\"http://art.gnome.org/themes/" -"gdm_greeter/\">sitio web de temas</ulink>." - -#: C/gdm.xml:6100(title) -msgid "Theme Overview" -msgstr "Descripción de los temas" - -#: C/gdm.xml:6102(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 <filename><share>/gdm/themes/<theme_name></filename>. " -"Usually this would be under <filename>/usr/share</filename>. The theme " -"directory should contain a file called <filename>GdmGreeterTheme.desktop</" -"filename> which has similar format to other .desktop files and looks like:" -msgstr "" -"Los temas GDM se pueden hacer creando un archivo XML que siga la " -"especificación en gui/greeter/greeter.dtd. Los archivos de temas se " -"almacenan en el directorio <filename><share>/gdm/themes/<" -"theme_name></filename>. Usualmente esto debería estar bajo <filename>/usr/" -"share</filename>. El directorio del tema debería contener un archivo llamado " -"<filename>GdmGreeterTheme.desktop</filename> que tiene un formato similar a " -"otros archivos .desktop como la siguiente:" - -#: C/gdm.xml:6113(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 "" -"\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" - -#: C/gdm.xml:6124(para) -msgid "" -"The Name, Description, Author and Copyright fields can be translated just " -"like the other <filename>.desktop</filename>files. 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 "" -"Los campos del nombre, descripción, autor y copyright pueden traducirse como " -"otros archivos <filename>.desktop</filename>. Todos los archivos que se " -"mencionan deberían estar en el propio directorio de temas. El campo " -"Screenshot apunta a un archivo que debería ser una captura de 200x150 del " -"tema en acción (está bien no tener una, pero lo hace más agradable al " -"usuario). El campo Greeter apunta a un archivo xml que contiene " -"descripciones del tema. La descripción se dará más tarde." - -#: C/gdm.xml:6134(para) -msgid "" -"Once a theme is installed, it can be tested with the " -"<command>gdmthemetester</command> program. This program assumes that the X " -"server supports a nested server command. This command takes two arguments, " -"first the environment that should be used. The environment can be one of the " -"following values: console, console-timed, flexi, remote-flexi, or xdmcp. The " -"\"console\" option tests the theme as it would be shown on an attached " -"display. The \"console-timed\" option tests the theme as it would be shown " -"on an attached display with timed login enabled. The \"flexi\" option tests " -"the theme as it would be shown on an attached flexible display (such as " -"started via Xnest). Finally, the \"xdmcp\" option tests the theme as it " -"would be shown for remote XDMCP displays. The second argument is the theme " -"name. For example, to test how the circles theme would look in XDMP remote " -"display mode, you would run the following command:" -msgstr "" - -#: C/gdm.xml:6153(command) -msgid "gdmthemetester xdmcp circles" -msgstr "gdmthemetester xdmcp circles" - -#: C/gdm.xml:6156(para) -msgid "" -"When developing a theme, make sure to test all the environments, and make " -"sure to test how the caps lock warning looks by pressing the caps lock key. " -"Running <command>gdmthemetester</command> is also a good way to take " -"screenshots of GDM themes. Simply take a screenshot of the theme running in " -"the nested display window. This can be done in GNOME by focusing the nested " -"login window and pressing Alt-PrintScreen." -msgstr "" -"Asegúrese de probar todos los entornos con su tema, y asegúrese de probar " -"cómo se muestran las advertencias de pulsación de bloqueo mayúsculas. " -"Ejecutar <command>gdmthemetester</command> también es una buena manera de " -"tomar capturas de pantallas. Tan sólo tomar una captura de la ventana de " -"Xnest. Esto se puede hacer en GNOME enfocando la pantalla de Xnest y " -"pulsando Alt-ImprPant." - -#: C/gdm.xml:6165(para) -msgid "" -"Once a theme has been fully tested, then make a tarball that contains the " -"directory as it would be insatlled to the <filename><share>/gdm/" -"themes</filename> directory. This is the standard format for distributing " -"GDM themes." -msgstr "" - -#: C/gdm.xml:6174(title) -msgid "Detailed Description of Theme XML format" -msgstr "Descripción detallada del formato XML de temas" - -#: C/gdm.xml:6177(title) -msgid "greeter tag" -msgstr "etiqueta greeter" - -#: C/gdm.xml:6179(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 "" -"El formato de temas de GDM está especificado en XML contenido dentro de una " -"etiqueta <greeter>. Puede especificar un tema GTK+ para usarlo con " -"este tema usando el elemento gtk-theme en la etiqueta greeter tal como el " -"siguiente ejemplo:" - -#: C/gdm.xml:6186(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 "" -"\n" -"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" -"<!DOCTYPE greeter SYSTEM \"greeter.dtd\">\n" -"<greeter gtk-theme=\"Crux\">\n" -"[...]\n" -"</greeter>\n" - -#: C/gdm.xml:6194(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 "" -"Contenidos dentro de la etiqueta greeter pueden estar los nodos descritos en " -"las siguientes secciones de este documento. Algunos de estos nodos son " -"contenedores (nodos caja, nodos de elemento rectangular) que se pueden usar " -"para organizar cómo mostrar los nodos con los que el usuario ve e " -"interactura (como nodos de botón, mapa de píxeles y entrada de texto)." - -#: C/gdm.xml:6204(title) -msgid "Box Nodes" -msgstr "Nodos caja" - -#: C/gdm.xml:6206(para) -msgid "" -"Box nodes are container nodes for item nodes. Box nodes are specified as " -"follows: <screen>\n" -"<box orientation=\"alignment\" min-width=\"num\"\n" -"xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -"homogeneous=\"bool\">\n" -"</screen> 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 "" -"Los nodos caja son nodos contenedores para nodos de elementos. Los nodos " -"caja se especifican como sigue: <screen>\n" -"<box orientation=\"alignment\" min-width=\"num\"\n" -"xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -"homogeneous=\"bool\">\n" -"</screen> Donde \"num\" significa número y bool significa o \"true\" o " -"\"false\". El valor de alineación puede ser tanto \"horizontal\" como " -"\"vertical\". Si deja cualquier propiedad desactivada, se establecerá a cero " -"de forma predeterminada o a \"false\" en caso de \"homogeneous\" y \"vertical" -"\" para la orientación." - -#: C/gdm.xml:6222(para) -msgid "" -"If the box is homogeneous then the children are allocated equal amount of " -"space." -msgstr "" -"Si la caja es homogénea entonces los hijos se les reserva la misma cantidad " -"de espacio." - -#: C/gdm.xml:6227(para) -msgid "" -"The \"min-width\" must be specified in pixels. Obviously there is also a " -"corresponding \"min-height\" property as well." -msgstr "" -"El \"min-width\" debe especificarse en píxeles. Obviamente hay además una " -"propiedad correspondiente \"min-height\"." - -#: C/gdm.xml:6235(title) -msgid "Fixed Nodes" -msgstr "Nodos fijos" - -#: C/gdm.xml:6237(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: <screen>\n" -"<fixed>\n" -"</screen> Then you put other items with proper position nodes inside this." -msgstr "" - -#: C/gdm.xml:6248(para) -msgid "The \"toplevel\" node is really just like a fixed node." -msgstr "El nodo \"toplevel\" es realmente como un nodo fijo." - -#: C/gdm.xml:6254(title) -msgid "Item Nodes" -msgstr "Nodos de elemento" - -#: C/gdm.xml:6256(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 "" -"Un tema GDM se crea especificando una jerarquía de nodos de elementos y " -"cajas. Los nodos de elementos pueden tener el siguiente valor para el tipo:" - -#: C/gdm.xml:6264(term) -msgid "button" -msgstr "button" - -#: C/gdm.xml:6266(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 "" -"Un campo de botón. Este campo usa un botón GTK+. También es posible hacer un " -"elemento \"rect\" que actúe como un botón estableciendo su elemento button a " -"true. Sin embargo es mejor usar los botones GTK+ en los temas GDM debido a " -"que éstos son accesibles a los usuarios discapacitados. Además, los botones " -"GTK pueden tener tema. Esta característica está soportada en GDM 2.14.6 y " -"posteriores." - -#: C/gdm.xml:6278(term) -msgid "entry" -msgstr "entry" - -#: C/gdm.xml:6280(para) -msgid "Text entry field." -msgstr "Campo de entrada de texto." - -#: C/gdm.xml:6287(term) -msgid "label" -msgstr "label" - -#: C/gdm.xml:6289(para) -msgid "A text label. Must have a \"text\" node to specify the text." -msgstr "Una etiqueta de texto. Debe tener un nodo \"text\" para especificar el texto." - -#: C/gdm.xml:6297(term) -msgid "list" -msgstr "list" - -#: C/gdm.xml:6299(para) -msgid "" -"A face browser widget. Only useful if the face browser is enabled via the " -"configuration." -msgstr "" - -#: C/gdm.xml:6307(term) -msgid "pixmap" -msgstr "pixmap" - -#: C/gdm.xml:6309(para) -msgid "" -"An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, " -"etc...)" -msgstr "" -"Una imagen pixmap en un formato que gdk-pixbuf soporte como PNG, JPEG, Tiff, " -"etc...)" - -#: C/gdm.xml:6317(term) -msgid "rect" -msgstr "rect" - -#: C/gdm.xml:6319(para) -msgid "Rectangle." -msgstr "Rectángulo." - -#: C/gdm.xml:6326(term) -msgid "svg" -msgstr "svg" - -#: C/gdm.xml:6328(para) -msgid "Scaled Vector Graphic image." -msgstr "Imagen Scaled Vector Graphic." - -#: C/gdm.xml:6335(para) -msgid "" -"For example: <screen>\n" -"<item type=\"label\">\n" -"</screen> 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:6346(para) -msgid "Entry items can have id values as follows:" -msgstr "Los elementos de entradas pueden tener valores id como siguen:" - -#: C/gdm.xml:6352(term) -msgid "user-pw-entry" -msgstr "user-pw-entry" - -#: C/gdm.xml:6354(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:6363(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:6373(term) -msgid "session" -msgstr "session" - -#: C/gdm.xml:6375(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:6385(term) -msgid "language" -msgstr "language" - -#: C/gdm.xml:6387(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:6397(term) -msgid "userlist" -msgstr "userlist" - -#: C/gdm.xml:6399(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:6412(term) -msgid "userlist-rect" -msgstr "userlist-rect" - -#: C/gdm.xml:6414(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:6426(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:6433(para) -msgid "Label items can have id values as follows:" -msgstr "Los elementos de etiquetas pueden tener valores id como siguen:" - -#: C/gdm.xml:6439(term) -msgid "clock" -msgstr "clock" - -#: C/gdm.xml:6441(para) -msgid "Label that displays the date and time." -msgstr "Etiqueta que muesta la fecha y la hora." - -#: C/gdm.xml:6448(term) -msgid "pam-prompt" -msgstr "pam-prompt" - -#: C/gdm.xml:6450(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:6458(term) -msgid "pam-error" -msgstr "pam-error" - -#: C/gdm.xml:6460(para) -msgid "Label that displayst PAM/GDM error messages. Such as when user can't log in." -msgstr "" - -#: C/gdm.xml:6468(term) -msgid "pam-error-logo" -msgstr "pam-error-logo" - -#: C/gdm.xml:6470(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 "" -"Una imagen que se mostrará sólo cuando un mensaje pam-error se muestre. Esto " -"es útil para mostrar un icono «Atención», por ejemplo. Esta característica " -"está soportada en GDM 2.14.6 y posteriores." - -#: C/gdm.xml:6480(term) -msgid "pam-message" -msgstr "pam-message" - -#: C/gdm.xml:6482(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 "" -"Etiqueta que muestra el mensaje PAM. Éstos son mensajes que PAM/GDM da " -"acerca del estado de la cuenta, ayuda acerca de los prompts y otra " -"información." - -#: C/gdm.xml:6491(term) -msgid "timed-label" -msgstr "timed-label" - -#: C/gdm.xml:6493(para) -msgid "Label that displays timed login information." -msgstr "Etiqueta que muestra la información de la entrada temporizada." - -#: C/gdm.xml:6500(para) -msgid "Rectangles can have id values as follows:" -msgstr "Los rectángulos pueden tener valores id como los siguientes:" - -#: C/gdm.xml:6506(term) -msgid "caps-lock-warning" -msgstr "caps-lock-warning" - -#: C/gdm.xml:6508(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:6517(para) -msgid "" -"If an item is of type rect, the item can be a button. Buttons must also " -"include a \"button\" value as follows: <screen>\n" -"<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6525(para) -msgid "Possible values for button ids are as follows." -msgstr "Los valores posibles para los ids de los botones son los siguientes:" - -#: C/gdm.xml:6531(term) -msgid "chooser_button" -msgstr "chooser_button" - -#: C/gdm.xml:6533(para) -msgid "Runs the XDMCP chooser." -msgstr "Ejecuta el selector XDMCP." - -#: C/gdm.xml:6540(term) -msgid "config_button" -msgstr "config_button" - -#: C/gdm.xml:6542(para) -msgid "Runs the GDM configuration application." -msgstr "Ejecuta la aplicación de configuración de GDM." - -#: C/gdm.xml:6549(term) -msgid "custom_cmd_button[0-9]" -msgstr "custom_cmd_button[0-9]" - -#: C/gdm.xml:6551(para) -msgid "Runs the <filename>n-th</filename> custom command." -msgstr "Ejecuta el <filename>enésimo</filename> comando personalizado." - -#: C/gdm.xml:6558(term) -msgid "disconnect_button" -msgstr "disconnect_button" - -#: C/gdm.xml:6560(para) -msgid "Disconnect from remote session." -msgstr "Desconecta de una sesión remota." - -#: C/gdm.xml:6567(term) -msgid "language_button" -msgstr "language_button" - -#: C/gdm.xml:6569(para) -msgid "Displays the language selection dialog." -msgstr "Muestra el diálogo de selección del idioma." - -#: C/gdm.xml:6576(term) -msgid "halt_button" -msgstr "halt_button" - -#: C/gdm.xml:6578(para) -msgid "Halt (shuts down) the system." -msgstr "Detiene (apaga) el sistema." - -#: C/gdm.xml:6585(term) -msgid "reboot_button" -msgstr "reboot_button" - -#: C/gdm.xml:6587(para) -msgid "Restart the system." -msgstr "Reinicia el sistema." - -#: C/gdm.xml:6594(term) -msgid "session_button" -msgstr "session_button" - -#: C/gdm.xml:6596(para) -msgid "List and select from available sessions." -msgstr "Lista y selecciona las sesiones disponibles." - -#: C/gdm.xml:6603(term) -msgid "suspend_button" -msgstr "suspend_button" - -#: C/gdm.xml:6605(para) -msgid "Suspend the system." -msgstr "Suspender el sistema." - -#: C/gdm.xml:6612(term) -msgid "system_button" -msgstr "system_button" - -#: C/gdm.xml:6614(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 "" -"Realiza las opciones detener/reiniciar/suspender/etc (si están permitidas " -"por la configuración de GSM). Además permite al usuario ejecutar el " -"configurador si el usuario introduce la contraseña de root (otra vez si lo " -"permite la configuración de GDM). Esto está normalmente ahora etiquetado " -"como Acciones, y referido como el menú de Acciones." - -#: C/gdm.xml:6625(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:6638(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:6644(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:6651(para) -msgid "" -"If no item node has \"background\" property set, then the background is not " -"modified when greeter exits." -msgstr "" - -#: C/gdm.xml:6656(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:6665(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:6684(title) -msgid "Position Node" -msgstr "Nodo de posición" - -#: C/gdm.xml:6686(para) -msgid "" -"Each item can specify its position and size via the \"pos\" node. For " -"example: <screen>\n" -"<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" -"</screen>" -msgstr "" -"Cada elemento puede especificar su posición y tamaño por medio del nodo " -"\"pos\". Por ejemplo <screen>\n" -"<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" -"</screen>" - -#: C/gdm.xml:6694(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 "" -"Tanto la posición como el tamaño pueden darse en porcentaje y se tomará como " -"el porcentaje del tamaño del contenedor actual. Para los elementos de nivel " -"superior su porcentaje es respecto de la pantalla completa." - -#: C/gdm.xml:6700(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:6707(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: <screen>\n" -"<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6718(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:6724(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:6730(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:6737(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: <screen>\n" -"<item type=\"label\">\n" -"<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6753(title) -msgid "Show Node" -msgstr "Mostrar nodo" - -#: C/gdm.xml:6755(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:6761(para) -msgid "<filename>console</filename> - In console mode." -msgstr "<filename>console</filename> - En modo consola." - -#: C/gdm.xml:6764(para) -msgid "<filename>console-fixed</filename> - In console non-flexi mode." -msgstr "<filename>console-fixed</filename> - En modo consola no-flexible." - -#: C/gdm.xml:6767(para) -msgid "<filename>console-flexi</filename> - In console & flexi mode." -msgstr "<filename>console-flexi</filename> - En modo consola y modo flexible." - -#: C/gdm.xml:6770(para) -msgid "<filename>flexi</filename> - In flexi mode." -msgstr "<filename>flexi</filename> - En modo flexible." - -#: C/gdm.xml:6773(para) -msgid "<filename>remote</filename> - In remote mode." -msgstr "<filename>remote</filename> - En modo remoto." - -#: C/gdm.xml:6776(para) -msgid "<filename>remote-flexi</filename> - In remote & flexi mode." -msgstr "<filename>remote-flexi</filename> - En modo remoto y flexible." - -#: C/gdm.xml:6780(para) -msgid "" -"For example: <screen>\n" -"<show modes=\"flexi,remote\"/>\n" -"</screen>" -msgstr "" -"Por ejemplo: <screen>\n" -"<show modes=\"console\" type=\"system\"/>\n" -"</screen>" - -#: C/gdm.xml:6787(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:6793(para) -msgid "" -"<filename>chooser</filename>, if ChooserButton is set to \"true\" in the GDM " -"configuration." -msgstr "" -"<filename>chooser</filename>, si ChooserButton está puesto a «true» en la " -"configuración de GDM." - -#: C/gdm.xml:6797(para) -msgid "" -"<filename>config</filename>, if ConfigAvailable is set to \"true\" in the " -"GDM configuration." -msgstr "" -"<filename>configurar</filename>, si ConfigAvailable está puesto a «true» en " -"la configuración de GDM." - -#: C/gdm.xml:6801(para) -msgid "" -"<filename>custom_cmd[0-9]</filename>, if <filename>n-th</filename> " -"CustomCommand is specified in the GDM configuration." -msgstr "" -"<filename>comando_personalizado[0-9]</filename>, si el <filename>enésimo</" -"filename> comando personalizado está especificado en la configuración de GDM." - -#: C/gdm.xml:6805(para) -msgid "" -"<filename>halt</filename>, if HaltDaemon is specified in the GDM " -"configuration." -msgstr "" -"<filename>halt</filename>, si HaltDaemon está especificado en la " -"configuración de GDM." - -#: C/gdm.xml:6809(para) -msgid "" -"<filename>reboot</filename>, if RebootCommand is specified in the GDM " -"configuration." -msgstr "" -"<filename>reiniciar</filename>, si RebootCommand está especificado en la " -"configuración de GDM." - -#: C/gdm.xml:6813(para) -msgid "" -"<filename>suspend</filename>, if SuspendCommand is specified in the GDM " -"configuration." -msgstr "" -"<filename>suspend</filename>, si SuspendCommand está especificado en la " -"configuración de GDM." - -#: C/gdm.xml:6817(para) -msgid "" -"<filename>system</filename>, if SystemMenu is specified in the GDM " -"configuration." -msgstr "" -"<filename>system</filename>, si SystemMenu está especificado en la " -"configuración de GDM." - -#: C/gdm.xml:6821(para) -msgid "" -"<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in the " -"GDM configuration." -msgstr "" -"<filename>timed</filename>, si TimedLoginEnabled está puesto a \"true\" en " -"la configuración de GDM." - -#: C/gdm.xml:6826(para) -msgid "" -"For example: <screen>\n" -"<show modes=\"console\" type=\"system\"/>\n" -"</screen>" -msgstr "" -"Por ejemplo: <screen>\n" -"<show modes=\"console\" type=\"system\"/>\n" -"</screen>" - -#: C/gdm.xml:6833(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:6840(para) -msgid "" -"For example: <screen>\n" -"<show min-screen-height=\"768\"/>\n" -"</screen>" -msgstr "" -"Por ejemplo: <screen>\n" -"<show min-screen-height=\"768\"/>\n" -"</screen>" - -#: C/gdm.xml:6847(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:6856(title) -msgid "Normal/Active/Prelight Nodes" -msgstr "Nodos normal/activo/prelight" - -#: C/gdm.xml:6858(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:6864(para) -msgid "<filename>normal</filename> - normal state." -msgstr "<filename>normal</filename> - estado normal." - -#: C/gdm.xml:6867(para) -msgid "<filename>active</filename> - when the item has active focus." -msgstr "<filename>activo</filename> - cuando el elemento tiene foco activo." - -#: C/gdm.xml:6870(para) -msgid "<filename>prelight</filename> - when the mouse is hovering over the item." -msgstr "<filename>prelight</filename> - cuando el ratón está sobre el elemento." - -#: C/gdm.xml:6875(para) -msgid "" -"When item is \"rect\" (alpha can be omitted and defaults to 0.0): <screen>\n" -"<normal color=\"#ffffff\" alpha=\"0.0\">\n" -"</screen>" -msgstr "" -"Cuando un elemento es \"rect\" (se puede omitir alpha y se toma 0.0): " -"<screen>\n" -"<normal color=\"#ffffff\" alpha=\"0.0\">\n" -"</screen>" - -#: C/gdm.xml:6883(para) -msgid "" -"When item is \"label\" <screen>\n" -"<normal color=\"#ffffff\" font=\"Sans 14\"/>\n" -"</screen>" -msgstr "" -"Cuando el elemento es \"label\" <screen>\n" -"<normal color=\"#ffffff\" font=\"Sans 14\"/>\n" -"</screen>" - -#: C/gdm.xml:6890(para) -msgid "" -"When the item type is \"pixmap\" or \"SVG\", then the normal, active, and " -"prelight tags specify the images to use as follows: <screen>\n" -"<normal file=\"picture.png\" tint=\"#dddddd\"/>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6899(para) -msgid "" -"Note that relative pathnames are assumed to be in the same directory as the " -"theme <filename>.xml</filename> file in <filename><share>/gdm/themes/" -"<theme_name></filename>." -msgstr "" - -#: C/gdm.xml:6905(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: " -"<screen>\n" -"<normal file=\"picture.png\" altfile1=\"distribution-blah-image.png\" " -"altfile2=\"distribution-foo-image.png\"/>\n" -"</screen> If <filename>distribution-foo-image.png</filename> 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:6920(title) -msgid "Face Browser Icon/Label Color Nodes" -msgstr "Icono del visor de rostros/Etiquetas de nodos de color" - -#: C/gdm.xml:6922(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 "" -"Si el tipo de elemento es «userlist», entonces el color de fondo para el " -"icono y la etiqueta se pueden establecer separadamente a través de la " -"siguiente etiqueta:" - -#: C/gdm.xml:6928(screen) -#, no-wrap -msgid "" -"\n" -"<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" -msgstr "" -"\n" -"<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" - -#: C/gdm.xml:6935(title) -msgid "Text Node" -msgstr "Nodo de texto" - -#: C/gdm.xml:6937(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): " -"<screen>\n" -"<text xml:lang=\"fr\">Option</text>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6946(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: <screen>\n" -"<text>\"foo<sup>bar</sup>\"</text>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6955(para) -msgid "" -"Text nodes can contain the following special character sequences which will " -"be translated as follows:" -msgstr "" -"Los nodos de texto pueden contener las siguientes secuencias de caracteres " -"especiales que se traducirán como sigue:" - -#: C/gdm.xml:6960(para) -msgid "%% - A literal % character" -msgstr "%% - Un carácter literal %" - -#: C/gdm.xml:6963(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 - Hora del reloj. Sólo las etiquetas con el id \"clock\" se actualizarán " -"automáticamente cada segundo. Las demás etiquetas contendrán un sello " -"temporal estático." - -#: C/gdm.xml:6968(para) -msgid "%d - Display name (DISPLAY environment variable)" -msgstr "%d - Nombre de la pantalla (variable de entorno DISPLAY)" - -#: C/gdm.xml:6971(para) -msgid "%h - Hostname (gethostname output)" -msgstr "%h - Nombre del host (salida de gethostname)" - -#: C/gdm.xml:6974(para) -msgid "%m - Machine name (uname.machine output)" -msgstr "%m - Nombre de la máquina (salida de uname.machine)" - -#: C/gdm.xml:6977(para) -msgid "%n - Node name (uname.nodename output)" -msgstr "%n - Nombre del nodo (salida de uname.nodename)" - -#: C/gdm.xml:6980(para) -msgid "%o - Domain name (getdomainname output)" -msgstr "%o - Nombre del dominio (salida de getdomainname)" - -#: C/gdm.xml:6983(para) -msgid "%r - Release name (uname.release output)" -msgstr "%r - Nombre del lanzamiento (salida de uname.release)" - -#: C/gdm.xml:6986(para) -msgid "%s - System name (uname.sysname output)" -msgstr "%s - Nombre del sistema (salida de uname.sysname)" - -#: C/gdm.xml:6989(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:6997(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:7003(para) -msgid "\\n - Carriage return" -msgstr "\\n - Retorno de carro" - -#: C/gdm.xml:7006(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 "" -"_ - Un guión bajo hace que el siguiente carácter sea subrayado. Si precede a " -"una secuencia de carácter %, la cadena que reemplace la secuencia de " -"caracteres se subraya." - -#: C/gdm.xml:7014(title) -msgid "Stock node" -msgstr "Nodo predeterminado" - -#: C/gdm.xml:7016(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 "" -"Ciertas etiquetas comunes localizadas pueden especificarse por medio de las " -"etiquetas de fábrica. La etiqueta \"text\" se ignora si se usa la etiqueta " -"\"stock\". Debería usar las etiquetas de fábrica en vez de poner todas las " -"traducciones en los temas. Esto da tiempos de carga más rápidos y mejores " -"traducciones. Los valores siguientes son válidos:" - -#: C/gdm.xml:7025(para) -msgid "<filename>cancel</filename>, _(\"_Cancel\"" -msgstr "<filename>cancel</filename>, _(\"_Cancelar\"" - -#: C/gdm.xml:7028(para) -msgid "<filename>caps-lock-warning</filename>, _(\"Caps Lock is on.\"" -msgstr "" -"<filename>caps-lock-warning</filename>, _(\"La tecla BloqMayús está activada." -"\"" - -#: C/gdm.xml:7032(para) -msgid "<filename>chooser</filename>, _(\"Remote Login via _XDMCP\"" -msgstr "<filename>chooser</filename>, _(\"Entrada remota via _XDMCP\"" - -#: C/gdm.xml:7035(para) -msgid "<filename>config</filename>, _(\"_Configure\"" -msgstr "<filename>config</filename>, _(\"_Configurar\"" - -#: C/gdm.xml:7038(para) -msgid "<filename>custom_cmd[0-9]</filename>, getting label from config file" -msgstr "" -"<filename>custom_cmd[0-9]</filename>, obtener etiqueta del archivo de " -"configuración" - -#: C/gdm.xml:7041(para) -msgid "<filename>disconnect</filename>, _(\"D_isconnect\"" -msgstr "<filename>disconnect</filename>, _(\"D_esconectar\"" - -#: C/gdm.xml:7044(para) -msgid "<filename>halt</filename>, _(\"Shut _Down\"" -msgstr "<filename>halt</filename>, _(\"_Apagar\")" - -#: C/gdm.xml:7047(para) -msgid "<filename>language</filename>, _(\"_Language\"" -msgstr "<filename>language</filename>, _(\"_Idioma\"" - -#: C/gdm.xml:7050(para) -msgid "<filename>ok</filename>, _(\"_OK\"" -msgstr "<filename>ok</filename>, _(\"_Aceptar\"" - -#: C/gdm.xml:7053(para) -msgid "<filename>options</filename>, _(\"_Options\"" -msgstr "<filename>options</filename>, _(\"_Opciones\"" - -#: C/gdm.xml:7056(para) -msgid "<filename>quit</filename>, _(\"_Quit\"" -msgstr "<filename>quit</filename>, _(\"_Salir\"" - -#: C/gdm.xml:7059(para) -msgid "<filename>reboot</filename>, _(\"_Restart\"" -msgstr "<filename>reboot</filename>, _(\"_Reiniciar\"" - -#: C/gdm.xml:7062(para) -msgid "<filename>session</filename>, _(\"_Session\"" -msgstr "<filename>session</filename>, _(\"_Sesión\"" - -#: C/gdm.xml:7065(para) -msgid "<filename>startagain</filename>, _(\"_Start Again\"" -msgstr "<filename>startagain</filename>, _(\"_Empezar de nuevo\"" - -#: C/gdm.xml:7068(para) -msgid "<filename>suspend</filename>, _(\"Sus_pend\"" -msgstr "<filename>suspend</filename>, _(\"Sus_pender\"" - -#: C/gdm.xml:7071(para) -msgid "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\"" -msgstr "<filename>system</filename>, _(\"_Acciones\" (Anteriormente \"S_istema\"" - -#: C/gdm.xml:7075(para) -msgid "<filename>timed-label</filename>, _(\"User %u will login in %t\"" -msgstr "<filename>timed-label</filename>, _(\"El usuario %u entrará en %t\"" - -#: C/gdm.xml:7079(para) -msgid "<filename>username-label</filename>, _(\"Username:\"" -msgstr "<filename>username-label</filename>, _(\"Usuario:\"" - -#: C/gdm.xml:7082(para) -msgid "<filename>welcome-label</filename>, _(\"Welcome to %n\"" -msgstr "<filename>welcome-label</filename>, _(\"Bienvenido a %n\"" - -#: C/gdm.xml:7086(para) -msgid "" -"For example: <screen>\n" -"<stock type=\"welcome-label\">\n" -"</screen>" -msgstr "" -"Por ejemplo: <screen>\n" -"<stock type=\"welcome-label\">\n" -"</screen>" - -#: C/gdm.xml:7095(title) -msgid "Custom Widgetry" -msgstr "Widgets personalizados" - -#: C/gdm.xml:7097(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 " -"<filename><ServAuthDir>/<display>.GreeterInfo</filename> as " -"<filename><list id>=<listitem id></filename>." -msgstr "" -"Actualmente hay un elemento que es personalizable y este es el elemento de " -"la lista. Si necesita preguntar al usuario cosas adicionales, como para " -"escoger de una lista o lugares desde donde entrar, o establecer un conjunto " -"de sesiones de entrada personalizadas puede configurar el elemento de la " -"lista y añadir hijos del elemento de la lista que describan las selecciones. " -"Cada elemento de la lista debe tener un id y un texto hijo. La elección será " -"grabada en el archivo <filename><ServAuthDir>/<display>." -"GreeterInfo</filename> como <filename><list id>=<listitem id></" -"filename>." - -#: C/gdm.xml:7108(para) -msgid "" -"For example suppose we are on display :0, <filename>ServAuthDir</filename> " -"is <filename><var>/lib/gdm</filename> and we have the following in the " -"theme:" -msgstr "" -"Por ejemplo suponga que estamos en la pantalla 0, <filename>ServAuthDir</" -"filename> es <filename><var>/lib/gdm</filename> y tenemos lo siguiente " -"en el tema:" - -#: C/gdm.xml:7115(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 "" -"\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" - -#: C/gdm.xml:7127(para) -msgid "" -"Then if the user chooses 'Foo' then <filename><var>/lib/gdm/:0." -"GreeterInfo</filename> will contain: <screen>\n" -"custom-config=foo\n" -"</screen>" -msgstr "" -"Entonces si el usuario elije «Foo» entonces <filename><var>/gdm/:0." -"GreeterInfo</filename> contendrá <screen>\n" -"custom-config=foo\n" -"</screen>" - -#: C/gdm.xml:7139(title) -msgid "Accessibility" -msgstr "Accesibilidad" - -#: C/gdm.xml:7140(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 <command>GOK</" -"command> (on-screen keyboard) and <command>orca</command> (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 <command>GOK</command>, do not yet work " -"with the \"Themed Greeter\"." -msgstr "" - -#: C/gdm.xml:7153(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 <filename>Greeter</" -"filename> and <filename>RemoteGreeter</filename> configuration options by " -"hand to be <command>/usr/lib/gdmlogin</command>." -msgstr "" - -#: C/gdm.xml:7162(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 "" -"La interfaz estándar soporta la capacidad de lanzar tecnologías de " -"asistencia en el momento de la entrada a través de «gestos» configurables. " -"Estos gestos se pueden definir para que sean teclas rápidas de un teclado " -"estándar, un dispositivo conmutador o eventos de movimiento del ratón. Al " -"usar «GTK+ Greeter», el usuario también puede cambiar la apariencia visual " -"de la IU de entrada, por ejemplo para usar un esquema de color de alto " -"contraste para una mejor visibilidad." - -#: C/gdm.xml:7171(para) -msgid "" -"Note that <command>gdmsetup</command> does not yet work with accessibility, " -"so that users who require AT programs should only configure GDM by editing " -"the ASCII files directly." -msgstr "" -"Note que <command>gdmsetup</command> aún no trabaja con accesibilidad, de " -"tal forma que los usuarios que requieran programas de tecnologías de " -"asistencia sólo deberían configurar GDM editando los archivos ASCII " -"directamente." - -#: C/gdm.xml:7178(title) -msgid "Accessibility Configuration" -msgstr "Configuración de accesibilidad" - -#: C/gdm.xml:7180(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 <command>GOK</command> and <command>orca</command>, " -"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:7196(title) -msgid "Accessibile Theming" -msgstr "Temas de accesibilidad" - -#: C/gdm.xml:7198(para) -msgid "" -"If using the \"GTK+ Greeter\" users can easily switch the color and contrast " -"scheme of the dialog. To do this, ensure the <filename>AllowGtkThemeChange</" -"filename> 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 " -"<filename>GtkThemesToAllow</filename> configuration choice can also be used " -"to limit the choices available as desired. For example:" -msgstr "" - -#: C/gdm.xml:7210(screen) -#, no-wrap -msgid "" -"\n" -"GtkThemesToAllow=HighContrast,HighContrastInverse\n" -msgstr "" -"\n" -"GtkThemesToAllow=HighContrast,HighContrastInverse\n" - -#: C/gdm.xml:7214(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:7226(title) -msgid "AT Program Support" -msgstr "Soporte de programas de tecnologías de asistencia" - -#: C/gdm.xml:7228(para) -msgid "" -"To enable user to launch AT such as the <command>GOK</command> or " -"<command>orca</command>, the <filename>AddGtkModules</filename> parameter in " -"the GDM configuration must be set to \"true\". Also the " -"<filename>GtkModulesList</filename> parameter must be uncommented and set as " -"follows:" -msgstr "" -"Para activar el uso de tecnologías de asistencia como <command>GOK</command> " -"u <command>orca</command>, el parámetro <filename>AddGtkModules</filename> " -"en la configuración de GDM debe establecerse a «true». Además el parámetro " -"<filename>GtkModulesList</filename> debe descomentarse y establecerse como " -"sigue:" - -#: C/gdm.xml:7237(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 "" -"\n" -"GtkModulesList=gail:atk-bridge:/usr/lib/gtk-2.0/modules/libdwellmouselistener:/usr/lib/gtk-2.0/modules/libkeymouselistener\n" - -#: C/gdm.xml:7241(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, <command>at-spi-registryd</" -"command>, to be running. This is handled by the GDM GUI starting with " -"version 2.17." -msgstr "" - -#: C/gdm.xml:7249(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:7264(para) -msgid "" -"Once \"keymouselistener\" and/or \"dwellmouselistener\" have been added to " -"the <filename>AddGtkModules</filename> loaded by GDM, then you may need to " -"modiify the gesture configurations to meet your user's needs. Default " -"gestures are provided for launching <command>GOK</command> and " -"<command>orca</command>, but it is recommended to modify these gestures so " -"they work best for your user base. These gesture associations are contained " -"in files <filename>AccessKeyMouseEvents</filename> and " -"<filename>AccessDwellMouseEvents</filename>, respectively. Both files are " -"located in the <filename><etc>/gdm/modules</filename> directory. The " -"gesture configuration format is described in the comment section of the two " -"configuration files." -msgstr "" - -#: C/gdm.xml:7281(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 " -"<filename>server-foo</filename> sections." -msgstr "" - -#: C/gdm.xml:7295(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:7311(para) -msgid "" -"On some operating systems, it is necessary to make sure that the GDM user is " -"a member of the \"audio\" group for AT programs that require audio output " -"(such as text-to-speech) to be functional." -msgstr "" -"En algunos sistemas operativos es necesario asegurarse de que el usuario de " -"GDM es un miembro del grupo \"audio\" para los programas de accesibilidad " -"que necesiten salida de sonido (tal como texto-a-voz) para su funcionamiento." - -#: C/gdm.xml:7318(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:7331(title) -msgid "AT Troubleshooting" -msgstr "Resolución de problemas de las tecnologías de asistencia" - -#: C/gdm.xml:7333(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 "" -"Hay algunas cuestiones comunes que provocan que los usuarios tengan " -"problemas al hacer funcionar los oyentes de gestos. Es recomendable que se " -"use la versión 2.18.0 o posterior de GDM para obtener los mejores resultados." - -#: C/gdm.xml:7339(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:7348(para) -msgid "" -"Some versions of <command>GOK</command> and <command>orca</command> 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:7357(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:7365(para) -msgid "" -"Also note that some input devices require X server configuration before GDM " -"will recognize them." -msgstr "" -"Note que algunos dispositivos de entrada requieren una configuración del " -"servidor X antes de que GDM los pueda reconocer." - -#: C/gdm.xml:7372(title) -msgid "Accessibility Login Sound Configuration" -msgstr "Configuración de sonido de accesibilidad en la entrada" - -#: C/gdm.xml:7374(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 <filename><bin>/play</filename> (or <filename><" -"bin>/audioplay</filename> on Solaris. This can be changed via the " -"<filename>SoundProgram</filename> GDM configuration option. Typically most " -"text-to-speech programs (such as <command>orca</command>) use a separate " -"mechanism to play audio, so this configuration setting is not needed for " -"them to work." -msgstr "" - -#: C/gdm.xml:7392(title) -msgid "Solaris Specific Features" -msgstr "Características específicas de Solaris" - -#: C/gdm.xml:7395(title) -msgid "Using GDM on Solaris" -msgstr "Usar GDM en Solaris" - -#: C/gdm.xml:7397(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:7410(screen) -#, no-wrap -msgid "" -"\n" -"svcs cde-login\n" -msgstr "" -"\n" -"svcs cde-login\n" - -#: C/gdm.xml:7414(para) -msgid "" -"If the <command>svcs</command> command responds that this service is " -"enabled, then run this command to disable CDE login:" -msgstr "" -"Si el comando <command>svcs</command> responde que este servicio está " -"activado, entonces ejecute este comando para desactivar la entrada de CDE." - -#: C/gdm.xml:7419(screen) -#, no-wrap -msgid "" -"\n" -"svcadm disable cde-login\n" -msgstr "" -"\n" -"svcadm disable cde-login\n" - -#: C/gdm.xml:7423(para) -msgid "" -"If the <command>svcs</command> command responds that this pattern doesn't " -"match any instances, then run these commands to stop CDE login:" -msgstr "" -"Si el comando <command>svcs</command> responde que este patrón no coincide " -"con ninguna instancia, entonces ejecute esos comandos para parar la entrada " -"en CDE:" - -#: C/gdm.xml:7429(screen) -#, no-wrap -msgid "" -"\n" -"/usr/dt/config/dtconfig -d\n" -"Either reboot, or kill any running dtlogin processes.\n" -msgstr "" -"\n" -"/usr/dt/config/dtconfig -d\n" -"Reinicie o mate cualquier proceso que esté ejecutando dtlogin.\n" - -#: C/gdm.xml:7434(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:7441(screen) -#, no-wrap -msgid "" -"\n" -"svcadm enable servicename\n" -msgstr "" -"\n" -"svcadm enable servicename\n" - -#: C/gdm.xml:7447(title) -msgid "Solaris Configuration" -msgstr "Configuración de Solaris" - -#: C/gdm.xml:7448(para) -msgid "" -"On Solaris, the following configuration is recommended. This turns on IPv6 " -"and also turns on PreFetch for performance benefit. <screen>\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" -"</screen>" -msgstr "" -"En Solaris, la siguiente configuración está recomendada. Esto activa IPv6 y " -"también activa PreFetch para mejorar el rendimiento. <screen>\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" -"</screen>" - -#: C/gdm.xml:7461(para) -msgid "" -"Configuring GDM with the \"--with-post-path=/usr/openwin/bin\" on Solaris is " -"recommended for accessing X server programs." -msgstr "" -"Configurar GDM con \"--with-post-path=/usr/openwin/bin\" en Solaris está " -"recomendado para acceder a programas del servidor X." - -#: C/gdm.xml:7469(title) -msgid "Solaris /etc/logindevperm" -msgstr "Solaris /etc/logindevperm" - -#: C/gdm.xml:7470(para) -msgid "" -"GDM supports /etc/logindevperm, but only on Solaris 10 and higher. Refer to " -"the logindevperm.4 man page for more information." -msgstr "" -"GDM soporta /etc/logindevperm, pero sólo en Solaris 10 y superiores. Vea la " -"página man logindevperm.4 para más información." - -#: C/gdm.xml:7476(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 "" -"Para hacer funcionar /etc/logindevperm en Solaris 9 o anteriores, deberá " -"haquear los scripts de GDM PreSession y PostSession para hacer un chmod a " -"los permisos del dispositivo directamente. En otras palabras, si /etc/" -"logindevperm se lista como esto:" - -#: C/gdm.xml:7483(screen) -#, no-wrap -msgid "" -"\n" -"/dev/console 0600 /dev/sound/* # audio devices\n" -msgstr "" -"\n" -"/dev/console 0600 /dev/sound/* # audio devices\n" - -#: C/gdm.xml:7487(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 "" -"El script de PreSession debería tener que modificarse para que haga chown " -"sobre /dev/console al usuario:grupo de quien esté entrando en la consola y " -"asegurarse cualesquiera de los permisos estén especificados en /etc/" -"logindevperm (0600 para la línea de arriba). Después en el script " -"PostSession volver a hacer un chmod del dispositivo a root:root y asegurarse " -"de que los permisos son 0600 esta vez (no usar el valor sobre el archivo /" -"etc/logindevperm). Linux usa un mecanismo diferente para gestionar los " -"permisos de dispositivos, así que este script adicional no es necesario." - -#: C/gdm.xml:7500(title) -msgid "Solaris Automatic Login" -msgstr "Inicio de sesión automático en Solaris" - -#: C/gdm.xml:7501(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:7512(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 "" -"Si está usando Solaris 10 o inferior, entonces necesita compilar el código " -"pam_allow.c proporcionado con la distribución de GDM e instalarlo en /usr/" -"lib/security (o proporcionar la ruta completa en /etc/pam.conf) y asegurarse " -"de que el propietario tiene un uid 0 y sin grupo o que sea editable por todo " -"usuario." - -#: C/gdm.xml:7519(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 "" -"Los siguientes son valores razonables para pam.conf para activar la entrada " -"automática en GDM. Asegúrese de leer la documentación de PAM (ej. página man " -"de pam.d/pam.conf) y conocer las implicaciones de seguridad que cualquier " -"cambio que intente hacer a la configuración." - -#: C/gdm.xml:7527(screen) -#, no-wrap -msgid "" -"\n" -" gdm-autologin auth required pam_unix_cred.so.1\n" -" gdm-autologin auth sufficient pam_allow.so.1\n" -" gdm-autologin account sufficient pam_allow.so.1\n" -" gdm-autologin session sufficient pam_allow.so.1\n" -" gdm-autologin password sufficient pam_allow.so.1\n" -msgstr "" -"\n" -" gdm-autologin auth required pam_unix_cred.so.1\n" -" gdm-autologin auth sufficient pam_allow.so.1\n" -" gdm-autologin account sufficient pam_allow.so.1\n" -" gdm-autologin session sufficient pam_allow.so.1\n" -" gdm-autologin password sufficient pam_allow.so.1\n" - -#: C/gdm.xml:7535(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 "" -"La configuración anterior hará que no se genere información de «lastlog». Si " -"se desea una entrada de «lastlog», use lo siguiente para la sesión:" - -#: C/gdm.xml:7540(screen) -#, no-wrap -msgid "" -"\n" -" gdm-autologin session required pam_unix_session.so.1\n" -msgstr "" -"\n" -" gdm-autologin session required pam_unix_session.so.1\n" - -#: C/gdm.xml:7546(title) -msgid "Solaris RBAC support for Shutdown, Reboot, and Suspend" -msgstr "Soporte RBAC en Solaris para apagar, reiniciar y suspender" - -#: C/gdm.xml:7548(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 <command>gdmflexiserver</command> " -"QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION commands." -msgstr "" -"Desde la versión GDM 2.19, GDM soporta RBAC (Role Based Access Control) para " -"activar los comandos del sistema apagar, reiniciar, suspender, etc " -"(shutdown, reboot, suspend, etc.) que aparecen en el menú gráfico y a través " -"de los comandos QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, y " -"SET_SAFE_LOGOUT_ACTION de <command>gdmflexiserver</command>." - -#: C/gdm.xml:7557(para) -msgid "" -"On Solaris GDM has the following value specified for the " -"<filename>RBACSystemCommandKeys</filename> configuration option." -msgstr "" -"En Solaris, GDM tiene el siguiente valor especificado para la opción de " -"configuración <filename>RBACSystemCommandKeys</filename>." - -#: C/gdm.xml:7563(screen) -#, no-wrap -msgid "" -"\n" -"HALT:solaris.system.shutdown;REBOOT:solaris.system.shutdown\n" -msgstr "" -"\n" -"HALT:solaris.system.shutdown;REBOOT:solaris.system.shutdown\n" - -#: C/gdm.xml:7567(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 " -"<filename>User</filename> configuration option, \"gdm\" by default) has such " -"RBAC permissions." -msgstr "" - -#: C/gdm.xml:7577(para) -msgid "" -"Therefore, add the \"solaris.system.shutdown\" authorization name to the " -"<filename>/etc/user_attr</filename> 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 " -"<filename>RBACSystemCommandKeys</filename> GDM configuration key, and this " -"will make the system commands available for all users. Refer to the " -"<filename>user_attr</filename> man page for more information about setting " -"RBAC privileges." -msgstr "" - -#: C/gdm.xml:7591(para) -msgid "" -"Note that on Solaris there are two programs that can be used to shutdown the " -"system. These are GDM and <command>gnome-sys-suspend</command>. " -"<command>gnome-sys-suspend</command> is a GUI front-end for the <command>sys-" -"suspend</command>." -msgstr "" -"Note que en Solaris hay dos programas que se pueden usar para apagar el " -"sistema. Estos son GDM y <command>gnome-sys-suspend</command>. " -"<command>gnome-sys-suspend</command> es un IGU «front-end» para <command>sys-" -"suspend</command>." - -#: C/gdm.xml:7599(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 <command>gnome-sys-suspend</" -"command> 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 <command>gnome-sys-suspend</command> command is " -"less functional since it does not support a reboot option, only shutdown and " -"suspend." -msgstr "" - -#: C/gdm.xml:7614(para) -msgid "" -"If GDM is not being used to manage shutdown, reboot, and suspend; then the " -"GNOME panel uses <command>gnome-sys-suspend</command> 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 <command>gnome-sys-suspend</command>. If you are " -"using this, then refer to the <command>sys-suspend</command> man page for " -"information about how to configure it. Or consider using GDM and configuring " -"it to provide these options." -msgstr "" - -#: C/gdm.xml:7630(title) -msgid "Other Solaris Features" -msgstr "Otras características de Solaris" - -#: C/gdm.xml:7631(para) -msgid "GDM supports a few features specific to Solaris, as follows:" -msgstr "" -"GDM soporta unas pocas características específicas a Solaris, como las " -"siguientes:" - -#: C/gdm.xml:7635(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 "" -"GDM soporta Solaris Auditing si se ejecuta sobre Solaris 10 o superior. GDM " -"no debería usarse si se necesita auditoría y se está ejecutando Solaris 9 o " -"anterior." - -#: C/gdm.xml:7641(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 "" -"GDM tiene una característica de seguridad que hace que el servidor X " -"funcione como el usuario en lugar del usuario root. GDM debe estar usando " -"PAM para que esta característica esté activada, lo cual es el caso normal en " -"Solaris. Esta segunda característica tiene el efecto colateral de hacer que " -"el servidor X siempre se reinicie entre las sesiones, lo cual desactiva la " -"opción de configuración AlwaysRestartServer." - -#: C/gdm.xml:7650(para) -msgid "" -"Solaris supports the <filename>/etc/default/login</filename> interface, " -"which affects the <filename>DefaultPath</filename>, <filename>RootPath</" -"filename>, <filename>PasswordRequired</filename>, and " -"<filename>AllowRemoteRoot</filename> options as described in the " -"\"Configuration\" section." -msgstr "" -"Solaris ssoporta el interfaz <filename>/etc/default/login</filename>,que " -"afecta las opciones <filename>DefaultPath</filename>, <filename>RootPath</" -"filename>, <filename>PasswordRequired</filename>, y " -"<filename>AllowRemoteRoot</filename> tal como se describen en la " -"sección«Configuración» ." - -#: C/gdm.xml:7662(title) -msgid "Example Configurations" -msgstr "Configuraciones de ejemplo" - -#: C/gdm.xml:7665(title) -msgid "Defining Custom Commands" -msgstr "Definir comando personalizados" - -#: C/gdm.xml:7667(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 <filename>[customcommand]</filename> " -"section of the GDM configuration file. <screen>\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" -" </screen> CustomCommand0 specifies two commands separated by a " -"semicolon: <filename>/sbin/rebootwindoze</filename> and <filename>/usr/local/" -"sbin/rebootwindoze</filename>. 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:7690(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 <filename>[customcommand]</filename> " -"section of your GDM configuration file. <screen>\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" -" </screen>" -msgstr "" - -#: C/gdm.xml:7710(para) -msgid "" -"Both custom commands could be defined as follows. <screen>\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" -" </screen>" -msgstr "" - -#: C/gdm.xml:7731(para) -msgid "" -"There can be up to 10 custom commands numbered 0-9. <screen>\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" -" </screen>" -msgstr "" - -#: C/gdm.xml:7765(title) -msgid "Troubleshooting" -msgstr "Resolución de problemas" - -#: C/gdm.xml:7767(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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome." -"org</ulink> or send an email to the <address><email>gdm-list@gnome.org</" -"email></address> mail list." -msgstr "" -"Esta sección hace acerca de consejos útiles para hacer funcionar GDM. En " -"general, si tiene un problema al usar GDM, puede enviar un bug a la " -"categoría «gdm» en <ulink type=\"http\" url=\"http://bugzilla.gnome.org/" -"\">bugzilla.gnome.org</ulink> o enviar un correo-e a la lista de correo " -"<address><email>gdm-list@gnome.org</email></address>." - -#: C/gdm.xml:7777(para) -msgid "" -"If GDM is failing to work properly, it is always a good idea to include " -"debug information. Use the <command>gdmsetup</command> 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 (<filename><var>/log/messages</filename> or " -"<filename><var>/adm/messages</filename> 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:7791(para) -msgid "" -"You should not leave debug on after collecting data. It will clutter your " -"syslog and slow system performance." -msgstr "" -"No debería dejar la depuración activada después de obtener los datos. " -"desordenará su archivo syslog y ralentizará el rendimiento del sistema." - -#: C/gdm.xml:7797(title) -msgid "GDM Will Not Start" -msgstr "GDM no se inicia" - -#: C/gdm.xml:7799(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 "" -"Puede haber muchos problemas que causen un fallo de GDM al inicio, pero esta " -"sección discutirá algunos problemas comunes y cómo solucionar un problema de " -"inicio de GDM. Algunos problemas provocarán que GDM responda con un mensaje " -"de error o un diálogo cuando intenta iniciarse, pero puede ser difícil " -"seguir un problema cuando GDM falla de forma silenciosa." - -#: C/gdm.xml:7808(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:7821(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 <command><" -"lib>/gdmlogin</command> or <command><lib>/gdmgreeter</command>. 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:7834(para) -msgid "" -"Also make sure that the <filename>/tmp</filename> directory has reasonable " -"ownership and permissions, and that the machine's file system is not full. " -"These problems will cause GDM to fail to start." -msgstr "" -"Asegúrese de que el directorio <filename>/tmp</filename> tiene permisos y " -"propiedad razonables, y que el sistema de archivos de la máquina no está " -"lleno. Estos problemas harán que GDM falle al iniciar." - -#: C/gdm.xml:7842(title) -msgid "GDM Will Not Access User Settings" -msgstr "GDM no accede a los ajustes del usuario" - -#: C/gdm.xml:7844(para) -msgid "" -"GDM saves user settings, such as your default session and default language, " -"in the <filename>~/.dmrc</filename>. Other files, such as the user's " -"<filename>~/.Xauthority</filename> 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 <filename>RelaxPermissions</filename> 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 "" -"GDM guarda los ajustes del usuario, como su sesión predeterminada y el " -"idioma, en el archivo <filename>~/.dmrc</filename>. Otros archivos, como el " -"archivo <filename>~/.Xauthority</filename> también afectarán a la entrad. " -"GDM, por omisión, es estricto acerca de cómo se intenta acceder a los " -"archivos en el directorio personal del usuario e ignorará el archivo si no " -"está de acuerdo con ciertas reglas. Puede usar la opción de configuración " -"<filename>RelaxPermissions</filename> para hacer que GDM sea menos estricto " -"acerca de cómo accede a los archivos en el directorio personal del usuario, " -"o corregir los problemas de permisos que hacen que DGM ignore el archivo. " -"Esto se trata en detalle en la sección «Acceso a archivos » en la «Vista " -"general»" - -#: C/gdm.xml:7863(title) -msgid "License" -msgstr "Licencia" - -#: C/gdm.xml:7864(para) -msgid "" -"This program is free software; you can redistribute it and/or modify it " -"under the terms of the <ulink type=\"help\" url=\"gnome-help:gpl" -"\"><citetitle>GNU General Public License</citetitle></ulink> as published by " -"the Free Software Foundation; either version 2 of the License, or (at your " -"option) any later version." -msgstr "" -"Este programa es software libre; puede redistribuirlo y/o modificarlo bajo " -"los términos de la <ulink type=\"help\" url=\"gnome-help:gpl" -"\"><citetitle>Licencia Pública General GNU</citetitle></ulink> tal como se " -"publica por la Free Software Foundation; ya sea la versión 2 de la Licencia, " -"o (a su elección) cualquier versión posterior." - -#: C/gdm.xml:7872(para) -msgid "" -"This program is distributed in the hope that it will be useful, but WITHOUT " -"ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or " -"FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public " -"License</citetitle> for more details." -msgstr "" -"Este programa se distribuye con la esperanza de que le sea útil, pero SIN " -"NINGUNA GARANTÍA; sin incluso la garantía implícita de MERCANTILIDAD o " -"IDONEIDAD PARA UN PROPÓSITO PARTICULAR. Vea la <citetitle>Licencia Pública " -"General GNU</citetitle> para más detalles." - -#: C/gdm.xml:7878(para) -msgid "" -"A copy of the <citetitle>GNU General Public License</citetitle> is included " -"as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also " -"obtain a copy of the <citetitle>GNU General Public License</citetitle> from " -"the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://" -"www.fsf.org\">their Web site</ulink> or by writing to <address> Free " -"Software Foundation, Inc. <street>51 Franklin Street, Fifth Floor</" -"street><city>Boston</city>, <state>MA</state><postcode>02110-1301</" -"postcode><country>USA</country></address>" -msgstr "" -"Se incluye una copia de la <citetitle>Licencia Pública General GNU</" -"citetitle> como un apéndice a la <citetitle>Guía del usuario de GNOME</" -"citetitle>. Quizá quiera obtener una copia de la <citetitle>Licencia Pública " -"General GNU</citetitle> de la Free Software Foundation visitando <ulink type=" -"\"http\" url=\"http://www.fsf.org\">su sitio web</ulink> o escribiendo a " -"<address>Free Software Foundation, Inc. <street>51 Franklin Street, Fifth " -"Floor</street><city>Boston</city>, <state>MA</state><postcode>02110-1301</" -"postcode><country>USA</country></address>" - -#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2. -#: C/gdm.xml:0(None) -msgid "translator-credits" -msgstr "" -"Jorge González <jorgegonz@svn.gnome.org>, 2007\n" -"Lucas Vieites <lucas@asixinformatica.com>, 2007\n" -"Francisco Javier F. Serrador <serrador@openshine.com>, 2003, 2006" - diff --git a/docs/es/figures/gdm_window.png b/docs/es/figures/gdm_window.png Binary files differdeleted file mode 100644 index 81644af7..00000000 --- a/docs/es/figures/gdm_window.png +++ /dev/null diff --git a/docs/es/gdm-es.omf b/docs/es/gdm-es.omf deleted file mode 100644 index ca18fc29..00000000 --- a/docs/es/gdm-es.omf +++ /dev/null @@ -1,18 +0,0 @@ -<omf> - <resource> - <creator>docs@gnome.org (GDP) </creator> - <maintainer>docs@gnome.org (GDP) </maintainer> - <title>Manual de Configuración de la pantalla de sesión, versión 2.0.1 </title> - <date>2004-01-19 </date> - <version identifier="2.0.1" date="2004-01-19" description="Created for Quicksilver, program version 2.4.2.101"/> - <subject category="GNOME|Applications|System Tools"/> - - <description>Manual del usuario para la aplicación Configuración de la pantalla de sesión. </description> - <type>guía del usuario </type> - <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/> - <identifier url="gdm.xml"/> - <language code="es"/> - <relation seriesid="be6a0524-46d3-11d8-983d-e135363498a8"/> - <rights type="GNU FDL" license.version="1.1" holder="Sun Microsystems"/> - </resource> -</omf> diff --git a/docs/fr/fr.po b/docs/fr/fr.po deleted file mode 100644 index e43a79a3..00000000 --- a/docs/fr/fr.po +++ /dev/null @@ -1,12577 +0,0 @@ -# French 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. -# -# Jonathan Ernst <jonathan@ernstfamily.ch>, 2006-2007. -# Gabriel De Sa <gabriel.desa@gmail.com>, 2007. -# Claude Paroz <claude@2xlibre.net>, 2007. -# -msgid "" -msgstr "" -"Project-Id-Version: gdm2 doc fr\n" -"POT-Creation-Date: 2007-08-27 22:30+0200\n" -"PO-Revision-Date: 2007-08-27 22:28+0200\n" -"Last-Translator: Claude Paroz <claude@2xlibre.net>\n" -"Language-Team: GNOME French Team <gnomefr@traduc.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../C/gdm.xml:13(title) -msgid "Gnome Display Manager Reference Manual" -msgstr "Manuel de référence du gestionnaire de connexions GNOME" - -#: ../C/gdm.xml:17(revnumber) -msgid "0.0" -msgstr "0.0" - -#: ../C/gdm.xml:18(date) -msgid "2007-01" -msgstr "01/2007" - -#: ../C/gdm.xml:23(para) -msgid "GDM is the GNOME Display Manager, a graphical login program." -msgstr "" -"GDM est le gestionnaire de connexions de GNOME, une application graphique " -"pour s'identifier" - -#: ../C/gdm.xml:30(firstname) -msgid "Martin" -msgstr "Martin" - -#: ../C/gdm.xml:30(othername) -msgid "K." -msgstr "K." - -#: ../C/gdm.xml:31(surname) -msgid "Petersen" -msgstr "Petersen" - -#: ../C/gdm.xml:33(email) -msgid "mkp@mkp.net" -msgstr "mkp@mkp.net" - -#: ../C/gdm.xml:37(firstname) -msgid "George" -msgstr "George" - -#: ../C/gdm.xml:37(surname) -msgid "Lebl" -msgstr "Lebl" - -#: ../C/gdm.xml:39(email) -msgid "jirka@5z.com" -msgstr "jirka@5z.com" - -#: ../C/gdm.xml:43(firstname) -msgid "Brian" -msgstr "Brian" - -#: ../C/gdm.xml:43(surname) -msgid "Cameron" -msgstr "Cameron" - -#: ../C/gdm.xml:45(email) -msgid "Brian.Cameron@Sun.COM" -msgstr "Brian.Cameron@Sun.COM" - -#: ../C/gdm.xml:49(firstname) -msgid "Bill" -msgstr "Bill" - -#: ../C/gdm.xml:49(surname) -msgid "Haneman" -msgstr "Haneman" - -#: ../C/gdm.xml:51(email) -msgid "Bill.Haneman@Sun.COM" -msgstr "Bill.Haneman@Sun.COM" - -#: ../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 "Martin K. Petersen" - -#: ../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 "George Lebl" - -#: ../C/gdm.xml:63(holder) -msgid "Red Hat, Inc." -msgstr "Red Hat, Inc." - -#: ../C/gdm.xml:66(holder) -msgid "Sun Microsystems, Inc." -msgstr "Sun Microsystems Inc." - -#: ../C/gdm.xml:2(para) -msgid "" -"Permission is granted to copy, distribute and/or modify this document under " -"the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any " -"later version published by the Free Software Foundation with no Invariant " -"Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy " -"of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or " -"in the file COPYING-DOCS distributed with this manual." -msgstr "" -"Permission vous est donnée de copier, distribuer et/ou modifier ce document " -"selon les termes de la Licence GNU Free Documentation License, Version 1.1 " -"ou ultérieure publiée par la Free Software Foundation sans section " -"inaltérable, sans texte de première page de couverture ni texte de dernière " -"page de couverture. Vous trouverez un exemplaire de cette licence en suivant " -"ce <ulink type=\"help\" url=\"ghelp:fdl\">lien</ulink> ou dans le fichier " -"COPYING-DOCS fourni avec le présent manuel." - -#: ../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 "" -"Ce manuel fait partie de la collection de manuels GNOME distribués selon les " -"termes de la licence de documentation libre GNU. Si vous souhaitez " -"distribuer ce manuel indépendamment de la collection, vous devez joindre un " -"exemplaire de la licence au document, comme indiqué dans la section 6 de " -"celle-ci." - -#: ../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 "" -"La plupart des noms utilisés par les entreprises pour distinguer leurs " -"produits et services sont des marques déposées. Lorsque ces noms " -"apparaissent dans la documentation GNOME et que les membres du projet de " -"Documentation GNOME sont informés de l'existence de ces marques déposées, " -"soit ces noms entiers, soit leur première lettre est en majuscule." - -#: ../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 "" -"LE PRÉSENT DOCUMENT EST FOURNI « TEL QUEL », SANS AUCUNE GARANTIE, EXPRESSE " -"OU IMPLICITE, Y COMPRIS, ET SANS LIMITATION, LES GARANTIES DE BONNE QUALITÉ " -"MARCHANDE OU D'APTITUDE À UN EMPLOI PARTICULIER OU AUTORISÉ DU DOCUMENT OU " -"DE SA VERSION MODIFIÉE. L'UTILISATEUR ASSUME TOUT RISQUE RELATIF À LA " -"QUALITÉ, À LA PERTINENCE ET À LA PERFORMANCE DU DOCUMENT OU DE SA VERSION DE " -"MISE À JOUR. SI LE DOCUMENT OU SA VERSION MODIFIÉE S'AVÉRAIT DÉFECTUEUSE, " -"L'UTILISATEUR (ET NON LE RÉDACTEUR INITIAL, L'AUTEUR, NI TOUT AUTRE " -"PARTICIPANT) ENDOSSERA LES COÛTS DE TOUTE INTERVENTION, RÉPARATION OU " -"CORRECTION NÉCESSAIRE. CETTE DÉNÉGATION DE RESPONSABILITÉ CONSTITUE UNE " -"PARTIE ESSENTIELLE DE CETTE LICENCE. AUCUNE UTILISATION DE CE DOCUMENT OU DE " -"SA VERSION MODIFIÉE N'EST AUTORISÉE AUX TERMES DU PRÉSENT ACCORD, EXCEPTÉ " -"SOUS CETTE DÉNÉGATION DE RESPONSABILITÉ ; " - -#: ../C/gdm.xml:55(para) -msgid "" -"UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING " -"NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY " -"CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE " -"DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON " -"FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF " -"ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, " -"WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES " -"OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED " -"VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE " -"POSSIBILITY OF SUCH DAMAGES." -msgstr "" -"EN AUCUNE CIRCONSTANCE ET SOUS AUCUNE INTERPRÉTATION DE LA LOI, QU'IL " -"S'AGISSE DE RESPONSABILITÉ CIVILE (Y COMPRIS LA NÉGLIGENCE), CONTRACTUELLE " -"OU AUTRE, L'AUTEUR, LE RÉDACTEUR INITIAL, TOUT PARTICIPANT ET TOUT " -"DISTRIBUTEUR DE CE DOCUMENTOU DE SA VERSION DE MISE À JOUR AINSI QUE TOUT " -"FOURNISSEUR DE QUELQUE PARTIE QUE CE SOIT NE POURRONT ÊTRE TENUS " -"RESPONSABLES À L'ÉGARD DE QUICONQUE POUR TOUT DOMMAGE DIRECT, INDIRECT, " -"PARTICULIER OU ACCIDENTEL DE TOUT TYPE Y COMPRIS, SANS LIMITATION, LES " -"DOMMAGES LIÉS À LA PERTE DE CLIENTÈLE, AUX ARRÊTS DE TRAVAIL, AUX " -"DÉFAILLANCES ET AUX DYSFONCTIONNEMENTS INFORMATIQUES OU TOUT AUTRE DOMMAGE " -"OU PERTE LIÉE À L'UTILISATION DU PRÉSENT DOCUMENT ET DE SES VERSIONS DE MISE " -"À JOUR, ET CE MÊME SI CES PARTIES ONT ÉTÉ INFORMÉES DE LA POSSIBILITÉ DE " -"TELS DOMMAGES." - -#: ../C/gdm.xml:28(para) -msgid "" -"DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS " -"OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: " -"<placeholder-1/>" -msgstr "" -"LE PRÉSENT DOCUMENT ET SES VERSIONS MODIFIÉES SONT FOURNIS SELON LES TERMES " -"DE LA LICENCE DE DOCUMENTATION LIBRE GNU SACHANT QUE : <placeholder-1/>" - -#: ../C/gdm.xml:71(releaseinfo) ../C/gdm.xml:80(para) -msgid "" -"This manual describes version 2.19.7 of the GNOME Display Manager. It was " -"last updated on 07/09/2007." -msgstr "" -"Ce manuel documente la version 2.19.7 du gestionnaire de connexions GNOME. " -"La dernière version date du 09/07/2007." - -#: ../C/gdm.xml:78(title) -msgid "Terms and Conventions Used in This Manual" -msgstr "Termes et conventions utilisés dans ce manuel" - -#: ../C/gdm.xml:85(para) -msgid "" -"Chooser - A program used to select a remote host for managing a display " -"remotely on the attached display (<command>gdmchooser</command>)." -msgstr "" -"Sélecteur - Un programme utilisé pour sélectionner un hôte distant pour " -"gérer cet affichage à distance sur l'affichage lié (<command>gdmchooser</" -"command>)." - -#: ../C/gdm.xml:90(para) -msgid "" -"Configurator - The configuration application (<command>gdmsetup</command>)." -msgstr "" -"Configurateur - L'application de configuration (<command>gdmsetup</command>)." - -#: ../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 "" -"GDM - Le gestionnaire de connexions. Utilisé pour décrire l'ensemble des " -"paquets de ce logiciel. Parfois désigné sous le nom de GDM2." - -#: ../C/gdm.xml:100(para) -msgid "gdm - The Gnome Display Manager daemon (<command>gdm</command>)." -msgstr "" -"gdm - Le démon du gestionnaire de connexions GNOME (<command>gdm</command>)." - -#: ../C/gdm.xml:104(para) -msgid "" -"Greeter - The graphical login window (<command>gdmlogin</command> or " -"<command>gdmgreeter</command>)." -msgstr "" -"Bannière d'accueil - La fenêtre d'identification (<command>gdmlogin</" -"command> ou <command>gdmgreeter</command>)." - -#: ../C/gdm.xml:109(para) -msgid "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)." -msgstr "" -"Bannière GTK+ - La fenêtre d'identification standard (<command>gdmlogin</" -"command>)." - -#: ../C/gdm.xml:113(para) -msgid "PAM - Pluggable Authentication Mechanism" -msgstr "" -"PAM - Mécanisme d'authentification enfichable (Pluggable Authentication " -"Mechanism)." - -#: ../C/gdm.xml:117(para) -msgid "" -"Themed Greeter - The themable login window ( <command>gdmgreeter</command>)." -msgstr "" -"Bannière avec thème - La fenêtre d'identification à thème " -"(<command>gdmgreeter</command>)." - -#: ../C/gdm.xml:122(para) -msgid "XDMCP - X Display Manage Protocol" -msgstr "XDMCP - Protocole de gestion d'affichage X." - -#: ../C/gdm.xml:126(para) -msgid "" -"Paths that start with a word in angle brackets are relative to the " -"installation prefix. I.e. <filename><share>/pixmaps/</filename> refers " -"to <filename><share>/pixmaps</filename> if GDM was configured with " -"<command>--prefix=/usr</command>. Normally also note that GDM is installed " -"with <command>--sysconfigdir=<etc>/X11</command>, meaning any path to " -"which we refer to as <filename><etc>/gdm/PreSession</filename> usually " -"means <filename><etc/X11>/gdm/PreSession</filename>. Note that for " -"interoperability it is recommended that you use a --prefix of <filename>/" -"usr</filename> and a --sysconfdir of <filename><etc>/X11</filename>." -msgstr "" -"Les chemins commençant par un mot entre chevrons sont relatifs au préfixe " -"d'installation. Par exemple, <filename><share>/pixmaps/</filename> se " -"réfère à <filename>usr/share/pixmaps</filename> si GDM a été configuré avec " -"<command>--prefix=/usr</command>. En principe, il faut savoir que GDM est " -"installé avec <command>--sysconfigdir=<etc>/X11</command>, ce qui " -"signifie que tout chemin du style <filename><etc>/gdm/PreSession</" -"filename> signifie généralement <filename><etc/X11>/gdm/PreSession</" -"filename>. Pour des raisons d'interopérabilité, il est conseillé d'utiliser " -"un --prefix <filename>/usr</filename> et un --sysconfdir <filename><" -"etc>/X11</filename>." - -#: ../C/gdm.xml:142(title) -msgid "Overview" -msgstr "Vue d'ensemble" - -#: ../C/gdm.xml:145(title) -msgid "Introduction" -msgstr "Introduction" - -#: ../C/gdm.xml:149(para) -msgid "" -"The Gnome Display Manager (GDM) is a display manager that implements all " -"significant features required for managing attached and remote displays. GDM " -"was written from scratch and does not contain any XDM / X Consortium code." -msgstr "" -"Le gestionnaire de connexions GNOME (GDM) est un gestionnaire d'affichage " -"qui implémente tous les outils nécessaires à la gestion des affichages liés " -"ou distants. GDM a été complètement réécrit et ne contient pas de code de " -"XDM ou du consortium X." - -#: ../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 "" -"Il est à noter que GDM est hautement configurable, et que beaucoup de " -"paramètres de configuration touchent à la sécurité. Les points auxquels il " -"s'agit de prêter attention sont mis en évidence dans ce document et dans les " -"fichiers de configuration GDM." - -#: ../C/gdm.xml:162(para) -msgid "" -"For further information about GDM, see the <ulink type=\"http\" url=\"http://" -"www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. Please " -"submit any bug reports or enhancement requests to the \"gdm\" category in " -"<ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</" -"ulink>. You can also send a message to the <address><email>gdm-list@gnome." -"org</email></address> mail list to discuss any issues or concerns with the " -"GDM program." -msgstr "" -"Pour plus d'informations à propos de GDM, visitez <ulink type=\"http\" url=" -"\"http://www.gnome.org/projects/gdm/\">le site Web du projet GDM</ulink>. " -"Merci de nous soumettre vos rapports d'anomalie ou propositions " -"d'amélioration dans la catégorie « gdm » de <ulink type=\"http\" url=" -"\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>. Vous pouvez aussi " -"envoyer un message sur la liste de diffusion <address><email>gdm-list@gnome." -"org</email></address> pour discuter de l'évolution ou des problèmes liés au " -"programme GDM." - -#: ../C/gdm.xml:175(title) -msgid "Interface Stability" -msgstr "Stabilité de l'interface" - -#: ../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 " -"<filename>server-foo</filename>." -msgstr "" -"Les paires clé/valeur définies dans les fichiers de configuration de GDM et " -"l'emplacement de ces fichiers sont considérés comme étant des interfaces " -"stables et tout changement devrait respecter la compatibilité descendante. " -"Il est à noter que cela inclut les fonctionnalités telles que les scripts " -"GDM (Init, PreSession, PostSession, PostLogin, XKeepsCrashing, etc.), " -"l'emplacement des répertoires (ServAuthDir, PidFile, etc.), les applications " -"systèmes (SoundProgram), etc. Certaines valeurs de configuration dépendent " -"d'interfaces du système d'exploitation et ont besoin d'être modifiées pour " -"fonctionner sur certains systèmes. Les exemples typiques sont HaltCommand, " -"RebootCommand, CustomCommands, SuspendCommand, StandardXServer, Xnest, " -"SoundProgram et la valeur « commande » de chaque <filename>server-foo</" -"filename>." - -#: ../C/gdm.xml:193(para) -msgid "" -"Command-line interfaces for GDM programs installed to <filename><bin></" -"filename> and <filename><sbin></filename> 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 "" -"Les interfaces en ligne de commande des programmes GDM installés dans " -"<filename><bin></filename> et <filename><sbin></filename> sont " -"considérées comme stables. Référez-vous à la documentation de votre " -"distribution pour voir s'il existe des changements spécifiques à votre " -"distribution pour ces interfaces de GDM et quel support existe pour ceux-ci." - -#: ../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 <command>gdmchooser</command>. These " -"arguments have been changed to now use two dashes." -msgstr "" -"À partir des séries de développement GDM 2.15, certains arguments à un seul " -"tiret ne sont plus pris en charge. Ceci inclut les arguments « -" -"xdmaddress », « -clientaddress » et « -connectionType » utilisés par " -"<command>gdmchooser</command>. Ces arguments ont été modifiés pour être " -"utilisés avec deux tirets." - -#: ../C/gdm.xml:209(para) -msgid "" -"If issues are discovered that break compatibility, please file a bug with an " -"\"urgent\" priority." -msgstr "" -"Si vous découvrez des éléments qui ne respectent pas la compatibilité, " -"saisissez un rapport d'anomalie avec la priorité « urgent »." - -#: ../C/gdm.xml:216(title) -msgid "The GDM Daemon" -msgstr "Le démon GDM" - -#: ../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 " -"<filename>Init</filename>, <filename>PostLogin</filename>, " -"<filename>PreSession</filename>, and <filename>PostSession</filename> " -"scripts discussed below are discussed in this \"Configuring GDM section\"." -msgstr "" -"Le démon GDM est responsable de la gestion des affichages du système. Ceci " -"inclut l'authentification des utilisateurs, le démarrage de la session " -"utilisateur et la fermeture de celle-ci. GDM est configurable et les moyens " -"de le configurer sont décrits dans la section « Configuration de GDM » de ce " -"document. Les scripts <filename>Init</filename>, <filename>PostLogin</" -"filename>, <filename>PreSession</filename> et <filename>PostSession</" -"filename> mentionnés ci-dessous sont abordés dans la section « Configuration " -"de GDM »." - -#: ../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 "" -"Le démon GDM gère le protocole de socket de domaine UNIX qui peut être " -"employé pour commander des aspects de son comportement et pour demander des " -"informations. Ce protocole est décrit dans la section « Contrôle de GDM » de " -"ce document." - -#: ../C/gdm.xml:236(para) -msgid "" -"GDM can be asked to manage a display a number of ways. Attached displays are " -"always managed when GDM starts and will be restarted when a user's session " -"is finished. Remote displays can be requested via XDMCP, flexible displays " -"via the <command>gdmflexiserver</command> command, and dynamic displays via " -"the <command>gdmdynamic</command> command. Displays that are started on " -"request are not restarted on session exit." -msgstr "" -"On peut demander à GDM de gérer un affichage de plusieurs manières. Les " -"affichages liés sont toujours gérés lorsque GDM démarre et sont redémarrés " -"lorsqu'une session utilisateur est terminée. Les affichages distants peuvent " -"être appelés par XDMCP, les affichages flexibles par la commande " -"<command>gdmflexiserver</command> et les affichages dynamiques par la " -"commande <command>gdmdynamic</command>. Les affichages démarrés sur appel ne " -"sont pas redémarrés lors de la fermeture d'une session." - -#: ../C/gdm.xml:246(para) -msgid "" -"When the GDM daemon is asked to manage a display, it will fork an X server " -"process, then run the <filename>Init</filename> script as the root user, and " -"start the login GUI dialog as a slave process on the display. GDM can be " -"configured to use either <command>gdmgreeter</command> (the default) or " -"<command>gdmlogin</command> as the GUI dialog program. The " -"<command>gdmlogin</command> program supports accessibility while the " -"<command>gdmgreeter</command> program supports greater themeability. The GUI " -"dialog is run as the unpriviledged \"gdm\" user/group which is described in " -"the \"Security\" section below. The GUI dialog communicates with the daemon " -"via a sockets protocol and via standard input/output. The slave, for example " -"passes the username and password information to the GDM daemon via standard " -"input/output so the daemon can handle the actual authentication." -msgstr "" -"Lorsque le démon GDM reçoit une demande de gestion d'affichage, il va " -"générer un processus du serveur X, puis lancer le script <filename>Init</" -"filename> en tant qu'utilisateur root et démarrer la boîte de dialogue " -"graphique d'identification comme processus esclave dans l'affichage. GDM " -"peut être configuré pour utiliser soit <command>gdmgreeter</command> (par " -"défaut) soit <command>gdmlogin</command> comme programme d'interface. Le " -"programme <command>gdmlogin</command> prend en charge l'accessibilité alors " -"que le programme <command>gdmgreeter</command> gère mieux l'utilisation de " -"thèmes. La fenêtre d'identification est lancée avec l'utilisateur et groupe " -"non privilégié « gdm », décrit dans la section « Sécurité » ci-dessous. La " -"fenêtre d'identification communique avec le démon au moyen d'un protocole de " -"sockets et par l'entrée/sortie standard. Par exemple, le processus esclave " -"transmet les informations du nom d'utilisateur et du mot de passe au démon " -"GDM par l'entrée/sortie standard afin que le démon puisse s'occuper de " -"l'authentification réelle." - -#: ../C/gdm.xml:263(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 "" -"L'écran de la fenêtre d'identification graphique permet à l'utilisateur de " -"sélectionner quelle session il veut démarrer et quelle langue il souhaite " -"utiliser. Les sessions sont définies dans des fichiers se terminant par " -"l'extension .desktop. Vous trouvez plus d'informations sur ces fichiers dans " -"la section « Configuration ». L'utilisateur saisit son nom et son mot de " -"passe, et si l'authentification réussit, GDM lance la session demandée par " -"l'utilisateur. Il est possible de configurer GDM pour ne pas utiliser le " -"procédé d'authentification en activant les fonctionnalités de connexion " -"automatique ou différée dans la configuration de GDM. La fenêtre " -"d'identification peut aussi être configurée pour fournir des fonctions " -"supplémentaires à l'utilisateur, comme le navigateur de figures, la capacité " -"d'arrêter, de redémarrer ou de mettre en veille le système, ou encore la " -"possibilité de modifier la configuration de la connexion (après avoir saisi " -"le mot de passe d'administration)." - -#: ../C/gdm.xml:278(para) -msgid "" -"GDM, by default, will use Pluggable Authentication Modules (PAM) for " -"authentication, but can also support regular crypt and shadow passwords on " -"legacy systems. After authenticating a user, the daemon runs the " -"<filename>PostLogin</filename> script as root, and forks a slave process to " -"start the requested session. This slave process runs the " -"<filename>PreSession</filename> script as root, sets up the user's " -"environment, and starts the requested session. GDM keeps track of the user's " -"default session and language in the user's <filename>~/.dmrc</filename> and " -"will use these defaults if the user did not pick a session or language in " -"the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN " -"interface after user authentication to tell the X server to be restarted as " -"the user instead of as root for added security. When the user's session " -"exits, the GDM daemon will run the <filename>PostSession</filename> script " -"as root." -msgstr "" -"Par défaut, GDM utilise PAM (Pluggable Authentication Modules) pour " -"l'authentification, mais il peut aussi prendre en charge les mots de passe " -"« crypt » et « shadow » des systèmes traditionnels. Après avoir authentifié " -"un utilisateur, le démon exécute le script <filename>PostLogin</filename> en " -"tant que root et génère un processus esclave pour démarrer la session " -"demandée. Ce processus exécute alors le script <filename>PreSession</" -"filename> en tant que root, met en place l'environnement utilisateur et " -"démarre la session demandée. GDM conserve la trace de la session par défaut " -"et de la langue de l'utilisateur dans le fichier <filename>~/.dmrc</" -"filename> de l'utilisateur. Il utilise ces informations si l'utilisateur ne " -"choisit pas spécifiquement une session ou une langue dans la fenêtre " -"d'identification. Sur Solaris, GDM (depuis la version 2.8.0.3) utilise " -"l'interface SDTLOGIN après l'authentification de l'utilisateur pour " -"signifier au serveur X de redémarrer en tant qu'utilisateur au lieu de root, " -"afin d'augmenter la sécurité. Lorsque la session de l'utilisateur se " -"termine, le démon GDM exécute le script <filename>PostSession</filename> en " -"tant que root." - -#: ../C/gdm.xml:295(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 " -"<filename>PamStack</filename> 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 "" -"Il est à noter que par défaut, GDM utilise le nom de service « gdm » pour " -"une connexion normale et le nom de service « gdm-autologin » pour une " -"connexion automatique. L'option de configuration <filename>PamStack</" -"filename> peut être utilisée afin de définir un autre nom de service. Par " -"exemple, si l'on indique « foo », GDM utilise le nom de service « foo » pour " -"une connexion normale et « foo-autologin » pour une connexion automatique." - -#: ../C/gdm.xml:305(para) -msgid "" -"For those looking at the code, the gdm_verify_user function in " -"<filename>daemon/verify-pam.c</filename> is used for normal login and the " -"gdm_verify_setup_user function is used for automatic login." -msgstr "" -"Pour ceux qui examinent le code, la fonction gdm_verify_user dans " -"<filename>daemon/verify-pam.c</filename> est utilisée pour une connexion " -"normale et la fonction gdm_verify_setup_user pour une connexion automatique." - -#: ../C/gdm.xml:313(title) -msgid "Different Display Types" -msgstr "Différents types d'affichage" - -#: ../C/gdm.xml:315(para) -msgid "" -"GDM supports three different display types: attached displays, flexible " -"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 "" -"GDM prend en charge trois différents types d'affichage : les affichages " -"liés, les affichages flexibles et les affichages XDMCP distants. La sous-" -"section « Définitions du serveur X » de la section « Configuration » " -"explique comment le serveur X peut être configuré pour les différents " -"affichages." - -#: ../C/gdm.xml:323(para) -msgid "" -"Attached (also known as local or static) displays are always started by the " -"daemon, and when they die or are killed, they are restarted. GDM can run as " -"many of these as needed. GDM can also manage displays on which it does not " -"manage a GUI login, thus GDM can be used for supporting X terminals. The " -"\"Attached DISPLAY Configuration\" subsection of the \"Configuration\" " -"section describes how attached displays are defined." -msgstr "" -"Les affichages liés (aussi appelés locaux ou statiques) sont toujours " -"démarrés par le démon, et lorsqu'ils meurent ou qu'ils sont terminés, ils " -"redémarrent. GDM peut en exécuter autant que nécessaire. GDM peut aussi " -"gérer des affichages pour lesquels il ne gère par de fenêtre " -"d'identification, ce qui signifie que GDM peut être utilisé pour prendre en " -"charge des terminaux X. La sous-section « Configuration de l'affichage X " -"lié » de la section « Configuration » explique comment sont définis les " -"affichages liés." - -#: ../C/gdm.xml:333(para) -msgid "" -"Flexible (also known as on-demand) displays are only available to users " -"logged 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 "" -"Les affichages flexibles (appelés aussi « à la demande ») ne sont " -"disponibles que pour les utilisateurs connectés sur la console. Le lancement " -"d'un affichage flexible verrouille la session actuelle et présente un nouvel " -"écran de connexion par-dessus la session en cours de fonctionnement. Si un " -"affichage flexible est déjà lancé et que l'utilisateur en demande un " -"nouveau, il verra apparaître une boîte de dialogue affichant les affichages " -"flexibles existants. Il peut alors choisir de revenir à un affichage " -"précédent ou de démarrer un nouvel affichage flexible. S'il revient à un " -"affichage existant, l'utilisateur doit ressaisir son mot de passe dans le " -"programme de verrouillage de session. Le fichier de configuration GDM " -"indique le nombre maximum d'affichages flexibles autorisés sur un système." - -#: ../C/gdm.xml:347(para) -msgid "" -"Flexible displays may be started by running the <command>gdmflexiserver</" -"command> 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 "" -"Les affichages flexibles peuvent être lancés en exécutant la commande " -"<command>gdmflexiserver</command> ou en appelant directement le protocole " -"socket de GDM. Certains programmes de verrouillage de session offrent un " -"bouton pour démarrer un nouvelle session flexible. Cela permet à un " -"utilisateur de démarrer une nouvelle session même si l'affichage est " -"verrouillé. L'applet GNOME de changement d'utilisateur utilise aussi le " -"protocole socket pour présenter une interface d'applet dans un tableau de " -"bord GNOME pour gérer facilement les affichages de plusieurs utilisateurs. " -"Les affichages flexibles ne sont pas redémarrés lorsqu'une session " -"utilisateur se termine. Les affichages flexibles exigent la prise en charge " -"des terminaux virtuels (VT) dans le noyau, et ne sont pas disponibles dans " -"le cas contraire (comme sur Solaris)." - -#: ../C/gdm.xml:360(para) -msgid "" -"The <filename>FlexibleXServers</filename>, <filename>FirstVT=7</filename>, " -"<filename>VTAllocation</filename>, and <filename>FlexiReapDelayMinutes</" -"filename> configuration settings are used to configure how flexible displays " -"operate." -msgstr "" -"Les paramètres de configuration <filename>FlexibleXServers</filename>, " -"<filename>FirstVT=7</filename>, <filename>VTAllocation</filename> et " -"<filename>FlexiReapDelayMinutes</filename> sont utilisés pour configurer le " -"fonctionnement des affichages flexibles." - -#: ../C/gdm.xml:367(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 " -"<command>gdmflexiserver -n</command> 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 <filename>Xnest</filename> " -"configuration option is used to configure how nested displays are started." -msgstr "" -"Les affichages imbriqués sont accessibles même si l'utilisateur n'est pas " -"connecté sur la console. Ils lancent un écran d'identification dans une " -"fenêtre de la session en cours de l'utilisateur. Cela peut être utile si " -"l'utilisateur dispose de plus d'un compte sur un ordinateur et souhaite se " -"connecter à un autre compte sans fermer ou verrouiller la session en cours. " -"Les affichages imbriqués peuvent être démarrés en exécutant la commande " -"<command>gdmflexiserver -n</command> ou en appelant directement le protocole " -"socket GDM. Les affichages imbriqués exigent que le serveur X prenne en " -"charge un serveur X imbriqué comme Xnest ou Xephyr. L'option de " -"configuration <filename>Xnest</filename> est utilisée pour configurer la " -"manière de démarrer les affichages imbriqués." - -#: ../C/gdm.xml:380(para) -msgid "" -"The <command>gdmdynamic</command> is similar to <command>gdmflexiserver</" -"command> in the sense that it allows the user to manage displays " -"dynamically. However displays started with <command>gdmdynamic</command> are " -"treated as attached 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 \"Attached 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 "" -"La commande <command>gdmdynamic</command> est semblable à " -"<command>gdmflexiserver</command> dans le sens où elle permet à " -"l'utilisateur de gérer des affichages dynamiquement. Cependant, les " -"affichages démarrés par la commande <command>gdmdynamic</command> sont " -"considérés comme des affichages liés ; ils sont donc redémarrés " -"automatiquement lorsque la session se termine. Cette commande est destinée à " -"une gestion plus efficace des affichages sur un serveur multi-utilisateurs " -"(plusieurs affichages connectés sur un seul serveur). En d'autres mots, " -"cette commande de gérer des affichages sans coder statiquement leurs " -"informations dans la section « Attached DISPLAY Configuration » du fichier " -"de configuration. C'est bien utile pour donner par exemple la possibilité " -"d'ajouter de nouveaux affichages sur le serveur sans devoir redémarrer GDM." - -#: ../C/gdm.xml:395(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 "" -"Le dernier type d'affichage est XDMCP distant, décrit dans la section " -"suivante. Les hôtes distants peuvent se connecter à GDM et voir apparaître " -"l'écran de connexion si cet affichage est activé. Certaines choses sont " -"différentes pour les sessions distantes. Par exemple, le menu Actions qui " -"permet d'éteindre, de redémarrer, de mettre en veille ou de configurer GDM " -"n'est pas affiché." - -#: ../C/gdm.xml:406(title) -msgid "XDMCP" -msgstr "XDMCP" - -#: ../C/gdm.xml:410(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 "" -"Le démon GDM peut être configuré pour écouter et gérer les requêtes XDMCP (X " -"Display Manage Protocol) provenant d'hôtes distants. Par défaut, XDMCP est " -"désactivé, mais il peut être activé au besoin. Si GDM a été compilé avec la " -"prise en charge de TCP Wrapper, le démon ne donnera accès qu'aux hôtes " -"indiqués dans la section de service GDM du fichier de configuration de TCP " -"Wrappers." - -#: ../C/gdm.xml:419(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 "" -"GDM contient plusieurs mesures afin d'être plus résistant aux attaques par " -"déni de service sur le service XDMCP. Beaucoup de paramètres du protocole, " -"des délais d'interaction, etc. peuvent être configurés. Les valeurs par " -"défaut devraient cependant convenir pour la plupart des systèmes. Ne les " -"modifiez pas sans savoir exactement ce que vous faites." - -#: ../C/gdm.xml:427(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 "" -"GDM écoute sur le port UDP 177 et répond aux requêtes QUERY et " -"BROADCAST_QUERY en envoyant un paquet WILLING au demandeur." - -#: ../C/gdm.xml:432(para) -msgid "" -"GDM can also be configured to honor INDIRECT queries and present a host " -"chooser to the remote display. GDM will remember the user's choice and " -"forward subsequent requests to the chosen manager. GDM also supports an " -"extension to the protocol which will make it forget the redirection once the " -"user's connection succeeds. This extension is only supported if both daemons " -"are GDM. It is transparent and will be ignored by XDM or other daemons that " -"implement XDMCP." -msgstr "" -"GDM peut aussi être configuré pour répondre aux requêtes INDIRECT et " -"présenter un sélecteur d'hôte à l'affichage distant. GDM mémorise le choix " -"de l'utilisateur et fait suivre les requêtes suivantes au gestionnaire " -"sélectionné. GDM gère également une extension au protocole qui lui fait " -"oublier la redirection dès que la connexion de l'utilisateur a réussi. Cette " -"extension n'est prise en charge que si les deux démons sont GDM. Ceci est " -"transparent et est ignoré par XDM ou d'autres démons qui implémentent XDMCP." - -#: ../C/gdm.xml:442(para) -msgid "" -"If XDMCP seems to not be working, make sure that all machines are specified " -"in <filename>/etc/hosts</filename>." -msgstr "" -"Si XDMCP semble ne pas fonctionner, assurez-vous que toutes les machines " -"sont présentes dans <filename>/etc/hosts</filename>." - -#: ../C/gdm.xml:447(para) -msgid "" -"Refer to the \"Security\" section for information about security concerns " -"when using XDMCP." -msgstr "" -"Référez-vous à la section « Sécurité » pour des informations sur les " -"questions de sécurité lors de l'utilisation de XDMCP." - -#: ../C/gdm.xml:454(title) -msgid "Securing Remote Connection Through SSH" -msgstr "Sécurisation de connexions distantes avec SSH" - -#: ../C/gdm.xml:457(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 "" -"Comme expliqué dans la section « Sécurité », XDMCP n'utilise aucune sort de " -"chiffrement, ce qui en fait un protocole non sécurisé en lui-même. Comme " -"XDMCP utilise UDP comme couche de transport réseau, il n'est pas possible de " -"le sécuriser simplement au travers d'un tunnel SSH." - -#: ../C/gdm.xml:464(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 "" -"Pour remédier à ce problème, GDM peut être configuré au moment de la " -"compilation avec l'option --enable-secureremote. Dans ce cas, GDM propose " -"dans la liste des sessions une session nommée « Connexion distante " -"sécurisée ». Au démarrage d'une connexion de ce type, l'utilisateur peut " -"saisir le nom et l'adresse de connexion à l'hôte ; si ce dernier exécute un " -"serveur SSH, l'utilisateur est connecté au serveur sur lequel la session X " -"par défaut est démarrée et affichée sur l'hôte local." - -#: ../C/gdm.xml:474(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 "" -"L'utilisation de cette session offre une connexion réseau bien mieux " -"sécurisée et exige uniquement la présence d'un serveur SSH fonctionnant sur " -"l'hôte distant." - -#: ../C/gdm.xml:481(title) -msgid "The GTK+ Greeter" -msgstr "La bannière GTK+" - -#: ../C/gdm.xml:483(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 "" -"La bannière GTK+ est l'interface graphique par défaut présentée à " -"l'utilisateur. La bannière contient un menu dans la partie supérieure, un " -"navigateur de figures facultatif, un logo facultatif et une zone de saisie " -"de texte. Cette bannière prend pleinement en charge l'accessibilité, et " -"devrait donc être utilisée par les utilisateurs qui en ont besoin." - -#: ../C/gdm.xml:491(para) -msgid "" -"The text entry field is used for entering logins, passwords, passphrases " -"etc. <command>gdmlogin</command> 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 "" -"La zone de saisie de texte est utilisée pour saisir l'identifiant, le mot de " -"passe, la phrase de passe, etc. <command>gdmlogin</command> est contrôlé par " -"le démon sous-jacent et est sans état. Le démon contrôle la bannière par un " -"protocole simple par lequel il peut demander à la bannière une chaîne de " -"texte avec l'écho activé ou non. De la même manière, le démon peut changer " -"l'étiquette au-dessus de la zone de saisie de texte pour qu'elle corresponde " -"à ce que le système d'authentification attend de la part de l'utilisateur." - -#: ../C/gdm.xml:501(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 "" -"La barre de menus au sommet de la bannière permet à l'utilisateur de " -"sélectionner le type de session ou l'environnement de bureau, une langue (ou " -"locale) adéquate, de stopper, démarrer ou mettre en veille l'ordinateur, de " -"configurer GDM (en saisissant le mot de passe d'administration), de changer " -"le thème GTK+ ou de démarrer un sélecteur XDMCP." - -#: ../C/gdm.xml:509(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 " -"<filename>Logo</filename> option in the reference section below for details." -msgstr "" -"De manière facultative, la bannière peut afficher un logo dans la fenêtre " -"d'identification. L'image doit être dans un format lisible par la " -"bibliothèque gdk-pixbuf (GIF, JPG, PNG, TIFF, XPM et peut-être d'autres) et " -"elle doit pouvoir être lue par l'utilisateur GDM. Consultez l'option " -"<filename>Logo</filename> dans la section Référence pour plus de détails." - -#: ../C/gdm.xml:519(title) -msgid "The Themed Greeter" -msgstr "La bannière à thème" - -#: ../C/gdm.xml:521(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 <filename>GraphicalTheme</" -"filename> 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 "" -"La bannière à thème est une interface de la bannière qui remplit tout " -"l'écran et qui peut être thématisée. Les thèmes peuvent être sélectionnés et " -"de nouveaux thèmes installés par l'application de configuration ou en " -"définissant la clé de configuration <filename>GraphicalTheme</filename>. La " -"bannière à thème est très semblable à la bannière GTK+, car elle est aussi " -"contrôlée par le démon sous-jacent, elle est sans état et utilise le même " -"protocole de communication avec le démon." - -#: ../C/gdm.xml:531(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 "" -"L'apparence de cette bannière est vraiment définie par le thème, ce qui fait " -"que les éléments d'interface peuvent être différents. La seule chose qui " -"doit toujours être présente est la zone de saisie de texte telle qu'elle est " -"décrite ci-dessus pour la bannière GTK+. Le thème peut contenir des boutons " -"permettant à l'utilisateur de choisir une langue (ou locale) adéquate, de " -"stopper, redémarrer ou mettre en veille l'ordinateur, de configurer GDM (en " -"donnant le mot de passe d'administration) ou de lancer un sélecteur XDMCP." - -#: ../C/gdm.xml:541(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 "" -"Vous pouvez toujours obtenir un menu des actions disponibles en appuyant sur " -"la touche F10. Cela peut se révéler utile si le thème n'affiche pas certains " -"boutons alors que vous souhaitez effectuer une action autorisée par la " -"configuration GDM." - -#: ../C/gdm.xml:549(title) -msgid "The GDM Face Browser" -msgstr "Le navigateur de figures GDM" - -#: ../C/gdm.xml:551(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 " -"<filename>Browser</filename> 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 "" -"GDM met à disposition un navigateur de figures qui affiche une liste " -"d'utilisateurs pouvant se connecter ainsi qu'une icône pour chaque " -"utilisateur. À partir de la version 2.18.1, l'option de configuration " -"<filename>Browser</filename> doit être définie à « true » pour que cette " -"fonctionnalité soit disponible. Dans les versions précédentes, cela n'était " -"nécessaire qu'avec la bannière GTK+. Avec la bannière à thème, le navigateur " -"de figures n'est disponible que si le thème GDM contient un type d'élément " -"« userlist »." - -#: ../C/gdm.xml:561(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 <command>gdmsetup</command>. This feature is " -"most practical to use on a system with a smaller number of users." -msgstr "" -"Par défaut, le navigateur de figures est désactivé car la présentation des " -"noms d'utilisateur sur l'écran de connexion n'est pas approprié sur bien des " -"systèmes pour des raisons de sécurité. GDM nécessite également certains " -"paramètres pour définir quels utilisateurs doivent être visibles. Cette " -"configuration peut se faire dans l'onglet « Utilisateurs » de " -"<command>gdmsetup</command>. Cette fonctionnalité est surtout utile sur des " -"systèmes qui comportent un petit nombre d'utilisateurs." - -#: ../C/gdm.xml:570(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 <filename><share>/pixmaps/faces/</filename> directory (though " -"this can be configured with the <filename>GlobalFaceDir</filename> " -"configuration option) and the filename should be the name of the user, " -"optionally with a <filename>.png</filename> 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 "" -"Les icônes utilisées par GDM peuvent être installées globalement par " -"l'administrateur ou peuvent être placées dans les dossiers personnels des " -"utilisateurs. Dans le premier cas, elles devraient se trouver dans le " -"répertoire <filename><share>/pixmaps/faces/</filename> (bien que ceci " -"peut être défini par l'option de configuration <filename>GlobalFaceDir</" -"filename>) et le nom de fichier doit correspondre au nom de l'utilisateur, " -"avec l'extension <filename>.png</filename> facultative. Les icônes de " -"figures placées dans le répertoire global doivent être accessibles en " -"lecture pour l'utilisateur GDM. Cependant, le démon fait office de proxy " -"pour la bannière ce qui fait que les images ne doivent pas forcément être " -"lisibles par l'utilisateur « gdm », mais par root." - -#: ../C/gdm.xml:583(para) -msgid "" -"Users may run the <command>gdmphotosetup</command> command to configure the " -"image to use for their userid. This program properly scales the file down if " -"it is larger than the <filename>MaxIconWidth</filename> or " -"<filename>MaxIconHeight</filename> configuration options and places the icon " -"in a file called <filename>~/.face</filename>. Although " -"<command>gdmphotosetup</command> scales user images automatically, this does " -"not guarantee that user images are properly scaled since a user may create " -"their <filename>~/.face</filename> file by hand." -msgstr "" -"Les utilisateurs peuvent exécuter la commande <command>gdmphotosetup</" -"command> pour configurer l'image utilisée avec leur identifiant. Ce " -"programme redimensionne correctement le fichier si celui-ci dépasse les " -"limites fixées par les options de configuration <filename>MaxIconWidth</" -"filename> ou <filename>MaxIconHeight</filename>, et il place l'icône dans un " -"fichier nommé <filename>~/.face</filename>. Même si <command>gdmphotosetup</" -"command> redimensionne automatiquement les images, cela ne garantit pas que " -"les images soient toutes de dimension correcte, car un utilisateur pourrait " -"aussi créer son fichier <filename>~/.face</filename> lui-même." - -#: ../C/gdm.xml:595(para) -msgid "" -"GDM will first look for the user's face image in <filename>~/.face</" -"filename>. If not found, it will try <filename>~/.face.icon</filename>. If " -"still not found, it will use the value defined for \"face/picture=\" in the " -"<filename>~/.gnome2/gdm</filename> file. Lastly, it will try <filename>~/." -"gnome2/photo</filename> and <filename>~/.gnome/photo</filename> which are " -"deprecated and supported for backwards compatibility." -msgstr "" -"GDM recherche d'abord l'image de l'utilisateur dans <filename>~/.face</" -"filename>. S'il ne trouve rien, il cherche <filename>~/.face.icon</" -"filename>. S'il ne trouve toujours rien, il utilise la valeur définie pour " -"« face/picture= » dans le fichier <filename>~/.gnome2/gdm</filename>. " -"Finalement, il regarde encore <filename>~/.gnome2/photo</filename> et " -"<filename>~/.gnome/photo</filename> qui sont obsolètes mais pris en charge " -"pour des raisons de compatibilité descendante." - -#: ../C/gdm.xml:606(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 <filename>DefaultFace</filename> " -"configuration option, normally <filename><share>/pixmaps/nobody.png</" -"filename>." -msgstr "" -"Si un utilisateur n'a pas défini d'image pour sa figure, GDM utilise l'icône " -"« stock_person » définie dans le thème GTK+ actuel. Si aucune image n'est " -"définie, il retourne à l'image définie dans l'option de configuration " -"<filename>DefaultFace</filename>, correspondant généralement à <filename><" -"share>/pixmaps/nobody.png</filename>." - -#: ../C/gdm.xml:614(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 <filename>Include</filename> 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 <filename>GlobalFaceDir</filename> configuration option." -msgstr "" -"Il faut savoir que le chargement et le redimensionnement des icônes de " -"figures situées dans les dossiers personnels peut devenir une tâche très " -"coûteuse en temps. Comme il n'est pas envisageable en pratique de charger " -"des images de figures au moyen de NIS ou NFS, GDM n'essaye même pas de les " -"charger si les dossiers personnels sont distants. De plus, GDM abandonne le " -"chargement après une attente de 5 secondes et n'affiche alors que les " -"utilisateurs dont il a réussi à obtenir l'image durant cet intervalle. " -"L'option de configuration <filename>Include</filename> peut être utilisée " -"pour définir un ensemble d'utilisateurs devant apparaître dans le navigateur " -"de figures. Pour autant que cette liste d'utilisateurs soit de taille " -"raisonnable, GDM ne devrait pas rencontrer de problème à accéder aux images " -"des figures. Pour éviter d'éventuels problèmes, il est conseillé de placer " -"les images de figures dans le répertoire défini dans l'option de " -"configuration <filename>GlobalFaceDir</filename>." - -#: ../C/gdm.xml:630(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 " -"<filename>IncludeAll</filename> option is set to true, then the password " -"file will be scanned and all users will be displayed. If " -"<filename>IncludeAll</filename> option is set to false, then the " -"<filename>Include</filename> option should contain a list of users separated " -"by commas. Only the users specified will be displayed. Any user listed in " -"the <filename>Exclude</filename> option and users whose UID's is lower than " -"<filename>MinimalUID</filename> will be filtered out regardless of the " -"<filename>IncludeAll</filename> setting. <filename>IncludeAll</filename> 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 "" -"Pour avoir le contrôle des utilisateurs qui apparaissent dans le navigateur " -"de figures, plusieurs options de configuration peuvent être utilisées. Si " -"l'option <filename>IncludeAll</filename> est définie à « true », le fichier " -"de mots de passe est analysé et tous les utilisateurs sont affichés. Si " -"l'option <filename>IncludeAll</filename> est définie à « false », l'option " -"<filename>Include</filename> doit contenir une liste d'utilisateurs séparés " -"par des virgules. Seuls les utilisateurs de la liste sont affichés. Tout " -"utilisateur présent dans la liste de l'option <filename>Exclude</filename> " -"et les utilisateurs dont le numéro d'identifiant est plus bas que " -"<filename>MinimalUID</filename> seront exclus, indépendamment de l'option " -"<filename>IncludeAll</filename>. Cette dernière n'est pas recommandée sur " -"les systèmes où les mots de passe sont chargés sur le réseau (comme avec " -"NIS), car cela peut devenir très lent, dès qu'un certain nombre " -"d'utilisateurs doivent être chargés par le réseau." - -#: ../C/gdm.xml:647(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 "" -"Lorsque le navigateur est activé, les noms d'utilisateurs valides sur le " -"système sont inévitablement exposés à un intrus potentiel. Ce n'est pas une " -"bonne solution si vous ne savez pas qui peut avoir accès à l'écran de " -"connexion. C'est encore plus sensible lorsque vous avez activé XDMCP " -"(désactivé par défaut)." - -#: ../C/gdm.xml:656(title) -msgid "Logging" -msgstr "Journalisation" - -#: ../C/gdm.xml:658(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 "" -"GDM lui-même utilise syslog pour journaliser les erreurs ou les états. Il " -"peut aussi journaliser les informations de débogage, qui peuvent être utiles " -"pour la résolution de problèmes lorsque GDM ne fonctionne pas correctement. " -"Cela peut être activé dans le fichier de configuration." - -#: ../C/gdm.xml:665(para) -msgid "" -"Output from the various X servers is stored in the GDM log directory, which " -"is configurable, but is usually <filename><var>/log/gdm/</filename>. " -"The output from the session can be found in a file called <filename><" -"display>.log</filename>. Four older files are also stored with " -"<filename>.1</filename> through <filename>.4</filename> 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 "" -"La sortie des différents serveurs X est stockée dans le répertoire journal " -"de GDM, qui est configurable, mais qui se trouve habituellement dans " -"<filename><var>/log/gdm/</filename>. La sortie provenant de la session " -"se trouve dans un fichier nommé <filename><display>.log</filename>. " -"Quatre fichiers plus anciens sont également conservés avec un suffixe de " -"<filename>.1</filename> à <filename>.4</filename>. Ils subissent une " -"rotation au fur et à mesure que d'autres sessions sont lancées sur cet " -"affichage. Vous pouvez consulter ces journaux pour voir ce que le serveur X " -"a produit lors de son démarrage." - -#: ../C/gdm.xml:677(para) -msgid "" -"The output from the user session is redirected to <filename>~/.xsession-" -"errors</filename> before even the <filename>PreSession</filename> 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 "" -"La sortie de la session utilisateur est redirigée dans <filename>~/.xsession-" -"errors</filename> avant même que le script <filename>PreSession</filename> " -"soit lancé. Il n'est donc pas vraiment nécessaire de le rediriger une " -"nouvelle fois dans le script de configuration de session. Et c'est ainsi que " -"cela se fait normalement. Si la session de l'utilisateur a duré moins de 10 " -"secondes, GDM part du principe que la session a échoué et permet à " -"l'utilisateur de voir ce fichier dans une boîte de dialogue avant de revenir " -"à l'écran de connexion. De cette façon, l'utilisateur peut voir les erreurs " -"de la dernière session et tenter de corriger le problème." - -#: ../C/gdm.xml:689(para) -msgid "" -"You can suppress the 10 second warning by returning code 66 from the " -"<filename>Xsession</filename>script or from your session binary (the default " -"<filename>Xsession</filename> 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 "" -"Vous pouvez supprimer l'avertissement des 10 secondes en retournant le code " -"66 dans le script <filename>Xsession</filename> ou dans le binaire de votre " -"session (le script <filename>Xsession</filename> par défaut propage ces " -"codes). Ceci peut être utile si vous avez des types de connexions spéciales " -"pour lesquelles une session de moins de 10 secondes n'est pas une erreur, ou " -"si vous avez déjà configuré la session pour afficher un message d'erreur et " -"que le message GDM est redondant et pourrait prêter à confusion." - -#: ../C/gdm.xml:699(para) -msgid "" -"The session output is piped through the GDM daemon and so the <filename>~/." -"xsession-errors</filename> 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 "" -"La sortie de la session est redirigée via le démon GDM ; en conséquence, le " -"fichier <filename>~/.xsession-errors</filename> est limité par GDM à environ " -"200 kilooctets pour empêcher une éventuelle attaque par déni de service sur " -"la session. À la lecture de certaines fausses données, une application " -"pourrait produire des avertissements ou des erreurs dans stderr ou stdout. " -"Cela pourrait remplir complètement le dossier personnel de l'utilisateur, " -"l'obligeant à se déconnecter et à retourner dans sa session pour effacer " -"cela. cela pourrait être particulièrement gênant si les quotas sont actifs. " -"GDM intercepte aussi correctement le signal XFSZ et bloque l'écriture dans " -"le fichier, ce qui, dans le cas contraire, amènerait à des sessions tuées si " -"le fichier était redirigé à l'ancienne façon depuis le script." - -#: ../C/gdm.xml:712(para) -msgid "" -"Note that some distributors seem to override the <filename>~/.xsession-" -"errors</filename> redirection and do it themselves in their own Xsession " -"script (set by the <filename>BaseXsession</filename> configuration key) " -"which means that GDM will not be able to trap the output and cap this file. " -"You also lose output from the <filename>PreSession</filename> 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 " -"<filename>BaseXsession</filename> configuration key for more information, " -"especially on how to handle multiple display managers using the same script." -msgstr "" -"Il est à noter que certaines distributions semblent ignorer la redirection " -"<filename>~/.xsession-errors</filename> et la réaliser elles-mêmes dans leur " -"propre script Xsession (défini par la clé de configuration " -"<filename>BaseXsession</filename>), ce qui signifie que GDM ne sera pas " -"capable d'intercepter la sortie et de limiter le fichier. La sortie du " -"script <filename>PreSession</filename> est également perdue, ce qui pourrait " -"compliquer le débogage par le fait que d'éventuels messages d'erreurs utiles " -"ne seraient écrits nulle part. Consultez la description de la clé de " -"configuration <filename>BaseXsession</filename> pour plus d'informations, " -"particulièrement sur la manière de gérer plusieurs gestionnaires d'affichage " -"à l'aide d'un même script." - -#: ../C/gdm.xml:726(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 <filename>/" -"tmp</filename> directory named <filename>/tmp/xses-<user>.XXXXXX</" -"filename> where the <filename>XXXXXX</filename> are some random characters." -msgstr "" -"Notez que dans le cas d'une session de secours ou si GDM ne peut ouvrir ce " -"fichier pour une raison quelconque, un fichier de remplacement sera créé " -"dans le répertoire <filename>/tmp</filename> avec le nom <filename>/tmp/xses-" -"<utilisateur>.XXXXXX</filename>, où <filename>XXXXXX</filename> " -"correspond à des caractères aléatoires." - -#: ../C/gdm.xml:734(para) -msgid "" -"If you run a system with quotas set, it would be good to delete the " -"<filename>~/.xsession-errors</filename> in the <filename>PostSession</" -"filename> script. Such that this log file doesn't unnecessarily stay around." -msgstr "" -"Si les quotas sont actifs sur votre système, il peut être utile de supprimer " -"le fichier <filename>~/.xsession-errors</filename> dans le script " -"<filename>PostSession</filename>, afin que ce fichier de journalisation " -"n'occupe pas de la place pour rien." - -#: ../C/gdm.xml:743(title) -msgid "Accessing Files" -msgstr "Accès aux fichiers" - -#: ../C/gdm.xml:745(para) -msgid "" -"In general GDM is very reluctant regarding reading/writing of user files " -"(such as the <filename>~/.dmrc</filename>, <filename>~/.face</filename>, " -"<filename>~/.xsession-errors</filename>, and <filename>~/.Xauthority</" -"filename> files). For instance it refuses to access anything but regular " -"files. Links, sockets and devices are ignored. The value of the " -"<filename>RelaxPermissions</filename> parameter determines whether GDM " -"should accept files writable by the user's group or others. These are " -"ignored by default." -msgstr "" -"En général, GDM est très prudent concernant la lecture et l'écriture dans " -"des fichiers d'utilisateur (tels que <filename>~/.dmrc</filename>, " -"<filename>~/.face</filename>, <filename>~/.xsession-errors</filename>et " -"<filename>~/.Xauthority</filename>). Par exemple, il refuse d'accéder aux " -"fichiers spéciaux. Les liens, sockets ou périphériques sont ignorés. La " -"valeur du paramètre <filename>RelaxPermissions</filename> détermine si GDM " -"doit accepter les fichiers accessibles en écriture par « groupe » et " -"« autres ». Par défaut, ces fichiers sont ignorés." - -#: ../C/gdm.xml:757(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 <filename>.Xauthority</" -"filename> file, a fallback cookie is created in the directory specified by " -"the <filename>UserAuthFBDir</filename> configuration setting (<filename>/" -"tmp</filename> by default)." -msgstr "" -"Toutes les opérations sur les fichiers utilisateurs sont réalisées avec " -"l'identifiant de l'utilisateur. Si le contrôle de validité du fichier " -"<filename>.Xauthority</filename> échoue, un cookie de secours est créé dans " -"le répertoire désigné par le paramètre de configuration " -"<filename>UserAuthFBDir</filename> (<filename>/tmp</filename> par défaut)." - -#: ../C/gdm.xml:765(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 "" -"Pour terminer, l'administrateur système peut indiquer la taille de fichier " -"maximum que GDM devrait accepter. Et, dans le cas où le navigateur de " -"figures est actif, une taille maximale d'icône, configurable, doit être " -"respectée. Sur des gros systèmes, il est cependant toujours conseillé de " -"désactiver le navigateur de figures pour des questions de performance. La " -"recherche des icônes dans les dossiers personnels, le redimensionnement et " -"l'affichage des icônes de figures peut consommer un temps important." - -#: ../C/gdm.xml:776(title) -msgid "GDM Performance" -msgstr "Performances de GDM" - -#: ../C/gdm.xml:778(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 "" -"Pour améliorer les performances, il est possible de compiler GDM pour qu'il " -"précharge les bibliothèques lors du premier affichage de bannière GDM. Il a " -"été démontré que ceci permet d'améliorer la rapidité de la première " -"connexion, car ces bibliothèques sont chargées en mémoire pendant que " -"l'utilisateur saisit son identifiant et son mot de passe." - -#: ../C/gdm.xml:786(para) -msgid "" -"To use this feature, configure GDM with the <command>--with-prefetch</" -"command> option. This will cause GDM to install the <command>gdmprefetch</" -"command> program to the <filename>libexecdir</filename> directory, install " -"the <filename>gdmprefetchlist</filename> to the <filename><etc>/gdm</" -"filename> directory, and set the <filename>PreFetchProgram</filename> " -"configuration variable so that the <command>gdmprefetch</command> program is " -"called with the default <filename>gdmprefetchlist</filename> file. The " -"default <filename>gdmprefetchlist</filename> 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 " -"<ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</" -"ulink>, so that they can be included in future GDM releases." -msgstr "" -"Pour utiliser cette fonctionnalité, configurez GDM avec l'option <command>--" -"with-prefetch</command>. Cela pousse GDM à installer le programme " -"<command>gdmprefetch</command> dans le répertoire <filename>libexecdir</" -"filename>, à copier <filename>gdmprefetchlist</filename> dans le répertoire " -"<filename><etc>/gdm</filename> et à définir la variable de " -"configuration <filename>PreFetchProgram</filename> afin que le programme " -"<command>gdmprefetch</command> soit appelé avec le fichier par défaut " -"<filename>gdmprefetchlist</filename>. Ce fichier a été optimisé pour un " -"bureau GNOME fonctionnant sous Solaris, il peut donc nécessiter quelques " -"adaptations sur d'autres systèmes. D'autres fichiers prefetchlist peuvent " -"être soumis dans <ulink type=\"http\" url=\"http://bugzilla.gnome.org/" -"\">bugzilla.gnome.org</ulink> dans la catégorie « gdm », afin qu'ils " -"puissent être inclus dans de futures versions de GDM." - -#: ../C/gdm.xml:807(title) -msgid "Security" -msgstr "Sécurité" - -#: ../C/gdm.xml:810(title) -msgid "PAM" -msgstr "PAM" - -#: ../C/gdm.xml:814(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 "" -"GDM utilise PAM pour authentifier les connexions, bien que si votre machine " -"ne prend pas en charge PAM, vous pouvez compiler GDM pour qu'il utilise la " -"base de données des mots de passe et la fonction de bibliothèque crypt." - -#: ../C/gdm.xml:820(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 "" -"PAM signifie Pluggable Authentication Module (Module d'authentification " -"enfichable) et est utilisé par la plupart des programmes qui demandent une " -"authentification sur votre ordinateur. Il permet à l'administrateur de " -"configurer différents types d'authentification pour différents programmes." - -#: ../C/gdm.xml:827(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 "" -"Certaines fonctionnalités de GDM (comme l'activation de la connexion " -"automatique) peuvent exiger la mise à jour de la configuration de PAM. La " -"configuration de PAM se fait par différentes interfaces, en général " -"similaires, selon les systèmes d'exploitation ; consultez la page de manuel " -"de pam.d ou de pam.conf pour plus de détails. Prenez soin de lire la " -"documentation de PAM (pages de manuel de pam.d ou pam.conf) et soyez bien " -"conscients des implications de sécurité induites par les modifications de " -"votre configuration." - -#: ../C/gdm.xml:837(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 "" -"S'il n'existe pas de rubrique GDM dans le fichier de configuration de PAM de " -"votre système, des fonctionnalités comme la connexion automatique peuvent ne " -"pas fonctionner. Dans ce cas, GDM utilise son comportement par défaut. Il " -"est probable alors que les paramètres stricts recommandés soient configurés " -"dans votre distribution." - -#: ../C/gdm.xml:844(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 <address><email>gdm-list@gnome.org</email></" -"address> mail list, so you can refer to the list archives for more " -"information." -msgstr "" -"Si vous souhaitez faire fonctionner GDM avec d'autres types de mécanismes " -"d'authentification (comme par ex. une SmartCard), il vous faut alors " -"implémenter cela en créant un module de service PAM pour ce type " -"d'authentification, plutôt qu'en essayant de modifier directement le code de " -"GDM. Référez-vous à la documentation de PAM sur votre système. Cette " -"question a été abordée sur la liste de diffusion <address><email>gdm-" -"list@gnome.org</email></address>, vous pouvez donc vous référer aux archives " -"de la liste pour plus d'informations." - -#: ../C/gdm.xml:854(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 " -"<filename>PamStack</filename> 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 "" -"Par exemple, une manière efficace de programmer un tel mécanisme " -"d'authentification exotique serait d'avoir un démon fonctionnant sur le " -"serveur et à l'écoute du périphérique d'authentification (que ce soit une " -"clé USB, un lecteur d'empreintes, etc.). Lorsque le périphérique signale une " -"saisie, le démon peut alors définir la valeur de configuration " -"<filename>PamStack</filename> à l'aide de la configuration spécifique à un " -"affichage et redémarrer la bannière avec la pile PAM correspondant à ce " -"périphérique. Cela évite de devoir manipuler directement le code du " -"gestionnaire d'affichage pour prendre en charge cette fonctionnalité." - -#: ../C/gdm.xml:869(title) -msgid "utmp/wtmp" -msgstr "utmp/wtmp" - -#: ../C/gdm.xml:873(para) -msgid "" -"GDM generates utmp and wtmp User Accounting Database entries upon session " -"login and logout. The utmp database contains user access and accounting " -"information that is accessed by commands such as <command>finger</command>, " -"<command>last</command>, <command>login</command>, and <command>who</" -"command>. The wtmp database contains the history of user access and " -"accounting information for the utmp database." -msgstr "" -"GDM génère des éléments utmp et wtmp dans la base de données de suivi des " -"utilisateurs lors de la connexion et déconnexion de sessions. La base de " -"données utmp contient des informations concernant le suivi et l'accès des " -"utilisateurs ; ces informations sont utilisées par des commandes telles que " -"<command>finger</command>, <command>last</command>, <command>login</command> " -"et <command>who</command>. La base de données wtmp contient l'historique des " -"informations de suivi et d'accès des utilisateurs de la base de données utmp." - -#: ../C/gdm.xml:883(para) -msgid "" -"GDM 2.18 and earlier would run the X server <command>sessreg</command> " -"program from the default GDM <command>PreSession</command> and " -"<command>PostSession</command> scripts. Starting with GDM 2.20, GDM " -"interacts with the UTMP and WTMP databases directly and supports the " -"following configuration options." -msgstr "" -"Les versions de GDM 2.18 et plus anciennes exécutaient le programme " -"<command>sessreg</command> du serveur X à partir des scripts GDM par défaut " -"<command>PreSession</command> et <command>PostSession</command>.À partir de " -"GDM 2.20, GDM interagit directement avec les bases de données UTMP et WTMP, " -"et prend en charge les options de configurations ci-après." - -#: ../C/gdm.xml:891(para) -msgid "" -"When doing utmp processing, GDM supports configurability on how the ut_line " -"value is set. Programs that access the database assume that this value is an " -"actual device, so GDM will set the device as follows. If the display is " -"attached and has an associated Virtual Terminal (VT) device, then this " -"device will be used. Otherwise, if an attached display in the <command>" -"[servers]</command> specifies a device name, then this value will be used. " -"Otherwise attached displays will default to the <filename>UtmpLineAttached</" -"filename> value in the GDM configuration. Remote displays will default to " -"the <filename>UtmpLineRemote</filename> value in the GDM configuration. " -"Device values must begin with \"/dev/\"." -msgstr "" -"Pour le traitement des données utmp, GDM peut être configuré sur la manière " -"de définir la valeur de ut_line. Les programmes qui accèdent à cette base de " -"données partent du principe que cette valeur correspond à un périphérique " -"réel. GDM définit donc ce périphérique comme suit. Si l'affichage est lié et " -"est associé à un terminal virtuel (VT), c'est ce dernier qui sera utilisé " -"comme périphérique. Sinon, pour les affichages liés, la valeur correspondra " -"à la valeur par défaut de <filename>UtmpLineAttached</filename> dans la " -"configuration de GDM. Pour les affichages distants, la valeur correspondra " -"par défaut à la valeur de <filename>UtmpLineRemote</filename> dans la " -"configuration de GDM. Les valeurs de périphérique doivent commencer par « /" -"dev/ »." - -#: ../C/gdm.xml:905(para) -msgid "" -"GDM also supports the <filename>UtmpPseudoDevice</filename> configuration " -"option. If this configuration setting is true, then GDM will ensure that the " -"specified device exists and will create a pseudo device if the device does " -"not exist. A pseudo device is a symlink to <filename>/dev/null</filename>. " -"If <filename>UtmpPseudoDevice</filename> is true, and the device does " -"already exist, GDM checks to see if the device is a symlink to <filename>/" -"dev/null</filename>. If so, then GDM will update the access time of the " -"symlink. This ensures that programs that check the access time of the device " -"will get a reasonable value for the last time the device was accessed. If " -"the <filename>UtmpPseudoDevice</filename> configuration option is false, " -"then GDM will only set the ut_line value as specified regardless of whether " -"the device exists or not." -msgstr "" -"GDM prend aussi en charge l'option de configuration " -"filename>UtmpPseudoDevice</filename>. Si cette valeur est définie à " -"« true » (vrai), GDM s'assure que le périphérique existe et crée un pseudo " -"périphérique s'il n'existe pas. Un pseudo périphérique est un lien " -"symbolique vers <filename>/dev/null</filename>. Si " -"<filename>UtmpPseudoDevice</filename> vaut « true » et que le périphérique " -"existe déjà, GDM vérifie si le périphérique est un lien symbolique vers " -"<filename>/dev/null</filename>. Si c'est le cas, GDM met à jour la date " -"d'accès au lien symbolique. Cela garantit que les programmes qui vérifient " -"la date d'accès au périphérique reçoivent une valeur correcte. Si l'option " -"de configuration <filename>UtmpPseudoDevice</filename> est définie à " -"« false » (faux), GDM définit simplement la valeur de ut_line selon ce qui " -"est défini, sans se préoccuper de l'existence réelle du périphérique." - -#: ../C/gdm.xml:923(title) -msgid "The GDM User" -msgstr "L'utilisateur GDM" - -#: ../C/gdm.xml:925(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 "" -"Pour des raisons de sécurité, un utilisateur et un groupe dédiés sont " -"indispensables pour un fonctionnement correct ! Le besoin de pouvoir écrire " -"des fichiers Xauth explique pourquoi l'utilisateur « nobody » (personne) " -"n'est pas adéquat pour GDM." - -#: ../C/gdm.xml:931(para) -msgid "" -"The GDM daemon normally runs as root, as does the slave. However GDM should " -"also have a dedicated user id and a group id which it uses for its graphical " -"interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</" -"command>. These are configured via the <filename>User</filename> and " -"<filename>Group</filename> configuration options in the GDM configuration " -"files. The user and group should be created before running \"make install\". " -"By default GDM assumes the user and the group are called \"gdm\"." -msgstr "" -"Le démon GDM fonctionne normalement en tant que root, ainsi que l'esclave. " -"Cependant, GDM doit aussi avoir un identifiant de groupe et d'utilisateur " -"utilisés pour ses interfaces graphiques telles que <command>gdmgreeter</" -"command> et <command>gdmlogin</command>. Ces identifiants sont définis dans " -"les options de configuration <filename>User</filename> et <filename>Group</" -"filename> dans les fichiers de configuration de GDM. L'utilisateur et le " -"groupe devraient être créés avec l'exécution de « make install ». Par " -"défaut, GDM part du principe que l'utilisateur et le groupe se nomment " -"« gdm »." - -#: ../C/gdm.xml:942(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 "" -"Cet identifiant utilisateur est utilisé pour lancer les programmes " -"graphiques de GDM requis par la connexion. Toutes les fonctions demandant " -"les droits « root » sont effectuées par le processus du démon GDM. Ces " -"principes permettent d'assurer qu'au cas où les programmes graphiques " -"étaient compromis d'une manière ou d'une autre, seuls les privilèges de " -"l'utilisateur dédié sont disponibles." - -#: ../C/gdm.xml:949(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 " -"<filename><var>/lib/gdm</filename>. 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 "" -"Il faut cependant relever que l'utilisateur et le groupe GDM disposent de " -"certains privilèges qui les rend quelque peu dangereux. D'une part, ils ont " -"accès au répertoire d'autorisation du serveur X. Ils doivent pouvoir lire et " -"écrire les clés Xauth dans <filename><var>/lib/gdm</filename>. Les " -"propriétaires de ce répertoire devraient être root:gdm avec les droits 1770. " -"L'exécution de « make install » configure ce répertoire de cette façon. Le " -"processus du démon GDM réinitialise ce répertoire avec les propriétaires et " -"les droits corrects au cas où il ne devait pas être configuré de la bonne " -"façon." - -#: ../C/gdm.xml:960(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 " -"<filename>nobody</filename>. 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 "" -"Le danger est que si quelqu'un obtient les droits de l'utilisateur et du " -"groupe GDM, il peut alors se connecter à n'importe quelle session. Vous ne " -"devriez donc sous aucun prétexte faciliter l'accès à cet utilisateur et à ce " -"groupe, comme c'est le cas avec l'utilisateur <filename>nobody</filename>. " -"Les utilisateurs obtenant l'accès à l'utilisateur « gdm » pourraient alors " -"modifier les clés Xauth et être la cause d'attaques par déni de service. " -"D'autre part, si quelqu'un obtient la possibilité de lancer des programmes " -"sous l'identité de « gdm », il pourrait se mettre à espionner les processus " -"GDM en cours de fonctionnement, y compris la saisie des noms d'utilisateur " -"et des mots de passe." - -#: ../C/gdm.xml:972(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 "" -"On attend des distributions et des administrateurs système utilisant GDM " -"qu'ils configurent proprement l'utilisateur dédié. Il est recommandé que cet " -"utilisateur ne soit pas autorisé à se connecter et qu'il n'ait pas de shell " -"par défaut. Le système de fichiers ne devrait pas non plus autoriser l'accès " -"à des fichiers sensibles à l'utilisateur GDM." - -#: ../C/gdm.xml:983(title) -msgid "X Server Authentication Scheme" -msgstr "Processus d'authentification du serveur X" - -#: ../C/gdm.xml:985(para) -msgid "" -"The X server authorization directory (the <filename>ServAuthDir</filename>) " -"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 <filename>root.gdm</filename> 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 "" -"Le répertoire d'autorisation du serveur X (<filename>ServAuthDir</filename>) " -"est utilisé pour toute une série de données internes diverses en plus des " -"fichiers d'autorisation au serveur X, et la nomenclature est vraiment un " -"reliquat historique. Le démon GDM oblige ce répertoire à être la propriété " -"de <filename>root.gdm</filename> avec les droits 1770. De cette façon, seuls " -"root et le groupe GDM ont un accès en écriture à ce répertoire, mais le " -"groupe GDM ne peut supprimer les fichiers appartenant à root dans ce " -"répertoire, comme par exemple les fichiers d'autorisation du serveur X." - -#: ../C/gdm.xml:997(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 "" -"Par défaut, GDM ne fait pas confiance au répertoire d'autorisation du " -"serveur X et le traite de la même manière que le dossier temporaire en ce " -"qui concerne la création de fichiers. Ainsi, celui qui abuserait de " -"l'utilisateur GDM ne pourrait pas produire d'attaque en créant des liens " -"dans ce répertoire. De la même manière, le répertoire de journalisation du " -"serveur X est traité de manière sûre, mais ce répertoire devrait vraiment " -"appartenir à root et n'être accessible en écriture que par lui." - -#: ../C/gdm.xml:1006(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 "" -"GDM ne prend en charge que le processus d'authentification du serveur X MIT-" -"MAGIC-COOKIE-1. Normalement, les autres processus n'apportent pas grand " -"chose et jusqu'à présent, aucun effort n'a été fait pour les implémenter. " -"Soyez extrêmement prudent lors de l'utilisation de XDMCP, car le cookie " -"d'authentification du serveur X passe en texte clair sur le réseau. Si un " -"pirate peut renifler le trafic réseau, il pourra simplement intercepter " -"votre mot de passe d'authentification lors de la connexion, quel que soit le " -"processus d'authentification utilisé. Lorsque vous ne pouvez pas faire " -"confiance au trafic réseau, vous devriez alors utiliser SSH au lieu de " -"XDMCP, pour faire transiter la connexion X par un tunnel. On peut comparer " -"XDMCP à une sorte de Telnet graphique, avec les mêmes problèmes de sécurité." - -#: ../C/gdm.xml:1019(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 <filename>/dev/audio</" -"filename> or <filename>/dev/mem</filename> 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 <filename>UserAuthDir</" -"filename> configuration key). So be careful about where you use remote X " -"display." -msgstr "" -"D'un autre côté, la génération de nombres aléatoires de GDM est très " -"classique et GDM prend des mesures extrêmes pour obtenir un nombre 128 bits " -"réellement aléatoire, à l'aide de générateurs de nombres aléatoires " -"matériels (si disponible), avec l'heure actuelle (à la microseconde), un " -"tableau de 20 octets de nombres pseudo-aléatoires, les identifiants de " -"processus ainsi que d'autres informations aléatoires (comprenant " -"l'utilisation de <filename>/dev/audio</filename> ou <filename>/dev/mem</" -"filename> si les générateurs matériels ne sont pas disponibles) afin de " -"créer un gros tampon, puis d'exécuter un hâchage MD5 par-dessus. Évidemment, " -"tout ce travail est gâché si vous envoyez ce cookie sur un réseau ouvert ou " -"que vous le stockez dans un répertoire NFS (voir la clé de configuration " -"<filename>UserAuthDir</filename>. Soyez donc prudent quant à l'environnement " -"d'utilisation de l'affichage X distant." - -#: ../C/gdm.xml:1036(title) -msgid "Firewall Security" -msgstr "Sécurité du pare-feu" - -#: ../C/gdm.xml:1038(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 "" -"Même si GDM essaie de déjouer les plans d'attaques potentiels sur le " -"protocole XDMCP, il est tout de même conseillé de bloquer le port XDMCP " -"(normalement le port UDP 177) sur votre pare-feu dans le cas où vous n'en " -"avez pas réellement besoin. GDM se protège des attaques par déni de service " -"(DoS), mais le protocole X est tout de même non sécurisé en lui-même et ne " -"devrait être utilisé que dans un environnement maîtrisé. De plus, chaque " -"connexion distante consomme beaucoup de ressources, ce qui rend les attaques " -"DoS plus simples par XDMCP que sur un serveur Web." - -#: ../C/gdm.xml:1048(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 "" -"Il est également sage de bloquer tous les ports du serveur X sur votre pare-" -"feu. Cela correspond aux ports TCP 6000 + le numéro d'affichage. Il est à " -"relever que GDM utilise des numéros d'affichage à partir de 20 pour les " -"serveurs flexibles sur demande." - -#: ../C/gdm.xml:1055(para) -msgid "" -"X is not a very safe protocol for leaving on the net, and XDMCP is even less " -"safe." -msgstr "" -"X n'est pas un protocole très sûr pour rester ouvert sur Internet, et XDMCP " -"l'est encore moins." - -#: ../C/gdm.xml:1062(title) -msgid "GDM Security With NFS" -msgstr "Sécurité GDM avec NFS" - -#: ../C/gdm.xml:1064(para) -msgid "" -"Note that NFS traffic really goes \"over the wire\" and thus can be snooped. " -"When accessing the user's X authorization file (<filename>~/.Xauthority</" -"filename>), 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 " -"<filename>UserAuthFBDir</filename>, which by default is set to <filename>/" -"tmp</filename>. This behavior can be changed by setting the " -"<filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</" -"filename> section to false." -msgstr "" -"Il faut relever que le trafic NFS transite « dans les fils » et qu'il peut " -"donc être espionné. Lors de l'accès au fichier d'autorisation de " -"l'utilisateur au serveur X (<filename>~/.Xauthority</filename>), GDM essaie " -"d'ouvrir le fichier en lecteur en tant que root. S'il échoue, GDM en conclut " -"qu'il se trouve sur un point de montage NFS et il utilise automatiquement " -"<filename>UserAuthFBDir</filename>, défini par défaut sur <filename>/tmp</" -"filename>. Ce comportement peut être modifié en définissant à « false » le " -"paramètre <filename>NeverPlaceCookiesOnNFS</filename> de la section " -"<filename>[security]</filename>." - -#: ../C/gdm.xml:1078(title) -msgid "XDMCP Security" -msgstr "Sécurité XDMCP" - -#: ../C/gdm.xml:1080(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 "" -"Même si votre affichage est protégé par des cookies, XEvents et donc aussi " -"les frappes au clavier lors de la saisie des mots de passe transitent " -"toujours sur le réseau en texte clair. Il est trivial de les capturer." - -#: ../C/gdm.xml:1086(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 "" -"XDMCP est surtout utile pour mettre en place des clients légers, par exemple " -"dans une salle de terminaux. Ces clients légers n'auront besoin du réseau " -"que pour accéder au serveur, il semble donc que la meilleure politique de " -"sécurité dans ce cas est de séparer ce réseau du monde externe et de le " -"réserver à l'accès au serveur. Le seul point à partir duquel vous avez " -"besoin d'accéder à l'extérieur est le serveur." - -#: ../C/gdm.xml:1095(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 "" -"Les sections ci-dessus, « Processus d'identification du serveur X » et " -"« Sécurité du pare-feu », contiennent aussi d'importantes informations sur " -"l'utilisation sécurisée de XDMCP. La section suivante aborde également la " -"manière de configurer le contrôle d'accès XDMCP." - -#: ../C/gdm.xml:1102(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 "" -"Pour détourner l'insécurité intrinsèque de XDMCP, GDM propose une session " -"prédéfinie qui utilise SSH pour chiffrer la connexion distante. Consultez la " -"section ci-dessus « Sécurisation de connexions distantes avec SSH »." - -#: ../C/gdm.xml:1110(title) -msgid "XDMCP Access Control" -msgstr "Contrôle d'accès XDMCP" - -#: ../C/gdm.xml:1112(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 "" -"Le contrôle d'accès XDMCP est réalisé par TCP wrappers. Cependant, il est " -"possible que GDM soit compilé sans la prise en charge de TCP wrappers, il " -"faut donc que vous testiez votre configuration pour vérifier qu'elle " -"fonctionne." - -#: ../C/gdm.xml:1118(para) -msgid "" -"You should use the daemon name <command>gdm</command> in the <filename><" -"etc>/hosts.allow</filename> and <filename><etc>/hosts.deny</" -"filename> files. For example to deny computers from <filename>.evil.domain</" -"filename> from logging in, then add" -msgstr "" -"Vous devriez utiliser le nom de démon <command>gdm</command> dans les " -"fichiers <filename><etc>/hosts.allow</filename> et <filename><" -"etc>/hosts.deny</filename>. Par exemple, pour empêcher les ordinateurs de " -"<filename>.danger.domaine</filename> de se connecter, ajoutez" - -#: ../C/gdm.xml:1125(screen) -#, no-wrap -msgid "" -"\n" -"gdm: .evil.domain\n" -msgstr "" -"\n" -"gdm: .danger.domaine\n" - -#: ../C/gdm.xml:1128(para) -msgid "" -"to <filename><etc>/hosts.deny</filename>. You may also need to add" -msgstr "" -"à <filename><etc>/hosts.deny</filename>. Il se peut que vous deviez " -"aussi ajouter" - -#: ../C/gdm.xml:1132(screen) -#, no-wrap -msgid "" -"\n" -"gdm: .your.domain\n" -msgstr "" -"\n" -"gdm: .votre.domaine\n" - -#: ../C/gdm.xml:1135(para) -msgid "" -"to your <filename><etc>/hosts.allow</filename> if you normally " -"disallow all services from all hosts. See the <ulink type=\"help\" url=\"man:" -"hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" -"à <filename><etc>/hosts.allow</filename>, dans le cas habituel où vous " -"refusez tous les services de tous les hôtes. Consultez la page de manuel de " -"<ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> pour les " -"détails." - -#: ../C/gdm.xml:1144(title) -msgid "RBAC (Role Based Access Control)" -msgstr "RBAC (Contrôle d'accès basé sur les rôles)" - -#: ../C/gdm.xml:1146(para) -msgid "" -"If GDM is compiled with RBAC support, then the " -"<filename>RBACSystemCommandKeys</filename> 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 " -"<command>gdmflexiserver</command> 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 <filename>User</filename> " -"configuration option) has permission via RBAC. Users will only be able to " -"use the <command>gdmflexiserver</command> commands if the user has " -"permission via RBAC." -msgstr "" -"Si GDM est compilé avec la prise en charge de RBAC, l'option de " -"configuration <filename>RBACSystemCommandKeys</filename> peut être utilisée " -"pour indiquer la clé RBAC à utiliser pour déterminer si l'utilisateur à le " -"droit d'utiliser des commandes. Ceci est valable pour les commandes " -"Éteindre, Redémarrer, Mettre en veille et pour les commandes personnalisées " -"qui apparaissent dans la bannière GDM et par les commandes " -"QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION et SET_SAFE_LOGOUT_ACTION de " -"<command>gdmflexiserver</command>. La bannière n'affiche l'option que si " -"l'utilisateur gdm (défini par l'option de configuration <filename>User</" -"filename>) a les permissions par RBAC. Les utilisateurs ne pourront utiliser " -"les commandes <command>gdmflexiserver</command> que s'ils en ont la " -"permission par RBAC." - -#: ../C/gdm.xml:1164(title) -msgid "Support for ConsoleKit" -msgstr "Prise en charge de ConsoleKit" - -#: ../C/gdm.xml:1166(para) -msgid "" -"GDM includes support for publishing user login information with the user and " -"login session accounting framework known as ConsoleKit. ConsoleKit is able " -"to keep track of all the users currently logged in. In this respect, it can " -"be used as a replacement for the utmp or utmpx files that are available on " -"most Unix-like operating systems." -msgstr "" -"GDM contient la prise en charge de la publication des informations de " -"connexion des utilisateurs au moyen de l'infrastructure de comptabilisation " -"des sessions et des utilisateurs, connue sous le nom de ConsoleKit. " -"ConsoleKit est capable de conserver la trace de tous les utilisateurs " -"connectés à un moment précis. Il peut donc être considéré comme un " -"remplacement des fichiers utmp et utmpx disponibles dans la plupart des " -"systèmes d'exploitation de type Unix." - -#: ../C/gdm.xml:1174(para) -msgid "" -"When GDM is about to create a new login process for a user it will call a " -"privileged method of ConsoleKit in order to open a new session for this " -"user. At this time GDM also provides ConsoleKit with information about this " -"user session such as: the user ID, the X11 Display name that will be " -"associated with the session, the host-name from which the session originates " -"(useful in the case of an XDMCP session), whether or not this session is " -"attached, etc. As the entity that initiates the user process, GDM is in a " -"unique position 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 "" -"Lorsque GDM est sur le point de créer un nouveau processus de connexion pour " -"un utilisateur, il appelle une méthode privilégiée de ConsoleKit dans le but " -"d'ouvrir une nouvelle session pour cet utilisateur. À cet instant, GDM " -"fournit aussi à ConsoleKit des informations au sujet de cette session : " -"l'identifiant de l'utilisateur, le nom d'affichage X11 qui sera associé à la " -"session, le nom d'hôte de provenance de la session (utile dans le cas d'un " -"session XDMCP), si la session est liée, etc. En tant qu'entité à l'origine " -"du processus utilisateur, GDM est dans une position unique pour fournir de " -"manière sûre ces éléments d'information sur la session de l'utilisateur. " -"L'utilisation de cette méthode privilégiée est limitée par le respect de la " -"politique de sécurité du bus de messages système D-Bus." - -#: ../C/gdm.xml:1187(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 "" -"Dans le cas d'un utilisateur ayant une session existante et s'authentifiant " -"par GDM pour demander la reprise de cette session, GDM appelle une méthode " -"privilégiée de ConsoleKit pour déverrouiller la session. Les détails précis " -"de ce qui se passe lorsque la session reçoit ce signal de déverrouillage ne " -"sont pas définis et sont spécifiques à la session. Cependant, la plupart des " -"sessions répondent en déverrouillant un économiseur d'écran." - -#: ../C/gdm.xml:1196(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 "" -"Lorsque l'utilisateur choisit de fermer sa session ou si GDM ou la session " -"se ferme de manière inattendue, la session utilisateur ne sera plus " -"référencée par ConsoleKit." - -#: ../C/gdm.xml:1201(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 "" -"Si la prise en charge de ConsoleKit n'est pas souhaitée, il peut être " -"désactivé au moment de la compilation à l'aide de l'option « --with-console-" -"kit=no » lors de l'exécution de « configure »." - -#: ../C/gdm.xml:1210(title) -msgid "Using gdmsetup To Configure GDM" -msgstr "Utilisation de gdmsetup pour configurer GDM" - -#: ../C/gdm.xml:1212(para) -msgid "" -"The <command>gdmsetup</command> 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 <command>gdmsetup</" -"command>. Editing the files by hand is explained in the \"Configuration\" " -"section of this document. Note that <command>gdmsetup</command> does not " -"support changing of all configuration variables, so it may be necessary to " -"edit the files by hand for some configurations." -msgstr "" -"L'application <command>gdmsetup</command> peut être utilisée pour configurer " -"GDM. Si vous pensez que le lancement d'une interface graphique en tant que " -"root pose des problèmes de sécurité, vous pouvez en rester à l'édition " -"manuelle de fichiers texte et faire l'impasse sur <command>gdmsetup</" -"command>. L'édition de fichiers à la main est expliqué à la section " -"« Configuration » de ce document. Il faut relever que <command>gdmsetup</" -"command> ne prend pas en charge la modification de toutes les variables de " -"configuration, il faudra donc passer obligatoirement par l'édition manuelle " -"des fichiers pour certaines options." - -#: ../C/gdm.xml:1223(para) -msgid "" -"The <command>gdmsetup</command> 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 "" -"Le programme <command>gdmsetup</command> possède cinq onglets : Locale, " -"Distante, Accessibilité, Sécurité et Utilisateurs. Ils sont décrits ci-" -"dessous. Vous trouverez entre parenthèses les relations entre les clés de " -"configuration GDM et les différentes options de l'interface. Pour plus de " -"détails sur chaque clé, consultez la section « Configuration » de ce manuel " -"ainsi que les commentaires dans le fichier de configuration par défaut du " -"système de GDM." - -#: ../C/gdm.xml:1233(title) -msgid "Local Tab" -msgstr "Onglet Locale" - -#: ../C/gdm.xml:1235(para) -msgid "" -"The Local tab is used for controlling the appearance of GDM for attached " -"(also known as local or static) displays. Attached displays are non-XDMCP " -"remote connections, for example. 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 "" -"L'onglet Locale est utilisé pour contrôler l'apparence de GDM pour les " -"affichages liés (aussi appelés locaux ou statiques). Les affichages liés " -"peuvent être, par exemple, des connexions distantes non XDMCP. Les choix " -"disponibles sur cet onglet dépendent du réglage de la liste déroulante " -"« Style ». Cette liste détermine le type de bannière utilisée (Simple ou " -"Avec thème). Les différences entre les bannières sont expliquées dans la " -"section « Aperçu » de ce document." - -#: ../C/gdm.xml:1246(para) -msgid "" -"If the \"Style\" choice is \"Plain\", then GDM will use the " -"<command>gdmlogin</command> program as the GUI (daemon/Greeter). When this " -"choice is selected, <command>gdmsetup</command> 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 "" -"Lorsque la liste Style contient « Simple », GDM utilise le programme " -"<command>gdmlogin</command> comme interface graphique de connexion (daemon/" -"Greeter). Avec ce choix, <command>gdmsetup</command> permet de sélectionner " -"si l'arrière-plan est une image ou une couleur unie (greeter/" -"BackgroundType). Si l'on choisit une image, un bouton de sélection de " -"fichier permet de sélectionner une image (greeter/BackgroundImage) et une " -"case à cocher indique s'il faut redimensionner l'image pour correspondre à " -"l'écran (greeter/BackgroundImageScaleToFit). Si l'on choisit une couleur " -"unie, un bouton permet de sélectionner la couleur (greeter/BackgroundColor). " -"De même, l'utilisateur peut choisir l'image du logo qui apparaît dans " -"gdmlogin (greeter/Logo)." - -#: ../C/gdm.xml:1260(para) -msgid "" -"If the \"Style\" choice is \"Plain with face browser\", then the " -"<command>gdmlogin</command> 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 "" -"Lorsque la liste Style contient « Simple avec navigateur de figures », GDM " -"utilise le programme <command>gdmlogin</command> comme interface graphique " -"de connexion (daemon/Greeter) et le navigateur de figures est activé " -"(greeter/Browser). Ce dernier est décrit dans la section « Aperçu ». Pour le " -"reste, les choix sont les mêmes qu'avec l'option « Simple ». Il peut être " -"souhaitable de configurer dans l'onglet Utilisateurs les noms qui " -"apparaîtront dans le navigateur de figures." - -#: ../C/gdm.xml:1270(para) -msgid "" -"If the \"Style\" choice is \"Themed\", then the <command>gdmgreeter</" -"command> program is used as the GUI (daemon/Greeter). When this choice is " -"selected, <command>gdmsetup</command> 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 "" -"Si l'option « Avec thème » est sélectionnée dans la liste Style, c'est le " -"programme <command>gdmgreeter</command> qui est employé comme interface " -"graphique (daemon/Greeter). Lorsque ce choix est sélectionné, " -"<command>gdmsetup</command> permet à l'utilisateur de choisir le thème à " -"utiliser (greeter/GraphicalTheme). Remarquez qu'il faut que la case à gauche " -"du nom du thème soit cochée pour qu'un thème soit sélectionné. Lorsqu'un " -"thème est mis en évidence, on voit apparaître sur la droite des informations " -"sur ses auteurs et son copyright. Le bouton Ajouter permet d'ajouter de " -"nouveaux thèmes dans le système. Les thèmes doivent être au format tar ou " -"tar compressé pour pouvoir être ajoutés. On peut aussi sélectionner la " -"couleur d'arrière-plan visible au démarrage de GDM (et dans les parties " -"transparentes du thème, le cas échéant) (greeter/GraphicalThemedColor). On " -"peut choisir « Sélection aléatoire » dans la liste déroulante Thème pour " -"afficher un thème au hasard lors de chaque connexion(greeter/" -"GraphicalThemeRand and greeter/GraphicalThemes). Dans ce mode, vous pouvez " -"encore cocher les thèmes devant faire partie de la sélection aléatoire. Par " -"défaut, la valeur de cette liste est « Uniquement sélectionné » ce qui fait " -"qu'un seul thème peut être sélectionné et actif à la fois." - -#: ../C/gdm.xml:1292(para) -msgid "" -"If the \"Style\" choice is \"Themed with face browser\", then the " -"<command>gdmgreeter</command> 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 "" -"Si l'option « Avec thème et navigateur de figures » est sélectionnée dans la " -"liste Style, c'est le programme <command>gdmgreeter</command> qui est " -"employé comme interface graphique (daemon/Greeter) et le navigateur de " -"figures est activé (greeter/Browser), pour autant que le thème le prenne en " -"charge. Le navigateur de figures est décrit dans la section Aperçu. Pour le " -"reste, les options sont identiques au choix « Avec thème » de la liste " -"Style. Il peut être souhaitable de configurer dans l'onglet Utilisateurs les " -"noms qui apparaîtront dans le navigateur de figures." - -#: ../C/gdm.xml:1303(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 <command>gdmsetup</command> (greeter/" -"ConfigAvailable), and whether the Action menu includes the choice to start " -"<command>gdmchooser</command> to run a remote XDMCP login session (greeter/" -"ChooserButton). The welcome message for attached DISPLAYS may be specified " -"(greeter/DefaultWelcome and greeter/Welcome). The welcome message may " -"contain the character sequences described in the \"Text Node\" subsection of " -"the \"Themed Greeter\" section of this manual. These character sequences " -"allow the welcome message to contain things like the display or host name." -msgstr "" -"Quelque soit la valeur de la liste Style, l'utilisateur peut aussi choisir " -"si le menu Actions doit être visible (greeter/SystemMenu), si le menu " -"Actions contient le choix de lancer <command>gdmsetup</command> (greeter/" -"ConfigAvailable) et si le menu Actions contient l'option de démarrer " -"<command>gdmchooser</command> pour exécuter une session XDMCP distante " -"(greeter/ChooserButton). Il est possible de définir le message de bienvenue " -"affiché pour les affichages liés (greeter/DefaultWelcome and greeter/" -"Welcome). Le message de bienvenue peut contenir les séquences de caractères " -"décrites dans la sous-section « Nœuds de texte » de la section « Bannière " -"avec thème » de ce manuel. Ces séquences de caractères permettent d'insérer " -"des éléments comme le nom d'hôte ou le nom d'affichage dans le message de " -"bienvenue." - -#: ../C/gdm.xml:1320(title) -msgid "Remote Tab" -msgstr "Onglet Distante" - -#: ../C/gdm.xml:1322(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 "" -"L'onglet Distante contrôle l'apparence de GDM pour les utilisateurs qui se " -"connectent par XDMCP. Par défaut, XDMCP est désactivé, et les utilisateurs " -"qui souhaiteraient l'activer devraient être à l'aise avec les sections " -"concernant XDMCP dans la section Sécurité de ce document. Cet onglet " -"contient une liste déroulante « Style » pouvant être utilisée pour activer " -"XDMCP et contrôler l'apparence de GDM pour les utilisateurs distants (gui/" -"RemoteGreeter et xdmcp/Enable). Il est possible de choisir d'utiliser la " -"même bannière d'accueil que dans l'onglet Locale, ou d'utiliser une autre " -"bannière. Si le navigateur de figures est activé dans l'onglet Locale, ce " -"sera aussi le cas pour l'onglet Distante. Idem en cas de désactivation de " -"cette fonctionnalité. Il est recommandé d'utiliser l'interface « Simple » " -"pour les connexions distantes car il est plus léger et présente de " -"meilleures performances sur un réseau." - -#: ../C/gdm.xml:1339(para) -msgid "" -"If Remote login is enabled, then the welcome message for remote DISPLAYs may " -"be specified (greeter/DefaultRemoteWelcome and greeter/RemoteWelcome). This " -"welcome message is separate from the one shown for attached displays defined " -"in the Local tab and can have a different value. The welcome message may " -"contain the character sequences described in the \"Text Node\" subsection of " -"the \"Themed Greeter\" section of this manual. These character sequences " -"allow the welcome message to contain things like the display or host name." -msgstr "" -"Si les connexions distantes sont activées, il est possible d'indiquer le " -"message de bienvenue pour les affichages distants (greeter/" -"DefaultRemoteWelcome et greeter/RemoteWelcome). Ce message de bienvenue est " -"différent du message affiché dans les affichages liés, défini dans l'onglet " -"Locale, et peut donc avoir un contenu différent. Il peut également contenir " -"les séquences de caractères décrites dans la sous-section « Nœud de texte » " -"de la section « Bannière avec thème » de ce manuel. Ces séquences de " -"caractères permettent d'insérer des éléments comme le nom d'hôte ou le nom " -"d'affichage dans le message de bienvenue." - -#: ../C/gdm.xml:1351(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 "" -"Si la liste Style contient « Identique à locale » et que le choix pour la " -"connexion locale est « Simple » ou « Simple avec navigateur de figures », il " -"est possible de choisir si l'image d'arrière-plan doit s'afficher pour les " -"connexions distantes (greeter/BackgroundRemoteOnlyColor)." - -#: ../C/gdm.xml:1359(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 "" -"Si la connexion distante sont activées et configurée sur une autre valeur " -"que l'onglet Locale, les options de configuration sont les mêmes que pour " -"l'onglet Locale à l'exception des options du menu Actions qui ne sont pas " -"présentes, car ce menu n'est jamais disponible lors de connexions distantes " -"pour des raisons de sécurité." - -#: ../C/gdm.xml:1367(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 "" -"Lorsque la connexion distante est activée, un bouton « Configurer XDMCP » " -"amène à une boîte de dialogue permettant de définir la configuration XDMCP " -"comprenant les paramètres suivants : honorer les requêtes indirectes (xdmcp/" -"HonorIndirect), le port UDP (xdmcp/Port), le nombre maximal de requêtes " -"indirectes en attente (xmdcp/MaxPendingIndirect), le nombre maximal de " -"sessions distantes (xdmcp/MaxSessions), le délai d'attente maximal (xdmcp/" -"MaxWait), le délai d'attente indirect maximal (xdmcp/MaxWaitIndirect), le " -"nombre d'affichages par hôte (xdmcp/DisplaysPerHost) et l'intervalle de ping " -"(xdmcp/PingIntervalSeconds). Les paramètres par défaut sont standards et ne " -"devraient être modifiés que par des personnes qui comprennent les " -"implications des changements." - -#: ../C/gdm.xml:1383(title) -msgid "Accessibility Tab" -msgstr "Onglet Accessibilité" - -#: ../C/gdm.xml:1385(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 "" -"L'onglet Accessibilité permet d'activer les fonctions d'accessibilité dans " -"GDM. « Activer l'accessibilité de la connexion » (daemon/AddGtkModules et " -"daemon/GtkModulesList) active les capteurs de mouvements, décrits dans la " -"section Accessibilité de ce document. On y trouve aussi une case à cocher " -"permettant aux utilisateurs de changer le thème de la bannière simple (gui/" -"AllowGtkThemeChange). Cette fonctionnalité permet aux utilisateurs de passer " -"à des thèmes avec des contrastes faibles ou élevés, selon les besoins. Il " -"est également possible de choisir si GDM doit émettre un son lorsque l'écran " -"de connexion est prêt, lorsque la connexion a réussi ou lorsqu'elle a " -"échoué. Des boutons de sélection de fichier permettent de sélectionner les " -"fichiers son, alors que le bouton Lecture permet d'écouter le son " -"sélectionné." - -#: ../C/gdm.xml:1402(title) -msgid "Security Tab" -msgstr "Onglet Sécurité" - -#: ../C/gdm.xml:1404(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 "" -"L'onglet Sécurité permet d'activer la connexion automatique ou la connexion " -"différée, de définir l'utilisateur connecté lors de ce type de connexion et " -"le délai avant la connexion différée (daemon/AutomaticLoginEnable, daemon/" -"AutomaticLogin, daemon/TimedLoginEnable, daemon/TimedLogin et daemon/" -"TimedLoginDelay). Lorsque la connexion automatique est activée, " -"l'utilisateur spécifié sera automatiquement connecté au redémarrage sans que " -"GDM demande de nom d'utilisateur ou de mot de passe. Si l'utilisateur sort " -"de sa session, GDM est lancé et demande un nom d'utilisateur et un mot de " -"passe pour ouvrir une nouvelle session. Lorsque la connexion différée est " -"activée, GDM ouvre une connexion pour l'utilisateur spécifié après le nombre " -"de secondes indiqué dans le champ correspondant. Il est possible d'activer " -"la connexion différée pour les connexions distantes (XDMCP) en cochant la " -"case « Autoriser les connexions différées à distance »." - -#: ../C/gdm.xml:1419(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 "" -"Dans cet onglet, il est possible de choisir si l'administrateur système " -"(root) peut se connecter et s'il peut accéder aux connexions à distance " -"(XDMCP) (security/AllowRoot et security/AllowRemoteRoot). Il est aussi " -"possible d'activer les messages de débogage GDM (debug/Enable) qui sont " -"envoyés dans le journal système. Le débogage devrait se limiter au " -"diagnostic de problèmes et ne devrait pas rester activé sans raison. Si elle " -"est sélectionnée, l'option « Refuser les connexions TCP au serveur X » " -"désactive le transfert (forwarding) X (security/DisallowTCP). Il est " -"possible de définir un délai entre connexions (security/RetryDelay) afin que " -"GDM attende un certain nombre de secondes après un échec de connexion." - -#: ../C/gdm.xml:1432(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 "" -"Le bouton « Configurer le serveur X » permet de spécifier comment GDM doit " -"gérer chaque affichage. La liste déroulante Serveurs montre les définitions " -"de serveurs disponibles (par défaut, Standard, Terminal et Chooser " -"(Sélecteur)). Consultez la sous-section « Définitions de serveurs X » de la " -"section Configuration pour plus d'informations sur la manière de créer de " -"nouvelles définitions de serveurs." - -#: ../C/gdm.xml:1441(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 "" -"Pour chaque type de serveur, il est possible de modifier le « Nom du " -"serveur » (server/name), la « Commande » à utiliser pour lancer le serveur X " -"(server/command), si le type de serveur va « Lancer » la bannière ou le " -"sélecteur après le démarrage du serveur X (server/chooser), si GDM gère ce " -"type (en principe, ne devrait être décoché que pour les connexions de type " -"Terminal) et si le type de session prend en charge les sessions " -"« Flexibles » (server/flexible)." - -#: ../C/gdm.xml:1451(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 "" -"La partie « Serveurs à démarrer » montre quel type de serveur est affiché " -"pour chaque affichage de la machine. Il est possible d'ajouter un nouvel " -"affichage à la liste ou d'en modifier un à l'aide du bouton Ajouter/" -"Modifier. Cela fait simplement correspondre chaque affichage physique avec " -"la définition de serveur à utiliser pour gérer cet affichage. Le bouton " -"Supprimer permet d'enlever un affichage de la liste." - -#: ../C/gdm.xml:1463(title) -msgid "Users Tab" -msgstr "Onglet Utilisateurs" - -#: ../C/gdm.xml:1465(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 "" -"L'onglet Utilisateurs contrôle quels utilisateurs apparaissent dans le " -"navigateur de figures. Si la case « Inclure tous les utilisateurs de /etc/" -"passwd » est cochée, tous les utilisateurs (ayant un numéro d'identifiant " -"plus grand que greeter/MinimalUID et ne figurant pas dans la liste Exclure) " -"sont affichés. Si cette case n'est pas cochée, les utilisateurs doivent être " -"ajoutés dans la liste Inclure. Les utilisateurs de la liste Exclure ne sont " -"jamais affichés. Les boutons Ajouter et Enlever permettent d'ajouter ou " -"d'enlever des utilisateurs dans les listes. Il est impératif de cliquer sur " -"le bouton « Appliquer les modifications des utilisateurs » après la " -"modification des listes Inclure et Exclure. Les boutons flèches gauche et " -"droite entre les deux listes permettent de déplacer un utilisateur " -"sélectionné dans une liste vers l'autre liste." - -#: ../C/gdm.xml:1483(title) -msgid "Configuration" -msgstr "Configuration" - -#: ../C/gdm.xml:1485(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 "" -"GDM dispose d'une puissante gestion de configuration. La configuration par " -"défaut du système est stockée dans le fichier de configuration par défaut de " -"GDM, alors que les modifications des utilisateurs par rapport à la " -"configuration par défaut sont stockées dans le fichier de configuration " -"personnalisée de GDM. Cela permet aux administrateurs système de placer le " -"fichier de configuration par défaut sur un système de fichiers partagé, afin " -"qu'un fichier unique puisse contrôler la configuration de plusieurs " -"machines. GDM prend aussi en charge la configuration par affichage pour les " -"clés liées à l'interface graphique." - -#: ../C/gdm.xml:1495(para) -msgid "" -"The <command>gdmsetup</command> 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 "" -"<command>gdmsetup</command> est un programme graphique autorisant l'édition " -"de la configuration de GDM. Ce programme peut aussi être lancé directement à " -"partir de l'écran de connexion si le paramètre greeter/ConfigAvailable est " -"défini à « true ». L'interface graphique ne gère pas toutes les clés du " -"fichier de configuration de GDM, il peut donc se révéler nécessaire d'éditer " -"certaines clés à la main. Si vous pensez que l'exécution d'interfaces " -"graphiques en tant que root constitue un risque de sécurité, vous préférerez " -"peut-être toujours éditer les fichiers à la main. Ce programme ne gère pas " -"la configuration de paramètres par affichage ; les fichiers de configuration " -"par affichage doivent être configurés à la main." - -#: ../C/gdm.xml:1507(para) -msgid "" -"Aside from the GDM System Defaults Configuration File, the other GDM " -"configuration files are located, by default, in the <filename><etc>/" -"gdm/</filename> 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 "" -"À l'exception du fichier de configuration système par défaut de GDM, Les " -"autres fichiers de configuration de GDM sont situés, par défaut, dans le " -"dossier <filename><etc>/gdm/</filename> ou ses sous-dossiers. " -"Remarquez que l'emplacement de beaucoup de fichiers de configuration sont " -"définis dans les fichiers de configuration de GDM, il s'agit donc de " -"consulter le fichier de configuration système par défaut et le fichier de " -"configuration personnalisée de GDM si les fichiers ne se trouvent pas aux " -"endroits indiqués dans ce document." - -#: ../C/gdm.xml:1517(para) -msgid "Listing of the config directory contents:" -msgstr "Liste du contenu du répertoire config :" - -#: ../C/gdm.xml:1521(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 "" -"\n" -"custom.conf\n" -"locale.alias\n" -"Xsession\n" -"XKeepsCrashing\n" -"modules/\n" -"Init/\n" -"PostLogin/\n" -"PreSession/\n" -"PostSession/\n" - -#: ../C/gdm.xml:1533(para) -msgid "" -"<filename>locale.alias</filename> 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 "" -"<filename>locale.alias</filename> est un fichier qui ressemble beaucoup à " -"locale.alias du système, mais ce n'est en fait pas le même. C'est une liste " -"de toutes les langues potentiellement installables sur votre système. Pour " -"chacune d'elles, GDM vérifie si elle est présente avant de l'afficher dans " -"l'interface de sélection de la langue. Seules celles qui existent réellement " -"sont affichées." - -#: ../C/gdm.xml:1541(para) -msgid "" -"<filename>Xsession</filename> 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 <filename>desktop</filename> file associated with " -"the session the user has picked. Some sessions may start the user's session " -"via a different mechanism than the <filename>Xsession</filename> script, so " -"please check the appropriate <filename>desktop</filename> before assuming a " -"session startup issue is being caused by this file." -msgstr "" -"<filename>Xsession</filename> est un script qui configure une session " -"utilisateur et qui exécute ensuite la session choisie par l'utilisateur. Il " -"est à relever que le script de session est habituellement démarré via le " -"fichier <filename>desktop</filename> correspondant à la session choisie par " -"l'utilisateur. Certaines sessions peuvent démarrer la session de " -"l'utilisateur par un autre moyen que le script <filename>Xsession</" -"filename>. Il faut donc contrôler le fichier <filename>desktop</filename> " -"correspondant avant de déduire qu'un problème de démarrage de session est " -"causé par ce fichier." - -#: ../C/gdm.xml:1552(para) -msgid "" -"<filename>XKeepsCrashing</filename> 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 "" -"<filename>XKeepsCrashing</filename> est un script qui est lancé lorsque le " -"serveur X plante continuellement et qu'on ne peut pas s'en sortir. Le script " -"fourni par défaut fonctionne avec la plupart des distributions Linux et peut " -"exécuter l'application de configuration de X pour autant que la personne " -"derrière la console connaisse le mot de passe administrateur." - -#: ../C/gdm.xml:1560(para) -msgid "" -"Accessibility modules are configured in the <filename>modules/</filename> " -"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 <filename>factory</filename> in their name, and " -"those files are not read, they are just there for you so you can always " -"revert to default config." -msgstr "" -"Les modules d'accessibilité sont configurés dans le sous-répertoire " -"<filename>modules/</filename>. Ils constituent un sujet à part. Parcourez " -"les fichiers fournis par défaut, ils disposent d'une documentation adéquate. " -"Normalement, dans une installation standard, vous trouvez des fichiers dont " -"le nom contient <filename>factory</filename> ; ces fichiers ne sont pas " -"utilisés, ils sont là uniquement pour que vous puissiez revenir à la " -"configuration par défaut." - -#: ../C/gdm.xml:1569(para) -msgid "" -"Files describing available GDM session follow the freedesktop.org desktop " -"file specification. The <filename>.desktop</filename>-style files are " -"installed to <filename><etc>/X11/sessions/</filename>. This directory " -"is also read by the KDE desktop manager (KDM) for common configuration. Next " -"the directory <filename><share>/gdm/BuiltInSessions/</filename> is " -"read for GDM specific built-in sessions (KDM hardcodes these at time of this " -"writing). Lastly the default setup will also read <filename><share>/" -"xsessions/</filename> (which should be <filename><share>/xsessions/</" -"filename> if you really wish to cooperate with KDM) where desktop packages " -"can install their session files. The directories under the <filename><" -"etc></filename> 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 <filename>SessionDesktopDir</filename> " -"configuration key for changing the paths. It used to be that GDM stored its " -"built in sessions in <filename><etc>/dm/Sessions/</filename> but this " -"is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the " -"<filename><etc>/dm/Sessions/</filename> was being read." -msgstr "" -"Les fichiers décrivant les sessions GDM disponibles respectent la " -"spécification des fichiers desktop de freedesktop.org. Les fichiers du style " -"<filename>.desktop</filename> sont installés dans <filename><etc>/X11/" -"sessions/</filename>. Ce répertoire est également parcouru par le " -"gestionnaire de bureau KDE (KDM) pour la configuration commune. Ensuite, le " -"répertoire <filename><share>/gdm/BuiltInSessions/</filename> est " -"parcouru pour les sessions prédéfinies spécifiques à GDM (au moment de la " -"rédaction de ce document, KDM fige ces informations dans son code). Pour " -"terminer, la configuration par défaut parcourt également <filename><" -"share>/xsessions/</filename> (qui doit être <filename><share>/" -"xsessions/</filename> pour réellement coopérer avec KDM), où les paquets de " -"bureau peuvent installer leurs fichiers de session. Les répertoires sous " -"<filename><etc></filename> devraient être réservés pour la " -"configuration. L'approche de la spécification des fichiers desktop simplifie " -"l'installation de gestionnaires de fenêtres et de différents types de " -"session par les systèmes de gestion de paquets, sans exiger l'édition de " -"fichiers par les administrateurs système. Consultez la clé de configuration " -"<filename>SessionDesktopDir</filename> pour modifier les chemins. " -"Anciennement, GDM stockait ses sessions prédéfinies dans <filename><" -"etc>/dm/Sessions/</filename>, mais ceci n'est plus indiqué à partir de " -"2.5.90.0. Il est à noter qu'avant la version 2.4.4.2, seul <filename><" -"etc>/dm/Sessions/</filename> était parcouru." - -#: ../C/gdm.xml:1592(para) -msgid "" -"A session can be disabled (if it was installed in <filename><share>/" -"xsessions/</filename>) by adding an identically named <filename>.desktop</" -"filename> to one of the directories earlier in the path (likely " -"<filename><etc>/X11/sessions</filename>) and using " -"<filename>Hidden=true</filename> in that file." -msgstr "" -"Une session peut être désactivée (si elle a été installée dans <filename><" -"share>/xsessions/</filename>) en ajoutant un fichier <filename>.desktop</" -"filename> du même nom dans l'un des répertoires précédents dans les chemins " -"parcourus (probablement <filename><etc>/X11/sessions</filename>) et en " -"écrivant <filename>Hidden=true</filename> dans ce fichier." - -#: ../C/gdm.xml:1600(para) -msgid "" -"GDM uses the optional key <filename>X-Gdm-XserverArgs</filename> in session " -"files to specify additional arguments to be passed to the X server. For " -"example, the entry <filename>X-Gdm-XserverArgs=-depth 16</filename> 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 "" -"GDM utilise la clé facultative <filename>X-Gdm-XserverArgs</filename> dans " -"les fichiers de sessions pour définir des arguments supplémentaires à passer " -"au serveur X. Par exemple, la ligne <filename>X-Gdm-XserverArgs=-depth 16</" -"filename> va démarrer le serveur X avec une profondeur de couleur de 16 " -"bits. De tels arguments supplémentaires sont ignorés en cas d'affichage " -"imbriqué (lorsque GDM est lancé dans une fenêtre)." - -#: ../C/gdm.xml:1611(title) -msgid "The Script Directories" -msgstr "Les répertoires de scripts" - -#: ../C/gdm.xml:1613(para) -msgid "" -"In this section we will explain the <filename>Init</filename>, " -"<filename>PostLogin</filename>, <filename>PreSession</filename> and " -"<filename>PostSession</filename> directories as they are very similar." -msgstr "" -"Dans cette section, nous présentons les répertoires <filename>Init</" -"filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> " -"et <filename>PostSession</filename>, car ils sont très semblables." - -#: ../C/gdm.xml:1619(para) -msgid "" -"When the X server has been successfully started, GDM will try to run the " -"script called <filename>Init/<displayname></filename>. I.e. " -"<filename>Init/:0</filename> for the first attached display. If this file is " -"not found, GDM will attempt to to run <filename>Init/<hostname></" -"filename>. I.e. <filename>Init/somehost</filename>. If this still is not " -"found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins or " -"<filename>Init/Flexi</filename> for all on demand flexible displays. If none " -"of the above were found, GDM will run <filename>Init/Default</filename>. The " -"script will be run as root and GDM blocks until it terminates. Use the " -"<filename>Init/*</filename> 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 "" -"Lorsque le serveur X a été démarré correctement, GDM essaye d'exécuter le " -"script nommé <filename>Init/<nomaffichage></filename>, par exemple " -"<filename>Init/:0</filename> pour le premier affichage lié. Si ce fichier " -"est absent, GDM essaye d'exécuter <filename>Init/<nomhôte></filename>. " -"Si ce fichier n'existe pas non plus, GDM essaye <filename>Init/XDMCP</" -"filename> pour les connexions XDMCP ou <filename>Init/Flexi</filename> pour " -"les affichages flexibles sur demande. Si aucun des fichiers ci-dessus n'est " -"trouvé, GDM exécute <filename>Init/Default</filename>. Le script s'exécute " -"en tant que root, et GDM attend que le script se termine. Utilisez le script " -"<filename>Init/*</filename> pour les applications qui sont censées " -"fonctionner en parallèle de la fenêtre de connexion GDM, par exemple " -"xconsole. Les commandes de configuration de l'arrière-plan ou d'autres " -"commandes du même genre vont également dans ce fichier." - -#: ../C/gdm.xml:1637(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 <filename>KillInitClients</filename> configuration option." -msgstr "" -"C'est à l'administrateur système de décider si les clients démarrés par le " -"script Init doivent être tués avant de démarrer la session utilisateur. Ceci " -"est contrôlé par l'option de configuration <filename>KillInitClients</" -"filename>." - -#: ../C/gdm.xml:1644(para) -msgid "" -"When the user has been successfully authenticated GDM tries the scripts in " -"the <filename>PostLogin</filename> directory in the same manner as for the " -"<filename>Init</filename> 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 <filename>pam_mount</" -"filename> module if you can for this). You have the <filename>$USER</" -"filename> and <filename>$DISPLAY</filename> 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 "" -"Lorsque l'utilisateur a été authentifié avec succès, GDM essaie de lancer " -"les scripts du répertoire <filename>PostLogin</filename> comme il l'a fait " -"avec le répertoire <filename>Init</filename>. Cela se passe avant toute " -"configuration de session ; c'est donc le script approprié pour la " -"configuration du dossier personnel, si nécessaire (bien que vous devriez " -"plutôt utiliser pour cela le module <filename>pam_mount</filename> si " -"possible). Les variables d'environnement <filename>$USER</filename> et " -"<filename>$DISPLAY</filename> sont définies pour ce script, et il est aussi " -"exécuté en tant que root. Le script doit renvoyer la valeur 0 en cas de " -"succès, sinon l'utilisateur ne sera pas connecté. Ce n'est cependant pas le " -"cas pour les sessions de secours." - -#: ../C/gdm.xml:1658(para) -msgid "" -"After the user session has been setup from the GDM side of things, GDM will " -"run the scripts in the <filename>PreSession</filename> directory, again in " -"the same manner as the <filename>Init</filename> directory. This script can " -"be used for session management or accounting, for example. The <filename>" -"$USER</filename> environment variable contains the login of the " -"authenticated user and <filename>$DISPLAY</filename> 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 <filename>$X_SERVERS</filename> environmental " -"variable is set and this points to a fake generated X servers file for use " -"with the sessreg accounting application." -msgstr "" -"Après avoir configuré la session utilisateur pour la partie concernant GDM, " -"GDM exécute les scripts du répertoire <filename>PreSession</filename>, " -"toujours de la même manière que pour le répertoire <filename>Init</" -"filename>. Ce script peut être utilisé par exemple pour la gestion et le " -"suivi des sessions. La variable d'environnement <filename>$USER</filename> " -"contient l'identifiant de l'utilisateur authentifié et <filename>$DISPLAY</" -"filename> est défini sur l'affichage actuel. Le script doit renvoyer la " -"valeur 0 en cas de succès. Toute autre valeur force GDM à interrompre le " -"processus de connexion. Ce n'est cependant pas le cas pour les sessions de " -"secours. La variable d'environnement <filename>$X_SERVERS</filename> est " -"aussi définie, et elle indique un fichier factice de serveurs X pour les " -"besoins de l'application de comptabilisation sessreg." - -#: ../C/gdm.xml:1673(para) -msgid "" -"After this the base <filename>Xsession</filename> 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 <filename>Exec=</filename> line in the <filename>.desktop</" -"filename> files in the path specified by <filename>SessionDesktopDir</" -"filename>. Usually this path is <filename><etc>/X11/sessions/:<" -"etc>/dm/Sessions:/usr/share/xsessions/</filename>. The first found file " -"is used. The user either picks from these sessions or GDM will look inside " -"the file <filename>~/.dmrc</filename> for the stored preference." -msgstr "" -"Après cela, le script <filename>Xsession</filename> de base est exécuté avec " -"l'exécutable de la session sélectionnée comme premier argument. Ce script " -"est exécuté avec les droits de l'utilisateur et forme réellement la session " -"de l'utilisateur. Les exécutables de session disponibles sont récupérés dans " -"la ligne <filename>Exec=</filename> dans les fichiers <filename>.desktop</" -"filename> du chemin désigné par <filename>SessionDesktopDir</filename>. En " -"principe, ce chemin est <filename><etc>/X11/sessions/:<etc>/dm/" -"Sessions:/usr/share/xsessions/</filename>. Le premier fichier trouvé est " -"utilisé. Soit l'utilisateur choisit parmi ces sessions, soit GDM examine le " -"fichier <filename>~/.dmrc</filename> pour y trouver la préférence " -"enregistrée." - -#: ../C/gdm.xml:1686(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 <filename>$GDM_LANG</" -"filename> 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 <filename>$GDM_LANG</filename> " -"is not set." -msgstr "" -"Ce script doit réellement charger le profil de l'utilisateur et s'occupe " -"généralement de toute la machinerie nécessaire au lancement de la session. " -"Étant donné que beaucoup de systèmes réinitialisent les sélections de langue " -"faites par GDM, ce dernier définit aussi la variable <filename>$GDM_LANG</" -"filename> à la langue sélectionnée. Vous pouvez utiliser cette étape pour " -"réinitialiser les variables d'environnement de langue après avoir exécuté le " -"profil de l'utilisateur. Si l'utilisateur a choisi d'utiliser la langue du " -"système, la variable <filename>$GDM_LANG</filename> n'est pas définie." - -#: ../C/gdm.xml:1696(para) -msgid "" -"When the user terminates his session, the <filename>PostSession</filename> " -"script will be run. Again operation is similar to <filename>Init</filename>, " -"<filename>PostLogin</filename> and <filename>PreSession</filename>. Again " -"the script will be run with root privileges, the slave daemon will block and " -"the <filename>$USER</filename> environment variable will contain the name of " -"the user who just logged out and <filename>$DISPLAY</filename> will be set " -"to the display the user used, however note that the X server for this " -"display may already be dead and so you shouldn't try to access it. Also " -"<filename>$X_SERVERS</filename> environmental variable is set and this " -"points to a fake generated X servers file for use with the sessreg " -"accounting application." -msgstr "" -"Lorsque l'utilisateur ferme sa session, le script <filename>PostSession</" -"filename> est exécuté. De nouveau, le principe est le même que pour les " -"répertoires <filename>Init</filename>, <filename>PostLogin</filename> et " -"<filename>PreSession</filename>. Le script s'exécutera aussi avec les " -"privilèges de l'administrateur, le démon esclave se fige, la variable " -"d'environnement <filename>$USER</filename> contient le nom de l'utilisateur " -"qui s'est déconnecté et la variable <filename>$DISPLAY</filename> est " -"définie sur l'affichage que l'utilisateur a utilisé. Cependant, il est à " -"relever que le serveur X de cet affichage n'existe peut-être déjà plus, vous " -"ne devriez donc pas essayer de l'atteindre. La variable d'environnement " -"<filename>$X_SERVERS</filename> est aussi définie, et elle indique un " -"fichier factice de serveurs X pour les besoins de l'application de " -"comptabilisation sessreg." - -#: ../C/gdm.xml:1711(para) -msgid "" -"Note that the <filename>PostSession</filename> script will be run even when " -"the display fails to respond due to an I/O error or similar. Thus, there is " -"no guarantee that X applications will work during script execution." -msgstr "" -"Il faut savoir que le script <filename>PostSession</filename> est exécuté " -"même lorsque l'affichage ne répond plus suite à une erreur d'entrée/sortie " -"ou autre. Il n'existe donc aucune garantie que les applications X " -"fonctionnent durant l'exécution de ce script." - -#: ../C/gdm.xml:1718(para) -msgid "" -"Except for the <filename>Xsession</filename> script all of these scripts " -"will also have the environment variable <filename>$RUNNING_UNDER_GDM</" -"filename> set to <filename>yes</filename>, so that you could perhaps use " -"similar scripts for different display managers. The <filename>Xsession</" -"filename> will always have the <filename>$GDMSESSION</filename> set to the " -"basename of the session that the user chose to run without the <filename>." -"desktop</filename> extension. In addition <filename>$DESKTOP_SESSION</" -"filename> is also set to the same value and in fact this will also be set by " -"KDM in future versions." -msgstr "" -"À l'exception du script <filename>Xsession</filename>, tous ces scripts " -"disposent aussi de la variable d'environnement <filename>$RUNNING_UNDER_GDM</" -"filename> définie à <filename>yes</filename>, ce qui permet d'utiliser " -"éventuellement les mêmes scripts avec d'autres gestionnaires d'affichage. Le " -"script <filename>Xsession</filename> dispose toujours de la variable " -"<filename>$GDMSESSION</filename> définie au nom de base de la session " -"choisie par l'utilisateur sans l'extension <filename>.desktop</filename>. De " -"plus, <filename>$DESKTOP_SESSION</filename> contient la même valeur et KDM " -"va aussi définir cette variable dans de futures versions." - -#: ../C/gdm.xml:1732(para) -msgid "" -"Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, " -"<filename>PreSession</filename> or <filename>PostSession</filename> scripts " -"are necessary and can be left out. The <filename>Xsession</filename> script " -"is however required as well as at least one session <filename>.desktop</" -"filename> file." -msgstr "" -"Aucun des scripts <filename>Init</filename>, <filename>PostLogin</filename>, " -"<filename>PreSession</filename> ou <filename>PostSession</filename> n'est " -"obligatoire et ils peuvent être omis. Par contre, le script " -"<filename>Xsession</filename> est indispensable, ainsi qu'au moins un " -"fichier de session <filename>.desktop</filename>." - -#: ../C/gdm.xml:1742(title) -msgid "" -"The Configuration Files - GDM System Defaults Configuration File and GDM " -"Custom Configuraiton File" -msgstr "" -"Les fichiers de configuration - le fichier de configuration par défaut du " -"système GDM et le fichier de configuration personnalisé GDM" - -#: ../C/gdm.xml:1745(para) -msgid "" -"GDM uses two configuration files: the GDM System Defaults Configuration File " -"(<filename><share>/gdm/defaults.conf</filename>) and the GDM Custom " -"Configuration File (<filename><etc>/gdm/custom.conf</filename>). 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 "" -"GDM utilise deux fichiers de configuration : le fichier de configuration " -"système par défaut GDM (<filename><share>/gdm/defaults.conf</" -"filename>) et le fichier de configuration personnalisée GDM (<filename><" -"etc>/gdm/custom.conf</filename>). Le fichier système par défaut GDM " -"contient les options de configuration par défaut de GDM et ne doit pas être " -"modifié par l'utilisateur. Le fichier de configuration personnalisée GDM est " -"destiné à recevoir les choix personnels de configuration des utilisateurs. " -"Si une option de configuration n'est définie dans aucun fichier, GDM utilise " -"la valeur par défaut décrite dans les commentaires du fichier de " -"configuration système par défaut GDM." - -#: ../C/gdm.xml:1758(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 "" -"Les deux fichiers de configuration sont divisés en sections contenant des " -"variables qui définissent le comportement d'une partie spécifique de la " -"suite GDM. Consultez les commentaires dans le fichier de configuration " -"système par défaut GDM pour obtenir plus d'informations sur chaque paramètre " -"de configuration." - -#: ../C/gdm.xml:1765(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 <filename><etc>/gdm/custom.conf<display " -"num></filename>. 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 <filename><etc>/gdm/custom.conf:0</" -"filename>. Per-display configuration is supported in GDM 2.14.6 and later." -msgstr "" -"GDM prend aussi en charge la configuration différenciée par affichage pour " -"les paramètres des sections « gui » et « greeter » du fichier de " -"configuration. C'est aussi le cas pour la clé « security/PamStack ». Une " -"configuration différenciée par affichage est définie en créant un fichier " -"appelé <filename><etc>/gdm/custom.conf<num affichage></" -"filename>. C'est dans ce fichier que l'on peut introduire des sections et " -"des clés spécifiques à un affichage. Par exemple, une configuration " -"prioritaire pour l'affichage « :103 » serait enregistrée dans le fichier " -"<filename><etc>/gdm/custom.conf:0</filename>. La configuration " -"différenciée par affichage est prise en charge à partir de la version GDM " -"2.14.6." - -#: ../C/gdm.xml:1778(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 "" -"Pour modifier manuellement une configuration, éditez le fichier de " -"configuration personnalisée GDM ou un fichier de configuration pour un " -"affichage spécifique et prenez bien soin de placer la paire nomdeclé=valeur " -"dans la section adéquate. Par exemple, pour changer la valeur de la clé " -"« Greeter » dans la section « daemon », il faut s'assurer que la clé et la " -"valeur à modifier se trouve bien à la suite de la section daemon du fichier " -"en cours d'édition. Comme dans l'exemple ci-dessous :" - -#: ../C/gdm.xml:1789(screen) -#, no-wrap -msgid "" -"\n" -"[daemon]\n" -"Greeter=/usr/lib/gdmgreeter\n" -msgstr "" -"\n" -"[daemon]\n" -"Greeter=/usr/lib/gdmgreeter\n" - -#: ../C/gdm.xml:1794(para) -msgid "" -"The <command>gdmsetup</command> command can be used to modify the GDM Custom " -"Configuration File. Note the <command>gdmsetup</command> 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 "" -"La commande <command>gdmsetup</command> peut être utilisée pour modifier le " -"fichier de configuration personnalisée GDM. Il faut relever que " -"<command>gdmsetup</command> doit être exécuté en tant que root. Si vous " -"trouvez qu'il n'est pas assez sûr de lancer des programmes graphiques en " -"tant que root, vous devrez alors éditer les fichiers de configuration à la " -"main." - -#: ../C/gdm.xml:1801(para) -msgid "" -"The GDM daemon <command>--config</command> 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 " -"<command>--with-defaults-conf</command> and <command>--with-custom-conf</" -"command> configuration options." -msgstr "" -"L'argument <command>--config</command> du démon GDM peut être utilisé pour " -"indiquer un emplacement différent du fichier de configuration. Le démon doit " -"être redémarré pour changer le fichier de configuration utilisé. Par " -"ailleurs, lors de la compilation de GDM, l'emplacement des fichiers de " -"configuration peut être spécifié avec les options de configuration " -"<command>--with-defaults-conf</command> et <command>--with-custom-conf</" -"command>." - -#: ../C/gdm.xml:1810(para) -msgid "" -"Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</" -"filename> 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 <filename><etc>/gdm/gdm.conf</filename> file is different than the " -"<filename><etc>/gdm/factory-gdm.conf</filename> file. If so, the " -"<filename><etc>/gdm/gdm.conf</filename> file will be automatically " -"copied to <filename><etc>/gdm/custom.conf</filename> to preserve any " -"configuration changes." -msgstr "" -"Avant la version 2.13.0.4 de GDM, il n'existait que <filename><etc>/" -"gdm/gdm.conf</filename>. Pour garantir une compatibilité descendante " -"maximale, ce fichier est utilisé à la place du fichier de configuration " -"personnalisée GDM s'il existe. En mettant à jour votre version de GDM, la " -"commande « make install » vérifie si les fichiers <filename><etc>/gdm/" -"gdm.conf</filename> et <filename><etc>/gdm/factory-gdm.conf</filename> " -"sont différents. Si c'est le cas, le fichier <filename><etc>/gdm/gdm." -"conf</filename> est automatiquement copié dans <filename><etc>/gdm/" -"custom.conf</filename> pour préserver toute modification de configuration." - -#: ../C/gdm.xml:1824(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 "" -"Les distributions devraient éditer le fichier de configuration système par " -"défaut de GDM pour définir les valeurs de configuration par défaut, afin que " -"les valeurs définies soient préservées comme valeurs par défaut, et qu'elles " -"ne soient pas modifiées par les utilisateurs qui éditent le fichier de " -"configuration personnalisée GDM. Il est à noter que les distributions " -"peuvent modifier le fichier de configuration système par défaut de GDM lors " -"de mises à jour pour améliorer la convivialité, la sécurité, etc. Ainsi, " -"tout changement effectué dans ce fichier peut être perdu." - -#: ../C/gdm.xml:1833(para) -msgid "" -"The GDM System Defaults Configuration File and the GDM Custom Configuration " -"File follow the standard <filename>.ini</filename> 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 "" -"Les fichiers de configuration par défaut et personnalisée de GDM respectent " -"le style standard de la syntaxe des fichiers de configuration <filename>." -"ini</filename>. Les mots-clés entre crochets définissent des sections, les " -"chaînes de caractères avant le signe égal (=) sont des variables et les " -"données après le signe égal représentent leur valeur. Les lignes vides ou " -"commençant par dièse (#) sont ignorées. Le programme de configuration " -"graphique tente de conserver aussi bien les commentaires (lignes débutant " -"par #) que la structure générale du fichier afin que vous puissiez utiliser " -"indifféremment l'interface graphique ou l'édition manuelle pour modifier le " -"fichier de configuration." - -#: ../C/gdm.xml:1845(para) -msgid "The following configuration keys are supported in GDM:" -msgstr "Les clés de configuration suivantes sont prises en charge par GDM :" - -#: ../C/gdm.xml:1850(title) -msgid "Daemon Configuration" -msgstr "Configuration du démon" - -#: ../C/gdm.xml:1853(title) -msgid "[daemon]" -msgstr "[daemon]" - -#: ../C/gdm.xml:1856(term) -msgid "AddGtkModules" -msgstr "AddGtkModules" - -#: ../C/gdm.xml:1858(synopsis) -#, no-wrap -msgid "AddGtkModules=false" -msgstr "AddGtkModules=false" - -#: ../C/gdm.xml:1859(para) -msgid "" -"If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</" -"command> 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 "" -"Si « true » (vrai), les commandes <command>gdmgreeter</command> et " -"<command>gdmlogin</command> peuvent être lancées avec des modules Gtk+ " -"supplémentaires. Cela est utile lorsque des fonctions supplémentaires sont " -"nécessaires, telles que la connexion accessible. Il est à relever que seules " -"des modules « de confiance » devraient être utilisés, pour limiter les " -"problèmes de sécurité." - -#: ../C/gdm.xml:1866(para) -msgid "" -"If true, then the registry daemon <command>at-spi-registryd</command> will " -"be launched by <command>gdmgreeter</command> or <command>gdmlogin</command> " -"starting with version GDM 2.17." -msgstr "" -"Si « true » (vrai), le démon de registre (<command>at-spi-registryd</" -"command>) est lancé par <command>gdmgreeter</command> ou <command>gdmlogin</" -"command>, à partir de la version 2.17 de GDM." - -#: ../C/gdm.xml:1872(para) -msgid "" -"Usually this is used for accessibility modules. The modules which are loaded " -"are specified with the <filename>GtkModulesList</filename> key." -msgstr "" -"En principe, ceci est utilisé pour les modules d'accessibilité. Les modules " -"chargés sont précisés par la clé <filename>GtkModulesList</filename>." - -#: ../C/gdm.xml:1881(term) -msgid "AllowLogoutActions" -msgstr "AllowLogoutActions" - -#: ../C/gdm.xml:1883(synopsis) -#, no-wrap -msgid "AllowLogoutActions=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD" -msgstr "AllowLogoutActions=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD" - -#: ../C/gdm.xml:1884(para) -msgid "" -"Specify which actions are supported by the QUERY_LOGOUT_ACTION, " -"SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</" -"command> 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 " -"<filename>SystemCommandsInMenu</filename> and " -"<filename>RBACSystemCommandKeys</filename> configuration options." -msgstr "" -"Indique quelles actions sont prises en charge par les commandes " -"QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION et SET_SAFE_LOGOUT_ACTION de " -"<command>gdmflexiserver</command>. Les valeurs possibles sont HALT, REBOOT, " -"SHUTDOWN, SUSPEND et CUSTOM_CMD ; ces valeurs doivent être séparées par deux-" -"points (:). Cette clé permet de désactiver certaines options, si nécessaire. " -"Référez-vous aux options de configuration comparables " -"<filename>SystemCommandsInMenu</filename> et " -"<filename>RBACSystemCommandKeys</filename>." - -#: ../C/gdm.xml:1899(term) -msgid "AlwaysLoginCurrentSession" -msgstr "AlwaysLoginCurrentSession" - -#: ../C/gdm.xml:1901(synopsis) -#, no-wrap -msgid "AlwaysLoginCurrentSession=true" -msgstr "AlwaysLoginCurrentSession=true" - -#: ../C/gdm.xml:1902(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 "" -"Si « true » (vrai), un utilisateur qui se connecte et pour lequel il existe " -"déjà une session est reconnecté à cette dernière au lieu d'ouvrir une " -"nouvelle session. Ceci fonctionne uniquement pour les sessions se trouvant " -"dans des terminaux virtuels (VT) démarrées avec gdmflexiserver, mais pas " -"avec XDMCP. Il faut savoir que les terminaux virtuels ne sont pas pris en " -"charge sur tous les systèmes d'exploitation." - -#: ../C/gdm.xml:1914(term) -msgid "AutomaticLoginEnable" -msgstr "AutomaticLoginEnable" - -#: ../C/gdm.xml:1916(synopsis) -#, no-wrap -msgid "AutomaticLoginEnable=false" -msgstr "AutomaticLoginEnable=false" - -#: ../C/gdm.xml:1917(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 " -"console security is not an issue and also could be useful for public " -"terminals. Refer also to <filename>TimedLogin</filename>." -msgstr "" -"Indique si l'utilisateur spécifié par AutomaticLogin doit être connecté lors " -"du démarrage initial. Aucun mot de passe n'est demandé. C'est utile pour des " -"ordinateurs ayant un seul utilisateur et où l'accès à la console ne pose " -"aucun problème de sécurité. Cela peut aussi être utile pour des terminaux " -"publics. Voir aussi l'option <filename>TimedLogin</filename>." - -#: ../C/gdm.xml:1928(term) -msgid "AutomaticLogin" -msgstr "AutomaticLogin" - -#: ../C/gdm.xml:1930(synopsis) -#, no-wrap -msgid "AutomaticLogin=" -msgstr "AutomaticLogin=" - -#: ../C/gdm.xml:1931(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 "" -"Cet utilisateur doit être connecté automatiquement lors du démarrage " -"initial. AutomaticLoginEnable doit être vrai (true) et cet utilisateur doit " -"être valide sur ce système. Il n'est cependant pas possible de connecter " -"automatiquement l'utilisateur « root », et GDM refusera de le faire même si " -"vous le configurez ainsi." - -#: ../C/gdm.xml:1939(para) -msgid "The following control chars are recognized within the specified name:" -msgstr "" -"Les caractères de contrôle suivants sont reconnus à l'intérieur du nom " -"spécifié :" - -#: ../C/gdm.xml:1944(para) ../C/gdm.xml:4056(para) -msgid "%% — the `%' character" -msgstr "%% — le caractère « % »" - -#: ../C/gdm.xml:1948(para) -msgid "%d — display's name" -msgstr "%d — nom de l'affichage" - -#: ../C/gdm.xml:1952(para) -msgid "%h — display's hostname" -msgstr "%h — nom d'hôte de l'affichage" - -#: ../C/gdm.xml:1956(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 "" -"Il est aussi possible que le nom se termine par une barre verticale (|), le " -"symbole du tube. Le nom est alors interprété comme une application à " -"exécuter et qui renvoie le nom d'utilisateur désiré sur la sortie standard. " -"Si un nom d'utilisateur vide ou non valide est renvoyé, la connexion " -"automatique n'est pas effectuée. Cette fonction est fréquemment utilisée " -"lorsque plusieurs affichages distants sont utilisés comme des bornes " -"Internet, avec un utilisateur bien précis devant être connecté " -"automatiquement sur chaque affichage." - -#: ../C/gdm.xml:1969(term) -msgid "BaseXsession" -msgstr "BaseXsession" - -#: ../C/gdm.xml:1971(synopsis) -#, no-wrap -msgid "BaseXsession=<etc>/gdm/Xsession" -msgstr "BaseXsession=<etc>/gdm/Xsession" - -#: ../C/gdm.xml:1972(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 <filename>Exec=</filename> from the <filename>.desktop</" -"filename> file of the session." -msgstr "" -"C'est le fichier de session X de base. Lorsqu'un utilisateur se connecte, ce " -"script est exécuté avec la session sélectionnée comme premier argument. La " -"session sélectionnée correspond à <filename>Exec=</filename> du fichier " -"<filename>.desktop</filename> de la session." - -#: ../C/gdm.xml:1980(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 <filename>GDMSESSION</filename> environmental variable. This " -"will always be set to the basename of <filename>.desktop</filename> (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 " -"<filename>GDM_LANG</filename>, but that is only set when the user picks a " -"non-system default language." -msgstr "" -"Si vous souhaitez utiliser le même script pour plusieurs gestionnaires " -"d'affichage différents et qu'une partie du script soit réservée uniquement à " -"GDM, vous pouvez vérifier la présence de la variable d'environnement " -"<filename>GDMSESSION</filename>. Elle sera toujours définie au nom de base " -"du fichier <filename>.desktop</filename> (sans l'extension) utilisé pour " -"cette session ; elle n'est définie que pour les sessions GDM. Anciennement, " -"certains scripts contrôlaient la présence de <filename>GDM_LANG</filename>, " -"mais celle-ci n'est définie que lorsque l'utilisateur choisit un langage par " -"défaut non système." - -#: ../C/gdm.xml:1993(para) -msgid "" -"This script should take care of doing the \"login\" for the user and so it " -"should source the <filename><etc>/profile</filename> and friends. The " -"standard script shipped with GDM sources the files in this order: " -"<filename><etc>/profile</filename> then <filename>~/.profile</" -"filename> then <filename><etc>/xprofile</filename> and finally " -"<filename>~/.xprofile</filename>. Note that different distributions may " -"change this however. Sometimes users personal setup will be in <filename>~/." -"bash_profile</filename>, however broken that is." -msgstr "" -"Ce script est chargé de s'occuper de la connexion effective de " -"l'utilisateur. Il doit donc utiliser <filename><etc>/profile</" -"filename> et autres fichiers du même genre. Le script standard livré avec " -"GDM parcourt les fichiers dans cet ordre : <filename><etc>/profile</" -"filename>, <filename>~/.profile</filename>, puis <filename><etc>/" -"xprofile</filename> et enfin <filename>~/.xprofile</filename>. Il faut " -"relever que certaines distributions peuvent agir différemment. Parfois, la " -"configuration personnelle des utilisateurs se trouvent dans <filename>~/." -"bash_profile</filename>, avec tous les problèmes de cette solution." - -#: ../C/gdm.xml:2010(term) -msgid "Chooser" -msgstr "Chooser" - -#: ../C/gdm.xml:2012(synopsis) -#, no-wrap -msgid "Chooser=<bin>/gdmchooser" -msgstr "Chooser=<bin>/gdmchooser" - -#: ../C/gdm.xml:2013(para) -msgid "" -"Full path and name of the chooser executable followed by optional arguments." -msgstr "" -"Chemin complet et nom de l'exécutable du sélecteur, suivi par des arguments " -"facultatifs." - -#: ../C/gdm.xml:2021(term) -msgid "Configurator" -msgstr "Configurator" - -#: ../C/gdm.xml:2023(synopsis) -#, no-wrap -msgid "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" -msgstr "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" - -#: ../C/gdm.xml:2024(para) -msgid "" -"The pathname to the configurator binary. If the greeter " -"<filename>ConfigAvailable</filename> 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 "" -"Le chemin d'accès au binaire du configurateur. Si l'option de la bannière " -"<filename>ConfigAvailable</filename> est définie à « true » (vrai), c'est ce " -"programme qui est lancé au moment où l'utilisateur choisit « Configuration » " -"dans le menu Actions. Mais bien sûr, GDM demande d'abord le mode de passe " -"d'administration. Et il ne permettra jamais cette opération depuis un " -"affichage distant." - -#: ../C/gdm.xml:2036(term) -msgid "ConsoleCannotHandle" -msgstr "ConsoleCannotHandle" - -#: ../C/gdm.xml:2038(synopsis) -#, no-wrap -msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" -msgstr "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" - -#: ../C/gdm.xml:2039(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 "" -"Ce sont les langues que la console ne sait pas gérer en raison de problèmes " -"de polices. Il s'agit ici de la console texte, pas de X. C'est uniquement " -"utilisé lorsqu'il y a des erreurs à signaler et que X ne peut démarrer." - -#: ../C/gdm.xml:2049(term) -msgid "ConsoleNotify" -msgstr "ConsoleNotify" - -#: ../C/gdm.xml:2051(synopsis) -#, no-wrap -msgid "ConsoleNotify=true" -msgstr "ConsoleNotify=true" - -#: ../C/gdm.xml:2052(para) -msgid "" -"If false, gdm will not display a message dialog on the console when an error " -"happens." -msgstr "" -"Si défini à « false » (faux), GDM n'affiche pas de boîte de dialogue de " -"message dans la console lorsqu'une erreur se produit." - -#: ../C/gdm.xml:2060(term) -msgid "DefaultPath" -msgstr "DefaultPath" - -#: ../C/gdm.xml:2062(synopsis) -#, no-wrap -msgid "DefaultPath=defaultpath (value set by configure)" -msgstr "DefaultPath=cheminpardéfaut (valeur définie par « configure »)" - -#: ../C/gdm.xml:2063(para) -msgid "" -"Specifies the path which will be set in the user's session. This value will " -"be overridden with the value from <filename>/etc/default/login</filename> if " -"it contains \"ROOT=<pathname>\". If the <filename>/etc/default/login</" -"filename> file exists, but contains no value for ROOT, the value as defined " -"in the GDM configuration will be be used." -msgstr "" -"Indique les chemins définis dans la session utilisateur. Cette valeur est " -"écrasée par la valeur de <filename>/etc/default/login</filename> si elle " -"contient « ROOT=<pathname> ». Si le fichier <filename>/etc/default/" -"login</filename> existe mais qu'il ne contient pas de valeur pour ROOT, " -"c'est la valeur définie dans la configuration de GDM qui sera utilisée." - -#: ../C/gdm.xml:2076(term) -msgid "DefaultSession" -msgstr "DefaultSession" - -#: ../C/gdm.xml:2078(synopsis) -#, no-wrap -msgid "DefaultSession=gnome.desktop" -msgstr "DefaultSession=gnome.desktop" - -#: ../C/gdm.xml:2079(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 <filename>ShowLastSession</filename> key." -msgstr "" -"La session utilisée par défaut si l'utilisateur n'a pas enregistré de " -"préférence et qu'il a sélectionné « Dernière session » dans la liste des " -"sessions. Remarquez que « Dernière session » n'est pas forcément affiché, " -"voir la clé <filename>ShowLastSession</filename>." - -#: ../C/gdm.xml:2090(term) -msgid "DisplayInitDir" -msgstr "DisplayInitDir" - -#: ../C/gdm.xml:2092(synopsis) -#, no-wrap -msgid "DisplayInitDir=<etc>/gdm/Init" -msgstr "DisplayInitDir=<etc>/gdm/Init" - -#: ../C/gdm.xml:2093(para) -msgid "" -"Directory containing the display init scripts. See the ``The Script " -"Directories'' section for more info." -msgstr "" -"Le répertoire contenant les scripts d'initialisation de l'affichage. " -"Consultez la section « Les répertoires de scripts » pour plus d'informations." - -#: ../C/gdm.xml:2101(term) -msgid "DisplayLastLogin" -msgstr "DisplayLastLogin" - -#: ../C/gdm.xml:2103(synopsis) -#, no-wrap -msgid "DisplayLastLogin=true" -msgstr "DisplayLastLogin=true" - -#: ../C/gdm.xml:2104(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 "" -"Si défini à « true » (vrai), les informations de la dernière connexion sont " -"présentées à l'utilisateur avant la saisie du mot de passe. Même si cela " -"divulgue certaines informations sur les utilisateurs configurés sur un " -"système, d'un autre côté, cela renseigne sur la date de la dernière " -"connexion ; si cette date paraît suspecte à l'utilisateur, il peut stopper " -"sa connexion et contacter l'administrateur système (pour éviter d'exécuter " -"des scripts de démarrage pernicieux). Cette fonctionnalité a été ajoutée " -"dans la version 2.5.90.0." - -#: ../C/gdm.xml:2113(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 <filename>http://www." -"radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> for more " -"info." -msgstr "" -"Ceci place GDM en conformité avec la norme CSC-STD-002-85, même si c'est " -"actuellement purement théorique. Il faudrait que quelqu'un lise la " -"spécification et s'assure que ceci est vraiment conforme (en plus d'autres " -"aspects de GDM). Consultez <filename>http://www.radium.ncsc.mil/tpep/library/" -"rainbow/CSC-STD-002-85.html</filename> pour plus d'informations." - -#: ../C/gdm.xml:2125(term) -msgid "DoubleLoginWarning" -msgstr "DoubleLoginWarning" - -#: ../C/gdm.xml:2127(synopsis) -#, no-wrap -msgid "DoubleLoginWarning=true" -msgstr "DoubleLoginWarning=true" - -#: ../C/gdm.xml:2128(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 "" -"Si défini à « true » (vrai), GDM avertit l'utilisateur lorsqu'il est déjà " -"connecté sur un autre terminal virtuel. Sur les systèmes où GDM gère la " -"vérification des terminaux virtuels X, GDM permet à l'utilisateur de " -"basculer sur le terminal virtuel de la connexion précédente, à la place de " -"se connecter." - -#: ../C/gdm.xml:2138(term) -msgid "DynamicXServers" -msgstr "DynamicXServers" - -#: ../C/gdm.xml:2140(synopsis) -#, no-wrap -msgid "DynamicXServers=false" -msgstr "DynamicXServers=false" - -#: ../C/gdm.xml:2141(para) -msgid "" -"If true, the GDM daemon will honor requests to manage displays via the " -"<filename>/tmp/.gdm_socket</filename> socket connection. Displays can be " -"created, started, and deleted with the appropriate commands. The " -"<filename>gdmdynamic</filename> command is a convenient method to send these " -"messages." -msgstr "" -"Si défini à « true » (vrai), le démon GDM répond aux requêtes de gestion " -"d'affichage via la connexion socket <filename>/tmp/.gdm_socket</filename>. " -"Des affichages peuvent être créés, démarrés ou détruits avec les commandes " -"correspondantes. La commande <filename>gdmdynamic</filename> est une méthode " -"appropriée pour envoyer ces messages." - -#: ../C/gdm.xml:2153(term) -msgid "FailsafeXServer" -msgstr "FailsafeXServer" - -#: ../C/gdm.xml:2155(synopsis) -#, no-wrap -msgid "FailsafeXServer=" -msgstr "FailsafeXServer=" - -#: ../C/gdm.xml:2156(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 " -"<filename>XKeepsCrashing</filename> script is run." -msgstr "" -"Une ligne de commande X dans le cas où il n'est pas possible de démarrer le " -"serveur X habituel. Cela devrait être une sorte de script exécutant un " -"serveur X à basse résolution qui devrait si possible fonctionner dans tous " -"les cas. Cette tentative est effectuée avant l'exécution du script " -"<filename>XKeepsCrashing</filename>." - -#: ../C/gdm.xml:2167(term) -msgid "FirstVT" -msgstr "FirstVT" - -#: ../C/gdm.xml:2169(synopsis) -#, no-wrap -msgid "FirstVT=7" -msgstr "FirstVT=7" - -#: ../C/gdm.xml:2170(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 <filename>VTAllocation</filename>." -msgstr "" -"Sur les systèmes où GDM prend en charge l'allocation automatique des " -"terminaux virtuels, cela correspond au premier terminal à essayer. En " -"principe, les connexions texte standard se trouvent sur les premiers " -"terminaux. Voir aussi <filename>VTAllocation</filename>." - -#: ../C/gdm.xml:2180(term) -msgid "FlexibleXServers" -msgstr "FlexibleXServers" - -#: ../C/gdm.xml:2182(synopsis) -#, no-wrap -msgid "FlexibleXServers=5" -msgstr "FlexibleXServers=5" - -#: ../C/gdm.xml:2183(para) -msgid "" -"The maximum number of allowed flexible displays. These are displays that can " -"be run using the <filename>/tmp/.gdm_socket</filename> socket connection. " -"This is used for both full flexible displays and for nested displays (refer " -"to the <filename>Xnest</filename> configuration option)." -msgstr "" -"Le nombre maximal d'affichages flexibles autorisés. Ce sont des affichages " -"pouvant être exécutés au moyen de la connexion socket <filename>/tmp/." -"gdm_socket</filename>. C'est utilisé à la fois pour les affichages flexibles " -"normaux et pour les affichages imbriqués (référez-vous à l'option de " -"configuration <filename>Xnest</filename>)." - -#: ../C/gdm.xml:2195(term) -msgid "FlexiReapDelayMinutes" -msgstr "FlexiReapDelayMinutes" - -#: ../C/gdm.xml:2197(synopsis) -#, no-wrap -msgid "FlexiReapDelayMinutes=5" -msgstr "FlexiReapDelayMinutes=5" - -#: ../C/gdm.xml:2198(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 <filename>Xnest</filename> " -"configuration option). To turn off this behavior set this value to 0. This " -"was added in version 2.5.90.0." -msgstr "" -"Le nombre de minutes d'inactivité d'un écran de connexion à la suite de quoi " -"un affichage flexible est désactivé. Cela n'a d'effet qu'avant une connexion " -"d'utilisateur. Cela n'affecte pas non plus les affichages imbriqués " -"(consultez l'option de configuration <filename>Xnest</filename>). Pour " -"désactiver ce comportement, définissez cette valeur à 0. Cette option a été " -"ajoutée dans la version 2.5.90.0." - -#: ../C/gdm.xml:2210(term) -msgid "Greeter" -msgstr "Greeter" - -#: ../C/gdm.xml:2212(synopsis) -#, no-wrap -msgid "Greeter=<bin>/gdmlogin" -msgstr "Greeter=<bin>/gdmlogin" - -#: ../C/gdm.xml:2213(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 <filename>RemoteGreeter</filename>" -msgstr "" -"Chemin complet et nom de l'exécutable de la bannière, suivi par des " -"arguments facultatifs. Cette bannière est utilisée par tous les affichages, " -"à l'exception des affichages XDMCP distants. Voir aussi " -"<filename>RemoteGreeter</filename>." - -#: ../C/gdm.xml:2223(term) -msgid "Group" -msgstr "Group" - -#: ../C/gdm.xml:2225(synopsis) -#, no-wrap -msgid "Group=gdm" -msgstr "Group=gdm" - -#: ../C/gdm.xml:2226(para) -msgid "" -"The group name under which <command>gdmlogin</command>, <command>gdmgreeter</" -"command>, <command>gdmchooser</command> and the internal failsafe GTK+ " -"dialogs are run. Also see <filename>User</filename>. 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 <filename>ServAuthDir</filename> is owned by this group. " -"The ownership and permissions of <filename>ServAuthDir</filename> should be " -"<filename>root.gdm</filename> and 1770." -msgstr "" -"Le nom du groupe avec lequel sont exécutés <command>gdmlogin</command>, " -"<command>gdmgreeter</command>, <command>gdmchooser</command> et les " -"dialogues internes GTK+ de secours. Voir aussi <filename>User</filename>. " -"Cet utilisateur a accès à tous les fichiers d'autorisation X et " -"potentiellement à d'autres données GDM internes ; ce devrait donc être un " -"utilisateur ad hoc, et non pas « nobody ». Le répertoire " -"<filename>ServAuthDir</filename> appartient à ce groupe. L'appartenance et " -"les droits sur <filename>ServAuthDir</filename> devraient être " -"<filename>root.gdm</filename> et 1770." - -#: ../C/gdm.xml:2243(term) -msgid "GtkModulesList" -msgstr "GtkModulesList" - -#: ../C/gdm.xml:2245(synopsis) -#, no-wrap -msgid "GtkModulesList=module-1:module-2:..." -msgstr "GtkModulesList=module-1:module-2:..." - -#: ../C/gdm.xml:2246(para) -msgid "" -"A colon separated list of Gtk+ modules that <command>gdmgreeter</command> or " -"<command>gdmlogin</command> will be invoked with if <filename>AddGtkModules</" -"filename> is true. The format is the same as the standard Gtk+ module " -"interface." -msgstr "" -"Une liste séparée par deux-points de modules Gtk+ appelés par " -"<command>gdmgreeter</command> ou <command>gdmlogin</command> si " -"<filename>AddGtkModules</filename> est vrai (true). Le format est identique " -"à l'interface standard de module Gtk+." - -#: ../C/gdm.xml:2257(term) -msgid "HaltCommand" -msgstr "HaltCommand" - -#: ../C/gdm.xml:2259(synopsis) -#, no-wrap -msgid "HaltCommand=<sbin>/shutdown -h now" -msgstr "HaltCommand=<sbin>/shutdown -h now" - -#: ../C/gdm.xml:2260(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 "" -"Chemin complet et arguments de la commande à exécuter lorsque l'utilisateur " -"choisit « Éteindre » dans le menu Actions. Ce peut être une liste de " -"commandes séparées par des « ; ». Si cette option n'a pas de valeur, la " -"commande Éteindre n'est pas disponible. Signalons que la valeur par défaut " -"n'est pas vide ; il faut donc définir une valeur vide pour désactiver la " -"fonction « Éteindre »." - -#: ../C/gdm.xml:2273(term) -msgid "KillInitClients" -msgstr "KillInitClients" - -#: ../C/gdm.xml:2275(synopsis) -#, no-wrap -msgid "KillInitClients=true" -msgstr "KillInitClients=true" - -#: ../C/gdm.xml:2276(para) -msgid "" -"Determines whether GDM should kill X clients started by the init scripts " -"when the user logs in." -msgstr "" -"Détermine s'il faut que GDM tue les clients X démarrés par les scripts " -"d'initialisation lorsque l'utilisateur se connecte." - -#: ../C/gdm.xml:2284(term) -msgid "LogDir" -msgstr "LogDir" - -#: ../C/gdm.xml:2286(synopsis) -#, no-wrap -msgid "LogDir=<var>/log/gdm" -msgstr "LogDir=<var>/log/gdm" - -#: ../C/gdm.xml:2287(para) -msgid "" -"Directory containing the log files for the individual displays. By default " -"this is the same as the ServAuthDir." -msgstr "" -"Répertoire contenant les fichiers journaux des différents affichages. Par " -"défaut, la valeur est la même que pour ServAuthDir." - -#: ../C/gdm.xml:2295(term) -msgid "PreFetchProgram" -msgstr "PreFetchProgram" - -#: ../C/gdm.xml:2297(synopsis) -#, no-wrap -msgid "PreFetchProgram=command" -msgstr "PreFetchProgram=command" - -#: ../C/gdm.xml:2298(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 "" -"Programme à exécuter par la bannière ou connexion GDM lorsque l'écran " -"initial est affiché. L'objectif est de fournir un point d'accrochage pour " -"que les fichiers qui seront utilisés après la connexion puissent être " -"préchargés, afin d'améliorer les performances. Ce programme est appelé une " -"seule fois, lors du premier affichage de la bannière. Il est possible " -"d'utiliser la commande gdmprefetch. Cet utilitaire charge toute bibliothèque " -"qui lui est transmise sur la ligne de commande, ou, si l'argument commence " -"par le caractère « @ », il considère le paramètre comme un fichier ASCII " -"contenant une liste de bibliothèques, une par ligne, et charge chaque " -"bibliothèque contenue dans le fichier." - -#: ../C/gdm.xml:2314(term) -msgid "PostLoginScriptDir" -msgstr "PostLoginScriptDir" - -#: ../C/gdm.xml:2316(synopsis) -#, no-wrap -msgid "PostLoginScriptDir=<etc>/gdm/PostLogin" -msgstr "PostLoginScriptDir=<etc>/gdm/PostLogin" - -#: ../C/gdm.xml:2317(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 "" -"Répertoire contenant les scripts exécutés juste après la connexion de " -"l'utilisateur, mais avant toute configuration de session. Consultez la " -"section « Répertoires de scripts » pour plus d'informations." - -#: ../C/gdm.xml:2326(term) -msgid "PostSessionScriptDir" -msgstr "PostSessionScriptDir" - -#: ../C/gdm.xml:2328(synopsis) -#, no-wrap -msgid "PostSessionScriptDir=<etc>/gdm/PostSession" -msgstr "PostSessionScriptDir=<etc>/gdm/PostSession" - -#: ../C/gdm.xml:2329(para) -msgid "" -"Directory containing the scripts run after the user logs out. See the ``The " -"Script Directories'' section for more info." -msgstr "" -"Répertoire contenant les scripts exécutés après la déconnexion de " -"l'utilisateur. Consultez la section « Répertoires de scripts » pour plus " -"d'informations." - -#: ../C/gdm.xml:2337(term) -msgid "PreSessionScriptDir" -msgstr "PreSessionScriptDir" - -#: ../C/gdm.xml:2339(synopsis) -#, no-wrap -msgid "PreSessionScriptDir=<etc>/gdm/PreSession" -msgstr "PreSessionScriptDir=<etc>/gdm/PreSession" - -#: ../C/gdm.xml:2340(para) -msgid "" -"Directory containing the scripts run before the user logs in. See the ``The " -"Script Directories'' section for more info." -msgstr "" -"Répertoire contenant les scripts exécutés avant la connexion de " -"l'utilisateur. Consultez la section « Répertoires de scripts » pour plus " -"d'informations." - -#: ../C/gdm.xml:2348(term) ../C/gdm.xml:2350(synopsis) -msgid "RBACSystemCommandKeys" -msgstr "RBACSystemCommandKeys" - -#: ../C/gdm.xml:2351(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 <command>gdmflexiserver</command> commands. Valid " -"actions are HALT, REBOOT, SUSPEND, and CUSTOM_CMD. The greeter will only " -"display the command if the gdm user (<filename>User</filename> 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 <filename>AllowLogoutActions</filename> and " -"<filename>SystemCommandsInMenu</filename> configuration options." -msgstr "" -"Prise en charge de RBAC (Role Based Access Control, contrôle d'accès basé " -"sur les rôles) pour les commandes systèmes (Éteindre, Redémarrer, Mettre en " -"veille, etc.). Cette fonctionnalité requiert que GDM ait été compilé avec la " -"prise en charge de RBAC. Indiquez la clé RBAC utilisée pour déterminer si " -"l'utilisateur a la permission d'effectuer une action au moyen des commandes " -"<command>gdmflexiserver</command> QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION et " -"SET_SAFE_LOGOUT_ACTION. Les actions possibles sont HALT, REBOOT, SUSPEND et " -"CUSTOM_CMD. La bannière n'affiche une commande que si l'utilisateur gdm (clé " -"de configuration <filename>User</filename>) a la permission RBAC d'effectuer " -"l'action. Des clés RBAC pour plusieurs actions peuvent être indiquées en les " -"séparant par des deux-points. Le format est « Action:clé RBAC ». Si une " -"action n'est pas mentionnée, il en est déduit que tous les utilisateurs ont " -"la permission d'effectuer cette action. Par exemple, une valeur possible de " -"cette option de configuration serait : « HALT:clé.pour.halt;REBOOT:clé.pour." -"reboot ». Consultez aussi les options de configuration apparentées " -"<filename>AllowLogoutActions</filename> et <filename>SystemCommandsInMenu</" -"filename>." - -#: ../C/gdm.xml:2375(term) -msgid "RebootCommand" -msgstr "RebootCommand" - -#: ../C/gdm.xml:2377(synopsis) -#, no-wrap -msgid "RebootCommand=<sbin>/shutdown -r now" -msgstr "RebootCommand=<sbin>/shutdown -r now" - -#: ../C/gdm.xml:2378(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 "" -"Chemin complet et arguments facultatifs de la commande à exécuter lorsque " -"l'utilisateur choisit « Redémarrer » dans le menu Actions. Ce peut être une " -"liste de commandes séparées par des « ; ». Si cette option n'a pas de " -"valeur, la commande Redémarrer n'est pas disponible. Signalons que la valeur " -"par défaut n'est pas vide ; il faut donc définir une valeur vide pour " -"désactiver la fonction « Redémarrer »." - -#: ../C/gdm.xml:2390(term) -msgid "RemoteGreeter" -msgstr "RemoteGreeter" - -#: ../C/gdm.xml:2392(synopsis) -#, no-wrap -msgid "RemoteGreeter=<bin>/gdmlogin" -msgstr "RemoteGreeter=<bin>/gdmlogin" - -#: ../C/gdm.xml:2393(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 <filename>Greeter</filename> key." -msgstr "" -"Chemin complet et nom de l'exécutable de la bannière, suivi par des " -"arguments facultatifs. Cette bannière est utilisée pour tous les affichages " -"XDMCP distants. Il peut être utile de placer ici une bannière exigeant moins " -"de ressources graphiques, dans le cas où vous utilisez la bannière avec " -"thème comme bannière principale. Voir aussi la clé <filename>Greeter</" -"filename>." - -#: ../C/gdm.xml:2404(term) -msgid "RootPath" -msgstr "RootPath" - -#: ../C/gdm.xml:2406(synopsis) -#, no-wrap -msgid "RootPath=defaultpath (value set by configure)" -msgstr "RootPath=cheminpardéfaut (valeur définie par « configure »)" - -#: ../C/gdm.xml:2407(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 <filename>/etc/default/login</filename> if " -"it contains \"SUROOT=<pathname>\". If the <filename>/etc/default/" -"login</filename> file exists, but contains no value for SUROOT, the value as " -"defined in the GDM configuration will be used." -msgstr "" -"Indique les chemins définis dans la session de root et dans les scripts " -"Init, PostLogin, PreSession et PostSession exécutés par GDM. Cette valeur " -"est écrasée par la valeur de <filename>/etc/default/login</filename> si elle " -"contient « SUROOT=<pathname> ». Si le fichier <filename>/etc/default/" -"login</filename> existe mais qu'il ne contient pas de valeur pour SUROOT, " -"c'est la valeur définie dans la configuration de GDM qui sera utilisée." - -#: ../C/gdm.xml:2421(term) -msgid "ServAuthDir" -msgstr "ServAuthDir" - -#: ../C/gdm.xml:2423(synopsis) -#, no-wrap -msgid "ServAuthDir=<var>/gdm" -msgstr "ServAuthDir=<var>/gdm" - -#: ../C/gdm.xml:2424(para) -msgid "" -"Directory containing the X authentication files for the individual displays. " -"Should be owned by <filename>root.gdm</filename> with permissions 1770, " -"where <filename>gdm</filename> is the GDM group as defined by the " -"<filename>Group</filename> option. That is should be owned by root, with " -"<filename>gdm</filename> 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 "" -"Répertoire contenant les fichiers d'authentification X pour les différents " -"affichages. Il devrait appartenir à <filename>root.gdm</filename> avec les " -"droits 1770, où <filename>gdm</filename> est le groupe défini par l'option " -"<filename>Group</filename>. Cela signifie qu'il devrait appartenir à root, " -"avec le groupe <filename>gdm</filename> possédant les droits d'écriture " -"complets, son bit « sticky » doit être activé et tous les autres ne " -"devraient avoir aucun accès. De cette façon, l'utilisateur GDM ne peut " -"supprimer les fichiers de ce répertoire appartenant à root, mais il peut " -"enregistrer ses propres fichiers à cet endroit. Si les permissions de ce " -"dossier sont différentes, GDM essaye de les corriger lorsqu'il démarre pour " -"la première fois. Ce répertoire est aussi employé pour stocker d'autres " -"fichiers privés que le démon utilise. Les autres utilisateurs ne devraient " -"en aucune manière avoir accès à ce répertoire et lire ou modifier ses " -"contenus. Tout utilisateur pouvant lire ce répertoire peut se connecter à " -"tous les affichages sur cet ordinateur." - -#: ../C/gdm.xml:2446(term) -msgid "SessionDesktopDir" -msgstr "SessionDesktopDir" - -#: ../C/gdm.xml:2448(synopsis) -#, no-wrap -msgid "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" -msgstr "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" - -#: ../C/gdm.xml:2449(para) -msgid "" -"Directory containing the <filename>.desktop</filename> 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 "" -"Répertoire contenant les fichiers <filename>.desktop</filename> " -"correspondant aux sessions disponibles sur le système. Depuis la version " -"2.4.4.2, ceci est considéré comme une variable de type PATH et le premier " -"fichier trouvé est utilisé." - -#: ../C/gdm.xml:2459(term) -msgid "SoundProgram" -msgstr "SoundProgram" - -#: ../C/gdm.xml:2461(filename) -msgid "<bin>/play" -msgstr "<bin>/play" - -#: ../C/gdm.xml:2461(filename) -msgid "<bin>/audioplay" -msgstr "<bin>/audioplay" - -#: ../C/gdm.xml:2461(synopsis) -#, no-wrap -msgid "SoundProgram=<placeholder-1/> (or <placeholder-2/> on Solaris)" -msgstr "SoundProgram=<placeholder-1/> (ou <placeholder-2/> sur Solaris)" - -#: ../C/gdm.xml:2462(para) -msgid "" -"Application to use when playing a sound. Currently used for playing the " -"login sound, see the <filename>SoundOnLoginFile</filename> key. Supported " -"since 2.5.90.0." -msgstr "" -"Application à utiliser pour lire les sons. Utilisé actuellement pour lire le " -"son de connexion, voir la clé <filename>SoundOnLoginFile</filename>. Pris en " -"charge depuis la version 2.5.90.0." - -#: ../C/gdm.xml:2472(term) -msgid "StandardXServer" -msgstr "StandardXServer" - -#: ../C/gdm.xml:2474(synopsis) -#, no-wrap -msgid "StandardXServer=/dir/to/X (value assigned by configuration file)" -msgstr "StandardXServer=/répertoire/vers/X (valeur attribuée par le fichier de configuration)" - -#: ../C/gdm.xml:2475(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 "" -"Chemin complet et arguments vers la commande standard du serveur X. Ceci est " -"utilisé lorsque GDM ne trouve aucune autre définition ; c'est la valeur par " -"défaut et la solution de secours à plusieurs endroits. Cette commande " -"devrait être capable d'exécuter un type quelconque de serveur X." - -#: ../C/gdm.xml:2486(term) -msgid "SuspendCommand" -msgstr "SuspendCommand" - -#: ../C/gdm.xml:2488(synopsis) -#, no-wrap -msgid "SuspendCommand=" -msgstr "SuspendCommand=" - -#: ../C/gdm.xml:2489(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 "" -"Chemin complet et arguments de la commande à exécuter lorsque l'utilisateur " -"choisit « Mettre en veille » dans le menu Actions. Si cette option n'a pas " -"de valeur, la commande n'est pas disponible. Signalons que la valeur par " -"défaut n'est pas vide ; il faut donc définir une valeur vide pour désactiver " -"la fonction « Mettre en veille »." - -#: ../C/gdm.xml:2500(term) -msgid "SystemCommandsInMenu" -msgstr "SystemCommandsInMenu" - -#: ../C/gdm.xml:2502(synopsis) -#, no-wrap -msgid "SuspendCommand=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD" -msgstr "SuspendCommand=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD" - -#: ../C/gdm.xml:2503(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 <command>gdmflexiserver</" -"command> 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 <filename>AllowLogoutActions</filename> and " -"<filename>RBACSystemCommandKeys</filename> configuration options." -msgstr "" -"Indique quelles commandes systèmes sont disponibles dans le menu de la " -"bannière d'accueil. Les valeurs possibles sont HALT, REBOOT, SHUTDOWN, " -"SUSPEND et CUSTOM_CMD, séparées par des deux-points. Cela peut être utile " -"pour désactiver certaines options du menu, tout en les conservant " -"disponibles pour les utilisateurs authentifiés par les commandes " -"<command>gdmflexiserver</command> SET_LOGOUT_ACTION ou " -"SET_SAFE_LOGOUT_ACTION. Par exemple, le tableau de bord GNOME utilise ces " -"commandes pour proposer Éteindre, Redémarrer et Mettre en veille dans le " -"menu Applications. Si donc vous désactivez ces options dans la bannière, " -"elles peuvent toujours être disponibles pour les utilisateurs authentifiés, " -"par l'intermédiaire du tableau de bord GNOME. Référez-vous aux options de " -"configuration liées <filename>AllowLogoutActions</filename> et " -"<filename>RBACSystemCommandKeys</filename>." - -#: ../C/gdm.xml:2524(term) -msgid "TimedLoginEnable" -msgstr "TimedLoginEnable" - -#: ../C/gdm.xml:2526(synopsis) -#, no-wrap -msgid "TimedLoginEnable=false" -msgstr "TimedLoginEnable=false" - -#: ../C/gdm.xml:2527(para) -msgid "" -"If the user given in <filename>TimedLogin</filename> should be logged in " -"after a number of seconds (set with <filename>TimedLoginDelay</filename>) of " -"inactivity on the login screen. This is useful for public access terminals " -"or perhaps even home use. If the user uses the keyboard or browses the " -"menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or " -"30 seconds, whichever is higher. If the user does not enter a username but " -"just hits the ENTER key while the login program is requesting the username, " -"then GDM will assume the user wants to login immediately as the timed user. " -"Note that no password will be asked for this user so you should be careful, " -"although if using PAM it can be configured to require password entry before " -"allowing login." -msgstr "" -"Indique si l'utilisateur spécifié par <filename>TimedLogin</filename> doit " -"être automatiquement connecté après un certain nombre de secondes (défini " -"par <filename>TimedLoginDelay</filename>) d'inactivité à l'écran de " -"connexion. C'est utile pour des terminaux à accès public, ou même pour une " -"utilisation privée. Si l'utilisateur emploie le clavier ou parcourt les " -"menus, le délai est réinitialisé à la valeur la plus élevée entre " -"<filename>TimedLoginDelay</filename> et 30 secondes. Si aucun nom " -"d'utilisateur n'est saisi et que l'utilisateur appuie sur la touche Entrée " -"alors que le programme de connexion demande un nom d'utilisateur, GDM " -"interprète cela comme le souhait de connecter immédiatement l'utilisateur " -"« différé ». Il faut relever qu'aucun mot de passe n'est exigé pour cet " -"utilisateur. Il faut donc rester prudent, même si avec PAM, il est possible " -"de configurer la demande du mot de passe avant d'autoriser la connexion." - -#: ../C/gdm.xml:2547(term) -msgid "TimedLogin" -msgstr "TimedLogin" - -#: ../C/gdm.xml:2549(synopsis) -#, no-wrap -msgid "TimedLogin=" -msgstr "TimedLogin=" - -#: ../C/gdm.xml:2550(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 <filename>AutomaticLogin</" -"filename> are supported. The same control chars and piping to a application " -"are supported." -msgstr "" -"Ceci est le nom de l'utilisateur devant être connecté après un nombre défini " -"de secondes d'inactivité. Cela ne peut jamais être « root », GDM " -"n'autorisant pas la connexion de root de cette manière. Les fonctionnalités " -"prises en charge sont identiques à <filename>AutomaticLogin</filename>. Il " -"est possible d'utiliser les mêmes caractères de contrôle et le même système " -"de tube vers une application." - -#: ../C/gdm.xml:2562(term) -msgid "TimedLoginDelay" -msgstr "TimedLoginDelay" - -#: ../C/gdm.xml:2564(synopsis) -#, no-wrap -msgid "TimedLoginDelay=30" -msgstr "TimedLoginDelay=30" - -#: ../C/gdm.xml:2565(para) -msgid "" -"Delay in seconds before the <filename>TimedLogin</filename> user will be " -"logged in. It must be greater then or equal to 10." -msgstr "" -"Délai en secondes avant que l'utilisateur <filename>TimedLogin</filename> " -"soit connecté. Cette valeur doit être égale ou plus grande que 10." - -#: ../C/gdm.xml:2573(term) -msgid "User" -msgstr "User" - -#: ../C/gdm.xml:2575(synopsis) -#, no-wrap -msgid "User=gdm" -msgstr "User=gdm" - -#: ../C/gdm.xml:2576(para) -msgid "" -"The username under which <command>gdmlogin</command>, <command>gdmgreeter</" -"command>, <command>gdmchooser</command> and the internal failsafe GTK+ " -"dialogs are run. Also see <filename>Group</filename>. 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 "" -"Le nom d'utilisateur avec lequel sont exécutés <command>gdmlogin</command>, " -"<command>gdmgreeter</command>, <command>gdmchooser</command> et les " -"dialogues internes GTK+ de secours. Voir aussi <filename>Group</filename>. " -"Cet utilisateur a accès à tous les fichiers d'autorisation X et " -"potentiellement à d'autres données GDM internes ; ce devrait donc être un " -"utilisateur ad hoc, et non pas « nobody »." - -#: ../C/gdm.xml:2590(term) -msgid "UserAuthDir" -msgstr "UserAuthDir" - -#: ../C/gdm.xml:2592(synopsis) -#, no-wrap -msgid "UserAuthDir=" -msgstr "UserAuthDir=" - -#: ../C/gdm.xml:2593(para) -msgid "" -"The directory where user's <filename>.Xauthority</filename> 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: <filename>~/authdir/</" -"filename>." -msgstr "" -"Répertoire dans lequel le fichier des utilisateurs <filename>.Xauthority</" -"filename> doit être enregistré. Si aucune valeur n'est définie, c'est le " -"dossier personnel qui est utilisé. Le caractère tilde est interprété, ce qui " -"permet de définir quelque chose comme : <filename>~/authdir/</filename>." - -#: ../C/gdm.xml:2600(para) -msgid "" -"If you do not use the tilde expansion, then the filename created will be " -"random, like in <filename>UserAuthFBDir</filename>. This way many users can " -"have the same authentication directory. For example you might want to set " -"this to <filename>/tmp</filename> 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 <filename>/tmp</" -"filename> directory." -msgstr "" -"Si vous n'utilisez pas le caractère tilde, le nom de fichier créé sera " -"aléatoire, comme pour <filename>UserAuthFBDir</filename>. De cette façon, " -"plusieurs utilisateurs peuvent partager le même répertoire " -"d'authentification. Par exemple, on pourrait définir cette valeur à " -"<filename>/tmp</filename> lorsque les dossiers personnels se trouvent sur " -"NFS, car il n'est vraiment pas souhaitable que des fichiers cookie " -"transitent sur le réseau. Les utilisateurs doivent disposer des droits en " -"écriture sur ce répertoire, et celui-ci devrait posséder le bit « sticky », " -"tout comme le répertoire <filename>/tmp</filename>." - -#: ../C/gdm.xml:2613(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 <filename>NeverPlaceCookiesOnNFS</filename> in the " -"<filename>[security]</filename> section to false." -msgstr "" -"Normalement, si cette valeur indique le dossier personnel de l'utilisateur, " -"GDM refuse d'y placer des cookies s'il pense qu'il se trouve sur NFS (par le " -"test root-squashing). Cela peut être modifié en définissant la valeur du " -"paramètre <filename>NeverPlaceCookiesOnNFS</filename> de la section " -"<filename>[security]</filename> à « false » (faux)." - -#: ../C/gdm.xml:2624(term) -msgid "UserAuthFBDir" -msgstr "UserAuthFBDir" - -#: ../C/gdm.xml:2626(synopsis) -#, no-wrap -msgid "UserAuthFBDir=/tmp" -msgstr "UserAuthFBDir=/tmp" - -#: ../C/gdm.xml:2627(para) -msgid "" -"If GDM fails to update the user's <filename>.Xauthority</filename> file a " -"fallback cookie is created in this directory." -msgstr "" -"Si GDM échoue dans la mise à jour du fichier <filename>.Xauthority</" -"filename> de l'utilisateur, un cookie de secours est créé dans ce répertoire." - -#: ../C/gdm.xml:2636(term) -msgid "UserAuthFile" -msgstr "UserAuthFile" - -#: ../C/gdm.xml:2638(synopsis) -#, no-wrap -msgid "UserAuthFile=.Xauthority" -msgstr "UserAuthFile=.Xauthority" - -#: ../C/gdm.xml:2639(para) -msgid "Name of the file used for storing user cookies." -msgstr "Nom du fichier utilisé pour stocker les cookies des utilisateurs." - -#: ../C/gdm.xml:2646(term) -msgid "VTAllocation" -msgstr "VTAllocation" - -#: ../C/gdm.xml:2648(synopsis) -#, no-wrap -msgid "VTAllocation=true" -msgstr "VTAllocation=true" - -#: ../C/gdm.xml:2649(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 " -"<filename>FirstVT</filename>." -msgstr "" -"Sur les systèmes où GDM prend en charge l'allocation des terminaux virtuels " -"(VT) (actuellement seulement sur Linux et FreeBSD), il est possible de " -"demander à GDM d'ajouter automatiquement l'argument vt à l'exécutable du " -"serveur X. De cette façon, la concurrence entre les serveurs X gérant chacun " -"l'allocation de leur terminal virtuel peut être évitée. Voir aussi " -"<filename>FirstVT</filename>." - -#: ../C/gdm.xml:2661(term) -msgid "XKeepsCrashing" -msgstr "XKeepsCrashing" - -#: ../C/gdm.xml:2663(synopsis) -#, no-wrap -msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" -msgstr "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" - -#: ../C/gdm.xml:2664(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 " -"<filename>XKeepsCrashing</filename> 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 "" -"Un script à exécuter dans le cas où X se plante continuellement. Ceci est " -"prévu pour lancer la configuration de X ou pour effectuer une autre action " -"permettant de faire fonctionner X. Examinez le script livré avec la " -"distribution comme example. Le script <filename>XKeepsCrashing</filename> " -"livré est testé sur Redhat, mais il devrait aussi fonctionner ailleurs. " -"Votre intégrateur système devrait s'assurer que ce script est à jour pour " -"votre système précis." - -#: ../C/gdm.xml:2673(para) -msgid "" -"In case <filename>FailsafeXServer</filename> is setup, that will be tried " -"first. and this only used as a backup if even that X server keeps crashing." -msgstr "" -"Dans le cas où <filename>FailsafeXServer</filename> est configuré, c'est ce " -"paramètre qui est essayé en premier. Puis, si le serveur X continue de " -"planter, <filename>XKeepsCrashing</filename> est alors utilisé comme " -"solution de secours." - -#: ../C/gdm.xml:2682(term) -msgid "Xnest" -msgstr "Xnest" - -#: ../C/gdm.xml:2684(synopsis) -#, no-wrap -msgid "Xnest=<bin>/X11/Xephyr -audit 0" -msgstr "Xnest=<bin>/X11/Xephyr -audit 0" - -#: ../C/gdm.xml:2685(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 "" -"Le chemin complet et les arguments de la commande du serveur X imbriqué, qui " -"peut être Xephyr, Xnest ou un autre programme semblable. Cette commande est " -"utilisée pour démarrer des affichages imbriqués, permettant aux utilisateurs " -"de de lancer de nouveaux écrans de connexion à l'intérieur d'une fenêtre. " -"Xephyr est recommandé car il fonctionne mieux et prend mieux en charge les " -"extensions récentes du serveur X. GDM définit donc la configuration par " -"défaut à Xephyr, s'il est disponible. Si Xephyr n'est pas disponible, c'est " -"Xnest qui sera utilisé à la place, s'il est disponible." - -#: ../C/gdm.xml:2699(term) -msgid "XnestUnscaledFontPath" -msgstr "XnestUnscaledFontPath" - -#: ../C/gdm.xml:2701(synopsis) -#, no-wrap -msgid "XnestUnscaledFontPath=true" -msgstr "XnestUnscaledFontPath=true" - -#: ../C/gdm.xml:2702(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 <filename>Xnest</filename> configuration option." -msgstr "" -"Défini à « true » (vrai) si le programme de serveur X imbriqué gère le " -"suffixe « :unscaled » dans FontPath (transmis à la commande du serveur X " -"imbriqué par l'argument -fp). Certains programmes Xnest (par ex. Xsun Xnest) " -"ne gèrent pas cela, et il est nécessaire de définir ce paramètre à " -"« false » (faux) pour qu'ils fonctionnent avec GDM. Référez-vous à l'option " -"de configuration <filename>Xnest</filename>." - -#: ../C/gdm.xml:2716(title) -msgid "Security Options" -msgstr "Options de sécurité" - -#: ../C/gdm.xml:2719(title) -msgid "[security]" -msgstr "[security]" - -#: ../C/gdm.xml:2722(term) -msgid "AllowRoot" -msgstr "AllowRoot" - -#: ../C/gdm.xml:2724(synopsis) -#, no-wrap -msgid "AllowRoot=true" -msgstr "AllowRoot=true" - -#: ../C/gdm.xml:2725(para) -msgid "" -"Allow root (privileged user) to log in through GDM. Set this to false if you " -"want to disallow such logins." -msgstr "" -"Permet à root (utilisateur privilégié) de se connecter avec GDM. Définissez " -"ce paramètre à « false » (faux) si vous voulez empêcher de telles connexions." - -#: ../C/gdm.xml:2729(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 "" -"Sur les systèmes qui prennent en charge PAM, ce paramètre n'est pas très " -"utile, puisque vous pouvez utiliser PAM pour faire la même chose, et même " -"plus. Cependant, ce paramètre est tout de même respecté, ce qui fait que " -"vous devriez probablement le laisser à « true » (vrai) pour les systèmes " -"utilisant PAM." - -#: ../C/gdm.xml:2739(term) -msgid "AllowRemoteRoot" -msgstr "AllowRemoteRoot" - -#: ../C/gdm.xml:2741(synopsis) -#, no-wrap -msgid "AllowRemoteRoot=false" -msgstr "AllowRemoteRoot=false" - -#: ../C/gdm.xml:2742(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 "" -"Permet à root (utilisateur privilégié) de se connecter à distance avec GDM. " -"La valeur doit être définie à « true » (vrai) pour autoriser de telles " -"connexions. Les connexions distantes sont celles qui passent par XDMCP." - -#: ../C/gdm.xml:2747(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 "" -"Sur les systèmes qui prennent en charge PAM, ce paramètre n'est pas très " -"utile, puisque vous pouvez utiliser PAM pour faire la même chose, et même " -"plus." - -#: ../C/gdm.xml:2752(para) -msgid "" -"This value will be overridden and set to false if the <filename>/etc/default/" -"login</filename> file exists and contains \"CONSOLE=/dev/login\", and set to " -"true if the <filename>/etc/default/login</filename> file exists and contains " -"any other value or no value for CONSOLE." -msgstr "" -"Cette valeur est écrasée et définie à « false » (faux) si le fichier " -"<filename>/etc/default/login</filename> existe et qu'il contient « CONSOLE=/" -"dev/login », mais définie à « true » (vrai) si le fichier <filename>/etc/" -"default/login</filename> existe et qu'il contient toute autre valeur ou " -"aucune valeur pour CONSOLE." - -#: ../C/gdm.xml:2763(term) -msgid "AllowRemoteAutoLogin" -msgstr "AllowRemoteAutoLogin" - -#: ../C/gdm.xml:2765(synopsis) -#, no-wrap -msgid "AllowRemoteAutoLogin=false" -msgstr "AllowRemoteAutoLogin=false" - -#: ../C/gdm.xml:2766(para) -msgid "" -"Allow the timed login feature to work for remote displays. In other words, " -"remote connections via XDMCP will be allowed to log into the \"TimedLogin\" " -"user after the delay defined by <filename>TimedLoginDelay</filename>." -msgstr "" -"Autorise le fonctionnement de la connexion différée pour les affichages " -"distants. En d'autres termes, les connexions distantes par XDMCP pourront " -"connecter l'utilisateur « TimedLogin » après le délai défini par " -"<filename>TimedLoginDelay</filename>." - -#: ../C/gdm.xml:2772(para) -msgid "" -"Note that this can make a system quite insecure, and thus is off by default." -msgstr "" -"Il faut noter que ceci peut affaiblir la sécurité du système, ce qui " -"explique que ce paramètre est désactivé par défaut." - -#: ../C/gdm.xml:2780(term) -msgid "CheckDirOwner" -msgstr "CheckDirOwner" - -#: ../C/gdm.xml:2782(synopsis) -#, no-wrap -msgid "CheckDirOwner=true" -msgstr "CheckDirOwner=true" - -#: ../C/gdm.xml:2783(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 <filename>RelaxPermissions</filename> 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 "" -"Par défaut, GDM vérifie l'appartenance des dossiers personnels avant d'y " -"écrire, ce qui évite des problèmes de sécurité en cas de mauvaise " -"configuration. Cependant, dans certains cas, il peut arriver que le " -"propriétaire d'un dossier personnel soit différent de l'utilisateur ; dans " -"ce cas, il est nécessaire de désactiver cette option. Il faudra très " -"probablement aussi définir la valeur de la clé <filename>RelaxPermissions</" -"filename> à au moins 1, car dans de telles situations, il est probable que " -"les dossiers personnels soient accessibles en écriture par le groupe. Pris " -"en charge à partir de la version 2.6.0.4." - -#: ../C/gdm.xml:2797(term) -msgid "SupportAutomount" -msgstr "SupportAutomount" - -#: ../C/gdm.xml:2799(synopsis) -#, no-wrap -msgid "SupportAutomount=false" -msgstr "SupportAutomount=false" - -#: ../C/gdm.xml:2800(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 "" -"Par défaut, GDM vérifie l'appartenance des dossiers personnels avant d'y " -"écrire, ce qui évite des problèmes de sécurité en cas de mauvaise " -"configuration. Cependant, lorsque les dossiers personnels sont gérés par " -"automounter, il arrive fréquemment qu'ils ne soient pas montés avant le " -"premier accès. Cette option pallie aux subtilités de automounter Linux." - -#: ../C/gdm.xml:2812(term) -msgid "DisallowTCP" -msgstr "DisallowTCP" - -#: ../C/gdm.xml:2814(synopsis) -#, no-wrap -msgid "DisallowTCP=true" -msgstr "DisallowTCP=true" - -#: ../C/gdm.xml:2815(para) -msgid "" -"If true, then always append <filename>-nolisten tcp</filename> to the " -"command line when starting attached X servers, thus disallowing TCP " -"connection. This is a more secure configuration if not using remote " -"connections." -msgstr "" -"Si défini à « true » (vrai), le paramètre <filename>-nolisten tcp</filename> " -"est toujours transmis sur la ligne de commande lors du démarrage de serveurs " -"X liés, ce qui interdit les connexions TCP. Cela permet de sécuriser la " -"configuration, lorsque les connexions distantes ne sont pas utilisées." - -#: ../C/gdm.xml:2825(term) -msgid "NeverPlaceCookiesOnNFS" -msgstr "NeverPlaceCookiesOnNFS" - -#: ../C/gdm.xml:2827(synopsis) -#, no-wrap -msgid "NeverPlaceCookiesOnNFS=true" -msgstr "NeverPlaceCookiesOnNFS=true" - -#: ../C/gdm.xml:2828(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 "" -"Normalement, si cette option est définie à « true » (vrai) (valeur par " -"défaut), GDM ne dépose pas de cookies dans le dossier personnel des " -"utilisateurs si ce dossier se trouve sur NFS. En fait, GDM considère tout " -"système de fichier utilisant le « root-squashing » comme un système de " -"fichiers NFS. Il peut cependant arriver qu'un système de fichiers distant " -"emploie le « root-squashing » tout en restant sûr (peut-être par " -"l'utilisation du chiffrement). Dans ce cas, définissez cette valeur à " -"« false » (faux). Il faut signaler que cette option est apparue dans la " -"version 2.4.4.4 et est ignorée dans les versions précédentes." - -#: ../C/gdm.xml:2842(term) -msgid "PasswordRequired" -msgstr "PasswordRequired" - -#: ../C/gdm.xml:2844(synopsis) -#, no-wrap -msgid "PasswordRequired=false" -msgstr "PasswordRequired=false" - -#: ../C/gdm.xml:2845(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 <filename>/etc/default/login</filename> if it " -"contains \"PASSREQ=[YES|NO]\". If the <filename>/etc/default/login</" -"filename> file exists, but contains no value for PASSREQ, the value as " -"defined in the GDM configuration will be used." -msgstr "" -"Si défini à « true » (vrai), pam_authenticate et pam_acct_mgmt reçoivent le " -"drapeau PAM_DISALLOW_NULL_AUTHTOK, ce qui désactive le mot de passe vide " -"(NULL). Ce paramètre n'est opérationnel que si GDM utilise PAM. Cette valeur " -"est écrasée par la valeur contenue dans <filename>/etc/default/login</" -"filename>, si ce dernier contient « PASSREQ=[YES|NO] ». Si le fichier " -"<filename>/etc/default/login</filename> existe, mais ne contient aucune " -"valeur pour PASSREQ, c'est la valeur définie dans la configuration GDM qui " -"est utilisée." - -#: ../C/gdm.xml:2861(term) -msgid "RelaxPermissions" -msgstr "RelaxPermissions" - -#: ../C/gdm.xml:2863(synopsis) -#, no-wrap -msgid "RelaxPermissions=0" -msgstr "RelaxPermissions=0" - -#: ../C/gdm.xml:2864(para) -msgid "" -"By default GDM ignores files and directories writable to other users than " -"the owner." -msgstr "" -"Par défaut, GDM ignore les fichiers et les répertoires accessibles en " -"écriture à d'autres utilisateurs que le propriétaire." - -#: ../C/gdm.xml:2869(para) -msgid "" -"Changing the value of RelaxPermissions makes it possible to alter this " -"behavior:" -msgstr "" -"La modification de la valeur de RelaxPermissions permet de changer ce " -"comportement :" - -#: ../C/gdm.xml:2874(para) -msgid "0 - Paranoia option. Only accepts user owned files and directories." -msgstr "" -"0 - option paranoïaque. N'accepte que les fichiers ou répertoires " -"accessibles uniquement par leur propriétaire." - -#: ../C/gdm.xml:2878(para) -msgid "1 - Allow group writable files and directories." -msgstr "" -"1 - accepte les fichiers et répertoires accessibles en écriture par le " -"groupe." - -#: ../C/gdm.xml:2881(para) -msgid "2 - Allow world writable files and directories." -msgstr "" -"2 - accepte les fichiers et répertoires accessibles en écriture par tout le " -"monde." - -#: ../C/gdm.xml:2888(term) -msgid "RetryDelay" -msgstr "RetryDelay" - -#: ../C/gdm.xml:2890(synopsis) -#, no-wrap -msgid "RetryDelay=1" -msgstr "RetryDelay=1" - -#: ../C/gdm.xml:2891(para) -msgid "" -"The number of seconds GDM should wait before reactivating the entry field " -"after a failed login." -msgstr "" -"Le nombre de secondes d'attente avant la réactivation par GDM du champ de " -"saisie à la suite d'un échec de connexion." - -#: ../C/gdm.xml:2899(term) -msgid "UserMaxFile" -msgstr "UserMaxFile" - -#: ../C/gdm.xml:2901(synopsis) -#, no-wrap -msgid "UserMaxFile=65536" -msgstr "UserMaxFile=65536" - -#: ../C/gdm.xml:2902(para) -msgid "" -"GDM will refuse to read/write files bigger than this number (specified in " -"bytes)." -msgstr "" -"GDM refuse de lire ou d'écrire des fichiers plus grands que cette valeur " -"(indiquée en octets)." - -#: ../C/gdm.xml:2907(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 " -"<filename>RelaxPermissions</filename> option for more info." -msgstr "" -"En plus du contrôle de la taille, GDM est extrêmement sensible lorsqu'il " -"s'agit d'accéder à des fichiers dans les dossiers des utilisateurs. Il ne " -"suit pas les liens symboliques et, selon la configuration, il peut refuser " -"de lire des fichiers et des répertoires accessibles en écriture par d'autres " -"personnes que leur propriétaire. Consultez l'option " -"<filename>RelaxPermissions</filename> pour plus d'informations." - -#: ../C/gdm.xml:2917(term) -msgid "UtmpLineAttached" -msgstr "UtmpLineAttached" - -#: ../C/gdm.xml:2919(synopsis) -#, no-wrap -msgid "UtmpLineAttached=/dev/console (or /dev/dtlocal on Solaris)" -msgstr "UtmpLineAttached=/dev/console (ou /dev/dtlocal sur Solaris)" - -#: ../C/gdm.xml:2920(para) -msgid "" -"When doing Utmp processing for attached displays, GDM sets the ut_line to " -"the device associated with the Virtual Terminal (VT) if it is being used. " -"Otherwise, it will use the value specified with the display in the <filename>" -"[servers]</filename> section if a value is provided. If not, then the " -"default value specified in UtmpLineAttached is used for attached displays. " -"The value can contain \"%d\" which is translated to the DISPLAY value or \"%h" -"\" which is translated to the hostname. This value must begin with " -"<filename>/dev/</filename>." -msgstr "" -"Lors du traitement Utmp pour les affichages liés, GDM définit ut_line comme " -"le périphérique associé au terminal virtuel (VT), si ce dernier est utilisé. " -"Sinon, il utilise la valeur définie avec l'affichage dans la section " -"<filename>[servers]</filename>, si une valeur est fournie. Dans le cas " -"contraire, c'est la valeur par défaut définie dans UtmpLineAttached qui est " -"utilisée pour les affichages liés. Cette valeur peut contenir « %d » qui " -"correspond au nom d'affichage (DISPLAY) ou « %h » qui correspond au nom " -"d'hôte. La valeur doit commencer par <filename>/dev/</filename>." - -#: ../C/gdm.xml:2935(term) -msgid "UtmpLineRemote" -msgstr "UtmpLineRemote" - -#: ../C/gdm.xml:2937(synopsis) -#, no-wrap -msgid "UtmpLineRemote= (or /dev/dtremote on Solaris)" -msgstr "UtmpLineRemote= (ou /dev/dtremote sur Solaris)" - -#: ../C/gdm.xml:2938(para) -msgid "" -"When doing Utmp processing, GDM sets the ut_line to this value for remote " -"displays. The value can contain \"%d\" which is translated to the DISPLAY " -"value or \"%h\" which is translated to the hostname. This value must begin " -"with <filename>/dev/</filename>." -msgstr "" -"Lors du traitement Utmp, GDM définit ut_line à cette valeur pour les " -"affichages distants. Cette valeur peut contenir « %d » qui correspond au nom " -"d'affichage (DISPLAY) ou « %h » qui correspond au nom d'hôte. La valeur doit " -"commencer par <filename>/dev/</filename>." - -#: ../C/gdm.xml:2948(term) -msgid "UtmpPseudoDevice" -msgstr "UtmpPseudoDevice" - -#: ../C/gdm.xml:2950(synopsis) -#, no-wrap -msgid "PseudoDevice=false (or true on Solaris)" -msgstr "PseudoDevice=false (ou true sur Solaris)" - -#: ../C/gdm.xml:2951(para) -msgid "" -"If the device associated with a display does not exist, then GDM will create " -"a symlink to <filename>/dev/null</filename>, or touch it if it is a symlink " -"to <filename>/dev/null</filename>. Some programs such as <command>last</" -"command>, <command>finger</command>, or <command>who</command> access the " -"utmp database and may assume that the device points to an actual file. " -"Creating such symlinks ensures that such programs work properly." -msgstr "" -"Si le périphérique associé à l'affichage n'existe pas, GDM crée un lien " -"symbolique vers <filename>/dev/null</filename> ou effectue un « touch » sur " -"le lien s'il existe déjà. Certains programmes comme <command>last</command>, " -"<command>finger</command> ou <command>who</command> ont accès à la base de " -"données utmp et peuvent supposer que le périphérique indique un fichier " -"réel. La création de tels liens symboliques assure que de tels programmes " -"fonctionnent correctement." - -#: ../C/gdm.xml:2967(title) -msgid "XDCMP Support" -msgstr "Prise en charge de XDMCP" - -#: ../C/gdm.xml:2970(title) -msgid "[xdmcp]" -msgstr "[xdmcp]" - -#: ../C/gdm.xml:2973(term) -msgid "DisplaysPerHost" -msgstr "DisplaysPerHost" - -#: ../C/gdm.xml:2975(synopsis) -#, no-wrap -msgid "DisplaysPerHost=1" -msgstr "DisplaysPerHost=1" - -#: ../C/gdm.xml:2976(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 " -"<filename>DisplaysPerHost</filename> value accordingly." -msgstr "" -"Pour empêcher des attaquants de remplir la file d'attente, GDM n'accepte " -"qu'une seule connexion par ordinateur distant. Si vous souhaitez offrir des " -"services d'affichage à des ordinateurs ayant plus d'un écran, vous devez " -"augmenter la valeur de <filename>DisplaysPerHost</filename> en conséquence." - -#: ../C/gdm.xml:2984(para) -msgid "" -"Note that the number of attached DISPLAYS allowed is not limited. Only " -"remote connections via XDMCP are limited by this configuration option." -msgstr "" -"Il faut relever que le nombre autorisé d'affichages liés est illimité. " -"Seules les connexions distantes par XDMCP sont limitées par cette option de " -"configuration." - -#: ../C/gdm.xml:2993(term) ../C/gdm.xml:4239(term) -msgid "Enable" -msgstr "Enable" - -#: ../C/gdm.xml:2995(synopsis) ../C/gdm.xml:4241(synopsis) -#, no-wrap -msgid "Enable=false" -msgstr "Enable=false" - -#: ../C/gdm.xml:2996(para) -msgid "" -"Setting this to true enables XDMCP support allowing remote displays/X " -"terminals to be managed by GDM." -msgstr "" -"La définition de cette option à « true » (vrai) active la prise en charge de " -"XDMCP pour permettre à des terminaux X ou des affichages distants d'être " -"gérés par GDM." - -#: ../C/gdm.xml:3001(para) -msgid "" -"<filename>gdm</filename> listens for requests on UDP port 177. See the Port " -"option for more information." -msgstr "" -"<filename>gdm</filename> écoute les requêtes sur le port UDP 177. Consultez " -"l'option Port pour plus d'informations." - -#: ../C/gdm.xml:3006(para) -msgid "" -"If GDM is compiled to support it, access from remote displays can be " -"controlled using the TCP Wrappers library. The service name is " -"<filename>gdm</filename>" -msgstr "" -"Si GDM est compilé pour le prendre en charge, l'accès à partir d'affichages " -"distants peut être contrôlé par la bibliothèque TCP Wrappers. Le nom de " -"service est <filename>gdm</filename>." - -#: ../C/gdm.xml:3012(para) -msgid "" -"You should add <screen>\n" -"gdm:.my.domain\n" -"</screen> to your <filename><etc>/hosts.allow</filename>, depending on " -"your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:" -"hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" -"Vous devez alors ajouter <screen>\n" -"gdm:.mon.domaine\n" -"</screen> à votre fichier <filename><etc>/hosts.allow</filename>, " -"selon votre configuration de TCP Wrappers. Consultez la page de manuel " -"<ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> pour " -"plus de détails." - -#: ../C/gdm.xml:3023(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 "" -"Il faut relever que XDMCP n'est pas un protocole particulièrement sécurisé, " -"et qu'il est conseillé de bloquer le port UDP 177 sur votre pare-feu si vous " -"n'en avez pas vraiment besoin." - -#: ../C/gdm.xml:3032(term) -msgid "EnableProxy" -msgstr "EnableProxy" - -#: ../C/gdm.xml:3034(synopsis) -#, no-wrap -msgid "EnableProxy=false" -msgstr "EnableProxy=false" - -#: ../C/gdm.xml:3035(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 "" -"La définition de cette option à « true » (vrai) active la possibilité " -"d'exécuter des sessions XDMCP sur un serveur X proxy local. Cela peut " -"améliorer les performances des sessions XDMCP, particulièrement sur les " -"réseaux à latence élevée, car beaucoup d'opérations du protocole X peuvent " -"s'effectuer sans transiter par le réseau." - -#: ../C/gdm.xml:3042(para) -msgid "" -"Note, however, that this mode will significantly increase the burden on the " -"machine hosting the XDMCP sessions" -msgstr "" -"Il faut cependant relever que ce mode va notablement augmenter la charge sur " -"la machine hébergeant les sessions XDMCP." - -#: ../C/gdm.xml:3046(para) -msgid "" -"See the <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</" -"filename> options for further details on how to configure support for this " -"feature." -msgstr "" -"Consultez les options <filename>FlexiProxy</filename> et " -"<filename>FlexiProxyDisconnect</filename> pour plus de détails sur la façon " -"de configurer la prise en charge de cette fonctionnalité." - -#: ../C/gdm.xml:3055(term) -msgid "HonorIndirect" -msgstr "HonorIndirect" - -#: ../C/gdm.xml:3057(synopsis) -#, no-wrap -msgid "HonorIndirect=true" -msgstr "HonorIndirect=true" - -#: ../C/gdm.xml:3058(para) -msgid "" -"Enables XDMCP INDIRECT choosing (i.e. remote execution of " -"<filename>gdmchooser</filename>) for X-terminals which don't supply their " -"own display browser." -msgstr "" -"Active le choix XDMCP INDIRECT (c'est-à-dire l'exécution distante de " -"<filename>gdmchooser</filename>) pour les terminaux X qui ne possèdent pas " -"leur propre navigateur d'affichage." - -#: ../C/gdm.xml:3067(term) -msgid "MaxPending" -msgstr "MaxPending" - -#: ../C/gdm.xml:3069(synopsis) -#, no-wrap -msgid "MaxPending=4" -msgstr "MaxPending=4" - -#: ../C/gdm.xml:3070(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 "" -"Pour éviter les attaques par déni de service, GDM dispose d'une file " -"d'attente de connexions limitée. Seuls MaxPending affichages peuvent " -"démarrer simultanément." - -#: ../C/gdm.xml:3076(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 "" -"Notez que ce paramètre ne limite *pas* le nombre d'affichages distants " -"gérables. Il limite seulement le nombre d'affichages lançant simultanément " -"une connexion." - -#: ../C/gdm.xml:3085(term) -msgid "MaxPendingIndirect" -msgstr "MaxPendingIndirect" - -#: ../C/gdm.xml:3087(synopsis) -#, no-wrap -msgid "MaxPendingIndirect=4" -msgstr "MaxPendingIndirect=4" - -#: ../C/gdm.xml:3088(para) -msgid "" -"GDM will only provide <filename>MaxPendingIndirect</filename> displays with " -"host choosers simultaneously. If more queries from different hosts come in, " -"the oldest ones will be forgotten." -msgstr "" -"GDM ne propose simultanément que le nombre d'affichages correspondant à " -"<filename>MaxPendingIndirect</filename> avec des sélecteurs d'hôte. Si des " -"requêtes supplémentaires lui parviennent d'hôtes différents, les plus " -"anciennes sont abandonnées." - -#: ../C/gdm.xml:3098(term) -msgid "MaxSessions" -msgstr "MaxSessions" - -#: ../C/gdm.xml:3100(synopsis) -#, no-wrap -msgid "MaxSessions=16" -msgstr "MaxSessions=16" - -#: ../C/gdm.xml:3101(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 "" -"Détermine le nombre maximal de connexions d'affichages distants gérées " -"simultanément. Cela correspond donc au nombre total d'affichages distants " -"utilisables par l'hôte." - -#: ../C/gdm.xml:3110(term) -msgid "MaxWait" -msgstr "MaxWait" - -#: ../C/gdm.xml:3112(synopsis) -#, no-wrap -msgid "MaxWait=30" -msgstr "MaxWait=30" - -#: ../C/gdm.xml:3113(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 "" -"Lorsque GDM est prêt à gérer un affichage, un paquet ACCEPT lui est envoyé " -"avec un identifiant de session unique qui sera utilisé dans les échanges " -"XDMCP subséquents." - -#: ../C/gdm.xml:3119(para) -msgid "" -"GDM will then place the session id in the pending queue waiting for the " -"display to respond with a MANAGE request." -msgstr "" -"GDM place ensuite l'identifiant de session dans la file d'attente, en " -"attendant que l'affichage réponde par une requête MANAGE." - -#: ../C/gdm.xml:3124(para) -msgid "" -"If no response is received within MaxWait seconds, GDM will declare the " -"display dead and erase it from the pending queue freeing up the slot for " -"other displays." -msgstr "" -"Si aucune réponse n'arrive dans l'intervalle en secondes défini par MaxWait, " -"GDM considère l'affichage comme mort et l'efface de la file d'attente, " -"libérant la place pour d'autres affichages." - -#: ../C/gdm.xml:3133(term) -msgid "MaxWaitIndirect" -msgstr "MaxWaitIndirect" - -#: ../C/gdm.xml:3135(synopsis) -#, no-wrap -msgid "MaxWaitIndirect=30" -msgstr "MaxWaitIndirect=30" - -#: ../C/gdm.xml:3136(para) -msgid "" -"The MaxWaitIndirect parameter determines the maximum number of seconds " -"between the time where a user chooses a host and the subsequent indirect " -"query where the user is connected to the host. When the timeout is exceeded, " -"the information about the chosen host is forgotten and the indirect slot " -"freed up for other displays. The information may be forgotten earlier if " -"there are more hosts trying to send indirect queries then " -"<filename>MaxPendingIndirect</filename>." -msgstr "" -"Le paramètre MaxWaitIndirect détermine le nombre maximal de secondes entre " -"le moment où un utilisateur choisit un hôte et la requête indirecte " -"correspondant à la connexion de l'utilisateur à l'hôte. Si ce délai est " -"dépassé, l'information à propos de l'hôte choisi est oubliée et la place est " -"libérée pour une autre demande d'affichage indirect. Il se peut que cette " -"information soit oubliée plus rapidement s'il y a davantage d'hôtes essayant " -"d'envoyer des requêtes indirectes que le nombre défini dans " -"<filename>MaxPendingIndirect</filename>." - -#: ../C/gdm.xml:3150(term) -msgid "Port" -msgstr "Port" - -#: ../C/gdm.xml:3152(synopsis) -#, no-wrap -msgid "Port=177" -msgstr "Port=177" - -#: ../C/gdm.xml:3153(para) -msgid "" -"The UDP port number <filename>gdm</filename> should listen to for XDMCP " -"requests. Don't change this unless you know what you are doing." -msgstr "" -"Le numéro de port UDP que <filename>gdm</filename> doit écouter pour les " -"requêtes XDMCP. Ne changez ce paramètre que si vous savez bien ce que vous " -"faites." - -#: ../C/gdm.xml:3162(term) -msgid "PingIntervalSeconds" -msgstr "PingIntervalSeconds" - -#: ../C/gdm.xml:3164(synopsis) -#, no-wrap -msgid "PingIntervalSeconds=15" -msgstr "PingIntervalSeconds=15" - -#: ../C/gdm.xml:3165(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 "" -"Intervalle en secondes des « ping » envoyés au serveur X. Si le serveur X ne " -"répond pas avant le prochain ping, la connexion est interrompue et la " -"session se termine. C'est une combinaison des paramètres PingInterval et " -"PingTimeout de XDM, mais en secondes." - -#: ../C/gdm.xml:3173(para) -msgid "" -"Note that GDM in the past used to have a <filename>PingInterval</filename> " -"configuration key which was also in minutes. For most purposes you'd want " -"this setting to be lower 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 "" -"Signalons que dans le passé, GDM avait une clé de configuration " -"<filename>PingInterval</filename> qui était aussi définie en minutes. Dans " -"bien des cas, il est souhaitable de définir une valeur en-dessous de la " -"minute, car dans la plupart des utilisations de XDMCP (comme dans des salles " -"de terminaux), des délais de réponse supérieurs à une quinzaine de secondes " -"signifie vraiment que le terminal a été éteint ou redémarré, et il est " -"préférable de terminer la session." - -#: ../C/gdm.xml:3186(term) -msgid "ProxyReconnect" -msgstr "ProxyReconnect" - -#: ../C/gdm.xml:3188(synopsis) -#, no-wrap -msgid "FlexiProxyReconnect=" -msgstr "FlexiProxyReconnect=" - -#: ../C/gdm.xml:3189(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 "" -"La définition de cette option active la prise en charge expérimentale des " -"migrations de sessions XDMCP. Ceci permet aux utilisateurs d'interrompre une " -"session, puis de se reconnecter à la même session, même depuis un autre " -"terminal." - -#: ../C/gdm.xml:3195(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 "" -"Pour pouvoir utiliser cette fonctionnalité, vous devez disposer d'un serveur " -"X imbriqué qui prend en charge la déconnexion de son serveur X parent et la " -"reconnexion à un autre serveur X. Actuellement, le serveur Distributed " -"Multihead X (DMX) gère partiellement cette fonctionnalité et d'autres " -"projets comme NoMachine NX font des efforts d'implémentation dans ce sens." - -#: ../C/gdm.xml:3202(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 "" -"Cette option devrait être définie au chemin d'une commande qui s'occupe de " -"reconnecter le proxy XDMCP à un autre moteur d'affichage. Un modèle " -"d'implémentation utilisable avec DMX est fourni." - -#: ../C/gdm.xml:3211(term) -msgid "ProxyXServer" -msgstr "ProxyXServer" - -#: ../C/gdm.xml:3213(synopsis) -#, no-wrap -msgid "ProxyXServer=" -msgstr "ProxyXServer=" - -#: ../C/gdm.xml:3214(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 "" -"La ligne de commande de serveur X pour un proxy XDMCP. Tout serveur X " -"imbriqué tel que Xnest, Xephyr ou Xdmx devrait assez bien fonctionner." - -#: ../C/gdm.xml:3222(term) -msgid "Willing" -msgstr "Willing" - -#: ../C/gdm.xml:3224(synopsis) -#, no-wrap -msgid "Willing=<etc>/gdm/Xwilling" -msgstr "Willing=<etc>/gdm/Xwilling" - -#: ../C/gdm.xml:3225(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 "" -"Lorsque la machine renvoie un paquet WILLING après une requête (QUERY), il " -"envoie une chaîne de caractères informant sur l'état actuel de ce serveur. " -"Le message par défaut est l'identifiant système, mais il est possible de " -"créer un script qui génère un message personnalisé. Si ce script n'existe " -"pas ou que cette clé est vide, c'est le message par défaut qui est envoyé. " -"Si ce script réussit à produire un résultat, la première ligne du résultat " -"est envoyée (et seulement la première ligne). Il s'exécute au maximum une " -"fois toutes les 3 secondes pour empêcher de possibles attaques par déni de " -"service qui submergeraient la machine de paquets QUERY." - -#: ../C/gdm.xml:3243(title) -msgid "Common GUI Configuration Options" -msgstr "Options de configuration courantes de l'interface graphique" - -#: ../C/gdm.xml:3246(title) -msgid "[gui]" -msgstr "[gui]" - -#: ../C/gdm.xml:3249(term) -msgid "AllowGtkThemeChange" -msgstr "AllowGtkThemeChange" - -#: ../C/gdm.xml:3251(synopsis) -#, no-wrap -msgid "AllowGtkThemeChange=true" -msgstr "AllowGtkThemeChange=true" - -#: ../C/gdm.xml:3252(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 "" -"Détermine s'il est permis de changer le thème GTK+ (widget) de la bannière. " -"Actuellement, cela ne concerne que la bannière standard, car la bannière " -"graphique ne dispose pas de cette possibilité. Le thème reste actif sur cet " -"affichage tant qu'il n'est pas modifié, et il influence toutes les autres " -"fenêtres ouvertes par GDM. Prise en charge depuis la version 2.5.90.2." - -#: ../C/gdm.xml:3264(term) -msgid "GtkRC" -msgstr "GtkRC" - -#: ../C/gdm.xml:3266(synopsis) -#, no-wrap -msgid "GtkRC=" -msgstr "GtkRC=" - -#: ../C/gdm.xml:3267(para) -msgid "" -"Path to a <filename>gtkrc</filename> to read when GDM puts up a window. You " -"should really now use the <filename>GtkTheme</filename> key for just setting " -"a theme." -msgstr "" -"Chemin vers un fichier <filename>gtkrc</filename> que GDM doit lire avant " -"d'ouvrir une fenêtre. Il faudrait dorénavant vraiment utiliser la clé " -"<filename>GtkTheme</filename> pour simplement définir un thème." - -#: ../C/gdm.xml:3276(term) -msgid "GtkTheme" -msgstr "GtkTheme" - -#: ../C/gdm.xml:3278(synopsis) -#, no-wrap -msgid "GtkTheme=Default" -msgstr "GtkTheme=Default" - -#: ../C/gdm.xml:3279(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 "" -"Le nom d'un thème à installer par défaut. Il sera utilisé dans la bannière, " -"le sélecteur et toutes les autres fenêtres graphiques ouvertes par GDM. Pris " -"en charge depuis la version 2.5.90.2." - -#: ../C/gdm.xml:3288(term) -msgid "GtkThemesToAllow" -msgstr "GtkThemesToAllow" - -#: ../C/gdm.xml:3290(synopsis) -#, no-wrap -msgid "GtkThemesToAllow=all" -msgstr "GtkThemesToAllow=all" - -#: ../C/gdm.xml:3291(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 " -"<filename>AllowGtkThemeChange</filename> key. Supported since 2.5.90.2." -msgstr "" -"Liste des thèmes à autoriser, séparés par des virgules. Ce doit être les " -"noms des thèmes installés dans les emplacements standards des thèmes GTK+. " -"Vous pouvez aussi indiquer « all » pour autoriser tous les thèmes installés. " -"Ceci est lié à la clé <filename>AllowGtkThemeChange</filename>. Pris en " -"charge depuis la version 2.5.90.2." - -#: ../C/gdm.xml:3303(term) -msgid "MaxIconWidth" -msgstr "MaxIconWidth" - -#: ../C/gdm.xml:3305(synopsis) -#, no-wrap -msgid "MaxIconWidth=128" -msgstr "MaxIconWidth=128" - -#: ../C/gdm.xml:3306(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 "" -"Indique la largeur d'icône maximale (en pixels) affichée par le navigateur " -"de figures. Les icônes plus larges que cette valeur sont redimensionnées. " -"Cela concerne également les icônes du sélecteur XDMCP." - -#: ../C/gdm.xml:3315(term) -msgid "MaxIconHeight" -msgstr "MaxIconHeight" - -#: ../C/gdm.xml:3317(synopsis) -#, no-wrap -msgid "MaxIconHeight=128" -msgstr "MaxIconHeight=128" - -#: ../C/gdm.xml:3318(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 "" -"Indique la hauteur d'icône maximale (en pixels) affichée par le navigateur " -"de figures. Les icônes plus hautes que cette valeur sont redimensionnées. " -"Cela concerne également les icônes du sélecteur XDMCP." - -#: ../C/gdm.xml:3329(title) -msgid "Greeter Configuration" -msgstr "Configuration de la bannière" - -#: ../C/gdm.xml:3332(title) -msgid "[greeter]" -msgstr "[greeter]" - -#: ../C/gdm.xml:3335(term) -msgid "BackgroundColor" -msgstr "BackgroundColor" - -#: ../C/gdm.xml:3337(synopsis) -#, no-wrap -msgid "BackgroundColor=#76848F" -msgstr "BackgroundColor=#76848F" - -#: ../C/gdm.xml:3338(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 "" -"Si la valeur de BackgroundType est de 2, c'est cette couleur qui sera " -"utilisée en arrière-plan de la bannière. Elle est aussi utilisée comme fond " -"des images transparentes placées sur l'arrière-plan, également dans le cas " -"où BackgroundRemoteOnlyColor est défini et que l'affichage est distant. Cela " -"ne concerne que la bannière GTK+." - -#: ../C/gdm.xml:3349(term) -msgid "BackgroundProgramInitialDelay" -msgstr "BackgroundProgramInitialDelay" - -#: ../C/gdm.xml:3351(synopsis) -#, no-wrap -msgid "BackgroundProgramInitialDelay=30" -msgstr "BackgroundProgramInitialDelay=30" - -#: ../C/gdm.xml:3352(para) -msgid "" -"The background application will be started after at least that many seconds " -"of inactivity." -msgstr "" -"L'application d'arrière-plan est démarrée après un nombre de secondes " -"d'inactivité au moins équivalent à cette valeur." - -#: ../C/gdm.xml:3360(term) -msgid "RestartBackgroundProgram" -msgstr "RestartBackgroundProgram" - -#: ../C/gdm.xml:3362(synopsis) -#, no-wrap -msgid "RestartBackgroundProgram=true" -msgstr "RestartBackgroundProgram=true" - -#: ../C/gdm.xml:3363(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 "" -"Si défini à « true » (vrai), l'application d'arrière-plan est redémarrée " -"après s'être arrêtée, après l'écoulement du délai défini dans le paramètre " -"ci-dessous. Cette option peut se révéler utile si vous voulez lancer un " -"économiseur d'écran lorsque personne n'utilise l'ordinateur." - -#: ../C/gdm.xml:3373(term) -msgid "BackgroundProgramRestartDelay" -msgstr "BackgroundProgramRestartDelay" - -#: ../C/gdm.xml:3375(synopsis) -#, no-wrap -msgid "BackgroundProgramRestartDelay=30" -msgstr "BackgroundProgramRestartDelay=30" - -#: ../C/gdm.xml:3376(para) -msgid "" -"The background application will be restarted after at least that many " -"seconds of inactivity." -msgstr "" -"L'application d'arrière-plan est redémarrée après un nombre de secondes " -"d'inactivité au moins équivalent à cette valeur." - -#: ../C/gdm.xml:3384(term) -msgid "BackgroundImage" -msgstr "BackgroundImage" - -#: ../C/gdm.xml:3386(synopsis) -#, no-wrap -msgid "BackgroundImage=somefile.png" -msgstr "BackgroundImage=unfichier.png" - -#: ../C/gdm.xml:3387(para) -msgid "" -"If the BackgroundType is 1, then display this file as the background in the " -"greeter. This only affects the GTK+ Greeter." -msgstr "" -"Si le paramètre BackgroundType vaut 1, ce fichier est affiché en arrière-" -"plan de la bannière. Cela ne concerne que la bannière GTK+." - -#: ../C/gdm.xml:3396(term) -msgid "BackgroundProgram" -msgstr "BackgroundProgram" - -#: ../C/gdm.xml:3398(synopsis) -#, no-wrap -msgid "BackgroundProgram=<bin>/xeyes" -msgstr "BackgroundProgram=<bin>/xeyes" - -#: ../C/gdm.xml:3399(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 "" -"Cette commande est exécutée en arrière-plan durant l'affichage de la fenêtre " -"de connexion. Notez que certaines applications peuvent ne pas fonctionner de " -"cette manière, car GDM n'a normalement pas de dossier personnel. Il est " -"possible de configurer un dossier personnel pour l'utilisateur GDM si vous " -"souhaitez lancer une application qui l'exige. Cela ne concerne que la " -"bannière GTK+." - -#: ../C/gdm.xml:3411(term) -msgid "BackgroundRemoteOnlyColor" -msgstr "BackgroundRemoteOnlyColor" - -#: ../C/gdm.xml:3413(synopsis) -#, no-wrap -msgid "BackgroundRemoteOnlyColor=true" -msgstr "BackgroundRemoteOnlyColor=true" - -#: ../C/gdm.xml:3414(para) -msgid "" -"On remote displays only set the color background. This is to make network " -"load lighter. The <filename>BackgroundProgram</filename> is also not run. " -"This only affects the GTK+ Greeter." -msgstr "" -"N'affiche que la couleur d'arrière-plan pour les affichages distants. Cela " -"permet d'alléger la charge réseau. Le programme défini par " -"<filename>BackgroundProgram</filename> n'est pas non plus exécuté. Cela ne " -"concerne que la bannière GTK+." - -#: ../C/gdm.xml:3424(term) -msgid "BackgroundScaleToFit" -msgstr "BackgroundScaleToFit" - -#: ../C/gdm.xml:3426(synopsis) -#, no-wrap -msgid "BackgroundScaleToFit=true" -msgstr "BackgroundScaleToFit=true" - -#: ../C/gdm.xml:3427(para) -msgid "" -"Scale background image to fit the screen. This only affects the GTK+ Greeter." -msgstr "" -"Redimensionne l'image d'arrière-plan pour correspondre à l'écran. Cela ne " -"concerne que la bannière GTK+." - -#: ../C/gdm.xml:3435(term) -msgid "BackgroundType" -msgstr "BackgroundType" - -#: ../C/gdm.xml:3437(synopsis) -#, no-wrap -msgid "BackgroundType=2" -msgstr "BackgroundType=2" - -#: ../C/gdm.xml:3438(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 "" -"Le type d'arrière-plan utilisé. 0 signifie aucun, 1 pour l'image et la " -"couleur, 2 pour la couleur et 3 pour l'image. Cela ne concerne que la " -"bannière GTK+." - -#: ../C/gdm.xml:3446(term) -msgid "Browser" -msgstr "Browser" - -#: ../C/gdm.xml:3448(synopsis) -#, no-wrap -msgid "Browser=true" -msgstr "Browser=true" - -#: ../C/gdm.xml:3449(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 "" -"Si défini à « true » (vrai), active le navigateur de figures. Consultez la " -"section « La bannière GTK+ » pour plus d'informations sur le navigateur de " -"figures. Cette option n'est valide que pour la bannière GTK+. En ce qui " -"concerne la bannière avec thème, le navigateur de figures est activé en " -"choisissant un thème qui le contient." - -#: ../C/gdm.xml:3460(term) -msgid "ChooserButton" -msgstr "ChooserButton" - -#: ../C/gdm.xml:3462(synopsis) -#, no-wrap -msgid "ChooserButton=true" -msgstr "ChooserButton=true" - -#: ../C/gdm.xml:3463(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 "" -"Si défini à « true » (vrai), ajoute un bouton de sélecteur au menu Actions " -"permettant de redémarrer le serveur X actuel avec un sélecteur. Il n'est pas " -"nécessaire d'activer XDMCP sur l'ordinateur local pour que cela fonctionne." - -#: ../C/gdm.xml:3472(term) -msgid "ConfigAvailable" -msgstr "ConfigAvailable" - -#: ../C/gdm.xml:3474(synopsis) -#, no-wrap -msgid "ConfigAvailable=false" -msgstr "ConfigAvailable=false" - -#: ../C/gdm.xml:3475(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 " -"<filename>Configurator</filename> option in the daemon section." -msgstr "" -"Si défini à « true » (vrai), permet le lancement du programme de " -"configuration à partir de la bannière. Il faut bien sûr que l'utilisateur " -"saisisse le mot de passe d'administration avant que le programme ne soit " -"lancé. Pour plus de sécurité, ce paramètre est défini à « false » (faux) par " -"défaut. Consultez l'option <filename>Configurator</filename> dans la section " -"« daemon »." - -#: ../C/gdm.xml:3487(term) -msgid "DefaultFace" -msgstr "DefaultFace" - -#: ../C/gdm.xml:3489(synopsis) -#, no-wrap -msgid "DefaultFace=<share>/pixmaps/nophoto.png" -msgstr "DefaultFace=<share>/pixmaps/nophoto.png" - -#: ../C/gdm.xml:3490(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 <filename>DefaultFace</filename> will be used. The image must " -"be in a gdk-pixbuf supported format and the file must be readable to the GDM " -"user." -msgstr "" -"Si un utilisateur ne dispose pas d'image de figure, GDM utilise l'icône " -"prédéfinie « stock_person » dans le thème GTK+ actuel. Si celle-ci n'existe " -"pas, c'est l'image définie par <filename>DefaultFace</filename> qui est " -"utilisée. L'image doit être dans un format pris en charge par gdk-pixbuf et " -"le fichier doit être accessible en lecture par l'utilisateur GDM." - -#: ../C/gdm.xml:3502(term) -msgid "Include" -msgstr "Include" - -#: ../C/gdm.xml:3504(synopsis) -#, no-wrap -msgid "Include=" -msgstr "Include=" - -#: ../C/gdm.xml:3505(para) -msgid "" -"Comma separated list of users to be included in the face browser and in the " -"<command>gdmsetup</command> selection list for Automatic/Timed login. See " -"also <filename>Exclude</filename>, <filename>IncludeAll</filename>, and " -"<filename>MinimalUID</filename>." -msgstr "" -"Liste d'utilisateurs, séparés par des virgules, à inclure dans le navigateur " -"de figures et dans la liste de sélection de <command>gdmsetup</command> pour " -"la connexion automatique ou différée. Voir aussi les paramètres " -"<filename>Exclude</filename>, <filename>IncludeAll</filename> et " -"<filename>MinimalUID</filename>." - -#: ../C/gdm.xml:3517(term) -msgid "Exclude" -msgstr "Exclude" - -#: ../C/gdm.xml:3519(synopsis) -#, no-wrap -msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." -msgstr "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." - -#: ../C/gdm.xml:3520(para) -msgid "" -"Comma separated list of users to be excluded from the face browser and from " -"the <command>gdmsetup</command> selection list for Automatic/Timed login. " -"Excluded users will still be able to log in, but will have to type their " -"username. See also <filename>Include</filename>, <filename>IncludeAll</" -"filename>, and <filename>MinimalUID</filename>." -msgstr "" -"Liste d'utilisateurs, séparés par des virgules, à exclure du navigateur de " -"figures et de la liste de sélection de <command>gdmsetup</command> pour la " -"connexion automatique ou différée. Les utilisateurs exclus pourront toujours " -"se connecter, mais en devant saisir leur nom d'utilisateur. Voir aussi les " -"paramètres <filename>Include</filename>, <filename>IncludeAll</filename> et " -"<filename>MinimalUID</filename>." - -#: ../C/gdm.xml:3533(term) -msgid "IncludeAll" -msgstr "IncludeAll" - -#: ../C/gdm.xml:3535(synopsis) -#, no-wrap -msgid "IncludeAll=false" -msgstr "IncludeAll=false" - -#: ../C/gdm.xml:3536(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 <filename>Include</filename>, <filename>Exclude</" -"filename>, and <filename>MinimalUID</filename>." -msgstr "" -"Par défaut, une liste « Include » vide signifie qu'aucun utilisateur n'est " -"affiché. En définissant IncludeAll à « true » (vrai), le fichier des mots de " -"passe est parcouru et tous les utilisateurs sont affichés, à l'exception des " -"exclus de la liste « Exclude » et de ceux dont l'identifiant est plus petit " -"que « MinimalUID ». Le parcours du fichier des mots de passe peut être lent " -"sur les systèmes ayant un grand nombre d'utilisateurs ; il ne faudrait donc " -"pas utiliser cette fonctionnalité sur de tels systèmes. Voir aussi les " -"paramètres <filename>Include</filename>, <filename>Exclude</filename> et " -"<filename>MinimalUID</filename>." - -#: ../C/gdm.xml:3552(term) -msgid "GlobalFaceDir" -msgstr "GlobalFaceDir" - -#: ../C/gdm.xml:3554(synopsis) -#, no-wrap -msgid "GlobalFaceDir=<share>/pixmaps/faces/" -msgstr "GlobalFaceDir=<share>/pixmaps/faces/" - -#: ../C/gdm.xml:3555(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 "" -"Répertoire contenant les fichiers de figures pour tout le système. Les " -"administrateurs systèmes peuvent placer les icônes des utilisateurs à cet " -"endroit, sans devoir toucher à leur dossier personnel. Les fichiers de " -"figures sont nommés d'après le nom de l'utilisateur correspondant." - -#: ../C/gdm.xml:3561(para) -msgid "" -"I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the " -"face icon for the user ``johndoe''. No image format extension should be " -"specified." -msgstr "" -"Par exemple, <filename><GlobalFaceDir>/jdupond</filename> contient " -"l'icône de figure pour l'utilisateur « jdupond ». Il ne faut pas ajouter " -"d'extension de format d'image." - -#: ../C/gdm.xml:3567(para) -msgid "" -"The face images must be stored in gdk-pixbuf supported formats and they must " -"be readable for the GDM user." -msgstr "" -"Les images de figures doivent être enregistrées dans un format pris en " -"charge par gdk-pixbuf et elles doivent être lisibles par l'utilisateur GDM." - -#: ../C/gdm.xml:3572(para) -msgid "" -"A user's own icon file will always take precedence over the sysadmin " -"provided one." -msgstr "" -"Un fichier de figure fourni par un utilisateur (à l'endroit adéquat de son " -"dossier personnel) a toujours la priorité sur le fichier système." - -#: ../C/gdm.xml:3580(term) -msgid "GraphicalTheme" -msgstr "GraphicalTheme" - -#: ../C/gdm.xml:3582(synopsis) -#, no-wrap -msgid "GraphicalTheme=circles" -msgstr "GraphicalTheme=circles" - -#: ../C/gdm.xml:3583(para) -msgid "" -"The graphical theme that the Themed Greeter should use. it should refer to a " -"directory in the theme directory set by <filename>GraphicalThemeDir</" -"filename>." -msgstr "" -"Le thème graphique que la bannière avec thème doit utiliser. La valeur doit " -"correspondre à un nom de répertoire dans le répertoire des thèmes défini par " -"<filename>GraphicalThemeDir</filename>." - -#: ../C/gdm.xml:3592(term) -msgid "GraphicalThemes" -msgstr "GraphicalThemes" - -#: ../C/gdm.xml:3594(synopsis) -#, no-wrap -msgid "GraphicalThemes=circles" -msgstr "GraphicalThemes=circles" - -#: ../C/gdm.xml:3595(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 <filename>GraphicalThemeDir</" -"filename>. This is only used if <filename>GraphicalThemeRand</filename> is " -"set to true." -msgstr "" -"Les thèmes graphiques, séparés par des deux-points, que la bannière avec " -"thème doit utiliser, dans le cas où le mode des thèmes aléatoires est " -"sélectionné. Les valeurs doivent correspondre à des noms de répertoires dans " -"le répertoire des thèmes défini par <filename>GraphicalThemeDir</filename>. " -"Ce paramètre n'est utilisé que si <filename>GraphicalThemeRand</filename> " -"est défini à « true » (vrai)." - -#: ../C/gdm.xml:3607(term) -msgid "GraphicalThemeRand" -msgstr "GraphicalThemeRand" - -#: ../C/gdm.xml:3609(synopsis) -#, no-wrap -msgid "GraphicalThemeRand=false" -msgstr "GraphicalThemeRand=false" - -#: ../C/gdm.xml:3610(para) -msgid "" -"Whether the graphical greeter will use Only One Theme or Random Theme mode. " -"Only One Theme mode uses themes listed by <filename>GraphicalTheme</" -"filename>, Random Themes mode uses themes listed by " -"<filename>GraphicalThemes</filename>. 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 "" -"Indique si la bannière graphique utilise le mode « Uniquement sélectionné » " -"ou « Sélection aléatoire ». Le premier mode utilise le thème indiqué par " -"<filename>GraphicalTheme</filename>, alors que le second utilise les thèmes " -"définis dans la liste <filename>GraphicalThemes</filename>. La valeur " -"« false » indique à la bannière d'utiliser le mode « Uniquement " -"sélectionné », alors que la valeur « true » (vrai) active le mode " -"« Sélection aléatoire »." - -#: ../C/gdm.xml:3622(term) -msgid "GraphicalThemeDir" -msgstr "GraphicalThemeDir" - -#: ../C/gdm.xml:3624(synopsis) -#, no-wrap -msgid "GraphicalThemeDir=<share>/gdm/themes/" -msgstr "GraphicalThemeDir=<share>/gdm/themes/" - -#: ../C/gdm.xml:3625(para) -msgid "The directory where themes for the Themed Greeter are installed." -msgstr "Répertoire contenant les thèmes installés pour la bannière avec thème." - -#: ../C/gdm.xml:3633(term) -msgid "GraphicalThemedColor" -msgstr "GraphicalThemedColor" - -#: ../C/gdm.xml:3635(synopsis) -#, no-wrap -msgid "GraphicalThemedColor=#76848F" -msgstr "GraphicalThemedColor=#76848F" - -#: ../C/gdm.xml:3636(para) -msgid "" -"Use this color in the background of the Themed Greeter. This only affects " -"the Themed Greeter." -msgstr "" -"Couleur utilisée pour l'arrière-plan de la bannière avec thème. Cela ne " -"concerne que la bannière avec thème." - -#: ../C/gdm.xml:3644(term) -msgid "InfoMsgFile" -msgstr "InfoMsgFile" - -#: ../C/gdm.xml:3646(synopsis) -#, no-wrap -msgid "InfoMsgFile=/path/to/infofile" -msgstr "InfoMsgFile=/chemin/vers/fichierinfo" - -#: ../C/gdm.xml:3647(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 "" -"Si ce paramètre est présent et que /chemin/vers/fichierinfo correspond à un " -"fichier texte existant et lisible (par ex. <etc>/infomsg.txt), le " -"contenu du fichier est présenté dans une boîte de dialogue modale avant que " -"l'utilisateur puisse se connecter. Cela fonctionne avec les deux types de " -"bannière (standard et avec thème)." - -#: ../C/gdm.xml:3658(term) -msgid "InfoMsgFont" -msgstr "InfoMsgFont" - -#: ../C/gdm.xml:3660(synopsis) -#, no-wrap -msgid "InfoMsgFont=fontspec" -msgstr "InfoMsgFont=police" - -#: ../C/gdm.xml:3661(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 "" -"Si ce paramètre est présent et que InfoMsgFile est renseigné (voir ci-" -"dessus), ce paramètre indique la police à utiliser lors de l'affichage du " -"contenu du fichier texte InfoMsgFile. Par exemple, la valeur « Sans 24 » " -"indique qu'une police Sans serif de 24 points doit être utilisée. Cela " -"fonctionne avec les deux types de bannière (standard et avec thème)." - -#: ../C/gdm.xml:3673(term) -msgid "LocaleFile" -msgstr "LocaleFile" - -#: ../C/gdm.xml:3675(synopsis) -#, no-wrap -msgid "LocaleFile=<etc>/gdm/locale.alias" -msgstr "LocaleFile=<etc>/gdm/locale.alias" - -#: ../C/gdm.xml:3676(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 "" -"Fichier dans un format semblable au format GNU locale, contenant des " -"références à toutes les langues prises en charge sur le système. Le format " -"est décrit ci-dessus ou dans un commentaire à l'intérieur du fichier." - -#: ../C/gdm.xml:3685(term) -msgid "LockPosition" -msgstr "LockPosition" - -#: ../C/gdm.xml:3687(synopsis) -#, no-wrap -msgid "LockPosition=true" -msgstr "LockPosition=true" - -#: ../C/gdm.xml:3688(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 "" -"Si défini à « true » (vrai), la position de la fenêtre de connexion de la " -"bannière GTK+ ne peut être modifiée, même si la barre de titre est visible." - -#: ../C/gdm.xml:3696(term) -msgid "Logo" -msgstr "Logo" - -#: ../C/gdm.xml:3698(synopsis) -#, no-wrap -msgid "Logo=<share>/pixmaps/gnome-logo-large.png" -msgstr "Logo=<share>/pixmaps/gnome-logo-large.png" - -#: ../C/gdm.xml:3699(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 "" -"Fichier image affiché dans la zone du logo. Le fichier doit être dans un " -"format pris en charge par gdk-pixbuf et il doit être accessible en lecture " -"par l'utilisateur GDM. Si aucun fichier n'est indiqué, l'affichage du logo " -"est désactivé. Cela ne concerne que la bannière GTK+." - -#: ../C/gdm.xml:3710(term) -msgid "ChooserButtonLogo" -msgstr "ChooserButtonLogo" - -#: ../C/gdm.xml:3712(synopsis) -#, no-wrap -msgid "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" -msgstr "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" - -#: ../C/gdm.xml:3713(para) -msgid "" -"Image file to display in the file chooser button in <command>gdmsetup</" -"command>. This key is modified by <command>gdmsetup</command> and should not " -"be manually modified by the user. This only affects the Login Window " -"Preferences (<command>gdmsetup</command>)." -msgstr "" -"Fichier image à afficher dans le bouton de sélection de fichier dans " -"<command>gdmsetup</command>. Cette clé est modifiée par <command>gdmsetup</" -"command> et ne devrait pas être modifiée manuellement par un utilisateur. " -"Cela ne concerne que les préférences de la Fenêtre de connexion " -"(<command>gdmsetup</command>)." - -#: ../C/gdm.xml:3724(term) -msgid "MinimalUID" -msgstr "MinimalUID" - -#: ../C/gdm.xml:3726(synopsis) -#, no-wrap -msgid "MinimalUID=100" -msgstr "MinimalUID=100" - -#: ../C/gdm.xml:3727(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 <filename>Include</" -"filename>, <filename>Exclude</filename>, and <filename>IncludeAll</filename>." -msgstr "" -"L'identifiant (UID) minimal que GDM considère comme un identifiant " -"d'utilisateur. Tout utilisateur avec un identifiant plus petit sera exclu du " -"navigateur de figures. Voir aussi les paramètres <filename>Include</" -"filename>, <filename>Exclude</filename> et <filename>IncludeAll</filename>." - -#: ../C/gdm.xml:3738(term) -msgid "PositionX" -msgstr "PositionX" - -#: ../C/gdm.xml:3740(synopsis) -#, no-wrap -msgid "PositionX=200" -msgstr "PositionX=200" - -#: ../C/gdm.xml:3741(para) -msgid "The horizontal position of the login window of the GTK+ Greeter." -msgstr "Position horizontale de la fenêtre de connexion de la bannière GTK+." - -#: ../C/gdm.xml:3749(term) -msgid "PositionY" -msgstr "PositionY" - -#: ../C/gdm.xml:3751(synopsis) -#, no-wrap -msgid "PositionY=100" -msgstr "PositionY=100" - -#: ../C/gdm.xml:3752(para) -msgid "The vertical position of the login window of the GTK+ Greeter." -msgstr "Position verticale de la fenêtre de connexion de la bannière GTK+." - -#: ../C/gdm.xml:3760(term) -msgid "Quiver" -msgstr "Quiver" - -#: ../C/gdm.xml:3762(synopsis) -#, no-wrap -msgid "Quiver=true" -msgstr "Quiver=true" - -#: ../C/gdm.xml:3763(para) -msgid "" -"Controls whether <command>gdmlogin</command> should shake the display when " -"an incorrect username/password is entered. This only affects the GTK+ " -"Greeter." -msgstr "" -"Indique si <command>gdmlogin</command> doit secouer l'affichage lorsqu'un " -"nom d'utilisateur ou un mot de passe incorrect est saisi. Cela ne concerne " -"que la bannière GTK+." - -#: ../C/gdm.xml:3773(term) -msgid "DefaultRemoteWelcome" -msgstr "DefaultRemoteWelcome" - -#: ../C/gdm.xml:3775(synopsis) -#, no-wrap -msgid "DefaultRemoteWelcome=true" -msgstr "DefaultRemoteWelcome=true" - -#: ../C/gdm.xml:3776(para) -msgid "" -"If set to true, the value \"Welcome to %n\" is used for the " -"<filename>RemoteWelcome</filename>. This value is translated into the " -"appropriate language for the user. If set to false, the " -"<filename>RemoteWelcome</filename> 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 "" -"Si défini à « true » (vrai), le texte « Welcome to %n » est utilisé comme " -"message d'accueil distant. Ce texte est traduit dans la langue du système. " -"Si défini à « false » (faux), c'est le texte contenu dans le paramètre " -"<filename>RemoteWelcome</filename> qui est utilisé. Cette chaîne de " -"caractères peut utiliser les mêmes séquences spéciales décrites dans la " -"section « Nœud de texte » du chapitre « Bannière avec thème ». Vous pouvez y " -"découvrir la signification de « %n »." - -#: ../C/gdm.xml:3790(term) -msgid "RemoteWelcome" -msgstr "RemoteWelcome" - -#: ../C/gdm.xml:3792(synopsis) -#, no-wrap -msgid "RemoteWelcome=Welcome to %n" -msgstr "RemoteWelcome=Welcome to %n" - -#: ../C/gdm.xml:3793(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 " -"<filename>Welcome</filename> string. This string can use the same special " -"character sequences as explained in the \"Text Node\" section of the " -"\"Themed Greeter\" chapter. chapter." -msgstr "" -"Indique le texte à afficher à côté du logo dans la bannière des sessions " -"XDMCP distantes. Ce texte est soumis au même processus d'expansion que le " -"texte <filename>Welcome</filename>. Cette chaîne de caractères peut utiliser " -"les mêmes séquences spéciales décrites dans la section « Nœud de texte » du " -"chapitre « Bannière avec thème »." - -#: ../C/gdm.xml:3806(term) -msgid "RunBackgroundProgramAlways" -msgstr "RunBackgroundProgramAlways" - -#: ../C/gdm.xml:3808(synopsis) -#, no-wrap -msgid "RunBackgroundProgramAlways=false" -msgstr "RunBackgroundProgramAlways=false" - -#: ../C/gdm.xml:3809(para) -msgid "" -"If this is true then the background application is run always, otherwise it " -"is only run when the <filename>BackgroundType</filename> is 0 (None) This " -"only affects the GTK+ Greeter." -msgstr "" -"Si défini à « true » (vrai), l'application d'arrière-plan est toujours " -"exécutée, sinon elle n'est exécutée que lorsque le paramètre " -"<filename>BackgroundType</filename> est à 0 (aucun). Cela ne concerne que la " -"bannière GTK+." - -#: ../C/gdm.xml:3819(term) -msgid "SetPosition" -msgstr "SetPosition" - -#: ../C/gdm.xml:3821(synopsis) -#, no-wrap -msgid "SetPosition=true" -msgstr "SetPosition=true" - -#: ../C/gdm.xml:3822(para) -msgid "" -"If true the position of the login window of the GTK+ Greeter is determined " -"by <filename>PositionX</filename> / <filename>PositionY</filename>." -msgstr "" -"Si défini à « true » (vrai), la position de la fenêtre de connexion de la " -"bannière GTK+ est déterminée par les paramètres <filename>PositionX</" -"filename> / <filename>PositionY</filename>." - -#: ../C/gdm.xml:3831(term) -msgid "ShowGnomeFailsafeSession" -msgstr "ShowGnomeFailsafeSession" - -#: ../C/gdm.xml:3833(synopsis) -#, no-wrap -msgid "ShowGnomeFailsafeSession=true" -msgstr "ShowGnomeFailsafeSession=true" - -#: ../C/gdm.xml:3834(para) -msgid "Should the greeter show the Gnome Failsafe session in th sessions list." -msgstr "" -"Indique si la bannière affiche la session GNOME de secours dans la liste des " -"sessions." - -#: ../C/gdm.xml:3842(term) -msgid "ShowLastSession" -msgstr "ShowLastSession" - -#: ../C/gdm.xml:3844(synopsis) -#, no-wrap -msgid "ShowLastSession=true" -msgstr "ShowLastSession=true" - -#: ../C/gdm.xml:3845(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 <filename>DefaultSession</filename>) unless " -"then pick something else for this session only. So if this is off, this " -"really circumvents saving of the last session." -msgstr "" -"Indique si la bannière doit afficher la « Dernière » session dans la liste " -"des sessions. Si défini à « false » (faux), GDM est dans le mode dit " -"« switchdesk », utilisé par exemple par Redhat. C'est-à-dire que les " -"utilisateurs ne peuvent pas choisir la session précédente. Ils obtiennent " -"alors la session par défaut (voir <filename>DefaultSession</filename>), sauf " -"dans les cas où ils choisissent explicitement une autre session. Donc, en " -"cas de désactivation, ce paramètre empêche la sauvegarde de la dernière " -"session." - -#: ../C/gdm.xml:3858(term) -msgid "ShowXtermFailsafeSession" -msgstr "ShowXtermFailsafeSession" - -#: ../C/gdm.xml:3860(synopsis) -#, no-wrap -msgid "ShowXtermFailsafeSession=true" -msgstr "ShowXtermFailsafeSession=true" - -#: ../C/gdm.xml:3861(para) -msgid "" -"Should the greeter show the Xterm Failsafe session in the sessions list." -msgstr "" -"Indique si la bannière affiche la session de secours Xterm dans la liste des " -"sessions." - -#: ../C/gdm.xml:3869(term) -msgid "SoundOnLogin" -msgstr "SoundOnLogin" - -#: ../C/gdm.xml:3871(synopsis) -#, no-wrap -msgid "SoundOnLogin=true" -msgstr "SoundOnLogin=true" - -#: ../C/gdm.xml:3872(para) -msgid "" -"If true, the greeter will play a sound or beep when it is ready for a login. " -"See also the <filename>SoundOnLoginFile</filename> key. Supported since " -"2.5.90.0." -msgstr "" -"Si défini à « true » (vrai), la bannière émet un son ou un bip lorsqu'elle " -"est prête pour effectuer une connexion. Voir aussi la clé " -"<filename>SoundOnLoginFile</filename>. Pris en charge depuis la version " -"2.5.90.0." - -#: ../C/gdm.xml:3882(term) -msgid "SoundOnLoginSuccess" -msgstr "SoundOnLoginSuccess" - -#: ../C/gdm.xml:3884(synopsis) -#, no-wrap -msgid "SoundOnLoginSuccess=true" -msgstr "SoundOnLoginSuccess=true" - -#: ../C/gdm.xml:3885(para) -msgid "" -"If true, the greeter will play a sound after a successful login attempt. See " -"also the <filename>SoundOnLoginSuccessFile</filename> key." -msgstr "" -"Si défini à « true » (vrai), la bannière émet un son après une tentative " -"réussie de connexion. Voir aussi la clé <filename>SoundOnLoginSuccessFile</" -"filename>." - -#: ../C/gdm.xml:3894(term) -msgid "SoundOnLoginFailure" -msgstr "SoundOnLoginFailure" - -#: ../C/gdm.xml:3896(synopsis) -#, no-wrap -msgid "SoundOnLoginFailure=true" -msgstr "SoundOnLoginFailure=true" - -#: ../C/gdm.xml:3897(para) -msgid "" -"If true, the greeter will play a sound after a failed login attempt. See " -"also the <filename>SoundOnLoginFailureFile</filename> key." -msgstr "" -"Si défini à « true » (vrai), la bannière émet un son après un échec de " -"connexion. Voir aussi la clé <filename>SoundOnLoginFailureFile</filename>." - -#: ../C/gdm.xml:3906(term) -msgid "SoundOnLoginFile" -msgstr "SoundOnLoginFile" - -#: ../C/gdm.xml:3908(synopsis) -#, no-wrap -msgid "SoundOnLoginFile=/path/to/sound.wav" -msgstr "SoundOnLoginFile=/chemin/vers/son.wav" - -#: ../C/gdm.xml:3909(para) -msgid "" -"The file that will be played using the specified sound application (by " -"default that is <filename>/usr/bin/play</filename>) instead of a beep when " -"the greeter is ready for a login. See also the <filename>SoundOnLogin</" -"filename> key and the <filename>SoundProgram</filename> key. Supported since " -"2.5.90.0." -msgstr "" -"Le fichier son qui sera lu avec l'application audio choisie (par défaut, " -"<filename>/usr/bin/play</filename>), en lieu et place du bip, lorsque la " -"bannière est prête pour effectuer une connexion. Voir aussi les clés " -"<filename>SoundOnLogin</filename> et <filename>SoundProgram</filename>. Pris " -"en charge depuis la version 2.5.90.0." - -#: ../C/gdm.xml:3922(term) -msgid "SoundOnLoginSuccessFile" -msgstr "SoundOnLoginSuccessFile" - -#: ../C/gdm.xml:3924(synopsis) -#, no-wrap -msgid "SoundOnLoginSuccessFile=/path/to/sound.wav" -msgstr "SoundOnLoginSuccessFile=/chemin/vers/son.wav" - -#: ../C/gdm.xml:3925(para) -msgid "" -"The file that will be played using the specified sound application (by " -"default that is <filename>/usr/bin/play</filename>) after a successful login " -"attempt. See also the <filename>SoundOnLoginSuccess</filename> key and the " -"<filename>SoundProgram</filename> key." -msgstr "" -"Le fichier son qui sera lu avec l'application audio choisie (par défaut, " -"<filename>/usr/bin/play</filename>), à la suite d'une connexion réussie. " -"Voir aussi les clés <filename>SoundOnLoginSuccess</filename> et " -"<filename>SoundProgram</filename>." - -#: ../C/gdm.xml:3936(term) -msgid "SoundOnLoginFailureFile" -msgstr "SoundOnLoginFailureFile" - -#: ../C/gdm.xml:3938(synopsis) -#, no-wrap -msgid "SoundOnLoginFailureFile=/path/to/sound.wav" -msgstr "SoundOnLoginFailureFile=/chemin/vers/son.wav" - -#: ../C/gdm.xml:3939(para) -msgid "" -"The file that will be played using the specified sound application (by " -"default that is <filename>/usr/bin/play</filename>) after a failed login " -"attempt. See also the <filename>SoundOnLoginFailure</filename> key and the " -"<filename>SoundProgram</filename> key." -msgstr "" -"Le fichier son qui sera lu avec l'application audio choisie (par défaut, " -"<filename>/usr/bin/play</filename>), à la suite d'un échec de connexion. " -"Voir aussi les clés <filename>SoundOnLoginFailure</filename> et " -"<filename>SoundProgram</filename>." - -#: ../C/gdm.xml:3950(term) -msgid "SystemMenu" -msgstr "SystemMenu" - -#: ../C/gdm.xml:3952(synopsis) -#, no-wrap -msgid "SystemMenu=true" -msgstr "SystemMenu=true" - -#: ../C/gdm.xml:3953(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 attached displays. It would not be safe or " -"even desirable on remote logins, so you do not have to worry about remote " -"users having these privileges." -msgstr "" -"Active ou désactive le menu Actions (qui était appelé menu Système). Si " -"défini à « false » (faux), l'une des actions sera disponible quelque part. " -"Ces actions comprennent Éteindre, Redémarrer, Configurer, Sélecteur XDMCP, " -"etc. Elle peuvent toutes être désactivées individuellement. Éteindre, " -"Redémarrer et Mettre en veille peuvent être simplement désactivées en " -"plaçant une valeur vide dans la clé correspondante. Il est à noter que le " -"menu Actions n'est affiché que pour les affichages liés, car il ne serait ni " -"sûr, ni souhaitable pour les connexions distantes. Vous n'avez donc pas à " -"vous préoccuper des privilèges obtenus par des utilisateurs distants." - -#: ../C/gdm.xml:3965(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 "" -"Il est à noter que si ce paramètre est défini à « false » (faux), aucune " -"action n'est disponible, même si une bannière graphique les affiche par " -"erreur. Il peut aussi arriver parfois qu'un thème graphique n'affiche pas " -"toutes les actions disponibles sous forme de boutons ; il s'agit alors " -"d'appuyer sur F10 pour voir le menu." - -#: ../C/gdm.xml:3976(term) -msgid "TitleBar" -msgstr "TitleBar" - -#: ../C/gdm.xml:3978(synopsis) -#, no-wrap -msgid "TitleBar=true" -msgstr "TitleBar=true" - -#: ../C/gdm.xml:3979(para) -msgid "" -"Display the title bar in the greeter. This only affects the GTK+ Greeter." -msgstr "" -"Affiche la barre de titre dans la bannière. Cela ne concerne que la bannière " -"GTK+." - -#: ../C/gdm.xml:3987(term) -msgid "Use24Clock" -msgstr "Use24Clock" - -#: ../C/gdm.xml:3989(synopsis) -#, no-wrap -msgid "Use24Clock=auto" -msgstr "Use24Clock=auto" - -#: ../C/gdm.xml:3990(para) -msgid "" -"Select the use of 24 hour clock. Some locales do not support 12 hour format " -"(like Finnish, that is <filename>fi_FI</filename>), and in those locales " -"this setting has no effect at all." -msgstr "" -"Détermine l'affichage de l'horloge en mode 24 heures. Certains paramètres " -"locaux ne prennent pas en charge le mode 12 heures (comme le finnois, c'est-" -"à-dire <filename>fi_FI</filename>) ; dans ce cas, ce paramètre n'a aucun " -"effet." - -#: ../C/gdm.xml:3996(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 "" -"Les valeurs possibles sont « auto » (par défaut), « true » et « false ». Si " -"ce paramètre est vide ou défini à « auto », le format d'heure est calqué sur " -"celui des paramètres locaux. Ceux-ci sont basés sur la langue en cours, ils " -"sont donc modifiés par la définition des variables d'environnement LANGUAGE " -"(extension GNU), LANG, LC_MESSAGES ou LC_ALL dans l'environnement " -"d'exécution de GDM. La priorité entre les variables d'environnement " -"mentionnées ci-dessus peut se trouver dans le manuel de la bibliothèque C du " -"système." - -#: ../C/gdm.xml:4011(term) -msgid "UseCirclesInEntry" -msgstr "UseCirclesInEntry" - -#: ../C/gdm.xml:4013(synopsis) -#, no-wrap -msgid "UseCirclesInEntry=false" -msgstr "UseCirclesInEntry=false" - -#: ../C/gdm.xml:4014(para) -msgid "" -"Use circles instead of asterisks in the password entry. This may not work " -"with all fonts however." -msgstr "" -"Utilise des puces à la place d'astérisques dans la zone de saisie du mot de " -"passe. Cela ne fonctionne cependant pas avec toutes les polices." - -#: ../C/gdm.xml:4022(term) -msgid "UseInvisibleInEntry" -msgstr "UseInvisibleInEntry" - -#: ../C/gdm.xml:4024(synopsis) -#, no-wrap -msgid "UseInvisibleInEntry=false" -msgstr "UseInvisibleInEntry=false" - -#: ../C/gdm.xml:4025(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 " -"<filename>UseCirclesInEntry</filename> option." -msgstr "" -"N'affiche aucun retour visuel dans la zone de saisie du mot de passe. C'est " -"le comportement standard dans la console et dans xdm. La définition de ce " -"paramètre annule l'option <filename>UseCirclesInEntry</filename>." - -#: ../C/gdm.xml:4035(term) -msgid "DefaultWelcome" -msgstr "DefaultWelcome" - -#: ../C/gdm.xml:4037(synopsis) -#, no-wrap -msgid "DefaultWelcome=true" -msgstr "DefaultWelcome=true" - -#: ../C/gdm.xml:4038(para) -msgid "" -"If set to true, the value \"Welcome\" is used for the <filename>Welcome</" -"filename>. This value is translated into the appropriate language for the " -"user. If set to false, the <filename>Welcome</filename> setting is used." -msgstr "" -"Si défini à « true » (vrai), la valeur « Welcome » est utilisée pour le " -"paramètre <filename>Welcome</filename>. Cette valeur est traduite dans la " -"langue correspondant au système. Si défini à « false » (faux), c'est la " -"valeur du paramètre <filename>Welcome</filename> qui est utilisée." - -#: ../C/gdm.xml:4048(term) -msgid "Welcome" -msgstr "Welcome" - -#: ../C/gdm.xml:4050(synopsis) -#, no-wrap -msgid "Welcome=Welcome" -msgstr "Welcome=Welcome" - -#: ../C/gdm.xml:4051(para) -msgid "" -"Controls which text to display next to the logo image in the standard " -"greeter. The following control chars are supported:" -msgstr "" -"Détermine le texte affiché à côté du logo dans la bannière standard. Les " -"caractères de contrôle suivants sont pris en charge :" - -#: ../C/gdm.xml:4060(para) -msgid "%d — display's hostname" -msgstr "%d — affiche le nom d'hôte" - -#: ../C/gdm.xml:4064(para) -msgid "%h — Fully qualified hostname" -msgstr "%h — nom d'hôte complet" - -#: ../C/gdm.xml:4068(para) -msgid "%m — machine (processor type)" -msgstr "%m — machine (type de processeur)" - -#: ../C/gdm.xml:4072(para) -msgid "%n — Nodename (i.e. hostname without .domain)" -msgstr "%n — nom de nœud (c.-à-d. nom d'hôte sans .domaine)" - -#: ../C/gdm.xml:4076(para) -msgid "%r — release (OS version)" -msgstr "%r — version (système d'exploitation)" - -#: ../C/gdm.xml:4080(para) -msgid "%s — sysname (i.e. OS)" -msgstr "%s — nom du système (système d'exploitation)" - -#: ../C/gdm.xml:4084(para) -msgid "" -"This string is only used for attached displays. For remote XDMCP displays we " -"use <filename>RemoteWelcome</filename>." -msgstr "" -"Ce texte n'est utilisé que pour les affichages liés. Pour les connexions " -"XDMCP distantes, c'est <filename>RemoteWelcome</filename> qui est utilisé." - -#: ../C/gdm.xml:4089(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 "" -"Dans la bannière avec thème, l'emplacement de ce texte dépend du thème. Si " -"le thème n'utilise nulle part le message de bienvenue prédéfini, ce texte ne " -"sera pas affiché du tout." - -#: ../C/gdm.xml:4099(term) -msgid "XineramaScreen" -msgstr "XineramaScreen" - -#: ../C/gdm.xml:4101(synopsis) -#, no-wrap -msgid "XineramaScreen=0" -msgstr "XineramaScreen=0" - -#: ../C/gdm.xml:4102(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 "" -"Si l'extension Xinerama est active, la fenêtre de connexion sera au centre " -"de cet écran physique (0 pour le premier écran, 1 pour le deuxième, etc.)." - -#: ../C/gdm.xml:4113(title) -msgid "XDCMP Chooser Options" -msgstr "Options du sélecteur XDMCP" - -#: ../C/gdm.xml:4116(title) -msgid "[chooser]" -msgstr "[chooser]" - -#: ../C/gdm.xml:4119(term) -msgid "AllowAdd" -msgstr "AllowAdd" - -#: ../C/gdm.xml:4121(synopsis) -#, no-wrap -msgid "AllowAdd=true" -msgstr "AllowAdd=true" - -#: ../C/gdm.xml:4122(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 "" -"Si défini à « true » (vrai), permet à l'utilisateur d'ajouter arbitrairement " -"des hôtes au sélecteur. De cette façon, l'utilisateur peut se connecter avec " -"le sélecteur à n'importe quel hôte répondant aux requêtes XDMCP." - -#: ../C/gdm.xml:4131(term) -msgid "Broadcast" -msgstr "Broadcast" - -#: ../C/gdm.xml:4133(synopsis) -#, no-wrap -msgid "Broadcast=true" -msgstr "Broadcast=true" - -#: ../C/gdm.xml:4134(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 " -"<filename>Hosts</filename> key." -msgstr "" -"Si défini à « true » (vrai), le sélecteur diffuse une requête sur le réseau " -"local et répertorie les réponses. De cette façon, le sélecteur affiche " -"toujours tous les gestionnaires disponibles sur le réseau. Si vous devez " -"ajouter certains hôtes en dehors du réseau local ou si vous ne souhaitez pas " -"diffuser les requêtes (broadcast), vous pouvez faire une liste d'hôtes " -"explicite dans la clé <filename>Hosts</filename>." - -#: ../C/gdm.xml:4146(term) -msgid "Multicast" -msgstr "Multicast" - -#: ../C/gdm.xml:4148(synopsis) -#, no-wrap -msgid "Multicast=true" -msgstr "Multicast=true" - -#: ../C/gdm.xml:4149(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 <filename>Hosts </filename> key. The host will respond if it is " -"listening to XDMCP requests and IPv6 is enabled there." -msgstr "" -"Si défini à « true » (vrai) et que IPv6 est actif, le sélecteur envoie une " -"requête en multidiffusion (multicast) sur le réseau local et répertorie les " -"réponses des hôtes ayant rejoint le groupe multidiffusion. Si vous ne " -"souhaitez pas envoyer en multidiffusion, vous pouvez indiquer des adresses " -"IPv6 dans la clé <filename>Hosts </filename>. L'hôte répond s'il écoute les " -"requêtes XDMCP et si IPv6 est actif sur son réseau." - -#: ../C/gdm.xml:4161(term) -msgid "MulticastAddr" -msgstr "MulticastAddr" - -#: ../C/gdm.xml:4163(synopsis) -#, no-wrap -msgid "MulticastAddr=ff02::1" -msgstr "MulticastAddr=ff02::1" - -#: ../C/gdm.xml:4164(para) -msgid "This is the Link-local Multicast address and is hardcoded here." -msgstr "C'est l'adresse de multidiffusion de lien local, codée ici en dur." - -#: ../C/gdm.xml:4171(term) -msgid "DefaultHostImage" -msgstr "DefaultHostImage" - -#: ../C/gdm.xml:4173(synopsis) -#, no-wrap -msgid "DefaultHostImage=<share>/pixmaps/nohost.png" -msgstr "DefaultHostImage=<share>/pixmaps/nohost.png" - -#: ../C/gdm.xml:4174(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 "" -"Nom de fichier de l'icône d'hôte par défaut. Cette image est affichée " -"lorsqu'aucune icône n'est précisée pour un hôte spécifique. Le fichier doit " -"être dans un format pris en charge par gdk-pixbuf et il doit être accessible " -"en lecture par l'utilisateur GDM." - -#: ../C/gdm.xml:4184(term) -msgid "HostImageDir" -msgstr "HostImageDir" - -#: ../C/gdm.xml:4186(synopsis) -#, no-wrap -msgid "HostImageDir=<share>/hosts" -msgstr "HostImageDir=<share>/hosts" - -#: ../C/gdm.xml:4187(para) -msgid "" -"Repository for host icon files. The sysadmin can place icons for remote " -"hosts here and they will appear in <filename>gdmchooser</filename>." -msgstr "" -"Répertoire de fichiers d'icônes d'hôtes. L'administrateur système peut y " -"placer des icônes pour les hôtes distants et elles apparaîtront dans " -"<filename>gdmchooser</filename>." - -#: ../C/gdm.xml:4193(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 "" -"Le nom de fichier doit correspondre au nom complet (FQDN) de l'hôte. Les " -"icônes doivent être dans un format pris en charge par gdk-pixbuf et elles " -"doivent être accessibles en lecture par l'utilisateur GDM." - -#: ../C/gdm.xml:4203(term) -msgid "Hosts" -msgstr "Hosts" - -#: ../C/gdm.xml:4205(synopsis) -#, no-wrap -msgid "Hosts=host1,host2" -msgstr "Hosts=hôte1,hôte2" - -#: ../C/gdm.xml:4206(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 " -"<filename>Broadcast</filename> 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 "" -"Les hôtes à présenter dans le sélecteur. Le sélecteur ne les affiche que " -"s'ils répondent. Ces hôtes s'ajoutent à ceux répertoriés par la diffusion " -"(si <filename>Broadcast</filename> est défini), ce qui fait qu'il n'est pas " -"nécessaire d'indiquer les hôtes du réseau local. Ceci est utile si votre " -"configuration réseau ne permet pas à tous les hôtes d'être accessibles par " -"un paquet de diffusion (broadcast)." - -#: ../C/gdm.xml:4218(term) -msgid "ScanTime" -msgstr "ScanTime" - -#: ../C/gdm.xml:4220(synopsis) -#, no-wrap -msgid "ScanTime=4" -msgstr "ScanTime=4" - -#: ../C/gdm.xml:4221(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 "" -"Indique pendant combien de secondes le sélecteur doit attendre des réponses " -"de sa requête BROADCAST_QUERY. Ceci correspond en fait à l'intervalle dans " -"lequel les réponses devraient arriver. Les hôtes sont tout de même ajoutés à " -"la liste s'ils répondent après ce délai." - -#: ../C/gdm.xml:4233(title) -msgid "Debug Configuration" -msgstr "Configuration de débogage" - -#: ../C/gdm.xml:4236(title) -msgid "[debug]" -msgstr "[debug]" - -#: ../C/gdm.xml:4242(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 "" -"Si défini à « true » (vrai), envoie la sortie de débogage dans le syslog. " -"Cela peut être utile pour analyser des problèmes avec GDM. Cette sortie a " -"tendance à produire beaucoup de messages, elle ne devrait donc pas être " -"activée de manière générale." - -#: ../C/gdm.xml:4252(term) -msgid "Gestures" -msgstr "Gestures" - -#: ../C/gdm.xml:4254(synopsis) -#, no-wrap -msgid "Gestures=false" -msgstr "Gestures=false" - -#: ../C/gdm.xml:4255(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 "" -"Si défini à « true » (vrai), envoie la sortie de débogage concernant la " -"détection de mouvements pour l'accessibilité dans le syslog. Cela peut être " -"utile pour analyser des problèmes liés à cette fonctionnalité. Cette sortie " -"a tendance à produire beaucoup de messages, elle ne devrait donc pas être " -"activée de manière générale." - -#: ../C/gdm.xml:4268(title) -msgid "Custom Commands" -msgstr "Commandes personnalisées" - -#: ../C/gdm.xml:4270(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 "" -"Vous pouvez créer jusqu'à 10 commandes différentes. Les espaces entre les " -"numéros de commandes sont autorisés, et leur position relative dans la " -"section et les unes par rapport aux autres n'est pas importante tant " -"qu'elles respectent l'intervalle autorisé de [0-9]." - -#: ../C/gdm.xml:4279(title) -msgid "[customcommand]" -msgstr "[customcommand]" - -#: ../C/gdm.xml:4282(term) -msgid "CustomCommand[0-9]" -msgstr "CustomCommand[0-9]" - -#: ../C/gdm.xml:4284(synopsis) -#, no-wrap -msgid "CustomCommand[0-9]=" -msgstr "CustomCommand[0-9]=" - -#: ../C/gdm.xml:4285(para) -msgid "" -"Full path and arguments to command to be executed when user selects " -"<filename>n-th</filename> \"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 <filename>CustomCommand</filename> suffix and " -"can be an integer between 0 and 9." -msgstr "" -"Chemin complet et arguments de la commande à exécuter lorsque l'utilisateur " -"sélectionne la nième commande personnalisée dans le menu Actions. Il peut y " -"avoir plusieurs commandes séparées par des « ; ». Si la valeur est vide ou " -"manquante, la commande personnalisée n'est pas disponible. Par défaut, cette " -"valeur n'est pas activée ; pour activer les « Commandes personnalisées », il " -"faut donc placer une valeur non vide. [0-9] représente le suffixe de " -"<filename>CustomCommand</filename> et peut être un nombre entier entre 0 et " -"9 y compris." - -#: ../C/gdm.xml:4300(term) -msgid "CustomCommandIsPersistent[0-9]" -msgstr "CustomCommandIsPersistent[0-9]" - -#: ../C/gdm.xml:4302(synopsis) -#, no-wrap -msgid "CustomCommandIsPersistent[0-9]=" -msgstr "CustomCommandIsPersistent[0-9]=" - -#: ../C/gdm.xml:4303(para) -msgid "" -"Specifies if <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is " -"defined. [0-9] represents <filename>CustomCommand</filename> suffix and can " -"be an integer between 0 and 9." -msgstr "" -"Indique si la nième commande personnalisée apparaît en dehors du " -"gestionnaire de connexions, par exemple sur le bureau par les boîtes de " -"dialogue de déconnexion et d'extinction. Si rien n'est spécifié, la valeur " -"par défaut est « false » (faux). Cette option n'est valide que si la " -"commande personnalisée (<filename>CustomCommand</filename>) correspondante " -"est définie. [0-9] représente le suffixe de <filename>CustomCommand</" -"filename> et peut être un nombre entier entre 0 et 9 y compris." - -#: ../C/gdm.xml:4317(term) -msgid "CustomCommandLabel[0-9]" -msgstr "CustomCommandLabel[0-9]" - -#: ../C/gdm.xml:4319(synopsis) -#, no-wrap -msgid "CustomCommandLabel[0-9]=" -msgstr "CustomCommandLabel[0-9]=" - -#: ../C/gdm.xml:4320(para) -msgid "" -"Specifies the stock label that will be displayed on the <filename>n-th</" -"filename> \"Custom Command\" buttons and menu items. If not specified the " -"default value is \"Custom_[0-9]\". This option is only valid if " -"corresponding <filename>CustomCommand</filename> is defined. [0-9] " -"represents <filename>CustomCommand</filename> suffix and can be an integer " -"between 0 and 9. This option can't contain any semicolon characters (i.e. \";" -"\")." -msgstr "" -"Indique le texte prédéfini affiché sur le bouton ou l'élément de menu " -"correspondant à la nième commande personnalisée. Si rien n'est spécifié, la " -"valeur par défaut est « Custom_[0-9] ». Cette option n'est valide que si la " -"commande personnalisée (<filename>CustomCommand</filename>) correspondante " -"est définie. [0-9] représente le suffixe de <filename>CustomCommand</" -"filename> et peut être un nombre entier entre 0 et 9 y compris. Cette option " -"ne peut pas contenir des points-virgules (« ; »)." - -#: ../C/gdm.xml:4334(term) -msgid "CustomCommandLRLabel[0-9]" -msgstr "CustomCommandLRLabel[0-9]" - -#: ../C/gdm.xml:4336(synopsis) -#, no-wrap -msgid "CustomCommandLRLabel[0-9]=" -msgstr "CustomCommandLRLabel[0-9]=" - -#: ../C/gdm.xml:4337(para) -msgid "" -"Specifies the stock label that will be displayed on the <filename>n-th</" -"filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] " -"represents <filename>CustomCommand</filename> suffix and can be an integer " -"between 0 and 9." -msgstr "" -"Indique le texte prédéfini affiché sur l'élément de liste ou le bouton radio " -"correspondant à la nième commande personnalisée. Si rien n'est spécifié, la " -"valeur par défaut est « Execute custom command _[0-9] ». Cette option n'est " -"valide que si la commande personnalisée (<filename>CustomCommand</filename>) " -"correspondante est définie. [0-9] représente le suffixe de " -"<filename>CustomCommand</filename> et peut être un nombre entier entre 0 et " -"9 y compris." - -#: ../C/gdm.xml:4351(term) -msgid "CustomCommandNoRestart[0-9]" -msgstr "CustomCommandNoRestart[0-9]" - -#: ../C/gdm.xml:4353(synopsis) -#, no-wrap -msgid "CustomCommandNoRestart[0-9]=" -msgstr "CustomCommandNoRestart[0-9]=" - -#: ../C/gdm.xml:4354(para) -msgid "" -"Specifies if gdm will be stopped/restarted once <filename>n-th</filename> " -"\"Custom Command\" has been executed. If not specified the default value is " -"\"false\". This option is only valid if corresponding " -"<filename>CustomCommand</filename> is defined. [0-9] represents " -"<filename>CustomCommand</filename> suffix and can be an integer between 0 " -"and 9. In addition when corresponding <filename>CustomCommandIsPersistent</" -"filename> is set to true, setting CustomCommandNoRestart to false will place " -"corresponding <filename>CustomCommand</filename> in the Shut Down dialog set " -"of actions, setting it to true will place corresponding " -"<filename>CustomCommand</filename> in the Log Out dialog set of actions." -msgstr "" -"Indique si GDM est arrêté et redémarré après que la nième commande " -"personnalisée ait été exécutée. Si rien n'est spécifié, la valeur par défaut " -"est « false ». Cette option n'est valide que si la commande personnalisée " -"(<filename>CustomCommand</filename>) correspondante est définie. [0-9] " -"représente le suffixe de <filename>CustomCommand</filename> et peut être un " -"nombre entier entre 0 et 9 y compris. De plus, lorsque le paramètre " -"<filename>CustomCommandIsPersistent</filename> correspondant est défini à " -"« true » (vrai), la définition de CustomCommandNoRestart à « false » place " -"la commande personnalisée correspondante dans les actions possibles de la " -"boîte de dialogue d'extinction, et la définition de ce même paramètre à " -"« true » place la commande personnalisée correspondante dans les actions " -"possibles de la boîte de dialogue de déconnexion." - -#: ../C/gdm.xml:4374(term) -msgid "CustomCommandText[0-9]" -msgstr "CustomCommandText[0-9]" - -#: ../C/gdm.xml:4376(synopsis) -#, no-wrap -msgid "CustomCommandText[0-9]=" -msgstr "CustomCommandText[0-9]=" - -#: ../C/gdm.xml:4377(para) -msgid "" -"Specifies the message that will be displayed on the warning dialog box once " -"<filename>n-th</filename> \"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 " -"<filename>CustomCommand</filename> is defined. [0-9] represents " -"<filename>CustomCommand</filename> suffix and can be an integer between 0 " -"and 9." -msgstr "" -"Indique le message qui apparaît dans la boîte de dialogue d'avertissement de " -"la nième commande personnalisée lorsque celle-ci est lancée par un bouton, " -"un élément de menu, un bouton radio ou un élément de liste. Si rien n'est " -"spécifié, la valeur par défaut est « Are you sure? ». Cette option n'est " -"valide que si la commande personnalisée (<filename>CustomCommand</filename>) " -"correspondante est définie. [0-9] représente le suffixe de " -"<filename>CustomCommand</filename> et peut être un nombre entier entre 0 et " -"9 y compris." - -#: ../C/gdm.xml:4391(term) -msgid "CustomCommandTooltip[0-9]" -msgstr "CustomCommandTooltip[0-9]" - -#: ../C/gdm.xml:4393(synopsis) -#, no-wrap -msgid "CustomCommandTooltip[0-9]=" -msgstr "CustomCommandTooltip[0-9]=" - -#: ../C/gdm.xml:4394(para) -msgid "" -"Specifies the message that will be displayed on tooltips for <filename>n-th</" -"filename> \"Custom Command\" entries. If not specified the default value is " -"\"Execute custom command [0-9]\". This option is only valid if corresponding " -"<filename>CustomCommand</filename> is defined. [0-9] represents " -"<filename>CustomCommand</filename> suffix and can be an integer between 0 " -"and 9." -msgstr "" -"Indique le message qui apparaît dans l'infobulle de la nième commande " -"personnalisée. Si rien n'est spécifié, la valeur par défaut est « Execute " -"custom command [0-9] ». Cette option n'est valide que si la commande " -"personnalisée (<filename>CustomCommand</filename>) correspondante est " -"définie. [0-9] représente le suffixe de <filename>CustomCommand</filename> " -"et peut être un nombre entier entre 0 et 9 y compris." - -#: ../C/gdm.xml:4409(title) -msgid "X Server Definitions" -msgstr "Définitions du serveur X" - -#: ../C/gdm.xml:4411(para) -msgid "" -"GDM needs to be provided with information about each X servers that will be " -"used. You can have as many different definitions as you wish, each " -"identified with a unique name. The name <filename>Standard</filename> is " -"required. If you do not specify this server, GDM will assume default values " -"for a 'Standard' server and the path given by <filename>daemon/" -"StandardXServer</filename>. <filename>Standard</filename> is used as the " -"default, in situations when no other server has been defined." -msgstr "" -"GDM doit recevoir des informations sur chaque serveur X qui sera utilisé. " -"Vous pouvez avoir autant de définitions que souhaité, chacune étant " -"identifiée par un nom unique. Le nom <filename>Standard</filename> est " -"obligatoire. Si vous ne définissez pas ce serveur, GDM prend les valeurs par " -"défaut d'un serveur « Standard » et le chemin donné par <filename>daemon/" -"StandardXServer</filename>. <filename>Standard</filename> est utilisé comme " -"valeur par défaut, dans les cas où aucun autre serveur n'a été défini." - -#: ../C/gdm.xml:4422(para) -msgid "" -"Servers are defined by sections named <filename>server-</filename> 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, <filename>server-</" -"filename> sections in the <filename><etc>/gdm/custom.conf</filename> " -"file override values in the <filename><share>/gdm/defaults.conf</" -"filename> file. In other words, if a <filename>server-Standard</filename> " -"section is defined in <filename><etc>/gdm/custom.conf</filename>, then " -"that will be used and the section in the <filename><share>/gdm/" -"defaults.conf</filename> file will be ignored." -msgstr "" -"Les serveurs sont définis par des sections nommées <filename>server-</" -"filename> suivi par l'identifiant du serveur. Cela devrait être un texte " -"purement ASCII, sans espace. Le programme de configuration graphique permet " -"de modifier les serveurs définis dans les fichiers de configuration de GDM, " -"mais ne permet actuellement pas d'ajouter ou de supprimer des définitions de " -"serveur. Comme les options de configuration normales, les sections " -"<filename>server-</filename> du fichier <filename><etc>/gdm/custom." -"conf</filename> ont la priorité sur les valeurs du fichier <filename><" -"share>/gdm/defaults.conf</filename>. Autrement dit, si une section " -"<filename>server-Standard</filename> est définie dans le fichier " -"<filename><etc>/gdm/custom.conf</filename>, ce sont ces informations " -"qui seront utilisées, et si une section semblable existe dans le fichier " -"<filename><share>/gdm/defaults.conf</filename>, elle sera ignorée." - -#: ../C/gdm.xml:4440(title) -msgid "[server-Standard]" -msgstr "[server-Standard]" - -#: ../C/gdm.xml:4443(term) -msgid "name" -msgstr "name" - -#: ../C/gdm.xml:4445(synopsis) -#, no-wrap -msgid "name=Standard server" -msgstr "name=Standard server" - -#: ../C/gdm.xml:4446(para) -msgid "The name that will be displayed to the user." -msgstr "Le nom que l'utilisateur voit apparaître." - -#: ../C/gdm.xml:4453(term) -msgid "command" -msgstr "command" - -#: ../C/gdm.xml:4455(synopsis) -#, no-wrap -msgid "command=/path/to/X" -msgstr "command=/chemin/vers/X" - -#: ../C/gdm.xml:4456(para) -msgid "" -"The command to execute, with full path to the binary of the X server, and " -"any extra arguments needed. Normally it is not necessary to add a <filename>-" -"nolisten tcp</filename> argument since the addition of this argument is " -"controlled by the <filename>DisallowTCP</filename> GDM configuration option." -msgstr "" -"La commande à exécuter, avec le chemin complet vers le binaire du serveur X " -"et tout argument supplémentaire requis. En principe, il n'est pas nécessaire " -"d'ajouter un argument <filename>-nolisten tcp</filename>, car l'ajout de cet " -"argument est contrôlé par l'option de configuration GDM " -"<filename>DisallowTCP</filename>." - -#: ../C/gdm.xml:4467(term) -msgid "flexible" -msgstr "flexible" - -#: ../C/gdm.xml:4469(synopsis) -#, no-wrap -msgid "flexible=true" -msgstr "flexible=true" - -#: ../C/gdm.xml:4470(para) -msgid "" -"Indicates if this server is available as a choice when a user wishes to run " -"a flexible, on demand server." -msgstr "" -"Indique si ce serveur est un choix possible lorsque l'utilisateur souhaite " -"lancer un serveur flexible, à la demande." - -#: ../C/gdm.xml:4478(term) -msgid "handled" -msgstr "handled" - -#: ../C/gdm.xml:4480(synopsis) -#, no-wrap -msgid "handled=true" -msgstr "handled=true" - -#: ../C/gdm.xml:4481(para) -msgid "" -"Indicates that GDM should run the login window on this server and allow a " -"user to log in. If set to false, then GDM will just run this server and wait " -"for it to terminate. This can be useful to run an X terminal using GDM. When " -"this is done you should normally also add <filename>-terminate</filename> to " -"the command line of the server to make the server terminate after each " -"session. Otherwise the control of the slave will never come back to GDM and, " -"for example, soft restarts won't work. This is because GDM assumes there is " -"a login in progress for the entire time this server is active." -msgstr "" -"Indique que GDM devrait lancer la fenêtre de connexion sur ce serveur, et " -"permettre à un utilisateur de s'y connecter. Si défini à « false » (faux), " -"GDM lance simplement le serveur et attend qu'il se termine. Ceci peut être " -"utile pour exécuter un terminal X avec GDM. Dans cette situation, vous " -"devriez normalement aussi ajouter <filename>-terminate</filename> à la ligne " -"de commande du serveur, afin que celui-ci se ferme après chaque session. " -"Sinon, le contrôle de l'esclave ne revient jamais à GDM et, par exemple, le " -"redémarrage logiciel ne fonctionnera pas. Cela est dû au fait que GDM pense " -"qu'une connexion est en cours aussi longtemps que le serveur est actif." - -#: ../C/gdm.xml:4497(term) -msgid "chooser" -msgstr "chooser" - -#: ../C/gdm.xml:4499(synopsis) -#, no-wrap -msgid "chooser=false" -msgstr "chooser=false" - -#: ../C/gdm.xml:4500(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 "" -"Indique que GDM doit lancer un sélecteur dans cette fenêtre à la place d'une " -"fenêtre de connexion, et permettre à l'utilisateur de choisir le serveur " -"auquel il souhaite se connecter." - -#: ../C/gdm.xml:4509(term) -msgid "priority" -msgstr "priority" - -#: ../C/gdm.xml:4511(synopsis) -#, no-wrap -msgid "priority=0" -msgstr "priority=0" - -#: ../C/gdm.xml:4512(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 "" -"Indique que le serveur X doit être démarré avec une priorité de processus " -"différente. Toute valeur entière acceptée par la fonction de bibliothèque C " -"setpriority est valable (normalement entre -20 et 20), 0 étant la valeur par " -"défaut. Pour les applications très interactives, -5 produit une bonne " -"réactivité. La valeur par défaut est 0, et la fonction setpriority n'est pas " -"appelée si la valeur reste à 0." - -#: ../C/gdm.xml:4527(title) -msgid "Attached DISPLAY Configuration" -msgstr "Configuration des affichages liés" - -#: ../C/gdm.xml:4529(para) -msgid "" -"The attached (also known as local or 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 attached " -"displays that are managed as you wish. Typically each display is associated " -"with a real display. On a typical single-display machine this section would " -"only contain one key <filename>0</filename> that corresponds to DISPLAY " -"<filename>:0</filename>." -msgstr "" -"La configuration d'affichage lié (aussi appelé local ou statique) indique " -"quels sont les affichages qui doivent toujours être gérés par GDM. Par " -"exemple, GDM redémarre le serveur X de l'affichage s'il meurt. Il peut y " -"avoir autant d'affichages liés gérés par GDM que souhaité. En principe, " -"chaque affichage est associé à un affichage réel. Sur un ordinateur " -"classique doté d'un seul écran, cette section ne contient qu'une clé " -"<filename>0</filename> correspondant à l'affichage (DISPLAY) <filename>:0</" -"filename>." - -#: ../C/gdm.xml:4540(para) -msgid "" -"The GUI configuration program allows users to edit the attached display " -"configuration defined in the GDM configuration files and allows the user to " -"add or delete entries. Like normal configuration options, the <filename>" -"[servers]</filename> section in the <filename><etc>/gdm/custom.conf</" -"filename> file overrides values in the <filename><share>/gdm/defaults." -"conf</filename> file." -msgstr "" -"Le programme de configuration graphique permet aux utilisateurs d'éditer la " -"configuration d'affichage lié définie dans les fichiers de configuration GDM " -"et d'ajouter ou de supprimer des entrées. Comme pour les autres options de " -"configuration, la section <filename>[servers]</filename> du fichier " -"<filename><etc>/gdm/custom.conf</filename> a la priorité sur les " -"valeurs du fichier filename><share>/gdm/defaults.conf</filename>." - -#: ../C/gdm.xml:4551(title) -msgid "[servers]" -msgstr "[servers]" - -#: ../C/gdm.xml:4554(term) -msgid "<display number>" -msgstr "<numéro d'affichage>" - -#: ../C/gdm.xml:4556(synopsis) -#, no-wrap -msgid "0=Standard [device=/dev/foo]" -msgstr "0=Standard [device=/dev/foo]" - -#: ../C/gdm.xml:4558(para) -msgid "" -"The key cooresponds to the DISPLAY to be managed, so that key <filename>0</" -"filename> cooresponds to DISPLAY <filename>:0</filename>. On a multi-display " -"machine you can configure GDM to manage a login program on other displays by " -"adding additional keys. For example, adding key <filename>1</filename> would " -"cause GDM to manage DISPLAY <filename>:1</filename>." -msgstr "" -"Cette clé correspond à l'affichage à gérer, la clé <filename>0</filename> " -"correspondant à l'affichage <filename>:0</filename>. Sur une machine à " -"plusieurs écrans, vous pouvez configurer GDM pour qu'il gère un programme de " -"connexion sur d'autres affichages en ajoutant des clés supplémentaires. Par " -"exemple, l'ajout de la clé <filename>1</filename> informe GDM qu'il doit " -"gérer l'affichage <filename>:1</filename>." - -#: ../C/gdm.xml:4568(para) -msgid "" -"The first word of the value corresponds to a X server definition in the \"X " -"Server Definitions\" section of the configuration file. For example, the " -"following entry means that DISPLAY <filename>:0</filename> will start an X " -"server as defined in the <filename>[server-Standard]</filename> section:" -msgstr "" -"Le premier mot de la valeur correspond à une définition de serveur X dans la " -"section « Définitions de serveurs X » du fichier de configuration. Par " -"exemple, les lignes ci-après signifient que l'affichage <filename>:0</" -"filename> va démarrer un serveur X tel que défini dans la section <filename>" -"[server-Standard]</filename> :" - -#: ../C/gdm.xml:4577(screen) -#, no-wrap -msgid "" -"\n" -"[servers]\n" -"0=Standard\n" -msgstr "" -"\n" -"[servers]\n" -"0=Standard\n" - -#: ../C/gdm.xml:4582(para) -msgid "" -"The first word of the value can also be set to the string \"inactive\" to " -"indicate that this DISPLAY should not be 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 "" -"Le premier mot de la valeur peut aussi être le texte « inactive » pour " -"indiquer que cet affichage ne doit pas être géré. Cela peut être utilisé " -"dans le fichier de configuration personnalisé de GDM pour désactiver un " -"affichage défini dans le fichier de configuration système par défaut de GDM." - -#: ../C/gdm.xml:4590(para) -msgid "" -"The optional device argument is used to specify the device that is " -"associated with the DISPLAY. When using Virtual Terminals (VT), this value " -"is ignored and GDM will use the correct device name associated with the VT. " -"If not using VT, then GDM will use the value specified by this optional " -"argument. If the device argument is not defined, then GDM will use the " -"default setting for attached displays defined in the " -"<filename>UtmpLineAttached</filename> configuration section. For the main " -"display (typically DISPLAY <filename>:0</filename>), <filename>/dev/console</" -"filename> is a reasonable value. For other displays it is probably best to " -"not include this argument unless you know the specific device associated " -"with the DISPLAY. The device value can contain \"%d\" which is translated to " -"the DISPLAY value or \"%h\" which is translated to the hostname." -msgstr "" -"L'argument facultatif « device » est utilisé pour préciser le périphérique " -"associé à l'affichage. Avec l'utilisation des terminaux virtuels (VT), cette " -"valeur est ignorée et GDM utilise le nom de périphérique correct associé au " -"VT. Si les terminaux virtuels ne sont pas utilisés, GDM utilise alors la " -"valeur spécifiée par cet argument facultatif. Si l'argument n'est pas " -"défini, GDM utilise le paramètre par défaut pour les affichages liés défini " -"dans la section de configuration <filename>UtmpLineAttached</filename>. En " -"ce qui concerne l'affichage principal (généralement <filename>:0</" -"filename>), <filename>/dev/console</filename> est une valeur habituelle. " -"Pour d'autres affichages, il est probablement plus sûr de ne pas inclure cet " -"argument, sauf si vous connaissez le périphérique précis associé à " -"l'affichage. La valeur de « device » peut contenir « %d » qui correspond au " -"nom d'affichage (DISPLAY) ou « %h » qui correspond au nom d'hôte." - -#: ../C/gdm.xml:4614(title) -msgid "Per User Configuration" -msgstr "Configuration par utilisateur" - -#: ../C/gdm.xml:4616(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 <filename>UserMaxFile</filename> 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 "" -"Il existe certains paramètres de configuration propres aux utilisateurs, qui " -"définissent le comportement de GDM. GDM est très sensible en rapport avec " -"l'appartenance et les permissions des fichiers utilisateurs auxquels il " -"accède, et il ignore les fichiers qui n'appartiennent pas à l'utilisateur ou " -"ceux qui sont accessibles en écriture pour le groupe ou tout le monde. Il " -"ignore aussi l'utilisateur s'il n'est pas propriétaire de son dossier " -"personnel ou s'il est accessible en écriture pour le groupe ou tout le " -"monde. Les fichiers doivent aussi être plus petits que la valeur " -"<filename>UserMaxFile</filename> définie dans la configuration GDM. S'il " -"semble que GDM n'accède pas correctement aux paramètres de configuration " -"d'un utilisateur, le problème est probablement causé par l'échec de l'une de " -"ces vérifications." - -#: ../C/gdm.xml:4630(para) -msgid "" -"First there is the <filename>~/.dmrc</filename> file. In theory this file " -"should be shared between GDM and KDM, so users only have to configure things " -"once. This is a standard <filename>.ini</filename> style configuration file. " -"It has one section called <filename>[Desktop]</filename> which has two keys: " -"<filename>Session</filename> and <filename>Language</filename>." -msgstr "" -"Tout d'abord, il y a le fichier <filename>~/.dmrc</filename>. En théorie, ce " -"fichier devrait être partagé entre GDM et KDM, afin que les utilisateurs ne " -"doivent configurer qu'une seule fois les choses. C'est un fichier de " -"configuration de style <filename>.ini</filename> standard. Il contient une " -"section nommée <filename>[Desktop]</filename> ayant deux clés : " -"<filename>Session</filename> et <filename>Language</filename>." - -#: ../C/gdm.xml:4639(para) -msgid "" -"The <filename>Session</filename> key specifies the basename of the session " -"<filename>.desktop</filename> file that the user wishes to normally use " -"(without the <filename>.desktop</filename> extension, in other words). The " -"<filename>Language</filename> key specifies the language that the user " -"wishes to use by default. If either of these keys is missing, the system " -"default is used. The file would normally look as follows:" -msgstr "" -"La clé <filename>Session</filename> indique le nom de base du fichier de " -"session <filename>.desktop</filename> que l'utilisateur souhaite normalement " -"utiliser (c.à-d. sans l'extension <filename>.desktop</filename>). La clé " -"<filename>Language</filename> indique la langue que l'utilisateur souhaite " -"utiliser par défaut. Si l'une des clés est manquante, c'est la valeur par " -"défaut du système qui est utilisée. Le fichier ressemble habituellement à " -"ceci :" - -#: ../C/gdm.xml:4649(screen) -#, no-wrap -msgid "" -"\n" -"[Desktop]\n" -"Session=gnome\n" -"Language=cs_CZ.UTF-8\n" -msgstr "" -"\n" -"[Desktop]\n" -"Session=gnome\n" -"Language=fr_FR.UTF-8\n" - -#: ../C/gdm.xml:4655(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 "" -"En principe, GDM écrit ce fichier lors de la première connexion de " -"l'utilisateur. Il le modifie lorsque l'utilisateur choisit de modifier les " -"valeurs par défaut lors d'une connexion suivante." - -#: ../C/gdm.xml:4661(para) -msgid "" -"If the GDM Face Browser is turned on, then the file <filename>$HOME/.face</" -"filename> 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 " -"<filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> " -"values defined in the GDM configuration or it will be ignored. Users can run " -"the <command>gdmphotosetup</command> program to specify a face image and it " -"will copy the file to the <filename>$HOME/.face</filename> location and " -"scale it so its longest dimension is not larger than the " -"<filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> " -"values. <command>gdmphotosetup</command> takes care to not change the aspect " -"ratio of the image." -msgstr "" -"Si le navigateur de figures GDM est activé, le fichier <filename>$HOME/." -"face</filename> est recherché. Ce fichier devrait être une image standard " -"dans un format que GTK+ sache lire, tel que PNG ou JPEG. Il doit aussi être " -"plus petit que les valeurs <filename>MaxIconWidth</filename> et " -"<filename>MaxIconHeight</filename> définies dans la configuration de GDM, " -"sans quoi il sera ignoré. Les utilisateurs peuvent lancer le programme " -"<command>gdmphotosetup</command> pour définir une image de figure, et ce " -"programme copie le fichier à l'emplacement <filename>$HOME/.face</filename> " -"et il le redimensionne afin qu'il ne soit pas plus grand que les valeurs " -"maximales ci-dessus. <command>gdmphotosetup</command> prend garde à ce que " -"les proportions de l'image soient respectées." - -#: ../C/gdm.xml:4676(para) -msgid "" -"Face images can also be placed in the global face directory, which is " -"specified by the <filename>GlobalFaceDir</filename> configuration option " -"( normally <filename><share>/pixmaps/faces/</filename>) and the " -"filename should be the name of the user, optionally with a <filename>.png</" -"filename>, <filename>.jpg</filename>, etc. appended." -msgstr "" -"Les images de figures peuvent aussi être placées dans le répertoire de " -"figures global, indiqué par l'option de configuration " -"<filename>GlobalFaceDir</filename> (habituellement <filename><share>/" -"pixmaps/faces/</filename>). Le nom de fichier doit alors correspondre au nom " -"de l'utilisateur, avec une extension facultative de type <filename>.png</" -"filename>, <filename>.jpg</filename>, etc." - -#: ../C/gdm.xml:4687(title) -msgid "Controlling GDM" -msgstr "Supervision de GDM" - -#: ../C/gdm.xml:4689(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 "" -"Vous pouvez contrôler le comportement de GDM durant son exécution de " -"différentes manières. Vous pouvez soit lancer certaines commandes, soit vous " -"pouvez communiquer avec GDM à l'aide du protocole socket Unix ou d'un " -"protocole FIFO." - -#: ../C/gdm.xml:4696(title) -msgid "Commands" -msgstr "Commandes" - -#: ../C/gdm.xml:4698(para) -msgid "" -"To stop GDM, you can either send the TERM signal to the main daemon or run " -"the <command>gdm-stop</command> command which is in the <filename><" -"sbin>/</filename> directory. To restart GDM, you can either send the HUP " -"signal to the main daemon or run the <command>gdm-restart</command> command " -"which is also in the <filename><sbin>/</filename> 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 <command>gdm-safe-" -"restart</command> command which is in the <filename><sbin>/</filename> " -"directory as well." -msgstr "" -"Pour arrêter GDM, vous pouvez soit envoyer le signal TERM au démon " -"principal, soit exécuter la commande <command>gdm-stop</command> qui se " -"trouve dans le répertoire <filename><sbin>/</filename>. Pour " -"redémarrer GDM, vous pouvez soit envoyer le signal HUP au démon principal, " -"soit exécuter la commande <command>gdm-restart</command> qui se trouve aussi " -"dans le répertoire <filename><sbin>/</filename>. Pour redémarrer GDM, " -"mais uniquement après la déconnexion de tous les utilisateurs, vous pouvez " -"soit envoyer le signal USR1 au démon principal, soit exécuter la commande " -"<command>gdm-safe-restart</command>, toujours dans le répertoire " -"<filename><sbin>/</filename>." - -#: ../C/gdm.xml:4711(para) -msgid "" -"The <command>gdmflexiserver</command> 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 " -"<command>gdmflexiserver</command> 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 <command>gdmflexiserver --help</" -"command> to get a listing of possible options." -msgstr "" -"La commande <command>gdmflexiserver</command> peut être utilisée pour lancer " -"de nouveaux affichages flexibles (sur demande) si votre système prend en " -"charge les terminaux virtuels. Normalement, cette commande verrouille la " -"session en cours par un économiseur d'écran, afin que l'utilisateur puisse " -"sans crainte s'éloigne de l'ordinateur et laisser un autre utilisateur se " -"connecter. Si plus de deux affichages flexibles ont été démarrés, " -"<command>gdmflexiserver</command> affiche une boîte de dialogue permettant à " -"l'utilisateur de choisir la session qu'il veut poursuivre. L'utilisateur " -"doit normalement saisir son mot de passe pour retourner dans sa session. À " -"la fin d'une session, le système revient au terminal virtuel précédent. " -"Lancez <command>gdmflexiserver --help</command> pour obtenir une liste des " -"options possibles." - -#: ../C/gdm.xml:4727(title) -msgid "The FIFO protocol" -msgstr "Le protocole FIFO" - -#: ../C/gdm.xml:4729(para) -msgid "" -"GDM also provides a FIFO called <filename>.gdmfifo</filename> in the " -"<filename>ServAuthDir</filename> directory (usually <filename><var>/" -"gdm/.gdmfifo</filename>). 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 "" -"GDM propose aussi un fichier FIFO nommé <filename>.gdmfifo</filename> dans " -"le répertoire <filename>ServAuthDir</filename> (habituellement <filename><" -"var>/gdm/.gdmfifo</filename>). Vous devez être administrateur (root) pour " -"utiliser ce protocole, et son utilisation est principalement réservée aux " -"communications internes de GDM. C'est un protocole très simple où il suffit " -"d'écrire une commande sur une seule ligne du fichier. Il peut être utilisé " -"pour signifier à GDM des ordres comme le redémarrage, la mise en veille de " -"l'ordinateur ou le redémarrage de tous les serveurs X à la prochaine " -"occasion (ce qui peut être utile pour une application de configuration de X)." - -#: ../C/gdm.xml:4740(para) -msgid "" -"Full and up to date documentation of the commands and their use is contained " -"in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look " -"for the defines starting with <filename>GDM_SOP_</filename>. The commands " -"which require the pid of the slave as an argument are the ones that are " -"really used for internal communication of the slave with the master and " -"should not be used." -msgstr "" -"Une documentation complète et à jour des commandes et de leur usage se " -"trouve dans l'arborescence de la source de GDM dans le fichier " -"<filename>daemon/gdm.h</filename>. Recherchez les définitions de constantes " -"commençant par <filename>GDM_SOP_</filename>. Les commandes qui exigent " -"l'identifiant de processus de l'esclave comme argument sont celles qui sont " -"réellement utilisées pour la communication interne entre l'esclave et le " -"maître. Elles ne devraient pas être employées." - -#: ../C/gdm.xml:4752(title) -msgid "Socket Protocol" -msgstr "Protocole socket" - -#: ../C/gdm.xml:4754(para) -msgid "" -"GDM provides a unix domain socket for communication at <filename>/tmp/." -"gdm_socket</filename>. 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 <command>gdmflexiserver</" -"command> command uses this protocol, for example, to launch flexible (on-" -"demand) displays." -msgstr "" -"GDM fournit un socket de domaine Unix pour la communication dans <filename>/" -"tmp/.gdm_socket</filename>. Par ce moyen, vous pouvez vérifier si GDM est " -"lancé, la version du démon, les affichages actuellement en cours avec les " -"noms des personnes connectées et, pour autant que GDM le prenne en charge " -"sur votre système d'exploitation, les terminaux virtuels de toutes les " -"connexions en console. Par exemple, la commande <command>gdmflexiserver</" -"command> utilise ce protocole pour lancer des affichages flexibles (à la " -"demande)." - -#: ../C/gdm.xml:4764(para) -msgid "" -"gdmflexiserver accepts the following commands with the --command option:" -msgstr "" -"gdmflexiserver accepte les commandes suivantes avec l'option --command :" - -#: ../C/gdm.xml:4769(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 "" -"\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" - -#: ../C/gdm.xml:4799(para) -msgid "" -"These are described in detail below, including required arguments, response " -"format, and return codes." -msgstr "" -"Ces options sont décrites en détails ci-dessous, y compris les arguments " -"obligatoires, le format des réponses et les codes de retour." - -#: ../C/gdm.xml:4805(title) -msgid "ADD_DYNAMIC_DISPLAY" -msgstr "ADD_DYNAMIC_DISPLAY" - -#: ../C/gdm.xml:4806(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 "" -"\n" -"ADD_DYNAMIC_DISPLAY: Crée une nouvelle définition de serveur qui\n" -" s'exécute sur l'affichage indiqué, le laissant\n" -" dans l'état DISPLAY_CONFIG.\n" -"Pris en charge depuis : 2.8.0.0\n" -"Arguments : <affichage d'exécution>=<serveur>\n" -" Où <serveur> est soit une configuration mentionnée dans\n" -" la configuration GDM, soit un nom de commande littéral.\n" -"Réponses :\n" -" OK <affichage>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 2 = Affichage existant\n" -" 3 = Aucune chaîne de serveur\n" -" 4 = Échec de démarrage d'affichage\n" -" 100 = Non authentifié\n" -" 200 = Affichages dynamiques non autorisés\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:4828(title) -msgid "ALL_SERVERS" -msgstr "ALL_SERVERS" - -#: ../C/gdm.xml:4829(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 "" -"\n" -"ALL_SERVERS: Énumère tous les affichages, y compris consoles, distants ou xnest.\n" -" Cela peut être utile, par exemple, pour vérifier si\n" -" votre affichage actuel est géré par le démon gdm,\n" -" en parcourant la liste. Cela ressemble à la commande\n" -" « w », mais pour les sessions graphiques.\n" -"Pris en charge depuis : 2.4.2.96\n" -"Arguments : aucun\n" -"Réponses :\n" -" OK <serveur>;<serveur>;...\n" -"\n" -" <serveur> is <affichage>,<utilisateur connecté>\n" -"\n" -" <utilisateur connecté> peut être vide si personne ne s'est encore connecté\n" -"\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:4852(title) -msgid "ATTACHED_SERVERS" -msgstr "ATTACHED_SERVERS" - -#: ../C/gdm.xml:4853(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 "" -"\n" -"ATTACHED_SERVERS: Énumère tous les affichages liés. N'affiche pas\n" -" les affichages XDMCP et xnest non liés.\n" -"Note : Cette commande s'appelait CONSOLE_SERVERS, et\n" -" elle est toujours reconnue pour assurer la\n" -" rétrocompatibilité. L'argument facultatif motif\n" -" est pris en charge à partir de la version 2.8.0.0.\n" -"Pris en charge depuis : 2.2.4.0\n" -"Arguments : <motif> (facultatif)\n" -" Sans argument, tous les affichages liés sont renvoyés. L'argument\n" -" facultatif <motif> est une chaîne de caractères pouvant contenir les\n" -" caractères d'expansion « * », « ? » et « [] ».\n" -" Seuls les affichages correspondants au motif sont renvoyés.\n" -"Réponses :\n" -" OK <serveur>;<serveur>;...\n" -"\n" -" <serveur> is <affichage>,<utilisateur connecté>,<affichage\n" -" vt ou xnest>\n" -"\n" -" <utilisateur connecté> peut être vide si personne ne s'est encore\n" -" connecté, et <vt> peut valoir -1 s'il est inconnu ou non pris en\n" -" charge (par ex. sur des systèmes autres que Linux). Si l'affichage est\n" -" xnest est qu'il est en console (c.-à-d. un xnest à l'intérieur d'un\n" -" autre affichage en console) il apparaît dans la liste, mais au lieu de\n" -" vt, c'est l'affichage parent sous la forme standard qui est mentionné.\n" -"\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:4886(title) -msgid "AUTH_LOCAL" -msgstr "AUTH_LOCAL" - -#: ../C/gdm.xml:4887(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 into attached displays, and here GDM\n" -" assumes only users logged in from GDM. They must\n" -" pass the xauth MIT-MAGIC-COOKIE-1 that they were\n" -" passed 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 "" -"\n" -"AUTH_LOCAL: Définit cette connexion comme authentifiée pour\n" -" FLEXI_SERVER. C'est parce qu'un affichage standard\n" -" (non imbriqué) ne peut être démarré que par des utilisateurs\n" -" connectés sur des affichages liés, et dans ce cas, GDM ne \n" -" considère que les utilisateurs connecté par GDM. Ils doivent\n" -" transmettre le cookie xauth MIT-MAGIC-COOKIE-1 qu'ils ont reçu\n" -" avant que la connexion ne soit authentifiée.\n" -"Note : La commande AUTH LOCAL exige\n" -" l'option --authenticate, même si seul\n" -" FLEXI XSERVER l'utilise actuellement.\n" -"Note : Depuis la version 2.6.0.6, vous pouvez aussi utiliser un\n" -" cookie global <ServAuthDir>/.cookie, qui fonctionne pour\n" -" toutes les authentifications, excepté pour SET_LOGOUT_ACTION,\n" -" QUERY_LOGOUT_ACTION et SET_SAFE_LOGOUT_ACTION\n" -" qui exigent un affichage avec connexion.\n" -"Pris en charge depuis : 2.2.4.0\n" -"Arguments : <cookie xauth>\n" -" <cookie xauth> est sous forme hexadécimale, sans préfixe 0x\n" -"Réponses :\n" -" OK\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:4917(title) -msgid "CLOSE" -msgstr "CLOSE" - -#: ../C/gdm.xml:4918(screen) -#, no-wrap -msgid "" -"\n" -"CLOSE: Close sockets connection\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers: None\n" -msgstr "" -"\n" -"CLOSE : Ferme la connexion socket.\n" -"Pris en charge depuis : 2.2.4.0\n" -"Arguments : aucun\n" -"Réponses : aucune\n" - -#: ../C/gdm.xml:4927(title) -msgid "FLEXI_XNEST" -msgstr "FLEXI_XNEST" - -#: ../C/gdm.xml:4928(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 "" -"\n" -"FLEXI_XNEXT: Démarre un nouvel affichage flexible imbriqué.\n" -"Note : Pris en charge dans les anciennes versions dès 2.2.4.0, puis\n" -" 2.2.4.2, mais depuis la version 2.3.90.4, vous devez fournir 4\n" -" arguments, sans quoi l'erreur 100 est renvoyée. Cela\n" -" va lancer la commande de serveur X imbriqué avec\n" -" le fichier XAUTHORITY spécifié et sous la même\n" -" identité que le propriétaire de ce fichier (et le même\n" -" que vous avez spécifié). Vous devez aussi fournir le cookie\n" -" comme 3ème argument de l'affichage, pour prouver que\n" -" vous êtes bien cet utilisateur. Ce fichier doit aussi être\n" -" UNIQUEMENT lisible par cet utilisateur, c'est-à-dire qu'il\n" -" doit être en mode 0600. Si l'une des conditions n'est pas\n" -" respectée, l'erreur 100 est renvoyée.\n" -"Note : Le cookie doit être MIT-MAGIC-COOKIE-1,\n" -" le premier que GDM peut trouver dans le fichier XAUTHORITY\n" -" pour cet affichage. Si ce n'est pas ce que vous utilisez,\n" -" vous devriez d'abord en générer un. Le cookie\n" -" doit être sous forme hexadécimale.\n" -"Pris en charge depuis : 2.3.90.4\n" -"Arguments : <affichage d'exécution> <identifiant d'utilisateur>\n" -" <cookie xauth pour l'affichage> <fichier xauth>\n" -"Réponses :\n" -" OK <affichage>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 1 = Plus de serveur flexi\n" -" 2 = Erreurs de démarrage\n" -" 3 = Échec de X\n" -" 4 = X trop occupé\n" -" 5 = Xnest ne peut se connecter\n" -" 6 = Aucun binaire de serveur\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:4967(title) -msgid "FLEXI_XNEST_USER" -msgstr "FLEXI_XNEST_USER" - -#: ../C/gdm.xml:4968(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 "" -"\n" -"FLEXI_XNEST_USER: Lance un nouvel affichage flexible imbriqué\n" -" et initialise la bannière avec le nom d'utilisateur indiqué.\n" -"Note : C'est une variante de la commande FLEXI_XNEST.\n" -"Note : Le cookie doit être MIT-MAGIC-COOKIE-1,\n" -" le premier que GDM peut trouver dans le fichier XAUTHORITY\n" -" pour cet affichage. Si ce n'est pas ce que vous utilisez,\n" -" vous devriez d'abord en générer un. Le cookie\n" -" doit être sous forme hexadécimale.\n" -"Pris en charge depuis : 2.17.7\n" -"Arguments : <nom d'utilisateur> <affichage d'exécution> <identifiant de\n" -" l'utilisateur> <cookie xauth pour l'affichage> <fichier xauth>\n" -"Réponses :\n" -" OK <affichage>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 1 = Plus de serveur flexi\n" -" 2 = Erreurs de démarrage\n" -" 3 = Échec de X\n" -" 4 = X trop occupé\n" -" 5 = Xnest ne peut se connecter\n" -" 6 = Aucun binaire de serveur\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:4997(title) -msgid "FLEXI_XSERVER" -msgstr "FLEXI_XSERVER" - -#: ../C/gdm.xml:4998(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 "" -"\n" -"FLEXI_XSERVER: Lance un nouvel affichage X flexible. Pris en charge uniquement\n" -" pour les connexions qui ont transmis AUTH_LOCAL.\n" -"Pris en charge depuis : 2.2.4.0\n" -"Arguments : <type xserver>\n" -" Sans argument, c'est le serveur X standard qui est lancé.\n" -"Réponses :\n" -" OK <affichage>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 1 = Plus de serveur flexi\n" -" 2 = Erreurs de démarrage\n" -" 3 = Échec de X\n" -" 4 = X trop occupé\n" -" 6 = Aucun binaire de serveur\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5020(title) -msgid "FLEXI_XSERVER_USER" -msgstr "FLEXI_XSERVER_USER" - -#: ../C/gdm.xml:5021(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 "" -"\n" -"FLEXI_XSERVER_USER: Lance un nouvel affichage X flexible et initialise la\n" -" bannière avec le nom d'utilisateur indiqué. Pris en charge\n" -" uniquement pour les connexions qui ont transmis AUTH_LOCAL.\n" -"Pris en charge depuis : 2.17.7 \n" -"Arguments : <nom d'utilisateur> <type de xserver>\n" -" Si aucun type de serveur n'est indiqué, c'est le serveur X standard qui est lancé.\n" -"Réponses :\n" -" OK <affichage>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 1 = Plus de serveur flexi\n" -" 2 = Erreurs de démarrage\n" -" 3 = Échec de X\n" -" 4 = X trop occupé\n" -" 6 = Aucun binaire de serveur\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5044(title) -msgid "GET_CONFIG" -msgstr "GET_CONFIG" - -#: ../C/gdm.xml:5045(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 "" -"\n" -"GET_CONFIG: Obtient la valeur de configuration de la clé. Utile\n" -" pour que d'autres applications puissent interroger GDM sur ses\n" -" informations de configuration. Toute clé définie comme GDM_KEY_*\n" -" dans gdm-daemon-config-keys.h est prise en charge. À partir de la\n" -" version 2.13.0.2, les clés traduites (telles que\n" -" « greeter/GdmWelcome[fr] » sont prises en charge par GET_CONFIG.\n" -" Depuis cette même version 2.13.0.2, il n'est plus nécessaire\n" -" d'inclure la valeur par défaut (c.-à-d. que vous pouvez indiquer\n" -" la clé « greeter/IncludeAll » au lieu de devoir indiquer\n" -" « greeter/IncludeAll=false ».\n" -"Pris en charge depuis : 2.6.0.9\n" -"Arguments : <clé>\n" -"Réponses :\n" -" OK <valeur>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 50 = Clé non prise en charge\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5069(title) -msgid "GET_CONFIG_FILE" -msgstr "GET_CONFIG_FILE" - -#: ../C/gdm.xml:5070(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 "" -"\n" -"GET_CONFIG_FILE: Obtient l'emplacement du fichier de configuration\n" -" utilisé par le démon. si le démon GDM a été lancé avec\n" -" l'option --config, il renvoie la valeur qui a été\n" -" transmise par cet argument.\n" -"Pris en charge depuis : 2.8.0.2\n" -"Arguments : aucun\n" -"Réponses :\n" -" OK <chemin complet vers le fichier de configuration de GDM>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5087(title) -msgid "GET_CUSTOM_CONFIG_FILE" -msgstr "GET_CUSTOM_CONFIG_FILE" - -#: ../C/gdm.xml:5088(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 "" -"\n" -"GET_CUSTOM_CONFIG_FILE: Obtient l'emplacement du fichier de configuration\n" -" utilisé par le démon.\n" -"Pris en charge depuis : 2.14.0.0\n" -"Arguments : aucun\n" -"Réponses :\n" -" OK <chemin complet vers le fichier de configuration personnalisée de GDM>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 1 = Fichier non trouvé\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5104(title) -msgid "GET_SERVER_DETAILS" -msgstr "GET_SERVER_DETAILS" - -#: ../C/gdm.xml:5105(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 "" -"\n" -"GET_SERVER_DETAILS: Obtient des informations détaillées sur un serveur spécifique.\n" -"Pris en charge depuis : 2.13.0.4\n" -"Arguments : <serveur> <clé>\n" -" Les valeurs de clé comprennent :\n" -" NAME - Renvoie le nom du serveur\n" -" COMMAND - Renvoie la commande du serveur\n" -" FLEXIBLE - Renvoie « true » si c'est un serveur flexible,\n" -" « false » sinon\n" -" CHOOSABLE - Renvoie « true » si c'est un serveur sélectionnable,\n" -" « false » sinon\n" -" HANDLED - Renvoie « true » si c'est un serveur géré,\n" -" « false » sinon\n" -" CHOOSER - Renvoie « true » si c'est un sélecteur,\n" -" « false » sinon\n" -" PRIORITY - Renvoie la priorité du processus\n" -"Réponses :\n" -" OK <valeur>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 1 = Serveur introuvable\n" -" 2 = Clé non valide\n" -" 50 = Clé non prise en charge\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5134(title) -msgid "GET_SERVER_LIST" -msgstr "GET_SERVER_LIST" - -#: ../C/gdm.xml:5135(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 "" -"\n" -"GET_SERVER_LIST: Obtient une liste des sections « server » du\n" -" fichier de configuration.\n" -"Pris en charge depuis : 2.13.0.4\n" -"Arguments : aucun\n" -"Réponses :\n" -" OK <valeur>;<valeur>;...\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 1 = Aucun serveur trouvé\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5151(title) -msgid "GREETERPIDS" -msgstr "GREETERPIDS" - -#: ../C/gdm.xml:5152(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 "" -"\n" -"GREETERPIDS: Énumère tous les identifiants de processus (pid) de bannière\n" -" afin de pouvoir leur envoyer le signal HUP pour qu'ils relisent\n" -" la configuration. Il faut bien sûr être root pour pouvoir faire cela.\n" -"Pris en charge depuis : 2.3.90.2\n" -"Arguments : aucun\n" -"Réponses :\n" -" OK <pid>;<pid>;...\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5168(title) -msgid "QUERY_LOGOUT_ACTION" -msgstr "QUERY_LOGOUT_ACTION" - -#: ../C/gdm.xml:5169(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 "" -"\n" -"QUERY_LOGOUT_ACTION: Interroge sur les actions de déconnexion possibles.\n" -" Pris en charge uniquement pour les connexions qui\n" -" ont transmis AUTH_LOCAL.\n" -"Pris en charge depuis : 2.5.90.0\n" -"Réponses :\n" -" OK <action>;<action>;...\n" -" Où action vaut HALT, REBOOT, SUSPEND ou CUSTOM_CMD[0-9].\n" -" Une liste vide peut aussi être renvoyée si aucune action n'est possible.\n" -" Un « ! » est ajouté à une action si elle a déjà été définie avec\n" -" SET_LOGOUT_ACTION ou SET_SAFE_LOGOUT_ACTION. Il faut relever que\n" -" SET_LOGOUT_ACTION a la priorité sur SET_SAFE_LOGOUT_ACTION.\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5191(title) -msgid "QUERY_CUSTOM_CMD_LABELS" -msgstr "QUERY_CUSTOM_CMD_LABELS" - -#: ../C/gdm.xml:5192(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 "" -"\n" -" QUERY_CUSTOM_CMD_LABELS: Interroge sur les étiquettes des commandes\n" -" personnalisées exportées. Pris en charge uniquement pour les\n" -" connexions qui ont transmis AUTH_LOCAL.\n" -" Pris en charge depuis : 2.5.90.0\n" -" Réponses :\n" -" OK <étiquette1>;<étiquette2>;...\n" -" Où étiquetteX est l'une des étiquettes des commandes CUSTOM_CMDX\n" -" (où X va de 0 à GDM_CUSTOM_COMMAND_MAX). Une liste vide peut\n" -" aussi être renvoyée si aucune des commandes personnalisées n'est\n" -" exportée hors du gestionnaire de connexions (aucune des options\n" -" CustomCommandIsPersistent n'est définie à « true »).\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5213(title) -msgid "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" -msgstr "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" - -#: ../C/gdm.xml:5214(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 "" -"\n" -"QUERY_CUSTOM_CMD_NO_RESTART_STATUS: Interroge les options de\n" -" configuration NoRestart pour chaque commande\n" -" personnalisée. Pris en charge uniquement pour les\n" -" connexions qui ont transmis AUTH_LOCAL.\n" -"Pris en charge depuis : 2.5.90.0\n" -"Réponses :\n" -" OK <état>\n" -" Où chaque bit d'état représente la valeur NoRestart\n" -" de chaque commande personnalisée.\n" -" bit activé (1) : NoRestart = true,\n" -" bit désactivé (0): NoRestart = false.\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5235(title) -msgid "QUERY_VT" -msgstr "QUERY_VT" - -#: ../C/gdm.xml:5236(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 "" -"\n" -"QUERY_VT: Demande au démon sur quel terminal virtuel nous nous trouvons.\n" -" C'est utile pour les connexions qui ne possèdent pas\n" -" /dev/console, mais qui sont tout de même des connexions\n" -" de console. Pris en charge uniquement sur Linux pour l'instant,\n" -" d'autres systèmes retournent simplement l'erreur 8. C'est aussi\n" -" la méthode privilégiée à utiliser pour savoir si la prise en charge\n" -" des terminaux virtuels est disponible dans le démon. Pris en charge\n" -" uniquement pour les connexions qui ont transmis AUTH_LOCAL.\n" -"Pris en charge depuis : 2.5.90.0\n" -"Arguments : aucun\n" -"Réponses :\n" -" OK <numéro de terminal virtuel>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 8 = Terminaux virtuels non pris en charge\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5259(title) -msgid "RELEASE_DYNAMIC_DISPLAYS" -msgstr "RELEASE_DYNAMIC_DISPLAYS" - -#: ../C/gdm.xml:5260(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 "" -"\n" -"RELEASE_DYNAMIC_DISPLAYS: Libère les affichages dynamiques actuellement\n" -" dans l'état DISPLAY_CONFIG.\n" -"Pris en charge depuis : 2.8.0.0\n" -"Arguments : <affichage à libérer>\n" -"Réponses :\n" -" OK <affichage>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 1 = Mauvais numéro d'affichage\n" -" 100 = Non authentifié\n" -" 200 = Affichages dynamiques non autorisés\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5277(title) -msgid "REMOVE_DYNAMIC_DISPLAY" -msgstr "REMOVE_DYNAMIC_DISPLAY" - -#: ../C/gdm.xml:5278(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 "" -"\n" -"REMOVE_DYNAMIC_DISPLAY: Supprime un affichage dynamique en tuant le\n" -" serveur et en nettoyant la configuration de l'affichage.\n" -"Pris en charge depuis : 2.8.0.0\n" -"Arguments : <affichage à supprimer>\n" -"Réponses :\n" -" OK <affichage>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 1 = Mauvais numéro d'affichage\n" -" 100 = Non authentifié\n" -" 200 = Affichages dynamiques non autorisés\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5295(title) -msgid "SERVER_BUSY" -msgstr "SERVER_BUSY" - -#: ../C/gdm.xml:5296(screen) -#, no-wrap -msgid "" -"\n" -"SERVER_BUSY: Returns true if half or more of the daemon's sockets\n" -" are busy, false otherwise. Used by slave programs\n" -" which want to ensure they do not overwhelm the \n" -" sever.\n" -"Supported since: 2.13.0.8\n" -"Arguments: None\n" -"Answers:\n" -" OK <value>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -msgstr "" -"\n" -"SERVER_BUSY: Renvoie « true » (vrai) si la moitié ou plus des sockets de\n" -" démons sont occupés, sinon renvoie « false » (faux). Utilisé par\n" -" des programmes esclaves qui veulent s'assurer de ne pas\n" -" surcharger le serveur.\n" -"Pris en charge depuis : 2.13.0.8\n" -"Arguments : aucun\n" -"Réponses :\n" -" OK <valeur>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5313(title) -msgid "SET_LOGOUT_ACTION" -msgstr "SET_LOGOUT_ACTION" - -#: ../C/gdm.xml:5314(screen) -#, no-wrap -msgid "" -"\n" -"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -" slave process exits. 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 "" -"\n" -"SET_LOGOUT_ACTION: Signale au démon qu'il doit stopper, redémarrer ou\n" -" mettre en veille après que le processus esclave soit fermé.\n" -" Pris en charge uniquement pour les connexions qui ont\n" -" transmis AUTH_LOCAL.\n" -"Pris en charge depuis : 2.5.90.0\n" -"Arguments : <action>\n" -" NONE Définit l'action de sortie à « none » (aucune)\n" -" HALT Définit l'action de sortie à « halt » (arrêter)\n" -" REBOOT Définit l'action de sortie à « reboot » (redémarrer)\n" -" SUSPEND Définit l'action de sortie à « suspend » (mettre en veille)\n" -" CUSTOM_CMD[0-9] Définit l'action de sortie à la commande personnalisée [0-9]\n" -"Réponses :\n" -" OK\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 7 = Action de déconnexion inconnue ou non disponible\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5337(title) -msgid "SET_SAFE_LOGOUT_ACTION" -msgstr "SET_SAFE_LOGOUT_ACTION" - -#: ../C/gdm.xml:5338(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 "" -"\n" -"SET_SAFE_LOGOUT_ACTION: Signale au démon qu'il doit stopper, redémarrer ou\n" -" mettre en veille après la déconnexion de tous les\n" -" utilisateurs. Si une seule personne se déconnecte,\n" -" cela revient au même que SET_LOGOUT_ACTION. Il\n" -" faut relever que SET_LOGOUT_ACTION a la priorité\n" -" sur SET_SAFE_LOGOUT_ACTION s'il contient autre\n" -" chose que « NONE ». Si personne n'est\n" -" connecté, l'action s'effectue immédiatement.\n" -" Pris en charge uniquement pour les connexions\n" -" qui ont transmis AUTH_LOCAL.\n" -"Pris en charge depuis : 2.5.90.0\n" -"Arguments : <action>\n" -" NONE Définit l'action de sortie à « none » (aucune)\n" -" HALT Définit l'action de sortie à « halt » (arrêter)\n" -" REBOOT Définit l'action de sortie à « reboot » (redémarrer)\n" -" SUSPEND Définit l'action de sortie à « suspend » (mettre en veille)\n" -" CUSTOM_CMD[0-9] Définit l'action de sortie à la commande personnalisée [0-9]\n" -"Réponses :\n" -" OK\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 7 = Action de déconnexion inconnue ou non disponible\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5368(title) -msgid "SET_VT" -msgstr "SET_VT" - -#: ../C/gdm.xml:5369(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 "" -"\n" -"SET_VT: Bascule sur le terminal virtuel indiqué.\n" -" C'est utile pour les connexions qui ne possèdent pas /dev/console\n" -" mais qui sont tout de même des connexions de console. Pris\n" -" en charge uniquement sur Linux pour l'instant, d'autres systèmes\n" -" renvoient simplement l'erreur 8. Pris en charge uniquement\n" -" pour les connexions qui ont transmis AUTH_LOCAL.\n" -"Pris en charge depuis : 2.5.90.0\n" -"Arguments : <vt>\n" -"Réponses :\n" -" OK\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 8 = Terminaux virtuels non pris en charge\n" -" 9 = Numéro de terminal virtuel non valide\n" -" 100 = Non authentifié\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5390(title) -msgid "UPDATE_CONFIG" -msgstr "UPDATE_CONFIG" - -#: ../C/gdm.xml:5391(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 "" -"\n" -"UPDATE_CONFIG: Signale au démon qu'il doit relire une clé\n" -" du fichier de configuration GDM. Tout utilisateur peut\n" -" demander que des valeurs soient lues à nouveau, mais\n" -" le démon ne le fait que si le fichier a été modifié depuis\n" -" sa première lecture par GDM. Seuls les utilisateurs\n" -" qui peuvent modifier le fichier de configuration de GDM\n" -" (normalement seul root peut y écrire) peuvent réellement\n" -" modifier la configuration de GDM. Cette commande\n" -" est utile pour demander à GDM de se mettre à jour\n" -" afin de prendre en compte une modification du fichier\n" -" de configuration de GDM effectuée par l'administrateur (root).\n" -"\n" -" À partir de la version 2.13.0.0, toutes les clés de GDM sont\n" -" prises en charge à l'exception des suivantes :\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 prend aussi en charge les pseudo-clés suivantes :\n" -"\n" -" xdmcp/PARAMETERS (2.3.90.2) met à jour ce qui suit :\n" -" xdmcp/MaxPending\n" -" xdmcp/MaxSessions\n" -" xdmcp/MaxWait\n" -" xdmcp/DisplaysPerHost\n" -" xdmcp/HonorIndirect\n" -" xdmcp/MaxPendingIndirect\n" -" xdmcp/MaxWaitIndirect\n" -" xdmcp/PingIntervalSeconds (concerne seulement les nouvelles connexions)\n" -"\n" -" xservers/PARAMETERS (2.13.0.4) met à jour ce qui suit :\n" -" toutes les sections [server-??].\n" -"\n" -" Clés prises en charge des versions précédentes de 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" -"Pris en charge depuis : 2.3.90.2\n" -"Arguments : <clé>\n" -" <clé> n'est que la partie de base de la clé, comme\n" -" « security/AllowRemoteRoot »\n" -"Réponses :\n" -" OK\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 0 = Non implémenté\n" -" 50 = Clé non prise en charge\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5467(title) -msgid "VERSION" -msgstr "VERSION" - -#: ../C/gdm.xml:5468(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 "" -"\n" -"VERSION: Interroge la version de GDM\n" -"Pris en charge depuis : 2.2.4.0\n" -"Arguments : aucun\n" -"Réponses :\n" -" GDM <version de GDM>\n" -" ERROR <numéro d'erreur> <description d'erreur en anglais>\n" -" 200 = Trop de messages\n" -" 999 = Erreur inconnue\n" - -#: ../C/gdm.xml:5485(title) -msgid "GDM Commands" -msgstr "Commandes GDM" - -#: ../C/gdm.xml:5488(title) -msgid "GDM User Commands" -msgstr "Commandes utilisateur GDM" - -#: ../C/gdm.xml:5490(para) -msgid "" -"The GDM package provides the following different commands in " -"<filename>bindir</filename> intended to be used by the end-user:" -msgstr "" -"Le paquet GDM fournit les différentes commandes ci-après dans " -"<filename>bindir</filename>, à l'intention de l'utilisateur :" - -#: ../C/gdm.xml:5496(title) -msgid "" -"<command>gdmXnestchooser</command> and <command>gdmXnest</command> Command " -"Line Options" -msgstr "" -"Options en ligne de commande de <command>gdmXnestchooser</command> et " -"<command>gdmXnest</command>" - -#: ../C/gdm.xml:5499(para) -msgid "" -"The <command>gdmXnestchooser</command> 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 <command>gdmXnestchooser somehost</command> will run " -"the XDMCP chooser from host <command>somehost</command> inside a nested X " -"server session. You can make this command do a direct query instead by " -"passing the <command>-d</command> option as well. In addition to the " -"following options, this command also supports standard GNOME options." -msgstr "" -"La commande <command>gdmXnestchooser</command> obtient automatiquement le " -"bon numéro d'affichage, configure l'accès et exécute la commande du serveur " -"X imbriqué avec l'argument « -indirect localhost ». Cela fournit un " -"programme sélecteur XDMCP. Vous pouvez également donner comme argument le " -"nom d'hôte duquel doit provenir le sélecteur affiché. Ainsi, la commande " -"<command>gdmXnestchooser hôteH</command> exécute le sélecteur XDMCP de " -"l'hôte <command>hôteH</command> à l'intérieur d'une session de serveur X " -"imbriqué. Vous pouvez faire que la commande effectue une requête directe en " -"lui passant aussi l'option <command>-d</command>. En plus des options " -"suivantes, cette commande prend aussi en charge les options standards de " -"GNOME." - -#: ../C/gdm.xml:5514(title) -msgid "<command>gdmXnestchooser</command> Command Line Options" -msgstr "Options en ligne de commande de <command>gdmXnestchooser</command>" - -#: ../C/gdm.xml:5517(term) -msgid "-x, --xnest=STRING" -msgstr "-x, --xnest=CHAÎNE" - -#: ../C/gdm.xml:5519(para) -msgid "" -"Nested X server command line, default is defined by the <filename>Xnest</" -"filename> configuration option." -msgstr "" -"Ligne de commande du serveur X imbriqué, la valeur par défaut étant définie " -"par l'option de configuration <filename>Xnest</filename>." - -#: ../C/gdm.xml:5527(term) -msgid "-o, --xnest-extra-options=OPTIONS" -msgstr "-o, --xnest-extra-options=OPTIONS" - -#: ../C/gdm.xml:5529(para) -msgid "Extra options for nested X server, default is no options." -msgstr "" -"Options supplémentaires pour le serveur X imbriqué, la valeur par défaut " -"étant aucune option." - -#: ../C/gdm.xml:5536(term) -msgid "-n, --no-query" -msgstr "-n, --no-query" - -#: ../C/gdm.xml:5538(para) -msgid "Just run nested X server, no query (no chooser)" -msgstr "Exécute simplement Xnest, sans requête (pas de sélecteur)" - -#: ../C/gdm.xml:5545(term) -msgid "-d, --direct" -msgstr "-d, --direct" - -#: ../C/gdm.xml:5547(para) -msgid "Do direct query instead of indirect (chooser)" -msgstr "Effectue une requête directe au lieu de indirecte (sélecteur)" - -#: ../C/gdm.xml:5554(term) -msgid "-B, --broadcast" -msgstr "-B, --broadcast" - -#: ../C/gdm.xml:5556(para) -msgid "Run broadcast instead of indirect (chooser)" -msgstr "Exécute la diffusion (broadcast) à la place de indirect (sélecteur)" - -#: ../C/gdm.xml:5563(term) -msgid "-b, --background" -msgstr "-b, --background" - -#: ../C/gdm.xml:5565(para) -msgid "Run in background" -msgstr "S'exécute en arrière-plan" - -#: ../C/gdm.xml:5572(term) -msgid "--no-gdm-check" -msgstr "--no-gdm-check" - -#: ../C/gdm.xml:5574(para) -msgid "Don't check for running GDM" -msgstr "Ne contrôle pas si d'autres GDM sont en cours d'exécution" - -#: ../C/gdm.xml:5583(title) ../C/gdm.xml:5626(title) -msgid "<command>gdmflexichooser</command> Command Line Options" -msgstr "Options en ligne de commande de <command>gdmflexichooser</command>" - -#: ../C/gdm.xml:5585(para) -msgid "" -"The <command>gdmflexiserver</command> 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 "" -"La commande <command>gdmflexiserver</command> offre trois fonctionnalités. " -"Elle peut être utilisée pour lancer des affichages X flexibles (à la " -"demande), pour lancer un affichage flexible via un serveur X imbriqué et " -"pour envoyer des commandes au processus démon de GDM." - -#: ../C/gdm.xml:5592(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 "" -"Le démarrage d'un affichage X flexible verrouille normalement la session en " -"cours avec un économiseur d'écran et réaffiche l'écran de connexion de GDM " -"pour qu'un deuxième utilisateur puisse s'y connecter. Cette fonctionnalité " -"n'est disponible que sur les systèmes qui prennent en charge les terminaux " -"virtuels et où ils sont activés. Cette fonctionnalité est utile si vous êtes " -"connecté comme utilisateur A et que B veut rapidement se connecter sans que " -"A doive se déconnecter. Le serveur X s'occupe du basculement de terminal " -"virtuel de manière transparente. S'il existe plus d'un affichage en fonction " -"avec le paramètre flexible=true, l'utilisateur voit apparaître une boîte de " -"dialogue présentant les sessions actuellement ouvertes. Il peut alors " -"choisir la session qu'il souhaite poursuivre et doit normalement saisir son " -"mot de passe pour déverrouiller l'écran." - -#: ../C/gdm.xml:5606(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 "" -"Les affichages imbriqués fonctionnent sur les systèmes qui ne prennent pas " -"en charge les terminaux virtuels. Cette option lance un affichage flexible " -"dans une fenêtre de la session actuelle. Cela ne verrouille pas la session " -"encours, ce qui fait que ce n'est pas aussi sécurisé qu'un serveur flexible " -"démarré via un terminal virtuel." - -#: ../C/gdm.xml:5613(para) -msgid "" -"The <command>gdmflexiserver --command</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 "" -"L'option <command>gdmflexiserver --command</command> offre une manière " -"d'envoyer des commandes au démon GDM et peut être employée pour résoudre des " -"problèmes ou pour modifier la configuration de GDM." - -#: ../C/gdm.xml:5619(para) -msgid "" -"In addition to the following options, <command>gdmflexiserver</command> also " -"supports standard GNOME options." -msgstr "" -"En plus des options suivantes, <command>gdmflexiserver</command> prend aussi " -"en charge les options GNOME standards." - -#: ../C/gdm.xml:5629(term) -msgid "-c, --command=COMMAND" -msgstr "-c, --command=COMMANDE" - -#: ../C/gdm.xml:5631(para) -msgid "Send the specified protocol command to GDM" -msgstr "Envoie la commande de protocole spécifiée à GDM" - -#: ../C/gdm.xml:5638(term) -msgid "-n, --xnest" -msgstr "-n, --xnest" - -#: ../C/gdm.xml:5640(para) -msgid "Start a flexible X display in Nested mode" -msgstr "Démarre un affichage X flexible en mode imbriqué" - -#: ../C/gdm.xml:5647(term) -msgid "-l, --no-lock" -msgstr "-l, --no-lock" - -#: ../C/gdm.xml:5649(para) -msgid "Do not lock current screen" -msgstr "Ne verrouille pas l'écran actuel" - -#: ../C/gdm.xml:5656(term) -msgid "-d, --debug" -msgstr "-d, --debug" - -#: ../C/gdm.xml:5658(para) -msgid "" -"Turns on debugging output which gets sent to syslog. Same as turning on " -"debug in the configuration file." -msgstr "" -"Active la sortie de débogage, qui est envoyée dans le syslog. Même effet " -"qu'en activant l'option « debug » dans le fichier de configuration." - -#: ../C/gdm.xml:5666(term) -msgid "-a, --authenticate" -msgstr "-a, --authenticate" - -#: ../C/gdm.xml:5668(para) -msgid "Authenticate before running --command" -msgstr "S'authentifie avant de lancer --command" - -#: ../C/gdm.xml:5675(term) -msgid "-s, --startnew" -msgstr "-s, --startnew" - -#: ../C/gdm.xml:5677(para) -msgid "" -"Starts a new flexible display without displaying a dialog asking the user if " -"they wish to continue any existing sessions." -msgstr "" -"Démarre un nouvel affichage flexible sans afficher de boîte de dialogue " -"demandant à l'utilisateur s'il veut continuer une session existante." - -#: ../C/gdm.xml:5688(title) ../C/gdm.xml:5715(title) -msgid "<command>gdmdynamic</command> Command Line Options" -msgstr "Options en ligne de commande de <command>gdmdynamic</command>" - -#: ../C/gdm.xml:5690(para) -msgid "" -"<command>gdmdynamic</command> 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 " -"<command>gdmdynamic</command> command can be used to create a new display on " -"a particular display number, run all newly created displays, or remove a " -"display. The <command>gdmdynamic</command> 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 "" -"<command>gdmdynamic</command> autorise la gestion des affichages de manière " -"dynamique. Il est habituellement utilisé dans des environnements qui ne " -"permettent pas d'énumérer les affichages possibles dans les fichiers de " -"configuration de GDM. La commande <command>gdmdynamic</command> peut être " -"utilisée pour créer un nouvel affichage sur un numéro d'affichage précis, " -"pour exécuter tous les affichage nouvellement créés ou pour supprimer un " -"affichage. Elle peut aussi être employée pour énumérer tous les affichages " -"liés, ou uniquement les affichages liés correspondant à certains critères. " -"L'option -a permet d'ajouter un affichage, l'option -r permet de lancer (ou " -"libérer) un affichage, l'option -d permet de supprimer un affichage et " -"l'option -l énumère les affichages existants. Une seule de ces quatre " -"options peut être indiquée à la fois. Le cycle de vie d'un affichage passe " -"en principe par un premier appel à la commande pour créer l'affichage, un " -"deuxième appel pour le libérer (lancer) et finalement un troisième appel " -"pour le supprimer lorsque la session doit être détruite." - -#: ../C/gdm.xml:5707(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 "" -"Ce programme est conçu pour gérer plusieurs requêtes simultanées et essaye " -"d'éviter de submerger le démon de requêtes. Si la connexion socket est " -"occupée, il se met en attente et réessaye un certain nombre de fois, ce qui " -"peut être ajusté avec les options -s et -t." - -#: ../C/gdm.xml:5718(term) -msgid "-a display=server" -msgstr "-a affichage=serveur" - -#: ../C/gdm.xml:5720(para) -msgid "" -"Add a new display configuration, leaving it in the DISPLAY_CONFIG state. For " -"example, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a 3=/usr/" -"X11R6/bin/X -dev /dev/fb2\"</command>" -msgstr "" -"Ajoute une nouvelle configuration d'affichage, le laissant dans l'état " -"DISPLAY_CONFIG. Par exemple, <command>« -a 2=StandardServeurDeux »</command> " -"ou <command>« -a 3=/usr/X11R6/bin/X -dev /dev/fb2 »</command>." - -#: ../C/gdm.xml:5726(para) -msgid "" -"The display will not actually be started until the display is released by " -"calling <command>gdmdynamic</command> again with the -r option." -msgstr "" -"L'affichage n'est pas réellement démarré tant que l'affichage n'a pas été " -"libéré en appelant une nouvelle fois <command>gdmdynamic</command> avec " -"l'option -r." - -#: ../C/gdm.xml:5734(term) -msgid "-r" -msgstr "-r" - -#: ../C/gdm.xml:5736(para) -msgid "Release (run) all displays waiting in the DISPLAY_CONFIG state." -msgstr "" -"Libère (exécute) tous les affichages en attente dans l'état DISPLAY_CONFIG." - -#: ../C/gdm.xml:5743(term) -msgid "-d display" -msgstr "-d affichage" - -#: ../C/gdm.xml:5745(para) -msgid "" -"Delete a display, killing the X server and purging the display " -"configuration. For example, \"-d 3\"." -msgstr "" -"Supprime un affichage, tuant le serveur X et nettoyant la configuration " -"d'affichage. Par exemple, « -d 3 »." - -#: ../C/gdm.xml:5753(term) -msgid "-l [pattern]" -msgstr "-l [motif]" - -#: ../C/gdm.xml:5755(para) -msgid "" -"List displays via the ATTACHED_SERVERS <command>gdmflexiserver</command> " -"command. Without a pattern lists all attached displays. With a pattern will " -"match using glob characters '*', '?', and '[]'. For example: <command>\"-l " -"Standard*\"</command><command>\"-l *Xorg*\"</command>" -msgstr "" -"Énumère les affichages via la commande ATTACHED_SERVERS de " -"<command>gdmflexiserver</command>. Sans motif, énumère tous les affichages " -"liés. Avec un motif, recherche les affichages liés correspondant au motif, " -"avec les caractères d'expansion « * », « ? » et « [] ». Par exemple : " -"<command>« -l Standard* »</command> ou <command>« -l *Xorg* »</command>." - -#: ../C/gdm.xml:5767(term) -msgid "-v" -msgstr "-v" - -#: ../C/gdm.xml:5769(para) -msgid "Verbose mode. Prints diagnostic messages. to GDM." -msgstr "Mode bavard. Affiche des messages de diagnostic." - -#: ../C/gdm.xml:5777(term) -msgid "-b" -msgstr "-b" - -#: ../C/gdm.xml:5779(para) -msgid "Background mode. Fork child to do the work and return immediately." -msgstr "" -"Mode arrière-plan. Génère un processus fils dédié à la tâche, puis retourne " -"immédiatement au shell." - -#: ../C/gdm.xml:5786(term) -msgid "-t RETRY" -msgstr "-t ESSAIS" - -#: ../C/gdm.xml:5788(para) -msgid "" -"If the daemon socket is busy, <command>gdmdynamic</command> will retry to " -"open the connection the specified RETRY number of times. Default value is 15." -msgstr "" -"Si le socket du démon est occupé, <command>gdmdynamic</command> essaie à " -"nouveau d'ouvrir la connexion le nombre de fois indiqué par ESSAIS. La " -"valeur par défaut est 15." - -#: ../C/gdm.xml:5797(term) -msgid "-s SLEEP" -msgstr "-s TEMPS" - -#: ../C/gdm.xml:5799(para) -msgid "" -"If the daemon socket is busy, <command>gdmdynamic</command> 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 "" -"Si le socket du démon est occupé, <command>gdmdynamic</command> se met en " -"veille un certain temps entre chaque tentative. Un nombre de secondes " -"aléatoire entre 0 et 5 est ajouté à la valeur TEMPS pour aider à s'assurer " -"que les différents appels à gdmdynamic n'essaient pas tous de se connecter " -"en même temps. Une valeur TEMPS de 0 produit un temps de veille de 1 " -"seconde. La valeur par défaut est de 8 secondes." - -#: ../C/gdm.xml:5814(title) -msgid "<command>gdmphotosetup</command> Command Line Options" -msgstr "Options en ligne de commande de <command>gdmphotosetup</command>" - -#: ../C/gdm.xml:5816(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 " -"<filename>~/.face</filename>. This command accepts standard GNOME options." -msgstr "" -"Permet à l'utilisateur de sélectionner une image qui sera utilisée par GDM " -"pour représenter l'utilisateur dans le navigateur de figures, s'il est " -"activé par GDM. Le fichier sélectionné est enregistré dans <filename>~/." -"face</filename>. Cette commande accepte les options GNOME standards." - -#: ../C/gdm.xml:5825(title) -msgid "<command>gdmthemetester</command> Command Line Options" -msgstr "Options en ligne de commande de <command>gdmthemetester</command>" - -#: ../C/gdm.xml:5827(para) -msgid "" -"<command>gdmthemetester</command> 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. <command>gdmthemetester</" -"command> requires that the system support <command>gdmXnest</command>. Note " -"that themes can display differently depending on the theme's \"Show mode\". " -"<command>gdmthemetester</command> allows viewing the themes in different " -"modes via the environment option. Valid environment values and their " -"meanings follow: <screen>\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" -"</screen>" -msgstr "" -"<command>gdmthemetester</command> prend deux paramètres. Le premier définit " -"l'environnement alors que le second indique le chemin ou le nom du thème à " -"visualiser. C'est un outil pour visualiser un thème en dehors de GDM. Il est " -"utile pour tester ou visualiser des thèmes. <command>gdmthemetester</" -"command> exige la prise en charge de <command>gdmXnest</command> par le " -"système. Il faut relever que les thèmes peuvent s'afficher différemment " -"selon leur mode d'affichage. <command>gdmthemetester</command> permet de " -"voir les thèmes dans différents modes par l'option d'environnement. Les " -"valeurs d'environnement possibles ainsi que leur signification sont les " -"suivantes : <screen>\n" -"console - En mode console.\n" -"console-timed - En mode console non flexible.\n" -"flexi - En mode flexible.\n" -"xdmcp - En mode distant (XDMCP).\n" -"remote-flexi - En mode distant et flexible (XDMCP).\n" -"</screen>" - -#: ../C/gdm.xml:5853(title) -msgid "GDM Root User Commands" -msgstr "Commandes GDM pour l'administrateur (root)" - -#: ../C/gdm.xml:5855(para) -msgid "" -"The GDM package provides the following different commands in " -"<filename>sbindir</filename> intended to be used by the root user:" -msgstr "" -"Le paquet GDM fournit les différentes commandes ci-après dans " -"<filename>bindir</filename>, à l'intention de l'administrateur (root) :" - -#: ../C/gdm.xml:5861(title) ../C/gdm.xml:5877(title) -msgid "" -"<command>gdm</command> and <command>gdm-binary</command> Command Line Options" -msgstr "" -"Options en ligne de commande de <command>gdm</command> et <command>gdm-" -"binary</command>" - -#: ../C/gdm.xml:5864(para) -msgid "" -"The <command>gdm</command> command is really just a script which runs the " -"<command>gdm-binary</command>, passing along any options. Before launching " -"<command>gdm-binary</command>, the gdm wrapper script will source the " -"<filename><etc>/profile</filename> file to set the standard system " -"environment variables. In order to better support internationalization, it " -"will also set the LC_MESSAGES environment variable to LANG if neither " -"LC_MESSAGES or LC_ALL are set. If you really need to set some additional " -"environment before launching GDM, you can do so in this script." -msgstr "" -"La commande <command>gdm</command> n'est en fait qu'un script qui lance " -"<command>gdm-binary</command>, en lui passant des options. Avant de lancer " -"<command>gdm-binary</command>, le script « façade » gdm va sourcer le " -"fichier <filename><etc>/profile</filename> pour paramétrer les " -"variables d'environnement standards du système. Pour mieux prendre en compte " -"l'internationalisation, il définit aussi la variable d'environnement " -"LC_MESSAGES à LANG si ni LC_MESSAGES, ni LC_ALL ne sont définies. Si vous " -"avez vraiment besoin de paramétrer davantage l'environnement avant de lancer " -"GDM, vous pouvez le faire dans ce script." - -#: ../C/gdm.xml:5881(term) -msgid "--help" -msgstr "--help" - -#: ../C/gdm.xml:5883(para) -msgid "Gives a brief overview of the command line options." -msgstr "Donne un bref aperçu des options en ligne de commande." - -#: ../C/gdm.xml:5890(term) -msgid "--nodaemon" -msgstr "--nodaemon" - -#: ../C/gdm.xml:5892(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 "" -"Si cette option est présente, GDM ne génère pas de processus en arrière-plan " -"lorsqu'il est lancé. Vous pouvez aussi utiliser ce paramètre avec un seul " -"tiret, « -nodaemon », pour des raisons de compatibilité avec d'autres " -"gestionnaires de connexions." - -#: ../C/gdm.xml:5902(term) -msgid "--no-console" -msgstr "--no-console" - -#: ../C/gdm.xml:5904(para) -msgid "" -"Tell the daemon that it should not run anything on the console. This means " -"that none of the attached servers from the <filename>[servers]</filename> " -"section will be started, and the console will not be used for communicating " -"errors to the user. An empty <filename>[servers]</filename> section " -"automatically implies this option." -msgstr "" -"Signale au démon qu'il ne doit rien exécuter sur la console. Cela signifie " -"qu'aucun des serveurs liés de la section <filename>[servers]</filename> ne " -"sera lancé, et que la console ne sera pas utilisée pour communiquer des " -"erreurs à l'utilisateur. Une section <filename>[servers]</filename> vide " -"implique automatiquement cette option." - -#: ../C/gdm.xml:5916(term) -msgid "--config=CONFIGFILE" -msgstr "--config=FICHIER_DE_CONFIGURATION" - -#: ../C/gdm.xml:5918(para) -msgid "Specify an alternative configuration file." -msgstr "Indique un fichier de configuration alternatif." - -#: ../C/gdm.xml:5925(term) -msgid "--preserve-ld-vars" -msgstr "--preserve-ld-vars" - -#: ../C/gdm.xml:5927(para) -msgid "" -"When clearing the environment internally, preserve all variables starting " -"with LD_. This is mostly for debugging purposes." -msgstr "" -"Lors du nettoyage interne de l'environnement, préserve toutes les variables " -"commençant pas LD_. C'est essentiellement utilisé pour des raisons de " -"débogage." - -#: ../C/gdm.xml:5935(term) -msgid "--version" -msgstr "--version" - -#: ../C/gdm.xml:5937(para) -msgid "Print the version of the GDM daemon." -msgstr "Affiche la version du démon GDM." - -#: ../C/gdm.xml:5944(term) -msgid "--wait-for-go" -msgstr "--wait-for-go" - -#: ../C/gdm.xml:5946(para) -msgid "" -"If started with this option, gdm will init, but only start the first " -"attached 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 "" -"Lorsqu'il est démarré avec cette option, GDM s'initialise, mais ne démarre " -"que le premier affichage lié, puis attend de recevoir un message GO par le " -"protocole FIFO. Aucune bannière n'apparaît avant que le message GO soit " -"reçu. Les requêtes flexiserver sont aussi refusées et XDMCP ne démarre pas " -"avant de recevoir le message GO. C'est utile pour les scripts " -"d'initialisation qui souhaitent démarrer X rapidement, mais qui ne veulent " -"pas que l'utilisateur puisse se connecter tout de suite. Ainsi, le script " -"envoie la commande GO par FIFO dès qu'il est prêt, et GDM continue dès cet " -"instant. Cette fonctionnalité a été ajoutée dans la version 2.5.90.0." - -#: ../C/gdm.xml:5964(title) -msgid "<command>gdmsetup</command> Command Line Options" -msgstr "Options en ligne de commande de <command>gdmsetup</command>" - -#: ../C/gdm.xml:5966(para) -msgid "" -"<command>gdmsetup</command> 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 <command>gdmsetup</command> 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 "" -"<command>gdmsetup</command> lance une application graphique pour modifier le " -"fichier de configuration de GDM. Normalement, sur les systèmes qui prennent " -"en charge « PAM userhelper », le système est paramétré de telle façon que " -"lorsqu'un utilisateur ordinaire lance <command>gdmsetup</command>, le mot de " -"passe administrateur (root) lui est demandé. Sinon, l'application ne peut " -"être exécutée que par root. Cette application gère les options standards de " -"GNOME." - -#: ../C/gdm.xml:5978(title) -msgid "<command>gdm-restart</command> Command Line Options" -msgstr "Options en ligne de commande de <command>gdm-restart</command>" - -#: ../C/gdm.xml:5980(para) -msgid "" -"<command>gdm-restart</command> stops and restarts GDM by sending the GDM " -"daemon a HUP signal. This command will immediately terminate all sessions " -"and log out users currently logged in with GDM." -msgstr "" -"<command>gdm-restart</command> arrête et redémarre GDM en envoyant un signal " -"HUP au démon GDM. Cette commande ferme immédiatement toutes les sessions et " -"déconnecte les utilisateurs actuellement connectés avec GDM." - -#: ../C/gdm.xml:5988(title) -msgid "<command>gdm-safe-restart</command> Command Line Options" -msgstr "Options en ligne de commande de <command>gdm-safe-restart</command>" - -#: ../C/gdm.xml:5990(para) -msgid "" -"<command>gdm-safe-restart</command> stops and restarts GDM by sending the " -"GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out." -msgstr "" -"<command>gdm-safe-restart</command> arrête et redémarre GDM en envoyant un " -"signal USR1 au démon GDM. GDM sera redémarré dès que tous les utilisateurs " -"se seront déconnectés." - -#: ../C/gdm.xml:5998(title) -msgid "<command>gdm-stop</command> Command Line Options" -msgstr "Options en ligne de commande de <command>gdm-stop</command>" - -#: ../C/gdm.xml:6000(para) -msgid "" -"<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM " -"signal." -msgstr "" -"<command>gdm-stop</command> arrête GDM en envoyant un signal TERM au démon " -"GDM." - -#: ../C/gdm.xml:6008(title) -msgid "GDM Internal Commands" -msgstr "Commandes internes de GDM" - -#: ../C/gdm.xml:6010(para) -msgid "" -"The GDM package provides the following different commands in " -"<filename>libexecdir</filename> intended to be used by the gdm daemon " -"process." -msgstr "" -"Le paquet GDM fournit les différentes commandes ci-après dans " -"<filename>libexecdir</filename> à l'intention du processus démon de GDM." - -#: ../C/gdm.xml:6017(title) -msgid "" -"<command>gdmchooser</command> and <command>gdmlogin</command> Command Line " -"Options" -msgstr "" -"Options en ligne de commande de <command>gdmchooser</command> et " -"<command>gdmlogin</command>" - -#: ../C/gdm.xml:6020(para) -msgid "" -"The <command>gdmgreeter</command> and <command>gdmlogin</command> are two " -"different login applications, either can be used by GDM. " -"<command>gdmgreeter</command> is themeable with GDM themes while " -"<command>gdmlogin</command> is themable with GTK+ themes. These applications " -"are normally executed by the GDM daemon. Both commands support standard " -"GNOME options." -msgstr "" -"<command>gdmgreeter</command> et <command>gdmlogin</command> sont deux " -"applications de connexion différentes, qui peuvent toutes deux être " -"utilisées par GDM. <command>gdmgreeter</command> peut être adapté avec des " -"thèmes GDM, alors que <command>gdmlogin</command> peut être adapté avec des " -"thèmes GTK+. En principe, ces applications sont exécutées par le démon GDM. " -"Les deux commandes gèrent les options standards de GNOME." - -#: ../C/gdm.xml:6031(title) ../C/gdm.xml:6041(title) -msgid "<command>gdmchooser</command> Command Line Options" -msgstr "Options en ligne de commande de <command>gdmchooser</command>" - -#: ../C/gdm.xml:6033(para) -msgid "" -"The <command>gdmchooser</command> is the XDMCP chooser application. The " -"<command>gdmchooser</command> is normally executed by the GDM daemon. It " -"supports the following options for XDM compatibility. This command supports " -"standard GNOME options." -msgstr "" -"<command>gdmchooser</command> est l'application du sélecteur de XDMCP. C'est " -"une commande qui est en principe exécutée par le démon GDM. Elle prend en " -"charge les options ci-après pour être compatible avec XDM. Cette commande " -"gère les options standards de GNOME." - -#: ../C/gdm.xml:6044(term) -msgid "--xdmaddress=SOCKET" -msgstr "--xdmaddress=SOCKET" - -#: ../C/gdm.xml:6046(para) -msgid "Socket for XDM communication." -msgstr "Socket pour communiquer avec XDM." - -#: ../C/gdm.xml:6053(term) -msgid "--clientaddress=ADDRESS" -msgstr "--clientaddress=ADRESSE" - -#: ../C/gdm.xml:6055(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 "" -"Adresse du client à renvoyer en réponse à XDM. Cette option sert à lancer " -"gdmchooser avec XDM, mais n'est pas utilisée avec GDM." - -#: ../C/gdm.xml:6063(term) -msgid "--connectionType=TYPE" -msgstr "--connectionType=TYPE" - -#: ../C/gdm.xml:6065(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 "" -"Type de connexion à renvoyer en réponse à XDM. Cette option sert à lancer " -"gdmchooser avec XDM, mais n'est pas utilisée avec GDM." - -#: ../C/gdm.xml:6075(command) -msgid "gdm-ssh-session" -msgstr "gdm-ssh-session" - -#: ../C/gdm.xml:6077(para) -msgid "" -"The <command>gdm-ssh-session</command> is normally executed by the GDM " -"daemon when starting a secure remote connection through ssh. It does not " -"take any options." -msgstr "" -"La commande <command>gdm-ssh-session</command> est normalement exécutée par " -"le démon GDM lors du lancement d'une connexion distante sécurisée par SSH. " -"Elle ne prend aucune option." - -#: ../C/gdm.xml:6089(title) -msgid "Themed Greeter" -msgstr "Bannière avec thème" - -#: ../C/gdm.xml:6091(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 <ulink type=\"http\" url=\"http://art.gnome.org/themes/" -"gdm_greeter/\"> the theme website</ulink>." -msgstr "" -"Cette section décrit la création de thèmes pour la bannière avec thème. Pour " -"obtenir des exemples contenant des captures d'écran, examinez les thèmes " -"standards installés et les thèmes du <ulink type=\"http\" url=\"http://art." -"gnome.org/themes/gdm_greeter/\">site Web des thèmes</ulink>." - -#: ../C/gdm.xml:6100(title) -msgid "Theme Overview" -msgstr "Aperçu des thèmes" - -#: ../C/gdm.xml:6102(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 <filename><share>/gdm/themes/<theme_name></filename>. " -"Usually this would be under <filename>/usr/share</filename>. The theme " -"directory should contain a file called <filename>GdmGreeterTheme.desktop</" -"filename> which has similar format to other .desktop files and looks like:" -msgstr "" -"Les thèmes GDM peuvent être créés en produisant un fichier XML respectant la " -"spécification gui/greeter/greeter.dtd. Les fichiers de thèmes sont " -"enregistrées dans le répertoire <filename><share>/gdm/themes/<" -"nom_du_thème></filename>. En principe, ils sont dans <filename>/usr/" -"share</filename>. Le répertoire du thème doit contenir un fichier nommé " -"<filename>GdmGreeterTheme.desktop</filename>, d'un format similaire aux " -"autres fichiers .desktop, et qui ressemble à ceci :" - -#: ../C/gdm.xml:6113(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 "" -"\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" - -#: ../C/gdm.xml:6124(para) -msgid "" -"The Name, Description, Author and Copyright fields can be translated just " -"like the other <filename>.desktop</filename>files. 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 "" -"Les champs Name, Description, Author and Copyright peuvent être traduits " -"comme pour les autres fichiers <filename>.desktop</filename>. Tous les " -"fichiers mentionnés doivent se trouver dans le répertoire du thème lui-même. " -"Le champ Screenshot indique un fichier qui doit représenter une capture " -"d'écran de 200x150 pixels du thème en action (il peut ne pas y en avoir, " -"mais c'est toujours apprécié des utilisateurs). Le champ Greeter indique un " -"fichier XML contenant la description du thème. La description est présentée " -"plus loin." - -#: ../C/gdm.xml:6134(para) -msgid "" -"Once a theme is installed, it can be tested with the " -"<command>gdmthemetester</command> program. This program assumes that the X " -"server supports a nested server command. This command takes two arguments, " -"first the environment that should be used. The environment can be one of the " -"following values: console, console-timed, flexi, remote-flexi, or xdmcp. The " -"\"console\" option tests the theme as it would be shown on an attached " -"display. The \"console-timed\" option tests the theme as it would be shown " -"on an attached display with timed login enabled. The \"flexi\" option tests " -"the theme as it would be shown on an attached flexible display (such as " -"started via Xnest). Finally, the \"xdmcp\" option tests the theme as it " -"would be shown for remote XDMCP displays. The second argument is the theme " -"name. For example, to test how the circles theme would look in XDMP remote " -"display mode, you would run the following command:" -msgstr "" -"Une fois qu'un thème est installé, vous pouvez le tester avec le programme " -"<command>gdmthemetester</command>. Ce programme présuppose que le serveur X " -"prend en charge une commande de serveur imbriqué. La commande prend deux " -"arguments. En premier, l'environnement qui doit être utilisé. Les valeurs " -"possibles sont console, console-timed, flexi, remote-flexi, xdmcp. L'option " -"« console » teste le thème comme s'il apparaissait sur un affichage lié. " -"L'option « console-timed » teste le thème comme s'il apparaissait sur un " -"affichage lié avec connexion différée. L'option « flexi » teste le thème " -"comme s'il apparaissait sur un affichage lié flexible (comme s'il était " -"lancé via Xnest). Finalement, l'option « xdmcp » teste le thème comme s'il " -"apparaissait sur un affichage XDMCP distant. Le second argument est le nom " -"du thème. Ainsi, par exemple, pour tester l'aspect du thème « circles » en " -"mode d'affichage distant XDMCP, vous devez exécuter :" - -#: ../C/gdm.xml:6153(command) -msgid "gdmthemetester xdmcp circles" -msgstr "gdmthemetester xdmcp circles" - -#: ../C/gdm.xml:6156(para) -msgid "" -"When developing a theme, make sure to test all the environments, and make " -"sure to test how the caps lock warning looks by pressing the caps lock key. " -"Running <command>gdmthemetester</command> is also a good way to take " -"screenshots of GDM themes. Simply take a screenshot of the theme running in " -"the nested display window. This can be done in GNOME by focusing the nested " -"login window and pressing Alt-PrintScreen." -msgstr "" -"Lorsque vous développez un thème, èrenez soin de tester tous les " -"environnements et prenez garde à l'aspect de l'avertissement concernant le " -"verrouillage majuscule lorsque vous appuyez sur cette touche. " -"<command>gdmthemetester</command> est également une bonne méthode pour " -"prendre des captures d'écran des thèmes GDM, car il suffit de capturer " -"l'image de la fenêtre de l'affichage imbriqué. On peut le faire dans GNOME " -"en activant la fenêtre concernée et en appuyant sur Alt-Impr écran." - -#: ../C/gdm.xml:6165(para) -msgid "" -"Once a theme has been fully tested, then make a tarball that contains the " -"directory as it would be insatlled to the <filename><share>/gdm/" -"themes</filename> directory. This is the standard format for distributing " -"GDM themes." -msgstr "" -"Quand un thème a été complètement testé, créez l'archive tar contenant le " -"répertoire tel qu'il doit être installé dans le répertoire <filename><" -"share>/gdm/themes</filename>. C'est le format standard pour la " -"distribution de thèmes GDM." - -#: ../C/gdm.xml:6174(title) -msgid "Detailed Description of Theme XML format" -msgstr "Description détaillée du format XML de thème" - -#: ../C/gdm.xml:6177(title) -msgid "greeter tag" -msgstr "Balise greeter" - -#: ../C/gdm.xml:6179(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 "" -"Le format de thème GDM est exprimé en format XML, contenu dans une balise " -"<greeter>. Vous pouvez indiquer qu'un thème GTK+ doit être utilisé " -"avec ce thème en exploitant l'élément gtk-theme dans la balise greeter, " -"comme dans l'exemple suivant." - -#: ../C/gdm.xml:6186(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 "" -"\n" -"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" -"<!DOCTYPE greeter SYSTEM \"greeter.dtd\">\n" -"<greeter gtk-theme=\"Crux\">\n" -"[...]\n" -"</greeter>\n" - -#: ../C/gdm.xml:6194(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 "" -"À l'intérieur de la balise greeter, on peut trouver les nœuds décrits dans " -"les sections suivantes de ce document. Certains de ces nœuds sont des " -"conteneurs (nœuds boîtes, nœuds d'éléments rectangulaires) qui peuvent être " -"utilisés pour organiser l'affichage des nœuds que l'utilisateur perçoit et " -"avec lesquels il interagit (tels que les nœuds boutons, images et zones de " -"saisie)." - -#: ../C/gdm.xml:6204(title) -msgid "Box Nodes" -msgstr "Nœuds boîtes (box)" - -#: ../C/gdm.xml:6206(para) -msgid "" -"Box nodes are container nodes for item nodes. Box nodes are specified as " -"follows: <screen>\n" -"<box orientation=\"alignment\" min-width=\"num\"\n" -"xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -"homogeneous=\"bool\">\n" -"</screen> 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 "" -"Les nœuds boîtes sont des conteneurs pour les nœuds éléments. Ils se " -"présentent comme suit : <screen>\n" -"<box orientation=\"alignement\" min-width=\"num\"\n" -"xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -"homogeneous=\"bool\">\n" -"</screen> où « num » représente un nombre et « bool » représente soit " -"« true » (vrai) ou « false » (faux). La valeur « alignement » peut être " -"« horizontal » ou « vertical ». Si vous ne spécifiez pas une propriété, la " -"valeur par défaut qui sera utilisée est 0 pour les valeurs numériques, " -"« false » pour la propriété « homogeneous » et « vertical » pour " -"l'orientation." - -#: ../C/gdm.xml:6222(para) -msgid "" -"If the box is homogeneous then the children are allocated equal amount of " -"space." -msgstr "" -"Si la valeur de la propriété « homogeneous » de la boîte est « true », les " -"nœuds enfants reçoivent tous une quantité égale d'espace." - -#: ../C/gdm.xml:6227(para) -msgid "" -"The \"min-width\" must be specified in pixels. Obviously there is also a " -"corresponding \"min-height\" property as well." -msgstr "" -"La propriété « min-width » (largeur minimale) est spécifiée en pixels. Il en " -"est évidemment de même pour la propriété « min-height » (hauteur minimale)." - -#: ../C/gdm.xml:6235(title) -msgid "Fixed Nodes" -msgstr "Nœuds fixes (fixed)" - -#: ../C/gdm.xml:6237(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: <screen>\n" -"<fixed>\n" -"</screen> Then you put other items with proper position nodes inside this." -msgstr "" -"Un nœud fixe est un conteneur dont les divers nœuds enfants sont disposés à " -"l'aide de coordonnées précises. La taille de ce conteneur est déterminée par " -"le rectangle englobant tous les enfants. Ce nœud n'a pas de propriétés " -"supplémentaires. Il suffit donc d'écrire : <screen>\n" -"<fixed>\n" -"</screen> Puis vous placez à l'intérieur les autres éléments avec les " -"postions précises des nœuds." - -#: ../C/gdm.xml:6248(para) -msgid "The \"toplevel\" node is really just like a fixed node." -msgstr "Le nœud de premier niveau est en fait comme un nœud fixe." - -#: ../C/gdm.xml:6254(title) -msgid "Item Nodes" -msgstr "Nœuds éléments (item)" - -#: ../C/gdm.xml:6256(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 "" -"Un thème GDM est créé en constituant une hiérarchie de nœuds éléments et " -"nœuds boîtes. La propriété « type » des nœuds éléments peut contenir les " -"valeurs suivantes :" - -#: ../C/gdm.xml:6264(term) -msgid "button" -msgstr "button" - -#: ../C/gdm.xml:6266(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 "" -"Un champ bouton. Ce champ utilise un bouton GTK+. Il est aussi possible " -"qu'un élément de type « rect » se comporte comme un bouton en définissant " -"son élément « button » à « true ». Cependant, il est préférable d'utiliser " -"des boutons GTK+ dans les thèmes GDM car ils sont accessibles aux " -"utilisateurs ayant des handicaps. Les boutons GTK+ sont aussi susceptibles " -"d'être adaptés avec des thèmes. Cette fonctionnalité est prise en charge à " -"partir de la version GDM 2.14.6." - -#: ../C/gdm.xml:6278(term) -msgid "entry" -msgstr "entry" - -#: ../C/gdm.xml:6280(para) -msgid "Text entry field." -msgstr "Champ de saisie de texte." - -#: ../C/gdm.xml:6287(term) -msgid "label" -msgstr "label" - -#: ../C/gdm.xml:6289(para) -msgid "A text label. Must have a \"text\" node to specify the text." -msgstr "" -"Une étiquette de texte. Elle doit comporter un nœud « text » pour préciser " -"le texte." - -#: ../C/gdm.xml:6297(term) -msgid "list" -msgstr "list" - -#: ../C/gdm.xml:6299(para) -msgid "" -"A face browser widget. Only useful if the face browser is enabled via the " -"configuration." -msgstr "" -"Un widget du navigateur de figure. Utile uniquement si le navigateur de " -"figures est activé par la configuration." - -#: ../C/gdm.xml:6307(term) -msgid "pixmap" -msgstr "pixmap" - -#: ../C/gdm.xml:6309(para) -msgid "" -"An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, " -"etc...)" -msgstr "" -"Une image pixmap dans un format pris en charge par gdk-pixbuf, tel que PNG, " -"JPEG, Tiff, etc." - -#: ../C/gdm.xml:6317(term) -msgid "rect" -msgstr "rect" - -#: ../C/gdm.xml:6319(para) -msgid "Rectangle." -msgstr "Un rectangle." - -#: ../C/gdm.xml:6326(term) -msgid "svg" -msgstr "svg" - -#: ../C/gdm.xml:6328(para) -msgid "Scaled Vector Graphic image." -msgstr "Image SVG (Scaled Vector Graphic)." - -#: ../C/gdm.xml:6335(para) -msgid "" -"For example: <screen>\n" -"<item type=\"label\">\n" -"</screen> 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 "" -"Par exemple : <screen>\n" -"<item type=\"label\">\n" -"</screen> Les éléments peuvent contenir des valeurs d'identifiant (ID) leur " -"donnant une apparence ou un format spécifique. De plus, vous pouvez " -"personnaliser le processus de connexion en ajoutant des widgets " -"personnalisés avec des identifiants personnalisés pour certains éléments " -"(actuellement pour l'élément « list » uniquement)." - -#: ../C/gdm.xml:6346(para) -msgid "Entry items can have id values as follows:" -msgstr "Les éléments « entry » peuvent posséder les valeurs « id » suivantes :" - -#: ../C/gdm.xml:6352(term) -msgid "user-pw-entry" -msgstr "user-pw-entry" - -#: ../C/gdm.xml:6354(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 "" -"Champ de saisie pour l'identifiant de l'utilisateur et le mot de passe. " -"C'est le champ utilisé pour répondre aux questions PAM/GDM (nom " -"d'utilisateur, mot de passe, etc.)" - -#: ../C/gdm.xml:6363(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 "" -"Par défaut, les éléments de liste apparaissent sous forme de liste standard, " -"mais l'attribut combo=\"true\" permet de transformer la liste en liste " -"déroulante (pris en charge à partir de GDM 2.16.2). Certaines listes " -"prédéfinies peuvent être inclues dans un thème en utilisant les valeurs id " -"ci-après. Il est aussi possible de définir des listes personnalisées, ce qui " -"est expliqué plus loin." - -#: ../C/gdm.xml:6373(term) -msgid "session" -msgstr "session" - -#: ../C/gdm.xml:6375(para) -msgid "" -"A list of available sessions, which allows the user to pick the session to " -"use. Supported since GDM 2.16.2." -msgstr "" -"Une liste des sessions disponibles, ce qui permet à l'utilisateur de choisir " -"la session qu'il souhaite utiliser. Pris en charge depuis GDM 2.16.2." - -#: ../C/gdm.xml:6385(term) -msgid "language" -msgstr "language" - -#: ../C/gdm.xml:6387(para) -msgid "" -"A list of available languages, which allows the user to pick the language to " -"use. Supported since GDM 2.16.2." -msgstr "" -"Une liste des langues disponibles, ce qui permet à l'utilisateur de choisir " -"la langue qu'il souhaite utiliser. Pris en charge depuis GDM 2.16.2." - -#: ../C/gdm.xml:6397(term) -msgid "userlist" -msgstr "userlist" - -#: ../C/gdm.xml:6399(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 "" -"Une liste du navigateur de figures permettant aux utilisateurs de choisir " -"leur nom d'utilisateur en cliquant dans la liste plutôt qu'en le saisissant " -"au clavier. Évidemment, cela expose les noms d'utilisateurs à ceux qui " -"peuvent voir l'écran de connexion. Ce n'est donc pas recommandé à ceux qui " -"pensent que cela restreint la sécurité. Le navigateur de figures ne prend " -"pas en charge les listes déroulantes." - -#: ../C/gdm.xml:6412(term) -msgid "userlist-rect" -msgstr "userlist-rect" - -#: ../C/gdm.xml:6414(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 "" -"Cet identifiant peut qualifier un objet <rect> contenant la liste des " -"utilisateurs. Si cette liste est vide, le rectangle n'apparaît pas. Cela " -"permet au thème de définir une zone avec une couleur ou une couche alpha " -"différente entourant la liste des utilisateurs, uniquement si celle-ci " -"contient des éléments. Pris en charge depuis la version 2.16.2." - -#: ../C/gdm.xml:6426(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 "" -"De plus, il est possible de définir un identifiant arbitraire (il est " -"recommandé de le préfixer avec « custom » pour qu'il n'entre pas en conflit " -"avec de futurs ajouts à cette spécification) et de demander des informations " -"supplémentaires concernant l'utilisateur. Consultez la section « Widgets " -"personnalisés »." - -#: ../C/gdm.xml:6433(para) -msgid "Label items can have id values as follows:" -msgstr "Les éléments « label » peuvent contenir les valeurs « id » suivantes :" - -#: ../C/gdm.xml:6439(term) -msgid "clock" -msgstr "clock" - -#: ../C/gdm.xml:6441(para) -msgid "Label that displays the date and time." -msgstr "Étiquette affichant la date et l'heure." - -#: ../C/gdm.xml:6448(term) -msgid "pam-prompt" -msgstr "pam-prompt" - -#: ../C/gdm.xml:6450(para) -msgid "" -"Label that displays the PAM prompt. This is the prompt that PAM uses to ask " -"for username, password, etc..." -msgstr "" -"Étiquette affichant l'invite de PAM. C'est l'invite que PAM utilise pour " -"demander le nom d'utilisateur, le mot de passe, etc." - -#: ../C/gdm.xml:6458(term) -msgid "pam-error" -msgstr "pam-error" - -#: ../C/gdm.xml:6460(para) -msgid "" -"Label that displayst PAM/GDM error messages. Such as when user can't log in." -msgstr "" -"Étiquette affichant les messages d'erreur de PAM et GDM. Comme par exemple " -"lorsqu'un utilisateur ne peut pas se connecter." - -#: ../C/gdm.xml:6468(term) -msgid "pam-error-logo" -msgstr "pam-error-logo" - -#: ../C/gdm.xml:6470(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 "" -"Une image affichée uniquement lorsqu'un message « pam-error » apparaît. Ceci " -"est utile pour l'affichage d'une icône « Attention », par exemple. Cette " -"fonctionnalité est prise en charge à partir de GDM 2.14.6." - -#: ../C/gdm.xml:6480(term) -msgid "pam-message" -msgstr "pam-message" - -#: ../C/gdm.xml:6482(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 "" -"Étiquette affichant un message PAM. Ce sont des messages que PAM ou GDM " -"produisent au sujet de l'état d'un compte ou pour donner de l'aide sur " -"l'invite ou pour d'autres informations." - -#: ../C/gdm.xml:6491(term) -msgid "timed-label" -msgstr "timed-label" - -#: ../C/gdm.xml:6493(para) -msgid "Label that displays timed login information." -msgstr "Étiquette affichant des informations sur la connexion différée." - -#: ../C/gdm.xml:6500(para) -msgid "Rectangles can have id values as follows:" -msgstr "Les rectangles peuvent contenir les valeurs « id » suivantes :" - -#: ../C/gdm.xml:6506(term) -msgid "caps-lock-warning" -msgstr "caps-lock-warning" - -#: ../C/gdm.xml:6508(para) -msgid "" -"Displays an icon that shows if the CAPS LOCK key is depressed. This " -"rectangle will be hidden/shown appropriately" -msgstr "" -"Affiche une icône signalant si la touche Verrouillage majuscule est " -"enfoncée. Ce rectangle est masqué et affiché de manière adéquate." - -#: ../C/gdm.xml:6517(para) -msgid "" -"If an item is of type rect, the item can be a button. Buttons must also " -"include a \"button\" value as follows: <screen>\n" -"<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n" -"</screen>" -msgstr "" -"Si un élément est de type « rect », ce peut être un bouton. Les boutons " -"doivent aussi contenir une valeur « button » comme dans l'exemple suivant : " -"<screen>\n" -"<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n" -"</screen>" - -#: ../C/gdm.xml:6525(para) -msgid "Possible values for button ids are as follows." -msgstr "" -"Les valeurs possibles de la propriété « id » des boutons sont les suivantes :" - -#: ../C/gdm.xml:6531(term) -msgid "chooser_button" -msgstr "chooser_button" - -#: ../C/gdm.xml:6533(para) -msgid "Runs the XDMCP chooser." -msgstr "Lance le sélecteur XDMCP." - -#: ../C/gdm.xml:6540(term) -msgid "config_button" -msgstr "config_button" - -#: ../C/gdm.xml:6542(para) -msgid "Runs the GDM configuration application." -msgstr "Lance l'application de configuration de GDM." - -#: ../C/gdm.xml:6549(term) -msgid "custom_cmd_button[0-9]" -msgstr "custom_cmd_button[0-9]" - -#: ../C/gdm.xml:6551(para) -msgid "Runs the <filename>n-th</filename> custom command." -msgstr "Lance la commande personnalisée n (0-9)." - -#: ../C/gdm.xml:6558(term) -msgid "disconnect_button" -msgstr "disconnect_button" - -#: ../C/gdm.xml:6560(para) -msgid "Disconnect from remote session." -msgstr "Déconnecte de la session distante." - -#: ../C/gdm.xml:6567(term) -msgid "language_button" -msgstr "language_button" - -#: ../C/gdm.xml:6569(para) -msgid "Displays the language selection dialog." -msgstr "Affiche la boîte de dialogue de sélection de langue." - -#: ../C/gdm.xml:6576(term) -msgid "halt_button" -msgstr "halt_button" - -#: ../C/gdm.xml:6578(para) -msgid "Halt (shuts down) the system." -msgstr "Arrête (éteint) le système." - -#: ../C/gdm.xml:6585(term) -msgid "reboot_button" -msgstr "reboot_button" - -#: ../C/gdm.xml:6587(para) -msgid "Restart the system." -msgstr "Redémarre le système." - -#: ../C/gdm.xml:6594(term) -msgid "session_button" -msgstr "session_button" - -#: ../C/gdm.xml:6596(para) -msgid "List and select from available sessions." -msgstr "Affiche la liste permettant de sélectionner une session." - -#: ../C/gdm.xml:6603(term) -msgid "suspend_button" -msgstr "suspend_button" - -#: ../C/gdm.xml:6605(para) -msgid "Suspend the system." -msgstr "Met en veille le système." - -#: ../C/gdm.xml:6612(term) -msgid "system_button" -msgstr "system_button" - -#: ../C/gdm.xml:6614(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 "" -"Met à disposition les options Éteindre, Redémarrer, Mettre en veille, etc. " -"(si autorisé dans la configuration de GDM). Permet aussi à l'utilisateur de " -"lancer l'application de configuration après avoir saisi le mot de passe " -"administrateur (également soumis à l'autorisation de la configuration de " -"GDM). En principe, cela s'appelle Actions, et l'on s'y réfère en parlant du " -"menu Actions." - -#: ../C/gdm.xml:6625(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 "" -"Par défaut, l'écran de connexion de GDM disparaît après l'authentification. " -"Cela peut produire des scintillements entre l'écran de connexion et la " -"session. La propriété « background » permet aux utilisateurs d'indiquer " -"quels éléments du thème forment l'image d'arrière-plan. Lorsque c'est " -"exploité, GDM enlève tous les éléments de l'affichage qui ne font pas partie " -"de l'arrière-plan et dessine les éléments d'arrière-plan restants dans la " -"fenêtre racine. Cela peut être utilisé pour créer une transition harmonieuse " -"entre l'écran de connexion et la session. Par exemple, si le thème GDM et la " -"session utilisent le même arrière-plan, cela permet de garder un arrière-" -"plan constant." - -#: ../C/gdm.xml:6638(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 "" -"Les nœuds éléments peuvent contenir une propriété « background » (arrière-" -"plan) pouvant être définie à « true » (vrai) ou « false » (faux) (l'absence " -"de la propriété correspond à la valeur « false »), comme ceci :" - -#: ../C/gdm.xml:6644(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 "" -"\n" -"<item type=\"rect\" background=\"true\">\n" -" <normal file=\"background.svg\"/>\n" -" <pos x=\"0\" y=\"0\" width=\"100%\" height=\"-75\"/>\n" -"</item>\n" - -#: ../C/gdm.xml:6651(para) -msgid "" -"If no item node has \"background\" property set, then the background is not " -"modified when greeter exits." -msgstr "" -"Si aucun nœud élément n'a de propriété « background », l'arrière-plan n'est " -"pas modifié lorsque la bannière se ferme." - -#: ../C/gdm.xml:6656(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 "" -"Pour utiliser un arrière-plan différent durant la transition de la connexion " -"que pendant la connexion elle-même, le thème doit indiquer deux nœuds " -"éléments (qui peuvent contenir par exemple des images pixmap ou svg). " -"L'élément qui correspond à l'arrière-plan de la bannière ne devrait pas " -"comporter de propriété « background », alors que l'élément correspondant à " -"l'arrière-plan de la transition devrait disposer de cette propriété. Par " -"exemple :" - -#: ../C/gdm.xml:6665(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 "" -"\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=\"arriereplan_de_connexion.svg\"/>\n" -" <pos x=\"0\" y=\"0\" width=\"100%\" height=\"100%\"/>\n" -" </item>\n" -" <item type=\"rect\">\n" -" <normal file=\"arriereplan_de_banniere.svg\"/>\n" -" <pos x=\"0\" y=\"0\" width=\"100%\" height=\"100%\"/>\n" -" </item>\n" -"[...]\n" -"</greeter>\n" - -#: ../C/gdm.xml:6684(title) -msgid "Position Node" -msgstr "Nœud de position (pos)" - -#: ../C/gdm.xml:6686(para) -msgid "" -"Each item can specify its position and size via the \"pos\" node. For " -"example: <screen>\n" -"<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" -"</screen>" -msgstr "" -"Chaque élément peut indiquer sa position et sa taille au moyen du nœud " -"« pos ». Par exemple : <screen>\n" -"<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" -"</screen>" - -#: ../C/gdm.xml:6694(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 "" -"Aussi bien la position que la taille peuvent être précisées en pourcentage, " -"ce qui sera interprété comme un pourcentage de la taille du conteneur " -"actuel. Pour les éléments de premier niveau, c'est un pourcentage de tout " -"l'écran." - -#: ../C/gdm.xml:6700(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 "" -"Pour les valeurs de x et de y, il est aussi possible d'indiquer une valeur " -"négative, ce qui signifie que la position est calculée depuis la droite ou " -"le bas de l'élément parent. Mais cela n'est valable que pour les coordonnées " -"absolues. Si vous indiquez des pourcentages négatifs, cela n'a aucune " -"influence sur la position." - -#: ../C/gdm.xml:6707(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: <screen>\n" -"<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/>\n" -"</screen>" -msgstr "" -"La position indique également l'ancrage de l'élément, qui peut valoir « n », " -"« ne », « e », « se », « s », « sw », « w » et « nw » qui correspondent au " -"différents coins et bordures, et « center » pour le centrage. Par exemple : " -"<screen>\n" -"<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/>\n" -"</screen>" - -#: ../C/gdm.xml:6718(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 "" -"Si l'élément contient une boîte, vous pouvez indiquer « box » comme valeur " -"de largeur ou de hauteur, ce qui signifie que la largeur ou la hauteur " -"correspondront aux grandeurs respectives des éléments dans la boîte, en plus " -"du remplissage." - -#: ../C/gdm.xml:6724(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 "" -"Si l'élément contient une image SVG, vous pouvez indiquer « scale » comme " -"valeur de largeur ou de hauteur, ce qui signifie que l'image sera " -"redimensionnée pour correspondre aux dimensions de la zone correspondante." - -#: ../C/gdm.xml:6730(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 "" -"Vous pouvez aussi attribuer la propriété « expand » à « true » ou « false ». " -"Si cette propriété est définie à « true », l'élément enfant sera agrandi au " -"maximum dans la boîte (c'est-à-dire qu'il recevra autant d'espace que " -"disponible)." - -#: ../C/gdm.xml:6737(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: <screen>\n" -"<item type=\"label\">\n" -"<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -"</screen>" -msgstr "" -"Dès la version 2.4.4.3, il existe deux propriétés supplémentaires pour les " -"étiquettes (et uniquement pour les étiquettes). La première est « max-" -"width » qui précise la largeur maximale de l'étiquette en pixels. La seconde " -"est « max-screen-percent-width » qui précise le pourcentage maximal de la " -"largeur de l'écran pouvant être occupé par l'étiquette. Par défaut, aucune " -"étiquette ne s'étend sur plus de 90% de la largeur de l'écran. Voici un " -"exemple : <screen>\n" -"<item type=\"label\">\n" -"<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -"</screen>" - -#: ../C/gdm.xml:6753(title) -msgid "Show Node" -msgstr "Nœuds d'affichage (show)" - -#: ../C/gdm.xml:6755(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 "" -"Certains éléments ne s'affichent que dans certains modes, comme par exemple " -"lors d'un affichage distant. Plusieurs valeurs peuvent être indiquées, et " -"elles doivent être séparées par des virgules. Les valeurs suivantes sont " -"possibles :" - -#: ../C/gdm.xml:6761(para) -msgid "<filename>console</filename> - In console mode." -msgstr "<filename>console</filename> - En mode console." - -#: ../C/gdm.xml:6764(para) -msgid "<filename>console-fixed</filename> - In console non-flexi mode." -msgstr "<filename>console-fixed</filename> - En mode console non flexible." - -#: ../C/gdm.xml:6767(para) -msgid "<filename>console-flexi</filename> - In console & flexi mode." -msgstr "<filename>console-flexi</filename> - En mode console et flexible." - -#: ../C/gdm.xml:6770(para) -msgid "<filename>flexi</filename> - In flexi mode." -msgstr "<filename>flexi</filename> - En mode flexible." - -#: ../C/gdm.xml:6773(para) -msgid "<filename>remote</filename> - In remote mode." -msgstr "<filename>remote</filename> - En mode distant." - -#: ../C/gdm.xml:6776(para) -msgid "<filename>remote-flexi</filename> - In remote & flexi mode." -msgstr "<filename>remote-flexi</filename> - En mode distant et flexible." - -#: ../C/gdm.xml:6780(para) -msgid "" -"For example: <screen>\n" -"<show modes=\"flexi,remote\"/>\n" -"</screen>" -msgstr "" -"Par exemple : <screen>\n" -"<show modes=\"flexi,remote\"/>\n" -"</screen>" - -#: ../C/gdm.xml:6787(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 "" -"Il est aussi possible d'indiquer la propriété « type » pour préciser que " -"certains éléments ne doivent être affichés que si le type correspondant est " -"actif. Voici quelques valeurs possibles :" - -#: ../C/gdm.xml:6793(para) -msgid "" -"<filename>chooser</filename>, if ChooserButton is set to \"true\" in the GDM " -"configuration." -msgstr "" -"<filename>chooser</filename>, affiché si le paramètre « ChooserButton » est " -"défini à « true » dans la configuration de GDM." - -#: ../C/gdm.xml:6797(para) -msgid "" -"<filename>config</filename>, if ConfigAvailable is set to \"true\" in the " -"GDM configuration." -msgstr "" -"<filename>config</filename>, affiché si le paramètre « ConfigAvailable » est " -"défini à « true » dans la configuration de GDM." - -#: ../C/gdm.xml:6801(para) -msgid "" -"<filename>custom_cmd[0-9]</filename>, if <filename>n-th</filename> " -"CustomCommand is specified in the GDM configuration." -msgstr "" -"<filename>custom_cmd[0-9]</filename>, affiché si la commande personnalisée " -"<filename>n</filename> (0-9) est définie dans la configuration de GDM." - -#: ../C/gdm.xml:6805(para) -msgid "" -"<filename>halt</filename>, if HaltDaemon is specified in the GDM " -"configuration." -msgstr "" -"<filename>halt</filename>, affiché si le paramètre « HaltDaemon » est défini " -"dans la configuration de GDM." - -#: ../C/gdm.xml:6809(para) -msgid "" -"<filename>reboot</filename>, if RebootCommand is specified in the GDM " -"configuration." -msgstr "" -"<filename>reboot</filename>, affiché si le paramètre « RebootCommand » est " -"défini dans la configuration de GDM." - -#: ../C/gdm.xml:6813(para) -msgid "" -"<filename>suspend</filename>, if SuspendCommand is specified in the GDM " -"configuration." -msgstr "" -"<filename>suspend</filename>, affiché si le paramètre « SuspendCommand » est " -"défini dans la configuration de GDM." - -#: ../C/gdm.xml:6817(para) -msgid "" -"<filename>system</filename>, if SystemMenu is specified in the GDM " -"configuration." -msgstr "" -"<filename>system</filename>, affiché si le paramètre « SystemMenu » est " -"défini dans la configuration de GDM." - -#: ../C/gdm.xml:6821(para) -msgid "" -"<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in the " -"GDM configuration." -msgstr "" -"<filename>timed</filename>, affiché si le paramètre « TimedLoginEnabled » " -"est défini à « true » dans la configuration de GDM." - -#: ../C/gdm.xml:6826(para) -msgid "" -"For example: <screen>\n" -"<show modes=\"console\" type=\"system\"/>\n" -"</screen>" -msgstr "" -"Par exemple : <screen>\n" -"<show modes=\"console\" type=\"system\"/>\n" -"</screen>" - -#: ../C/gdm.xml:6833(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 "" -"Il est aussi possible d'ajouter les propriétés « min-screen-width » ou « min-" -"screen-height » pour indiquer que certains éléments ne doivent être affichés " -"que si la résolution de l'écran correspond au minimum aux valeurs indiquées." - -#: ../C/gdm.xml:6840(para) -msgid "" -"For example: <screen>\n" -"<show min-screen-height=\"768\"/>\n" -"</screen>" -msgstr "" -"Par exemple : <screen>\n" -"<show min-screen-height=\"768\"/>\n" -"</screen>" - -#: ../C/gdm.xml:6847(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 "" -"Il faut signaler que si le paramètre SystemMenu est désactivé, les options " -"Éteindre, Redémarrer, Sélecteur et Configuration ne sont pas affichées. Ce " -"paramètre est donc un un moyen de désactiver globalement toutes ces options. " -"Référez-vous à certains thèmes standards pour observer l'utilisation des " -"modes « show »." - -#: ../C/gdm.xml:6856(title) -msgid "Normal/Active/Prelight Nodes" -msgstr "Nœuds normal/actif/survol" - -#: ../C/gdm.xml:6858(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 "" -"Selon le type d'élément, il est possible de définir sa couleur, sa police ou " -"son image au moyen des balises suivantes (excepté le type « userlist », voir " -"le nœud couleur ci-dessous) :" - -#: ../C/gdm.xml:6864(para) -msgid "<filename>normal</filename> - normal state." -msgstr "<filename>normal</filename> - état normal." - -#: ../C/gdm.xml:6867(para) -msgid "<filename>active</filename> - when the item has active focus." -msgstr "" -"<filename>active</filename> - lorsque l'élément représente la zone active." - -#: ../C/gdm.xml:6870(para) -msgid "" -"<filename>prelight</filename> - when the mouse is hovering over the item." -msgstr "<filename>prelight</filename> - lorsque la souris survole l'élément." - -#: ../C/gdm.xml:6875(para) -msgid "" -"When item is \"rect\" (alpha can be omitted and defaults to 0.0): <screen>\n" -"<normal color=\"#ffffff\" alpha=\"0.0\">\n" -"</screen>" -msgstr "" -"Lorsque l'élément est de type « rect » (la propriété alpha peut être omise, " -"et sa valeur par défaut est 0.0) : <screen>\n" -"<normal color=\"#ffffff\" alpha=\"0.0\">\n" -"</screen>" - -#: ../C/gdm.xml:6883(para) -msgid "" -"When item is \"label\" <screen>\n" -"<normal color=\"#ffffff\" font=\"Sans 14\"/>\n" -"</screen>" -msgstr "" -"Lorsque l'élément est de type étiquette (« label ») : <screen>\n" -"<normal color=\"#ffffff\" font=\"Sans 14\"/>\n" -"</screen>" - -#: ../C/gdm.xml:6890(para) -msgid "" -"When the item type is \"pixmap\" or \"SVG\", then the normal, active, and " -"prelight tags specify the images to use as follows: <screen>\n" -"<normal file=\"picture.png\" tint=\"#dddddd\"/>\n" -"</screen>" -msgstr "" -"Lorsque l'élément est de type « pixmap » ou « SVG », les balises « normal », " -"« active » et « prelight » indiquent les images à utiliser, comme dans " -"l'exemple suivant : <screen>\n" -"<normal file=\"image.png\" tint=\"#dddddd\"/>\n" -"</screen>" - -#: ../C/gdm.xml:6899(para) -msgid "" -"Note that relative pathnames are assumed to be in the same directory as the " -"theme <filename>.xml</filename> file in <filename><share>/gdm/themes/" -"<theme_name></filename>." -msgstr "" -"Il faut relever que les chemins relatifs utilisent comme base le même " -"répertoire que le fichier <filename>.xml</filename> du thème dans " -"<filename><share>/gdm/themes/<nom_du_thème></filename>." - -#: ../C/gdm.xml:6905(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: " -"<screen>\n" -"<normal file=\"picture.png\" altfile1=\"distribution-blah-image.png\" " -"altfile2=\"distribution-foo-image.png\"/>\n" -"</screen> If <filename>distribution-foo-image.png</filename> 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 "" -"Signalons qu'un fichier image de substitution peut être indiqué par la " -"propriété « altfile[n] ». GDM utilise le dernier nom de fichier image " -"valable. Par exemple : <screen>\n" -"<normal file=\"image.png\" altfile1=\"image_de_distrib_toto.png\" " -"altfile2=\"image_de_distrib_riri.png\"/>\n" -"</screen> Si <filename>image_de_distrib_riri.png</filename> est un nom de " -"fichier image correct, c'est cette image qui sera utilisée. Sinon, c'est " -"<filename>image_de_distrib_toto.png</filename> qui sera utilisé, si le " -"fichier existe. Cette fonctionnalité est prise en charge depuis la version " -"2.16.3." - -#: ../C/gdm.xml:6920(title) -msgid "Face Browser Icon/Label Color Nodes" -msgstr "Nœuds de couleur des icônes et étiquettes du navigateur de figures" - -#: ../C/gdm.xml:6922(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 "" -"Si le type d'élément est « userlist », la couleur d'arrière-plan de l'icône " -"et de l'étiquette peut être définie séparément au moyen de la balise " -"suivante :" - -#: ../C/gdm.xml:6928(screen) -#, no-wrap -msgid "" -"\n" -"<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" -msgstr "" -"\n" -"<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" - -#: ../C/gdm.xml:6935(title) -msgid "Text Node" -msgstr "Nœud texte" - -#: ../C/gdm.xml:6937(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): " -"<screen>\n" -"<text xml:lang=\"fr\">Option</text>\n" -"</screen>" -msgstr "" -"Les balises « text » sont utilisées pour les étiquettes. Elles peuvent être " -"utilisées pour afficher du texte traduit, comme le montre l'exemple suivant " -"(si l'attribut« xml:lang » est omis, c'est la locale C qui est utilisée) : " -"<screen>\n" -"<text xml:lang=\"fr\">Option</text>\n" -"</screen>" - -#: ../C/gdm.xml:6946(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: <screen>\n" -"<text>\"foo<sup>bar</sup>\"</text>\n" -"</screen>" -msgstr "" -"Il est possible d'insérer du balisage Pango dans les nœuds texte des " -"étiquettes. Il faut cependant le coder. Par exemple, si vous souhaitez " -"écrire « foo<sup>bar</sup> » dans une étiquette, vous devez " -"saisir : <screen>\n" -"<text>\"foo<sup>bar</sup>\"</text>\n" -"</screen>" - -#: ../C/gdm.xml:6955(para) -msgid "" -"Text nodes can contain the following special character sequences which will " -"be translated as follows:" -msgstr "" -"Les nœuds texte peuvent contenir des séquences de caractères spéciales. " -"Voici ces séquences avec leur signification :" - -#: ../C/gdm.xml:6960(para) -msgid "%% - A literal % character" -msgstr "%% - Un caractère % littéral" - -#: ../C/gdm.xml:6963(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 - Heure d'horloge. Seules les étiquettes dotées de la propriété id " -"« clock » affichent l'heure mise à jour en temps réel. Les autres étiquettes " -"contiennent une heure statique." - -#: ../C/gdm.xml:6968(para) -msgid "%d - Display name (DISPLAY environment variable)" -msgstr "%d - Nom d'affichage (variable d'environnement DISPLAY)" - -#: ../C/gdm.xml:6971(para) -msgid "%h - Hostname (gethostname output)" -msgstr "%h - Nom d'hôte (résultat de gethostname)" - -#: ../C/gdm.xml:6974(para) -msgid "%m - Machine name (uname.machine output)" -msgstr "%m - Nom de machine (résultat de uname.machine)" - -#: ../C/gdm.xml:6977(para) -msgid "%n - Node name (uname.nodename output)" -msgstr "%n - Nom de nœud (résultat de uname.nodename)" - -#: ../C/gdm.xml:6980(para) -msgid "%o - Domain name (getdomainname output)" -msgstr "%o - Nom de domaine (résultat de getdomainname)" - -#: ../C/gdm.xml:6983(para) -msgid "%r - Release name (uname.release output)" -msgstr "%r - Nom de version (résultat de uname.release)" - -#: ../C/gdm.xml:6986(para) -msgid "%s - System name (uname.sysname output)" -msgstr "%s - Nom du système (résultat de uname.sysname)" - -#: ../C/gdm.xml:6989(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 "" -"%t - Valeur actuelle du délai de connexion différée du fichier de " -"configuration (0 si désactivé), suivie par le mot « seconde(s) ». Cette " -"séquence de caractères est prévue uniquement pour une utilisation interne " -"lors de l'affichage du message « timed-label » qui est mis à jour " -"automatiquement chaque seconde." - -#: ../C/gdm.xml:6997(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 "" -"%u - Nom d'utilisateur de connexion différée dans le fichier de " -"configuration (vide si désactivé). Cette séquence de caractères est prévue " -"uniquement pour une utilisation interne lors de l'affichage du message " -"« timed-label » qui est mis à jour automatiquement chaque seconde." - -#: ../C/gdm.xml:7003(para) -msgid "\\n - Carriage return" -msgstr "\\n - Retour de ligne" - -#: ../C/gdm.xml:7006(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 "" -"_ - Le caractère soulignement provoque le soulignement du caractère suivant. " -"S'il précède une séquence de caractères %, le texte qui remplace la séquence " -"de caractères est souligné." - -#: ../C/gdm.xml:7014(title) -msgid "Stock node" -msgstr "Nœud prédéfini (stock)" - -#: ../C/gdm.xml:7016(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 "" -"Certaines étiquettes couramment traduites peuvent être indiquées par les " -"balises « stock ». La balise « text » est ignorée si la balise « stock » est " -"présente. Il est vraiment conseillé d'utiliser les étiquettes prédéfinies " -"plutôt que de simplement placer toutes les traductions dans les thèmes. Cela " -"réduit le temps de chargement et améliore certainement la cohérence des " -"traductions. Voici les valeurs possibles :" - -#: ../C/gdm.xml:7025(para) -msgid "<filename>cancel</filename>, _(\"_Cancel\"" -msgstr "<filename>cancel</filename>, A_nnuler" - -#: ../C/gdm.xml:7028(para) -msgid "<filename>caps-lock-warning</filename>, _(\"Caps Lock is on.\"" -msgstr "" -"<filename>caps-lock-warning</filename>, Le verrouillage majuscule est actif." - -#: ../C/gdm.xml:7032(para) -msgid "<filename>chooser</filename>, _(\"Remote Login via _XDMCP\"" -msgstr "<filename>chooser</filename>, Connexion distante via _XDMCP" - -#: ../C/gdm.xml:7035(para) -msgid "<filename>config</filename>, _(\"_Configure\"" -msgstr "<filename>config</filename>, Confi_gurer" - -#: ../C/gdm.xml:7038(para) -msgid "<filename>custom_cmd[0-9]</filename>, getting label from config file" -msgstr "" -"<filename>custom_cmd[0-9]</filename>, récupération de l'étiquette dans le " -"fichier de configuration" - -#: ../C/gdm.xml:7041(para) -msgid "<filename>disconnect</filename>, _(\"D_isconnect\"" -msgstr "<filename>disconnect</filename>, _Déconnecter" - -#: ../C/gdm.xml:7044(para) -msgid "<filename>halt</filename>, _(\"Shut _Down\"" -msgstr "<filename>halt</filename>, Étein_dre" - -#: ../C/gdm.xml:7047(para) -msgid "<filename>language</filename>, _(\"_Language\"" -msgstr "<filename>language</filename>, _Langue" - -#: ../C/gdm.xml:7050(para) -msgid "<filename>ok</filename>, _(\"_OK\"" -msgstr "<filename>ok</filename>, _Valider" - -#: ../C/gdm.xml:7053(para) -msgid "<filename>options</filename>, _(\"_Options\"" -msgstr "<filename>options</filename>, _Options" - -#: ../C/gdm.xml:7056(para) -msgid "<filename>quit</filename>, _(\"_Quit\"" -msgstr "<filename>quit</filename>, _Quitter" - -#: ../C/gdm.xml:7059(para) -msgid "<filename>reboot</filename>, _(\"_Restart\"" -msgstr "<filename>reboot</filename>, _Redémarrer" - -#: ../C/gdm.xml:7062(para) -msgid "<filename>session</filename>, _(\"_Session\"" -msgstr "<filename>session</filename>, _Session" - -#: ../C/gdm.xml:7065(para) -msgid "<filename>startagain</filename>, _(\"_Start Again\"" -msgstr "<filename>startagain</filename>, _Recommencer" - -#: ../C/gdm.xml:7068(para) -msgid "<filename>suspend</filename>, _(\"Sus_pend\"" -msgstr "<filename>suspend</filename>, Mettre en _veille" - -#: ../C/gdm.xml:7071(para) -msgid "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\"" -msgstr "<filename>system</filename>, _Actions" - -#: ../C/gdm.xml:7075(para) -msgid "<filename>timed-label</filename>, _(\"User %u will login in %t\"" -msgstr "" -"<filename>timed-label</filename>, L'utilisateur %u se connectera dans %t" - -#: ../C/gdm.xml:7079(para) -msgid "<filename>username-label</filename>, _(\"Username:\"" -msgstr "<filename>username-label</filename>, Identifiant :" - -#: ../C/gdm.xml:7082(para) -msgid "<filename>welcome-label</filename>, _(\"Welcome to %n\"" -msgstr "<filename>welcome-label</filename>, Bienvenue sur %n" - -#: ../C/gdm.xml:7086(para) -msgid "" -"For example: <screen>\n" -"<stock type=\"welcome-label\">\n" -"</screen>" -msgstr "" -"Par exemple : <screen>\n" -"<stock type=\"welcome-label\">\n" -"</screen>" - -#: ../C/gdm.xml:7095(title) -msgid "Custom Widgetry" -msgstr "Widgets personnalisés" - -#: ../C/gdm.xml:7097(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 " -"<filename><ServAuthDir>/<display>.GreeterInfo</filename> as " -"<filename><list id>=<listitem id></filename>." -msgstr "" -"Actuellement, l'élément que l'on peut personnaliser est l'élément liste. Si " -"vous avez besoin de demander des informations supplémentaires à " -"l'utilisateur, comme de choisir dans une liste d'emplacements de connexion " -"ou dans un ensemble de sessions personnalisées, vous pouvez paramétrer " -"l'élément liste et y ajouter des éléments enfants présentant ces options. " -"Chaque élément de liste (« listitem ») doit posséder un sous-élément « id » " -"et « text ». L'option est enregistrée dans le fichier <filename><" -"ServAuthDir>/<affichage>.GreeterInfo</filename> sous la forme " -"<filename><list id>=<listitem id></filename>." - -#: ../C/gdm.xml:7108(para) -msgid "" -"For example suppose we are on display :0, <filename>ServAuthDir</filename> " -"is <filename><var>/lib/gdm</filename> and we have the following in the " -"theme:" -msgstr "" -"Par exemple, supposons que nous sommes sur l'affichage :0, que " -"<filename>ServAuthDir</filename> correspond à <filename><var>/lib/gdm</" -"filename> et que l'on trouve ceci dans le thème :" - -#: ../C/gdm.xml:7115(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 "" -"\n" -"<item type=\"list\" id=\"config-perso\">\n" -"<pos anchor=\"nw\" x=\"1\" y=\"1\" height=\"200\" width=\"100\">\n" -"<listitem id=\"toto\">\n" -"<text>Toto</text>\n" -"</listitem>\n" -"<listitem id=\"titi\">\n" -"<text>Titi</text>\n" -"</listitem>\n" -"</item>\n" - -#: ../C/gdm.xml:7127(para) -msgid "" -"Then if the user chooses 'Foo' then <filename><var>/lib/gdm/:0." -"GreeterInfo</filename> will contain: <screen>\n" -"custom-config=foo\n" -"</screen>" -msgstr "" -"Si l'utilisateur choisit « Toto », l'élément <filename><var>/lib/" -"gdm/:0.GreeterInfo</filename> contiendra : <screen>\n" -"config-perso=toto\n" -"</screen>" - -#: ../C/gdm.xml:7139(title) -msgid "Accessibility" -msgstr "Accessibilité" - -#: ../C/gdm.xml:7140(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 <command>GOK</" -"command> (on-screen keyboard) and <command>orca</command> (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 <command>GOK</command>, do not yet work " -"with the \"Themed Greeter\"." -msgstr "" -"GDM prend en charge la « connexion accessible », permettant aux utilisateurs " -"de se connecter dans une session même s'ils ne peuvent pas facilement " -"utiliser l'écran, la souris ou le clavier de manière conventionnelle. Les " -"programmes d'aide technique (AT) comme <command>GOK</command> (clavier " -"visuel) et <command>Orca</command> (loupe et synthèse vocale) sont pris en " -"charge. C'est la bannière GTK+ qui prend le mieux en charge l'accessibilité, " -"il est donc recommandé de l'utiliser pour des besoins d'accessibilité. La " -"bannière avec thème gère certaines fonctions d'accessibilité et peut être " -"suffisante pour certains. Mais certaines aides techniques, comme " -"<command>GOK</command>, ne fonctionnent pas avec la bannière avec thème." - -#: ../C/gdm.xml:7153(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 <filename>Greeter</" -"filename> and <filename>RemoteGreeter</filename> configuration options by " -"hand to be <command>/usr/lib/gdmlogin</command>." -msgstr "" -"L'accessibilité peut être activée en choisissant la bannière GTK+ (Simple) " -"dans l'onglet « Locale » ou dans l'onglet « Distante » des préférences de la " -"fenêtre de connexion. Vous pouvez aussi modifier directement les options de " -"configuration <filename>Greeter</filename> et <filename>RemoteGreeter</" -"filename> dans la configuration de GDM en les définissant à <command>/usr/" -"lib/gdmlogin</command>." - -#: ../C/gdm.xml:7162(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 "" -"Les programmes de bannière GDM permettent de lancer des aides techniques au " -"moment de la connexion à l'aide de « mouvements » configurables. Ces " -"mouvements peuvent être définis comme des raccourcis clavier standards, des " -"événements d'appareils de commutation ou des événements de déplacement de " -"souris. S'il utilise la bannière GTK+, l'utilisateur peut aussi modifier " -"l'apparence de l'interface de connexion. Par exemple, dans le but d'activer " -"une combinaison de couleurs très contrastées pour améliorer la visibilité." - -#: ../C/gdm.xml:7171(para) -msgid "" -"Note that <command>gdmsetup</command> does not yet work with accessibility, " -"so that users who require AT programs should only configure GDM by editing " -"the ASCII files directly." -msgstr "" -"Il faut relever que la configuration graphique (<command>gdmsetup</command>) " -"ne fonctionne pas encore avec l'accessibilité, ce qui fait que les " -"utilisateurs ayant besoin de programmes d'aide technique sont contraints de " -"configurer GDM en éditant directement les fichiers texte." - -#: ../C/gdm.xml:7178(title) -msgid "Accessibility Configuration" -msgstr "Configuration de l'accessibilité" - -#: ../C/gdm.xml:7180(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 <command>GOK</command> and <command>orca</command>, " -"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 "" -"Pour pouvoir activer la connexion accessible, l'administrateur système doit " -"effectuer certaines modifications à la configuration de connexion par " -"défaut, en modifiant manuellement trois fichiers de configuration lisibles " -"par un humain : le fichier de configuration personnalisée de GDM, le fichier " -"AccessKeyMouseEvents et le fichier AccessDwellMouseEvents. Ces deux derniers " -"fichiers contiennent des valeurs par défaut raisonnables pour les mouvements " -"permettant de lancer <command>GOK</command> et <command>Orca</command>, mais " -"il est possible que certaines personnes aient besoin de les configurer " -"différemment pour mieux répondre à leurs besoins. Par exemple, augmenter ou " -"diminuer la durée de pression sur un bouton ou une touche peut faciliter la " -"connexion pour certains. Il est aussi possible d'ajouter d'autres programmes " -"d'aide technique dans le fichier de configuration, si nécessaire." - -#: ../C/gdm.xml:7196(title) -msgid "Accessibile Theming" -msgstr "Thèmes et accessibilité" - -#: ../C/gdm.xml:7198(para) -msgid "" -"If using the \"GTK+ Greeter\" users can easily switch the color and contrast " -"scheme of the dialog. To do this, ensure the <filename>AllowGtkThemeChange</" -"filename> 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 " -"<filename>GtkThemesToAllow</filename> configuration choice can also be used " -"to limit the choices available as desired. For example:" -msgstr "" -"Avec la bannière GTK+, les utilisateurs peuvent facilement changer de " -"combinaisons de couleurs et de contrastes de la fenêtre. Pour cela, il faut " -"s'assurer que le paramètre <filename>AllowGtkThemeChange</filename> de la " -"configuration GDM est défini à « true » (vrai). Ce devrait être la valeur " -"par défaut. Dans ce cas, la bannière standard (simple) contient un menu " -"permettant de changer de thème GTK+. L'option de configuration " -"<filename>GtkThemesToAllow</filename> peut aussi être exploitée pour limiter " -"les options disponibles, le cas échéant. Par exemple :" - -#: ../C/gdm.xml:7210(screen) -#, no-wrap -msgid "" -"\n" -"GtkThemesToAllow=HighContrast,HighContrastInverse\n" -msgstr "" -"\n" -"GtkThemesToAllow=HighContrast,HighContrastInverse\n" - -#: ../C/gdm.xml:7214(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 "" -"La bannière avec thème peut aussi contenir des thèmes GDM comportant des " -"combinaisons de couleurs et de contrastes adaptés aux besoins, mais il n'en " -"existe pas encore dans la version livrée avec GDM. Certaines distributions " -"peuvent contenir de tels thèmes. Il n'existe pour l'instant aucun mécanisme " -"permettant de changer de thème à la volée dans la bannière avec thème. Cela " -"signifie que si un utilisateur a besoin d'un thème accessible, tous les " -"autres utilisateurs devront aussi utiliser ce thème." - -#: ../C/gdm.xml:7226(title) -msgid "AT Program Support" -msgstr "Prise en charge des aides techniques" - -#: ../C/gdm.xml:7228(para) -msgid "" -"To enable user to launch AT such as the <command>GOK</command> or " -"<command>orca</command>, the <filename>AddGtkModules</filename> parameter in " -"the GDM configuration must be set to \"true\". Also the " -"<filename>GtkModulesList</filename> parameter must be uncommented and set as " -"follows:" -msgstr "" -"Pour permettre aux utilisateurs de lancer des aides techniques telles que " -"<command>GOK</command> ou<command>Orca</command>, le paramètre " -"<filename>AddGtkModules</filename> de la configuration GDM doit être défini " -"à « true » (vrai). De plus, le paramètre <filename>GtkModulesList</filename> " -"doit être décommenté et défini comme suit :" - -#: ../C/gdm.xml:7237(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 "" -"\n" -"GtkModulesList=gail:atk-bridge:/usr/lib/gtk-2.0/modules/libdwellmouselistener:/usr/lib/gtk-2.0/modules/libkeymouselistener\n" - -#: ../C/gdm.xml:7241(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, <command>at-spi-registryd</" -"command>, to be running. This is handled by the GDM GUI starting with " -"version 2.17." -msgstr "" -"Ainsi, toutes les interfaces graphiques de GDM sont lancées avec les modules " -"GTK appropriés au lancement des programmes d'aide technique. L'utilisation " -"des aides techniques et du module « atk-bridge » exige que le démon de " -"registre <command>at-spi-registryd</command> soit en cours d'exécution. À " -"partir de la version 2.17, l'interface de GDM s'occupe de cela." - -#: ../C/gdm.xml:7249(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 "" -"Les administrateurs système souhaitent parfois ne charger que les modules " -"vraiment nécessaires à leurs utilisateurs. Le module « libkeymouselistener » " -"offre la prise en charge des mouvements de claviers et de commutateurs, " -"alors que le module « libdwellmouselistener » prend en charge les mouvements " -"de souris. Si vos utilisateurs n'ont besoin que de l'un ou de l'autre, " -"incluez uniquement le gestionnaire d'écoute requis. Certaines aides " -"techniques n'ont pas non plus besoin de « gail » ou de « atk-bridge ». Si " -"vous constatez que les programmes d'aide technique fonctionnent très bien " -"sans ces modules, ils peuvent donc être omis. Notez que certains programmes " -"fonctionnent de manière limitée lorsque ces modules sont absents. Cependant, " -"pour des besoins généraux d'accessibilité, il est souhaitable d'inclure les " -"quatre modules." - -#: ../C/gdm.xml:7264(para) -msgid "" -"Once \"keymouselistener\" and/or \"dwellmouselistener\" have been added to " -"the <filename>AddGtkModules</filename> loaded by GDM, then you may need to " -"modiify the gesture configurations to meet your user's needs. Default " -"gestures are provided for launching <command>GOK</command> and " -"<command>orca</command>, but it is recommended to modify these gestures so " -"they work best for your user base. These gesture associations are contained " -"in files <filename>AccessKeyMouseEvents</filename> and " -"<filename>AccessDwellMouseEvents</filename>, respectively. Both files are " -"located in the <filename><etc>/gdm/modules</filename> directory. The " -"gesture configuration format is described in the comment section of the two " -"configuration files." -msgstr "" -"Après avoir ajouté « keymouselistener » ou « dwellmouselistener » dans " -"<filename>AddGtkModules</filename> chargé par GDM, il peut être souhaitable " -"de modifier les configurations de gestes afin de les adapter aux besoins de " -"vos utilisateurs. Les gestes par défaut sont conçus pour pour lancer " -"<command>GOK</command> et <command>Orca</command>, mais il est recommandé de " -"les modifier pour qu'ils correspondent au mieux à vos besoins. Ces " -"associations de gestes se trouvent dans les fichiers " -"<filename>AccessKeyMouseEvents</filename> et " -"<filename>AccessDwellMouseEvents</filename>, situés dans le répertoire " -"<filename><etc>/gdm/modules</filename>. Le format de configuration des " -"gestes est décrit dans les commentaires des deux fichiers de configuration." - -#: ../C/gdm.xml:7281(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 " -"<filename>server-foo</filename> sections." -msgstr "" -"Le fichier AccessKeyMouseEvents contrôle le détecteur de gestes " -"« keymouselistener ». Il est utilisé pour définir des séquences de pressions " -"de touches, de clics de souris ou d'autres périphériques XInput permettant " -"de lancer des applications nécessaires à l'accessibilité. Afin de réduire la " -"probabilité de lancement involontaire, ces « gestes » peuvent être associés " -"avec plusieurs pressions de commutateur ou des durées minimales. Il est à " -"relever que l'extension XKB est nécessaire au fonctionnement des gestes de " -"clavier, il peut donc être utile d'ajouter « +xkb » à la ligne de commande " -"de votre serveur X pour que tout fonctionne. Cette ligne de commande est " -"définie dans le fichier de configuration GDM sous les sections " -"<filename>server-?</filename>." - -#: ../C/gdm.xml:7295(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 "" -"Le fichier DwellKeyMouseEvents contrôle le détecteur de gestes " -"« dwellmouselistner » et il prend en charge les gestes comprenant des " -"mouvements de périphériques de pointage, tels que la souris du système, une " -"souris de tête ou une boule de commande (trackball). Les gestes de " -"déplacement sont définis comme des « événements de traversée » dans et hors " -"de la fenêtre de connexion. Si le détecteur de gestes « dwellmouselistner » " -"est chargé, les périphériques de pointages alternatifs sont temporairement " -"associés au pointeur principal, afin que les mouvements de ces périphériques " -"produisent des déplacements du pointeur à l'écran. Tous les gestes sont " -"définis par une même syntaxe, c'est-à-dire qu'il n'y a aucune distinction " -"entre le mouvement d'une souris principale et celui d'un périphérique " -"d'entrée alternatif." - -#: ../C/gdm.xml:7311(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 "" -"Sur certains systèmes d'exploitation, il est nécessaire de s'assurer que " -"l'utilisateur GDM est un membre du groupe « audio », si l'on veut que les " -"aides techniques qui génèrent une sortie sonore (comme la synthèse vocale) " -"puissent fonctionner." - -#: ../C/gdm.xml:7318(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 "" -"Actuellement, GDM ne se souvient pas des programmes d'aide technique qui ont " -"été lancés au moment de changer d'application. Ainsi, si par exemple " -"l'utilisateur bascule du programme de connexion à un sélecteur, il faut que " -"l'utilisateur effectue à nouveau le geste nécessaire. Les utilisateurs " -"peuvent aussi avoir besoin de configurer leur session par défaut afin que " -"les aides techniques nécessaires soient lancées automatiquement (ou que des " -"combinaisons clavier spécifiques permettent de les lancer) après le " -"démarrage de la session utilisateur." - -#: ../C/gdm.xml:7331(title) -msgid "AT Troubleshooting" -msgstr "Dépannage des aides techniques" - -#: ../C/gdm.xml:7333(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 "" -"Il existe un certain nombre de problèmes courants à la base des difficultés " -"de fonctionnement des détecteurs de gestes. Il est recommandé d'utiliser la " -"version 2.18.0 ou ultérieure de GDM pour mettre toutes les chances de son " -"côté." - -#: ../C/gdm.xml:7339(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 "" -"Certains serveurs X anciens ont une anomalie qui empêche la détection de " -"répétition automatique lorsque XEVIE est activé (ce qui arrive lorsque atk-" -"bridge est inclu comme module GTK). En raison de cette anomalie, les gestes " -"clavier avec une durée plus grande que 0 échouent toujours. Une solution est " -"de simplement redéfinir tous les gestes concernés en leur attribuant une " -"durée de 0 ; une autre possibilité est de mettre à jour le serveur X." - -#: ../C/gdm.xml:7348(para) -msgid "" -"Some versions of <command>GOK</command> and <command>orca</command> 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 "" -"Certaines versions de <command>GOK</command> et d'<command>Orca</command> ne " -"démarrent pas tant que l'utilisateur « gdm » ne dispose pas d'un dossier " -"personnel accessible en écriture. Cela a été résolu dans GNOME 2.18, mais si " -"vous utilisez une version plus ancienne de GNOME, vous pouvez corriger le " -"problème et faire fonctionner ces applications en donnant à l'utilisateur " -"GDM un dossier personnel accessible en écriture." - -#: ../C/gdm.xml:7357(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 "" -"Si vous voyez un curseur en forme de montre lorsque vous effectuez un geste " -"mais que le programme ne démarre pas, cela signifie que le geste a été " -"détecté, mais qu'il y a un problème pour lancer le programme. Il s'agit très " -"probablement du problème de l'absence d'un dossier personnel accessible en " -"écriture pour l'utilisateur GDM." - -#: ../C/gdm.xml:7365(para) -msgid "" -"Also note that some input devices require X server configuration before GDM " -"will recognize them." -msgstr "" -"Veuillez aussi prendre note du fait que certains périphériques d'entrée " -"nécessitent d'être configurés au niveau du serveur X avant que GDM ne puisse " -"les reconnaître." - -#: ../C/gdm.xml:7372(title) -msgid "Accessibility Login Sound Configuration" -msgstr "Configuration du son de la connexion accessible" - -#: ../C/gdm.xml:7374(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 <filename><bin>/play</filename> (or <filename><" -"bin>/audioplay</filename> on Solaris. This can be changed via the " -"<filename>SoundProgram</filename> GDM configuration option. Typically most " -"text-to-speech programs (such as <command>orca</command>) use a separate " -"mechanism to play audio, so this configuration setting is not needed for " -"them to work." -msgstr "" -"Par défaut, GDM exige la présence d'une application audio du genre « play » " -"pour pouvoir émettre des sons lors de l'échec ou du succès de connexions. " -"GDM cherche cette application à l'emplacement <filename><bin>/play</" -"filename> (ou <filename><bin>/audioplay</filename> sur Solaris). Cela " -"peut être ajusté par l'option de configuration <filename>SoundProgram</" -"filename> de GDM. Habituellement, la plupart des programmes de synthèse " -"vocale (comme <command>Orca</command>) utilisent un dispositif distinct pour " -"émettre des sons, ce qui fait qu'ils n'ont pas besoin de cette option de " -"configuration pour fonctionner." - -#: ../C/gdm.xml:7392(title) -msgid "Solaris Specific Features" -msgstr "Fonctionnalités spécifiques à Solaris" - -#: ../C/gdm.xml:7395(title) -msgid "Using GDM on Solaris" -msgstr "Utilisation de GDM sur Solaris" - -#: ../C/gdm.xml:7397(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 "" -"GDM n'est pas encore le programme de connexion par défaut sur Solaris. Si " -"vous souhaitez utiliser GDM, vous devez alors désactiver la connexion CDE et " -"lancer le service GDM. Notez que la désactivation de la connexion CDE " -"provoque la fermeture immédiate de toute session en cours, et que toute " -"donnée non sauvegardée est perdue. N'exécutez ces commandes que si vous êtes " -"certain que les sessions en cours ne contiennent pas de données non " -"enregistrées. Le mieux serait de lancer ces commandes depuis une connexion " -"en console ou un terminal de secours plutôt que depuis une session graphique " -"en cours. La première étape est d'exécuter la commande suivante pour savoir " -"si la connexion CDE fonctionne en tant que service SMF." - -#: ../C/gdm.xml:7410(screen) -#, no-wrap -msgid "" -"\n" -"svcs cde-login\n" -msgstr "" -"\n" -"svcs cde-login\n" - -#: ../C/gdm.xml:7414(para) -msgid "" -"If the <command>svcs</command> command responds that this service is " -"enabled, then run this command to disable CDE login:" -msgstr "" -"Si la commande <command>svcs</command> répond que ce service est actif, " -"exécutez cette commande pour désactiver la connexion CDE :" - -#: ../C/gdm.xml:7419(screen) -#, no-wrap -msgid "" -"\n" -"svcadm disable cde-login\n" -msgstr "" -"\n" -"svcadm disable cde-login\n" - -#: ../C/gdm.xml:7423(para) -msgid "" -"If the <command>svcs</command> command responds that this pattern doesn't " -"match any instances, then run these commands to stop CDE login:" -msgstr "" -"Si la commande <command>svcs</command> répond que ce motif ne correspond à " -"aucune instance, exécutez alors ces commandes pour arrêter la connexion CDE :" - -#: ../C/gdm.xml:7429(screen) -#, no-wrap -msgid "" -"\n" -"/usr/dt/config/dtconfig -d\n" -"Either reboot, or kill any running dtlogin processes.\n" -msgstr "" -"\n" -"/usr/dt/config/dtconfig -d\n" -"Redémarrez ou tuez tout processus dtlogin en cours de fonctionnement.\n" - -#: ../C/gdm.xml:7434(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 "" -"À cet instant, vous verrez apparaître une connexion en console. Connectez-" -"vous en tant que root et exécutez la commande ci-après. Sur Solaris 10, le " -"nom de service est « gdm2-login » et sur Solaris Nevada, le nom de service " -"est « gdm »." - -#: ../C/gdm.xml:7441(screen) -#, no-wrap -msgid "" -"\n" -"svcadm enable servicename\n" -msgstr "" -"\n" -"svcadm enable nom_de_service\n" - -#: ../C/gdm.xml:7447(title) -msgid "Solaris Configuration" -msgstr "Configuration de Solaris" - -#: ../C/gdm.xml:7448(para) -msgid "" -"On Solaris, the following configuration is recommended. This turns on IPv6 " -"and also turns on PreFetch for performance benefit. <screen>\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" -"</screen>" -msgstr "" -"Sur Solaris, la configuration suivante est recommandée. Cela active IPv6 " -"ainsi que PreFetch, afin d'améliorer les performances. <screen>\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" -"</screen>" - -#: ../C/gdm.xml:7461(para) -msgid "" -"Configuring GDM with the \"--with-post-path=/usr/openwin/bin\" on Solaris is " -"recommended for accessing X server programs." -msgstr "" -"La configuration de GDM sur Solaris avec « --with-post-path=/usr/openwin/" -"bin » est recommandée pour accéder aux programmes de serveur X." - -#: ../C/gdm.xml:7469(title) -msgid "Solaris /etc/logindevperm" -msgstr "Solaris et /etc/logindevperm" - -#: ../C/gdm.xml:7470(para) -msgid "" -"GDM supports /etc/logindevperm, but only on Solaris 10 and higher. Refer to " -"the logindevperm.4 man page for more information." -msgstr "" -"GDM prend en charge /etc/logindevperm, mais uniquement à partir de Solaris " -"10. Référez-vous à la page de manuel logindevperm.4 pour plus d'informations." - -#: ../C/gdm.xml:7476(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 "" -"Pour rendre fonctionnel /etc/logindevperm sur Solaris 9 ou une version plus " -"ancienne, vous êtes obligé de manipuler les scripts GDM PreSession et " -"PostSession pour changer directement les droits d'accès (chmod) aux " -"périphériques. En d'autres termes, si /etc/logindevperm présente la ligne " -"suvante :" - -#: ../C/gdm.xml:7483(screen) -#, no-wrap -msgid "" -"\n" -"/dev/console 0600 /dev/sound/* # audio devices\n" -msgstr "" -"\n" -"/dev/console 0600 /dev/sound/* # audio devices\n" - -#: ../C/gdm.xml:7487(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 "" -"Alors le script PreSession devrait être modifié pour que /dev/console " -"appartienne au couple utilisateur:groupe qui se connecte par la console et " -"pour s'assurer que les bonnes permissions soient définies, selon /etc/" -"logindevperm (0600 pour la ligne ci-dessus). Ensuite, dans le script " -"PostSession, il s'agit de remettre l'appartenance du périphérique à root:" -"root et les droits à 0600 dans tous les cas (n'utilisez pas la valeur du " -"fichier /etc/logindevperm). Linux utilise un mécanisme différent pour gérer " -"les permissions des périphériques, ce qui fait que les opérations de script " -"décrites ici ne sont pas nécessaires." - -#: ../C/gdm.xml:7500(title) -msgid "Solaris Automatic Login" -msgstr "Connexion automatique sur Solaris" - -#: ../C/gdm.xml:7501(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 "" -"La connexion automatique ne fonctionne pas sur Solaris 10 ou plus ancien, " -"car PAM n'est pas configuré pour prendre en charge cette fonctionnalité par " -"défaut. Comme la connexion automatique est une fonctionnalité de GDM qui " -"n'est pas activée par défaut, vous ne constaterez ce problème que si vous " -"essayez de l'utiliser. L'activation de cette fonctionnalité permet à votre " -"ordinateur de se connecter au démarrage avec un nom d'utilisateur défini " -"sans devoir saisir de nom d'utilisateur ni de mot de passe. C'est une façon " -"non sécurisée de configurer un ordinateur." - -#: ../C/gdm.xml:7512(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 "" -"Si vous utilisez Solaris 10 ou une version plus ancienne, vous devez " -"compiler le code pam_allow.c fourni avec la version de GDM, l'installer " -"dans /usr/lib/security (ou indiquer le chemin complet dans /etc/pam.conf) et " -"vous assurer que son propriétaire possède l'uid 0 et qu'il ne soit pas " -"accessible en écriture par le groupe ou par tout le monde." - -#: ../C/gdm.xml:7519(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 "" -"Vous trouverez ci-après des valeurs convenables de pam.conf pour " -"l'activation de la connexion automatique avec GDM. Prenez soin de lire la " -"documentation de PAM (par ex. la page de manuel pam.d/pam.conf) et soyez " -"bien conscient des conséquences sur la sécurité suite aux changements de " -"configuration que vous pensez effectuer." - -#: ../C/gdm.xml:7527(screen) -#, no-wrap -msgid "" -"\n" -" gdm-autologin auth required pam_unix_cred.so.1\n" -" gdm-autologin auth sufficient pam_allow.so.1\n" -" gdm-autologin account sufficient pam_allow.so.1\n" -" gdm-autologin session sufficient pam_allow.so.1\n" -" gdm-autologin password sufficient pam_allow.so.1\n" -msgstr "" -"\n" -" gdm-autologin auth required pam_unix_cred.so.1\n" -" gdm-autologin auth sufficient pam_allow.so.1\n" -" gdm-autologin account sufficient pam_allow.so.1\n" -" gdm-autologin session sufficient pam_allow.so.1\n" -" gdm-autologin password sufficient pam_allow.so.1\n" - -#: ../C/gdm.xml:7535(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 "" -"La configuration ci-dessus ne produit aucune journalisation dans lastlog. Si " -"vous souhaitez une telle journalisation, utilisez la configuration suivante " -"pour l'élément session :" - -#: ../C/gdm.xml:7540(screen) -#, no-wrap -msgid "" -"\n" -" gdm-autologin session required pam_unix_session.so.1\n" -msgstr "" -"\n" -" gdm-autologin session required pam_unix_session.so.1\n" - -#: ../C/gdm.xml:7546(title) -msgid "Solaris RBAC support for Shutdown, Reboot, and Suspend" -msgstr "" -"Prise en charge de RBAC sur Solaris pour l'extinction, le redémarrage et la " -"mise en veille" - -#: ../C/gdm.xml:7548(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 <command>gdmflexiserver</command> " -"QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION commands." -msgstr "" -"À partir de la version 2.19 de GDM, celui-ci prend en charge RBAC (Role " -"Based Access Control) pour l'activation des commandes système (Éteindre, " -"Redémarrer, Mettre en veille, etc.) qui apparaissent dans le menu système de " -"la bannière et par les commandes QUERY_LOGOUT_ACTION SET_LOGOUT_ACTION et " -"SET_SAFE_LOGOUT_ACTION de <command>gdmflexiserver</command>." - -#: ../C/gdm.xml:7557(para) -msgid "" -"On Solaris GDM has the following value specified for the " -"<filename>RBACSystemCommandKeys</filename> configuration option." -msgstr "" -"Sur Solaris, GDM dispose de la valeur ci-après dans l'option de " -"configuration <filename>RBACSystemCommandKeys</filename>." - -#: ../C/gdm.xml:7563(screen) -#, no-wrap -msgid "" -"\n" -"HALT:solaris.system.shutdown;REBOOT:solaris.system.shutdown\n" -msgstr "" -"\n" -"HALT:solaris.system.shutdown;REBOOT:solaris.system.shutdown\n" - -#: ../C/gdm.xml:7567(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 " -"<filename>User</filename> configuration option, \"gdm\" by default) has such " -"RBAC permissions." -msgstr "" -"En conséquence, seuls les utilisateurs ayant l'autorité RBAC auront accès " -"aux fonctions d'extinction et de redémarrage (SHUTDOWN / REBOOT). Autrement " -"dit, les utilisateurs qui disposent du nom d'autorisation « solaris.system." -"shutdown ». La bannière GDM n'affiche ces options que si l'utilisateur GDM " -"(défini par l'option de configuration <filename>User</filename>, « gdm » par " -"défaut) possède les permissions RBAC correspondantes." - -#: ../C/gdm.xml:7577(para) -msgid "" -"Therefore, add the \"solaris.system.shutdown\" authorization name to the " -"<filename>/etc/user_attr</filename> 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 " -"<filename>RBACSystemCommandKeys</filename> GDM configuration key, and this " -"will make the system commands available for all users. Refer to the " -"<filename>user_attr</filename> man page for more information about setting " -"RBAC privileges." -msgstr "" -"C'est pourquoi vous devez ajouter le nom d'autorisation « solaris.system." -"shutdown » dans le fichier <filename>/etc/user_attr</filename> pour tous les " -"utilisateurs censés avoir accès à l'extinction et au redémarrage du système. " -"Si vous souhaitez que ces options apparaissent dans la bannière, il faut " -"aussi ajouter ce nom d'autorisation à l'utilisateur GDM. Si vous ne " -"souhaitez pas utiliser RBAC, il vous suffit de ne pas définir la clé de " -"configuration GDM <filename>RBACSystemCommandKeys</filename>, ce qui rendra " -"disponible les commandes système à tous les utilisateurs. Référez-vous à la " -"page de manuel de <filename>user_attr</filename> pour plus d'informations " -"sur l'attribution de privilèges RBAC." - -#: ../C/gdm.xml:7591(para) -msgid "" -"Note that on Solaris there are two programs that can be used to shutdown the " -"system. These are GDM and <command>gnome-sys-suspend</command>. " -"<command>gnome-sys-suspend</command> is a GUI front-end for the <command>sys-" -"suspend</command>." -msgstr "" -"Il faut relever que sur Solaris, il existe deux programmes pour éteindre le " -"système. Ce sont GDM et <command>gnome-sys-suspend</command>. Ce dernier est " -"une interface graphique pour la commande <command>sys-suspend</command>." - -#: ../C/gdm.xml:7599(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 <command>gnome-sys-suspend</" -"command> 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 <command>gnome-sys-suspend</command> command is " -"less functional since it does not support a reboot option, only shutdown and " -"suspend." -msgstr "" -"Si GDM est utilisé comme programme de connexion et que l'utilisateur dispose " -"des droits RBAC pour éteindre la machine (ou que la prise en charge de RBAC " -"est désactivée dans GDM), l'option « Éteindre » du tableau de bord GNOME " -"utilise GDM pour éteindre, redémarrer ou mettre en veille la machine. C'est " -"un peu plus élégant que d'utiliser <command>gnome-sys-suspend</command>, car " -"GDM attend que la session utilisateur soit terminée avant d'exécuter la " -"commande souhaitée (y compris l'exécution du script PostSession, etc.). De " -"plus, la commande <command>gnome-sys-suspend</command> est moins complète " -"puisqu'elle ne comprend pas d'option de redémarrage, mais uniquement " -"éteindre et mettre en veille." - -#: ../C/gdm.xml:7614(para) -msgid "" -"If GDM is not being used to manage shutdown, reboot, and suspend; then the " -"GNOME panel uses <command>gnome-sys-suspend</command> 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 <command>gnome-sys-suspend</command>. If you are " -"using this, then refer to the <command>sys-suspend</command> man page for " -"information about how to configure it. Or consider using GDM and configuring " -"it to provide these options." -msgstr "" -"Si GDM n'est pas exploité pour gérer l'extinction, le redémarrage et la mise " -"en veille, le tableau de bord GNOME utilise <command>gnome-sys-suspend</" -"command> lorsque vous choisissez l'option « Arrêter » dans le menu " -"applications. Si la boîte de dialogue qui apparaît lorsque vous sélectionnez " -"cette option ne présente que les options de mise en veille et d'extinction, " -"il est probable que ce soit la commande <command>gnome-sys-suspend</command> " -"qui est utilisée. Dans ce cas, consultez la page de manuel de <command>sys-" -"suspend</command> pour obtenir des informations sur sa configuration. Ou " -"envisagez l'utilisation de GDM que vous pourrez configurer pour fournir ces " -"options." - -#: ../C/gdm.xml:7630(title) -msgid "Other Solaris Features" -msgstr "Autres fonctionnalités sur Solaris" - -#: ../C/gdm.xml:7631(para) -msgid "GDM supports a few features specific to Solaris, as follows:" -msgstr "" -"GDM prend en charge quelques fonctionnalités spécifiques à Solaris, telles " -"que :" - -#: ../C/gdm.xml:7635(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 "" -"GDM prend en charge « Solaris Auditing » à partir de Solaris 10. GDM ne " -"devrait pas être utilisé si la fonction d'audit est nécessaire et que vous " -"utilisez Solaris 9 ou une version plus ancienne." - -#: ../C/gdm.xml:7641(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 "" -"GDM prend en charge une fonction de sécurité où le serveur X fonctionne sous " -"l'identité de l'utilisateur plutôt qu'avec root. GDM doit utiliser PAM pour " -"que cette fonction soit activée, ce qui est la situation normale avec " -"Solaris. Un effet de bord de cette deuxième fonctionnalité est que le " -"serveur X redémarre toujours entre les sessions, ce qui désactive l'option " -"de configuration AlwaysRestartServer." - -#: ../C/gdm.xml:7650(para) -msgid "" -"Solaris supports the <filename>/etc/default/login</filename> interface, " -"which affects the <filename>DefaultPath</filename>, <filename>RootPath</" -"filename>, <filename>PasswordRequired</filename>, and " -"<filename>AllowRemoteRoot</filename> options as described in the " -"\"Configuration\" section." -msgstr "" -"Solaris prend en charge l'interface <filename>/etc/default/login</filename>, " -"ce qui influence les options <filename>DefaultPath</filename>, " -"<filename>RootPath</filename>, <filename>PasswordRequired</filename> et " -"<filename>AllowRemoteRoot</filename>, comme expliqué dans la section " -"« Configuration »." - -#: ../C/gdm.xml:7662(title) -msgid "Example Configurations" -msgstr "Exemples de configuration" - -#: ../C/gdm.xml:7665(title) -msgid "Defining Custom Commands" -msgstr "Définition de commandes personnalisées" - -#: ../C/gdm.xml:7667(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 <filename>[customcommand]</filename> " -"section of the GDM configuration file. <screen>\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" -" </screen> CustomCommand0 specifies two commands separated by a " -"semicolon: <filename>/sbin/rebootwindoze</filename> and <filename>/usr/local/" -"sbin/rebootwindoze</filename>. GDM will use the first valid command in the " -"list. This allows different commands for different operating systems to be " -"included." -msgstr "" -"Admettons que vous souhaitez ajouter une commande personnalisée au menu GDM " -"afin de donner la possibilité de démarrer avec d'autres systèmes " -"d'exploitation, comme Windoze. Il suffit d'ajouter les options suivantes " -"dans la section <filename>[customcommand]</filename> du fichier de " -"configuration GDM. <screen>\n" -" [customcommand]\n" -" CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze\n" -" CustomCommandLabel0=_Windoze\n" -" CustomCommandLRLabel0=Redémarrer avec _Windoze\n" -" CustomCommandText0=Êtes-vous sûr de vouloir redémarrer " -"l'ordinateur avec Windoze ?\n" -" CustomCommandTooltip0=Redémarre l'ordinateur avec Windows\n" -" CustomCommandIsPersistent0=true\n" -" </screen> CustomCommand0 indique deux commandes séparées par un " -"point-virgule : filename>/sbin/rebootwindoze</filename> et <filename>/usr/" -"local/sbin/rebootwindoze</filename>. GDM utilise la première commande " -"valable de la liste. Cela permet d'inclure différentes commandes pour " -"différents systèmes d'exploitation." - -#: ../C/gdm.xml:7690(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 <filename>[customcommand]</filename> " -"section of your GDM configuration file. <screen>\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" -" </screen>" -msgstr "" -"À part la possibilité de personnaliser cette option pour redémarrer avec un " -"autre système d'exploitation, vous pouvez aussi l'utiliser pour définir vos " -"propres commandes que vous souhaitez lancer à partir du menu GDM. Supposons " -"que vous souhaitez donner la possibilité aux utilisateurs de lancer des " -"scripts de mise à jour du système à partir de l'écran de connexion. Ajoutez " -"les options suivantes dans la section <filename>[customcommand]</filename> " -"de votre fichier de configuration de GDM. <screen>\n" -" [customcommand]\n" -" CustomCommand0=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" -" CustomCommandLabel0=_Mettez-moi à jour\n" -" CustomCommandLRLabel0=Mettre à jour le système\n" -" CustomCommandText0=Êtes-vous sûr de vouloir mettre à jour le " -"logiciel système ?\n" -" CustomCommandTooltip0=Met à jour le système\n" -" CustomCommandNoRestart0=true\n" -" </screen>" - -#: ../C/gdm.xml:7710(para) -msgid "" -"Both custom commands could be defined as follows. <screen>\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" -" </screen>" -msgstr "" -"Les deux commandes personnalisée pourraient être définies comme ceci : " -"<screen>\n" -" [customcommand]\n" -" CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze\n" -" CustomCommandLabel0=_Windoze\n" -" CustomCommandLRLabel0=Redémarrer avec _Windoze\n" -" CustomCommandText0=Êtes-vous sûr de vouloir redémarrer " -"l'ordinateur avec Windoze ?\n" -" CustomCommandTooltip0=Redémarre l'ordinateur avec Windows\n" -" CustomCommandIsPersistent0=true\n" -" \n" -" CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" -" CustomCommandLabel1=_Mettez-moi à jour\n" -" CustomCommandLRLabel1=Mettre à jour le système\n" -" CustomCommandText1=Êtes-vous sûr de vouloir mettre à jour le " -"logiciel système ?\n" -" CustomCommandTooltip1=Met à jour le système\n" -" CustomCommandNoRestart1=true\n" -" </screen>" - -#: ../C/gdm.xml:7731(para) -msgid "" -"There can be up to 10 custom commands numbered 0-9. <screen>\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" -" </screen>" -msgstr "" -"Il peut y avoir jusqu'à 10 commandes personnalisées, numérotées de 0 à 9. " -"<screen>\n" -" [customcommand]\n" -" CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze\n" -" CustomCommandLabel0=_Windoze\n" -" CustomCommandLRLabel0=Redémarrer avec _Windoze\n" -" CustomCommandText0=Êtes-vous sûr de vouloir redémarrer " -"l'ordinateur avec Windoze ?\n" -" CustomCommandTooltip0=Redémarre l'ordinateur avec Windows\n" -" CustomCommandIsPersistent0=true\n" -" \n" -" CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" -" CustomCommandLabel1=_Mettez-moi à jour\n" -" CustomCommandLRLabel1=Mettre à jour le système\n" -" CustomCommandText1=Êtes-vous sûr de vouloir mettre à jour le " -"logiciel système ?\n" -" CustomCommandTooltip1=Met à jour le système\n" -" CustomCommandNoRestart1=true\n" -" \n" -" CustomCommand3=/sbin/fais_quelque_chose\n" -" .\n" -" .\n" -" .\n" -" \n" -" CustomCommand4=/sbin/fais_autre_chose\n" -" .\n" -" .\n" -" .\n" -" </screen>" - -#: ../C/gdm.xml:7765(title) -msgid "Troubleshooting" -msgstr "Dépannage" - -#: ../C/gdm.xml:7767(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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome." -"org</ulink> or send an email to the <address><email>gdm-list@gnome.org</" -"email></address> mail list." -msgstr "" -"Cette section présente des astuces pratiques pour faire fonctionner GDM. En " -"général, si vous rencontrez des problèmes dans l'utilisation de GDM, vous " -"pouvez soumettre une anomalie dans la catégorie « gdm » de <ulink type=\"http" -"\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink> ou vous " -"pouvez envoyer un courriel à la liste de diffusion <address><email>gdm-" -"list@gnome.org</email></address>" - -#: ../C/gdm.xml:7777(para) -msgid "" -"If GDM is failing to work properly, it is always a good idea to include " -"debug information. Use the <command>gdmsetup</command> 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 (<filename><var>/log/messages</filename> or " -"<filename><var>/adm/messages</filename> 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 "" -"Si GDM ne fonctionne pas correctement, il est toujours utile de fournir des " -"informations de débogage. Utilisez la commande <command>gdmsetup</command> " -"pour activer le débogage (« Activer les messages de débogage dans les " -"journaux système » de l'onglet Sécurité), puis amenez GDM à l'endroit où se " -"pose le problème et faites part de la sortie de GDM récoltée dans votre " -"journal système (<filename><var>/log/messages</filename> ou " -"<filename><var>/adm/messages</filename> selon votre système " -"d'exploitation). Dans la mesure où le journal système peut être très long, " -"extrayez uniquement les informations liées à GDM et n'envoyez pas le fichier " -"entier. Si vous ne voyez pas apparaître de données GDM dans le journal " -"système, il peut être nécessaire de configurer syslog (voir la page de " -"manuel syslog.3c)." - -#: ../C/gdm.xml:7791(para) -msgid "" -"You should not leave debug on after collecting data. It will clutter your " -"syslog and slow system performance." -msgstr "" -"Vous ne devriez pas laisser activés les messages de débogage après avoir " -"récolté les données. Cela va surcharger votre journal système et ralentir " -"les performances du système." - -#: ../C/gdm.xml:7797(title) -msgid "GDM Will Not Start" -msgstr "GDM ne démarre pas" - -#: ../C/gdm.xml:7799(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 "" -"Il existe de nombreux problèmes qui peuvent empêcher le démarrage de GDM, " -"mais dans cette section, nous abordons quelques problèmes courants et la " -"manière de suivre attentivement un problème lors du démarrage de GDM. " -"Certains problèmes génèrent un message d'erreur ou une boîte de dialogue de " -"GDM lorsqu'il essaie de démarrer, mais lorsque ce n'est pas le cas, il est " -"souvent difficile de trouver les causes d'un problème." - -#: ../C/gdm.xml:7808(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 "" -"Tout d'abord, assurez-vous que le serveur X est correctement configuré. Le " -"fichier de configuration de GDM contient une commande utilisée pour lancer " -"le serveur X, dans la section [server-Standard]. Vérifiez que cette commande " -"fonctionne sur votre système. Le lancement de cette commande à partir d'une " -"console devrait démarrer le serveur X. Si cela échoue, le problème est " -"probablement dû à la configuration du serveur X. Consultez le journal " -"d'erreurs du serveur X pour obtenir des informations sur la cause possible " -"du problème. Le problème pourrait aussi être dû au fait que le serveur X ait " -"besoin d'options de ligne de commande différentes. Si c'est le cas, modifiez " -"la commande du serveur X dans le fichier de configuration de GDM afin qu'il " -"corresponde aux besoins de votre système." - -#: ../C/gdm.xml:7821(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 <command><" -"lib>/gdmlogin</command> or <command><lib>/gdmgreeter</command>. 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 "" -"Un autre problème courant est que le programme de la bannière GDM a des " -"difficultés à démarrer. Cela peut arriver, par exemple, si GDM ne peut pas " -"trouver une bibliothèque nécessaire ou une autre ressource. Essayez de " -"lancer le serveur X et un terminal, définissez la variable d'environnement " -"de shell DOING_GDM_DEVELOPMENT=1 et exécutez <command><lib>/gdmlogin</" -"command> ou <command><lib>/gdmgreeter</command>. Tout message d'erreur " -"apparaissant dans le terminal peut être une indication utile sur la cause du " -"problème. Il est aussi possible d'activer le débogage et de contrôler les " -"résultats apparaissant dans le journal système pour donner un éclairage sur " -"le problème." - -#: ../C/gdm.xml:7834(para) -msgid "" -"Also make sure that the <filename>/tmp</filename> directory has reasonable " -"ownership and permissions, and that the machine's file system is not full. " -"These problems will cause GDM to fail to start." -msgstr "" -"Vérifiez aussi que le répertoire <filename>/tmp</filename> dispose d'un " -"propriétaire convenable avec des permissions adéquates, et que le système de " -"fichier de la machine n'est pas saturé. Ces problèmes empêchent GDM de " -"démarrer." - -#: ../C/gdm.xml:7842(title) -msgid "GDM Will Not Access User Settings" -msgstr "GDM n'accède pas aux paramètres de l'utilisateur" - -#: ../C/gdm.xml:7844(para) -msgid "" -"GDM saves user settings, such as your default session and default language, " -"in the <filename>~/.dmrc</filename>. Other files, such as the user's " -"<filename>~/.Xauthority</filename> 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 <filename>RelaxPermissions</filename> 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 "" -"GDM enregistre les paramètres des utilisateurs, tels que la session par " -"défaut et la langue par défaut dans le fichier <filename>~/.dmrc</filename>. " -"D'autres fichiers, comme le fichier <filename>~/.Xauthority</filename> de " -"l'utilisateur a aussi une influence sur la connexion. Par défaut, GDM est " -"strict sur la manière d'accéder aux fichiers du dossier personnel de " -"l'utilisateur, et il ignore tout fichier qui ne respecte pas certaines " -"règles. Vous pouvez utiliser l'option de configuration " -"<filename>RelaxPermissions</filename> pour que GDM soit moins strict dans sa " -"manière d'accéder aux fichiers du dossier personnel des utilisateurs. Vous " -"pouvez aussi corriger les problèmes de permissions qui empêchent GDM " -"d'accéder aux fichiers. Tout ceci est abordé en détails dans la section " -"« Accès aux fichiers » du chapitre Aperçu." - -#: ../C/gdm.xml:7863(title) -msgid "License" -msgstr "Licence" - -#: ../C/gdm.xml:7864(para) -msgid "" -"This program is free software; you can redistribute it and/or modify it " -"under the terms of the <ulink type=\"help\" url=\"gnome-help:gpl" -"\"><citetitle>GNU General Public License</citetitle></ulink> as published by " -"the Free Software Foundation; either version 2 of the License, or (at your " -"option) any later version." -msgstr "" -"Ce programme est un logiciel libre ; vous pouvez le redistribuer et/ou le " -"modifier conformément aux dispositions de la <ulink type=\"help\" url=" -"\"gnome-help:gpl\"><citetitle>Licence Publique Générale GNU</citetitle></" -"ulink>, telle que publiée par la Free Software Foundation ; version 2 de la " -"licence, ou encore (à votre choix) toute version ultérieure." - -#: ../C/gdm.xml:7872(para) -msgid "" -"This program is distributed in the hope that it will be useful, but WITHOUT " -"ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or " -"FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public " -"License</citetitle> for more details." -msgstr "" -"Ce programme est distribué dans l'espoir qu'il sera utile, mais SANS AUCUNE " -"GARANTIE ; sans même la garantie implicite de COMMERCIALISATION ou " -"D'ADAPTATION À UN OBJET PARTICULIER. Pour plus de détails, voir la " -"<citetitle>Licence Publique Générale GNU</citetitle>." - -#: ../C/gdm.xml:7878(para) -msgid "" -"A copy of the <citetitle>GNU General Public License</citetitle> is included " -"as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also " -"obtain a copy of the <citetitle>GNU General Public License</citetitle> from " -"the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://" -"www.fsf.org\">their Web site</ulink> or by writing to <address> Free " -"Software Foundation, Inc. <street>51 Franklin Street, Fifth Floor</" -"street><city>Boston</city>, <state>MA</state><postcode>02110-1301</" -"postcode><country>USA</country></address>" -msgstr "" -"Un exemplaire de la <citetitle>Licence Publique Générale GNU</citetitle> est " -"inclus en annexe du <citetitle>Guide d'utilisation du bureau GNOME</" -"citetitle>. Vous pouvez également en obtenir un exemplaire en visitant " -"<ulink type=\"http\" url=\"http://www.fsf.org\">le site Web</ulink> de la " -"Free Software Foundation ou en écrivant à <address> Free Software " -"Foundation, Inc. <street>51 Franklin Street, Fifth Floor</" -"street><city>Boston</city>, <state>MA</state><postcode>02110-1301</" -"postcode><country>USA</country></address>" - -#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2. -#: ../C/gdm.xml:0(None) -msgid "translator-credits" -msgstr "" -"Jonathan Ernst <jonathan@ernstfamily.ch>, 2006,2007.\n" -"Gabriel De Sa <gabriel.desa@gmail.com>, 2007.\n" -"Claude Paroz <claude@2xlibre.net, 2007." diff --git a/docs/gdm.1 b/docs/gdm.1 deleted file mode 100644 index ebe7a6b2..00000000 --- a/docs/gdm.1 +++ /dev/null @@ -1,81 +0,0 @@ -.\" gdm.1 - GNOME Display Manager -.\" Copyright 2003 Red Hat, Inc. -.TH GDM 1 "Aug 21 2003" "GDM 2.4.2.102" -.SH NAME -GDM \- The GNOME Display Manager -.SH SYNOPSIS -.B gdm [options] -.br -.B gdm-binary [options] -.br -.B gdmsetup [options] -.br -.B gdm-stop -.br -.B gdm-restart -.br -.B gdm-safe-restart -.SH DESCRIPTION -GDM is a replacement for XDM, the X Display Manager. Unlike its -competitors (X3DM, KDM, WDM) GDM was written from scratch and -does not contain any original XDM / X Consortium code. GDM runs and -manages the X servers for both local and remote logins (using XDMCP). -See http://www.gnome.org/projects/gdm/ for more details. -.P -.B gdm -is just a script that runs the actual -.B gdm-binary -executable. -.B gdm-stop -is a script that stops the current running daemon immediately, -.B gdm-restart -restarts the current daemon immediately and -.B gdm-safe-restart -restarts the current daemon after everyone has logged out. -.B gdmsetup -is a graphical tool for easily changing the most commonly -used options. -.P -For full documentation see the GNOME help browser -under the -.B Applications / System Tools -section. -.SH OPTIONS -.B gdm -and thus also -.B gdm-binary -accept the following options: -.TP -.BI \-nodaemon -Do not fork into the background -.TP -.BI \-\-no\-console -No console (local) servers to be run -.TP -.BI \-\-preserve\-ld\-vars -Preserve LD_* variables -.TP -.BI \-\-version -Print the GDM version -.TP -.BI \-\-help -Print simple description of accepted options -.P -.B gdmsetup -accepts all standard GNOME options. -.SH CONFIGURATION -Configuration is done either by running -.B gdmsetup -or by editting the /etc/X11/gdm/gdm.conf (usually, -could also be /etc/gdm/gdm.conf) file. The graphical -tool does not support all the options possible so -editting the configuration file is sometimes necessary. -.SH AUTHOR -.B GDM -is being written and maintained by George (Jiri) Lebl <jirka@5z.com> -based on the original codebase by Martin K. Peterson <mkp@mkp.net>. -.SH SEE ALSO -.BR X (7x), -.BR xdm (1), -.BR Xsecurity (7x), -.BR Xserver (1), diff --git a/docs/gdm.omf.in b/docs/gdm.omf.in deleted file mode 100644 index 71ffa178..00000000 --- a/docs/gdm.omf.in +++ /dev/null @@ -1,9 +0,0 @@ -<?xml version="1.0" standalone="no"?> -<omf> - <resource> - <subject category="GNOME|System"/> - <type>manual</type> - <relation seriesid="61d86786-ba0d-11d7-9eda-8a77bf52d52a"/> - <rights type="GNU FDL" license.version="1.1" holder="George Lebl and Martin K. Petersen"/> - </resource> -</omf> diff --git a/docs/it/.cvsignore b/docs/it/.cvsignore deleted file mode 100644 index ab4d4d42..00000000 --- a/docs/it/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -Makefile -Makefile.in -*.out -omf_timestamp diff --git a/docs/it/figures/gdm_window.png b/docs/it/figures/gdm_window.png Binary files differdeleted file mode 100644 index 813e3a4b..00000000 --- a/docs/it/figures/gdm_window.png +++ /dev/null diff --git a/docs/it/gdm-it.omf b/docs/it/gdm-it.omf deleted file mode 100644 index 6e8b270b..00000000 --- a/docs/it/gdm-it.omf +++ /dev/null @@ -1,18 +0,0 @@ -<?xml version="1.0" encoding="UTF8"?> <omf> - <resource> - <creator>docs@gnome.org (GDP) </creator> - <maintainer>docs@gnome.org (GDP) </maintainer> - <title>Manuale della Configurazione della schermata di login V2.0.1 </title> - <date>2004-01-19 </date> - <version identifier="2.0.1" date="2004-01-19" description="Creato per Quicksilver, versione programma 2.4.2.101"/> - <subject category="GNOME|Applications|System Tools"/> - - <description>Manuale utente dell'applicazione Configurazione della schermata di login. </description> - <type>user's guide </type> - <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/> - <identifier url="gdm.xml"/> - <language code="it"/> - <relation seriesid="be6a0524-46d3-11d8-983d-e135363498a8"/> - <rights type="GNU FDL" license.version="1.1" holder="Sun Microsystems"/> - </resource> -</omf> diff --git a/docs/ja/.cvsignore b/docs/ja/.cvsignore deleted file mode 100644 index ab4d4d42..00000000 --- a/docs/ja/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -Makefile -Makefile.in -*.out -omf_timestamp diff --git a/docs/ja/figures/gdm_window.png b/docs/ja/figures/gdm_window.png Binary files differdeleted file mode 100644 index 2dc78e34..00000000 --- a/docs/ja/figures/gdm_window.png +++ /dev/null diff --git a/docs/ja/gdm-ja.omf b/docs/ja/gdm-ja.omf deleted file mode 100644 index ff8af3c0..00000000 --- a/docs/ja/gdm-ja.omf +++ /dev/null @@ -1,19 +0,0 @@ -<?xml version="1.0" encoding="UTF8"?> -<omf> - <resource> - <creator>docs@gnome.org (GDP) </creator> - <maintainer>docs@gnome.org (GDP) </maintainer> - <title>ログイン画面設定マニュアル V2.0.1 </title> - <date>2004-01-19 </date> - <version identifier="2.0.1" date="2004-01-19" description="Quicksilver のために作成。プログラムバージョン 2.4.2.101"/> - <subject category="GNOME|Applications|System Tools"/> - - <description>ログイン画面設定アプリケーションのユーザーマニュアル </description> - <type>ユーザーズガイド </type> - <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/> - <identifier url="gdm.xml"/> - <language code="ja"/> - <relation seriesid="be6a0524-46d3-11d8-983d-e135363498a8"/> - <rights type="GNU FDL" license.version="1.1" holder="Sun Microsystems"/> - </resource> -</omf> diff --git a/docs/ko/.cvsignore b/docs/ko/.cvsignore deleted file mode 100644 index ab4d4d42..00000000 --- a/docs/ko/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -Makefile -Makefile.in -*.out -omf_timestamp diff --git a/docs/ko/ko.po b/docs/ko/ko.po deleted file mode 100644 index 52033df1..00000000 --- a/docs/ko/ko.po +++ /dev/null @@ -1,5092 +0,0 @@ -# Sun Microsystems, 2003, 2004. -# Changwoo Ryu <cwryu@debian.org>, 2007. -# -msgid "" -msgstr "" -"Project-Id-Version: gdm help\n" -"POT-Creation-Date: 2007-04-13 04:42+0900\n" -"PO-Revision-Date: 2007-04-13 08:28+0900\n" -"Last-Translator: Changwoo Ryu <cwryu@debian.org>\n" -"Language-Team: GNOME Korea <gnome-kr-hackers@lists.kldp.net>\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../C/legal.xml:2(para) -msgid "Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or in the file COPYING-DOCS distributed with this manual." -msgstr "" - -#: ../C/legal.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) -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) -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) -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) -msgid "DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: <placeholder-1/>" -msgstr "" - -#: ../C/gdm.xml:11(title) -msgid "Gnome Display Manager Reference Manual" -msgstr "그놈 화면 관리자 참고서" - -#: ../C/gdm.xml:15(revnumber) -msgid "0.0" -msgstr "0.0" - -#: ../C/gdm.xml:16(date) -msgid "2007-01" -msgstr "2007-01" - -#: ../C/gdm.xml:21(para) -msgid "GDM is the GNOME Display Manager, a graphical login program." -msgstr "" - -#: ../C/gdm.xml:28(firstname) -msgid "Martin" -msgstr "Martin" - -#: ../C/gdm.xml:28(othername) -msgid "K." -msgstr "K." - -#: ../C/gdm.xml:29(surname) -msgid "Petersen" -msgstr "Petersen" - -#: ../C/gdm.xml:31(email) -msgid "mkp@mkp.net" -msgstr "mkp@mkp.net" - -#: ../C/gdm.xml:35(firstname) -msgid "George" -msgstr "George" - -#: ../C/gdm.xml:35(surname) -msgid "Lebl" -msgstr "Lebl" - -#: ../C/gdm.xml:37(email) -msgid "jirka@5z.com" -msgstr "jirka@5z.com" - -#: ../C/gdm.xml:41(firstname) -msgid "Brian" -msgstr "Brian" - -#: ../C/gdm.xml:41(surname) -msgid "Cameron" -msgstr "Cameron" - -#: ../C/gdm.xml:43(email) -msgid "Brian.Cameron@Sun.COM" -msgstr "Brian.Cameron@Sun.COM" - -#: ../C/gdm.xml:47(firstname) -msgid "Bill" -msgstr "Bill" - -#: ../C/gdm.xml:47(surname) -msgid "Haneman" -msgstr "Haneman" - -#: ../C/gdm.xml:49(email) -msgid "Bill.Haneman@Sun.COM" -msgstr "Bill.Haneman@Sun.COM" - -#: ../C/gdm.xml:54(year) -msgid "1998" -msgstr "1998" - -#: ../C/gdm.xml:54(year) -msgid "1999" -msgstr "1999" - -#: ../C/gdm.xml:54(holder) -msgid "Martin K. Petersen" -msgstr "Martin K. Petersen" - -#: ../C/gdm.xml:57(year) -msgid "2001" -msgstr "2001" - -#: ../C/gdm.xml:57(year) ../C/gdm.xml:61(year) ../C/gdm.xml:64(year) -msgid "2003" -msgstr "2003" - -#: ../C/gdm.xml:57(year) ../C/gdm.xml:64(year) -msgid "2004" -msgstr "2004" - -#: ../C/gdm.xml:58(holder) -msgid "George Lebl" -msgstr "George Lebl" - -#: ../C/gdm.xml:61(holder) -msgid "Red Hat, Inc." -msgstr "Red Hat, Inc." - -#: ../C/gdm.xml:64(holder) -msgid "Sun Microsystems, Inc." -msgstr "Sun Microsystems, Inc." - -#: ../C/gdm.xml:69(releaseinfo) ../C/gdm.xml:78(para) -msgid "This manual describes version 2.19.0 of the GNOME Display Manager. It was last updated on 03/23/2007." -msgstr "" - -#: ../C/gdm.xml:76(title) -msgid "Terms and Conventions Used in This Manual" -msgstr "이 설명서의 용어 및 관례" - -#: ../C/gdm.xml:83(para) -msgid "Chooser - A program used to select a remote host for managing a display remotely on the local display (<command>gdmchooser</command>)." -msgstr "" - -#: ../C/gdm.xml:88(para) -msgid "Configurator - The configuration application (<command>gdmsetup</command>)." -msgstr "" - -#: ../C/gdm.xml:93(para) -msgid "GDM - Gnome Display Manager. Used to describe the software package as a whole. Sometimes also referred to as GDM2." -msgstr "" - -#: ../C/gdm.xml:98(para) -msgid "gdm - The Gnome Display Manager daemon (<command>gdm</command>)." -msgstr "" - -#: ../C/gdm.xml:102(para) -msgid "Greeter - The graphical login window (<command>gdmlogin</command> or <command>gdmgreeter</command>)." -msgstr "" - -#: ../C/gdm.xml:107(para) -msgid "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)." -msgstr "" - -#: ../C/gdm.xml:111(para) -msgid "PAM - Pluggable Authentication Mechanism" -msgstr "" - -#: ../C/gdm.xml:115(para) -msgid "Themed Greeter - The themable login window ( <command>gdmgreeter</command>)." -msgstr "" - -#: ../C/gdm.xml:120(para) -msgid "XDMCP - X Display Manage Protocol" -msgstr "" - -#: ../C/gdm.xml:124(para) -msgid "Paths that start with a word in angle brackets are relative to the installation prefix. I.e. <filename><share>/pixmaps/</filename> refers to <filename><share>/pixmaps</filename> if GDM was configured with <command>--prefix=/usr</command>. Normally also note that GDM is installed with <command>--sysconfigdir=<etc>/X11</command>, meaning any path to which we refer to as <filename><etc>/gdm/PreSession</filename> usually means <filename><etc/X11>/gdm/PreSession</filename>. Note that for interoperability it is recommended that you use a --prefix of <filename>/usr</filename> and a --sysconfdir of <filename><etc>/X11</filename>." -msgstr "" - -#: ../C/gdm.xml:140(title) -msgid "Overview" -msgstr "개요" - -#: ../C/gdm.xml:143(title) -msgid "Introduction" -msgstr "" - -#: ../C/gdm.xml:147(para) -msgid "The Gnome Display Manager (GDM) is a display manager that implements all significant features required for managing local and remote displays. GDM was written from scratch and does not contain any XDM / X Consortium code." -msgstr "" - -#: ../C/gdm.xml:154(para) -msgid "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:160(para) -msgid "For further information about GDM, see the <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. Please submit any bug reports or enhancement requests to the \"gdm\" category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>. You can also send a message to the <address><email>gdm-list@gnome.org</email></address> mail list to discuss any issues or concerns with the GDM program." -msgstr "" - -#: ../C/gdm.xml:173(title) -msgid "Interface Stability" -msgstr "" - -#: ../C/gdm.xml:177(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:191(para) -msgid "Command-line interfaces for GDM programs installed to <filename><bin></filename> and <filename><sbin></filename> 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:199(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 <command>gdmchooser</command>. These arguments have been changed to now use two dashes." -msgstr "" - -#: ../C/gdm.xml:207(para) -msgid "If issues are discovered that break compatibility, please file a bug with an \"urgent\" priority." -msgstr "" - -#: ../C/gdm.xml:214(title) -msgid "The GDM Daemon" -msgstr "" - -#: ../C/gdm.xml:216(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 <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename>, and <filename>PostSession</filename> scripts discussed below are discussed in this \"Configuring GDM section\"." -msgstr "" - -#: ../C/gdm.xml:227(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:234(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 <command>gdmflexiserver</command> command. Displays that are started on request are not restarted on session exit. GDM also provides the <command>gdmdynamic</command> 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:246(para) -msgid "When the GDM daemon is asked to manage a display, it will fork an X server process, then run the <filename>Init</filename> script as the root user, and start the login GUI dialog as a slave process on the display. GDM can be configured to use either <command>gdmgreeter</command> (the default) or <command>gdmlogin</command> as the GUI dialog program. The <command>gdmlogin</command> program supports accessibility while the <command>gdmgreeter</command> program supports greater themeability. The GUI dialog is run as the unpriviledged \"gdm\" user/group which is described in the \"Security\" section below. The GUI dialog communicates with the daemon via a sockets protocol and via standard input/output. The slave, for example passes the username and password information to the GDM daemon via standard input/output so the daemon can handle the actual authentication." -msgstr "" - -#: ../C/gdm.xml:263(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:278(para) -msgid "GDM, by default, will use Pluggable Authentication Modules (PAM) for authentication, but can also support regular crypt and shadow passwords on legacy systems. After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, and forks a slave process to start the requested session. This slave process runs the <filename>PreSession</filename> script as root, sets up the user's environment, and starts the requested session. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN interface after user authentication to tell the X server to be restarted as the user instead of as root for added security. When the user's session exits, the GDM daemon will run the <filename>PostSession</filename> script as root." -msgstr "" - -#: ../C/gdm.xml:295(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 <filename>PamStack</filename> 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:305(para) -msgid "For those looking at the code, the gdm_verify_user function in <filename>daemon/verify-pam.c</filename> is used for normal login and the gdm_verify_setup_user function is used for automatic login." -msgstr "" - -#: ../C/gdm.xml:313(title) -msgid "Different Display Types" -msgstr "" - -#: ../C/gdm.xml:315(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:323(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:333(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:347(para) -msgid "Flexible displays may be started by running the <command>gdmflexiserver</command> 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:360(para) -msgid "The <filename>FlexibleXServers</filename>, <filename>FirstVT=7</filename>, <filename>VTAllocation</filename>, and <filename>FlexiReapDelayMinutes</filename> configuration settings are used to configure how flexible displays operate." -msgstr "" - -#: ../C/gdm.xml:367(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 <command>gdmflexiserver -n</command> 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 <filename>Xnest</filename> configuration option is used to configure how nested displays operate" -msgstr "" - -#: ../C/gdm.xml:380(para) -msgid "The <command>gdmdynamic</command> is similar to <command>gdmflexiserver</command> in the sense that it allows the user to manage displays dynamically. However displays started with <command>gdmdynamic</command> 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:395(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:406(title) -msgid "XDMCP" -msgstr "XDMCP" - -#: ../C/gdm.xml:410(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:419(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:427(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:432(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:442(para) -msgid "If XDMCP seems to not be working, make sure that all machines are specified in <filename>/etc/hosts</filename>." -msgstr "" - -#: ../C/gdm.xml:447(para) -msgid "Refer to the \"Security\" section for information about security concerns when using XDMCP." -msgstr "" - -#: ../C/gdm.xml:454(title) -msgid "Securing Remote Connection Through SSH" -msgstr "" - -#: ../C/gdm.xml:457(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:464(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:474(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:481(title) -msgid "The GTK+ Greeter" -msgstr "" - -#: ../C/gdm.xml:483(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:491(para) -msgid "The text entry field is used for entering logins, passwords, passphrases etc. <command>gdmlogin</command> 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:501(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:509(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 <filename>Logo</filename> option in the reference section below for details." -msgstr "" - -#: ../C/gdm.xml:519(title) -msgid "The Themed Greeter" -msgstr "" - -#: ../C/gdm.xml:521(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 <filename>GraphicalTheme</filename> 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:531(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:541(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:549(title) -msgid "The GDM Face Browser" -msgstr "" - -#: ../C/gdm.xml:551(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 <filename>Browser</filename> 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:561(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 <command>gdmsetup</command>. This feature is most practical to use on a system with a smaller number of users." -msgstr "" - -#: ../C/gdm.xml:570(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 <filename><share>/pixmaps/faces/</filename> directory (though this can be configured with the <filename>GlobalFaceDir</filename> configuration option) and the filename should be the name of the user, optionally with a <filename>.png</filename> 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:583(para) -msgid "Users may run the <command>gdmphotosetup</command> command to configure the image to use for their userid. This program properly scales the file down if it is larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> configuration options and places the icon in a file called <filename>~/.face</filename>. Although <command>gdmphotosetup</command> scales user images automatically, this does not guarantee that user images are properly scaled since a user may create their <filename>~/.face</filename> file by hand." -msgstr "" - -#: ../C/gdm.xml:595(para) -msgid "GDM will first look for the user's face image in <filename>~/.face</filename>. If not found, it will try <filename>~/.face.icon</filename>. If still not found, it will use the value defined for \"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file. Lastly, it will try <filename>~/.gnome2/photo</filename> and <filename>~/.gnome/photo</filename> which are deprecated and supported for backwards compatibility." -msgstr "" - -#: ../C/gdm.xml:606(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 <filename>DefaultFace</filename> configuration option, normally <filename><share>/pixmaps/nobody.png</filename>." -msgstr "" - -#: ../C/gdm.xml:614(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 <filename>Include</filename> 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 <filename>GlobalFaceDir</filename> configuration option." -msgstr "" - -#: ../C/gdm.xml:630(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 <filename>IncludeAll</filename> option is set to true, then the password file will be scanned and all users will be displayed. If <filename>IncludeAll</filename> option is set to false, then the <filename>Include</filename> option should contain a list of users separated by commas. Only the users specified will be displayed. Any user listed in the <filename>Exclude</filename> option and users whose UID's is lower than <filename>MinimalUID</filename> will be filtered out regardless of the <filename>IncludeAll</filename> setting. <filename>IncludeAll</filename> 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:647(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:656(title) -msgid "Logging" -msgstr "" - -#: ../C/gdm.xml:658(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:665(para) -msgid "Output from the various X servers is stored in the GDM log directory, which is configurable, but is usually <filename><var>/log/gdm/</filename>. The output from the session can be found in a file called <filename><display>.log</filename>. Four older files are also stored with <filename>.1</filename> through <filename>.4</filename> 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:677(para) -msgid "The output from the user session is redirected to <filename>~/.xsession-errors</filename> before even the <filename>PreSession</filename> 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:689(para) -msgid "You can suppress the 10 second warning by returning code 66 from the <filename>Xsession</filename>script or from your session binary (the default <filename>Xsession</filename> 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:699(para) -msgid "The session output is piped through the GDM daemon and so the <filename>~/.xsession-errors</filename> 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:712(para) -msgid "Note that some distributors seem to override the <filename>~/.xsession-errors</filename> redirection and do it themselves in their own Xsession script (set by the <filename>BaseXsession</filename> configuration key) which means that GDM will not be able to trap the output and cap this file. You also lose output from the <filename>PreSession</filename> 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 <filename>BaseXsession</filename> configuration key for more information, especially on how to handle multiple display managers using the same script." -msgstr "" - -#: ../C/gdm.xml:726(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 <filename>/tmp</filename> directory named <filename>/tmp/xses-<user>.XXXXXX</filename> where the <filename>XXXXXX</filename> are some random characters." -msgstr "" - -#: ../C/gdm.xml:734(para) -msgid "If you run a system with quotas set, it would be good to delete the <filename>~/.xsession-errors</filename> in the <filename>PostSession</filename> script. Such that this log file doesn't unnecessarily stay around." -msgstr "" - -#: ../C/gdm.xml:743(title) -msgid "Accessing Files" -msgstr "" - -#: ../C/gdm.xml:745(para) -msgid "In general GDM is very reluctant regarding reading/writing of user files (such as the <filename>~/.dmrc</filename>, <filename>~/.face</filename>, <filename>~/.xsession-errors</filename>, and <filename>~/.Xauthority</filename> files). For instance it refuses to access anything but regular files. Links, sockets and devices are ignored. The value of the <filename>RelaxPermissions</filename> parameter determines whether GDM should accept files writable by the user's group or others. These are ignored by default." -msgstr "" - -#: ../C/gdm.xml:757(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 <filename>.Xauthority</filename> file, a fallback cookie is created in the directory specified by the <filename>UserAuthFBDir</filename> configuration setting (<filename>/tmp</filename> by default)." -msgstr "" - -#: ../C/gdm.xml:765(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:776(title) -msgid "GDM Performance" -msgstr "" - -#: ../C/gdm.xml:778(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:786(para) -msgid "To use this feature, configure GDM with the <command>--with-prefetch</command> option. This will cause GDM to install the <command>gdmprefetch</command> program to the <filename>libexecdir</filename> directory, install the <filename>gdmprefetchlist</filename> to the <filename><etc>/gdm</filename> directory, and set the <filename>PreFetchProgram</filename> configuration variable so that the <command>gdmprefetch</command> program is called with the default <filename>gdmprefetchlist</filename> file. The default <filename>gdmprefetchlist</filename> 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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>, so that they can be included in future GDM releases." -msgstr "" - -#: ../C/gdm.xml:807(title) -msgid "Security" -msgstr "보안" - -#: ../C/gdm.xml:810(title) -msgid "PAM" -msgstr "PAM" - -#: ../C/gdm.xml:814(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:820(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:827(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:837(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:844(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 <address><email>gdm-list@gnome.org</email></address> mail list, so you can refer to the list archives for more information." -msgstr "" - -#: ../C/gdm.xml:854(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 <filename>PamStack</filename> 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:869(title) -msgid "The GDM User" -msgstr "" - -#: ../C/gdm.xml:871(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:877(para) -msgid "The GDM daemon normally runs as root, as does the slave. However GDM should also have a dedicated user id and a group id which it uses for its graphical interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</command>. These are configured via the <filename>User</filename> and <filename>Group</filename> configuration options in the GDM configuration files. The user and group should be created before running \"make install\". By default GDM assumes the user and the group are called \"gdm\"." -msgstr "" - -#: ../C/gdm.xml:888(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:895(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 <filename><var>/lib/gdm</filename>. 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:906(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 <filename>nobody</filename>. 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:918(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:929(title) -msgid "X Server Authentication Scheme" -msgstr "" - -#: ../C/gdm.xml:931(para) -msgid "The X server authorization directory (the <filename>ServAuthDir</filename>) 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 <filename>root.gdm</filename> 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:943(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:952(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:965(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 <filename>/dev/audio</filename> or <filename>/dev/mem</filename> 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 <filename>UserAuthDir</filename> configuration key). So be careful about where you use remote X display." -msgstr "" - -#: ../C/gdm.xml:982(title) -msgid "Firewall Security" -msgstr "" - -#: ../C/gdm.xml:984(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:994(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:1001(para) -msgid "X is not a very safe protocol for leaving on the net, and XDMCP is even less safe." -msgstr "" - -#: ../C/gdm.xml:1008(title) -msgid "GDM Security With NFS" -msgstr "" - -#: ../C/gdm.xml:1010(para) -msgid "Note that NFS traffic really goes \"over the wire\" and thus can be snooped. When accessing the user's X authorization file (<filename>~/.Xauthority</filename>), 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 <filename>UserAuthFBDir</filename>, which by default is set to <filename>/tmp</filename>. This behavior can be changed by setting the <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false." -msgstr "" - -#: ../C/gdm.xml:1024(title) -msgid "XDMCP Security" -msgstr "" - -#: ../C/gdm.xml:1026(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:1032(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:1041(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:1048(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:1056(title) -msgid "XDMCP Access Control" -msgstr "" - -#: ../C/gdm.xml:1058(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:1064(para) -msgid "You should use the daemon name <command>gdm</command> in the <filename><etc>/hosts.allow</filename> and <filename><etc>/hosts.deny</filename> files. For example to deny computers from <filename>.evil.domain</filename> from logging in, then add" -msgstr "" - -#: ../C/gdm.xml:1071(screen) -#, no-wrap -msgid "\ngdm: .evil.domain\n" -msgstr "" - -#: ../C/gdm.xml:1074(para) -msgid "to <filename><etc>/hosts.deny</filename>. You may also need to add" -msgstr "" - -#: ../C/gdm.xml:1078(screen) -#, no-wrap -msgid "\ngdm: .your.domain\n" -msgstr "" - -#: ../C/gdm.xml:1081(para) -msgid "to your <filename><etc>/hosts.allow</filename> if you normally disallow all services from all hosts. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" - -#: ../C/gdm.xml:1091(title) -msgid "Support for ConsoleKit" -msgstr "ConsoleKit 지원" - -#: ../C/gdm.xml:1093(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:1101(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:1114(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:1123(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:1128(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:1137(title) -msgid "Using gdmsetup To Configure GDM" -msgstr "gdmsetup으로 GDM 설정하기" - -#: ../C/gdm.xml:1139(para) -msgid "The <command>gdmsetup</command> 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 <command>gdmsetup</command>. Editing the files by hand is explained in the \"Configuration\" section of this document. Note that <command>gdmsetup</command> 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:1150(para) -msgid "The <command>gdmsetup</command> 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:1160(title) -msgid "Local Tab" -msgstr "" - -#: ../C/gdm.xml:1162(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:1172(para) -msgid "If the \"Style\" choice is \"Plain\", then GDM will use the <command>gdmlogin</command> program as the GUI (daemon/Greeter). When this choice is selected, <command>gdmsetup</command> 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:1186(para) -msgid "If the \"Style\" choice is \"Plain with face browser\", then the <command>gdmlogin</command> 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:1196(para) -msgid "If the \"Style\" choice is \"Themed\", then the <command>gdmgreeter</command> program is used as the GUI (daemon/Greeter). When this choice is selected, <command>gdmsetup</command> 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:1218(para) -msgid "If the \"Style\" choice is \"Themed with face browser\", then the <command>gdmgreeter</command> 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:1229(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 <command>gdmsetup</command> (greeter/ConfigAvailable), and whether the Action menu includes the choice to start <command>gdmchooser</command> to run a remote XDMCP login session (greeter/ChooserButton). Note that the root password must be entered to start <command>gdmsetup</command> 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:1246(title) -msgid "Remote Tab" -msgstr "" - -#: ../C/gdm.xml:1248(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:1265(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:1275(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:1283(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:1291(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:1307(title) -msgid "Accessibility Tab" -msgstr "" - -#: ../C/gdm.xml:1309(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:1326(title) -msgid "Security Tab" -msgstr "" - -#: ../C/gdm.xml:1328(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:1343(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:1356(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:1365(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:1375(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:1387(title) -msgid "Users Tab" -msgstr "" - -#: ../C/gdm.xml:1389(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:1407(title) -msgid "Configuration" -msgstr "설정" - -#: ../C/gdm.xml:1409(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:1419(para) -msgid "The <command>gdmsetup</command> 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:1431(para) -msgid "Aside from the GDM System Defaults Configuration File, the other GDM configuration files are located, by default, in the <filename><etc>/gdm/</filename> 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:1441(para) -msgid "Listing of the config directory contents:" -msgstr "" - -#: ../C/gdm.xml:1445(screen) -#, no-wrap -msgid "\ncustom.conf\nlocale.alias\nXsession\nXKeepsCrashing\nmodules/\nInit/\nPostLogin/\nPreSession/\nPostSession/\n" -msgstr "" - -#: ../C/gdm.xml:1457(para) -msgid "<filename>locale.alias</filename> 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:1465(para) -msgid "<filename>Xsession</filename> 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 <filename>desktop</filename> file associated with the session the user has picked. Some sessions may start the user's session via a different mechanism than the <filename>Xsession</filename> script, so please check the appropriate <filename>desktop</filename> before assuming a session startup issue is being caused by this file." -msgstr "" - -#: ../C/gdm.xml:1476(para) -msgid "<filename>XKeepsCrashing</filename> 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:1484(para) -msgid "Accessibility modules are configured in the <filename>modules/</filename> 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 <filename>factory</filename> 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:1493(para) -msgid "Files describing available GDM session follow the freedesktop.org desktop file specification. The <filename>.desktop</filename>-style files are installed to <filename><etc>/X11/sessions/</filename>. This directory is also read by the KDE desktop manager (KDM) for common configuration. Next the directory <filename><share>/gdm/BuiltInSessions/</filename> is read for GDM specific built-in sessions (KDM hardcodes these at time of this writing). Lastly the default setup will also read <filename><share>/xsessions/</filename> (which should be <filename><share>/xsessions/</filename> if you really wish to cooperate with KDM) where desktop packages can install their session files. The directories under the <filename><etc></filename> 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 <filename>SessionDesktopDir</filename> configuration key for changing the paths. It used to be that GDM stored its built in sessions in <filename><etc>/dm/Sessions/</filename> but this is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the <filename><etc>/dm/Sessions/</filename> was being read." -msgstr "" - -#: ../C/gdm.xml:1516(para) -msgid "A session can be disabled (if it was installed in <filename><share>/xsessions/</filename>) by adding an identically named <filename>.desktop</filename> to one of the directories earlier in the path (likely <filename><etc>/X11/sessions</filename>) and using <filename>Hidden=true</filename> in that file." -msgstr "" - -#: ../C/gdm.xml:1525(title) -msgid "The Script Directories" -msgstr "" - -#: ../C/gdm.xml:1527(para) -msgid "In this section we will explain the <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> and <filename>PostSession</filename> directories as they are very similar." -msgstr "" - -#: ../C/gdm.xml:1533(para) -msgid "When the X server has been successfully started, GDM will try to run the script called <filename>Init/<displayname></filename>. I.e. <filename>Init/:0</filename> for the first local display. If this file is not found, GDM will attempt to to run <filename>Init/<hostname></filename>. I.e. <filename>Init/somehost</filename>. If this still is not found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins or <filename>Init/Flexi</filename> for all on demand flexible displays. If none of the above were found, GDM will run <filename>Init/Default</filename>. The script will be run as root and GDM blocks until it terminates. Use the <filename>Init/*</filename> 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:1551(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 <filename>KillInitClients</filename> configuration option." -msgstr "" - -#: ../C/gdm.xml:1558(para) -msgid "When the user has been successfully authenticated GDM tries the scripts in the <filename>PostLogin</filename> directory in the same manner as for the <filename>Init</filename> 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 <filename>pam_mount</filename> module if you can for this). You have the <filename>$USER</filename> and <filename>$DISPLAY</filename> 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:1572(para) -msgid "After the user session has been setup from the GDM side of things, GDM will run the scripts in the <filename>PreSession</filename> directory, again in the same manner as the <filename>Init</filename> directory. Use this script for local session management or accounting stuff. The <filename>$USER</filename> environment variable contains the login of the authenticated user and <filename>$DISPLAY</filename> 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 <filename>$X_SERVERS</filename> 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:1587(para) -msgid "After this the base <filename>Xsession</filename> 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 <filename>Exec=</filename> line in the <filename>.desktop</filename> files in the path specified by <filename>SessionDesktopDir</filename>. Usually this path is <filename><etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/xsessions/</filename>. The first found file is used. The user either picks from these sessions or GDM will look inside the file <filename>~/.dmrc</filename> for the stored preference." -msgstr "" - -#: ../C/gdm.xml:1600(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 <filename>$GDM_LANG</filename> 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 <filename>$GDM_LANG</filename> is not set." -msgstr "" - -#: ../C/gdm.xml:1610(para) -msgid "When the user terminates his session, the <filename>PostSession</filename> script will be run. Again operation is similar to <filename>Init</filename>, <filename>PostLogin</filename> and <filename>PreSession</filename>. Again the script will be run with root privileges, the slave daemon will block and the <filename>$USER</filename> environment variable will contain the name of the user who just logged out and <filename>$DISPLAY</filename> will be set to the display the user used, however note that the X server for this display may already be dead and so you shouldn't try to access it. Also <filename>$X_SERVERS</filename> 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:1625(para) -msgid "Note that the <filename>PostSession</filename> script will be run even when the display fails to respond due to an I/O error or similar. Thus, there is no guarantee that X applications will work during script execution." -msgstr "" - -#: ../C/gdm.xml:1632(para) -msgid "Except for the <filename>Xsession</filename> script all of these scripts will also have the environment variable <filename>$RUNNING_UNDER_GDM</filename> set to <filename>yes</filename>, so that you could perhaps use similar scripts for different display managers. The <filename>Xsession</filename> will always have the <filename>$GDMSESSION</filename> set to the basename of the session that the user chose to run without the <filename>.desktop</filename> extension. In addition <filename>$DESKTOP_SESSION</filename> is also set to the same value and in fact this will also be set by KDM in future versions." -msgstr "" - -#: ../C/gdm.xml:1646(para) -msgid "Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> or <filename>PostSession</filename> scripts are necessary and can be left out. The <filename>Xsession</filename> script is however required as well as at least one session <filename>.desktop</filename> file." -msgstr "" - -#: ../C/gdm.xml:1656(title) -msgid "The Configuration Files - GDM System Defaults Configuration File and GDM Custom Configuraiton File" -msgstr "" - -#: ../C/gdm.xml:1659(para) -msgid "GDM uses two configuration files: the GDM System Defaults Configuration File (<filename><share>/gdm/defaults.conf</filename>) and the GDM Custom Configuration File (<filename><etc>/gdm/custom.conf</filename>). 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:1672(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:1679(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 <filename><etc>/gdm/custom.conf<display num></filename>. 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 <filename><etc>/gdm/custom.conf:0</filename>. Per-display configuration is supported in GDM 2.14.6 and later." -msgstr "" - -#: ../C/gdm.xml:1692(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:1703(screen) -#, no-wrap -msgid "\n[daemon]\nGreeter=/usr/lib/gdmgreeter\n" -msgstr "" - -#: ../C/gdm.xml:1708(para) -msgid "The <command>gdmsetup</command> command can be used to modify the GDM Custom Configuration File. Note the <command>gdmsetup</command> 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:1715(para) -msgid "The GDM daemon <command>--config</command> 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 <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options." -msgstr "" - -#: ../C/gdm.xml:1724(para) -msgid "Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</filename> 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 <filename><etc>/gdm/gdm.conf</filename> file is different than the <filename><etc>/gdm/factory-gdm.conf</filename> file. If so, the <filename><etc>/gdm/gdm.conf</filename> file will be automatically copied to <filename><etc>/gdm/custom.conf</filename> to preserve any configuration changes." -msgstr "" - -#: ../C/gdm.xml:1738(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:1747(para) -msgid "The GDM System Defaults Configuration File and the GDM Custom Configuration File follow the standard <filename>.ini</filename> 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:1759(para) -msgid "The following configuration keys are supported in GDM:" -msgstr "" - -#: ../C/gdm.xml:1764(title) -msgid "Daemon Configuration" -msgstr "" - -#: ../C/gdm.xml:1767(title) -msgid "[daemon]" -msgstr "[daemon]" - -#: ../C/gdm.xml:1770(term) -msgid "AddGtkModules" -msgstr "AddGtkModules" - -#: ../C/gdm.xml:1772(synopsis) -#, no-wrap -msgid "AddGtkModules=false" -msgstr "AddGtkModules=false" - -#: ../C/gdm.xml:1773(para) -msgid "If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</command> 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:1780(para) -msgid "If true, then the registry daemon <command>at-spi-registryd</command> will be launched by <command>gdmgreeter</command> or <command>gdmlogin</command> starting with version GDM 2.17." -msgstr "" - -#: ../C/gdm.xml:1786(para) -msgid "Usually this is used for accessibility modules. The modules which are loaded are specified with the <filename>GtkModulesList</filename> key." -msgstr "" - -#: ../C/gdm.xml:1795(term) -msgid "AlwaysLoginCurrentSession" -msgstr "AlwaysLoginCurrentSession" - -#: ../C/gdm.xml:1797(synopsis) -#, no-wrap -msgid "AlwaysLoginCurrentSession=true" -msgstr "AlwaysLoginCurrentSession=true" - -#: ../C/gdm.xml:1798(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:1810(term) -msgid "AutomaticLoginEnable" -msgstr "AutomaticLoginEnable" - -#: ../C/gdm.xml:1812(synopsis) -#, no-wrap -msgid "AutomaticLoginEnable=false" -msgstr "AutomaticLoginEnable=false" - -#: ../C/gdm.xml:1813(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 <filename>TimedLogin</filename>." -msgstr "" - -#: ../C/gdm.xml:1824(term) -msgid "AutomaticLogin" -msgstr "AutomaticLogin" - -#: ../C/gdm.xml:1826(synopsis) -#, no-wrap -msgid "AutomaticLogin=" -msgstr "AutomaticLogin=" - -#: ../C/gdm.xml:1827(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:1835(para) -msgid "The following control chars are recognized within the specified name:" -msgstr "" - -#: ../C/gdm.xml:1840(para) ../C/gdm.xml:3857(para) -msgid "%%— the `%' character" -msgstr "%%— the `%' character" - -#: ../C/gdm.xml:1844(para) -msgid "%d — display's name" -msgstr "" - -#: ../C/gdm.xml:1848(para) -msgid "%h — display's hostname" -msgstr "" - -#: ../C/gdm.xml:1852(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:1865(term) -msgid "BaseXsession" -msgstr "BaseXsession" - -#: ../C/gdm.xml:1867(synopsis) -#, no-wrap -msgid "BaseXsession=<etc>/gdm/Xsession" -msgstr "BaseXsession=<etc>/gdm/Xsession" - -#: ../C/gdm.xml:1868(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 <filename>Exec=</filename> from the <filename>.desktop</filename> file of the session." -msgstr "" - -#: ../C/gdm.xml:1876(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 <filename>GDMSESSION</filename> environmental variable. This will always be set to the basename of <filename>.desktop</filename> (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 <filename>GDM_LANG</filename>, but that is only set when the user picks a non-system default language." -msgstr "" - -#: ../C/gdm.xml:1889(para) -msgid "This script should take care of doing the \"login\" for the user and so it should source the <filename><etc>/profile</filename> and friends. The standard script shipped with GDM sources the files in this order: <filename><etc>/profile</filename> then <filename>~/.profile</filename> then <filename><etc>/xprofile</filename> and finally <filename>~/.xprofile</filename>. Note that different distributions may change this however. Sometimes users personal setup will be in <filename>~/.bash_profile</filename>, however broken that is." -msgstr "" - -#: ../C/gdm.xml:1906(term) -msgid "Chooser" -msgstr "Chooser" - -#: ../C/gdm.xml:1908(synopsis) -#, no-wrap -msgid "Chooser=<bin>/gdmchooser" -msgstr "Chooser=<bin>/gdmchooser" - -#: ../C/gdm.xml:1909(para) -msgid "Full path and name of the chooser executable followed by optional arguments." -msgstr "" - -#: ../C/gdm.xml:1917(term) -msgid "Configurator" -msgstr "Configurator" - -#: ../C/gdm.xml:1919(synopsis) -#, no-wrap -msgid "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" -msgstr "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" - -#: ../C/gdm.xml:1920(para) -msgid "The pathname to the configurator binary. If the greeter <filename>ConfigAvailable</filename> 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:1932(term) -msgid "ConsoleCannotHandle" -msgstr "ConsoleCannotHandle" - -#: ../C/gdm.xml:1934(synopsis) -#, no-wrap -msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" -msgstr "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" - -#: ../C/gdm.xml:1935(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:1945(term) -msgid "ConsoleNotify" -msgstr "ConsoleNotify" - -#: ../C/gdm.xml:1947(synopsis) -#, no-wrap -msgid "ConsoleNotify=true" -msgstr "ConsoleNotify=true" - -#: ../C/gdm.xml:1948(para) -msgid "If false, gdm will not display a message dialog on the console when an error happens." -msgstr "" - -#: ../C/gdm.xml:1956(term) -msgid "DefaultPath" -msgstr "DefaultPath" - -#: ../C/gdm.xml:1958(synopsis) -#, no-wrap -msgid "DefaultPath=defaultpath (value set by configure)" -msgstr "" - -#: ../C/gdm.xml:1959(para) -msgid "Specifies the path which will be set in the user's session. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains \"ROOT=<pathname>\". If the <filename>/etc/default/login</filename> file exists, but contains no value for ROOT, the value as defined in the GDM configuration will be be used." -msgstr "" - -#: ../C/gdm.xml:1972(term) -msgid "DefaultSession" -msgstr "DefaultSession" - -#: ../C/gdm.xml:1974(synopsis) -#, no-wrap -msgid "DefaultSession=gnome.desktop" -msgstr "DefaultSession=gnome.desktop" - -#: ../C/gdm.xml:1975(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 <filename>ShowLastSession</filename> key." -msgstr "" - -#: ../C/gdm.xml:1986(term) -msgid "DisplayInitDir" -msgstr "DisplayInitDir" - -#: ../C/gdm.xml:1988(synopsis) -#, no-wrap, fuzzy -msgid "DisplayInitDir=<etc>/gdm/Init" -msgstr "DisplayInitDir=<etc>/gdm/Init" - -#: ../C/gdm.xml:1989(para) -msgid "Directory containing the display init scripts. See the ``The Script Directories'' section for more info." -msgstr "" - -#: ../C/gdm.xml:1997(term) -msgid "DisplayLastLogin" -msgstr "DisplayLastLogin" - -#: ../C/gdm.xml:1999(synopsis) -#, no-wrap -msgid "DisplayLastLogin=true" -msgstr "DisplayLastLogin=true" - -#: ../C/gdm.xml:2000(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:2009(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 <filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> for more info." -msgstr "" - -#: ../C/gdm.xml:2021(term) -msgid "DoubleLoginWarning" -msgstr "DoubleLoginWarning" - -#: ../C/gdm.xml:2023(synopsis) -#, no-wrap -msgid "DoubleLoginWarning=true" -msgstr "DoubleLoginWarning=true" - -#: ../C/gdm.xml:2024(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:2034(term) -msgid "DynamicXServers" -msgstr "DynamicXServers" - -#: ../C/gdm.xml:2036(synopsis) -#, no-wrap -msgid "DynamicXServers=false" -msgstr "DynamicXServers=false" - -#: ../C/gdm.xml:2037(para) -msgid "If true, the GDM daemon will honor requests to manage displays via the <filename>/tmp/.gdm_socket</filename> socket connection. Displays can be created, started, and deleted with the appropriate commands. The <filename>gdmdynamic</filename> command is a convenient method to send these messages." -msgstr "" - -#: ../C/gdm.xml:2049(term) -msgid "FailsafeXServer" -msgstr "FailsafeXServer" - -#: ../C/gdm.xml:2051(synopsis) -#, no-wrap -msgid "FailsafeXServer=" -msgstr "FailsafeXServer=" - -#: ../C/gdm.xml:2052(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 <filename>XKeepsCrashing</filename> script is run." -msgstr "" - -#: ../C/gdm.xml:2063(term) -msgid "FirstVT" -msgstr "FirstVT" - -#: ../C/gdm.xml:2065(synopsis) -#, no-wrap -msgid "FirstVT=7" -msgstr "FirstVT=7" - -#: ../C/gdm.xml:2066(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 <filename>VTAllocation</filename>." -msgstr "" - -#: ../C/gdm.xml:2076(term) -msgid "FlexibleXServers" -msgstr "FlexibleXServers" - -#: ../C/gdm.xml:2078(synopsis) -#, no-wrap -msgid "FlexibleXServers=5" -msgstr "FlexibleXServers=5" - -#: ../C/gdm.xml:2079(para) -msgid "The maximum number of allowed flexible displays. These are displays that can be run using the <filename>/tmp/.gdm_socket</filename> socket connection. This is used for both full flexible displays and for nested displays (refer to the <filename>Xnest</filename> configuration option)." -msgstr "" - -#: ../C/gdm.xml:2091(term) -msgid "FlexiReapDelayMinutes" -msgstr "FlexiReapDelayMinutes" - -#: ../C/gdm.xml:2093(synopsis) -#, no-wrap -msgid "FlexiReapDelayMinutes=5" -msgstr "FlexiReapDelayMinutes=5" - -#: ../C/gdm.xml:2094(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 <filename>Xnest</filename> 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:2106(term) -msgid "Greeter" -msgstr "Greeter" - -#: ../C/gdm.xml:2108(synopsis) -#, no-wrap -msgid "Greeter=<bin>/gdmlogin" -msgstr "Greeter=<bin>/gdmlogin" - -#: ../C/gdm.xml:2109(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 <filename>RemoteGreeter</filename>" -msgstr "" - -#: ../C/gdm.xml:2119(term) -msgid "Group" -msgstr "Group" - -#: ../C/gdm.xml:2121(synopsis) -#, no-wrap -msgid "Group=gdm" -msgstr "Group=gdm" - -#: ../C/gdm.xml:2122(para) -msgid "The group name under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogs are run. Also see <filename>User</filename>. 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 <filename>ServAuthDir</filename> is owned by this group. The ownership and permissions of <filename>ServAuthDir</filename> should be <filename>root.gdm</filename> and 1770." -msgstr "" - -#: ../C/gdm.xml:2139(term) -msgid "GtkModulesList" -msgstr "GtkModulesList" - -#: ../C/gdm.xml:2141(synopsis) -#, no-wrap -msgid "GtkModulesList=module-1:module-2:..." -msgstr "GtkModulesList=module-1:module-2:..." - -#: ../C/gdm.xml:2142(para) -msgid "A colon separated list of Gtk+ modules that <command>gdmgreeter</command> or <command>gdmlogin</command> will be invoked with if <filename>AddGtkModules</filename> is true. The format is the same as the standard Gtk+ module interface." -msgstr "" - -#: ../C/gdm.xml:2153(term) -msgid "HaltCommand" -msgstr "HaltCommand" - -#: ../C/gdm.xml:2155(synopsis) -#, no-wrap -msgid "HaltCommand=<sbin>/shutdown -h now" -msgstr "HaltCommand=<sbin>/shutdown -h now" - -#: ../C/gdm.xml:2156(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:2169(term) -msgid "KillInitClients" -msgstr "KillInitClients" - -#: ../C/gdm.xml:2171(synopsis) -#, no-wrap -msgid "KillInitClients=true" -msgstr "KillInitClients=true" - -#: ../C/gdm.xml:2172(para) -msgid "Determines whether GDM should kill X clients started by the init scripts when the user logs in." -msgstr "" - -#: ../C/gdm.xml:2180(term) -msgid "LogDir" -msgstr "LogDir" - -#: ../C/gdm.xml:2182(synopsis) -#, no-wrap -msgid "LogDir=<var>/log/gdm" -msgstr "LogDir=<var>/log/gdm" - -#: ../C/gdm.xml:2183(para) -msgid "Directory containing the log files for the individual displays. By default this is the same as the ServAuthDir." -msgstr "" - -#: ../C/gdm.xml:2191(term) -msgid "PreFetchProgram" -msgstr "PreFetchProgram" - -#: ../C/gdm.xml:2193(synopsis) -#, no-wrap -msgid "PreFetchProgram=command" -msgstr "PreFetchProgram=command" - -#: ../C/gdm.xml:2194(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:2210(term) -msgid "PostLoginScriptDir" -msgstr "PostLoginScriptDir" - -#: ../C/gdm.xml:2212(synopsis) -#, no-wrap -msgid "PostLoginScriptDir=<etc>/gdm/PostLogin" -msgstr "PostLoginScriptDir=<etc>/gdm/PostLogin" - -#: ../C/gdm.xml:2213(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:2222(term) -msgid "PostSessionScriptDir" -msgstr "PostSessionScriptDir" - -#: ../C/gdm.xml:2224(synopsis) -#, no-wrap -msgid "PostSessionScriptDir=<etc>/gdm/PostSession" -msgstr "PostSessionScriptDir=<etc>/gdm/PostSession" - -#: ../C/gdm.xml:2225(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:2233(term) -msgid "PreSessionScriptDir" -msgstr "PreSessionScriptDir" - -#: ../C/gdm.xml:2235(synopsis) -#, no-wrap -msgid "PreSessionScriptDir=<etc>/gdm/PreSession" -msgstr "PreSessionScriptDir=<etc>/gdm/PreSession" - -#: ../C/gdm.xml:2236(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:2244(term) -msgid "RebootCommand" -msgstr "RebootCommand" - -#: ../C/gdm.xml:2246(synopsis) -#, no-wrap -msgid "RebootCommand=<sbin>/shutdown -r now" -msgstr "RebootCommand=<sbin>/shutdown -r now" - -#: ../C/gdm.xml:2247(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:2259(term) -msgid "RemoteGreeter" -msgstr "RemoteGreeter" - -#: ../C/gdm.xml:2261(synopsis) -#, no-wrap -msgid "RemoteGreeter=<bin>/gdmlogin" -msgstr "RemoteGreeter=<bin>/gdmlogin" - -#: ../C/gdm.xml:2262(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 <filename>Greeter</filename> key." -msgstr "" - -#: ../C/gdm.xml:2273(term) -msgid "RootPath" -msgstr "RootPath" - -#: ../C/gdm.xml:2275(synopsis) -#, no-wrap, fuzzy -msgid "RootPath=defaultpath (value set by configure)" -msgstr "RootPath=defaultpath (value set by configure)" - -#: ../C/gdm.xml:2276(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 <filename>/etc/default/login</filename> if it contains \"SUROOT=<pathname>\". If the <filename>/etc/default/login</filename> file exists, but contains no value for SUROOT, the value as defined in the GDM configuration will be used." -msgstr "" - -#: ../C/gdm.xml:2290(term) -msgid "ServAuthDir" -msgstr "ServAuthDir" - -#: ../C/gdm.xml:2292(synopsis) -#, no-wrap -msgid "ServAuthDir=<var>/gdm" -msgstr "ServAuthDir=<var>/gdm" - -#: ../C/gdm.xml:2293(para) -msgid "Directory containing the X authentication files for the individual displays. Should be owned by <filename>root.gdm</filename> with permissions 1770, where <filename>gdm</filename> is the GDM group as defined by the <filename>Group</filename> option. That is should be owned by root, with <filename>gdm</filename> 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:2315(term) -msgid "SessionDesktopDir" -msgstr "SessionDesktopDir" - -#: ../C/gdm.xml:2317(synopsis) -#, no-wrap -msgid "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" -msgstr "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" - -#: ../C/gdm.xml:2318(para) -msgid "Directory containing the <filename>.desktop</filename> 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:2328(term) -msgid "SoundProgram" -msgstr "SoundProgram" - -#: ../C/gdm.xml:2330(filename) -msgid "<bin>/play" -msgstr "<bin>/play" - -#: ../C/gdm.xml:2330(filename) -msgid "<bin>/audioplay" -msgstr "<bin>/audioplay" - -#: ../C/gdm.xml:2330(synopsis) -#, no-wrap -msgid "SoundProgram=<placeholder-1/> (or <placeholder-2/> on Solaris)" -msgstr "SoundProgram=<placeholder-1/> (솔라리스의 경우 <placeholder-2/>)" - -#: ../C/gdm.xml:2331(para) -msgid "Application to use when playing a sound. Currently used for playing the login sound, see the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0." -msgstr "" - -#: ../C/gdm.xml:2341(term) -msgid "StandardXServer" -msgstr "StandardXServer" - -#: ../C/gdm.xml:2343(synopsis) -#, no-wrap -msgid "StandardXServer=/dir/to/X (value assigned by configuration file)" -msgstr "StandardXServer=/dir/to/X (value assigned by configuration file)" - -#: ../C/gdm.xml:2344(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:2355(term) -msgid "SuspendCommand" -msgstr "SuspendCommand" - -#: ../C/gdm.xml:2357(synopsis) -#, no-wrap -msgid "SuspendCommand=" -msgstr "SuspendCommand=" - -#: ../C/gdm.xml:2358(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:2369(term) -msgid "TimedLoginEnable" -msgstr "TimedLoginEnable" - -#: ../C/gdm.xml:2371(synopsis) -#, no-wrap -msgid "TimedLoginEnable=false" -msgstr "TimedLoginEnable=false" - -#: ../C/gdm.xml:2372(para) -msgid "If the user given in <filename>TimedLogin</filename> should be logged in after a number of seconds (set with <filename>TimedLoginDelay</filename>) of inactivity on the login screen. This is useful for public access terminals or perhaps even home use. If the user uses the keyboard or browses the menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or 30 seconds, whichever is higher. If the user does not enter a username but just hits the ENTER key while the login program is requesting the username, then GDM will assume the user wants to login immediately as the timed user. Note that no password will be asked for this user so you should be careful, although if using PAM it can be configured to require password entry before allowing login." -msgstr "" - -#: ../C/gdm.xml:2392(term) -msgid "TimedLogin" -msgstr "TimedLogin" - -#: ../C/gdm.xml:2394(synopsis) -#, no-wrap -msgid "TimedLogin=" -msgstr "TimedLogin=" - -#: ../C/gdm.xml:2395(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 <filename>AutomaticLogin</filename> are supported. The same control chars and piping to a application are supported." -msgstr "" - -#: ../C/gdm.xml:2407(term) -msgid "TimedLoginDelay" -msgstr "TimedLoginDelay" - -#: ../C/gdm.xml:2409(synopsis) -#, no-wrap -msgid "TimedLoginDelay=30" -msgstr "TimedLoginDelay=30" - -#: ../C/gdm.xml:2410(para) -msgid "Delay in seconds before the <filename>TimedLogin</filename> user will be logged in. It must be greater then or equal to 10." -msgstr "" - -#: ../C/gdm.xml:2418(term) -msgid "User" -msgstr "User" - -#: ../C/gdm.xml:2420(synopsis) -#, no-wrap -msgid "User=gdm" -msgstr "User=gdm" - -#: ../C/gdm.xml:2421(para) -msgid "The username under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogs are run. Also see <filename>Group</filename>. 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:2435(term) -msgid "UserAuthDir" -msgstr "UserAuthDir" - -#: ../C/gdm.xml:2437(synopsis) -#, no-wrap -msgid "UserAuthDir=" -msgstr "UserAuthDir=" - -#: ../C/gdm.xml:2438(para) -msgid "The directory where user's <filename>.Xauthority</filename> 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: <filename>~/authdir/</filename>." -msgstr "" - -#: ../C/gdm.xml:2445(para) -msgid "If you do not use the tilde expansion, then the filename created will be random, like in <filename>UserAuthFBDir</filename>. This way many users can have the same authentication directory. For example you might want to set this to <filename>/tmp</filename> 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 <filename>/tmp</filename> directory." -msgstr "" - -#: ../C/gdm.xml:2458(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 <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false." -msgstr "" - -#: ../C/gdm.xml:2469(term) -msgid "UserAuthFBDir" -msgstr "UserAuthFBDir" - -#: ../C/gdm.xml:2471(synopsis) -#, no-wrap -msgid "UserAuthFBDir=/tmp" -msgstr "UserAuthFBDir=/tmp" - -#: ../C/gdm.xml:2472(para) -msgid "If GDM fails to update the user's <filename>.Xauthority</filename> file a fallback cookie is created in this directory." -msgstr "" - -#: ../C/gdm.xml:2481(term) -msgid "UserAuthFile" -msgstr "UserAuthFile" - -#: ../C/gdm.xml:2483(synopsis) -#, no-wrap -msgid "UserAuthFile=.Xauthority" -msgstr "UserAuthFile=.Xauthority" - -#: ../C/gdm.xml:2484(para) -msgid "Name of the file used for storing user cookies." -msgstr "" - -#: ../C/gdm.xml:2491(term) -msgid "VTAllocation" -msgstr "VTAllocation" - -#: ../C/gdm.xml:2493(synopsis) -#, no-wrap -msgid "VTAllocation=true" -msgstr "VTAllocation=true" - -#: ../C/gdm.xml:2494(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 <filename>FirstVT</filename>." -msgstr "" - -#: ../C/gdm.xml:2506(term) -msgid "XKeepsCrashing" -msgstr "XKeepsCrashing" - -#: ../C/gdm.xml:2508(synopsis) -#, no-wrap -msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" -msgstr "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" - -#: ../C/gdm.xml:2509(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 <filename>XKeepsCrashing</filename> 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:2518(para) -msgid "In case <filename>FailsafeXServer</filename> 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:2527(term) -msgid "Xnest" -msgstr "" - -#: ../C/gdm.xml:2529(synopsis) -#, no-wrap -msgid "Xnest=<bin>/X11/Xephyr -audit 0" -msgstr "Xnest=<bin>/X11/Xephyr -audit 0" - -#: ../C/gdm.xml:2530(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:2544(term) -msgid "XnestUnscaledFontPath" -msgstr "XnestUnscaledFontPath" - -#: ../C/gdm.xml:2546(synopsis) -#, no-wrap -msgid "XnestUnscaledFontPath=true" -msgstr "XnestUnscaledFontPath=true" - -#: ../C/gdm.xml:2547(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 <filename>Xnest</filename> configuration option." -msgstr "" - -#: ../C/gdm.xml:2561(title) -msgid "Security Options" -msgstr "보안 옵션" - -#: ../C/gdm.xml:2564(title) -msgid "[security]" -msgstr "[security]" - -#: ../C/gdm.xml:2567(term) -msgid "AllowRoot" -msgstr "AllowRoot" - -#: ../C/gdm.xml:2569(synopsis) -#, no-wrap -msgid "AllowRoot=true" -msgstr "AllowRoot=true" - -#: ../C/gdm.xml:2570(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:2574(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:2584(term) -msgid "AllowRemoteRoot" -msgstr "AllowRemoteRoot" - -#: ../C/gdm.xml:2586(synopsis) -#, no-wrap -msgid "AllowRemoteRoot=false" -msgstr "AllowRemoteRoot=false" - -#: ../C/gdm.xml:2587(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:2592(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:2597(para) -msgid "This value will be overridden and set to false if the <filename>/etc/default/login</filename> file exists and contains \"CONSOLE=/dev/login\", and set to true if the <filename>/etc/default/login</filename> file exists and contains any other value or no value for CONSOLE." -msgstr "" - -#: ../C/gdm.xml:2608(term) -msgid "AllowRemoteAutoLogin" -msgstr "AllowRemoteAutoLogin" - -#: ../C/gdm.xml:2610(synopsis) -#, no-wrap -msgid "AllowRemoteAutoLogin=false" -msgstr "AllowRemoteAutoLogin=false" - -#: ../C/gdm.xml:2611(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:2617(para) -msgid "Note that this can make a system quite insecure, and thus is off by default." -msgstr "" - -#: ../C/gdm.xml:2625(term) -msgid "CheckDirOwner" -msgstr "CheckDirOwner" - -#: ../C/gdm.xml:2627(synopsis) -#, no-wrap -msgid "CheckDirOwner=true" -msgstr "CheckDirOwner=true" - -#: ../C/gdm.xml:2628(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 <filename>RelaxPermissions</filename> 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:2642(term) -msgid "SupportAutomount" -msgstr "SupportAutomount" - -#: ../C/gdm.xml:2644(synopsis) -#, no-wrap -msgid "SupportAutomount=false" -msgstr "SupportAutomount=false" - -#: ../C/gdm.xml:2645(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:2657(term) -msgid "DisallowTCP" -msgstr "DisallowTCP" - -#: ../C/gdm.xml:2659(synopsis) -#, no-wrap -msgid "DisallowTCP=true" -msgstr "DisallowTCP=true" - -#: ../C/gdm.xml:2660(para) -msgid "If true, then always append <filename>-nolisten tcp</filename> 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:2673(term) -msgid "NeverPlaceCookiesOnNFS" -msgstr "NeverPlaceCookiesOnNFS" - -#: ../C/gdm.xml:2675(synopsis) -#, no-wrap -msgid "NeverPlaceCookiesOnNFS=true" -msgstr "NeverPlaceCookiesOnNFS=true" - -#: ../C/gdm.xml:2676(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:2690(term) -msgid "PasswordRequired" -msgstr "" - -#: ../C/gdm.xml:2692(synopsis) -#, no-wrap -msgid "PasswordRequired=false" -msgstr "" - -#: ../C/gdm.xml:2693(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 <filename>/etc/default/login</filename> if it contains \"PASSREQ=[YES|NO]\". If the <filename>/etc/default/login</filename> file exists, but contains no value for PASSREQ, the value as defined in the GDM configuration will be used." -msgstr "" - -#: ../C/gdm.xml:2709(term) -msgid "RelaxPermissions" -msgstr "RelaxPermissions" - -#: ../C/gdm.xml:2711(synopsis) -#, no-wrap -msgid "RelaxPermissions=0" -msgstr "RelaxPermissions=0" - -#: ../C/gdm.xml:2712(para) -msgid "By default GDM ignores files and directories writable to other users than the owner." -msgstr "" - -#: ../C/gdm.xml:2717(para) -msgid "Changing the value of RelaxPermissions makes it possible to alter this behavior:" -msgstr "" - -#: ../C/gdm.xml:2722(para) -msgid "0 - Paranoia option. Only accepts user owned files and directories." -msgstr "" - -#: ../C/gdm.xml:2726(para) -msgid "1 - Allow group writable files and directories." -msgstr "" - -#: ../C/gdm.xml:2729(para) -msgid "2 - Allow world writable files and directories." -msgstr "" - -#: ../C/gdm.xml:2736(term) -msgid "RetryDelay" -msgstr "RetryDelay" - -#: ../C/gdm.xml:2738(synopsis) -#, no-wrap -msgid "RetryDelay=1" -msgstr "RetryDelay=1" - -#: ../C/gdm.xml:2739(para) -msgid "The number of seconds GDM should wait before reactivating the entry field after a failed login." -msgstr "" - -#: ../C/gdm.xml:2747(term) -msgid "UserMaxFile" -msgstr "UserMaxFile" - -#: ../C/gdm.xml:2749(synopsis) -#, no-wrap -msgid "UserMaxFile=65536" -msgstr "UserMaxFile=65536" - -#: ../C/gdm.xml:2750(para) -msgid "GDM will refuse to read/write files bigger than this number (specified in bytes)." -msgstr "" - -#: ../C/gdm.xml:2755(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 <filename>RelaxPermissions</filename> option for more info." -msgstr "" - -#: ../C/gdm.xml:2768(title) -msgid "XDCMP Support" -msgstr "" - -#: ../C/gdm.xml:2771(title) -msgid "[xdmcp]" -msgstr "[xdmcp]" - -#: ../C/gdm.xml:2774(term) -msgid "DisplaysPerHost" -msgstr "DisplaysPerHost" - -#: ../C/gdm.xml:2776(synopsis) -#, no-wrap -msgid "DisplaysPerHost=1" -msgstr "DisplaysPerHost=1" - -#: ../C/gdm.xml:2777(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 <filename>DisplaysPerHost</filename> value accordingly." -msgstr "" - -#: ../C/gdm.xml:2785(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:2793(term) ../C/gdm.xml:4040(term) -msgid "Enable" -msgstr "Enable" - -#: ../C/gdm.xml:2795(synopsis) ../C/gdm.xml:4042(synopsis) -#, no-wrap -msgid "Enable=false" -msgstr "Enable=false" - -#: ../C/gdm.xml:2796(para) -msgid "Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM." -msgstr "" - -#: ../C/gdm.xml:2801(para) -msgid "<filename>gdm</filename> listens for requests on UDP port 177. See the Port option for more information." -msgstr "" - -#: ../C/gdm.xml:2806(para) -msgid "If GDM is compiled to support it, access from remote displays can be controlled using the TCP Wrappers library. The service name is <filename>gdm</filename>" -msgstr "" - -#: ../C/gdm.xml:2812(para) -msgid "You should add <screen>\ngdm:.my.domain\n</screen> to your <filename><etc>/hosts.allow</filename>, depending on your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" - -#: ../C/gdm.xml:2823(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:2832(term) -msgid "EnableProxy" -msgstr "EnableProxy" - -#: ../C/gdm.xml:2834(synopsis) -#, no-wrap -msgid "EnableProxy=false" -msgstr "EnableProxy=false" - -#: ../C/gdm.xml:2835(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:2842(para) -msgid "Note, however, that this mode will significantly increase the burden on the machine hosting the XDMCP sessions" -msgstr "" - -#: ../C/gdm.xml:2846(para) -msgid "See the <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</filename> options for further details on how to configure support for this feature." -msgstr "" - -#: ../C/gdm.xml:2855(term) -msgid "HonorIndirect" -msgstr "HonorIndirect" - -#: ../C/gdm.xml:2857(synopsis) -#, no-wrap -msgid "HonorIndirect=true" -msgstr "HonorIndirect=true" - -#: ../C/gdm.xml:2858(para) -msgid "Enables XDMCP INDIRECT choosing (i.e. remote execution of <filename>gdmchooser</filename>) for X-terminals which don't supply their own display browser." -msgstr "" - -#: ../C/gdm.xml:2867(term) -msgid "MaxPending" -msgstr "MaxPending" - -#: ../C/gdm.xml:2869(synopsis) -#, no-wrap -msgid "MaxPending=4" -msgstr "MaxPending=4" - -#: ../C/gdm.xml:2870(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:2876(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:2885(term) -msgid "MaxPendingIndirect" -msgstr "MaxPendingIndirect" - -#: ../C/gdm.xml:2887(synopsis) -#, no-wrap -msgid "MaxPendingIndirect=4" -msgstr "MaxPendingIndirect=4" - -#: ../C/gdm.xml:2888(para) -msgid "GDM will only provide <filename>MaxPendingIndirect</filename> displays with host choosers simultaneously. If more queries from different hosts come in, the oldest ones will be forgotten." -msgstr "" - -#: ../C/gdm.xml:2898(term) -msgid "MaxSessions" -msgstr "MaxSessions" - -#: ../C/gdm.xml:2900(synopsis) -#, no-wrap -msgid "MaxSessions=16" -msgstr "MaxSessions=16" - -#: ../C/gdm.xml:2901(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:2910(term) -msgid "MaxWait" -msgstr "MaxWait" - -#: ../C/gdm.xml:2912(synopsis) -#, no-wrap -msgid "MaxWait=30" -msgstr "MaxWait=30" - -#: ../C/gdm.xml:2913(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:2919(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:2924(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:2933(term) -msgid "MaxWaitIndirect" -msgstr "MaxWaitIndirect" - -#: ../C/gdm.xml:2935(synopsis) -#, no-wrap -msgid "MaxWaitIndirect=30" -msgstr "MaxWaitIndirect=30" - -#: ../C/gdm.xml:2936(para) -msgid "The MaxWaitIndirect parameter determines the maximum number of seconds between the time where a user chooses a host and the subsequent indirect query where the user is connected to the host. When the timeout is exceeded, the information about the chosen host is forgotten and the indirect slot freed up for other displays. The information may be forgotten earlier if there are more hosts trying to send indirect queries then <filename>MaxPendingIndirect</filename>." -msgstr "" - -#: ../C/gdm.xml:2950(term) -msgid "Port" -msgstr "Port" - -#: ../C/gdm.xml:2952(synopsis) -#, no-wrap -msgid "Port=177" -msgstr "Port=177" - -#: ../C/gdm.xml:2953(para) -msgid "The UDP port number <filename>gdm</filename> should listen to for XDMCP requests. Don't change this unless you know what you are doing." -msgstr "" - -#: ../C/gdm.xml:2962(term) -msgid "PingIntervalSeconds" -msgstr "PingIntervalSeconds" - -#: ../C/gdm.xml:2964(synopsis) -#, no-wrap -msgid "PingIntervalSeconds=15" -msgstr "PingIntervalSeconds=15" - -#: ../C/gdm.xml:2965(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:2973(para) -msgid "Note that GDM in the past used to have a <filename>PingInterval</filename> configuration key which was also in minutes. For most purposes you'd want this setting to be lower 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:2986(term) -msgid "ProxyReconnect" -msgstr "ProxyReconnect" - -#: ../C/gdm.xml:2988(synopsis) -#, no-wrap -msgid "FlexiProxyReconnect=" -msgstr "FlexiProxyReconnect=" - -#: ../C/gdm.xml:2989(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:2995(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:3002(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:3011(term) -msgid "ProxyXServer" -msgstr "ProxyXServer" - -#: ../C/gdm.xml:3013(synopsis) -#, no-wrap -msgid "ProxyXServer=" -msgstr "ProxyXServer=" - -#: ../C/gdm.xml:3014(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:3022(term) -msgid "Willing" -msgstr "Willing" - -#: ../C/gdm.xml:3024(synopsis) -#, no-wrap -msgid "Willing=<etc>/gdm/Xwilling" -msgstr "Willing=<etc>/gdm/Xwilling" - -#: ../C/gdm.xml:3025(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:3043(title) -msgid "Common GUI Configuration Options" -msgstr "" - -#: ../C/gdm.xml:3046(title) -msgid "[gui]" -msgstr "[gui]" - -#: ../C/gdm.xml:3049(term) -msgid "AllowGtkThemeChange" -msgstr "AllowGtkThemeChange" - -#: ../C/gdm.xml:3051(synopsis) -#, no-wrap -msgid "AllowGtkThemeChange=true" -msgstr "AllowGtkThemeChange=true" - -#: ../C/gdm.xml:3052(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:3064(term) -msgid "GtkRC" -msgstr "GtkRC" - -#: ../C/gdm.xml:3066(synopsis) -#, no-wrap -msgid "GtkRC=" -msgstr "GtkRC=" - -#: ../C/gdm.xml:3067(para) -msgid "Path to a <filename>gtkrc</filename> to read when GDM puts up a window. You should really now use the <filename>GtkTheme</filename> key for just setting a theme." -msgstr "" - -#: ../C/gdm.xml:3076(term) -msgid "GtkTheme" -msgstr "GtkTheme" - -#: ../C/gdm.xml:3078(synopsis) -#, no-wrap -msgid "GtkTheme=Default" -msgstr "GtkTheme=Default" - -#: ../C/gdm.xml:3079(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:3088(term) -msgid "GtkThemesToAllow" -msgstr "GtkThemesToAllow" - -#: ../C/gdm.xml:3090(synopsis) -#, no-wrap -msgid "GtkThemesToAllow=all" -msgstr "GtkThemesToAllow=all" - -#: ../C/gdm.xml:3091(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 <filename>AllowGtkThemeChange</filename> key. Supported since 2.5.90.2." -msgstr "" - -#: ../C/gdm.xml:3103(term) -msgid "MaxIconWidth" -msgstr "MaxIconWidth" - -#: ../C/gdm.xml:3105(synopsis) -#, no-wrap -msgid "MaxIconWidth=128" -msgstr "MaxIconWidth=128" - -#: ../C/gdm.xml:3106(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:3115(term) -msgid "MaxIconHeight" -msgstr "MaxIconHeight" - -#: ../C/gdm.xml:3117(synopsis) -#, no-wrap -msgid "MaxIconHeight=128" -msgstr "MaxIconHeight=128" - -#: ../C/gdm.xml:3118(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:3129(title) -msgid "Greeter Configuration" -msgstr "" - -#: ../C/gdm.xml:3132(title) -msgid "[greeter]" -msgstr "[greeter]" - -#: ../C/gdm.xml:3135(term) -msgid "BackgroundColor" -msgstr "BackgroundColor" - -#: ../C/gdm.xml:3137(synopsis) -#, no-wrap -msgid "BackgroundColor=#76848F" -msgstr "BackgroundColor=#76848F" - -#: ../C/gdm.xml:3138(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:3149(term) -msgid "BackgroundProgramInitialDelay" -msgstr "BackgroundProgramInitialDelay" - -#: ../C/gdm.xml:3151(synopsis) -#, no-wrap -msgid "BackgroundProgramInitialDelay=30" -msgstr "BackgroundProgramInitialDelay=30" - -#: ../C/gdm.xml:3152(para) -msgid "The background application will be started after at least that many seconds of inactivity." -msgstr "" - -#: ../C/gdm.xml:3160(term) -msgid "RestartBackgroundProgram" -msgstr "RestartBackgroundProgram" - -#: ../C/gdm.xml:3162(synopsis) -#, no-wrap -msgid "RestartBackgroundProgram=true" -msgstr "RestartBackgroundProgram=true" - -#: ../C/gdm.xml:3163(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:3173(term) -msgid "BackgroundProgramRestartDelay" -msgstr "BackgroundProgramRestartDelay" - -#: ../C/gdm.xml:3175(synopsis) -#, no-wrap -msgid "BackgroundProgramRestartDelay=30" -msgstr "BackgroundProgramRestartDelay=30" - -#: ../C/gdm.xml:3176(para) -msgid "The background application will be restarted after at least that many seconds of inactivity." -msgstr "" - -#: ../C/gdm.xml:3184(term) -msgid "BackgroundImage" -msgstr "BackgroundImage" - -#: ../C/gdm.xml:3186(synopsis) -#, no-wrap, fuzzy -msgid "BackgroundImage=somefile.png" -msgstr "BackgroundImage=somefile.png" - -#: ../C/gdm.xml:3187(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:3196(term) -msgid "BackgroundProgram" -msgstr "BackgroundProgram" - -#: ../C/gdm.xml:3198(synopsis) -#, no-wrap -msgid "BackgroundProgram=<bin>/xeyes" -msgstr "BackgroundProgram=<bin>/xeyes" - -#: ../C/gdm.xml:3199(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:3211(term) -msgid "BackgroundRemoteOnlyColor" -msgstr "BackgroundRemoteOnlyColor" - -#: ../C/gdm.xml:3213(synopsis) -#, no-wrap -msgid "BackgroundRemoteOnlyColor=true" -msgstr "BackgroundRemoteOnlyColor=true" - -#: ../C/gdm.xml:3214(para) -msgid "On remote displays only set the color background. This is to make network load lighter. The <filename>BackgroundProgram</filename> is also not run. This only affects the GTK+ Greeter." -msgstr "" - -#: ../C/gdm.xml:3224(term) -msgid "BackgroundScaleToFit" -msgstr "BackgroundScaleToFit" - -#: ../C/gdm.xml:3226(synopsis) -#, no-wrap -msgid "BackgroundScaleToFit=true" -msgstr "BackgroundScaleToFit=true" - -#: ../C/gdm.xml:3227(para) -msgid "Scale background image to fit the screen. This only affects the GTK+ Greeter." -msgstr "" - -#: ../C/gdm.xml:3235(term) -msgid "BackgroundType" -msgstr "BackgroundType" - -#: ../C/gdm.xml:3237(synopsis) -#, no-wrap -msgid "BackgroundType=2" -msgstr "BackgroundType=2" - -#: ../C/gdm.xml:3238(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:3246(term) -msgid "Browser" -msgstr "Browser" - -#: ../C/gdm.xml:3248(synopsis) -#, no-wrap -msgid "Browser=true" -msgstr "Browser=true" - -#: ../C/gdm.xml:3249(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:3260(term) -msgid "ChooserButton" -msgstr "ChooserButton" - -#: ../C/gdm.xml:3262(synopsis) -#, no-wrap -msgid "ChooserButton=true" -msgstr "ChooserButton=true" - -#: ../C/gdm.xml:3263(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:3272(term) -msgid "ConfigAvailable" -msgstr "ConfigAvailable" - -#: ../C/gdm.xml:3274(synopsis) -#, no-wrap -msgid "ConfigAvailable=false" -msgstr "ConfigAvailable=false" - -#: ../C/gdm.xml:3275(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 <filename>Configurator</filename> option in the daemon section." -msgstr "" - -#: ../C/gdm.xml:3287(term) -msgid "DefaultFace" -msgstr "DefaultFace" - -#: ../C/gdm.xml:3289(synopsis) -#, no-wrap -msgid "DefaultFace=<share>/pixmaps/nophoto.png" -msgstr "DefaultFace=<share>/pixmaps/nophoto.png" - -#: ../C/gdm.xml:3290(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 <filename>DefaultFace</filename> 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:3302(term) -msgid "Include" -msgstr "Include" - -#: ../C/gdm.xml:3304(synopsis) -#, no-wrap -msgid "Include=" -msgstr "Include=" - -#: ../C/gdm.xml:3305(para) -msgid "Comma separated list of users to be included in the face browser and in the <command>gdmsetup</command> selection list for Automatic/Timed login. See also <filename>Exclude</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." -msgstr "" - -#: ../C/gdm.xml:3317(term) -msgid "Exclude" -msgstr "Exclude" - -#: ../C/gdm.xml:3319(synopsis) -#, no-wrap -msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." -msgstr "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." - -#: ../C/gdm.xml:3320(para) -msgid "Comma separated list of users to be excluded from the face browser and from the <command>gdmsetup</command> selection list for Automatic/Timed login. Excluded users will still be able to log in, but will have to type their username. See also <filename>Include</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." -msgstr "" - -#: ../C/gdm.xml:3333(term) -msgid "IncludeAll" -msgstr "IncludeAll" - -#: ../C/gdm.xml:3335(synopsis) -#, no-wrap -msgid "IncludeAll=false" -msgstr "IncludeAll=false" - -#: ../C/gdm.xml:3336(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 <filename>Include</filename>, <filename>Exclude</filename>, and <filename>MinimalUID</filename>." -msgstr "" - -#: ../C/gdm.xml:3352(term) -msgid "GlobalFaceDir" -msgstr "GlobalFaceDir" - -#: ../C/gdm.xml:3354(synopsis) -#, no-wrap -msgid "GlobalFaceDir=<share>/pixmaps/faces/" -msgstr "GlobalFaceDir=<share>/pixmaps/faces/" - -#: ../C/gdm.xml:3355(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:3361(para) -msgid "I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the face icon for the user ``johndoe''. No image format extension should be specified." -msgstr "" - -#: ../C/gdm.xml:3367(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:3372(para) -msgid "A user's own icon file will always take precedence over the sysadmin provided one." -msgstr "" - -#: ../C/gdm.xml:3380(term) -msgid "GraphicalTheme" -msgstr "GraphicalTheme" - -#: ../C/gdm.xml:3382(synopsis) -#, no-wrap -msgid "GraphicalTheme=circles" -msgstr "GraphicalTheme=circles" - -#: ../C/gdm.xml:3383(para) -msgid "The graphical theme that the Themed Greeter should use. it should refer to a directory in the theme directory set by <filename>GraphicalThemeDir</filename>." -msgstr "" - -#: ../C/gdm.xml:3392(term) -msgid "GraphicalThemes" -msgstr "GraphicalThemes" - -#: ../C/gdm.xml:3394(synopsis) -#, no-wrap -msgid "GraphicalThemes=circles" -msgstr "GraphicalThemes=circles" - -#: ../C/gdm.xml:3395(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 <filename>GraphicalThemeDir</filename>. This is only used if <filename>GraphicalThemeRand</filename> is set to true." -msgstr "" - -#: ../C/gdm.xml:3407(term) -msgid "GraphicalThemeRand" -msgstr "GraphicalThemeRand" - -#: ../C/gdm.xml:3409(synopsis) -#, no-wrap -msgid "GraphicalThemeRand=false" -msgstr "GraphicalThemeRand=false" - -#: ../C/gdm.xml:3410(para) -msgid "Whether the graphical greeter will use Only One Theme or Random Theme mode. Only One Theme mode uses themes listed by <filename>GraphicalTheme</filename>, Random Themes mode uses themes listed by <filename>GraphicalThemes</filename>. 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:3422(term) -msgid "GraphicalThemeDir" -msgstr "GraphicalThemeDir" - -#: ../C/gdm.xml:3424(synopsis) -#, no-wrap -msgid "GraphicalThemeDir=<share>/gdm/themes/" -msgstr "GraphicalThemeDir=<share>/gdm/themes/" - -#: ../C/gdm.xml:3425(para) -msgid "The directory where themes for the Themed Greeter are installed." -msgstr "" - -#: ../C/gdm.xml:3433(term) -msgid "GraphicalThemedColor" -msgstr "GraphicalThemedColor" - -#: ../C/gdm.xml:3435(synopsis) -#, no-wrap -msgid "GraphicalThemedColor=#76848F" -msgstr "GraphicalThemedColor=#76848F" - -#: ../C/gdm.xml:3436(para) -msgid "Use this color in the background of the Themed Greeter. This only affects the Themed Greeter." -msgstr "" - -#: ../C/gdm.xml:3444(term) -msgid "InfoMsgFile" -msgstr "InfoMsgFile" - -#: ../C/gdm.xml:3446(synopsis) -#, no-wrap -msgid "InfoMsgFile=/path/to/infofile" -msgstr "InfoMsgFile=/path/to/infofile" - -#: ../C/gdm.xml:3447(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:3458(term) -msgid "InfoMsgFont" -msgstr "InfoMsgFont" - -#: ../C/gdm.xml:3460(synopsis) -#, no-wrap -msgid "InfoMsgFont=fontspec" -msgstr "InfoMsgFont=fontspec" - -#: ../C/gdm.xml:3461(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:3473(term) -msgid "LocaleFile" -msgstr "LocaleFile" - -#: ../C/gdm.xml:3475(synopsis) -#, no-wrap -msgid "LocaleFile=<etc>/gdm/locale.alias" -msgstr "LocaleFile=<etc>/gdm/locale.alias" - -#: ../C/gdm.xml:3476(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:3485(term) -msgid "LockPosition" -msgstr "LockPosition" - -#: ../C/gdm.xml:3487(synopsis) -#, no-wrap -msgid "LockPosition=true" -msgstr "LockPosition=true" - -#: ../C/gdm.xml:3488(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:3496(term) -msgid "Logo" -msgstr "Logo" - -#: ../C/gdm.xml:3498(synopsis) -#, no-wrap -msgid "Logo=<share>/pixmaps/gnome-logo-large.png" -msgstr "Logo=<share>/pixmaps/gnome-logo-large.png" - -#: ../C/gdm.xml:3499(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:3510(term) -msgid "ChooserButtonLogo" -msgstr "ChooserButtonLogo" - -#: ../C/gdm.xml:3512(synopsis) -#, no-wrap -msgid "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" -msgstr "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" - -#: ../C/gdm.xml:3513(para) -msgid "Image file to display in the file chooser button in <command>gdmsetup</command>. This key is modified by <command>gdmsetup</command> and should not be manually modified by the user. This only affects the Login Window Preferences (<command>gdmsetup</command>)." -msgstr "" - -#: ../C/gdm.xml:3524(term) -msgid "MinimalUID" -msgstr "MinimalUID" - -#: ../C/gdm.xml:3526(synopsis) -#, no-wrap -msgid "MinimalUID=100" -msgstr "MinimalUID=100" - -#: ../C/gdm.xml:3527(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 <filename>Include</filename>, <filename>Exclude</filename>, and <filename>IncludeAll</filename>." -msgstr "" - -#: ../C/gdm.xml:3538(term) -msgid "PositionX" -msgstr "PositionX" - -#: ../C/gdm.xml:3540(synopsis) -#, no-wrap -msgid "PositionX=200" -msgstr "PositionX=200" - -#: ../C/gdm.xml:3541(para) -msgid "The horizontal position of the login window of the GTK+ Greeter." -msgstr "" - -#: ../C/gdm.xml:3549(term) -msgid "PositionY" -msgstr "PositionY" - -#: ../C/gdm.xml:3551(synopsis) -#, no-wrap -msgid "PositionY=100" -msgstr "PositionY=100" - -#: ../C/gdm.xml:3552(para) -msgid "The vertical position of the login window of the GTK+ Greeter." -msgstr "" - -#: ../C/gdm.xml:3560(term) -msgid "Quiver" -msgstr "Quiver" - -#: ../C/gdm.xml:3562(synopsis) -#, no-wrap -msgid "Quiver=true" -msgstr "Quiver=true" - -#: ../C/gdm.xml:3563(para) -msgid "Controls whether <command>gdmlogin</command> should shake the display when an incorrect username/password is entered. This only affects the GTK+ Greeter." -msgstr "" - -#: ../C/gdm.xml:3573(term) -msgid "DefaultRemoteWelcome" -msgstr "DefaultRemoteWelcome" - -#: ../C/gdm.xml:3575(synopsis) -#, no-wrap -msgid "DefaultRemoteWelcome=true" -msgstr "DefaultRemoteWelcome=true" - -#: ../C/gdm.xml:3576(para) -msgid "If set to true, the value \"Welcome to %n\" is used for the <filename>RemoteWelcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>RemoteWelcome</filename> 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:3590(term) -msgid "RemoteWelcome" -msgstr "RemoteWelcome" - -#: ../C/gdm.xml:3592(synopsis) -#, no-wrap, fuzzy -msgid "RemoteWelcome=Welcome to %n" -msgstr "RemoteWelcome=Welcome to %n" - -#: ../C/gdm.xml:3593(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 <filename>Welcome</filename> 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:3606(term) -msgid "RunBackgroundProgramAlways" -msgstr "RunBackgroundProgramAlways" - -#: ../C/gdm.xml:3608(synopsis) -#, no-wrap -msgid "RunBackgroundProgramAlways=false" -msgstr "RunBackgroundProgramAlways=false" - -#: ../C/gdm.xml:3609(para) -msgid "If this is true then the background application is run always, otherwise it is only run when the <filename>BackgroundType</filename> is 0 (None) This only affects the GTK+ Greeter." -msgstr "" - -#: ../C/gdm.xml:3619(term) -msgid "SetPosition" -msgstr "SetPosition" - -#: ../C/gdm.xml:3621(synopsis) -#, no-wrap -msgid "SetPosition=true" -msgstr "SetPosition=true" - -#: ../C/gdm.xml:3622(para) -msgid "If true the position of the login window of the GTK+ Greeter is determined by <filename>PositionX</filename> / <filename>PositionY</filename>." -msgstr "" - -#: ../C/gdm.xml:3631(term) -msgid "ShowGnomeFailsafeSession" -msgstr "ShowGnomeFailsafeSession" - -#: ../C/gdm.xml:3633(synopsis) -#, no-wrap -msgid "ShowGnomeFailsafeSession=true" -msgstr "ShowGnomeFailsafeSession=true" - -#: ../C/gdm.xml:3634(para) -msgid "Should the greeter show the Gnome Failsafe session in th sessions list." -msgstr "" - -#: ../C/gdm.xml:3642(term) -msgid "ShowLastSession" -msgstr "ShowLastSession" - -#: ../C/gdm.xml:3644(synopsis) -#, no-wrap -msgid "ShowLastSession=true" -msgstr "ShowLastSession=true" - -#: ../C/gdm.xml:3645(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 <filename>DefaultSession</filename>) 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:3658(term) -msgid "ShowXtermFailsafeSession" -msgstr "ShowXtermFailsafeSession" - -#: ../C/gdm.xml:3660(synopsis) -#, no-wrap -msgid "ShowXtermFailsafeSession=true" -msgstr "ShowXtermFailsafeSession=true" - -#: ../C/gdm.xml:3661(para) -msgid "Should the greeter show the Xterm Failsafe session in the sessions list." -msgstr "" - -#: ../C/gdm.xml:3669(term) -msgid "SoundOnLogin" -msgstr "SoundOnLogin" - -#: ../C/gdm.xml:3671(synopsis) -#, no-wrap -msgid "SoundOnLogin=true" -msgstr "SoundOnLogin=true" - -#: ../C/gdm.xml:3672(para) -msgid "If true, the greeter will play a sound or beep when it is ready for a login. See also the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0." -msgstr "" - -#: ../C/gdm.xml:3682(term) -msgid "SoundOnLoginSuccess" -msgstr "SoundOnLoginSuccess" - -#: ../C/gdm.xml:3684(synopsis) -#, no-wrap -msgid "SoundOnLoginSuccess=true" -msgstr "SoundOnLoginSuccess=true" - -#: ../C/gdm.xml:3685(para) -msgid "If true, the greeter will play a sound after a successful login attempt. See also the <filename>SoundOnLoginSuccessFile</filename> key." -msgstr "" - -#: ../C/gdm.xml:3694(term) -msgid "SoundOnLoginFailure" -msgstr "SoundOnLoginFailure" - -#: ../C/gdm.xml:3696(synopsis) -#, no-wrap -msgid "SoundOnLoginFailure=true" -msgstr "SoundOnLoginFailure=true" - -#: ../C/gdm.xml:3697(para) -msgid "If true, the greeter will play a sound after a failed login attempt. See also the <filename>SoundOnLoginFailureFile</filename> key." -msgstr "" - -#: ../C/gdm.xml:3706(term) -msgid "SoundOnLoginFile" -msgstr "SoundOnLoginFile" - -#: ../C/gdm.xml:3708(synopsis) -#, no-wrap -msgid "SoundOnLoginFile=/path/to/sound.wav" -msgstr "SoundOnLoginFile=/path/to/sound.wav" - -#: ../C/gdm.xml:3709(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) instead of a beep when the greeter is ready for a login. See also the <filename>SoundOnLogin</filename> key and the <filename>SoundProgram</filename> key. Supported since 2.5.90.0." -msgstr "" - -#: ../C/gdm.xml:3722(term) -msgid "SoundOnLoginSuccessFile" -msgstr "SoundOnLoginSuccessFile" - -#: ../C/gdm.xml:3724(synopsis) -#, no-wrap, fuzzy -msgid "SoundOnLoginSuccessFile=/path/to/sound.wav" -msgstr "SoundOnLoginSuccessFile=/path/to/sound.wav" - -#: ../C/gdm.xml:3725(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a successful login attempt. See also the <filename>SoundOnLoginSuccess</filename> key and the <filename>SoundProgram</filename> key." -msgstr "" - -#: ../C/gdm.xml:3736(term) -msgid "SoundOnLoginFailureFile" -msgstr "SoundOnLoginFailureFile" - -#: ../C/gdm.xml:3738(synopsis) -#, no-wrap, fuzzy -msgid "SoundOnLoginFailureFile=/path/to/sound.wav" -msgstr "SoundOnLoginFailureFile=/path/to/sound.wav" - -#: ../C/gdm.xml:3739(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a failed login attempt. See also the <filename>SoundOnLoginFailure</filename> key and the <filename>SoundProgram</filename> key." -msgstr "" - -#: ../C/gdm.xml:3750(term) -msgid "SystemMenu" -msgstr "SystemMenu" - -#: ../C/gdm.xml:3752(synopsis) -#, no-wrap -msgid "SystemMenu=true" -msgstr "SystemMenu=true" - -#: ../C/gdm.xml:3753(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:3766(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:3777(term) -msgid "TitleBar" -msgstr "TitleBar" - -#: ../C/gdm.xml:3779(synopsis) -#, no-wrap -msgid "TitleBar=true" -msgstr "TitleBar=true" - -#: ../C/gdm.xml:3780(para) -msgid "Display the title bar in the greeter. This only affects the GTK+ Greeter." -msgstr "" - -#: ../C/gdm.xml:3788(term) -msgid "Use24Clock" -msgstr "Use24Clock" - -#: ../C/gdm.xml:3790(synopsis) -#, no-wrap -msgid "Use24Clock=auto" -msgstr "Use24Clock=auto" - -#: ../C/gdm.xml:3791(para) -msgid "Select the use of 24 hour clock. Some locales do not support 12 hour format (like Finnish, that is <filename>fi_FI</filename>), and in those locales this setting has no effect at all." -msgstr "" - -#: ../C/gdm.xml:3797(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:3812(term) -msgid "UseCirclesInEntry" -msgstr "UseCirclesInEntry" - -#: ../C/gdm.xml:3814(synopsis) -#, no-wrap -msgid "UseCirclesInEntry=false" -msgstr "UseCirclesInEntry=false" - -#: ../C/gdm.xml:3815(para) -msgid "Use circles instead of asterisks in the password entry. This may not work with all fonts however." -msgstr "" - -#: ../C/gdm.xml:3823(term) -msgid "UseInvisibleInEntry" -msgstr "UseInvisibleInEntry" - -#: ../C/gdm.xml:3825(synopsis) -#, no-wrap -msgid "UseInvisibleInEntry=false" -msgstr "UseInvisibleInEntry=false" - -#: ../C/gdm.xml:3826(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 <filename>UseCirclesInEntry</filename> option." -msgstr "" - -#: ../C/gdm.xml:3836(term) -msgid "DefaultWelcome" -msgstr "DefaultWelcome" - -#: ../C/gdm.xml:3838(synopsis) -#, no-wrap -msgid "DefaultWelcome=true" -msgstr "DefaultWelcome=true" - -#: ../C/gdm.xml:3839(para) -msgid "If set to true, the value \"Welcome\" is used for the <filename>Welcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>Welcome</filename> setting is used." -msgstr "" - -#: ../C/gdm.xml:3849(term) -msgid "Welcome" -msgstr "Welcome" - -#: ../C/gdm.xml:3851(synopsis) -#, no-wrap, fuzzy -msgid "Welcome=Welcome" -msgstr "Welcome=Welcome" - -#: ../C/gdm.xml:3852(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:3861(para) -msgid "%d — display's hostname" -msgstr "" - -#: ../C/gdm.xml:3865(para) -msgid "%h — Fully qualified hostname" -msgstr "" - -#: ../C/gdm.xml:3869(para) -msgid "%m — machine (processor type)" -msgstr "" - -#: ../C/gdm.xml:3873(para) -msgid "%n — Nodename (i.e. hostname without .domain)" -msgstr "" - -#: ../C/gdm.xml:3877(para) -msgid "%r — release (OS version)" -msgstr "" - -#: ../C/gdm.xml:3881(para) -msgid "%s — sysname (i.e. OS)" -msgstr "" - -#: ../C/gdm.xml:3885(para) -msgid "This string is only used for local logins. For remote XDMCP logins we use <filename>RemoteWelcome</filename>." -msgstr "" - -#: ../C/gdm.xml:3890(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:3900(term) -msgid "XineramaScreen" -msgstr "XineramaScreen" - -#: ../C/gdm.xml:3902(synopsis) -#, no-wrap -msgid "XineramaScreen=0" -msgstr "XineramaScreen=0" - -#: ../C/gdm.xml:3903(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:3914(title) -msgid "XDCMP Chooser Options" -msgstr "" - -#: ../C/gdm.xml:3917(title) -msgid "[chooser]" -msgstr "[chooser]" - -#: ../C/gdm.xml:3920(term) -msgid "AllowAdd" -msgstr "AllowAdd" - -#: ../C/gdm.xml:3922(synopsis) -#, no-wrap -msgid "AllowAdd=true" -msgstr "AllowAdd=true" - -#: ../C/gdm.xml:3923(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:3932(term) -msgid "Broadcast" -msgstr "Broadcast" - -#: ../C/gdm.xml:3934(synopsis) -#, no-wrap -msgid "Broadcast=true" -msgstr "Broadcast=true" - -#: ../C/gdm.xml:3935(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 <filename>Hosts</filename> key." -msgstr "" - -#: ../C/gdm.xml:3947(term) -msgid "Multicast" -msgstr "Multicast" - -#: ../C/gdm.xml:3949(synopsis) -#, no-wrap -msgid "Multicast=true" -msgstr "Multicast=true" - -#: ../C/gdm.xml:3950(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 <filename>Hosts </filename> key. The host will respond if it is listening to XDMCP requests and IPv6 is enabled there." -msgstr "" - -#: ../C/gdm.xml:3962(term) -msgid "MulticastAddr" -msgstr "MulticastAddr" - -#: ../C/gdm.xml:3964(synopsis) -#, no-wrap -msgid "MulticastAddr=ff02::1" -msgstr "MulticastAddr=ff02::1" - -#: ../C/gdm.xml:3965(para) -msgid "This is the Link-local Multicast address and is hardcoded here." -msgstr "" - -#: ../C/gdm.xml:3972(term) -msgid "DefaultHostImage" -msgstr "DefaultHostImage" - -#: ../C/gdm.xml:3974(synopsis) -#, no-wrap -msgid "DefaultHostImage=<share>/pixmaps/nohost.png" -msgstr "DefaultHostImage=<share>/pixmaps/nohost.png" - -#: ../C/gdm.xml:3975(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:3985(term) -msgid "HostImageDir" -msgstr "HostImageDir" - -#: ../C/gdm.xml:3987(synopsis) -#, no-wrap -msgid "HostImageDir=<share>/hosts" -msgstr "HostImageDir=<share>/hosts" - -#: ../C/gdm.xml:3988(para) -msgid "Repository for host icon files. The sysadmin can place icons for remote hosts here and they will appear in <filename>gdmchooser</filename>." -msgstr "" - -#: ../C/gdm.xml:3994(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:4004(term) -msgid "Hosts" -msgstr "Hosts" - -#: ../C/gdm.xml:4006(synopsis) -#, no-wrap, fuzzy -msgid "Hosts=host1,host2" -msgstr "Hosts=host1,host2" - -#: ../C/gdm.xml:4007(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 <filename>Broadcast</filename> 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:4019(term) -msgid "ScanTime" -msgstr "ScanTime" - -#: ../C/gdm.xml:4021(synopsis) -#, no-wrap -msgid "ScanTime=4" -msgstr "ScanTime=4" - -#: ../C/gdm.xml:4022(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:4034(title) -msgid "Debug Configuration" -msgstr "" - -#: ../C/gdm.xml:4037(title) -msgid "[debug]" -msgstr "[debug]" - -#: ../C/gdm.xml:4043(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:4053(term) -msgid "Gestures" -msgstr "Gestures" - -#: ../C/gdm.xml:4055(synopsis) -#, no-wrap -msgid "Gestures=false" -msgstr "Gestures=false" - -#: ../C/gdm.xml:4056(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:4069(title) -msgid "Custom Commands" -msgstr "" - -#: ../C/gdm.xml:4071(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:4080(title) -msgid "[customcommand]" -msgstr "[customcommand]" - -#: ../C/gdm.xml:4083(term) -msgid "CustomCommand[0-9]" -msgstr "CustomCommand[0-9]" - -#: ../C/gdm.xml:4085(synopsis) -#, no-wrap -msgid "CustomCommand[0-9]=" -msgstr "CustomCommand[0-9]=" - -#: ../C/gdm.xml:4086(para) -msgid "Full path and arguments to command to be executed when user selects <filename>n-th</filename> \"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 <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "" - -#: ../C/gdm.xml:4101(term) -msgid "CustomCommandIsPersistent[0-9]" -msgstr "CustomCommandIsPersistent[0-9]" - -#: ../C/gdm.xml:4103(synopsis) -#, no-wrap -msgid "CustomCommandIsPersistent[0-9]=" -msgstr "CustomCommandIsPersistent[0-9]=" - -#: ../C/gdm.xml:4104(para) -msgid "Specifies if <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "" - -#: ../C/gdm.xml:4118(term) -msgid "CustomCommandLabel[0-9]" -msgstr "CustomCommandLabel[0-9]" - -#: ../C/gdm.xml:4120(synopsis) -#, no-wrap -msgid "CustomCommandLabel[0-9]=" -msgstr "CustomCommandLabel[0-9]=" - -#: ../C/gdm.xml:4121(para) -msgid "Specifies the stock label that will be displayed on the <filename>n-th</filename> \"Custom Command\" buttons and menu items. If not specified the default value is \"Custom_[0-9]\". This option is only valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9. This option can't contain any semicolon characters (i.e. \";\")." -msgstr "" - -#: ../C/gdm.xml:4135(term) -msgid "CustomCommandLRLabel[0-9]" -msgstr "CustomCommandLRLabel[0-9]" - -#: ../C/gdm.xml:4137(synopsis) -#, no-wrap -msgid "CustomCommandLRLabel[0-9]=" -msgstr "CustomCommandLRLabel[0-9]=" - -#: ../C/gdm.xml:4138(para) -msgid "Specifies the stock label that will be displayed on the <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "" - -#: ../C/gdm.xml:4152(term) -msgid "CustomCommandNoRestart[0-9]" -msgstr "CustomCommandNoRestart[0-9]" - -#: ../C/gdm.xml:4154(synopsis) -#, no-wrap -msgid "CustomCommandNoRestart[0-9]=" -msgstr "CustomCommandNoRestart[0-9]=" - -#: ../C/gdm.xml:4155(para) -msgid "Specifies if gdm will be stopped/restarted once <filename>n-th</filename> \"Custom Command\" has been executed. If not specified the default value is \"false\". This option is only valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9. In addition when corresponding <filename>CustomCommandIsPersistent</filename> is set to true, setting CustomCommandNoRestart to false will place corresponding <filename>CustomCommand</filename> in the Shut Down dialog set of actions, setting it to true will place corresponding <filename>CustomCommand</filename> in the Log Out dialog set of actions." -msgstr "" - -#: ../C/gdm.xml:4175(term) -msgid "CustomCommandText[0-9]" -msgstr "CustomCommandText[0-9]" - -#: ../C/gdm.xml:4177(synopsis) -#, no-wrap -msgid "CustomCommandText[0-9]=" -msgstr "CustomCommandText[0-9]=" - -#: ../C/gdm.xml:4178(para) -msgid "Specifies the message that will be displayed on the warning dialog box once <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "" - -#: ../C/gdm.xml:4192(term) -msgid "CustomCommandTooltip[0-9]" -msgstr "CustomCommandTooltip[0-9]" - -#: ../C/gdm.xml:4194(synopsis) -#, no-wrap -msgid "CustomCommandTooltip[0-9]=" -msgstr "CustomCommandTooltip[0-9]=" - -#: ../C/gdm.xml:4195(para) -msgid "Specifies the message that will be displayed on tooltips for <filename>n-th</filename> \"Custom Command\" entries. If not specified the default value is \"Execute custom command [0-9]\". This option is only valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "" - -#: ../C/gdm.xml:4210(title) -msgid "X Server Definitions" -msgstr "" - -#: ../C/gdm.xml:4212(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 <filename>Standard</filename> is required. If you do not specify this server, GDM will assume default values for a 'Standard' server and the path given by <filename>daemon/StandardXServer</filename>. <filename>Standard</filename> is used as the default, in situations when no other server has been defined." -msgstr "" - -#: ../C/gdm.xml:4223(para) -msgid "Servers are defined by sections named <filename>server-</filename> 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, <filename>server-</filename> sections in the GDM Custom Configuration File override values in the GDM System Defaults Configuration File. In other words, if a <filename>server-Standard</filename> 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:4238(title) -msgid "[server-Standard]" -msgstr "[server-Standard]" - -#: ../C/gdm.xml:4241(term) -msgid "name" -msgstr "name" - -#: ../C/gdm.xml:4243(synopsis) -#, no-wrap -msgid "name=Standard server" -msgstr "name=Standard server" - -#: ../C/gdm.xml:4244(para) -msgid "The name that will be displayed to the user." -msgstr "" - -#: ../C/gdm.xml:4251(term) -msgid "command" -msgstr "command" - -#: ../C/gdm.xml:4253(synopsis) -#, no-wrap, fuzzy -msgid "command=/path/to/X" -msgstr "command=/path/to/X" - -#: ../C/gdm.xml:4254(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:4262(term) -msgid "flexible" -msgstr "flexible" - -#: ../C/gdm.xml:4264(synopsis) -#, no-wrap -msgid "flexible=true" -msgstr "flexible=true" - -#: ../C/gdm.xml:4265(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:4273(term) -msgid "handled" -msgstr "handled" - -#: ../C/gdm.xml:4275(synopsis) -#, no-wrap -msgid "handled=true" -msgstr "handled=true" - -#: ../C/gdm.xml:4276(para) -msgid "Indicates that GDM should run the login window on this server and allow a user to log in. If set to false, then GDM will just run this server and wait for it to terminate. This can be useful to run an X terminal using GDM. When this is done you should normally also add <filename>-terminate</filename> to the command line of the server to make the server terminate after each session. Otherwise the control of the slave will never come back to GDM and, for example, soft restarts won't work. This is because GDM assumes there is a login in progress for the entire time this server is active." -msgstr "" - -#: ../C/gdm.xml:4292(term) -msgid "chooser" -msgstr "chooser" - -#: ../C/gdm.xml:4294(synopsis) -#, no-wrap -msgid "chooser=false" -msgstr "chooser=false" - -#: ../C/gdm.xml:4295(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:4306(title) -msgid "Local Static X Display Configuration" -msgstr "" - -#: ../C/gdm.xml:4308(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 <filename>[servers]</filename> section corresponds to the display number to be managed. Normally there is only one key, which is the key <filename>0</filename>, which corresponds to the display <filename>:0</filename>." -msgstr "" - -#: ../C/gdm.xml:4323(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 <filename>[servers]</filename> section in the GDM Custom Configuration File overrides values in the GDM System Defaults Configuration File." -msgstr "" - -#: ../C/gdm.xml:4333(title) -msgid "[servers]" -msgstr "[servers]" - -#: ../C/gdm.xml:4336(term) -msgid "<display number>" -msgstr "" - -#: ../C/gdm.xml:4338(synopsis) -#, no-wrap -msgid "0=Standard" -msgstr "" - -#: ../C/gdm.xml:4339(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:4345(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:4358(para) -msgid "GDM will splice \"<filename>-auth <ServAuthDir>/:n.Xauth :n</filename>\", where n is the display number. Inside the command line before all other arguments before running the X server." -msgstr "" - -#: ../C/gdm.xml:4365(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 <filename>VTAllocation</filename> key is set." -msgstr "" - -#: ../C/gdm.xml:4374(para) -msgid "Normally you do not need to add a <filename>-nolisten tcp</filename> flag as this is added automatically for local X servers when the <filename>DisallowTCP</filename> option is set." -msgstr "" - -#: ../C/gdm.xml:4384(term) -msgid "priority" -msgstr "priority" - -#: ../C/gdm.xml:4386(synopsis) -#, no-wrap -msgid "priority=0" -msgstr "priority=0" - -#: ../C/gdm.xml:4387(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:4403(title) -msgid "Per User Configuration" -msgstr "" - -#: ../C/gdm.xml:4405(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 <filename>UserMaxFile</filename> 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:4419(para) -msgid "First there is the <filename>~/.dmrc</filename> file. In theory this file should be shared between GDM and KDM, so users only have to configure things once. This is a standard <filename>.ini</filename> style configuration file. It has one section called <filename>[Desktop]</filename> which has two keys: <filename>Session</filename> and <filename>Language</filename>." -msgstr "" - -#: ../C/gdm.xml:4428(para) -msgid "The <filename>Session</filename> key specifies the basename of the session <filename>.desktop</filename> file that the user wishes to normally use (without the <filename>.desktop</filename> extension, in other words). The <filename>Language</filename> key specifies the language that the user wishes to use by default. If either of these keys is missing, the system default is used. The file would normally look as follows:" -msgstr "" - -#: ../C/gdm.xml:4438(screen) -#, no-wrap -msgid "\n[Desktop]\nSession=gnome\nLanguage=cs_CZ.UTF-8\n" -msgstr "" - -#: ../C/gdm.xml:4444(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:4450(para) -msgid "If the GDM Face Browser is turned on, then the file <filename>$HOME/.face</filename> 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 <filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> values defined in the GDM configuration or it will be ignored. Users can run the <command>gdmphotosetup</command> program to specify a face image and it will copy the file to the <filename>$HOME/.face</filename> location and scale it so its longest dimension is not larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> values. <command>gdmphotosetup</command> takes care to not change the aspect ratio of the image." -msgstr "" - -#: ../C/gdm.xml:4465(para) -msgid "Face images can also be placed in the global face directory, which is specified by the <filename>GlobalFaceDir</filename> configuration option ( normally <filename><share>/pixmaps/faces/</filename>) and the filename should be the name of the user, optionally with a <filename>.png</filename>, <filename>.jpg</filename>, etc. appended." -msgstr "" - -#: ../C/gdm.xml:4476(title) -#, fuzzy -msgid "Controlling GDM" -msgstr "GDM 조종하기" - -#: ../C/gdm.xml:4478(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:4485(title) -msgid "Commands" -msgstr "" - -#: ../C/gdm.xml:4487(para) -msgid "To stop GDM, you can either send the TERM signal to the main daemon or run the <command>gdm-stop</command> command which is in the <filename><sbin>/</filename> directory. To restart GDM, you can either send the HUP signal to the main daemon or run the <command>gdm-restart</command> command which is also in the <filename><sbin>/</filename> 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 <command>gdm-safe-restart</command> command which is in the <filename><sbin>/</filename> directory as well." -msgstr "" - -#: ../C/gdm.xml:4500(para) -msgid "The <command>gdmflexiserver</command> 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 <command>gdmflexiserver</command> 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 <command>gdmflexiserver --help</command> to get a listing of possible options." -msgstr "" - -#: ../C/gdm.xml:4516(title) -msgid "The FIFO protocol" -msgstr "" - -#: ../C/gdm.xml:4518(para) -msgid "GDM also provides a FIFO called <filename>.gdmfifo</filename> in the <filename>ServAuthDir</filename> directory (usually <filename><var>/gdm/.gdmfifo</filename>). 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:4529(para) -msgid "Full and up to date documentation of the commands and their use is contained in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look for the defines starting with <filename>GDM_SOP_</filename>. The commands which require the pid of the slave as an argument are the ones that are really used for internal communication of the slave with the master and should not be used." -msgstr "" - -#: ../C/gdm.xml:4541(title) -msgid "Socket Protocol" -msgstr "" - -#: ../C/gdm.xml:4543(para) -msgid "GDM provides a unix domain socket for communication at <filename>/tmp/.gdm_socket</filename>. 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 <command>gdmflexiserver</command> command uses this protocol, for example, to launch flexible (on-demand) displays." -msgstr "" - -#: ../C/gdm.xml:4553(para) -msgid "gdmflexiserver accepts the following commands with the --command option:" -msgstr "" - -#: ../C/gdm.xml:4558(screen) -#, no-wrap -msgid "\nADD_DYNAMIC_DISPLAY\nALL_SERVERS\nATTACHED_SERVERS\nAUTH_LOCAL\nCLOSE\nFLEXI_XNEST\nFLEXI_XNEST_USER\nFLEXI_XSERVER\nFLEXI_XSERVER_USER\nGET_CONFIG\nGET_CONFIG_FILE\nGET_CUSTOM_CONFIG_FILE\nGET_SERVER_LIST\nGET_SERVER_DETAILS\nGREETERPIDS\nQUERY_LOGOUT_ACTION\nQUERY_CUSTOM_CMD_LABELS\nQUERY_CUSTOM_CMD_NO_RESTART_STATUS\nQUERY_VT\nRELEASE_DYNAMIC_DISPLAYS\nREMOVE_DYNAMIC_DISPLAY\nSERVER_BUSY\nSET_LOGOUT_ACTION\nSET_SAFE_LOGOUT_ACTION\nSET_VT\nUPDATE_CONFIG\nVERSION\n" -msgstr "" - -#: ../C/gdm.xml:4588(para) -msgid "These are described in detail below, including required arguments, response format, and return codes." -msgstr "" - -#: ../C/gdm.xml:4594(title) -msgid "ADD_DYNAMIC_DISPLAY" -msgstr "ADD_DYNAMIC_DISPLAY" - -#: ../C/gdm.xml:4595(screen) -#, no-wrap -msgid "\nADD_DYNAMIC_DISPLAY: Create a new server definition that will\n run on the specified display leaving, it\n in DISPLAY_CONFIG state.\nSupported since: 2.8.0.0\nArguments: <display to run on>=<server>\n Where <server> is either a configuration named in the\n GDM configuration or a literal command name.\nAnswers:\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:4617(title) -msgid "ALL_SERVERS" -msgstr "ALL_SERVERS" - -#: ../C/gdm.xml:4618(screen) -#, no-wrap -msgid "\nALL_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.\nSupported since: 2.4.2.96\nArguments: None\nAnswers:\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:4641(title) -msgid "ATTACHED_SERVERS" -msgstr "ATTACHED_SERVERS" - -#: ../C/gdm.xml:4642(screen) -#, no-wrap -msgid "\nATTACHED_SERVERS: List all attached displays. Doesn't list XDMCP\n and xnest non-attached displays.\nNote: 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.\nSupported since: 2.2.4.0\nArguments: <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.\nAnswers:\n OK <server>;<server>;...\n\n <server> is <display>,<logged in user>,<vt or xnest 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:4674(title) -msgid "AUTH_LOCAL" -msgstr "AUTH_LOCAL" - -#: ../C/gdm.xml:4675(screen) -#, no-wrap -msgid "\nAUTH_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.\nNote: The AUTH LOCAL command requires the\n --authenticate option, although only\n FLEXI XSERVER uses this currently.\nNote: 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.\nSupported since: 2.2.4.0\nArguments: <xauth cookie>\n <xauth cookie> is in hex form with no 0x prefix\nAnswers:\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:4705(title) -msgid "CLOSE" -msgstr "CLOSE" - -#: ../C/gdm.xml:4706(screen) -#, no-wrap -msgid "\nCLOSE: Close sockets connection\nSupported since: 2.2.4.0\nArguments: None\nAnswers: None\n" -msgstr "" - -#: ../C/gdm.xml:4715(title) -msgid "FLEXI_XNEST" -msgstr "FLEXI_XNEST" - -#: ../C/gdm.xml:4716(screen) -#, no-wrap -msgid "\nFLEXI_XNEXT: Start a new flexible nested display.\nNote: 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.\nNote: 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.\nSupported since: 2.3.90.4\nArguments: <display to run on> <uid of requesting user>\n <xauth cookie for the display> <xauth file>\nAnswers:\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:4755(title) -msgid "FLEXI_XNEST_USER" -msgstr "FLEXI_XNEST_USER" - -#: ../C/gdm.xml:4756(screen) -#, no-wrap -msgid "\nFLEXI_XNEST_USER: Start a new flexible nested display and\n initialize the greeter with the given username.\nNote: This is a variant of the FLEXI_XNEST command.\nNote: 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.\nSupported since: 2.17.7\nArguments: <username> <display to run on> <uid of requesting user>\n <xauth cookie for the display> <xauth file>\nAnswers:\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:4785(title) -msgid "FLEXI_XSERVER" -msgstr "FLEXI_XSERVER" - -#: ../C/gdm.xml:4786(screen) -#, no-wrap -msgid "\nFLEXI_XSERVER: Start a new X flexible display. Only supported on\n connection that passed AUTH_LOCAL\nSupported since: 2.2.4.0\nArguments: <xserver type>\n If no arguments, starts the standard X server\nAnswers:\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:4808(title) -msgid "FLEXI_XSERVER_USER" -msgstr "FLEXI_XSERVER_USER" - -#: ../C/gdm.xml:4809(screen) -#, no-wrap -msgid "\nFLEXI_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\nSupported since: 2.17.7 \nArguments: <username> <xserver type>\n If no server type specified, starts the standard X server\nAnswers:\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:4832(title) -msgid "GET_CONFIG" -msgstr "GET_CONFIG" - -#: ../C/gdm.xml:4833(screen) -#, no-wrap -msgid "\nGET_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 2.13.0.2\n translated keys (such as \"greeter/GdmWelcome[cs]\" are\n supported via GET_CONFIG. Also starting with version\n 2.13.0.2 it is no longer necessary to include the\n default value (i.e. you can use key \"greeter/IncludeAll\"\n instead of having to use \"greeter/IncludeAll=false\". \nSupported since: 2.6.0.9\nArguments: <key>\nAnswers:\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:4856(title) -msgid "GET_CONFIG_FILE" -msgstr "GET_CONFIG_FILE" - -#: ../C/gdm.xml:4857(screen) -#, no-wrap -msgid "\nGET_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.\nSupported since: 2.8.0.2\nArguments: None\nAnswers:\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:4874(title) -msgid "GET_CUSTOM_CONFIG_FILE" -msgstr "GET_CUSTOM_CONFIG_FILE" - -#: ../C/gdm.xml:4875(screen) -#, no-wrap -msgid "\nGET_CUSTOM_CONFIG_FILE: Get custom config file location being\n used by the daemon.\nSupported since: 2.14.0.0\nArguments: None\nAnswers:\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:4891(title) -msgid "GET_SERVER_DETAILS" -msgstr "GET_SERVER_DETAILS" - -#: ../C/gdm.xml:4892(screen) -#, no-wrap -msgid "\nGET_SERVER_DETAILS: Get detail information for a specific server.\nSupported since: 2.13.0.4\nArguments: <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\nAnswers:\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:4921(title) -msgid "GET_SERVER_LIST" -msgstr "GET_SERVER_LIST" - -#: ../C/gdm.xml:4922(screen) -#, no-wrap -msgid "\nGET_SERVER_LIST: Get a list of the server sections from\n the configuration file.\nSupported since: 2.13.0.4\nArguments: None\nAnswers:\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:4938(title) -msgid "GREETERPIDS" -msgstr "GREETERPIDS" - -#: ../C/gdm.xml:4939(screen) -#, no-wrap -msgid "\nGREETERPIDS: 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.\nSupported since: 2.3.90.2\nArguments: None\nAnswers:\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:4955(title) -msgid "QUERY_LOGOUT_ACTION" -msgstr "QUERY_LOGOUT_ACTION" - -#: ../C/gdm.xml:4956(screen) -#, no-wrap -msgid "\nQUERY_LOGOUT_ACTION: Query which logout actions are possible\n Only supported on connections that passed\n AUTH_LOCAL.\nSupported since: 2.5.90.0\nAnswers:\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:4978(title) -msgid "QUERY_CUSTOM_CMD_LABELS" -msgstr "QUERY_CUSTOM_CMD_LABELS" - -#: ../C/gdm.xml:4979(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:5000(title) -msgid "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" -msgstr "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" - -#: ../C/gdm.xml:5001(screen) -#, no-wrap -msgid "\nQUERY_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.\nSupported since: 2.5.90.0\nAnswers:\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:5022(title) -msgid "QUERY_VT" -msgstr "QUERY_VT" - -#: ../C/gdm.xml:5023(screen) -#, no-wrap -msgid "\nQUERY_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.\nSupported since: 2.5.90.0\nArguments: None\nAnswers:\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:5046(title) -msgid "RELEASE_DYNAMIC_DISPLAYS" -msgstr "RELEASE_DYNAMIC_DISPLAYS" - -#: ../C/gdm.xml:5047(screen) -#, no-wrap -msgid "\nRELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in \n DISPLAY_CONFIG state\nSupported since: 2.8.0.0\nArguments: <display to release>\nAnswers:\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:5064(title) -msgid "REMOVE_DYNAMIC_DISPLAY" -msgstr "REMOVE_DYNAMIC_DISPLAY" - -#: ../C/gdm.xml:5065(screen) -#, no-wrap -msgid "\nREMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server\n and purging the display configuration\nSupported since: 2.8.0.0\nArguments: <display to remove>\nAnswers:\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:5082(title) -msgid "SERVER_BUSY" -msgstr "SERVER_BUSY" - -#: ../C/gdm.xml:5083(screen) -#, no-wrap -msgid "\nSERVER_BUSY: Returns true if half or more of the daemon's sockets\n are busy, false otherwise. Used by slave programs\n which want to ensure they do not overwhelm the \n sever.\nSupported since: 2.13.0.8\nArguments: None\nAnswers:\n OK <value>\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:5100(title) -msgid "SET_LOGOUT_ACTION" -msgstr "SET_LOGOUT_ACTION" - -#: ../C/gdm.xml:5101(screen) -#, no-wrap -msgid "\nSET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n slave process exits. Only supported on\n connections that passed AUTH_LOCAL.\nSupported since: 2.5.90.0\nArguments: <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]'\nAnswers:\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:5124(title) -msgid "SET_SAFE_LOGOUT_ACTION" -msgstr "SET_SAFE_LOGOUT_ACTION" - -#: ../C/gdm.xml:5125(screen) -#, no-wrap -msgid "\nSET_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.\nSupported since: 2.5.90.0\nArguments: <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]'\nAnswers:\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:5155(title) -msgid "SET_VT" -msgstr "SET_VT" - -#: ../C/gdm.xml:5156(screen) -#, no-wrap -msgid "\nSET_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.\nSupported since: 2.5.90.0\nArguments: <vt>\nAnswers:\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:5177(title) -msgid "UPDATE_CONFIG" -msgstr "UPDATE_CONFIG" - -#: ../C/gdm.xml:5178(screen) -#, no-wrap -msgid "\nUPDATE_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)\nSupported since: 2.3.90.2\nArguments: <key>\n <key> is just the base part of the key such as\n \"security/AllowRemoteRoot\"\nAnswers:\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:5254(title) -msgid "VERSION" -msgstr "VERSION" - -#: ../C/gdm.xml:5255(screen) -#, no-wrap -msgid "\nVERSION: Query GDM version\nSupported since: 2.2.4.0\nArguments: None\nAnswers:\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:5272(title) -msgid "GDM Commands" -msgstr "GDM 명령어" - -#: ../C/gdm.xml:5275(title) -msgid "GDM User Commands" -msgstr "" - -#: ../C/gdm.xml:5277(para) -msgid "The GDM package provides the following different commands in <filename>bindir</filename> intended to be used by the end-user:" -msgstr "" - -#: ../C/gdm.xml:5283(title) -msgid "<command>gdmXnestchooser</command> and <command>gdmXnest</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5286(para) -msgid "The <command>gdmXnestchooser</command> 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 <command>gdmXnestchooser somehost</command> will run the XDMCP chooser from host <command>somehost</command> inside a nested X server session. You can make this command do a direct query instead by passing the <command>-d</command> option as well. In addition to the following options, this command also supports standard GNOME options." -msgstr "" - -#: ../C/gdm.xml:5301(title) -msgid "<command>gdmXnestchooser</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5304(term) -msgid "-x, --xnest=STRING" -msgstr "-x, --xnest=<문자열>" - -#: ../C/gdm.xml:5306(para) -msgid "Nested X server command line, default is defined by the <filename>Xnest</filename> configuration option." -msgstr "" - -#: ../C/gdm.xml:5314(term) -msgid "-o, --xnest-extra-options=OPTIONS" -msgstr "-o, --xnest-extra-options=<옵션>" - -#: ../C/gdm.xml:5316(para) -msgid "Extra options for nested X server, default is no options." -msgstr "" - -#: ../C/gdm.xml:5323(term) -msgid "-n, --no-query" -msgstr "-n, --no-query" - -#: ../C/gdm.xml:5325(para) -msgid "Just run nested X server, no query (no chooser)" -msgstr "" - -#: ../C/gdm.xml:5332(term) -msgid "-d, --direct" -msgstr "-d, --direct" - -#: ../C/gdm.xml:5334(para) -msgid "Do direct query instead of indirect (chooser)" -msgstr "" - -#: ../C/gdm.xml:5341(term) -msgid "-B, --broadcast" -msgstr "-B, --broadcast" - -#: ../C/gdm.xml:5343(para) -msgid "Run broadcast instead of indirect (chooser)" -msgstr "" - -#: ../C/gdm.xml:5350(term) -msgid "-b, --background" -msgstr "-b, --background" - -#: ../C/gdm.xml:5352(para) -msgid "Run in background" -msgstr "" - -#: ../C/gdm.xml:5359(term) -msgid "--no-gdm-check" -msgstr "--no-gdm-check" - -#: ../C/gdm.xml:5361(para) -msgid "Don't check for running GDM" -msgstr "" - -#: ../C/gdm.xml:5370(title) ../C/gdm.xml:5413(title) -msgid "<command>gdmflexichooser</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5372(para) -msgid "The <command>gdmflexiserver</command> 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:5379(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:5393(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:5400(para) -msgid "The <command>gdmflexiserver --command</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:5406(para) -msgid "In addition to the following options, <command>gdmflexiserver</command> also supports standard GNOME options." -msgstr "" - -#: ../C/gdm.xml:5416(term) -msgid "-c, --command=COMMAND" -msgstr "-c, --command=<명령어>" - -#: ../C/gdm.xml:5418(para) -msgid "Send the specified protocol command to GDM" -msgstr "" - -#: ../C/gdm.xml:5425(term) -msgid "-n, --xnest" -msgstr "-n, --xnest" - -#: ../C/gdm.xml:5427(para) -msgid "Start a flexible X display in Nested mode" -msgstr "" - -#: ../C/gdm.xml:5434(term) -msgid "-l, --no-lock" -msgstr "-l, --no-lock" - -#: ../C/gdm.xml:5436(para) -msgid "Do not lock current screen" -msgstr "" - -#: ../C/gdm.xml:5443(term) -msgid "-d, --debug" -msgstr "-d, --debug" - -#: ../C/gdm.xml:5445(para) -msgid "Turns on debugging output which gets sent to syslog. Same as turning on debug in the configuration file." -msgstr "" - -#: ../C/gdm.xml:5453(term) -msgid "-a, --authenticate" -msgstr "-a, --authenticate" - -#: ../C/gdm.xml:5455(para) -msgid "Authenticate before running --command" -msgstr "" - -#: ../C/gdm.xml:5462(term) -msgid "-s, --startnew" -msgstr "-s, --startnew" - -#: ../C/gdm.xml:5464(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:5475(title) ../C/gdm.xml:5501(title) -msgid "<command>gdmdynamic</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5477(para) -msgid "The <command>gdmdynamic</command> command which creates, runs, and removes displays (X servers) on demand." -msgstr "" - -#: ../C/gdm.xml:5482(para) -msgid "<command>gdmdynamic</command> 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 <command>gdmdynamic</command> command can be used to create a new display on a particular display number, run all newly created displays, or remove a display. The <command>gdmdynamic</command> command can also be used to list all attached displays, or only attached displays that match a pattern." -msgstr "" - -#: ../C/gdm.xml:5493(para) -msgid "This program is designed to manage multiple simultaneous requests and works 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:5506(emphasis) -msgid "One of the following options can be used per instance:" -msgstr "" - -#: ../C/gdm.xml:5513(term) -msgid "-a display=server" -msgstr "-a <디스플레이>=<서버>" - -#: ../C/gdm.xml:5515(para) -msgid "Add a new display configuration, leaving it in the DISPLAY_CONFIG state. For example, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a 3=/usr/X11R6/bin/X -dev /dev/fb2\"</command>" -msgstr "" - -#: ../C/gdm.xml:5521(para) -msgid "The display will not actually be started until the display is released by calling <command>gdmdynamic</command> again with the -r option." -msgstr "" - -#: ../C/gdm.xml:5529(term) -msgid "-r" -msgstr "-r" - -#: ../C/gdm.xml:5531(para) -msgid "Release (run) all displays waiting in the DISPLAY_CONFIG state." -msgstr "" - -#: ../C/gdm.xml:5538(term) -msgid "-d display" -msgstr "-d <디스플레이>" - -#: ../C/gdm.xml:5540(para) -msgid "Delete a display, killing the X server and purging the display configuration. For example, \"-d 3\"." -msgstr "" - -#: ../C/gdm.xml:5548(term) -msgid "-l [pattern]" -msgstr "" - -#: ../C/gdm.xml:5550(para) -msgid "List displays via the ATTACHED_SERVERS <command>gdmflexiserver</command> command. Without a pattern lists all attached displays. With a pattern will match using glob characters '*', '?', and '[]'. For example: <command>\"-l Standard*\"</command><command>\"-l *Xorg*\"</command>" -msgstr "" - -#: ../C/gdm.xml:5563(emphasis) -msgid "These options can be added to the above:" -msgstr "" - -#: ../C/gdm.xml:5570(term) -msgid "-v" -msgstr "-v" - -#: ../C/gdm.xml:5572(para) -msgid "Verbose mode. Prinr diagnostic messages about each message sent to GDM." -msgstr "" - -#: ../C/gdm.xml:5580(term) -msgid "-b" -msgstr "-b" - -#: ../C/gdm.xml:5582(para) -msgid "Background mode. Fork child to do the work and return immediately." -msgstr "" - -#: ../C/gdm.xml:5589(term) -msgid "-t RETRY" -msgstr "" - -#: ../C/gdm.xml:5591(para) -msgid "If the daemon socket is busy, <command>gdmdynamic</command> will retry to open the connection the specified RETRY number of times. Default value is 15." -msgstr "" - -#: ../C/gdm.xml:5600(term) -msgid "-s SLEEP" -msgstr "" - -#: ../C/gdm.xml:5602(para) -msgid "If the daemon socket is busy, <command>gdmdynamic</command> 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:5617(title) -msgid "<command>gdmphotosetup</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5619(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 <filename>~/.face</filename>. This command accepts standard GNOME options." -msgstr "" - -#: ../C/gdm.xml:5628(title) -msgid "<command>gdmthemetester</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5630(para) -msgid "<command>gdmthemetester</command> 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. <command>gdmthemetester</command> requires that the system support <command>gdmXnest</command>. Note that themes can display differently depending on the theme's \"Show mode\". <command>gdmthemetester</command> allows viewing the themes in different modes via the environment option. Valid environment values and their meanings follow: <screen>\nconsole - In console mode.\nconsole-timed - In console non-flexi mode.\nflexi - In flexi mode.\nxdmcp - In remote (XDMCP) mode.\nremote-flexi - In remote (XDMCP) & flexi mode.\n</screen>" -msgstr "" - -#: ../C/gdm.xml:5656(title) -msgid "GDM Root User Commands" -msgstr "" - -#: ../C/gdm.xml:5658(para) -msgid "The GDM package provides the following different commands in <filename>sbindir</filename> intended to be used by the root user:" -msgstr "" - -#: ../C/gdm.xml:5664(title) ../C/gdm.xml:5680(title) -msgid "<command>gdm</command> and <command>gdm-binary</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5667(para) -msgid "The <command>gdm</command> command is really just a script which runs the <command>gdm-binary</command>, passing along any options. Before launching <command>gdm-binary</command>, the gdm wrapper script will source the <filename><etc>/profile</filename> file to set the standard system environment variables. In order to better support internationalization, it will also set the LC_MESSAGES environment variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you really need to set some additional environment before launching GDM, you can do so in this script." -msgstr "" - -#: ../C/gdm.xml:5684(term) -msgid "--help" -msgstr "--help" - -#: ../C/gdm.xml:5686(para) -msgid "Gives a brief overview of the command line options." -msgstr "" - -#: ../C/gdm.xml:5693(term) -msgid "--nodaemon" -msgstr "--nodaemon" - -#: ../C/gdm.xml:5695(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:5705(term) -msgid "--no-console" -msgstr "--no-console" - -#: ../C/gdm.xml:5707(para) -msgid "Tell the daemon that it should not run anything on the console. This means that none of the local servers from the <filename>[servers]</filename> section will be run, and the console will not be used for communicating errors to the user. An empty <filename>[servers]</filename> section automatically implies this option." -msgstr "" - -#: ../C/gdm.xml:5719(term) -msgid "--config=CONFIGFILE" -msgstr "--config=<설정파일>" - -#: ../C/gdm.xml:5721(para) -msgid "Specify an alternative configuration file." -msgstr "" - -#: ../C/gdm.xml:5728(term) -msgid "--preserve-ld-vars" -msgstr "--preserve-ld-vars" - -#: ../C/gdm.xml:5730(para) -msgid "When clearing the environment internally, preserve all variables starting with LD_. This is mostly for debugging purposes." -msgstr "" - -#: ../C/gdm.xml:5738(term) -msgid "--version" -msgstr "--version" - -#: ../C/gdm.xml:5740(para) -msgid "Print the version of the GDM daemon." -msgstr "" - -#: ../C/gdm.xml:5747(term) -msgid "--wait-for-go" -msgstr "--wait-for-go" - -#: ../C/gdm.xml:5749(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:5767(title) -msgid "<command>gdmsetup</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5769(para) -msgid "<command>gdmsetup</command> 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 <command>gdmsetup</command> 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:5781(title) -msgid "<command>gdm-restart</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5783(para) -msgid "<command>gdm-restart</command> stops and restarts GDM by sending the GDM daemon a HUP signal. This command will immediately terminate all sessions and log out users currently logged in with GDM." -msgstr "" - -#: ../C/gdm.xml:5791(title) -msgid "<command>gdm-safe-restart</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5793(para) -msgid "<command>gdm-safe-restart</command> stops and restarts GDM by sending the GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out." -msgstr "" - -#: ../C/gdm.xml:5801(title) -msgid "<command>gdm-stop</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5803(para) -msgid "<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM signal." -msgstr "" - -#: ../C/gdm.xml:5811(title) -msgid "GDM Internal Commands" -msgstr "" - -#: ../C/gdm.xml:5813(para) -msgid "The GDM package provides the following different commands in <filename>libexecdir</filename> intended to be used by the gdm daemon process." -msgstr "" - -#: ../C/gdm.xml:5820(title) -msgid "<command>gdmchooser</command> and <command>gdmlogin</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5823(para) -msgid "The <command>gdmgreeter</command> and <command>gdmlogin</command> are two different login applications, either can be used by GDM. <command>gdmgreeter</command> is themeable with GDM themes while <command>gdmlogin</command> is themable with GTK+ themes. These applications are normally executed by the GDM daemon. Both commands support standard GNOME options." -msgstr "" - -#: ../C/gdm.xml:5834(title) ../C/gdm.xml:5845(title) -msgid "<command>gdmchooser</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5836(para) -msgid "The <command>gdmchooser</command> is the XDMCP chooser application. The <command>gdmchooser</command> is normally executed by the GDM daemon. It supports the following options for XDM compatibility. This command supports standard GNOME options and is found in support standard GNOME options." -msgstr "" - -#: ../C/gdm.xml:5848(term) -msgid "--xdmaddress=SOCKET" -msgstr "--xdmaddress=<소켓>" - -#: ../C/gdm.xml:5850(para) -msgid "Socket for XDM communication." -msgstr "" - -#: ../C/gdm.xml:5857(term) -msgid "--clientaddress=ADDRESS" -msgstr "--clientaddress=<주소>" - -#: ../C/gdm.xml:5859(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:5867(term) -msgid "--connectionType=TYPE" -msgstr "--connectionType=<종류>" - -#: ../C/gdm.xml:5869(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:5879(command) -msgid "gdm-ssh-session" -msgstr "gdm-ssh-session" - -#: ../C/gdm.xml:5881(para) -msgid "The <command>gdm-ssh-session</command> 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:5893(title) -msgid "Themed Greeter" -msgstr "테마 환영 프로그램" - -#: ../C/gdm.xml:5895(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 <ulink type=\"http\" url=\"http://art.gnome.org/themes/gdm_greeter/\"> the theme website</ulink>." -msgstr "" - -#: ../C/gdm.xml:5904(title) -msgid "Theme Overview" -msgstr "" - -#: ../C/gdm.xml:5906(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 <filename><share>/gdm/themes/<theme_name></filename>. Usually this would be under <filename>/usr/share</filename>. The theme directory should contain a file called <filename>GdmGreeterTheme.desktop</filename> which has similar format to other .desktop files and looks like:" -msgstr "" - -#: ../C/gdm.xml:5917(screen) -#, no-wrap -msgid "\n[GdmGreeterTheme]\nEncoding=UTF-8\nGreeter=circles.xml\nName=Circles\nDescription=Theme with blue circles\nAuthor=Bond, James Bond\nCopyright=(c) 2002 Bond, James Bond\nScreenshot=screenshot.png\n" -msgstr "" - -#: ../C/gdm.xml:5928(para) -msgid "The Name, Description, Author and Copyright fields can be translated just like the other <filename>.desktop</filename>files. 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:5938(para) -msgid "Once you have theme ready and installed you can test it with the installed <command>gdmthemetester</command> 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:5954(command) -msgid "gdmthemetester xdmcp circles" -msgstr "" - -#: ../C/gdm.xml:5957(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:5965(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 <filename><share>/gdm/themes</filename> directory). And this is the tarball you distribute and people can install from the graphical configuration application. You can do this with the commands: <screen>\ncd <share>/gdm/themes\ntar czvf <theme_name>.tar.gz <theme_name>/\n</screen>" -msgstr "" - -#: ../C/gdm.xml:5979(title) -msgid "Detailed Description of Theme XML format" -msgstr "테마 XML 형식의 자세한 설명" - -#: ../C/gdm.xml:5982(title) -msgid "greeter tag" -msgstr "" - -#: ../C/gdm.xml:5984(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:5991(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:5999(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:6009(title) -msgid "Box Nodes" -msgstr "" - -#: ../C/gdm.xml:6011(para) -msgid "Box nodes are container nodes for item nodes. Box nodes are specified as follows: <screen>\n<box orientation=\"alignment\" min-width=\"num\"\nxpadding=\"num\" ypadding=\"num\" spacing=\"num\"\nhomogeneous=\"bool\">\n</screen> 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:6027(para) -msgid "If the box is homogeneous then the children are allocated equal amount of space." -msgstr "" - -#: ../C/gdm.xml:6032(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:6040(title) -msgid "Fixed Nodes" -msgstr "" - -#: ../C/gdm.xml:6042(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: <screen>\n<fixed>\n</screen> Then you put other items with proper position nodes inside this." -msgstr "" - -#: ../C/gdm.xml:6053(para) -msgid "The \"toplevel\" node is really just like a fixed node." -msgstr "" - -#: ../C/gdm.xml:6059(title) -msgid "Item Nodes" -msgstr "" - -#: ../C/gdm.xml:6061(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:6069(term) -msgid "button" -msgstr "" - -#: ../C/gdm.xml:6071(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:6083(term) -msgid "entry" -msgstr "" - -#: ../C/gdm.xml:6085(para) -msgid "Text entry field." -msgstr "" - -#: ../C/gdm.xml:6092(term) -msgid "label" -msgstr "" - -#: ../C/gdm.xml:6094(para) -msgid "A text label. Must have a \"text\" node to specify the text." -msgstr "" - -#: ../C/gdm.xml:6102(term) -msgid "list" -msgstr "" - -#: ../C/gdm.xml:6104(para) -msgid "A face browser widget. Only useful if the face browser is enabled via the configuration." -msgstr "" - -#: ../C/gdm.xml:6112(term) -msgid "pixmap" -msgstr "" - -#: ../C/gdm.xml:6114(para) -msgid "An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, etc...)" -msgstr "" - -#: ../C/gdm.xml:6122(term) -msgid "rect" -msgstr "" - -#: ../C/gdm.xml:6124(para) -msgid "Rectangle." -msgstr "" - -#: ../C/gdm.xml:6131(term) -msgid "svg" -msgstr "" - -#: ../C/gdm.xml:6133(para) -msgid "Scaled Vector Graphic image." -msgstr "" - -#: ../C/gdm.xml:6140(para) -msgid "For example: <screen>\n<item type=\"label\">\n</screen> 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:6151(para) -msgid "Entry items can have id values as follows:" -msgstr "" - -#: ../C/gdm.xml:6157(term) -msgid "user-pw-entry" -msgstr "" - -#: ../C/gdm.xml:6159(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:6168(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:6178(term) -msgid "session" -msgstr "" - -#: ../C/gdm.xml:6180(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:6190(term) -msgid "language" -msgstr "" - -#: ../C/gdm.xml:6192(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:6202(term) -msgid "userlist" -msgstr "" - -#: ../C/gdm.xml:6204(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:6217(term) -msgid "userlist-rect" -msgstr "" - -#: ../C/gdm.xml:6219(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:6231(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:6238(para) -msgid "Label items can have id values as follows:" -msgstr "" - -#: ../C/gdm.xml:6244(term) -msgid "clock" -msgstr "" - -#: ../C/gdm.xml:6246(para) -msgid "Label that displays the date and time." -msgstr "" - -#: ../C/gdm.xml:6253(term) -msgid "pam-prompt" -msgstr "" - -#: ../C/gdm.xml:6255(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:6263(term) -msgid "pam-error" -msgstr "" - -#: ../C/gdm.xml:6265(para) -msgid "Label that displayst PAM/GDM error messages. Such as when user can't log in." -msgstr "" - -#: ../C/gdm.xml:6273(term) -msgid "pam-error-logo" -msgstr "" - -#: ../C/gdm.xml:6275(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:6285(term) -msgid "pam-message" -msgstr "" - -#: ../C/gdm.xml:6287(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:6296(term) -msgid "timed-label" -msgstr "" - -#: ../C/gdm.xml:6298(para) -msgid "Label that displays timed login information." -msgstr "" - -#: ../C/gdm.xml:6305(para) -msgid "Rectangles can have id values as follows:" -msgstr "" - -#: ../C/gdm.xml:6311(term) -msgid "caps-lock-warning" -msgstr "" - -#: ../C/gdm.xml:6313(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:6322(para) -msgid "If an item is of type rect, the item can be a button. Buttons must also include a \"button\" value as follows: <screen>\n<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6330(para) -msgid "Possible values for button ids are as follows." -msgstr "" - -#: ../C/gdm.xml:6336(term) -msgid "chooser_button" -msgstr "" - -#: ../C/gdm.xml:6338(para) -msgid "Runs the XDMCP chooser." -msgstr "" - -#: ../C/gdm.xml:6345(term) -msgid "config_button" -msgstr "" - -#: ../C/gdm.xml:6347(para) -msgid "Runs the GDM configuration application." -msgstr "" - -#: ../C/gdm.xml:6354(term) -msgid "custom_cmd_button[0-9]" -msgstr "" - -#: ../C/gdm.xml:6356(para) -msgid "Runs the <filename>n-th</filename> custom command." -msgstr "" - -#: ../C/gdm.xml:6363(term) -msgid "disconnect_button" -msgstr "" - -#: ../C/gdm.xml:6365(para) -msgid "Disconnect from remote session." -msgstr "" - -#: ../C/gdm.xml:6372(term) -msgid "language_button" -msgstr "" - -#: ../C/gdm.xml:6374(para) -msgid "Displays the language selection dialog." -msgstr "" - -#: ../C/gdm.xml:6381(term) -msgid "halt_button" -msgstr "" - -#: ../C/gdm.xml:6383(para) -msgid "Halt (shuts down) the system." -msgstr "" - -#: ../C/gdm.xml:6390(term) -msgid "reboot_button" -msgstr "" - -#: ../C/gdm.xml:6392(para) -msgid "Restart the system." -msgstr "" - -#: ../C/gdm.xml:6399(term) -msgid "session_button" -msgstr "" - -#: ../C/gdm.xml:6401(para) -msgid "List and select from available sessions." -msgstr "" - -#: ../C/gdm.xml:6408(term) -msgid "suspend_button" -msgstr "" - -#: ../C/gdm.xml:6410(para) -msgid "Suspend the system." -msgstr "" - -#: ../C/gdm.xml:6417(term) -msgid "system_button" -msgstr "" - -#: ../C/gdm.xml:6419(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:6432(title) -msgid "Position Node" -msgstr "" - -#: ../C/gdm.xml:6434(para) -msgid "Each item can specify its position and size via the \"pos\" node. For example: <screen>\n<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6442(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:6448(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:6455(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: <screen>\n<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/>\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6466(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:6472(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:6478(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:6485(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: <screen>\n<item type=\"label\">\n<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6501(title) -msgid "Show Node" -msgstr "" - -#: ../C/gdm.xml:6503(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:6509(para) -msgid "<filename>console</filename> - In console mode." -msgstr "" - -#: ../C/gdm.xml:6512(para) -msgid "<filename>console-fixed</filename> - In console non-flexi mode." -msgstr "" - -#: ../C/gdm.xml:6515(para) -msgid "<filename>console-flexi</filename> - In console & flexi mode." -msgstr "" - -#: ../C/gdm.xml:6518(para) -msgid "<filename>flexi</filename> - In flexi mode." -msgstr "" - -#: ../C/gdm.xml:6521(para) -msgid "<filename>remote</filename> - In remote mode." -msgstr "" - -#: ../C/gdm.xml:6524(para) -msgid "<filename>remote-flexi</filename> - In remote & flexi mode." -msgstr "" - -#: ../C/gdm.xml:6528(para) -msgid "For example: <screen>\n<show modes=\"flexi,remote\"/>\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6535(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:6541(para) -msgid "<filename>chooser</filename>, if ChooserButton is set to \"true\" in the GDM configuration." -msgstr "" - -#: ../C/gdm.xml:6545(para) -msgid "<filename>config</filename>, if ConfigAvailable is set to \"true\" in the GDM configuration." -msgstr "" - -#: ../C/gdm.xml:6549(para) -msgid "<filename>custom_cmd[0-9]</filename>, if <filename>n-th</filename> CustomCommand is specified in the GDM configuration." -msgstr "" - -#: ../C/gdm.xml:6553(para) -msgid "<filename>halt</filename>, if HaltDaemon is specified in the GDM configuration." -msgstr "" - -#: ../C/gdm.xml:6557(para) -msgid "<filename>reboot</filename>, if RebootCommand is specified in the GDM configuration." -msgstr "" - -#: ../C/gdm.xml:6561(para) -msgid "<filename>suspend</filename>, if SuspendCommand is specified in the GDM configuration." -msgstr "" - -#: ../C/gdm.xml:6565(para) -msgid "<filename>system</filename>, if SystemMenu is specified in the GDM configuration." -msgstr "" - -#: ../C/gdm.xml:6569(para) -msgid "<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in the GDM configuration." -msgstr "" - -#: ../C/gdm.xml:6574(para) -msgid "For example: <screen>\n<show modes=\"console\" type=\"system\"/>\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6581(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:6588(para) -msgid "For example: <screen>\n<show min-screen-height=\"768\"/>\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6595(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:6604(title) -msgid "Normal/Active/Prelight Nodes" -msgstr "" - -#: ../C/gdm.xml:6606(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:6612(para) -msgid "<filename>normal</filename> - normal state." -msgstr "" - -#: ../C/gdm.xml:6615(para) -msgid "<filename>active</filename> - when the item has active focus." -msgstr "" - -#: ../C/gdm.xml:6618(para) -msgid "<filename>prelight</filename> - when the mouse is hovering over the item." -msgstr "" - -#: ../C/gdm.xml:6623(para) -msgid "When item is \"rect\" (alpha can be omitted and defaults to 0.0): <screen>\n<normal color=\"#ffffff\" alpha=\"0.0\">\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6631(para) -msgid "When item is \"label\" <screen>\n<normal color=\"#ffffff\" font=\"Sans 14\"/>\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6638(para) -msgid "When the item type is \"pixmap\" or \"SVG\", then the normal, active, and prelight tags specify the images to use as follows: <screen>\n<normal file=\"picture.png\" tint=\"#dddddd\"/>\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6647(para) -msgid "Note that relative pathnames are assumed to be in the same directory as the theme <filename>.xml</filename> file in <filename><share>/gdm/themes/<theme_name></filename>." -msgstr "" - -#: ../C/gdm.xml:6653(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: <screen>\n<normal file=\"picture.png\" altfile1=\"distribution-blah-image.png\" altfile2=\"distribution-foo-image.png\"/>\n</screen> If <filename>distribution-foo-image.png</filename> 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:6668(title) -msgid "Face Browser Icon/Label Color Nodes" -msgstr "" - -#: ../C/gdm.xml:6670(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:6676(screen) -#, no-wrap -msgid "\n<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" -msgstr "" - -#: ../C/gdm.xml:6683(title) -msgid "Text Node" -msgstr "" - -#: ../C/gdm.xml:6685(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): <screen>\n<text xml:lang=\"fr\">Option</text>\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6694(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: <screen>\n<text>\"foo<sup>bar</sup>\"</text>\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6703(para) -msgid "Text nodes can contain the following special character sequences which will be translated as follows:" -msgstr "" - -#: ../C/gdm.xml:6708(para) -msgid "%% - A literal % character" -msgstr "" - -#: ../C/gdm.xml:6711(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:6716(para) -msgid "%d - Display name (DISPLAY environment variable)" -msgstr "" - -#: ../C/gdm.xml:6719(para) -msgid "%h - Hostname (gethostname output)" -msgstr "" - -#: ../C/gdm.xml:6722(para) -msgid "%m - Machine name (uname.machine output)" -msgstr "" - -#: ../C/gdm.xml:6725(para) -msgid "%n - Node name (uname.nodename output)" -msgstr "" - -#: ../C/gdm.xml:6728(para) -msgid "%o - Domain name (getdomainname output)" -msgstr "" - -#: ../C/gdm.xml:6731(para) -msgid "%r - Release name (uname.release output)" -msgstr "" - -#: ../C/gdm.xml:6734(para) -msgid "%s - System name (uname.sysname output)" -msgstr "" - -#: ../C/gdm.xml:6737(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:6745(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:6751(para) -msgid "\\n - Carriage return" -msgstr "" - -#: ../C/gdm.xml:6754(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:6762(title) -msgid "Stock" -msgstr "" - -#: ../C/gdm.xml:6764(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:6773(para) -msgid "<filename>cancel</filename>, _(\"_Cancel\"" -msgstr "" - -#: ../C/gdm.xml:6776(para) -msgid "<filename>caps-lock-warning</filename>, _(\"Caps Lock key is on.\"" -msgstr "" - -#: ../C/gdm.xml:6780(para) -msgid "<filename>chooser</filename>, _(\"Remote Login via _XDMCP\"" -msgstr "" - -#: ../C/gdm.xml:6783(para) -msgid "<filename>config</filename>, _(\"_Configure\"" -msgstr "" - -#: ../C/gdm.xml:6786(para) -msgid "<filename>custom_cmd[0-9]</filename>, _(\"Custom_[0-9]\"" -msgstr "" - -#: ../C/gdm.xml:6789(para) -msgid "<filename>disconnect</filename>, _(\"D_isconnect\"" -msgstr "" - -#: ../C/gdm.xml:6792(para) -msgid "<filename>halt</filename>, _(\"Shut _Down\"" -msgstr "" - -#: ../C/gdm.xml:6795(para) -msgid "<filename>language</filename>, _(\"_Language\"" -msgstr "" - -#: ../C/gdm.xml:6798(para) -msgid "<filename>ok</filename>, _(\"_OK\"" -msgstr "" - -#: ../C/gdm.xml:6801(para) -msgid "<filename>quit</filename>, _(\"_Quit\"" -msgstr "" - -#: ../C/gdm.xml:6804(para) -msgid "<filename>reboot</filename>, _(\"_Restart\"" -msgstr "" - -#: ../C/gdm.xml:6807(para) -msgid "<filename>session</filename>, _(\"_Session\"" -msgstr "" - -#: ../C/gdm.xml:6810(para) -msgid "<filename>startover</filename>, _(\"_Start Over\"" -msgstr "" - -#: ../C/gdm.xml:6813(para) -msgid "<filename>suspend</filename>, _(\"Sus_pend\"" -msgstr "" - -#: ../C/gdm.xml:6816(para) -msgid "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\"" -msgstr "" - -#: ../C/gdm.xml:6820(para) -msgid "<filename>timed-label</filename>, _(\"User %u will login in %t\"" -msgstr "" - -#: ../C/gdm.xml:6824(para) -msgid "<filename>username-label</filename>, _(\"Username:\"" -msgstr "" - -#: ../C/gdm.xml:6827(para) -msgid "<filename>welcome-label</filename>, _(\"Welcome to %n\"" -msgstr "" - -#: ../C/gdm.xml:6831(para) -msgid "For example: <screen>\n<stock type=\"welcome-label\">\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6840(title) -msgid "Custom Widgetry" -msgstr "" - -#: ../C/gdm.xml:6842(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 <filename><ServAuthDir>/<display>.GreeterInfo</filename> as <filename><list id>=<listitem id></filename>." -msgstr "" - -#: ../C/gdm.xml:6853(para) -msgid "For example suppose we are on display :0, <filename>ServAuthDir</filename> is <filename><var>/lib/gdm</filename> and we have the following in the theme:" -msgstr "" - -#: ../C/gdm.xml:6860(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:6872(para) -msgid "Then if the user chooses 'Foo' then <filename><var>/lib/gdm/:0.GreeterInfo</filename> will contain: <screen>\ncustom-config=foo\n</screen>" -msgstr "" - -#: ../C/gdm.xml:6884(title) -msgid "Accessibility" -msgstr "접근성 기능" - -#: ../C/gdm.xml:6885(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 <command>GOK</command> (on-screen keyboard) and <command>orca</command> (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 <command>GOK</command>, do not yet work with the \"Themed Greeter\"." -msgstr "" - -#: ../C/gdm.xml:6898(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 <filename>Greeter</filename> and <filename>RemoteGreeter</filename> configuration options by hand to be <command>/usr/lib/gdmlogin</command>." -msgstr "" - -#: ../C/gdm.xml:6907(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:6916(para) -msgid "Note that <command>gdmsetup</command> 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:6923(title) -msgid "Accessibility Configuration" -msgstr "" - -#: ../C/gdm.xml:6925(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 <command>GOK</command> and <command>orca</command>, 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:6941(title) -msgid "Accessibile Theming" -msgstr "" - -#: ../C/gdm.xml:6943(para) -msgid "If using the \"GTK+ Greeter\" users can easily switch the color and contrast scheme of the dialog. To do this, ensure the <filename>AllowGtkThemeChange</filename> 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 <filename>GtkThemesToAllow</filename> configuration choice can also be used to limit the choices available as desired. For example:" -msgstr "" - -#: ../C/gdm.xml:6955(screen) -#, no-wrap -msgid "\nGtkThemesToAllow=HighContrast,HighContrastInverse\n" -msgstr "" - -#: ../C/gdm.xml:6959(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:6971(title) -msgid "AT Program Support" -msgstr "" - -#: ../C/gdm.xml:6973(para) -msgid "To enable user to launch AT such as the <command>GOK</command> or <command>orca</command>, the <filename>AddGtkModules</filename> parameter in the GDM configuration must be set to \"true\". Also the <filename>GtkModulesList</filename> parameter must be uncommented and set as follows:" -msgstr "" - -#: ../C/gdm.xml:6982(screen) -#, no-wrap -msgid "\nGtkModulesList=gail:atk-bridge:/usr/lib/gtk-2.0/modules/libdwellmouselistener:/usr/lib/gtk-2.0/modules/libkeymouselistener\n" -msgstr "" - -#: ../C/gdm.xml:6986(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, <command>at-spi-registryd</command>, to be running. This is handled by the GDM GUI starting with version 2.17." -msgstr "" - -#: ../C/gdm.xml:6994(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:7009(para) -msgid "Once \"keymouselistener\" and/or \"dwellmouselistener\" have been added to the <filename>AddGtkModules</filename> loaded by GDM, then you may need to modiify the gesture configurations to meet your user's needs. Default gestures are provided for launching <command>GOK</command> and <command>orca</command>, but it is recommended to modify these gestures so they work best for your user base. These gesture associations are contained in files <filename>AccessKeyMouseEvents</filename> and <filename>AccessDwellMouseEvents</filename>, respectively. Both files are located in the <filename><etc>/gdm/modules</filename> directory. The gesture configuration format is described in the comment section of the two configuration files." -msgstr "" - -#: ../C/gdm.xml:7026(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:7040(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:7056(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:7063(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:7076(title) -msgid "AT Troubleshooting" -msgstr "" - -#: ../C/gdm.xml:7078(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:7084(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:7093(para) -msgid "Some versions of <command>GOK</command> and <command>orca</command> 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:7102(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:7110(para) -msgid "Also note that some input devices require X server configuration before GDM will recognize them." -msgstr "" - -#: ../C/gdm.xml:7117(title) -msgid "Accessibility Login Sound Configuration" -msgstr "" - -#: ../C/gdm.xml:7119(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 <filename><bin>/play</filename> (or <filename><bin>/audioplay</filename> on Solaris. This can be changed via the <filename>SoundProgram</filename> GDM configuration option. Typically most text-to-speech programs (such as <command>orca</command>) use a separate mechanism to play audio, so this configuration setting is not needed for them to work." -msgstr "" - -#: ../C/gdm.xml:7137(title) -msgid "Solaris Specific Features" -msgstr "솔라리스 전용 기능" - -#: ../C/gdm.xml:7140(title) -msgid "Using GDM on Solaris" -msgstr "솔라리스에서 GDM 사용하기" - -#: ../C/gdm.xml:7142(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:7155(screen) -#, no-wrap -msgid "\nsvcs cde-login\n" -msgstr "" - -#: ../C/gdm.xml:7159(para) -msgid "If the <command>svcs</command> command responds that this service is enabled, then run this command to disable CDE login:" -msgstr "" - -#: ../C/gdm.xml:7164(screen) -#, no-wrap -msgid "\nsvcadm disable cde-login\n" -msgstr "" - -#: ../C/gdm.xml:7168(para) -msgid "If the <command>svcs</command> command responds that this pattern doesn't match any instances, then run these commands to stop CDE login:" -msgstr "" - -#: ../C/gdm.xml:7174(screen) -#, no-wrap -msgid "\n/usr/dt/config/dtconfig -d\nEither reboot, or kill any running dtlogin processes.\n" -msgstr "" - -#: ../C/gdm.xml:7179(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:7186(screen) -#, no-wrap -msgid "\nsvcadm enable servicename\n" -msgstr "" - -#: ../C/gdm.xml:7192(title) -msgid "Solaris Configuration" -msgstr "솔라리스 설정" - -#: ../C/gdm.xml:7193(para) -msgid "On Solaris, the following configuration is recommended. This turns on IPv6 and also turns on PreFetch for performance benefit. <screen>\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</screen>" -msgstr "" - -#: ../C/gdm.xml:7206(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:7214(title) -msgid "Solaris /etc/logindevperm" -msgstr "솔라리스 /etc/logindevperm" - -#: ../C/gdm.xml:7215(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:7221(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:7228(screen) -#, no-wrap -msgid "\n/dev/console 0600 /dev/sound/* # audio devices\n" -msgstr "" - -#: ../C/gdm.xml:7232(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:7245(title) -msgid "Solaris Automatic Login" -msgstr "솔라리스 자동 로그인" - -#: ../C/gdm.xml:7246(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:7257(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:7264(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:7272(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:7280(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:7285(screen) -#, no-wrap -msgid "\n gdm-autologin session required pam_unix_session.so.1\n" -msgstr "" - -#: ../C/gdm.xml:7291(title) -msgid "Other Solaris Features" -msgstr "기타 솔라리스 기능" - -#: ../C/gdm.xml:7292(para) -msgid "GDM supports a few features specific to Solaris, as follows:" -msgstr "" - -#: ../C/gdm.xml:7296(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:7302(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:7311(para) -msgid "Solaris supports the <filename>/etc/default/login</filename> interface, which affects the <filename>DefaultPath</filename>, <filename>RootPath</filename>, <filename>PasswordRequired</filename>, and <filename>AllowRemoteRoot</filename> options as described in the \"Configuration\" section." -msgstr "" - -#: ../C/gdm.xml:7323(title) -msgid "Example Configurations" -msgstr "설정 예" - -#: ../C/gdm.xml:7325(para) -msgid "This section has some example configurations that are useful for various setups." -msgstr "" - -#: ../C/gdm.xml:7331(title) -msgid "Terminal Lab With One Server" -msgstr "" - -#: ../C/gdm.xml:7333(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 <filename>xterminal</filename> and let's call the server machine <filename>appserver</filename>. You install GDM on both." -msgstr "" - -#: ../C/gdm.xml:7340(para) -msgid "On <filename>appserver</filename> you enable XDMCP, so you have <screen>\n[xdmcp]\nEnable=true\n</screen> If you want no local screens here, you can then make the <filename>[servers]</filename> section empty." -msgstr "" - -#: ../C/gdm.xml:7350(para) -msgid "On the <filename>xterminal</filename> you disable XDMCP (you don't want anyone to connect to the xterminal really). You will add a server type perhaps called <filename>Terminal</filename> as follows: <screen>\n[server-Terminal]\nname=Terminal server\ncommand=/path/to/X -terminate\nflexible=false\nhandled=false\n</screen> This definition should in fact be included in the standard configuration file. Notice that we made the <filename>handled</filename> key false since we don't want GDM to handle this server localy. Also note that we have not yet added the <filename>-query</filename> argument, you can add that here, or in the <filename>[servers]</filename> section. We'll define our local servers as follows: <screen>\n[servers]\n0=Terminal -query appserver\n</screen> This will run a direct XDMCP query to the server named <filename>appserver</filename>." -msgstr "" - -#: ../C/gdm.xml:7378(title) -msgid "Terminal Lab With Two Or More Servers" -msgstr "" - -#: ../C/gdm.xml:7380(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 <filename>appserverone</filename> and <filename>appservertwo</filename>. Again we'll call our example X terminal server <filename>xterminal</filename>. 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:7391(para) -msgid "So on the <filename>xterminal</filename> you again disable XDMCP. You will add a server type perhaps called <filename>Chooser</filename> as follows: <screen>\n[server-Chooser]\nname=Chooser server\ncommand=/path/to/X\nflexible=false\nchooser=true\n</screen> And again this definition should in fact be included in the standard configuration file. Notice that we made the <filename>chooser</filename> 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: <screen>\n[servers]\n0=Chooser\n</screen>" -msgstr "" - -#: ../C/gdm.xml:7414(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 <filename>[chooser]</filename> section you would have: <screen>\nHosts=appserverone,appservertwo\n</screen> and any other servers you wish the users to be able to connect to." -msgstr "" - -#: ../C/gdm.xml:7426(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 <filename>appserver</filename> and on the X terminals you'd have <screen>\n[servers]\n0=Terminal -indirect appserver\n</screen> This way for example you only have to maintain one <filename>Hosts</filename> entry. However as a disadvantage then, the <filename>appserver</filename> 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:7447(title) -msgid "Defining Custom Commands" -msgstr "" - -#: ../C/gdm.xml:7449(para) -msgid "Suppose you want to add a custom command to the GDM menu that will give you the oportunity to boot into other operating system such as Windoze. Jsut add the following options into the <filename>[customcommand]</filename> section of the GDM configuration file. <screen>\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 </screen> CustomCommand0 specifies two commands separated by a semicolon: <filename>/sbin/rebootwindoze</filename> and <filename>/usr/local/sbin/rebootwindoze</filename>. 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:7472(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 oportunity to run system update scripts from the login screen. Add the following options into the <filename>[customcommand]</filename> section of your GDM configuration file. <screen>\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 </screen>" -msgstr "" - -#: ../C/gdm.xml:7492(para) -msgid "Both custom commands could be defined as follows. <screen>\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 </screen>" -msgstr "" - -#: ../C/gdm.xml:7513(para) -msgid "There can be up to 10 custom commands numbered 0-9. <screen>\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 </screen>" -msgstr "" - -#: ../C/gdm.xml:7547(title) -msgid "Troubleshooting" -msgstr "문제 해결" - -#: ../C/gdm.xml:7549(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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink> or send an email to the <address><email>gdm-list@gnome.org</email></address> mail list." -msgstr "" - -#: ../C/gdm.xml:7559(para) -msgid "If GDM is failing to work properly, it is always a good idea to include debug information. Use the <command>gdmsetup</command> 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 (<filename><var>/log/messages</filename> or <filename><var>/adm/messages</filename> 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:7573(para) -msgid "You should not leave debug on after collecting data. It will clutter your syslog and slow system performance." -msgstr "" - -#: ../C/gdm.xml:7579(title) -#, fuzzy -msgid "GDM Will Not Start" -msgstr "GDM이 시작하지 않습니다" - -#: ../C/gdm.xml:7581(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:7590(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:7603(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 <command><lib>/gdmlogin</command> or <command><lib>/gdmgreeter</command>. 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:7616(para) -msgid "Also make sure that the <filename>/tmp</filename> directory has reasonable ownership and permissions, and that the machine's file system is not full. These problems will cause GDM to fail to start." -msgstr "" - -#: ../C/gdm.xml:7624(title) -msgid "GDM Will Not Access User Settings" -msgstr "" - -#: ../C/gdm.xml:7626(para) -msgid "GDM saves user settings, such as your default session and default language, in the <filename>~/.dmrc</filename>. Other files, such as the user's <filename>~/.Xauthority</filename> 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 <filename>RelaxPermissions</filename> 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:7645(title) -msgid "License" -msgstr "" - -#: ../C/gdm.xml:7646(para) -msgid "This program is free software; you can redistribute it and/or modify it under the terms of the <ulink type=\"help\" url=\"gnome-help:gpl\"><citetitle>GNU General Public License</citetitle></ulink> as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version." -msgstr "" - -#: ../C/gdm.xml:7654(para) -msgid "This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public License</citetitle> for more details." -msgstr "" - -#: ../C/gdm.xml:7660(para) -msgid "A copy of the <citetitle>GNU General Public License</citetitle> is included as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also obtain a copy of the <citetitle>GNU General Public License</citetitle> from the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://www.fsf.org\">their Web site</ulink> or by writing to <address> Free Software Foundation, Inc. <street>59 Temple Place</street> - Suite 330 <city>Boston</city>, <state>MA</state><postcode>02111-1307</postcode><country>USA</country></address>" -msgstr "" - -#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2. -#: ../C/gdm.xml:0(None) -msgid "translator-credits" -msgstr "" -"Sun Microsystems, 2003, 2004.\n" -"류창우 <cwryu@debian.org>, 2007." - diff --git a/docs/oc/oc.po b/docs/oc/oc.po deleted file mode 100644 index f6e0f88d..00000000 --- a/docs/oc/oc.po +++ /dev/null @@ -1,8640 +0,0 @@ -# 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) <yannig@marchegay.org>\n" -"Language-Team: Occitan (post 1500) <ubuntu-l10n-oci@lists.ubuntu.com>\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 <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> 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: " -"<placeholder-1/>" -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 (<command>gdmchooser</command>)." -msgstr "" - -#: ../C/gdm.xml:90(para) -msgid "Configurator - The configuration application (<command>gdmsetup</command>)." -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 (<command>gdm</command>)." -msgstr "" - -#: ../C/gdm.xml:104(para) -msgid "" -"Greeter - The graphical login window (<command>gdmlogin</command> or " -"<command>gdmgreeter</command>)." -msgstr "" - -#: ../C/gdm.xml:109(para) -msgid "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)." -msgstr "" - -#: ../C/gdm.xml:113(para) -msgid "PAM - Pluggable Authentication Mechanism" -msgstr "" - -#: ../C/gdm.xml:117(para) -msgid "Themed Greeter - The themable login window ( <command>gdmgreeter</command>)." -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. <filename><share>/pixmaps/</filename> refers " -"to <filename><share>/pixmaps</filename> if GDM was configured with " -"<command>--prefix=/usr</command>. Normally also note that GDM is installed " -"with <command>--sysconfigdir=<etc>/X11</command>, meaning any path to " -"which we refer to as <filename><etc>/gdm/PreSession</filename> usually " -"means <filename><etc/X11>/gdm/PreSession</filename>. Note that for " -"interoperability it is recommended that you use a --prefix of <filename>/" -"usr</filename> and a --sysconfdir of <filename><etc>/X11</filename>." -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 <ulink type=\"http\" url=\"http://" -"www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. Please " -"submit any bug reports or enhancement requests to the \"gdm\" category in " -"<ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</" -"ulink>. You can also send a message to the <address><email>gdm-list@gnome." -"org</email></address> 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 <filename><bin></" -"filename> and <filename><sbin></filename> 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 <command>gdmchooser</command>. 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 " -"<filename>Init</filename>, <filename>PostLogin</filename>, " -"<filename>PreSession</filename>, and <filename>PostSession</filename> " -"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 <command>gdmflexiserver</command> command. Displays " -"that are started on request are not restarted on session exit. GDM also " -"provides the <command>gdmdynamic</command> 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:248(para) -msgid "" -"When the GDM daemon is asked to manage a display, it will fork an X server " -"process, then run the <filename>Init</filename> script as the root user, and " -"start the login GUI dialog as a slave process on the display. GDM can be " -"configured to use either <command>gdmgreeter</command> (the default) or " -"<command>gdmlogin</command> as the GUI dialog program. The " -"<command>gdmlogin</command> program supports accessibility while the " -"<command>gdmgreeter</command> program supports greater themeability. The GUI " -"dialog is run as the unpriviledged \"gdm\" user/group which is described in " -"the \"Security\" section below. The GUI dialog communicates with the daemon " -"via a sockets protocol and via standard input/output. The slave, for example " -"passes the username and password information to the GDM daemon via standard " -"input/output so the daemon can handle the actual authentication." -msgstr "" - -#: ../C/gdm.xml: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:280(para) -msgid "" -"GDM, by default, will use Pluggable Authentication Modules (PAM) for " -"authentication, but can also support regular crypt and shadow passwords on " -"legacy systems. After authenticating a user, the daemon runs the " -"<filename>PostLogin</filename> script as root, and forks a slave process to " -"start the requested session. This slave process runs the " -"<filename>PreSession</filename> script as root, sets up the user's " -"environment, and starts the requested session. GDM keeps track of the user's " -"default session and language in the user's <filename>~/.dmrc</filename> and " -"will use these defaults if the user did not pick a session or language in " -"the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN " -"interface after user authentication to tell the X server to be restarted as " -"the user instead of as root for added security. When the user's session " -"exits, the GDM daemon will run the <filename>PostSession</filename> script " -"as root." -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 " -"<filename>PamStack</filename> 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 " -"<filename>daemon/verify-pam.c</filename> 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 <command>gdmflexiserver</" -"command> 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 <filename>FlexibleXServers</filename>, <filename>FirstVT=7</filename>, " -"<filename>VTAllocation</filename>, and <filename>FlexiReapDelayMinutes</" -"filename> 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 " -"<command>gdmflexiserver -n</command> 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 <filename>Xnest</filename> " -"configuration option is used to configure how nested displays operate" -msgstr "" - -#: ../C/gdm.xml:382(para) -msgid "" -"The <command>gdmdynamic</command> is similar to <command>gdmflexiserver</" -"command> in the sense that it allows the user to manage displays " -"dynamically. However displays started with <command>gdmdynamic</command> 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 <filename>/etc/hosts</filename>." -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. <command>gdmlogin</command> 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 " -"<filename>Logo</filename> 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 <filename>GraphicalTheme</" -"filename> 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 " -"<filename>Browser</filename> 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 <command>gdmsetup</command>. 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 <filename><share>/pixmaps/faces/</filename> directory (though " -"this can be configured with the <filename>GlobalFaceDir</filename> " -"configuration option) and the filename should be the name of the user, " -"optionally with a <filename>.png</filename> 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 <command>gdmphotosetup</command> command to configure the " -"image to use for their userid. This program properly scales the file down if " -"it is larger than the <filename>MaxIconWidth</filename> or " -"<filename>MaxIconHeight</filename> configuration options and places the icon " -"in a file called <filename>~/.face</filename>. Although " -"<command>gdmphotosetup</command> scales user images automatically, this does " -"not guarantee that user images are properly scaled since a user may create " -"their <filename>~/.face</filename> file by hand." -msgstr "" - -#: ../C/gdm.xml:597(para) -msgid "" -"GDM will first look for the user's face image in <filename>~/.face</" -"filename>. If not found, it will try <filename>~/.face.icon</filename>. If " -"still not found, it will use the value defined for \"face/picture=\" in the " -"<filename>~/.gnome2/gdm</filename> file. Lastly, it will try <filename>~/." -"gnome2/photo</filename> and <filename>~/.gnome/photo</filename> 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 <filename>DefaultFace</filename> " -"configuration option, normally <filename><share>/pixmaps/nobody.png</" -"filename>." -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 <filename>Include</filename> 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 <filename>GlobalFaceDir</filename> 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 " -"<filename>IncludeAll</filename> option is set to true, then the password " -"file will be scanned and all users will be displayed. If " -"<filename>IncludeAll</filename> option is set to false, then the " -"<filename>Include</filename> option should contain a list of users separated " -"by commas. Only the users specified will be displayed. Any user listed in " -"the <filename>Exclude</filename> option and users whose UID's is lower than " -"<filename>MinimalUID</filename> will be filtered out regardless of the " -"<filename>IncludeAll</filename> setting. <filename>IncludeAll</filename> 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 <filename><var>/log/gdm/</filename>. " -"The output from the session can be found in a file called <filename><" -"display>.log</filename>. Four older files are also stored with " -"<filename>.1</filename> through <filename>.4</filename> 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 <filename>~/.xsession-" -"errors</filename> before even the <filename>PreSession</filename> 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 " -"<filename>Xsession</filename>script or from your session binary (the default " -"<filename>Xsession</filename> 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 <filename>~/." -"xsession-errors</filename> 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 <filename>~/.xsession-" -"errors</filename> redirection and do it themselves in their own Xsession " -"script (set by the <filename>BaseXsession</filename> configuration key) " -"which means that GDM will not be able to trap the output and cap this file. " -"You also lose output from the <filename>PreSession</filename> 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 " -"<filename>BaseXsession</filename> 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 <filename>/" -"tmp</filename> directory named <filename>/tmp/xses-<user>.XXXXXX</" -"filename> where the <filename>XXXXXX</filename> 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 " -"<filename>~/.xsession-errors</filename> in the <filename>PostSession</" -"filename> 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 <filename>~/.dmrc</filename>, <filename>~/.face</filename>, " -"<filename>~/.xsession-errors</filename>, and <filename>~/.Xauthority</" -"filename> files). For instance it refuses to access anything but regular " -"files. Links, sockets and devices are ignored. The value of the " -"<filename>RelaxPermissions</filename> 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 <filename>.Xauthority</" -"filename> file, a fallback cookie is created in the directory specified by " -"the <filename>UserAuthFBDir</filename> configuration setting (<filename>/" -"tmp</filename> 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 <command>--with-prefetch</" -"command> option. This will cause GDM to install the <command>gdmprefetch</" -"command> program to the <filename>libexecdir</filename> directory, install " -"the <filename>gdmprefetchlist</filename> to the <filename><etc>/gdm</" -"filename> directory, and set the <filename>PreFetchProgram</filename> " -"configuration variable so that the <command>gdmprefetch</command> program is " -"called with the default <filename>gdmprefetchlist</filename> file. The " -"default <filename>gdmprefetchlist</filename> 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 " -"<ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</" -"ulink>, 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 <address><email>gdm-list@gnome.org</email></" -"address> mail list, so you can refer to the list archives for more " -"information." -msgstr "" - -#: ../C/gdm.xml: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 " -"<filename>PamStack</filename> 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:879(para) -msgid "" -"The GDM daemon normally runs as root, as does the slave. However GDM should " -"also have a dedicated user id and a group id which it uses for its graphical " -"interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</" -"command>. These are configured via the <filename>User</filename> and " -"<filename>Group</filename> configuration options in the GDM configuration " -"files. The user and group should be created before running \"make install\". " -"By default GDM assumes the user and the group are called \"gdm\"." -msgstr "" - -#: ../C/gdm.xml: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 " -"<filename><var>/lib/gdm</filename>. 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 " -"<filename>nobody</filename>. 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 <filename>ServAuthDir</filename>) " -"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 <filename>root.gdm</filename> 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 <filename>/dev/audio</" -"filename> or <filename>/dev/mem</filename> 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 <filename>UserAuthDir</" -"filename> 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 (<filename>~/.Xauthority</" -"filename>), 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 " -"<filename>UserAuthFBDir</filename>, which by default is set to <filename>/" -"tmp</filename>. This behavior can be changed by setting the " -"<filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</" -"filename> 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 <command>gdm</command> in the <filename><" -"etc>/hosts.allow</filename> and <filename><etc>/hosts.deny</" -"filename> files. For example to deny computers from <filename>.evil.domain</" -"filename> 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 <filename><etc>/hosts.deny</filename>. 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 <filename><etc>/hosts.allow</filename> if you normally " -"disallow all services from all hosts. See the <ulink type=\"help\" url=\"man:" -"hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" - -#: ../C/gdm.xml:1092(title) -msgid "RBAC (Role Based Access Control)" -msgstr "" - -#: ../C/gdm.xml:1094(para) -msgid "" -"If GDM is compiled with RBAC support, then the " -"<filename>RBACSystemCommandKeys</filename> 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 " -"<command>gdmflexiserver</command> 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 <filename>User</filename> " -"configuration option) has permission via RBAC. Users will only be able to " -"use the <command>gdmflexiserver</command> 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 <command>gdmsetup</command> 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 <command>gdmsetup</" -"command>. Editing the files by hand is explained in the \"Configuration\" " -"section of this document. Note that <command>gdmsetup</command> 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 <command>gdmsetup</command> 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 " -"<command>gdmlogin</command> program as the GUI (daemon/Greeter). When this " -"choice is selected, <command>gdmsetup</command> 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 " -"<command>gdmlogin</command> 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 <command>gdmgreeter</" -"command> program is used as the GUI (daemon/Greeter). When this choice is " -"selected, <command>gdmsetup</command> 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 " -"<command>gdmgreeter</command> 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 <command>gdmsetup</command> (greeter/" -"ConfigAvailable), and whether the Action menu includes the choice to start " -"<command>gdmchooser</command> to run a remote XDMCP login session (greeter/" -"ChooserButton). Note that the root password must be entered to start " -"<command>gdmsetup</command> 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 <command>gdmsetup</command> 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 <filename><etc>/" -"gdm/</filename> 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 "" -"<filename>locale.alias</filename> 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 "" -"<filename>Xsession</filename> 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 <filename>desktop</filename> file associated with " -"the session the user has picked. Some sessions may start the user's session " -"via a different mechanism than the <filename>Xsession</filename> script, so " -"please check the appropriate <filename>desktop</filename> before assuming a " -"session startup issue is being caused by this file." -msgstr "" - -#: ../C/gdm.xml:1497(para) -msgid "" -"<filename>XKeepsCrashing</filename> 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 <filename>modules/</filename> " -"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 <filename>factory</filename> 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 <filename>.desktop</filename>-style files are " -"installed to <filename><etc>/X11/sessions/</filename>. This directory " -"is also read by the KDE desktop manager (KDM) for common configuration. Next " -"the directory <filename><share>/gdm/BuiltInSessions/</filename> is " -"read for GDM specific built-in sessions (KDM hardcodes these at time of this " -"writing). Lastly the default setup will also read <filename><share>/" -"xsessions/</filename> (which should be <filename><share>/xsessions/</" -"filename> if you really wish to cooperate with KDM) where desktop packages " -"can install their session files. The directories under the <filename><" -"etc></filename> 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 <filename>SessionDesktopDir</filename> " -"configuration key for changing the paths. It used to be that GDM stored its " -"built in sessions in <filename><etc>/dm/Sessions/</filename> but this " -"is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the " -"<filename><etc>/dm/Sessions/</filename> was being read." -msgstr "" - -#: ../C/gdm.xml:1537(para) -msgid "" -"A session can be disabled (if it was installed in <filename><share>/" -"xsessions/</filename>) by adding an identically named <filename>.desktop</" -"filename> to one of the directories earlier in the path (likely " -"<filename><etc>/X11/sessions</filename>) and using " -"<filename>Hidden=true</filename> in that file." -msgstr "" - -#: ../C/gdm.xml:1545(para) -msgid "" -"GDM uses the optional key <filename>X-Gdm-XserverArgs</filename> in session " -"files to specify additional arguments to be passed to the X server. For " -"example, the entry <filename>X-Gdm-XserverArgs=-depth 16</filename> 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 <filename>Init</filename>, " -"<filename>PostLogin</filename>, <filename>PreSession</filename> and " -"<filename>PostSession</filename> 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 <filename>Init/<displayname></filename>. I.e. " -"<filename>Init/:0</filename> for the first local display. If this file is " -"not found, GDM will attempt to to run <filename>Init/<hostname></" -"filename>. I.e. <filename>Init/somehost</filename>. If this still is not " -"found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins or " -"<filename>Init/Flexi</filename> for all on demand flexible displays. If none " -"of the above were found, GDM will run <filename>Init/Default</filename>. The " -"script will be run as root and GDM blocks until it terminates. Use the " -"<filename>Init/*</filename> 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 <filename>KillInitClients</filename> configuration option." -msgstr "" - -#: ../C/gdm.xml:1589(para) -msgid "" -"When the user has been successfully authenticated GDM tries the scripts in " -"the <filename>PostLogin</filename> directory in the same manner as for the " -"<filename>Init</filename> 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 <filename>pam_mount</" -"filename> module if you can for this). You have the <filename>$USER</" -"filename> and <filename>$DISPLAY</filename> 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 <filename>PreSession</filename> directory, again in " -"the same manner as the <filename>Init</filename> directory. Use this script " -"for local session management or accounting stuff. The <filename>$USER</" -"filename> environment variable contains the login of the authenticated user " -"and <filename>$DISPLAY</filename> 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 " -"<filename>$X_SERVERS</filename> 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 <filename>Xsession</filename> 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 <filename>Exec=</filename> line in the <filename>.desktop</" -"filename> files in the path specified by <filename>SessionDesktopDir</" -"filename>. Usually this path is <filename><etc>/X11/sessions/:<" -"etc>/dm/Sessions:/usr/share/xsessions/</filename>. The first found file " -"is used. The user either picks from these sessions or GDM will look inside " -"the file <filename>~/.dmrc</filename> 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 <filename>$GDM_LANG</" -"filename> 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 <filename>$GDM_LANG</filename> " -"is not set." -msgstr "" - -#: ../C/gdm.xml:1641(para) -msgid "" -"When the user terminates his session, the <filename>PostSession</filename> " -"script will be run. Again operation is similar to <filename>Init</filename>, " -"<filename>PostLogin</filename> and <filename>PreSession</filename>. Again " -"the script will be run with root privileges, the slave daemon will block and " -"the <filename>$USER</filename> environment variable will contain the name of " -"the user who just logged out and <filename>$DISPLAY</filename> will be set " -"to the display the user used, however note that the X server for this " -"display may already be dead and so you shouldn't try to access it. Also " -"<filename>$X_SERVERS</filename> 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:1656(para) -msgid "" -"Note that the <filename>PostSession</filename> script will be run even when " -"the display fails to respond due to an I/O error or similar. Thus, there is " -"no guarantee that X applications will work during script execution." -msgstr "" - -#: ../C/gdm.xml:1663(para) -msgid "" -"Except for the <filename>Xsession</filename> script all of these scripts " -"will also have the environment variable <filename>$RUNNING_UNDER_GDM</" -"filename> set to <filename>yes</filename>, so that you could perhaps use " -"similar scripts for different display managers. The <filename>Xsession</" -"filename> will always have the <filename>$GDMSESSION</filename> set to the " -"basename of the session that the user chose to run without the <filename>." -"desktop</filename> extension. In addition <filename>$DESKTOP_SESSION</" -"filename> 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 <filename>Init</filename>, <filename>PostLogin</filename>, " -"<filename>PreSession</filename> or <filename>PostSession</filename> scripts " -"are necessary and can be left out. The <filename>Xsession</filename> script " -"is however required as well as at least one session <filename>.desktop</" -"filename> 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 " -"(<filename><share>/gdm/defaults.conf</filename>) and the GDM Custom " -"Configuration File (<filename><etc>/gdm/custom.conf</filename>). 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 <filename><etc>/gdm/custom.conf<display " -"num></filename>. 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 <filename><etc>/gdm/custom.conf:0</" -"filename>. 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 <command>gdmsetup</command> command can be used to modify the GDM Custom " -"Configuration File. Note the <command>gdmsetup</command> 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 <command>--config</command> 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 " -"<command>--with-defaults-conf</command> and <command>--with-custom-conf</" -"command> configuration options." -msgstr "" - -#: ../C/gdm.xml:1755(para) -msgid "" -"Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</" -"filename> 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 <filename><etc>/gdm/gdm.conf</filename> file is different than the " -"<filename><etc>/gdm/factory-gdm.conf</filename> file. If so, the " -"<filename><etc>/gdm/gdm.conf</filename> file will be automatically " -"copied to <filename><etc>/gdm/custom.conf</filename> 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 <filename>.ini</filename> 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 <command>gdmgreeter</command> or <command>gdmlogin</" -"command> 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 <command>at-spi-registryd</command> will " -"be launched by <command>gdmgreeter</command> or <command>gdmlogin</command> " -"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 <filename>GtkModulesList</filename> 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 <command>gdmflexiserver</" -"command> 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 " -"<filename>SystemCommandsInMenu</filename> and " -"<filename>RBACSystemCommandKeys</filename> 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 <filename>TimedLogin</filename>." -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 <filename>Exec=</filename> from the <filename>.desktop</" -"filename> 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 <filename>GDMSESSION</filename> environmental variable. This " -"will always be set to the basename of <filename>.desktop</filename> (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 " -"<filename>GDM_LANG</filename>, 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 <filename><etc>/profile</filename> and friends. The " -"standard script shipped with GDM sources the files in this order: " -"<filename><etc>/profile</filename> then <filename>~/.profile</" -"filename> then <filename><etc>/xprofile</filename> and finally " -"<filename>~/.xprofile</filename>. Note that different distributions may " -"change this however. Sometimes users personal setup will be in <filename>~/." -"bash_profile</filename>, 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 " -"<filename>ConfigAvailable</filename> 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 <filename>/etc/default/login</filename> if " -"it contains \"ROOT=<pathname>\". If the <filename>/etc/default/login</" -"filename> 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 <filename>ShowLastSession</filename> 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 <filename>http://www." -"radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> 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 " -"<filename>/tmp/.gdm_socket</filename> socket connection. Displays can be " -"created, started, and deleted with the appropriate commands. The " -"<filename>gdmdynamic</filename> 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 " -"<filename>XKeepsCrashing</filename> 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 <filename>VTAllocation</filename>." -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 <filename>/tmp/.gdm_socket</filename> socket connection. " -"This is used for both full flexible displays and for nested displays (refer " -"to the <filename>Xnest</filename> 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 <filename>Xnest</filename> " -"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 <filename>RemoteGreeter</filename>" -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 <command>gdmlogin</command>, <command>gdmgreeter</" -"command>, <command>gdmchooser</command> and the internal failsafe GTK+ " -"dialogs are run. Also see <filename>User</filename>. 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 <filename>ServAuthDir</filename> is owned by this group. " -"The ownership and permissions of <filename>ServAuthDir</filename> should be " -"<filename>root.gdm</filename> 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 <command>gdmgreeter</command> or " -"<command>gdmlogin</command> will be invoked with if <filename>AddGtkModules</" -"filename> 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 <command>gdmflexiserver</command> commands. Valid " -"actions are HALT, REBOOT, SUSPEND, and CUSTOM_CMD. The greeter will only " -"display the command if the gdm user (<filename>User</filename> 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 <filename>AllowLogoutActions</filename> and " -"<filename>SystemCommandsInMenu</filename> 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 <filename>Greeter</filename> 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 <filename>/etc/default/login</filename> if " -"it contains \"SUROOT=<pathname>\". If the <filename>/etc/default/" -"login</filename> 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 <filename>root.gdm</filename> with permissions 1770, " -"where <filename>gdm</filename> is the GDM group as defined by the " -"<filename>Group</filename> option. That is should be owned by root, with " -"<filename>gdm</filename> 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 <filename>.desktop</filename> 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=<placeholder-1/> (or <placeholder-2/> 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 <filename>SoundOnLoginFile</filename> 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 <command>gdmflexiserver</" -"command> 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 <filename>AllowLogoutActions</filename> and " -"<filename>RBACSystemCommandKeys</filename> 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 <filename>TimedLogin</filename> should be logged in " -"after a number of seconds (set with <filename>TimedLoginDelay</filename>) of " -"inactivity on the login screen. This is useful for public access terminals " -"or perhaps even home use. If the user uses the keyboard or browses the " -"menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or " -"30 seconds, whichever is higher. If the user does not enter a username but " -"just hits the ENTER key while the login program is requesting the username, " -"then GDM will assume the user wants to login immediately as the timed user. " -"Note that no password will be asked for this user so you should be careful, " -"although if using PAM it can be configured to require password entry before " -"allowing login." -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 <filename>AutomaticLogin</" -"filename> 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 <filename>TimedLogin</filename> 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 <command>gdmlogin</command>, <command>gdmgreeter</" -"command>, <command>gdmchooser</command> and the internal failsafe GTK+ " -"dialogs are run. Also see <filename>Group</filename>. 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 <filename>.Xauthority</filename> 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: <filename>~/authdir/</" -"filename>." -msgstr "" - -#: ../C/gdm.xml:2545(para) -msgid "" -"If you do not use the tilde expansion, then the filename created will be " -"random, like in <filename>UserAuthFBDir</filename>. This way many users can " -"have the same authentication directory. For example you might want to set " -"this to <filename>/tmp</filename> 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 <filename>/tmp</" -"filename> 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 <filename>NeverPlaceCookiesOnNFS</filename> in the " -"<filename>[security]</filename> 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 <filename>.Xauthority</filename> 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 " -"<filename>FirstVT</filename>." -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 " -"<filename>XKeepsCrashing</filename> 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 <filename>FailsafeXServer</filename> 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 <filename>Xnest</filename> 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 <filename>/etc/default/" -"login</filename> file exists and contains \"CONSOLE=/dev/login\", and set to " -"true if the <filename>/etc/default/login</filename> 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 <filename>RelaxPermissions</filename> 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 <filename>-nolisten tcp</filename> 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 <filename>/etc/default/login</filename> if it " -"contains \"PASSREQ=[YES|NO]\". If the <filename>/etc/default/login</" -"filename> 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 " -"<filename>RelaxPermissions</filename> 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 " -"<filename>DisplaysPerHost</filename> 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 "" -"<filename>gdm</filename> 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 " -"<filename>gdm</filename>" -msgstr "" - -#: ../C/gdm.xml:2912(para) -msgid "" -"You should add <screen>\n" -"gdm:.my.domain\n" -"</screen> to your <filename><etc>/hosts.allow</filename>, depending on " -"your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:" -"hosts.allow\">hosts.allow(5)</ulink> 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 <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</" -"filename> 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 " -"<filename>gdmchooser</filename>) 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 <filename>MaxPendingIndirect</filename> 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 " -"<filename>MaxPendingIndirect</filename>." -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 <filename>gdm</filename> 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 <filename>PingInterval</filename> " -"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 <filename>gtkrc</filename> to read when GDM puts up a window. You " -"should really now use the <filename>GtkTheme</filename> 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 " -"<filename>AllowGtkThemeChange</filename> 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 <filename>BackgroundProgram</filename> 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 " -"<filename>Configurator</filename> 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 <filename>DefaultFace</filename> 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 " -"<command>gdmsetup</command> selection list for Automatic/Timed login. See " -"also <filename>Exclude</filename>, <filename>IncludeAll</filename>, and " -"<filename>MinimalUID</filename>." -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 <command>gdmsetup</command> selection list for Automatic/Timed login. " -"Excluded users will still be able to log in, but will have to type their " -"username. See also <filename>Include</filename>, <filename>IncludeAll</" -"filename>, and <filename>MinimalUID</filename>." -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 <filename>Include</filename>, <filename>Exclude</" -"filename>, and <filename>MinimalUID</filename>." -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. <filename><GlobalFaceDir>/johndoe</filename> 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 <filename>GraphicalThemeDir</" -"filename>." -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 <filename>GraphicalThemeDir</" -"filename>. This is only used if <filename>GraphicalThemeRand</filename> 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 <filename>GraphicalTheme</" -"filename>, Random Themes mode uses themes listed by " -"<filename>GraphicalThemes</filename>. 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 <command>gdmsetup</" -"command>. This key is modified by <command>gdmsetup</command> and should not " -"be manually modified by the user. This only affects the Login Window " -"Preferences (<command>gdmsetup</command>)." -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 <filename>Include</" -"filename>, <filename>Exclude</filename>, and <filename>IncludeAll</filename>." -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 <command>gdmlogin</command> 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 " -"<filename>RemoteWelcome</filename>. This value is translated into the " -"appropriate language for the user. If set to false, the " -"<filename>RemoteWelcome</filename> 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 " -"<filename>Welcome</filename> 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 <filename>BackgroundType</filename> 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 <filename>PositionX</filename> / <filename>PositionY</filename>." -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 <filename>DefaultSession</filename>) 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 <filename>SoundOnLoginFile</filename> 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 <filename>SoundOnLoginSuccessFile</filename> 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 <filename>SoundOnLoginFailureFile</filename> 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 <filename>/usr/bin/play</filename>) instead of a beep when " -"the greeter is ready for a login. See also the <filename>SoundOnLogin</" -"filename> key and the <filename>SoundProgram</filename> 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 <filename>/usr/bin/play</filename>) after a successful login " -"attempt. See also the <filename>SoundOnLoginSuccess</filename> key and the " -"<filename>SoundProgram</filename> 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 <filename>/usr/bin/play</filename>) after a failed login " -"attempt. See also the <filename>SoundOnLoginFailure</filename> key and the " -"<filename>SoundProgram</filename> 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 <filename>fi_FI</filename>), 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 " -"<filename>UseCirclesInEntry</filename> 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 <filename>Welcome</" -"filename>. This value is translated into the appropriate language for the " -"user. If set to false, the <filename>Welcome</filename> 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 " -"<filename>RemoteWelcome</filename>." -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 " -"<filename>Hosts</filename> 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 <filename>Hosts </filename> 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 <filename>gdmchooser</filename>." -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 " -"<filename>Broadcast</filename> 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 " -"<filename>n-th</filename> \"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 <filename>CustomCommand</filename> 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 <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is " -"defined. [0-9] represents <filename>CustomCommand</filename> 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 <filename>n-th</" -"filename> \"Custom Command\" buttons and menu items. If not specified the " -"default value is \"Custom_[0-9]\". This option is only valid if " -"corresponding <filename>CustomCommand</filename> is defined. [0-9] " -"represents <filename>CustomCommand</filename> 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 <filename>n-th</" -"filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] " -"represents <filename>CustomCommand</filename> 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 <filename>n-th</filename> " -"\"Custom Command\" has been executed. If not specified the default value is " -"\"false\". This option is only valid if corresponding " -"<filename>CustomCommand</filename> is defined. [0-9] represents " -"<filename>CustomCommand</filename> suffix and can be an integer between 0 " -"and 9. In addition when corresponding <filename>CustomCommandIsPersistent</" -"filename> is set to true, setting CustomCommandNoRestart to false will place " -"corresponding <filename>CustomCommand</filename> in the Shut Down dialog set " -"of actions, setting it to true will place corresponding " -"<filename>CustomCommand</filename> 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 " -"<filename>n-th</filename> \"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 " -"<filename>CustomCommand</filename> is defined. [0-9] represents " -"<filename>CustomCommand</filename> 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 <filename>n-th</" -"filename> \"Custom Command\" entries. If not specified the default value is " -"\"Execute custom command [0-9]\". This option is only valid if corresponding " -"<filename>CustomCommand</filename> is defined. [0-9] represents " -"<filename>CustomCommand</filename> 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 <filename>Standard</filename> " -"is required. If you do not specify this server, GDM will assume default " -"values for a 'Standard' server and the path given by <filename>daemon/" -"StandardXServer</filename>. <filename>Standard</filename> 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 <filename>server-</filename> 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, <filename>server-</" -"filename> sections in the GDM Custom Configuration File override values in " -"the GDM System Defaults Configuration File. In other words, if a " -"<filename>server-Standard</filename> 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:4376(para) -msgid "" -"Indicates that GDM should run the login window on this server and allow a " -"user to log in. If set to false, then GDM will just run this server and wait " -"for it to terminate. This can be useful to run an X terminal using GDM. When " -"this is done you should normally also add <filename>-terminate</filename> to " -"the command line of the server to make the server terminate after each " -"session. Otherwise the control of the slave will never come back to GDM and, " -"for example, soft restarts won't work. This is because GDM assumes there is " -"a login in progress for the entire time this server is active." -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 <filename>[servers]</filename> " -"section corresponds to the display number to be managed. Normally there is " -"only one key, which is the key <filename>0</filename>, which corresponds to " -"the display <filename>:0</filename>." -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 <filename>" -"[servers]</filename> 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 \"<filename>-auth <ServAuthDir>/:n.Xauth :n</filename>" -"\", 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 <filename>VTAllocation</" -"filename> key is set." -msgstr "" - -#: ../C/gdm.xml:4474(para) -msgid "" -"Normally you do not need to add a <filename>-nolisten tcp</filename> flag as " -"this is added automatically for local X servers when the " -"<filename>DisallowTCP</filename> 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 <filename>UserMaxFile</filename> 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 <filename>~/.dmrc</filename> file. In theory this file " -"should be shared between GDM and KDM, so users only have to configure things " -"once. This is a standard <filename>.ini</filename> style configuration file. " -"It has one section called <filename>[Desktop]</filename> which has two keys: " -"<filename>Session</filename> and <filename>Language</filename>." -msgstr "" - -#: ../C/gdm.xml:4528(para) -msgid "" -"The <filename>Session</filename> key specifies the basename of the session " -"<filename>.desktop</filename> file that the user wishes to normally use " -"(without the <filename>.desktop</filename> extension, in other words). The " -"<filename>Language</filename> key specifies the language that the user " -"wishes to use by default. If either of these keys is missing, the system " -"default is used. The file would normally look as follows:" -msgstr "" - -#: ../C/gdm.xml: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 <filename>$HOME/.face</" -"filename> 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 " -"<filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> " -"values defined in the GDM configuration or it will be ignored. Users can run " -"the <command>gdmphotosetup</command> program to specify a face image and it " -"will copy the file to the <filename>$HOME/.face</filename> location and " -"scale it so its longest dimension is not larger than the " -"<filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> " -"values. <command>gdmphotosetup</command> 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 <filename>GlobalFaceDir</filename> configuration option " -"( normally <filename><share>/pixmaps/faces/</filename>) and the " -"filename should be the name of the user, optionally with a <filename>.png</" -"filename>, <filename>.jpg</filename>, 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 <command>gdm-stop</command> command which is in the <filename><" -"sbin>/</filename> directory. To restart GDM, you can either send the HUP " -"signal to the main daemon or run the <command>gdm-restart</command> command " -"which is also in the <filename><sbin>/</filename> 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 <command>gdm-safe-" -"restart</command> command which is in the <filename><sbin>/</filename> " -"directory as well." -msgstr "" - -#: ../C/gdm.xml:4600(para) -msgid "" -"The <command>gdmflexiserver</command> 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 " -"<command>gdmflexiserver</command> 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 <command>gdmflexiserver --help</" -"command> 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 <filename>.gdmfifo</filename> in the " -"<filename>ServAuthDir</filename> directory (usually <filename><var>/" -"gdm/.gdmfifo</filename>). 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:4629(para) -msgid "" -"Full and up to date documentation of the commands and their use is contained " -"in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look " -"for the defines starting with <filename>GDM_SOP_</filename>. The commands " -"which require the pid of the slave as an argument are the ones that are " -"really used for internal communication of the slave with the master and " -"should not be used." -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 <filename>/tmp/." -"gdm_socket</filename>. 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 <command>gdmflexiserver</" -"command> 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:5185(screen) -#, no-wrap -msgid "" -"\n" -"SERVER_BUSY: Returns true if half or more of the daemon's sockets\n" -" are busy, false otherwise. Used by slave programs\n" -" which want to ensure they do not overwhelm the \n" -" sever.\n" -"Supported since: 2.13.0.8\n" -"Arguments: None\n" -"Answers:\n" -" OK <value>\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:5202(title) -msgid "SET_LOGOUT_ACTION" -msgstr "" - -#: ../C/gdm.xml:5203(screen) -#, no-wrap -msgid "" -"\n" -"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -" slave process exits. 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: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 " -"<filename>bindir</filename> intended to be used by the end-user:" -msgstr "" - -#: ../C/gdm.xml:5385(title) -msgid "" -"<command>gdmXnestchooser</command> and <command>gdmXnest</command> Command " -"Line Options" -msgstr "" - -#: ../C/gdm.xml:5388(para) -msgid "" -"The <command>gdmXnestchooser</command> 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 <command>gdmXnestchooser somehost</command> will run " -"the XDMCP chooser from host <command>somehost</command> inside a nested X " -"server session. You can make this command do a direct query instead by " -"passing the <command>-d</command> option as well. In addition to the " -"following options, this command also supports standard GNOME options." -msgstr "" - -#: ../C/gdm.xml:5403(title) -msgid "<command>gdmXnestchooser</command> 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 <filename>Xnest</" -"filename> 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 "<command>gdmflexichooser</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5474(para) -msgid "" -"The <command>gdmflexiserver</command> 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 <command>gdmflexiserver --command</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, <command>gdmflexiserver</command> 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 "<command>gdmdynamic</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5579(para) -msgid "" -"<command>gdmdynamic</command> 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 " -"<command>gdmdynamic</command> command can be used to create a new display on " -"a particular display number, run all newly created displays, or remove a " -"display. The <command>gdmdynamic</command> 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, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a 3=/usr/" -"X11R6/bin/X -dev /dev/fb2\"</command>" -msgstr "" - -#: ../C/gdm.xml:5615(para) -msgid "" -"The display will not actually be started until the display is released by " -"calling <command>gdmdynamic</command> 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 <command>gdmflexiserver</command> " -"command. Without a pattern lists all attached displays. With a pattern will " -"match using glob characters '*', '?', and '[]'. For example: <command>\"-l " -"Standard*\"</command><command>\"-l *Xorg*\"</command>" -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, <command>gdmdynamic</command> 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, <command>gdmdynamic</command> 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 "<command>gdmphotosetup</command> 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 " -"<filename>~/.face</filename>. This command accepts standard GNOME options." -msgstr "" - -#: ../C/gdm.xml:5713(title) -msgid "<command>gdmthemetester</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5715(para) -msgid "" -"<command>gdmthemetester</command> 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. <command>gdmthemetester</" -"command> requires that the system support <command>gdmXnest</command>. Note " -"that themes can display differently depending on the theme's \"Show mode\". " -"<command>gdmthemetester</command> allows viewing the themes in different " -"modes via the environment option. Valid environment values and their " -"meanings follow: <screen>\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" -"</screen>" -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 " -"<filename>sbindir</filename> intended to be used by the root user:" -msgstr "" - -#: ../C/gdm.xml:5749(title) ../C/gdm.xml:5765(title) -msgid "<command>gdm</command> and <command>gdm-binary</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5752(para) -msgid "" -"The <command>gdm</command> command is really just a script which runs the " -"<command>gdm-binary</command>, passing along any options. Before launching " -"<command>gdm-binary</command>, the gdm wrapper script will source the " -"<filename><etc>/profile</filename> file to set the standard system " -"environment variables. In order to better support internationalization, it " -"will also set the LC_MESSAGES environment variable to LANG if neither " -"LC_MESSAGES or LC_ALL are set. 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 <filename>[servers]</filename> " -"section will be run, and the console will not be used for communicating " -"errors to the user. An empty <filename>[servers]</filename> 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 "<command>gdmsetup</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5854(para) -msgid "" -"<command>gdmsetup</command> 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 <command>gdmsetup</command> 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 "<command>gdm-restart</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5868(para) -msgid "" -"<command>gdm-restart</command> stops and restarts GDM by sending the GDM " -"daemon a HUP signal. This command will immediately terminate all sessions " -"and log out users currently logged in with GDM." -msgstr "" - -#: ../C/gdm.xml:5876(title) -msgid "<command>gdm-safe-restart</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5878(para) -msgid "" -"<command>gdm-safe-restart</command> stops and restarts GDM by sending the " -"GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out." -msgstr "" - -#: ../C/gdm.xml:5886(title) -msgid "<command>gdm-stop</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5888(para) -msgid "" -"<command>gdm-stop</command> 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 " -"<filename>libexecdir</filename> intended to be used by the gdm daemon " -"process." -msgstr "" - -#: ../C/gdm.xml:5905(title) -msgid "" -"<command>gdmchooser</command> and <command>gdmlogin</command> Command Line " -"Options" -msgstr "" - -#: ../C/gdm.xml:5908(para) -msgid "" -"The <command>gdmgreeter</command> and <command>gdmlogin</command> are two " -"different login applications, either can be used by GDM. " -"<command>gdmgreeter</command> is themeable with GDM themes while " -"<command>gdmlogin</command> 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 "<command>gdmchooser</command> Command Line Options" -msgstr "" - -#: ../C/gdm.xml:5921(para) -msgid "" -"The <command>gdmchooser</command> is the XDMCP chooser application. The " -"<command>gdmchooser</command> 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 <command>gdm-ssh-session</command> 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 <ulink type=\"http\" url=\"http://art.gnome.org/themes/" -"gdm_greeter/\"> the theme website</ulink>." -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 <filename><share>/gdm/themes/<theme_name></filename>. " -"Usually this would be under <filename>/usr/share</filename>. The theme " -"directory should contain a file called <filename>GdmGreeterTheme.desktop</" -"filename> 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 <filename>.desktop</filename>files. 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 " -"<command>gdmthemetester</command> 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 <filename><share>/gdm/" -"themes</filename> directory). And this is the tarball you distribute and " -"people can install from the graphical configuration application. You can do " -"this with the commands: <screen>\n" -"cd <share>/gdm/themes\n" -"tar czvf <theme_name>.tar.gz <theme_name>/\n" -"</screen>" -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: <screen>\n" -"<box orientation=\"alignment\" min-width=\"num\"\n" -"xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -"homogeneous=\"bool\">\n" -"</screen> 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: <screen>\n" -"<fixed>\n" -"</screen> 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: <screen>\n" -"<item type=\"label\">\n" -"</screen> 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: <screen>\n" -"<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n" -"</screen>" -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 <filename>n-th</filename> 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: <screen>\n" -"<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" -"</screen>" -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: <screen>\n" -"<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/>\n" -"</screen>" -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: <screen>\n" -"<item type=\"label\">\n" -"<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -"</screen>" -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 "<filename>console</filename> - In console mode." -msgstr "" - -#: ../C/gdm.xml:6653(para) -msgid "<filename>console-fixed</filename> - In console non-flexi mode." -msgstr "" - -#: ../C/gdm.xml:6656(para) -msgid "<filename>console-flexi</filename> - In console & flexi mode." -msgstr "" - -#: ../C/gdm.xml:6659(para) -msgid "<filename>flexi</filename> - In flexi mode." -msgstr "" - -#: ../C/gdm.xml:6662(para) -msgid "<filename>remote</filename> - In remote mode." -msgstr "" - -#: ../C/gdm.xml:6665(para) -msgid "<filename>remote-flexi</filename> - In remote & flexi mode." -msgstr "" - -#: ../C/gdm.xml:6669(para) -msgid "" -"For example: <screen>\n" -"<show modes=\"flexi,remote\"/>\n" -"</screen>" -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 "" -"<filename>chooser</filename>, if ChooserButton is set to \"true\" in the GDM " -"configuration." -msgstr "" - -#: ../C/gdm.xml:6686(para) -msgid "" -"<filename>config</filename>, if ConfigAvailable is set to \"true\" in the " -"GDM configuration." -msgstr "" - -#: ../C/gdm.xml:6690(para) -msgid "" -"<filename>custom_cmd[0-9]</filename>, if <filename>n-th</filename> " -"CustomCommand is specified in the GDM configuration." -msgstr "" - -#: ../C/gdm.xml:6694(para) -msgid "" -"<filename>halt</filename>, if HaltDaemon is specified in the GDM " -"configuration." -msgstr "" - -#: ../C/gdm.xml:6698(para) -msgid "" -"<filename>reboot</filename>, if RebootCommand is specified in the GDM " -"configuration." -msgstr "" - -#: ../C/gdm.xml:6702(para) -msgid "" -"<filename>suspend</filename>, if SuspendCommand is specified in the GDM " -"configuration." -msgstr "" - -#: ../C/gdm.xml:6706(para) -msgid "" -"<filename>system</filename>, if SystemMenu is specified in the GDM " -"configuration." -msgstr "" - -#: ../C/gdm.xml:6710(para) -msgid "" -"<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in the " -"GDM configuration." -msgstr "" - -#: ../C/gdm.xml:6715(para) -msgid "" -"For example: <screen>\n" -"<show modes=\"console\" type=\"system\"/>\n" -"</screen>" -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: <screen>\n" -"<show min-screen-height=\"768\"/>\n" -"</screen>" -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 "<filename>normal</filename> - normal state." -msgstr "" - -#: ../C/gdm.xml:6756(para) -msgid "<filename>active</filename> - when the item has active focus." -msgstr "" - -#: ../C/gdm.xml:6759(para) -msgid "<filename>prelight</filename> - 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): <screen>\n" -"<normal color=\"#ffffff\" alpha=\"0.0\">\n" -"</screen>" -msgstr "" - -#: ../C/gdm.xml:6772(para) -msgid "" -"When item is \"label\" <screen>\n" -"<normal color=\"#ffffff\" font=\"Sans 14\"/>\n" -"</screen>" -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: <screen>\n" -"<normal file=\"picture.png\" tint=\"#dddddd\"/>\n" -"</screen>" -msgstr "" - -#: ../C/gdm.xml:6788(para) -msgid "" -"Note that relative pathnames are assumed to be in the same directory as the " -"theme <filename>.xml</filename> file in <filename><share>/gdm/themes/" -"<theme_name></filename>." -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: " -"<screen>\n" -"<normal file=\"picture.png\" altfile1=\"distribution-blah-image.png\" " -"altfile2=\"distribution-foo-image.png\"/>\n" -"</screen> If <filename>distribution-foo-image.png</filename> 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): " -"<screen>\n" -"<text xml:lang=\"fr\">Option</text>\n" -"</screen>" -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: <screen>\n" -"<text>\"foo<sup>bar</sup>\"</text>\n" -"</screen>" -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 "<filename>cancel</filename>, _(\"_Cancel\"" -msgstr "" - -#: ../C/gdm.xml:6917(para) -msgid "<filename>caps-lock-warning</filename>, _(\"Caps Lock is on.\"" -msgstr "" - -#: ../C/gdm.xml:6921(para) -msgid "<filename>chooser</filename>, _(\"Remote Login via _XDMCP\"" -msgstr "" - -#: ../C/gdm.xml:6924(para) -msgid "<filename>config</filename>, _(\"_Configure\"" -msgstr "" - -#: ../C/gdm.xml:6927(para) -msgid "<filename>custom_cmd[0-9]</filename>, getting label from config file" -msgstr "" - -#: ../C/gdm.xml:6930(para) -msgid "<filename>disconnect</filename>, _(\"D_isconnect\"" -msgstr "" - -#: ../C/gdm.xml:6933(para) -msgid "<filename>halt</filename>, _(\"Shut _Down\"" -msgstr "" - -#: ../C/gdm.xml:6936(para) -msgid "<filename>language</filename>, _(\"_Language\"" -msgstr "" - -#: ../C/gdm.xml:6939(para) -msgid "<filename>ok</filename>, _(\"_OK\"" -msgstr "" - -#: ../C/gdm.xml:6942(para) -msgid "<filename>options</filename>, _(\"_Options\"" -msgstr "" - -#: ../C/gdm.xml:6945(para) -msgid "<filename>quit</filename>, _(\"_Quit\"" -msgstr "" - -#: ../C/gdm.xml:6948(para) -msgid "<filename>reboot</filename>, _(\"_Restart\"" -msgstr "" - -#: ../C/gdm.xml:6951(para) -msgid "<filename>session</filename>, _(\"_Session\"" -msgstr "" - -#: ../C/gdm.xml:6954(para) -msgid "<filename>startagain</filename>, _(\"_Start Again\"" -msgstr "" - -#: ../C/gdm.xml:6957(para) -msgid "<filename>suspend</filename>, _(\"Sus_pend\"" -msgstr "" - -#: ../C/gdm.xml:6960(para) -msgid "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\"" -msgstr "" - -#: ../C/gdm.xml:6964(para) -msgid "<filename>timed-label</filename>, _(\"User %u will login in %t\"" -msgstr "" - -#: ../C/gdm.xml:6968(para) -msgid "<filename>username-label</filename>, _(\"Username:\"" -msgstr "" - -#: ../C/gdm.xml:6971(para) -msgid "<filename>welcome-label</filename>, _(\"Welcome to %n\"" -msgstr "" - -#: ../C/gdm.xml:6975(para) -msgid "" -"For example: <screen>\n" -"<stock type=\"welcome-label\">\n" -"</screen>" -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 " -"<filename><ServAuthDir>/<display>.GreeterInfo</filename> as " -"<filename><list id>=<listitem id></filename>." -msgstr "" - -#: ../C/gdm.xml:6997(para) -msgid "" -"For example suppose we are on display :0, <filename>ServAuthDir</filename> " -"is <filename><var>/lib/gdm</filename> 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 <filename><var>/lib/gdm/:0." -"GreeterInfo</filename> will contain: <screen>\n" -"custom-config=foo\n" -"</screen>" -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 <command>GOK</" -"command> (on-screen keyboard) and <command>orca</command> (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 <command>GOK</command>, 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 <filename>Greeter</" -"filename> and <filename>RemoteGreeter</filename> configuration options by " -"hand to be <command>/usr/lib/gdmlogin</command>." -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 <command>gdmsetup</command> 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 <command>GOK</command> and <command>orca</command>, " -"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 <filename>AllowGtkThemeChange</" -"filename> 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 " -"<filename>GtkThemesToAllow</filename> 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 <command>GOK</command> or " -"<command>orca</command>, the <filename>AddGtkModules</filename> parameter in " -"the GDM configuration must be set to \"true\". Also the " -"<filename>GtkModulesList</filename> 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, <command>at-spi-registryd</" -"command>, 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 <filename>AddGtkModules</filename> loaded by GDM, then you may need to " -"modiify the gesture configurations to meet your user's needs. Default " -"gestures are provided for launching <command>GOK</command> and " -"<command>orca</command>, but it is recommended to modify these gestures so " -"they work best for your user base. These gesture associations are contained " -"in files <filename>AccessKeyMouseEvents</filename> and " -"<filename>AccessDwellMouseEvents</filename>, respectively. Both files are " -"located in the <filename><etc>/gdm/modules</filename> 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 <command>GOK</command> and <command>orca</command> 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 <filename><bin>/play</filename> (or <filename><" -"bin>/audioplay</filename> on Solaris. This can be changed via the " -"<filename>SoundProgram</filename> GDM configuration option. Typically most " -"text-to-speech programs (such as <command>orca</command>) 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 <command>svcs</command> 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 <command>svcs</command> 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. <screen>\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" -"</screen>" -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 <command>gdmflexiserver</command> " -"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 " -"<filename>RBACSystemCommandKeys</filename> 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 " -"<filename>User</filename> 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 " -"<filename>/etc/user_attr</filename> 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 " -"<filename>RBACSystemCommandKeys</filename> GDM configuration key, and this " -"will make the system commands available for all users. Refer to the " -"<filename>user_attr</filename> 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 <command>gnome-sys-suspend</command>. " -"<command>gnome-sys-suspend</command> is a GUI front-end for the <command>sys-" -"suspend</command>." -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 <command>gnome-sys-suspend</" -"command> 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 <command>gnome-sys-suspend</command> 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 <command>gnome-sys-suspend</command> 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 <command>gnome-sys-suspend</command>. If you are " -"using this, then refer to the <command>sys-suspend</command> 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 <filename>/etc/default/login</filename> interface, " -"which affects the <filename>DefaultPath</filename>, <filename>RootPath</" -"filename>, <filename>PasswordRequired</filename>, and " -"<filename>AllowRemoteRoot</filename> 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 <filename>xterminal</filename> " -"and let's call the server machine <filename>appserver</filename>. You " -"install GDM on both." -msgstr "" - -#: ../C/gdm.xml:7568(para) -msgid "" -"On <filename>appserver</filename> you enable XDMCP, so you have <screen>\n" -"[xdmcp]\n" -"Enable=true\n" -"</screen> If you want no local screens here, you can then make the <filename>" -"[servers]</filename> section empty." -msgstr "" - -#: ../C/gdm.xml:7578(para) -msgid "" -"On the <filename>xterminal</filename> you disable XDMCP (you don't want " -"anyone to connect to the xterminal really). You will add a server type " -"perhaps called <filename>Terminal</filename> as follows: <screen>\n" -"[server-Terminal]\n" -"name=Terminal server\n" -"command=/path/to/X -terminate\n" -"flexible=false\n" -"handled=false\n" -"</screen> This definition should in fact be included in the standard " -"configuration file. Notice that we made the <filename>handled</filename> key " -"false since we don't want GDM to handle this server localy. Also note that " -"we have not yet added the <filename>-query</filename> argument, you can add " -"that here, or in the <filename>[servers]</filename> section. We'll define " -"our local servers as follows: <screen>\n" -"[servers]\n" -"0=Terminal -query appserver\n" -"</screen> This will run a direct XDMCP query to the server named " -"<filename>appserver</filename>." -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 <filename>appserverone</filename> " -"and <filename>appservertwo</filename>. Again we'll call our example X " -"terminal server <filename>xterminal</filename>. 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 <filename>xterminal</filename> you again disable XDMCP. You will " -"add a server type perhaps called <filename>Chooser</filename> as follows: " -"<screen>\n" -"[server-Chooser]\n" -"name=Chooser server\n" -"command=/path/to/X\n" -"flexible=false\n" -"chooser=true\n" -"</screen> And again this definition should in fact be included in the " -"standard configuration file. Notice that we made the <filename>chooser</" -"filename> 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: <screen>\n" -"[servers]\n" -"0=Chooser\n" -"</screen>" -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 <filename>[chooser]</filename> section you would have: <screen>\n" -"Hosts=appserverone,appservertwo\n" -"</screen> 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 <filename>appserver</filename> and on the X terminals you'd have " -"<screen>\n" -"[servers]\n" -"0=Terminal -indirect appserver\n" -"</screen> This way for example you only have to maintain one " -"<filename>Hosts</filename> entry. However as a disadvantage then, the " -"<filename>appserver</filename> 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 <filename>[customcommand]</filename> " -"section of the GDM configuration file. <screen>\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" -" </screen> CustomCommand0 specifies two commands separated by a " -"semicolon: <filename>/sbin/rebootwindoze</filename> and <filename>/usr/local/" -"sbin/rebootwindoze</filename>. 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 <filename>[customcommand]</filename> " -"section of your GDM configuration file. <screen>\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" -" </screen>" -msgstr "" - -#: ../C/gdm.xml:7720(para) -msgid "" -"Both custom commands could be defined as follows. <screen>\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" -" </screen>" -msgstr "" - -#: ../C/gdm.xml:7741(para) -msgid "" -"There can be up to 10 custom commands numbered 0-9. <screen>\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" -" </screen>" -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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome." -"org</ulink> or send an email to the <address><email>gdm-list@gnome.org</" -"email></address> 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 <command>gdmsetup</command> 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 (<filename><var>/log/messages</filename> or " -"<filename><var>/adm/messages</filename> 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 <command><" -"lib>/gdmlogin</command> or <command><lib>/gdmgreeter</command>. 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 <filename>/tmp</filename> directory has reasonable " -"ownership and permissions, and that the machine's file system is not full. " -"These problems will cause GDM to fail to start." -msgstr "" - -#: ../C/gdm.xml: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 <filename>~/.dmrc</filename>. Other files, such as the user's " -"<filename>~/.Xauthority</filename> 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 <filename>RelaxPermissions</filename> 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 <ulink type=\"help\" url=\"gnome-help:gpl" -"\"><citetitle>GNU General Public License</citetitle></ulink> as published by " -"the Free Software Foundation; either version 2 of the License, or (at your " -"option) any later version." -msgstr "" - -#: ../C/gdm.xml: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 <citetitle>GNU General Public " -"License</citetitle> for more details." -msgstr "" - -#: ../C/gdm.xml:7888(para) -msgid "" -"A copy of the <citetitle>GNU General Public License</citetitle> is included " -"as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also " -"obtain a copy of the <citetitle>GNU General Public License</citetitle> from " -"the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://" -"www.fsf.org\">their Web site</ulink> or by writing to <address> Free " -"Software Foundation, Inc. <street>51 Franklin Street, Fifth Floor</" -"street><city>Boston</city>, <state>MA</state><postcode>02110-1301</" -"postcode><country>USA</country></address>" -msgstr "" - -#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2. -#: ../C/gdm.xml:0(None) -msgid "translator-credits" -msgstr "" - diff --git a/docs/sv/.cvsignore b/docs/sv/.cvsignore deleted file mode 100644 index ab4d4d42..00000000 --- a/docs/sv/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -Makefile -Makefile.in -*.out -omf_timestamp diff --git a/docs/sv/figures/gdm_window.png b/docs/sv/figures/gdm_window.png Binary files differdeleted file mode 100644 index 2dc78e34..00000000 --- a/docs/sv/figures/gdm_window.png +++ /dev/null diff --git a/docs/sv/sv.po b/docs/sv/sv.po deleted file mode 100644 index 8becf1e3..00000000 --- a/docs/sv/sv.po +++ /dev/null @@ -1,5801 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: gdm2\n" -"POT-Creation-Date: 2007-01-27 04:04+0000\n" -"PO-Revision-Date: 2007-03-11 21:41+0100\n" -"Last-Translator: Daniel Nylander <po@danielnylander.se>\n" -"Language-Team: Swedish <tp-sv@listor.tp-sv.se>\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: C/legal.xml:2(para) -#: C/gdm.xml:2(para) -msgid "Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or in the file COPYING-DOCS distributed with this manual." -msgstr "Tillstånd att kopiera, distribuera och/eller modifiera detta dokument ges under villkoren i GNU Free Documentation License (GFDL), version 1.1 eller senare, utgivet av Free Software Foundation utan standardavsnitt och omslagstexter. En kopia av GFDL finns att hämta på denna <ulink type=\"help\" url=\"ghelp:fdl\">länk</ulink> eller i filen COPYING-DOCS som medföljer denna handbok." - -#: 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 "Denna handbok utgör en av flera GNOME-handböcker som distribueras under villkoren i GFDL. Om du vill distribuera denna handbok separat från övriga handböcker kan du göra detta genom att lägga till en kopia av licensavtalet i handboken enligt instruktionerna i avsnitt 6 i licensavtalet." - -#: 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 "Flera namn på produkter och tjänster är registrerade varumärken. I de fall dessa namn förekommer i GNOME-dokumentation - och medlemmarna i GNOME-dokumentationsprojektet är medvetna om dessa varumärken - är de skrivna med versaler eller med inledande versal." - -#: 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 "DOKUMENTET TILLHANDAHÅLLS I \"BEFINTLIGT SKICK\" UTAN NÅGRA SOM HELST GARANTIER, VARE SIG UTTRYCKLIGA ELLER UNDERFÖRSTÅDDA, INKLUSIVE, MEN INTE BEGRÄNSAT TILL, GARANTIER ATT DOKUMENTET ELLER EN MODIFIERAD VERSION AV DOKUMENTET INTE INNEHÅLLER NÅGRA FELAKTIGHETER, ÄR LÄMPLIGT FÖR ETT VISST ÄNDAMÅL ELLER INTE STRIDER MOT LAG. HELA RISKEN VAD GÄLLER KVALITET, EXAKTHET OCH UTFÖRANDE AV DOKUMENTET OCH MODIFIERADE VERSIONER AV DOKUMENTET LIGGER HELT OCH HÅLLET PÅ ANVÄNDAREN. OM ETT DOKUMENT ELLER EN MODIFIERAD VERSION AV ETT DOKUMENT SKULLE VISA SIG INNEHÅLLA FELAKTIGHETER I NÅGOT HÄNSEENDE ÄR DET DU (INTE DEN URSPRUNGLIGA SKRIBENTEN, FÖRFATTAREN ELLER NÅGON ANNAN MEDARBETARE) SOM FÅR STÅ FÖR ALLA EVENTUELLA KOSTNADER FÖR SERVICE, REPARATIONER ELLER KORRIGERINGAR. DENNA GARANTIFRISKRIVNING UTGÖR EN VÄSENTLIG DEL AV DETTA LICENSAVTAL. DETTA INNEBÄR ATT ALL ANVÄNDNING AV ETT DOKUMENT ELLER EN MODIFIERAD VERSION AV ETT DOKUMENT BEVILJAS ENDAST UNDER DENNA ANSVARSFRISKRIVNING;" - -#: 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 "UNDER INGA OMSTÄNDIGHETER ELLER INOM RAMEN FÖR NÅGON LAGSTIFTNING, OAVSETT OM DET GÄLLER KRÄNKNING (INKLUSIVE VÅRDSLÖSHET), KONTRAKT ELLER DYLIKT, SKA FÖRFATTAREN, DEN URSPRUNGLIGA SKRIBENTEN ELLER ANNAN MEDARBETARE ELLER ÅTERFÖRSÄLJARE AV DOKUMENTET ELLER AV EN MODIFIERAD VERSION AV DOKUMENTET ELLER NÅGON LEVERANTÖR TILL NÅGON AV NÄMNDA PARTER STÄLLAS ANSVARIG GENTEMOT NÅGON FÖR NÅGRA DIREKTA, INDIREKTA, SÄRSKILDA ELLER OFÖRUTSEDDA SKADOR ELLER FÖLJDSKADOR AV NÅGOT SLAG, INKLUSIVE, MEN INTE BEGRÄNSAT TILL, SKADOR BETRÄFFANDE FÖRLORAD GOODWILL, HINDER I ARBETET, DATORHAVERI ELLER NÅGRA ANDRA TÄNKBARA SKADOR ELLER FÖRLUSTER SOM KAN UPPKOMMA PÅ GRUND AV ELLER RELATERAT TILL ANVÄNDNINGEN AV DOKUMENTET ELLER MODIFIERADE VERSIONER AV DOKUMENTET, ÄVEN OM PART SKA HA BLIVIT INFORMERAD OM MÖJLIGHETEN TILL SÅDANA SKADOR." - -#: 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: <placeholder-1/>" -msgstr "DOKUMENTET OCH MODIFIERADE VERSIONER AV DOKUMENTET TILLHANDAHÅLLS UNDER VILLKOREN I GNU FREE DOCUMENTATION LICENSE ENDAST UNDER FÖLJANDE FÖRUTSÄTTNINGAR: <placeholder-1/>" - -#: C/gdm.xml:11(title) -msgid "Gnome Display Manager Reference Manual" -msgstr "Referenshandbok för Gnome Display Manager" - -#: C/gdm.xml:15(revnumber) -msgid "0.0" -msgstr "0.0" - -#: C/gdm.xml:16(date) -msgid "2006-12" -msgstr "2006-12" - -#: C/gdm.xml:21(para) -msgid "GDM is the GNOME Display Manager, a graphical login program." -msgstr "GDM är GNOME:s displayhanterare, ett grafiskt inloggningsprogram." - -#: C/gdm.xml:28(firstname) -msgid "Martin" -msgstr "Martin" - -#: C/gdm.xml:28(othername) -msgid "K." -msgstr "K." - -#: C/gdm.xml:29(surname) -msgid "Petersen" -msgstr "Petersen" - -#: C/gdm.xml:31(email) -msgid "mkp@mkp.net" -msgstr "mkp@mkp.net" - -#: C/gdm.xml:35(firstname) -msgid "George" -msgstr "George" - -#: C/gdm.xml:35(surname) -msgid "Lebl" -msgstr "Lebl" - -#: C/gdm.xml:37(email) -msgid "jirka@5z.com" -msgstr "jirka@5z.com" - -#: C/gdm.xml:41(firstname) -msgid "Brian" -msgstr "Brian" - -#: C/gdm.xml:41(surname) -msgid "Cameron" -msgstr "Cameron" - -#: C/gdm.xml:43(email) -msgid "Brian.Cameron@Sun.COM" -msgstr "Brian.Cameron@Sun.COM" - -#: C/gdm.xml:47(firstname) -msgid "Bill" -msgstr "Bill" - -#: C/gdm.xml:47(surname) -msgid "Haneman" -msgstr "Haneman" - -#: C/gdm.xml:49(email) -msgid "Bill.Haneman@Sun.COM" -msgstr "Bill.Haneman@Sun.COM" - -#: C/gdm.xml:54(year) -msgid "1998" -msgstr "1998" - -#: C/gdm.xml:54(year) -msgid "1999" -msgstr "1999" - -#: C/gdm.xml:54(holder) -msgid "Martin K. Petersen" -msgstr "Martin K. Petersen" - -#: C/gdm.xml:57(year) -msgid "2001" -msgstr "2001" - -#: C/gdm.xml:57(year) -#: C/gdm.xml:61(year) -#: C/gdm.xml:64(year) -msgid "2003" -msgstr "2003" - -#: C/gdm.xml:57(year) -#: C/gdm.xml:64(year) -msgid "2004" -msgstr "2004" - -#: C/gdm.xml:58(holder) -msgid "George Lebl" -msgstr "George Lebl" - -#: C/gdm.xml:61(holder) -msgid "Red Hat, Inc." -msgstr "Red Hat, Inc." - -#: C/gdm.xml:64(holder) -msgid "Sun Microsystems, Inc." -msgstr "Sun Microsystems, Inc." - -#: C/gdm.xml:69(releaseinfo) -#: C/gdm.xml:78(para) -msgid "This manual describes version 2.17.4 of the GNOME Display Manager. It was last updated on 12/13/2006." -msgstr "Den här handboken beskriver version 2.17.4 av GNOME:s displayhanterare. Den uppdaterades senast 20061213." - -#: C/gdm.xml:76(title) -msgid "Terms and Conventions Used in This Manual" -msgstr "Terminologi och standarder använda i den här handboken" - -#: C/gdm.xml:83(para) -msgid "Chooser - A program used to select a remote host for managing a display remotely on the local display (<command>gdmchooser</command>)." -msgstr "Väljare - Ett program som används för att välja en fjärrvärd för att hantera en fjärrdisplay på lokal display (<command>gdmchooser</command>)." - -#: C/gdm.xml:88(para) -msgid "Configurator - The configuration application (<command>gdmsetup</command>)." -msgstr "Konfigurator - Konfigurationsprogrammet (<command>gdmsetup</command>)." - -#: C/gdm.xml:93(para) -msgid "GDM - Gnome Display Manager. Used to describe the software package as a whole. Sometimes also referred to as GDM2." -msgstr "GDM - Gnome Display Manager. Används för att beskriva programvarupaketet som en helhet. Ibland refereras den till som GDM2." - -#: C/gdm.xml:98(para) -msgid "gdm - The Gnome Display Manager daemon (<command>gdm</command>)." -msgstr "gdm - Gnome Display Manager-demonen (<command>gdm</command>)." - -#: C/gdm.xml:102(para) -msgid "Greeter - The graphical login window (<command>gdmlogin</command> or <command>gdmgreeter</command>)." -msgstr "Hälsare - Det grafiska inloggningsfönstret (<command>gdmlogin</command> eller <command>gdmgreeter</command>)." - -#: C/gdm.xml:107(para) -msgid "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)." -msgstr "" - -#: C/gdm.xml:111(para) -msgid "PAM - Pluggable Authentication Mechanism" -msgstr "PAM - Pluggable Authentication Mechanism" - -#: C/gdm.xml:115(para) -msgid "Themed Greeter - The themable login window ( <command>gdmgreeter</command>)." -msgstr "" - -#: C/gdm.xml:120(para) -msgid "XDMCP - X Display Manage Protocol" -msgstr "XDMCP - X Display Manage Protocol" - -#: C/gdm.xml:124(para) -msgid "Paths that start with a word in angle brackets are relative to the installation prefix. I.e. <filename><share>/pixmaps/</filename> refers to <filename><share>/pixmaps</filename> if GDM was configured with <command>--prefix=/usr</command>. Normally also note that GDM is installed with <command>--sysconfigdir=<etc>/X11</command>, meaning any path to which we refer to as <filename><etc>/gdm/PreSession</filename> usually means <filename><etc/X11>/gdm/PreSession</filename>. Note that for interoperability it is recommended that you use a --prefix of <filename>/usr</filename> and a --sysconfdir of <filename><etc>/X11</filename>." -msgstr "" - -#: C/gdm.xml:140(title) -msgid "Overview" -msgstr "Översikt" - -#: C/gdm.xml:143(title) -msgid "Introduction" -msgstr "Introdution" - -#: C/gdm.xml:147(para) -msgid "The Gnome Display Manager (GDM) is a display manager that implements all significant features required for managing local and remote displays. GDM was written from scratch and does not contain any XDM / X Consortium code." -msgstr "" - -#: C/gdm.xml:154(para) -msgid "For further information about GDM, see the <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. Please submit any bug reports or enhancement requests to the \"gdm\" category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>. You can also send a message to the <address><email>gdm-list@gnome.org</email></address> mail list to discuss any issues or concerns with the GDM program." -msgstr "För ytterligare information om GDM, se <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> GDM-projektets webbsida</ulink>. Skicka in eventuella felrapporter eller förslag på förbättringar till \"gdm\"-kategorin på <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>. Du kan även skicka ett meddelande till sändlistan <address><email>gdm-list@gnome.org</email></address> för att diskutera tankar eller problem med GDM-programmet." - -#: C/gdm.xml:167(title) -msgid "Interface Stability" -msgstr "Gränssnittsstabilitet" - -#: C/gdm.xml:171(para) -msgid "The key/value pairs defined in the GDM configuration files and the location of these files are considered \"stable\" interfaces and should only change in ways that are backwards compatible. Note that this includes functionality like the GDM scripts (Init, PreSession, PostSession, PostLogin, XKeepsCrashing, etc.); directory locations (ServAuthDir, PidFile, etc.), system applications (SoundProgram), etc. Some configuration values depend on OS interfaces may need to be modified to work on a given OS. Typical examples are HaltCommand, RebootCommand, CustomCommands, SuspendCommand, StandardXServer, Xnest, SoundProgram, and the \"command\" value for each \"server-foo\"." -msgstr "" - -#: C/gdm.xml:185(para) -msgid "Note: distributions often change the default values of keys to support their platform. Command-line interfaces for GDM programs installed to <filename><bin></filename> and <filename><sbin></filename> are considered stable. Refer to your distribution documentation to see if there are any distribution-specific changes to these GDM interfaces and what support exists for them." -msgstr "" - -#: C/gdm.xml:194(para) -msgid "As of the GDM 2.15 development series, some one-dash arguments are no longer supported. This includes the \"-xdmaddress\", \"-clientaddress\", and \"-connectionType\" arguments used by <command>gdmchooser</command>. These arguments have been changed to now use two dashes." -msgstr "" - -#: C/gdm.xml:202(para) -msgid "If issues are discovered that break compatibility, please file a bug with an \"urgent\" priority." -msgstr "" - -#: C/gdm.xml:209(title) -msgid "The GDM Daemon" -msgstr "GDM-demonen" - -#: C/gdm.xml:211(para) -msgid "The GDM daemon is responsible for managing displays on the system. This includes authenticating users, starting the user session, and terminating the user session. GDM is configurable and the ways it can be configured are described in the \"Configuring GDM\" section of this document. The <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename>, and <filename>PostSession</filename> scripts discussed below are discussed in this \"Configuring GDM section\"." -msgstr "" - -#: C/gdm.xml:222(para) -msgid "The GDM daemon supports a UNIX domain socket protocol which can be used to control aspects of its behavior and to query information. This protocol is described in the \"Controlling GDM\" section of this document." -msgstr "" - -#: C/gdm.xml:229(para) -msgid "GDM can be asked to manage a display a number of ways. Local displays are always managed when GDM starts and will be restarted when a user's session is finished. Displays can be requested via XDMCP, flexible displays can be requested by running the <command>gdmflexiserver</command> command. Displays that are started on request are not restarted on session exit. GDM also provides the <command>gdmdynamic</command> command to allow easier management of displays on a multi-user server. These display types are discussed further in the next section." -msgstr "" - -#: C/gdm.xml:241(para) -msgid "When the GDM daemon is asked to manage a display, it will fork an X server process, then run the <filename>Init</filename> script as the root user, and start the login GUI dialog as a slave process on the display. GDM can be configured to use either <command>gdmgreeter</command> (the default) or <command>gdmlogin</command> as the GUI dialog program. The <command>gdmlogin</command> program supports accessibility while the <command>gdmgreeter</command> program supports greater themeability. The GUI dialog is run as the unpriviledged \"gdm\" user/group which is described in the \"Security\" section below. The GUI dialog communicates with the daemon via a sockets protocol and via standard input/output. The slave, for example passes the username and password information to the GDM daemon via standard input/output so the daemon can handle the actual authentication." -msgstr "" - -#: C/gdm.xml:258(para) -msgid "The login GUI dialog screen allows the user to select which session they wish to start and which language they wish to use. Sessions are defined by files that end in the .desktop extension and more information about these files can be found in the \"Configuration\" section. The user enters their name and password and if these successfully authenticate, GDM will start the requested session for the user. It is possible to configure GDM to avoid the authentication process by turning on the Automatic or Timed Login features in the GDM configuration. The login GUI can also be configured to provide additional features to the user, such as the Face Browser; the ability to halt, restart, or suspend the system; and/or edit the login configuration (after entering the root password)." -msgstr "" - -#: C/gdm.xml:273(para) -msgid "GDM, by default, will use Pluggable Authentication Modules (PAM) for authentication, but can also support regular crypt and shadow passwords on legacy systems. After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, and forks a slave process to start the requested session. This slave process runs the <filename>PreSession</filename> script as root, sets up the user's environment, and starts the requested session. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN interface after user authentication to tell the X server to be restarted as the user instead of as root for added security. When the user's session exits, the GDM daemon will run the <filename>PostSession</filename> script as root." -msgstr "" - -#: C/gdm.xml:290(para) -msgid "Note that, by default, GDM uses the \"gdm\" service name for normal login and the \"gdm-autologin\" service name for automatic login. The <filename>PamStack</filename> configuration option can be used to specify a different service name. For example, if \"foo\" is specified, then GDM will use the \"foo\" service name for normal login and \"foo-autologin\" for automatic login." -msgstr "" - -#: C/gdm.xml:300(para) -msgid "For those looking at the code, the gdm_verify_user function in <filename>daemon/verify-pam.c</filename> is used for normal login and the gdm_verify_setup_user function is used for automatic login." -msgstr "" - -#: C/gdm.xml:308(title) -msgid "Different Display Types" -msgstr "" - -#: C/gdm.xml:310(para) -msgid "GDM supports three different display types: static (local) displays, flexible (on-demand) displays, and XDMCP (remote) displays. The \"X Server Definitions\" and the \"Local Static X Display Configuration\" subsections of the \"Configuration\" section explains how these various types of displays are defined in the GDM configuration file." -msgstr "" - -#: C/gdm.xml:319(para) -msgid "Local static displays are always started by the daemon, and when they die or are killed, they are restarted. GDM can run as many of these as needed. GDM can also manage displays on which it does not manage a GUI login, thus GDM can be used for supporting X terminals." -msgstr "" - -#: C/gdm.xml:326(para) -msgid "Flexible, or on demand displays, are started via the socket protocol with the <command>gdmflexiserver</command> command. This feature is only available to users logged in on the console and will display a new login screen. If a flexible display has previously been started on the console, running <command>gdmflexiserver</command> again will display a menu allowing users to switch back to a previous session or start a new flexible session. The <command>gdmflexiserver</command> locks the current session before starting a new flexible display, so the user's password must be entered before returning to an existing session. The <command>gdmflexiserver</command> command can also be used to launch nested <command>Xnest</command> display. These are launched in a window in the user's current session. Nested displays can be started even if not logged into the console and are started by running the <command>gdmflexiserver -n</command> command. Flexible displays are not restarted when the user session ends. Flexible displays require virtual terminal (VT) support in the kernel, and will not be available if not supported (such as on Solaris). Nested displays require that the X server supports Xnest." -msgstr "" - -#: C/gdm.xml:347(para) -msgid "The last display type is the XDMCP remote displays which are described in the next section. Remote hosts can connect to GDM and present the login screen if this is enabled. Some things are different for remote sessions. For example, the Actions menu which allows you to shut down, restart, suspend, or configure GDM are not shown." -msgstr "" - -#: C/gdm.xml:355(para) -msgid "Displays started via the <command>gdmdynamic</command> command are treated as local displays, so they are restarted automatically on when the session exits. This command is intended to more effectively manage the displays on a multi-user server (many displays connected to a single server)." -msgstr "" - -#: C/gdm.xml:365(title) -msgid "XDMCP" -msgstr "XDMCP" - -#: C/gdm.xml:369(para) -msgid "The GDM daemon can be configured to listen for and manage X Display Manage Protocol (XDMCP) requests from remote displays. By default XDMCP support is turned off, but can be enabled if desired. If GDM is built with TCP Wrapper support, then the daemon will only grant access to hosts specified in the GDM service section in the TCP Wrappers configuration file." -msgstr "" - -#: C/gdm.xml:378(para) -msgid "GDM includes several measures making it more resistant to denial of service attacks on the XDMCP service. A lot of the protocol parameters, handshaking timeouts etc. can be fine tuned. The defaults should work for most systems, however. Do not change them unless you know what you are doing." -msgstr "" - -#: C/gdm.xml:386(para) -msgid "GDM listens to UDP port 177 and will respond to QUERY and BROADCAST_QUERY requests by sending a WILLING packet to the originator." -msgstr "" - -#: C/gdm.xml:391(para) -msgid "GDM can also be configured to honor INDIRECT queries and present a host chooser to the remote display. GDM will remember the user's choice and forward subsequent requests to the chosen manager. GDM also supports an extension to the protocol which will make it forget the redirection once the user's connection succeeds. This extension is only supported if both daemons are GDM. It is transparent and will be ignored by XDM or other daemons that implement XDMCP." -msgstr "" - -#: C/gdm.xml:401(para) -msgid "Refer to the \"Security\" section for information about security concerns when using XDMCP." -msgstr "" - -#: C/gdm.xml:408(title) -msgid "Securing Remote Connection Through SSH" -msgstr "Säkra upp fjärranslutning genom SSH" - -#: C/gdm.xml:411(para) -msgid "As explained in the \"Security\" section, XDMCP does not use any kind of encryption and as such is inherently insecure. As XDMCP uses UDP as a network transport layer, it is not possible to simply secure it through an SSH tunnel." -msgstr "" - -#: C/gdm.xml:418(para) -msgid "To remedy this problem, gdm can be configured at compilation-time with the option --enable-secureremote, in which case gdm proposes as a built-in session a session called \"Secure Remote Connection\". Starting such a session allows the user to enter the name or the address of the host on which to connect; provided the said host runs an SSH server, the user then gets connected to the server on which the default X session is started and displayed on the local host." -msgstr "" - -#: C/gdm.xml:428(para) -msgid "Using this session allows a much more secure network connection and only necessitates to have an SSH server running on the remote host." -msgstr "" - -#: C/gdm.xml:435(title) -msgid "The GTK+ Greeter" -msgstr "GTK+-hälsaren" - -#: C/gdm.xml:437(para) -msgid "The GTK+ Greeter is the default graphical user interface that is presented to the user. The greeter contains a menu at the top, an optional face browser, an optional logo and a text entry widget. This greeter has full accessibility support, and should be used by users with accessibility needs." -msgstr "" - -#: C/gdm.xml:445(para) -msgid "The text entry field is used for entering logins, passwords, passphrases etc. <command>gdmlogin</command> is controlled by the underlying daemon and is basically stateless. The daemon controls the greeter through a simple protocol where it can ask the greeter for a text string with echo turned on or off. Similarly, the daemon can change the label above the text entry widget to correspond to the value the authentication system wants the user to enter." -msgstr "" - -#: C/gdm.xml:455(para) -msgid "The menu bar in the top of the greeter enables the user to select the requested session type/desktop environment, select an appropriate locale/language, halt/restart/suspend the computer, configure GDM (given the user knows the root password), change the GTK+ theme, or start an XDMCP chooser." -msgstr "" - -#: C/gdm.xml:463(para) -msgid "The greeter can optionally display a logo in the login window. The image must be in a format readable to the gdk-pixbuf library (GIF, JPG, PNG, TIFF, XPM and possibly others), and it must be readable to the GDM user. See the <filename>Logo</filename> option in the reference section below for details." -msgstr "" - -#: C/gdm.xml:473(title) -msgid "The Themed Greeter" -msgstr "" - -#: C/gdm.xml:475(para) -msgid "The Themed Greeter is a greeter interface that takes up the whole screen and is very themable. Themes can be selected and new themes can be installed by the configuration application or by setting the <filename>GraphicalTheme</filename> configuration key. The Themed Greeter is much like the GTK+ Greeter in that it is controlled by the underlying daemon, is stateless, and is controlled by the daemon using the same simple protocol." -msgstr "" - -#: C/gdm.xml:485(para) -msgid "The look and feel of this greeter is really controlled by the theme and so the user interface elements that are present may be different. The only thing that must always be present is the text entry field as described above in the GTK+ Greeter. The theme can include buttons that allow the user to select an appropriate locale/language, halt/restart/suspend the computer, configure GDM (given the user knows the root password), or start an XDMCP chooser." -msgstr "" - -#: C/gdm.xml:495(para) -msgid "You can always get a menu of available actions by pressing the F10 key. This can be useful if the theme doesn't provide certain buttons when you wish to do some action allowed by the GDM configuration." -msgstr "" - -#: C/gdm.xml:503(title) -msgid "The GDM Face Browser" -msgstr "" - -#: C/gdm.xml:505(para) -msgid "GDM supports a face browser which will display a list of users who can login and an icon for each user. This feature can be used with the GTK+ Greeter if the <filename>Browser</filename> configuration option is set to \"true\". This feature can be used with the Themed Greeter if using a GDM theme which includes a \"userlist\" item type is defined, such as \"happygnome-list\"" -msgstr "" - -#: C/gdm.xml:515(para) -msgid "By default, the face browser is disabled since revealing usernames on the login screen is not appropriate on many systems for security reasons. Also GDM requires some setup to specify which users should be visible. Setup can be done on the \"Users\" tab in <command>gdmsetup</command>. This feature is most practical to use on a system with a smaller number of users." -msgstr "" - -#: C/gdm.xml:524(para) -msgid "The icons used by GDM can be installed globally by the sysadmin or can be located in the users' home directories. If installed globally they should be in the <filename><share>/pixmaps/faces/</filename> directory (though this can be configured with the <filename>GlobalFaceDir</filename> configuration option) and the filename should be the name of the user, optionally with a <filename>.png</filename> appended. Face icons placed in the global face directory must be readable to the GDM user. However, the daemon, proxies user pictures to the greeter and thus those do not have be be readable by the \"gdm\" user, but root." -msgstr "" - -#: C/gdm.xml:537(para) -msgid "Users may run the <command>gdmphotosetup</command> command to configure the image to use for their userid. This program properly scales the file down if it is larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> configuration options and places the icon in a file called <filename>~/.face</filename>. Although <command>gdmphotosetup</command> scales user images automatically, this does not guarantee that user images are properly scaled since a user may create their <filename>~/.face</filename> file by hand." -msgstr "" - -#: C/gdm.xml:549(para) -msgid "GDM will first look for the user's face image in <filename>~/.face</filename>. If not found, it will try <filename>~/.face.icon</filename>. If still not found, it will use the value defined for \"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file. Lastly, it will try <filename>~/.gnome2/photo</filename> and <filename>~/.gnome/photo</filename> which are deprecated and supported for backwards compatibility." -msgstr "" - -#: C/gdm.xml:560(para) -msgid "If a user has no defined face image, GDM will use the \"stock_person\" icon defined in the current GTK+ theme. If no such image is defined, it will fallback to the image specified in the <filename>DefaultFace</filename> configuration option, normally <filename><share>/pixmaps/nobody.png</filename>." -msgstr "" - -#: C/gdm.xml:568(para) -msgid "Please note that loading and scaling face icons located in user home directories can be a very time-consuming task. Since it not practical to load images over NIS or NFS, GDM does not attempt to load face images from remote home directories. Furthermore, GDM will give up loading face images after 5 seconds of activity and will only display the users whose pictures it has gotten so far. The <filename>Include</filename> 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 <filename>GlobalFaceDir</filename> configuration option." -msgstr "" - -#: C/gdm.xml:584(para) -msgid "To control the users who get displayed in the face browser, there are a number of configuration options that can be used. If the <filename>IncludeAll</filename> option is set to true, then the password file will be scanned and all users will be displayed. If <filename>IncludeAll</filename> option is set to false, then the <filename>Include</filename> option should contain a list of users separated by commas. Only the users specified will be displayed. Any user listed in the <filename>Exclude</filename> option and users whose UID's is lower than <filename>MinimalUID</filename> will be filtered out regardless of the <filename>IncludeAll</filename> setting. <filename>IncludeAll</filename> is not recommended for systems where the passwords are loaded over a network (such as when NIS is used), since it can be very slow to load more than a small number of users over the network.." -msgstr "" - -#: C/gdm.xml:601(para) -msgid "When the browser is turned on, valid usernames on the computer are inherently exposed to a potential intruder. This may be a bad idea if you do not know who can get to a login screen. This is especially true if you run XDMCP (turned off by default)." -msgstr "" - -#: C/gdm.xml:610(title) -msgid "Logging" -msgstr "Loggning" - -#: C/gdm.xml:612(para) -msgid "GDM itself will use syslog to log errors or status. It can also log debugging information, which can be useful for tracking down problems if GDM is not working properly. This can be enabled in the configuration file." -msgstr "" - -#: C/gdm.xml:619(para) -msgid "Output from the various X servers is stored in the GDM log directory, which is configurable, but is usually <filename><var>/log/gdm/</filename>. The output from the session can be found in a file called <filename><display>.log</filename>. Four older files are also stored with <filename>.1</filename> through <filename>.4</filename> appended. These will be rotated as new sessions on that display are started. You can use these logs to view what the X server said when it started up." -msgstr "" - -#: C/gdm.xml:631(para) -msgid "The output from the user session is redirected to <filename>~/.xsession-errors</filename> before even the <filename>PreSession</filename> script is started. So it is not really necessary to redirect this again in the session setup script. As is usually done. If the user session lasted less then 10 seconds, GDM assumes that the session crashed and allows the user to view this file in a dialog before returning to the login screen. This way the user can view the session errors from the last session and correct the problem this way." -msgstr "" - -#: C/gdm.xml:643(para) -msgid "You can suppress the 10 second warning by returning code 66 from the <filename>Xsession</filename>script or from your session binary (the default <filename>Xsession</filename> script propagates those codes back). This is useful if you have some sort of special logins for which it is not an error to return less then 10 seconds later, or if you setup the session to already display some error message and the GDM message would be confusing and redundant." -msgstr "" - -#: C/gdm.xml:653(para) -msgid "The session output is piped through the GDM daemon and so the <filename>~/.xsession-errors</filename> file is capped at about 200 kilobytes by GDM to prevent a possible denial of service attack on the session. An app could perhaps on reading some wrong data print out warnings or errors on the stderr or stdout. This could perhaps fill up the user's home directory who would then have to log out and log back in to clear this. This could be especially nasty if quotas are set. GDM also correctly traps the XFSZ signal and stops writing the file, which would lead to killed sessions if the file was redirected in the old fashioned way from the script." -msgstr "" - -#: C/gdm.xml:666(para) -msgid "Note that some distributors seem to override the <filename>~/.xsession-errors</filename> redirection and do it themselves in their own Xsession script (set by the <filename>BaseXsession</filename> configuration key) which means that GDM will not be able to trap the output and cap this file. You also lose output from the <filename>PreSession</filename> 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 <filename>BaseXsession</filename> configuration key for more information, especially on how to handle multiple display managers using the same script." -msgstr "" - -#: C/gdm.xml:680(para) -msgid "Note that if the session is a failsafe session, or if GDM can't open this file for some reason, then a fallback file will be created in the <filename>/tmp</filename> directory named <filename>/tmp/xses-<user>.XXXXXX</filename> where the <filename>XXXXXX</filename> are some random characters." -msgstr "" - -#: C/gdm.xml:688(para) -msgid "If you run a system with quotas set, it would be good to delete the <filename>~/.xsession-errors</filename> in the <filename>PostSession</filename> script. Such that this log file doesn't unnecessarily stay around." -msgstr "" - -#: C/gdm.xml:697(title) -msgid "Accessing Files" -msgstr "Komma åt filer" - -#: C/gdm.xml:699(para) -msgid "In general GDM is very reluctant regarding reading/writing of user files (such as the <filename>~/.dmrc</filename>, <filename>~/.face</filename>, <filename>~/.xsession-errors</filename>, and <filename>~/.Xauthority</filename> files). For instance it refuses to access anything but regular files. Links, sockets and devices are ignored. The value of the <filename>RelaxPermissions</filename> parameter determines whether GDM should accept files writable by the user's group or others. These are ignored by default." -msgstr "" - -#: C/gdm.xml:711(para) -msgid "All operations on user files are done with the effective user id of the user. If the sanity check fails on the user's <filename>.Xauthority</filename> file, a fallback cookie is created in the directory specified by the <filename>UserAuthFBDir</filename> configuration setting (<filename>/tmp</filename> by default)." -msgstr "" - -#: C/gdm.xml:719(para) -msgid "Finally, the sysadmin can specify the maximum file size GDM should accept, and, if the face browser is enabled, a tunable maximum icon size is also enforced. On large systems it is still advised to turn off the face browser for performance reasons. Looking up icons in home directories, scaling and rendering face icons can take a long time." -msgstr "" - -#: C/gdm.xml:730(title) -msgid "GDM Performance" -msgstr "GDM-prestanda" - -#: C/gdm.xml:732(para) -msgid "To speed performance it is possible to build GDM so that it will preload libraries when GDM first displays a greeter program. This has been shown to speed first time login since these libraries can be loaded into memory while the user types in their username and password." -msgstr "" - -#: C/gdm.xml:740(para) -msgid "To use this feature, configure GDM with the <command>--with-prefetch</command> option. This will cause GDM to install the <command>gdmprefetch</command> program to the <filename>libexecdir</filename> directory, install the <filename>gdmprefetchlist</filename> to the <filename><etc>/gdm</filename> directory, and set the <filename>PreFetchProgram</filename> configuration variable so that the <command>gdmprefetch</command> program is called with the default <filename>gdmprefetchlist</filename> file. The default <filename>gdmprefetchlist</filename> 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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>, so that they can be included in future GDM releases." -msgstr "" - -#: C/gdm.xml:761(title) -msgid "Security" -msgstr "Säkerhet" - -#: C/gdm.xml:764(title) -msgid "PAM" -msgstr "PAM" - -#: C/gdm.xml:768(para) -msgid "GDM uses PAM for login authentication, though if your machine does not support PAM you can build GDM to work with the password database and the crypt library function." -msgstr "" - -#: C/gdm.xml:774(para) -msgid "PAM stands for Pluggable Authentication Module, and is used by most programs that request authentication on your computer. It allows the administrator to configure different authentication behavior for different programs." -msgstr "" - -#: C/gdm.xml:781(para) -msgid "Some GDM features (like turning on automatic login) may require that you update your PAM configuration. PAM configuration has different, but similar, interfaces on different operating systems, so check your pam.d or pam.conf man page for details. Be sure that you read the PAM documentation (e.g. pam.d/pam.conf man page) and are comfortable with the security implications of any changes you intend to make to your configuration." -msgstr "" - -#: C/gdm.xml:791(para) -msgid "If there is no entry for GDM in your system's PAM configuration file, then features like automatic login may not work. Not having an entry will cause GDM to use default behavior, conservative settings are recommended and probably shipped with your distribution." -msgstr "" - -#: C/gdm.xml:798(para) -msgid "If you wish to make GDM work with other types of authentication mechanisms (such as a SmartCard), then you should implement this by using a PAM service module for the desired authentication type rather than by trying to modify the GDM code directly. Refer to the PAM documentation on your system. This issue has been discussed on the <address><email>gdm-list@gnome.org</email></address> mail list, so you can refer to the list archives for more information." -msgstr "" - -#: C/gdm.xml:810(title) -msgid "The GDM User" -msgstr "GDM-användaren" - -#: C/gdm.xml:812(para) -msgid "For security reasons a dedicated user and group id are required for proper operation! The need to be able to write Xauth files is why user \"nobody\" is not appropriate for gdm." -msgstr "" - -#: C/gdm.xml:818(para) -msgid "The GDM daemon normally runs as root, as does the slave. However GDM should also have a dedicated user id and a group id which it uses for its graphical interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</command>. These are configured via the <filename>User</filename> and <filename>Group</filename> configuration options in the GDM configuration files. The user and group should be created before running \"make install\". By default GDM assumes the user and the group are called \"gdm\"." -msgstr "" - -#: C/gdm.xml:829(para) -msgid "This userid is used to run the GDM GUI programs required for login. All functionality that requires root authority is done by the GDM daemon process. This design ensures that if the GUI programs are somehow exploited, only the dedicated user privileges are available." -msgstr "" - -#: C/gdm.xml:836(para) -msgid "It should however be noted that the GDM user and group have some privileges that make them somewhat dangerous. For one, they have access to the X server authorization directory. It must be able to read and write Xauth keys to <filename><var>/lib/gdm</filename>. This directory should have root:gdm ownership and 1770 permissions. Running \"make install\" will set this directory to these values. The GDM daemon process will reset this directory to proper ownership/permissions if it is somehow not set properly." -msgstr "" - -#: C/gdm.xml:847(para) -msgid "The danger is that someone who gains the GDM user/group privileges can then connect to any session. So you should not, under any circumstances, make this some user/group which may be easy to get access to, such as the user <filename>nobody</filename>. Users who gain access to the \"gdm\" user could also modify the Xauth keys causing Denial-Of-Service attacks. Also if a person gains the ability to run programs as the user \"gdm\", it would be possible to snoop on running GDM processes, including usernames and passwords as they are being typed in." -msgstr "" - -#: C/gdm.xml:859(para) -msgid "Distributions and system administrators using GDM are expected to setup the dedicated user properly. It is recommended that this userid be configured to disallow login and to not have a default shell. Distributions and system administrators should set up the filesystem to ensure that the GDM user does not have read or write access to sensitive files." -msgstr "" - -#: C/gdm.xml:870(title) -msgid "X Server Authentication Scheme" -msgstr "" - -#: C/gdm.xml:872(para) -msgid "The X server authorization directory (the <filename>ServAuthDir</filename>) 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 <filename>root.gdm</filename> with the permissions of 1770. This way, only root and the GDM group have write access to this directory, but the GDM group cannot remove the root owned files from this directory, such as the X server authorization files." -msgstr "" - -#: C/gdm.xml:884(para) -msgid "GDM by default doesn't trust the X server authorization directory and treats it in the same way as the temporary directory with respect to creating files. This way someone breaking the GDM user cannot mount attacks by creating links in this directory. Similarly the X server log directory is treated safely, but that directory should really be owned and writable only by root." -msgstr "" - -#: C/gdm.xml:893(para) -msgid "GDM only supports the MIT-MAGIC-COOKIE-1 X server authentication scheme. Normally little is gained from the other schemes, and no effort has been made to implement them so far. Be especially careful about using XDMCP because the X server authentication cookie goes over the wire as clear text. If snooping is possible, then an attacker could simply snoop your authentication password as you log in, regardless of the authentication scheme being used. If snooping is possible and undesirable, then you should use ssh for tunneling an X connection rather then using XDMCP. You could think of XDMCP as a sort of graphical telnet, having the same security issues." -msgstr "" - -#: C/gdm.xml:906(para) -msgid "On the upside, GDM's random number generation is very conservative and GDM goes to extraordinary measures to truly get a 128 bit random number, using hardware random number generators (if available), plus the current time (in microsecond precision), a 20 byte array of pseudorandom numbers, process pid's, and other random information (possibly using <filename>/dev/audio</filename> or <filename>/dev/mem</filename> 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 <filename>UserAuthDir</filename> configuration key). So be careful about where you use remote X display." -msgstr "" - -#: C/gdm.xml:923(title) -msgid "Firewall Security" -msgstr "Brandväggssäkerhet" - -#: C/gdm.xml:925(para) -msgid "Even though GDM tries to outsmart potential attackers trying to take advantage of XDMCP, it is still advised that you block the XDMCP port (normally UDP port 177) on your firewall unless you really need it. GDM guards against DoS (Denial of Service) attacks, but the X protocol is still inherently insecure and should only be used in controlled environments. Also each remote connection takes up lots of resources, so it is much easier to DoS via XDMCP then a webserver." -msgstr "" - -#: C/gdm.xml:935(para) -msgid "It is also wise to block all of the X Server ports. These are TCP ports 6000 + the display number of course) on your firewall. Note that GDM will use display numbers 20 and higher for flexible on-demand servers." -msgstr "" - -#: C/gdm.xml:942(para) -msgid "X is not a very safe protocol for leaving on the net, and XDMCP is even less safe." -msgstr "" - -#: C/gdm.xml:949(title) -msgid "GDM Security With NFS" -msgstr "GDM-säkerhet med NFS" - -#: C/gdm.xml:951(para) -msgid "Note that NFS traffic really goes \"over the wire\" and thus can be snooped. When accessing the user's X authorization file (<filename>~/.Xauthority</filename>), 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 <filename>UserAuthFBDir</filename>, which by default is set to <filename>/tmp</filename>. This behavior can be changed by setting the <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false." -msgstr "" - -#: C/gdm.xml:965(title) -msgid "XDMCP Security" -msgstr "XDMCP-säkerhet" - -#: C/gdm.xml:967(para) -msgid "Even though your display is protected by cookies, XEvents and thus keystrokes typed when entering passwords will still go over the wire in clear text. It is trivial to capture these." -msgstr "" - -#: C/gdm.xml:973(para) -msgid "XDMCP is primarily useful for running thin clients such as in terminal labs. Those thin clients will only ever need the network to access the server, and so it seems like the best security policy to have those thin clients on a separate network that cannot be accessed by the outside world, and can only connect to the server. The only point from which you need to access outside is the server." -msgstr "" - -#: C/gdm.xml:982(para) -msgid "The above sections \"X Server Authentication Scheme\" and \"Firewall Security\" also contain important information about using XDMCP securely. The next section also discusses how to set up XDMCP access control." -msgstr "" - -#: C/gdm.xml:989(para) -msgid "To workaround the inherent insecurity of XDMCP, gdm proposes a default built-in session that uses SSH to encrypt the remote connection. See the section \"Securing remote connection through SSH\" above." -msgstr "" - -#: C/gdm.xml:997(title) -msgid "XDMCP Access Control" -msgstr "" - -#: C/gdm.xml:999(para) -msgid "XDMCP access control is done using TCP wrappers. It is possible to compile GDM without TCP wrappers however, so you should test your configuration and verify that they work." -msgstr "" - -#: C/gdm.xml:1005(para) -msgid "You should use the daemon name <command>gdm</command> in the <filename><etc>/hosts.allow</filename> and <filename><etc>/hosts.deny</filename> files. For example to deny computers from <filename>.evil.domain</filename> from logging in, then add" -msgstr "" - -#: C/gdm.xml:1012(screen) -#, no-wrap -msgid "" -"\n" -"gdm: .evil.domain\n" -msgstr "" -"\n" -"gdm: .ond.domän\n" - -#: C/gdm.xml:1015(para) -msgid "to <filename><etc>/hosts.deny</filename>. You may also need to add" -msgstr "" - -#: C/gdm.xml:1019(screen) -#, no-wrap -msgid "" -"\n" -"gdm: .your.domain\n" -msgstr "" -"\n" -"gdm: .din.domän\n" - -#: C/gdm.xml:1022(para) -msgid "to your <filename><etc>/hosts.allow</filename> if you normally disallow all services from all hosts. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" - -#: C/gdm.xml:1032(title) -msgid "Support for ConsoleKit" -msgstr "Stöd för ConsoleKit" - -#: C/gdm.xml:1034(para) -msgid "GDM includes support for publishing user login information with the user and login session accounting framework known as ConsoleKit. ConsoleKit is able to keep track of all the users currently logged in. In this respect, it can be used as a replacement for the utmp or utmpx files that are available on most Unix-like operating systems." -msgstr "" - -#: C/gdm.xml:1041(para) -msgid "When GDM is about to create a new login process for a user it will call a privileged method of ConsoleKit in order to open a new session for this user. At this time GDM also provides ConsoleKit with information about this user session such as: the user ID, the X11 Display name that will be associated with the session, the host-name from which the session originates (useful in the case of an XDMCP session), whether or not this session is local, etc. As the entity that initiates the user process, GDM is in a unique position know and to be trusted to provide these bits of information about the user session. The use of this privileged method is restricted by the use of D-Bus system message bus security policy." -msgstr "" - -#: C/gdm.xml:1052(para) -msgid "In the case where a user with an existing session and has authenticated at GDM and requests to resume that existing session GDM calls a privileged method of ConsoleKit to unlock that session. The exact details of what happens when the session receives this unlock signal is undefined and session-specific. However, most sessions will unlock a screensaver in response." -msgstr "" - -#: C/gdm.xml:1059(para) -msgid "When the user chooses to log out, or if GDM or the session quit unexpectedly the user session will be unregistered from ConsoleKit." -msgstr "" - -#: C/gdm.xml:1064(para) -msgid "If support for ConsoleKit is not desired it can be disabled at build time using the --with-console-kit=no option when running configure." -msgstr "" - -#: C/gdm.xml:1072(title) -msgid "Using gdmsetup To Configure GDM" -msgstr "Användning av gdmsetup för att konfigurera GDM" - -#: C/gdm.xml:1074(para) -msgid "The <command>gdmsetup</command> 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 <command>gdmsetup</command>. Editing the files by hand is explained in the \"Configuration\" section of this document. Note that <command>gdmsetup</command> does not support changing of all configuration variables, so it may be necessary to edit the files by hand for some configurations." -msgstr "" - -#: C/gdm.xml:1085(para) -msgid "The <command>gdmsetup</command> program has five tabs: Local, Remote, Accessibility, Security, and Users, described below. In parenthesis is information about which GDM configuration key is affected by each GUI choice. Refer to the \"Configuration\" section of this manual and the comments in the <share>/gdm/defaults.conf file for additional details about each key." -msgstr "" - -#: C/gdm.xml:1095(title) -msgid "Local Tab" -msgstr "Fliken Lokal" - -#: C/gdm.xml:1097(para) -msgid "The Local tab is used for controlling the appearance of GDM for local/static displays (non-XDMCP remote connections). The choices available in this tab depend on the setting of the \"Style\" combobox. This combobox is used to determine whether the \"Plain\" or \"Themed\" greeter GUI is used. The differences between these greeter programs are explained in the \"Overview\" section of this document." -msgstr "" - -#: C/gdm.xml:1107(para) -msgid "If the \"Style\" choice is \"Plain\", then GDM will use the <command>gdmlogin</command> program as the GUI (daemon/Greeter). When this choice is selected, <command>gdmsetup</command> allows the user to select whether the background is an image or solid color (greeter/BackgroundType). If image is selected, there is a file selection button to pick the image file (greeter/BackgroundImage) and a checkbox to scale the image to fit the screen (greeter/BackgroundImageScaleToFit). If solid color is selected, there is a button available to allow the color selection (greeter/BackgroundColor). Also, the user may select the logo image that appears in gdmlogin (greeter/Logo)." -msgstr "" - -#: C/gdm.xml:1121(para) -msgid "If the \"Style\" choice is \"Plain with face browser\", then the <command>gdmlogin</command> program is used as the GUI (daemon/Greeter) and the face browser is turned on (greeter/Browser). The Face Browser is explained in the Overview section. Otherwise, the choices are the same as when the \"Style\" choice is \"Plain\". Additional setup in the Users tab may be necessary to choose which users appear in the Face Browser." -msgstr "" - -#: C/gdm.xml:1131(para) -msgid "If the \"Style\" choice is \"Themed\", then the <command>gdmgreeter</command> program is used as the GUI (daemon/Greeter). When this choice is selected, <command>gdmsetup</command> allows the user to select the theme to be used (greeter/GraphicalTheme). Note that the checkbox to the left of the theme's name must be checked for a theme to be selected. Clicking on the theme, but not selecting the checkbox will highlight the theme and the \"Remove\" button can be used to delete the theme. Information about the theme's author and copyright are shown for the highlighted theme. The \"Add\" button can be used to add new themes to the system. To turn on the Face Browser, a theme which includes a Face Browser must be selected, such as happygnome-list. The \"Background color\" displayed when GDM starts (and if the theme has transparent elements) can also be selected (greeter/GraphicalThemedColor). The \"Theme\" combo box may be set to \"Random from selected\" if you want a random theme to be used for each login (greeter/GraphicalThemeRand and greeter/GraphicalThemes). To use random themes, select each theme that you wish to be used. By default this combobox is set to \"Selected only\", so that only a single theme can be selected and be used." -msgstr "" - -#: C/gdm.xml:1155(para) -msgid "Regardless of the \"Style\" choice, the user may also select whether the Actions menu is visible (greeter/SystemMenu), whether the Actions menu includes the choice to start <command>gdmsetup</command> (greeter/ConfigAvailable), and whether the Action menu includes the choice to start <command>gdmchooser</command> to run a remote XDMCP login session (greeter/ChooserButton). Note that the root password must be entered to start <command>gdmsetup</command> from the login screen if it is enabled. Also the Welcome message displayed for local sessions may be selected (greeter/DefaultWelcome and greeter/Welcome). The Welcome message can contain the character sequences described in the \"Text Node\" section of the \"Themed Greeter\" section of this manual." -msgstr "" - -#: C/gdm.xml:1172(title) -msgid "Remote Tab" -msgstr "Fliken Fjärr" - -#: C/gdm.xml:1174(para) -msgid "The Remote tab controls the appearance of the GDM for users logging in via XDMCP. By default XDMCP is disabled, and users should be comfortable with the XDMCP-related sections of the Security section of this document before enabling it. This tab includes a \"Style\" combobox which can be used to turn on XDMCP and control the appearance of GDM for remote users (gui/RemoteGreeter and xdmcp/Enable). This combobox may be set to \"Remote login disabled\" or \"Same as Local\". If the Local tab is set to \"Plain\" or \"Plain with Face Browser\", then the user may also select \"Themed\". If the Local tab is set to \"Themed\", then the user may also select \"Plain\" or \"Plain with face browser\". It is recommended that the \"Plain\" GUI be used for remote connections since it is more lightweight and tends to have better performance across a network." -msgstr "" - -#: C/gdm.xml:1192(para) -msgid "If Remote login is enabled, then the user can specify the remote Welcome Message to be displayed (greeter/DefaultRemoteWelcome and greeter/RemoteWelcome). This welcome message is separate from the Local welcome message and can have a different value. The Welcome message can contain the character sequences described in the \"Text Node\" section of the \"Themed Greeter\" section of this manual." -msgstr "" - -#: C/gdm.xml:1202(para) -msgid "If the \"Style\" choice is \"Same as Local\" and the local selection is \"Plain\" or \"Plain with face browser\", then the user may select whether background images should be displayed for remote logins (greeter/BackgroundRemoteOnlyColor)." -msgstr "" - -#: C/gdm.xml:1210(para) -msgid "If the \"Style\" choice is enabled and set to a different value than the Local tab, then the user has the same configuration choices as found on the Local tab except that the System Menu choices are not available since this is never available for remote logins for security purposes." -msgstr "" - -#: C/gdm.xml:1218(para) -msgid "If Remote login is enabled, there is a \"Configure XDMCP\" button which displays a dialog allowing the user to set XDMCP configuration, including whether indirect requests are honored (xdmcp/HonorIndirect), UDP port (xdmcp/Port), maximum pending requests (xdmcp/MaxPending), maximum pending indirect requests (xmdcp/MaxPendingIndirect), maximum remote sessions (xdmcp/MaxSessions), maximum wait time (xdmcp/MaxWait), maximum indirect wait time (xdmcp/MaxWaitIndirect), displays per host (xdmcp/DisplaysPerHost), and ping interval (xdmcp/PingIntervalSeconds). The default settings are standard settings and should only be changed by someone who understands the ramifications of the change." -msgstr "" - -#: C/gdm.xml:1234(title) -msgid "Accessibility Tab" -msgstr "Fliken Tillgänglighet" - -#: C/gdm.xml:1236(para) -msgid "The Accessibility tab is used to turn on Accessibility features in GDM. \"Enable accessible login\" (daemon/AddGtkModules and daemon/GtkModulesList) turns on GDM's gesture listeners which are explained in the \"Accessibility\" section of this document. There is also a checkbox to allow users to change the theme when using the Plain greeter (gui/AllowGtkThemeChange). This feature allows GDM users to switch the theme to the HighContrast or LowContrast themes if needed. The user may also select whether GDM should play a sound when the login screen is ready, when login is successful and when login has failed. File chooser buttons are used to select the sound file to be played, and the \"Play\" button can be used to sample the sound." -msgstr "" - -#: C/gdm.xml:1253(title) -msgid "Security Tab" -msgstr "Fliken Säkerhet" - -#: C/gdm.xml:1255(para) -msgid "The Security tab allows the user to turn on Automatic and Timed login, which user is logged in via an automatic or timed login, and the timed login delay (daemon/AutomaticLoginEnable, daemon/AutomaticLogin, daemon/TimedLoginEnable, daemon/TimedLogin, and daemon/TimedLoginDelay). If automatic login is turned on, then the specified user will immediately log in on reboot without GDM asking for username/password. If the user logs out of their session, GDM will start and ask for username and password to log back in. If TimedLogin is turned on, then GDM will log in to the specified user after a specified number of seconds. The user may enable Timed Login for remote (XDMCP) connections by checking the \"Allow remote timed logins\" checkbox." -msgstr "" - -#: C/gdm.xml:1270(para) -msgid "On this tab, the user may select whether the system administrator user can log in, and whether the system administrator user can log in via remote (XDMCP) connections (security/AllowRoot and security/AllowRemoteRoot). The user may turn on GDM debug (debug/Enable) which causes debug messages to be sent to the system log. Debug should only be used when diagnosing a problem and not be left on when not needed. The \"Deny TCP connections to Xserver\" choice will disable X forwarding if selected (security/DisallowTCP). A login retry delay (security/RetryDelay) can be set to cause GDM to wait a number of seconds after a failed login." -msgstr "" - -#: C/gdm.xml:1283(para) -msgid "The \"Configure X Server\" button can be used to specify how GDM manages each display. The \"Servers\" combobox shows what server definitions are available (Standard, Terminal, and Chooser by default). Refer to the \"X Server Definitions\" section of the \"Configuration\" section for more information about how to create new Server Definitions." -msgstr "" - -#: C/gdm.xml:1292(para) -msgid "For any server type, the user may modify the \"Server Name\" (server/name), the \"Command\" (server/command) to be used to launch the Xserver, whether the server type will \"Launch\" (server/chooser) the greeter or chooser GUI after starting the Xserver, whether GDM handles this type (normally only set to false when logging into a Terminal session type), and whether the session type supports \"Flexible\" (server/flexible) sessions." -msgstr "" - -#: C/gdm.xml:1302(para) -msgid "The \"Servers To Start\" section shows what server type is displayed for each display on the machine. Users may click on the \"Add/Modify\" button to add a new display to the list or to modify a selected display. This simply corresponds each physical display with the Server Definition to be used for managing that display. The \"Remove\" button may be used to remove a display from the list." -msgstr "" - -#: C/gdm.xml:1314(title) -msgid "Users Tab" -msgstr "Fliken Användare" - -#: C/gdm.xml:1316(para) -msgid "The Users tab controls which users appear in the Face Browser. If the \"Include all users from /etc/password\" checkbox is selected, then all users (with a userid above greeter/MinimalUID and not in the Exclude list) are displayed. If this checkbox is not selected, then users must be added to the \"Include\" list. Users in the \"Exclude\" list are never displayed. The \"Add\" and \"Remove\" buttons are used to add a new user to the list or remove a selected user from the list. The \"Apply User Changes\" button must be pressed after the \"Include\" and \"Exclude\" lists have been modified. The left and right arrow buttons between the \"Include\" and \"Exclude\" lists can be used to move a selected user from one list to the other." -msgstr "" - -#: C/gdm.xml:1334(title) -msgid "Configuration" -msgstr "Konfiguration" - -#: C/gdm.xml:1336(para) -msgid "GDM has powerful configuration management. System configuration is stored in <filename><share>/gdm/defaults.conf</filename> and the intention is that this file can be stored on a shared filesystem so that sysadmins can have a single file to modify to control configuration for multiple machines. Also GDM distributions may patch this file on update to improve usability, improve security, etc. Configuration may be customized for a specific machine by editing the <filename><etc>/gdm/custom.conf</filename> file to include an override for a specific key. Those parameters in the \"gui\", \"greeter\" sections, and the security/PamStack key may be customized per-display by specifying them in a file named <filename><etc>/gdm/custom.conf<display num></filename>. For example, configuration overrides for display \":103\" would be stored in the file <filename><etc>/gdm/custom.conf:0</filename>. Per-display configuration is supported in GDM 2.14.6 and later." -msgstr "" - -#: C/gdm.xml:1354(para) -msgid "The <command>gdmsetup</command> is a GUI program you can use to edit the GDM configuration. This program may also be launched directly from the login screen if the greeter/ConfigAvailable key is set to \"true\" Not all keys in the GDM configuration file are supported in the GUI, so you may need to edit the configuration files by hand to edit these keys. If you believe running root-owned GUI's causes security risk, then you would want to always edit the files by hand. This program does not support setting per-display configuration, so per-display configuration files must be set up by hand." -msgstr "" - -#: C/gdm.xml:1366(para) -msgid "Distributions should edit the <filename><share>/gdm/defaults.conf</filename> file to establish the default values so these are preserved as defaults and not modified by users modifying their personal configuration file <filename><etc>/gdm/custom.conf</filename>." -msgstr "" - -#: C/gdm.xml:1374(para) -msgid "If you want to change configuration by hand, edit the <filename><etc>/gdm/custom.conf</filename> file and make sure the keyname=value pair you want is included in the appropriate section. For example, to change the \"Greeter\" key in the \"daemon\" section, make sure the daemon section of the <filename><etc>/gdm/custom.conf</filename> file has the value like in this example." -msgstr "" - -#: C/gdm.xml:1384(screen) -#, no-wrap -msgid "" -"\n" -"[daemon]\n" -"Greeter=/usr/lib/gdmgreeter\n" -msgstr "" -"\n" -"[daemon]\n" -"Greeter=/usr/lib/gdmgreeter\n" - -#: C/gdm.xml:1389(para) -msgid "The configuration files (especially the <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename> files) contain useful comments and examples, so read them for more information about changing your configuration. GDM considers lines that start with the \"#\" character a comment, and these lines will be ignored by GDM. Some keys in the <filename><share>/gdm/defaults.conf</filename> are commented out while others are set. Commented out values show the default value." -msgstr "" - -#: C/gdm.xml:1401(para) -msgid "The <filename><share>/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename><etc>/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename><etc>/gdm/custom.conf</filename> file override the values in the main <filename><share>/gdm/defaults.conf</filename> file. Running the <command>gdmsetup</command> command will cause the <filename><etc>/gdm/custom.conf</filename> to be modified with the user's configuration choices and will cause any running GDM GUI programs to automatically update. Previous to version 2.13.0.4 GDM only supported the <filename><etc>/gdm/gdm.conf</filename> file, so if using an older version of GDM just edit that file directly." -msgstr "" - -#: C/gdm.xml:1417(para) -msgid "The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may also be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used." -msgstr "" - -#: C/gdm.xml:1426(para) -msgid "<filename><share>/gdm/factory-defaults.conf</filename> is the configuration file as shipped with the daemon. This can be useful for to see if the <filename><share>/gdm/defaults.conf</filename> file has been changed." -msgstr "" - -#: C/gdm.xml:1433(para) -msgid "The other GDM configuration files are located, by default, in the <filename><etc>/gdm/</filename> folder or its subdirectories. However, the location of all configuration files are defined in the GDM configuration files, so the sysadmin may choose to locate these files in any location." -msgstr "" - -#: C/gdm.xml:1441(para) -msgid "This is a listing of the config directory contents:" -msgstr "" - -#: C/gdm.xml:1445(screen) -#, no-wrap -msgid "" -"\n" -"locale.alias\n" -"Xsession\n" -"XKeepsCrashing\n" -"modules/\n" -"Init/\n" -"PostLogin/\n" -"PreSession/\n" -"PostSession/\n" -msgstr "" -"\n" -"locale.alias\n" -"Xsession\n" -"XKeepsCrashing\n" -"modules/\n" -"Init/\n" -"PostLogin/\n" -"PreSession/\n" -"PostSession/\n" - -#: C/gdm.xml:1456(para) -msgid "<filename>locale.alias</filename> is a file which looks much like the system locale alias but in fact it is not the same. These are the languages that are available on your system. All the languages are still tested to see if they actually exist before presenting them to the user." -msgstr "" - -#: C/gdm.xml:1464(para) -msgid "<filename>Xsession</filename> 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 <filename>desktop</filename> file associated with the session the user has picked. Some sessions may start the user's session via a different mechanism than the <filename>Xsession</filename> script, so please check the appropriate <filename>desktop</filename> before assuming a session startup issue is being caused by this file." -msgstr "" - -#: C/gdm.xml:1475(para) -msgid "<filename>XKeepsCrashing</filename> is a script which gets run when the X server keeps crashing and we cannot recover. The shipped default script will work with most Linux distributions and can run the X configuration application provided the person on the console knows the root password." -msgstr "" - -#: C/gdm.xml:1483(para) -msgid "Accessibility modules are configured in the <filename>modules/</filename> 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 <filename>factory</filename> in their name, and those files are not read, they are just there for you so you can always revert to default config." -msgstr "" - -#: C/gdm.xml:1492(para) -msgid "Files describing available GDM session follow the freedesktop.org desktop file specification and are <filename>.desktop</filename>-style files are installed to <filename><etc>/X11/sessions/</filename>. This directory is also read by the KDE desktop manager (KDM) for common configuration. Next the directory <filename><share>/gdm/BuiltInSessions/</filename> is read for GDM specific built-in sessions (KDM hardcodes these at time of this writing). Lastly the default setup will also read <filename><share>/xsessions/</filename> (which should be <filename><share>/xsessions/</filename> if you really wish to cooperate with KDM) where desktop packages can install their session files. The directories under the <filename><etc></filename> 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 <filename>SessionDesktopDir</filename> configuration key for changing the paths. It used to be that GDM stored its built in sessions in <filename><etc>/dm/Sessions/</filename> but this is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the <filename><etc>/dm/Sessions/</filename> was being read." -msgstr "" - -#: C/gdm.xml:1515(para) -msgid "A session can be disabled (if it was installed in <filename><share>/xsessions/</filename>) by adding an identically named <filename>.desktop</filename> to one of the directories earlier in the path (likely <filename><etc>/X11/sessions</filename>) and using <filename>Hidden=true</filename> in that file." -msgstr "" - -#: C/gdm.xml:1524(title) -msgid "The Script Directories" -msgstr "Skriptkatalogerna" - -#: C/gdm.xml:1526(para) -msgid "In this section we will explain the <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> and <filename>PostSession</filename> directories as they are very similar." -msgstr "" - -#: C/gdm.xml:1532(para) -msgid "When the X server has been successfully started, GDM will try to run the script called <filename>Init/<displayname></filename>. I.e. <filename>Init/:0</filename> for the first local display. If this file is not found, GDM will attempt to to run <filename>Init/<hostname></filename>. I.e. <filename>Init/somehost</filename>. If this still is not found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins or <filename>Init/Flexi</filename> for all on demand flexible displays. If none of the above were found, GDM will run <filename>Init/Default</filename>. The script will be run as root and GDM blocks until it terminates. Use the <filename>Init/*</filename> script for applications that are supposed to run alongside with the GDM login window. xconsole for instance. Commands to set the background etc. go in this file too." -msgstr "" - -#: C/gdm.xml:1550(para) -msgid "It is up to the sysadmin to decide whether clients started by the Init script should be killed before starting the user session. This is controlled with the <filename>KillInitClients</filename> configuration option." -msgstr "" - -#: C/gdm.xml:1557(para) -msgid "When the user has been successfully authenticated GDM tries the scripts in the <filename>PostLogin</filename> directory in the same manner as for the <filename>Init</filename> 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 <filename>pam_mount</filename> module if you can for this). You have the <filename>$USER</filename> and <filename>$DISPLAY</filename> environment variables set for this script, and again it is run as root. The script should return 0 on success as otherwise the user won't be logged in. This is not true for failsafe session however." -msgstr "" - -#: C/gdm.xml:1571(para) -msgid "After the user session has been setup from the GDM side of things, GDM will run the scripts in the <filename>PreSession</filename> directory, again in the same manner as the <filename>Init</filename> directory. Use this script for local session management or accounting stuff. The <filename>$USER</filename> environment variable contains the login of the authenticated user and <filename>$DISPLAY</filename> 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 <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." -msgstr "" - -#: C/gdm.xml:1586(para) -msgid "After this the base <filename>Xsession</filename> 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 <filename>Exec=</filename> line in the <filename>.desktop</filename> files in the path specified by <filename>SessionDesktopDir</filename>. Usually this path is <filename><etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/xsessions/</filename>. The first found file is used. The user either picks from these sessions or GDM will look inside the file <filename>~/.dmrc</filename> for the stored preference." -msgstr "" - -#: C/gdm.xml:1599(para) -msgid "This script should really load the user's profile and generally do all the voodoo that is needed to launch a session. Since many systems reset the language selections done by GDM, GDM will also set the <filename>$GDM_LANG</filename> 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 <filename>$GDM_LANG</filename> is not set." -msgstr "" - -#: C/gdm.xml:1609(para) -msgid "When the user terminates his session, the <filename>PostSession</filename> script will be run. Again operation is similar to <filename>Init</filename>, <filename>PostLogin</filename> and <filename>PreSession</filename>. Again the script will be run with root privileges, the slave daemon will block and the <filename>$USER</filename> environment variable will contain the name of the user who just logged out and <filename>$DISPLAY</filename> will be set to the display the user used, however note that the X server for this display may already be dead and so you shouldn't try to access it. Also <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." -msgstr "" - -#: C/gdm.xml:1624(para) -msgid "Note that the <filename>PostSession</filename> script will be run even when the display fails to respond due to an I/O error or similar. Thus, there is no guarantee that X applications will work during script execution." -msgstr "" - -#: C/gdm.xml:1631(para) -msgid "Except for the <filename>Xsession</filename> script all of these scripts will also have the environment variable <filename>$RUNNING_UNDER_GDM</filename> set to <filename>yes</filename>, so that you could perhaps use similar scripts for different display managers. The <filename>Xsession</filename> will always have the <filename>$GDMSESSION</filename> set to the basename of the session that the user chose to run without the <filename>.desktop</filename> extension. In addition <filename>$DESKTOP_SESSION</filename> is also set to the same value and in fact this will also be set by KDM in future versions." -msgstr "" - -#: C/gdm.xml:1645(para) -msgid "Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> or <filename>PostSession</filename> scripts are necessary and can be left out. The <filename>Xsession</filename> script is however required as well as at least one session <filename>.desktop</filename> file." -msgstr "" - -#: C/gdm.xml:1655(title) -msgid "The Configuration Files - <filename>defaults.conf</filename> and <filename>custom.conf</filename>" -msgstr "" - -#: C/gdm.xml:1658(para) -msgid "GDM uses two configuration files: <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename>. The <filename><share>/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename><etc>/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename><etc>/gdm/custom.conf</filename> file override the values in the <filename><share>/gdm/defaults.conf</filename> file. If a configuration option is not defined in either file, GDM will default to the value described in the comments in the <filename><share>/gdm/defaults.conf</filename> file." -msgstr "" - -#: C/gdm.xml:1674(para) -msgid "Running the <command>gdmsetup</command> command will cause the <filename><etc>/gdm/custom.conf</filename> to be modified with the user's configuration choices." -msgstr "" - -#: C/gdm.xml:1680(para) -msgid "Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</filename> existed. If upgrading to the new version of GDM, install will check to see if your <filename><etc>/gdm/gdm.conf</filename> file is different than your <filename><etc>/gdm/factory-gdm.conf</filename> file. If so, your <filename><etc>/gdm/gdm.conf</filename> file will be automatically copied to <filename><etc>/gdm/custom.conf</filename> to preserve any configuration changes." -msgstr "" - -#: C/gdm.xml:1692(para) -msgid "The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may instead be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used." -msgstr "" - -#: C/gdm.xml:1701(para) -msgid "Both configuration files are divided into sections each containing variables that define the behavior for a specific part of the GDM suite. Refer to the comments in the <filename><share>/gdm/defaults.conf</filename> file for additional information about each configuration setting." -msgstr "" - -#: C/gdm.xml:1709(para) -msgid "The <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename> files follow the standard <filename>.ini</filename> style configuration file syntax. Keywords in brackets define sections, strings before an equal sign (=) are variables and the data after equal sign represents their value. Empty lines or lines starting with the hash mark (#) are ignored. The graphical configurator will try to preserve both comments (lines with a hash mark) and the overall structure of the file so you can intermix using the GUI or hand editing the configuration file." -msgstr "" - -#: C/gdm.xml:1722(title) -msgid "Daemon Configuration" -msgstr "Konfiguration av demonerna" - -#: C/gdm.xml:1725(title) -msgid "[daemon]" -msgstr "[daemon]" - -#: C/gdm.xml:1728(term) -msgid "AddGtkModules" -msgstr "AddGtkModules" - -#: C/gdm.xml:1730(synopsis) -#, no-wrap -msgid "AddGtkModules=false" -msgstr "AddGtkModules=false" - -#: C/gdm.xml:1731(para) -msgid "If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</command> to be launched with additional Gtk+ modules. This is useful when extra features are required such as accessible login. Note that only \"trusted\" modules should be used to minimize security issues." -msgstr "" - -#: C/gdm.xml:1738(para) -msgid "If true, then the registry daemon <command>at-spi-registryd</command> will be launched by <command>gdmgreeter</command> or <command>gdmlogin</command> starting with version GDM 2.17." -msgstr "" - -#: C/gdm.xml:1744(para) -msgid "Usually this is used for accessibility modules. The modules which are loaded are specified with the <filename>GtkModulesList</filename> key." -msgstr "" - -#: C/gdm.xml:1753(term) -msgid "AlwaysRestartServer" -msgstr "AlwaysRestartServer" - -#: C/gdm.xml:1755(synopsis) -#, no-wrap -msgid "AlwaysRestartServer=false" -msgstr "AlwaysRestartServer=false" - -#: C/gdm.xml:1756(para) -msgid "If true, then gdm never tries to reuse existing X servers by reinitializing them. It will just kill the existing X server and start over. Normally, just reinitializing is a nicer way to go but if the X server memory usage keeps growing this may be a safer option. On Solaris, this value is always true, and this configuration setting is ignored." -msgstr "" - -#: C/gdm.xml:1768(term) -msgid "AlwaysLoginCurrentSession" -msgstr "AlwaysLoginCurrentSession" - -#: C/gdm.xml:1770(synopsis) -#, no-wrap -msgid "AlwaysLoginCurrentSession=true" -msgstr "AlwaysLoginCurrentSession=true" - -#: C/gdm.xml:1771(para) -msgid "If true, then when the user logs in and already has an existing session, then they are connected to that session rather than starting a new session. This only works for sessions running on VTs (Virtual Terminals) started with gdmflexiserver, and not with XDMCP. Note that VTs are not supported on all operating systems." -msgstr "" - -#: C/gdm.xml:1783(term) -msgid "AutomaticLoginEnable" -msgstr "AutomaticLoginEnable" - -#: C/gdm.xml:1785(synopsis) -#, no-wrap -msgid "AutomaticLoginEnable=false" -msgstr "AutomaticLoginEnable=false" - -#: C/gdm.xml:1786(para) -msgid "If the user given in AutomaticLogin should be logged in upon first bootup. No password will be asked. This is useful for single user workstations where local console security is not an issue. Also could be useful for public terminals, although there see <filename>TimedLogin</filename>." -msgstr "" - -#: C/gdm.xml:1797(term) -msgid "AutomaticLogin" -msgstr "AutomaticLogin" - -#: C/gdm.xml:1799(synopsis) -#, no-wrap -msgid "AutomaticLogin=" -msgstr "AutomaticLogin=" - -#: C/gdm.xml:1800(para) -msgid "This user should be automatically logged in on first bootup. AutomaticLoginEnable must be true and this must be a valid user for this to happen. \"root\" can never be autologged in however and gdm will just refuse to do it even if you set it up." -msgstr "" - -#: C/gdm.xml:1808(para) -msgid "The following control chars are recognized within the specified name:" -msgstr "" - -#: C/gdm.xml:1813(para) -#: C/gdm.xml:3821(para) -msgid "%%— the `%' character" -msgstr "" - -#: C/gdm.xml:1817(para) -msgid "%d — display's name" -msgstr "" - -#: C/gdm.xml:1821(para) -msgid "%h — display's hostname" -msgstr "" - -#: C/gdm.xml:1825(para) -msgid "Alternatively, the name may end with a vertical bar |, the pipe symbol. The name is then used as a application to execute which returns the desired username on standard output. If an empty or otherwise invalid username is returned, automatic login is not performed. This feature is typically used when several remote displays are used as internet kiosks, with a specific user to automatically login for each display." -msgstr "" - -#: C/gdm.xml:1838(term) -msgid "BaseXsession" -msgstr "BaseXsession" - -#: C/gdm.xml:1840(synopsis) -#, no-wrap -msgid "BaseXsession=<etc>/gdm/Xsession" -msgstr "BaseXsession=<etc>/gdm/Xsession" - -#: C/gdm.xml:1841(para) -msgid "This is the base X session file. When a user logs in, this script will be run with the selected session as the first argument. The selected session will be the <filename>Exec=</filename> from the <filename>.desktop</filename> file of the session." -msgstr "" - -#: C/gdm.xml:1849(para) -msgid "If you wish to use the same script for several different display managers, and wish to have some of the script run only for GDM, then you can check the presence of the <filename>GDMSESSION</filename> environmental variable. This will always be set to the basename of <filename>.desktop</filename> (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 <filename>GDM_LANG</filename>, but that is only set when the user picks a non-system default language." -msgstr "" - -#: C/gdm.xml:1862(para) -msgid "This script should take care of doing the \"login\" for the user and so it should source the <filename><etc>/profile</filename> and friends. The standard script shipped with GDM sources the files in this order: <filename><etc>/profile</filename> then <filename>~/.profile</filename> then <filename><etc>/xprofile</filename> and finally <filename>~/.xprofile</filename>. Note that different distributions may change this however. Sometimes users personal setup will be in <filename>~/.bash_profile</filename>, however broken that is." -msgstr "" - -#: C/gdm.xml:1879(term) -msgid "Chooser" -msgstr "Chooser" - -#: C/gdm.xml:1881(synopsis) -#, no-wrap -msgid "Chooser=<bin>/gdmchooser" -msgstr "Chooser=<bin>/gdmchooser" - -#: C/gdm.xml:1882(para) -msgid "Full path and name of the chooser executable followed by optional arguments." -msgstr "" - -#: C/gdm.xml:1890(term) -msgid "Configurator" -msgstr "Configurator" - -#: C/gdm.xml:1892(synopsis) -#, no-wrap -msgid "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" -msgstr "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" - -#: C/gdm.xml:1893(para) -msgid "The pathname to the configurator binary. If the greeter <filename>ConfigAvailable</filename> option is set to true then run this binary when somebody chooses Configuration from the Actions menu. Of course GDM will first ask for root password however. And it will never allow this to happen from a remote display." -msgstr "" - -#: C/gdm.xml:1905(term) -msgid "ConsoleCannotHandle" -msgstr "ConsoleCannotHandle" - -#: C/gdm.xml:1907(synopsis) -#, no-wrap -msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" -msgstr "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" - -#: C/gdm.xml:1908(para) -msgid "These are the languages that the console cannot handle because of font issues. Here we mean the text console, not X. This is only used when there are errors to report and we cannot start X." -msgstr "" - -#: C/gdm.xml:1918(term) -msgid "ConsoleNotify" -msgstr "ConsoleNotify" - -#: C/gdm.xml:1920(synopsis) -#, no-wrap -msgid "ConsoleNotify=true" -msgstr "ConsoleNotify=true" - -#: C/gdm.xml:1921(para) -msgid "If false, gdm will not display a message dialog on the console when an error happens." -msgstr "" - -#: C/gdm.xml:1929(term) -msgid "DefaultPath" -msgstr "DefaultPath" - -#: C/gdm.xml:1931(synopsis) -#, no-wrap -msgid "DefaultPath=defaultpath (value set by configure)" -msgstr "DefaultPath=standardsökväg (värdet ställs in av configure)" - -#: C/gdm.xml:1932(para) -msgid "Specifies the path which will be set in the user's session. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains \"ROOT=<pathname>\". If the <filename>/etc/default/login</filename> file exists, but contains no value for ROOT, the value as defined in the GDM configuration will be be used." -msgstr "" - -#: C/gdm.xml:1945(term) -msgid "DefaultSession" -msgstr "DefaultSession" - -#: C/gdm.xml:1947(synopsis) -#, no-wrap -msgid "DefaultSession=gnome.desktop" -msgstr "DefaultSession=gnome.desktop" - -#: C/gdm.xml:1948(para) -msgid "The session that is used by default if the user does not have a saved preference and has picked 'Last' from the list of sessions. Note that 'Last' need not be displayed, see the <filename>ShowLastSession</filename> key." -msgstr "" - -#: C/gdm.xml:1959(term) -msgid "DisplayInitDir" -msgstr "DisplayInitDir" - -#: C/gdm.xml:1961(synopsis) -#, no-wrap -msgid "DisplayInitDir=<etc>/gdm/Init" -msgstr "DisplayInitDir=<etc>/gdm/Init" - -#: C/gdm.xml:1962(para) -msgid "Directory containing the display init scripts. See the ``The Script Directories'' section for more info." -msgstr "" - -#: C/gdm.xml:1970(term) -msgid "DisplayLastLogin" -msgstr "DisplayLastLogin" - -#: C/gdm.xml:1972(synopsis) -#, no-wrap -msgid "DisplayLastLogin=true" -msgstr "DisplayLastLogin=true" - -#: C/gdm.xml:1973(para) -msgid "If true then the last login information is printed to the user before being prompted for password. While this gives away some info on what users are on a system, it on the other hand should give the user an idea of when they logged in and if it doesn't seem kosher to them, they can just abort the login and contact the sysadmin (avoids running malicious startup scripts). This was added in version 2.5.90.0." -msgstr "" - -#: C/gdm.xml:1982(para) -msgid "This is for making GDM conformant to CSC-STD-002-85, although that is purely theoretical now. Someone should read that spec and ensure that this actually conforms (in addition to other places in GDM). See <filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> for more info." -msgstr "" - -#: C/gdm.xml:1994(term) -msgid "DoubleLoginWarning" -msgstr "DoubleLoginWarning" - -#: C/gdm.xml:1996(synopsis) -#, no-wrap -msgid "DoubleLoginWarning=true" -msgstr "DoubleLoginWarning=true" - -#: C/gdm.xml:1997(para) -msgid "If true, GDM will warn the user if they are already logged in on another virtual terminal. On systems where GDM supports checking the X virtual terminals, GDM will let the user switch to the previous login virtual terminal instead of logging in." -msgstr "" - -#: C/gdm.xml:2007(term) -msgid "DynamicXServers" -msgstr "DynamicXServers" - -#: C/gdm.xml:2009(synopsis) -#, no-wrap -msgid "DynamicXServers=false" -msgstr "DynamicXServers=false" - -#: C/gdm.xml:2010(para) -msgid "If true, the GDM daemon will honor requests to manage displays via the <filename>/tmp/.gdm_socket</filename> socket connection. Displays can be created, started, and deleted with the appropriate commands. The <filename>gdmdynamic</filename> command is a convenient method to send these messages." -msgstr "" - -#: C/gdm.xml:2022(term) -msgid "FailsafeXServer" -msgstr "FailsafeXServer" - -#: C/gdm.xml:2024(synopsis) -#, no-wrap -msgid "FailsafeXServer=" -msgstr "FailsafeXServer=" - -#: C/gdm.xml:2025(para) -msgid "An X command line in case we can't start the normal X server. should probably be some sort of a script that runs an appropriate low resolution X server that will just work. This is tried before the <filename>XKeepsCrashing</filename> script is run." -msgstr "" - -#: C/gdm.xml:2036(term) -msgid "FirstVT" -msgstr "FirstVT" - -#: C/gdm.xml:2038(synopsis) -#, no-wrap -msgid "FirstVT=7" -msgstr "FirstVT=7" - -#: C/gdm.xml:2039(para) -msgid "On systems where GDM supports automatic VT (virtual terminal) allocation, this is the first vt to try. Usually standard text logins are run on the lower vts. See also <filename>VTAllocation</filename>." -msgstr "" - -#: C/gdm.xml:2049(term) -msgid "FlexibleXServers" -msgstr "FlexibleXServers" - -#: C/gdm.xml:2051(synopsis) -#, no-wrap -msgid "FlexibleXServers=5" -msgstr "FlexibleXServers=5" - -#: C/gdm.xml:2052(para) -msgid "The maximum number of allowed flexible displays. These are displays that can be run using the <filename>/tmp/.gdm_socket</filename> socket connection. This is used for both full flexible displays and for Xnest displays." -msgstr "" - -#: C/gdm.xml:2063(term) -msgid "FlexiReapDelayMinutes" -msgstr "FlexiReapDelayMinutes" - -#: C/gdm.xml:2065(synopsis) -#, no-wrap -msgid "FlexiReapDelayMinutes=5" -msgstr "FlexiReapDelayMinutes=5" - -#: C/gdm.xml:2066(para) -msgid "After how many minutes of inactivity at the login screen should a flexi display be reaped. This is only in effect before a user logs in. Also it does not affect the Xnest flexiservers. To turn off this behavior set this value to 0. This was added in version 2.5.90.0." -msgstr "" - -#: C/gdm.xml:2077(term) -msgid "Greeter" -msgstr "Greeter" - -#: C/gdm.xml:2079(synopsis) -#, no-wrap -msgid "Greeter=<bin>/gdmlogin" -msgstr "Greeter=<bin>/gdmlogin" - -#: C/gdm.xml:2080(para) -msgid "Full path and name of the greeter executable followed by optional arguments. This is the greeter used for all displays except for the XDMCP remote displays. See also <filename>RemoteGreeter</filename>" -msgstr "" - -#: C/gdm.xml:2090(term) -msgid "Group" -msgstr "Group" - -#: C/gdm.xml:2092(synopsis) -#, no-wrap -msgid "Group=gdm" -msgstr "Group=gdm" - -#: C/gdm.xml:2093(para) -msgid "The group name under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogs are run. Also see <filename>User</filename>. 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 <filename>ServAuthDir</filename> is owned by this group. The ownership and permissions of <filename>ServAuthDir</filename> should be <filename>root.gdm</filename> and 1770." -msgstr "" - -#: C/gdm.xml:2110(term) -msgid "GtkModulesList" -msgstr "GtkModulesList" - -#: C/gdm.xml:2112(synopsis) -#, no-wrap -msgid "GtkModulesList=module-1:module-2:..." -msgstr "GtkModulesList=modul-1:modul-2:..." - -#: C/gdm.xml:2113(para) -msgid "A colon separated list of Gtk+ modules that <command>gdmgreeter</command> or <command>gdmlogin</command> will be invoked with if <filename>AddGtkModules</filename> is true. The format is the same as the standard Gtk+ module interface." -msgstr "" - -#: C/gdm.xml:2124(term) -msgid "HaltCommand" -msgstr "HaltCommand" - -#: C/gdm.xml:2126(synopsis) -#, no-wrap -msgid "HaltCommand=<sbin>/shutdown -h now" -msgstr "HaltCommand=<sbin>/shutdown -h now" - -#: C/gdm.xml:2127(para) -msgid "Full path and arguments to command to be executed when user selects \"Shut Down\" from the Actions menu. This can be a ';' separated list of commands to try. If a value is missing, the shut down command is not available. Note that the default for this value is not empty, so to disable \"Shut Down\" it must be set to an empty value." -msgstr "" - -#: C/gdm.xml:2140(term) -msgid "KillInitClients" -msgstr "KillInitClients" - -#: C/gdm.xml:2142(synopsis) -#, no-wrap -msgid "KillInitClients=true" -msgstr "KillInitClients=true" - -#: C/gdm.xml:2143(para) -msgid "Determines whether GDM should kill X clients started by the init scripts when the user logs in." -msgstr "" - -#: C/gdm.xml:2151(term) -msgid "LogDir" -msgstr "LogDir" - -#: C/gdm.xml:2153(synopsis) -#, no-wrap -msgid "LogDir=<var>/log/gdm" -msgstr "LogDir=<var>/log/gdm" - -#: C/gdm.xml:2154(para) -msgid "Directory containing the log files for the individual displays. By default this is the same as the ServAuthDir." -msgstr "" - -#: C/gdm.xml:2162(term) -msgid "PidFile" -msgstr "PidFile" - -#: C/gdm.xml:2164(synopsis) -#, no-wrap -msgid "PidFile=<var>/run/gdm.pid" -msgstr "PidFile=<var>/run/gdm.pid" - -#: C/gdm.xml:2165(para) -msgid "Name of the file containing the <filename>gdm</filename> process id." -msgstr "" - -#: C/gdm.xml:2173(term) -msgid "PreFetchProgram" -msgstr "PreFetchProgram" - -#: C/gdm.xml:2175(synopsis) -#, no-wrap -msgid "PreFetchProgram=command" -msgstr "PreFetchProgram=command" - -#: C/gdm.xml:2176(para) -msgid "Program to be run by the GDM greeter/login program when the initial screen is displayed. The purpose is to provide a hook where files which will be used after login can be preloaded to speed performance for the user. The program will be called once only, the first time a greeter is displayed. The gdmprefetch command may be used. This utility will load any libraries passed in on the command line, or if the argument starts with a \"@\" character, it will process the file assuming it is an ASCII file containing a list of libraries, one per line, and load each library in the file." -msgstr "" - -#: C/gdm.xml:2192(term) -msgid "PostLoginScriptDir" -msgstr "PostLoginScriptDir" - -#: C/gdm.xml:2194(synopsis) -#, no-wrap -msgid "PostLoginScriptDir=<etc>/gdm/PostLogin" -msgstr "PostLoginScriptDir=<etc>/gdm/PostLogin" - -#: C/gdm.xml:2195(para) -msgid "Directory containing the scripts run right after the user logs in, but before any session setup is done. See the ``The Script Directories'' section for more info." -msgstr "" - -#: C/gdm.xml:2204(term) -msgid "PostSessionScriptDir" -msgstr "PostSessionScriptDir" - -#: C/gdm.xml:2206(synopsis) -#, no-wrap -msgid "PostSessionScriptDir=<etc>/gdm/PostSession" -msgstr "PostSessionScriptDir=<etc>/gdm/PostSession" - -#: C/gdm.xml:2207(para) -msgid "Directory containing the scripts run after the user logs out. See the ``The Script Directories'' section for more info." -msgstr "" - -#: C/gdm.xml:2215(term) -msgid "PreSessionScriptDir" -msgstr "PreSessionScriptDir" - -#: C/gdm.xml:2217(synopsis) -#, no-wrap -msgid "PreSessionScriptDir=<etc>/gdm/PreSession" -msgstr "PreSessionScriptDir=<etc>/gdm/PreSession" - -#: C/gdm.xml:2218(para) -msgid "Directory containing the scripts run before the user logs in. See the ``The Script Directories'' section for more info." -msgstr "" - -#: C/gdm.xml:2226(term) -msgid "RebootCommand" -msgstr "RebootCommand" - -#: C/gdm.xml:2228(synopsis) -#, no-wrap -msgid "RebootCommand=<sbin>/shutdown -r now" -msgstr "RebootCommand=<sbin>/shutdown -r now" - -#: C/gdm.xml:2229(para) -msgid "Full path and optional arguments to the command to be executed when user selects Restart from the Actions menu. This can be a ';' separated list of commands to try. If missing, the restart command is not available. Note that the default for this value is not empty so to disable restart you must set this explicitly to an empty value." -msgstr "" - -#: C/gdm.xml:2241(term) -msgid "RemoteGreeter" -msgstr "RemoteGreeter" - -#: C/gdm.xml:2243(synopsis) -#, no-wrap -msgid "RemoteGreeter=<bin>/gdmlogin" -msgstr "RemoteGreeter=<bin>/gdmlogin" - -#: C/gdm.xml:2244(para) -msgid "Full path and name of the greeter executable followed by optional arguments. This is used for all remote XDMCP sessions. It is useful to have the less graphically demanding greeter here if you use the Themed Greeter for your main greeter. See also the <filename>Greeter</filename> key." -msgstr "" - -#: C/gdm.xml:2255(term) -msgid "RootPath" -msgstr "RootPath" - -#: C/gdm.xml:2257(synopsis) -#, no-wrap -msgid "RootPath=defaultpath (value set by configure)" -msgstr "RootPath=defaultpath (value set by configure)" - -#: C/gdm.xml:2258(para) -msgid "Specifies the path which will be set in the root's session and the {Init,PostLogin,PreSession,PostSession} scripts executed by GDM. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains \"SUROOT=<pathname>\". If the <filename>/etc/default/login</filename> file exists, but contains no value for SUROOT, the value as defined in the GDM configuration will be used." -msgstr "" - -#: C/gdm.xml:2272(term) -msgid "ServAuthDir" -msgstr "ServAuthDir" - -#: C/gdm.xml:2274(synopsis) -#, no-wrap -msgid "ServAuthDir=<var>/gdm" -msgstr "ServAuthDir=<var>/gdm" - -#: C/gdm.xml:2275(para) -msgid "Directory containing the X authentication files for the individual displays. Should be owned by <filename>root.gdm</filename> with permissions 1770, where <filename>gdm</filename> is the GDM group as defined by the <filename>Group</filename> option. That is should be owned by root, with <filename>gdm</filename> group having full write permissions and the directory should be sticky and others should have no permission to the directory. This way the GDM user can't remove files owned by root in that directory, while still being able to write its own files there. GDM will attempt to change permissions for you when it's first run if the permissions are not the above. This directory is also used for other private files that the daemon needs to store. Other users should not have any way to get into this directory and read/change it's contents. Anybody who can read this directory can connect to any display on this computer." -msgstr "" - -#: C/gdm.xml:2297(term) -msgid "SessionDesktopDir" -msgstr "SessionDesktopDir" - -#: C/gdm.xml:2299(synopsis) -#, no-wrap -msgid "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" -msgstr "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" - -#: C/gdm.xml:2300(para) -msgid "Directory containing the <filename>.desktop</filename> files which are the available sessions on the system. Since 2.4.4.2 this is treated like a PATH type variable and the first file found is used." -msgstr "" - -#: C/gdm.xml:2310(term) -msgid "SoundProgram" -msgstr "SoundProgram" - -#: C/gdm.xml:2312(filename) -msgid "<bin>/play" -msgstr "<bin>/play" - -#: C/gdm.xml:2312(filename) -msgid "<bin>/audioplay" -msgstr "<bin>/audioplay" - -#: C/gdm.xml:2312(synopsis) -#, no-wrap -msgid "SoundProgram=<placeholder-1/> (or <placeholder-2/> on Solaris)" -msgstr "SoundProgram=<placeholder-1/> (eller <placeholder-2/> på Solaris)" - -#: C/gdm.xml:2313(para) -msgid "Application to use when playing a sound. Currently used for playing the login sound, see the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0." -msgstr "" - -#: C/gdm.xml:2323(term) -msgid "StandardXServer" -msgstr "StandardXServer" - -#: C/gdm.xml:2325(synopsis) -#, no-wrap -msgid "StandardXServer=/dir/to/X (value assigned by configuration file)" -msgstr "StandardXServer=/sökväg/till/X (värdet tilldelat av konfigurationsfilen)" - -#: C/gdm.xml:2326(para) -msgid "Full path and arguments to the standard X server command. This is used when gdm cannot find any other definition, and it's used as the default and failsafe fallback in a number of places. This should be able to run some sort of X server." -msgstr "" - -#: C/gdm.xml:2337(term) -msgid "SuspendCommand" -msgstr "SuspendCommand" - -#: C/gdm.xml:2339(synopsis) -#, no-wrap -msgid "SuspendCommand=" -msgstr "SuspendCommand=" - -#: C/gdm.xml:2340(para) -msgid "Full path and arguments to command to be executed when user selects Suspend from the Actions menu. If empty there is no such menu item. Note that the default for this value is not empty so to disable suspend you must set this explicitly to an empty value." -msgstr "" - -#: C/gdm.xml:2351(term) -msgid "TimedLoginEnable" -msgstr "TimedLoginEnable" - -#: C/gdm.xml:2353(synopsis) -#, no-wrap -msgid "TimedLoginEnable=false" -msgstr "TimedLoginEnable=false" - -#: C/gdm.xml:2354(para) -msgid "If the user given in <filename>TimedLogin</filename> should be logged in after a number of seconds (set with <filename>TimedLoginDelay</filename>) of inactivity on the login screen. This is useful for public access terminals or perhaps even home use. If the user uses the keyboard or browses the menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or 30 seconds, whichever is higher. If the user does not enter a username but just hits the ENTER key while the login program is requesting the username, then GDM will assume the user wants to login immediately as the timed user. Note that no password will be asked for this user so you should be careful, although if using PAM it can be configured to require password entry before allowing login." -msgstr "" - -#: C/gdm.xml:2374(term) -msgid "TimedLogin" -msgstr "TimedLogin" - -#: C/gdm.xml:2376(synopsis) -#, no-wrap -msgid "TimedLogin=" -msgstr "TimedLogin=" - -#: C/gdm.xml:2377(para) -msgid "This is the user that should be logged in after a specified number of seconds of inactivity. This can never be \"root\" and gdm will refuse to log in root this way. The same features as for <filename>AutomaticLogin</filename> are supported. The same control chars and piping to a application are supported." -msgstr "" - -#: C/gdm.xml:2389(term) -msgid "TimedLoginDelay" -msgstr "TimedLoginDelay" - -#: C/gdm.xml:2391(synopsis) -#, no-wrap -msgid "TimedLoginDelay=30" -msgstr "TimedLoginDelay=30" - -#: C/gdm.xml:2392(para) -msgid "Delay in seconds before the <filename>TimedLogin</filename> user will be logged in. It must be greater then or equal to 10." -msgstr "" - -#: C/gdm.xml:2400(term) -msgid "User" -msgstr "User" - -#: C/gdm.xml:2402(synopsis) -#, no-wrap -msgid "User=gdm" -msgstr "User=gdm" - -#: C/gdm.xml:2403(para) -msgid "The username under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogs are run. Also see <filename>Group</filename>. This user will have access to all the X authorization files, and perhaps to other internal GDM data and it should not therefore be a user such as nobody, but rather a dedicated user." -msgstr "" - -#: C/gdm.xml:2417(term) -msgid "UserAuthDir" -msgstr "UserAuthDir" - -#: C/gdm.xml:2419(synopsis) -#, no-wrap -msgid "UserAuthDir=" -msgstr "UserAuthDir=" - -#: C/gdm.xml:2420(para) -msgid "The directory where user's <filename>.Xauthority</filename> 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: <filename>~/authdir/</filename>." -msgstr "" - -#: C/gdm.xml:2427(para) -msgid "If you do not use the tilde expansion, then the filename created will be random, like in <filename>UserAuthFBDir</filename>. This way many users can have the same authentication directory. For example you might want to set this to <filename>/tmp</filename> 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 <filename>/tmp</filename> directory." -msgstr "" - -#: C/gdm.xml:2440(para) -msgid "Normally if this is the user's home directory GDM will still refuse to put cookies there if it thinks it is NFS (by testing root-squashing). This can be changed by setting <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false." -msgstr "" - -#: C/gdm.xml:2451(term) -msgid "UserAuthFBDir" -msgstr "UserAuthFBDir" - -#: C/gdm.xml:2453(synopsis) -#, no-wrap -msgid "UserAuthFBDir=/tmp" -msgstr "UserAuthFBDir=/tmp" - -#: C/gdm.xml:2454(para) -msgid "If GDM fails to update the user's <filename>.Xauthority</filename> file a fallback cookie is created in this directory." -msgstr "" - -#: C/gdm.xml:2463(term) -msgid "UserAuthFile" -msgstr "UserAuthFile" - -#: C/gdm.xml:2465(synopsis) -#, no-wrap -msgid "UserAuthFile=.Xauthority" -msgstr "UserAuthFile=.Xauthority" - -#: C/gdm.xml:2466(para) -msgid "Name of the file used for storing user cookies." -msgstr "" - -#: C/gdm.xml:2473(term) -msgid "VTAllocation" -msgstr "VTAllocation" - -#: C/gdm.xml:2475(synopsis) -#, no-wrap -msgid "VTAllocation=true" -msgstr "VTAllocation=true" - -#: C/gdm.xml:2476(para) -msgid "On systems where GDM supports automatic VT (virtual terminal) allocation (currently Linux and FreeBSD only), you can have GDM automatically append the vt argument to the X server executable. This way races that come up from each X server managing it's own vt allocation can be avoided. See also <filename>FirstVT</filename>." -msgstr "" - -#: C/gdm.xml:2488(term) -msgid "XKeepsCrashing" -msgstr "XKeepsCrashing" - -#: C/gdm.xml:2490(synopsis) -#, no-wrap -msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" -msgstr "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" - -#: C/gdm.xml:2491(para) -msgid "A script to run in case X keeps crashing. This is for running An X configuration or whatever else to make the X configuration work. See the script that came with the distribution for an example. The distributed <filename>XKeepsCrashing</filename> script is tested on Red Hat, but may work elsewhere. Your system integrator should make sure this script is up to date for your particular system." -msgstr "" - -#: C/gdm.xml:2500(para) -msgid "In case <filename>FailsafeXServer</filename> is setup, that will be tried first. and this only used as a backup if even that X server keeps crashing." -msgstr "" - -#: C/gdm.xml:2509(term) -msgid "Xnest" -msgstr "Xnest" - -#: C/gdm.xml:2511(synopsis) -#, no-wrap -msgid "Xnest=<bin>/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)" -msgstr "Xnest=<bin>/X11/Xnest (/usr/openwin/bin/Xnest på Solaris)" - -#: C/gdm.xml:2512(para) -msgid "The full path and arguments to the Xnest command. This is used for the flexible Xnest displays. This way the user can start new login screens in a nested window. Of course you must have the Xnest display from your X server packages installed for this to work." -msgstr "" - -#: C/gdm.xml:2525(title) -msgid "Security Options" -msgstr "Säkerhetsalternativ" - -#: C/gdm.xml:2528(title) -msgid "[security]" -msgstr "[security]" - -#: C/gdm.xml:2531(term) -msgid "AllowRoot" -msgstr "AllowRoot" - -#: C/gdm.xml:2533(synopsis) -#, no-wrap -msgid "AllowRoot=true" -msgstr "AllowRoot=true" - -#: C/gdm.xml:2534(para) -msgid "Allow root (privileged user) to log in through GDM. Set this to false if you want to disallow such logins." -msgstr "" - -#: C/gdm.xml:2538(para) -msgid "On systems that support PAM, this parameter is not as useful as you can use PAM to do the same thing, and in fact do even more. However it is still followed, so you should probably leave it true for PAM systems." -msgstr "" - -#: C/gdm.xml:2548(term) -msgid "AllowRemoteRoot" -msgstr "AllowRemoteRoot" - -#: C/gdm.xml:2550(synopsis) -#, no-wrap -msgid "AllowRemoteRoot=false" -msgstr "AllowRemoteRoot=false" - -#: C/gdm.xml:2551(para) -msgid "Allow root (privileged user) to log in remotely through GDM. This value should be set to true to allow such logins. Remote logins are any logins that come in through the XDMCP." -msgstr "" - -#: C/gdm.xml:2556(para) -msgid "On systems that support PAM, this parameter is not as useful since you can use PAM to do the same thing, and do even more." -msgstr "" - -#: C/gdm.xml:2561(para) -msgid "This value will be overridden and set to false if the <filename>/etc/default/login</filename> file exists and contains \"CONSOLE=/dev/login\", and set to true if the <filename>/etc/default/login</filename> file exists and contains any other value or no value for CONSOLE." -msgstr "" - -#: C/gdm.xml:2572(term) -msgid "AllowRemoteAutoLogin" -msgstr "AllowRemoteAutoLogin" - -#: C/gdm.xml:2574(synopsis) -#, no-wrap -msgid "AllowRemoteAutoLogin=false" -msgstr "AllowRemoteAutoLogin=false" - -#: C/gdm.xml:2575(para) -msgid "Allow the timed login to work remotely. That is, remote connections through XDMCP will be allowed to log into the \"TimedLogin\" user by letting the login window time out, just like the local user on the first console." -msgstr "" - -#: C/gdm.xml:2581(para) -msgid "Note that this can make a system quite insecure, and thus is off by default." -msgstr "" - -#: C/gdm.xml:2589(term) -msgid "CheckDirOwner" -msgstr "CheckDirOwner" - -#: C/gdm.xml:2591(synopsis) -#, no-wrap -msgid "CheckDirOwner=true" -msgstr "CheckDirOwner=true" - -#: C/gdm.xml:2592(para) -msgid "By default GDM checks the ownership of the home directories before writing to them, this prevents security issues in case of bad setup. However in some instances home directories will be owned by a different user and in this case it is necessary to turn this option on. You will also most likely have to turn the <filename>RelaxPermissions</filename> key to at least value 1 since in such a scenario home directories are likely to be group writable. Supported since 2.6.0.4." -msgstr "" - -#: C/gdm.xml:2606(term) -msgid "SupportAutomount" -msgstr "SupportAutomount" - -#: C/gdm.xml:2608(synopsis) -#, no-wrap -msgid "SupportAutomount=false" -msgstr "SupportAutomount=false" - -#: C/gdm.xml:2609(para) -msgid "By default GDM checks the ownership of the home directories before writing to them, this prevents security issues in case of bad setup. However, when home directories are managed by automounter, they are often not mounted before they are accessed. This option works around subtleties of Linux automounter." -msgstr "" - -#: C/gdm.xml:2621(term) -msgid "DisallowTCP" -msgstr "DisallowTCP" - -#: C/gdm.xml:2623(synopsis) -#, no-wrap -msgid "DisallowTCP=true" -msgstr "DisallowTCP=true" - -#: C/gdm.xml:2624(para) -msgid "If true, then always append <filename>-nolisten tcp</filename> to the command line of local X servers, thus disallowing TCP connection. This is useful if you do not care for allowing remote connections, since the X protocol could really be potentially a security hazard to leave open, even though no known security problems exist." -msgstr "" - -#: C/gdm.xml:2637(term) -msgid "NeverPlaceCookiesOnNFS" -msgstr "NeverPlaceCookiesOnNFS" - -#: C/gdm.xml:2639(synopsis) -#, no-wrap -msgid "NeverPlaceCookiesOnNFS=true" -msgstr "NeverPlaceCookiesOnNFS=true" - -#: C/gdm.xml:2640(para) -msgid "Normally if this is true (which is by default), GDM will not place cookies into the user's home directory if this directory is on NFS. Well, GDM will consider any filesystem with root-squashing an NFS filesystem. Sometimes however the remote file system can have root squashing and be safe (perhaps by using encryption). In this case set this to 'false'. Note that this option appeared in version 2.4.4.4 and is ignored in previous versions." -msgstr "" - -#: C/gdm.xml:2654(term) -msgid "PasswordRequired" -msgstr "PasswordRequired" - -#: C/gdm.xml:2656(synopsis) -#, no-wrap -msgid "PasswordRequired=false" -msgstr "PasswordRequired=false" - -#: C/gdm.xml:2657(para) -msgid "If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be passed as a flag to pam_authenticate and pam_acct_mgmt, disallowing NULL password. This setting will only take effect if PAM is being used by GDM. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains \"PASSREQ=[YES|NO]\". If the <filename>/etc/default/login</filename> file exists, but contains no value for PASSREQ, the value as defined in the GDM configuration will be used." -msgstr "" - -#: C/gdm.xml:2673(term) -msgid "RelaxPermissions" -msgstr "RelaxPermissions" - -#: C/gdm.xml:2675(synopsis) -#, no-wrap -msgid "RelaxPermissions=0" -msgstr "RelaxPermissions=0" - -#: C/gdm.xml:2676(para) -msgid "By default GDM ignores files and directories writable to other users than the owner." -msgstr "" - -#: C/gdm.xml:2681(para) -msgid "Changing the value of RelaxPermissions makes it possible to alter this behavior:" -msgstr "" - -#: C/gdm.xml:2686(para) -msgid "0 - Paranoia option. Only accepts user owned files and directories." -msgstr "" - -#: C/gdm.xml:2690(para) -msgid "1 - Allow group writable files and directories." -msgstr "" - -#: C/gdm.xml:2693(para) -msgid "2 - Allow world writable files and directories." -msgstr "" - -#: C/gdm.xml:2700(term) -msgid "RetryDelay" -msgstr "RetryDelay" - -#: C/gdm.xml:2702(synopsis) -#, no-wrap -msgid "RetryDelay=1" -msgstr "RetryDelay=1" - -#: C/gdm.xml:2703(para) -msgid "The number of seconds GDM should wait before reactivating the entry field after a failed login." -msgstr "" - -#: C/gdm.xml:2711(term) -msgid "UserMaxFile" -msgstr "UserMaxFile" - -#: C/gdm.xml:2713(synopsis) -#, no-wrap -msgid "UserMaxFile=65536" -msgstr "UserMaxFile=65536" - -#: C/gdm.xml:2714(para) -msgid "GDM will refuse to read/write files bigger than this number (specified in bytes)." -msgstr "" - -#: C/gdm.xml:2719(para) -msgid "In addition to the size check GDM is extremely picky about accessing files in user directories. It will not follow symlinks and can optionally refuse to read files and directories writable by other than the owner. See the <filename>RelaxPermissions</filename> option for more info." -msgstr "" - -#: C/gdm.xml:2732(title) -msgid "XDCMP Support" -msgstr "XDCMP-stöd" - -#: C/gdm.xml:2735(title) -msgid "[xdmcp]" -msgstr "[xdmcp]" - -#: C/gdm.xml:2738(term) -msgid "DisplaysPerHost" -msgstr "DisplaysPerHost" - -#: C/gdm.xml:2740(synopsis) -#, no-wrap -msgid "DisplaysPerHost=1" -msgstr "DisplaysPerHost=1" - -#: C/gdm.xml:2741(para) -msgid "To prevent attackers from filling up the pending queue, GDM will only allow one connection for each remote computer. If you want to provide display services to computers with more than one screen, you should increase the <filename>DisplaysPerHost</filename> value accordingly." -msgstr "" - -#: C/gdm.xml:2749(para) -msgid "Note that the number of connections from the local computer is unlimited. Only remote connections are limited by this number." -msgstr "" - -#: C/gdm.xml:2757(term) -#: C/gdm.xml:4004(term) -msgid "Enable" -msgstr "Enable" - -#: C/gdm.xml:2759(synopsis) -#: C/gdm.xml:4006(synopsis) -#, no-wrap -msgid "Enable=false" -msgstr "Enable=false" - -#: C/gdm.xml:2760(para) -msgid "Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM." -msgstr "" - -#: C/gdm.xml:2765(para) -msgid "<filename>gdm</filename> listens for requests on UDP port 177. See the Port option for more information." -msgstr "" - -#: C/gdm.xml:2770(para) -msgid "If GDM is compiled to support it, access from remote displays can be controlled using the TCP Wrappers library. The service name is <filename>gdm</filename>" -msgstr "" - -#: C/gdm.xml:2776(para) -msgid "" -"You should add <screen>\n" -"gdm:.my.domain\n" -"</screen> to your <filename><etc>/hosts.allow</filename>, depending on your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" - -#: C/gdm.xml:2787(para) -msgid "Please note that XDMCP is not a particularly secure protocol and that it is a good idea to block UDP port 177 on your firewall unless you really need it." -msgstr "" - -#: C/gdm.xml:2796(term) -msgid "EnableProxy" -msgstr "EnableProxy" - -#: C/gdm.xml:2798(synopsis) -#, no-wrap -msgid "EnableProxy=false" -msgstr "EnableProxy=false" - -#: C/gdm.xml:2799(para) -msgid "Setting this to true enables support for running XDMCP sessions on a local proxy X server. This may improve the performance of XDMCP sessions, especially on high latency networks, as many X protocol operations can be completed without going over the network." -msgstr "" - -#: C/gdm.xml:2806(para) -msgid "Note, however, that this mode will significantly increase the burden on the machine hosting the XDMCP sessions" -msgstr "" - -#: C/gdm.xml:2810(para) -msgid "See the <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</filename> options for further details on how to configure support for this feature." -msgstr "" - -#: C/gdm.xml:2819(term) -msgid "HonorIndirect" -msgstr "HonorIndirect" - -#: C/gdm.xml:2821(synopsis) -#, no-wrap -msgid "HonorIndirect=true" -msgstr "HonorIndirect=true" - -#: C/gdm.xml:2822(para) -msgid "Enables XDMCP INDIRECT choosing (i.e. remote execution of <filename>gdmchooser</filename>) for X-terminals which don't supply their own display browser." -msgstr "" - -#: C/gdm.xml:2831(term) -msgid "MaxPending" -msgstr "MaxPending" - -#: C/gdm.xml:2833(synopsis) -#, no-wrap -msgid "MaxPending=4" -msgstr "MaxPending=4" - -#: C/gdm.xml:2834(para) -msgid "To avoid denial of service attacks, GDM has fixed size queue of pending connections. Only MaxPending displays can start at the same time." -msgstr "" - -#: C/gdm.xml:2840(para) -msgid "Please note that this parameter does *not* limit the number of remote displays which can be managed. It only limits the number of displays initiating a connection simultaneously." -msgstr "" - -#: C/gdm.xml:2849(term) -msgid "MaxPendingIndirect" -msgstr "MaxPendingIndirect" - -#: C/gdm.xml:2851(synopsis) -#, no-wrap -msgid "MaxPendingIndirect=4" -msgstr "MaxPendingIndirect=4" - -#: C/gdm.xml:2852(para) -msgid "GDM will only provide <filename>MaxPendingIndirect</filename> displays with host choosers simultaneously. If more queries from different hosts come in, the oldest ones will be forgotten." -msgstr "" - -#: C/gdm.xml:2862(term) -msgid "MaxSessions" -msgstr "MaxSessions" - -#: C/gdm.xml:2864(synopsis) -#, no-wrap -msgid "MaxSessions=16" -msgstr "MaxSessions=16" - -#: C/gdm.xml:2865(para) -msgid "Determines the maximum number of remote display connections which will be managed simultaneously. I.e. the total number of remote displays that can use your host." -msgstr "" - -#: C/gdm.xml:2874(term) -msgid "MaxWait" -msgstr "MaxWait" - -#: C/gdm.xml:2876(synopsis) -#, no-wrap -msgid "MaxWait=30" -msgstr "MaxWait=30" - -#: C/gdm.xml:2877(para) -msgid "When GDM is ready to manage a display an ACCEPT packet is sent to it containing a unique session id which will be used in future XDMCP conversations." -msgstr "" - -#: C/gdm.xml:2883(para) -msgid "GDM will then place the session id in the pending queue waiting for the display to respond with a MANAGE request." -msgstr "" - -#: C/gdm.xml:2888(para) -msgid "If no response is received within MaxWait seconds, GDM will declare the display dead and erase it from the pending queue freeing up the slot for other displays." -msgstr "" - -#: C/gdm.xml:2897(term) -msgid "MaxWaitIndirect" -msgstr "MaxWaitIndirect" - -#: C/gdm.xml:2899(synopsis) -#, no-wrap -msgid "MaxWaitIndirect=30" -msgstr "MaxWaitIndirect=30" - -#: C/gdm.xml:2900(para) -msgid "The MaxWaitIndirect parameter determines the maximum number of seconds between the time where a user chooses a host and the subsequent indirect query where the user is connected to the host. When the timeout is exceeded, the information about the chosen host is forgotten and the indirect slot freed up for other displays. The information may be forgotten earlier if there are more hosts trying to send indirect queries then <filename>MaxPendingIndirect</filename>." -msgstr "" - -#: C/gdm.xml:2914(term) -msgid "Port" -msgstr "Port" - -#: C/gdm.xml:2916(synopsis) -#, no-wrap -msgid "Port=177" -msgstr "Port=177" - -#: C/gdm.xml:2917(para) -msgid "The UDP port number <filename>gdm</filename> should listen to for XDMCP requests. Don't change this unless you know what you are doing." -msgstr "" - -#: C/gdm.xml:2926(term) -msgid "PingIntervalSeconds" -msgstr "PingIntervalSeconds" - -#: C/gdm.xml:2928(synopsis) -#, no-wrap -msgid "PingIntervalSeconds=15" -msgstr "PingIntervalSeconds=15" - -#: C/gdm.xml:2929(para) -msgid "Interval in which to ping the X server in seconds. If the X server doesn't return before the next time we ping it, the connection is stopped and the session ended. This is a combination of the XDM PingInterval and PingTimeout, but in seconds." -msgstr "" - -#: C/gdm.xml:2937(para) -msgid "Note that GDM in the past used to have a <filename>PingInterval</filename> configuration key which was also in minutes. For most purposes you'd want this setting to be lower then one minute however since in most cases where XDMCP would be used (such as terminal labs), a lag of more than 15 or so seconds would really mean that the terminal was turned off or restarted and you would want to end the session." -msgstr "" - -#: C/gdm.xml:2950(term) -msgid "ProxyReconnect" -msgstr "ProxyReconnect" - -#: C/gdm.xml:2952(synopsis) -#, no-wrap -msgid "FlexiProxyReconnect=" -msgstr "FlexiProxyReconnect=" - -#: C/gdm.xml:2953(para) -msgid "Setting this option enables experimental support for session migration with XDMCP sessions. This enables users to disconnect from their session and later reconnect to that same session, possibly from a different terminal." -msgstr "" - -#: C/gdm.xml:2959(para) -msgid "In order to use this feature, you must have a nested X server available which supports disconnecting from its parent X server and reconnecting to another X server. Currently, the Distributed Multihead X (DMX) server supports this feature to some extent and other projects like NoMachine NX are busy implementing it." -msgstr "" - -#: C/gdm.xml:2966(para) -msgid "This option should be set to the path of a command which will handle reconnecting the XDMCP proxy to another backend display. A sample implementation for use with DMX is supplied." -msgstr "" - -#: C/gdm.xml:2975(term) -msgid "ProxyXServer" -msgstr "ProxyXServer" - -#: C/gdm.xml:2977(synopsis) -#, no-wrap -msgid "ProxyXServer=" -msgstr "ProxyXServer=" - -#: C/gdm.xml:2978(para) -msgid "The X server command line for a XDMCP proxy. Any nested X server like Xnest, Xephr or Xdmx should work fairly well." -msgstr "" - -#: C/gdm.xml:2986(term) -msgid "Willing" -msgstr "Willing" - -#: C/gdm.xml:2988(synopsis) -#, no-wrap -msgid "Willing=<etc>/gdm/Xwilling" -msgstr "Willing=<etc>/gdm/Xwilling" - -#: C/gdm.xml:2989(para) -msgid "When the machine sends a WILLING packet back after a QUERY it sends a string that gives the current status of this server. The default message is the system ID, but it is possible to create a script that displays customized message. If this script doesn't exist or this key is empty the default message is sent. If this script succeeds and produces some output, the first line of it's output is sent (and only the first line). It runs at most once every 3 seconds to prevent possible denial of service by flooding the machine with QUERY packets." -msgstr "" - -#: C/gdm.xml:3007(title) -msgid "Common GUI Configuration Options" -msgstr "" - -#: C/gdm.xml:3010(title) -msgid "[gui]" -msgstr "[gui]" - -#: C/gdm.xml:3013(term) -msgid "AllowGtkThemeChange" -msgstr "AllowGtkThemeChange" - -#: C/gdm.xml:3015(synopsis) -#, no-wrap -msgid "AllowGtkThemeChange=true" -msgstr "AllowGtkThemeChange=true" - -#: C/gdm.xml:3016(para) -msgid "If to allow changing the GTK+ (widget) theme from the greeter. Currently this only affects the standard greeter as the graphical greeter does not yet have this ability. The theme will stay in effect on this display until changed and will affect all the other windows that are put up by GDM. Supported since 2.5.90.2." -msgstr "" - -#: C/gdm.xml:3028(term) -msgid "GtkRC" -msgstr "GtkRC" - -#: C/gdm.xml:3030(synopsis) -#, no-wrap -msgid "GtkRC=" -msgstr "GtkRC=" - -#: C/gdm.xml:3031(para) -msgid "Path to a <filename>gtkrc</filename> to read when GDM puts up a window. You should really now use the <filename>GtkTheme</filename> key for just setting a theme." -msgstr "" - -#: C/gdm.xml:3040(term) -msgid "GtkTheme" -msgstr "GtkTheme" - -#: C/gdm.xml:3042(synopsis) -#, no-wrap -msgid "GtkTheme=Default" -msgstr "GtkTheme=Default" - -#: C/gdm.xml:3043(para) -msgid "A name of an installed theme to use by default. It will be used in the greeter, chooser and all other GUI windows put up by GDM. Supported since 2.5.90.2." -msgstr "" - -#: C/gdm.xml:3052(term) -msgid "GtkThemesToAllow" -msgstr "GtkThemesToAllow" - -#: C/gdm.xml:3054(synopsis) -#, no-wrap -msgid "GtkThemesToAllow=all" -msgstr "GtkThemesToAllow=all" - -#: C/gdm.xml:3055(para) -msgid "Comma separated list of themes to allow. These must be the names of the themes installed in the standard locations for GTK+ themes. You can also specify 'all' to allow all installed themes. This is related to the <filename>AllowGtkThemeChange</filename> key. Supported since 2.5.90.2." -msgstr "" - -#: C/gdm.xml:3067(term) -msgid "MaxIconWidth" -msgstr "MaxIconWidth" - -#: C/gdm.xml:3069(synopsis) -#, no-wrap -msgid "MaxIconWidth=128" -msgstr "MaxIconWidth=128" - -#: C/gdm.xml:3070(para) -msgid "Specifies the maximum icon width (in pixels) that the face browser will display. Icons larger than this will be scaled. This also affects icons in the XDMCP chooser." -msgstr "" - -#: C/gdm.xml:3079(term) -msgid "MaxIconHeight" -msgstr "MaxIconHeight" - -#: C/gdm.xml:3081(synopsis) -#, no-wrap -msgid "MaxIconHeight=128" -msgstr "MaxIconHeight=128" - -#: C/gdm.xml:3082(para) -msgid "Specifies the maximum icon height (in pixels) that the face browser will display. Icons larger than this will be scaled. This also affects icons in the XDMCP chooser." -msgstr "" - -#: C/gdm.xml:3093(title) -msgid "Greeter Configuration" -msgstr "" - -#: C/gdm.xml:3096(title) -msgid "[greeter]" -msgstr "[greeter]" - -#: C/gdm.xml:3099(term) -msgid "BackgroundColor" -msgstr "BackgroundColor" - -#: C/gdm.xml:3101(synopsis) -#, no-wrap -msgid "BackgroundColor=#76848F" -msgstr "BackgroundColor=#76848F" - -#: C/gdm.xml:3102(para) -msgid "If the BackgroundType is 2, use this color in the background of the greeter. Also use it as the back of transparent images set on the background and if the BackgroundRemoteOnlyColor is set and this is a remote display. This only affects the GTK+ Greeter." -msgstr "" - -#: C/gdm.xml:3113(term) -msgid "BackgroundProgramInitialDelay" -msgstr "BackgroundProgramInitialDelay" - -#: C/gdm.xml:3115(synopsis) -#, no-wrap -msgid "BackgroundProgramInitialDelay=30" -msgstr "BackgroundProgramInitialDelay=30" - -#: C/gdm.xml:3116(para) -msgid "The background application will be started after at least that many seconds of inactivity." -msgstr "" - -#: C/gdm.xml:3124(term) -msgid "RestartBackgroundProgram" -msgstr "RestartBackgroundProgram" - -#: C/gdm.xml:3126(synopsis) -#, no-wrap -msgid "RestartBackgroundProgram=true" -msgstr "RestartBackgroundProgram=true" - -#: C/gdm.xml:3127(para) -msgid "If set the background application will be restarted when it has exited, after the delay described below has elapsed. This option can be useful when you wish to run a screen saver application when no user is using the computer." -msgstr "" - -#: C/gdm.xml:3137(term) -msgid "BackgroundProgramRestartDelay" -msgstr "BackgroundProgramRestartDelay" - -#: C/gdm.xml:3139(synopsis) -#, no-wrap -msgid "BackgroundProgramRestartDelay=30" -msgstr "BackgroundProgramRestartDelay=30" - -#: C/gdm.xml:3140(para) -msgid "The background application will be restarted after at least that many seconds of inactivity." -msgstr "" - -#: C/gdm.xml:3148(term) -msgid "BackgroundImage" -msgstr "BackgroundImage" - -#: C/gdm.xml:3150(synopsis) -#, no-wrap -msgid "BackgroundImage=somefile.png" -msgstr "BackgroundImage=någonfil.png" - -#: C/gdm.xml:3151(para) -msgid "If the BackgroundType is 1, then display this file as the background in the greeter. This only affects the GTK+ Greeter." -msgstr "" - -#: C/gdm.xml:3160(term) -msgid "BackgroundProgram" -msgstr "BackgroundProgram" - -#: C/gdm.xml:3162(synopsis) -#, no-wrap -msgid "BackgroundProgram=<bin>/xeyes" -msgstr "BackgroundProgram=<bin>/xeyes" - -#: C/gdm.xml:3163(para) -msgid "If set this command will be run in the background while the login window is being displayed. Note that not all applications will run this way, since GDM does not usually have a home directory. You could set up home directory for the GDM user if you wish to run applications which require it. This only affects the GTK+ Greeter." -msgstr "" - -#: C/gdm.xml:3175(term) -msgid "BackgroundRemoteOnlyColor" -msgstr "BackgroundRemoteOnlyColor" - -#: C/gdm.xml:3177(synopsis) -#, no-wrap -msgid "BackgroundRemoteOnlyColor=true" -msgstr "BackgroundRemoteOnlyColor=true" - -#: C/gdm.xml:3178(para) -msgid "On remote displays only set the color background. This is to make network load lighter. The <filename>BackgroundProgram</filename> is also not run. This only affects the GTK+ Greeter." -msgstr "" - -#: C/gdm.xml:3188(term) -msgid "BackgroundScaleToFit" -msgstr "BackgroundScaleToFit" - -#: C/gdm.xml:3190(synopsis) -#, no-wrap -msgid "BackgroundScaleToFit=true" -msgstr "BackgroundScaleToFit=true" - -#: C/gdm.xml:3191(para) -msgid "Scale background image to fit the screen. This only affects the GTK+ Greeter." -msgstr "" - -#: C/gdm.xml:3199(term) -msgid "BackgroundType" -msgstr "BackgroundType" - -#: C/gdm.xml:3201(synopsis) -#, no-wrap -msgid "BackgroundType=2" -msgstr "BackgroundType=2" - -#: C/gdm.xml:3202(para) -msgid "The type of background to set. 0 is none, 1 is image and color, 2 is color and 3 is image. This only affects the GTK+ Greeter." -msgstr "" - -#: C/gdm.xml:3210(term) -msgid "Browser" -msgstr "Browser" - -#: C/gdm.xml:3212(synopsis) -#, no-wrap -msgid "Browser=true" -msgstr "Browser=true" - -#: C/gdm.xml:3213(para) -msgid "Set to true to enable the face browser. See the ``The GTK+ Greeter'' section for more information on the face browser. This option only works for the GTK+ Greeter. For the Themed Greeter, the face browser is enabled by choosing a theme which includes a face browser" -msgstr "" - -#: C/gdm.xml:3224(term) -msgid "ChooserButton" -msgstr "ChooserButton" - -#: C/gdm.xml:3226(synopsis) -#, no-wrap -msgid "ChooserButton=true" -msgstr "ChooserButton=true" - -#: C/gdm.xml:3227(para) -msgid "If true, add a chooser button to the Actions menu that will restart the current X server with a chooser. XDMCP does not need to be enabled on the local computer for this to work." -msgstr "" - -#: C/gdm.xml:3236(term) -msgid "ConfigAvailable" -msgstr "ConfigAvailable" - -#: C/gdm.xml:3238(synopsis) -#, no-wrap -msgid "ConfigAvailable=false" -msgstr "ConfigAvailable=false" - -#: C/gdm.xml:3239(para) -msgid "If true, allows the configurator to be run from the greeter. Note that the user will need to type in the root password before the configurator will be started. This is set to false by default for additional security. See the <filename>Configurator</filename> option in the daemon section." -msgstr "" - -#: C/gdm.xml:3251(term) -msgid "DefaultFace" -msgstr "DefaultFace" - -#: C/gdm.xml:3253(synopsis) -#, no-wrap -msgid "DefaultFace=<share>/pixmaps/nophoto.png" -msgstr "DefaultFace=<share>/pixmaps/nophoto.png" - -#: C/gdm.xml:3254(para) -msgid "If a user has no defined face image, GDM will use the \"stock_person\" icon defined in the current GTK+ theme. If no such image is defined, the image specified by <filename>DefaultFace</filename> will be used. The image must be in a gdk-pixbuf supported format and the file must be readable to the GDM user." -msgstr "" - -#: C/gdm.xml:3266(term) -msgid "Include" -msgstr "Include" - -#: C/gdm.xml:3268(synopsis) -#, no-wrap -msgid "Include=" -msgstr "Include=" - -#: C/gdm.xml:3269(para) -msgid "Comma separated list of users to be included in the face browser and in the <command>gdmsetup</command> selection list for Automatic/Timed login. See also <filename>Exclude</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." -msgstr "" - -#: C/gdm.xml:3281(term) -msgid "Exclude" -msgstr "Exclude" - -#: C/gdm.xml:3283(synopsis) -#, no-wrap -msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." -msgstr "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." - -#: C/gdm.xml:3284(para) -msgid "Comma separated list of users to be excluded from the face browser and from the <command>gdmsetup</command> selection list for Automatic/Timed login. Excluded users will still be able to log in, but will have to type their username. See also <filename>Include</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." -msgstr "" - -#: C/gdm.xml:3297(term) -msgid "IncludeAll" -msgstr "IncludeAll" - -#: C/gdm.xml:3299(synopsis) -#, no-wrap -msgid "IncludeAll=false" -msgstr "IncludeAll=false" - -#: C/gdm.xml:3300(para) -msgid "By default, an empty include list means display no users. By setting IncludeAll to true, the password file will be scanned and all users will be displayed aside from users excluded via the Exclude setting and user ID's less than MinimalUID. Scanning the password file can be slow on systems with large numbers of users and this feature should not be used in such environments. See also <filename>Include</filename>, <filename>Exclude</filename>, and <filename>MinimalUID</filename>." -msgstr "" - -#: C/gdm.xml:3316(term) -msgid "GlobalFaceDir" -msgstr "GlobalFaceDir" - -#: C/gdm.xml:3318(synopsis) -#, no-wrap -msgid "GlobalFaceDir=<share>/pixmaps/faces/" -msgstr "GlobalFaceDir=<share>/pixmaps/faces/" - -#: C/gdm.xml:3319(para) -msgid "Systemwide directory for face files. The sysadmin can place icons for users here without touching their homedirs. Faces are named after their users' logins." -msgstr "" - -#: C/gdm.xml:3325(para) -msgid "I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the face icon for the user ``johndoe''. No image format extension should be specified." -msgstr "" - -#: C/gdm.xml:3331(para) -msgid "The face images must be stored in gdk-pixbuf supported formats and they must be readable for the GDM user." -msgstr "" - -#: C/gdm.xml:3336(para) -msgid "A user's own icon file will always take precedence over the sysadmin provided one." -msgstr "" - -#: C/gdm.xml:3344(term) -msgid "GraphicalTheme" -msgstr "GraphicalTheme" - -#: C/gdm.xml:3346(synopsis) -#, no-wrap -msgid "GraphicalTheme=circles" -msgstr "GraphicalTheme=circles" - -#: C/gdm.xml:3347(para) -msgid "The graphical theme that the Themed Greeter should use. it should refer to a directory in the theme directory set by <filename>GraphicalThemeDir</filename>." -msgstr "" - -#: C/gdm.xml:3356(term) -msgid "GraphicalThemes" -msgstr "GraphicalThemes" - -#: C/gdm.xml:3358(synopsis) -#, no-wrap -msgid "GraphicalThemes=circles" -msgstr "GraphicalThemes=circles" - -#: C/gdm.xml:3359(para) -msgid "The graphical themes that the Themed Greeter should use is the Mode is set on Random Themes. This is a \"/:\" delimited list. It should refer to a directory in the theme directory set by <filename>GraphicalThemeDir</filename>. This is only used if <filename>GraphicalThemeRand</filename> is set to true." -msgstr "" - -#: C/gdm.xml:3371(term) -msgid "GraphicalThemeRand" -msgstr "GraphicalThemeRand" - -#: C/gdm.xml:3373(synopsis) -#, no-wrap -msgid "GraphicalThemeRand=false" -msgstr "GraphicalThemeRand=false" - -#: C/gdm.xml:3374(para) -msgid "Whether the graphical greeter will use Only One Theme or Random Theme mode. Only One Theme mode uses themes listed by <filename>GraphicalTheme</filename>, Random Themes mode uses themes listed by <filename>GraphicalThemes</filename>. 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:3386(term) -msgid "GraphicalThemeDir" -msgstr "GraphicalThemeDir" - -#: C/gdm.xml:3388(synopsis) -#, no-wrap -msgid "GraphicalThemeDir=<share>/gdm/themes/" -msgstr "GraphicalThemeDir=<share>/gdm/themes/" - -#: C/gdm.xml:3389(para) -msgid "The directory where themes for the Themed Greeter are installed." -msgstr "" - -#: C/gdm.xml:3397(term) -msgid "GraphicalThemedColor" -msgstr "GraphicalThemedColor" - -#: C/gdm.xml:3399(synopsis) -#, no-wrap -msgid "GraphicalThemedColor=#76848F" -msgstr "GraphicalThemedColor=#76848F" - -#: C/gdm.xml:3400(para) -msgid "Use this color in the background of the Themed Greeter. This only affects the Themed Greeter." -msgstr "" - -#: C/gdm.xml:3408(term) -msgid "InfoMsgFile" -msgstr "InfoMsgFile" - -#: C/gdm.xml:3410(synopsis) -#, no-wrap -msgid "InfoMsgFile=/path/to/infofile" -msgstr "InfoMsgFile=/sökväg/till/informationsfil" - -#: C/gdm.xml:3411(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:3422(term) -msgid "InfoMsgFont" -msgstr "InfoMsgFont" - -#: C/gdm.xml:3424(synopsis) -#, no-wrap -msgid "InfoMsgFont=fontspec" -msgstr "InfoMsgFont=fontspec" - -#: C/gdm.xml:3425(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:3437(term) -msgid "LocaleFile" -msgstr "LocaleFile" - -#: C/gdm.xml:3439(synopsis) -#, no-wrap -msgid "LocaleFile=<etc>/gdm/locale.alias" -msgstr "LocaleFile=<etc>/gdm/locale.alias" - -#: C/gdm.xml:3440(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:3449(term) -msgid "LockPosition" -msgstr "LockPosition" - -#: C/gdm.xml:3451(synopsis) -#, no-wrap -msgid "LockPosition=true" -msgstr "LockPosition=true" - -#: C/gdm.xml:3452(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:3460(term) -msgid "Logo" -msgstr "Logo" - -#: C/gdm.xml:3462(synopsis) -#, no-wrap -msgid "Logo=<share>/pixmaps/gnome-logo-large.png" -msgstr "Logo=<share>/pixmaps/gnome-logo-large.png" - -#: C/gdm.xml:3463(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:3474(term) -msgid "ChooserButtonLogo" -msgstr "ChooserButtonLogo" - -#: C/gdm.xml:3476(synopsis) -#, no-wrap -msgid "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" -msgstr "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" - -#: C/gdm.xml:3477(para) -msgid "Image file to display in the file chooser button in <command>gdmsetup</command>. This key is modified by <command>gdmsetup</command> and should not be manually modified by the user. This only affects the Login Window Preferences (<command>gdmsetup</command>)." -msgstr "" - -#: C/gdm.xml:3488(term) -msgid "MinimalUID" -msgstr "MinimalUID" - -#: C/gdm.xml:3490(synopsis) -#, no-wrap -msgid "MinimalUID=100" -msgstr "MinimalUID=100" - -#: C/gdm.xml:3491(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 <filename>Include</filename>, <filename>Exclude</filename>, and <filename>IncludeAll</filename>." -msgstr "" - -#: C/gdm.xml:3502(term) -msgid "PositionX" -msgstr "PositionX" - -#: C/gdm.xml:3504(synopsis) -#, no-wrap -msgid "PositionX=200" -msgstr "PositionX=200" - -#: C/gdm.xml:3505(para) -msgid "The horizontal position of the login window of the GTK+ Greeter." -msgstr "" - -#: C/gdm.xml:3513(term) -msgid "PositionY" -msgstr "PositionY" - -#: C/gdm.xml:3515(synopsis) -#, no-wrap -msgid "PositionY=100" -msgstr "PositionY=100" - -#: C/gdm.xml:3516(para) -msgid "The vertical position of the login window of the GTK+ Greeter." -msgstr "" - -#: C/gdm.xml:3524(term) -msgid "Quiver" -msgstr "Quiver" - -#: C/gdm.xml:3526(synopsis) -#, no-wrap -msgid "Quiver=true" -msgstr "Quiver=true" - -#: C/gdm.xml:3527(para) -msgid "Controls whether <command>gdmlogin</command> should shake the display when an incorrect username/password is entered. This only affects the GTK+ Greeter." -msgstr "" - -#: C/gdm.xml:3537(term) -msgid "DefaultRemoteWelcome" -msgstr "DefaultRemoteWelcome" - -#: C/gdm.xml:3539(synopsis) -#, no-wrap -msgid "DefaultRemoteWelcome=true" -msgstr "DefaultRemoteWelcome=true" - -#: C/gdm.xml:3540(para) -msgid "If set to true, the value \"Welcome to %n\" is used for the <filename>RemoteWelcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>RemoteWelcome</filename> 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:3554(term) -msgid "RemoteWelcome" -msgstr "RemoteWelcome" - -#: C/gdm.xml:3556(synopsis) -#, no-wrap -msgid "RemoteWelcome=Welcome to %n" -msgstr "RemoteWelcome=Välkommen till %n" - -#: C/gdm.xml:3557(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 <filename>Welcome</filename> 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:3570(term) -msgid "RunBackgroundProgramAlways" -msgstr "RunBackgroundProgramAlways" - -#: C/gdm.xml:3572(synopsis) -#, no-wrap -msgid "RunBackgroundProgramAlways=false" -msgstr "RunBackgroundProgramAlways=false" - -#: C/gdm.xml:3573(para) -msgid "If this is true then the background application is run always, otherwise it is only run when the <filename>BackgroundType</filename> is 0 (None) This only affects the GTK+ Greeter." -msgstr "" - -#: C/gdm.xml:3583(term) -msgid "SetPosition" -msgstr "SetPosition" - -#: C/gdm.xml:3585(synopsis) -#, no-wrap -msgid "SetPosition=true" -msgstr "SetPosition=true" - -#: C/gdm.xml:3586(para) -msgid "If true the position of the login window of the GTK+ Greeter is determined by <filename>PositionX</filename> / <filename>PositionY</filename>." -msgstr "" - -#: C/gdm.xml:3595(term) -msgid "ShowGnomeFailsafeSession" -msgstr "ShowGnomeFailsafeSession" - -#: C/gdm.xml:3597(synopsis) -#, no-wrap -msgid "ShowGnomeFailsafeSession=true" -msgstr "ShowGnomeFailsafeSession=true" - -#: C/gdm.xml:3598(para) -msgid "Should the greeter show the Gnome Failsafe session in th sessions list." -msgstr "" - -#: C/gdm.xml:3606(term) -msgid "ShowLastSession" -msgstr "ShowLastSession" - -#: C/gdm.xml:3608(synopsis) -#, no-wrap -msgid "ShowLastSession=true" -msgstr "ShowLastSession=true" - -#: C/gdm.xml:3609(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 <filename>DefaultSession</filename>) 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:3622(term) -msgid "ShowXtermFailsafeSession" -msgstr "ShowXtermFailsafeSession" - -#: C/gdm.xml:3624(synopsis) -#, no-wrap -msgid "ShowXtermFailsafeSession=true" -msgstr "ShowXtermFailsafeSession=true" - -#: C/gdm.xml:3625(para) -msgid "Should the greeter show the Xterm Failsafe session in the sessions list." -msgstr "" - -#: C/gdm.xml:3633(term) -msgid "SoundOnLogin" -msgstr "SoundOnLogin" - -#: C/gdm.xml:3635(synopsis) -#, no-wrap -msgid "SoundOnLogin=true" -msgstr "SoundOnLogin=true" - -#: C/gdm.xml:3636(para) -msgid "If true, the greeter will play a sound or beep when it is ready for a login. See also the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0." -msgstr "" - -#: C/gdm.xml:3646(term) -msgid "SoundOnLoginSuccess" -msgstr "SoundOnLoginSuccess" - -#: C/gdm.xml:3648(synopsis) -#, no-wrap -msgid "SoundOnLoginSuccess=true" -msgstr "SoundOnLoginSuccess=true" - -#: C/gdm.xml:3649(para) -msgid "If true, the greeter will play a sound after a successful login attempt. See also the <filename>SoundOnLoginSuccessFile</filename> key." -msgstr "" - -#: C/gdm.xml:3658(term) -msgid "SoundOnLoginFailure" -msgstr "SoundOnLoginFailure" - -#: C/gdm.xml:3660(synopsis) -#, no-wrap -msgid "SoundOnLoginFailure=true" -msgstr "SoundOnLoginFailure=true" - -#: C/gdm.xml:3661(para) -msgid "If true, the greeter will play a sound after a failed login attempt. See also the <filename>SoundOnLoginFailureFile</filename> key." -msgstr "" - -#: C/gdm.xml:3670(term) -msgid "SoundOnLoginFile" -msgstr "SoundOnLoginFile" - -#: C/gdm.xml:3672(synopsis) -#, no-wrap -msgid "SoundOnLoginFile=/path/to/sound.wav" -msgstr "SoundOnLoginFile=/sökväg/till/ljud.wav" - -#: C/gdm.xml:3673(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) instead of a beep when the greeter is ready for a login. See also the <filename>SoundOnLogin</filename> key and the <filename>SoundProgram</filename> key. Supported since 2.5.90.0." -msgstr "" - -#: C/gdm.xml:3686(term) -msgid "SoundOnLoginSuccessFile" -msgstr "SoundOnLoginSuccessFile" - -#: C/gdm.xml:3688(synopsis) -#, no-wrap -msgid "SoundOnLoginSuccessFile=/path/to/sound.wav" -msgstr "SoundOnLoginSuccessFile=/sökväg/till/ljud.wav" - -#: C/gdm.xml:3689(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a successful login attempt. See also the <filename>SoundOnLoginSuccess</filename> key and the <filename>SoundProgram</filename> key." -msgstr "" - -#: C/gdm.xml:3700(term) -msgid "SoundOnLoginFailureFile" -msgstr "SoundOnLoginFailureFile" - -#: C/gdm.xml:3702(synopsis) -#, no-wrap -msgid "SoundOnLoginFailureFile=/path/to/sound.wav" -msgstr "SoundOnLoginFailureFile=/sökväg/till/ljud.wav" - -#: C/gdm.xml:3703(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a failed login attempt. See also the <filename>SoundOnLoginFailure</filename> key and the <filename>SoundProgram</filename> key." -msgstr "" - -#: C/gdm.xml:3714(term) -msgid "SystemMenu" -msgstr "SystemMenu" - -#: C/gdm.xml:3716(synopsis) -#, no-wrap -msgid "SystemMenu=true" -msgstr "SystemMenu=true" - -#: C/gdm.xml:3717(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:3730(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:3741(term) -msgid "TitleBar" -msgstr "TitleBar" - -#: C/gdm.xml:3743(synopsis) -#, no-wrap -msgid "TitleBar=true" -msgstr "TitleBar=true" - -#: C/gdm.xml:3744(para) -msgid "Display the title bar in the greeter. This only affects the GTK+ Greeter." -msgstr "" - -#: C/gdm.xml:3752(term) -msgid "Use24Clock" -msgstr "Use24Clock" - -#: C/gdm.xml:3754(synopsis) -#, no-wrap -msgid "Use24Clock=auto" -msgstr "Use24Clock=auto" - -#: C/gdm.xml:3755(para) -msgid "Select the use of 24 hour clock. Some locales do not support 12 hour format (like Finnish, that is <filename>fi_FI</filename>), and in those locales this setting has no effect at all." -msgstr "" - -#: C/gdm.xml:3761(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:3776(term) -msgid "UseCirclesInEntry" -msgstr "UseCirclesInEntry" - -#: C/gdm.xml:3778(synopsis) -#, no-wrap -msgid "UseCirclesInEntry=false" -msgstr "UseCirclesInEntry=false" - -#: C/gdm.xml:3779(para) -msgid "Use circles instead of asterisks in the password entry. This may not work with all fonts however." -msgstr "" - -#: C/gdm.xml:3787(term) -msgid "UseInvisibleInEntry" -msgstr "UseInvisibleInEntry" - -#: C/gdm.xml:3789(synopsis) -#, no-wrap -msgid "UseInvisibleInEntry=false" -msgstr "UseInvisibleInEntry=false" - -#: C/gdm.xml:3790(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 <filename>UseCirclesInEntry</filename> option." -msgstr "" - -#: C/gdm.xml:3800(term) -msgid "DefaultWelcome" -msgstr "DefaultWelcome" - -#: C/gdm.xml:3802(synopsis) -#, no-wrap -msgid "DefaultWelcome=true" -msgstr "DefaultWelcome=true" - -#: C/gdm.xml:3803(para) -msgid "If set to true, the value \"Welcome\" is used for the <filename>Welcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>Welcome</filename> setting is used." -msgstr "" - -#: C/gdm.xml:3813(term) -msgid "Welcome" -msgstr "Welcome" - -#: C/gdm.xml:3815(synopsis) -#, no-wrap -msgid "Welcome=Welcome" -msgstr "Welcome=Välkommen" - -#: C/gdm.xml:3816(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:3825(para) -msgid "%d — display's hostname" -msgstr "" - -#: C/gdm.xml:3829(para) -msgid "%h — Fully qualified hostname" -msgstr "" - -#: C/gdm.xml:3833(para) -msgid "%m — machine (processor type)" -msgstr "" - -#: C/gdm.xml:3837(para) -msgid "%n — Nodename (i.e. hostname without .domain)" -msgstr "" - -#: C/gdm.xml:3841(para) -msgid "%r — release (OS version)" -msgstr "" - -#: C/gdm.xml:3845(para) -msgid "%s — sysname (i.e. OS)" -msgstr "" - -#: C/gdm.xml:3849(para) -msgid "This string is only used for local logins. For remote XDMCP logins we use <filename>RemoteWelcome</filename>." -msgstr "" - -#: C/gdm.xml:3854(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:3864(term) -msgid "XineramaScreen" -msgstr "XineramaScreen" - -#: C/gdm.xml:3866(synopsis) -#, no-wrap -msgid "XineramaScreen=0" -msgstr "XineramaScreen=0" - -#: C/gdm.xml:3867(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:3878(title) -msgid "XDCMP Chooser Options" -msgstr "" - -#: C/gdm.xml:3881(title) -msgid "[chooser]" -msgstr "[chooser]" - -#: C/gdm.xml:3884(term) -msgid "AllowAdd" -msgstr "AllowAdd" - -#: C/gdm.xml:3886(synopsis) -#, no-wrap -msgid "AllowAdd=true" -msgstr "AllowAdd=true" - -#: C/gdm.xml:3887(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:3896(term) -msgid "Broadcast" -msgstr "Broadcast" - -#: C/gdm.xml:3898(synopsis) -#, no-wrap -msgid "Broadcast=true" -msgstr "Broadcast=true" - -#: C/gdm.xml:3899(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 <filename>Hosts</filename> key." -msgstr "" - -#: C/gdm.xml:3911(term) -msgid "Multicast" -msgstr "Multicast" - -#: C/gdm.xml:3913(synopsis) -#, no-wrap -msgid "Multicast=true" -msgstr "Multicast=true" - -#: C/gdm.xml:3914(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 <filename>Hosts </filename> key. The host will respond if it is listening to XDMCP requests and IPv6 is enabled there." -msgstr "" - -#: C/gdm.xml:3926(term) -msgid "MulticastAddr" -msgstr "MulticastAddr" - -#: C/gdm.xml:3928(synopsis) -#, no-wrap -msgid "MulticastAddr=ff02::1" -msgstr "MulticastAddr=ff02::1" - -#: C/gdm.xml:3929(para) -msgid "This is the Link-local Multicast address and is hardcoded here." -msgstr "" - -#: C/gdm.xml:3936(term) -msgid "DefaultHostImage" -msgstr "DefaultHostImage" - -#: C/gdm.xml:3938(synopsis) -#, no-wrap -msgid "DefaultHostImage=<share>/pixmaps/nohost.png" -msgstr "DefaultHostImage=<share>/pixmaps/nohost.png" - -#: C/gdm.xml:3939(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:3949(term) -msgid "HostImageDir" -msgstr "HostImageDir" - -#: C/gdm.xml:3951(synopsis) -#, no-wrap -msgid "HostImageDir=<share>/hosts" -msgstr "HostImageDir=<share>/hosts" - -#: C/gdm.xml:3952(para) -msgid "Repository for host icon files. The sysadmin can place icons for remote hosts here and they will appear in <filename>gdmchooser</filename>." -msgstr "" - -#: C/gdm.xml:3958(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:3968(term) -msgid "Hosts" -msgstr "Hosts" - -#: C/gdm.xml:3970(synopsis) -#, no-wrap -msgid "Hosts=host1,host2" -msgstr "Hosts=värd1,värd2" - -#: C/gdm.xml:3971(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 <filename>Broadcast</filename> 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:3983(term) -msgid "ScanTime" -msgstr "ScanTime" - -#: C/gdm.xml:3985(synopsis) -#, no-wrap -msgid "ScanTime=4" -msgstr "ScanTime=4" - -#: C/gdm.xml:3986(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:3998(title) -msgid "Debug Configuration" -msgstr "Felsökningskonfiguration" - -#: C/gdm.xml:4001(title) -msgid "[debug]" -msgstr "[debug]" - -#: C/gdm.xml:4007(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:4017(term) -msgid "Gestures" -msgstr "Gestures" - -#: C/gdm.xml:4019(synopsis) -#, no-wrap -msgid "Gestures=false" -msgstr "Gestures=false" - -#: C/gdm.xml:4020(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:4033(title) -msgid "Custom Commands" -msgstr "Anpassade kommandon" - -#: C/gdm.xml:4035(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:4044(title) -msgid "[customcommand]" -msgstr "[customcommand]" - -#: C/gdm.xml:4047(term) -msgid "CustomCommand[0-9]" -msgstr "CustomCommand[0-9]" - -#: C/gdm.xml:4049(synopsis) -#, no-wrap -msgid "CustomCommand[0-9]=" -msgstr "CustomCommand[0-9]=" - -#: C/gdm.xml:4050(para) -msgid "Full path and arguments to command to be executed when user selects <filename>n-th</filename> \"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 <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "" - -#: C/gdm.xml:4065(term) -msgid "CustomCommandIsPersistent[0-9]" -msgstr "CustomCommandIsPersistent[0-9]" - -#: C/gdm.xml:4067(synopsis) -#, no-wrap -msgid "CustomCommandIsPersistent[0-9]=" -msgstr "CustomCommandIsPersistent[0-9]=" - -#: C/gdm.xml:4068(para) -msgid "Specifies if <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "" - -#: C/gdm.xml:4082(term) -msgid "CustomCommandLabel[0-9]" -msgstr "CustomCommandLabel[0-9]" - -#: C/gdm.xml:4084(synopsis) -#, no-wrap -msgid "CustomCommandLabel[0-9]=" -msgstr "CustomCommandLabel[0-9]=" - -#: C/gdm.xml:4085(para) -msgid "Specifies the stock label that will be displayed on the <filename>n-th</filename> \"Custom Command\" buttons and menu items. If not specified the default value is \"Custom_[0-9]\". This option is only valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9. This option can't contain any semicolon characters (i.e. \";\")." -msgstr "" - -#: C/gdm.xml:4099(term) -msgid "CustomCommandLRLabel[0-9]" -msgstr "CustomCommandLRLabel[0-9]" - -#: C/gdm.xml:4101(synopsis) -#, no-wrap -msgid "CustomCommandLRLabel[0-9]=" -msgstr "CustomCommandLRLabel[0-9]=" - -#: C/gdm.xml:4102(para) -msgid "Specifies the stock label that will be displayed on the <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "" - -#: C/gdm.xml:4116(term) -msgid "CustomCommandNoRestart[0-9]" -msgstr "CustomCommandNoRestart[0-9]" - -#: C/gdm.xml:4118(synopsis) -#, no-wrap -msgid "CustomCommandNoRestart[0-9]=" -msgstr "CustomCommandNoRestart[0-9]=" - -#: C/gdm.xml:4119(para) -msgid "Specifies if gdm will be stopped/restarted once <filename>n-th</filename> \"Custom Command\" has been executed. If not specified the default value is \"false\". This option is only valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9. In addition when corresponding <filename>CustomCommandIsPersistent</filename> is set to true, setting CustomCommandNoRestart to false will place corresponding <filename>CustomCommand</filename> in the Shut Down dialog set of actions, setting it to true will place corresponding <filename>CustomCommand</filename> in the Log Out dialog set of actions." -msgstr "" - -#: C/gdm.xml:4139(term) -msgid "CustomCommandText[0-9]" -msgstr "CustomCommandText[0-9]" - -#: C/gdm.xml:4141(synopsis) -#, no-wrap -msgid "CustomCommandText[0-9]=" -msgstr "CustomCommandText[0-9]=" - -#: C/gdm.xml:4142(para) -msgid "Specifies the message that will be displayed on the warning dialog box once <filename>n-th</filename> \"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 <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "" - -#: C/gdm.xml:4156(term) -msgid "CustomCommandTooltip[0-9]" -msgstr "CustomCommandTooltip[0-9]" - -#: C/gdm.xml:4158(synopsis) -#, no-wrap -msgid "CustomCommandTooltip[0-9]=" -msgstr "CustomCommandTooltip[0-9]=" - -#: C/gdm.xml:4159(para) -msgid "Specifies the message that will be displayed on tooltips for <filename>n-th</filename> \"Custom Command\" entries. If not specified the default value is \"Execute custom command [0-9]\". This option is only valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] represents <filename>CustomCommand</filename> suffix and can be an integer between 0 and 9." -msgstr "" - -#: C/gdm.xml:4174(title) -msgid "X Server Definitions" -msgstr "" - -#: C/gdm.xml:4176(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 <filename>Standard</filename> is required. If you do not specify this server, GDM will assume default values for a 'Standard' server and the path given by <filename>daemon/StandardXServer</filename>. <filename>Standard</filename> is used as the default, in situations when no other server has been defined." -msgstr "" - -#: C/gdm.xml:4187(para) -msgid "Servers are defined by sections named <filename>server-</filename> 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, <filename>server-</filename> sections in the <filename><etc>/gdm/custom.conf</filename> file override values in the <filename><share>/gdm/defaults.conf</filename> file. In other words, if a <filename>server-Standard</filename> section is defined in <filename><etc>/gdm/custom.conf</filename>, then that will be used and the section in the <filename><share>/gdm/defaults.conf</filename> file will be ignored." -msgstr "" - -#: C/gdm.xml:4205(title) -msgid "[server-Standard]" -msgstr "[server-Standard]" - -#: C/gdm.xml:4208(term) -msgid "name" -msgstr "name" - -#: C/gdm.xml:4210(synopsis) -#, no-wrap -msgid "name=Standard server" -msgstr "name=Standardserver" - -#: C/gdm.xml:4211(para) -msgid "The name that will be displayed to the user." -msgstr "Namnet som ska visas för användaren." - -#: C/gdm.xml:4218(term) -msgid "command" -msgstr "command" - -#: C/gdm.xml:4220(synopsis) -#, no-wrap -msgid "command=/path/to/X" -msgstr "command=/sökväg/till/X" - -#: C/gdm.xml:4221(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:4229(term) -msgid "flexible" -msgstr "flexible" - -#: C/gdm.xml:4231(synopsis) -#, no-wrap -msgid "flexible=true" -msgstr "flexible=true" - -#: C/gdm.xml:4232(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:4240(term) -msgid "handled" -msgstr "handled" - -#: C/gdm.xml:4242(synopsis) -#, no-wrap -msgid "handled=true" -msgstr "handled=true" - -#: C/gdm.xml:4243(para) -msgid "Indicates that GDM should run the login window on this server and allow a user to log in. If set to false, then GDM will just run this server and wait for it to terminate. This can be useful to run an X terminal using GDM. When this is done you should normally also add <filename>-terminate</filename> to the command line of the server to make the server terminate after each session. Otherwise the control of the slave will never come back to GDM and, for example, soft restarts won't work. This is because GDM assumes there is a login in progress for the entire time this server is active." -msgstr "" - -#: C/gdm.xml:4259(term) -msgid "chooser" -msgstr "chooser" - -#: C/gdm.xml:4261(synopsis) -#, no-wrap -msgid "chooser=false" -msgstr "chooser=false" - -#: C/gdm.xml:4262(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:4273(title) -msgid "Local Static X Display Configuration" -msgstr "" - -#: C/gdm.xml:4275(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 <filename>[servers]</filename> section corresponds to the display number to be managed. Normally there is only one key, which is the key <filename>0</filename>, which corresponds to the display <filename>:0</filename>." -msgstr "" - -#: C/gdm.xml:4290(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 <filename>[servers]</filename> section in the <filename><etc>/gdm/custom.conf</filename> file overrides values in the <filename><share>/gdm/defaults.conf</filename> file." -msgstr "" - -#: C/gdm.xml:4301(title) -msgid "[servers]" -msgstr "[servers]" - -#: C/gdm.xml:4304(term) -msgid "<display number>" -msgstr "<display number>" - -#: C/gdm.xml:4306(synopsis) -#, no-wrap -msgid "0=Standard" -msgstr "0=Standard" - -#: C/gdm.xml:4307(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:4313(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 <filename><etc>/gdm/custom.conf</filename> to turn off a display that is defined in the <filename><share>/gdm/defaults.conf</filename> file." -msgstr "" - -#: C/gdm.xml:4327(para) -msgid "GDM will splice \"<filename>-auth <ServAuthDir>/:n.Xauth :n</filename>\", where n is the display number. Inside the command line before all other arguments before running the X server." -msgstr "" - -#: C/gdm.xml:4334(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 <filename>VTAllocation</filename> key is set." -msgstr "" - -#: C/gdm.xml:4343(para) -msgid "Normally you do not need to add a <filename>-nolisten tcp</filename> flag as this is added automatically for local X servers when the <filename>DisallowTCP</filename> option is set." -msgstr "" - -#: C/gdm.xml:4353(term) -msgid "priority" -msgstr "priority" - -#: C/gdm.xml:4355(synopsis) -#, no-wrap -msgid "priority=0" -msgstr "priority=0" - -#: C/gdm.xml:4356(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:4372(title) -msgid "Per User Configuration" -msgstr "" - -#: C/gdm.xml:4374(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 <filename>UserMaxFile</filename> 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:4388(para) -msgid "First there is the <filename>~/.dmrc</filename> file. In theory this file should be shared between GDM and KDM, so users only have to configure things once. This is a standard <filename>.ini</filename> style configuration file. It has one section called <filename>[Desktop]</filename> which has two keys: <filename>Session</filename> and <filename>Language</filename>." -msgstr "" - -#: C/gdm.xml:4397(para) -msgid "The <filename>Session</filename> key specifies the basename of the session <filename>.desktop</filename> file that the user wishes to normally use (without the <filename>.desktop</filename> extension, in other words). The <filename>Language</filename> key specifies the language that the user wishes to use by default. If either of these keys is missing, the system default is used. The file would normally look as follows:" -msgstr "" - -#: C/gdm.xml:4407(screen) -#, no-wrap -msgid "" -"\n" -"[Desktop]\n" -"Session=gnome\n" -"Language=cs_CZ.UTF-8\n" -msgstr "" - -#: C/gdm.xml:4413(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:4419(para) -msgid "If the GDM Face Browser is turned, then the file <filename>$HOME/.face</filename> 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 <filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> values defined in the GDM configuration or it will be ignored. Users can run the <command>gdmphotosetup</command> program to specify a face image and it will copy the file to the <filename>$HOME/.face</filename> location and scale it so its longest dimension is not larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> values. <command>gdmphotosetup</command> takes care to not change the aspect ratio of the image." -msgstr "" - -#: C/gdm.xml:4434(para) -msgid "Face images can also be placed in the global face directory, which is specified by the <filename>GlobalFaceDir</filename> configuration option ( normally <filename><share>/pixmaps/faces/</filename>) and the filename should be the name of the user, optionally with a <filename>.png</filename>, <filename>.jpg</filename>, etc. appended." -msgstr "" - -#: C/gdm.xml:4445(title) -msgid "Controlling GDM" -msgstr "" - -#: C/gdm.xml:4447(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:4454(title) -msgid "Commands" -msgstr "Kommandon" - -#: C/gdm.xml:4456(para) -msgid "To stop GDM, you can either send the TERM signal to the main daemon or run the <command>gdm-stop</command> command which is in the <filename><sbin>/</filename> directory. To restart GDM, you can either send the HUP signal to the main daemon or run the <command>gdm-restart</command> command which is also in the <filename><sbin>/</filename> 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 <command>gdm-safe-restart</command> command which is in the <filename><sbin>/</filename> directory as well." -msgstr "" - -#: C/gdm.xml:4469(para) -msgid "The <command>gdmflexiserver</command> 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 <command>gdmflexiserver</command> 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 <command>gdmflexiserver --help</command> to get a listing of possible options." -msgstr "" - -#: C/gdm.xml:4485(title) -msgid "The FIFO protocol" -msgstr "" - -#: C/gdm.xml:4487(para) -msgid "GDM also provides a FIFO called <filename>.gdmfifo</filename> in the <filename>ServAuthDir</filename> directory (usually <filename><var>/gdm/.gdmfifo</filename>). 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:4498(para) -msgid "Full and up to date documentation of the commands and their use is contained in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look for the defines starting with <filename>GDM_SOP_</filename>. The commands which require the pid of the slave as an argument are the ones that are really used for internal communication of the slave with the master and should not be used." -msgstr "" - -#: C/gdm.xml:4510(title) -msgid "Socket Protocol" -msgstr "" - -#: C/gdm.xml:4512(para) -msgid "GDM provides a unix domain socket for communication at <filename>/tmp/.gdm_socket</filename>. 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 <command>gdmflexiserver</command> command uses this protocol, for example, to launch flexible (on-demand) displays." -msgstr "" - -#: C/gdm.xml:4522(para) -msgid "gdmflexiserver accepts the following commands with the --command option:" -msgstr "" - -#: C/gdm.xml:4527(screen) -#, no-wrap -msgid "" -"\n" -"ADD_DYNAMIC_DISPLAY\n" -"ALL_SERVERS\n" -"ATTACHED_SERVERS\n" -"AUTH_LOCAL\n" -"CLOSE\n" -"FLEXI_XNEST\n" -"FLEXI_XSERVER\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_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 "" -"\n" -"ADD_DYNAMIC_DISPLAY\n" -"ALL_SERVERS\n" -"ATTACHED_SERVERS\n" -"AUTH_LOCAL\n" -"CLOSE\n" -"FLEXI_XNEST\n" -"FLEXI_XSERVER\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_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" - -#: C/gdm.xml:4553(para) -msgid "These are described in detail below, including required arguments, response format, and return codes." -msgstr "" - -#: C/gdm.xml:4559(title) -msgid "ADD_DYNAMIC_DISPLAY" -msgstr "ADD_DYNAMIC_DISPLAY" - -#: C/gdm.xml:4560(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:4582(title) -msgid "ALL_SERVERS" -msgstr "ALL_SERVERS" - -#: C/gdm.xml:4583(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:4606(title) -msgid "ATTACHED_SERVERS" -msgstr "ATTACHED_SERVERS" - -#: C/gdm.xml:4607(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 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:4639(title) -msgid "AUTH_LOCAL" -msgstr "AUTH_LOCAL" - -#: C/gdm.xml:4640(screen) -#, no-wrap -msgid "" -"\n" -"AUTH_LOCAL: Setup this connection as authenticated for\n" -" FLEXI_SERVER. Because all full blown (non-Xnest)\n" -" displays can be started only from users logged in\n" -" locally, and here GDM assumes only users logged\n" -" in from GDM. They must pass the xauth\n" -" MIT-MAGIC-COOKIE-1 that they were passed before\n" -" 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:4670(title) -msgid "CLOSE" -msgstr "CLOSE" - -#: C/gdm.xml:4671(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:4680(title) -msgid "FLEXI_XNEST" -msgstr "FLEXI_XNEST" - -#: C/gdm.xml:4681(screen) -#, no-wrap -msgid "" -"\n" -"FLEXI_XNEXT: Start a new flexible Xnest 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 Xnest using the XAUTHORITY file\n" -" supplied and as the uid same as the owner of\n" -" that file (and same as you supply). You must\n" -" also supply the cookie as the third argument\n" -" for this display, to prove that you indeed are\n" -" this user. Also this file must be readable\n" -" ONLY by this user, that is have a mode of 0600.\n" -" If this all is not met, 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:4719(title) -msgid "FLEXI_XSERVER" -msgstr "FLEXI_XSERVER" - -#: C/gdm.xml:4720(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:4742(title) -msgid "GET_CONFIG" -msgstr "GET_CONFIG" - -#: C/gdm.xml:4743(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.h is supported. Starting with version 2.13.0.2\n" -" translated keys (such as \"greeter/GdmWelcome[cs]\" are\n" -" supported via GET_CONFIG. Also starting with version\n" -" 2.13.0.2 it is no longer necessary to include the\n" -" default value (i.e. you can use key \"greeter/IncludeAll\"\n" -" instead of having to use \"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:4766(title) -msgid "GET_CONFIG_FILE" -msgstr "GET_CONFIG_FILE" - -#: C/gdm.xml:4767(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:4784(title) -msgid "GET_CUSTOM_CONFIG_FILE" -msgstr "GET_CUSTOM_CONFIG_FILE" - -#: C/gdm.xml:4785(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:4801(title) -msgid "GET_SERVER_DETAILS" -msgstr "GET_SERVER_DETAILS" - -#: C/gdm.xml:4802(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:4831(title) -msgid "GET_SERVER_LIST" -msgstr "GET_SERVER_LIST" - -#: C/gdm.xml:4832(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:4848(title) -msgid "GREETERPIDS" -msgstr "GREETERPIDS" - -#: C/gdm.xml:4849(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:4865(title) -msgid "QUERY_LOGOUT_ACTION" -msgstr "QUERY_LOGOUT_ACTION" - -#: C/gdm.xml:4866(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:4888(title) -msgid "QUERY_CUSTOM_CMD_LABELS" -msgstr "QUERY_CUSTOM_CMD_LABELS" - -#: C/gdm.xml:4889(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:4910(title) -msgid "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" -msgstr "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" - -#: C/gdm.xml:4911(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:4932(title) -msgid "QUERY_VT" -msgstr "QUERY_VT" - -#: C/gdm.xml:4933(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:4956(title) -msgid "RELEASE_DYNAMIC_DISPLAYS" -msgstr "RELEASE_DYNAMIC_DISPLAYS" - -#: C/gdm.xml:4957(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:4974(title) -msgid "REMOVE_DYNAMIC_DISPLAY" -msgstr "REMOVE_DYNAMIC_DISPLAY" - -#: C/gdm.xml:4975(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:4992(title) -msgid "SERVER_BUSY" -msgstr "SERVER_BUSY" - -#: C/gdm.xml:4993(screen) -#, no-wrap -msgid "" -"\n" -"SERVER_BUSY: Returns true if half or more of the daemon's sockets\n" -" are busy, false otherwise. Used by slave programs\n" -" which want to ensure they do not overwhelm the \n" -" sever.\n" -"Supported since: 2.13.0.8\n" -"Arguments: None\n" -"Answers:\n" -" OK <value>\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:5010(title) -msgid "SET_LOGOUT_ACTION" -msgstr "SET_LOGOUT_ACTION" - -#: C/gdm.xml:5011(screen) -#, no-wrap -msgid "" -"\n" -"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -" slave process exits. 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:5034(title) -msgid "SET_SAFE_LOGOUT_ACTION" -msgstr "SET_SAFE_LOGOUT_ACTION" - -#: C/gdm.xml:5035(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:5065(title) -msgid "SET_VT" -msgstr "SET_VT" - -#: C/gdm.xml:5066(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:5087(title) -msgid "UPDATE_CONFIG" -msgstr "UPDATE_CONFIG" - -#: C/gdm.xml:5088(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:5164(title) -msgid "VERSION" -msgstr "VERSION" - -#: C/gdm.xml:5165(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:5182(title) -msgid "GDM Commands" -msgstr "" - -#: C/gdm.xml:5185(title) -msgid "GDM User Commands" -msgstr "" - -#: C/gdm.xml:5187(para) -msgid "The GDM package provides the following different commands in <filename>bindir</filename> intended to be used by the end-user:" -msgstr "" - -#: C/gdm.xml:5193(title) -msgid "<command>gdmXnestchooser</command> and <command>gdmXnest</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5196(para) -msgid "The <command>gdmXnestchooser</command> command automatically gets the correct display number, sets up access, and runs <command>Xnest</command> with -indirect localhost. This way you get an XDMCP chooser provided by your computer. You can also supply as an argument the hostname whose chooser should be displayed, so <command>gdmXnestchooser somehost</command> will run the XDMCP chooser from host <command>somehost</command> inside an Xnest session. You can make this command do a direct query instead by passing the <command>-d</command> option as well. In addition to the following options, this command also supports standard GNOME options." -msgstr "" - -#: C/gdm.xml:5211(title) -msgid "<command>gdmXnestchooser</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5214(term) -msgid "-x, --xnest=STRING" -msgstr "-x, --xnest=STRÄNG" - -#: C/gdm.xml:5216(para) -msgid "Xnest command line, default is \"Xnest\"" -msgstr "" - -#: C/gdm.xml:5223(term) -msgid "-o, --xnest-extra-options=OPTIONS" -msgstr "-o, --xnest-extra-options=FLAGGOR" - -#: C/gdm.xml:5225(para) -msgid "Extra options for Xnest, default is no options." -msgstr "" - -#: C/gdm.xml:5232(term) -msgid "-n, --no-query" -msgstr "-n, --no-query" - -#: C/gdm.xml:5234(para) -msgid "Just run Xnest, no query (no chooser)" -msgstr "" - -#: C/gdm.xml:5241(term) -msgid "-d, --direct" -msgstr "-d, --direct" - -#: C/gdm.xml:5243(para) -msgid "Do direct query instead of indirect (chooser)" -msgstr "" - -#: C/gdm.xml:5250(term) -msgid "-B, --broadcast" -msgstr "-B, --broadcast" - -#: C/gdm.xml:5252(para) -msgid "Run broadcast instead of indirect (chooser)" -msgstr "" - -#: C/gdm.xml:5259(term) -msgid "-b, --background" -msgstr "-b, --background" - -#: C/gdm.xml:5261(para) -msgid "Run in background" -msgstr "Kör i bakgrunden" - -#: C/gdm.xml:5268(term) -msgid "--no-gdm-check" -msgstr "--no-gdm-check" - -#: C/gdm.xml:5270(para) -msgid "Don't check for running GDM" -msgstr "" - -#: C/gdm.xml:5279(title) -#: C/gdm.xml:5323(title) -msgid "<command>gdmflexichooser</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5281(para) -msgid "The <command>gdmflexiserver</command> command provides three features. It can be used to run flexible (on demand) X displays, to run a flexible display via Xnest, and to send commands to the GDM daemon process." -msgstr "" - -#: C/gdm.xml:5288(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:5302(para) -msgid "Flexible displays started via Xnest 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:5310(para) -msgid "The <command>gdmflexiserver --command</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:5316(para) -msgid "In addition to the following options, <command>gdmflexiserver</command> also supports standard GNOME options." -msgstr "" - -#: C/gdm.xml:5326(term) -msgid "-c, --command=COMMAND" -msgstr "-c, --command=KOMMANDO" - -#: C/gdm.xml:5328(para) -msgid "Send the specified protocol command to GDM" -msgstr "" - -#: C/gdm.xml:5335(term) -msgid "-n, --xnest" -msgstr "-n, --xnest" - -#: C/gdm.xml:5337(para) -msgid "Start a flexible X display in Xnest mode" -msgstr "" - -#: C/gdm.xml:5344(term) -msgid "-l, --no-lock" -msgstr "-l, --no-lock" - -#: C/gdm.xml:5346(para) -msgid "Do not lock current screen" -msgstr "" - -#: C/gdm.xml:5353(term) -msgid "-d, --debug" -msgstr "-d, --debug" - -#: C/gdm.xml:5355(para) -msgid "Turns on debugging output which gets sent to syslog. Same as turning on debug in the configuration file." -msgstr "" - -#: C/gdm.xml:5363(term) -msgid "-a, --authenticate" -msgstr "-a, --authenticate" - -#: C/gdm.xml:5365(para) -msgid "Authenticate before running --command" -msgstr "" - -#: C/gdm.xml:5372(term) -msgid "-s, --startnew" -msgstr "-s, --startnew" - -#: C/gdm.xml:5374(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:5385(title) -#: C/gdm.xml:5411(title) -msgid "<command>gdmdynamic</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5387(para) -msgid "The <command>gdmdynamic</command> command which creates, runs, and removes displays (X servers) on demand." -msgstr "" - -#: C/gdm.xml:5392(para) -msgid "<command>gdmdynamic</command> 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 <command>gdmdynamic</command> command can be used to create a new display on a particular display number, run all newly created displays, or remove a display. The <command>gdmdynamic</command> command can also be used to list all attached displays, or only attached displays that match a pattern." -msgstr "" - -#: C/gdm.xml:5403(para) -msgid "This program is designed to manage multiple simultaneous requests and works 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:5416(emphasis) -msgid "One of the following options can be used per instance:" -msgstr "" - -#: C/gdm.xml:5423(term) -msgid "-a display=server" -msgstr "-a display=server" - -#: C/gdm.xml:5425(para) -msgid "Add a new display configuration, leaving it in the DISPLAY_CONFIG state. For example, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a 3=/usr/X11R6/bin/X -dev /dev/fb2\"</command>" -msgstr "" - -#: C/gdm.xml:5431(para) -msgid "The display will not actually be started until the display is released by calling <command>gdmdynamic</command> again with the -r option." -msgstr "" - -#: C/gdm.xml:5439(term) -msgid "-r" -msgstr "-r" - -#: C/gdm.xml:5441(para) -msgid "Release (run) all displays waiting in the DISPLAY_CONFIG state." -msgstr "" - -#: C/gdm.xml:5448(term) -msgid "-d display" -msgstr "-d display" - -#: C/gdm.xml:5450(para) -msgid "Delete a display, killing the X server and purging the display configuration. For example, \"-d 3\"." -msgstr "" - -#: C/gdm.xml:5458(term) -msgid "-l [pattern]" -msgstr "-l [mönster]" - -#: C/gdm.xml:5460(para) -msgid "List displays via the ATTACHED_SERVERS <command>gdmflexiserver</command> command. Without a pattern lists all attached displays. With a pattern will match using glob characters '*', '?', and '[]'. For example: <command>\"-l Standard*\"</command><command>\"-l *Xorg*\"</command>" -msgstr "" - -#: C/gdm.xml:5473(emphasis) -msgid "These options can be added to the above:" -msgstr "" - -#: C/gdm.xml:5480(term) -msgid "-v" -msgstr "-v" - -#: C/gdm.xml:5482(para) -msgid "Verbose mode. Prinr diagnostic messages about each message sent to GDM." -msgstr "" - -#: C/gdm.xml:5490(term) -msgid "-b" -msgstr "-b" - -#: C/gdm.xml:5492(para) -msgid "Background mode. Fork child to do the work and return immediately." -msgstr "" - -#: C/gdm.xml:5499(term) -msgid "-t RETRY" -msgstr "" - -#: C/gdm.xml:5501(para) -msgid "If the daemon socket is busy, <command>gdmdynamic</command> will retry to open the connection the specified RETRY number of times. Default value is 15." -msgstr "" - -#: C/gdm.xml:5510(term) -msgid "-s SLEEP" -msgstr "" - -#: C/gdm.xml:5512(para) -msgid "If the daemon socket is busy, <command>gdmdynamic</command> 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:5527(title) -msgid "<command>gdmphotosetup</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5529(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 <filename>~/.face</filename>. This command accepts standard GNOME options." -msgstr "" - -#: C/gdm.xml:5538(title) -msgid "<command>gdmthemetester</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5540(para) -msgid "" -"<command>gdmthemetester</command> 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. <command>gdmthemetester</command> requires that the system support <command>gdmXnest</command>. Note that themes can display differently depending on the theme's \"Show mode\". <command>gdmthemetester</command> allows viewing the themes in different modes via the environment option. Valid environment values and their meanings follow: <screen>\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" -"</screen>" -msgstr "" - -#: C/gdm.xml:5566(title) -msgid "GDM Root User Commands" -msgstr "" - -#: C/gdm.xml:5568(para) -msgid "The GDM package provides the following different commands in <filename>sbindir</filename> intended to be used by the root user:" -msgstr "" - -#: C/gdm.xml:5574(title) -#: C/gdm.xml:5590(title) -msgid "<command>gdm</command> and <command>gdm-binary</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5577(para) -msgid "The <command>gdm</command> command is really just a script which runs the <command>gdm-binary</command>, passing along any options. Before launching <command>gdm-binary</command>, the gdm wrapper script will source the <filename><etc>/profile</filename> file to set the standard system environment variables. In order to better support internationalization, it will also set the LC_MESSAGES environment variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you really need to set some additional environment before launching GDM, you can do so in this script." -msgstr "" - -#: C/gdm.xml:5594(term) -msgid "--help" -msgstr "--help" - -#: C/gdm.xml:5596(para) -msgid "Gives a brief overview of the command line options." -msgstr "" - -#: C/gdm.xml:5603(term) -msgid "--nodaemon" -msgstr "--nodaemon" - -#: C/gdm.xml:5605(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:5615(term) -msgid "--no-console" -msgstr "--no-console" - -#: C/gdm.xml:5617(para) -msgid "Tell the daemon that it should not run anything on the console. This means that none of the local servers from the <filename>[servers]</filename> section will be run, and the console will not be used for communicating errors to the user. An empty <filename>[servers]</filename> section automatically implies this option." -msgstr "" - -#: C/gdm.xml:5629(term) -msgid "--config=CONFIGFILE" -msgstr "" - -#: C/gdm.xml:5631(para) -msgid "Specify an alternative configuration file." -msgstr "" - -#: C/gdm.xml:5638(term) -msgid "--preserve-ld-vars" -msgstr "--preserve-ld-vars" - -#: C/gdm.xml:5640(para) -msgid "When clearing the environment internally, preserve all variables starting with LD_. This is mostly for debugging purposes." -msgstr "" - -#: C/gdm.xml:5648(term) -msgid "--version" -msgstr "--version" - -#: C/gdm.xml:5650(para) -msgid "Print the version of the GDM daemon." -msgstr "" - -#: C/gdm.xml:5657(term) -msgid "--wait-for-go" -msgstr "--wait-for-go" - -#: C/gdm.xml:5659(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:5677(title) -msgid "<command>gdmsetup</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5679(para) -msgid "<command>gdmsetup</command> 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 <command>gdmsetup</command> 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:5691(title) -msgid "<command>gdm-restart</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5693(para) -msgid "<command>gdm-restart</command> stops and restarts GDM by sending the GDM daemon a HUP signal. This command will immediately terminate all sessions and log out users currently logged in with GDM." -msgstr "" - -#: C/gdm.xml:5701(title) -msgid "<command>gdm-safe-restart</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5703(para) -msgid "<command>gdm-safe-restart</command> stops and restarts GDM by sending the GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out." -msgstr "" - -#: C/gdm.xml:5711(title) -msgid "<command>gdm-stop</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5713(para) -msgid "<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM signal." -msgstr "" - -#: C/gdm.xml:5721(title) -msgid "GDM Internal Commands" -msgstr "" - -#: C/gdm.xml:5723(para) -msgid "The GDM package provides the following different commands in <filename>libexecdir</filename> intended to be used by the gdm daemon process." -msgstr "" - -#: C/gdm.xml:5730(title) -msgid "<command>gdmchooser</command> and <command>gdmlogin</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5733(para) -msgid "The <command>gdmgreeter</command> and <command>gdmlogin</command> are two different login applications, either can be used by GDM. <command>gdmgreeter</command> is themeable with GDM themes while <command>gdmlogin</command> is themable with GTK+ themes. These applications are normally executed by the GDM daemon. Both commands support standard GNOME options." -msgstr "" - -#: C/gdm.xml:5744(title) -#: C/gdm.xml:5755(title) -msgid "<command>gdmchooser</command> Command Line Options" -msgstr "" - -#: C/gdm.xml:5746(para) -msgid "The <command>gdmchooser</command> is the XDMCP chooser application. The <command>gdmchooser</command> is normally executed by the GDM daemon. It supports the following options for XDM compatibility. This command supports standard GNOME options and is found in support standard GNOME options." -msgstr "" - -#: C/gdm.xml:5758(term) -msgid "--xdmaddress=SOCKET" -msgstr "--xdmaddress=UTTAG" - -#: C/gdm.xml:5760(para) -msgid "Socket for XDM communication." -msgstr "" - -#: C/gdm.xml:5767(term) -msgid "--clientaddress=ADDRESS" -msgstr "--clientaddress=ADRESS" - -#: C/gdm.xml:5769(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:5777(term) -msgid "--connectionType=TYPE" -msgstr "--connectionType=TYP" - -#: C/gdm.xml:5779(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:5789(command) -msgid "gdm-ssh-session" -msgstr "gdm-ssh-session" - -#: C/gdm.xml:5791(para) -msgid "The <command>gdm-ssh-session</command> 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:5803(title) -msgid "Themed Greeter" -msgstr "" - -#: C/gdm.xml:5805(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 <ulink type=\"http\" url=\"http://art.gnome.org/themes/gdm_greeter/\"> the theme website</ulink>." -msgstr "" - -#: C/gdm.xml:5814(title) -msgid "Theme Overview" -msgstr "" - -#: C/gdm.xml:5816(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 <filename><share>/gdm/themes/<theme_name></filename>. Usually this would be under <filename>/usr/share</filename>. The theme directory should contain a file called <filename>GdmGreeterTheme.desktop</filename> which has similar format to other .desktop files and looks like:" -msgstr "" - -#: C/gdm.xml:5827(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:5838(para) -msgid "The Name, Description, Author and Copyright fields can be translated just like the other <filename>.desktop</filename>files. 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:5848(para) -msgid "Once you have theme ready and installed you can test it with the installed <command>gdmthemetester</command> script. This script assumes that the X server supports Xnest. 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:5863(command) -msgid "gdmthemetester xdmcp circles" -msgstr "" - -#: C/gdm.xml:5866(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 Xnest window. This can be done in GNOME by focusing the Xnest window and pressing Alt-PrintScreen." -msgstr "" - -#: C/gdm.xml:5874(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 <filename><share>/gdm/themes</filename> directory). And this is the tarball you distribute and people can install from the graphical configuration application. You can do this with the commands: <screen>\n" -"cd <share>/gdm/themes\n" -"tar czvf <theme_name>.tar.gz <theme_name>/\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:5888(title) -msgid "Detailed Description of Theme XML format" -msgstr "" - -#: C/gdm.xml:5891(title) -msgid "greeter tag" -msgstr "" - -#: C/gdm.xml:5893(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:5900(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 "" -"\n" -"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" -"<!DOCTYPE greeter SYSTEM \"greeter.dtd\">\n" -"<greeter gtk-theme=\"Crux\">\n" -"[...]\n" -"</greeter>\n" - -#: C/gdm.xml:5908(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:5918(title) -msgid "Box Nodes" -msgstr "" - -#: C/gdm.xml:5920(para) -msgid "" -"Box nodes are container nodes for item nodes. Box nodes are specified as follows: <screen>\n" -"<box orientation=\"alignment\" min-width=\"num\"\n" -"xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -"homogeneous=\"bool\">\n" -"</screen> 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:5936(para) -msgid "If the box is homogeneous then the children are allocated equal amount of space." -msgstr "" - -#: C/gdm.xml:5941(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:5949(title) -msgid "Fixed Nodes" -msgstr "" - -#: C/gdm.xml:5951(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: <screen>\n" -"<fixed>\n" -"</screen> Then you put other items with proper position nodes inside this." -msgstr "" - -#: C/gdm.xml:5962(para) -msgid "The \"toplevel\" node is really just like a fixed node." -msgstr "" - -#: C/gdm.xml:5968(title) -msgid "Item Nodes" -msgstr "" - -#: C/gdm.xml:5970(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:5978(term) -msgid "button" -msgstr "" - -#: C/gdm.xml:5980(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:5992(term) -msgid "entry" -msgstr "" - -#: C/gdm.xml:5994(para) -msgid "Text entry field." -msgstr "" - -#: C/gdm.xml:6001(term) -msgid "label" -msgstr "" - -#: C/gdm.xml:6003(para) -msgid "A text label. Must have a \"text\" node to specify the text." -msgstr "" - -#: C/gdm.xml:6011(term) -msgid "list" -msgstr "" - -#: C/gdm.xml:6013(para) -msgid "A face browser widget. Only useful if the face browser is enabled via the configuration." -msgstr "" - -#: C/gdm.xml:6021(term) -msgid "pixmap" -msgstr "" - -#: C/gdm.xml:6023(para) -msgid "An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, etc...)" -msgstr "" - -#: C/gdm.xml:6031(term) -msgid "rect" -msgstr "" - -#: C/gdm.xml:6033(para) -msgid "Rectangle." -msgstr "" - -#: C/gdm.xml:6040(term) -msgid "svg" -msgstr "svg" - -#: C/gdm.xml:6042(para) -msgid "Scaled Vector Graphic image." -msgstr "Scaled Vector Graphic-bild." - -#: C/gdm.xml:6049(para) -msgid "" -"For example: <screen>\n" -"<item type=\"label\">\n" -"</screen> 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:6060(para) -msgid "Entry items can have id values as follows:" -msgstr "" - -#: C/gdm.xml:6066(term) -msgid "user-pw-entry" -msgstr "user-pw-entry" - -#: C/gdm.xml:6068(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:6077(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:6087(term) -msgid "session" -msgstr "session" - -#: C/gdm.xml:6089(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:6099(term) -msgid "language" -msgstr "language" - -#: C/gdm.xml:6101(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:6111(term) -msgid "userlist" -msgstr "userlist" - -#: C/gdm.xml:6113(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:6126(term) -msgid "userlist-rect" -msgstr "userlist-rect" - -#: C/gdm.xml:6128(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:6140(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:6147(para) -msgid "Label items can have id values as follows:" -msgstr "" - -#: C/gdm.xml:6153(term) -msgid "clock" -msgstr "clock" - -#: C/gdm.xml:6155(para) -msgid "Label that displays the date and time." -msgstr "" - -#: C/gdm.xml:6162(term) -msgid "pam-prompt" -msgstr "pam-prompt" - -#: C/gdm.xml:6164(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:6172(term) -msgid "pam-error" -msgstr "pam-error" - -#: C/gdm.xml:6174(para) -msgid "Label that displayst PAM/GDM error messages. Such as when user can't log in." -msgstr "" - -#: C/gdm.xml:6182(term) -msgid "pam-error-logo" -msgstr "pam-error-logo" - -#: C/gdm.xml:6184(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:6194(term) -msgid "pam-message" -msgstr "pam-message" - -#: C/gdm.xml:6196(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:6205(term) -msgid "timed-label" -msgstr "timed-label" - -#: C/gdm.xml:6207(para) -msgid "Label that displays timed login information." -msgstr "" - -#: C/gdm.xml:6214(para) -msgid "Rectangles can have id values as follows:" -msgstr "" - -#: C/gdm.xml:6220(term) -msgid "caps-lock-warning" -msgstr "caps-lock-warning" - -#: C/gdm.xml:6222(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:6231(para) -msgid "" -"If an item is of type rect, the item can be a button. Buttons must also include a \"button\" value as follows: <screen>\n" -"<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6239(para) -msgid "Possible values for button ids are as follows." -msgstr "" - -#: C/gdm.xml:6245(term) -msgid "chooser_button" -msgstr "chooser_button" - -#: C/gdm.xml:6247(para) -msgid "Runs the XDMCP chooser." -msgstr "Kör XDMCP-väljaren." - -#: C/gdm.xml:6254(term) -msgid "config_button" -msgstr "config_button" - -#: C/gdm.xml:6256(para) -msgid "Runs the GDM configuration application." -msgstr "" - -#: C/gdm.xml:6263(term) -msgid "custom_cmd_button[0-9]" -msgstr "custom_cmd_button[0-9]" - -#: C/gdm.xml:6265(para) -msgid "Runs the <filename>n-th</filename> custom command." -msgstr "" - -#: C/gdm.xml:6272(term) -msgid "disconnect_button" -msgstr "disconnect_button" - -#: C/gdm.xml:6274(para) -msgid "Disconnect from remote session." -msgstr "" - -#: C/gdm.xml:6281(term) -msgid "language_button" -msgstr "language_button" - -#: C/gdm.xml:6283(para) -msgid "Displays the language selection dialog." -msgstr "" - -#: C/gdm.xml:6290(term) -msgid "halt_button" -msgstr "halt_button" - -#: C/gdm.xml:6292(para) -msgid "Halt (shuts down) the system." -msgstr "" - -#: C/gdm.xml:6299(term) -msgid "reboot_button" -msgstr "reboot_button" - -#: C/gdm.xml:6301(para) -msgid "Restart the system." -msgstr "Starta om systemet." - -#: C/gdm.xml:6308(term) -msgid "session_button" -msgstr "session_button" - -#: C/gdm.xml:6310(para) -msgid "List and select from available sessions." -msgstr "" - -#: C/gdm.xml:6317(term) -msgid "suspend_button" -msgstr "suspend_button" - -#: C/gdm.xml:6319(para) -msgid "Suspend the system." -msgstr "" - -#: C/gdm.xml:6326(term) -msgid "system_button" -msgstr "system_button" - -#: C/gdm.xml:6328(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:6341(title) -msgid "Position Node" -msgstr "" - -#: C/gdm.xml:6343(para) -msgid "" -"Each item can specify its position and size via the \"pos\" node. For example: <screen>\n" -"<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6351(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:6357(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:6364(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: <screen>\n" -"<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6375(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:6381(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:6387(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:6394(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: <screen>\n" -"<item type=\"label\">\n" -"<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6410(title) -msgid "Show Node" -msgstr "" - -#: C/gdm.xml:6412(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:6418(para) -msgid "<filename>console</filename> - In console mode." -msgstr "" - -#: C/gdm.xml:6421(para) -msgid "<filename>console-fixed</filename> - In console non-flexi mode." -msgstr "" - -#: C/gdm.xml:6424(para) -msgid "<filename>console-flexi</filename> - In console & flexi mode." -msgstr "" - -#: C/gdm.xml:6427(para) -msgid "<filename>flexi</filename> - In flexi mode." -msgstr "" - -#: C/gdm.xml:6430(para) -msgid "<filename>remote</filename> - In remote mode." -msgstr "" - -#: C/gdm.xml:6433(para) -msgid "<filename>remote-flexi</filename> - In remote & flexi mode." -msgstr "" - -#: C/gdm.xml:6437(para) -msgid "" -"For example: <screen>\n" -"<show modes=\"flexi,remote\"/>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6444(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:6450(para) -msgid "<filename>chooser</filename>, if ChooserButton is set to \"true\" in the GDM configuration." -msgstr "" - -#: C/gdm.xml:6454(para) -msgid "<filename>config</filename>, if ConfigAvailable is set to \"true\" in the GDM configuration." -msgstr "" - -#: C/gdm.xml:6458(para) -msgid "<filename>custom_cmd[0-9]</filename>, if <filename>n-th</filename> CustomCommand is specified in the GDM configuration." -msgstr "" - -#: C/gdm.xml:6462(para) -msgid "<filename>halt</filename>, if HaltDaemon is specified in the GDM configuration." -msgstr "" - -#: C/gdm.xml:6466(para) -msgid "<filename>reboot</filename>, if RebootCommand is specified in the GDM configuration." -msgstr "" - -#: C/gdm.xml:6470(para) -msgid "<filename>suspend</filename>, if SuspendCommand is specified in the GDM configuration." -msgstr "" - -#: C/gdm.xml:6474(para) -msgid "<filename>system</filename>, if SystemMenu is specified in the GDM configuration." -msgstr "" - -#: C/gdm.xml:6478(para) -msgid "<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in the GDM configuration." -msgstr "" - -#: C/gdm.xml:6483(para) -msgid "" -"For example: <screen>\n" -"<show modes=\"console\" type=\"system\"/>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6490(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:6499(title) -msgid "Normal/Active/Prelight Nodes" -msgstr "" - -#: C/gdm.xml:6501(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:6507(para) -msgid "<filename>normal</filename> - normal state." -msgstr "" - -#: C/gdm.xml:6510(para) -msgid "<filename>active</filename> - when the item has active focus." -msgstr "" - -#: C/gdm.xml:6513(para) -msgid "<filename>prelight</filename> - when the mouse is hovering over the item." -msgstr "" - -#: C/gdm.xml:6518(para) -msgid "" -"When item is \"rect\" (alpha can be omitted and defaults to 0.0): <screen>\n" -"<normal color=\"#ffffff\" alpha=\"0.0\">\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6526(para) -msgid "" -"When item is \"label\" <screen>\n" -"<normal color=\"#ffffff\" font=\"Sans 14\"/>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6533(para) -msgid "" -"When the item type is \"pixmap\" or \"SVG\", then the normal, active, and prelight tags specify the images to use as follows: <screen>\n" -"<normal file=\"picture.png\" tint=\"#dddddd\"/>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6542(para) -msgid "Note that relative pathnames are assumed to be in the same directory as the theme <filename>.xml</filename> file in <filename><share>/gdm/themes/<theme_name></filename>." -msgstr "" - -#: C/gdm.xml:6548(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: <screen>\n" -"<normal file=\"picture.png\" altfile1=\"distribution-blah-image.png\" altfile2=\"distribution-foo-image.png\"/>\n" -"</screen> If <filename>distribution-foo-image.png</filename> 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:6563(title) -msgid "Face Browser Icon/Label Color Nodes" -msgstr "" - -#: C/gdm.xml:6565(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:6571(screen) -#, no-wrap -msgid "" -"\n" -"<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" -msgstr "" - -#: C/gdm.xml:6578(title) -msgid "Text Node" -msgstr "" - -#: C/gdm.xml:6580(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): <screen>\n" -"<text xml:lang=\"fr\">Option</text>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6589(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: <screen>\n" -"<text>\"foo<sup>bar</sup>\"</text>\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6598(para) -msgid "Text nodes can contain the following special character sequences which will be translated as follows:" -msgstr "" - -#: C/gdm.xml:6603(para) -msgid "%% - A literal % character" -msgstr "" - -#: C/gdm.xml:6606(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:6611(para) -msgid "%d - Display name (DISPLAY environment variable)" -msgstr "" - -#: C/gdm.xml:6614(para) -msgid "%h - Hostname (gethostname output)" -msgstr "" - -#: C/gdm.xml:6617(para) -msgid "%m - Machine name (uname.machine output)" -msgstr "" - -#: C/gdm.xml:6620(para) -msgid "%n - Node name (uname.nodename output)" -msgstr "" - -#: C/gdm.xml:6623(para) -msgid "%o - Domain name (getdomainname output)" -msgstr "" - -#: C/gdm.xml:6626(para) -msgid "%r - Release name (uname.release output)" -msgstr "" - -#: C/gdm.xml:6629(para) -msgid "%s - System name (uname.sysname output)" -msgstr "" - -#: C/gdm.xml:6632(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:6640(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:6646(para) -msgid "" -"\\n" -" - Carriage return" -msgstr "" - -#: C/gdm.xml:6649(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:6657(title) -msgid "Stock" -msgstr "" - -#: C/gdm.xml:6659(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:6668(para) -msgid "<filename>cancel</filename>, _(\"_Cancel\"" -msgstr "" - -#: C/gdm.xml:6671(para) -msgid "<filename>caps-lock-warning</filename>, _(\"Caps Lock key is on.\"" -msgstr "" - -#: C/gdm.xml:6675(para) -msgid "<filename>chooser</filename>, _(\"Remote Login via _XDMCP\"" -msgstr "" - -#: C/gdm.xml:6678(para) -msgid "<filename>config</filename>, _(\"_Configure\"" -msgstr "" - -#: C/gdm.xml:6681(para) -msgid "<filename>custom_cmd[0-9]</filename>, _(\"Custom_[0-9]\"" -msgstr "" - -#: C/gdm.xml:6684(para) -msgid "<filename>disconnect</filename>, _(\"D_isconnect\"" -msgstr "" - -#: C/gdm.xml:6687(para) -msgid "<filename>halt</filename>, _(\"Shut _Down\"" -msgstr "" - -#: C/gdm.xml:6690(para) -msgid "<filename>language</filename>, _(\"_Language\"" -msgstr "<filename>language</filename>, _(\"_Språk\"" - -#: C/gdm.xml:6693(para) -msgid "<filename>ok</filename>, _(\"_OK\"" -msgstr "<filename>ok</filename>, _(\"_OK\"" - -#: C/gdm.xml:6696(para) -msgid "<filename>quit</filename>, _(\"_Quit\"" -msgstr "<filename>quit</filename>, _(\"_Avsluta\"" - -#: C/gdm.xml:6699(para) -msgid "<filename>reboot</filename>, _(\"_Restart\"" -msgstr "<filename>reboot</filename>, _(\"_Starta om\"" - -#: C/gdm.xml:6702(para) -msgid "<filename>session</filename>, _(\"_Session\"" -msgstr "<filename>session</filename>, _(\"_Session\"" - -#: C/gdm.xml:6705(para) -msgid "<filename>startover</filename>, _(\"_Start Over\"" -msgstr "" - -#: C/gdm.xml:6708(para) -msgid "<filename>suspend</filename>, _(\"Sus_pend\"" -msgstr "" - -#: C/gdm.xml:6711(para) -msgid "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\"" -msgstr "" - -#: C/gdm.xml:6715(para) -msgid "<filename>timed-label</filename>, _(\"User %u will login in %t\"" -msgstr "" - -#: C/gdm.xml:6719(para) -msgid "<filename>username-label</filename>, _(\"Username:\"" -msgstr "<filename>username-label</filename>, _(\"Användarnamn:\"" - -#: C/gdm.xml:6722(para) -msgid "<filename>welcome-label</filename>, _(\"Welcome to %n\"" -msgstr "<filename>welcome-label</filename>, _(\"Välkommen till %n\"" - -#: C/gdm.xml:6726(para) -msgid "" -"For example: <screen>\n" -"<stock type=\"welcome-label\">\n" -"</screen>" -msgstr "" -"Till exempel: <screen>\n" -"<stock type=\"welcome-label\">\n" -"</screen>" - -#: C/gdm.xml:6735(title) -msgid "Custom Widgetry" -msgstr "" - -#: C/gdm.xml:6737(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 <filename><ServAuthDir>/<display>.GreeterInfo</filename> as <filename><list id>=<listitem id></filename>." -msgstr "" - -#: C/gdm.xml:6748(para) -msgid "For example suppose we are on display :0, <filename>ServAuthDir</filename> is <filename><var>/lib/gdm</filename> and we have the following in the theme:" -msgstr "" - -#: C/gdm.xml:6755(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:6767(para) -msgid "" -"Then if the user chooses 'Foo' then <filename><var>/lib/gdm/:0.GreeterInfo</filename> will contain: <screen>\n" -"custom-config=foo\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6779(title) -msgid "Accessibility" -msgstr "Tillgänglighet" - -#: C/gdm.xml:6780(para) -msgid "GDM supports \"Accessible Login\" to allow users to log in to their desktop session even if they cannot easily use the screen, mouse, or keyboard in the usual way. Only the \"Standard Greeter\" supports accessibility, so use this login GUI for accessibility support. This is done by specifying the \"Standard Greeter\" in the \"Local\" tab for the console display and specifying the \"Standard Greeter\" in the \"Remote\" tab for remote displays. Or you can modify the <filename>Greeter</filename> configuration option by hand to be <command>gdmlogin</command>." -msgstr "" - -#: C/gdm.xml:6792(para) -msgid "The Standard Greeter supports the ability to launch assistive technologies at login time via configurable \"gestures\" from the standard keyboard, pointing device, or switch device attached to the USB or PS/2 mouse port. Also the user can change the visual appearance of the login UI before logging in, for instance to use a higher-contrast color scheme for better visibility." -msgstr "" - -#: C/gdm.xml:6802(title) -msgid "Accessibility Configuration" -msgstr "" - -#: C/gdm.xml:6803(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 configuration, AccessKeyMouseEvents and AccessDwellMouseEvents." -msgstr "" - -#: C/gdm.xml:6811(para) -msgid "In order to allow users to change the color and contrast scheme of the login dialog, make sure the <filename>AllowThemeChange</filename> parameter in the GDM configuration is set to \"true\"." -msgstr "" - -#: C/gdm.xml:6818(para) -msgid "To restrict user changes to the visual appearance to a subset of available themes, the <filename>GtkThemesToAllow</filename> parameter in the GDM configuration can be set to a list of acceptable themes separated by commas. For example:" -msgstr "" - -#: C/gdm.xml:6825(screen) -#, no-wrap -msgid "" -"\n" -"GtkThemesToAllow=HighContrast,HighContrastInverse\n" -msgstr "" - -#: C/gdm.xml:6829(para) -msgid "To enable the use of assistive technologies such as the Onscreen Keyboard, Screen Reader, or Magnifier, the <filename>AddGtkModules</filename> parameter in the GDM configuration must be uncommented and set to \"true\". Also the <filename>GtkModulesList</filename> parameter must be uncommented and set as follows:" -msgstr "" - -#: C/gdm.xml:6838(screen) -#, no-wrap -msgid "" -"\n" -"GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener\n" -msgstr "" - -#: C/gdm.xml:6842(para) -msgid "The use of assistive technologies and the atk-bridge module requires the registry daemon, <command>at-spi-registryd</command>, to be running. This is handled by the GDM GUI starting with version 2.17." -msgstr "" - -#: C/gdm.xml:6849(para) -msgid "System administrators may wish to load only the minimum subset of these modules which is required to support their user base. Depending on the end-user needs, not all of the above GtkModules may need to be loaded. If your end-users need the integrated Screen Reader and Magnifier, you must include \"gail\" and \"atk-bridge\". If your end-users will be using a pointing device without buttons or switches, include \"dwellmouselistener\". If some of your users will use pointing devices with switches, alternative physical keyboards, or switch/button devices, include \"keymouselistener\". Including all four is suitable for most system configurations. The Onscreen Keyboard can operate without gail and atk-bridge, but with a reduced feature set; for optimum accessibility we recommend including both gail and atk-bridge." -msgstr "" - -#: C/gdm.xml:6866(para) -msgid "Once \"keymouselistener\" and/or \"dwellmouselistener\" have been added to the GtkModules loaded by GDM, you can assign end-user actions with the launching of specific assistive technologies. These gesture associations are contained in files AccessKeyMouseEvents and AccessDwellMouseEvents, respectively. Both files are located in the <etc>/gdm/modules directory. The gesture format is described in the two configuration files." -msgstr "" - -#: C/gdm.xml:6877(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 Xserver command line for gestures to work properly." -msgstr "" - -#: C/gdm.xml:6889(para) -msgid "The DwellKeyMouseEvents file controls the dwellmouselistner and supports gestures that involve only 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. 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:6899(para) -msgid "Motion gestures are defined as \"crossing events\" into and out of the login dialog window. If the \"dwellmouselistener\" GtkModule is loaded, alternative pointing devices are temporarily \"latched\" to the core pointer, such that motion from alternative devices results in movement of the onscreen pointer." -msgstr "" - -#: C/gdm.xml:6908(para) -msgid "In order to use text-to-speech services at login time (for instance, when using the Screen Reader in speech mode) on some operating systems, the GDM user must be made a member of the \"audio\" group" -msgstr "" - -#: C/gdm.xml:6915(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:6926(para) -msgid "There are some issues that cause users to have problems getting the gesture listeners to work. It is recommended that people use GDM version 2.8.0.5 or later for best results. Some 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. Some versions of GOK and gnopernicus will not launch unless the \"gdm\" user has a writable home directory. If you see an hourglass cursor when you complete a gesture but the program does not start, then you are likely having this problem. It should be considered a bug for AT programs to require having a writable home directory, so please file a bug with the AT program if you encounter this problem. Also note that some input devices require X server configuration before GDM will recognize them." -msgstr "" - -#: C/gdm.xml:6947(title) -msgid "Accessibility Login Sound Configuration" -msgstr "" - -#: C/gdm.xml:6948(para) -msgid "By default, GDM requires a media application such as \"sox\" to be present to play sounds for successful or failed login. GDM defaults the location of this application to <filename><bin>/play</filename> (or <filename><bin>/audioplay</filename> on Solaris. This can be changed via the SoundProgram GDM configuration option. Typically most text-to-speech programs (such as ORCA or Gnopernicus) use a separate mechanism to play audio." -msgstr "" - -#: C/gdm.xml:6963(title) -msgid "Solaris Specific Features" -msgstr "" - -#: C/gdm.xml:6966(title) -msgid "Solaris Configuration" -msgstr "Konfiguration för Solaris" - -#: C/gdm.xml:6967(para) -msgid "" -"On Solaris, the following configuration is recommended. This turns on IPv6 and also turns on PreFetch for performance benefit. <screen>\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\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:6979(para) -msgid "Configuring GDM with the \"--with-post-path=/usr/openwin/bin\" on Solaris is recommended for access to programs like Xnest." -msgstr "" - -#: C/gdm.xml:6987(title) -msgid "Solaris /etc/logindevperm" -msgstr "Solaris /etc/logindevperm" - -#: C/gdm.xml:6988(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:6993(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:7000(screen) -#, no-wrap -msgid "" -"\n" -"/dev/console 0600 /dev/sound/* # audio devices\n" -msgstr "" -"\n" -"/dev/console 0600 /dev/sound/* # ljudenheter\n" - -#: C/gdm.xml:7004(para) -msgid "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:7017(title) -msgid "Solaris Automatic Login" -msgstr "" - -#: C/gdm.xml:7018(para) -msgid "Automatic login does not work on Solaris 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:7029(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:7037(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:7045(screen) -#, no-wrap -msgid "" -"\n" -" gdm-autologin auth required pam_unix_cred.so.1\n" -" gdm-autologin auth sufficient pam_allow.so.1\n" -" gdm-autologin account sufficient pam_allow.so.1\n" -" gdm-autologin session sufficient pam_allow.so.1\n" -" gdm-autologin password sufficient pam_allow.so.1\n" -msgstr "" -"\n" -" gdm-autologin auth required pam_unix_cred.so.1\n" -" gdm-autologin auth sufficient pam_allow.so.1\n" -" gdm-autologin account sufficient pam_allow.so.1\n" -" gdm-autologin session sufficient pam_allow.so.1\n" -" gdm-autologin password sufficient pam_allow.so.1\n" - -#: C/gdm.xml:7053(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:7058(screen) -#, no-wrap -msgid "" -"\n" -" gdm-autologin session required pam_unix_session.so.1\n" -msgstr "" -"\n" -" gdm-autologin session required pam_unix_session.so.1\n" - -#: C/gdm.xml:7064(title) -msgid "Other Solaris Features" -msgstr "" - -#: C/gdm.xml:7065(para) -msgid "GDM supports a few features specific to Solaris, as follows:" -msgstr "" - -#: C/gdm.xml:7069(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:7075(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:7084(para) -msgid "Solaris supports the <filename>/etc/default/login</filename> interface, which affects the <filename>DefaultPath</filename>, <filename>RootPath</filename>, <filename>PasswordRequired</filename>, and <filename>AllowRemoteRoot</filename> options as described in the \"Configuration\" section." -msgstr "" - -#: C/gdm.xml:7096(title) -msgid "Example Configurations" -msgstr "Exempelkonfigurationer" - -#: C/gdm.xml:7098(para) -msgid "This section has some example configurations that are useful for various setups." -msgstr "" - -#: C/gdm.xml:7104(title) -msgid "Terminal Lab With One Server" -msgstr "" - -#: C/gdm.xml:7106(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 <filename>xterminal</filename> and let's call the server machine <filename>appserver</filename>. You install GDM on both." -msgstr "" - -#: C/gdm.xml:7113(para) -msgid "" -"On <filename>appserver</filename> you enable XDMCP, so you have <screen>\n" -"[xdmcp]\n" -"Enable=true\n" -"</screen> If you want no local screens here, you can then make the <filename>[servers]</filename> section empty." -msgstr "" - -#: C/gdm.xml:7123(para) -msgid "" -"On the <filename>xterminal</filename> you disable XDMCP (you don't want anyone to connect to the xterminal really). You will add a server type perhaps called <filename>Terminal</filename> as follows: <screen>\n" -"[server-Terminal]\n" -"name=Terminal server\n" -"command=/path/to/X -terminate\n" -"flexible=false\n" -"handled=false\n" -"</screen> This definition should in fact be included in the standard configuration file. Notice that we made the <filename>handled</filename> key false since we don't want GDM to handle this server localy. Also note that we have not yet added the <filename>-query</filename> argument, you can add that here, or in the <filename>[servers]</filename> section. We'll define our local servers as follows: <screen>\n" -"[servers]\n" -"0=Terminal -query appserver\n" -"</screen> This will run a direct XDMCP query to the server named <filename>appserver</filename>." -msgstr "" - -#: C/gdm.xml:7151(title) -msgid "Terminal Lab With Two Or More Servers" -msgstr "" - -#: C/gdm.xml:7153(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 <filename>appserverone</filename> and <filename>appservertwo</filename>. Again we'll call our example X terminal server <filename>xterminal</filename>. 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:7164(para) -msgid "" -"So on the <filename>xterminal</filename> you again disable XDMCP. You will add a server type perhaps called <filename>Chooser</filename> as follows: <screen>\n" -"[server-Chooser]\n" -"name=Chooser server\n" -"command=/path/to/X\n" -"flexible=false\n" -"chooser=true\n" -"</screen> And again this definition should in fact be included in the standard configuration file. Notice that we made the <filename>chooser</filename> 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: <screen>\n" -"[servers]\n" -"0=Chooser\n" -"</screen>" -msgstr "" - -#: C/gdm.xml:7187(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 <filename>[chooser]</filename> section you would have: <screen>\n" -"Hosts=appserverone,appservertwo\n" -"</screen> and any other servers you wish the users to be able to connect to." -msgstr "" - -#: C/gdm.xml:7199(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 <filename>appserver</filename> and on the X terminals you'd have <screen>\n" -"[servers]\n" -"0=Terminal -indirect appserver\n" -"</screen> This way for example you only have to maintain one <filename>Hosts</filename> entry. However as a disadvantage then, the <filename>appserver</filename> 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:7220(title) -msgid "Defining Custom Commands" -msgstr "" - -#: C/gdm.xml:7222(para) -msgid "" -"Suppose you want to add a custom command to the GDM menu that will give you the oportunity to boot into other operating system such as Windoze. Jsut add the following options into the <filename>[customcommand]</filename> section of the GDM configuration file. <screen>\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" -" </screen> CustomCommand0 specifies two commands separated by a semicolon: <filename>/sbin/rebootwindoze</filename> and <filename>/usr/local/sbin/rebootwindoze</filename>. 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:7245(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 oportunity to run system update scripts from the login screen. Add the following options into the <filename>[customcommand]</filename> section of your GDM configuration file. <screen>\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" -" </screen>" -msgstr "" - -#: C/gdm.xml:7265(para) -msgid "" -"Both custom commands could be defined as follows. <screen>\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" -" </screen>" -msgstr "" - -#: C/gdm.xml:7286(para) -msgid "" -"There can be up to 10 custom commands numbered 0-9. <screen>\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" -" </screen>" -msgstr "" - -#: C/gdm.xml:7320(title) -msgid "Troubleshooting" -msgstr "Problemlösning" - -#: C/gdm.xml:7322(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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink> or send an email to the <address><email>gdm-list@gnome.org</email></address> mail list." -msgstr "" - -#: C/gdm.xml:7332(para) -msgid "If GDM is failing to work properly, it is always a good idea to include debug information. Use the <command>gdmsetup</command> 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 (<filename><var>/log/messages</filename> or <filename><var>/adm/messages</filename> 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:7346(para) -msgid "You should not leave debug on after collecting data. It will clutter your syslog and slow system performance." -msgstr "" - -#: C/gdm.xml:7352(title) -msgid "GDM Will Not Start" -msgstr "GDM vill inte starta" - -#: C/gdm.xml:7354(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:7363(para) -msgid "First make sure that the Xserver is configured properly. The GDM configuration file contains a command in the [server-Standard] section that is used for starting the Xserver. Verify that this command works on your system. Running this command from the console should start the Xserver. If it fails, then the problem is likely with your Xserver configuration. Refer to your Xserver error log for an idea of what the problem may be. The problem may also be that your Xserver requires different command-line options. If so, then modify the Xserver command in the GDM configuration file so that it is correct for your system." -msgstr "" - -#: C/gdm.xml:7376(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 Xserver and a terminal program, set the shell environment variable DOING_GDM_DEVELOPMENT=1 and run <command><lib>/gdmlogin</command> or <command><lib>/gdmgreeter</command>. 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:7389(para) -msgid "Also make sure that the <filename>/tmp</filename> directory has reasonable ownership and permissions, and that the machine's file system is not full. These problems will cause GDM to fail to start." -msgstr "" - -#: C/gdm.xml:7397(title) -msgid "GDM Will Not Access User Settings" -msgstr "" - -#: C/gdm.xml:7399(para) -msgid "GDM saves user settings, such as your default session and default language, in the <filename>~/.dmrc</filename>. Other files, such as the user's <filename>~/.Xauthority</filename> 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 <filename>RelaxPermissions</filename> 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:7418(title) -msgid "License" -msgstr "Licens" - -#: C/gdm.xml:7419(para) -msgid "This program is free software; you can redistribute it and/or modify it under the terms of the <ulink type=\"help\" url=\"gnome-help:gpl\"><citetitle>GNU General Public License</citetitle></ulink> as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version." -msgstr "" - -#: C/gdm.xml:7427(para) -msgid "This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public License</citetitle> for more details." -msgstr "" - -#: C/gdm.xml:7433(para) -msgid "A copy of the <citetitle>GNU General Public License</citetitle> is included as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also obtain a copy of the <citetitle>GNU General Public License</citetitle> from the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://www.fsf.org\">their Web site</ulink> or by writing to <address> Free Software Foundation, Inc. <street>59 Temple Place</street> - Suite 330 <city>Boston</city>, <state>MA</state><postcode>02111-1307</postcode><country>USA</country></address>" -msgstr "" - -#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2. -#: C/gdm.xml:0(None) -msgid "translator-credits" -msgstr "Daniel Nylander <po@danielnylander.se>, 2007" - diff --git a/docs/uk/.cvsignore b/docs/uk/.cvsignore deleted file mode 100644 index 611a1bf0..00000000 --- a/docs/uk/.cvsignore +++ /dev/null @@ -1,5 +0,0 @@ -.xml2po.mo -Makefile -Makefile.in -*.out -omf_timestamp diff --git a/docs/uk/gdm-uk.omf b/docs/uk/gdm-uk.omf deleted file mode 100644 index 5569605b..00000000 --- a/docs/uk/gdm-uk.omf +++ /dev/null @@ -1,37 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE omf PUBLIC "-//OMF//DTD Scrollkeeper OMF Variant V1.0//EN" "http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd"> -<omf> - <resource> - <creator> - Martin K. Petersen <mkp@mkp.net> - </creator> - - <creator> - George Lebl <jirka@5z.com> - </creator> - - <maintainer> - George Lebl <jirka@5z.com> - </maintainer> - - <title> - Довідка з менеджера дисплеїв Gnome - </title> - - <date> - 2003-07-19 - </date> - - <subject category="GNOME|System"/> - - <description> - Довідка з менеджера дисплеїв Gnome (GDM). - </description> - - <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/> - <identifier url="gdm.xml"/> - <language code="uk"/> - <relation seriesid="61d86786-ba0d-11d7-9eda-8a77bf52d52a"/> - <rights type="GNU FDL" license.version="1.1" holder="George Lebl and Martin K. Petersen"/> - </resource> -</omf> diff --git a/docs/uk/uk.po b/docs/uk/uk.po deleted file mode 100644 index b4e39cef..00000000 --- a/docs/uk/uk.po +++ /dev/null @@ -1,5797 +0,0 @@ -# Ukrainian translation of gdm manual. -# Copyright (C) 1999 Free Software Foundation, Inc. -# Maxim Dziumanenko <mvd@mylinux.com.ua>, 2005 -msgid "" -msgstr "" -"Project-Id-Version: gdm manual\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2006-03-15 16:02+0200\n" -"PO-Revision-Date: 2006-03-17 19:24+0300\n" -"Last-Translator: Maxim V. Dziumanenko <mvd@mylinux.ua>\n" -"Language-Team: Ukrainian <uk@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../C/legal.xml:2(para) -msgid "Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or in the file COPYING-DOCS distributed with this manual." -msgstr "Дозволяється копіювати, розповсюджувати та/або змінювати цей документ на умовах ліцензії GNU Free Documentation License (GFDL), версії 1.1 або будь-якої старшої версії, що опублікована Free Software Foundation без інваріантних розділів, тексту титульної сторінки, та тексту фінальної сторінки. Копію GFDL можна знайти <ulink type=\"help\" url=\"ghelp:fdl\">за адресою</ulink> або у файлі COPYING-DOCS, що постачається з цією довідкою." - -#: ../C/legal.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 "Ця довідка є частиною збірки документації з GNOME, що постачається на умовах ліцензії GFDL. Якщо ви бажаєте розповсюджувати цю довідку окремо від збірки, можете це зробити додавши до довідки копію ліцензії, як описано у пункті 6 ліцензії." - -#: ../C/legal.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 "Більшість назв, що використовуються компаніями для розповсюдження їх продуктів та послуг є торговими марками. Якщо такі назви зустрічаються у документації з GNOME та учасникам проекту документування GNOME відомо, що вони є торговими марками, тоді ці назви пишуться великими літерами або починаються з великої літери." - -#: ../C/legal.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) -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) -msgid "DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: <placeholder-1/>" -msgstr "ДОКУМЕНТ ТА ЗМІНЕНІ ВЕРСІЇ ЦЬОГО ДОКУМЕНТУ ПОСТАЧАЮТЬСЯ НА УМОВАХ ВІЛЬНОЇ ЛІЦЕНЗІЇ ДЛЯ ДОКУМЕНТАЦІЇ GNU З ПОДАЛЬШИМ РОЗУМІННЯМ ЩО: <placeholder-1/>" - -#: ../C/gdm.xml:11(title) -msgid "Gnome Display Manager Reference Manual" -msgstr "Посібник з менеджера дисплїв середовища Gnome" - -#: ../C/gdm.xml:14(para) -msgid "GDM is the GNOME Display Manager, a graphical login program." -msgstr "GDM - менеджер дисплеїв GNOME, графічна програма входу у сеанс." - -#: ../C/gdm.xml:21(firstname) -msgid "Martin" -msgstr "Martin" - -#: ../C/gdm.xml:21(othername) -msgid "K." -msgstr "K." - -#: ../C/gdm.xml:22(surname) -msgid "Petersen" -msgstr "Petersen" - -#: ../C/gdm.xml:24(email) -msgid "mkp@mkp.net" -msgstr "mkp@mkp.net" - -#: ../C/gdm.xml:28(firstname) -msgid "George" -msgstr "George" - -#: ../C/gdm.xml:28(surname) -msgid "Lebl" -msgstr "Lebl" - -#: ../C/gdm.xml:30(email) -msgid "jirka@5z.com" -msgstr "jirka@5z.com" - -#: ../C/gdm.xml:34(firstname) -msgid "Brian" -msgstr "Brian" - -#: ../C/gdm.xml:34(surname) -msgid "Cameron" -msgstr "Cameron" - -#: ../C/gdm.xml:36(email) -msgid "Brian.Cameron@Sun.COM" -msgstr "Brian.Cameron@Sun.COM" - -#: ../C/gdm.xml:40(firstname) -msgid "Bill" -msgstr "Bill" - -#: ../C/gdm.xml:40(surname) -msgid "Haneman" -msgstr "Haneman" - -#: ../C/gdm.xml:42(email) -msgid "Bill.Haneman@Sun.COM" -msgstr "Bill.Haneman@Sun.COM" - -#: ../C/gdm.xml:47(year) -msgid "1998" -msgstr "1998" - -#: ../C/gdm.xml:47(year) -msgid "1999" -msgstr "1999" - -#: ../C/gdm.xml:47(holder) -msgid "Martin K. Petersen" -msgstr "Martin K. Petersen" - -#: ../C/gdm.xml:50(year) -msgid "2001" -msgstr "2001" - -#: ../C/gdm.xml:50(year) -#: ../C/gdm.xml:54(year) -#: ../C/gdm.xml:57(year) -msgid "2003" -msgstr "2003" - -#: ../C/gdm.xml:50(year) -#: ../C/gdm.xml:57(year) -msgid "2004" -msgstr "2004" - -#: ../C/gdm.xml:51(holder) -msgid "George Lebl" -msgstr "George Lebl" - -#: ../C/gdm.xml:54(holder) -msgid "Red Hat, Inc." -msgstr "Red Hat, Inc." - -#: ../C/gdm.xml:57(holder) -msgid "Sun Microsystems, Inc." -msgstr "Sun Microsystems, Inc." - -#: ../C/gdm.xml:62(releaseinfo) -#: ../C/gdm.xml:71(para) -msgid "This manual describes version 2.13.0.8 of the GNOME Display Manager. It was last updated on 02/13/2006." -msgstr "У посібнику описується менеджер дисплеїв середовища Gnome версії 2.13.0.8. Останній раз оновлювався 02/13/2006." - -#: ../C/gdm.xml:69(title) -msgid "Terms and Conventions Used in This Manual" -msgstr "Терміни та домовленості використані у цьому посібнику" - -#: ../C/gdm.xml:76(para) -msgid "Chooser - A program used to select a remote host for managing a display remotely on the local display (<command>gdmchooser</command>)." -msgstr "Селектор - програма, що використовується для керування дисплеєм віддаленого вузла з локального дисплея (<command>gdmchooser</command>)." - -#: ../C/gdm.xml:81(para) -msgid "Configurator - The configuration application (<command>gdmsetup</command>)." -msgstr "Конфігуратор - програма налаштовування (<command>gdmsetup</command>)." - -#: ../C/gdm.xml:86(para) -msgid "GDM - Gnome Display Manager. Used to describe the software package as a whole. Sometimes also referred to as GDM2." -msgstr "GDM - менеджер дисплеїв середовища Gnome (Gnome Display Manager). Назва використовується при посиланні на програмний пакет взагалі. Іноді відомий як GDM2." - -#: ../C/gdm.xml:91(para) -msgid "gdm - The Gnome Display Manager daemon (<command>gdm</command>)." -msgstr "gdm - програма-сервер менеджеру дисплею середовища Gnome (<command>gdm</command>)." - -#: ../C/gdm.xml:95(para) -msgid "Greeter - The graphical login window (<command>gdmlogin</command> or <command>gdmgreeter</command>)." -msgstr "Програма привітання - графічне вікно входу (<command>gdmlogin</command> або <command>gdmgreeter</command>)." - -#: ../C/gdm.xml:100(para) -msgid "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)." -msgstr "GTK+ програма привітання - стандартне вікно входу (<command>gdmlogin</command>)." - -#: ../C/gdm.xml:104(para) -msgid "PAM - Pluggable Authentication Mechanism" -msgstr "PAM - механізм модульної автентифікації" - -#: ../C/gdm.xml:108(para) -msgid "Themed Greeter - The themable login window ( <command>gdmgreeter</command>)." -msgstr "Програма привітання з темами - вікно входу з підтримкою тем (<command>gdmlogin</command>)." - -#: ../C/gdm.xml:113(para) -msgid "XDMCP - X Display Manage Protocol" -msgstr "XDMCP - протокол керування дисплеєм X" - -#: ../C/gdm.xml:117(para) -msgid "Paths that start with a word in angle brackets are relative to the installation prefix. I.e. <filename><share>/pixmaps/</filename> refers to <filename><share>/pixmaps</filename> if GDM was configured with <command>--prefix=/usr</command>. Normally also note that GDM is installed with <command>--sysconfigdir=<etc>/X11</command>, meaning any path to which we refer to as <filename><etc>/gdm/PreSession</filename> usually means <filename><etc/X11>/gdm/PreSession</filename>. Note that for interoperability it is recommended that you use a --prefix of <filename>/usr</filename> and a --sysconfdir of <filename><etc>/X11</filename>." -msgstr "Шляхи, що починаються з кутових дужок є відносними до префіксу встановлення пакету. Наприклад, <filename><share>/pixmaps/</filename> перетворюється у <filename><share>/pixmaps</filename>, якщо GDM був зібрано з <filename><share>/pixmaps</filename>. Зазвичай, GDM встановлено з <command>--sysconfigdir=<etc>/X11</command>, таким чином посилання на шлях <filename><etc>/gdm/PreSession</filename> перетворюється у <filename><etc>/gdm/PreSession</filename>. Зауважте, для сумісності з іншими системами рекомендовано, щоб значення prefix було <filename>/usr</filename>, а значення sysconfdir було <filename><etc>/X11</filename>." - -#: ../C/gdm.xml:133(title) -msgid "Overview" -msgstr "Огляд" - -#: ../C/gdm.xml:136(title) -msgid "Introduction" -msgstr "Введення" - -#: ../C/gdm.xml:140(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 "GDM - менеджер дисплею для GNOME, у якому реалізовано більшість функцій, що вимагаються для керування локальними та віддаленими дисплеями. GDM створено \"з чистого аркуша\" та він не містить оригінального коду XDM / X Consortium." - -#: ../C/gdm.xml:147(para) -msgid "For further information about GDM, see the <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. Please submit any bug reports or enhancement requests to the \"gdm\" category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>. You can also send a message to the <address><email>gdm-list@gnome.org</email></address> mail list to discuss any issues or concerns with the GDM program." -msgstr "Подальшу інформацію про GDM шукайте на сторінці <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\">проекту GDM</ulink>. Надсилайте повідомлення про будь-які помилки чи вдосконалення з категорією \"gdm\" на сайт <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>. Також можна надсилати повідомлення до списку розсилки <address><email>gdm-list@gnome.org</email></address>, де обговорюються питання пов'язані з програмою GDM." - -#: ../C/gdm.xml:160(title) -msgid "Interface Stability" -msgstr "Стабільність інтерфейсу" - -#: ../C/gdm.xml:164(para) -msgid "The key/value pairs defined in the GDM configuration files and the location of these files are considered \"stable\" interfaces and should only change in ways that are backwards compatible. Note that this includes functionality like the GDM scripts (Init, PreSession, PostSession, PostLogin, XKeepsCrashing, etc.); directory locations (ServAuthDir, PidFile, etc.), system applications (SoundProgram), etc. Some configuration values depend on OS interfaces may need to be modified to work on a given OS. Typical examples are HaltCommand, RebootCommand, SuspendCommand, StandardXServer, Xnest, SoundProgram, and the \"command\" value for each \"server-foo\"." -msgstr "" - -#: ../C/gdm.xml:177(para) -msgid "Note: distributions often change the default values of keys to support their platform. Command-line interfaces for GDM programs installed to <filename><bin></filename> and <filename><sbin></filename> 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:186(para) -msgid "If issues are discovered that break compatibility, please file a bug with an \"urgent\" priority." -msgstr "" - -#: ../C/gdm.xml:193(title) -msgid "The GDM Daemon" -msgstr "Сервер GDM" - -#: ../C/gdm.xml:195(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 <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename>, and <filename>PostSession</filename> scripts discussed below are discussed in this \"Configuring GDM section\"." -msgstr "" - -#: ../C/gdm.xml:206(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:213(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 <command>gdmflexiserver</command> command. Displays that are started on request are not restarted on session exit. GDM also provides the <command>gdmdynamic</command> 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:225(para) -msgid "When the GDM daemon is asked to manage a display, it will fork an X server process, then run the <filename>Init</filename> script as the root user, and start the login GUI dialog as a slave process on the display. GDM can be configured to use either <command>gdmgreeter</command> (the default) or <command>gdmlogin</command> as the GUI dialog program. The <command>gdmlogin</command> program supports accessibility while the <command>gdmgreeter</command> program supports greater themeability. The GUI dialog is run as the unpriviledged \"gdm\" user/group which is described in the \"Security\" section below. The GUI dialog communicates with the daemon via a sockets protocol and via standard input/output. The slave, for example passes the username and password information to the GDM daemon via standard input/output so the daemon can handle the actual authentication." -msgstr "" - -#: ../C/gdm.xml:242(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:257(para) -msgid "GDM, by default, will use Pluggable Authentication Modules (PAM) for authentication, but can also support regular crypt and shadow passwords on legacy systems. After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, and forks a slave process to start the requested session. This slave process runs the <filename>PreSession</filename> script as root, sets up the users environment, and starts the requested session. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN interface after user authentication to tell the X server to be restarted as the user instead of as root for added security. When the users session exits, the GDM daemon will run the <filename>PostSession</filename> script as root." -msgstr "" - -#: ../C/gdm.xml:276(title) -msgid "Different Display Types" -msgstr "Різні типи дисплеїв" - -#: ../C/gdm.xml:278(para) -msgid "GDM supports three different display types: static (local) displays, flexible (on-demand) displays, and XDMCP (remote) displays. The \"X Server Definitions\" and the \"Local Static X Display Configuration\" subsections of the \"Configuration\" section explains how these various types of displays are defined in the GDM configuration file." -msgstr "" - -#: ../C/gdm.xml:287(para) -msgid "Local static displays are always started by the daemon, and when they die or are killed, they are restarted. GDM can run as many of these as needed. GDM can also manage displays on which it does not manage a GUI login, thus GDM can be used for supporting X terminals." -msgstr "Локальні статичні дисплеї завжди запускаються службою, якщо вони завершуються або вмирають, вони перезапускаються. GDM може запускати їх стільки, скільки буде потрібно. GDM також може керувати серверами, на яких він не керує власне самим процесом входу, це дозволяє використовувати GDM при створенні X-терміналів." - -#: ../C/gdm.xml:294(para) -msgid "Flexible, or on demand displays, are started via the socket protocol with the <command>gdmflexiserver</command> command. This feature is only available to users logged in on the console and will display a new login screen. If a flexible display has previously been started on the console, running <command>gdmflexiserver</command> again will display a menu allowing users to switch back to a previous session or start a new flexible session. The <command>gdmflexiserver</command> locks the current session before starting a new flexible display, so the user's password must be entered before returning to an existing session. The <command>gdmflexiserver</command> command can also be used to launch nested <command>Xnest</command> display. These are launched in a window in the user's current session. Nested displays can be started even if not logged into the console and are started by running the <command>gdmflexiserver -n</command> command. Flexible displays are not restarted when the user session ends. Flexible displays require virtual terminal (VT) support in the kernel, and will not be available if not supported (such as on Solaris). Nested displays require that the X server supports Xnest." -msgstr "" - -#: ../C/gdm.xml:315(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 "Останній тип дисплеїв - віддалені XDMCP дисплеї, які описані у наступному розділі. Якщо цей параметр увімкнено, віддалені вузли можуть з'єднуватись з GDM та показувати вікно входу. Для цього типу сеансів є відмінності, наприклад, у меню <quote>Дії</quote> не показуються пункти, які дозволяють вимикати, перезавантажувати, або налаштовувати GDM." - -#: ../C/gdm.xml:323(para) -msgid "Displays started via the <command>gdmdynamic</command> command are treated as local displays, so they are restarted automatically on when the session exits. This command is intended to more effectively manage the displays on a multi-user server (many displays connected to a single server)." -msgstr "" - -#: ../C/gdm.xml:333(title) -msgid "XDMCP" -msgstr "XDMCP" - -#: ../C/gdm.xml:337(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:346(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 "GDM включає декілька заходів, які роблять його більш стійким до атак типу <quote>відмова у обслуговуванні</quote> на службу XDMCP. Можна налаштувати значну кількість параметрів протоколу, час очікування з'єднання, тощо. Проте, типові значення підійдуть для більшості систем. Не змінюйте їх, якщо не розумієте їх вплив на систему." - -#: ../C/gdm.xml:354(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 "GDM прослуховує UDP порт 177 та відповідає не запити QUERY та BROADCAST_QUERY надсилаючи пакет WILLING ініціатору з'єднання." - -#: ../C/gdm.xml:359(para) -msgid "GDM can also be configured to honor INDIRECT queries and present a host chooser to the remote display. GDM will remember the user's choice and forward subsequent requests to the chosen manager. GDM also supports an extension to the protocol which will make it forget the redirection once the user's connection succeeds. This extension is only supported if both daemons are GDM. It is transparent and will be ignored by XDM or other daemons that implement XDMCP." -msgstr "GDM можна налаштувати на обробку INDIRECT запитів та відображення селектора вузлів на віддаленому дисплеї. GDM запам'ятовує вибір користувача та пересилає наступні запити вибраному менеджеру. GDM також підтримує розширення до протоколу, яке змушує забути про перенаправлення одразу після успішного з'єднання користувача. Це розширення підтримується якщо з обох сторін сервери GDM. Розширення прозоре і ігнорується XDM та іншими серверами, що підтримують XDMCP." - -#: ../C/gdm.xml:369(para) -msgid "Refer to the \"Security\" section for information about security concerns when using XDMCP." -msgstr "" - -#: ../C/gdm.xml:376(title) -msgid "Securing Remote Connection Through SSH" -msgstr "Безпечне віддалене з'єднання через SSH" - -#: ../C/gdm.xml:379(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:386(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:396(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:403(title) -msgid "The GTK+ Greeter" -msgstr "Програма привітання на GTK+" - -#: ../C/gdm.xml:405(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 "Програма привітання на GTK+ - типовий графічний інтерфейс користувача. Вікно привітання містить меню, необов'язковий переглядач портретів, необов'язкову емблему та текстове поле. Програма привітання має повну підтримку допоміжних технологій та має використовуватись у випадках, якщо потрібна така підтримка." - -#: ../C/gdm.xml:413(para) -msgid "The text entry field is used for entering logins, passwords, passphrases etc. <command>gdmlogin</command> 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 "Текстове поле використовується для вводу імен користувачів, паролів, парольних фраз тощо. <command>gdmlogin</command> контролюється основним сервером та не має певного стану. Сервер контролює вікно привітання використовуючи простий протокол, він може запитати у програми привітання текстовий рядок в виводом копії рядка або без виводу. Подібним чином, сервер може змінити етикетку над текстовим полем, щоб її вміст відповідав значенню, яке система автентифікації очікує від користувача." - -#: ../C/gdm.xml:423(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 "Панель меню вгорі вікна привітання дозволяє користувачу вибрати тип сеансу/робочого середовища, вибрати відповідну локалізацію/мову та зупинити/перезавантажити/призупинити комп'ютер, налаштувати GDM (якщо користувач знає пароль адміністратора (root)), змінити тему GTK+, або запустити селектор XDMCP." - -#: ../C/gdm.xml:431(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 <filename>Logo</filename> option in the reference section below for details." -msgstr "Вікно привітання може відображати портрет у вікні входу. Зображення повинно бути у форматі, зрозумілому для бібліотеки gdk-pixbuf (GIF, JPG, PNG, TIFF, XPM та можливо іншому), та має бути доступним для читання користувачу gdm. Докладнішу інформацію дивіться у описі параметра <filename>Logo</filename> у розділі опису конфігураційного файлу." - -#: ../C/gdm.xml:441(title) -msgid "The Themed Greeter" -msgstr "Програма привітання з темами" - -#: ../C/gdm.xml:443(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 <filename>GraphicalTheme</filename> configuration key. The Themed Greeter is much like the GTK+ Greeter in that it is controlled by the underlying daeon, is stateless, and is controlled by the daemon using the same simple protocol." -msgstr "Програма привітання з темами - графічний інтерфейс, який займає весь екран та має підтримку тем зовнішнього вигляду. Теми можна вибирати та встановлювати у програмі налаштовування gdm, або ж можна визначити поточну тему у конфігураційній змінній <filename>GraphicalTheme</filename>. Програма привітання з темами подібна до стандартної програми привітання GTK+ у тому, що вона теж контролюється основним сервером, не має стану та контролюється тип самим простим протоколом." - -#: ../C/gdm.xml:453(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 "Зовнішній вигляд вікна привітання залежить від теми, тому елементи інтерфейсу можуть відрізнятись. Єдиний елемент який завжди присутній - це текстове поле, яке описане у розділі <quote>Програма привітання на GTK+</quote>. Тема вожу включати кнопки вибору локалі/мови, зупинення/перезапуску/призупинення комп'ютера, налаштовування GDM (якщо користувач знає пароль адміністратора (root)), чи запуску селектора XDMCP. " - -#: ../C/gdm.xml:463(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 "Ви завжди можете вивести меню з наявними діями натиснувши на клавішу F10. Це може знадобитись, якщо тема не містить деяких кнопок, але ви бажаєте виконати певну дію, що дозволена конфігурацією." - -#: ../C/gdm.xml:471(title) -msgid "The GDM Face Browser" -msgstr "Переглядач портретів GDM" - -#: ../C/gdm.xml:473(para) -msgid "GDM supports a face browser which will display a list of users who can login and an icon for each user. This feature can be used with the GTK+ Greeter if the <filename>Browser</filename> configuration option is set to \"true\". This feature can be used with the Themed Greeter if using a GDM theme which includes a \"userlist\" item type is defined, such as \"happygnome-list\"" -msgstr "" - -#: ../C/gdm.xml:483(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 <command>gdmsetup</command>. This feature is most practical to use on a system with a smaller number of users." -msgstr "" - -#: ../C/gdm.xml:492(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 <filename><share>/pixmaps/faces/</filename> directory (though this can be configured with the <filename>GlobalFaceDir</filename> configuration option) and the filename should be the name of the user, optionally with a <filename>.png</filename> 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 "Зображення можуть бути встановлені глобально адміністратором, або братись з домашніх каталогів користувачів. Якщо вони встановлені глобально, вони мають знаходитись у каталозі <filename><share>/pixmaps/faces/</filename> (шлях до каталогу можна змінити використовуючи конфігураційну змінну <filename>GlobalFaceDir</filename>) та назва файлу повинна відповідати імені користувача, з необов'язковим суфіксом <filename>.png</filename>. Значки програм з глобального каталогу мають бути доступні для читання користувачу GDM. Проте, програма сервера передає зображення програмі привітання та таким права на читання потрібні не не користувачу \"gdm\", а root." - -#: ../C/gdm.xml:505(para) -msgid "Users may run the <command>gdmphotosetup</command> command to configure the image to use for their userid. This program properly scales the file down if it is larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> configuration options and places the icon in a file called <filename>~/.face</filename>. Although <command>gdmphotosetup</command> scales user images automatically, this does not guarantee that user images are properly scaled since a user may create their <filename>~/.face</filename> file by hand." -msgstr "" - -#: ../C/gdm.xml:517(para) -msgid "GDM will first look for the user's face image in <filename>~/.face</filename>. If not found, it will try <filename>~/.face.icon</filename>. If still not found, it will use the value defined for \"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file. Lastly, it will try <filename>~/.gnome2/photo</filename> and <filename>~/.gnome/photo</filename> which are deprecated and supported for backwards compatibility." -msgstr "" - -#: ../C/gdm.xml:528(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 <filename>DefaultFace</filename> configuration option, normally <filename><share>/pixmaps/nobody.png</filename>." -msgstr "" - -#: ../C/gdm.xml:536(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 <filename>Include</filename> 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 <filename>GlobalFaceDir</filename> configuration option." -msgstr "" - -#: ../C/gdm.xml:552(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 <filename>IncludeAll</filename> option is set to true, then the password file will be scanned and all users will be displayed. If <filename>IncludeAll</filename> option is set to false, then the <filename>Include</filename> option should contain a list of users separated by commas. Only the users specified will be displayed. Any user listed in the <filename>Exclude</filename> option and users whose UID's is lower than <filename>MinimalUID</filename> will be filtered out regardless of the <filename>IncludeAll</filename> setting. <filename>IncludeAll</filename> is not 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 "Для керування відображенням портретів у конфігураційному файлі є декілька параметрів. Якщо параметр <filename>IncludeAll</filename> встановлено у true, тоді у параметрі <filename>Include</filename> вказується список розділених комою імен користувачів, які будуть відображатись. Не залежно від параметра <filename>IncludeAll</filename> не будуть відображатись будь-які користувачі, перелічені у списку <filename>Exclude</filename> та користувачі, ідентифікатор користувача (UID) яких менший за <filename>MinimalUID</filename>. <filename>IncludeAll</filename> не рекомендується для систем, на яких паролі передаються через мережу (наприклад NIS), тому що передавання великої кількості зображень через мережу може бути досить повільним." - -#: ../C/gdm.xml:569(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 "Якщо ввімкнено перегляд портретів, потенційному зловмиснику виставляється на показ список дійсних імен користувачів. Це погана ідея, якщо ви не знаєте хто може отримати доступ до екрану входу. Особливо це стосується випадку, коли використовується XDMCP (зазвичай вимкнено). " - -#: ../C/gdm.xml:578(title) -msgid "Logging" -msgstr "Реєстрація подій" - -#: ../C/gdm.xml:580(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 "GDM використовує syslog для реєстрації помилок або стану. Також він може реєструвати налагоджувальну інформацію, що можна використовувати при аналізі проблем з GDM, якщо він неправильно працює. Реєстрацію налагоджувальної інформації можна увімкнути у конфігураційному файлі." - -#: ../C/gdm.xml:587(para) -msgid "Output from the various X servers is stored in the GDM log directory, which is configurable, but is usually <filename><var>/log/gdm/</filename>. The output from the session can be found in a file called <filename><display>.log</filename>. Four older files are also stored with <filename>.1</filename> through <filename>.4</filename> 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 "Інформація отримана з різних X серверів зберігається у реєстраційному каталозі GDM. Зазвичай це <filename><var>/log/gdm/</filename>, але його можна змінити. Інформацію про сеанс можна знайти у файлі з назвою <filename><display>.log</filename>. Чотири попередні версії зберігаються у файлах з назвою, до якої додаються суфікси від <filename>.1</filename> до <filename>.4</filename>. Інформація про нові сеанси замінює інформацію про старіші сеанси. Ви можете скористатись цими файлами, щоб переглянути інформацію від X-сервера при його запуску." - -#: ../C/gdm.xml:599(para) -msgid "The output from the user session is redirected to <filename>~/.xsession-errors</filename> before even the <filename>PreSession</filename> 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 "Інформація від сеансів користувача направляється у файл <filename>~/.xsession-errors</filename> перед запуском сценарію <filename>PreSession</filename>. Тому немає потреби перенаправляти її знову у сценарії встановлення сеансу. Якщо сеанс користувача тривав менше за 10 секунд, GDM вважає, що сеанс завершився аварійно та дозволяє користувачу переглянути цей файл у вікні, до того як повернутись до віна входу. Таким чином користувач може переглянути помилки під час останнього сеансу та виправити їх." - -#: ../C/gdm.xml:611(para) -msgid "You can suppress the 10 second warning by returning code 66 from the <filename>Xsession</filename>script or from your session binary (the default <filename>Xsession</filename> 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 "Можна позбутись виводу повідомлення про малу тривалість сеансу, якщо вернути код результату 66 із сценарію <filename>Xsession</filename> або двійкового файлу сеансу (типовий сценарій <filename>Xsession</filename> передає цей код назад). Це корисно, якщо у вас є особливий тип входу у сеанс, для якого тривалість сеансу менша за 10 секунд не є помилкою, або якщо ваш сеанс вже налаштований для відображення повідомлення про помилку, та повідомлення від gdm буде зайвим і буде збивати з пантелику." - -#: ../C/gdm.xml:621(para) -msgid "The session output is piped through the GDM daemon and so the <filename>~/.xsession-errors</filename> file is capped at about 200 kilobytes by GDM to prevent a possible denial of service attack on the session. An app could perhaps on reading some wrong data print out warnings or errors on the stderr or stdout. This could perhaps fill up the users home directory who would then have to log out and log back in to clear this. This could be especially nasty if quotas are set. GDM also correctly traps the XFSZ signal and stops writing the file, which would lead to killed sessions if the file was redirected in the old fashioned way from the script." -msgstr "Інформація від сеансу перенаправляється через сервер GDM, тому GDM обмежує розмір файлу <filename>~/.xsession-errors</filename> значенням 200 кілобайт, щоб запобігти атакам на сеанс типу <quote>відмова у обслуговуванні</quote>. Програма могла б при читанні деяких неправильних даних виводити попередження та помилки у стандартний потік виводу чи у стандартний потік помилок. Це могло б призвести до заповнення домашнього каталогу користувача, якому б довелось вийти та зайти знову щоб очистити файл реєстрації. Це було б особливо неприємно, якщо встановлено дискові квоти. GDM також коректно перехоплює сигнал XFSZ та припиняє запис у файл, що могло б призвести до знищення сеансів, якщо файл був переправлений старим способом зі сценарію." - -#: ../C/gdm.xml:634(para) -msgid "Note that some distributors seem to override the <filename>~/.xsession-errors</filename> redirection and do it themselves in their own Xsession script (set by the <filename>BaseXsession</filename> configuration key) which means that GDM will not be able to trap the output and cap this file. You also lose output from the <filename>PreSession</filename> 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 <filename>BaseXsession</filename> configuration key for more information, especially on how to handle multiple display managers using the same script." -msgstr "Зауважте, у деяких дистрибутивах перевизначають перенаправлення <filename>~/.xsession-errors</filename> та роблять перенаправлення у своєму власному сценарії Xsession (визначається конфігураційною змінною <filename>BaseXsession</filename>). Це означає, що GDM не зможе перехоплювати вивід та обмежувати цей файлу. Також ви втрачаєте інформацію, яка виводиться сценарієм <filename>PreSession</filename>, що може ускладнити налагодження та пошук помилки, бо частина інформації не буде виведена. Докладнішу інформацію дивіться у описі конфігураційного параметра <filename>BaseXsession</filename>, особливо спосіб обробки інформації від декількох менеджерів дисплеїв у одному сценарії." - -#: ../C/gdm.xml:648(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 <filename>/tmp</filename> directory named <filename>/tmp/xses-<user>.XXXXXX</filename> where the <filename>XXXXXX</filename> are some random characters." -msgstr "Зверніть увагу, якщо сеанс є аварійним, або якщо GDM з деяких причин не може відкрити цей файл, тоді створюється запасний файл у каталозі <filename>/tmp</filename> з назвою <filename>/tmp/xses-<user>.XXXXXX</filename>, де <filename>XXXXXX</filename> - деякі випадкові символи." - -#: ../C/gdm.xml:656(para) -msgid "If you run a system with quotas set, it would be good to delete the <filename>~/.xsession-errors</filename> in the <filename>PostSession</filename> script. Such that this log file doesn't unnecessarily stay around." -msgstr "Якщо у вашій системі використовуються квоти, краще буде видаляти <filename>~/.xsession-errors</filename> у сценарії <filename>PostSession</filename>. Тоді цей реєстраційний файл не буде без необхідності залишатись." - -#: ../C/gdm.xml:665(title) -msgid "Accessing Files" -msgstr "Доступ до файлів" - -#: ../C/gdm.xml:667(para) -msgid "In general GDM is very reluctant regarding reading/writing of user files (such as the <filename>~/.dmrc</filename>, <filename>~/.face</filename>, <filename>~/.xsession-errors</filename>, and <filename>~/.Xauthority</filename> files). For instance it refuses to access anything but regular files. Links, sockets and devices are ignored. The value of the <filename>RelaxPermissions</filename> parameter determines whether GDM should accept files writable by the user's group or others. These are ignored by default." -msgstr "Взагалі, GDM дуже неохочій відносно зчитування/запису файлів користувачів (таких як <filename>~/.dmrc</filename>, <filename>~/.face</filename>, <filename>~/.xsession-errors</filename>, та <filename>~/.Xauthority</filename> files). Наприклад, він відмовляється обробляти будь-який тип файлів, крім звичайних файлів. Посилання, сокети та пристрої ігноруються. Значення параметру <filename>RelaxPermissions</filename> вказує чи повинен GDM сприймати файли, до яких є доступ на запис з боку групи їх власника, чи інших осіб. Зазвичай вони ігноруються." - -#: ../C/gdm.xml:679(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 <filename>.Xauthority</filename> file, a fallback cookie is created in the directory specified by the <filename>UserAuthFBDir</filename> configuration setting (<filename>/tmp</filename> by default)." -msgstr "Всі операції над файлами користувача виконуються з ефективним ідентифікатором користувача який відповідає власнику цих файлів. Якщо перевірка безпечності файлу <filename>.Xauthority</filename> завершується невдало, створюються аварійні cookie у каталозі що визначається <filename>UserAuthFBDir</filename> (типово це <filename>/tmp</filename>)." - -#: ../C/gdm.xml:687(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 "Зрештою, системний адміністратор може вказати максимальний розмір файлу, який оброблятиме GDM. Якщо ввімкнено переглядач портретів, то можна вказати максимальний розмір файлу зображення. На великих системах, з міркувань швидкодії, рекомендується вимкнути переглядач портретів. Перегляд домашніх каталогів користувачів, зміна масштабу та відображення портретів може зайняти значний час." - -#: ../C/gdm.xml:698(title) -msgid "GDM Performance" -msgstr "Швидкодія GDM" - -#: ../C/gdm.xml:700(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:708(para) -msgid "To use this feature, configure GDM with the <command>--with-prefetch</command> option. This will cause GDM to install the <command>gdmprefetch</command> program to the EXPANDED_LIBEXEC directory, install the <filename>gdmprefetchlist</filename> to the <filename><etc>/gdm</filename> directory, and set the <filename>PreFetchProgram</filename> configuration variable so that the <command>gdmprefetch</command> program is called with the default <filename>gdmprefetchlist</filename> file. The default <filename>gdmprefetchlist</filename> 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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink>, so that they can be included in future GDM releases." -msgstr "" - -#: ../C/gdm.xml:729(title) -msgid "Security" -msgstr "Безпека" - -#: ../C/gdm.xml:732(title) -msgid "PAM" -msgstr "PAM" - -#: ../C/gdm.xml:735(para) -msgid "GDM uses PAM for username/authentication, though if your machine does not support PAM you can build GDM to work with shadow passwords and crypt." -msgstr "" - -#: ../C/gdm.xml:741(para) -msgid "PAM stands for Pluggable Authentication Module, and is used by most programs that request username/password authentication on your computer. It allows the user to configure different authentication behavior for different programs." -msgstr "" - -#: ../C/gdm.xml:748(para) -msgid "Some GDM features (like turning on automatic login) may require that you update your PAM configuration. PAM has different, but similar, interfaces on different operating systems, so check your pam.d or pam.conf man page for details about how to configure it. 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:758(para) -msgid "If there is no entry for GDM in your system's PAM configuration file, then features like tomatic login may not work. Not having an entry will causes GDM to use default behavior, conservative settings are recommended and probably shipped with your distribution." -msgstr "" - -#: ../C/gdm.xml:765(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 writing a PAM module 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 <address><email>gdm-list@gnome.org</email></address> mail list, so you can refer to the list archives for more information." -msgstr "" - -#: ../C/gdm.xml:777(title) -msgid "The GDM User" -msgstr "Користувач GDM" - -#: ../C/gdm.xml:779(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:785(para) -msgid "The GDM daemon normally runs as root, as does the slave. However GDM should also have a dedicated user id and a group id which it uses for its graphical interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</command>. These are configured via the <filename>User</filename> and <filename>Group</filename> configuration options in the GDM configuration files. The user and group should be created before running \"make install\". By default GDM assumes the user and the group are called \"gdm\"." -msgstr "Зазвичай GDM сервер запускається від імені адміністратора (root). Але GDM також має призначені ідентифікатори користувача (uid) та групи (gid), якими він користується для запуску графічного інтерфейсу, тобто <command>gdmgreeter</command> та <command>gdmlogin</command>. Вона налаштовуються у параметрах <filename>User</filename> та <filename>Group</filename> у файлі конфігурації GDM. Користувач та група мають існувати перед запуском \"make install\". Зазвичай користувач та група GDM називається \"gdm\". " - -#: ../C/gdm.xml:796(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:803(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 <filename><var>/lib/gdm</filename>. 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 " слід зауважити, що користувач та група GDM мають деякі привілеї, які іноді можуть становити загрозу безпеці. По-перше, вони мають доступ до каталогу авторизації X-сервера. Також GDM повинен мати право на читання та запис ключів Xauth у <filename><var>/lib/gdm</filename>. Власником цього каталогу має бути root:gdm, а права доступу 1770. Ці права призначаються каталогу при виконанні \"make install\". Служба GDM буде встановлювати цьому каталогу правильні права, якщо вони відрізняються. " - -#: ../C/gdm.xml:815(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 <filename>nobody</filename>. 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:828(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:839(title) -msgid "X Server Authentication Scheme" -msgstr "Схема аутентифікації X-серверів" - -#: ../C/gdm.xml:841(para) -msgid "The X server authorization directory (the <filename>ServAuthDir</filename>) 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 <filename>root.gdm</filename> 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 "Каталог авторизації сервера (<filename>ServAuthDir</filename>) використовується для зберігання окрім файлів авторизації X сервера, також для випадкових внутрішніх даних, але схема назв насправді є пережитком минулого. Сервер GDM примусово призначає власником цього каталогу <filename>root.gdm</filename> з правами 1770. Таким чином, лише адміністратор(root) та група GDM має доступ на запис до цього каталогу, але група GDM не може видалити з цього каталогу файли, власником яких є root, такі як файли авторизації X сервера." - -#: ../C/gdm.xml:853(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 "Типово GDM не довіряє каталогу авторизації сервера та при створенні файлів поводиться з ним таким самим чином, як з тимчасовим каталогом. Таким чином, якщо хтось зламає GDM, він не зможе використати атаки типу атак монтування шляхом створення посилань у каталозі. Подібним чином каталог реєстрації X сервера також обробляється безпечно, але власником цього каталогу має бути адміністратор (root), також лише він повинен мати можливість запису." - -#: ../C/gdm.xml:862(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 "GDM підтримує лише систему автентифікації MIT-MAGIC-COOKIE-1. Зазвичай від інших схем користі не набагато більше, тому до сих пір не було вжито зусиль для їх реалізації. При використанні XDMCP слід бути особливо обережним, тому що cookie передаються по мережі у незмінному вигляді. Якщо можливе прослуховування лінії зв'язку, тоді нападник може просто отримати ваш пароль під час реєстрації, незалежно від схеми автентифікації. Якщо прослуховування можливе але небажане, тоді використовуйте ssh для тунелювання X з'єднань, замість використання XDMCP. Ви можете розглядати XDMCP як графічний telnet, який має ті ж самі властивості безпеки." - -#: ../C/gdm.xml:875(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 <filename>/dev/audio</filename> or <filename>/dev/mem</filename> 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 <filename>UserAuthDir</filename> configuration key). So be careful about where you use remote X display." -msgstr "З одного боку, генератор випадкових чисел GDM дуже слабкий, та GDM виконує надзвичайні заходи для отримання справді випадкових 128-бітних чисел, при можливості використовує апаратний генератор випадкових чисел, додає поточний час (у мікросекундах), 20-байтний масив псевдовипадкових чисел, ідентифікаторів процесів, плюс іншу випадкову інформацію (можливо використовуючи <filename>/dev/audio</filename> або <filename>/dev/mem</filename>, якщо апаратний генератор відсутній) для створення великого буферу, а потім бере MD5 хеш-суму від нього. Зрозуміло, вся ця робота не має сенсу, якщо ви передаєте отриманий таким чином cookie через відкриту мережі або зберігаєте його у каталозі на томі NFS (дивіться конфігураційний параметр <filename>UserAuthDir</filename>). Тому будьте обережні з використанням віддалених X-дисплеїв." - -#: ../C/gdm.xml:892(title) -msgid "Firewall Security" -msgstr "" - -#: ../C/gdm.xml:894(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 "Хоча GDM намагається ввести в оману потенційних нападників, рекомендується блокувати XDMCP (UDP порт 177) на вашому брандмауері, якщо він вам не потрібен. GDM протидіє DoS атакам (атаки типу відмови у обслуговуванні), але X протоколу властиві успадковані вади безпеки, тому його слід використовувати у контрольованому оточенні. Також кожне віддалене з'єднання споживає багато ресурсів, тому набагато простіше викликати відмову обслуговування XDMCP сервера, ніж, скажімо, у веб-сервера." - -#: ../C/gdm.xml:904(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 "Також буде розумно блокувати на брандмауері всі порти X сервера (TCP порт 6000 + номер дисплею). Зауважте, що різні частини GDM використовують дисплеї з номером 20 та більше (наприклад, при запуску серверів за вимогою)." - -#: ../C/gdm.xml:911(para) -msgid "X is not a very safe protocol for leaving on the net, and XDMCP is even less safe." -msgstr "" - -#: ../C/gdm.xml:918(title) -msgid "GDM Security With NFS" -msgstr "Безпека GDM при використанні з NFS" - -#: ../C/gdm.xml:920(para) -msgid "Note that NFS traffic really goes \"over the wire\" and thus can be snooped. When accessing the user's X authorization file (<filename>~/.Xauthority</filename>), 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 <filename>UserAuthFBDir</filename>, which by default is set to <filename>/tmp</filename>. This behavior can be changed by setting the <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false." -msgstr "Зауважте, трафік NFS насправді прямує <quote>по дроту</quote>, та може прослуховуватись. При доступі до файлів авторизації X-сервера (<filename>~/.Xauthority</filename>), GDM намагатиметься відкрити його від імені адміністратора (root). Якщо це не вдасться, він вважатиме, що має справу із підключеним томом NFS та автоматично буде використовувати змінну <filename>UserAuthFBDir</filename>, яка зазвичай має значення <filename>/tmp</filename>. Цю поведінку можна змінити, встановивши значення false змінній <filename>NeverPlaceCookiesOnNFS</filename> у розділі <filename>[security]</filename>." - -#: ../C/gdm.xml:934(title) -msgid "XDMCP Security" -msgstr "Безпека XDCMP" - -#: ../C/gdm.xml:936(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:942(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 "Головним чином XDMCP використовується для тонких клієнтів у лабораторних умовах. Цім тонким клієнтам для доступу до сервера необхідна лише мережа, та, здається, найкращою політикою безпеки буде тримати їх у окремій мережі, до якої неможливо отримати доступ із зовнішнього світу, а зв'язок є лише з сервером. Єдиною точкою доступу до зовнішнього світу повинен бути сервер." - -#: ../C/gdm.xml:951(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:958(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:966(title) -msgid "XDMCP Access Control" -msgstr "Контроль доступу XDMCP" - -#: ../C/gdm.xml:968(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 "Контроль доступу XDMCP виконується за допомогою обгорток TCP (TCP wrappers). GDM може бути зібрано без обгорток TCP, тому слід перевірити чи ваш GDM це підтримує." - -#: ../C/gdm.xml:974(para) -msgid "You should use the daemon name <command>gdm</command> in the <filename><etc>/hosts.allow</filename> and <filename><etc>/hosts.deny</filename> files. For example to deny computers from <filename>.evil.domain</filename> from logging in, then add" -msgstr "У файлах <filename><etc>/hosts.allow</filename> та <filename><etc>hosts.deny</filename> слід використовувати сервер з назвою <command>gdm</command>. Наприклад, щоб заборонити доступ комп'ютерам з <filename>.evil.domain</filename> додайте " - -#: ../C/gdm.xml:981(screen) -#, no-wrap -msgid "" -"\n" -"gdm: .evil.domain\n" -msgstr "" -"\n" -"gdm: .evil.domain\n" - -#: ../C/gdm.xml:984(para) -msgid "to <filename><etc>/hosts.deny</filename>. You may also need to add" -msgstr "у файл <filename><etc>/hosts.deny</filename>. Також можна додати" - -#: ../C/gdm.xml:988(screen) -#, no-wrap -msgid "" -"\n" -"gdm: .your.domain\n" -msgstr "" -"\n" -"gdm: .your.domain\n" - -#: ../C/gdm.xml:991(para) -msgid "to your <filename><etc>/hosts.allow</filename> if you normally disallow all services from all hosts. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "у файл <filename><etc>/hosts.allow</filename>, якщо ви вимикаєте усі служби з усіх вузлів. Докладнішу інформацію дивіться у man-сторінці <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink>." - -#: ../C/gdm.xml:1001(title) -msgid "Configuration" -msgstr "Налаштовування" - -#: ../C/gdm.xml:1003(para) -msgid "This section will cover the configuration of GDM and the format of the GDM configuration files. You can use the <command>gdmsetup</command> command to configure GDM, but the configuration application does not let you configure every aspect of GDM." -msgstr "У цьому розділі описується налаштовування GDM та формат конфігураційного файлу. Проте, для налаштовування GDM ви можете скористуватись графічною програмою <command>gdmsetup</command>. Але графічна програма не дозволяє налаштувати кожен аспект GDM." - -#: ../C/gdm.xml:1010(para) -msgid "You can either run <command>gdmsetup</command> as root or turn on the GDM configuration feature that allows you to run <command>gdmsetup</command> from the login screen (where it will run as root). If you believe running root owned GUI's is a security risk, then you would want to edit the files by hand." -msgstr "" - -#: ../C/gdm.xml:1018(para) -msgid "If you are a distribution and want to set machine defaults, you should edit the <filename><share>/gdm/defaults.conf</filename> file rather than editing the <filename><etc>/gdm/custom.conf</filename> file, so the distribution changes are preserved as defaults." -msgstr "" - -#: ../C/gdm.xml:1025(para) -msgid "If you want to change configuration by hand, edit the <filename><etc>/gdm/custom.conf</filename> file and make sure the keyname=value pair you want is included in the appropriate section. For example, to change the \"Greeter\" key in the \"daemon\" section, make sure the daemon section of the <filename><etc>/gdm/custom.conf</filename> file has the value like in this example. The modified option does not have to come anywhere in the section. The <command>gdmsetup</command> program manages editing these files for you." -msgstr "" - -#: ../C/gdm.xml:1037(screen) -#, no-wrap -msgid "" -"\n" -"[daemon]\n" -"Greeter=/usr/lib/gdmgreeter\n" -msgstr "" -"\n" -"[daemon]\n" -"Greeter=/usr/lib/gdmgreeter\n" - -#: ../C/gdm.xml:1042(para) -msgid "The configuration files (especially the <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename> files) contains useful comments and examples, so read these for more information about changing your setup." -msgstr "У конфігураційних файлах (зокрема <filename><share>/gdm/defaults.conf</filename> та <filename><etc>/gdm/custom.conf</filename>), міститься багато корисних коментарів, тож читайте їх, коли будете змінювати параметри." - -#: ../C/gdm.xml:1050(para) -msgid "Some keys in the configuration file as shipped are commented out while others are set. This is done so that defaults can be easily changed in the future for some keys. GDM considers lines that start with the \"#\" character a comment, and these lines will be ignored by GDM." -msgstr "Деякі змінні у початковому конфігураційному файлі закоментовані, інші - ні. Це зроблено через те, що типові значення деяких змінних можуть змінитись у майбутньому. GDM вважає коментарями рядки, що починаються зі знаку \"#\", та ігнорує їх." - -#: ../C/gdm.xml:1058(para) -msgid "The <filename><share>/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename><etc>/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename><etc>/gdm/custom.conf</filename> file override the values in the main <filename><share>/gdm/defaults.conf</filename> file. Running the <command>gdmsetup</command> command will cause the <filename><etc>/gdm/custom.conf</filename> to be modified with the user's configuration choices and will cause any running GDM GUI programs to automatically update. Previous to version 2.13.0.4 GDM only supported the <filename><etc>/gdm/gdm.conf</filename> file, so if using an older version of GDM just edit that file directly." -msgstr "" - -#: ../C/gdm.xml:1074(para) -msgid "The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may also be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used." -msgstr "" - -#: ../C/gdm.xml:1083(para) -msgid "<filename><share>/gdm/factory-defaults.conf</filename> is the configuration file as shipped with the daemon. This can be useful for to see if the <filename><share>/gdm/defaults.conf</filename> file has been changed." -msgstr "<filename><share>/gdm/factory-defaults.conf</filename> - конфігураційний файл, що постачається із службою. Він може знадобитись щоб побачити зміни у файлі <filename><share>/gdm/defaults.conf</filename> ." - -#: ../C/gdm.xml:1090(para) -msgid "The other GDM configuration files are located, by default, in the <filename><etc>/gdm/</filename> folder or its subdirectories. However, the location of all configuration files are defined in the GDM configuration files, so the sysadmin may choose to locate these files in any location." -msgstr "Інші конфігураційні файли GDM типово розташовані у каталозі <filename><etc>/gdm/</filename> та його підкаталогах. Проте, розташування усіх конфігураційних файлів можна вказати у конфігураційному файлі GDM, тож системний адміністратор може розташувати ці файли будь-де." - -#: ../C/gdm.xml:1098(para) -msgid "This is a listing of the config directory contents:" -msgstr "Перелік вмісту конфігураційного каталогу:" - -#: ../C/gdm.xml:1102(screen) -#, no-wrap -msgid "" -"\n" -"locale.alias\n" -"Xsession\n" -"XKeepsCrashing\n" -"modules/\n" -"Init/\n" -"PostLogin/\n" -"PreSession/\n" -"PostSession/\n" -msgstr "" - -#: ../C/gdm.xml:1113(para) -msgid "<filename>locale.alias</filename> is a file which looks much like the system locale alias but in fact it is not the same. These are the languages that are available on your system. All the languages are still tested to see if they actually exist before presenting them to the user." -msgstr "<filename>locale.alias</filename> - файл, який схожий на системний файл псевдонімів локалізацій, але насправді вони відрізняються. У ньому перелічені доступні у вашій системі мови. Підтримка кожної мови перевіряється, перш ніж показати її користувачу у списку." - -#: ../C/gdm.xml:1121(para) -msgid "<filename>Xsession</filename> is a script which sets up a user session and then executes the users choice of session. Note that the session script is typically started via the <filename>desktop</filename> file associated with the session the user has picked. Some sessions may start the user's session via a different mechanism than the <filename>Xsession</filename> script, so please check the appropriate <filename>desktop</filename> before assuming a session startup issue is being caused by this file." -msgstr "" - -#: ../C/gdm.xml:1132(para) -msgid "<filename>XKeepsCrashing</filename> 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 "<filename>XKeepsCrashing</filename> - сценарій, який запускається коли X-сервер аварійно завершується декілька разів. Типовий сценарій працює у більшості дистрибутивів Linux. Він може запустити програму налаштовування X-Window, за умови, що особа за консоллю знає пароль адміністратора (root)." - -#: ../C/gdm.xml:1140(para) -msgid "Accessibility modules are configured in the <filename>modules/</filename> 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 <filename>factory</filename> in their name, and those files are not read, they are just there for you so you can always revert to default config." -msgstr "Модулі спеціальних можливостей знаходяться у каталозі <filename>modules/</filename>, їх розглянемо окремо. Читайте самі файли, у них міститься відповідна документація. Типова конфігурація знаходиться, що у своїй назві містять <filename>factory</filename>. Ці файли не читаються, вони існують лише для того, щоб ви завжди мали могли повернути типову конфігурацію." - -#: ../C/gdm.xml:1149(para) -msgid "Files describing available GDM session follow the freedesktop.org desktop file specification and are <filename>.desktop</filename>-style files are installed to <filename><etc>/X11/sessions/</filename>. This directory is also read by the KDE desktop manager (KDM) for common configuration. Next the directory <filename><share>/gdm/BuiltInSessions/</filename> is read for GDM specific built-in sessions (KDM hardcodes these at time of this writing). Lastly the default setup will also read <filename><share>/xsessions/</filename> (which should be <filename><share>/xsessions/</filename> if you really wish to cooperate with KDM) where desktop packages can install their session files. The directories under the <filename><etc></filename> 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 <filename>SessionDesktopDir</filename> configuration key for changing the paths. It used to be that GDM stored its built in sessions in <filename><etc>/dm/Sessions/</filename> but this is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the <filename><etc>/dm/Sessions/</filename> was being read." -msgstr "Наявні сеанси відповідають специфікації freedesktop.org та визначається <filename>.desktop</filename>-файлами у каталозі <filename><etc>/X11/sessions/</filename>. З них також отримує загальну інформацію про конфігурацію і менеджер KDM. Далі читається каталог <filename><share>/gdm/BuiltInSessions/</filename>, у ньому шукаються специфічні для GDM вбудовані сеанси (у KDM це жорстко закодовано на момент написання). Зрештою читається каталог <filename><share>/xsessions/</filename> (який повинен бути <filename>/usr/share/xsessions/</filename>, якщо ви бажаєте сумісності з KDM), де можуть встановлюватись власні файли сеансів з пакетів графічного середовища. Каталоги у <filename><etc></filename> повинні бути зарезервованими для конфігурації. Цей підхід спрощує керування пакетами системи для встановлення менеджерів вікон без необхідності редагування файлів системним адміністратором. Щоб змінити шлях дивіться параметр конфігурації <filename>SessionDesktopDir</filename>. Раніше GDM зберігав свої вбудовані сенси у <filename><etc>/dm/Sessions/</filename>, але це не рекомендовано починаючи з версії 2.5.90.0. Зауважте, до версії 2.4.4.2 читався лише каталог <filename><etc>/dm/Sessions/</filename>." - -#: ../C/gdm.xml:1172(para) -msgid "A session can be disabled (if it was installed in <filename><share>/xsessions/</filename>) by adding an identically named <filename>.desktop</filename> to one of the directories earlier in the path (likely <filename><etc>/X11/sessions</filename>) and using <filename>Hidden=true</filename> in that file." -msgstr "Сеанси можна вимкнути (якщо вони встановлені у <filename><share>/xsessions/</filename>), якщо додати ідентичні за назвою <filename>.desktop</filename>-файли до одного раніше згаданих каталогів, (наприклад <filename><etc>/X11/sessions</filename>) та вказати <filename>Hidden=true</filename> у цьому файлі." - -#: ../C/gdm.xml:1181(title) -msgid "The Script Directories" -msgstr "Каталоги сценаріїв" - -#: ../C/gdm.xml:1183(para) -msgid "In this section we will explain the <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> and <filename>PostSession</filename> directories as they are very similar." -msgstr "У цьому розділі описуються каталоги <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> та <filename>PostSession</filename>, котрі дуже подібні один до одного." - -#: ../C/gdm.xml:1189(para) -msgid "When the X server has been successfully started, GDM will try to run the script called <filename>Init/<displayname></filename>. I.e. <filename>Init/:0</filename> for the first local display. If this file is not found, GDM will attempt to to run <filename>Init/<hostname></filename>. I.e. <filename>Init/somehost</filename>. If this still is not found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins or <filename>Init/Flexi</filename> for all on demand flexible displays. If none of the above were found, GDM will run <filename>Init/Default</filename>. The script will be run as root and GDM blocks until it terminates. Use the <filename>Init/*</filename> script for applications that are supposed to run alongside with the GDM login window. xconsole for instance. Commands to set the background etc. goes in this file too." -msgstr "Після успішного запуску X-сервера, GDM намагається запусти сценарій з назвою <filename>Init/<displayname></filename>. Тобто <filename>Init/:0</filename> для першого локального дисплею. Якщо файл не існує, GDM намагається запустити сценарій <filename>Init/<hostname></filename>. Тобто <filename>Init/somehost</filename>. Якщо він також не існує, GDM намагається виконати <filename>Init/XDMCP</filename> для всіх входів типу XDMCP, або <filename>Init/Flexi</filename> для всіх гнучких серверів за вимогою. Якщо жоден з них не існує, GDM запускає <filename>Init/Default</filename>. Сценарій запускається з правами адміністратора (root) та GDM блокується до його завершення. Використовуйте сценарії <filename>Init/*</filename> для програм, які допускають одночасний запуск з вікном входу GDM. Наприклад xconsole. Також у цьому файлі можуть використовуватись команди встановлення тла, тощо." - -#: ../C/gdm.xml:1207(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 <filename>KillInitClients</filename> configuration option." -msgstr "Системний адміністратор може вказати, чи потрібно завершувати запущені у сценарії Init програми перед початком вибраного користувачем сеансу. Це контролюється параметром <filename>KillInitClients</filename>." - -#: ../C/gdm.xml:1214(para) -msgid "When the user has been successfully authenticated GDM tries the scripts in the <filename>PostLogin</filename> directory in the same manner as for the <filename>Init</filename> 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 <filename>pam_mount</filename> module if you can for this). You have the <filename>$USER</filename> and <filename>$DISPLAY</filename> 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 "Після успішної аутентифікації користувача, GDM намагається виконати сценарій з каталогу <filename>PostLogin</filename> таким самим чином як і у каталозі <filename>Init</filename>. Це робиться до будь-якого встановлення сеансу, тому у цьому сценарії, при необхідності, можна визначити домашній каталог (але, якщо можливо, бажано використовувати для цього модуль <filename>pam_mount</filename>). У цьому сценарії доступні змінні <filename>$USER</filename> та <filename>$DISPLAY</filename>, та він також запускається з правами адміністратора (root). Сценарій повинен повернути 0 при успішному виконанні, у іншому випадку користувачу не буде дозволено увійти. Проте при запуску аварійного сеансу це не так." - -#: ../C/gdm.xml:1228(para) -msgid "After the user session has been setup from the GDM side of things, GDM will run the scripts in the <filename>PreSession</filename> directory, again in the same manner as the <filename>Init</filename> directory. Use this script for local session management or accounting stuff. The <filename>$USER</filename> environment variable contains the login of the authenticated user and <filename>$DISPLAY</filename> 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 <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." -msgstr "Коли GDM налаштує сеанс користувача, він запускає сценарій з каталогу <filename>PreSession</filename>, знову ж таки тим самим чином, як і у каталозі <filename>Init</filename>. Цей сценарій можна використовувати для встановлення локального сеансу або налаштовування обліку. Змінна оточення <filename>$USER</filename> містить ім'я користувача, що пройшов автентифікацію, значення змінної <filename>$DISPLAY</filename> дорівнює значенню поточного дисплею. При успішному виконанні сценарій повинен повернути 0. Будь-яке інше значення призведе до завершення поточного процесу реєстрації у системі. Проте, при запуску аварійного сеансу це не так. Тут встановлено змінну оточення <filename>$X_SERVERS</filename> у значення підробленого згенерованого фай'лу X-сервера для використання з програмою обліку sessreg." - -#: ../C/gdm.xml:1243(para) -msgid "After this the base <filename>Xsession</filename> 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 <filename>Exec=</filename> line in the <filename>.desktop</filename> files in the path specified by <filename>SessionDesktopDir</filename>. Usually this path is <filename><etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/xsessions/</filename>. The first found file is used. The user either picks from these sessions or GDM will look inside the file <filename>~/.dmrc</filename> for the stored preference." -msgstr "Після цього запускається основний сценарій <filename>Xsession</filename>, якому у першому аргументі передається вибраний виконуваний файл сеансу. Він запускається з правами користувача. Наявні виконувані файли сеансів беруться з рядка <filename>Exec=</filename> у <filename>.desktop</filename> файлах з каталогів вказаних у <filename>SessionDesktopDir</filename>. Зазвичай цей шлях такий: <filename><etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/xsessions/</filename>. Використовується перший знайдений файл. Вподобання користувача або вибираються або з цих сеансів, або GDM шукає їх у файлі <filename>~/.dmrc</filename>." - -#: ../C/gdm.xml:1256(para) -msgid "This script should really load the users 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 <filename>$GDM_LANG</filename> variable to the selected language. You can use this to reset the language environmental variables after you run the users profile. If the user elected to use the system language, then <filename>$GDM_LANG</filename> is not set." -msgstr "Цей сценарій повинен зчитати профіль користувача та виконати всю роботу, необхідну для встановлення сеансу. Через те, що у деяких системах скидається вибране користувачем у GDM значення мови, GDM також встановлює змінну оточення <filename>$GDM_LANG</filename> у вибране значення мови. Можна її використовувати для встановлення змінних оточення після запуску профілю, які відповідають за вибір мови. Якщо користувач вибрав системну мову, тоді <filename>$GDM_LANG</filename> не встановлюється." - -#: ../C/gdm.xml:1266(para) -msgid "When the user terminates his session, the <filename>PostSession</filename> script will be run. Again operation is similar to <filename>Init</filename>, <filename>PostLogin</filename> and <filename>PreSession</filename>. Again the script will be run with root privileges, the slave daemon will block and the <filename>$USER</filename> environment variable will contain the name of the user who just logged out and <filename>$DISPLAY</filename> will be set to the display the user used, however note that the X server for this display may already be dead and so you shouldn't try to access it. Also <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." -msgstr "Коли користувач завершує сеанс, знову виконується сценарій з <filename>PostSession</filename>. Всі дії такі самі як і у <filename>Init</filename>, <filename>PostLogin</filename> та <filename>PreSession</filename>. Знову ж таки сценарій запускається з правами адміністратора (root), допоміжний процес сервера блокується. Змінна оточення <filename>$USER</filename> містить ім'я користувача, який завершує сеанс, змінна оточення <filename>$DISPLAY</filename> буде встановлена у значення дисплею, але зверніть увагу, що X-сервер для цього дисплею може бути вже завершений, тому не слід намагатись отримати до нього доступ. Тут встановлена змінна оточення <filename>$X_SERVERS</filename>, вона має значення фальшивого згенерованого файлу x-сервера для використання з програмою обліку sessreg." - -#: ../C/gdm.xml:1281(para) -msgid "Note that the <filename>PostSession</filename> script will be run even when the display fails to respond due to an I/O error or similar. Thus, there is no guarantee that X applications will work during script execution." -msgstr "Зверніть увагу, сценарій <filename>PostSession</filename> запускається навіть якщо дисплей завершився аварійно через помилку вводу/виводу або щось подібне. Тому, не гарантується, що X-програми працюватимуть при його виконанні." - -#: ../C/gdm.xml:1288(para) -msgid "Except for the <filename>Xsession</filename> script all of these scripts will also have the environment variable <filename>$RUNNING_UNDER_GDM</filename> set to <filename>yes</filename>, so that you could perhaps use similar scripts for different display managers. The <filename>Xsession</filename> will always have the <filename>$GDMSESSION</filename> set to the basename of the session that the user chose to run without the <filename>.desktop</filename> extension. In addition <filename>$DESKTOP_SESSION</filename> is also set to the same value and in fact this will also be set by KDM in future versions." -msgstr "З винятком сценарію <filename>Xsession</filename> в усіх цих сценаріях визначена змінна оточення <filename>$RUNNING_UNDER_GDM</filename> встановлена у <filename>yes</filename>, тому ви можете використовувати ці сценарії з іншими менеджерами дисплеїв. У сценарії <filename>Xsession</filename> завжди визначена змінна <filename>$GDMSESSION</filename>, її значення - назва файлу сеансу користувача (без частини зі шляхом та без розширення <filename>.desktop</filename>). Додатково також визначено змінну <filename>$DESKTOP_SESSION</filename>. Вона має те ж саме значення, фактично воно буде також встановлюватись у майбутніх версіях менеджеру дисплеїв KDM." - -#: ../C/gdm.xml:1302(para) -msgid "Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> or <filename>PostSession</filename> scripts are necessary and can be left out. The <filename>Xsession</filename> script is however required as well as at least one session <filename>.desktop</filename> file." -msgstr "Жоден з <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename> чи <filename>PostSession</filename> сценаріїв не є необхідним, та може бути пропущений. Але вимагається сценарій <filename>Xsession</filename>, та хоча б один файл сеансу <filename>.desktop</filename>." - -#: ../C/gdm.xml:1312(title) -msgid "The Configuration Files - <filename>defaults.conf</filename> and <filename>custom.conf</filename>" -msgstr "Конфігураційний файл - <filename>defaults.conf</filename> та <filename>custom.conf</filename>" - -#: ../C/gdm.xml:1315(para) -msgid "GDM uses two configuration files: <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename>. The <filename><share>/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename><etc>/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename><etc>/gdm/custom.conf</filename> file override the values in the <filename><share>/gdm/defaults.conf</filename> file. If a configuration option is not defined in either file, GDM will default to the value described in the comments in the <filename><share>/gdm/defaults.conf</filename> file." -msgstr "" - -#: ../C/gdm.xml:1331(para) -msgid "Running the <command>gdmsetup</command> command will cause the <filename><etc>/gdm/custom.conf</filename> to be modified with the user's configuration choices." -msgstr "" - -#: ../C/gdm.xml:1337(para) -msgid "Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</filename> existed. If upgrading to the new version of GDM, install will check to see if your <filename><etc>/gdm/gdm.conf</filename> file is different than your <filename><etc>/gdm/factory-gdm.conf</filename> file. If so, your <filename><etc>/gdm/gdm.conf</filename> file will be automatically copied to <filename><etc>/gdm/custom.conf</filename> to preserve any configuration changes." -msgstr "" - -#: ../C/gdm.xml:1349(para) -msgid "The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may instead be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used." -msgstr "" - -#: ../C/gdm.xml:1358(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 <filename><share>/gdm/defaults.conf</filename> file for additional information about each configuration setting." -msgstr "Обидва конфігураційні файли поділяється на розділи, кожен з яких містить змінні, які визначають поведінку окремих частин пакету GDM. Додаткову інформацію про конфігураційні параметри можна отримати з коментарів у файлі <filename><share>/gdm/defaults.conf</filename>." - -#: ../C/gdm.xml:1366(para) -msgid "The <filename><share>/gdm/defaults.conf</filename> and <filename><etc>/gdm/custom.conf</filename> files follow the standard <filename>.ini</filename> 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 "<filename><share>/gdm/defaults.conf</filename> та <filename><etc>/gdm/custom.conf</filename> має синтаксис конфігураційних файлів у стилі <filename>.ini</filename>. Ключові слова у прямокутних дужках визначають розділи, рядки перед знаком <quote>дорівнює</quote> (=) є змінними, а дані після знаку тотожності є їх значеннями. Порожні рядки або рядки, що починаються зі знаку (#) ігноруються. Графічна програма налаштовування намагається зберігати як коментарі (рядки зі знаком діез), так і загальну структуру файлу, тому ви можете змінювати файл як за допомогою графічної програми, так і за допомогою текстового редактора." - -#: ../C/gdm.xml:1379(title) -msgid "Daemon Configuration" -msgstr "Конфігурація сервера" - -#: ../C/gdm.xml:1382(title) -msgid "[daemon]" -msgstr "[daemon]" - -#: ../C/gdm.xml:1385(term) -msgid "AddGtkModules" -msgstr "AddGtkModules" - -#: ../C/gdm.xml:1387(synopsis) -#, no-wrap -msgid "AddGtkModules=false" -msgstr "AddGtkModules=false" - -#: ../C/gdm.xml:1388(para) -msgid "If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</command> 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 "Якщо має значення true, це дозволяє запускати <command>gdmgreeter</command> чи <command>gdmlogin</command> з додатковими модулями Gtk+. Це корисно якщо необхідні додаткові властивості, наприклад підтримку спеціальних можливостей. Зверніть увагу, для мінімізації загроз безпеці повинні використовуватись лише \"довірені\" модулі." - -#: ../C/gdm.xml:1395(para) -msgid "Usually this is used for accessibility modules. The modules which are loaded are specified with the <filename>GtkModulesList</filename> key." -msgstr "Зазвичай використовується для підтримки спеціальних можливостей. Модулі, які завантажуються, визначаються параметром <filename>GtkModulesList</filename>." - -#: ../C/gdm.xml:1404(term) -msgid "AlwaysRestartServer" -msgstr "AlwaysRestartServer" - -#: ../C/gdm.xml:1406(synopsis) -#, no-wrap -msgid "AlwaysRestartServer=false" -msgstr "AlwaysRestartServer=false" - -#: ../C/gdm.xml:1407(para) -msgid "If true, then gdm never tries to reuse existing X servers by reinitializing them. It will just kill the existing X server and start over. Normally, just reinitializing is a nicer way to go but if the X server memory usage keeps growing this may be a safer option. On Solaris, this value is always true, and this configuration setting is ignored." -msgstr "Якщо має значення true, то gdm ніколи не намагатиметься повторно використати існуючі X-сервери шляхом їх повторної ініціалізації. Наявні серверні процеси будуть знищуватись та будуть запускатись нові. Зазвичай, повторна ініціалізація більш гарний шлях, але якщо зростає обсяг пам'яті, яку використовує X-сервер, то цей шлях більш безпечний. На Solaris значення завжди true, та цей параметр ігнорується.'" - -#: ../C/gdm.xml:1419(term) -msgid "AutomaticLoginEnable" -msgstr "AutomaticLoginEnable" - -#: ../C/gdm.xml:1421(synopsis) -#, no-wrap -msgid "AutomaticLoginEnable=false" -msgstr "AutomaticLoginEnable=false" - -#: ../C/gdm.xml:1422(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 <filename>TimedLogin</filename>." -msgstr "Чи починати автоматично сеанс при першому завантаженні від імені користувача, що вказаний у змінній AutomaticLogin. Пароль не буде запитано. Ця функція використовується на робочих станціях з єдиним користувачем, коли безпека локальної консолі не має особливого значення. Також може використовуватись для публічних терміналів, хоча дивіться параметр <filename>TimedLogin</filename>." - -#: ../C/gdm.xml:1433(term) -msgid "AutomaticLogin" -msgstr "AutomaticLogin" - -#: ../C/gdm.xml:1435(synopsis) -#, no-wrap -msgid "AutomaticLogin=" -msgstr "AutomaticLogin=" - -#: ../C/gdm.xml:1436(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 "Після першого запуску починається сеанс цього користувача. Для цього необхідно щоб ім'я було ім'ям дійсного користувача, та щоб параметр AutomaticLoginEnable мав значення true. Проте, автоматичний вхід адміністратора (\"root\") недопустимий, та gdm не буде автоматично починати сеанс адміністратора, навіть якщо ви так вкажете." - -#: ../C/gdm.xml:1444(para) -msgid "The following control chars are recognized within the specified name:" -msgstr "У значенні цього параметра допустимі такі макроси:" - -#: ../C/gdm.xml:1449(para) -#: ../C/gdm.xml:3442(para) -msgid "%%— the `%' character" -msgstr "%%— the `%' character" - -#: ../C/gdm.xml:1453(para) -msgid "%d — display's name" -msgstr "%d — назва дсплею" - -#: ../C/gdm.xml:1457(para) -msgid "%h — display's hostname" -msgstr "%h — назва вузла дисплею" - -#: ../C/gdm.xml:1461(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:1474(term) -msgid "BaseXsession" -msgstr "BaseXsession" - -#: ../C/gdm.xml:1476(synopsis) -#, no-wrap -msgid "BaseXsession=<etc>/gdm/Xsession" -msgstr "BaseXsession=<etc>/gdm/Xsession" - -#: ../C/gdm.xml:1477(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 <filename>Exec=</filename> from the <filename>.desktop</filename> file of the session." -msgstr "Це - основний файл X-сеансу. При реєстрації користувача, у першому аргументі сценарію передається вибраний виконуваний файл сеансу. Вибраний сеанс буде значенням з рядка <filename>Exec=</filename> у <filename>.desktop</filename> файлі сеансу." - -#: ../C/gdm.xml:1485(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 <filename>GDMSESSION</filename> environmental variable. This will always be set to the basename of <filename>.desktop</filename> (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 <filename>GDM_LANG</filename>, but that is only set when the user picks a non-system default language." -msgstr "Якщо ви бажаєте використовувати один сценарій для усіх менеджерів дисплеїв, та бажаєте, щоб деякі сценарії запускались лише при використанні GDM, тоді слід перевіряти наявність змінної оточення <filename>GDMSESSION</filename>. Її значення завжди дорівнює назві файлу <filename>.desktop</filename> (без розширення), що використовується для поточного сеансу, та встановлюється лише для GDM сеансів. Раніше деякі сценарії перевіряли змінну <filename>GDM_LANG</filename>, але вона встановлюється лише якщо користувач обирає несистемну мову." - -#: ../C/gdm.xml:1498(para) -msgid "This script should take care of doing the \"login\" for the user and so it should source the <filename><etc>/profile</filename> and friends. The standard script shipped with GDM sources the files in this order: <filename><etc>/profile</filename> then <filename>~/.profile</filename> then <filename><etc>/xprofile</filename> and finally <filename>~/.xprofile</filename>. Note that different distributions may change this however. Sometimes users personal setup will be in <filename>~/.bash_profile</filename>, however broken that is." -msgstr "Цей сценарій має подбати про виконання \"login\" для користувача та має включати файл <filename><etc>/profile</filename> та інші подібні файли. Стандартний сценарій, що постачається з GDM включає файли у такому порядку: <filename><etc>/profile</filename>, потім <filename>~/.profile</filename> потім <filename><etc>/xprofile</filename> та зрештою <filename>~/.xprofile</filename>. Зауважте, у різних дистрибутивах порядок може відрізнятись. Іноді особисті параметри користувача встановлюються у <filename>~/.bash_profile</filename>, але це неправильно." - -#: ../C/gdm.xml:1515(term) -msgid "Chooser" -msgstr "Chooser" - -#: ../C/gdm.xml:1517(synopsis) -#, no-wrap -msgid "Chooser=<bin>/gdmchooser" -msgstr "Chooser=<bin>/gdmchooser" - -#: ../C/gdm.xml:1518(para) -msgid "Full path and name of the chooser executable followed by optional arguments." -msgstr "Повний шлях та назва програми вибору, за якими можуть йти аргументи." - -#: ../C/gdm.xml:1526(term) -msgid "Configurator" -msgstr "Configurator" - -#: ../C/gdm.xml:1528(synopsis) -#, no-wrap -msgid "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" -msgstr "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" - -#: ../C/gdm.xml:1529(para) -msgid "The pathname to the configurator binary. If the greeter <filename>ConfigAvailable</filename> 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 "Шлях до програми налаштовування. Якщо параметр програми привітання <filename>ConfigAvailable</filename> встановлено у true, тоді ця програма запускається коли хтось обирає Налаштовування з меню Дії. Звичайно GDM спершу запитає пароль користувача root. Ця функція недоступна на віддалених дисплеях." - -#: ../C/gdm.xml:1541(term) -msgid "ConsoleCannotHandle" -msgstr "ConsoleCannotHandle" - -#: ../C/gdm.xml:1543(synopsis) -#, no-wrap -msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" -msgstr "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" - -#: ../C/gdm.xml:1544(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 "Ці мови не можуть оброблятись консоллю через проблеми з шрифтами. Тут мається на увазі текстова консоль, а не X Window. Використовується лише коли є повідомлення про помилки та неможливо запустити систему X." - -#: ../C/gdm.xml:1554(term) -msgid "ConsoleNotify" -msgstr "ConsoleNotify" - -#: ../C/gdm.xml:1556(synopsis) -#, no-wrap -msgid "ConsoleNotify=true" -msgstr "ConsoleNotify=true" - -#: ../C/gdm.xml:1557(para) -msgid "If false, gdm will not display a message dialog on the console when an error happens." -msgstr "Якщо встановлено значення false, то gdm не відображатиме повідомлення про помилки на консолі." - -#: ../C/gdm.xml:1565(term) -msgid "DefaultPath" -msgstr "DefaultPath" - -#: ../C/gdm.xml:1567(synopsis) -#, no-wrap -msgid "DefaultPath=defaultpath (value set by configure)" -msgstr "DefaultPath=типовийшлях (значення визначається при configure)" - -#: ../C/gdm.xml:1568(para) -msgid "Specifies the path which will be set in the user's session. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains \"ROOT=<pathname>\". If the <filename>/etc/default/login</filename> file exists, but contains no value for ROOT, the value as defined in the GDM configuration will be be used." -msgstr "" - -#: ../C/gdm.xml:1581(term) -msgid "DefaultSession" -msgstr "DefaultSession" - -#: ../C/gdm.xml:1583(synopsis) -#, no-wrap -msgid "DefaultSession=gnome.desktop" -msgstr "DefaultSession=gnome.desktop" - -#: ../C/gdm.xml:1584(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 <filename>ShowLastSession</filename> key." -msgstr "Сеанс, що використовується коли користувач у списку сеансів вибрав 'Останній' і не має збережених уподобань. Зауважте, сеанс 'Останній' не відображається, дивіться ключ <filename>ShowLastSession</filename>." - -#: ../C/gdm.xml:1595(term) -msgid "DisplayInitDir" -msgstr "DisplayInitDir" - -#: ../C/gdm.xml:1597(synopsis) -#, no-wrap -msgid "DisplayInitDir=<etc>/gdm/Init" -msgstr "DisplayInitDir=<etc>/gdm/Init" - -#: ../C/gdm.xml:1598(para) -msgid "Directory containing the display init scripts. See the ``The Script Directories'' section for more info." -msgstr "Каталог, що містить сценарій ініціалізації дисплею. Докладніше про це дивіться у розділі ``Каталоги сценаріїв''." - -#: ../C/gdm.xml:1606(term) -msgid "DisplayLastLogin" -msgstr "DisplayLastLogin" - -#: ../C/gdm.xml:1608(synopsis) -#, no-wrap -msgid "DisplayLastLogin=true" -msgstr "DisplayLastLogin=true" - -#: ../C/gdm.xml:1609(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 "Якщо має значення true, то перед запитом паролю користувачу виводиться інформація про останній сеанс. " - -#: ../C/gdm.xml:1618(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 <filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> for more info." -msgstr "Це для відповідності GDM до CSC-STD-002-85, хоча наразі це суто теоретично. Хтось має прочитати цю специфікацію та переконатись що відповідність є (так само як і у інших місцях GDM). Докладніше про це дивіться <filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename>." - -#: ../C/gdm.xml:1630(term) -msgid "DoubleLoginWarning" -msgstr "DoubleLoginWarning" - -#: ../C/gdm.xml:1632(synopsis) -#, no-wrap -msgid "DoubleLoginWarning=true" -msgstr "DoubleLoginWarning=true" - -#: ../C/gdm.xml:1633(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 "Якщо має значення true, GDM буде попереджувати користувача, якщо він вже увійшов у сеанс з іншого віртуального терміналу. На системах, де GDM підтримує перевірку віртуальних терміналів X, GDM дозволить користувачу замість входу у сеанс перемкнутись на попередній віртуальний термінал з сеансом." - -#: ../C/gdm.xml:1643(term) -msgid "DynamicXServers" -msgstr "DynamicXServers" - -#: ../C/gdm.xml:1645(synopsis) -#, no-wrap -msgid "DynamicXServers=false" -msgstr "DynamicXServers=false" - -#: ../C/gdm.xml:1646(para) -msgid "If true, the GDM daemon will honor requests to manage displays via the <filename>/tmp/.gdm_socket</filename> socket connection. Displays can be created, started, and deleted with the appropriate commands. The <filename>gdmdynamic</filename> command is a convenient method to send these messages." -msgstr "Якщо має значення true, служба GDM буде обробляти запити керування дисплеями через сокет <filename>/tmp/.gdm_socket</filename>. Відповідними командами можна створювати, запускати та видаляти дисплеї. Команда <filename>gdmdynamic</filename> - зручний метод надсилання таких повідомлень." - -#: ../C/gdm.xml:1658(term) -msgid "FailsafeXServer" -msgstr "FailsafeXServer" - -#: ../C/gdm.xml:1660(synopsis) -#, no-wrap -msgid "FailsafeXServer=" -msgstr "FailsafeXServer=" - -#: ../C/gdm.xml:1661(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 <filename>XKeepsCrashing</filename> script is run." -msgstr "Командний рядок X у разі неможливості запуску звичайного X-сервера. Має бути невеликим сценарієм, що запускає відповідний сервер з низькою роздільною здатністю, який напевно працюватиме. Він випробовується перед запуском сценарію <filename>XKeepsCrashing</filename>." - -#: ../C/gdm.xml:1672(term) -msgid "FirstVT" -msgstr "FirstVT" - -#: ../C/gdm.xml:1674(synopsis) -#, no-wrap -msgid "FirstVT=7" -msgstr "FirstVT=7" - -#: ../C/gdm.xml:1675(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 <filename>VTAllocation</filename>." -msgstr "На системах де GDM підтримує автоматичне призначення віртуальних терміналів (VT), це перший віртуальний термінал, який буде випробуваний. Зазвичай, на віртуальних терміналах з молодшими номерами запускаються текстові консолі. Також дивіться <filename>VTAllocation</filename>." - -#: ../C/gdm.xml:1685(term) -msgid "FlexibleXServers" -msgstr "FlexibleXServers" - -#: ../C/gdm.xml:1687(synopsis) -#, no-wrap -msgid "FlexibleXServers=5" -msgstr "FlexibleXServers=5" - -#: ../C/gdm.xml:1688(para) -msgid "The maximum number of allowed flexible displays. These are displays that can be run using the <filename>/tmp/.gdm_socket</filename> socket connection. This is used for both full flexible displays and for Xnest displays." -msgstr "Максимальна допустима кількість гнучких серверів. Це сервери, які можуть запускатись використовуючи сокет <filename>/tmp/.gdm_socket</filename>. Це використовується як для повноцінних гнучких серверів, так і для серверів Xnest." - -#: ../C/gdm.xml:1699(term) -msgid "FlexiReapDelayMinutes" -msgstr "FlexiReapDelayMinutes" - -#: ../C/gdm.xml:1701(synopsis) -#, no-wrap -msgid "FlexiReapDelayMinutes=5" -msgstr "FlexiReapDelayMinutes=5" - -#: ../C/gdm.xml:1702(para) -msgid "After how many minutes of inactivity at the login screen should a flexi display be reaped. This is only in effect before a user logs in. Also it does not affect the Xnest flexiservers. To turn off this behavior set this value to 0. This was added in version 2.5.90.0." -msgstr "Скільки хвилин неактивності має минути у екрані входу, щоб гнучкий сервер став be reaped. Це матиме ефект лише до входу користувача у сеанс. Також це не впливає на гнучкі сервери Xnest. Для вимикання цієї функції встановіть значення у 0. Функцію додано починаючи з версії 2.5.90.0." - -#: ../C/gdm.xml:1713(term) -msgid "Greeter" -msgstr "Greeter" - -#: ../C/gdm.xml:1715(synopsis) -#, no-wrap -msgid "Greeter=<bin>/gdmlogin" -msgstr "Greeter=<bin>/gdmlogin" - -#: ../C/gdm.xml:1716(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 <filename>RemoteGreeter</filename>" -msgstr "Повний шлях та назва файлу програми привітання, а також необов'язкові аргументи. Ця програма привітання використовується для всіх серверів за винятком віддалених серверів XDMCP. Також дивіться <filename>RemoteGreeter</filename>" - -#: ../C/gdm.xml:1726(term) -msgid "Group" -msgstr "Group" - -#: ../C/gdm.xml:1728(synopsis) -#, no-wrap -msgid "Group=gdm" -msgstr "Group=gdm" - -#: ../C/gdm.xml:1729(para) -msgid "The group name under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogs are run. Also see <filename>User</filename>. 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 <filename>ServAuthDir</filename> is owned by this group. The ownership and permissions of <filename>ServAuthDir</filename> should be <filename>root.gdm</filename> and 1770." -msgstr "Назва групи, від імені якої запускаються <command>gdmlogin</command>, <command>gdmgreeter</command> <command>gdmchooser</command> та внутрішні аварійні діалогові вікна GTK+. Також дивіться параметр <filename>User</filename>. Цей користувач матиме доступ до усіх файлів авторизації X-сервера, та, можливо, до інших внутрішніх даних GDM, тому він не повинен бути таким користувачем як nobody, а цілком окремим користувачем. До цієї групи належить <filename>ServAuthDir</filename>. Власник та права доступу <filename>ServAuthDir</filename> мають бути <filename>root.gdm</filename> та 1770." - -#: ../C/gdm.xml:1746(term) -msgid "GtkModulesList" -msgstr "GtkModulesList" - -#: ../C/gdm.xml:1748(synopsis) -#, no-wrap -msgid "GtkModulesList=module-1:module-2:..." -msgstr "GtkModulesList=module-1:module-2:..." - -#: ../C/gdm.xml:1749(para) -msgid "A colon separated list of Gtk+ modules that <command>gdmgreeter</command> or <command>gdmlogin</command> will be invoked with if <filename>AddGtkModules</filename> is true. The format is the same as the standard Gtk+ module interface." -msgstr "Список модулів Gtk+, що розділені комою, які <command>gdmgreeter</command> чи <command>gdmlogin</command> будуть викликати якщо параметр <filename>AddGtkModules</filename> має значення true. Формат такий самий як у стандартному інтерфейсі модулів Gtk+." - -#: ../C/gdm.xml:1760(term) -msgid "HaltCommand" -msgstr "HaltCommand" - -#: ../C/gdm.xml:1762(synopsis) -#, no-wrap -msgid "HaltCommand=<sbin>/shutdown -h now" -msgstr "HaltCommand=<sbin>/shutdown -h now" - -#: ../C/gdm.xml:1763(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:1776(term) -msgid "KillInitClients" -msgstr "KillInitClients" - -#: ../C/gdm.xml:1778(synopsis) -#, no-wrap -msgid "KillInitClients=true" -msgstr "KillInitClients=true" - -#: ../C/gdm.xml:1779(para) -msgid "Determines whether GDM should kill X clients started by the init scripts when the user logs in." -msgstr "Визначає чи GDM має знищувати (командою kill) X-клієнтів, які запущені у сценаріях ініціалізації при вході користувач у сеанс." - -#: ../C/gdm.xml:1787(term) -msgid "LogDir" -msgstr "LogDir" - -#: ../C/gdm.xml:1789(synopsis) -#, no-wrap -msgid "LogDir=<var>/log/gdm" -msgstr "LogDir=<var>/log/gdm" - -#: ../C/gdm.xml:1790(para) -msgid "Directory containing the log files for the individual displays. By default this is the same as the ServAuthDir." -msgstr "Каталог, що містить файли журналів для окремих дисплеїв. Типово має таке саме значення як і параметр ServAuthDir." - -#: ../C/gdm.xml:1798(term) -msgid "PidFile" -msgstr "PidFile" - -#: ../C/gdm.xml:1800(synopsis) -#, no-wrap -msgid "PidFile=<var>/run/gdm.pid" -msgstr "PidFile=<var>/run/gdm.pid" - -#: ../C/gdm.xml:1801(para) -msgid "Name of the file containing the <filename>gdm</filename> process id." -msgstr "Назва файлу, що містить ідентифікатор процесу <filename>gdm</filename>." - -#: ../C/gdm.xml:1809(term) -msgid "PreFetchProgram" -msgstr "PreFetchProgram" - -#: ../C/gdm.xml:1811(synopsis) -#, no-wrap -msgid "PreFetchProgram=command" -msgstr "PreFetchProgram=command" - -#: ../C/gdm.xml:1812(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:1828(term) -msgid "PostLoginScriptDir" -msgstr "PostLoginScriptDir" - -#: ../C/gdm.xml:1830(synopsis) -#, no-wrap -msgid "PostLoginScriptDir=<etc>/gdm/PostLogin" -msgstr "PostLoginScriptDir=<etc>/gdm/PostLogin" - -#: ../C/gdm.xml:1831(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:1840(term) -msgid "PostSessionScriptDir" -msgstr "PostSessionScriptDir" - -#: ../C/gdm.xml:1842(synopsis) -#, no-wrap -msgid "PostSessionScriptDir=<etc>/gdm/PostSession" -msgstr "PostSessionScriptDir=<etc>/gdm/PostSession" - -#: ../C/gdm.xml:1843(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:1851(term) -msgid "PreSessionScriptDir" -msgstr "PreSessionScriptDir" - -#: ../C/gdm.xml:1853(synopsis) -#, no-wrap -msgid "PreSessionScriptDir=<etc>/gdm/PreSession" -msgstr "PreSessionScriptDir=<etc>/gdm/PreSession" - -#: ../C/gdm.xml:1854(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:1862(term) -msgid "RebootCommand" -msgstr "RebootCommand" - -#: ../C/gdm.xml:1864(synopsis) -#, no-wrap -msgid "RebootCommand=<sbin>/shutdown -r now" -msgstr "RebootCommand=<sbin>/shutdown -r now" - -#: ../C/gdm.xml:1865(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:1877(term) -msgid "RemoteGreeter" -msgstr "RemoteGreeter" - -#: ../C/gdm.xml:1879(synopsis) -#, no-wrap -msgid "RemoteGreeter=<bin>/gdmlogin" -msgstr "RemoteGreeter=<bin>/gdmlogin" - -#: ../C/gdm.xml:1880(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 <filename>Greeter</filename> key." -msgstr "Повний шлях та назва файлу програми привітання та її необов'язкові аргументи. Використовується для усіх віддалених сенсів XDMCP. Тут бажано вказати менш вибагливу до ресурсів програму привітання, якщо основною програмою привітання використовується програма привітання з темами. Також дивіться ключ <filename>Greeter</filename>." - -#: ../C/gdm.xml:1891(term) -msgid "RootPath" -msgstr "RootPath" - -#: ../C/gdm.xml:1893(synopsis) -#, no-wrap -msgid "RootPath=defaultpath (value set by configure)" -msgstr "RootPath=типовийшлях (значення визначається при configure)" - -#: ../C/gdm.xml:1894(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 <filename>/etc/default/login</filename> if it contains \"SUROOT=<pathname>\". If the <filename>/etc/default/login</filename> file exists, but contains no value for SUROOT, the value as defined in the GDM configuration will be used." -msgstr "" - -#: ../C/gdm.xml:1908(term) -msgid "ServAuthDir" -msgstr "ServAuthDir" - -#: ../C/gdm.xml:1910(synopsis) -#, no-wrap -msgid "ServAuthDir=<var>/gdm" -msgstr "ServAuthDir=<var>/gdm" - -#: ../C/gdm.xml:1911(para) -msgid "Directory containing the X authentication files for the individual displays. Should be owned by <filename>root.gdm</filename> with permissions 1770, where <filename>gdm</filename> is the GDM group as defined by the <filename>Group</filename> option. That is should be owned by root, with <filename>gdm</filename> 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 "Каталог містить файли X-аутентифікації для окремих дисплеїв. Має належати <filename>root.gdm</filename> з правами 1770, де <filename>gdm</filename> - група GDM, яка визначена параметром <filename>Group</filename>. Тобто власником має бути root, група <filename>gdm</filename> повинна мати права на запис, для каталогу має бути встановлено sticky-біт, та інші не повинні мати прав доступу до каталогу. Таким чином користувач gdm не зможе видалити у цьому каталозі файли, що створені root, однак зможе створювати власні файли. GDM намагатиметься змінити права доступу, якщо при першому запуску права будуть відрізнятись від вказаних вище. Каталог також використовується для інших приватних файлів, які зберігає служба. Інші користувачі не повинні мати змогу увійти в цей каталог та читати чи писати у файли у ньому. Будь-хто, хто може читати цей каталог, може з'єднатись з будь-яким дисплеєм на цьому комп'ютері." - -#: ../C/gdm.xml:1933(term) -msgid "SessionDesktopDir" -msgstr "SessionDesktopDir" - -#: ../C/gdm.xml:1935(synopsis) -#, no-wrap -msgid "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" -msgstr "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/" - -#: ../C/gdm.xml:1936(para) -msgid "Directory containing the <filename>.desktop</filename> 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 "Каталог, що містить файли <filename>.desktop</filename>, які представляють доступні сеанси на цій системі. Починаючи з 2.4.4.2, він розглядається як змінна типу PATH та використовується перший знайдений файл." - -#: ../C/gdm.xml:1946(term) -msgid "SoundProgram" -msgstr "SoundProgram" - -#: ../C/gdm.xml:1948(filename) -msgid "<bin>/play" -msgstr "<bin>/play" - -#: ../C/gdm.xml:1948(filename) -msgid "<bin>/audioplay" -msgstr "<bin>/audioplay" - -#: ../C/gdm.xml:1948(synopsis) -#, no-wrap -msgid "SoundProgram=<placeholder-1/> (or <placeholder-2/> on Solaris)" -msgstr "SoundProgram=<placeholder-1/> (або <placeholder-2/> на Solaris)" - -#: ../C/gdm.xml:1949(para) -msgid "Application to use when playing a sound. Currently used for playing the login sound, see the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0." -msgstr "Програма, що використовується для відтворення звуку. Наразі використовується для відтворення звуку при вході у сеанс, дивіться ключ <filename>SoundOnLoginFile</filename>. Підтримується з 2.5.90.0." - -#: ../C/gdm.xml:1959(term) -msgid "StandardXServer" -msgstr "StandardXServer" - -#: ../C/gdm.xml:1961(synopsis) -#, no-wrap -msgid "StandardXServer=/dir/to/X (value assigned by configuration file)" -msgstr "StandardXServer=/каталог/до/X (значення, що визначається у конфігураційному файлі)" - -#: ../C/gdm.xml:1962(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 "Повний шлях та необов'язкові аргументи команди запуску стандартного X-сервера. Використовується коли gdm не може знайти ніяке інше визначення, та використовується як типовий та аварійний варіант у кількох випадках. Має запускати якийсь X-сервер." - -#: ../C/gdm.xml:1973(term) -msgid "SuspendCommand" -msgstr "SuspendCommand" - -#: ../C/gdm.xml:1975(synopsis) -#, no-wrap -msgid "SuspendCommand=" -msgstr "SuspendCommand=" - -#: ../C/gdm.xml:1976(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:1987(term) -msgid "TimedLoginEnable" -msgstr "TimedLoginEnable" - -#: ../C/gdm.xml:1989(synopsis) -#, no-wrap -msgid "TimedLoginEnable=false" -msgstr "TimedLoginEnable=false" - -#: ../C/gdm.xml:1990(para) -msgid "If the user given in <filename>TimedLogin</filename> should be logged in after a number of seconds (set with <filename>TimedLoginDelay</filename>) of inactivity on the login screen. This is useful for public access terminals or perhaps even home use. If the user uses the keyboard or browses the menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or 30 seconds, whichever is higher. If the user does not enter a username but just hits the ENTER key while the login program is requesting the username, then GDM will assume the user wants to login immediately as the timed user. Note that no password will be asked for this user so you should be careful, although if using PAM it can be configured to require password entry before allowing login." -msgstr "Чи має запускатись сеанс користувача, вказаного у параметрі <filename>TimedLogin</filename>, після певної кількості секунд (у параметрі <filename>TimedLoginDelay</filename>) відсутності активності у вікні входу. Використовується для терміналів загального доступу або навіть у домашньому використанні. Якщо користувач використовує клавіатуру або переглядає меню, відлік часу скидається на <filename>TimedLoginDelay</filename> або 30 секунд, в залежності від того яке значення більше. Якщо користувач не ввів ім'я а просто натиснув на клавішу ENTER, тоді GDM вважає що користувач бажає негайно увійти з іменем користувача відкладеного входу. Зауважте, при цьому не запитується пароль, тож будьте обережні, хоча при використанні PAM можна налаштувати запит паролю перш, ніж дозволити вхід." - -#: ../C/gdm.xml:2010(term) -msgid "TimedLogin" -msgstr "TimedLogin" - -#: ../C/gdm.xml:2012(synopsis) -#, no-wrap -msgid "TimedLogin=" -msgstr "TimedLogin=" - -#: ../C/gdm.xml:2013(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 <filename>AutomaticLogin</filename> are supported. The same control chars and piping to a application are supported." -msgstr "Користувач, сеанс якого запускається після вказаного інтервалу неактивності. Ним не може бути \"root\", у будь-якому разі gdm відмовлятиметься запускати таким способом сеанс root. Підтримуються такі самі функції як і для <filename>AutomaticLogin</filename>. Використовуються такі самі керуючи символи та канали до програм." - -#: ../C/gdm.xml:2025(term) -msgid "TimedLoginDelay" -msgstr "TimedLoginDelay" - -#: ../C/gdm.xml:2027(synopsis) -#, no-wrap -msgid "TimedLoginDelay=30" -msgstr "TimedLoginDelay=30" - -#: ../C/gdm.xml:2028(para) -msgid "This is the delay before the <filename>TimedLogin</filename> user will be logged in. It must be greater then or equal to 10." -msgstr "Затримка до початку сеансу користувача, що вказаний у <filename>TimedLogin</filename>. Має бути більше або дорівнювати 10." - -#: ../C/gdm.xml:2036(term) -msgid "User" -msgstr "User" - -#: ../C/gdm.xml:2038(synopsis) -#, no-wrap -msgid "User=gdm" -msgstr "User=gdm" - -#: ../C/gdm.xml:2039(para) -msgid "The username under which <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> and the internal failsafe GTK+ dialogs are run. Also see <filename>Group</filename>. 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 "Ім'я користувача, від імені якого запускаються <command>gdmlogin</command>, <command>gdmgreeter</command>, <command>gdmchooser</command> та внутрішні аварійні діалогові вікна GTK+. Також дивіться параметр <filename>Group</filename>. Цей користувач матиме доступ до усіх файлів авторизації X-сервера, та, можливо, до інших внутрішніх даних GDM, тому він не повинен бути таким користувачем як nobody, а цілком окремим користувачем." - -#: ../C/gdm.xml:2053(term) -msgid "UserAuthDir" -msgstr "UserAuthDir" - -#: ../C/gdm.xml:2055(synopsis) -#, no-wrap -msgid "UserAuthDir=" -msgstr "UserAuthDir=" - -#: ../C/gdm.xml:2056(para) -msgid "The directory where user's <filename>.Xauthority</filename> 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: <filename>~/authdir/</filename>." -msgstr "Каталог, де має зберігатись файл <filename>.Xauthority</filename>. Якщо нічого не вказано, використовується домашній каталог користувача. Тильда розпізнається як домашній каталог, тому можна вказати щось подібне: <filename>~/authdir/</filename>." - -#: ../C/gdm.xml:2063(para) -msgid "If you do not use the tilde expansion, then the filename created will be random, like in <filename>UserAuthFBDir</filename>. This way many users can have the same authentication directory. For example you might want to set this to <filename>/tmp</filename> 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 <filename>/tmp</filename> directory." -msgstr "Якщо ви не використовуєте тильду, тоді назва створюваного файлу буде випадковою, подібна до <filename>UserAuthFBDir</filename>. Таким чином користувачі матимуть однаковий каталог аутентифікації. Наприклад, якщо домашній каталог користувача на NFS, ви можете встановити значення цього параметра <filename>/tmp</filename>, щоб файли cookie не передавались через мережу. Користувачі повинні мати право запису у цьому каталозі, та для цього каталогу має бути виставлений sticky-біт, як для каталогу <filename>/tmp</filename>." - -#: ../C/gdm.xml:2076(para) -msgid "Normally if this is the users 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 <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</filename> section to false." -msgstr "Зазвичай, якщо це домашній каталог користувачів, GDM не зберігатиме у ньому cookies, якщо вважатиме що він знаходиться на NFS (шляхом перевірки root-squashing). Це можна змінити призначивши параметру <filename>NeverPlaceCookiesOnNFS</filename> у розділі <filename>[security]</filename> значення false." - -#: ../C/gdm.xml:2087(term) -msgid "UserAuthFBDir" -msgstr "UserAuthFBDir" - -#: ../C/gdm.xml:2089(synopsis) -#, no-wrap -msgid "UserAuthFBDir=/tmp" -msgstr "UserAuthFBDir=/tmp" - -#: ../C/gdm.xml:2090(para) -msgid "If GDM fails to update the user's <filename>.Xauthority</filename> file a fallback cookie is created in this directory." -msgstr "Якщо GDM не вдається оновити файл <filename>.Xauthority</filename> для користувача, аварійний файл створюється у цьому каталозі." - -#: ../C/gdm.xml:2099(term) -msgid "UserAuthFile" -msgstr "UserAuthFile" - -#: ../C/gdm.xml:2101(synopsis) -#, no-wrap -msgid "UserAuthFile=.Xauthority" -msgstr "UserAuthFile=.Xauthority" - -#: ../C/gdm.xml:2102(para) -msgid "Name of the file used for storing user cookies." -msgstr "Назва файлу, що використовується для зберігання файлів cookie користувачів." - -#: ../C/gdm.xml:2109(term) -msgid "VTAllocation" -msgstr "VTAllocation" - -#: ../C/gdm.xml:2111(synopsis) -#, no-wrap -msgid "VTAllocation=true" -msgstr "VTAllocation=true" - -#: ../C/gdm.xml:2112(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 <filename>FirstVT</filename>." -msgstr "На системах, де GDM підтримує автоматичне призначення віртуальних терміналів (VT) (наразі лише у Linux), ви можете змусити GDM додавати аргумент vt до команди запуску X-сервера. Таким чином можна уникнути стану змагання, який виникає коли кожен X-сервер робить власний запит на керування віртуальним терміналом. Також дивіться <filename>FirstVT</filename>." - -#: ../C/gdm.xml:2124(term) -msgid "XKeepsCrashing" -msgstr "XKeepsCrashing" - -#: ../C/gdm.xml:2126(synopsis) -#, no-wrap -msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" -msgstr "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" - -#: ../C/gdm.xml:2127(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 <filename>XKeepsCrashing</filename> 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 "Сценарій, що запускається у випадку багаторазового аварійного завершення X-сервера. Використовується для запуску програми налаштовування X-сервера, або чогось іншого, що має створити працездатну конфігурацію X-сервера. Як приклад, дивіться сценарій, який постачається з дистрибутивом. Сценарій <filename>XKeepsCrashing</filename>, що надається, перевірявся на Red Hat, але може працювати і для інших систем. Ваш системний інтегратор має оновити цей сценарій для вашої системи." - -#: ../C/gdm.xml:2136(para) -msgid "In case <filename>FailsafeXServer</filename> is setup, that will be tried first. and this only used as a backup if even that X server keeps crashing." -msgstr "Якщо встановлено значення <filename>FailsafeXServer</filename>, його буде випробувано першим. Використовується лише як резерв, якщо сервер продовжує аварійно завершуватись." - -#: ../C/gdm.xml:2145(term) -msgid "Xnest" -msgstr "Xnest" - -#: ../C/gdm.xml:2147(synopsis) -#, no-wrap -msgid "Xnest=<bin>/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)" -msgstr "Xnest=<bin>/X11/Xnest (/usr/openwin/bin/Xnest на Solaris)" - -#: ../C/gdm.xml:2148(para) -msgid "The full path and arguments to the Xnest command. This is used for the flexible Xnest displays. This way the user can start new login screens in a nested window. Of course you must have the Xnest display from your X server packages installed for this to work." -msgstr "Повний шлях та необов'язкові аргументи команди запуску Xnest. Використовується для гнучких серверів Xnest. Таким чином користувач може запустити нові екрани входу у вкладених вікнах. Звичайно, у системі має бути встановлено Xnest з пакету X-сервера." - -#: ../C/gdm.xml:2161(title) -msgid "Security Options" -msgstr "Параметри безпеки" - -#: ../C/gdm.xml:2164(title) -msgid "[security]" -msgstr "[security]" - -#: ../C/gdm.xml:2167(term) -msgid "AllowRoot" -msgstr "AllowRoot" - -#: ../C/gdm.xml:2169(synopsis) -#, no-wrap -msgid "AllowRoot=true" -msgstr "AllowRoot=true" - -#: ../C/gdm.xml:2170(para) -msgid "Allow root (privileged user) to log in through GDM. Set this to false if you want to disallow such logins." -msgstr "Чи дозволяти користувачу root (адміністратору) входити через GDM. Значення false забороняє такий вхід." - -#: ../C/gdm.xml:2174(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 "На системах, що підтримуються PAM, цей параметр не такий корисний, тому що те саме можна зробити за допомогою PAM, або навіть більше. Проте, він досі діє, тому на системах з підтримкою PAM, можливо, слід встановити значення true." - -#: ../C/gdm.xml:2184(term) -msgid "AllowRemoteRoot" -msgstr "AllowRemoteRoot" - -#: ../C/gdm.xml:2186(synopsis) -#, no-wrap -msgid "AllowRemoteRoot=false" -msgstr "AllowRemoteRoot=false" - -#: ../C/gdm.xml:2187(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 "Чи дозволяти користувачу root (адміністратору) входити віддалено через GDM. Якщо треба вимкнути такий тип входу, встановіть значення false. Віддаленим входом є будь-який вхід через XDMCP." - -#: ../C/gdm.xml:2192(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 "На системах, що підтримуються PAM, цей параметр не такий корисний, тому що те саме можна зробити за допомогою PAM, та навіть більше." - -#: ../C/gdm.xml:2197(para) -msgid "This value will be overridden and set to false if the <filename>/etc/default/login</filename> file exists and contains \"CONSOLE=/dev/login\", and set to true if the <filename>/etc/default/login</filename> file exists and contains any other value or no value for CONSOLE." -msgstr "" - -#: ../C/gdm.xml:2208(term) -msgid "AllowRemoteAutoLogin" -msgstr "AllowRemoteAutoLogin" - -#: ../C/gdm.xml:2210(synopsis) -#, no-wrap -msgid "AllowRemoteAutoLogin=false" -msgstr "AllowRemoteAutoLogin=false" - -#: ../C/gdm.xml:2211(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 "Дозволити відкладений віддалений вхід. Тобто, віддалені з'єднання через XDMCP будуть мати можливість входу користувача, вказаного у \"TimedLogin\", при певному часі неактивності вікна входу, так само як і для користувачів на локальній консолі." - -#: ../C/gdm.xml:2217(para) -msgid "Note that this can make a system quite insecure, and thus is off by default." -msgstr "Зауважте, це може зробити систему дуже вразливою, тому початково вимкнено." - -#: ../C/gdm.xml:2225(term) -msgid "CheckDirOwner" -msgstr "CheckDirOwner" - -#: ../C/gdm.xml:2227(synopsis) -#, no-wrap -msgid "CheckDirOwner=true" -msgstr "CheckDirOwner=true" - -#: ../C/gdm.xml:2228(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 <filename>RelaxPermissions</filename> 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 "Типово, GDM перевіряє власників домашніх каталогів перед записом до них, це запобігає порушенню безпеки у разі помилок встановлення. Проте у деяких випадках власником домашніх каталогів буде інший користувач, тоді необхідно увімкнути цей параметр. Також слід встановити значення ключа <filename>RelaxPermissions</filename> принаймні у значення 1, бо за цим сценарієм домашні каталоги швидше за все доступні групі для запису. Підтримується з 2.6.0.4." - -#: ../C/gdm.xml:2242(term) -msgid "DisallowTCP" -msgstr "DisallowTCP" - -#: ../C/gdm.xml:2244(synopsis) -#, no-wrap -msgid "DisallowTCP=true" -msgstr "DisallowTCP=true" - -#: ../C/gdm.xml:2245(para) -msgid "If true, then always append <filename>-nolisten tcp</filename> 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 "Якщо встановлено, тоді завжди додається <filename>-nolisten tcp</filename> до команди запуску X-сервера, таким чином вимикаються TCP-з'єднання. Використовується якщо ви не збираєтесь використовувати віддалені з'єднання, тому що X-протокол потенційно може бути небезпечним, навіть якщо не відомо про існуючі проблеми з безпекою." - -#: ../C/gdm.xml:2258(term) -msgid "NeverPlaceCookiesOnNFS" -msgstr "NeverPlaceCookiesOnNFS" - -#: ../C/gdm.xml:2260(synopsis) -#, no-wrap -msgid "NeverPlaceCookiesOnNFS=true" -msgstr "NeverPlaceCookiesOnNFS=true" - -#: ../C/gdm.xml:2261(para) -msgid "Normally if this is true (which is by default), GDM will not place cookies into the users 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 "Зазвичай, якщо встановлено значення true (типово), GDM не зберігає cookie к домашньому каталозі користувача, якщо каталог знаходиться на NFS. GDM вважатиме будь-яку файлову систему з root-squashing файловою системою NFS. Проте іноді віддалені файлова система може мати root squashing та бути безпечною (можливо, з використанням шифрування). У цьому випадку встановіть значення 'false'. Зауважте, що цей параметр з'явився у версії 2.4.4.4 та ігнорується попередніми версіями." - -#: ../C/gdm.xml:2275(term) -msgid "PasswordRequired" -msgstr "PasswordRequired" - -#: ../C/gdm.xml:2277(synopsis) -#, no-wrap -msgid "PasswordRequired=false" -msgstr "PasswordRequired=false" - -#: ../C/gdm.xml:2278(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 <filename>/etc/default/login</filename> if it contains \"PASSREQ=[YES|NO]\". If the <filename>/etc/default/login</filename> file exists, but contains no value for PASSREQ, the value as defined in the GDM configuration will be used." -msgstr "" - -#: ../C/gdm.xml:2294(term) -msgid "RelaxPermissions" -msgstr "RelaxPermissions" - -#: ../C/gdm.xml:2296(synopsis) -#, no-wrap -msgid "RelaxPermissions=0" -msgstr "RelaxPermissions=0" - -#: ../C/gdm.xml:2297(para) -msgid "By default GDM ignores files and directories writable to other users than the owner." -msgstr "Типово, GDM ігнорує файли та каталоги доступні для запису іншим користувачам, окрім власника." - -#: ../C/gdm.xml:2302(para) -msgid "Changing the value of RelaxPermissions makes it possible to alter this behavior:" -msgstr "Зміна значення RelaxPermissions робить можливим зміну цієї поведінки:" - -#: ../C/gdm.xml:2307(para) -msgid "0 - Paranoia option. Only accepts user owned files and directories." -msgstr "0 - Параноїдальний режим. Допускаються лише файли та каталоги, власником яких є користувач." - -#: ../C/gdm.xml:2311(para) -msgid "1 - Allow group writable files and directories." -msgstr "1 - Допускаються файли та каталоги доступні для запису групі." - -#: ../C/gdm.xml:2314(para) -msgid "2 - Allow world writable files and directories." -msgstr "2 - Допускаються файли та каталоги доступні для запису іншим користувачам." - -#: ../C/gdm.xml:2321(term) -msgid "RetryDelay" -msgstr "RetryDelay" - -#: ../C/gdm.xml:2323(synopsis) -#, no-wrap -msgid "RetryDelay=1" -msgstr "RetryDelay=1" - -#: ../C/gdm.xml:2324(para) -msgid "The number of seconds GDM should wait before reactivating the entry field after a failed login." -msgstr "Кількість секунд, які GDM має зачекати після невдалої спроби входу перед повторною активацією поля входу." - -#: ../C/gdm.xml:2332(term) -msgid "UserMaxFile" -msgstr "UserMaxFile" - -#: ../C/gdm.xml:2334(synopsis) -#, no-wrap -msgid "UserMaxFile=65536" -msgstr "UserMaxFile=65536" - -#: ../C/gdm.xml:2335(para) -msgid "GDM will refuse to read/write files bigger than this number (specified in bytes)." -msgstr "GDM не буде читати/записувати файли більші за розміром за це число (у байтах)." - -#: ../C/gdm.xml:2340(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 <filename>RelaxPermissions</filename> option for more info." -msgstr "Окрім перевірки розміру GDM дуже прискіпливий відносно доступу до файлів у каталогах. Він не розв'язує символічні посилання, та може, в залежності від параметрів, не сприймати файли та каталоги, що доступні для запису іншим користувачам від власника. Докладнішу інформацію дивіться у параметрі <filename>RelaxPermissions</filename>і." - -#: ../C/gdm.xml:2353(title) -msgid "XDCMP Support" -msgstr "Підтримка XDCMP" - -#: ../C/gdm.xml:2356(title) -msgid "[xdmcp]" -msgstr "[xdmcp]" - -#: ../C/gdm.xml:2359(term) -msgid "DisplaysPerHost" -msgstr "DisplaysPerHost" - -#: ../C/gdm.xml:2361(synopsis) -#, no-wrap -msgid "DisplaysPerHost=1" -msgstr "DisplaysPerHost=1" - -#: ../C/gdm.xml:2362(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 <filename>DisplaysPerHost</filename> value accordingly." -msgstr "Щоб атакуючі не змогли наводнити запитами чергу очікування, GDM допускає одне з'єднання з одного віддаленого комп'ютера. Якщо ви бажаєте надавати дисплей комп'ютерам з більш ніж одним екраном, відповідно слід збільшити значення <filename>DisplaysPerHost</filename>." - -#: ../C/gdm.xml:2370(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:2378(term) -#: ../C/gdm.xml:3625(term) -msgid "Enable" -msgstr "Enable" - -#: ../C/gdm.xml:2380(synopsis) -#: ../C/gdm.xml:3627(synopsis) -#, no-wrap -msgid "Enable=false" -msgstr "Enable=false" - -#: ../C/gdm.xml:2381(para) -msgid "Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM." -msgstr "Встановлення значення у true вмикає підтримку XDMCP, що дозволяє керувати GDM віддаленими дисплеями/X-терміналами." - -#: ../C/gdm.xml:2386(para) -msgid "<filename>gdm</filename> listens for requests on UDP port 177. See the Port option for more information." -msgstr "<filename>gdm</filename> очікує запити на UDP-порту 177. Докладніше дивіться у параметрі Port." - -#: ../C/gdm.xml:2391(para) -msgid "If GDM is compiled to support it, access from remote displays can be controlled using the TCP Wrappers library. The service name is <filename>gdm</filename>" -msgstr "Якщо GDM скомпільовано з бібліотекою tcp_wrapper, доступ з віддалених дисплеїв може контролюватись цією бібліотекою. Назва служби - <filename>gdm</filename>" - -#: ../C/gdm.xml:2397(para) -msgid "" -"You should add <screen>\n" -"gdm:.my.domain\n" -"</screen> to your <filename><etc>/hosts.allow</filename>, depending on your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details." -msgstr "" -"До файлу <filename><etc>/hosts.allow</filename> слід додати <screen>\n" -"gdm:.my.domain\n" -"</screen>, в залежності від конфігурації бібліотеки TCP Wrappers. Докладнішу інформацію дивіться у man-сторінці <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink>." - -#: ../C/gdm.xml:2408(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 "Зауважте, що XDMCP не є безпечним протоколом, тому якщо ви не використовуєте UDP-порт 177, його краще заблокувати на вашому брандмауері." - -#: ../C/gdm.xml:2417(term) -msgid "EnableProxy" -msgstr "EnableProxy" - -#: ../C/gdm.xml:2419(synopsis) -#, no-wrap -msgid "EnableProxy=false" -msgstr "EnableProxy=false" - -#: ../C/gdm.xml:2420(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 "При встановленні значення true вмикається підтримка запуску сеансів XDMCP на локальному проксі X-сервері. Таким чином можна збільшити продуктивність сеансів XDMCP, особливо у мережах з великою затримкою, бо багато операцій X-протоколу можуть завершуватись без передачі по мережі." - -#: ../C/gdm.xml:2427(para) -msgid "Note, however, that this mode will significantly increase the burden on the machine hosting the XDMCP sessions" -msgstr "Проте зауважте, у цьому режимі значно збільшується навантаження на сервер сеансів XDMCP" - -#: ../C/gdm.xml:2431(para) -msgid "See the <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</filename> options for further details on how to configure support for this feature." -msgstr "Докладніше про налаштовування цієї функції дивіться у описі параметрів <filename>FlexiProxy</filename> та <filename>FlexiProxyDisconnect</filename>." - -#: ../C/gdm.xml:2440(term) -msgid "HonorIndirect" -msgstr "HonorIndirect" - -#: ../C/gdm.xml:2442(synopsis) -#, no-wrap -msgid "HonorIndirect=true" -msgstr "HonorIndirect=true" - -#: ../C/gdm.xml:2443(para) -msgid "Enables XDMCP INDIRECT choosing (i.e. remote execution of <filename>gdmchooser</filename>) for X-terminals which don't supply their own display browser." -msgstr "Дозволяє XDMCP INDIRECT вибір (тобто віддалене виконання <filename>gdmchooser</filename>) для X-терміналів, як не мають власної програми перегляду дисплеїв." - -#: ../C/gdm.xml:2452(term) -msgid "MaxPending" -msgstr "MaxPending" - -#: ../C/gdm.xml:2454(synopsis) -#, no-wrap -msgid "MaxPending=4" -msgstr "MaxPending=4" - -#: ../C/gdm.xml:2455(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 "Для запобігання атакам типу \"відмова у доступі\", GDM має фіксований розмір черги очікуючих з'єднань. Одночасно можуть бути запущені лише MaxPending дисплеїв." - -#: ../C/gdm.xml:2461(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:2470(term) -msgid "MaxPendingIndirect" -msgstr "MaxPendingIndirect" - -#: ../C/gdm.xml:2472(synopsis) -#, no-wrap -msgid "MaxPendingIndirect=4" -msgstr "MaxPendingIndirect=4" - -#: ../C/gdm.xml:2473(para) -msgid "GDM will only provide <filename>MaxPendingIndirect</filename> displays with host choosers simultaneously. If more queries from different hosts come in, the oldest ones will be forgotten." -msgstr "Одночасно GDM надає лише <filename>MaxPendingIndirect</filename> дисплеїв з програмою вибору вузла. При отриманні більшої кількості запитів від різних вузлів, старші з них забуваються." - -#: ../C/gdm.xml:2483(term) -msgid "MaxSessions" -msgstr "MaxSessions" - -#: ../C/gdm.xml:2485(synopsis) -#, no-wrap -msgid "MaxSessions=16" -msgstr "MaxSessions=16" - -#: ../C/gdm.xml:2486(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:2495(term) -msgid "MaxWait" -msgstr "MaxWait" - -#: ../C/gdm.xml:2497(synopsis) -#, no-wrap -msgid "MaxWait=30" -msgstr "MaxWait=30" - -#: ../C/gdm.xml:2498(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 "Коли GDM готовий керувати дисплеєм, йому надсилається пакет ACCEPT який містить унікальний ідентифікатор сеансу, що використовується у майбутніх пакетах XDMCP." - -#: ../C/gdm.xml:2504(para) -msgid "GDM will then place the session id in the pending queue waiting for the display to respond with a MANAGE request." -msgstr "Потім GDM зберігає ідентифікатор сеансу у черзі, очікуючи відповіді від дисплея пакетом MANAGE." - -#: ../C/gdm.xml:2509(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 "Якщо відповідь не надійшла протягом MaxWait секунд, GDM вважає дисплей мертвим та стирає його з черги очікування звільняючи слот для іншого дисплею." - -#: ../C/gdm.xml:2518(term) -msgid "MaxWaitIndirect" -msgstr "MaxWaitIndirect" - -#: ../C/gdm.xml:2520(synopsis) -#, no-wrap -msgid "MaxWaitIndirect=30" -msgstr "MaxWaitIndirect=30" - -#: ../C/gdm.xml:2521(para) -msgid "The MaxWaitIndirect parameter determines the maximum number of seconds between the time where a user chooses a host and the subsequent indirect query where the user is connected to the host. When the timeout is exceeded, the information about the chosen host is forgotten and the indirect slot freed up for other displays. The information may be forgotten earlier if there are more hosts trying to send indirect queries then <filename>MaxPendingIndirect</filename>." -msgstr "Параметр MaxWaitIndirect визначає максимальну кількість секунд між часом, коли користувач вибрав вузол та наступним непрямим запитом до вузла. При перевищенні інтервалу очікування, інформація про вибраний вузол забувається та слот непрямого запиту звільняється. Інформація може відкинутись раніше, якщо вузлів, що намагаються надіслати непрямі запити більше за <filename>MaxPendingIndirect</filename>." - -#: ../C/gdm.xml:2535(term) -msgid "Port" -msgstr "Port" - -#: ../C/gdm.xml:2537(synopsis) -#, no-wrap -msgid "Port=177" -msgstr "Port=177" - -#: ../C/gdm.xml:2538(para) -msgid "The UDP port number <filename>gdm</filename> should listen to for XDMCP requests. Don't change this unless you know what you are doing." -msgstr "Номер UDP-порта, на якому <filename>gdm</filename> очікуватиме XDMCP-запитів. Не змінюйте його, якщо ви не знаєте що робите." - -#: ../C/gdm.xml:2547(term) -msgid "PingIntervalSeconds" -msgstr "PingIntervalSeconds" - -#: ../C/gdm.xml:2549(synopsis) -#, no-wrap -msgid "PingIntervalSeconds=15" -msgstr "PingIntervalSeconds=15" - -#: ../C/gdm.xml:2550(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 "Інтервал у секундах між ping-запитами до X-сервера. Якщо X-сервер не повернув відповідь до наступного ping-запиту, з'єднання розривається та сеанс завершується. Це - комбінація XDM PingInterval та PingTimeout, але у секундах." - -#: ../C/gdm.xml:2558(para) -msgid "Note that GDM in the past used to have a <filename>PingInterval</filename> configuration key which was also in minutes. For most purposes you'd want this setting to be lower 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 "Зауважте, що GDM у минулому мав ключ конфігурації <filename>PingInterval</filename>, який вказував час у хвилинах. Для більшості застосувань XDMCP не потрібно, щоб значення цього параметра було менше за одну хвилину, проте затримка більша за 15 секунд означатиме, що термінал вимкнений або перезавантажений, та вам слід завершити сеанс." - -#: ../C/gdm.xml:2571(term) -msgid "ProxyReconnect" -msgstr "ProxyReconnect" - -#: ../C/gdm.xml:2573(synopsis) -#, no-wrap -msgid "FlexiProxyReconnect=" -msgstr "FlexiProxyReconnect=" - -#: ../C/gdm.xml:2574(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 "Встановлення значення параметра вмикає експериментальну підтримку міграції сеансів XDMCP. Це дозволяє користувачам від'єднуватись від їх сеансів та пізніше приєднуватись до того самого сеансу, можливо з іншого терміналу." - -#: ../C/gdm.xml:2580(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 "Для використання цієї функції потрібен вкладений X-сервер з підтримкою від'єднання від батьківського X-сервера та з'єднання з іншим сервером. Наразі, цю функцію у деякому ступені підтримує розподілений багатоекранний X-сервер (Distributed Multihead X - DMX), а інші проекти, такі як NoMachine NX зайняті її реалізацією." - -#: ../C/gdm.xml:2587(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 "Значенням цього параметра слід встановити шлях до команди, яка обробляє повторне з'єднання XDMCP-проксі до іншого дисплею. Приклад реалізації постачається з DMX." - -#: ../C/gdm.xml:2596(term) -msgid "ProxyXServer" -msgstr "ProxyXServer" - -#: ../C/gdm.xml:2598(synopsis) -#, no-wrap -msgid "ProxyXServer=" -msgstr "ProxyXServer=" - -#: ../C/gdm.xml:2599(para) -msgid "The X server command line for a XDMCP proxy. Any nested X server like Xnest, Xephr or Xdmx should work fairly well." -msgstr "Рядок з командою X-сервера для XDMCP-проксі. Можна вказати будь-який вкладений X-сервер, такий як Xnest, Xephr чи Xdmx." - -#: ../C/gdm.xml:2607(term) -msgid "Willing" -msgstr "Willing" - -#: ../C/gdm.xml:2609(synopsis) -#, no-wrap -msgid "Willing=<etc>/gdm/Xwilling" -msgstr "Willing=<etc>/gdm/Xwilling" - -#: ../C/gdm.xml:2610(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 "Коли сервер надсилає пакет WILLING у відповідь на QUERY, він надсилає рядок з поточним статусом цього сервера. Типовим повідомленням є системний ідентифікатор, але можна створити власний сценарій, який відображатиме власне повідомлення. Якщо цей сценарій не існує або цей ключ порожній - надсилається типове повідомлення. Якщо цей сценарій успішно виконується та виводить деякий текст, надсилається перший рядок цього тексту (та лише перший рядок). Він запускається максимум раз на 3 секунди для запобігання можливим атакам типу \"відмова у доступі\" шляхом затоплення його запитами QUERY." - -#: ../C/gdm.xml:2628(title) -msgid "Common GUI Configuration Options" -msgstr "Загальні параметри графічного інтерфейсу" - -#: ../C/gdm.xml:2631(title) -msgid "[gui]" -msgstr "[gui]" - -#: ../C/gdm.xml:2634(term) -msgid "AllowGtkThemeChange" -msgstr "AllowGtkThemeChange" - -#: ../C/gdm.xml:2636(synopsis) -#, no-wrap -msgid "AllowGtkThemeChange=true" -msgstr "AllowGtkThemeChange=true" - -#: ../C/gdm.xml:2637(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 "Чи дозволяти зміну теми GTK+ (віджет) з програми привітання. Наразі це стосується лише стандартної програми привітання, а графічна програма привітання поки не має такої можливості. Тема застосовується до екрану доки її не буде змінено та буде стосуватись усіх інших вікон GDM. Підтримується з 2.5.90.2." - -#: ../C/gdm.xml:2649(term) -msgid "GtkRC" -msgstr "Gtkrc" - -#: ../C/gdm.xml:2651(synopsis) -#, no-wrap -msgid "GtkRC=" -msgstr "GtkRC=" - -#: ../C/gdm.xml:2652(para) -msgid "Path to a <filename>gtkrc</filename> to read when GDM puts up a window. You should really now use the <filename>GtkTheme</filename> key for just setting a theme." -msgstr "Шлях до <filename>gtkrc</filename>, що читається коли GDM виводить вікно. Зараз, натомість використовуйте ключ <filename>GtkTheme</filename> для встановлення теми." - -#: ../C/gdm.xml:2661(term) -msgid "GtkTheme" -msgstr "GtkTheme" - -#: ../C/gdm.xml:2663(synopsis) -#, no-wrap -msgid "GtkTheme=Default" -msgstr "GtkTheme=Default" - -#: ../C/gdm.xml:2664(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 "Назва встановленої теми. Вона використовується у програмі привітання, програмі вибору, та усіх інших графічних вікнах GDM. Підтримується з 2.5.90.2." - -#: ../C/gdm.xml:2673(term) -msgid "GtkThemesToAllow" -msgstr "GtkThemesToAllow" - -#: ../C/gdm.xml:2675(synopsis) -#, no-wrap -msgid "GtkThemesToAllow=all" -msgstr "GtkThemesToAllow=all" - -#: ../C/gdm.xml:2676(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 <filename>AllowGtkThemeChange</filename> key. Supported since 2.5.90.2." -msgstr "Список розділених комою допустимих тем. Це мають бути назви встановлених у стандартному місці тем GTK+. Також можна вказати 'all', щоб дозволити усі встановлені теми. Це відноситься до ключа <filename>AllowGtkThemeChange</filename>. Підтримується з 2.5.90.2." - -#: ../C/gdm.xml:2688(term) -msgid "MaxIconWidth" -msgstr "MaxIconWidth" - -#: ../C/gdm.xml:2690(synopsis) -#, no-wrap -msgid "MaxIconWidth=128" -msgstr "MaxIconWidth=128" - -#: ../C/gdm.xml:2691(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 "Визначає максимальну ширину значка (у точках) при перегляді портретів. Більші за розміром значку будуть змінювати масштаб. Це також впливає на значки програми вибору XDMCP." - -#: ../C/gdm.xml:2700(term) -msgid "MaxIconHeight" -msgstr "MaxIconHeight" - -#: ../C/gdm.xml:2702(synopsis) -#, no-wrap -msgid "MaxIconHeight=128" -msgstr "MaxIconHeight=128" - -#: ../C/gdm.xml:2703(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 "Визначає максимальну висоту значка (у точках) у переглядачі портретів. Більші за розміром значку будуть змінювати масштаб. Це також впливає на значки програми вибору XDMCP." - -#: ../C/gdm.xml:2714(title) -msgid "Greeter Configuration" -msgstr "Конфігурація програми привітання" - -#: ../C/gdm.xml:2717(title) -msgid "[greeter]" -msgstr "[greeter]" - -#: ../C/gdm.xml:2720(term) -msgid "BackgroundColor" -msgstr "BackgroundColor" - -#: ../C/gdm.xml:2722(synopsis) -#, no-wrap -msgid "BackgroundColor=#76848F" -msgstr "BackgroundColor=#76848F" - -#: ../C/gdm.xml:2723(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 "Якщо BackgroundType дорівнює 2, тоді цей колір використовується для тла програми привітання. Він також використовується як задній план прозорих зображень на тлі, якщо встановлено параметр BackgroundRemoteOnlyColor та це віддалений дисплей. Впливає лише на програму привітання на GTK+." - -#: ../C/gdm.xml:2734(term) -msgid "BackgroundProgramInitialDelay" -msgstr "BackgroundProgramInitialDelay" - -#: ../C/gdm.xml:2736(synopsis) -#, no-wrap -msgid "BackgroundProgramInitialDelay=30" -msgstr "BackgroundProgramInitialDelay=30" - -#: ../C/gdm.xml:2737(para) -msgid "The background application will be started after at least that many seconds of inactivity." -msgstr "Програма на тлі запускатиметься після вказаної кількості секунд неактивності." - -#: ../C/gdm.xml:2745(term) -msgid "RestartBackgroundProgram" -msgstr "RestartBackgroundProgram" - -#: ../C/gdm.xml:2747(synopsis) -#, no-wrap -msgid "RestartBackgroundProgram=true" -msgstr "RestartBackgroundProgram=true" - -#: ../C/gdm.xml:2748(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:2758(term) -msgid "BackgroundProgramRestartDelay" -msgstr "BackgroundProgramRestartDelay" - -#: ../C/gdm.xml:2760(synopsis) -#, no-wrap -msgid "BackgroundProgramRestartDelay=30" -msgstr "BackgroundProgramRestartDelay=30" - -#: ../C/gdm.xml:2761(para) -msgid "The background application will be restarted after at least that many seconds of inactivity." -msgstr "Програма на тлі буде перезапускатись після неактивності протягом вказаної кількості секунд." - -#: ../C/gdm.xml:2769(term) -msgid "BackgroundImage" -msgstr "BackgroundImage" - -#: ../C/gdm.xml:2771(synopsis) -#, no-wrap -msgid "BackgroundImage=somefile.png" -msgstr "BackgroundImage=somefile.png" - -#: ../C/gdm.xml:2772(para) -msgid "If the BackgroundType is 1, then display this file as the background in the greeter. This only affects the GTK+ Greeter." -msgstr "Якщо BackgroundType дорівнює 1, тоді цей файл відображається як тло програми привітання. Впливає лише на програму привітання на GTK+." - -#: ../C/gdm.xml:2781(term) -msgid "BackgroundProgram" -msgstr "BackgroundProgram" - -#: ../C/gdm.xml:2783(synopsis) -#, no-wrap -msgid "BackgroundProgram=<bin>/xeyes" -msgstr "BackgroundProgram=<bin>/xeyes" - -#: ../C/gdm.xml:2784(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 "Якщо значення встановлено, ця команда буде запускатись на тлі під час відображення вікна входу. Зауважте, що не усі програми запускаються таким чином, тому що для GDM зазвичай не встановлено домашній каталог. Можна встановити домашній каталог для користувача GDM, якщо ви бажаєте запускати програми які цього вимагають. Цей параметр впливає лише на програму привітання на GTK+." - -#: ../C/gdm.xml:2796(term) -msgid "BackgroundRemoteOnlyColor" -msgstr "BackgroundRemoteOnlyColor" - -#: ../C/gdm.xml:2798(synopsis) -#, no-wrap -msgid "BackgroundRemoteOnlyColor=true" -msgstr "BackgroundRemoteOnlyColor=true" - -#: ../C/gdm.xml:2799(para) -msgid "On remote displays only set the color background. This is to make network load lighter. The <filename>BackgroundProgram</filename> is also not run. This only affects the GTK+ Greeter." -msgstr "На віддалених дисплеях встановлюється лише колір тла. Це зменшує навантаження на мережу. Також не запускається визначена у <filename>BackgroundProgram</filename> програма. Цей параметр впливає лише на програму привітання на GTK+." - -#: ../C/gdm.xml:2809(term) -msgid "BackgroundScaleToFit" -msgstr "BackgroundScaleToFit" - -#: ../C/gdm.xml:2811(synopsis) -#, no-wrap -msgid "BackgroundScaleToFit=true" -msgstr "BackgroundScaleToFit=true" - -#: ../C/gdm.xml:2812(para) -msgid "Scale background image to fit the screen. This only affects the GTK+ Greeter." -msgstr "Змінювати масштаб зображення до меж екрану. Цей параметр впливає лише на програму привітання на GTK+." - -#: ../C/gdm.xml:2820(term) -msgid "BackgroundType" -msgstr "BackgroundType" - -#: ../C/gdm.xml:2822(synopsis) -#, no-wrap -msgid "BackgroundType=2" -msgstr "BackgroundType=2" - -#: ../C/gdm.xml:2823(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 "Тип тла. 0 - немає, 1 - зображення, 2 - колір, 3 - зображення. Цей параметр впливає лише на програму привітання на GTK+." - -#: ../C/gdm.xml:2831(term) -msgid "Browser" -msgstr "Browser" - -#: ../C/gdm.xml:2833(synopsis) -#, no-wrap -msgid "Browser=true" -msgstr "Browser=true" - -#: ../C/gdm.xml:2834(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 "При значенні true вмикається переглядач портретів. Докладніше про переглядач портретів дивіться у розділі ``Програма привітання на GTK+''. Цей параметр впливає лише на програму привітання на GTK+ . При використанні програми привітання з підтримкою тем, переглядач портретів вмикається вибором теми, яка включає переглядач портретів" - -#: ../C/gdm.xml:2845(term) -msgid "ChooserButton" -msgstr "ChooserButton" - -#: ../C/gdm.xml:2847(synopsis) -#, no-wrap -msgid "ChooserButton=true" -msgstr "ChooserButton=true" - -#: ../C/gdm.xml:2848(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 "Якщо має значення true, до меню Дії додається кнопка, якою перезапускається поточний сервер з програмою вибору. Для цього не обов'язково вмикати XDMCP на локальному комп'ютері." - -#: ../C/gdm.xml:2857(term) -msgid "ConfigAvailable" -msgstr "ConfigAvailable" - -#: ../C/gdm.xml:2859(synopsis) -#, no-wrap -msgid "ConfigAvailable=false" -msgstr "ConfigAvailable=false" - -#: ../C/gdm.xml:2860(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 <filename>Configurator</filename> option in the daemon section." -msgstr "Якщо має значення true, це дозволяє запускати програму налаштовування з програми привітання. Зауважте, перед запуском програми налаштовування користувач має ввести пароль root. Дивіться параметр <filename>Configurator</filename> у розділі daemon." - -#: ../C/gdm.xml:2872(term) -msgid "DefaultFace" -msgstr "DefaultFace" - -#: ../C/gdm.xml:2874(synopsis) -#, no-wrap -msgid "DefaultFace=<share>/pixmaps/nophoto.png" -msgstr "DefaultFace=<share>/pixmaps/nophoto.png" - -#: ../C/gdm.xml:2875(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 <filename>DefaultFace</filename> will be used. The image must be in an gdk-pixbuf supported format and the file must be readable to the GDM user." -msgstr "Якщо користувач не визначив зображення для перегляду портретів, GDM використовує стандартний_значок з поточної теми GTK+. Якщо такий значок не визначений, використовується <filename>DefaultFace</filename>. Зображення має бути у форматі, який підтримує gdk-pixbuf та файл має бути доступним для читання користувачу GDM." - -#: ../C/gdm.xml:2887(term) -msgid "Include" -msgstr "Include" - -#: ../C/gdm.xml:2889(synopsis) -#, no-wrap -msgid "Include=" -msgstr "Include=" - -#: ../C/gdm.xml:2890(para) -msgid "Comma separated list of users to be included in the face browser and in the <command>gdmsetup</command> selection list for Automatic/Timed login. See also <filename>Exclude</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." -msgstr "Список розділених комою користувачів, які включаються у переглядач портретів та у список для вибору в <command>gdmsetup</command> користувача для автоматичного входу у сеанс. Також дивіться <filename>Exclude</filename>, <filename>IncludeAll</filename>, та <filename>MinimalUID</filename>." - -#: ../C/gdm.xml:2902(term) -msgid "Exclude" -msgstr "Exclude" - -#: ../C/gdm.xml:2904(synopsis) -#, no-wrap -msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." -msgstr "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." - -#: ../C/gdm.xml:2905(para) -msgid "Comma separated list of users to be excluded from the face browser and from the <command>gdmsetup</command> selection list for Automatic/Timed login. Excluded users will still be able to log in, but will have to type their username. See also <filename>Include</filename>, <filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." -msgstr "Список розділених комою користувачів, які виключаються з переглядача портретів та зі списку для вибору в <command>gdmsetup</command> користувача для автоматичного входу у сеанс. Виключені користувачі все-таки можуть увійти, але мають ввести своє ім'я. Також дивіться <filename>Include</filename>, <filename>IncludeAll</filename>, та <filename>MinimalUID</filename>." - -#: ../C/gdm.xml:2918(term) -msgid "IncludeAll" -msgstr "IncludeAll" - -#: ../C/gdm.xml:2920(synopsis) -#, no-wrap -msgid "IncludeAll=false" -msgstr "IncludeAll=false" - -#: ../C/gdm.xml:2921(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 <filename>Include</filename>, <filename>Exclude</filename>, and <filename>MinimalUID</filename>." -msgstr "Типово, порожній список включених користувачів означає - не відображати користувачів. Але при встановленні значення IncludeAll у true, буде скануватись файл паролів та будуть відображатись усі користувач окрім користувачів, виключених у параметрі Exclude, та користувачів чий ідентифікатор менший за MinimalUID. Сканування файл паролі може сповільнити систему з великою кількістю користувачів, тому цю властивість не слід використовувати у таких середовищах. Також дивіться <filename>Include</filename>, <filename>Exclude</filename>, та <filename>MinimalUID</filename>." - -#: ../C/gdm.xml:2937(term) -msgid "GlobalFaceDir" -msgstr "GlobalFaceDir" - -#: ../C/gdm.xml:2939(synopsis) -#, no-wrap -msgid "GlobalFaceDir=<share>/pixmaps/faces/" -msgstr "GlobalFaceDir=<share>/pixmaps/faces/" - -#: ../C/gdm.xml:2940(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:2946(para) -msgid "I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the face icon for the user ``johndoe''. No image format extension should be specified." -msgstr "Наприклад, <filename><GlobalFaceDir>/johndoe</filename> містить портрет користувача ``johndoe''. Не слід вказувати розширення файлу." - -#: ../C/gdm.xml:2952(para) -msgid "The face images must be stored in gdk-pixbuf supported formats and they must be readable for the GDM user." -msgstr "Зображення портретів мають бути у підтримуваному gdk-pixbuf форматі та доступні для читання користувачу GDM." - -#: ../C/gdm.xml:2957(para) -msgid "A user's own icon file will always take precedence over the sysadmin provided one." -msgstr "Власний файл користувача завжди має перевагу над встановленим системним адміністратором." - -#: ../C/gdm.xml:2965(term) -msgid "GraphicalTheme" -msgstr "GraphicalTheme" - -#: ../C/gdm.xml:2967(synopsis) -#, no-wrap -msgid "GraphicalTheme=circles" -msgstr "GraphicalTheme=circles" - -#: ../C/gdm.xml:2968(para) -msgid "The graphical theme that the Themed Greeter should use. it should refer to a directory in the theme directory set by <filename>GraphicalThemeDir</filename>." -msgstr "Графічна тема, яку використовує програма привітання з підтримкою тем. Параметр має посилатись на каталог у каталозі тем, що встановлений у <filename>GraphicalThemeDir</filename>." - -#: ../C/gdm.xml:2977(term) -msgid "GraphicalThemes" -msgstr "GraphicalThemes" - -#: ../C/gdm.xml:2979(synopsis) -#, no-wrap -msgid "GraphicalThemes=circles" -msgstr "GraphicalThemes=circles" - -#: ../C/gdm.xml:2980(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 <filename>GraphicalThemeDir</filename>. This is only used if <filename>GraphicalThemeRand</filename> is set to true." -msgstr "Графічні теми, які використовує програма привітання з підтримкою тем, у режимі випадкової зміни тем. Теми у списку розділюються знаком \"/:\". Каталог з темами визначається параметром <filename>GraphicalThemeDir</filename>. Використовується лише якщо <filename>GraphicalThemeRand</filename> має значення true." - -#: ../C/gdm.xml:2992(term) -msgid "GraphicalThemeRand" -msgstr "GraphicalThemeRand" - -#: ../C/gdm.xml:2994(synopsis) -#, no-wrap -msgid "GraphicalThemeRand=false" -msgstr "GraphicalThemeRand=false" - -#: ../C/gdm.xml:2995(para) -msgid "Whether the graphical greeter will use Only One Theme or Random Theme mode. Only One Theme mode uses themes listed by <filename>GraphicalTheme</filename>, Random Themes mode uses themes listed by <filename>GraphicalThemes</filename>. 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 "Чи буде графічна програма привітання у режимі з однією темою або у режимі випадкової зміни теми. У режимі з однією темою використовуються теми, що перелічені у <filename>GraphicalTheme</filename>. У режимі з випадковою зміною тем використовуються теми, перелічені у <filename>GraphicalThemes</filename>. Якщо параметр має значення false - використовується режим з однією темою, якщо значення дорівнює true - використовується режим з випадковою зміною тем." - -#: ../C/gdm.xml:3007(term) -msgid "GraphicalThemeDir" -msgstr "GraphicalThemeDir" - -#: ../C/gdm.xml:3009(synopsis) -#, no-wrap -msgid "GraphicalThemeDir=<share>/gdm/themes/" -msgstr "GraphicalThemeDir=<share>/gdm/themes/" - -#: ../C/gdm.xml:3010(para) -msgid "The directory where themes for the Themed Greeter are installed." -msgstr "Каталог де встановлено теми програми привітання з темами." - -#: ../C/gdm.xml:3018(term) -msgid "GraphicalThemedColor" -msgstr "GraphicalThemedColor" - -#: ../C/gdm.xml:3020(synopsis) -#, no-wrap -msgid "GraphicalThemedColor=#76848F" -msgstr "GraphicalThemedColor=#76848F" - -#: ../C/gdm.xml:3021(para) -msgid "Use this color in the background of the Themed Greeter. This only affects the Themed Greeter." -msgstr "Використовувати цей колір як тло програми привітання з підтримкою тем. Впливає лише на програму привітання на GTK+." - -#: ../C/gdm.xml:3029(term) -msgid "InfoMsgFile" -msgstr "InfoMsgFile" - -#: ../C/gdm.xml:3031(synopsis) -#, no-wrap -msgid "InfoMsgFile=/path/to/infofile" -msgstr "InfoMsgFile=/шлях/до/файлу" - -#: ../C/gdm.xml:3032(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 "Якщо цей параметр вказаний та /шлях/до/файлу вказує на існуючий та доступний для читання файл (наприклад, <etc>/infomsg.txt), перед допуском користувача до входу у модальному діалоговому вікні відобразиться вміст цього файлу. Параметр впливає як на стандартну програму привітання, так і програму привітання з підтримкою тем." - -#: ../C/gdm.xml:3043(term) -msgid "InfoMsgFont" -msgstr "InfoMsgFont" - -#: ../C/gdm.xml:3045(synopsis) -#, no-wrap -msgid "InfoMsgFont=fontspec" -msgstr "InfoMsgFont=шрифт" - -#: ../C/gdm.xml:3046(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 "Якщо цей параметр вказаний та використовується параметр InfoMsgFile (дивіться вище), тут вказується шрифт для відображення вмісту текстового файлу, вказаного у InfoMsgFile. Наприклад, для вказівки шрифту без зарубок можна вказати Sans 24. Параметр впливає як на стандартну програму привітання, так і програму привітання з підтримкою тем." - -#: ../C/gdm.xml:3058(term) -msgid "LocaleFile" -msgstr "LocaleFile" - -#: ../C/gdm.xml:3060(synopsis) -#, no-wrap -msgid "LocaleFile=<etc>/gdm/locale.alias" -msgstr "LocaleFile=<etc>/gdm/locale.alias" - -#: ../C/gdm.xml:3061(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 "Файл у подібному до GNU locale форматі з записами для усіх підтримуваних системою мов. Опис формату можна знайти вище або у коментарях у цьому файлі." - -#: ../C/gdm.xml:3070(term) -msgid "LockPosition" -msgstr "LockPosition" - -#: ../C/gdm.xml:3072(synopsis) -#, no-wrap -msgid "LockPosition=true" -msgstr "LockPosition=true" - -#: ../C/gdm.xml:3073(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 "Якщо має значення true - позицію вікна входу у графічній програм привітання GTK+ Greeter буде неможливо змінити, навіть якщо увімкнено заголовок вікна." - -#: ../C/gdm.xml:3081(term) -msgid "Logo" -msgstr "Logo" - -#: ../C/gdm.xml:3083(synopsis) -#, no-wrap -msgid "Logo=<share>/pixmaps/gnome-logo-large.png" -msgstr "Logo=<share>/pixmaps/gnome-logo-large.png" - -#: ../C/gdm.xml:3084(para) -msgid "Image file to display in the logo box. The file must be in an 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 "Файл зображення, що відображається у діалоговому вікні. Файл має бути у форматі, який підтримується gdk-pixbuf та повинен бути доступний для читання користувачу GDM. Якщо файл не вказано, функція показу зображення вимикається. Цей параметр впливає лише на програму привітання на базі GTK+." - -#: ../C/gdm.xml:3095(term) -msgid "ChooserButtonLogo" -msgstr "ChooserButtonLogo" - -#: ../C/gdm.xml:3097(synopsis) -#, no-wrap -msgid "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" -msgstr "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" - -#: ../C/gdm.xml:3098(para) -msgid "Image file to display in the file chooser button in <command>gdmsetup</command>. This key is modified by <command>gdmsetup</command> and should not be manually modified by the user. This only affects the Login Window Preferences (<command>gdmsetup</command>)." -msgstr "" - -#: ../C/gdm.xml:3109(term) -msgid "MinimalUID" -msgstr "MinimalUID" - -#: ../C/gdm.xml:3111(synopsis) -#, no-wrap -msgid "MinimalUID=100" -msgstr "MinimalUID=100" - -#: ../C/gdm.xml:3112(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 <filename>Include</filename>, <filename>Exclude</filename>, and <filename>IncludeAll</filename>." -msgstr "Мінімальній ідентифікатор користувача, який GDM вважає користувачем. Усі користувачі з меншими ідентифікаторами не включаються у переглядач портретів. Також дивіться параметри <filename>Include</filename>, <filename>Exclude</filename>, та <filename>IncludeAll</filename>." - -#: ../C/gdm.xml:3123(term) -msgid "PositionX" -msgstr "PositionX" - -#: ../C/gdm.xml:3125(synopsis) -#, no-wrap -msgid "PositionX=200" -msgstr "PositionX=200" - -#: ../C/gdm.xml:3126(para) -msgid "The horizontal position of the login window of the GTK+ Greeter." -msgstr "Горизонтальна позиція вікна входу стандартної (GTK+) програми привітання." - -#: ../C/gdm.xml:3134(term) -msgid "PositionY" -msgstr "PositionY" - -#: ../C/gdm.xml:3136(synopsis) -#, no-wrap -msgid "PositionY=100" -msgstr "PositionY=100" - -#: ../C/gdm.xml:3137(para) -msgid "The vertical position of the login window of the GTK+ Greeter." -msgstr "Вертикальна позиція вікна входу стандартної (GTK+) програми привітання." - -#: ../C/gdm.xml:3145(term) -msgid "Quiver" -msgstr "Quiver" - -#: ../C/gdm.xml:3147(synopsis) -#, no-wrap -msgid "Quiver=true" -msgstr "Quiver=true" - -#: ../C/gdm.xml:3148(para) -msgid "Controls whether <command>gdmlogin</command> should shake the display when an incorrect username/password is entered. This only affects the GTK+ Greeter." -msgstr "Визначає чи <command>gdmlogin</command> слід трясти екран при вводі неправильного паролю/імені користувач. Це впливає лише на стандартну (GTK+)програму привітання." - -#: ../C/gdm.xml:3158(term) -msgid "DefaultRemoteWelcome" -msgstr "DefaultRemoteWelcome" - -#: ../C/gdm.xml:3160(synopsis) -#, no-wrap -msgid "DefaultRemoteWelcome=true" -msgstr "DefaultRemoteWelcome=true" - -#: ../C/gdm.xml:3161(para) -msgid "If set to true, the value \"Welcome to %n\" is used for the <filename>RemoteWelcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>RemoteWelcome</filename> 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 " має значення true, тоді для параметра <filename>RemoteWelcome</filename> використовується значення \"Welcome to %n\". Це повідомлення виводиться користувачу у перекладі відповідною мовою. Якщо значення параметра false - використовується параметр <filename>RemoteWelcome</filename>. У рядку можуть використовуватись ті ж самі спеціальні символи, що описані у розділі \"Текстовий вузол\" глави \"Привітання з підтримкою тем\". Там пояснюється значення символа \"%n\"." - -#: ../C/gdm.xml:3175(term) -msgid "RemoteWelcome" -msgstr "RemoteWelcome" - -#: ../C/gdm.xml:3177(synopsis) -#, no-wrap -msgid "RemoteWelcome=Welcome to %n" -msgstr "RemoteWelcome=Welcome to %n" - -#: ../C/gdm.xml:3178(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 <filename>Welcome</filename> string. This string can use the same special character sequences as explained in the \"Text Node\" section of the \"Themed Greeter\" chapter. chapter." -msgstr "Визначає текст, який відображається біля значка привітання віддаленого сеансу XDMCP. Тут діють такі самі розширення, як і у рядку <filename>Welcome</filename>. У рядку можуть використовуватись ті ж самі спеціальні символи, що описані у розділі \"Текстовий вузол\" глави \"Привітання з підтримкою тем\"." - -#: ../C/gdm.xml:3191(term) -msgid "RunBackgroundProgramAlways" -msgstr "RunBackgroundProgramAlways" - -#: ../C/gdm.xml:3193(synopsis) -#, no-wrap -msgid "RunBackgroundProgramAlways=false" -msgstr "RunBackgroundProgramAlways=false" - -#: ../C/gdm.xml:3194(para) -msgid "If this is true then the background application is run always, otherwise it is only run when the <filename>BackgroundType</filename> is 0 (None) This only affects the GTK+ Greeter." -msgstr "Якщо має значення true, тоді завжди запускається програма на тлі, у іншому випадку програма запускається лише коли <filename>BackgroundType</filename> має значення 0 (None). Параметр впливає лише на стандартну програму привітання на GTK+." - -#: ../C/gdm.xml:3204(term) -msgid "SetPosition" -msgstr "SetPosition" - -#: ../C/gdm.xml:3206(synopsis) -#, no-wrap -msgid "SetPosition=true" -msgstr "SetPosition=true" - -#: ../C/gdm.xml:3207(para) -msgid "If true the position of the login window of the GTK+ Greeter is determined by <filename>PositionX</filename> / <filename>PositionY</filename>." -msgstr "Якщо має значення true - позиція вікна входу у програмі привітання на GTK+ визначається значеннями <filename>PositionX</filename> / <filename>PositionY</filename>." - -#: ../C/gdm.xml:3216(term) -msgid "ShowGnomeFailsafeSession" -msgstr "ShowGnomeFailsafeSession" - -#: ../C/gdm.xml:3218(synopsis) -#, no-wrap -msgid "ShowGnomeFailsafeSession=true" -msgstr "ShowGnomeFailsafeSession=true" - -#: ../C/gdm.xml:3219(para) -msgid "Should the greeter show the Gnome Failsafe session in th sessions list." -msgstr "Чи відображає програма привітання у списку сеансів аварійний сеанс Gnome." - -#: ../C/gdm.xml:3227(term) -msgid "ShowLastSession" -msgstr "ShowLastSession" - -#: ../C/gdm.xml:3229(synopsis) -#, no-wrap -msgid "ShowLastSession=true" -msgstr "ShowLastSession=true" - -#: ../C/gdm.xml:3230(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 <filename>DefaultSession</filename>) unless then pick something else for this session only. So if this is off, this really circumvents saving of the last session." -msgstr "Чи показувати 'Останній' сеанс у списку сеансів. Якщо цей параметри вимкнений, тоді GDM працює у так званому 'switchdesk' режимі, який відомий користувачам Red Hat. Тобто, користувачі не можуть вибрати останній сеанс, відбувається вхід у типовий сеанс (дивіться <filename>DefaultSession</filename>), доки не буде вибрано інший тип сеансу для цього конкретного сеансу. Тому, якщо цей параметр вимкнено, збереження останнього сеансу не відбувається." - -#: ../C/gdm.xml:3243(term) -msgid "ShowXtermFailsafeSession" -msgstr "ShowXtermFailsafeSession" - -#: ../C/gdm.xml:3245(synopsis) -#, no-wrap -msgid "ShowXtermFailsafeSession=true" -msgstr "ShowXtermFailsafeSession=true" - -#: ../C/gdm.xml:3246(para) -msgid "Should the greeter show the Xterm Failsafe session in the sessions list." -msgstr "Чи відображає програма привітання у списку сеансів аварійний сеанс Xterm." - -#: ../C/gdm.xml:3254(term) -msgid "SoundOnLogin" -msgstr "SoundOnLogin" - -#: ../C/gdm.xml:3256(synopsis) -#, no-wrap -msgid "SoundOnLogin=true" -msgstr "SoundOnLogin=true" - -#: ../C/gdm.xml:3257(para) -msgid "If true, the greeter will play a sound or beep when it is ready for a login. See also the <filename>SoundOnLoginFile</filename> key. Supported since 2.5.90.0." -msgstr "Якщо має значення true, програма привітання подає звуковий сигнал, при готовності до входу у сеанс. Також дивіться ключ <filename>SoundOnLoginFile</filenamіe>. Підтримується з 2.5.90.0." - -#: ../C/gdm.xml:3267(term) -msgid "SoundOnLoginSuccess" -msgstr "SoundOnLoginSuccess" - -#: ../C/gdm.xml:3269(synopsis) -#, no-wrap -msgid "SoundOnLoginSuccess=true" -msgstr "SoundOnLoginSuccess=true" - -#: ../C/gdm.xml:3270(para) -msgid "If true, the greeter will play a sound after a successful login attempt. See also the <filename>SoundOnLoginSuccessFile</filename> key." -msgstr "Якщо має значення true, програма привітання подає звуковий сигнал після успішного входу у сеанс. Також дивіться ключ <filename>SoundOnLoginSuccessFile</filename>." - -#: ../C/gdm.xml:3279(term) -msgid "SoundOnLoginFailure" -msgstr "SoundOnLoginFailure" - -#: ../C/gdm.xml:3281(synopsis) -#, no-wrap -msgid "SoundOnLoginFailure=true" -msgstr "SoundOnLoginFailure=true" - -#: ../C/gdm.xml:3282(para) -msgid "If true, the greeter will play a sound after a failed login attempt. See also the <filename>SoundOnLoginFailureFile</filename> key." -msgstr "Якщо має значення true, програма привітання подає звуковий сигнал після невдалої спроби входу у сеанс. Також дивіться ключ <filename>SoundOnLoginFailureFile</filename>." - -#: ../C/gdm.xml:3291(term) -msgid "SoundOnLoginFile" -msgstr "SoundOnLoginFile" - -#: ../C/gdm.xml:3293(synopsis) -#, no-wrap -msgid "SoundOnLoginFile=/path/to/sound.wav" -msgstr "SoundOnLoginFile=/path/to/sound.wav" - -#: ../C/gdm.xml:3294(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) instead of a beep when the greeter is ready for a login. See also the <filename>SoundOnLogin</filename> key and the <filename>SoundProgram</filename> key. Supported since 2.5.90.0." -msgstr "Файл, який буде відтворюватись при готовності програми привітання до входу у сеанс. Файл відтворюється через певну програму відтворення звуку (типово <filename>/usr/bin/play</filename>). Також дивіться параметри <filename>SoundOnLogin</filename> та <filename>SoundProgram</filename>. Підтримується з 2.5.90.0." - -#: ../C/gdm.xml:3307(term) -msgid "SoundOnLoginSuccessFile" -msgstr "SoundOnLoginSuccessFile" - -#: ../C/gdm.xml:3309(synopsis) -#, no-wrap -msgid "SoundOnLoginSuccessFile=/path/to/sound.wav" -msgstr "SoundOnLoginSuccessFile=/path/to/sound.wav" - -#: ../C/gdm.xml:3310(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a successful login attempt. See also the <filename>SoundOnLoginSuccess</filename> key and the <filename>SoundProgram</filename> key." -msgstr "Файл, який буде відтворюватись після успішного входу у сеанс. Файл відтворюється через певну програму відтворення звуку (типово <filename>/usr/bin/play</filename>). Також дивіться параметри <filename>SoundOnLoginSuccess</filename> та <filename>SoundProgram</filename>." - -#: ../C/gdm.xml:3321(term) -msgid "SoundOnLoginFailureFile" -msgstr "SoundOnLoginFailureFile" - -#: ../C/gdm.xml:3323(synopsis) -#, no-wrap -msgid "SoundOnLoginFailureFile=/path/to/sound.wav" -msgstr "SoundOnLoginFailureFile=/path/to/sound.wav" - -#: ../C/gdm.xml:3324(para) -msgid "The file that will be played using the specified sound application (by default that is <filename>/usr/bin/play</filename>) after a failed login attempt. See also the <filename>SoundOnLoginFailure</filename> key and the <filename>SoundProgram</filename> key." -msgstr "Файл, який буде відтворюватись після невдалої спроби входу у сеанс. Файл відтворюється через певну програму відтворення звуку (типово <filename>/usr/bin/play</filename>). Також дивіться параметри <filename>SoundOnLoginFailure</filename> та <filename>SoundProgram</filename>." - -#: ../C/gdm.xml:3335(term) -msgid "SystemMenu" -msgstr "SystemMenu" - -#: ../C/gdm.xml:3337(synopsis) -#, no-wrap -msgid "SystemMenu=true" -msgstr "SystemMenu=true" - -#: ../C/gdm.xml:3338(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 "Чи вмикати меню Дії (яке ще іноді називають системним меню). Якщо меню вимкнено, тоді не буде доступна одна жодна з дій. Ці дії включають Вимкнути, Перезавантажити, Налаштувати, програма вибору XDMCP та таке інше. Усі ці дії можна вимикати вибірково. Дії Вимкнути, Перезапустити та Призупинити можна вимкнути встановивши порожнє значення у відповідному параметрі. Зауважте, що меню дії відображається при вході з локального терміналу, тому що воно може містити небезпеку, або бути небажаним при вході з віддаленого терміналу, тому не слід турбуватись, що віддалені користувачі матимуть привілеї консольних користувачів." - -#: ../C/gdm.xml:3351(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 "Зауважте, якщо параметри вимкнено, жодна з цих дій не буде доступна, навіть якщо графічна програма привітання помилково відображає їх. Також зауважте, що іноді графічна тема може не відображати усі доступні дії у вигляді кнопок, тоді слід натиснути F10, щоб з'явилось системне меню." - -#: ../C/gdm.xml:3362(term) -msgid "TitleBar" -msgstr "TitleBar" - -#: ../C/gdm.xml:3364(synopsis) -#, no-wrap -msgid "TitleBar=true" -msgstr "TitleBar=true" - -#: ../C/gdm.xml:3365(para) -msgid "Display the title bar in the greeter. This only affects the GTK+ Greeter." -msgstr "Чи відображати заголовок вікна привітання. Впливає лише на програму привітання на GTK+." - -#: ../C/gdm.xml:3373(term) -msgid "Use24Clock" -msgstr "Use24Clock" - -#: ../C/gdm.xml:3375(synopsis) -#, no-wrap -msgid "Use24Clock=auto" -msgstr "Use24Clock=auto" - -#: ../C/gdm.xml:3376(para) -msgid "Select the use of 24 hour clock. Some locales do not support 12 hour format (like Finnish, that is <filename>fi_FI</filename>), and in those locales this setting has no effect at all." -msgstr "Чи використовувати 24-годинний формат годинника. У деяких локалях не підтримується 12-годинний формат (наприклад у Finnish, тобто <filename>fi_FI</filename>). У таких локалях цей параметр на на що не впливає." - -#: ../C/gdm.xml:3382(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 "Можливі значення \"auto\" (типово), \"true\", та \"false\". Якщо має значення \"auto\" або значення відсутнє, формат часу вибирається відповідно до параметрів локалі. Параметри локалі залежать від мови, яка використовується. Таким чином вони змінюються змінною LANGUAGE (розширення GNU), LANG, LC_MESSAGES чи LC_ALL у оточенні запуску GDM. Пріоритет перегляду змінних можна знайти у довіднику з вашої системної бібліотеки C." - -#: ../C/gdm.xml:3397(term) -msgid "UseCirclesInEntry" -msgstr "UseCirclesInEntry" - -#: ../C/gdm.xml:3399(synopsis) -#, no-wrap -msgid "UseCirclesInEntry=false" -msgstr "UseCirclesInEntry=false" - -#: ../C/gdm.xml:3400(para) -msgid "Use circles instead of asterisks in the password entry. This may not work with all fonts however." -msgstr "У полі вводу пароля використовувати кола, замість зірочок. Проте може не підтримуватись в усіх шрифтах." - -#: ../C/gdm.xml:3408(term) -msgid "UseInvisibleInEntry" -msgstr "UseInvisibleInEntry" - -#: ../C/gdm.xml:3410(synopsis) -#, no-wrap -msgid "UseInvisibleInEntry=false" -msgstr "UseInvisibleInEntry=false" - -#: ../C/gdm.xml:3411(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 <filename>UseCirclesInEntry</filename> option." -msgstr "Не показувати візуальний зворотний зв'язок у полі паролю. Це стандартна поведінка у консолі та xdm. Встановлення цього параметра скасовує параметр <filename>UseCirclesInEntry</filename>." - -#: ../C/gdm.xml:3421(term) -msgid "DefaultWelcome" -msgstr "DefaultWelcome" - -#: ../C/gdm.xml:3423(synopsis) -#, no-wrap -msgid "DefaultWelcome=true" -msgstr "DefaultWelcome=true" - -#: ../C/gdm.xml:3424(para) -msgid "If set to true, the value \"Welcome\" is used for the <filename>Welcome</filename>. This value is translated into the appropriate language for the user. If set to false, the <filename>Welcome</filename> setting is used." -msgstr "Якщо має значення true, у якості повідомлення привітання використовується \"Ласкаво просимо\". Це значення перекладається мовою користувача. Якщо поле має значення false, для рядка привітання використовується значення параметра <filename>Welcome</filename>." - -#: ../C/gdm.xml:3434(term) -msgid "Welcome" -msgstr "Welcome" - -#: ../C/gdm.xml:3436(synopsis) -#, no-wrap -msgid "Welcome=Welcome" -msgstr "Welcome=Welcome" - -#: ../C/gdm.xml:3437(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:3446(para) -msgid "%d — display's hostname" -msgstr "%d — назва вузла дисплею" - -#: ../C/gdm.xml:3450(para) -msgid "%h — Fully qualified hostname" -msgstr "%h — повна назва домену" - -#: ../C/gdm.xml:3454(para) -msgid "%m — machine (processor type)" -msgstr "%m — машина (тиb процесора)" - -#: ../C/gdm.xml:3458(para) -msgid "%n — Nodename (i.e. hostname without .domain)" -msgstr "%n — назва вузла (тобто, назва вузла без .domain)" - -#: ../C/gdm.xml:3462(para) -msgid "%r — release (OS version)" -msgstr "%r — випуск (версія OS)" - -#: ../C/gdm.xml:3466(para) -msgid "%s — sysname (i.e. OS)" -msgstr "%s — назва системи (тобто ОС)" - -#: ../C/gdm.xml:3470(para) -msgid "This string is only used for local logins. For remote XDMCP logins we use <filename>RemoteWelcome</filename>." -msgstr "Рядок використовується для локальної консолі. Для віддалених сеансів XDMCP використовується <filename>RemoteWelcome</filename>." - -#: ../C/gdm.xml:3475(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:3485(term) -msgid "XineramaScreen" -msgstr "XineramaScreen" - -#: ../C/gdm.xml:3487(synopsis) -#, no-wrap -msgid "XineramaScreen=0" -msgstr "XineramaScreen=0" - -#: ../C/gdm.xml:3488(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 "Якщо активне розширення Xinerama, вікно входу виводиться у центрі фізичного екрану (0 - для першого екрану, 1 - для другого...)." - -#: ../C/gdm.xml:3499(title) -msgid "XDCMP Chooser Options" -msgstr "Параметри селектора XDCMP" - -#: ../C/gdm.xml:3502(title) -msgid "[chooser]" -msgstr "[chooser]" - -#: ../C/gdm.xml:3505(term) -msgid "AllowAdd" -msgstr "AllowAdd" - -#: ../C/gdm.xml:3507(synopsis) -#, no-wrap -msgid "AllowAdd=true" -msgstr "AllowAdd=true" - -#: ../C/gdm.xml:3508(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 "Якщо має значення true, користувачу дозволено додавати довільні вузли до селектора. Таким чином користувач може з'єднатись з будь-яким вузлом, який відповідає на запити XDMCP від селектора." - -#: ../C/gdm.xml:3517(term) -msgid "Broadcast" -msgstr "Broadcast" - -#: ../C/gdm.xml:3519(synopsis) -#, no-wrap -msgid "Broadcast=true" -msgstr "Broadcast=true" - -#: ../C/gdm.xml:3520(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 <filename>Hosts</filename> key." -msgstr "Якщо має значення true, селектор створює широкомовні запити до локальної мережі та прослуховує відповіді. Таким чином селектор завжди показує доступні у мережі менеджери сеансів. Якщо слід додати деякі вузли, які не є локальними для цієї мережі, або не бажаєте використовувати широкомовні запити, можете вказати вузли у параметрі <filename>Hosts</filename>." - -#: ../C/gdm.xml:3532(term) -msgid "Multicast" -msgstr "Multicast" - -#: ../C/gdm.xml:3534(synopsis) -#, no-wrap -msgid "Multicast=true" -msgstr "Multicast=true" - -#: ../C/gdm.xml:3535(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 <filename>Hosts </filename> key. The host will respond if it is listening to XDMCP requests and IPv6 is enabled there." -msgstr "Якщо має значення true та увімкнено IPv6, селектор буде надсилати multicast-запити у локальну мережу та слухати відповідь від вузлів, які входять у multicast-групу. Якщо ви не бажаєте надсилати групові запити. можна вказати адресу IPv6 у параметрі <filename>Hosts </filename>. Вузол відповідатиме, якщо він прослуховує запити XDMCP та на ньому увімкнено підтримку IPv6." - -#: ../C/gdm.xml:3547(term) -msgid "MulticastAddr" -msgstr "MulticastAddr" - -#: ../C/gdm.xml:3549(synopsis) -#, no-wrap -msgid "MulticastAddr=ff02::1" -msgstr "MulticastAddr=ff02::1" - -#: ../C/gdm.xml:3550(para) -msgid "This is the Link-local Multicast address and is hardcoded here." -msgstr "У цьому параметрі вказується Link-local адреса Multicast." - -#: ../C/gdm.xml:3557(term) -msgid "DefaultHostImage" -msgstr "DefaultHostImage" - -#: ../C/gdm.xml:3559(synopsis) -#, no-wrap -msgid "DefaultHostImage=<share>/pixmaps/nohost.png" -msgstr "DefaultHostImage=<share>/pixmaps/nohost.png" - -#: ../C/gdm.xml:3560(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 an gdk-pixbuf supported format and it must be readable for the GDM user." -msgstr "Назва файлу типового значка. Це зображення відображатиметься, якщо для вказаного вузла не вказано власний значок. Файл повинен мати формат, який підтримується gdk-pixbuf, та користувач GDM повинен мати доступ на читання до нього." - -#: ../C/gdm.xml:3570(term) -msgid "HostImageDir" -msgstr "HostImageDir" - -#: ../C/gdm.xml:3572(synopsis) -#, no-wrap -msgid "HostImageDir=<share>/hosts" -msgstr "HostImageDir=<share>/hosts" - -#: ../C/gdm.xml:3573(para) -msgid "Repository for host icon files. The sysadmin can place icons for remote hosts here and they will appear in <filename>gdmchooser</filename>." -msgstr "Каталог для файлів значків до комп'ютерів. Системний адміністратор може покласти сюди значки до віддалених вузлів, і вони будуть відображатись у <filename>gdmchooser</filename>." - -#: ../C/gdm.xml:3579(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 "Назва файлу має відповідати повній доменній назві (FQDN) вузла. Значки мають зберігатись у форматі, який підтримується gdk-pixbuf та мають бути доступні для читання користувачу GDM." - -#: ../C/gdm.xml:3589(term) -msgid "Hosts" -msgstr "Hosts" - -#: ../C/gdm.xml:3591(synopsis) -#, no-wrap -msgid "Hosts=host1,host2" -msgstr "Hosts=host1,host2" - -#: ../C/gdm.xml:3592(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 <filename>Broadcast</filename> 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 "Вузли які мають бути у списку програми вибору вузлів. Вузли відображаються у списку лише якщо вони відповідають на запити. Для цього надсилаються широкомовні запити (якщо встановлено <filename>Broadcast</filename>), тому не слід вказувати вузли локальної мережі. Це корисно, якщо конфігурація мережі не дозволяє дістатись до усіх вузлів пакетами широкомовних запитів." - -#: ../C/gdm.xml:3604(term) -msgid "ScanTime" -msgstr "ScanTime" - -#: ../C/gdm.xml:3606(synopsis) -#, no-wrap -msgid "ScanTime=4" -msgstr "ScanTime=4" - -#: ../C/gdm.xml:3607(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 "Визначає скільки секунд програма вибору вузлів буде очікувати відповідь на BROADCAST_QUERY. Насправді це лише час очікування відповіді. Але вузли будуть додаватись, якщо від них буде отримано відповідь після цього періоду." - -#: ../C/gdm.xml:3619(title) -msgid "Debug Configuration" -msgstr "Налаштовування налагодження" - -#: ../C/gdm.xml:3622(title) -msgid "[debug]" -msgstr "[debug]" - -#: ../C/gdm.xml:3628(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:3638(term) -msgid "Gestures" -msgstr "Жести" - -#: ../C/gdm.xml:3640(synopsis) -#, no-wrap -msgid "Gestures=false" -msgstr "Gestures=false" - -#: ../C/gdm.xml:3641(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:3654(title) -msgid "X Server Definitions" -msgstr "X Server Definitions" - -#: ../C/gdm.xml:3656(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 <filename>Standard</filename> is required. If you do not specify this server, GDM will assume default values for a 'Standard' server and the path given by <filename>daemon/StandardXServer</filename>. <filename>Standard</filename> is used as the default, in situations when no other server has been defined." -msgstr "Щоб встановити X-сервери, слід вказати GDM інформацію про встановлені X-сервери. Можна створити довільну кількість різних визначень, кожна повинна мати унікальну назву. Назва <filename>Standard</filename> є обов'язковою. Якщо ви не вказали цей сервер, GDM беруться типові значення сервера 'Standard' та шлях вказаний у <filename>daemon/StandardXServer</filename>. Якщо не визначені інші сервери, використовується <filename>Standard</filename>." - -#: ../C/gdm.xml:3667(para) -msgid "Servers are defined by sections named <filename>server-</filename> 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, <filename>server-</filename> sections in the <filename><etc>/gdm/custom.conf</filename> file override values in the <filename><share>/gdm/defaults.conf</filename> file. In other words, if a <filename>server-Standard</filename> section is defined in <filename><etc>/gdm/custom.conf</filename>, then that will be used and the section in the <filename><share>/gdm/defaults.conf</filename> file will be ignored." -msgstr "" - -#: ../C/gdm.xml:3685(title) -msgid "[server-Standard]" -msgstr "[server-Standard]" - -#: ../C/gdm.xml:3688(term) -msgid "name" -msgstr "name" - -#: ../C/gdm.xml:3690(synopsis) -#, no-wrap -msgid "name=Standard server" -msgstr "name=Standard server" - -#: ../C/gdm.xml:3691(para) -msgid "The name that will be displayed to the user." -msgstr "Назва, яка відображається користувачу." - -#: ../C/gdm.xml:3698(term) -msgid "command" -msgstr "command" - -#: ../C/gdm.xml:3700(synopsis) -#, no-wrap -msgid "command=/path/to/X" -msgstr "command=/шлях/до/X" - -#: ../C/gdm.xml:3701(para) -msgid "The command to execute, with full path to the binary of the X server, and any extra arguments needed." -msgstr "Повний шлях та назва виконуваного файлу X-сервера та інші потрібні аргументи команди." - -#: ../C/gdm.xml:3709(term) -msgid "flexible" -msgstr "flexible" - -#: ../C/gdm.xml:3711(synopsis) -#, no-wrap -msgid "flexible=true" -msgstr "flexible=true" - -#: ../C/gdm.xml:3712(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:3720(term) -msgid "handled" -msgstr "handled" - -#: ../C/gdm.xml:3722(synopsis) -#, no-wrap -msgid "handled=true" -msgstr "handled=true" - -#: ../C/gdm.xml:3723(para) -msgid "Indicates that GDM should run the login window on this server and allow a user to log in. If set to false, then GDM will just run this server and wait for it to terminate. This can be useful to run an X terminal using GDM. When this is done you should normally also add <filename>-terminate</filename> to the command line of the server to make the server terminate after each session. Otherwise the control of the slave will never come back to GDM and, for example, soft restarts won't work. This is because GDM assumes there is a login in progress for the entire time this server is active." -msgstr "Означає, що GDM має виводити вікно запрошення до входу на цьому сервері. Якщо значення false, тоді GDM просто запускає цей сервер та очікує завершення. Це корисно для запуску X-терміналів через GDM. Також звичайно можна додати до командного рядка сервера <filename>-terminate</filename>, щоб сервер завершувався після завершення кожного сеансу. У іншому випадку керування над породженим процесом ніколи не повернеться до GDM та, наприклад, не працюватиме м'який перезапуск, бо GDM вважатиме, що сеанс триває весь час активності сервера." - -#: ../C/gdm.xml:3739(term) -msgid "chooser" -msgstr "chooser" - -#: ../C/gdm.xml:3741(synopsis) -#, no-wrap -msgid "chooser=false" -msgstr "chooser=false" - -#: ../C/gdm.xml:3742(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 "Означає, що GDM замість вікна входу має запустити селектор вузлів та дозволити користувачу обрати сервер на який увійти." - -#: ../C/gdm.xml:3753(title) -msgid "Local Static X Display Configuration" -msgstr "Конфігурація локального статичного X-сервера" - -#: ../C/gdm.xml:3755(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 <filename>[servers]</filename> section corresponds to the display number to be managed. Normally there is only one key, which is the key <filename>0</filename>, which corresponds to the display <filename>:0</filename>." -msgstr "Статичні X-сервери - це сервери, які завжди керуються GDM. Наприклад, якщо сервер будь-коли завершується, він перезапускається. Можна мати будь-яку кількість статичних серверів, хоча зазвичай кожен з них підключений до реального дисплею . Наприклад, якщо в комп'ютері є два дисплеї (скажімо дисплей \":0\" та дисплей \":1\"), тоді у цьому розділі можна вказати, що для кожного екрану має використовуватись окремий екран входу. Кожен ключ у розділі <filename>[servers]</filename> відповідає номеру дисплея, на якому запускається сервер. Наприклад, зазвичай є лише один ключ, це <filename>0</filename>, який відповідає дисплею <filename>:0</filename>." - -#: ../C/gdm.xml:3770(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 <filename>[servers]</filename> section in the <filename><etc>/gdm/custom.conf</filename> file overrides values in the <filename><share>/gdm/defaults.conf</filename> file." -msgstr "" - -#: ../C/gdm.xml:3781(title) -msgid "[servers]" -msgstr "[servers]" - -#: ../C/gdm.xml:3784(term) -msgid "<display number>" -msgstr "<номер дисплею>" - -#: ../C/gdm.xml:3786(synopsis) -#, no-wrap -msgid "0=Standard" -msgstr "0=Standard" - -#: ../C/gdm.xml:3787(para) -#, fuzzy -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 "Розділ керування локальними X-серверами. У кожному рядку вказується номер локального дисплею та команда запуску X-сервера. " - -#: ../C/gdm.xml:3793(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 <filename><etc>/gdm/custom.conf</filename> to turn off a display that is defined in the <filename><share>/gdm/defaults.conf</filename> file." -msgstr "" - -#: ../C/gdm.xml:3807(para) -#, fuzzy -msgid "GDM will splice \"<filename>-auth <ServAuthDir>/:n.Xauth :n</filename>\", where n is the display number. Inside the command line before all other arguments before running the X server." -msgstr "В середину командного рядка перед іншими аргументами GDM додасть \"<filename>-auth <ServAuthDir>/:n.Xauth :n</filename>\", де n - номер дисплею." - -#: ../C/gdm.xml:3814(para) -#, fuzzy -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 <filename>VTAllocation</filename> key is set." -msgstr "На деяких системах потрібно, щоб GDM було відомо на яких віртуальних консолях запущено X-сервери. У цьому випадку, (якщо запущено XFree86) додайте до командного рядка \"vt7\", щоб запускати сервер на віртуальній консолі 7. Проте на Linux та FreeBSD це, зазвичай, виконується автоматично якщо встановлено ключ <filename>VTAllocation</filename>." - -#: ../C/gdm.xml:3823(para) -#, fuzzy -msgid "Normally you do not need to add a <filename>-nolisten tcp</filename> flag as this is added automatically for local X servers when the <filename>DisallowTCP</filename> option is set." -msgstr "Зазвичай, не слід додавати ключ <filename>-nolisten tcp</filename>. Якщо встановлено параметр <filename>DisallowTCP</filename>, це робиться автоматично для локальних серверів." - -#: ../C/gdm.xml:3833(term) -msgid "priority" -msgstr "priority" - -#: ../C/gdm.xml:3835(synopsis) -#, no-wrap -msgid "priority=0" -msgstr "priority=0" - -#: ../C/gdm.xml:3836(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:3852(title) -msgid "Per User Configuration" -msgstr "Параметри специфічні для користувача" - -#: ../C/gdm.xml:3854(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 <filename>UserMaxFile</filename> 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:3868(para) -#, fuzzy -msgid "First there is the <filename>~/.dmrc</filename> file. In theory this file should be shared between GDM and KDM, so users only have to configure things once. This is a standard <filename>.ini</filename> style configuration file. It has one section called <filename>[Desktop]</filename> which has two keys: <filename>Session</filename> and <filename>Language</filename>." -msgstr "Є деякі специфічні для користувача параметри, які контролюють поведінку GDM. По-перше, це файл <filename>~/.dmrc</filename>. Теоретично цей файл має бути спільним між GDM та KDM, тому користувачі налаштовують його один раз. Це файл у форматі <filename>.ini</filename>. У цьому може міститись один розділ <filename>[Desktop]</filename> та два ключі. У ключі <filename>Session</filename> вказуються базова назва <filename>.desktop</filename>-файлу сеансу, який користувач хоче використовувати (без розширення <filename>.desktop</filename>).У ключі <filename>Language</filename> вказується мова, яку бажає використовувати користувач. Якщо якийсь з цих ключів відсутній, використовується типове для системи значення. Зазвичай, файл має виглядати наступним чином:" - -#: ../C/gdm.xml:3877(para) -#, fuzzy -msgid "The <filename>Session</filename> key specifies the basename of the session <filename>.desktop</filename> file that the user wishes to normally use (without the <filename>.desktop</filename> extension, in other words). The <filename>Language</filename> key specifies the language that the user wishes to use by default. If either of these keys is missing, the system default is used. The file would normally look as follows:" -msgstr "Є деякі специфічні для користувача параметри, які контролюють поведінку GDM. По-перше, це файл <filename>~/.dmrc</filename>. Теоретично цей файл має бути спільним між GDM та KDM, тому користувачі налаштовують його один раз. Це файл у форматі <filename>.ini</filename>. У цьому може міститись один розділ <filename>[Desktop]</filename> та два ключі. У ключі <filename>Session</filename> вказуються базова назва <filename>.desktop</filename>-файлу сеансу, який користувач хоче використовувати (без розширення <filename>.desktop</filename>).У ключі <filename>Language</filename> вказується мова, яку бажає використовувати користувач. Якщо якийсь з цих ключів відсутній, використовується типове для системи значення. Зазвичай, файл має виглядати наступним чином:" - -#: ../C/gdm.xml:3887(screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"[Desktop]\n" -"Session=gnome\n" -"Language=cs_CZ.UTF-8\n" -msgstr "" -"\n" -"[Desktop]\n" -"Session=gnome\n" -"Language=uk_UA.UTF-8\n" -" " - -#: ../C/gdm.xml:3893(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:3899(para) -msgid "If the GDM Face Browser is turned, then the file <filename>$HOME/.face</filename> 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 <filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> values defined in the GDM configuration or it will be ignored. Users can run the <command>gdmphotosetup</command> program to specify a face image and it will copy the file to the <filename>$HOME/.face</filename> location and scale it so its longest dimension is not larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> values. <command>gdmphotosetup</command> takes care to not change the aspect ratio of the image." -msgstr "" - -#: ../C/gdm.xml:3914(para) -#, fuzzy -msgid "Face images can also be placed in the global face directory, which is specified by the <filename>GlobalFaceDir</filename> configuration option ( normally <filename><share>/pixmaps/faces/</filename>) and the filename should be the name of the user, optionally with a <filename>.png</filename>, <filename>.jpg</filename>, etc. appended." -msgstr "Портрети можна зберігати у глобальній теці портретів, зазвичай це <filename><share>/pixmaps/faces/</filename> (значення змінюється у параметрі <filename>GlobalFaceDir</filename>). Файл повинен мати назву як назва користувача, можливо з додаванням <filename>.png</filename>." - -#: ../C/gdm.xml:3925(title) -msgid "Controlling GDM" -msgstr "Керування сервером GDM" - -#: ../C/gdm.xml:3927(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 "Ви можете керувати поведінкою запущеної служби GDM. Можна або давати певні команди, або спілкуватися з GDM через unix-сокет чи протокол FIFO." - -#: ../C/gdm.xml:3934(title) -msgid "Commands" -msgstr "Команди" - -#: ../C/gdm.xml:3936(para) -#, fuzzy -msgid "To stop GDM, you can either send the TERM signal to the main daemon or run the <command>gdm-stop</command> command which is in the <filename><sbin>/</filename> directory. To restart GDM, you can either send the HUP signal to the main daemon or run the <command>gdm-restart</command> command which is also in the <filename><sbin>/</filename> 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 <command>gdm-safe-restart</command> command which is in the <filename><sbin>/</filename> directory as well." -msgstr "Щоб зупинити GDM, ви можете або надіслати сигнал TERM головному процесу служби або виконати команду <filename>gdm-stop</filename> з каталогу <filename><sbin>/</filename>. Щоб перезапустити GDM, можна або надіслати сигнал HUP головному процесу служби або виконати команду <filename>gdm-restart</filename> з каталогу <filename><sbin>/</filename>. Щоб перезапустити GDM але після завершення користувачами усіх сеансів, можна надіслати головному процесу служби сигнал USR1 або виконати <filename>gdm-safe-restart</filename> з каталогу <filename><sbin>/</filename>." - -#: ../C/gdm.xml:3949(para) -msgid "The <command>gdmflexiserver</command> 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 <command>gdmflexiserver</command> 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 <command>gdmflexiserver --help</command> to get a listing of possible options." -msgstr "" - -#: ../C/gdm.xml:3965(title) -msgid "The FIFO protocol" -msgstr "Протокол роботи з FIFO" - -#: ../C/gdm.xml:3967(para) -msgid "GDM also provides a FIFO called <filename>.gdmfifo</filename> in the <filename>ServAuthDir</filename> directory (usually <filename><var>/gdm/.gdmfifo</filename>). 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 "GDM також має канал FIFO з назвою <filename>.gdmfifo</filename> у каталозі <filename>ServAuthDir</filename> (зазвичай <filename><var>/gdm/.gdmfifo</filename>). Користуватись цим протоколом може лише root, і він здебільшого використовується для внутрішнього обміну GDM. Це дуже простий протокол. Ви надсилаєте команди через echo по одній команді на рядок. Він може використовуватись, щоб змусити GDM виконати перезавантаження, призупинення комп'ютера чи перезапустити усі X-сервери одразу коли буде можливість (це корисно для програми налаштовування X-сервера)." - -#: ../C/gdm.xml:3978(para) -msgid "Full and up to date documentation of the commands and their use is contained in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look for the defines starting with <filename>GDM_SOP_</filename>. The commands which require the pid of the slave as an argument are the ones that are really used for internal communication of the slave with the master and should not be used." -msgstr "Повна та оновлена документація з команд та їх використання міститься у програмному коді GDM у файлі <filename>daemon/gdm.h</filename>. Шукайте визначення, що починаються з <filename>GDM_SOP_</filename>. Команди, яким у аргументі слід вказувати pid дочірнього процесу, - це команди які справді використовуються для внутрішнього зв'язку дочірнього процесу з головним процесом. Такі команди не слід використовувати." - -#: ../C/gdm.xml:3990(title) -msgid "Socket Protocol" -msgstr "Протокол роботи з сокетом" - -#: ../C/gdm.xml:3992(para) -#, fuzzy -msgid "GDM provides a unix domain socket for communication at <filename>/tmp/.gdm_socket</filename>. 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 <command>gdmflexiserver</command> command uses this protocol, for example, to launch flexible (on-demand) displays." -msgstr "GDM має unix-сокет для зв'язку за шляхом <filename>/tmp/.gdm_socket</filename>. З його допомогою ви можете перевіряти чи запущений GDM, версію служби, поточні запущені сервери та зареєстрованих на них користувачів, та віртуальні термінали усіх входів через консоль, якщо ваша операційна система це підтримує. Також через цей протокол, можна запитати запуск нових гнучких серверів, але це краще робити командою <filename>gdmflexiserver</filename>." - -#: ../C/gdm.xml:4002(para) -msgid "gdmflexiserver accepts the following commands with the --command option:" -msgstr "gdmflexiserver приймає наступні команди у командному рядку --command:" - -#: ../C/gdm.xml:4007(screen) -#, no-wrap -msgid "" -"\n" -"ADD_DYNAMIC_DISPLAY\n" -"ALL_SERVERS\n" -"ATTACHED_SERVERS\n" -"AUTH_LOCAL\n" -"CLOSE\n" -"FLEXI_XNEST\n" -"FLEXI_XSERVER\n" -"GET_CONFIG\n" -"GET_CONFIG_FILE\n" -"GET_SERVER_LIST\n" -"GET_SERVER_DETAILS\n" -"GREETERPIDS\n" -"QUERY_LOGOUT_ACTION\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 "" -"\n" -"ADD_DYNAMIC_DISPLAY\n" -"ALL_SERVERS\n" -"ATTACHED_SERVERS\n" -"AUTH_LOCAL\n" -"CLOSE\n" -"FLEXI_XNEST\n" -"FLEXI_XSERVER\n" -"GET_CONFIG\n" -"GET_CONFIG_FILE\n" -"GET_SERVER_LIST\n" -"GET_SERVER_DETAILS\n" -"GREETERPIDS\n" -"QUERY_LOGOUT_ACTION\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" - -#: ../C/gdm.xml:4032(para) -msgid "These are described in detail below, including required arguments, response format, and return codes." -msgstr "Вони докладніше описані нижче, включено з аргументами, форматом відповідей, та кодами результату." - -#: ../C/gdm.xml:4038(title) -msgid "ADD_DYNAMIC_DISPLAY" -msgstr "ADD_DYNAMIC_DISPLAY" - -#: ../C/gdm.xml:4039(screen) -#, fuzzy, 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 "" -"\n" -"ADD_DYNAMIC_DISPLAY: створює новий гнучкий X-сервер, який запускається\n" -" на вказаному дисплеї залишаючи його у стані DISPLAY_CONFIG.\n" -"Підтримується з: 2.8.0.0\n" -"Аргументи: <дисплей для запуску на >=<сервер>\n" -" Де <сервер> - або конфігурація з назвою у gdm.conf або\n" -" символьна назва команди.\n" -"Відповіді:\n" -" OK <дисплей>\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 2 = Існуючий дисплей\n" -" 3 = Немає рядка сервера\n" -" 4 = помилка запуску дисплею\n" -" 100 = Немає аутентифікації\n" -" 200 = Динамічні дисплеї не дозволені\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4061(title) -msgid "ALL_SERVERS" -msgstr "ALL_SERVERS" - -#: ../C/gdm.xml:4062(screen) -#, fuzzy, 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 "" -"\n" -"ALL_SERVERS: Список усіх серверів, включаючи консольні, віддалені, xnest.\n" -" Це може бути корисно, наприклад, щоб перевірити чи ваш сервер\n" -" керується службою gdm, шляхом пошуку його у списку.\n" -" Цей запит подібний до команди 'w', але для графічних сеансів.\n" -"Підтримується з: 2.4.2.96\n" -"Аргументи: Немає\n" -"Відповідь:\n" -" OK <сервер>;<сервер>;...\n" -"\n" -" <сервер> - <дисплей>,<користувач, що увійшов>\n" -"\n" -" <користувач, що увійшов> може бути порожнім, якщо ніхто досі не увійшов,\n" -"\n" -" ERROR <код помилки> <опис помилки англійської>\n" -" 0 = Не реалізовано\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4085(title) -msgid "ATTACHED_SERVERS" -msgstr "ATTACHED_SERVERS" - -#: ../C/gdm.xml:4086(screen) -#, fuzzy, 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 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" -" 1 = Not implemented\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -msgstr "" -"\n" -"ATTACHED_SERVERS: Список усіх приєднаних серверів. Не включає у список XDMCP та xnest\n" -" не-приєднані сервери\n" -"Підтримується з: 2.2.4.0\n" -"Примітка: Ця команда використовується замість CONSOLE_SERVERS, яка досі розпізнається для\n" -" зворотної сумісності. Не обов'язковий аргумент шаблон підтримується\n" -" з версії 2.8.0.0.\n" -"Аргументи: <шаблон> (не обов'язковий)\n" -" Без аргументів, повертається список усіх приєднаних дисплеїв. Необов'язковий\n" -" <шаблон> - це рядок, який може містити символи '*', '?', та\n" -" '[]'. Повертається список дисплеїв, які відповідають шаблону.\n" -"Відповідь:\n" -" OK <сервер>;<сервер>;...\n" -"\n" -" <сервер> - це <дисплей>,<користувач, що увійшов>,<vt або дисплей xnest>\n" -"\n" -" <користувач, що увійшов> може бути порожнім, якщо ніхто досі не увійшов,\n" -" а <vt> може бути -1, якщо термінал невідомий чи не підтримується\n" -" (наприклад, не-Linux термінал). Якщо дисплей є дисплеєм\n" -" xnest та є консольним (тобто, це xnest у іншому консольному дисплеї)\n" -" він включається у список замість vt, батьківський дисплей включається у список.\n" -" у стандартному вигляді.\n" -"\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 1 = Не реалізовано\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4118(title) -msgid "AUTH_LOCAL" -msgstr "AUTH_LOCAL" - -#: ../C/gdm.xml:4119(screen) -#, no-wrap -msgid "" -"\n" -"AUTH_LOCAL: Setup this connection as authenticated for\n" -" FLEXI_SERVER. Because all full blown (non-Xnest)\n" -" displays can be started only from users logged in\n" -" locally, and here GDM assumes only users logged\n" -" in from GDM. They must pass the xauth\n" -" MIT-MAGIC-COOKIE-1 that they were passed before\n" -" 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 "" -"\n" -"AUTH_LOCAL: Автентифікація з'єднання для FLEXI_SERVER\n" -" оскільки усі повноцінні (не-Xnest)\n" -" сервери можуть запускати лише користувачі які увійшли\n" -" локально, тому тут GDM допускає лише користувачів, які\n" -" увійшли з GDM. Вони мають пройти xauth\n" -" MIT-MAGIC-COOKIE-1, які вони отримали перед автентифікацією\n" -" з'єднання.Примітка: Команда AUTH LOCAL має обов'язковий параметр\n" -" --authenticate, хоча він поки-що використовується\n" -" лише для FLEXI XSERVER.\n" -"Примітка: З версії 2.6.0.6 також можна використовувати глобальний\n" -" <ServAuthDir>/.cookie, що працює для усіх типів\n" -" автентифікації за винятком SET_LOGOUT_ACTION та\n" -" QUERY_LOGOUT_ACTION і SET_SAFE_LOGOUT_ACTION\n" -" коли вимагається вхід на дисплей.\n" -"Підтримується з: 2.2.4.0\n" -"Аргументи: <xauth cookie>\n" -" <xauth cookie> у шістнадцятковому форматі без префікса 0x\n" -"Відповідь:\n" -" OK\n" -" ERROR <номер помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 100 = Немає автентифікації\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" - -#: ../C/gdm.xml:4149(title) -msgid "CLOSE" -msgstr "CLOSE" - -#: ../C/gdm.xml:4150(screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"CLOSE: Close sockets connection\n" -"Supported since: 2.2.4.0\n" -"Arguments: None\n" -"Answers: None\n" -msgstr "" -"\n" -"CLOSE Відповіді: Немає\n" -"Підтримується з: 2.2.4.0\n" -" " - -#: ../C/gdm.xml:4159(title) -msgid "FLEXI_XNEST" -msgstr "FLEXI_XNEST" - -#: ../C/gdm.xml:4160(screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"FLEXI_XNEXT: Start a new flexible Xnest 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 Xnest using the XAUTHORITY file\n" -" supplied and as the uid same as the owner of\n" -" that file (and same as you supply). You must\n" -" also supply the cookie as the third argument\n" -" for this display, to prove that you indeed are\n" -" this user. Also this file must be readable\n" -" ONLY by this user, that is have a mode of 0600.\n" -" If this all is not met, 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 "" -"\n" -"FLEXI_XNEXT: Запустити новий гнучкий сервер Xnest\n" -"Примітка: Підтримується стара версія з 2.2.4.0, до\n" -" 2.2.4.2, але з 2.3.90.4 слід передавати 4\n" -" аргументи, або буде отримано помилку з кодом 100\n" -" Xnest запуститься з використанням переданого файлу XAUTHORITY\n" -" та з uid таким самим як і у власника цього файлу\n" -" (такий самий як у переданий вами). У третьому аргументі\n" -" слід також передати cookie для цього дисплею,\n" -" щоб довести, що ви той самий користувач.\n" -" Цей файл має бути доступний для читання ЛИШЕ\n" -" для цього користувача, тобто мати режим 0600.\n" -" Якщо ці аргументи не вказані, повертається помилка з кодом 100.\n" -"Примітка: cookie має бути MIT-MAGIC-COOKIE-1,\n" -" перший GDM може знайти у файлі XAUTHORITY\n" -" для цього дисплею. Якщо він вами не використовується,\n" -" спочатку слід створити його. cookie\n" -" має бути у шістнадцятковому представленні.\n" -"Підтримується з: 2.3.90.4\n" -"Аргументи: <дисплей, на якому запускати> <uid запитаного користувача>\n" -" <xauth cookie для дисплею> <файл xauth>\n" -"Відповідь:\n" -" OK <дисплей>\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 1 = Більше немає гнучких серверів\n" -" 2 = Помилки запуску\n" -" 3 = помилка системи X\n" -" 4 = система X надто зайнята\n" -" 5 = немає зв'язку з Xnest\n" -" 6 = Відсутній виконуваний файл сервера\n" -" 100 = Немає автентифікації\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4198(title) -msgid "FLEXI_XSERVER" -msgstr "FLEXI_XSERVER" - -#: ../C/gdm.xml:4199(screen) -#, fuzzy, 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 "" -"\n" -"FLEXI_XSERVER: запустити новий гнучкий X-сервер\n" -"Підтримуються лише при з'єднанні яке пройшло AUTH_LOCAL\n" -"Підтримується з: 2.2.4.0\n" -"Аргументи: <ти x-сервера>\n" -" Якщо не вказано аргументи, запускається звичайний x-сервер\n" -"Відповідь:\n" -" OK <display>\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 1 = Більше нема є гнучких серверів\n" -" 2 = Помилка запуску\n" -" 3 = збій системи X\n" -" 4 = система X надто зайнята\n" -" 6 = Немає виконуваного файлу сервера\n" -" 100 = Немає автентифікації\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4221(title) -msgid "GET_CONFIG" -msgstr "GET_CONFIG" - -#: ../C/gdm.xml:4222(screen) -#, fuzzy, 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.h is supported. Starting with version 2.13.0.2\n" -" translated keys (such as \"greeter/GdmWelcome[cs]\" are\n" -" supported via GET_CONFIG. Also starting with version\n" -" 2.13.0.2 it is no longer necessary to include the\n" -" default value (i.e. you can use key \"greeter/IncludeAll\"\n" -" instead of having to use \"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 "" -"\n" -"GET_CONFIG: Отримання значення конфігурації за ключем. Використовується\n" -" для отримання іншими програмами інформації про конфігурацію від\n" -" GDM. Підтримується будь-який ключ GDM_KEY_* у gdm.h.\n" -"Підтримується з: 2.6.0.9\n" -"Аргументи: <ключ>\n" -"Ключі:\n" -" OK <значення>\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 50 = Ключ не підтримується\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4245(title) -msgid "GET_CONFIG_FILE" -msgstr "GET_CONFIG_FILE" - -#: ../C/gdm.xml:4246(screen) -#, fuzzy, 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 "" -"\n" -"GET_CONFIG_FILE: Отримати розташування конфігураційного файлу,\n" -" який використовується службою.\n" -"Підтримується з: 2.8.0.2\n" -"Аргументи: Немає\n" -"Відповідь:\n" -" OK <повний шлях до конфігураційного файлу GDM>\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4263(title) -msgid "GET_SERVER_DETAILS" -msgstr "GET_SERVER_DETAILS" - -#: ../C/gdm.xml:4264(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 "" -"\n" -"GET_SERVER_DETAILS: Отримати від сервера інформацію про вказаний сервер.\n" -"Підтримується з: 2.13.0.4\n" -"Аргументи: <server> <key>\n" -" Значення ключів:\n" -" NAME - повернути назву сервера\n" -" COMMAND - повернути команду сервера\n" -" FLEXIBLE - Повернути \"true\" якщо сервер гнучкий,\"\n" -" інакше \"false\\n" -" CHOOSABLE - Повернути \"true\" якщо choosable,\n" -" інакше \"false\"\n" -" HANDLED - Повернути \"true\" якщо handled,\n" -" інакше \"false\"\n" -" CHOOSER - Повернути \"true\" якщо chooser,\n" -" інакше \"false\"\n" -" PRIORITY - Повернути пріоритет процесу\n" -"Відповідь:\n" -" OK <значення>\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 1 = Сервер не існує\n" -" 2 = Ключ недійсний\n" -" 50 = Непідтримуваний ключ\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" - -#: ../C/gdm.xml:4293(title) -msgid "GET_SERVER_LIST" -msgstr "GET_SERVER_LIST" - -#: ../C/gdm.xml:4294(screen) -#, fuzzy, 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" -" 50 = Unsupported key\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -msgstr "" -"\n" -"GET_CONFIG_FILE: Отримати розташування конфігураційного файлу,\n" -" який використовується службою.\n" -"Підтримується з: 2.8.0.2\n" -"Аргументи: Немає\n" -"Відповідь:\n" -" OK <повний шлях до конфігураційного файлу GDM>\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4311(title) -msgid "GREETERPIDS" -msgstr "GREETERPIDS" - -#: ../C/gdm.xml:4312(screen) -#, fuzzy, 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 "" -"\n" -"GREETERPIDS: Список усіх ідентифікаторів процесів програм привітання.\n" -" З його допомогою можна надіслати сигнал HUP усім процесам\n" -" для повторного зчитування конфігурації. Це може робити лише root.\n" -"Підтримується з: 2.3.90.2\n" -"Аргументи: Немає\n" -"Відповідь:\n" -" OK <номер процесу>;<номер процесу>;...\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4328(title) -msgid "QUERY_LOGOUT_ACTION" -msgstr "QUERY_LOGOUT_ACTION" - -#: ../C/gdm.xml:4329(screen) -#, fuzzy, 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 or SUSPEND. An\n" -" 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 "" -"\n" -"QUERY_LOGOUT_ACTION: Запит відносно можливих дій при виході\n" -"Підтримується у з'єднаннях які пройшли AUTH_LOCAL.\n" -"Підтримується з: 2.5.90.0\n" -"Відповіді:\n" -" OK <дія>;<дія>;...\n" -" Де дія - одне з HALT, REBOOT чи SUSPEND. Якщо дії неможливі,\n" -" повертається порожній список. До дії додається '!' вона вже встановлена\n" -" командою SET_LOGOUT_ACTION чи SET_SAFE_LOGOUT_ACTION. Зауважте,\n" -" SET_LOGOUT_ACTION має перевагу над\n" -" SET_SAFE_LOGOUT_ACTION.\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 100 = Немає автентифікації\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4351(title) -msgid "QUERY_VT" -msgstr "QUERY_VT" - -#: ../C/gdm.xml:4352(screen) -#, fuzzy, 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 "" -"\n" -"QUERY_VT: Спитати службу про який VT наразі активний.\n" -" Це корисно для сеансів, які не є власниками\n" -" /dev/console, але є консольними входами. Наразі\n" -" підтримується лише у Linux. На інших системах\n" -" результатом є помилка з кодом 8. Також може слугувати\n" -" способом визначення підтримки VT, якщо служба на\n" -" першому місці.\n" -"Підтримується лише для з'єднань, які пройшли AUTH_LOCAL.\n" -"Підтримується з: 2.5.90.0\n" -"Аргументи: Немає\n" -"Відповідь:\n" -" OK <номер vt>\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 8 = Віртуальний термінал не підтримується\n" -" 100 = Немає автентифікації\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4375(title) -msgid "RELEASE_DYNAMIC_DISPLAYS" -msgstr "RELEASE_DYNAMIC_DISPLAYS" - -#: ../C/gdm.xml:4376(screen) -#, fuzzy, 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: None\n" -"Answers:\n" -" OK <display>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 100 = Not authenticated\n" -" 200 = Dynamic Displays not allowed\n" -" 999 = Unknown error\n" -msgstr "" -"\n" -"RELEASE_DYNAMIC_DISPLAYS: Звільняє динамічні дисплеї наразі у стані DISPLAY_CONFIG\n" -"Підтримується з: 2.8.0.0\n" -"Аргументи: Немає\n" -"Відповідь:\n" -" OK <дисплей>\n" -" ERROR <код помилки> <опис помили англійською>\n" -" 0 = Не реалізовано\n" -" 100 = Немає автентифікації\n" -" 200 = Динамічні дисплеї не дозволені\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4392(title) -msgid "REMOVE_DYNAMIC_DISPLAY" -msgstr "REMOVE_DYNAMIC_DISPLAY" - -#: ../C/gdm.xml:4393(screen) -#, fuzzy, 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 "" -"\n" -"REMOVE_DYNAMIC_DISPLAY: Видалити динамічний дисплей, знищити сервер та очистити\n" -" конфігурацію дисплею\n" -"Підтримується з: 2.8.0.0\n" -"Аргументи: <дисплей для видалення>\n" -"Відповідь:\n" -" OK <дисплей>\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 1 = Неправильний номер дисплею\n" -" 100 = Немає аутентифікації\n" -" 200 = Динамічні дисплеї не дозволені\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4410(title) -msgid "SERVER_BUSY" -msgstr "SERVER_BUSY" - -#: ../C/gdm.xml:4411(screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"SERVER_BUSY: Returns true if half or more of the daemon's sockets\n" -" are busy, false otherwise. Used by slave programs\n" -" which want to ensure they do not overwhelm the \n" -" sever.\n" -"Supported since: 2.13.0.8\n" -"Arguments: None\n" -"Answers:\n" -" OK <value>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -msgstr "" -"\n" -"GREETERPIDS: Список усіх ідентифікаторів процесів програм привітання.\n" -" З його допомогою можна надіслати сигнал HUP усім процесам\n" -" для повторного зчитування конфігурації. Це може робити лише root.\n" -"Підтримується з: 2.3.90.2\n" -"Аргументи: Немає\n" -"Відповідь:\n" -" OK <номер процесу>;<номер процесу>;...\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4428(title) -msgid "SET_LOGOUT_ACTION" -msgstr "SET_LOGOUT_ACTION" - -#: ../C/gdm.xml:4429(screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -" slave process exits. 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" -"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 "" -"\n" -"SET_LOGOUT_ACTION: Вказує службі вимкнути/перезапустити/призупинити\n" -" комп'ютер після завершення підлеглого процесу. \n" -"Підтримується лише для з'єднань, які пройшли AUTH_LOCAL.\n" -"Підтримується з: 2.5.90.0\n" -"Аргументи: <дія>\n" -" NONE Встановити дію при виході у 'none'\n" -" HALT Встановити дію при виході у 'halt'\n" -" REBOOT Встановити дію при виході у 'reboot'\n" -" SUSPEND Встановити дію при виході у 'suspend'\n" -"\n" -"Відповідь:\n" -" OK\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 7 = Невідома дія при виході, або дія недоступна\n" -" 100 = Немає автентифікації\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4451(title) -msgid "SET_SAFE_LOGOUT_ACTION" -msgstr "SET_SAFE_LOGOUT_ACTION" - -#: ../C/gdm.xml:4452(screen) -#, fuzzy, 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" -"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 "" -"\n" -"SET_SAFE_LOGOUT_ACTION: Вказує службі вимкнути/перезапустити/призупинити\n" -" комп'ютер після виходу усіх користувачів. Якщо\n" -" виходить лише одна особа, тоді діє як \n" -" SET_LOGOUT_ACTION. Зауважте, що\n" -" SET_LOGOUT_ACTION має перевагу над\n" -" SET_SAFE_LOGOUT_ACTION, якщо має значення\n" -" відмінне від NONE. Якщо ніхто не увійшов у сеанс,\n" -" тоді дія виконується негайно.\n" -"Підтримується лише для з'єднань, які пройшли AUTH_LOCAL.\n" -"Підтримується з: 2.5.90.0\n" -"Аргументи: <дія>\n" -" NONE Встановлює дію 'none'\n" -" HALT Встановлює дію 'вимкнути'\n" -" REBOOT Встановлює дію 'перезапустити'\n" -" SUSPEND Встановлює дію 'призупинити'\n" -"\n" -"Відповідь:\n" -" OK\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 7 = Невідома дія при виході, або дія недоступна\n" -" 100 = Немає автентифікації\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4481(title) -msgid "SET_VT" -msgstr "SET_VT" - -#: ../C/gdm.xml:4482(screen) -#, fuzzy, 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 "" -"\n" -"SET_VT: Змінити на вказаний віртуальний термінал.\n" -" Корисно для сеансів, які не володіють власним /dev/console\n" -" але все ще є консольними сеансами. Наразі підтримується\n" -" лише на Linux, на інших системах команда повертає ERROR 8.\n" -"Підтримується лише для з'єднань, які пройшли AUTH_LOCAL.\n" -"Підтримується з: 2.5.90.0\n" -"Аргументи: <vt>\n" -"Відповіді:\n" -" OK\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 8 = Віртуальні термінали не підтримуються\n" -" 9 = Неправильний номер віртуального терміналу\n" -" 100 = Немає автентифікації\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - -#: ../C/gdm.xml:4503(title) -msgid "UPDATE_CONFIG" -msgstr "UPDATE_CONFIG" - -#: ../C/gdm.xml:4504(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:4580(title) -msgid "VERSION" -msgstr "VERSION" - -#: ../C/gdm.xml:4581(screen) -#, fuzzy, 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 "" -"\n" -"VERSION: запит версії\n" -"Підтримується з: 2.2.4.0\n" -"Аргументи: Немає\n" -"Відповідь:\n" -" GDM <версія gdm>\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка)\n" -" " - -#: ../C/gdm.xml:4598(title) -msgid "GDM Commands" -msgstr "Команди GDM" - -#: ../C/gdm.xml:4601(title) -msgid "GDM User Commands" -msgstr "Команди користувача GDM" - -#: ../C/gdm.xml:4603(para) -msgid "The GDM package provides the following different commands in EXPANDED_BINDIR intended to be used by the end-user:" -msgstr "Пакет GDM має наступні команди у EXPANDED_BINDIR, які призначені для використання користувачем:" - -#: ../C/gdm.xml:4609(title) -#, fuzzy -msgid "<command>gdmXnestchooser</command> and <command>gdmXnest</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdmXnestchooser</filename> та <filename>gdmXnest</filename>" - -#: ../C/gdm.xml:4612(para) -#, fuzzy -msgid "The <command>gdmXnestchooser</command> command automatically gets the correct display number, sets up access, and runs <command>Xnest</command> with -indirect localhost. This way you get an XDMCP chooser provided by your computer. You can also supply as an argument the hostname whose chooser should be displayed, so <command>gdmXnestchooser somehost</command> will run the XDMCP chooser from host <command>somehost</command> inside an Xnest session. You can make this command do a direct query instead by passing the <command>-d</command> option as well. In addition to the following options, this command also supports standard GNOME options." -msgstr "Команда <filename>gdmXnestchooser</filename> автоматично повертає коректний номер дисплею, встановлює доступ, та запускає <filename>Xnest</filename> з -indirect localhost. Таким чином отримується селектор XDMCP, що постачається вашим комп'ютером. Можна вказати аргумент з назвою вузла, чия програма вибору має відображатись, тож <filename>gdmXnestchooser somehost</filename> призведе до запуску програми вибору XDMCP з вузла <filename>somehost</filename> у сеансі Xnest. Можете змусити команду зробити прямий запит, якщо вказати параметр <filename>-d</filename>. Окрім наступних параметрів, ця команда підтримує стандартні параметри GNOME." - -#: ../C/gdm.xml:4627(title) -#, fuzzy -msgid "<command>gdmXnestchooser</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdmXnestchooser</filename>" - -#: ../C/gdm.xml:4630(term) -msgid "-x, --xnest=STRING" -msgstr "-x, --xnest=РЯДОК" - -#: ../C/gdm.xml:4632(para) -msgid "Xnest command line, default is \"Xnest\"" -msgstr "Командна Xnest, типово \"Xnest\"" - -#: ../C/gdm.xml:4639(term) -msgid "-o, --xnest-extra-options=OPTIONS" -msgstr "-o, --xnest-extra-options=ПАРАМЕТРИ" - -#: ../C/gdm.xml:4641(para) -msgid "Extra options for Xnest, default is no options." -msgstr "Додаткові параметри для Xnest, типово параметрів немає." - -#: ../C/gdm.xml:4648(term) -msgid "-n, --no-query" -msgstr "-n, --no-query" - -#: ../C/gdm.xml:4650(para) -msgid "Just run Xnest, no query (no chooser)" -msgstr "Просто запустити Xnest, без запиту (без програми привітання)" - -#: ../C/gdm.xml:4657(term) -msgid "-d, --direct" -msgstr "-d, --direct" - -#: ../C/gdm.xml:4659(para) -msgid "Do direct query instead of indirect (chooser)" -msgstr "Виконати прямий запит, замість непрямого (селектор)" - -#: ../C/gdm.xml:4666(term) -msgid "-B, --broadcast" -msgstr "-B, --broadcast" - -#: ../C/gdm.xml:4668(para) -msgid "Run broadcast instead of indirect (chooser)" -msgstr "Запустити у широкомовному режимі, замість непрямого запиту (селектор)" - -#: ../C/gdm.xml:4675(term) -msgid "-b, --background" -msgstr "-b, --background" - -#: ../C/gdm.xml:4677(para) -msgid "Run in background" -msgstr "Запустити у фоновому режимі" - -#: ../C/gdm.xml:4684(term) -msgid "--no-gdm-check" -msgstr "--no-gdm-check" - -#: ../C/gdm.xml:4686(para) -msgid "Don't check for running GDM" -msgstr "Не перевіряти, чи запущений GDM" - -#: ../C/gdm.xml:4695(title) -#: ../C/gdm.xml:4739(title) -#, fuzzy -msgid "<command>gdmflexichooser</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdmflexichooser</filename>" - -#: ../C/gdm.xml:4697(para) -msgid "The <command>gdmflexiserver</command> command provides three features. It can be used to run flexible (on demand) X displays, to run a flexible display via Xnest, and to send commands to the GDM daemon process." -msgstr "" - -#: ../C/gdm.xml:4704(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:4718(para) -msgid "Flexible displays started via Xnest 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:4726(para) -#, fuzzy -msgid "The <command>gdmflexiserver --command</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 "Параметр команди <filename>gdmflexiserver</filename> забезпечує шлях для надсилання довільних команд до GDM та може використовуватись для виявленняпроблем у сценаріях, хоча <filename>gdmflexiserver</filename> вимагає, щоб був запущений X-сервер." - -#: ../C/gdm.xml:4732(para) -#, fuzzy -msgid "In addition to the following options, <command>gdmflexiserver</command> also supports standard GNOME options." -msgstr "Окрім наступних параметрів, <filename>gdmflexiserver</filename> також підтримує стандартні параметри GNOME." - -#: ../C/gdm.xml:4742(term) -msgid "-c, --command=COMMAND" -msgstr "-c, --command=COMMAND" - -#: ../C/gdm.xml:4744(para) -msgid "Send the specified protocol command to GDM" -msgstr "Відіслати вказану протокольну команду до серверу GDM" - -#: ../C/gdm.xml:4751(term) -msgid "-n, --xnest" -msgstr "-n, --xnest" - -#: ../C/gdm.xml:4753(para) -msgid "Start a flexible X display in Xnest mode" -msgstr "" - -#: ../C/gdm.xml:4760(term) -msgid "-l, --no-lock" -msgstr "-l, --no-lock" - -#: ../C/gdm.xml:4762(para) -msgid "Do not lock current screen" -msgstr "Не блокувати поточний екран" - -#: ../C/gdm.xml:4769(term) -msgid "-d, --debug" -msgstr "-d, --debug" - -#: ../C/gdm.xml:4771(para) -msgid "Turns on debugging output which gets sent to syslog. Same as turning on debug in the configuration file." -msgstr "" - -#: ../C/gdm.xml:4779(term) -msgid "-a, --authenticate" -msgstr "-a, --authenticate" - -#: ../C/gdm.xml:4781(para) -msgid "Authenticate before running --command" -msgstr "Автентифікація перед запуском --command" - -#: ../C/gdm.xml:4788(term) -msgid "-s, --startnew" -msgstr "-s, --startnew" - -#: ../C/gdm.xml:4790(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:4801(title) -#: ../C/gdm.xml:4827(title) -#, fuzzy -msgid "<command>gdmdynamic</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdmdynamic</filename>" - -#: ../C/gdm.xml:4803(para) -#, fuzzy -msgid "The <command>gdmdynamic</command> command which creates, runs, and removes displays (X servers) on demand." -msgstr "Команда <filename>gdmdynamic</filename> створює, запускає та видаляє дисплеї (X сервери) за вимогою." - -#: ../C/gdm.xml:4808(para) -#, fuzzy -msgid "Some environments need the ability to tell GDM to create and manage new displays on the fly, where it is not possible to list the possible displays in GDM configuration files. The <command>gdmdynamic</command> command can be used to create a new display on a particular display number, run all newly created displays, or remove a display. The <command>gdmdynamic</command> command can also be used to list all attached displays, or only attached displays that match a pattern. This program is designed to manage multiple simultaneous requests and works to avoid flooding the daemon with requests. If the socket connection is busy, it will sleep and retry a certain number of times that can be tuned with the <command>-t</command> and <command>-s</command> arguments. <command>gdmdynamic</command> returns 1 on normal failure, and returns 2 if it is unable to connect to the daemon. Callers can choose to call again if a return code of 2 is received." -msgstr "У деяких випадках потрібно вказувати GDM створювати та керувати новими дисплеями на льоту, коли неможливо отримати список дисплеїв з gdm.conf. Команда gdmdynamic використовується для створення нового дисплею з певним номером, запуску усіх нових створених дисплеїв, або видалення дисплею. Команда gdmdynamic також може використовуватись для отримання списку усіх приєднаних дисплеїв, чи приєднаних дисплеїв що відповідають певному шаблону." - -#: ../C/gdm.xml:4832(emphasis) -msgid "One of the following options can be used per instance:" -msgstr "Можна використовувати один з наступних параметрів на екземпляр:" - -#: ../C/gdm.xml:4839(term) -msgid "-a display=server" -msgstr "-a display=сервер" - -#: ../C/gdm.xml:4841(para) -msgid "Add a new display configuration. For example, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a 3=/usr/X11R6/bin/X -dev /dev/fb2\"</command>" -msgstr "Додати нову конфігурацію дисплею. Наприклад, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a 3=/usr/X11R6/bin/X -dev /dev/fb2\"</command>" - -#: ../C/gdm.xml:4850(term) -msgid "-r" -msgstr "-r" - -#: ../C/gdm.xml:4852(para) -msgid "Release (run) all displays waiting in the DISPLAY_CONFIG state." -msgstr "Звільнити (запустити) усі дисплеї, що очікують стан DISPLAY_CONFIG." - -#: ../C/gdm.xml:4859(term) -msgid "-d display" -msgstr "-d display" - -#: ../C/gdm.xml:4861(para) -msgid "Delete a display, killing the X server and purging the display configuration. For example, \"-d 3\"." -msgstr "Видалити дисплей, знищити X-сервер та стерти конфігурацію дисплея. Наприклад, \"-d 3\"." - -#: ../C/gdm.xml:4869(term) -msgid "-l [pattern]" -msgstr "-l [шаблон]" - -#: ../C/gdm.xml:4871(para) -msgid "List displays via the ATTACHED_SERVERS command. Without a pattern lists all attached displays. With a pattern will match using glob characters '*', '?', and '[]'. For example: <command>\"-l Standard*\"</command><command>\"-l *Xorg*\"</command>" -msgstr "Отримати перелік дисплеїв командою ATTACHED_SERVERS. Без шаблону виводиться список усіх приєднаних дисплеїв. У шаблоні можуть використовуватись метасимволи '*', '?', та '[]'. Наприклад: <command>\"-l Standard*\"</command><command>\"-l *Xorg*\"</command>" - -#: ../C/gdm.xml:4884(emphasis) -msgid "These options can be added to the above:" -msgstr "До вказаного вище може додаватись цей параметр:" - -#: ../C/gdm.xml:4891(term) -msgid "-v" -msgstr "-v" - -#: ../C/gdm.xml:4893(para) -msgid "Verbose mode. Prinr diagnostic messages about each message sent to GDM." -msgstr "Докладний режим. Виводяться діагностичні повідомлення про кожну команду. надіслану до GDM." - -#: ../C/gdm.xml:4901(term) -msgid "-b" -msgstr "-b" - -#: ../C/gdm.xml:4903(para) -msgid "Background mode. Fork child to do the work and return immediately." -msgstr "Фоновий режим. Створити дочірній процес негайно повернутись." - -#: ../C/gdm.xml:4910(term) -msgid "-t RETRY" -msgstr "-t СПРОБ" - -#: ../C/gdm.xml:4912(para) -msgid "If the daemon socket is busy, <command>gdmdynamic</command> will retry to open the connection the specified RETRY number of times. Default value is 15." -msgstr "Якщо сокет служби зайнятий, <command>gdmdynamic</command> буде намагатись відкрити з'єднання з вказану у СПРОБ кількість раз. Типове значення 15." - -#: ../C/gdm.xml:4921(term) -msgid "-s SLEEP" -msgstr "-s ПАУЗА" - -#: ../C/gdm.xml:4923(para) -msgid "If the daemon socket is busy, <command>gdmdynamic</command> 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 "Якщо сокет служби зайнятий, <command>gdmdynamic</command> буде призупинятися на час очікування між спробами. До вказаного числа ПАУЗА випадково додається 0-5 секунд, щоб кілька екземплярів gdmdynamic не намагались перезапуститись одночасно. Якщо значення ПАУЗА дорівнює нулю, період призупинення встановлюється 1 секунда. Типове значення 8 секунд." - -#: ../C/gdm.xml:4938(title) -#, fuzzy -msgid "<command>gdmphotosetup</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdmphotosetup</filename>" - -#: ../C/gdm.xml:4940(para) -#, fuzzy -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 <filename>~/.face</filename>. This command accepts standard GNOME options." -msgstr "Дозволяє користувачу обирати зображення, яке буде використовуватись як фотографія у при перегляді портретів GDM, якщо цю функцію увімкнено у GDM. Вибраний файл зберігається у ~/.face. Команда приймає стандартні для GNOME аргументи." - -#: ../C/gdm.xml:4949(title) -#, fuzzy -msgid "<command>gdmthemetester</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdmthemetester</filename>" - -#: ../C/gdm.xml:4951(para) -#, fuzzy -msgid "" -"<command>gdmthemetester</command> 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. <command>gdmthemetester</command> requires that the system support <command>gdmXnest</command>. Note that themes can display differently depending on the theme's \"Show mode\". <command>gdmthemetester</command> allows viewing the themes in different modes via the environment option. Valid environment values and their meanings follow: <screen>\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" -"</screen>" -msgstr "" -"<filename>gdmthemetester</filename> приймає два параметри. Перший вказує оточення а другий вказує шлях або назву теми, що переглядається. Це інструмент для перегляду тем GDM. Він може використовуватись для перевірки та перегляду тем. <filename>gdmthemetester</filename> вимагає, щоб система підтримувала <filename>gdmXnest</filename>. Зауважте, що теми можуть відображатись по-різному в залежності від \"Режиму відображення\" теми. <filename>gdmthemetester</filename> дозволяє змінювати режим перегляду теми у змінній оточення. Можливі значення змінної оточення та їх сенс: <screen>\n" -"console - консольний режим.\n" -"console-timed - консольний не гнучкий режим.\n" -"flexi - гнучкий режим.\n" -"xdmcp - віддалений (XDMCP) режим.\n" -"remote-flexi - віддалений (XDMCP) та гнучкий режим.\n" -" </screen>" - -#: ../C/gdm.xml:4977(title) -#, fuzzy -msgid "GDM Root User Commands" -msgstr "RebootCommand" - -#: ../C/gdm.xml:4979(para) -msgid "The GDM package provides the following different commands in EXPANDED_SBINDIR intended to be used by the root user:" -msgstr "Пакет GDM підтримує наступні команди у EXPANDED_SBINDIR, що призначені для використання користувачем root:" - -#: ../C/gdm.xml:4985(title) -#: ../C/gdm.xml:5001(title) -#, fuzzy -msgid "<command>gdm</command> and <command>gdm-binary</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdm</filename> та <filename>gdm-binary</filename>" - -#: ../C/gdm.xml:4988(para) -#, fuzzy -msgid "The <command>gdm</command> command is really just a script which runs the <command>gdm-binary</command>, passing along any options. Before launching <command>gdm-binary</command>, the gdm wrapper script will source the <filename><etc>/profile</filename> file to set the standard system environment variables. In order to better support internationalization, it will also set the LC_MESSAGES environment variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you really need to set some additional environment before launching GDM, you can do so in this script." -msgstr "Команда <filename>gdm</filename> насправді є сценарієм, який запускає <filename>gdm-binary</filename> та передає їх декілька параметрів. Перед запуском gdm-binary, обгортка gdm включає файл <filename><etc>/profile</filename> для встановлення стандартних змінних оточення. Для кращої підтримки інтернаціоналізації, значення змінної оточення LC_MESSAGES встановлюється у значення LANG, якщо не встановлено ані LC_MESSAGES, ані LC_ALL. Якщо перед запуском GDM треба встановити інші змінні оточення, їх можна встановити у цьому сценарії." - -#: ../C/gdm.xml:5005(term) -msgid "--help" -msgstr "--help" - -#: ../C/gdm.xml:5007(para) -msgid "Gives a brief overview of the command line options." -msgstr "Виводить коротку довідку з переліком параметрів командного рядка." - -#: ../C/gdm.xml:5014(term) -msgid "-nodaemon" -msgstr "-nodaemon" - -#: ../C/gdm.xml:5016(para) -msgid "If this option is specified, then GDM does not fork into the background when run. You can use just a single dash with this option to preserve compatibility with XDM." -msgstr "Якщо вказано цей параметр, тоді після старту GDM не буде створюватись дочірній процес у фоновому режимі. У цьому параметрі можна просто використовувати дефіс, щоб зберегти сумісність XDM." - -#: ../C/gdm.xml:5025(term) -msgid "--no-console" -msgstr "--no-console" - -#: ../C/gdm.xml:5027(para) -msgid "Tell the daemon that it should not run anything on the console. This means that none of the local servers from the <filename>[servers]</filename> section will be run, and the console will not be used for communicating errors to the user. An empty <filename>[servers]</filename> section automatically implies this option." -msgstr "Вказує службі не запускати нічого у консолі. Це означає, що не буде запускатись жоден з локальних серверів, вказаних в розділі <filename>[servers]</filename>, та консоль не буде використовуватись для виводу помилок. Цей параметр автоматично вмикається, якщо розділ <filename>[servers]</filename> порожній." - -#: ../C/gdm.xml:5039(term) -msgid "--config=CONFIGFILE" -msgstr "--config=CONFIGFILE" - -#: ../C/gdm.xml:5041(para) -msgid "Specify an alternative configuration file." -msgstr "Визначає альтернативний конфігураційний файл." - -#: ../C/gdm.xml:5048(term) -msgid "--preserve-ld-vars" -msgstr "--preserve-ld-vars" - -#: ../C/gdm.xml:5050(para) -msgid "When clearing the environment internally, preserve all variables starting with LD_. This is mostly for debugging purposes." -msgstr "При внутрішньому очищенні оточення, зберігаються усі змінні, що починаються з LD_. Це задля спрощення налагодження." - -#: ../C/gdm.xml:5058(term) -msgid "--version" -msgstr "--version" - -#: ../C/gdm.xml:5060(para) -msgid "Print the version of the GDM daemon." -msgstr "Вивести версію сервера GDM." - -#: ../C/gdm.xml:5067(term) -msgid "--wait-for-go" -msgstr "--wait-for-go" - -#: ../C/gdm.xml:5069(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 "Якщо вказано цей параметр, gdm виконає ініціалізацію, але запустить лише перший локальний дисплей та буде чекати повідомлення GO через протокол fifo. Програма привітання не виводиться, доки не буде отримано повідомлення GO. Також до надходження цього повідомлення заборонені запити гнучких серверів та не запускається XDMCP. Ця функція використовується у сценаріях для раннього запуску X, але коли поки-що небажано надавати можливість входу у сеанс. Коли сценарій готовий розпочати сеанс, він надсилає GO та GDM продовжує роботу. Цю функцію додано у версії 2.5.90.0." - -#: ../C/gdm.xml:5087(title) -#, fuzzy -msgid "<command>gdmsetup</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdmsetup</filename>" - -#: ../C/gdm.xml:5089(para) -#, fuzzy -msgid "<command>gdmsetup</command> 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 <command>gdmsetup</command> 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 "Команда gdmsetup запускає графічну програму для зміни конфігураційного файлу GDM gdm.conf. Зазвичай. на системах, що підтримуються PAM userhelper, ви можете запускати <filename>gdmsetup</filename> як звичайний користувач, але перед запуском програма запитає пароль користувача root. У інших системах програму може запускати лише. Ця програма підтримує стандартні параметри GNOME." - -#: ../C/gdm.xml:5101(title) -#, fuzzy -msgid "<command>gdm-restart</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdm-restart</filename>" - -#: ../C/gdm.xml:5103(para) -#, fuzzy -msgid "<command>gdm-restart</command> stops and restarts GDM by sending the GDM daemon a HUP signal. This command will immediately terminate all sessions and log out users currently logged in with GDM." -msgstr "<filename>gdm-restart</filename> зупиняє та перезапускає GDM надсилаючи службі GDM сигнал HUP. Це призводить до негайного припинення усіх сеансів та виходу користувачів, що увійшли через GDM." - -#: ../C/gdm.xml:5111(title) -#, fuzzy -msgid "<command>gdm-safe-restart</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdm-safe-restart</filename>" - -#: ../C/gdm.xml:5113(para) -#, fuzzy -msgid "<command>gdm-safe-restart</command> stops and restarts GDM by sending the GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out." -msgstr "<filename>gdm-safe-restart</filename> зупиняє та перезапускає GDM надсилаючи службі GDM сигнал USR1. GDM перезапускається одразу після виходу усіх користувачів." - -#: ../C/gdm.xml:5121(title) -#, fuzzy -msgid "<command>gdm-stop</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdm-stop</filename>" - -#: ../C/gdm.xml:5123(para) -#, fuzzy -msgid "<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM signal." -msgstr "<filename>gdm-stop</filename> зупиняє GDM надсилаючи службі GDM сигнал TERM." - -#: ../C/gdm.xml:5131(title) -msgid "GDM Internal Commands" -msgstr "Внутрішні команди GDM" - -#: ../C/gdm.xml:5133(para) -msgid "The GDM package provides the following different commands in EXPANDED_LIBEXECDIR intended to be used by the gdm daemon process." -msgstr "Пакет GDM містить наступні команди у EXPANDED_LIBEXECDIR, що призначені для використання процесом служби gdm." - -#: ../C/gdm.xml:5139(title) -#, fuzzy -msgid "<command>gdmchooser</command> and <command>gdmlogin</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdmchooser</filename> та <filename>gdmlogin</filename>" - -#: ../C/gdm.xml:5142(para) -#, fuzzy -msgid "The <command>gdmgreeter</command> and <command>gdmlogin</command> are two different login applications, either can be used by GDM. <command>gdmgreeter</command> is themeable with GDM themes while <command>gdmlogin</command> is themable with GTK+ themes. These applications are normally executed by the GDM daemon. Both commands support standard GNOME options." -msgstr "<filename>gdmgreeter</filename> та <filename>gdmlogin</filename> - це дві різні програми входу у сеанс, що використовуються GDM. <filename>gdmgreeter</filename> - підтримує теми GDM, а <filename>gdmlogin</filename> підтримує теми GTK+. Ці програми зазвичай запускаються службою GDM. Обидві команди підтримують стандартні параметри GNOME." - -#: ../C/gdm.xml:5153(title) -#: ../C/gdm.xml:5164(title) -#, fuzzy -msgid "<command>gdmchooser</command> Command Line Options" -msgstr "Параметри командного рядка <filename>gdmchooser</filename>" - -#: ../C/gdm.xml:5155(para) -#, fuzzy -msgid "The <command>gdmchooser</command> is the XDMCP chooser application. The <command>gdmchooser</command> is normally executed by the GDM daemon. It supports the following options for XDM compatibility. This command supports standard GNOME options and is found in support standard GNOME options." -msgstr "<filename>gdmchooser</filename> - це програма вибору вузла XDMCP. <filename>gdmchooser</filename> зазвичай запускається службою GDM. Програма підтримує сумісність з XDM. Команда підтримує стандартні параметри GNOME." - -#: ../C/gdm.xml:5167(term) -msgid "-xdmaddress=SOCKET" -msgstr "-xdmaddress=СОКЕТ" - -#: ../C/gdm.xml:5169(para) -msgid "Socket for XDM communication." -msgstr "Сокет для зв'язку з XDM." - -#: ../C/gdm.xml:5176(term) -msgid "--clientaddress=ADDRESS" -msgstr "--clientaddress=АДРЕСА" - -#: ../C/gdm.xml:5178(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 "Адреса клієнта для повернення на запит XDM. Цей параметр використовується для запуску gdmchooser з XDM, та не використовується з GDM." - -#: ../C/gdm.xml:5186(term) -msgid "-connectionType=TYPE" -msgstr "-connectionType=ТИП" - -#: ../C/gdm.xml:5188(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 "Тип з'єднання для повернення на запит XDM. Цей параметр використовується для запуску gdmchooser з XDM, та не використовується з GDM." - -#: ../C/gdm.xml:5198(command) -msgid "gdm-ssh-session" -msgstr "gdm-ssh-session" - -#: ../C/gdm.xml:5200(para) -msgid "The <command>gdm-ssh-session</command> is normally executed by the GDM daemon when starting a secure remote connection through ssh. It does not take any options." -msgstr "<command>gdm-ssh-session</command> зазвичай запускається службою GDM коли встановлюється віддалене безпечне з'єднання через ssh. Програма не приймає ніяких параметрів." - -#: ../C/gdm.xml:5212(title) -msgid "Themed Greeter" -msgstr "Програма привітання з темами" - -#: ../C/gdm.xml:5214(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 <ulink type=\"http\" url=\"http://art.gnome.org/themes/gdm_greeter/\"> the theme website</ulink>." -msgstr "У цьому розділі описується створення тем для програми привітання з підтримкою тем. Приклади, включно з знімками екранів, дивіться у стандартних встановлених темах та темах з <ulink type=\"http\" url=\"http://art.gnome.org/themes/gdm_greeter/\"> веб-сайту тем</ulink>." - -#: ../C/gdm.xml:5223(title) -msgid "Theme Overview" -msgstr "Огляд тем" - -#: ../C/gdm.xml:5225(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 <filename><share>/gdm/themes/<theme_name></filename>. Usually this would be under <filename>/usr/share</filename>. The theme directory should contain a file called <filename>GdmGreeterTheme.desktop</filename> which has similar format to other .desktop files and looks like:" -msgstr "Тема GDM складається з XML файлу який відповідає специфікації у gui/greeter/greeter.dtd. Файли теми зберігаються у каталозі <filename><share>/gdm/themes/<theme_name></filename>. Зазвичай каталог знаходиться у <filename>/usr/share</filename>. Каталог теми має містити файл з назвою <filename>GdmGreeterTheme.desktop</filename> з форматом подібним до інших файлів типу .desktop та має виглядати таким чином:" - -#: ../C/gdm.xml:5236(screen) -#, fuzzy, 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 "" -"\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" -" " - -#: ../C/gdm.xml:5247(para) -msgid "The Name, Description, Author and Copyright fields can be translated just like the other <filename>.desktop</filename>files. 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 "Назва, опис, автор та авторські права можна перекладати як і у інших файлах типу <filename>.desktop</filename>. Усі файли вказані файли мають у каталозі з темами. Файл, на який вказує поле Screenshot повинен бутизнімком екрану теми з розмірами 200x150 (він може бути відсутній, але якщо він є - це краще для користувача). У полі Greeter вказується файл XML, який містить опис теми. Опис буде згаданий далі." - -#: ../C/gdm.xml:5257(para) -#, fuzzy -msgid "Once you have theme ready and installed you can test it with the installed <command>gdmthemetester</command> script. This script assumes that the X server supports Xnest. 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 "Якщо тема готова та встановлена можете перевірити її сценарієм <filename>gdmthemetester</filename>. Цей сценарій використовує сервер X-сервер Xnest, тож він має бути встановлений. Програма приймає два аргументи, перший - оточення, яке слід встановити - одне з console, console-timed, flexi, remote-flexi, xdmcp. Де console - стандартний вхід з консолі, console-timed - вхід з консолі з увімкненим відкладеним входом, flexi - будь-який локальний гнучкий сервер, remote-flexi - гнучкий сервер, який не є локальним (наприклад гнучкий сервер Xnest, запущений на віддаленому дисплеї) та xdmcp - для віддалених з'єднань XDMCP. другий аргумент - назва теми. Наприклад, щоб перевірити вигляд у режимі XDMCP теми circles слід запустити:" - -#: ../C/gdm.xml:5272(command) -msgid "gdmthemetester xdmcp circles" -msgstr "gdmthemetester xdmcp circles" - -#: ../C/gdm.xml:5275(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 Xnest window. This can be done in GNOME by focusing the Xnest window and pressing Alt-PrintScreen." -msgstr "Перевірте тему в усіх варіантах оточення, та перевірте вигляд попередження про натискання caps lock. Також було б добре зробити знімок екрану, просто зробіть знімок екрану вікна Xnest. це можна зробити у GNOME, якщо передати фоку вводу вікну Xnest та натиснути Alt-PrintScreen." - -#: ../C/gdm.xml:5283(para) -#, fuzzy -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 <filename><share>/gdm/themes</filename> directory). And this is the tarball you distribute and people can install from the graphical configuration application. You can do this with the commands: <screen>\n" -"cd <share>/gdm/themes\n" -"tar czvf <theme_name>.tar.gz <theme_name>/\n" -"</screen>" -msgstr "" -"Якщо все завершено, зробіть tar-архів, що містить каталог (щоб ви могли просто розпакувати його у каталозі <filename>/usr/share/gdm/themes</filename>). Можете розповсюджувати цей tar-архів, інші можуть встановити з графічної програми налаштовування. Тому це можна зробити командами: <screen>\n" -"cd /usr/share/gdm/themes\n" -"tar czvf <theme_name>.tar.gz <theme_name>/\n" -" </screen>" - -#: ../C/gdm.xml:5297(title) -msgid "Detailed Description of Theme XML format" -msgstr "Докладний опис XML формату тем" - -#: ../C/gdm.xml:5300(title) -msgid "Box Nodes" -msgstr "Box Nodes" - -#: ../C/gdm.xml:5302(para) -#, fuzzy -msgid "" -"Box nodes are container nodes for item nodes. Box nodes are specified as follows: <screen>\n" -"<box orientation=\"alignment\" min-width=\"num\"\n" -"xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -"homogeneous=\"bool\">\n" -"</screen> 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 "" -"Вузли контейнерів є контейнерами для вузлів елементів. Вузли контейнерів вказуються наступним чином: <screen>\n" -"<box orientation=\"alignment\" min-width=\"num\" xpadding=\"num\"\n" -"ypadding=\"num\" spacing=\"num\" homogeneous=\"bool\">\n" -" </screen> Де \"num\" означає число, а bool означає \"true\" чи \"false\". Значення вирівнювання може бути \"horizontal\" чи \"vertical\". Якщо ви залишите будь-яку властивість вимкненою, її типове значення буде нуль, \"false\" або для \"homogeneous\", та \"vertical\" для орієнтації." - -#: ../C/gdm.xml:5318(para) -msgid "If the box is homogeneous then the children are allocated equal amount of space." -msgstr "Якщо контейнер є однорідним, тоді дочірні елементи займають однаковий простір." - -#: ../C/gdm.xml:5323(para) -msgid "The \"min-width\" must be specified in pixels. Obviously there is also a corresponding \"min-height\" property as well." -msgstr "\"min-width\" вказує величину у точках. Також є відповідна властивість \"min-height\"." - -#: ../C/gdm.xml:5331(title) -msgid "Fixed Nodes" -msgstr "Вузли Fixed" - -#: ../C/gdm.xml:5333(para) -#, fuzzy -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: <screen>\n" -"<fixed>\n" -"</screen> Then you put other items with proper position nodes inside this." -msgstr "Fixed - контейнер дочірні елементи якого розташовані за вказаними координатами. Розмір контейнера є найбільшим прямокутником, який містить усі дочірні елементи. Контейнер Fixed не має додаткових властивостей, можна просто використовувати: <screen><fixed></screen>, потім помістити інші вузли з відповідними позиціями." - -#: ../C/gdm.xml:5344(para) -msgid "The \"toplevel\" node is really just like a fixed node." -msgstr "Вузол \"toplevel\" подібний до вузла fixed." - -#: ../C/gdm.xml:5350(title) -msgid "Item Nodes" -msgstr "Вузли елементів" - -#: ../C/gdm.xml:5352(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 "Тема GDM, що створена вказуванням ієрархії вузлів елемента та контейнера. Вузли елементів можуть мати наступні значення \"type\":" - -#: ../C/gdm.xml:5360(term) -msgid "entry" -msgstr "entry" - -#: ../C/gdm.xml:5362(para) -msgid "Text entry field." -msgstr "Поле вводу тексту." - -#: ../C/gdm.xml:5369(term) -msgid "list" -msgstr "list" - -#: ../C/gdm.xml:5371(para) -msgid "A list widget." -msgstr "Віджет списку." - -#: ../C/gdm.xml:5378(term) -msgid "label" -msgstr "label" - -#: ../C/gdm.xml:5380(para) -msgid "A text label. Must have a \"text\" node to specify the text." -msgstr "Текстова позначка. Мусить мати вузол \"text\" для вказування тексту." - -#: ../C/gdm.xml:5388(term) -msgid "pixmap" -msgstr "pixmap" - -#: ../C/gdm.xml:5390(para) -msgid "An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, etc...)" -msgstr "Растрове зображення у форматі, який підтримує gdk-pixbuf. Наприклад, PNG, JPEG, Tiff, etc...)" - -#: ../C/gdm.xml:5398(term) -msgid "rect" -msgstr "rect" - -#: ../C/gdm.xml:5400(para) -msgid "Rectangle." -msgstr "Прямокутник." - -#: ../C/gdm.xml:5407(term) -msgid "svg" -msgstr "svg" - -#: ../C/gdm.xml:5409(para) -msgid "Scaled Vector Graphic image." -msgstr "Зображення у форматі векторної графіки." - -#: ../C/gdm.xml:5416(para) -#, fuzzy -msgid "" -"For example: <screen>\n" -"<item type=\"label\">\n" -"</screen> 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 "Наприклад: елементи <screen><item type=\"label\"></screen> можуть визначати ідентифікатори значень, які надають їм специфічний вигляд та поведінку чи форматування. Далі можна змінити процес входу шляхом додавання власних віджетів з власними ідентифікаторами для деяких елементів (наразі лише для елементу списку)" - -#: ../C/gdm.xml:5427(para) -msgid "Entry items can have id values as follows:" -msgstr "Елементи вузлів можуть мати такі значення ідентифікаторів:" - -#: ../C/gdm.xml:5433(term) -msgid "user-pw-entry" -msgstr "user-pw-entry" - -#: ../C/gdm.xml:5435(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 "Поле вводу для ідентифікатора користувача та паролю. Це поле використовується для відповіді на запити PAM/GDM (Ім'я користувача, пароль, тощо..)." - -#: ../C/gdm.xml:5445(para) -msgid "List items can have id values as follows:" -msgstr "Елементи списку можуть мати такі значення:" - -#: ../C/gdm.xml:5451(term) -msgid "userlist" -msgstr "userlist" - -#: ../C/gdm.xml:5453(para) -msgid "A Face Browser list, so that users can pick their username by clicking on this instead of typing." -msgstr "Елемент перегляду портретів. Ці користувачі можуть вибирати їх ім'я користувача натискаючи на портреті." - -#: ../C/gdm.xml:5462(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 "Окрім того, можна мати довільний ідентифікатор (рекомендується, щоб вони починались з 'custom', щоб не конфліктувати з наступними доповненими версіями цієї специфікації) та запитувати у користувача додаткову інформацію. Дивіться розділ 'Власні віджети'" - -#: ../C/gdm.xml:5469(para) -msgid "Label items can have id values as follows:" -msgstr "Елементи позначок можуть мати такі ідентифікатори:" - -#: ../C/gdm.xml:5475(term) -msgid "clock" -msgstr "clock" - -#: ../C/gdm.xml:5477(para) -#, fuzzy -msgid "Label that displays the date and time." -msgstr "Позначка, що відображає дату та час." - -#: ../C/gdm.xml:5484(term) -msgid "pam-prompt" -msgstr "pam-prompt" - -#: ../C/gdm.xml:5486(para) -#, fuzzy -msgid "Label that displays the PAM prompt. This is the prompt that PAM uses to ask for username, password, etc..." -msgstr "Позначки відображає запрошення PAM. Це запрошення використовується PAM для запиту імені користувача, паролю, тощо..." - -#: ../C/gdm.xml:5494(term) -msgid "pam-error" -msgstr "pam-error" - -#: ../C/gdm.xml:5496(para) -#, fuzzy -msgid "Label that displayst PAM/GDM error messages. Such as when user can't log in." -msgstr "Позначка для відображення повідомлень про помилки від PAM/GDM. Тобто, повідомлення про неможливість входу у сеанс." - -#: ../C/gdm.xml:5504(term) -msgid "pam-message" -msgstr "pam-message" - -#: ../C/gdm.xml:5506(para) -#, fuzzy -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 "Позначка для відображення повідомлень від PAM. Ці повідомлення PAM/GDM виводять стан облікового рахунку, довідку про запрошення та іншу інформацію." - -#: ../C/gdm.xml:5515(term) -msgid "timed-label" -msgstr "timed-label" - -#: ../C/gdm.xml:5517(para) -msgid "Label that displays timed login information." -msgstr "Позначка, що відображає інформацію про вхід у сеанс." - -#: ../C/gdm.xml:5524(para) -msgid "Rectangles can have id values as follows:" -msgstr "прямокутники можуть мати такі значення ідентифікаторів:" - -#: ../C/gdm.xml:5530(term) -msgid "caps-lock-warning" -msgstr "caps-lock-warning" - -#: ../C/gdm.xml:5532(para) -msgid "Displays an icon that shows if the CAPS LOCK key is depressed. This rectangle will be hidden/shown appropriately" -msgstr "Відображає значок, який показує чи нажата клавіша CAPS LOCK." - -#: ../C/gdm.xml:5541(para) -#, fuzzy -msgid "" -"If an item is of type rect, the item can be a button. Buttons must also include a \"button\" value as follows: <screen>\n" -"<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n" -"</screen>" -msgstr "Якщо елемент має тип прямокутник, елемент може бути кнопкою. Кнопки також мають включати значення \"button\": <screen><item type=\"rect\" id=\"disconnect_button\" button=\"true\">.</screen>" - -#: ../C/gdm.xml:5549(para) -msgid "Possible values for button ids are as follows:" -msgstr "Можливі значення для кнопок:" - -#: ../C/gdm.xml:5555(term) -msgid "chooser_button" -msgstr "chooser_button" - -#: ../C/gdm.xml:5557(para) -msgid "Runs the XDMCP chooser." -msgstr "Запускає програму вибору XDMCP." - -#: ../C/gdm.xml:5564(term) -msgid "config_button" -msgstr "config_button" - -#: ../C/gdm.xml:5566(para) -msgid "Runs the GDM configuration application." -msgstr "Запускає програму налаштовування GDM." - -#: ../C/gdm.xml:5573(term) -msgid "disconnect_button" -msgstr "disconnect_button" - -#: ../C/gdm.xml:5575(para) -msgid "Disconnect from remote session." -msgstr "Відключає від віддаленого сеансу." - -#: ../C/gdm.xml:5582(term) -msgid "language_button" -msgstr "language_button" - -#: ../C/gdm.xml:5584(para) -msgid "Displays the language selection dialog." -msgstr "Відображає діалогове вікно вибору мови." - -#: ../C/gdm.xml:5591(term) -msgid "halt_button" -msgstr "halt_button" - -#: ../C/gdm.xml:5593(para) -msgid "Halt (shuts down) the system." -msgstr "Зупиняє (вимикає) систему." - -#: ../C/gdm.xml:5600(term) -msgid "reboot_button" -msgstr "reboot_button" - -#: ../C/gdm.xml:5602(para) -msgid "Restart the system." -msgstr "Перезапуск системи." - -#: ../C/gdm.xml:5609(term) -msgid "session_button" -msgstr "session_button" - -#: ../C/gdm.xml:5611(para) -msgid "List and select from available sessions." -msgstr "Виводить список доступних сеансів." - -#: ../C/gdm.xml:5618(term) -msgid "suspend_button" -msgstr "suspend_button" - -#: ../C/gdm.xml:5620(para) -msgid "Suspend the system." -msgstr "Призупиняє систему." - -#: ../C/gdm.xml:5627(term) -msgid "system_button" -msgstr "system_button" - -#: ../C/gdm.xml:5629(para) -#, fuzzy -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 "Функція вимкнення/перезавантаження/призупинення/тощо (якщо дозволено у параметрах GDM). Також дозволяє користувачу запускати програму налаштовування, якщо користувач введе пароль користувача root (знову ж таки, якщо увімкнено у конфігурації GDM). Цей елемент звичайно називається Дії, та посилається на меню Дії." - -#: ../C/gdm.xml:5642(title) -msgid "Position Node" -msgstr "Вузол позиції" - -#: ../C/gdm.xml:5644(para) -#, fuzzy -msgid "" -"Each item can specify its position and size via the \"pos\" node. For example: <screen>\n" -"<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" -"</screen>" -msgstr "Для кожного елементу можна вказати його позицію та розмір через вузол \"pos\". Наприклад: <screen><pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/></screen>" - -#: ../C/gdm.xml:5652(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:5658(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 "Для x та y, також можна вказати від'ємне значення розташування, що буде означати відлік від правого чи нижнього боку. Але це стосується лише абсолютних координат. Якщо вказано від'ємне значення відсотків, відлік все одно буде з того самого боку." - -#: ../C/gdm.xml:5665(para) -#, fuzzy -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: <screen>\n" -"<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/>\n" -"</screen>" -msgstr "позиція також вказує якір елемента, це може бути \"n\", \"ne\", \"e\", \"se\", \"s\", \"sw\", \"w\" та \"nw\" чи \"center\" що означає різні краї/кути чи центр, якщо вказано \"center\". Наприклад: <screen><pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/></screen>" - -#: ../C/gdm.xml:5676(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 "Якщо елемент містить контейнер, можна вказати ширину та висоту \"box\", що означає, що вони вважаються шириною та висотою контейнера, тобто елементи у контейнері плюс відступи." - -#: ../C/gdm.xml:5682(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 "Якщо елемент містить зображення SVG, ви можете вказати ширину та висоту \"scale\", що означає, що масштаб зображення SVG буде змінено, щоб воно пристосувалось до запитаної області." - -#: ../C/gdm.xml:5688(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 "Можна вказати властивості \"expand\" значення \"true\" чи false. Якщо вказано true, тоді дочірній елемент буде розширено наскільки це можливо (тобто він займатиме більше простору, якщо він є)." - -#: ../C/gdm.xml:5695(para) -#, fuzzy -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: <screen>\n" -"<item type=\"label\">\n" -"<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -"</screen>" -msgstr "" -"Для позначок (починаючи з 2.4.4.3) є дві додаткові властивості (та лише для позначок). Перша - \"max-width\", яка вказує максимальну ширину позначки у точках. Другий - \"max-screen-percent-width\" який вказує максимальний відсоток ширини екрану, який може зайняти позначка. Типово позначка не може зайняти більше ніж 90% відсотків ширини екрану. Приклад: <screen>\n" -"<item type=\"label\">\n" -"<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -" </screen>" - -#: ../C/gdm.xml:5711(title) -msgid "Show Node" -msgstr "Вузол Show" - -#: ../C/gdm.xml:5713(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 "Вузли типу Some можуть відображатись у кількох режимах, як при віддаленому режимі. Декілька значень можна вказати та вони мають розділятись комами. Можливі значення:" - -#: ../C/gdm.xml:5719(para) -msgid "<filename>console</filename> - In console mode." -msgstr "<filename>console</filename> - консольний режим." - -#: ../C/gdm.xml:5722(para) -msgid "<filename>console-fixed</filename> - In console non-flexi mode." -msgstr "<filename>console-fixed</filename> - консольний не-гнучкий режим." - -#: ../C/gdm.xml:5725(para) -msgid "<filename>console-flexi</filename> - In console & flexi mode." -msgstr "<filename>console-flexi</filename> - консольний та гнучкий режим." - -#: ../C/gdm.xml:5728(para) -msgid "<filename>flexi</filename> - In flexi mode." -msgstr "<filename>flexi</filename> - гнучкий режим." - -#: ../C/gdm.xml:5731(para) -msgid "<filename>remote</filename> - In remote mode." -msgstr "<filename>remote</filename> - віддалений режим." - -#: ../C/gdm.xml:5734(para) -msgid "<filename>remote-flexi</filename> - In remote & flexi mode." -msgstr "<filename>remote-flexi</filename> - віддалений та гнучкий режим." - -#: ../C/gdm.xml:5738(para) -#, fuzzy -msgid "" -"For example: <screen>\n" -"<show modes=\"flexi,remote\"/>\n" -"</screen>" -msgstr "Наприклад: <screen><show modes=\"flexi,remote\"/></screen>" - -#: ../C/gdm.xml:5745(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 "Також ви можете вказати значення \"type\", щоб позначити, що певні елементи мають відображатись якщо type має значення true. Допустимі значення:" - -#: ../C/gdm.xml:5751(para) -#, fuzzy -msgid "<filename>chooser</filename>, if ChooserButton is set to \"true\" in the GDM configuration." -msgstr "<filename>chooser</filename>, якщо ChooserButton у файлі <filename>gdm.conf</filename> має значення \"true\"." - -#: ../C/gdm.xml:5755(para) -#, fuzzy -msgid "<filename>config</filename>, if ConfigAvailable is set to \"true\" in the GDM configuration." -msgstr "<filename>config</filename>, якщо ConfigAvailable у файлі <filename>gdm.conf</filename> має значення \"true\"." - -#: ../C/gdm.xml:5759(para) -#, fuzzy -msgid "<filename>halt</filename>, if HaltDaemon is specified in the GDM configuration." -msgstr "<filename>halt</filename>, якщо у файлі <filename>gdm.conf</filename> вказано HaltDaemon." - -#: ../C/gdm.xml:5763(para) -#, fuzzy -msgid "<filename>reboot</filename>, if RebootCommand is specified in the GDM configuration." -msgstr "<filename>reboot</filename>, якщо у файлі <filename>gdm.conf</filename> вказано RebootCommand." - -#: ../C/gdm.xml:5767(para) -#, fuzzy -msgid "<filename>suspend</filename>, if SuspendCommand is specified in the GDM configuration." -msgstr "<filename>suspend</filename>, якщо у файлі <filename>gdm.conf</filename> вказано SuspendCommand." - -#: ../C/gdm.xml:5771(para) -#, fuzzy -msgid "<filename>system</filename>, if SystemMenu is specified in the GDM configuration." -msgstr "<filename>system</filename>, якщо у файлі <filename>gdm.conf</filename> вказано SystemMenu" - -#: ../C/gdm.xml:5775(para) -#, fuzzy -msgid "<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in the GDM configuration." -msgstr "<filename>timed</filename>, якщо у файлі <filename>gdm.conf</filename> TimedLoginEnabled має значення \"true\"." - -#: ../C/gdm.xml:5780(para) -#, fuzzy -msgid "" -"For example: <screen>\n" -"<show modes=\"console\" type=\"system\"/>\n" -"</screen>" -msgstr "Наприклад: <screen><show modes=\"console\" type=\"system\"/></screen>" - -#: ../C/gdm.xml:5787(para) -#, fuzzy -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 "Зауважте, що якщо SystemMenu вимкнено то елементи вимикання, перезавантаження, призупинення, селектор вузлів та налаштовування не відображаються, тому він є глобальним перемикачем. Приклади використання режимів дивіться у стандартних темах." - -#: ../C/gdm.xml:5796(title) -msgid "Normal/Active/Prelight Nodes" -msgstr "Вузли Normal/Active/Prelight" - -#: ../C/gdm.xml:5798(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 "В залежності від типу вузла (за винятком списку користувачів - дивіться вузол Color нижче), можна вказати його колір, шрифт, або зображення у наступних тегах:" - -#: ../C/gdm.xml:5804(para) -msgid "<filename>normal</filename> - normal state." -msgstr "<filename>normal</filename> - звичайний стан." - -#: ../C/gdm.xml:5807(para) -msgid "<filename>active</filename> - when the item has active focus." -msgstr "<filename>active</filename> - стан, коли елемент має фокус вводу." - -#: ../C/gdm.xml:5810(para) -msgid "<filename>prelight</filename> - when the mouse is hovering over the item." -msgstr "<filename>prelight</filename> - коли миша знаходиться над елементом." - -#: ../C/gdm.xml:5815(para) -#, fuzzy -msgid "" -"When item is \"rect\" (alpha can be omitted and defaults to 0.0): <screen>\n" -"<normal color=\"#ffffff\" alpha=\"0.0\">\n" -"</screen>" -msgstr "Якщо елемент - \"rect\" (альфа-канал можна пропустити, типове значення - 0.0): <screen><normal color=\"#ffffff\" alpha=\"0.0\"></screen>" - -#: ../C/gdm.xml:5823(para) -#, fuzzy -msgid "" -"When item is \"label\" <screen>\n" -"<normal color=\"#ffffff\" font=\"Sans 14\"/>\n" -"</screen>" -msgstr "Якщо елемент \"label\": <screen><normal color=\"#ffffff\" font=\"Sans 14\"/></screen>" - -#: ../C/gdm.xml:5830(para) -#, fuzzy -msgid "" -"When the item type is \"pixmap\" or \"SVG\", then the normal, active, and prelight tags specify the images to use as follows: <screen>\n" -"<normal file=\"picture.png\" tint=\"#dddddd\"/>\n" -"</screen>" -msgstr "Коли елемент має тип \"pixmap\" чи \"SVG\", тоді у тегах normal, active, та prelight вказуються зображення наступним чином: <screen><normal file=\"picture.png\" tint=\"#dddddd\"/></screen>" - -#: ../C/gdm.xml:5839(para) -msgid "Note that relative pathnames are assumed to be in the same directory as the theme <filename>.xml</filename> file in <filename><share>/gdm/themes/<theme_name></filename>." -msgstr "Зауважте, що відносні назви шляхів мають бути у тому самому каталозі, що й <filename>.xml</filename> файл теми у <filename><share>/gdm/themes/<theme_name></filename>." - -#: ../C/gdm.xml:5847(title) -msgid "Face Browser Icon/Label Color Nodes" -msgstr "Значок перегляду портретів/вузли кольорів позначки" - -#: ../C/gdm.xml:5849(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:5855(screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" -msgstr "<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>" - -#: ../C/gdm.xml:5862(title) -msgid "Text Node" -msgstr "Текстовий вузол" - -#: ../C/gdm.xml:5864(para) -#, fuzzy -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): <screen>\n" -"<text xml:lang=\"fr\">Option</text>\n" -"</screen>" -msgstr "Текстові теги використовуються у позначках. Вони можуть використовуватись для відображення локалізованого тексту, наприклад (якщо атрибут \"xml:lang\" пропущений, мається припускається локаль C): <screen><text xml:lang=\"fr\">Option</text></screen>" - -#: ../C/gdm.xml:5873(para) -#, fuzzy -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: <screen>\n" -"<text>\"foo<sup>bar</sup>\"</text>\n" -"</screen>" -msgstr "У текстові вузли для позначок ви можете включити розмітку pango, проте слід закодувати її. Наприклад, щоб отримати позначку\"foo<sup>bar</sup>\", слід ввести: <screen><text\">foo&lt;sup&gt;bar&lt;/sup&gt;</text></screen>" - -#: ../C/gdm.xml:5882(para) -msgid "Text nodes can contain the following special character sequences which will be translated as follows:" -msgstr "Текстові вузли можуть містити наступні спеціальні послідовності символів:" - -#: ../C/gdm.xml:5887(para) -#, fuzzy -msgid "%% - A literal % character" -msgstr "символ `'" - -#: ../C/gdm.xml:5890(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 - час годинника. Лише позначки з ідентифікатором \"clock\" будуть оновлюватись кожну секунду. Інші позначки будуть містити статичне значення часу." - -#: ../C/gdm.xml:5895(para) -msgid "%d - Display name (DISPLAY environment variable)" -msgstr "%d - назва дисплею (змінна оточення DISPLAY)" - -#: ../C/gdm.xml:5898(para) -msgid "%h - Hostname (gethostname output)" -msgstr "%h - назва вузла (вивід gethostname)" - -#: ../C/gdm.xml:5901(para) -msgid "%m - Machine name (uname.machine output)" -msgstr "%m - назва машини (вивід uname.machine)" - -#: ../C/gdm.xml:5904(para) -#, fuzzy -msgid "%n - Node name (uname.nodename output)" -msgstr "n назва вузла (тобто, назва вузла без .domain)" - -#: ../C/gdm.xml:5907(para) -msgid "%o - Domain name (getdomainname output)" -msgstr "%o - назва домену (вивід getdomainname)" - -#: ../C/gdm.xml:5910(para) -msgid "%r - Release name (uname.release output)" -msgstr "%r - назва випуску (вивід uname.release)" - -#: ../C/gdm.xml:5913(para) -msgid "%s - System name (uname.sysname output)" -msgstr "%s - назва системи (вивід uname.sysname)" - -#: ../C/gdm.xml:5916(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 "%t - поточне значення затримки для входу із затримкою з конфігураційного файл (0 - якщо вимкнено), за яким йде слово \"seconds\", якщо значення більше ніж 1 або слово \"second\" якщо значення дорівнює 1. Ця символьна послідовність призначена для внутрішнього використання всередині для відображення повідомлень типу \"позначка часу\", що автоматично оновлюються кожної секунди." - -#: ../C/gdm.xml:5924(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 "%u - ім'я користувача для входу із затримкою з конфігураційного файлу (порожнє, якщо вимкнено) Ця символьна послідовність призначена для внутрішнього використання всередині для відображення повідомлень типу \"позначка часу\", що автоматично оновлюються кожної секунди." - -#: ../C/gdm.xml:5930(para) -msgid "" -"\\n" -" - Carriage return" -msgstr "" -"\\n" -" - переведення каретки" - -#: ../C/gdm.xml:5933(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:5941(title) -msgid "Stock" -msgstr "Stock" - -#: ../C/gdm.xml:5943(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 "Деякі загальні локалізовані позначки можна вказувати через теги з набору. Якщо вказано тег \"stock\", тоді тег \"text\" ігнорується. Слід використовувати позначки з набору позначок, замість призначення перекладеного значення у тему. При цьому прискорюється час завантаження та краще відбувається переклад. Можливі значення:" - -#: ../C/gdm.xml:5952(para) -#, fuzzy -msgid "<filename>cancel</filename>, _(\"_Cancel\"" -msgstr "<filename>cancel</filename>, _(\"_Cancel\")" - -#: ../C/gdm.xml:5955(para) -#, fuzzy -msgid "<filename>caps-lock-warning</filename>, _(\"Caps Lock key is on.\"" -msgstr "<filename>caps-lock-warning</filename>, _(\"You've got capslock on!\")" - -#: ../C/gdm.xml:5959(para) -#, fuzzy -msgid "<filename>chooser</filename>, _(\"Remote Login via _XDMCP\"" -msgstr "<filename>chooser</filename>, _(\"_XDMCP Chooser\")" - -#: ../C/gdm.xml:5962(para) -#, fuzzy -msgid "<filename>config</filename>, _(\"_Configure\"" -msgstr "<filename>cancel</filename>, _(\"_Cancel\")" - -#: ../C/gdm.xml:5965(para) -#, fuzzy -msgid "<filename>disconnect</filename>, _(\"D_isconnect\"" -msgstr "<filename>disconnect</filename>, _(\"D_isconnect\")" - -#: ../C/gdm.xml:5968(para) -#, fuzzy -msgid "<filename>halt</filename>, _(\"Shut _Down\"" -msgstr "<filename>halt</filename>, _(\"Shut_down\")" - -#: ../C/gdm.xml:5971(para) -#, fuzzy -msgid "<filename>language</filename>, _(\"_Language\"" -msgstr "<filename>language</filename>, _(\"_Language\")" - -#: ../C/gdm.xml:5974(para) -#, fuzzy -msgid "<filename>ok</filename>, _(\"_OK\"" -msgstr "<filename>ok</filename>, _(\"_OK\")" - -#: ../C/gdm.xml:5977(para) -#, fuzzy -msgid "<filename>quit</filename>, _(\"_Quit\"" -msgstr "<filename>quit</filename>, _(\"_Quit\")" - -#: ../C/gdm.xml:5980(para) -#, fuzzy -msgid "<filename>reboot</filename>, _(\"_Restart\"" -msgstr "<filename>reboot</filename>, _(\"_Reboot\")" - -#: ../C/gdm.xml:5983(para) -#, fuzzy -msgid "<filename>session</filename>, _(\"_Session\"" -msgstr "<filename>session</filename>, _(\"_Session\")" - -#: ../C/gdm.xml:5986(para) -#, fuzzy -msgid "<filename>suspend</filename>, _(\"Sus_pend\"" -msgstr "<filename>suspend</filename>, _(\"Sus_pend\")" - -#: ../C/gdm.xml:5989(para) -#, fuzzy -msgid "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\"" -msgstr "<filename>system</filename>, _(\"_Actions\") (Formerly \"S_ystem\")" - -#: ../C/gdm.xml:5993(para) -#, fuzzy -msgid "<filename>timed-label</filename>, _(\"User %u will login in %t\"" -msgstr "<filename>timed-label</filename>, _(\"User %s will login in %d seconds\")" - -#: ../C/gdm.xml:5997(para) -#, fuzzy -msgid "<filename>username-label</filename>, _(\"Username:\"" -msgstr "<filename>username-label</filename>, _(\"Username:\")" - -#: ../C/gdm.xml:6000(para) -#, fuzzy -msgid "<filename>welcome-label</filename>, _(\"Welcome to %n\"" -msgstr "<filename>welcome-label</filename>, _(\"Welcome to %h\")" - -#: ../C/gdm.xml:6004(para) -#, fuzzy -msgid "" -"For example: <screen>\n" -"<stock type=\"welcome-label\">\n" -"</screen>" -msgstr "Наприклад: <screen><stock type=\"welcome-label\"/></screen>" - -#: ../C/gdm.xml:6013(title) -msgid "Custom Widgetry" -msgstr "Власні віджети" - -#: ../C/gdm.xml:6015(para) -msgid "Currently there is one item which can be 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 <filename><ServAuthDir>/<display>.GreeterInfo</filename> as <filename><list id>=<listitem id></filename>." -msgstr "Наразі є один елемент, який може налаштовуватись - це список елементів. Якщо треба запитати у користувача додаткову інформацію, таку як вибір місця входу з і списку, або встановити власні сеанси входу ви можете налаштувати елемент списку та додати дочірній елемент списку, який описує вибір. Кожен елемент списку повинен мати ідентифікатор та дочірній елемент text. Вибір буде записано у файл <filename><ServAuthDir>/<display>.GreeterInfo</filename> у вигляді <filename><list id>=<listitem id></filename>." - -#: ../C/gdm.xml:6026(para) -msgid "For example suppose we are on display :0, <filename>ServAuthDir</filename> is <filename><var>/gdm</filename> and we have the following in the theme:" -msgstr "Наприклад, припустимо, ви на дисплеї :0, <filename>ServAuthDir</filename> дорівнює <filename><var>/gdm</filename> та у вас наступна тема:" - -#: ../C/gdm.xml:6033(screen) -#, fuzzy, 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 "" -"\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" -" " - -#: ../C/gdm.xml:6045(para) -#, fuzzy -msgid "" -"Then if the user chooses 'Foo' then <filename><var>/gdm/:0.GreeterInfo</filename> will contain: <screen>\n" -"custom-config=foo\n" -"</screen>" -msgstr "Якщо користувач обере 'Foo', тоді <filename><var>/gdm/:0.GreeterInfo</filename> буде містити: <screen>custom-config=foo</screen>" - -#: ../C/gdm.xml:6057(title) -msgid "Accessibility" -msgstr "Спеціальні можливості" - -#: ../C/gdm.xml:6058(para) -msgid "GDM supports \"Accessible Login\" to allow users to log in to their desktop session even if they cannot easily use the screen, mouse, or keyboard in the usual way. Only the \"Standard Greeter\" supports accessibility, so use this login GUI for accessibility support. This is done by specifying the \"Standard Greeter\" in the \"Local\" tab for the console display and specifying the \"Standard Greeter\" in the \"Remote\" tab for remote displays. Or you can modify the <filename>Greeter</filename> configuration option by hand to be <command>gdmlogin</command>." -msgstr "" - -#: ../C/gdm.xml:6070(para) -#, fuzzy -msgid "The Standard Greeter supports the ability to launch assistive technologies at login time via configurable \"gestures\" from the standard keyboard, pointing device, or switch device attached to the USB or PS/2 mouse port. Also the user can change the visual appearance of the login UI before logging in, for instance to use a higher-contrast color scheme for better visibility." -msgstr "GDM підтримує \"Вхід зі спеціальним можливостями\", що дозволяє користувачам входити у їх сеанси навіть, якщо вони не можуть використовувати екран, мишу, чи клавіатуру звичайним способом. Ця функція дозволяє користувачу запускати спеціальні можливості під час входу використовуючи спеціальні \"жести\" на стандартній миші та клавіатурі, пристроїв вказування, чи перемикачі приєднані до USB чи порту PS/2 миші. Це також дозволяє користувачу змінити візуальне представлення графічного інтерфейсу входу перед входом у сеанс, наприклад, для використання схеми з високим контрастом для кращої видимості. GDM підтримує лише спеціальні можливості з GTK+ Greeter, тому параметр \"Greeter\" у gdm.conf повинен мати значення GTK+ Greeter \"gdmlogin\"." - -#: ../C/gdm.xml:6080(title) -msgid "Accessibility Configuration" -msgstr "Налаштовування спеціальних можливостей" - -#: ../C/gdm.xml:6081(para) -#, fuzzy -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 configuration, AccessKeyMouseEvents and AccessDwellMouseEvents." -msgstr "Якщо увімкнено вхід з використанням спеціальних можливостей, системний адміністратор повинен вручну внести декілька змін у типову конфігурацію змінивши три конфігураційні файли, що зберігаються у gdm.conf, AccessKeyMouseEvents та AccessDwellMouseEvents." - -#: ../C/gdm.xml:6089(para) -#, fuzzy -msgid "In order to allow users to change the color and contrast scheme of the login dialog, make sure the <filename>AllowThemeChange</filename> parameter in the GDM configuration is set to \"true\"." -msgstr "Щоб дозволити користувачам змінювати колір та контраст діалогового вікна входу, встановіть значення \"true\" параметру \"AllowThemeChange\" у gdm.conf." - -#: ../C/gdm.xml:6096(para) -#, fuzzy -msgid "To restrict user changes to the visual appearance to a subset of available themes, the <filename>GtkThemesToAllow</filename> parameter in the GDM configuration can be set to a list of acceptable themes separated by commas. For example:" -msgstr "Щоб обмежити користувачам зміни зовнішнього вигляду набором наперед заданих тем, параметру \"GtkThemesToAllow\" у gdm.conf слід призначити список допустимих тем, елементи списку мають розділятись комами. Наприклад:" - -#: ../C/gdm.xml:6103(screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"GtkThemesToAllow=HighContrast,HighContrastInverse\n" -msgstr "GtkThemesToAllow=HighContrast,HighContrastInverse" - -#: ../C/gdm.xml:6107(para) -#, fuzzy -msgid "To enable the use of assistive technologies such as the Onscreen Keyboard, Screen Reader, or Magnifier, the <filename>AddGtkModules</filename> parameter in the GDM configuration must be uncommented and set to \"true\". Also the <filename>GtkModulesList</filename> parameter must be uncommented and set as follows:" -msgstr "Щоб увімкнути такі допоміжні технології, як Екранна клавіатура, Читання екрану, чи Екранну лупа, слід розкоментувати параметр \"AddGtkModules\" у gdm.conf та встановитизначення \"true\". Також слід розкоментувати параметр \"GtkModulesList\" та встановити наступне значення:" - -#: ../C/gdm.xml:6116(screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener\n" -msgstr "GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener" - -#: ../C/gdm.xml:6120(para) -#, fuzzy -msgid "System administrators may wish to load only the minimum subset of these modules which is required to support their user base. Depending on the end-user needs, not all of the above GtkModules may need to be loaded. If your end-users need the integrated Screen Reader and Magnifier, you must include \"gail\" and \"atk-bridge\". If your end-users will be using a pointing device without buttons or switches, include \"dwellmouselistener\". If some of your users will use pointing devices with switches, alternative physical keyboards, or switch/button devices, include \"keymouselistener\". Including all four is suitable for most system configurations. The Onscreen Keyboard can operate without gail and atk-bridge, but with a reduced feature set; for optimum accessibility we recommend including both gail and atk-bridge." -msgstr "Системні адміністратори можуть налаштувати gdm, щоб завантажувався мінімальний набір цих модулів, які необхідні для підтримки їх користувачів. В залежності від потреб користувачів, не усі з GtkModules потрібно завантажувати. Якщо користувачам потрібна інтегрована підтримка програми читання екрану та екранної лупи, слід включити \"gail\" та \"atk-bridge\". Якщо користувачі будуть використовувати пристрої вказування буз кнопок чи перемикачів, включіть \"dwellmouselistener\". Якщо деякі з ваших користувачів будуть використовувати пристрої вказування з перемикачами, альтернативними фізичними клавіатурами, чи пристроями перемикання/кнопками, включіть \"keymouselistener\". Включення усіх чотирьох параметрів підходить для більшості конфігурацій. Екранна клавіатура може працювати навіть без gail чи atk-bridge, але з обмеженою функціональністю; для оптимальної функціональності рекомендується включати gail та atk-bridge." - -#: ../C/gdm.xml:6137(para) -#, fuzzy -msgid "Once \"keymouselistener\" and/or \"dwellmouselistener\" have been added to the GtkModules loaded by GDM, you can assign end-user actions with the launching of specific assistive technologies. These gesture associations are contained in files AccessKeyMouseEvents and AccessDwellMouseEvents, respectively. Both files are located in the <etc>/gdm/modules directory. The gesture format is described in the two configuration files." -msgstr "Якщо \"keymouselistener\" та/або \"dwellmouselistener\" додані до GtkModules що завантажуються GDM, ви можете призначити дії для запуску певних спеціальних можливостей. Дії пов'язані з жестами містяться у файлах AccessKeyMouseEvents та AccessDwellMouseEvents, відповідно.Формат жестів описано у двух конфігураційних файлах." - -#: ../C/gdm.xml:6148(para) -#, fuzzy -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 Xserver command line for gestures to work properly." -msgstr "Зміст файлу AccessKeyMouseEvents керує keymouselistener Gesture Listener та використовується для визначення натискання на клавіші, кнопки миші, або послідовностей пристрою XInput, які можна використовувати для запуску програм, що потрібні для спеціальних можливостей. Для зменшення ймовірності випадкового запуску, ці 'жести' можуть бути пов'язані з численними натисканнями перемикачів та/або мінімальною тривалістю натискання." - -#: ../C/gdm.xml:6160(para) -#, fuzzy -msgid "The DwellKeyMouseEvents file controls the dwellmouselistner and supports gestures that involve only 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. 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 "Файл DwellKeyMouseEvents керує dwellmouselistner та підтримує жести, які включають дише рухи пристроєм вказування, таким як системна миша чи альтернативний пристрій вказування, такий як трекбол. Усі жести вказуються з однаковим синтаксисом; тобто, немає різниці між жестом 'мишею' та рухом альтернативним пристроєм вводу." - -#: ../C/gdm.xml:6170(para) -#, fuzzy -msgid "Motion gestures are defined as \"crossing events\" into and out of the login dialog window. If the \"dwellmouselistener\" GtkModule is loaded, alternative pointing devices are temporarily \"latched\" to the core pointer, such that motion from alternative devices results in movement of the onscreen pointer." -msgstr "Жести рухами визначені як \"перехресні події\" у діалоговому вікні входу та поза ним. Якщо 'dwellmouselistener' GtkModule завантажений, альтернативний вказівний пристрій тимчасово \"закритий\", такий рух альтернативного пристрою призводить до переміщення екранного вказівника." - -#: ../C/gdm.xml:6179(para) -msgid "In order to use text-to-speech services at login time (for instance, when using the Screen Reader in speech mode) on some operating systems, the GDM user must be made a member of the \"audio\" group" -msgstr "Для використання служби промови тексту під час входу (наприклад, при використанні програми читання екрану в режимі speech) на деяких операційних системах, GDM user must be made a member of the \"audio\" group" - -#: ../C/gdm.xml:6186(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:6197(para) -msgid "There are some issues that cause users to have problems getting the gesture listeners to work. It is recommended that people use GDM version 2.8.0.5 or later for best results. Some 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. Some versions of GOK and gnopernicus will not launch unless the \"gdm\" user has a writable home directory. If you see an hourglass cursor when you complete a gesture but the program does not start, then you are likely having this problem. It should be considered a bug for AT programs to require having a writable home directory, so please file a bug with the AT program if you encounter this problem. Also note that some input devices require X server configuration before GDM will recognize them." -msgstr "" - -#: ../C/gdm.xml:6218(title) -msgid "Accessibility Login Sound Configuration" -msgstr "Налаштовування звуку спеціальних пожливостей" - -#: ../C/gdm.xml:6219(para) -#, fuzzy -msgid "By default, GDM requires a media application such as \"sox\" to be present to play sounds for successful or failed login. GDM defaults the location of this application to <filename><bin>/play</filename> (or <filename><bin>/audioplay</filename> on Solaris. This can be changed via the SoundProgram GDM configuration option. Typically most text-to-speech programs (such as ORCA or Gnopernicus) use a separate mechanism to play audio." -msgstr "Звичайно, для відтворення звуку gdm потрібна програма для роботи зі звуком, такої як \"sox\". Типове розташування цієї програми <filename>/usr/bin/play</filename> і визначається параметром конфігурації SoundProgram у файлі <filename>gdm.conf</filename>. Це значення можна змінити, змінивши значення параметра у файлі <filename>gdm.conf</filename>." - -#: ../C/gdm.xml:6234(title) -msgid "Solaris Specific Features" -msgstr "Спеціальні функції Solaris" - -#: ../C/gdm.xml:6237(title) -msgid "Solaris Configuration" -msgstr "Налаштовування Solaris" - -#: ../C/gdm.xml:6238(para) -msgid "" -"On Solaris, the following configuration is recommended. This turns on IPv6 and also turns on PreFetch for performance benefit. <screen>\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\n" -"</screen>" -msgstr "" - -#: ../C/gdm.xml:6250(para) -msgid "Configuring GDM with the \"--with-post-path=/usr/openwin/bin\" on Solaris is recommended for access to programs like Xnest." -msgstr "" - -#: ../C/gdm.xml:6258(title) -msgid "Solaris /etc/logindevperm" -msgstr "Solaris /etc/logindevperm" - -#: ../C/gdm.xml:6259(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:6264(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:6271(screen) -#, no-wrap -msgid "" -"\n" -"/dev/console 0600 /dev/sound/* # audio devices\n" -msgstr "" -"\n" -"/dev/console 0600 /dev/sound/* # звукові пристрої\n" - -#: ../C/gdm.xml:6275(para) -msgid "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:6288(title) -msgid "Solaris Automatic Login" -msgstr "Автоматичний вхід на Solaris" - -#: ../C/gdm.xml:6289(para) -msgid "Automatic login does not work on Solaris 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 unsecure way to set up your computer." -msgstr "" - -#: ../C/gdm.xml:6300(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:6308(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:6316(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:6324(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:6329(screen) -#, no-wrap -msgid "" -"\n" -" gdm-autologin session required pam_unix_session.so.1\n" -msgstr "" - -#: ../C/gdm.xml:6335(title) -msgid "Other Solaris Features" -msgstr "Інші особливості Solaris" - -#: ../C/gdm.xml:6336(para) -msgid "GDM supports a few features specific to Solaris, as follows:" -msgstr "GDM підтримує деякі специфічні властивості Solaris:" - -#: ../C/gdm.xml:6340(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:6346(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:6355(para) -#, fuzzy -msgid "Solaris supports the <filename>/etc/default/login</filename> interface, which affects the <filename>DefaultPath</filename>, <filename>RootPath</filename>, <filename>PasswordRequired</filename>, and <filename>AllowRemoteRoot</filename> options as described in the \"Configuration\" section." -msgstr "Сценарії <filename>Init</filename>, <filename>PreSession</filename>, <filename>PostSession</filename>, та <filename>PostLogin</filename> описуються далі у цьому розділі." - -#: ../C/gdm.xml:6367(title) -msgid "Example Configurations" -msgstr "Приклади конфігурацій" - -#: ../C/gdm.xml:6369(para) -msgid "This section has some example configurations that are useful for various setups." -msgstr "У цій секції наведені приклади конфігурацій, які корисні у різних випадках." - -#: ../C/gdm.xml:6375(title) -msgid "Terminal Lab With One Server" -msgstr "Термінальна лабораторія з одним сервером" - -#: ../C/gdm.xml:6377(para) -#, fuzzy -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 <filename>xterminal</filename> and let's call the server machine <filename>appserver</filename>. You install GDM on both." -msgstr "Скажімо, ви бажаєте створити лабораторію з X-терміналами, які з'єднуються з одним головним сервером. Тож будемо називати X-термінал <filename>xterminal</filename>, а сервер <filename>appserver</filename>. GDM треба встановити на обох." - -#: ../C/gdm.xml:6384(para) -#, fuzzy -msgid "" -"On <filename>appserver</filename> you enable XDMCP, so you have <screen>\n" -"[xdmcp]\n" -"Enable=true\n" -"</screen> If you want no local screens here, you can then make the <filename>[servers]</filename> section empty." -msgstr "" -"На <filename>appserver</filename> треба увімкнути XDMCP, тож встановіть <screen>\n" -"[xdmcp]\n" -"Enable=true\n" -" </screen> Якщо у цій системі не буде локального дисплею, можна залишити розділ <filename>[servers]</filename> порожнім." - -#: ../C/gdm.xml:6394(para) -#, fuzzy -msgid "" -"On the <filename>xterminal</filename> you disable XDMCP (you don't want anyone to connect to the xterminal really). You will add a server type perhaps called <filename>Terminal</filename> as follows: <screen>\n" -"[server-Terminal]\n" -"name=Terminal server\n" -"command=/path/to/X -terminate\n" -"flexible=false\n" -"handled=false\n" -"</screen> This definition should in fact be included in the standard configuration file. Notice that we made the <filename>handled</filename> key false since we don't want GDM to handle this server localy. Also note that we have not yet added the <filename>-query</filename> argument, you can add that here, or in the <filename>[servers]</filename> section. We'll define our local servers as follows: <screen>\n" -"[servers]\n" -"0=Terminal -query appserver\n" -"</screen> This will run a direct XDMCP query to the server named <filename>appserver</filename>." -msgstr "" -"На <filename>xterminal</filename> вимикаємо XDMCP (до xterminal ніхто не повинен підключатись). Додайте сервер, що називається <filename>Terminal</filename>: <screen>\n" -"[server-Terminal]\n" -"name=Terminal server\n" -"command=/usr/X11R6/bin/X -terminate\n" -"flexible=false\n" -"handled=false\n" -" </screen> Це визначення фактично буде включено у стандартний конфігураційний файл. Зауважте, що ключ <filename>handled</filename> має значення false, тому що GDM не повинен запускати цей сервер локально. Також заважте, що не додано аргумент <filename>-query</filename>, його можна додати тут, або у розділі <filename>[servers]</filename>. Локальні сервери визначаються наступним чином: <screen>\n" -"[servers]\n" -"0=Terminal -query appserver\n" -" </screen> Це призводить до запуску прямого запиту XDMCP до сервера з назвою <filename>appserver</filename>." - -#: ../C/gdm.xml:6422(title) -msgid "Terminal Lab With Two Or More Servers" -msgstr "Термінальна лабораторія з двома або кількома серверами" - -#: ../C/gdm.xml:6424(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 <filename>appserverone</filename> and <filename>appservertwo</filename>. Again we'll call our example X terminal server <filename>xterminal</filename>. 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 "Скажімо ви хочете створити лабораторію з X-терміналами, які з'єднані з кількома серверами. Тож створимо їх <filename>appserverone</filename> та <filename>appservertwo</filename>. Знову назвемо наш сервер X-терміналів <filename>xterminal</filename>. Параметри на обох серверах такі ж як і у випадку з одним сервером. Не слід явно вмикати непрямі запити до сервера, бо на X-терміналах локально запускається селектор вузлів." - -#: ../C/gdm.xml:6435(para) -#, fuzzy -msgid "" -"So on the <filename>xterminal</filename> you again disable XDMCP. You will add a server type perhaps called <filename>Chooser</filename> as follows: <screen>\n" -"[server-Chooser]\n" -"name=Chooser server\n" -"command=/path/to/X\n" -"flexible=false\n" -"chooser=true\n" -"</screen> And again this definition should in fact be included in the standard configuration file. Notice that we made the <filename>chooser</filename> 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: <screen>\n" -"[servers]\n" -"0=Chooser\n" -"</screen>" -msgstr "" -"На <filename>xterminal</filename> знову вимкніть XDMCP. Додайте сервер з назвою <filename>Chooser</filename>: <screen>\n" -"[server-Chooser]\n" -"name=Chooser server\n" -"command=/usr/X11R6/bin/X\n" -"flexible=false\n" -"chooser=true\n" -" </screen> І знову це визначення фактично слід включати у стандартний конфігураційний файл. Зауважте, що ключ <filename>chooser</filename> має значення true. Це приводить до запуску селектора вузлів XDMCP, і коли користувач вибере вузол GDM буде зроблено запит до цього вузлі. Потім визначаються локальні сервери: <screen>\n" -"[servers]\n" -"0=Chooser\n" -" </screen>" - -#: ../C/gdm.xml:6458(para) -#, fuzzy -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 <filename>[chooser]</filename> section you would have: <screen>\n" -"Hosts=appserverone,appservertwo\n" -"</screen> and any other servers you wish the users to be able to connect to." -msgstr "Селектор вузлів XDMCP на X-терміналі надсилає широкомовні запити для пошуку серверів у мережі. Якщо сервери недоступні для широкомовних запитів, слід вручну їх додати у конфігураційний файл. Тож у розділі <filename>[chooser]</filename> будемо мати: <screen>Hosts=appserverone,appservertwo</screen> та будь-які інші сервери, на які можуть заходити користувачі." - -#: ../C/gdm.xml:6470(para) -#, fuzzy -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 <filename>appserver</filename> and on the X terminals you'd have <screen>\n" -"[servers]\n" -"0=Terminal -indirect appserver\n" -"</screen> This way for example you only have to maintain one <filename>Hosts</filename> entry. However as a disadvantage then, the <filename>appserver</filename> 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 "" -"Іноді потрібно також запускати селектор вузлів і на стороні сервера. Тоді слід налаштувати сервер таким самим чином як у попередньому розділі з одним сервером з вмиканням XDMCP непрямих запитів на <filename>appserver</filename> та на X-терміналах будемо мати <screen>\n" -"[servers]\n" -"0=Terminal -indirect appserver\n" -" </screen> Таким чином ви матимете лише один вузол <filename>Hosts</filename>. Проте є один недолік, <filename>appserver</filename> має бути завжди доступний. Що не підходить для випадків коли у вас декілька серверів та не всі з них увімкнені весь час. Також можна змусити один з X-терміналів обробляти непрямі запити XDMCP та слугувати селектором вузлів для інших X-терміналів." - -#: ../C/gdm.xml:6492(title) -msgid "Troubleshooting" -msgstr "Усунення проблем" - -#: ../C/gdm.xml:6494(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 <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</ulink> or send an email to the <address><email>gdm-list@gnome.org</email></address> mail list." -msgstr "" - -#: ../C/gdm.xml:6504(para) -msgid "If GDM is failing to work properly, it is always a good idea to include debug information. Use the <command>gdmsetup</command> 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 (<filename><var>/log/messages</filename> or <filename><var>/adm/messages</filename> 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:6518(para) -msgid "You should not leave debug on after collecting data. It will clutter your syslog and slow system performance." -msgstr "" - -#: ../C/gdm.xml:6524(title) -msgid "GDM Will Not Start" -msgstr "GDM не запускається" - -#: ../C/gdm.xml:6526(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:6535(para) -msgid "First make sure that the Xserver is configured properly. The GDM configuration file contains a command in the [server-Standard] section that is used for starting the Xserver. Verify that this command works on your system. Running this command from the console should start the Xserver. If it fails, then the problem is likely with your Xserver configuration. Refer to your Xserver error log for an idea of what the problem may be. The problem may also be that your Xserver requires different command-line options. If so, then modify the Xserver command in the GDM configuration file so that it is correct for your system." -msgstr "" - -#: ../C/gdm.xml:6548(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 Xserver and a terminal program, set the shell environment variable DOING_GDM_DEVELOPMENT=1 and run <command><lib>/gdmlogin</command> or <command><lib>/gdmgreeter</command>. 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:6561(para) -msgid "Also make sure that the <filename>/tmp</filename> directory has reasonable ownership and permissions, and that the machine's file system is not full. These problems will cause GDM to fail to start." -msgstr "" - -#: ../C/gdm.xml:6569(title) -msgid "GDM Will Not Access User Settings" -msgstr "GDM не може отримати доступ до параметрів користувача" - -#: ../C/gdm.xml:6571(para) -msgid "GDM saves user settings, such as your default session and default language, in the <filename>~/.dmrc</filename>. Other files, such as the user's <filename>~/.Xauthority</filename> file will also affect login. GDM, by default, is strict about how it tries to access files in the users home directory, and will ignore the file if they do not conform to certain rules. You can use the <filename>RelaxPermissions</filename> 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:6590(title) -msgid "License" -msgstr "Ліцензія" - -#: ../C/gdm.xml:6591(para) -msgid "This program is free software; you can redistribute it and/or modify it under the terms of the <ulink type=\"help\" url=\"gnome-help:gpl\"><citetitle>GNU General Public License</citetitle></ulink> as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version." -msgstr "Ця програма є вільним програмним забезпеченням; ви можете розповсюджувати її ат/чи змінювати на умовах ліцензії <ulink type=\"help\" url=\"gnome-help:gpl\"><citetitle>GNU General Public License</citetitle></ulink> яка опублікована Free Software Foundation; версії 2 цієї ліцензії, або (за вашим бажанням) будь-якої більш пізньої версії." - -#: ../C/gdm.xml:6599(para) -msgid "This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public License</citetitle> for more details." -msgstr "Ця програма поширюється з надією, що буде корисною, але БЕЗ БУДЬ_ЯКИХ ГАРАНТІЙ; навіть без неявної гарантії ПРИДАТНОСТІ ДО ПРОДАЖУ або ВІДПОВІДНОСТІ ПЕВНІЙ МЕТІ. Докладніше про це дивіться у <citetitle>GNU General Public License</citetitle>." - -#: ../C/gdm.xml:6605(para) -msgid "A copy of the <citetitle>GNU General Public License</citetitle> is included as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also obtain a copy of the <citetitle>GNU General Public License</citetitle> from the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://www.fsf.org\">their Web site</ulink> or by writing to <address> Free Software Foundation, Inc. <street>59 Temple Place</street> - Suite 330 <city>Boston</city>, <state>MA</state><postcode>02111-1307</postcode><country>USA</country></address>" -msgstr "Копія <citetitle>GNU General Public License</citetitle> включається як додаток до <citetitle>Довідки користувача GNOME</citetitle>. Також можна отримати копію <citetitle>GNU General Public License</citetitle> від Free Software Foundation відвідавши <ulink type=\"http\" url=\"http://www.fsf.org\">їх веб-сайт</ulink> або написавши за адресою <address> Free Software Foundation, Inc. <street>59 Temple Place</street> - Suite 330 <city>Boston</city>, <state>MA</state><postcode>02111-1307</postcode><country>USA</country></address>" - -#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2. -#: ../C/gdm.xml:0(None) -msgid "translator-credits" -msgstr "Максим Дзюманенко <mvd@mylinux.ua>, 2004, 2006" - diff --git a/docs/zh_CN/.cvsignore b/docs/zh_CN/.cvsignore deleted file mode 100644 index ab4d4d42..00000000 --- a/docs/zh_CN/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -Makefile -Makefile.in -*.out -omf_timestamp diff --git a/docs/zh_CN/figures/gdm_window.png b/docs/zh_CN/figures/gdm_window.png Binary files differdeleted file mode 100644 index 2dc78e34..00000000 --- a/docs/zh_CN/figures/gdm_window.png +++ /dev/null diff --git a/docs/zh_CN/gdm-zh_CN.omf b/docs/zh_CN/gdm-zh_CN.omf deleted file mode 100644 index 466eedbc..00000000 --- a/docs/zh_CN/gdm-zh_CN.omf +++ /dev/null @@ -1,18 +0,0 @@ -<?xml version="1.0" encoding="UTF8"?> <omf> - <resource> - <creator>docs@gnome.org (GDP) </creator> - <maintainer>docs@gnome.org (GDP) </maintainer> - <title>登录屏幕设置手册 2.0.1 版 </title> - <date>2004-01-19 </date> - <version identifier="2.0.1" date="2004-01-19" description="Created for Quicksilver, program version 2.4.2.101"/> - <subject category="GNOME|Applications|System Tools"/> - - <description>登录屏幕设置应用程序用户手册。 </description> - <type>用户指南 </type> - <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/> - <identifier url="gdm.xml"/> - <language code="zh_CN"/> - <relation seriesid="be6a0524-46d3-11d8-983d-e135363498a8"/> - <rights type="GNU FDL" license.version="1.1" holder="Sun Microsystems"/> - </resource> -</omf> diff --git a/docs/zh_HK/.cvsignore b/docs/zh_HK/.cvsignore deleted file mode 100644 index ab4d4d42..00000000 --- a/docs/zh_HK/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -Makefile -Makefile.in -*.out -omf_timestamp diff --git a/docs/zh_HK/figures/gdm_window.png b/docs/zh_HK/figures/gdm_window.png Binary files differdeleted file mode 100644 index 2dc78e34..00000000 --- a/docs/zh_HK/figures/gdm_window.png +++ /dev/null diff --git a/docs/zh_HK/gdm-zh_HK.omf b/docs/zh_HK/gdm-zh_HK.omf deleted file mode 100644 index 6ac01adc..00000000 --- a/docs/zh_HK/gdm-zh_HK.omf +++ /dev/null @@ -1,18 +0,0 @@ -<?xml version="1.0" encoding="UTF8"?> <omf> - <resource> - <creator>docs@gnome.org (GDP) </creator> - <maintainer>docs@gnome.org (GDP) </maintainer> - <title>登入畫面設定手冊 V2.0.1 </title> - <date>2004 年 1 月 19 日 </date> - <version identifier="2.0.1" date="2004-01-19" description="Created for Quicksilver, program version 2.4.2.101"/> - <subject category="GNOME|Applications|System Tools"/> - - <description>「登入畫面設定」應用程式的使用者手冊。 </description> - <type>使用者指南 </type> - <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/> - <identifier url="gdm.xml"/> - <language code="zh_HK"/> - <relation seriesid="be6a0524-46d3-11d8-983d-e135363498a8"/> - <rights type="GNU FDL" license.version="1.1" holder="Sun Microsystems"/> - </resource> -</omf> diff --git a/docs/zh_TW/.cvsignore b/docs/zh_TW/.cvsignore deleted file mode 100644 index ab4d4d42..00000000 --- a/docs/zh_TW/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -Makefile -Makefile.in -*.out -omf_timestamp diff --git a/docs/zh_TW/figures/gdm_window.png b/docs/zh_TW/figures/gdm_window.png Binary files differdeleted file mode 100644 index 2dc78e34..00000000 --- a/docs/zh_TW/figures/gdm_window.png +++ /dev/null diff --git a/docs/zh_TW/gdm-zh_TW.omf b/docs/zh_TW/gdm-zh_TW.omf deleted file mode 100644 index 3c6cf1e6..00000000 --- a/docs/zh_TW/gdm-zh_TW.omf +++ /dev/null @@ -1,18 +0,0 @@ -<?xml version="1.0" encoding="UTF8"?> <omf> - <resource> - <creator>docs@gnome.org (GDP) </creator> - <maintainer>docs@gnome.org (GDP) </maintainer> - <title>登入畫面設定手冊 V2.0.1 </title> - <date>2004 年 1 月 19 日 </date> - <version identifier="2.0.1" date="2004-01-19" description="Created for Quicksilver, program version 2.4.2.101"/> - <subject category="GNOME|Applications|System Tools"/> - - <description>「登入畫面設定」應用程式的使用者手冊。 </description> - <type>使用者指南 </type> - <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/> - <identifier url="gdm.xml"/> - <language code="zh_TW"/> - <relation seriesid="be6a0524-46d3-11d8-983d-e135363498a8"/> - <rights type="GNU FDL" license.version="1.1" holder="Sun Microsystems"/> - </resource> -</omf> |
