3
"Project-Id-Version: gdm help\n"
4
"POT-Creation-Date: 2008-12-08 20:07+0000\n"
5
"PO-Revision-Date: 2008-12-10 14:08+0100\n"
6
"Last-Translator: Luca Ferretti <elle.uca@libero.it>\n"
7
"Language-Team: Italian <tp@lists.linux.it>\n"
9
"Content-Type: text/plain; charset=UTF-8\n"
10
"Content-Transfer-Encoding: 8bit\n"
12
#: C/gdm.xml:13(title)
13
msgid "GNOME Display Manager Reference Manual"
14
msgstr "Manuale di riferimento per GNOME Display Manager"
16
#: C/gdm.xml:17(revnumber)
26
msgid "GDM is the GNOME Display Manager, a graphical login program."
27
msgstr "GDM è il display manager di GNOME, un programma per accessi grafici."
29
#: C/gdm.xml:30(firstname)
33
#: C/gdm.xml:30(othername)
37
#: C/gdm.xml:31(surname)
41
#: C/gdm.xml:33(email)
45
#: C/gdm.xml:37(firstname)
49
#: C/gdm.xml:37(surname)
53
#: C/gdm.xml:39(email)
57
#: C/gdm.xml:43(firstname)
61
#: C/gdm.xml:43(surname)
65
#: C/gdm.xml:45(email)
66
msgid "mccann@jhu.edu"
67
msgstr "mccann@jhu.edu"
69
#: C/gdm.xml:49(firstname)
73
#: C/gdm.xml:49(surname)
77
#: C/gdm.xml:51(email)
78
msgid "rstrode@redhat.com"
79
msgstr "rstrode@redhat.com"
81
#: C/gdm.xml:55(firstname)
85
#: C/gdm.xml:55(surname)
89
#: C/gdm.xml:57(email)
90
msgid "Brian.Cameron@Sun.COM"
91
msgstr "Brian.Cameron@Sun.COM"
101
#: C/gdm.xml:64(holder)
102
msgid "Martin K. Petersen"
103
msgstr "Martin K. Petersen"
105
#: C/gdm.xml:67(year)
109
#: C/gdm.xml:68(year) C/gdm.xml:73(year) C/gdm.xml:79(year)
113
#: C/gdm.xml:69(year) C/gdm.xml:80(year)
117
#: C/gdm.xml:70(holder)
121
#: C/gdm.xml:74(year) C/gdm.xml:83(year)
125
#: C/gdm.xml:75(year) C/gdm.xml:84(year)
129
#: C/gdm.xml:76(holder)
130
msgid "Red Hat, Inc."
131
msgstr "Red Hat, Inc."
133
#: C/gdm.xml:81(year)
137
#: C/gdm.xml:82(year)
141
#: C/gdm.xml:85(holder)
142
msgid "Sun Microsystems, Inc."
143
msgstr "Sun Microsystems, Inc."
146
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."
149
#: C/gdm.xml:12(para)
150
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."
153
#: C/gdm.xml:19(para)
154
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."
157
#: C/gdm.xml:35(para)
158
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"
161
#: C/gdm.xml:55(para)
162
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."
165
#: C/gdm.xml:28(para)
166
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/>"
169
#: C/gdm.xml:90(releaseinfo) C/gdm.xml:101(para)
170
msgid "This manual describes version 2.24.0 of the GNOME Display Manager. It was last updated on 08/27/2008."
171
msgstr "Questo manuale descrive la versione 2.24.0 di GNOME Display Manager. È stato aggiornato l'ultima volta il 27 agosto 2008."
173
#: C/gdm.xml:99(title)
174
msgid "Terms and Conventions Used in This Manual"
175
msgstr "Termini e convenzioni usate in questo manuale"
177
#: C/gdm.xml:106(para)
178
msgid "Chooser - A program used to select a remote host for managing a display remotely on the attached display (<command>gdm-host-chooser</command>)."
179
msgstr "Chooser - Un programma usato per selezionare un host remoto per gestire un display da remoto sul display attaccato (<command>gdm-host-chooser</command>)."
181
#: C/gdm.xml:111(para)
182
msgid "FreeDesktop - The organization providing desktop standards, such as the Desktop Entry Specification used by GDM. <ulink type=\"http\" url=\"http://www.freedesktop.org/\"> http://www.freedesktop.org</ulink>."
183
msgstr "FreeDesktop - L'organizzazione che fornisce standard per l'ambiente grafico, come la specifica Destkop Entry usata da GDM. <ulink type=\"http\" url=\"http://www.freedesktop.org/\"> http://www.freedesktop.org</ulink>."
185
#: C/gdm.xml:117(para)
186
msgid "GDM - GNOME Display Manager. Used to describe the software package as a whole."
187
msgstr "GDM - GNOME Display Manager. Usato per descrivere il pacchetto software nella sua interezza."
189
#: C/gdm.xml:122(para)
190
msgid "Greeter - The graphical login window (<command>gdm-simple-greeter</command>)."
191
msgstr "Greeter - La finestra di accesso grafico (<command>gdm-simple-greeter</command>)."
193
#: C/gdm.xml:126(para)
194
msgid "PAM - Pluggable Authentication Mechanism"
195
msgstr "PAM - Pluggable Authentication Mechanism"
197
#: C/gdm.xml:130(para)
198
msgid "XDMCP - X Display Manage Protocol"
199
msgstr "XDMCP - X Display Manage Protocol"
201
#: C/gdm.xml:134(para)
202
msgid "Xserver - An implemention of the X Window System. For example the Xorg webserver provided by the X.org Foundation <ulink type=\"http\" url=\"http://www.x.org/\">http://www.x.org</ulink>."
203
msgstr "Xserver - Una implementazione del X Window System. Per esempio il webserver Xorg fornito dala X.org Foundation <ulink type=\"http\" url=\"http://www.x.org/\">http://www.x.org</ulink>"
205
#: C/gdm.xml:140(para)
206
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>/usr/share/pixmaps</filename> if GDM was configured with <command>--prefix=/usr</command>."
207
msgstr "I percorsi che cominciano con una parola tra parentesi angolari sono relativi al prefisso di installazione. Per esempio <filename><share>/pixmaps/</filename> fa riferimento a <filename>/usr/share/pixmaps</filename> se GDM è stato configurato con <command>--prefix=/usr</command>."
209
#: C/gdm.xml:151(title)
213
#: C/gdm.xml:154(title)
215
msgstr "Introduzione"
217
#: C/gdm.xml:156(para)
218
msgid "The GNOME Display Manager (GDM) is a display manager that implements all significant features required for managing attached and remote displays. GDM was written from scratch and does not contain any XDM or X Consortium code."
219
msgstr "Lo GNOME Display Manager (GDM) è un display manager che implemente tutte le funzioni significative richieste per la gestione di display collegati e remoti. GDM è stato scritto da zero e non contiene alcun codice derivato da XDM o X Consortium."
221
#: C/gdm.xml:163(para)
222
msgid "Note that GDM is configurable, and many configuration settings have an impact on security. Issues to be aware of are highlighted in this document."
223
msgstr "Notare che GDM è configurabile e molte impostazioni di configurazione hanno un impatto sulla sicurezza. In questo documento, le problematiche di cui è bene essere a conoscenza sono messe in evidenza."
225
#: C/gdm.xml:169(para)
226
msgid "Please note that some Operating Systems configure GDM to behave differently than the default values as described in this document. If GDM does not seem to behave as documented, then check to see if any related configuration may be different than described here."
227
msgstr "Notare che alcuni sistemi operativi configurano GDM per comportarsi diversamente dai valori predefiniti descritti in questo documento. Se GDM non dovesse comportarsi come qui documentato, controllare che ogni configurazione relativa non sia differente da quanto qui descritto."
229
#: C/gdm.xml:176(para)
230
msgid "For further information about GDM, refer to the project website at <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> http://www.gnome.org/projects/gdm</ulink> and the project Wiki <ulink type=\"http\" url=\"http://live.gnome.org/GDM\"> http://live.gnome.org/GDM</ulink>."
231
msgstr "Per maggiori informazioni su GDM, fare riferimento al sito web del progetto presso <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> http://www.gnome.org/projects/gdm</ulink> e al Wiki del progetto presso <ulink type=\"http\" url=\"http://live.gnome.org/GDM\"> http://live.gnome.org/GDM</ulink>."
233
# FIXME da rivedere la forma...
234
#: C/gdm.xml:184(para)
235
msgid "For discussion or queries about GDM, refer to the <address><email>gdm-list@gnome.org</email></address> mail list. This list is archived, and is a good resource to check to seek answers to common questions. This list is archived at <ulink type=\"http\" url=\"http://mail.gnome.org/archives/gdm-list/\"> http://mail.gnome.org/archives/gdm-list/</ulink> and has a search facility to look for messages with keywords."
236
msgstr "Per discudere o fare domande su GDM, fare riferimento alla mailing list <address><email>gdm-list@gnome.org</email></address>. Tutti i messaggi sono archiviati e rappresentano un'ottima risorsa da controllare per trovare risposta a domande comuni. L'archivio della lista è disponibile presso <ulink type=\"http\" url=\"http://mail.gnome.org/archives/gdm-list/\"> http://mail.gnome.org/archives/gdm-list/</ulink> ed è presesnete una funziona ricerca per consultare i messaggi in base a parole chiave."
238
# lo so che è diverso dall'originale, ma non ci sono categorie su bugzilla
241
#: C/gdm.xml:194(para)
242
msgid "Please submit any bug reports or enhancement requests to the \"gdm\" category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\"> http://bugzilla.gnome.org</ulink>."
243
msgstr "Inviare le segnalazioni di bug o le richieste di miglioramenti su <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\"> http://bugzilla.gnome.org</ulink>."
245
#: C/gdm.xml:203(title)
246
msgid "Interface Stability"
247
msgstr "Stabilità dell'interfaccia"
249
#: C/gdm.xml:205(para)
250
msgid "GDM 2.20 and earlier supported stable configuration interfaces. However, the codebase was completely rewritten for GDM 2.22, and is not completely backward compatible with older releases. This is in part because things work differently, so some options just don't make sense, in part because some options never made sense, and in part because some functionaly hasn't been reimplemented yet."
251
msgstr "In GDM 2.20 e predecenti erano supportati configurazioni stabili delle interfacce. Però il codice è stato completamente riscrito per GDM 2.22 e non è del tutto compatibile con i rilasci più vecchi. Questo perché il parte le cose operano in modo diverso, perciò alcune opzioni seplicemente non hanno senso, in parte perché alcune opzioni non avevano mai avuto senso e in parte perchè alcune funzionalità non sono ancora state reimplementate."
253
#: C/gdm.xml:214(para)
254
msgid "Interfaces which continue to be supported in a stable fashion include the Init, PreSession, PostSession, PostLogin, and Xsession scripts. Some daemon configuration options in the <filename><etc>/gdm/custom.conf</filename> file continue to be supported. Also, the <filename>~/.dmrc</filename>, and face browser image locations are still supported."
255
msgstr "Le interfacce che continuano ad essere supportate in modo stabile includono gli script Init, PreSession, PostSession, PostLogin e Xsession. Alcune opzioni di configurazione del demone nel file <filename><etc>/gdm/custom.conf</filename> continuano ad essere supportate. Sono infine ancora supportati il file <filename>~/.dmrc</filename> e le posizioni delle immagini del \"face browser\"."
257
#: C/gdm.xml:223(para)
258
msgid "GDM 2.20 and earlier supported the ability to manage multiple displays with separate graphics cards, such as used in terminal server environments, login in a window via a program like Xnest or Xephyr, the gdmsetup program, XML-based greeter themes, and the ability to run the XDMCP chooser from the login screen. These features are did not get added back during the 2.22 rewrite."
259
msgstr "GDM 2.20 e precedenti supportavano la possibità di gestire display multipli con schede grafiche separate, come in uso un ambienti server di terminale, l'accesso in una finestra per mezzo di programmi come Xnest o Xephyr, il programma gdmsetup, i temi per il greeter basati su XML e la possibilità di esegure il chooser XDMCP dallo schermo di accesso. Tali funzioni non sono state reinserite durante la riscrittura."
261
#: C/gdm.xml:235(title)
262
msgid "Functional Description"
263
msgstr "Descrizione funzionale"
265
# FIXME use <xref> o <ulink>
267
#. TODO - Would be good to discuss D-Bus, perhaps the new GObject model,
268
#. and to explain the reasons why the rewrite made GDM better.
269
#. From a high-level overview perspective, rather than the
270
#. technical aspects.
272
#: C/gdm.xml:246(para)
273
msgid "GDM is responsible for managing displays on the system. This includes authenticating users, starting the user session, and terminating the user session. GDM is configurable and the ways it can be configured are described in the \"Configuring GDM\" section of this document. GDM is also accessible for users with disabilities."
274
msgstr "GDM è responsabile della gestione dei display sul sistema. Ciò include l'autenticazione degli utenti, l'avvio di sessioni utente e la terminazione di sessioni utente. GDM è configurabile nei modi descritti nella sezione «Configurare GDM» di questo documento. GDM risulta inoltre accessibile per utenti con disabilità."
276
#: C/gdm.xml:254(para)
277
msgid "GDM provides the ability to manage the main console display, and displays launched via VT. It is integrated with other programs, such as the Fast User Switch Applet (FUSA) and gnome-screensaver to manage multiple displays on the console via the Xserver Virtual Terminal (VT) interface. It also can manage XDMCP displays."
278
msgstr "GDM fornisce la possibilità di gestire il display di console principale e i display lanciati attraverso VT. Ciò risulta integrato con altri programmi, come l'applet «Cambia utente» e gnome-screensaver per poter gestire display multipli sulla console attraverso l'interfaccia Xserver Virtual Terminal (VT). È anche possibile gestire i display XDMCP."
280
#: C/gdm.xml:262(para)
281
msgid "Regardless of the display type, GDM will do the following when it manages the display. It will start an Xserver process, then run the <filename>Init</filename> script as the root user, and start the greeter program on the display."
282
msgstr "Indipendentemente dal tipo di display, GDM esegue quanto di seguito indicato quando gestisce il display: avvia un processo Xserver, poi avvia lo script <filename>Init</filename> come utente root, infine avvia il programma greeter sul display."
284
# FIXME!! xlink o xref
285
#: C/gdm.xml:269(para)
286
msgid "The greeter program is run as the unpriviledged \"gdm\" user/group. This user and group are described in the \"Security\" section of this document. The main function of the greeter program is to authenticate the user. The authentication process is driven by Pluggable Authentication Modules (PAM). The PAM modules determine what prompts (if any) are shown to the user to authenticate. On the average system, the greeter program will request a username and password for authentication. However some systems may be configured to use alternative mechanisms such as a fingerprint or SmartCard reader. GDM and PAM can be configured to not require any input, which will cause GDM to automatically log in and simply start a session, which can be useful for some environments, such as for kiosks."
287
msgstr "Il programma greeter è eseguito con i pemessi senza privilegi dell'utente/gruppo \"gdm\". Tale utente e gruppo sono descritti nella sezione \"Sicurezza\" di questo documento. La funzione principale del programma greeter è quella di autenticare gli utenti. Il processo di autenticazione è guidato da PAM (Pluggable Authentication Modules). I moduli PAM determinano se e quali prompt sono mostrati all'utente per autenticarsi. Su un sistema tipico, il programma greeter richiede nome utente e password per l'autenticazione. Alcuni sistemi potrebbero però essere configurati per usare meccanismi alternativi come lettori di impronte digitali o SmartCard. GDM e PAM possono essere configurati per non richiedere alcun imput, nel qual caso GDM effettua automaticamente l'accesso e semplicemente avvia una sessione, comportamento utile per alcuni ambienti come i chioschi."
289
# FIXME use xref o ulink
290
#: C/gdm.xml:285(para)
291
msgid "In addition to authentication, the greeter program allows the user to select which session to start and which language to use. Sessions are defined by files that end in the .desktop suffix and more information about these files can be found in the \"Configuration\" section of this document. By default, GDM is configured to display a face browser so the user can select their user account by clicking on an image instead of having to type their username. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI."
292
msgstr "In aggiunta all'autenticazione, il programma greeter consente all'utente di selezionare quale sessione avviare e quale lingua usare. Le sessioni sono definite da file che terminano con il suffisso .desktop; maggiori informazioni sul questi file sono presenti nella sezione «Configurazione» di questo documento. In modo prefinito GDM è configurato per mostrare un \"face browser\" in modo che l'utente possa selezionare il proprio account facendo clic su un'immagine invece che digitando il proprio nome utente. GDM mantiene traccia della sessione e della lingua predefinita degli utente nei file <filename>~/.dmrc</filename> e fa uso di tali valori predefiniti se l'utente non sceglie una sessione o una ligua al momento dell'accesso."
294
#: C/gdm.xml:298(para)
295
msgid "After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, then runs the <filename>PreSession</filename> script as root. After running these scripts, the user session is started. When the user exits their session, the <filename>PostSession</filename> script is run as root. These scripts are provided as hooks for distributions and end-users to customize how sessions are managed. For example, using these hooks you could set up a machine which creates the user's $HOME directory on the fly, and erases it on logout. The difference between the <filename>PostLogin</filename> and <filename>PreSession</filename> scripts is that <filename>PostLogin</filename> is run before the pam_open_session call so is the right place to do anything which should be run before the user session is initialized. The <filename>PreSession</filename> script is called after session initialization."
296
msgstr "Dopo aver autenticato un utente, il demone esegue lo script <filename>PostLogin</filename> come root, quindi lo script <filename>PreSession</filename> come root. Dopo l'esecuzione di questi script viene avviata la sessione utente. Quando l'utente termina la propria sessione, viene eseguito lo script <filename>PostSession</filename> come root. Tali script sono forniti come agganci per i distributori e gli utenti finali al fine di personalizzare la gestione delle sessioni. Per esempio, usando tali agganci è possibile impostare una macchina in modo da creare al volo la directory $HOME dell'utente e di eliminarla al temine della sessione. La differenza tra gli script <filename>PostLogin</filename> e <filename>PreSession</filename> risiede nel fatto che <filename>PostLogin</filename> è eseguito prima della chiamata pam_open_session, rendendolo così il posto adatto per ogni azione che debba essere eseguita prima dell'inizializzazione della sessione utente. Lo script <filename>PreSession</filename> è chiamato dopo l'inizializzazione della sessione."
298
#: C/gdm.xml:318(title)
299
msgid "Greeter Panel"
300
msgstr "Pannello greeter"
302
#: C/gdm.xml:319(para)
303
msgid "The GDM greeter program displays a panel docked at the bottom of the screen which provides additional functionality. When a user is selected, the panel allows the user to select which session, language, and keyboard layout to use after logging in. The keyboard layout selector also changes the keyboard layout used when typing your password. The panel also contains an area for login services to leave status icons. Some example status icons include a battery icon for current battery usage, and an icon for enabling accessibility features. The greeter program also provides buttons which allow the user to shutdown or restart the system. It is possible to configure GDM to not provide the shutdown and restart buttons, if desired. GDM can also be configured via PolicyKit (or via RBAC on Solaris) to require the user have appropriate authorization before accepting the shutdown or restart request."
304
msgstr "Il programma greeter di GDM mostra un pannello agganciato alla parte inferiore dello schermo che fornisce diverse funzionalità. Quando è selezionato un utente, il pannello consente all'utente di selezioanare quale sessione, lingua e disposizione di tastiera usare dopo l'accesso. Il selettore di disposizione di tastiera inoltre cambia la disposizione usata quando si digita la propria password. Il pannello contiene anche un'area in cui i servizi di accesso possono porre le proprie icone di stato. Alcuni esempi di icone di stato includono un'icona batteria che indica l'uso attuale della batteria e un'icona per abilitare le funzioni di accesso universale. Il programma greeter inoltre fornisce che consentono all'utente di spegnere o riavvare il sistema. È possibile configurare GDM in modo da non fornire tali pulsanti, se desiderato. GDM infine può essere configurato attraverso PolicyKit (o attraverso BRAC su Solaris) in modo da richiedere che l'utente abbia l'autorizzazione appropriata prima di accettare le richieste di spegnimento e riavvio."
306
#: C/gdm.xml:337(title)
307
msgid "Accessibility"
308
msgstr "Accesso universale"
311
#: C/gdm.xml:339(para)
312
msgid "GDM supports \"Accessible Login\", allowing users to log into their desktop session even if they cannot easily use the screen, mouse, or keyboard in the usual way. Accessible Technology (AT) features such as an on-screen keyboard, screen reader, screen magnifier, and Xserver AccessX keyboard accessibility are available. It is also possible to enable large text or high contrast icons and controls, if needed."
313
msgstr "GDM supporta il «login accessibile», consentendo agli utenti di eseguire l'accesso nelle loro sessioni desktop anche se non possono facilmente usare lo schermo, il mouse o la tastiera nei modi usuali. Sono disponibili funzioni di tecnologia assistiva come tastiera a schermo, lettore di schermo, ingranditore di schermo e accessibilità della tastiera. È anche possibile abilitare se necessario il testo largo o le icone e i controlli a contrasto elevato."
316
#: C/gdm.xml:349(para)
317
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."
318
msgstr "Su alcuni sistemi è necessario assicurarsi che l'utente GDM sia un membro del gruppo \"audio\" per quei programmi di tecnologia assistiva che richiedono una uscita audio (come testo-a-parlato)."
320
#: C/gdm.xml:357(title)
321
msgid "The GDM Face Browser"
322
msgstr "Il face browser di GDM"
324
#: C/gdm.xml:359(para)
325
msgid "The Face Browser is the interface which allows users to select their username by clicking on an image. This feature can be enabled or disabled via the /apps/gdm/simple-greeter/disable_user_list GConf key and is on by default. When disabled, users must type their complete username by hand. When enabled, it displays all local users which are available for login on the system (all user accounts defined in the /etc/passwd file that have a valid shell and sufficiently high UID) and remote users that have recently logged in. The face browser in GDM 2.20 and earlier would attempt to display all remote users, which caused performance problems in large, enterprise deployments."
328
#: C/gdm.xml:373(para)
329
msgid "The Face Browser is configured to display the users who log in most frequently at the top of the list. This helps to ensure that users who log in frequently can quickly find their login image."
332
#: C/gdm.xml:379(para)
333
msgid "The Face Browser supports \"type-ahead search\" which dynamically moves the face selection as the user types to the corresponding username in the list. This means that a user with a long username will only have to type the first few characters of the username before the correct item in the list gets selected."
336
#: C/gdm.xml:387(para)
337
msgid "The icons used by GDM can be installed globally by the sysadmin or can be located in the user's home directories. If installed globally they should be in the <filename><share>/pixmaps/faces/</filename> directory and the filename should be the name of the user. Face image files should be a standard image that GTK+ can read, such as PNG or JPEG. Face icons placed in the global face directory must be readable to the GDM user."
341
#. TODO - In the old GDM the ~/gnome2/gdm file is used, but the new code
342
#. seems to use ~/.gnome/gdm. Error?
344
#: C/gdm.xml:403(para)
345
msgid "If there is no global icon for the user, GDM will look in the user's $HOME directory for the image file. GDM will first look for the user's face image in <filename>~/.face</filename>. If not found, it will try <filename>~/.face.icon</filename>. If still not found, it will use the value defined for \"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file."
348
#: C/gdm.xml:412(para)
349
msgid "If a user has no defined face image, GDM will use the \"stock_person\" icon defined in the current GTK+ theme. If no such image is defined, it will fallback to a generic face image."
352
#: C/gdm.xml:418(para)
353
msgid "Please note that loading and scaling face icons located in remote user home directories can be a very time-consuming task. Since it not practical to load images over NIS or NFS, GDM does not attempt to load face images from remote home directories."
356
#: C/gdm.xml:425(para)
357
msgid "When the browser is turned on, valid usernames on the computer are exposed for everyone to see. If XDMCP is enabled, then the usernames are exposed to remote users. This, of course, limits security somewhat since a malicious user does not need to guess valid usernames. In some very restrictive environments the face browser may not be appropriate."
360
#: C/gdm.xml:437(title)
365
#. TODO - What XDMCP features actually work? I know that the
366
#. chooser is missing.
368
#: C/gdm.xml:446(para)
369
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."
372
#: C/gdm.xml:455(para)
373
msgid "GDM includes several measures making it more resistant to denial of service attacks on the XDMCP service. A lot of the protocol parameters, handshaking timeouts, etc. can be fine tuned. The default configuration should work reasonably most systems."
376
#: C/gdm.xml:462(para)
377
msgid "GDM by default listens for XDMCP requests on the normal UDP port used for XDMCP, port 177, and will respond to QUERY and BROADCAST_QUERY requests by sending a WILLING packet to the originator."
380
#: C/gdm.xml:468(para)
381
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."
384
#: C/gdm.xml:478(para)
385
msgid "If XDMCP seems to not be working, make sure that all machines are specified in <filename>/etc/hosts</filename>."
388
#: C/gdm.xml:483(para)
389
msgid "Refer to the \"Security\" section for information about security concerns when using XDMCP."
392
#: C/gdm.xml:490(title)
396
#: C/gdm.xml:492(para)
397
msgid "GDM uses syslog to log errors and status. It can also log debugging information, which can be useful for tracking down problems if GDM is not working properly. This can be enabled by starting the GDM daemon with the \"--debug\" option."
400
#: C/gdm.xml:499(para)
401
msgid "Output from the various Xservers is stored in the GDM log directory, which is normally <filename><var>/log/gdm/</filename>. Any Xserver messages are saved to a file associated with the display value, <filename><display>.log</filename>."
404
#: C/gdm.xml:506(para)
405
msgid "The session output is piped through the GDM daemon to the <filename>~/.xsession-errors</filename> file. The file is overwritten on each login, so logging out and logging back into the same user via GDM will cause any messages from the previous session to be lost."
408
#: C/gdm.xml:513(para)
409
msgid "Note that if GDM can not create this file for some reason, then a fallback file will be created named <filename>~/.xsession-errors.XXXXXXXX</filename> where the <filename>XXXXXXXX</filename> are some random characters."
412
#: C/gdm.xml:521(title)
413
msgid "Fast User Switching"
416
#: C/gdm.xml:523(para)
417
msgid "GDM allows multiple users to be logged in at the same time. After one user is logged in, additional, users can log in via the User Switcher on the GNOME Panel, or from the \"Switch User\" button in Lock Screen dialog of GNOME Screensaver. The active session can be changed back and forth using the same mechanism. Note that some distributions may not add the User Switcher to the default panel configuration. It can be added using the panel context menu."
420
#: C/gdm.xml:538(title)
424
#: C/gdm.xml:541(title)
425
msgid "The GDM User And Group"
428
#: C/gdm.xml:543(para)
429
msgid "For security reasons a dedicated user and group id are recommended for proper operation. This user and group are normally \"gdm\" on most systems, but can be configured to any user or group. All GDM GUI programs are run as this user, so that the programs which interact with the user are run in a sandbox. This user and group should have limited privilege."
432
#: C/gdm.xml:552(para)
433
msgid "The only special privilege the \"gdm\" user requires is the ability to read and write Xauth files to the <filename><var>/run/gdm</filename> directory. The <filename><var>/run/gdm</filename> directory should have root:gdm ownership and 1777 permissions."
436
#: C/gdm.xml:560(para)
437
msgid "You should not, under any circumstances, configure the GDM user/group to a user which a user could easily gain access to, such as the user <filename>nobody</filename>. Any user who gains access to an Xauth key can snoop on and control running GUI programs running in the associated or perform a denial-of-service attack on that session. It is important to ensure that the system is configured properly so that only the \"gdm\" user has access to these files and that it is not easy to login to this account. For example, the account should be setup to not have a password or allow non-root users to login to the account."
440
#: C/gdm.xml:573(para)
441
msgid "The GDM greeter configuration is stored in GConf. To allow the GDM user to be able to write configuration, it is necessary for the \"gdm\" user to have a writable $HOME directory. Users may configure the default GConf configuration as desired to avoid the need to provide the \"gdm\" user with a writable $HOME directory. However, some features of GDM may be disabled if it is unable to write state information to GConf configuration."
444
#: C/gdm.xml:585(title)
448
#: C/gdm.xml:587(para)
449
msgid "GDM uses PAM for login authentication. PAM stands for Pluggable Authentication Module, and is used by most programs that request authentication on your computer. It allows the administrator to configure specific authentication behavior for different login programs (such as ssh, login GUI, screensaver, etc.)"
452
#: C/gdm.xml:595(para)
453
msgid "PAM is complicated and highly configurable, and this documentation does not intend to explain this in detail. Instead, it is intended to give an overview of how PAM configuration relates with GDM, how PAM is commonly configured with GDM, and known issues. It is expected that a person needing to do PAM configuration would need to do further reading of PAM documentation to understand how to configure PAM and to understand terms used in this section."
456
#: C/gdm.xml:605(para)
457
msgid "PAM configuration has different, but similar, interfaces on different Operating Systems, so check the <ulink type=\"help\" url=\"man:pam.d\">pam.d</ulink> or <ulink type=\"help\" url=\"man:pam.conf\">pam.conf</ulink> man page for details. Be sure to you read the PAM documentation and are comfortable with the security implications of any changes you intend to make to your configuration."
460
#: C/gdm.xml:615(para)
461
msgid "Note that, by default, GDM uses the \"gdm\" PAM service name for normal login and the \"gdm-autologin\" PAM service name for automatic login. These services may not be defined in your pam.d or pam.conf configured file. If there is no entry, then GDM will use the default PAM behavior. On most systems this should work fine. However, the automatic login feature may not work if the gdm-autologin service is not defined."
464
#: C/gdm.xml:625(para)
465
msgid "The <filename>PostLogin</filename> script is run before pam_open_session is called, and the <filename>PreSession</filename> script is called after. This allows the system administrator to add any scripting to the login process either before or after PAM initializes the session."
468
#: C/gdm.xml:633(para)
469
msgid "If you wish to make GDM work with other types of authentication mechanisms (such as a fingerprint or SmartCard reader), then you should implement this by using a PAM service module for the desired authentication type rather than by trying to modify the GDM code directly. Refer to the PAM documentation on your system. How to do this is frequently discussed on the <address><email>gdm-list@gnome.org</email></address> mail list, so you can refer to the list archives for more information."
472
#: C/gdm.xml:644(para)
473
msgid "PAM does have some limitations regarding being able to work with multiple types of authentication at the same time, like supporting the ability to accept either SmartCard and the ability to type the username and password into the login program. There are techniques that are used to make this work, and it is best to research how this problem is commonly solved when setting up such a configuration."
476
#: C/gdm.xml:653(para)
477
msgid "If automatic login does not work on a system, check to see if the \"gdm-autologin\" PAM stack is defined in the PAM configuration. For this to work, it is necessary to use a PAM module that simply does no authentication, or which simply returns PAM_SUCCESS from all of its public interfaces. Assuming your system has a pam_allow.so PAM module which does this, a PAM configuration to enable \"gdm-autologin\" would look like this:"
480
#: C/gdm.xml:663(screen)
482
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"
485
#: C/gdm.xml:671(para)
486
msgid "The above setup will cause no lastlog entry to be generated. If a lastlog entry is desired, then use the following for session:"
489
#: C/gdm.xml:676(screen)
491
msgid "\n gdm-autologin session required pam_unix_session.so.1\n"
494
#: C/gdm.xml:682(title)
495
msgid "utmp and wtmp"
498
#: C/gdm.xml:684(para)
499
msgid "GDM generates utmp and wtmp User Accounting Database entries upon session login and logout. The utmp database contains user access and accounting information that is accessed by commands such as <command>finger</command>, <command>last</command>, <command>login</command>, and <command>who</command>. The wtmp database contains the history of user access and accounting information for the utmp database. Refer to the <ulink type=\"help\" url=\"man:utmp\">utmp</ulink> and <ulink type=\"help\" url=\"man:wtmp\">wtmp</ulink> man pages on your system for more information."
502
#: C/gdm.xml:699(title)
503
msgid "X Server Authentication Scheme"
506
#: C/gdm.xml:701(para)
507
msgid "X server authorization files are stored in a newly created subdirectory of <filename><var>/run/gdm</filename> at start up. These files contain a is used to store a \"password\" between X clients and the X server. This \"password\" is unqiue for each logged in session, so users from one session can't snoop on users from another."
510
#: C/gdm.xml:709(para)
511
msgid "GDM only supports the MIT-MAGIC-COOKIE-1 Xserver authentication scheme. Normally little is gained from the other schemes, and no effort has been made to implement them so far. Be especially careful about using XDMCP because the Xserver authentication cookie goes over the wire as clear text. If snooping is possible, then an attacker could simply snoop your authentication password as you log in, regardless of the authentication scheme being used. If snooping is possible and undesirable, then you should use ssh for tunneling an X connection rather then using XDMCP. You could think of XDMCP as a sort of graphical telnet, having the same security issues. In most cases, ssh -Y should be prefered over GDM's XDMCP features."
514
#: C/gdm.xml:726(title)
515
msgid "XDMCP Security"
518
#: C/gdm.xml:728(para)
519
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."
522
#: C/gdm.xml:734(para)
523
msgid "XDMCP is primarily useful for running thin clients such as in terminal labs. Those thin clients will only ever need the network to access the server, and so it seems like the best security policy to have those thin clients on a separate network that cannot be accessed by the outside world, and can only connect to the server. The only point from which you need to access outside is the server. This type of set up should never use an unmanaged hub or other sniffable network."
526
#: C/gdm.xml:747(title)
527
msgid "XDMCP Access Control"
530
#: C/gdm.xml:749(para)
531
msgid "XDMCP access control is done using TCP wrappers. It is possible to compile GDM without TCP wrapper support, so this feature may not be supported on some Operating Systems."
534
#: C/gdm.xml:755(para)
535
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"
538
#: C/gdm.xml:762(screen)
540
msgid "\ngdm: .evil.domain\n"
543
#: C/gdm.xml:765(para)
544
msgid "to <filename><etc>/hosts.deny</filename>. You may also need to add"
547
#: C/gdm.xml:769(screen)
549
msgid "\ngdm: .your.domain\n"
552
#: C/gdm.xml:772(para)
553
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."
556
#: C/gdm.xml:781(title)
557
msgid "Firewall Security"
560
#: C/gdm.xml:783(para)
561
msgid "Even though GDM tries to outsmart potential attackers trying to take advantage of XDMCP, it is still advised that you block the XDMCP port (normally UDP port 177) on your firewall unless really needed. GDM guards against denial of service attacks, but the X protocol is still inherently insecure and should only be used in controlled environments. Also each remote connection takes up lots of resources, so it is much easier to do a denial of service attack via XDMCP then a webserver."
564
#: C/gdm.xml:793(para)
565
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."
568
#: C/gdm.xml:800(para)
569
msgid "X is not a very safe protocol for using over the net, and XDMCP is even less safe."
572
#: C/gdm.xml:807(title)
577
#. TODO - Should we say more?
579
#: C/gdm.xml:815(para)
580
msgid "GDM may be configured to use PolicyKit to allow the system administrator to control whether the login screen should provide the shutdown and restart buttons on the greeter screen."
583
#: C/gdm.xml:821(para)
584
msgid "These buttons are controlled by the <filename>org.freedesktop.consolekit.system.stop-multiple-users</filename> and <filename>org.freedesktop.consolekit.system.restart-multiple-users</filename> actions respectively. Policy for these actions can be set up using the polkit-gnome-authorization tool, or the polkit-auth command line program."
587
#: C/gdm.xml:833(title)
588
msgid "RBAC (Role Based Access Control)"
591
#: C/gdm.xml:835(para)
592
msgid "GDM may be configured to use RBAC instead of PolicyKit. In this case, RBAC configuration is used to control whether the login screen should provide the shutdown and restart buttons on the greeter screen."
595
#: C/gdm.xml:841(para)
596
msgid "For example, on Solaris, the \"solaris.system.shutdown\" authorization is used to control this. Simply modify the <filename>/etc/user_attr</filename> file so that the \"gdm\" user has this authorization."
599
#: C/gdm.xml:854(title)
600
msgid "Support for ConsoleKit"
604
#. TODO - Should we update these docs? Probably should mention any
605
#. configuration that users may want to do for using it with GDM?
606
#. If so, perhaps this section should be moved to a subsection of
607
#. the "Configure" section?
609
#: C/gdm.xml:865(para)
610
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."
613
#: C/gdm.xml:873(para)
614
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."
617
#: C/gdm.xml:886(para)
618
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."
621
#: C/gdm.xml:895(para)
622
msgid "When the user chooses to log out, or if GDM or the session quit unexpectedly the user session will be unregistered from ConsoleKit."
625
#: C/gdm.xml:900(para)
626
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."
629
#: C/gdm.xml:910(title)
630
msgid "Configuration"
633
#: C/gdm.xml:912(para)
634
msgid "GDM has a number of configuration interfaces. These include scripting integration points, daemon configuration, greeter configuration, general session settings, integration with gnome-settings-daemon configuration, and session configuration. These types of integration are described in detail below."
637
#: C/gdm.xml:921(title)
638
msgid "Scripting Integration Points"
641
#: C/gdm.xml:923(para)
642
msgid "The GDM script integration points can be found in the <filename><etc>/gdm/</filename> directory:"
645
#: C/gdm.xml:928(screen)
647
msgid "\nXsession\nInit/\nPostLogin/\nPreSession/\nPostSession/\n"
650
#: C/gdm.xml:936(para)
651
msgid "The <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename>, and <filename>PostSession</filename> scripts all work as described below."
654
#: C/gdm.xml:942(para)
655
msgid "For each type of script, the default one which will be executed is called \"Default\" and is stored in a directory associated with the script type. So the default <filename>Init</filename> script is <filename><etc>/gdm/Init/Default</filename>. A per-display script can be provided, and if it exists it will be run instead of the default script. Such scripts are stored in the same directory as the default script and have the same name as the Xserver DISPLAY value for that display. For example, if the <filename><Init>/:0</filename> script exists, it will be run for DISPLAY \":0\"."
658
#: C/gdm.xml:954(para)
659
msgid "All of these scripts are run with root privilege return 0 if run successfully, and a non-zero return code if there was any failure that should cause the login session to be aborted. Also note that GDM will block until the scripts finish, so if any of these scripts hang, this will cause the login process to also hang."
662
#: C/gdm.xml:962(para)
663
msgid "When the Xserver has been successfully started, GDM will run the <filename>Init</filename> script. This script is useful for starting programs that should be run while the login screen is showing, or for doing any special initialization required."
666
#: C/gdm.xml:969(para)
667
msgid "After the user has been successfully authenticated GDM will run the <filename>PostLogin</filename> script. This is done before any session setup has been done, including before the pam_open_session call. This script is useful for doing any session initialization that needs to happen before the session starts. For example, you might setup the user's $HOME directory if needed."
670
#: C/gdm.xml:978(para)
671
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."
674
#: C/gdm.xml:985(para)
675
msgid "After the user session has been initialized, GDM will run the <filename>PreSession</filename> script. This script is useful for doing any session initialization that needs to happen after the session has been initialized. It can be used for session management or accounting, for example."
678
#: C/gdm.xml:993(para)
679
msgid "When the user terminates his session, GDM will run the <filename>PostSession</filename> script. Note that the Xserver will have been stopped by the time this script is run, so it should not be accessed."
682
#: C/gdm.xml:1000(para)
683
msgid "All of the above scripts will set the <filename>$RUNNING_UNDER_GDM</filename> environment variable to <filename>yes</filename>. If the scripts are also shared with other display managers, this allows you to identify when GDM is calling these scripts, so you can run specific code when GDM is used."
686
#: C/gdm.xml:1010(title)
687
msgid "Xsession Script"
690
#: C/gdm.xml:1012(para)
691
msgid "There is also an <filename>Xsession</filename> script located at <filename><etc>/gdm/Xsession</filename> which is called between the <filename>PreSession</filename> and the <filename>PostSession</filename> scripts. This script does not supports per-display like the other scripts. This script is used for actually starting the user session. This script is run as the user, and it will run whatever session was specified by the Desktop session file the user selected to start."
694
#: C/gdm.xml:1025(title)
695
msgid "Daemon Configuration"
698
#: C/gdm.xml:1027(para)
699
msgid "The GDM daemon is configured using the <filename><etc>/gdm/custom.conf</filename> file. Default values are stored in GConf in the <filename>gdm.schemas</filename> file. It is recommended that end-users modify the <filename>/etc/gdm/custom.conf</filename> file because the schemas file may be overwritten when the user updates their system to have a newer version of GDM."
702
#: C/gdm.xml:1037(para)
703
msgid "Note that older versions of GDM supported additional configuration options which are no longer supported in the latest versions of GDM."
706
#: C/gdm.xml:1042(para)
707
msgid "The <filename><etc>/gdm/custom.conf</filename> file is in the <filename>keyfile</filename> format. Keywords in brackets define group sections, strings before an equal sign (=) are keys and the data after equal sign represents their value. Empty lines or lines starting with the hash mark (#) are ignored."
710
#: C/gdm.xml:1050(para)
711
msgid "The <filename>/etc/gdm/custom.conf</filename> supports the \"[daemon]\", \"[security]\", and \"[xdmcp]\" group sections. Within each group, there are particular key/value pairs that can be specified to modify how GDM behaves. For example, to enable timed login and specify the timed login user to be a user named \"you\", you would modify the file so it contains the following lines:"
714
#: C/gdm.xml:1060(screen)
716
msgid "\n[daemon]\nTimedLoginEnable=true\nTimedLogin=you\n"
719
#: C/gdm.xml:1066(para)
720
msgid "A full list of supported configuration keys follow:"
723
#: C/gdm.xml:1071(title)
727
#: C/gdm.xml:1075(term)
731
#: C/gdm.xml:1077(synopsis)
736
#: C/gdm.xml:1078(para)
737
msgid "The group name under which the greeter and other GUI programs are run. Refer to the <filename>User</filename> configuration key and to the \"Security->GDM User And Group\" section of this document for more information."
740
#: C/gdm.xml:1088(term)
741
msgid "TimedLoginEnable"
744
#: C/gdm.xml:1090(synopsis)
746
msgid "TimedLoginEnable=false"
749
#: C/gdm.xml:1091(para)
750
msgid "If the user given in <filename>TimedLogin</filename> should be logged in after a number of seconds (set with <filename>TimedLoginDelay</filename>) of inactivity on the login screen. This is useful for public access terminals or perhaps even home use. If the user uses the keyboard or browses the menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or 30 seconds, whichever is higher. If the user does not enter a username but just hits the ENTER key while the login program is requesting the username, then GDM will assume the user wants to login immediately as the timed user. Note that no password will be asked for this user so you should be careful, although if using PAM it can be configured to require password entry before allowing login. Refer to the \"Security->PAM\" section of the manual for more information, or for help if this feature does not seem to work."
753
#: C/gdm.xml:1113(term)
757
#: C/gdm.xml:1115(synopsis)
762
#: C/gdm.xml:1116(para)
763
msgid "This is the user that should be logged in after a specified number of seconds of inactivity."
766
#: C/gdm.xml:1124(term)
767
msgid "TimedLoginDelay"
770
#: C/gdm.xml:1126(synopsis)
772
msgid "TimedLoginDelay=30"
775
#: C/gdm.xml:1127(para)
776
msgid "Delay in seconds before the <filename>TimedLogin</filename> user will be logged in."
779
#: C/gdm.xml:1135(term)
780
msgid "AutomaticLoginEnable"
783
#: C/gdm.xml:1137(synopsis)
785
msgid "AutomaticLoginEnable=false"
788
#: C/gdm.xml:1138(para)
789
msgid "If true, the user given in <filename>AutomaticLogin</filename> should be logged in immediately. This feature is like timed login with a delay of 0."
792
#: C/gdm.xml:1146(term)
793
msgid "AutomaticLogin"
796
#: C/gdm.xml:1148(synopsis)
798
msgid "AutomaticLogin="
801
#: C/gdm.xml:1149(para)
802
msgid "This is the user that should be logged in immediately if <filename>AutomaticLoginEnable</filename> is true."
805
#: C/gdm.xml:1157(term)
809
#: C/gdm.xml:1159(synopsis)
814
#: C/gdm.xml:1160(para)
815
msgid "The username under which the greeter and other GUI programs are run. Refer to the <filename>Group</filename> configuration key and to the \"Security->GDM User And Group\" section of this document for more information."
818
#: C/gdm.xml:1172(title)
819
msgid "Security Options"
822
#: C/gdm.xml:1175(title)
826
#: C/gdm.xml:1178(term)
830
#: C/gdm.xml:1180(synopsis)
832
msgid "DisallowTCP=true"
835
#: C/gdm.xml:1181(para)
836
msgid "If true, then always append <filename>-nolisten tcp</filename> to the command line when starting attached Xservers, thus disallowing TCP connection. This is a more secure configuration if you are not using remote connections."
839
#: C/gdm.xml:1193(title)
840
msgid "XDCMP Support"
843
#: C/gdm.xml:1196(title)
847
#: C/gdm.xml:1199(term)
848
msgid "DisplaysPerHost"
851
#: C/gdm.xml:1201(synopsis)
853
msgid "DisplaysPerHost=1"
856
#: C/gdm.xml:1202(para)
857
msgid "To prevent attackers from filling up the pending queue, GDM will only allow one connection for each remote computer. If you want to provide display services to computers with more than one screen, you should increase this value."
860
#: C/gdm.xml:1209(para)
861
msgid "Note that the number of attached DISPLAYS allowed is not limited. Only remote connections via XDMCP are limited by this configuration option."
864
#: C/gdm.xml:1218(term)
868
#: C/gdm.xml:1220(synopsis)
873
#: C/gdm.xml:1221(para)
874
msgid "Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM."
877
#: C/gdm.xml:1226(para)
878
msgid "<filename>gdm</filename> listens for requests on UDP port 177. See the Port option for more information."
881
#: C/gdm.xml:1231(para)
882
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>"
885
#: C/gdm.xml:1237(para)
886
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</ulink> man page for details."
889
#: C/gdm.xml:1248(para)
890
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."
893
#: C/gdm.xml:1257(term)
897
#: C/gdm.xml:1259(synopsis)
899
msgid "EnableProxy=false"
902
#: C/gdm.xml:1260(para)
903
msgid "Setting this to true enables support for running XDMCP sessions on a local proxy Xserver. 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."
906
#: C/gdm.xml:1268(para)
907
msgid "Note, however, that this mode will significantly increase the burden on the machine hosting the XDMCP sessions"
910
#: C/gdm.xml:1273(para)
911
msgid "See the <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</filename> options for further details on how to configure support for this feature."
914
#: C/gdm.xml:1282(term)
915
msgid "HonorIndirect"
918
#: C/gdm.xml:1284(synopsis)
920
msgid "HonorIndirect=true"
923
#: C/gdm.xml:1285(para)
924
msgid "Enables XDMCP INDIRECT choosing (i.e. remote execution of <filename>gdmchooser</filename>) for X-terminals which do not supply their own display browser."
927
#: C/gdm.xml:1294(term)
931
#: C/gdm.xml:1296(synopsis)
936
#: C/gdm.xml:1297(para)
937
msgid "To avoid denial of service attacks, GDM has fixed size queue of pending connections. Only MaxPending displays can start at the same time."
940
#: C/gdm.xml:1303(para)
941
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."
944
#: C/gdm.xml:1312(term)
945
msgid "MaxPendingIndirect"
948
#: C/gdm.xml:1314(synopsis)
950
msgid "MaxPendingIndirect=4"
953
#: C/gdm.xml:1315(para)
954
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."
957
#: C/gdm.xml:1325(term)
961
#: C/gdm.xml:1327(synopsis)
963
msgid "MaxSessions=16"
966
#: C/gdm.xml:1328(para)
967
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."
970
#: C/gdm.xml:1337(term)
974
#: C/gdm.xml:1339(synopsis)
979
#: C/gdm.xml:1340(para)
980
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."
983
#: C/gdm.xml:1346(para)
984
msgid "GDM will then place the session id in the pending queue waiting for the display to respond with a MANAGE request."
987
#: C/gdm.xml:1351(para)
988
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."
991
#: C/gdm.xml:1360(term)
992
msgid "MaxWaitIndirect"
995
#: C/gdm.xml:1362(synopsis)
997
msgid "MaxWaitIndirect=30"
1000
#: C/gdm.xml:1363(para)
1001
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>."
1004
#: C/gdm.xml:1377(term)
1008
#: C/gdm.xml:1379(synopsis)
1013
#: C/gdm.xml:1380(para)
1014
msgid "The UDP port number <filename>gdm</filename> should listen to for XDMCP requests. Do not change this unless you know what you are doing."
1017
#: C/gdm.xml:1389(term)
1018
msgid "PingIntervalSeconds"
1021
#: C/gdm.xml:1391(synopsis)
1023
msgid "PingIntervalSeconds=15"
1026
#: C/gdm.xml:1392(para)
1027
msgid "Interval in which to ping the Xserver in seconds. If the Xserver does not 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."
1030
#: C/gdm.xml:1400(para)
1031
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."
1034
#: C/gdm.xml:1413(term)
1035
msgid "ProxyReconnect"
1038
#: C/gdm.xml:1415(synopsis)
1040
msgid "FlexiProxyReconnect="
1043
#: C/gdm.xml:1416(para)
1044
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."
1047
#: C/gdm.xml:1423(para)
1048
msgid "In order to use this feature, you must have a nested Xserver available which supports disconnecting from its parent Xserver and reconnecting to another Xserver. Currently, the Distributed Multihead X (DMX) server supports this feature to some extent and other projects like NoMachine NX are busy implementing it."
1051
#: C/gdm.xml:1431(para)
1052
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."
1055
#: C/gdm.xml:1440(term)
1056
msgid "ProxyXServer"
1059
#: C/gdm.xml:1442(synopsis)
1061
msgid "ProxyXServer="
1064
#: C/gdm.xml:1443(para)
1065
msgid "The Xserver command line for a XDMCP proxy. Any nested X server like Xnest, Xephyr or Xdmx should work fairly well."
1068
#: C/gdm.xml:1451(term)
1072
#: C/gdm.xml:1453(synopsis)
1074
msgid "Willing=<etc>/gdm/Xwilling"
1077
#: C/gdm.xml:1454(para)
1078
msgid "When the machine sends a WILLING packet back after a QUERY it sends a string that gives the current status of this server. The default message is the system ID, but it is possible to create a script that displays customized message. If this script does not exist or this key is empty the default message is sent. If this script succeeds and produces some output, the first line of it's output is sent (and only the first line). It runs at most once every 3 seconds to prevent possible denial of service by flooding the machine with QUERY packets."
1081
#: C/gdm.xml:1473(title)
1082
msgid "Simple Greeter Configuration"
1085
#: C/gdm.xml:1475(para)
1086
msgid "The GDM default greeter is called the simple Greeter and is configured via GConf. Default values are stored in GConf in the <filename>gdm-simple-greeter.schemas</filename> file. These defaults can be overridden if the \"gdm\" user has a writable $HOME directory to store GConf settings. These values can be edited using the <command>gconftool-2</command> or <command>gconf-editor</command> programs. The following configuration options are supported:"
1089
#: C/gdm.xml:1486(title)
1090
msgid "Greeter Configuration Keys"
1093
#: C/gdm.xml:1489(term)
1094
msgid "/apps/gdm/simple-greeter/banner_message_enable"
1097
#: C/gdm.xml:1491(synopsis) C/gdm.xml:1522(synopsis) C/gdm.xml:1533(synopsis)
1099
msgid "false (boolean)"
1102
#: C/gdm.xml:1492(para)
1103
msgid "Controls whether the banner message text is displayed."
1106
#: C/gdm.xml:1499(term)
1107
msgid "/apps/gdm/simple-greeter/banner_message_text"
1110
#: C/gdm.xml:1501(synopsis)
1112
msgid "NULL (string)"
1115
#: C/gdm.xml:1502(para)
1116
msgid "Specifies the text banner message to show on the greeter window."
1119
#: C/gdm.xml:1510(term)
1120
msgid "/apps/gdm/simple-greeter/logo_icon_name"
1123
#: C/gdm.xml:1512(synopsis)
1125
msgid "computer (string)"
1128
#: C/gdm.xml:1513(para)
1129
msgid "Set to the themed icon name to use for the greeter logo."
1132
#: C/gdm.xml:1520(term)
1133
msgid "/apps/gdm/simple-greeter/disable_restart_buttons"
1136
#: C/gdm.xml:1523(para)
1137
msgid "Controls whether to show the restart buttons in the login window."
1140
#: C/gdm.xml:1531(term)
1141
msgid "/apps/gdm/simple-greeter/wm_use_compiz"
1144
#: C/gdm.xml:1534(para)
1145
msgid "Controls whether compiz is used as the window manager instead of metacity."
1148
#: C/gdm.xml:1544(title)
1149
msgid "General Session Settings"
1153
#. TODO - I think this section should be expanded upon. What specific
1154
#. keys are of interest, or would some users be likely to want
1155
#. to configure? Also, would be good to be more specific about
1156
#. how lock down management is handled.
1158
#: C/gdm.xml:1553(para)
1159
msgid "The GDM Greeter uses some of the same framework that your desktop session will use. And so, it is influenced by a number of the same GConf settings. For each of these settings the Greeter will use the default value unless it is specifically overridden by a) GDM's installed mandatory policy b) system mandatory policy. GDM installs its own mandatory policy to lock down some settings for security."
1162
#: C/gdm.xml:1564(title)
1163
msgid "GNOME Settings Daemon"
1167
#. TODO - I think this section should be expanded upon. What specific
1168
#. keys are of interest, or would some users be likely to want
1169
#. to configure? Also, would be good to give a more complete
1170
#. list of plugins that users might want to consider disabling.
1171
#. Also, shouldn't we list the sound/active key in the Greeter
1172
#. configuration setting? Oddly I do not find this key used
1173
#. in anything but the chooser in SVN.
1175
#: C/gdm.xml:1577(para)
1176
msgid "GDM enables the following gnome-settings-daemon plugins: a11y-keyboard, background, sound, xsettings."
1179
#: C/gdm.xml:1582(para)
1180
msgid "These are responsible for things like the background image, font and theme settings, sound events, etc."
1183
#: C/gdm.xml:1587(para)
1184
msgid "Plugins can also be disabled using GConf. For example, if you want to disable the sound plugin then unset the following key: <filename>/apps/gdm/simple-greeter/settings-manager-plugins/sound/active</filename>."
1187
#: C/gdm.xml:1595(title)
1188
msgid "GDM Session Configuration"
1191
#: C/gdm.xml:1597(para)
1192
msgid "GDM sessions are specified using the FreeDesktop.org Desktop Entry Specification, which can be referenced at the following URL: <ulink url=\"http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec\"> http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec</ulink>."
1195
#: C/gdm.xml:1604(para)
1196
msgid "These files are installed, by default, to <filename><etc>/X11/sessions/</filename>. For backwards compatibility any desktop files in the <filename><etc>/Sessions</filename>, <filename><share>/xsessions</filename>, and <filename><share/gdm/BuiltInSessions</filename> directories are also recognized by GDM."
1199
#: C/gdm.xml:1613(para)
1200
msgid "A session can be disabled by editing the desktop file and adding a line that says <filename>Hidden=true</filename>."
1203
#: C/gdm.xml:1620(title)
1204
msgid "GDM User Session and Language Configuration"
1207
#: C/gdm.xml:1621(para)
1208
msgid "The user's default session and language choices are stored in the <filename>~/.dmrc</filename> file. When a user logs in for the first time, this file is created with the user's initial choices. The user can change these default values by simply changing to a different value when logging in. GDM will remember this change for subsequent logins."
1211
#: C/gdm.xml:1629(para)
1212
msgid "The <filename>~/.dmrc</filename> file is in the standard <filename>INI</filename> format. It has one section called <filename>[Desktop]</filename> which has two keys: <filename>Session</filename> and <filename>Language</filename>."
1215
#: C/gdm.xml:1636(para)
1216
msgid "The <filename>Session</filename> key specifies the basename of the session <filename>.desktop</filename> file that the user wishes to normally use without the <filename>.desktop</filename> extension. The <filename>Language</filename> key specifies the language that the user wishes to use by default. If either of these keys is missing, the system default is used. The file would normally look as follows:"
1219
#: C/gdm.xml:1645(screen)
1221
msgid "\n[Desktop]\nSession=gnome\nLanguage=cs_CZ.UTF-8\n"
1224
#: C/gdm.xml:1657(title)
1225
msgid "GDM Commands"
1228
#: C/gdm.xml:1660(title)
1229
msgid "GDM Root User Commands"
1232
#: C/gdm.xml:1662(para)
1233
msgid "The GDM package provides the following commands in <filename>sbindir</filename> intended to be run by the root user:"
1236
#: C/gdm.xml:1668(title) C/gdm.xml:1683(title)
1237
msgid "<command>gdm</command> and <command>gdm-binary</command> Command Line Options"
1240
#: C/gdm.xml:1671(para)
1241
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. The <command>gdm-binary</command> is the actual GDM daemon."
1244
#: C/gdm.xml:1687(term)
1248
#: C/gdm.xml:1689(para)
1249
msgid "Gives a brief overview of the command line options."
1252
#: C/gdm.xml:1696(term)
1256
#: C/gdm.xml:1698(para)
1257
msgid "Print debug output to the syslog. This is typically <filename><var>/log/messages</filename> or <filename><var>/adm/messages</filename> depending on your Operating System."
1260
#: C/gdm.xml:1708(term)
1261
msgid "--fatal-warnings"
1264
#: C/gdm.xml:1710(para)
1265
msgid "Make all warnings cause GDM to exit."
1268
#: C/gdm.xml:1717(term)
1269
msgid "--timed-exit"
1272
#: C/gdm.xml:1719(para)
1273
msgid "Exit after 30 seconds. Useful for debugging."
1276
#: C/gdm.xml:1726(term)
1280
#: C/gdm.xml:1728(para)
1281
msgid "Print the version of the GDM daemon."
1284
#: C/gdm.xml:1737(title)
1285
msgid "<command>gdm-restart</command> Command Line Options"
1288
#: C/gdm.xml:1739(para)
1289
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."
1292
#: C/gdm.xml:1747(title)
1293
msgid "<command>gdm-safe-restart</command> Command Line Options"
1296
#: C/gdm.xml:1749(para)
1297
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."
1300
#: C/gdm.xml:1757(title)
1301
msgid "<command>gdm-stop</command> Command Line Options"
1304
#: C/gdm.xml:1759(para)
1305
msgid "<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM signal."
1308
#: C/gdm.xml:1770(title)
1309
msgid "Troubleshooting"
1313
#. TODO - any other tips we should add? Might be useful to highlight any
1314
#. common D-Bus configuration issues?
1316
#: C/gdm.xml:1778(para)
1317
msgid "This section discusses helpful tips for getting GDM working. In general, if you have a problem using GDM, you can submit a bug or send an email to the gdm-list mailing list. Information about how to do this is in the Introduction section of the document."
1320
#: C/gdm.xml:1785(para)
1321
msgid "If GDM is failing to work properly, it is always a good idea to include debug information. To turn on debug, launch gdm with the --debug option. Then use GDM to the point where it fails, and debug output will be sent to your system log (<filename><var>/log/messages</filename> or <filename><var>/adm/messages</filename> depending on your Operating System). If you share this output with the GDM community via a bug report or email, please only include the GDM related debug information and not the entire file since it can be large. If you do not see any GDM syslog output, you may need to configure syslog (refer to the <ulink type=\"help\" url=\"man:syslog\">syslog</ulink> man page)."
1324
#: C/gdm.xml:1800(title)
1325
msgid "GDM Will Not Start"
1328
#: C/gdm.xml:1802(para)
1329
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."
1332
#: C/gdm.xml:1811(para)
1333
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."
1336
#: C/gdm.xml:1824(para)
1337
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."
1340
#: C/gdm.xml:1835(title)
1344
#: C/gdm.xml:1836(para)
1345
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."
1348
#: C/gdm.xml:1844(para)
1349
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."
1352
#: C/gdm.xml:1850(para)
1353
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>"
1356
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
1357
#: C/gdm.xml:0(None)
1358
msgid "translator-credits"
added
removed
docs/it/it.po
