« back to all changes in this revision
Viewing changes to docs/oc/oc.po
- browse files at revision 1.4.19
- compare with another revision
- download diff
- download tarball
- view history from revision 1.4.19
- Committer: Bazaar Package Importer
- Author(s): Sebastien Bacher
- Date: 2007-08-28 14:00:59 UTC
- mto: (2.1.2 lenny) (1.4.50)
- mto: This revision was merged to the branch mainline in revision 76.
- Revision ID: james.westby@ubuntu.com-20070828140059-h273g7z6ffhaiww9
Tags: upstream-2.19.7
Import upstream version 2.19.7
- files added:
- docs/oc
- files removed:
- gui/greeter/themes/happygnome-list/happygnome.xml
- files modified:
- ChangeLog
added
removed
docs/oc/oc.po
1
# Occitan translation of gdm2 documentation.
2
# Copyright (C) 2006-2007 Free Software Foundation, Inc.
3
# This file is distributed under the same license as the gdm documentation package.
4
#
5
# Yannig MARCHEGAY (yannig@marchegay.org) - 2006-2007
6
#
7
msgid ""
8
msgstr ""
9
"Project-Id-Version: gdm2 doc fr\n"
10
"Report-Msgid-Bugs-To: \n"
11
"POT-Creation-Date: 2007-06-09 17:20+0200\n"
12
"PO-Revision-Date: 2007-08-21 21:38+0200\n"
13
"Last-Translator: Yannig Marchegay (Kokoyaya) <yannig@marchegay.org>\n"
14
"Language-Team: Occitan (post 1500) <ubuntu-l10n-oci@lists.ubuntu.com>\n"
15
"MIME-Version: 1.0\n"
16
"Content-Type: text/plain; charset=UTF-8\n"
17
"Content-Transfer-Encoding: 8bit\n"
18
"Plural-Forms: nplurals=2; plural=(n > 1);"
19
20
#: ../C/legal.xml:2(para) ../C/gdm.xml:2(para)
21
msgid ""
22
"Permission is granted to copy, distribute and/or modify this document under "
23
"the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any "
24
"later version published by the Free Software Foundation with no Invariant "
25
"Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy "
26
"of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or "
27
"in the file COPYING-DOCS distributed with this manual."
28
msgstr ""
29
30
#: ../C/legal.xml:12(para) ../C/gdm.xml:12(para)
31
msgid ""
32
"This manual is part of a collection of GNOME manuals distributed under the "
33
"GFDL. If you want to distribute this manual separately from the collection, "
34
"you can do so by adding a copy of the license to the manual, as described in "
35
"section 6 of the license."
36
msgstr ""
37
38
#: ../C/legal.xml:19(para) ../C/gdm.xml:19(para)
39
msgid ""
40
"Many of the names used by companies to distinguish their products and "
41
"services are claimed as trademarks. Where those names appear in any GNOME "
42
"documentation, and the members of the GNOME Documentation Project are made "
43
"aware of those trademarks, then the names are in capital letters or initial "
44
"capital letters."
45
msgstr ""
46
47
#: ../C/legal.xml:35(para) ../C/gdm.xml:35(para)
48
msgid ""
49
"DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, "
50
"EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT "
51
"THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS "
52
"MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE "
53
"RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR "
54
"MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR "
55
"MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL "
56
"WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY "
57
"SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN "
58
"ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION "
59
"OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND"
60
msgstr ""
61
62
#: ../C/legal.xml:55(para) ../C/gdm.xml:55(para)
63
msgid ""
64
"UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING "
65
"NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY "
66
"CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE "
67
"DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON "
68
"FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF "
69
"ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, "
70
"WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES "
71
"OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED "
72
"VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE "
73
"POSSIBILITY OF SUCH DAMAGES."
74
msgstr ""
75
76
#: ../C/legal.xml:28(para) ../C/gdm.xml:28(para)
77
msgid ""
78
"DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS "
79
"OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: "
80
"<placeholder-1/>"
81
msgstr ""
82
83
#: ../C/gdm.xml:13(title)
84
msgid "Gnome Display Manager Reference Manual"
85
msgstr ""
86
87
#: ../C/gdm.xml:17(revnumber)
88
msgid "0.0"
89
msgstr ""
90
91
#: ../C/gdm.xml:18(date)
92
msgid "2007-01"
93
msgstr ""
94
95
#: ../C/gdm.xml:23(para)
96
msgid "GDM is the GNOME Display Manager, a graphical login program."
97
msgstr ""
98
99
#: ../C/gdm.xml:30(firstname)
100
msgid "Martin"
101
msgstr ""
102
103
#: ../C/gdm.xml:30(othername)
104
msgid "K."
105
msgstr ""
106
107
#: ../C/gdm.xml:31(surname)
108
msgid "Petersen"
109
msgstr ""
110
111
#: ../C/gdm.xml:33(email)
112
msgid "mkp@mkp.net"
113
msgstr ""
114
115
#: ../C/gdm.xml:37(firstname)
116
msgid "George"
117
msgstr ""
118
119
#: ../C/gdm.xml:37(surname)
120
msgid "Lebl"
121
msgstr ""
122
123
#: ../C/gdm.xml:39(email)
124
msgid "jirka@5z.com"
125
msgstr ""
126
127
#: ../C/gdm.xml:43(firstname)
128
msgid "Brian"
129
msgstr ""
130
131
#: ../C/gdm.xml:43(surname)
132
msgid "Cameron"
133
msgstr ""
134
135
#: ../C/gdm.xml:45(email)
136
msgid "Brian.Cameron@Sun.COM"
137
msgstr ""
138
139
#: ../C/gdm.xml:49(firstname)
140
msgid "Bill"
141
msgstr ""
142
143
#: ../C/gdm.xml:49(surname)
144
msgid "Haneman"
145
msgstr ""
146
147
#: ../C/gdm.xml:51(email)
148
msgid "Bill.Haneman@Sun.COM"
149
msgstr ""
150
151
#: ../C/gdm.xml:56(year)
152
msgid "1998"
153
msgstr "1998"
154
155
#: ../C/gdm.xml:56(year)
156
msgid "1999"
157
msgstr "1999"
158
159
#: ../C/gdm.xml:56(holder)
160
msgid "Martin K. Petersen"
161
msgstr ""
162
163
#: ../C/gdm.xml:59(year)
164
msgid "2001"
165
msgstr "2001"
166
167
#: ../C/gdm.xml:59(year) ../C/gdm.xml:63(year) ../C/gdm.xml:66(year)
168
msgid "2003"
169
msgstr "2003"
170
171
#: ../C/gdm.xml:59(year) ../C/gdm.xml:66(year)
172
msgid "2004"
173
msgstr "2004"
174
175
#: ../C/gdm.xml:60(holder)
176
msgid "George Lebl"
177
msgstr ""
178
179
#: ../C/gdm.xml:63(holder)
180
msgid "Red Hat, Inc."
181
msgstr ""
182
183
#: ../C/gdm.xml:66(holder)
184
msgid "Sun Microsystems, Inc."
185
msgstr ""
186
187
#: ../C/gdm.xml:71(releaseinfo) ../C/gdm.xml:80(para)
188
msgid ""
189
"This manual describes version 2.19.2 of the GNOME Display Manager. It was "
190
"last updated on 06/04/2007."
191
msgstr ""
192
193
#: ../C/gdm.xml:78(title)
194
msgid "Terms and Conventions Used in This Manual"
195
msgstr ""
196
197
#: ../C/gdm.xml:85(para)
198
msgid ""
199
"Chooser - A program used to select a remote host for managing a display "
200
"remotely on the local display (<command>gdmchooser</command>)."
201
msgstr ""
202
203
#: ../C/gdm.xml:90(para)
204
msgid "Configurator - The configuration application (<command>gdmsetup</command>)."
205
msgstr ""
206
207
#: ../C/gdm.xml:95(para)
208
msgid ""
209
"GDM - Gnome Display Manager. Used to describe the software package as a "
210
"whole. Sometimes also referred to as GDM2."
211
msgstr ""
212
213
#: ../C/gdm.xml:100(para)
214
msgid "gdm - The Gnome Display Manager daemon (<command>gdm</command>)."
215
msgstr ""
216
217
#: ../C/gdm.xml:104(para)
218
msgid ""
219
"Greeter - The graphical login window (<command>gdmlogin</command> or "
220
"<command>gdmgreeter</command>)."
221
msgstr ""
222
223
#: ../C/gdm.xml:109(para)
224
msgid "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)."
225
msgstr ""
226
227
#: ../C/gdm.xml:113(para)
228
msgid "PAM - Pluggable Authentication Mechanism"
229
msgstr ""
230
231
#: ../C/gdm.xml:117(para)
232
msgid "Themed Greeter - The themable login window ( <command>gdmgreeter</command>)."
233
msgstr ""
234
235
#: ../C/gdm.xml:122(para)
236
msgid "XDMCP - X Display Manage Protocol"
237
msgstr ""
238
239
#: ../C/gdm.xml:126(para)
240
msgid ""
241
"Paths that start with a word in angle brackets are relative to the "
242
"installation prefix. I.e. <filename><share>/pixmaps/</filename> refers "
243
"to <filename><share>/pixmaps</filename> if GDM was configured with "
244
"<command>--prefix=/usr</command>. Normally also note that GDM is installed "
245
"with <command>--sysconfigdir=<etc>/X11</command>, meaning any path to "
246
"which we refer to as <filename><etc>/gdm/PreSession</filename> usually "
247
"means <filename><etc/X11>/gdm/PreSession</filename>. Note that for "
248
"interoperability it is recommended that you use a --prefix of <filename>/"
249
"usr</filename> and a --sysconfdir of <filename><etc>/X11</filename>."
250
msgstr ""
251
252
#: ../C/gdm.xml:142(title)
253
msgid "Overview"
254
msgstr ""
255
256
#: ../C/gdm.xml:145(title)
257
msgid "Introduction"
258
msgstr ""
259
260
#: ../C/gdm.xml:149(para)
261
msgid ""
262
"The Gnome Display Manager (GDM) is a display manager that implements all "
263
"significant features required for managing local and remote displays. GDM "
264
"was written from scratch and does not contain any XDM / X Consortium code."
265
msgstr ""
266
267
#: ../C/gdm.xml:156(para)
268
msgid ""
269
"Note that GDM is highly configurable, and many configuration settings can "
270
"affect security. Issues to be aware of are highlighted in this document and "
271
"in the GDM Configuration files."
272
msgstr ""
273
274
#: ../C/gdm.xml:162(para)
275
msgid ""
276
"For further information about GDM, see the <ulink type=\"http\" url=\"http://"
277
"www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. Please "
278
"submit any bug reports or enhancement requests to the \"gdm\" category in "
279
"<ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</"
280
"ulink>. You can also send a message to the <address><email>gdm-list@gnome."
281
"org</email></address> mail list to discuss any issues or concerns with the "
282
"GDM program."
283
msgstr ""
284
285
#: ../C/gdm.xml:175(title)
286
msgid "Interface Stability"
287
msgstr ""
288
289
#: ../C/gdm.xml:179(para)
290
msgid ""
291
"The key/value pairs defined in the GDM configuration files and the location "
292
"of these files are considered \"stable\" interfaces should only change in "
293
"ways that are backwards compatible. Note that this includes functionality "
294
"like the GDM scripts (Init, PreSession, PostSession, PostLogin, "
295
"XKeepsCrashing, etc.); directory locations (ServAuthDir, etc.), system "
296
"applications (SoundProgram), etc. Some configuration values depend on OS "
297
"interfaces may need to be modified to work on a given OS. Typical examples "
298
"are HaltCommand, RebootCommand, CustomCommands, SuspendCommand, "
299
"StandardXServer, Xnest, SoundProgram, and the \"command\" value for each "
300
"\"server-foo\"."
301
msgstr ""
302
303
#: ../C/gdm.xml:193(para)
304
msgid ""
305
"Command-line interfaces for GDM programs installed to <filename><bin></"
306
"filename> and <filename><sbin></filename> are considered stable. Refer "
307
"to your distribution documentation to see if there are any distribution-"
308
"specific changes to these GDM interfaces and what support exists for them."
309
msgstr ""
310
311
#: ../C/gdm.xml:201(para)
312
msgid ""
313
"As of the GDM 2.15 development series, some one-dash arguments are no longer "
314
"supported. This includes the \"-xdmaddress\", \"-clientaddress\", and \"-"
315
"connectionType\" arguments used by <command>gdmchooser</command>. These "
316
"arguments have been changed to now use two dashes."
317
msgstr ""
318
319
#: ../C/gdm.xml:209(para)
320
msgid ""
321
"If issues are discovered that break compatibility, please file a bug with an "
322
"\"urgent\" priority."
323
msgstr ""
324
325
#: ../C/gdm.xml:216(title)
326
msgid "The GDM Daemon"
327
msgstr ""
328
329
#: ../C/gdm.xml:218(para)
330
msgid ""
331
"The GDM daemon is responsible for managing displays on the system. This "
332
"includes authenticating users, starting the user session, and terminating "
333
"the user session. GDM is configurable and the ways it can be configured are "
334
"described in the \"Configuring GDM\" section of this document. The "
335
"<filename>Init</filename>, <filename>PostLogin</filename>, "
336
"<filename>PreSession</filename>, and <filename>PostSession</filename> "
337
"scripts discussed below are discussed in this \"Configuring GDM section\"."
338
msgstr ""
339
340
#: ../C/gdm.xml:229(para)
341
msgid ""
342
"The GDM daemon supports a UNIX domain socket protocol which can be used to "
343
"control aspects of its behavior and to query information. This protocol is "
344
"described in the \"Controlling GDM\" section of this document."
345
msgstr ""
346
347
#: ../C/gdm.xml:236(para)
348
msgid ""
349
"GDM can be asked to manage a display a number of ways. Local displays are "
350
"always managed when GDM starts and will be restarted when a user's session "
351
"is finished. Displays can be requested via XDMCP, flexible displays can be "
352
"requested by running the <command>gdmflexiserver</command> command. Displays "
353
"that are started on request are not restarted on session exit. GDM also "
354
"provides the <command>gdmdynamic</command> command to allow easier "
355
"management of displays on a multi-user server. These display types are "
356
"discussed further in the next section."
357
msgstr ""
358
359
#: ../C/gdm.xml:248(para)
360
msgid ""
361
"When the GDM daemon is asked to manage a display, it will fork an X server "
362
"process, then run the <filename>Init</filename> script as the root user, and "
363
"start the login GUI dialog as a slave process on the display. GDM can be "
364
"configured to use either <command>gdmgreeter</command> (the default) or "
365
"<command>gdmlogin</command> as the GUI dialog program. The "
366
"<command>gdmlogin</command> program supports accessibility while the "
367
"<command>gdmgreeter</command> program supports greater themeability. The GUI "
368
"dialog is run as the unpriviledged \"gdm\" user/group which is described in "
369
"the \"Security\" section below. The GUI dialog communicates with the daemon "
370
"via a sockets protocol and via standard input/output. The slave, for example "
371
"passes the username and password information to the GDM daemon via standard "
372
"input/output so the daemon can handle the actual authentication."
373
msgstr ""
374
375
#: ../C/gdm.xml:265(para)
376
msgid ""
377
"The login GUI dialog screen allows the user to select which session they "
378
"wish to start and which language they wish to use. Sessions are defined by "
379
"files that end in the .desktop extension and more information about these "
380
"files can be found in the \"Configuration\" section. The user enters their "
381
"name and password and if these successfully authenticate, GDM will start the "
382
"requested session for the user. It is possible to configure GDM to avoid the "
383
"authentication process by turning on the Automatic or Timed Login features "
384
"in the GDM configuration. The login GUI can also be configured to provide "
385
"additional features to the user, such as the Face Browser; the ability to "
386
"halt, restart, or suspend the system; and/or edit the login configuration "
387
"(after entering the root password)."
388
msgstr ""
389
390
#: ../C/gdm.xml:280(para)
391
msgid ""
392
"GDM, by default, will use Pluggable Authentication Modules (PAM) for "
393
"authentication, but can also support regular crypt and shadow passwords on "
394
"legacy systems. After authenticating a user, the daemon runs the "
395
"<filename>PostLogin</filename> script as root, and forks a slave process to "
396
"start the requested session. This slave process runs the "
397
"<filename>PreSession</filename> script as root, sets up the user's "
398
"environment, and starts the requested session. GDM keeps track of the user's "
399
"default session and language in the user's <filename>~/.dmrc</filename> and "
400
"will use these defaults if the user did not pick a session or language in "
401
"the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN "
402
"interface after user authentication to tell the X server to be restarted as "
403
"the user instead of as root for added security. When the user's session "
404
"exits, the GDM daemon will run the <filename>PostSession</filename> script "
405
"as root."
406
msgstr ""
407
408
#: ../C/gdm.xml:297(para)
409
msgid ""
410
"Note that, by default, GDM uses the \"gdm\" service name for normal login "
411
"and the \"gdm-autologin\" service name for automatic login. The "
412
"<filename>PamStack</filename> configuration option can be used to specify a "
413
"different service name. For example, if \"foo\" is specified, then GDM will "
414
"use the \"foo\" service name for normal login and \"foo-autologin\" for "
415
"automatic login."
416
msgstr ""
417
418
#: ../C/gdm.xml:307(para)
419
msgid ""
420
"For those looking at the code, the gdm_verify_user function in "
421
"<filename>daemon/verify-pam.c</filename> is used for normal login and the "
422
"gdm_verify_setup_user function is used for automatic login."
423
msgstr ""
424
425
#: ../C/gdm.xml:315(title)
426
msgid "Different Display Types"
427
msgstr ""
428
429
#: ../C/gdm.xml:317(para)
430
msgid ""
431
"GDM supports three different display types: static (local) displays, "
432
"flexible (on-demand) displays, and XDMCP (remote) displays. The \"X Server "
433
"Definitions\" subsection of the \"Configuration\" section explains how the X "
434
"server is configured for different displays."
435
msgstr ""
436
437
#: ../C/gdm.xml:325(para)
438
msgid ""
439
"Static (local) displays are always started by the daemon, and when they die "
440
"or are killed, they are restarted. GDM can run as many of these as needed. "
441
"GDM can also manage displays on which it does not manage a GUI login, thus "
442
"GDM can be used for supporting X terminals. The \"Local Static X Display "
443
"Configuration\" subsection of the \"Configuration\" section describes how "
444
"Static (local) displays are defined."
445
msgstr ""
446
447
#: ../C/gdm.xml:335(para)
448
msgid ""
449
"Flexible, or on demand displays are only available to users logged in on the "
450
"console. Starting a flexible display will lock the current user session and "
451
"will show a new login screen over the current running session. If at least "
452
"one flexible display is already running, and the user requests another, then "
453
"a dialog will display showing existing flexible displays. The user can "
454
"choose to switch back to a previous display or start a new flexible display. "
455
"If the user switches back to a previous display, they will need to enter the "
456
"password in the lock screen program to return to their session. The GDM "
457
"configuration file specifies the maximum number of flexible displays allowed "
458
"on the system."
459
msgstr ""
460
461
#: ../C/gdm.xml:349(para)
462
msgid ""
463
"Flexible displays may be started by running the <command>gdmflexiserver</"
464
"command> command, or via calling the GDM socket protocol directly. Some lock "
465
"screen programs provide a button to start a new flexible session. This "
466
"allows a user to start a new session even if the screen was left locked. The "
467
"GNOME Fast User Switch applet also uses the socket protocol to provide an "
468
"applet interface on the GNOME panel for managing user displays quickly. "
469
"Flexible displays are not restarted when the user session ends. Flexible "
470
"displays require virtual terminal (VT) support in the kernel, and will not "
471
"be available if not supported (such as on Solaris)."
472
msgstr ""
473
474
#: ../C/gdm.xml:362(para)
475
msgid ""
476
"The <filename>FlexibleXServers</filename>, <filename>FirstVT=7</filename>, "
477
"<filename>VTAllocation</filename>, and <filename>FlexiReapDelayMinutes</"
478
"filename> configuration settings are used to configure how flexible displays "
479
"operate."
480
msgstr ""
481
482
#: ../C/gdm.xml:369(para)
483
msgid ""
484
"Nested displays are available to users even if not logged in on the console. "
485
"Nested displays launch a login screen in a window in the user's current "
486
"session. This can be useful if the user has more than one account on a "
487
"machine and wishes to login to the other account without disrupting their "
488
"current session. Nested displays may be started by running the "
489
"<command>gdmflexiserver -n</command> command or via calling the GDM socket "
490
"protocol directly. Nested displays require that the X server supports a "
491
"nested X server command like Xnest or Xephyr. The <filename>Xnest</filename> "
492
"configuration option is used to configure how nested displays operate"
493
msgstr ""
494
495
#: ../C/gdm.xml:382(para)
496
msgid ""
497
"The <command>gdmdynamic</command> is similar to <command>gdmflexiserver</"
498
"command> in the sense that it allows the user to manage displays "
499
"dynamically. However displays started with <command>gdmdynamic</command> are "
500
"treated as local displays, so they are restarted automatically when the "
501
"session exits. This command is intended to be used in multi-user server "
502
"environments (many displays connected to a single server). In other words, "
503
"this command allows the displays to be managed without hardcoding the "
504
"display information in the \"Local Static X Display Configuration\" section "
505
"of the configuration file. This is useful to support the ability of adding "
506
"new displays to the server without needing to restart GDM, for example."
507
msgstr ""
508
509
#: ../C/gdm.xml:397(para)
510
msgid ""
511
"The last display type is the XDMCP remote displays which are described in "
512
"the next section. Remote hosts can connect to GDM and present the login "
513
"screen if this is enabled. Some things are different for remote sessions. "
514
"For example, the Actions menu which allows you to shut down, restart, "
515
"suspend, or configure GDM are not shown."
516
msgstr ""
517
518
#: ../C/gdm.xml:408(title)
519
msgid "XDMCP"
520
msgstr ""
521
522
#: ../C/gdm.xml:412(para)
523
msgid ""
524
"The GDM daemon can be configured to listen for and manage X Display Manage "
525
"Protocol (XDMCP) requests from remote displays. By default XDMCP support is "
526
"turned off, but can be enabled if desired. If GDM is built with TCP Wrapper "
527
"support, then the daemon will only grant access to hosts specified in the "
528
"GDM service section in the TCP Wrappers configuration file."
529
msgstr ""
530
531
#: ../C/gdm.xml:421(para)
532
msgid ""
533
"GDM includes several measures making it more resistant to denial of service "
534
"attacks on the XDMCP service. A lot of the protocol parameters, handshaking "
535
"timeouts etc. can be fine tuned. The defaults should work for most systems, "
536
"however. Do not change them unless you know what you are doing."
537
msgstr ""
538
539
#: ../C/gdm.xml:429(para)
540
msgid ""
541
"GDM listens to UDP port 177 and will respond to QUERY and BROADCAST_QUERY "
542
"requests by sending a WILLING packet to the originator."
543
msgstr ""
544
545
#: ../C/gdm.xml:434(para)
546
msgid ""
547
"GDM can also be configured to honor INDIRECT queries and present a host "
548
"chooser to the remote display. GDM will remember the user's choice and "
549
"forward subsequent requests to the chosen manager. GDM also supports an "
550
"extension to the protocol which will make it forget the redirection once the "
551
"user's connection succeeds. This extension is only supported if both daemons "
552
"are GDM. It is transparent and will be ignored by XDM or other daemons that "
553
"implement XDMCP."
554
msgstr ""
555
556
#: ../C/gdm.xml:444(para)
557
msgid ""
558
"If XDMCP seems to not be working, make sure that all machines are specified "
559
"in <filename>/etc/hosts</filename>."
560
msgstr ""
561
562
#: ../C/gdm.xml:449(para)
563
msgid ""
564
"Refer to the \"Security\" section for information about security concerns "
565
"when using XDMCP."
566
msgstr ""
567
568
#: ../C/gdm.xml:456(title)
569
msgid "Securing Remote Connection Through SSH"
570
msgstr ""
571
572
#: ../C/gdm.xml:459(para)
573
msgid ""
574
"As explained in the \"Security\" section, XDMCP does not use any kind of "
575
"encryption and as such is inherently insecure. As XDMCP uses UDP as a "
576
"network transport layer, it is not possible to simply secure it through an "
577
"SSH tunnel."
578
msgstr ""
579
580
#: ../C/gdm.xml:466(para)
581
msgid ""
582
"To remedy this problem, gdm can be configured at compilation-time with the "
583
"option --enable-secureremote, in which case gdm proposes as a built-in "
584
"session a session called \"Secure Remote Connection\". Starting such a "
585
"session allows the user to enter the name or the address of the host on "
586
"which to connect; provided the said host runs an SSH server, the user then "
587
"gets connected to the server on which the default X session is started and "
588
"displayed on the local host."
589
msgstr ""
590
591
#: ../C/gdm.xml:476(para)
592
msgid ""
593
"Using this session allows a much more secure network connection and only "
594
"necessitates to have an SSH server running on the remote host."
595
msgstr ""
596
597
#: ../C/gdm.xml:483(title)
598
msgid "The GTK+ Greeter"
599
msgstr ""
600
601
#: ../C/gdm.xml:485(para)
602
msgid ""
603
"The GTK+ Greeter is the default graphical user interface that is presented "
604
"to the user. The greeter contains a menu at the top, an optional face "
605
"browser, an optional logo and a text entry widget. This greeter has full "
606
"accessibility support, and should be used by users with accessibility needs."
607
msgstr ""
608
609
#: ../C/gdm.xml:493(para)
610
msgid ""
611
"The text entry field is used for entering logins, passwords, passphrases "
612
"etc. <command>gdmlogin</command> is controlled by the underlying daemon and "
613
"is basically stateless. The daemon controls the greeter through a simple "
614
"protocol where it can ask the greeter for a text string with echo turned on "
615
"or off. Similarly, the daemon can change the label above the text entry "
616
"widget to correspond to the value the authentication system wants the user "
617
"to enter."
618
msgstr ""
619
620
#: ../C/gdm.xml:503(para)
621
msgid ""
622
"The menu bar in the top of the greeter enables the user to select the "
623
"requested session type/desktop environment, select an appropriate locale/"
624
"language, halt/restart/suspend the computer, configure GDM (given the user "
625
"knows the root password), change the GTK+ theme, or start an XDMCP chooser."
626
msgstr ""
627
628
#: ../C/gdm.xml:511(para)
629
msgid ""
630
"The greeter can optionally display a logo in the login window. The image "
631
"must be in a format readable to the gdk-pixbuf library (GIF, JPG, PNG, TIFF, "
632
"XPM and possibly others), and it must be readable to the GDM user. See the "
633
"<filename>Logo</filename> option in the reference section below for details."
634
msgstr ""
635
636
#: ../C/gdm.xml:521(title)
637
msgid "The Themed Greeter"
638
msgstr ""
639
640
#: ../C/gdm.xml:523(para)
641
msgid ""
642
"The Themed Greeter is a greeter interface that takes up the whole screen and "
643
"is very themable. Themes can be selected and new themes can be installed by "
644
"the configuration application or by setting the <filename>GraphicalTheme</"
645
"filename> configuration key. The Themed Greeter is much like the GTK+ "
646
"Greeter in that it is controlled by the underlying daemon, is stateless, and "
647
"is controlled by the daemon using the same simple protocol."
648
msgstr ""
649
650
#: ../C/gdm.xml:533(para)
651
msgid ""
652
"The look and feel of this greeter is really controlled by the theme and so "
653
"the user interface elements that are present may be different. The only "
654
"thing that must always be present is the text entry field as described above "
655
"in the GTK+ Greeter. The theme can include buttons that allow the user to "
656
"select an appropriate locale/language, halt/restart/suspend the computer, "
657
"configure GDM (given the user knows the root password), or start an XDMCP "
658
"chooser."
659
msgstr ""
660
661
#: ../C/gdm.xml:543(para)
662
msgid ""
663
"You can always get a menu of available actions by pressing the F10 key. This "
664
"can be useful if the theme doesn't provide certain buttons when you wish to "
665
"do some action allowed by the GDM configuration."
666
msgstr ""
667
668
#: ../C/gdm.xml:551(title)
669
msgid "The GDM Face Browser"
670
msgstr ""
671
672
#: ../C/gdm.xml:553(para)
673
msgid ""
674
"GDM supports a face browser which will display a list of users who can login "
675
"and an icon for each user. Starting with version 2.18.1 the "
676
"<filename>Browser</filename> configuration option must be set to \"true\" "
677
"for this function to be available. In previous versions it was only required "
678
"when using the GTK+ Greeter. When using the Themed Greeter, the Face Browser "
679
"is only available if the GDM theme includes a \"userlist\" item type."
680
msgstr ""
681
682
#: ../C/gdm.xml:563(para)
683
msgid ""
684
"By default, the face browser is disabled since revealing usernames on the "
685
"login screen is not appropriate on many systems for security reasons. Also "
686
"GDM requires some setup to specify which users should be visible. Setup can "
687
"be done on the \"Users\" tab in <command>gdmsetup</command>. This feature is "
688
"most practical to use on a system with a smaller number of users."
689
msgstr ""
690
691
#: ../C/gdm.xml:572(para)
692
msgid ""
693
"The icons used by GDM can be installed globally by the sysadmin or can be "
694
"located in the users' home directories. If installed globally they should be "
695
"in the <filename><share>/pixmaps/faces/</filename> directory (though "
696
"this can be configured with the <filename>GlobalFaceDir</filename> "
697
"configuration option) and the filename should be the name of the user, "
698
"optionally with a <filename>.png</filename> appended. Face icons placed in "
699
"the global face directory must be readable to the GDM user. However, the "
700
"daemon, proxies user pictures to the greeter and thus those do not have be "
701
"be readable by the \"gdm\" user, but root."
702
msgstr ""
703
704
#: ../C/gdm.xml:585(para)
705
msgid ""
706
"Users may run the <command>gdmphotosetup</command> command to configure the "
707
"image to use for their userid. This program properly scales the file down if "
708
"it is larger than the <filename>MaxIconWidth</filename> or "
709
"<filename>MaxIconHeight</filename> configuration options and places the icon "
710
"in a file called <filename>~/.face</filename>. Although "
711
"<command>gdmphotosetup</command> scales user images automatically, this does "
712
"not guarantee that user images are properly scaled since a user may create "
713
"their <filename>~/.face</filename> file by hand."
714
msgstr ""
715
716
#: ../C/gdm.xml:597(para)
717
msgid ""
718
"GDM will first look for the user's face image in <filename>~/.face</"
719
"filename>. If not found, it will try <filename>~/.face.icon</filename>. If "
720
"still not found, it will use the value defined for \"face/picture=\" in the "
721
"<filename>~/.gnome2/gdm</filename> file. Lastly, it will try <filename>~/."
722
"gnome2/photo</filename> and <filename>~/.gnome/photo</filename> which are "
723
"deprecated and supported for backwards compatibility."
724
msgstr ""
725
726
#: ../C/gdm.xml:608(para)
727
msgid ""
728
"If a user has no defined face image, GDM will use the \"stock_person\" icon "
729
"defined in the current GTK+ theme. If no such image is defined, it will "
730
"fallback to the image specified in the <filename>DefaultFace</filename> "
731
"configuration option, normally <filename><share>/pixmaps/nobody.png</"
732
"filename>."
733
msgstr ""
734
735
#: ../C/gdm.xml:616(para)
736
msgid ""
737
"Please note that loading and scaling face icons located in user home "
738
"directories can be a very time-consuming task. Since it not practical to "
739
"load images over NIS or NFS, GDM does not attempt to load face images from "
740
"remote home directories. Furthermore, GDM will give up loading face images "
741
"after 5 seconds of activity and will only display the users whose pictures "
742
"it has gotten so far. The <filename>Include</filename> configuration option "
743
"can be used to specify a set of users who should appear on the face browser. "
744
"As long as the users to include is of a reasonable size, there should not be "
745
"a problem with GDM being unable to access the face images. To work around "
746
"such problems, it is recommended to place face images in the directory "
747
"specified by the <filename>GlobalFaceDir</filename> configuration option."
748
msgstr ""
749
750
#: ../C/gdm.xml:632(para)
751
msgid ""
752
"To control the users who get displayed in the face browser, there are a "
753
"number of configuration options that can be used. If the "
754
"<filename>IncludeAll</filename> option is set to true, then the password "
755
"file will be scanned and all users will be displayed. If "
756
"<filename>IncludeAll</filename> option is set to false, then the "
757
"<filename>Include</filename> option should contain a list of users separated "
758
"by commas. Only the users specified will be displayed. Any user listed in "
759
"the <filename>Exclude</filename> option and users whose UID's is lower than "
760
"<filename>MinimalUID</filename> will be filtered out regardless of the "
761
"<filename>IncludeAll</filename> setting. <filename>IncludeAll</filename> is "
762
"not recommended for systems where the passwords are loaded over a network "
763
"(such as when NIS is used), since it can be very slow to load more than a "
764
"small number of users over the network.."
765
msgstr ""
766
767
#: ../C/gdm.xml:649(para)
768
msgid ""
769
"When the browser is turned on, valid usernames on the computer are "
770
"inherently exposed to a potential intruder. This may be a bad idea if you do "
771
"not know who can get to a login screen. This is especially true if you run "
772
"XDMCP (turned off by default)."
773
msgstr ""
774
775
#: ../C/gdm.xml:658(title)
776
msgid "Logging"
777
msgstr ""
778
779
#: ../C/gdm.xml:660(para)
780
msgid ""
781
"GDM itself will use syslog to log errors or status. It can also log "
782
"debugging information, which can be useful for tracking down problems if GDM "
783
"is not working properly. This can be enabled in the configuration file."
784
msgstr ""
785
786
#: ../C/gdm.xml:667(para)
787
msgid ""
788
"Output from the various X servers is stored in the GDM log directory, which "
789
"is configurable, but is usually <filename><var>/log/gdm/</filename>. "
790
"The output from the session can be found in a file called <filename><"
791
"display>.log</filename>. Four older files are also stored with "
792
"<filename>.1</filename> through <filename>.4</filename> appended. These will "
793
"be rotated as new sessions on that display are started. You can use these "
794
"logs to view what the X server said when it started up."
795
msgstr ""
796
797
#: ../C/gdm.xml:679(para)
798
msgid ""
799
"The output from the user session is redirected to <filename>~/.xsession-"
800
"errors</filename> before even the <filename>PreSession</filename> script is "
801
"started. So it is not really necessary to redirect this again in the session "
802
"setup script. As is usually done. If the user session lasted less then 10 "
803
"seconds, GDM assumes that the session crashed and allows the user to view "
804
"this file in a dialog before returning to the login screen. This way the "
805
"user can view the session errors from the last session and correct the "
806
"problem this way."
807
msgstr ""
808
809
#: ../C/gdm.xml:691(para)
810
msgid ""
811
"You can suppress the 10 second warning by returning code 66 from the "
812
"<filename>Xsession</filename>script or from your session binary (the default "
813
"<filename>Xsession</filename> script propagates those codes back). This is "
814
"useful if you have some sort of special logins for which it is not an error "
815
"to return less then 10 seconds later, or if you setup the session to already "
816
"display some error message and the GDM message would be confusing and "
817
"redundant."
818
msgstr ""
819
820
#: ../C/gdm.xml:701(para)
821
msgid ""
822
"The session output is piped through the GDM daemon and so the <filename>~/."
823
"xsession-errors</filename> file is capped at about 200 kilobytes by GDM to "
824
"prevent a possible denial of service attack on the session. An application "
825
"could perhaps on reading some wrong data print out warnings or errors on the "
826
"stderr or stdout. This could perhaps fill up the user's home directory "
827
"making it necessary to log out and back into their session to clear this. "
828
"This could be especially nasty if quotas are set. GDM also correctly traps "
829
"the XFSZ signal and stops writing the file, which would lead to killed "
830
"sessions if the file was redirected in the old fashioned way from the script."
831
msgstr ""
832
833
#: ../C/gdm.xml:714(para)
834
msgid ""
835
"Note that some distributors seem to override the <filename>~/.xsession-"
836
"errors</filename> redirection and do it themselves in their own Xsession "
837
"script (set by the <filename>BaseXsession</filename> configuration key) "
838
"which means that GDM will not be able to trap the output and cap this file. "
839
"You also lose output from the <filename>PreSession</filename> script which "
840
"can make debugging things harder to figure out as perhaps useful output of "
841
"what is wrong will not be printed out. See the description of the "
842
"<filename>BaseXsession</filename> configuration key for more information, "
843
"especially on how to handle multiple display managers using the same script."
844
msgstr ""
845
846
#: ../C/gdm.xml:728(para)
847
msgid ""
848
"Note that if the session is a failsafe session, or if GDM can't open this "
849
"file for some reason, then a fallback file will be created in the <filename>/"
850
"tmp</filename> directory named <filename>/tmp/xses-<user>.XXXXXX</"
851
"filename> where the <filename>XXXXXX</filename> are some random characters."
852
msgstr ""
853
854
#: ../C/gdm.xml:736(para)
855
msgid ""
856
"If you run a system with quotas set, it would be good to delete the "
857
"<filename>~/.xsession-errors</filename> in the <filename>PostSession</"
858
"filename> script. Such that this log file doesn't unnecessarily stay around."
859
msgstr ""
860
861
#: ../C/gdm.xml:745(title)
862
msgid "Accessing Files"
863
msgstr ""
864
865
#: ../C/gdm.xml:747(para)
866
msgid ""
867
"In general GDM is very reluctant regarding reading/writing of user files "
868
"(such as the <filename>~/.dmrc</filename>, <filename>~/.face</filename>, "
869
"<filename>~/.xsession-errors</filename>, and <filename>~/.Xauthority</"
870
"filename> files). For instance it refuses to access anything but regular "
871
"files. Links, sockets and devices are ignored. The value of the "
872
"<filename>RelaxPermissions</filename> parameter determines whether GDM "
873
"should accept files writable by the user's group or others. These are "
874
"ignored by default."
875
msgstr ""
876
877
#: ../C/gdm.xml:759(para)
878
msgid ""
879
"All operations on user files are done with the effective user id of the "
880
"user. If the sanity check fails on the user's <filename>.Xauthority</"
881
"filename> file, a fallback cookie is created in the directory specified by "
882
"the <filename>UserAuthFBDir</filename> configuration setting (<filename>/"
883
"tmp</filename> by default)."
884
msgstr ""
885
886
#: ../C/gdm.xml:767(para)
887
msgid ""
888
"Finally, the sysadmin can specify the maximum file size GDM should accept, "
889
"and, if the face browser is enabled, a tunable maximum icon size is also "
890
"enforced. On large systems it is still advised to turn off the face browser "
891
"for performance reasons. Looking up icons in home directories, scaling and "
892
"rendering face icons can take a long time."
893
msgstr ""
894
895
#: ../C/gdm.xml:778(title)
896
msgid "GDM Performance"
897
msgstr ""
898
899
#: ../C/gdm.xml:780(para)
900
msgid ""
901
"To speed performance it is possible to build GDM so that it will preload "
902
"libraries when GDM first displays a greeter program. This has been shown to "
903
"speed first time login since these libraries can be loaded into memory while "
904
"the user types in their username and password."
905
msgstr ""
906
907
#: ../C/gdm.xml:788(para)
908
msgid ""
909
"To use this feature, configure GDM with the <command>--with-prefetch</"
910
"command> option. This will cause GDM to install the <command>gdmprefetch</"
911
"command> program to the <filename>libexecdir</filename> directory, install "
912
"the <filename>gdmprefetchlist</filename> to the <filename><etc>/gdm</"
913
"filename> directory, and set the <filename>PreFetchProgram</filename> "
914
"configuration variable so that the <command>gdmprefetch</command> program is "
915
"called with the default <filename>gdmprefetchlist</filename> file. The "
916
"default <filename>gdmprefetchlist</filename> file was optimized for a GNOME "
917
"desktop running on Solaris, so may need fine-tuning on other systems. "
918
"Alternative prefetchlist files can be contributed to the \"gdm\" category in "
919
"<ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome.org</"
920
"ulink>, so that they can be included in future GDM releases."
921
msgstr ""
922
923
#: ../C/gdm.xml:809(title)
924
msgid "Security"
925
msgstr ""
926
927
#: ../C/gdm.xml:812(title)
928
msgid "PAM"
929
msgstr ""
930
931
#: ../C/gdm.xml:816(para)
932
msgid ""
933
"GDM uses PAM for login authentication, though if your machine does not "
934
"support PAM you can build GDM to work with the password database and the "
935
"crypt library function."
936
msgstr ""
937
938
#: ../C/gdm.xml:822(para)
939
msgid ""
940
"PAM stands for Pluggable Authentication Module, and is used by most programs "
941
"that request authentication on your computer. It allows the administrator to "
942
"configure different authentication behavior for different programs."
943
msgstr ""
944
945
#: ../C/gdm.xml:829(para)
946
msgid ""
947
"Some GDM features (like turning on automatic login) may require that you "
948
"update your PAM configuration. PAM configuration has different, but similar, "
949
"interfaces on different operating systems, so check your pam.d or pam.conf "
950
"man page for details. Be sure that you read the PAM documentation (e.g. pam."
951
"d/pam.conf man page) and are comfortable with the security implications of "
952
"any changes you intend to make to your configuration."
953
msgstr ""
954
955
#: ../C/gdm.xml:839(para)
956
msgid ""
957
"If there is no entry for GDM in your system's PAM configuration file, then "
958
"features like automatic login may not work. Not having an entry will cause "
959
"GDM to use default behavior, conservative settings are recommended and "
960
"probably shipped with your distribution."
961
msgstr ""
962
963
#: ../C/gdm.xml:846(para)
964
msgid ""
965
"If you wish to make GDM work with other types of authentication mechanisms "
966
"(such as a SmartCard), then you should implement this by using a PAM service "
967
"module for the desired authentication type rather than by trying to modify "
968
"the GDM code directly. Refer to the PAM documentation on your system. This "
969
"issue has been discussed on the <address><email>gdm-list@gnome.org</email></"
970
"address> mail list, so you can refer to the list archives for more "
971
"information."
972
msgstr ""
973
974
#: ../C/gdm.xml:856(para)
975
msgid ""
976
"For example, an effective way to implement such an exotic authentication "
977
"mechanism would be to have a daemon running on the server listening to the "
978
"authentication device (e.g. USB key, fingerprint reader, etc.). When the "
979
"device announces that it has received input, then the daemon can set the "
980
"<filename>PamStack</filename> configuration value using per-display "
981
"configuration, and restart the greeter with the PAM stack that works with "
982
"this device. This avoids needing to hack the display manager code directly "
983
"to support the feature."
984
msgstr ""
985
986
#: ../C/gdm.xml:871(title)
987
msgid "The GDM User"
988
msgstr ""
989
990
#: ../C/gdm.xml:873(para)
991
msgid ""
992
"For security reasons a dedicated user and group id are required for proper "
993
"operation! The need to be able to write Xauth files is why user \"nobody\" "
994
"is not appropriate for gdm."
995
msgstr ""
996
997
#: ../C/gdm.xml:879(para)
998
msgid ""
999
"The GDM daemon normally runs as root, as does the slave. However GDM should "
1000
"also have a dedicated user id and a group id which it uses for its graphical "
1001
"interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</"
1002
"command>. These are configured via the <filename>User</filename> and "
1003
"<filename>Group</filename> configuration options in the GDM configuration "
1004
"files. The user and group should be created before running \"make install\". "
1005
"By default GDM assumes the user and the group are called \"gdm\"."
1006
msgstr ""
1007
1008
#: ../C/gdm.xml:890(para)
1009
msgid ""
1010
"This userid is used to run the GDM GUI programs required for login. All "
1011
"functionality that requires root authority is done by the GDM daemon "
1012
"process. This design ensures that if the GUI programs are somehow exploited, "
1013
"only the dedicated user privileges are available."
1014
msgstr ""
1015
1016
#: ../C/gdm.xml:897(para)
1017
msgid ""
1018
"It should however be noted that the GDM user and group have some privileges "
1019
"that make them somewhat dangerous. For one, they have access to the X server "
1020
"authorization directory. It must be able to read and write Xauth keys to "
1021
"<filename><var>/lib/gdm</filename>. This directory should have root:"
1022
"gdm ownership and 1770 permissions. Running \"make install\" will set this "
1023
"directory to these values. The GDM daemon process will reset this directory "
1024
"to proper ownership/permissions if it is somehow not set properly."
1025
msgstr ""
1026
1027
#: ../C/gdm.xml:908(para)
1028
msgid ""
1029
"The danger is that someone who gains the GDM user/group privileges can then "
1030
"connect to any session. So you should not, under any circumstances, make "
1031
"this some user/group which may be easy to get access to, such as the user "
1032
"<filename>nobody</filename>. Users who gain access to the \"gdm\" user could "
1033
"also modify the Xauth keys causing Denial-Of-Service attacks. Also if a "
1034
"person gains the ability to run programs as the user \"gdm\", it would be "
1035
"possible to snoop on running GDM processes, including usernames and "
1036
"passwords as they are being typed in."
1037
msgstr ""
1038
1039
#: ../C/gdm.xml:920(para)
1040
msgid ""
1041
"Distributions and system administrators using GDM are expected to setup the "
1042
"dedicated user properly. It is recommended that this userid be configured to "
1043
"disallow login and to not have a default shell. Distributions and system "
1044
"administrators should set up the filesystem to ensure that the GDM user does "
1045
"not have read or write access to sensitive files."
1046
msgstr ""
1047
1048
#: ../C/gdm.xml:931(title)
1049
msgid "X Server Authentication Scheme"
1050
msgstr ""
1051
1052
#: ../C/gdm.xml:933(para)
1053
msgid ""
1054
"The X server authorization directory (the <filename>ServAuthDir</filename>) "
1055
"is used for a host of random internal data in addition to the X server "
1056
"authorization files, and the naming is really a relic of history. GDM daemon "
1057
"enforces this directory to be owned by <filename>root.gdm</filename> with "
1058
"the permissions of 1770. This way, only root and the GDM group have write "
1059
"access to this directory, but the GDM group cannot remove the root owned "
1060
"files from this directory, such as the X server authorization files."
1061
msgstr ""
1062
1063
#: ../C/gdm.xml:945(para)
1064
msgid ""
1065
"GDM by default doesn't trust the X server authorization directory and treats "
1066
"it in the same way as the temporary directory with respect to creating "
1067
"files. This way someone breaking the GDM user cannot mount attacks by "
1068
"creating links in this directory. Similarly the X server log directory is "
1069
"treated safely, but that directory should really be owned and writable only "
1070
"by root."
1071
msgstr ""
1072
1073
#: ../C/gdm.xml:954(para)
1074
msgid ""
1075
"GDM only supports the MIT-MAGIC-COOKIE-1 X server authentication scheme. "
1076
"Normally little is gained from the other schemes, and no effort has been "
1077
"made to implement them so far. Be especially careful about using XDMCP "
1078
"because the X server authentication cookie goes over the wire as clear text. "
1079
"If snooping is possible, then an attacker could simply snoop your "
1080
"authentication password as you log in, regardless of the authentication "
1081
"scheme being used. If snooping is possible and undesirable, then you should "
1082
"use ssh for tunneling an X connection rather then using XDMCP. You could "
1083
"think of XDMCP as a sort of graphical telnet, having the same security "
1084
"issues."
1085
msgstr ""
1086
1087
#: ../C/gdm.xml:967(para)
1088
msgid ""
1089
"On the upside, GDM's random number generation is very conservative and GDM "
1090
"goes to extraordinary measures to truly get a 128 bit random number, using "
1091
"hardware random number generators (if available), plus the current time (in "
1092
"microsecond precision), a 20 byte array of pseudorandom numbers, process "
1093
"pid's, and other random information (possibly using <filename>/dev/audio</"
1094
"filename> or <filename>/dev/mem</filename> if hardware random generators are "
1095
"not available) to create a large buffer and then run MD5 digest on this. "
1096
"Obviously, all this work is wasted if you send this cookie over an open "
1097
"network or store it on an NFS directory (see <filename>UserAuthDir</"
1098
"filename> configuration key). So be careful about where you use remote X "
1099
"display."
1100
msgstr ""
1101
1102
#: ../C/gdm.xml:984(title)
1103
msgid "Firewall Security"
1104
msgstr ""
1105
1106
#: ../C/gdm.xml:986(para)
1107
msgid ""
1108
"Even though GDM tries to outsmart potential attackers trying to take "
1109
"advantage of XDMCP, it is still advised that you block the XDMCP port "
1110
"(normally UDP port 177) on your firewall unless you really need it. GDM "
1111
"guards against DoS (Denial of Service) attacks, but the X protocol is still "
1112
"inherently insecure and should only be used in controlled environments. Also "
1113
"each remote connection takes up lots of resources, so it is much easier to "
1114
"DoS via XDMCP then a webserver."
1115
msgstr ""
1116
1117
#: ../C/gdm.xml:996(para)
1118
msgid ""
1119
"It is also wise to block all of the X Server ports. These are TCP ports 6000 "
1120
"+ the display number of course) on your firewall. Note that GDM will use "
1121
"display numbers 20 and higher for flexible on-demand servers."
1122
msgstr ""
1123
1124
#: ../C/gdm.xml:1003(para)
1125
msgid ""
1126
"X is not a very safe protocol for leaving on the net, and XDMCP is even less "
1127
"safe."
1128
msgstr ""
1129
1130
#: ../C/gdm.xml:1010(title)
1131
msgid "GDM Security With NFS"
1132
msgstr ""
1133
1134
#: ../C/gdm.xml:1012(para)
1135
msgid ""
1136
"Note that NFS traffic really goes \"over the wire\" and thus can be snooped. "
1137
"When accessing the user's X authorization file (<filename>~/.Xauthority</"
1138
"filename>), GDM will try to open the file for reading as root. If it fails, "
1139
"GDM will conclude that it is on an NFS mount and it will automatically use "
1140
"<filename>UserAuthFBDir</filename>, which by default is set to <filename>/"
1141
"tmp</filename>. This behavior can be changed by setting the "
1142
"<filename>NeverPlaceCookiesOnNFS</filename> in the <filename>[security]</"
1143
"filename> section to false."
1144
msgstr ""
1145
1146
#: ../C/gdm.xml:1026(title)
1147
msgid "XDMCP Security"
1148
msgstr ""
1149
1150
#: ../C/gdm.xml:1028(para)
1151
msgid ""
1152
"Even though your display is protected by cookies, XEvents and thus "
1153
"keystrokes typed when entering passwords will still go over the wire in "
1154
"clear text. It is trivial to capture these."
1155
msgstr ""
1156
1157
#: ../C/gdm.xml:1034(para)
1158
msgid ""
1159
"XDMCP is primarily useful for running thin clients such as in terminal labs. "
1160
"Those thin clients will only ever need the network to access the server, and "
1161
"so it seems like the best security policy to have those thin clients on a "
1162
"separate network that cannot be accessed by the outside world, and can only "
1163
"connect to the server. The only point from which you need to access outside "
1164
"is the server."
1165
msgstr ""
1166
1167
#: ../C/gdm.xml:1043(para)
1168
msgid ""
1169
"The above sections \"X Server Authentication Scheme\" and \"Firewall Security"
1170
"\" also contain important information about using XDMCP securely. The next "
1171
"section also discusses how to set up XDMCP access control."
1172
msgstr ""
1173
1174
#: ../C/gdm.xml:1050(para)
1175
msgid ""
1176
"To workaround the inherent insecurity of XDMCP, gdm proposes a default built-"
1177
"in session that uses SSH to encrypt the remote connection. See the section "
1178
"\"Securing remote connection through SSH\" above."
1179
msgstr ""
1180
1181
#: ../C/gdm.xml:1058(title)
1182
msgid "XDMCP Access Control"
1183
msgstr ""
1184
1185
#: ../C/gdm.xml:1060(para)
1186
msgid ""
1187
"XDMCP access control is done using TCP wrappers. It is possible to compile "
1188
"GDM without TCP wrappers however, so you should test your configuration and "
1189
"verify that they work."
1190
msgstr ""
1191
1192
#: ../C/gdm.xml:1066(para)
1193
msgid ""
1194
"You should use the daemon name <command>gdm</command> in the <filename><"
1195
"etc>/hosts.allow</filename> and <filename><etc>/hosts.deny</"
1196
"filename> files. For example to deny computers from <filename>.evil.domain</"
1197
"filename> from logging in, then add"
1198
msgstr ""
1199
1200
#: ../C/gdm.xml:1073(screen)
1201
#, no-wrap
1202
msgid ""
1203
"\n"
1204
"gdm: .evil.domain\n"
1205
msgstr ""
1206
1207
#: ../C/gdm.xml:1076(para)
1208
msgid "to <filename><etc>/hosts.deny</filename>. You may also need to add"
1209
msgstr ""
1210
1211
#: ../C/gdm.xml:1080(screen)
1212
#, no-wrap
1213
msgid ""
1214
"\n"
1215
"gdm: .your.domain\n"
1216
msgstr ""
1217
1218
#: ../C/gdm.xml:1083(para)
1219
msgid ""
1220
"to your <filename><etc>/hosts.allow</filename> if you normally "
1221
"disallow all services from all hosts. See the <ulink type=\"help\" url=\"man:"
1222
"hosts.allow\">hosts.allow(5)</ulink> man page for details."
1223
msgstr ""
1224
1225
#: ../C/gdm.xml:1092(title)
1226
msgid "RBAC (Role Based Access Control)"
1227
msgstr ""
1228
1229
#: ../C/gdm.xml:1094(para)
1230
msgid ""
1231
"If GDM is compiled with RBAC support, then the "
1232
"<filename>RBACSystemCommandKeys</filename> configuration option can be used "
1233
"to specify the RBAC key to be used to determine if the user has authority to "
1234
"use commands. This is supported for the Shutdown, Reboot, Suspend, and "
1235
"Custom Commands that appear in the GDM greeter and via the "
1236
"<command>gdmflexiserver</command> QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, "
1237
"and SET_SAFE_LOGOUT_ACTION commands. The greeter will only display the "
1238
"option if the gdm user (specified by the <filename>User</filename> "
1239
"configuration option) has permission via RBAC. Users will only be able to "
1240
"use the <command>gdmflexiserver</command> commands if the user has "
1241
"permission via RBAC."
1242
msgstr ""
1243
1244
#: ../C/gdm.xml:1112(title)
1245
msgid "Support for ConsoleKit"
1246
msgstr ""
1247
1248
#: ../C/gdm.xml:1114(para)
1249
msgid ""
1250
"GDM includes support for publishing user login information with the user and "
1251
"login session accounting framework known as ConsoleKit. ConsoleKit is able "
1252
"to keep track of all the users currently logged in. In this respect, it can "
1253
"be used as a replacement for the utmp or utmpx files that are available on "
1254
"most Unix-like operating systems."
1255
msgstr ""
1256
1257
#: ../C/gdm.xml:1122(para)
1258
msgid ""
1259
"When GDM is about to create a new login process for a user it will call a "
1260
"privileged method of ConsoleKit in order to open a new session for this "
1261
"user. At this time GDM also provides ConsoleKit with information about this "
1262
"user session such as: the user ID, the X11 Display name that will be "
1263
"associated with the session, the host-name from which the session originates "
1264
"(useful in the case of an XDMCP session), whether or not this session is "
1265
"local, etc. As the entity that initiates the user process, GDM is in a "
1266
"unique position know and to be trusted to provide these bits of information "
1267
"about the user session. The use of this privileged method is restricted by "
1268
"the use of D-Bus system message bus security policy."
1269
msgstr ""
1270
1271
#: ../C/gdm.xml:1135(para)
1272
msgid ""
1273
"In the case where a user with an existing session and has authenticated at "
1274
"GDM and requests to resume that existing session GDM calls a privileged "
1275
"method of ConsoleKit to unlock that session. The exact details of what "
1276
"happens when the session receives this unlock signal is undefined and "
1277
"session-specific. However, most sessions will unlock a screensaver in "
1278
"response."
1279
msgstr ""
1280
1281
#: ../C/gdm.xml:1144(para)
1282
msgid ""
1283
"When the user chooses to log out, or if GDM or the session quit unexpectedly "
1284
"the user session will be unregistered from ConsoleKit."
1285
msgstr ""
1286
1287
#: ../C/gdm.xml:1149(para)
1288
msgid ""
1289
"If support for ConsoleKit is not desired it can be disabled at build time "
1290
"using the \"--with-console-kit=no\" option when running configure."
1291
msgstr ""
1292
1293
#: ../C/gdm.xml:1158(title)
1294
msgid "Using gdmsetup To Configure GDM"
1295
msgstr ""
1296
1297
#: ../C/gdm.xml:1160(para)
1298
msgid ""
1299
"The <command>gdmsetup</command> application can be used to configure GDM. If "
1300
"you believe running root-owned GUI's causes security risk, then you would "
1301
"want to always edit the files by hand and not use <command>gdmsetup</"
1302
"command>. Editing the files by hand is explained in the \"Configuration\" "
1303
"section of this document. Note that <command>gdmsetup</command> does not "
1304
"support changing of all configuration variables, so it may be necessary to "
1305
"edit the files by hand for some configurations."
1306
msgstr ""
1307
1308
#: ../C/gdm.xml:1171(para)
1309
msgid ""
1310
"The <command>gdmsetup</command> program has five tabs: Local, Remote, "
1311
"Accessibility, Security, and Users, described below. In parenthesis is "
1312
"information about which GDM configuration key is affected by each GUI "
1313
"choice. Refer to the \"Configuration\" section of this manual and the "
1314
"comments in the GDM System Defaults Configuration File for additional "
1315
"details about each key."
1316
msgstr ""
1317
1318
#: ../C/gdm.xml:1181(title)
1319
msgid "Local Tab"
1320
msgstr ""
1321
1322
#: ../C/gdm.xml:1183(para)
1323
msgid ""
1324
"The Local tab is used for controlling the appearance of GDM for local/static "
1325
"displays (non-XDMCP remote connections). The choices available in this tab "
1326
"depend on the setting of the \"Style\" combobox. This combobox is used to "
1327
"determine whether the \"Plain\" or \"Themed\" greeter GUI is used. The "
1328
"differences between these greeter programs are explained in the \"Overview\" "
1329
"section of this document."
1330
msgstr ""
1331
1332
#: ../C/gdm.xml:1193(para)
1333
msgid ""
1334
"If the \"Style\" choice is \"Plain\", then GDM will use the "
1335
"<command>gdmlogin</command> program as the GUI (daemon/Greeter). When this "
1336
"choice is selected, <command>gdmsetup</command> allows the user to select "
1337
"whether the background is an image or solid color (greeter/BackgroundType). "
1338
"If image is selected, there is a file selection button to pick the image "
1339
"file (greeter/BackgroundImage) and a checkbox to scale the image to fit the "
1340
"screen (greeter/BackgroundImageScaleToFit). If solid color is selected, "
1341
"there is a button available to allow the color selection (greeter/"
1342
"BackgroundColor). Also, the user may select the logo image that appears in "
1343
"gdmlogin (greeter/Logo)."
1344
msgstr ""
1345
1346
#: ../C/gdm.xml:1207(para)
1347
msgid ""
1348
"If the \"Style\" choice is \"Plain with face browser\", then the "
1349
"<command>gdmlogin</command> program is used as the GUI (daemon/Greeter) and "
1350
"the face browser is turned on (greeter/Browser). The Face Browser is "
1351
"explained in the \"Overview\" section. Otherwise, the choices are the same "
1352
"as when the \"Style\" choice is \"Plain\". Additional setup in the Users tab "
1353
"may be necessary to choose which users appear in the Face Browser."
1354
msgstr ""
1355
1356
#: ../C/gdm.xml:1217(para)
1357
msgid ""
1358
"If the \"Style\" choice is \"Themed\", then the <command>gdmgreeter</"
1359
"command> program is used as the GUI (daemon/Greeter). When this choice is "
1360
"selected, <command>gdmsetup</command> allows the user to select the theme to "
1361
"be used (greeter/GraphicalTheme). Note that the checkbox to the left of the "
1362
"theme's name must be checked for a theme to be selected. Information about "
1363
"the theme's author and copyright are shown for the highlighted theme. The "
1364
"\"Remove\" button can be used to delete the highlighted theme. The \"Add\" "
1365
"button can be used to add new themes to the system. For a new theme to be "
1366
"added it must be in tar or compressed tar format. The \"Background color\" "
1367
"displayed when GDM starts (and if the theme has transparent elements) can be "
1368
"selected (greeter/GraphicalThemedColor). The \"Theme\" combo box may be set "
1369
"to \"Random from selected\" to display a random theme for each login "
1370
"(greeter/GraphicalThemeRand and greeter/GraphicalThemes). To use random "
1371
"themes, select each theme that you wish to be displayed. By default this "
1372
"combobox is set to \"Selected only\", so that only a single theme may be "
1373
"selected and be used."
1374
msgstr ""
1375
1376
#: ../C/gdm.xml:1239(para)
1377
msgid ""
1378
"If the \"Style\" choice is \"Themed with face browser\", then the "
1379
"<command>gdmgreeter</command> program is used as the GUI (daemon/Greeter) "
1380
"and the face browser is turned on (greeter/Browser) if supported by the "
1381
"theme. The Face Browser is explained in the Overview section. Otherwise, the "
1382
"choices are the same as when the \"Style\" choice is \"Themed\". Additional "
1383
"setup in the Users tab may be necessary to choose which users appear in the "
1384
"Face Browser."
1385
msgstr ""
1386
1387
#: ../C/gdm.xml:1250(para)
1388
msgid ""
1389
"Regardless of the \"Style\" choice, the user may also select whether the "
1390
"Actions menu is visible (greeter/SystemMenu), whether the Actions menu "
1391
"includes the choice to start <command>gdmsetup</command> (greeter/"
1392
"ConfigAvailable), and whether the Action menu includes the choice to start "
1393
"<command>gdmchooser</command> to run a remote XDMCP login session (greeter/"
1394
"ChooserButton). Note that the root password must be entered to start "
1395
"<command>gdmsetup</command> from the login screen if it is enabled. Also the "
1396
"Welcome message displayed for local sessions may be selected (greeter/"
1397
"DefaultWelcome and greeter/Welcome). The Welcome message can contain the "
1398
"character sequences described in the \"Text Node\" section of the \"Themed "
1399
"Greeter\" section of this manual."
1400
msgstr ""
1401
1402
#: ../C/gdm.xml:1267(title)
1403
msgid "Remote Tab"
1404
msgstr ""
1405
1406
#: ../C/gdm.xml:1269(para)
1407
msgid ""
1408
"The Remote tab controls the appearance of the GDM for users logging in via "
1409
"XDMCP. By default XDMCP is disabled, and users should be comfortable with "
1410
"the XDMCP-related sections of the Security section of this document before "
1411
"enabling it. This tab includes a \"Style\" combobox which can be used to "
1412
"turn on XDMCP and control the appearance of GDM for remote users (gui/"
1413
"RemoteGreeter and xdmcp/Enable). The user may specify to use either the same "
1414
"greeter as used on the Local tab, or the other Greeter program. If the Face "
1415
"Browser setting is true on the Local tab, then it will also be true for the "
1416
"Remote tab. If the Face Browser setting is false on the Local tab, then it "
1417
"will also be false for the Remote tab. It is recommended that the \"Plain\" "
1418
"GUI be used for remote connections since it is more lightweight and tends to "
1419
"have better performance across a network."
1420
msgstr ""
1421
1422
#: ../C/gdm.xml:1286(para)
1423
msgid ""
1424
"If Remote login is enabled, then the user can specify the remote Welcome "
1425
"Message to be displayed (greeter/DefaultRemoteWelcome and greeter/"
1426
"RemoteWelcome). This welcome message is separate from the Local welcome "
1427
"message and can have a different value. The Welcome message can contain the "
1428
"character sequences described in the \"Text Node\" section of the \"Themed "
1429
"Greeter\" section of this manual."
1430
msgstr ""
1431
1432
#: ../C/gdm.xml:1296(para)
1433
msgid ""
1434
"If the \"Style\" choice is \"Same as Local\" and the local selection is "
1435
"\"Plain\" or \"Plain with face browser\", then the user may select whether "
1436
"background images should be displayed for remote logins (greeter/"
1437
"BackgroundRemoteOnlyColor)."
1438
msgstr ""
1439
1440
#: ../C/gdm.xml:1304(para)
1441
msgid ""
1442
"If the \"Style\" choice is enabled and set to a different value than the "
1443
"Local tab, then the user has the same configuration choices as found on the "
1444
"Local tab except that the System Menu choices are not available since this "
1445
"is never available for remote logins for security purposes."
1446
msgstr ""
1447
1448
#: ../C/gdm.xml:1312(para)
1449
msgid ""
1450
"If Remote login is enabled, there is a \"Configure XDMCP\" button which "
1451
"displays a dialog allowing the user to set XDMCP configuration, including "
1452
"whether indirect requests are honored (xdmcp/HonorIndirect), UDP port (xdmcp/"
1453
"Port), maximum pending requests (xdmcp/MaxPending), maximum pending indirect "
1454
"requests (xmdcp/MaxPendingIndirect), maximum remote sessions (xdmcp/"
1455
"MaxSessions), maximum wait time (xdmcp/MaxWait), maximum indirect wait time "
1456
"(xdmcp/MaxWaitIndirect), displays per host (xdmcp/DisplaysPerHost), and ping "
1457
"interval (xdmcp/PingIntervalSeconds). The default settings are standard "
1458
"settings and should only be changed by someone who understands the "
1459
"ramifications of the change."
1460
msgstr ""
1461
1462
#: ../C/gdm.xml:1328(title)
1463
msgid "Accessibility Tab"
1464
msgstr ""
1465
1466
#: ../C/gdm.xml:1330(para)
1467
msgid ""
1468
"The Accessibility tab is used to turn on Accessibility features in GDM. "
1469
"\"Enable accessible login\" (daemon/AddGtkModules and daemon/GtkModulesList) "
1470
"turns on GDM's gesture listeners which are explained in the \"Accessibility"
1471
"\" section of this document. There is also a checkbox to allow users to "
1472
"change the theme when using the Plain greeter (gui/AllowGtkThemeChange). "
1473
"This feature allows GDM users to switch the theme to the HighContrast or "
1474
"LowContrast themes if needed. The user may also select whether GDM should "
1475
"play a sound when the login screen is ready, when login is successful and "
1476
"when login has failed. File chooser buttons are used to select the sound "
1477
"file to be played, and the \"Play\" button can be used to sample the sound."
1478
msgstr ""
1479
1480
#: ../C/gdm.xml:1347(title)
1481
msgid "Security Tab"
1482
msgstr ""
1483
1484
#: ../C/gdm.xml:1349(para)
1485
msgid ""
1486
"The Security tab allows the user to turn on Automatic and Timed login, which "
1487
"user is logged in via an automatic or timed login, and the timed login delay "
1488
"(daemon/AutomaticLoginEnable, daemon/AutomaticLogin, daemon/"
1489
"TimedLoginEnable, daemon/TimedLogin, and daemon/TimedLoginDelay). If "
1490
"automatic login is turned on, then the specified user will immediately log "
1491
"in on reboot without GDM asking for username/password. If the user logs out "
1492
"of their session, GDM will start and ask for username and password to log "
1493
"back in. If TimedLogin is turned on, then GDM will log into the specified "
1494
"user after a specified number of seconds. The user may enable Timed Login "
1495
"for remote (XDMCP) connections by checking the \"Allow remote timed logins\" "
1496
"checkbox."
1497
msgstr ""
1498
1499
#: ../C/gdm.xml:1364(para)
1500
msgid ""
1501
"On this tab, the user may select whether the system administrator user can "
1502
"log in, and whether the system administrator user can log in via remote "
1503
"(XDMCP) connections (security/AllowRoot and security/AllowRemoteRoot). The "
1504
"user may turn on GDM debug (debug/Enable) which causes debug messages to be "
1505
"sent to the system log. Debug should only be used when diagnosing a problem "
1506
"and not be left on when not needed. The \"Deny TCP connections to X server\" "
1507
"choice will disable X forwarding if selected (security/DisallowTCP). A login "
1508
"retry delay (security/RetryDelay) can be set to cause GDM to wait a number "
1509
"of seconds after a failed login."
1510
msgstr ""
1511
1512
#: ../C/gdm.xml:1377(para)
1513
msgid ""
1514
"The \"Configure X Server\" button can be used to specify how GDM manages "
1515
"each display. The \"Servers\" combobox shows what server definitions are "
1516
"available (Standard, Terminal, and Chooser by default). Refer to the \"X "
1517
"Server Definitions\" section of the \"Configuration\" section for more "
1518
"information about how to create new Server Definitions."
1519
msgstr ""
1520
1521
#: ../C/gdm.xml:1386(para)
1522
msgid ""
1523
"For any server type, the user may modify the \"Server Name\" (server/name), "
1524
"the \"Command\" (server/command) to be used to launch the X server, whether "
1525
"the server type will \"Launch\" (server/chooser) the greeter or chooser GUI "
1526
"after starting the X server, whether GDM handles this type (normally only "
1527
"set to false when logging into a Terminal session type), and whether the "
1528
"session type supports \"Flexible\" (server/flexible) sessions."
1529
msgstr ""
1530
1531
#: ../C/gdm.xml:1396(para)
1532
msgid ""
1533
"The \"Servers To Start\" section shows what server type is displayed for "
1534
"each display on the machine. Users may click on the \"Add/Modify\" button to "
1535
"add a new display to the list or to modify a selected display. This simply "
1536
"corresponds each physical display with the Server Definition to be used for "
1537
"managing that display. The \"Remove\" button may be used to remove a display "
1538
"from the list."
1539
msgstr ""
1540
1541
#: ../C/gdm.xml:1408(title)
1542
msgid "Users Tab"
1543
msgstr ""
1544
1545
#: ../C/gdm.xml:1410(para)
1546
msgid ""
1547
"The Users tab controls which users appear in the Face Browser. If the "
1548
"\"Include all users from /etc/password\" checkbox is selected, then all "
1549
"users (with a userid above greeter/MinimalUID and not in the Exclude list) "
1550
"are displayed. If this checkbox is not selected, then users must be added to "
1551
"the \"Include\" list. Users in the \"Exclude\" list are never displayed. The "
1552
"\"Add\" and \"Remove\" buttons are used to add a new user to the list or "
1553
"remove a selected user from the list. The \"Apply User Changes\" button must "
1554
"be pressed after the \"Include\" and \"Exclude\" lists have been modified. "
1555
"The left and right arrow buttons between the \"Include\" and \"Exclude\" "
1556
"lists can be used to move a selected user from one list to the other."
1557
msgstr ""
1558
1559
#: ../C/gdm.xml:1428(title)
1560
msgid "Configuration"
1561
msgstr ""
1562
1563
#: ../C/gdm.xml:1430(para)
1564
msgid ""
1565
"GDM has powerful configuration management. System default configuration is "
1566
"stored in the GDM System Defaults Configuration File and user changes to the "
1567
"default configuration are stored in the GDM Custom Configuration File. This "
1568
"allows sysadmins to store the GDM System Defaults Configuration File on a "
1569
"shared filesystem, so a single file can be used to control configuration for "
1570
"multiple machines. GDM also supports per-display configuration for GUI-"
1571
"related keys."
1572
msgstr ""
1573
1574
#: ../C/gdm.xml:1440(para)
1575
msgid ""
1576
"The <command>gdmsetup</command> is a GUI program you can use to edit the GDM "
1577
"configuration. This program may also be launched directly from the login "
1578
"screen if the greeter/ConfigAvailable key is set to \"true\" Not all keys in "
1579
"the GDM configuration file are supported in the GUI, so you may need to edit "
1580
"the configuration files by hand to edit these keys. If you believe running "
1581
"root-owned GUI's causes security risk, then you would want to always edit "
1582
"the files by hand. This program does not support setting per-display "
1583
"configuration, so per-display configuration files must be set up by hand."
1584
msgstr ""
1585
1586
#: ../C/gdm.xml:1452(para)
1587
msgid ""
1588
"Aside from the GDM System Defaults Configuration File, the other GDM "
1589
"configuration files are located, by default, in the <filename><etc>/"
1590
"gdm/</filename> folder or its subdirectories. Note that the location of many "
1591
"configuration files are defined in the GDM configuration files, so check the "
1592
"GDM System Defaults Configuration File and the GDM Custom Configuration File "
1593
"if the files are not in the locations specified in this document."
1594
msgstr ""
1595
1596
#: ../C/gdm.xml:1462(para)
1597
msgid "Listing of the config directory contents:"
1598
msgstr ""
1599
1600
#: ../C/gdm.xml:1466(screen)
1601
#, no-wrap
1602
msgid ""
1603
"\n"
1604
"custom.conf\n"
1605
"locale.alias\n"
1606
"Xsession\n"
1607
"XKeepsCrashing\n"
1608
"modules/\n"
1609
"Init/\n"
1610
"PostLogin/\n"
1611
"PreSession/\n"
1612
"PostSession/\n"
1613
msgstr ""
1614
1615
#: ../C/gdm.xml:1478(para)
1616
msgid ""
1617
"<filename>locale.alias</filename> is a file which looks much like the system "
1618
"locale alias but, in fact, is not the same. This is a list of all languages "
1619
"that may be on your system. All languages are checked to see if they exist "
1620
"before displaying them in the Language Selection dialog in the login GUI. "
1621
"Only those that exist are displayed."
1622
msgstr ""
1623
1624
#: ../C/gdm.xml:1486(para)
1625
msgid ""
1626
"<filename>Xsession</filename> is a script which sets up a user session and "
1627
"then executes the user's choice of session. Note that the session script is "
1628
"typically started via the <filename>desktop</filename> file associated with "
1629
"the session the user has picked. Some sessions may start the user's session "
1630
"via a different mechanism than the <filename>Xsession</filename> script, so "
1631
"please check the appropriate <filename>desktop</filename> before assuming a "
1632
"session startup issue is being caused by this file."
1633
msgstr ""
1634
1635
#: ../C/gdm.xml:1497(para)
1636
msgid ""
1637
"<filename>XKeepsCrashing</filename> is a script which gets run when the X "
1638
"server keeps crashing and we cannot recover. The shipped default script will "
1639
"work with most Linux distributions and can run the X configuration "
1640
"application provided the person on the console knows the root password."
1641
msgstr ""
1642
1643
#: ../C/gdm.xml:1505(para)
1644
msgid ""
1645
"Accessibility modules are configured in the <filename>modules/</filename> "
1646
"subdirectory, and are a separate topic. Read the default files provided, "
1647
"they have adequate documentation. Again normally the default install is "
1648
"given in the files with <filename>factory</filename> in their name, and "
1649
"those files are not read, they are just there for you so you can always "
1650
"revert to default config."
1651
msgstr ""
1652
1653
#: ../C/gdm.xml:1514(para)
1654
msgid ""
1655
"Files describing available GDM session follow the freedesktop.org desktop "
1656
"file specification. The <filename>.desktop</filename>-style files are "
1657
"installed to <filename><etc>/X11/sessions/</filename>. This directory "
1658
"is also read by the KDE desktop manager (KDM) for common configuration. Next "
1659
"the directory <filename><share>/gdm/BuiltInSessions/</filename> is "
1660
"read for GDM specific built-in sessions (KDM hardcodes these at time of this "
1661
"writing). Lastly the default setup will also read <filename><share>/"
1662
"xsessions/</filename> (which should be <filename><share>/xsessions/</"
1663
"filename> if you really wish to cooperate with KDM) where desktop packages "
1664
"can install their session files. The directories under the <filename><"
1665
"etc></filename> should be reserved for configuration. The desktop file "
1666
"specification approach makes it easy for package management systems to "
1667
"install window managers and different session types without requiring the "
1668
"sysadmin to edit files. See the <filename>SessionDesktopDir</filename> "
1669
"configuration key for changing the paths. It used to be that GDM stored its "
1670
"built in sessions in <filename><etc>/dm/Sessions/</filename> but this "
1671
"is deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the "
1672
"<filename><etc>/dm/Sessions/</filename> was being read."
1673
msgstr ""
1674
1675
#: ../C/gdm.xml:1537(para)
1676
msgid ""
1677
"A session can be disabled (if it was installed in <filename><share>/"
1678
"xsessions/</filename>) by adding an identically named <filename>.desktop</"
1679
"filename> to one of the directories earlier in the path (likely "
1680
"<filename><etc>/X11/sessions</filename>) and using "
1681
"<filename>Hidden=true</filename> in that file."
1682
msgstr ""
1683
1684
#: ../C/gdm.xml:1545(para)
1685
msgid ""
1686
"GDM uses the optional key <filename>X-Gdm-XserverArgs</filename> in session "
1687
"files to specify additional arguments to be passed to the X server. For "
1688
"example, the entry <filename>X-Gdm-XserverArgs=-depth 16</filename> will "
1689
"start the X server with a color depth of 16 bits. Any such additional "
1690
"arguments are ignored when using a Nested display (when GDM is launched in a "
1691
"window)."
1692
msgstr ""
1693
1694
#: ../C/gdm.xml:1556(title)
1695
msgid "The Script Directories"
1696
msgstr ""
1697
1698
#: ../C/gdm.xml:1558(para)
1699
msgid ""
1700
"In this section we will explain the <filename>Init</filename>, "
1701
"<filename>PostLogin</filename>, <filename>PreSession</filename> and "
1702
"<filename>PostSession</filename> directories as they are very similar."
1703
msgstr ""
1704
1705
#: ../C/gdm.xml:1564(para)
1706
msgid ""
1707
"When the X server has been successfully started, GDM will try to run the "
1708
"script called <filename>Init/<displayname></filename>. I.e. "
1709
"<filename>Init/:0</filename> for the first local display. If this file is "
1710
"not found, GDM will attempt to to run <filename>Init/<hostname></"
1711
"filename>. I.e. <filename>Init/somehost</filename>. If this still is not "
1712
"found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins or "
1713
"<filename>Init/Flexi</filename> for all on demand flexible displays. If none "
1714
"of the above were found, GDM will run <filename>Init/Default</filename>. The "
1715
"script will be run as root and GDM blocks until it terminates. Use the "
1716
"<filename>Init/*</filename> script for applications that are supposed to run "
1717
"alongside with the GDM login window. xconsole for instance. Commands to set "
1718
"the background etc. go in this file too."
1719
msgstr ""
1720
1721
#: ../C/gdm.xml:1582(para)
1722
msgid ""
1723
"It is up to the sysadmin to decide whether clients started by the Init "
1724
"script should be killed before starting the user session. This is controlled "
1725
"with the <filename>KillInitClients</filename> configuration option."
1726
msgstr ""
1727
1728
#: ../C/gdm.xml:1589(para)
1729
msgid ""
1730
"When the user has been successfully authenticated GDM tries the scripts in "
1731
"the <filename>PostLogin</filename> directory in the same manner as for the "
1732
"<filename>Init</filename> directory. This is done before any session setup "
1733
"is done, and so this would be the script where you might setup the home "
1734
"directory if you need to (though you should use the <filename>pam_mount</"
1735
"filename> module if you can for this). You have the <filename>$USER</"
1736
"filename> and <filename>$DISPLAY</filename> environment variables set for "
1737
"this script, and again it is run as root. The script should return 0 on "
1738
"success as otherwise the user won't be logged in. This is not true for "
1739
"failsafe session however."
1740
msgstr ""
1741
1742
#: ../C/gdm.xml:1603(para)
1743
msgid ""
1744
"After the user session has been setup from the GDM side of things, GDM will "
1745
"run the scripts in the <filename>PreSession</filename> directory, again in "
1746
"the same manner as the <filename>Init</filename> directory. Use this script "
1747
"for local session management or accounting stuff. The <filename>$USER</"
1748
"filename> environment variable contains the login of the authenticated user "
1749
"and <filename>$DISPLAY</filename> is set to the current display. The script "
1750
"should return 0 on success. Any other value will cause GDM to terminate the "
1751
"current login process. This is not true for failsafe sessions however. Also "
1752
"<filename>$X_SERVERS</filename> environmental variable is set and this "
1753
"points to a fake generated X servers file for use with the sessreg "
1754
"accounting application."
1755
msgstr ""
1756
1757
#: ../C/gdm.xml:1618(para)
1758
msgid ""
1759
"After this the base <filename>Xsession</filename> script is run with the "
1760
"selected session executable as the first argument. This is run as the user, "
1761
"and really this is the user session. The available session executables are "
1762
"taken from the <filename>Exec=</filename> line in the <filename>.desktop</"
1763
"filename> files in the path specified by <filename>SessionDesktopDir</"
1764
"filename>. Usually this path is <filename><etc>/X11/sessions/:<"
1765
"etc>/dm/Sessions:/usr/share/xsessions/</filename>. The first found file "
1766
"is used. The user either picks from these sessions or GDM will look inside "
1767
"the file <filename>~/.dmrc</filename> for the stored preference."
1768
msgstr ""
1769
1770
#: ../C/gdm.xml:1631(para)
1771
msgid ""
1772
"This script should really load the user's profile and generally do all the "
1773
"voodoo that is needed to launch a session. Since many systems reset the "
1774
"language selections done by GDM, GDM will also set the <filename>$GDM_LANG</"
1775
"filename> variable to the selected language. You can use this to reset the "
1776
"language environmental variables after you run the user's profile. If the "
1777
"user elected to use the system language, then <filename>$GDM_LANG</filename> "
1778
"is not set."
1779
msgstr ""
1780
1781
#: ../C/gdm.xml:1641(para)
1782
msgid ""
1783
"When the user terminates his session, the <filename>PostSession</filename> "
1784
"script will be run. Again operation is similar to <filename>Init</filename>, "
1785
"<filename>PostLogin</filename> and <filename>PreSession</filename>. Again "
1786
"the script will be run with root privileges, the slave daemon will block and "
1787
"the <filename>$USER</filename> environment variable will contain the name of "
1788
"the user who just logged out and <filename>$DISPLAY</filename> will be set "
1789
"to the display the user used, however note that the X server for this "
1790
"display may already be dead and so you shouldn't try to access it. Also "
1791
"<filename>$X_SERVERS</filename> environmental variable is set and this "
1792
"points to a fake generated X servers file for use with the sessreg "
1793
"accounting application."
1794
msgstr ""
1795
1796
#: ../C/gdm.xml:1656(para)
1797
msgid ""
1798
"Note that the <filename>PostSession</filename> script will be run even when "
1799
"the display fails to respond due to an I/O error or similar. Thus, there is "
1800
"no guarantee that X applications will work during script execution."
1801
msgstr ""
1802
1803
#: ../C/gdm.xml:1663(para)
1804
msgid ""
1805
"Except for the <filename>Xsession</filename> script all of these scripts "
1806
"will also have the environment variable <filename>$RUNNING_UNDER_GDM</"
1807
"filename> set to <filename>yes</filename>, so that you could perhaps use "
1808
"similar scripts for different display managers. The <filename>Xsession</"
1809
"filename> will always have the <filename>$GDMSESSION</filename> set to the "
1810
"basename of the session that the user chose to run without the <filename>."
1811
"desktop</filename> extension. In addition <filename>$DESKTOP_SESSION</"
1812
"filename> is also set to the same value and in fact this will also be set by "
1813
"KDM in future versions."
1814
msgstr ""
1815
1816
#: ../C/gdm.xml:1677(para)
1817
msgid ""
1818
"Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, "
1819
"<filename>PreSession</filename> or <filename>PostSession</filename> scripts "
1820
"are necessary and can be left out. The <filename>Xsession</filename> script "
1821
"is however required as well as at least one session <filename>.desktop</"
1822
"filename> file."
1823
msgstr ""
1824
1825
#: ../C/gdm.xml:1687(title)
1826
msgid ""
1827
"The Configuration Files - GDM System Defaults Configuration File and GDM "
1828
"Custom Configuraiton File"
1829
msgstr ""
1830
1831
#: ../C/gdm.xml:1690(para)
1832
msgid ""
1833
"GDM uses two configuration files: the GDM System Defaults Configuration File "
1834
"(<filename><share>/gdm/defaults.conf</filename>) and the GDM Custom "
1835
"Configuration File (<filename><etc>/gdm/custom.conf</filename>). The "
1836
"GDM System Defaults File contains the default configuration choices for GDM, "
1837
"and should not be modified by the user. The GDM Custom Configuration File is "
1838
"where users may specify their custom configuration choices. If a "
1839
"configuration option is not defined in either file, GDM will default to the "
1840
"value described in the comments in the GDM System Defaults Configuration "
1841
"File."
1842
msgstr ""
1843
1844
#: ../C/gdm.xml:1703(para)
1845
msgid ""
1846
"Both configuration files are divided into sections each containing variables "
1847
"that define the behavior for a specific part of the GDM suite. Refer to the "
1848
"comments in the GDM System Defaults Configuration File for additional "
1849
"information about each configuration setting."
1850
msgstr ""
1851
1852
#: ../C/gdm.xml:1710(para)
1853
msgid ""
1854
"GDM also supports per-display configuration for parameters in the \"gui\", "
1855
"\"greeter\" sections of the configuration file Also the security/PamStack "
1856
"key may be customized per-display. Per-display configuration is specified by "
1857
"creating a file named <filename><etc>/gdm/custom.conf<display "
1858
"num></filename>. In this file the section and keys to use on this display "
1859
"can be specified. For example, configuration overrides for display \":103\" "
1860
"would be stored in the file <filename><etc>/gdm/custom.conf:0</"
1861
"filename>. Per-display configuration is supported in GDM 2.14.6 and later."
1862
msgstr ""
1863
1864
#: ../C/gdm.xml:1723(para)
1865
msgid ""
1866
"To change configuration by hand, edit the GDM Custom Configuration File or "
1867
"per-display configuration file and make sure the keyname=value pair you want "
1868
"is included in the appropriate section. For example, to change the value for "
1869
"the \"Greeter\" key in the \"daemon\" section, make sure the daemon section "
1870
"of the GDM Custom Configuration File or per-display configuration file "
1871
"includes the \"[daemon]\" section followed by the key and value change "
1872
"desired. As in this example:"
1873
msgstr ""
1874
1875
#: ../C/gdm.xml:1734(screen)
1876
#, no-wrap
1877
msgid ""
1878
"\n"
1879
"[daemon]\n"
1880
"Greeter=/usr/lib/gdmgreeter\n"
1881
msgstr ""
1882
1883
#: ../C/gdm.xml:1739(para)
1884
msgid ""
1885
"The <command>gdmsetup</command> command can be used to modify the GDM Custom "
1886
"Configuration File. Note the <command>gdmsetup</command> is intended to be "
1887
"run as root, so users who feel it is insecure to run GUI programs as root "
1888
"should edit the configuration files by hand."
1889
msgstr ""
1890
1891
#: ../C/gdm.xml:1746(para)
1892
msgid ""
1893
"The GDM daemon <command>--config</command> argument may instead be used to "
1894
"specify a different configuration file location. The GDM daemon must be "
1895
"restarted to change the configuration file being used. Also when building "
1896
"GDM, the location of the configuration files may be specified via the "
1897
"<command>--with-defaults-conf</command> and <command>--with-custom-conf</"
1898
"command> configuration options."
1899
msgstr ""
1900
1901
#: ../C/gdm.xml:1755(para)
1902
msgid ""
1903
"Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</"
1904
"filename> existed. For best backwards compatibility, this file will be used "
1905
"instead of the GDM Custom Configuration File if it exists on your system. If "
1906
"upgrading to the new version of GDM, \"make install\" will check to see if "
1907
"the <filename><etc>/gdm/gdm.conf</filename> file is different than the "
1908
"<filename><etc>/gdm/factory-gdm.conf</filename> file. If so, the "
1909
"<filename><etc>/gdm/gdm.conf</filename> file will be automatically "
1910
"copied to <filename><etc>/gdm/custom.conf</filename> to preserve any "
1911
"configuration changes."
1912
msgstr ""
1913
1914
#: ../C/gdm.xml:1769(para)
1915
msgid ""
1916
"Distributions should edit the GDM System Defaults Configuration File to "
1917
"establish default configuration values, so that they are preserved as "
1918
"defaults and not modified by users modifying the GDM Custom Configuration "
1919
"File. Note that distributions may modify the GDM System Defaults "
1920
"Configuration File on update to improve usability, security, etc. So any "
1921
"changes made to this file may be lost."
1922
msgstr ""
1923
1924
#: ../C/gdm.xml:1778(para)
1925
msgid ""
1926
"The GDM System Defaults Configuration File and the GDM Custom Configuration "
1927
"File follow the standard <filename>.ini</filename> style configuration file "
1928
"syntax. Keywords in brackets define sections, strings before an equal sign "
1929
"(=) are variables and the data after equal sign represents their value. "
1930
"Empty lines or lines starting with the hash mark (#) are ignored. The "
1931
"graphical configurator will try to preserve both comments (lines with a hash "
1932
"mark) and the overall structure of the file so you can intermix using the "
1933
"GUI or hand editing the configuration file."
1934
msgstr ""
1935
1936
#: ../C/gdm.xml:1790(para)
1937
msgid "The following configuration keys are supported in GDM:"
1938
msgstr ""
1939
1940
#: ../C/gdm.xml:1795(title)
1941
msgid "Daemon Configuration"
1942
msgstr ""
1943
1944
#: ../C/gdm.xml:1798(title)
1945
msgid "[daemon]"
1946
msgstr ""
1947
1948
#: ../C/gdm.xml:1801(term)
1949
msgid "AddGtkModules"
1950
msgstr ""
1951
1952
#: ../C/gdm.xml:1803(synopsis)
1953
#, no-wrap
1954
msgid "AddGtkModules=false"
1955
msgstr ""
1956
1957
#: ../C/gdm.xml:1804(para)
1958
msgid ""
1959
"If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</"
1960
"command> to be launched with additional Gtk+ modules. This is useful when "
1961
"extra features are required such as accessible login. Note that only "
1962
"\"trusted\" modules should be used to minimize security issues."
1963
msgstr ""
1964
1965
#: ../C/gdm.xml:1811(para)
1966
msgid ""
1967
"If true, then the registry daemon <command>at-spi-registryd</command> will "
1968
"be launched by <command>gdmgreeter</command> or <command>gdmlogin</command> "
1969
"starting with version GDM 2.17."
1970
msgstr ""
1971
1972
#: ../C/gdm.xml:1817(para)
1973
msgid ""
1974
"Usually this is used for accessibility modules. The modules which are loaded "
1975
"are specified with the <filename>GtkModulesList</filename> key."
1976
msgstr ""
1977
1978
#: ../C/gdm.xml:1826(term)
1979
msgid "AllowLogoutActions"
1980
msgstr ""
1981
1982
#: ../C/gdm.xml:1828(synopsis)
1983
#, no-wrap
1984
msgid "AllowLogoutActions=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD"
1985
msgstr ""
1986
1987
#: ../C/gdm.xml:1829(para)
1988
msgid ""
1989
"Specify which actions are supported by the QUERY_LOGOUT_ACTION, "
1990
"SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</"
1991
"command> commands. Valid values are HALT, REBOOT, SHUTDOWN, SUSPEND, and "
1992
"CUSTOM_CMD and these should be separated by semicolons. This allows certain "
1993
"options to be disabled if desired. Refer to the related "
1994
"<filename>SystemCommandsInMenu</filename> and "
1995
"<filename>RBACSystemCommandKeys</filename> configuration options."
1996
msgstr ""
1997
1998
#: ../C/gdm.xml:1844(term)
1999
msgid "AlwaysLoginCurrentSession"
2000
msgstr ""
2001
2002
#: ../C/gdm.xml:1846(synopsis)
2003
#, no-wrap
2004
msgid "AlwaysLoginCurrentSession=true"
2005
msgstr ""
2006
2007
#: ../C/gdm.xml:1847(para)
2008
msgid ""
2009
"If true, then when the user logs in and already has an existing session, "
2010
"then they are connected to that session rather than starting a new session. "
2011
"This only works for sessions running on VTs (Virtual Terminals) started with "
2012
"gdmflexiserver, and not with XDMCP. Note that VTs are not supported on all "
2013
"operating systems."
2014
msgstr ""
2015
2016
#: ../C/gdm.xml:1859(term)
2017
msgid "AutomaticLoginEnable"
2018
msgstr ""
2019
2020
#: ../C/gdm.xml:1861(synopsis)
2021
#, no-wrap
2022
msgid "AutomaticLoginEnable=false"
2023
msgstr ""
2024
2025
#: ../C/gdm.xml:1862(para)
2026
msgid ""
2027
"If the user given in AutomaticLogin should be logged in upon first bootup. "
2028
"No password will be asked. This is useful for single user workstations where "
2029
"local console security is not an issue. Also could be useful for public "
2030
"terminals, although there see <filename>TimedLogin</filename>."
2031
msgstr ""
2032
2033
#: ../C/gdm.xml:1873(term)
2034
msgid "AutomaticLogin"
2035
msgstr ""
2036
2037
#: ../C/gdm.xml:1875(synopsis)
2038
#, no-wrap
2039
msgid "AutomaticLogin="
2040
msgstr ""
2041
2042
#: ../C/gdm.xml:1876(para)
2043
msgid ""
2044
"This user should be automatically logged in on first bootup. "
2045
"AutomaticLoginEnable must be true and this must be a valid user for this to "
2046
"happen. \"root\" can never be autologged in however and gdm will just refuse "
2047
"to do it even if you set it up."
2048
msgstr ""
2049
2050
#: ../C/gdm.xml:1884(para)
2051
msgid "The following control chars are recognized within the specified name:"
2052
msgstr ""
2053
2054
#: ../C/gdm.xml:1889(para) ../C/gdm.xml:3957(para)
2055
msgid "%% — the `%' character"
2056
msgstr ""
2057
2058
#: ../C/gdm.xml:1893(para)
2059
msgid "%d — display's name"
2060
msgstr ""
2061
2062
#: ../C/gdm.xml:1897(para)
2063
msgid "%h — display's hostname"
2064
msgstr ""
2065
2066
#: ../C/gdm.xml:1901(para)
2067
msgid ""
2068
"Alternatively, the name may end with a vertical bar |, the pipe symbol. The "
2069
"name is then used as a application to execute which returns the desired "
2070
"username on standard output. If an empty or otherwise invalid username is "
2071
"returned, automatic login is not performed. This feature is typically used "
2072
"when several remote displays are used as internet kiosks, with a specific "
2073
"user to automatically login for each display."
2074
msgstr ""
2075
2076
#: ../C/gdm.xml:1914(term)
2077
msgid "BaseXsession"
2078
msgstr ""
2079
2080
#: ../C/gdm.xml:1916(synopsis)
2081
#, no-wrap
2082
msgid "BaseXsession=<etc>/gdm/Xsession"
2083
msgstr ""
2084
2085
#: ../C/gdm.xml:1917(para)
2086
msgid ""
2087
"This is the base X session file. When a user logs in, this script will be "
2088
"run with the selected session as the first argument. The selected session "
2089
"will be the <filename>Exec=</filename> from the <filename>.desktop</"
2090
"filename> file of the session."
2091
msgstr ""
2092
2093
#: ../C/gdm.xml:1925(para)
2094
msgid ""
2095
"If you wish to use the same script for several different display managers, "
2096
"and wish to have some of the script run only for GDM, then you can check the "
2097
"presence of the <filename>GDMSESSION</filename> environmental variable. This "
2098
"will always be set to the basename of <filename>.desktop</filename> (without "
2099
"the extension) file that is being used for this session, and will only be "
2100
"set for GDM sessions. Previously some scripts were checking for "
2101
"<filename>GDM_LANG</filename>, but that is only set when the user picks a "
2102
"non-system default language."
2103
msgstr ""
2104
2105
#: ../C/gdm.xml:1938(para)
2106
msgid ""
2107
"This script should take care of doing the \"login\" for the user and so it "
2108
"should source the <filename><etc>/profile</filename> and friends. The "
2109
"standard script shipped with GDM sources the files in this order: "
2110
"<filename><etc>/profile</filename> then <filename>~/.profile</"
2111
"filename> then <filename><etc>/xprofile</filename> and finally "
2112
"<filename>~/.xprofile</filename>. Note that different distributions may "
2113
"change this however. Sometimes users personal setup will be in <filename>~/."
2114
"bash_profile</filename>, however broken that is."
2115
msgstr ""
2116
2117
#: ../C/gdm.xml:1955(term)
2118
msgid "Chooser"
2119
msgstr ""
2120
2121
#: ../C/gdm.xml:1957(synopsis)
2122
#, no-wrap
2123
msgid "Chooser=<bin>/gdmchooser"
2124
msgstr ""
2125
2126
#: ../C/gdm.xml:1958(para)
2127
msgid "Full path and name of the chooser executable followed by optional arguments."
2128
msgstr ""
2129
2130
#: ../C/gdm.xml:1966(term)
2131
msgid "Configurator"
2132
msgstr ""
2133
2134
#: ../C/gdm.xml:1968(synopsis)
2135
#, no-wrap
2136
msgid "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog"
2137
msgstr ""
2138
2139
#: ../C/gdm.xml:1969(para)
2140
msgid ""
2141
"The pathname to the configurator binary. If the greeter "
2142
"<filename>ConfigAvailable</filename> option is set to true then run this "
2143
"binary when somebody chooses Configuration from the Actions menu. Of course "
2144
"GDM will first ask for root password however. And it will never allow this "
2145
"to happen from a remote display."
2146
msgstr ""
2147
2148
#: ../C/gdm.xml:1981(term)
2149
msgid "ConsoleCannotHandle"
2150
msgstr ""
2151
2152
#: ../C/gdm.xml:1983(synopsis)
2153
#, no-wrap
2154
msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh"
2155
msgstr ""
2156
2157
#: ../C/gdm.xml:1984(para)
2158
msgid ""
2159
"These are the languages that the console cannot handle because of font "
2160
"issues. Here we mean the text console, not X. This is only used when there "
2161
"are errors to report and we cannot start X."
2162
msgstr ""
2163
2164
#: ../C/gdm.xml:1994(term)
2165
msgid "ConsoleNotify"
2166
msgstr ""
2167
2168
#: ../C/gdm.xml:1996(synopsis)
2169
#, no-wrap
2170
msgid "ConsoleNotify=true"
2171
msgstr ""
2172
2173
#: ../C/gdm.xml:1997(para)
2174
msgid ""
2175
"If false, gdm will not display a message dialog on the console when an error "
2176
"happens."
2177
msgstr ""
2178
2179
#: ../C/gdm.xml:2005(term)
2180
msgid "DefaultPath"
2181
msgstr ""
2182
2183
#: ../C/gdm.xml:2007(synopsis)
2184
#, no-wrap
2185
msgid "DefaultPath=defaultpath (value set by configure)"
2186
msgstr ""
2187
2188
#: ../C/gdm.xml:2008(para)
2189
msgid ""
2190
"Specifies the path which will be set in the user's session. This value will "
2191
"be overridden with the value from <filename>/etc/default/login</filename> if "
2192
"it contains \"ROOT=<pathname>\". If the <filename>/etc/default/login</"
2193
"filename> file exists, but contains no value for ROOT, the value as defined "
2194
"in the GDM configuration will be be used."
2195
msgstr ""
2196
2197
#: ../C/gdm.xml:2021(term)
2198
msgid "DefaultSession"
2199
msgstr ""
2200
2201
#: ../C/gdm.xml:2023(synopsis)
2202
#, no-wrap
2203
msgid "DefaultSession=gnome.desktop"
2204
msgstr ""
2205
2206
#: ../C/gdm.xml:2024(para)
2207
msgid ""
2208
"The session that is used by default if the user does not have a saved "
2209
"preference and has picked 'Last' from the list of sessions. Note that 'Last' "
2210
"need not be displayed, see the <filename>ShowLastSession</filename> key."
2211
msgstr ""
2212
2213
#: ../C/gdm.xml:2035(term)
2214
msgid "DisplayInitDir"
2215
msgstr ""
2216
2217
#: ../C/gdm.xml:2037(synopsis)
2218
#, no-wrap
2219
msgid "DisplayInitDir=<etc>/gdm/Init"
2220
msgstr ""
2221
2222
#: ../C/gdm.xml:2038(para)
2223
msgid ""
2224
"Directory containing the display init scripts. See the ``The Script "
2225
"Directories'' section for more info."
2226
msgstr ""
2227
2228
#: ../C/gdm.xml:2046(term)
2229
msgid "DisplayLastLogin"
2230
msgstr ""
2231
2232
#: ../C/gdm.xml:2048(synopsis)
2233
#, no-wrap
2234
msgid "DisplayLastLogin=true"
2235
msgstr ""
2236
2237
#: ../C/gdm.xml:2049(para)
2238
msgid ""
2239
"If true then the last login information is printed to the user before being "
2240
"prompted for password. While this gives away some info on what users are on "
2241
"a system, it on the other hand should give the user an idea of when they "
2242
"logged in and if it doesn't seem kosher to them, they can just abort the "
2243
"login and contact the sysadmin (avoids running malicious startup scripts). "
2244
"This was added in version 2.5.90.0."
2245
msgstr ""
2246
2247
#: ../C/gdm.xml:2058(para)
2248
msgid ""
2249
"This is for making GDM conformant to CSC-STD-002-85, although that is purely "
2250
"theoretical now. Someone should read that spec and ensure that this actually "
2251
"conforms (in addition to other places in GDM). See <filename>http://www."
2252
"radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85.html</filename> for more "
2253
"info."
2254
msgstr ""
2255
2256
#: ../C/gdm.xml:2070(term)
2257
msgid "DoubleLoginWarning"
2258
msgstr ""
2259
2260
#: ../C/gdm.xml:2072(synopsis)
2261
#, no-wrap
2262
msgid "DoubleLoginWarning=true"
2263
msgstr ""
2264
2265
#: ../C/gdm.xml:2073(para)
2266
msgid ""
2267
"If true, GDM will warn the user if they are already logged in on another "
2268
"virtual terminal. On systems where GDM supports checking the X virtual "
2269
"terminals, GDM will let the user switch to the previous login virtual "
2270
"terminal instead of logging in."
2271
msgstr ""
2272
2273
#: ../C/gdm.xml:2083(term)
2274
msgid "DynamicXServers"
2275
msgstr ""
2276
2277
#: ../C/gdm.xml:2085(synopsis)
2278
#, no-wrap
2279
msgid "DynamicXServers=false"
2280
msgstr ""
2281
2282
#: ../C/gdm.xml:2086(para)
2283
msgid ""
2284
"If true, the GDM daemon will honor requests to manage displays via the "
2285
"<filename>/tmp/.gdm_socket</filename> socket connection. Displays can be "
2286
"created, started, and deleted with the appropriate commands. The "
2287
"<filename>gdmdynamic</filename> command is a convenient method to send these "
2288
"messages."
2289
msgstr ""
2290
2291
#: ../C/gdm.xml:2098(term)
2292
msgid "FailsafeXServer"
2293
msgstr ""
2294
2295
#: ../C/gdm.xml:2100(synopsis)
2296
#, no-wrap
2297
msgid "FailsafeXServer="
2298
msgstr ""
2299
2300
#: ../C/gdm.xml:2101(para)
2301
msgid ""
2302
"An X command line in case we can't start the normal X server. should "
2303
"probably be some sort of a script that runs an appropriate low resolution X "
2304
"server that will just work. This is tried before the "
2305
"<filename>XKeepsCrashing</filename> script is run."
2306
msgstr ""
2307
2308
#: ../C/gdm.xml:2112(term)
2309
msgid "FirstVT"
2310
msgstr ""
2311
2312
#: ../C/gdm.xml:2114(synopsis)
2313
#, no-wrap
2314
msgid "FirstVT=7"
2315
msgstr ""
2316
2317
#: ../C/gdm.xml:2115(para)
2318
msgid ""
2319
"On systems where GDM supports automatic VT (virtual terminal) allocation, "
2320
"this is the first vt to try. Usually standard text logins are run on the "
2321
"lower vts. See also <filename>VTAllocation</filename>."
2322
msgstr ""
2323
2324
#: ../C/gdm.xml:2125(term)
2325
msgid "FlexibleXServers"
2326
msgstr ""
2327
2328
#: ../C/gdm.xml:2127(synopsis)
2329
#, no-wrap
2330
msgid "FlexibleXServers=5"
2331
msgstr ""
2332
2333
#: ../C/gdm.xml:2128(para)
2334
msgid ""
2335
"The maximum number of allowed flexible displays. These are displays that can "
2336
"be run using the <filename>/tmp/.gdm_socket</filename> socket connection. "
2337
"This is used for both full flexible displays and for nested displays (refer "
2338
"to the <filename>Xnest</filename> configuration option)."
2339
msgstr ""
2340
2341
#: ../C/gdm.xml:2140(term)
2342
msgid "FlexiReapDelayMinutes"
2343
msgstr ""
2344
2345
#: ../C/gdm.xml:2142(synopsis)
2346
#, no-wrap
2347
msgid "FlexiReapDelayMinutes=5"
2348
msgstr ""
2349
2350
#: ../C/gdm.xml:2143(para)
2351
msgid ""
2352
"After how many minutes of inactivity at the login screen should a flexi "
2353
"display be reaped. This is only in effect before a user logs in. Also it "
2354
"does not affect nested displays (refer to the <filename>Xnest</filename> "
2355
"configuration option). To turn off this behavior set this value to 0. This "
2356
"was added in version 2.5.90.0."
2357
msgstr ""
2358
2359
#: ../C/gdm.xml:2155(term)
2360
msgid "Greeter"
2361
msgstr ""
2362
2363
#: ../C/gdm.xml:2157(synopsis)
2364
#, no-wrap
2365
msgid "Greeter=<bin>/gdmlogin"
2366
msgstr ""
2367
2368
#: ../C/gdm.xml:2158(para)
2369
msgid ""
2370
"Full path and name of the greeter executable followed by optional arguments. "
2371
"This is the greeter used for all displays except for the XDMCP remote "
2372
"displays. See also <filename>RemoteGreeter</filename>"
2373
msgstr ""
2374
2375
#: ../C/gdm.xml:2168(term)
2376
msgid "Group"
2377
msgstr ""
2378
2379
#: ../C/gdm.xml:2170(synopsis)
2380
#, no-wrap
2381
msgid "Group=gdm"
2382
msgstr ""
2383
2384
#: ../C/gdm.xml:2171(para)
2385
msgid ""
2386
"The group name under which <command>gdmlogin</command>, <command>gdmgreeter</"
2387
"command>, <command>gdmchooser</command> and the internal failsafe GTK+ "
2388
"dialogs are run. Also see <filename>User</filename>. This user will have "
2389
"access to all the X authorization files, and perhaps to other internal GDM "
2390
"data and it should not therefore be a user such as nobody, but rather a "
2391
"dedicated user. The <filename>ServAuthDir</filename> is owned by this group. "
2392
"The ownership and permissions of <filename>ServAuthDir</filename> should be "
2393
"<filename>root.gdm</filename> and 1770."
2394
msgstr ""
2395
2396
#: ../C/gdm.xml:2188(term)
2397
msgid "GtkModulesList"
2398
msgstr ""
2399
2400
#: ../C/gdm.xml:2190(synopsis)
2401
#, no-wrap
2402
msgid "GtkModulesList=module-1:module-2:..."
2403
msgstr ""
2404
2405
#: ../C/gdm.xml:2191(para)
2406
msgid ""
2407
"A colon separated list of Gtk+ modules that <command>gdmgreeter</command> or "
2408
"<command>gdmlogin</command> will be invoked with if <filename>AddGtkModules</"
2409
"filename> is true. The format is the same as the standard Gtk+ module "
2410
"interface."
2411
msgstr ""
2412
2413
#: ../C/gdm.xml:2202(term)
2414
msgid "HaltCommand"
2415
msgstr ""
2416
2417
#: ../C/gdm.xml:2204(synopsis)
2418
#, no-wrap
2419
msgid "HaltCommand=<sbin>/shutdown -h now"
2420
msgstr ""
2421
2422
#: ../C/gdm.xml:2205(para)
2423
msgid ""
2424
"Full path and arguments to command to be executed when user selects \"Shut "
2425
"Down\" from the Actions menu. This can be a ';' separated list of commands "
2426
"to try. If a value is missing, the shut down command is not available. Note "
2427
"that the default for this value is not empty, so to disable \"Shut Down\" it "
2428
"must be set to an empty value."
2429
msgstr ""
2430
2431
#: ../C/gdm.xml:2218(term)
2432
msgid "KillInitClients"
2433
msgstr ""
2434
2435
#: ../C/gdm.xml:2220(synopsis)
2436
#, no-wrap
2437
msgid "KillInitClients=true"
2438
msgstr ""
2439
2440
#: ../C/gdm.xml:2221(para)
2441
msgid ""
2442
"Determines whether GDM should kill X clients started by the init scripts "
2443
"when the user logs in."
2444
msgstr ""
2445
2446
#: ../C/gdm.xml:2229(term)
2447
msgid "LogDir"
2448
msgstr ""
2449
2450
#: ../C/gdm.xml:2231(synopsis)
2451
#, no-wrap
2452
msgid "LogDir=<var>/log/gdm"
2453
msgstr ""
2454
2455
#: ../C/gdm.xml:2232(para)
2456
msgid ""
2457
"Directory containing the log files for the individual displays. By default "
2458
"this is the same as the ServAuthDir."
2459
msgstr ""
2460
2461
#: ../C/gdm.xml:2240(term)
2462
msgid "PreFetchProgram"
2463
msgstr ""
2464
2465
#: ../C/gdm.xml:2242(synopsis)
2466
#, no-wrap
2467
msgid "PreFetchProgram=command"
2468
msgstr ""
2469
2470
#: ../C/gdm.xml:2243(para)
2471
msgid ""
2472
"Program to be run by the GDM greeter/login program when the initial screen "
2473
"is displayed. The purpose is to provide a hook where files which will be "
2474
"used after login can be preloaded to speed performance for the user. The "
2475
"program will be called once only, the first time a greeter is displayed. The "
2476
"gdmprefetch command may be used. This utility will load any libraries passed "
2477
"in on the command line, or if the argument starts with a \"@\" character, it "
2478
"will process the file assuming it is an ASCII file containing a list of "
2479
"libraries, one per line, and load each library in the file."
2480
msgstr ""
2481
2482
#: ../C/gdm.xml:2259(term)
2483
msgid "PostLoginScriptDir"
2484
msgstr ""
2485
2486
#: ../C/gdm.xml:2261(synopsis)
2487
#, no-wrap
2488
msgid "PostLoginScriptDir=<etc>/gdm/PostLogin"
2489
msgstr ""
2490
2491
#: ../C/gdm.xml:2262(para)
2492
msgid ""
2493
"Directory containing the scripts run right after the user logs in, but "
2494
"before any session setup is done. See the ``The Script Directories'' section "
2495
"for more info."
2496
msgstr ""
2497
2498
#: ../C/gdm.xml:2271(term)
2499
msgid "PostSessionScriptDir"
2500
msgstr ""
2501
2502
#: ../C/gdm.xml:2273(synopsis)
2503
#, no-wrap
2504
msgid "PostSessionScriptDir=<etc>/gdm/PostSession"
2505
msgstr ""
2506
2507
#: ../C/gdm.xml:2274(para)
2508
msgid ""
2509
"Directory containing the scripts run after the user logs out. See the ``The "
2510
"Script Directories'' section for more info."
2511
msgstr ""
2512
2513
#: ../C/gdm.xml:2282(term)
2514
msgid "PreSessionScriptDir"
2515
msgstr ""
2516
2517
#: ../C/gdm.xml:2284(synopsis)
2518
#, no-wrap
2519
msgid "PreSessionScriptDir=<etc>/gdm/PreSession"
2520
msgstr ""
2521
2522
#: ../C/gdm.xml:2285(para)
2523
msgid ""
2524
"Directory containing the scripts run before the user logs in. See the ``The "
2525
"Script Directories'' section for more info."
2526
msgstr ""
2527
2528
#: ../C/gdm.xml:2293(term) ../C/gdm.xml:2295(synopsis)
2529
msgid "RBACSystemCommandKeys"
2530
msgstr ""
2531
2532
#: ../C/gdm.xml:2296(para)
2533
msgid ""
2534
"Support RBAC (Role Based Access Control) for system commands (Shutdown, "
2535
"Reboot, Suspend, etc.). This feature is only functional if GDM is compiled "
2536
"with RBAC support. Specify the RBAC key used to determine if the user has "
2537
"permission to use the action via the QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, "
2538
"and SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</command> commands. Valid "
2539
"actions are HALT, REBOOT, SUSPEND, and CUSTOM_CMD. The greeter will only "
2540
"display the command if the gdm user (<filename>User</filename> configuration "
2541
"key) has RBAC permissions to use the action. RBAC keys for multiple actions "
2542
"can be specified by separating them with semicolons. The format for each is "
2543
"\"Action:RBAC key\". If an action is not specified, it is assumed that all "
2544
"users have permission to use this action. For example, a valid value for "
2545
"this configuration option would be \"HALT:key.for.halt;REBOOT:key.for.reboot"
2546
"\". Refer to the related <filename>AllowLogoutActions</filename> and "
2547
"<filename>SystemCommandsInMenu</filename> configuration options."
2548
msgstr ""
2549
2550
#: ../C/gdm.xml:2320(term)
2551
msgid "RebootCommand"
2552
msgstr ""
2553
2554
#: ../C/gdm.xml:2322(synopsis)
2555
#, no-wrap
2556
msgid "RebootCommand=<sbin>/shutdown -r now"
2557
msgstr ""
2558
2559
#: ../C/gdm.xml:2323(para)
2560
msgid ""
2561
"Full path and optional arguments to the command to be executed when user "
2562
"selects Restart from the Actions menu. This can be a ';' separated list of "
2563
"commands to try. If missing, the restart command is not available. Note that "
2564
"the default for this value is not empty so to disable restart you must set "
2565
"this explicitly to an empty value."
2566
msgstr ""
2567
2568
#: ../C/gdm.xml:2335(term)
2569
msgid "RemoteGreeter"
2570
msgstr ""
2571
2572
#: ../C/gdm.xml:2337(synopsis)
2573
#, no-wrap
2574
msgid "RemoteGreeter=<bin>/gdmlogin"
2575
msgstr ""
2576
2577
#: ../C/gdm.xml:2338(para)
2578
msgid ""
2579
"Full path and name of the greeter executable followed by optional arguments. "
2580
"This is used for all remote XDMCP sessions. It is useful to have the less "
2581
"graphically demanding greeter here if you use the Themed Greeter for your "
2582
"main greeter. See also the <filename>Greeter</filename> key."
2583
msgstr ""
2584
2585
#: ../C/gdm.xml:2349(term)
2586
msgid "RootPath"
2587
msgstr ""
2588
2589
#: ../C/gdm.xml:2351(synopsis)
2590
#, no-wrap
2591
msgid "RootPath=defaultpath (value set by configure)"
2592
msgstr ""
2593
2594
#: ../C/gdm.xml:2352(para)
2595
msgid ""
2596
"Specifies the path which will be set in the root's session and the {Init,"
2597
"PostLogin,PreSession,PostSession} scripts executed by GDM. This value will "
2598
"be overridden with the value from <filename>/etc/default/login</filename> if "
2599
"it contains \"SUROOT=<pathname>\". If the <filename>/etc/default/"
2600
"login</filename> file exists, but contains no value for SUROOT, the value as "
2601
"defined in the GDM configuration will be used."
2602
msgstr ""
2603
2604
#: ../C/gdm.xml:2366(term)
2605
msgid "ServAuthDir"
2606
msgstr ""
2607
2608
#: ../C/gdm.xml:2368(synopsis)
2609
#, no-wrap
2610
msgid "ServAuthDir=<var>/gdm"
2611
msgstr ""
2612
2613
#: ../C/gdm.xml:2369(para)
2614
msgid ""
2615
"Directory containing the X authentication files for the individual displays. "
2616
"Should be owned by <filename>root.gdm</filename> with permissions 1770, "
2617
"where <filename>gdm</filename> is the GDM group as defined by the "
2618
"<filename>Group</filename> option. That is should be owned by root, with "
2619
"<filename>gdm</filename> group having full write permissions and the "
2620
"directory should be sticky and others should have no permission to the "
2621
"directory. This way the GDM user can't remove files owned by root in that "
2622
"directory, while still being able to write its own files there. GDM will "
2623
"attempt to change permissions for you when it's first run if the permissions "
2624
"are not the above. This directory is also used for other private files that "
2625
"the daemon needs to store. Other users should not have any way to get into "
2626
"this directory and read/change it's contents. Anybody who can read this "
2627
"directory can connect to any display on this computer."
2628
msgstr ""
2629
2630
#: ../C/gdm.xml:2391(term)
2631
msgid "SessionDesktopDir"
2632
msgstr ""
2633
2634
#: ../C/gdm.xml:2393(synopsis)
2635
#, no-wrap
2636
msgid "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<share>/xsessions/"
2637
msgstr ""
2638
2639
#: ../C/gdm.xml:2394(para)
2640
msgid ""
2641
"Directory containing the <filename>.desktop</filename> files which are the "
2642
"available sessions on the system. Since 2.4.4.2 this is treated like a PATH "
2643
"type variable and the first file found is used."
2644
msgstr ""
2645
2646
#: ../C/gdm.xml:2404(term)
2647
msgid "SoundProgram"
2648
msgstr ""
2649
2650
#: ../C/gdm.xml:2406(filename)
2651
msgid "<bin>/play"
2652
msgstr ""
2653
2654
#: ../C/gdm.xml:2406(filename)
2655
msgid "<bin>/audioplay"
2656
msgstr ""
2657
2658
#: ../C/gdm.xml:2406(synopsis)
2659
#, no-wrap
2660
msgid "SoundProgram=<placeholder-1/> (or <placeholder-2/> on Solaris)"
2661
msgstr ""
2662
2663
#: ../C/gdm.xml:2407(para)
2664
msgid ""
2665
"Application to use when playing a sound. Currently used for playing the "
2666
"login sound, see the <filename>SoundOnLoginFile</filename> key. Supported "
2667
"since 2.5.90.0."
2668
msgstr ""
2669
2670
#: ../C/gdm.xml:2417(term)
2671
msgid "StandardXServer"
2672
msgstr ""
2673
2674
#: ../C/gdm.xml:2419(synopsis)
2675
#, no-wrap
2676
msgid "StandardXServer=/dir/to/X (value assigned by configuration file)"
2677
msgstr ""
2678
2679
#: ../C/gdm.xml:2420(para)
2680
msgid ""
2681
"Full path and arguments to the standard X server command. This is used when "
2682
"gdm cannot find any other definition, and it's used as the default and "
2683
"failsafe fallback in a number of places. This should be able to run some "
2684
"sort of X server."
2685
msgstr ""
2686
2687
#: ../C/gdm.xml:2431(term)
2688
msgid "SuspendCommand"
2689
msgstr ""
2690
2691
#: ../C/gdm.xml:2433(synopsis)
2692
#, no-wrap
2693
msgid "SuspendCommand="
2694
msgstr ""
2695
2696
#: ../C/gdm.xml:2434(para)
2697
msgid ""
2698
"Full path and arguments to command to be executed when user selects Suspend "
2699
"from the Actions menu. If empty there is no such menu item. Note that the "
2700
"default for this value is not empty so to disable suspend you must set this "
2701
"explicitly to an empty value."
2702
msgstr ""
2703
2704
#: ../C/gdm.xml:2445(term)
2705
msgid "SystemCommandsInMenu"
2706
msgstr ""
2707
2708
#: ../C/gdm.xml:2447(synopsis)
2709
#, no-wrap
2710
msgid "SuspendCommand=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD"
2711
msgstr ""
2712
2713
#: ../C/gdm.xml:2448(para)
2714
msgid ""
2715
"Specify which system commands are available in the greeter menu. Valid "
2716
"values are HALT, REBOOT, SHUTDOWN, SUSPEND, and CUSTOM_CMD and these should "
2717
"be separated by semicolons. This can be useful if you want to disable some "
2718
"options in the menu, but still have them available to authenticated users "
2719
"via the SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</"
2720
"command> commands. For example, the GNOME panel uses these commands to "
2721
"provide Shutdown, Reboot, and Suspend in the application menu. Therefore if "
2722
"you turn off these options in the greeter, these options can still be "
2723
"available to users who have authenticated via the GNOME panel. Refer to the "
2724
"related <filename>AllowLogoutActions</filename> and "
2725
"<filename>RBACSystemCommandKeys</filename> configuration options."
2726
msgstr ""
2727
2728
#: ../C/gdm.xml:2469(term)
2729
msgid "TimedLoginEnable"
2730
msgstr ""
2731
2732
#: ../C/gdm.xml:2471(synopsis)
2733
#, no-wrap
2734
msgid "TimedLoginEnable=false"
2735
msgstr ""
2736
2737
#: ../C/gdm.xml:2472(para)
2738
msgid ""
2739
"If the user given in <filename>TimedLogin</filename> should be logged in "
2740
"after a number of seconds (set with <filename>TimedLoginDelay</filename>) of "
2741
"inactivity on the login screen. This is useful for public access terminals "
2742
"or perhaps even home use. If the user uses the keyboard or browses the "
2743
"menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or "
2744
"30 seconds, whichever is higher. If the user does not enter a username but "
2745
"just hits the ENTER key while the login program is requesting the username, "
2746
"then GDM will assume the user wants to login immediately as the timed user. "
2747
"Note that no password will be asked for this user so you should be careful, "
2748
"although if using PAM it can be configured to require password entry before "
2749
"allowing login."
2750
msgstr ""
2751
2752
#: ../C/gdm.xml:2492(term)
2753
msgid "TimedLogin"
2754
msgstr ""
2755
2756
#: ../C/gdm.xml:2494(synopsis)
2757
#, no-wrap
2758
msgid "TimedLogin="
2759
msgstr ""
2760
2761
#: ../C/gdm.xml:2495(para)
2762
msgid ""
2763
"This is the user that should be logged in after a specified number of "
2764
"seconds of inactivity. This can never be \"root\" and gdm will refuse to log "
2765
"in root this way. The same features as for <filename>AutomaticLogin</"
2766
"filename> are supported. The same control chars and piping to a application "
2767
"are supported."
2768
msgstr ""
2769
2770
#: ../C/gdm.xml:2507(term)
2771
msgid "TimedLoginDelay"
2772
msgstr ""
2773
2774
#: ../C/gdm.xml:2509(synopsis)
2775
#, no-wrap
2776
msgid "TimedLoginDelay=30"
2777
msgstr ""
2778
2779
#: ../C/gdm.xml:2510(para)
2780
msgid ""
2781
"Delay in seconds before the <filename>TimedLogin</filename> user will be "
2782
"logged in. It must be greater then or equal to 10."
2783
msgstr ""
2784
2785
#: ../C/gdm.xml:2518(term)
2786
msgid "User"
2787
msgstr ""
2788
2789
#: ../C/gdm.xml:2520(synopsis)
2790
#, no-wrap
2791
msgid "User=gdm"
2792
msgstr ""
2793
2794
#: ../C/gdm.xml:2521(para)
2795
msgid ""
2796
"The username under which <command>gdmlogin</command>, <command>gdmgreeter</"
2797
"command>, <command>gdmchooser</command> and the internal failsafe GTK+ "
2798
"dialogs are run. Also see <filename>Group</filename>. This user will have "
2799
"access to all the X authorization files, and perhaps to other internal GDM "
2800
"data and it should not therefore be a user such as nobody, but rather a "
2801
"dedicated user."
2802
msgstr ""
2803
2804
#: ../C/gdm.xml:2535(term)
2805
msgid "UserAuthDir"
2806
msgstr ""
2807
2808
#: ../C/gdm.xml:2537(synopsis)
2809
#, no-wrap
2810
msgid "UserAuthDir="
2811
msgstr ""
2812
2813
#: ../C/gdm.xml:2538(para)
2814
msgid ""
2815
"The directory where user's <filename>.Xauthority</filename> file should be "
2816
"saved. When nothing is specified the user's home directory is used. This is "
2817
"tilde expanded so you can set it to things like: <filename>~/authdir/</"
2818
"filename>."
2819
msgstr ""
2820
2821
#: ../C/gdm.xml:2545(para)
2822
msgid ""
2823
"If you do not use the tilde expansion, then the filename created will be "
2824
"random, like in <filename>UserAuthFBDir</filename>. This way many users can "
2825
"have the same authentication directory. For example you might want to set "
2826
"this to <filename>/tmp</filename> when user has the home directory on NFS, "
2827
"since you really don't want cookie files to go over the wire. The users "
2828
"should really have write privileges to this directory, and this directory "
2829
"should really be sticky and all that, just like the <filename>/tmp</"
2830
"filename> directory."
2831
msgstr ""
2832
2833
#: ../C/gdm.xml:2558(para)
2834
msgid ""
2835
"Normally if this is the user's home directory GDM will still refuse to put "
2836
"cookies there if it thinks it is NFS (by testing root-squashing). This can "
2837
"be changed by setting <filename>NeverPlaceCookiesOnNFS</filename> in the "
2838
"<filename>[security]</filename> section to false."
2839
msgstr ""
2840
2841
#: ../C/gdm.xml:2569(term)
2842
msgid "UserAuthFBDir"
2843
msgstr ""
2844
2845
#: ../C/gdm.xml:2571(synopsis)
2846
#, no-wrap
2847
msgid "UserAuthFBDir=/tmp"
2848
msgstr ""
2849
2850
#: ../C/gdm.xml:2572(para)
2851
msgid ""
2852
"If GDM fails to update the user's <filename>.Xauthority</filename> file a "
2853
"fallback cookie is created in this directory."
2854
msgstr ""
2855
2856
#: ../C/gdm.xml:2581(term)
2857
msgid "UserAuthFile"
2858
msgstr ""
2859
2860
#: ../C/gdm.xml:2583(synopsis)
2861
#, no-wrap
2862
msgid "UserAuthFile=.Xauthority"
2863
msgstr ""
2864
2865
#: ../C/gdm.xml:2584(para)
2866
msgid "Name of the file used for storing user cookies."
2867
msgstr ""
2868
2869
#: ../C/gdm.xml:2591(term)
2870
msgid "VTAllocation"
2871
msgstr ""
2872
2873
#: ../C/gdm.xml:2593(synopsis)
2874
#, no-wrap
2875
msgid "VTAllocation=true"
2876
msgstr ""
2877
2878
#: ../C/gdm.xml:2594(para)
2879
msgid ""
2880
"On systems where GDM supports automatic VT (virtual terminal) allocation "
2881
"(currently Linux and FreeBSD only), you can have GDM automatically append "
2882
"the vt argument to the X server executable. This way races that come up from "
2883
"each X server managing it's own vt allocation can be avoided. See also "
2884
"<filename>FirstVT</filename>."
2885
msgstr ""
2886
2887
#: ../C/gdm.xml:2606(term)
2888
msgid "XKeepsCrashing"
2889
msgstr ""
2890
2891
#: ../C/gdm.xml:2608(synopsis)
2892
#, no-wrap
2893
msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing"
2894
msgstr ""
2895
2896
#: ../C/gdm.xml:2609(para)
2897
msgid ""
2898
"A script to run in case X keeps crashing. This is for running An X "
2899
"configuration or whatever else to make the X configuration work. See the "
2900
"script that came with the distribution for an example. The distributed "
2901
"<filename>XKeepsCrashing</filename> script is tested on Red Hat, but may "
2902
"work elsewhere. Your system integrator should make sure this script is up to "
2903
"date for your particular system."
2904
msgstr ""
2905
2906
#: ../C/gdm.xml:2618(para)
2907
msgid ""
2908
"In case <filename>FailsafeXServer</filename> is setup, that will be tried "
2909
"first. and this only used as a backup if even that X server keeps crashing."
2910
msgstr ""
2911
2912
#: ../C/gdm.xml:2627(term)
2913
msgid "Xnest"
2914
msgstr ""
2915
2916
#: ../C/gdm.xml:2629(synopsis)
2917
#, no-wrap
2918
msgid "Xnest=<bin>/X11/Xephyr -audit 0"
2919
msgstr ""
2920
2921
#: ../C/gdm.xml:2630(para)
2922
msgid ""
2923
"The full path and arguments to the nested X server command, which can be "
2924
"Xephyr, Xnest, or similar program. This command is used for starting nested "
2925
"displays allowing the user to start new login screens in a nested window. "
2926
"Xephyr is recommended since it works best and better supports modern X "
2927
"server extensions. Therefore GDM will set the default configuration to use "
2928
"Xephyr if available. If Xephyr is not available, then Xnest will be used if "
2929
"it is available."
2930
msgstr ""
2931
2932
#: ../C/gdm.xml:2644(term)
2933
msgid "XnestUnscaledFontPath"
2934
msgstr ""
2935
2936
#: ../C/gdm.xml:2646(synopsis)
2937
#, no-wrap
2938
msgid "XnestUnscaledFontPath=true"
2939
msgstr ""
2940
2941
#: ../C/gdm.xml:2647(para)
2942
msgid ""
2943
"Set to true if the nested X server command program supports the \":unscaled"
2944
"\" suffix in the FontPath (passed to nested X server command via the -fp "
2945
"argument). Some Xnest (e.g. Xsun Xnest) programs do not, and it is necessary "
2946
"to set this to false for such nested X server commands to work with GDM. "
2947
"Refer to the <filename>Xnest</filename> configuration option."
2948
msgstr ""
2949
2950
#: ../C/gdm.xml:2661(title)
2951
msgid "Security Options"
2952
msgstr ""
2953
2954
#: ../C/gdm.xml:2664(title)
2955
msgid "[security]"
2956
msgstr ""
2957
2958
#: ../C/gdm.xml:2667(term)
2959
msgid "AllowRoot"
2960
msgstr ""
2961
2962
#: ../C/gdm.xml:2669(synopsis)
2963
#, no-wrap
2964
msgid "AllowRoot=true"
2965
msgstr ""
2966
2967
#: ../C/gdm.xml:2670(para)
2968
msgid ""
2969
"Allow root (privileged user) to log in through GDM. Set this to false if you "
2970
"want to disallow such logins."
2971
msgstr ""
2972
2973
#: ../C/gdm.xml:2674(para)
2974
msgid ""
2975
"On systems that support PAM, this parameter is not as useful as you can use "
2976
"PAM to do the same thing, and in fact do even more. However it is still "
2977
"followed, so you should probably leave it true for PAM systems."
2978
msgstr ""
2979
2980
#: ../C/gdm.xml:2684(term)
2981
msgid "AllowRemoteRoot"
2982
msgstr ""
2983
2984
#: ../C/gdm.xml:2686(synopsis)
2985
#, no-wrap
2986
msgid "AllowRemoteRoot=false"
2987
msgstr ""
2988
2989
#: ../C/gdm.xml:2687(para)
2990
msgid ""
2991
"Allow root (privileged user) to log in remotely through GDM. This value "
2992
"should be set to true to allow such logins. Remote logins are any logins "
2993
"that come in through the XDMCP."
2994
msgstr ""
2995
2996
#: ../C/gdm.xml:2692(para)
2997
msgid ""
2998
"On systems that support PAM, this parameter is not as useful since you can "
2999
"use PAM to do the same thing, and do even more."
3000
msgstr ""
3001
3002
#: ../C/gdm.xml:2697(para)
3003
msgid ""
3004
"This value will be overridden and set to false if the <filename>/etc/default/"
3005
"login</filename> file exists and contains \"CONSOLE=/dev/login\", and set to "
3006
"true if the <filename>/etc/default/login</filename> file exists and contains "
3007
"any other value or no value for CONSOLE."
3008
msgstr ""
3009
3010
#: ../C/gdm.xml:2708(term)
3011
msgid "AllowRemoteAutoLogin"
3012
msgstr ""
3013
3014
#: ../C/gdm.xml:2710(synopsis)
3015
#, no-wrap
3016
msgid "AllowRemoteAutoLogin=false"
3017
msgstr ""
3018
3019
#: ../C/gdm.xml:2711(para)
3020
msgid ""
3021
"Allow the timed login to work remotely. That is, remote connections through "
3022
"XDMCP will be allowed to log into the \"TimedLogin\" user by letting the "
3023
"login window time out, just like the local user on the first console."
3024
msgstr ""
3025
3026
#: ../C/gdm.xml:2717(para)
3027
msgid "Note that this can make a system quite insecure, and thus is off by default."
3028
msgstr ""
3029
3030
#: ../C/gdm.xml:2725(term)
3031
msgid "CheckDirOwner"
3032
msgstr ""
3033
3034
#: ../C/gdm.xml:2727(synopsis)
3035
#, no-wrap
3036
msgid "CheckDirOwner=true"
3037
msgstr ""
3038
3039
#: ../C/gdm.xml:2728(para)
3040
msgid ""
3041
"By default GDM checks the ownership of the home directories before writing "
3042
"to them, this prevents security issues in case of bad setup. However in some "
3043
"instances home directories will be owned by a different user and in this "
3044
"case it is necessary to turn this option on. You will also most likely have "
3045
"to turn the <filename>RelaxPermissions</filename> key to at least value 1 "
3046
"since in such a scenario home directories are likely to be group writable. "
3047
"Supported since 2.6.0.4."
3048
msgstr ""
3049
3050
#: ../C/gdm.xml:2742(term)
3051
msgid "SupportAutomount"
3052
msgstr ""
3053
3054
#: ../C/gdm.xml:2744(synopsis)
3055
#, no-wrap
3056
msgid "SupportAutomount=false"
3057
msgstr ""
3058
3059
#: ../C/gdm.xml:2745(para)
3060
msgid ""
3061
"By default GDM checks the ownership of the home directories before writing "
3062
"to them, this prevents security issues in case of bad setup. However, when "
3063
"home directories are managed by automounter, they are often not mounted "
3064
"before they are accessed. This option works around subtleties of Linux "
3065
"automounter."
3066
msgstr ""
3067
3068
#: ../C/gdm.xml:2757(term)
3069
msgid "DisallowTCP"
3070
msgstr ""
3071
3072
#: ../C/gdm.xml:2759(synopsis)
3073
#, no-wrap
3074
msgid "DisallowTCP=true"
3075
msgstr ""
3076
3077
#: ../C/gdm.xml:2760(para)
3078
msgid ""
3079
"If true, then always append <filename>-nolisten tcp</filename> to the "
3080
"command line of local X servers, thus disallowing TCP connection. This is "
3081
"useful if you do not care for allowing remote connections, since the X "
3082
"protocol could really be potentially a security hazard to leave open, even "
3083
"though no known security problems exist."
3084
msgstr ""
3085
3086
#: ../C/gdm.xml:2773(term)
3087
msgid "NeverPlaceCookiesOnNFS"
3088
msgstr ""
3089
3090
#: ../C/gdm.xml:2775(synopsis)
3091
#, no-wrap
3092
msgid "NeverPlaceCookiesOnNFS=true"
3093
msgstr ""
3094
3095
#: ../C/gdm.xml:2776(para)
3096
msgid ""
3097
"Normally if this is true (which is by default), GDM will not place cookies "
3098
"into the user's home directory if this directory is on NFS. Well, GDM will "
3099
"consider any filesystem with root-squashing an NFS filesystem. Sometimes "
3100
"however the remote file system can have root squashing and be safe (perhaps "
3101
"by using encryption). In this case set this to 'false'. Note that this "
3102
"option appeared in version 2.4.4.4 and is ignored in previous versions."
3103
msgstr ""
3104
3105
#: ../C/gdm.xml:2790(term)
3106
msgid "PasswordRequired"
3107
msgstr ""
3108
3109
#: ../C/gdm.xml:2792(synopsis)
3110
#, no-wrap
3111
msgid "PasswordRequired=false"
3112
msgstr ""
3113
3114
#: ../C/gdm.xml:2793(para)
3115
msgid ""
3116
"If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be passed as a flag to "
3117
"pam_authenticate and pam_acct_mgmt, disallowing NULL password. This setting "
3118
"will only take effect if PAM is being used by GDM. This value will be "
3119
"overridden with the value from <filename>/etc/default/login</filename> if it "
3120
"contains \"PASSREQ=[YES|NO]\". If the <filename>/etc/default/login</"
3121
"filename> file exists, but contains no value for PASSREQ, the value as "
3122
"defined in the GDM configuration will be used."
3123
msgstr ""
3124
3125
#: ../C/gdm.xml:2809(term)
3126
msgid "RelaxPermissions"
3127
msgstr ""
3128
3129
#: ../C/gdm.xml:2811(synopsis)
3130
#, no-wrap
3131
msgid "RelaxPermissions=0"
3132
msgstr ""
3133
3134
#: ../C/gdm.xml:2812(para)
3135
msgid ""
3136
"By default GDM ignores files and directories writable to other users than "
3137
"the owner."
3138
msgstr ""
3139
3140
#: ../C/gdm.xml:2817(para)
3141
msgid ""
3142
"Changing the value of RelaxPermissions makes it possible to alter this "
3143
"behavior:"
3144
msgstr ""
3145
3146
#: ../C/gdm.xml:2822(para)
3147
msgid "0 - Paranoia option. Only accepts user owned files and directories."
3148
msgstr ""
3149
3150
#: ../C/gdm.xml:2826(para)
3151
msgid "1 - Allow group writable files and directories."
3152
msgstr ""
3153
3154
#: ../C/gdm.xml:2829(para)
3155
msgid "2 - Allow world writable files and directories."
3156
msgstr ""
3157
3158
#: ../C/gdm.xml:2836(term)
3159
msgid "RetryDelay"
3160
msgstr ""
3161
3162
#: ../C/gdm.xml:2838(synopsis)
3163
#, no-wrap
3164
msgid "RetryDelay=1"
3165
msgstr ""
3166
3167
#: ../C/gdm.xml:2839(para)
3168
msgid ""
3169
"The number of seconds GDM should wait before reactivating the entry field "
3170
"after a failed login."
3171
msgstr ""
3172
3173
#: ../C/gdm.xml:2847(term)
3174
msgid "UserMaxFile"
3175
msgstr ""
3176
3177
#: ../C/gdm.xml:2849(synopsis)
3178
#, no-wrap
3179
msgid "UserMaxFile=65536"
3180
msgstr ""
3181
3182
#: ../C/gdm.xml:2850(para)
3183
msgid ""
3184
"GDM will refuse to read/write files bigger than this number (specified in "
3185
"bytes)."
3186
msgstr ""
3187
3188
#: ../C/gdm.xml:2855(para)
3189
msgid ""
3190
"In addition to the size check GDM is extremely picky about accessing files "
3191
"in user directories. It will not follow symlinks and can optionally refuse "
3192
"to read files and directories writable by other than the owner. See the "
3193
"<filename>RelaxPermissions</filename> option for more info."
3194
msgstr ""
3195
3196
#: ../C/gdm.xml:2868(title)
3197
msgid "XDCMP Support"
3198
msgstr ""
3199
3200
#: ../C/gdm.xml:2871(title)
3201
msgid "[xdmcp]"
3202
msgstr ""
3203
3204
#: ../C/gdm.xml:2874(term)
3205
msgid "DisplaysPerHost"
3206
msgstr ""
3207
3208
#: ../C/gdm.xml:2876(synopsis)
3209
#, no-wrap
3210
msgid "DisplaysPerHost=1"
3211
msgstr ""
3212
3213
#: ../C/gdm.xml:2877(para)
3214
msgid ""
3215
"To prevent attackers from filling up the pending queue, GDM will only allow "
3216
"one connection for each remote computer. If you want to provide display "
3217
"services to computers with more than one screen, you should increase the "
3218
"<filename>DisplaysPerHost</filename> value accordingly."
3219
msgstr ""
3220
3221
#: ../C/gdm.xml:2885(para)
3222
msgid ""
3223
"Note that the number of connections from the local computer is unlimited. "
3224
"Only remote connections are limited by this number."
3225
msgstr ""
3226
3227
#: ../C/gdm.xml:2893(term) ../C/gdm.xml:4140(term)
3228
msgid "Enable"
3229
msgstr ""
3230
3231
#: ../C/gdm.xml:2895(synopsis) ../C/gdm.xml:4142(synopsis)
3232
#, no-wrap
3233
msgid "Enable=false"
3234
msgstr ""
3235
3236
#: ../C/gdm.xml:2896(para)
3237
msgid ""
3238
"Setting this to true enables XDMCP support allowing remote displays/X "
3239
"terminals to be managed by GDM."
3240
msgstr ""
3241
3242
#: ../C/gdm.xml:2901(para)
3243
msgid ""
3244
"<filename>gdm</filename> listens for requests on UDP port 177. See the Port "
3245
"option for more information."
3246
msgstr ""
3247
3248
#: ../C/gdm.xml:2906(para)
3249
msgid ""
3250
"If GDM is compiled to support it, access from remote displays can be "
3251
"controlled using the TCP Wrappers library. The service name is "
3252
"<filename>gdm</filename>"
3253
msgstr ""
3254
3255
#: ../C/gdm.xml:2912(para)
3256
msgid ""
3257
"You should add <screen>\n"
3258
"gdm:.my.domain\n"
3259
"</screen> to your <filename><etc>/hosts.allow</filename>, depending on "
3260
"your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:"
3261
"hosts.allow\">hosts.allow(5)</ulink> man page for details."
3262
msgstr ""
3263
3264
#: ../C/gdm.xml:2923(para)
3265
msgid ""
3266
"Please note that XDMCP is not a particularly secure protocol and that it is "
3267
"a good idea to block UDP port 177 on your firewall unless you really need it."
3268
msgstr ""
3269
3270
#: ../C/gdm.xml:2932(term)
3271
msgid "EnableProxy"
3272
msgstr ""
3273
3274
#: ../C/gdm.xml:2934(synopsis)
3275
#, no-wrap
3276
msgid "EnableProxy=false"
3277
msgstr ""
3278
3279
#: ../C/gdm.xml:2935(para)
3280
msgid ""
3281
"Setting this to true enables support for running XDMCP sessions on a local "
3282
"proxy X server. This may improve the performance of XDMCP sessions, "
3283
"especially on high latency networks, as many X protocol operations can be "
3284
"completed without going over the network."
3285
msgstr ""
3286
3287
#: ../C/gdm.xml:2942(para)
3288
msgid ""
3289
"Note, however, that this mode will significantly increase the burden on the "
3290
"machine hosting the XDMCP sessions"
3291
msgstr ""
3292
3293
#: ../C/gdm.xml:2946(para)
3294
msgid ""
3295
"See the <filename>FlexiProxy</filename> and <filename>FlexiProxyDisconnect</"
3296
"filename> options for further details on how to configure support for this "
3297
"feature."
3298
msgstr ""
3299
3300
#: ../C/gdm.xml:2955(term)
3301
msgid "HonorIndirect"
3302
msgstr ""
3303
3304
#: ../C/gdm.xml:2957(synopsis)
3305
#, no-wrap
3306
msgid "HonorIndirect=true"
3307
msgstr ""
3308
3309
#: ../C/gdm.xml:2958(para)
3310
msgid ""
3311
"Enables XDMCP INDIRECT choosing (i.e. remote execution of "
3312
"<filename>gdmchooser</filename>) for X-terminals which don't supply their "
3313
"own display browser."
3314
msgstr ""
3315
3316
#: ../C/gdm.xml:2967(term)
3317
msgid "MaxPending"
3318
msgstr ""
3319
3320
#: ../C/gdm.xml:2969(synopsis)
3321
#, no-wrap
3322
msgid "MaxPending=4"
3323
msgstr ""
3324
3325
#: ../C/gdm.xml:2970(para)
3326
msgid ""
3327
"To avoid denial of service attacks, GDM has fixed size queue of pending "
3328
"connections. Only MaxPending displays can start at the same time."
3329
msgstr ""
3330
3331
#: ../C/gdm.xml:2976(para)
3332
msgid ""
3333
"Please note that this parameter does *not* limit the number of remote "
3334
"displays which can be managed. It only limits the number of displays "
3335
"initiating a connection simultaneously."
3336
msgstr ""
3337
3338
#: ../C/gdm.xml:2985(term)
3339
msgid "MaxPendingIndirect"
3340
msgstr ""
3341
3342
#: ../C/gdm.xml:2987(synopsis)
3343
#, no-wrap
3344
msgid "MaxPendingIndirect=4"
3345
msgstr ""
3346
3347
#: ../C/gdm.xml:2988(para)
3348
msgid ""
3349
"GDM will only provide <filename>MaxPendingIndirect</filename> displays with "
3350
"host choosers simultaneously. If more queries from different hosts come in, "
3351
"the oldest ones will be forgotten."
3352
msgstr ""
3353
3354
#: ../C/gdm.xml:2998(term)
3355
msgid "MaxSessions"
3356
msgstr ""
3357
3358
#: ../C/gdm.xml:3000(synopsis)
3359
#, no-wrap
3360
msgid "MaxSessions=16"
3361
msgstr ""
3362
3363
#: ../C/gdm.xml:3001(para)
3364
msgid ""
3365
"Determines the maximum number of remote display connections which will be "
3366
"managed simultaneously. I.e. the total number of remote displays that can "
3367
"use your host."
3368
msgstr ""
3369
3370
#: ../C/gdm.xml:3010(term)
3371
msgid "MaxWait"
3372
msgstr ""
3373
3374
#: ../C/gdm.xml:3012(synopsis)
3375
#, no-wrap
3376
msgid "MaxWait=30"
3377
msgstr ""
3378
3379
#: ../C/gdm.xml:3013(para)
3380
msgid ""
3381
"When GDM is ready to manage a display an ACCEPT packet is sent to it "
3382
"containing a unique session id which will be used in future XDMCP "
3383
"conversations."
3384
msgstr ""
3385
3386
#: ../C/gdm.xml:3019(para)
3387
msgid ""
3388
"GDM will then place the session id in the pending queue waiting for the "
3389
"display to respond with a MANAGE request."
3390
msgstr ""
3391
3392
#: ../C/gdm.xml:3024(para)
3393
msgid ""
3394
"If no response is received within MaxWait seconds, GDM will declare the "
3395
"display dead and erase it from the pending queue freeing up the slot for "
3396
"other displays."
3397
msgstr ""
3398
3399
#: ../C/gdm.xml:3033(term)
3400
msgid "MaxWaitIndirect"
3401
msgstr ""
3402
3403
#: ../C/gdm.xml:3035(synopsis)
3404
#, no-wrap
3405
msgid "MaxWaitIndirect=30"
3406
msgstr ""
3407
3408
#: ../C/gdm.xml:3036(para)
3409
msgid ""
3410
"The MaxWaitIndirect parameter determines the maximum number of seconds "
3411
"between the time where a user chooses a host and the subsequent indirect "
3412
"query where the user is connected to the host. When the timeout is exceeded, "
3413
"the information about the chosen host is forgotten and the indirect slot "
3414
"freed up for other displays. The information may be forgotten earlier if "
3415
"there are more hosts trying to send indirect queries then "
3416
"<filename>MaxPendingIndirect</filename>."
3417
msgstr ""
3418
3419
#: ../C/gdm.xml:3050(term)
3420
msgid "Port"
3421
msgstr ""
3422
3423
#: ../C/gdm.xml:3052(synopsis)
3424
#, no-wrap
3425
msgid "Port=177"
3426
msgstr ""
3427
3428
#: ../C/gdm.xml:3053(para)
3429
msgid ""
3430
"The UDP port number <filename>gdm</filename> should listen to for XDMCP "
3431
"requests. Don't change this unless you know what you are doing."
3432
msgstr ""
3433
3434
#: ../C/gdm.xml:3062(term)
3435
msgid "PingIntervalSeconds"
3436
msgstr ""
3437
3438
#: ../C/gdm.xml:3064(synopsis)
3439
#, no-wrap
3440
msgid "PingIntervalSeconds=15"
3441
msgstr ""
3442
3443
#: ../C/gdm.xml:3065(para)
3444
msgid ""
3445
"Interval in which to ping the X server in seconds. If the X server doesn't "
3446
"return before the next time we ping it, the connection is stopped and the "
3447
"session ended. This is a combination of the XDM PingInterval and "
3448
"PingTimeout, but in seconds."
3449
msgstr ""
3450
3451
#: ../C/gdm.xml:3073(para)
3452
msgid ""
3453
"Note that GDM in the past used to have a <filename>PingInterval</filename> "
3454
"configuration key which was also in minutes. For most purposes you'd want "
3455
"this setting to be lower then one minute however since in most cases where "
3456
"XDMCP would be used (such as terminal labs), a lag of more than 15 or so "
3457
"seconds would really mean that the terminal was turned off or restarted and "
3458
"you would want to end the session."
3459
msgstr ""
3460
3461
#: ../C/gdm.xml:3086(term)
3462
msgid "ProxyReconnect"
3463
msgstr ""
3464
3465
#: ../C/gdm.xml:3088(synopsis)
3466
#, no-wrap
3467
msgid "FlexiProxyReconnect="
3468
msgstr ""
3469
3470
#: ../C/gdm.xml:3089(para)
3471
msgid ""
3472
"Setting this option enables experimental support for session migration with "
3473
"XDMCP sessions. This enables users to disconnect from their session and "
3474
"later reconnect to that same session, possibly from a different terminal."
3475
msgstr ""
3476
3477
#: ../C/gdm.xml:3095(para)
3478
msgid ""
3479
"In order to use this feature, you must have a nested X server available "
3480
"which supports disconnecting from its parent X server and reconnecting to "
3481
"another X server. Currently, the Distributed Multihead X (DMX) server "
3482
"supports this feature to some extent and other projects like NoMachine NX "
3483
"are busy implementing it."
3484
msgstr ""
3485
3486
#: ../C/gdm.xml:3102(para)
3487
msgid ""
3488
"This option should be set to the path of a command which will handle "
3489
"reconnecting the XDMCP proxy to another backend display. A sample "
3490
"implementation for use with DMX is supplied."
3491
msgstr ""
3492
3493
#: ../C/gdm.xml:3111(term)
3494
msgid "ProxyXServer"
3495
msgstr ""
3496
3497
#: ../C/gdm.xml:3113(synopsis)
3498
#, no-wrap
3499
msgid "ProxyXServer="
3500
msgstr ""
3501
3502
#: ../C/gdm.xml:3114(para)
3503
msgid ""
3504
"The X server command line for a XDMCP proxy. Any nested X server like Xnest, "
3505
"Xephyr or Xdmx should work fairly well."
3506
msgstr ""
3507
3508
#: ../C/gdm.xml:3122(term)
3509
msgid "Willing"
3510
msgstr ""
3511
3512
#: ../C/gdm.xml:3124(synopsis)
3513
#, no-wrap
3514
msgid "Willing=<etc>/gdm/Xwilling"
3515
msgstr ""
3516
3517
#: ../C/gdm.xml:3125(para)
3518
msgid ""
3519
"When the machine sends a WILLING packet back after a QUERY it sends a string "
3520
"that gives the current status of this server. The default message is the "
3521
"system ID, but it is possible to create a script that displays customized "
3522
"message. If this script doesn't exist or this key is empty the default "
3523
"message is sent. If this script succeeds and produces some output, the first "
3524
"line of it's output is sent (and only the first line). It runs at most once "
3525
"every 3 seconds to prevent possible denial of service by flooding the "
3526
"machine with QUERY packets."
3527
msgstr ""
3528
3529
#: ../C/gdm.xml:3143(title)
3530
msgid "Common GUI Configuration Options"
3531
msgstr ""
3532
3533
#: ../C/gdm.xml:3146(title)
3534
msgid "[gui]"
3535
msgstr ""
3536
3537
#: ../C/gdm.xml:3149(term)
3538
msgid "AllowGtkThemeChange"
3539
msgstr ""
3540
3541
#: ../C/gdm.xml:3151(synopsis)
3542
#, no-wrap
3543
msgid "AllowGtkThemeChange=true"
3544
msgstr ""
3545
3546
#: ../C/gdm.xml:3152(para)
3547
msgid ""
3548
"If to allow changing the GTK+ (widget) theme from the greeter. Currently "
3549
"this only affects the standard greeter as the graphical greeter does not yet "
3550
"have this ability. The theme will stay in effect on this display until "
3551
"changed and will affect all the other windows that are put up by GDM. "
3552
"Supported since 2.5.90.2."
3553
msgstr ""
3554
3555
#: ../C/gdm.xml:3164(term)
3556
msgid "GtkRC"
3557
msgstr ""
3558
3559
#: ../C/gdm.xml:3166(synopsis)
3560
#, no-wrap
3561
msgid "GtkRC="
3562
msgstr ""
3563
3564
#: ../C/gdm.xml:3167(para)
3565
msgid ""
3566
"Path to a <filename>gtkrc</filename> to read when GDM puts up a window. You "
3567
"should really now use the <filename>GtkTheme</filename> key for just setting "
3568
"a theme."
3569
msgstr ""
3570
3571
#: ../C/gdm.xml:3176(term)
3572
msgid "GtkTheme"
3573
msgstr ""
3574
3575
#: ../C/gdm.xml:3178(synopsis)
3576
#, no-wrap
3577
msgid "GtkTheme=Default"
3578
msgstr ""
3579
3580
#: ../C/gdm.xml:3179(para)
3581
msgid ""
3582
"A name of an installed theme to use by default. It will be used in the "
3583
"greeter, chooser and all other GUI windows put up by GDM. Supported since "
3584
"2.5.90.2."
3585
msgstr ""
3586
3587
#: ../C/gdm.xml:3188(term)
3588
msgid "GtkThemesToAllow"
3589
msgstr ""
3590
3591
#: ../C/gdm.xml:3190(synopsis)
3592
#, no-wrap
3593
msgid "GtkThemesToAllow=all"
3594
msgstr ""
3595
3596
#: ../C/gdm.xml:3191(para)
3597
msgid ""
3598
"Comma separated list of themes to allow. These must be the names of the "
3599
"themes installed in the standard locations for GTK+ themes. You can also "
3600
"specify 'all' to allow all installed themes. This is related to the "
3601
"<filename>AllowGtkThemeChange</filename> key. Supported since 2.5.90.2."
3602
msgstr ""
3603
3604
#: ../C/gdm.xml:3203(term)
3605
msgid "MaxIconWidth"
3606
msgstr ""
3607
3608
#: ../C/gdm.xml:3205(synopsis)
3609
#, no-wrap
3610
msgid "MaxIconWidth=128"
3611
msgstr ""
3612
3613
#: ../C/gdm.xml:3206(para)
3614
msgid ""
3615
"Specifies the maximum icon width (in pixels) that the face browser will "
3616
"display. Icons larger than this will be scaled. This also affects icons in "
3617
"the XDMCP chooser."
3618
msgstr ""
3619
3620
#: ../C/gdm.xml:3215(term)
3621
msgid "MaxIconHeight"
3622
msgstr ""
3623
3624
#: ../C/gdm.xml:3217(synopsis)
3625
#, no-wrap
3626
msgid "MaxIconHeight=128"
3627
msgstr ""
3628
3629
#: ../C/gdm.xml:3218(para)
3630
msgid ""
3631
"Specifies the maximum icon height (in pixels) that the face browser will "
3632
"display. Icons larger than this will be scaled. This also affects icons in "
3633
"the XDMCP chooser."
3634
msgstr ""
3635
3636
#: ../C/gdm.xml:3229(title)
3637
msgid "Greeter Configuration"
3638
msgstr ""
3639
3640
#: ../C/gdm.xml:3232(title)
3641
msgid "[greeter]"
3642
msgstr ""
3643
3644
#: ../C/gdm.xml:3235(term)
3645
msgid "BackgroundColor"
3646
msgstr ""
3647
3648
#: ../C/gdm.xml:3237(synopsis)
3649
#, no-wrap
3650
msgid "BackgroundColor=#76848F"
3651
msgstr ""
3652
3653
#: ../C/gdm.xml:3238(para)
3654
msgid ""
3655
"If the BackgroundType is 2, use this color in the background of the greeter. "
3656
"Also use it as the back of transparent images set on the background and if "
3657
"the BackgroundRemoteOnlyColor is set and this is a remote display. This only "
3658
"affects the GTK+ Greeter."
3659
msgstr ""
3660
3661
#: ../C/gdm.xml:3249(term)
3662
msgid "BackgroundProgramInitialDelay"
3663
msgstr ""
3664
3665
#: ../C/gdm.xml:3251(synopsis)
3666
#, no-wrap
3667
msgid "BackgroundProgramInitialDelay=30"
3668
msgstr ""
3669
3670
#: ../C/gdm.xml:3252(para)
3671
msgid ""
3672
"The background application will be started after at least that many seconds "
3673
"of inactivity."
3674
msgstr ""
3675
3676
#: ../C/gdm.xml:3260(term)
3677
msgid "RestartBackgroundProgram"
3678
msgstr ""
3679
3680
#: ../C/gdm.xml:3262(synopsis)
3681
#, no-wrap
3682
msgid "RestartBackgroundProgram=true"
3683
msgstr ""
3684
3685
#: ../C/gdm.xml:3263(para)
3686
msgid ""
3687
"If set the background application will be restarted when it has exited, "
3688
"after the delay described below has elapsed. This option can be useful when "
3689
"you wish to run a screen saver application when no user is using the "
3690
"computer."
3691
msgstr ""
3692
3693
#: ../C/gdm.xml:3273(term)
3694
msgid "BackgroundProgramRestartDelay"
3695
msgstr ""
3696
3697
#: ../C/gdm.xml:3275(synopsis)
3698
#, no-wrap
3699
msgid "BackgroundProgramRestartDelay=30"
3700
msgstr ""
3701
3702
#: ../C/gdm.xml:3276(para)
3703
msgid ""
3704
"The background application will be restarted after at least that many "
3705
"seconds of inactivity."
3706
msgstr ""
3707
3708
#: ../C/gdm.xml:3284(term)
3709
msgid "BackgroundImage"
3710
msgstr ""
3711
3712
#: ../C/gdm.xml:3286(synopsis)
3713
#, no-wrap
3714
msgid "BackgroundImage=somefile.png"
3715
msgstr ""
3716
3717
#: ../C/gdm.xml:3287(para)
3718
msgid ""
3719
"If the BackgroundType is 1, then display this file as the background in the "
3720
"greeter. This only affects the GTK+ Greeter."
3721
msgstr ""
3722
3723
#: ../C/gdm.xml:3296(term)
3724
msgid "BackgroundProgram"
3725
msgstr ""
3726
3727
#: ../C/gdm.xml:3298(synopsis)
3728
#, no-wrap
3729
msgid "BackgroundProgram=<bin>/xeyes"
3730
msgstr ""
3731
3732
#: ../C/gdm.xml:3299(para)
3733
msgid ""
3734
"If set this command will be run in the background while the login window is "
3735
"being displayed. Note that not all applications will run this way, since GDM "
3736
"does not usually have a home directory. You could set up home directory for "
3737
"the GDM user if you wish to run applications which require it. This only "
3738
"affects the GTK+ Greeter."
3739
msgstr ""
3740
3741
#: ../C/gdm.xml:3311(term)
3742
msgid "BackgroundRemoteOnlyColor"
3743
msgstr ""
3744
3745
#: ../C/gdm.xml:3313(synopsis)
3746
#, no-wrap
3747
msgid "BackgroundRemoteOnlyColor=true"
3748
msgstr ""
3749
3750
#: ../C/gdm.xml:3314(para)
3751
msgid ""
3752
"On remote displays only set the color background. This is to make network "
3753
"load lighter. The <filename>BackgroundProgram</filename> is also not run. "
3754
"This only affects the GTK+ Greeter."
3755
msgstr ""
3756
3757
#: ../C/gdm.xml:3324(term)
3758
msgid "BackgroundScaleToFit"
3759
msgstr ""
3760
3761
#: ../C/gdm.xml:3326(synopsis)
3762
#, no-wrap
3763
msgid "BackgroundScaleToFit=true"
3764
msgstr ""
3765
3766
#: ../C/gdm.xml:3327(para)
3767
msgid "Scale background image to fit the screen. This only affects the GTK+ Greeter."
3768
msgstr ""
3769
3770
#: ../C/gdm.xml:3335(term)
3771
msgid "BackgroundType"
3772
msgstr ""
3773
3774
#: ../C/gdm.xml:3337(synopsis)
3775
#, no-wrap
3776
msgid "BackgroundType=2"
3777
msgstr ""
3778
3779
#: ../C/gdm.xml:3338(para)
3780
msgid ""
3781
"The type of background to set. 0 is none, 1 is image and color, 2 is color "
3782
"and 3 is image. This only affects the GTK+ Greeter."
3783
msgstr ""
3784
3785
#: ../C/gdm.xml:3346(term)
3786
msgid "Browser"
3787
msgstr ""
3788
3789
#: ../C/gdm.xml:3348(synopsis)
3790
#, no-wrap
3791
msgid "Browser=true"
3792
msgstr ""
3793
3794
#: ../C/gdm.xml:3349(para)
3795
msgid ""
3796
"Set to true to enable the face browser. See the ``The GTK+ Greeter'' section "
3797
"for more information on the face browser. This option only works for the GTK"
3798
"+ Greeter. For the Themed Greeter, the face browser is enabled by choosing a "
3799
"theme which includes a face browser"
3800
msgstr ""
3801
3802
#: ../C/gdm.xml:3360(term)
3803
msgid "ChooserButton"
3804
msgstr ""
3805
3806
#: ../C/gdm.xml:3362(synopsis)
3807
#, no-wrap
3808
msgid "ChooserButton=true"
3809
msgstr ""
3810
3811
#: ../C/gdm.xml:3363(para)
3812
msgid ""
3813
"If true, add a chooser button to the Actions menu that will restart the "
3814
"current X server with a chooser. XDMCP does not need to be enabled on the "
3815
"local computer for this to work."
3816
msgstr ""
3817
3818
#: ../C/gdm.xml:3372(term)
3819
msgid "ConfigAvailable"
3820
msgstr ""
3821
3822
#: ../C/gdm.xml:3374(synopsis)
3823
#, no-wrap
3824
msgid "ConfigAvailable=false"
3825
msgstr ""
3826
3827
#: ../C/gdm.xml:3375(para)
3828
msgid ""
3829
"If true, allows the configurator to be run from the greeter. Note that the "
3830
"user will need to type in the root password before the configurator will be "
3831
"started. This is set to false by default for additional security. See the "
3832
"<filename>Configurator</filename> option in the daemon section."
3833
msgstr ""
3834
3835
#: ../C/gdm.xml:3387(term)
3836
msgid "DefaultFace"
3837
msgstr ""
3838
3839
#: ../C/gdm.xml:3389(synopsis)
3840
#, no-wrap
3841
msgid "DefaultFace=<share>/pixmaps/nophoto.png"
3842
msgstr ""
3843
3844
#: ../C/gdm.xml:3390(para)
3845
msgid ""
3846
"If a user has no defined face image, GDM will use the \"stock_person\" icon "
3847
"defined in the current GTK+ theme. If no such image is defined, the image "
3848
"specified by <filename>DefaultFace</filename> will be used. The image must "
3849
"be in a gdk-pixbuf supported format and the file must be readable to the GDM "
3850
"user."
3851
msgstr ""
3852
3853
#: ../C/gdm.xml:3402(term)
3854
msgid "Include"
3855
msgstr ""
3856
3857
#: ../C/gdm.xml:3404(synopsis)
3858
#, no-wrap
3859
msgid "Include="
3860
msgstr ""
3861
3862
#: ../C/gdm.xml:3405(para)
3863
msgid ""
3864
"Comma separated list of users to be included in the face browser and in the "
3865
"<command>gdmsetup</command> selection list for Automatic/Timed login. See "
3866
"also <filename>Exclude</filename>, <filename>IncludeAll</filename>, and "
3867
"<filename>MinimalUID</filename>."
3868
msgstr ""
3869
3870
#: ../C/gdm.xml:3417(term)
3871
msgid "Exclude"
3872
msgstr ""
3873
3874
#: ../C/gdm.xml:3419(synopsis)
3875
#, no-wrap
3876
msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..."
3877
msgstr ""
3878
3879
#: ../C/gdm.xml:3420(para)
3880
msgid ""
3881
"Comma separated list of users to be excluded from the face browser and from "
3882
"the <command>gdmsetup</command> selection list for Automatic/Timed login. "
3883
"Excluded users will still be able to log in, but will have to type their "
3884
"username. See also <filename>Include</filename>, <filename>IncludeAll</"
3885
"filename>, and <filename>MinimalUID</filename>."
3886
msgstr ""
3887
3888
#: ../C/gdm.xml:3433(term)
3889
msgid "IncludeAll"
3890
msgstr ""
3891
3892
#: ../C/gdm.xml:3435(synopsis)
3893
#, no-wrap
3894
msgid "IncludeAll=false"
3895
msgstr ""
3896
3897
#: ../C/gdm.xml:3436(para)
3898
msgid ""
3899
"By default, an empty include list means display no users. By setting "
3900
"IncludeAll to true, the password file will be scanned and all users will be "
3901
"displayed aside from users excluded via the Exclude setting and user ID's "
3902
"less than MinimalUID. Scanning the password file can be slow on systems with "
3903
"large numbers of users and this feature should not be used in such "
3904
"environments. See also <filename>Include</filename>, <filename>Exclude</"
3905
"filename>, and <filename>MinimalUID</filename>."
3906
msgstr ""
3907
3908
#: ../C/gdm.xml:3452(term)
3909
msgid "GlobalFaceDir"
3910
msgstr ""
3911
3912
#: ../C/gdm.xml:3454(synopsis)
3913
#, no-wrap
3914
msgid "GlobalFaceDir=<share>/pixmaps/faces/"
3915
msgstr ""
3916
3917
#: ../C/gdm.xml:3455(para)
3918
msgid ""
3919
"Systemwide directory for face files. The sysadmin can place icons for users "
3920
"here without touching their homedirs. Faces are named after their users' "
3921
"logins."
3922
msgstr ""
3923
3924
#: ../C/gdm.xml:3461(para)
3925
msgid ""
3926
"I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the "
3927
"face icon for the user ``johndoe''. No image format extension should be "
3928
"specified."
3929
msgstr ""
3930
3931
#: ../C/gdm.xml:3467(para)
3932
msgid ""
3933
"The face images must be stored in gdk-pixbuf supported formats and they must "
3934
"be readable for the GDM user."
3935
msgstr ""
3936
3937
#: ../C/gdm.xml:3472(para)
3938
msgid ""
3939
"A user's own icon file will always take precedence over the sysadmin "
3940
"provided one."
3941
msgstr ""
3942
3943
#: ../C/gdm.xml:3480(term)
3944
msgid "GraphicalTheme"
3945
msgstr ""
3946
3947
#: ../C/gdm.xml:3482(synopsis)
3948
#, no-wrap
3949
msgid "GraphicalTheme=circles"
3950
msgstr ""
3951
3952
#: ../C/gdm.xml:3483(para)
3953
msgid ""
3954
"The graphical theme that the Themed Greeter should use. it should refer to a "
3955
"directory in the theme directory set by <filename>GraphicalThemeDir</"
3956
"filename>."
3957
msgstr ""
3958
3959
#: ../C/gdm.xml:3492(term)
3960
msgid "GraphicalThemes"
3961
msgstr ""
3962
3963
#: ../C/gdm.xml:3494(synopsis)
3964
#, no-wrap
3965
msgid "GraphicalThemes=circles"
3966
msgstr ""
3967
3968
#: ../C/gdm.xml:3495(para)
3969
msgid ""
3970
"The graphical themes that the Themed Greeter should use is the Mode is set "
3971
"on Random Themes. This is a \"/:\" delimited list. It should refer to a "
3972
"directory in the theme directory set by <filename>GraphicalThemeDir</"
3973
"filename>. This is only used if <filename>GraphicalThemeRand</filename> is "
3974
"set to true."
3975
msgstr ""
3976
3977
#: ../C/gdm.xml:3507(term)
3978
msgid "GraphicalThemeRand"
3979
msgstr ""
3980
3981
#: ../C/gdm.xml:3509(synopsis)
3982
#, no-wrap
3983
msgid "GraphicalThemeRand=false"
3984
msgstr ""
3985
3986
#: ../C/gdm.xml:3510(para)
3987
msgid ""
3988
"Whether the graphical greeter will use Only One Theme or Random Theme mode. "
3989
"Only One Theme mode uses themes listed by <filename>GraphicalTheme</"
3990
"filename>, Random Themes mode uses themes listed by "
3991
"<filename>GraphicalThemes</filename>. A value of false sets greeter to use "
3992
"Only One Theme mode, a value of true sets the greeter to use Random Theme "
3993
"mode."
3994
msgstr ""
3995
3996
#: ../C/gdm.xml:3522(term)
3997
msgid "GraphicalThemeDir"
3998
msgstr ""
3999
4000
#: ../C/gdm.xml:3524(synopsis)
4001
#, no-wrap
4002
msgid "GraphicalThemeDir=<share>/gdm/themes/"
4003
msgstr ""
4004
4005
#: ../C/gdm.xml:3525(para)
4006
msgid "The directory where themes for the Themed Greeter are installed."
4007
msgstr ""
4008
4009
#: ../C/gdm.xml:3533(term)
4010
msgid "GraphicalThemedColor"
4011
msgstr ""
4012
4013
#: ../C/gdm.xml:3535(synopsis)
4014
#, no-wrap
4015
msgid "GraphicalThemedColor=#76848F"
4016
msgstr ""
4017
4018
#: ../C/gdm.xml:3536(para)
4019
msgid ""
4020
"Use this color in the background of the Themed Greeter. This only affects "
4021
"the Themed Greeter."
4022
msgstr ""
4023
4024
#: ../C/gdm.xml:3544(term)
4025
msgid "InfoMsgFile"
4026
msgstr ""
4027
4028
#: ../C/gdm.xml:3546(synopsis)
4029
#, no-wrap
4030
msgid "InfoMsgFile=/path/to/infofile"
4031
msgstr ""
4032
4033
#: ../C/gdm.xml:3547(para)
4034
msgid ""
4035
"If present and /path/to/infofile specifies an existing and readable text "
4036
"file (e.g. <etc>/infomsg.txt) the contents of the file will be "
4037
"displayed in a modal dialog box before the user is allowed to login. This "
4038
"works both with the standard and the themable greeters."
4039
msgstr ""
4040
4041
#: ../C/gdm.xml:3558(term)
4042
msgid "InfoMsgFont"
4043
msgstr ""
4044
4045
#: ../C/gdm.xml:3560(synopsis)
4046
#, no-wrap
4047
msgid "InfoMsgFont=fontspec"
4048
msgstr ""
4049
4050
#: ../C/gdm.xml:3561(para)
4051
msgid ""
4052
"If present and InfoMsgFile (see above) is used, this specifies the font to "
4053
"use when displaying the contents of the InfoMsgFile text file. For example "
4054
"fontspec could be Sans 24 to get a sans serif font of size 24 points. This "
4055
"works both with the standard and the themable greeters."
4056
msgstr ""
4057
4058
#: ../C/gdm.xml:3573(term)
4059
msgid "LocaleFile"
4060
msgstr ""
4061
4062
#: ../C/gdm.xml:3575(synopsis)
4063
#, no-wrap
4064
msgid "LocaleFile=<etc>/gdm/locale.alias"
4065
msgstr ""
4066
4067
#: ../C/gdm.xml:3576(para)
4068
msgid ""
4069
"File in format similar to the GNU locale format with entries for all "
4070
"supported languages on the system. The format is described above or in a "
4071
"comment inside that file."
4072
msgstr ""
4073
4074
#: ../C/gdm.xml:3585(term)
4075
msgid "LockPosition"
4076
msgstr ""
4077
4078
#: ../C/gdm.xml:3587(synopsis)
4079
#, no-wrap
4080
msgid "LockPosition=true"
4081
msgstr ""
4082
4083
#: ../C/gdm.xml:3588(para)
4084
msgid ""
4085
"If true the position of the login window of the GTK+ Greeter cannot be "
4086
"changed even if the title bar is turned on."
4087
msgstr ""
4088
4089
#: ../C/gdm.xml:3596(term)
4090
msgid "Logo"
4091
msgstr ""
4092
4093
#: ../C/gdm.xml:3598(synopsis)
4094
#, no-wrap
4095
msgid "Logo=<share>/pixmaps/gnome-logo-large.png"
4096
msgstr ""
4097
4098
#: ../C/gdm.xml:3599(para)
4099
msgid ""
4100
"Image file to display in the logo box. The file must be in a gdk-pixbuf "
4101
"supported format and it must be readable by the GDM user. If no file is "
4102
"specified the logo feature is disabled. This only affects the GTK+ Greeter."
4103
msgstr ""
4104
4105
#: ../C/gdm.xml:3610(term)
4106
msgid "ChooserButtonLogo"
4107
msgstr ""
4108
4109
#: ../C/gdm.xml:3612(synopsis)
4110
#, no-wrap
4111
msgid "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png"
4112
msgstr ""
4113
4114
#: ../C/gdm.xml:3613(para)
4115
msgid ""
4116
"Image file to display in the file chooser button in <command>gdmsetup</"
4117
"command>. This key is modified by <command>gdmsetup</command> and should not "
4118
"be manually modified by the user. This only affects the Login Window "
4119
"Preferences (<command>gdmsetup</command>)."
4120
msgstr ""
4121
4122
#: ../C/gdm.xml:3624(term)
4123
msgid "MinimalUID"
4124
msgstr ""
4125
4126
#: ../C/gdm.xml:3626(synopsis)
4127
#, no-wrap
4128
msgid "MinimalUID=100"
4129
msgstr ""
4130
4131
#: ../C/gdm.xml:3627(para)
4132
msgid ""
4133
"The minimal UID that GDM should consider a user. All users with a lower UID "
4134
"will be excluded from the face browser. See also <filename>Include</"
4135
"filename>, <filename>Exclude</filename>, and <filename>IncludeAll</filename>."
4136
msgstr ""
4137
4138
#: ../C/gdm.xml:3638(term)
4139
msgid "PositionX"
4140
msgstr ""
4141
4142
#: ../C/gdm.xml:3640(synopsis)
4143
#, no-wrap
4144
msgid "PositionX=200"
4145
msgstr ""
4146
4147
#: ../C/gdm.xml:3641(para)
4148
msgid "The horizontal position of the login window of the GTK+ Greeter."
4149
msgstr ""
4150
4151
#: ../C/gdm.xml:3649(term)
4152
msgid "PositionY"
4153
msgstr ""
4154
4155
#: ../C/gdm.xml:3651(synopsis)
4156
#, no-wrap
4157
msgid "PositionY=100"
4158
msgstr ""
4159
4160
#: ../C/gdm.xml:3652(para)
4161
msgid "The vertical position of the login window of the GTK+ Greeter."
4162
msgstr ""
4163
4164
#: ../C/gdm.xml:3660(term)
4165
msgid "Quiver"
4166
msgstr ""
4167
4168
#: ../C/gdm.xml:3662(synopsis)
4169
#, no-wrap
4170
msgid "Quiver=true"
4171
msgstr ""
4172
4173
#: ../C/gdm.xml:3663(para)
4174
msgid ""
4175
"Controls whether <command>gdmlogin</command> should shake the display when "
4176
"an incorrect username/password is entered. This only affects the GTK+ "
4177
"Greeter."
4178
msgstr ""
4179
4180
#: ../C/gdm.xml:3673(term)
4181
msgid "DefaultRemoteWelcome"
4182
msgstr ""
4183
4184
#: ../C/gdm.xml:3675(synopsis)
4185
#, no-wrap
4186
msgid "DefaultRemoteWelcome=true"
4187
msgstr ""
4188
4189
#: ../C/gdm.xml:3676(para)
4190
msgid ""
4191
"If set to true, the value \"Welcome to %n\" is used for the "
4192
"<filename>RemoteWelcome</filename>. This value is translated into the "
4193
"appropriate language for the user. If set to false, the "
4194
"<filename>RemoteWelcome</filename> setting is used. This string can use the "
4195
"same special character sequences as explained in the \"Text Node\" section "
4196
"of the \"Themed Greeter\" chapter. This explains the meaning of \"%n\"."
4197
msgstr ""
4198
4199
#: ../C/gdm.xml:3690(term)
4200
msgid "RemoteWelcome"
4201
msgstr ""
4202
4203
#: ../C/gdm.xml:3692(synopsis)
4204
#, no-wrap
4205
msgid "RemoteWelcome=Welcome to %n"
4206
msgstr ""
4207
4208
#: ../C/gdm.xml:3693(para)
4209
msgid ""
4210
"Controls which text to display next to the logo image in the greeter for "
4211
"remote XDMCP sessions. The same expansion is done here as in the "
4212
"<filename>Welcome</filename> string. This string can use the same special "
4213
"character sequences as explained in the \"Text Node\" section of the "
4214
"\"Themed Greeter\" chapter. chapter."
4215
msgstr ""
4216
4217
#: ../C/gdm.xml:3706(term)
4218
msgid "RunBackgroundProgramAlways"
4219
msgstr ""
4220
4221
#: ../C/gdm.xml:3708(synopsis)
4222
#, no-wrap
4223
msgid "RunBackgroundProgramAlways=false"
4224
msgstr ""
4225
4226
#: ../C/gdm.xml:3709(para)
4227
msgid ""
4228
"If this is true then the background application is run always, otherwise it "
4229
"is only run when the <filename>BackgroundType</filename> is 0 (None) This "
4230
"only affects the GTK+ Greeter."
4231
msgstr ""
4232
4233
#: ../C/gdm.xml:3719(term)
4234
msgid "SetPosition"
4235
msgstr ""
4236
4237
#: ../C/gdm.xml:3721(synopsis)
4238
#, no-wrap
4239
msgid "SetPosition=true"
4240
msgstr ""
4241
4242
#: ../C/gdm.xml:3722(para)
4243
msgid ""
4244
"If true the position of the login window of the GTK+ Greeter is determined "
4245
"by <filename>PositionX</filename> / <filename>PositionY</filename>."
4246
msgstr ""
4247
4248
#: ../C/gdm.xml:3731(term)
4249
msgid "ShowGnomeFailsafeSession"
4250
msgstr ""
4251
4252
#: ../C/gdm.xml:3733(synopsis)
4253
#, no-wrap
4254
msgid "ShowGnomeFailsafeSession=true"
4255
msgstr ""
4256
4257
#: ../C/gdm.xml:3734(para)
4258
msgid "Should the greeter show the Gnome Failsafe session in th sessions list."
4259
msgstr ""
4260
4261
#: ../C/gdm.xml:3742(term)
4262
msgid "ShowLastSession"
4263
msgstr ""
4264
4265
#: ../C/gdm.xml:3744(synopsis)
4266
#, no-wrap
4267
msgid "ShowLastSession=true"
4268
msgstr ""
4269
4270
#: ../C/gdm.xml:3745(para)
4271
msgid ""
4272
"Should the greeter show the 'Last' session in the session list. If this is "
4273
"off, then GDM is in the so called 'switchdesk' mode which for example Red "
4274
"Hat uses. That is, the users can't pick the last session and will just then "
4275
"get the default session (see <filename>DefaultSession</filename>) unless "
4276
"then pick something else for this session only. So if this is off, this "
4277
"really circumvents saving of the last session."
4278
msgstr ""
4279
4280
#: ../C/gdm.xml:3758(term)
4281
msgid "ShowXtermFailsafeSession"
4282
msgstr ""
4283
4284
#: ../C/gdm.xml:3760(synopsis)
4285
#, no-wrap
4286
msgid "ShowXtermFailsafeSession=true"
4287
msgstr ""
4288
4289
#: ../C/gdm.xml:3761(para)
4290
msgid "Should the greeter show the Xterm Failsafe session in the sessions list."
4291
msgstr ""
4292
4293
#: ../C/gdm.xml:3769(term)
4294
msgid "SoundOnLogin"
4295
msgstr ""
4296
4297
#: ../C/gdm.xml:3771(synopsis)
4298
#, no-wrap
4299
msgid "SoundOnLogin=true"
4300
msgstr ""
4301
4302
#: ../C/gdm.xml:3772(para)
4303
msgid ""
4304
"If true, the greeter will play a sound or beep when it is ready for a login. "
4305
"See also the <filename>SoundOnLoginFile</filename> key. Supported since "
4306
"2.5.90.0."
4307
msgstr ""
4308
4309
#: ../C/gdm.xml:3782(term)
4310
msgid "SoundOnLoginSuccess"
4311
msgstr ""
4312
4313
#: ../C/gdm.xml:3784(synopsis)
4314
#, no-wrap
4315
msgid "SoundOnLoginSuccess=true"
4316
msgstr ""
4317
4318
#: ../C/gdm.xml:3785(para)
4319
msgid ""
4320
"If true, the greeter will play a sound after a successful login attempt. See "
4321
"also the <filename>SoundOnLoginSuccessFile</filename> key."
4322
msgstr ""
4323
4324
#: ../C/gdm.xml:3794(term)
4325
msgid "SoundOnLoginFailure"
4326
msgstr ""
4327
4328
#: ../C/gdm.xml:3796(synopsis)
4329
#, no-wrap
4330
msgid "SoundOnLoginFailure=true"
4331
msgstr ""
4332
4333
#: ../C/gdm.xml:3797(para)
4334
msgid ""
4335
"If true, the greeter will play a sound after a failed login attempt. See "
4336
"also the <filename>SoundOnLoginFailureFile</filename> key."
4337
msgstr ""
4338
4339
#: ../C/gdm.xml:3806(term)
4340
msgid "SoundOnLoginFile"
4341
msgstr ""
4342
4343
#: ../C/gdm.xml:3808(synopsis)
4344
#, no-wrap
4345
msgid "SoundOnLoginFile=/path/to/sound.wav"
4346
msgstr ""
4347
4348
#: ../C/gdm.xml:3809(para)
4349
msgid ""
4350
"The file that will be played using the specified sound application (by "
4351
"default that is <filename>/usr/bin/play</filename>) instead of a beep when "
4352
"the greeter is ready for a login. See also the <filename>SoundOnLogin</"
4353
"filename> key and the <filename>SoundProgram</filename> key. Supported since "
4354
"2.5.90.0."
4355
msgstr ""
4356
4357
#: ../C/gdm.xml:3822(term)
4358
msgid "SoundOnLoginSuccessFile"
4359
msgstr ""
4360
4361
#: ../C/gdm.xml:3824(synopsis)
4362
#, no-wrap
4363
msgid "SoundOnLoginSuccessFile=/path/to/sound.wav"
4364
msgstr ""
4365
4366
#: ../C/gdm.xml:3825(para)
4367
msgid ""
4368
"The file that will be played using the specified sound application (by "
4369
"default that is <filename>/usr/bin/play</filename>) after a successful login "
4370
"attempt. See also the <filename>SoundOnLoginSuccess</filename> key and the "
4371
"<filename>SoundProgram</filename> key."
4372
msgstr ""
4373
4374
#: ../C/gdm.xml:3836(term)
4375
msgid "SoundOnLoginFailureFile"
4376
msgstr ""
4377
4378
#: ../C/gdm.xml:3838(synopsis)
4379
#, no-wrap
4380
msgid "SoundOnLoginFailureFile=/path/to/sound.wav"
4381
msgstr ""
4382
4383
#: ../C/gdm.xml:3839(para)
4384
msgid ""
4385
"The file that will be played using the specified sound application (by "
4386
"default that is <filename>/usr/bin/play</filename>) after a failed login "
4387
"attempt. See also the <filename>SoundOnLoginFailure</filename> key and the "
4388
"<filename>SoundProgram</filename> key."
4389
msgstr ""
4390
4391
#: ../C/gdm.xml:3850(term)
4392
msgid "SystemMenu"
4393
msgstr ""
4394
4395
#: ../C/gdm.xml:3852(synopsis)
4396
#, no-wrap
4397
msgid "SystemMenu=true"
4398
msgstr ""
4399
4400
#: ../C/gdm.xml:3853(para)
4401
msgid ""
4402
"Turns the Actions menu (which used to be called System menu) on or off. If "
4403
"this is off then one of the actions will be available anywhere. These "
4404
"actions include Shutdown, Restart, Configure, XDMCP chooser and such. All of "
4405
"those can however be turned off individually. Shutdown, Restart and Suspend "
4406
"can be turned off by just setting the corresponding keys to empty. Note that "
4407
"the actions menu is only shown on local logins as it would not be safe or "
4408
"even desirable on remote logins, so you don't have to worry about remote "
4409
"users having any sort of console privileges."
4410
msgstr ""
4411
4412
#: ../C/gdm.xml:3866(para)
4413
msgid ""
4414
"Note that if this is off none of the actions will be available even if a "
4415
"theme for a graphical greeter mistakenly shows them. Also note that "
4416
"sometimes a graphical theme may not show all the available actions as "
4417
"buttons and you may have to press F10 to see the menu."
4418
msgstr ""
4419
4420
#: ../C/gdm.xml:3877(term)
4421
msgid "TitleBar"
4422
msgstr ""
4423
4424
#: ../C/gdm.xml:3879(synopsis)
4425
#, no-wrap
4426
msgid "TitleBar=true"
4427
msgstr ""
4428
4429
#: ../C/gdm.xml:3880(para)
4430
msgid "Display the title bar in the greeter. This only affects the GTK+ Greeter."
4431
msgstr ""
4432
4433
#: ../C/gdm.xml:3888(term)
4434
msgid "Use24Clock"
4435
msgstr ""
4436
4437
#: ../C/gdm.xml:3890(synopsis)
4438
#, no-wrap
4439
msgid "Use24Clock=auto"
4440
msgstr ""
4441
4442
#: ../C/gdm.xml:3891(para)
4443
msgid ""
4444
"Select the use of 24 hour clock. Some locales do not support 12 hour format "
4445
"(like Finnish, that is <filename>fi_FI</filename>), and in those locales "
4446
"this setting has no effect at all."
4447
msgstr ""
4448
4449
#: ../C/gdm.xml:3897(para)
4450
msgid ""
4451
"Possible values are \"auto\" (default), \"true\", and \"false\". If this is "
4452
"set to \"auto\" or left empty, then time format is chosen from locale "
4453
"settings. Locale settings are based on the language in use, thus it is "
4454
"changed by setting environment variables LANGUAGE (GNU extension), LANG, "
4455
"LC_MESSAGES or LC_ALL in the GDM's runtime environment. Priorities between "
4456
"the mentioned environment variables can be found from your system's C "
4457
"library manual."
4458
msgstr ""
4459
4460
#: ../C/gdm.xml:3912(term)
4461
msgid "UseCirclesInEntry"
4462
msgstr ""
4463
4464
#: ../C/gdm.xml:3914(synopsis)
4465
#, no-wrap
4466
msgid "UseCirclesInEntry=false"
4467
msgstr ""
4468
4469
#: ../C/gdm.xml:3915(para)
4470
msgid ""
4471
"Use circles instead of asterisks in the password entry. This may not work "
4472
"with all fonts however."
4473
msgstr ""
4474
4475
#: ../C/gdm.xml:3923(term)
4476
msgid "UseInvisibleInEntry"
4477
msgstr ""
4478
4479
#: ../C/gdm.xml:3925(synopsis)
4480
#, no-wrap
4481
msgid "UseInvisibleInEntry=false"
4482
msgstr ""
4483
4484
#: ../C/gdm.xml:3926(para)
4485
msgid ""
4486
"Do not show any visual feedback is the password entry. This is the standard "
4487
"in console and xdm. Settings this option discards the "
4488
"<filename>UseCirclesInEntry</filename> option."
4489
msgstr ""
4490
4491
#: ../C/gdm.xml:3936(term)
4492
msgid "DefaultWelcome"
4493
msgstr ""
4494
4495
#: ../C/gdm.xml:3938(synopsis)
4496
#, no-wrap
4497
msgid "DefaultWelcome=true"
4498
msgstr ""
4499
4500
#: ../C/gdm.xml:3939(para)
4501
msgid ""
4502
"If set to true, the value \"Welcome\" is used for the <filename>Welcome</"
4503
"filename>. This value is translated into the appropriate language for the "
4504
"user. If set to false, the <filename>Welcome</filename> setting is used."
4505
msgstr ""
4506
4507
#: ../C/gdm.xml:3949(term)
4508
msgid "Welcome"
4509
msgstr ""
4510
4511
#: ../C/gdm.xml:3951(synopsis)
4512
#, no-wrap
4513
msgid "Welcome=Welcome"
4514
msgstr ""
4515
4516
#: ../C/gdm.xml:3952(para)
4517
msgid ""
4518
"Controls which text to display next to the logo image in the standard "
4519
"greeter. The following control chars are supported:"
4520
msgstr ""
4521
4522
#: ../C/gdm.xml:3961(para)
4523
msgid "%d — display's hostname"
4524
msgstr ""
4525
4526
#: ../C/gdm.xml:3965(para)
4527
msgid "%h — Fully qualified hostname"
4528
msgstr ""
4529
4530
#: ../C/gdm.xml:3969(para)
4531
msgid "%m — machine (processor type)"
4532
msgstr ""
4533
4534
#: ../C/gdm.xml:3973(para)
4535
msgid "%n — Nodename (i.e. hostname without .domain)"
4536
msgstr ""
4537
4538
#: ../C/gdm.xml:3977(para)
4539
msgid "%r — release (OS version)"
4540
msgstr ""
4541
4542
#: ../C/gdm.xml:3981(para)
4543
msgid "%s — sysname (i.e. OS)"
4544
msgstr ""
4545
4546
#: ../C/gdm.xml:3985(para)
4547
msgid ""
4548
"This string is only used for local logins. For remote XDMCP logins we use "
4549
"<filename>RemoteWelcome</filename>."
4550
msgstr ""
4551
4552
#: ../C/gdm.xml:3990(para)
4553
msgid ""
4554
"In the Themed Greeter the location of this text depends on the theme. Unless "
4555
"the theme uses the stock welcome string somewhere this string will not be "
4556
"displayed at all."
4557
msgstr ""
4558
4559
#: ../C/gdm.xml:4000(term)
4560
msgid "XineramaScreen"
4561
msgstr ""
4562
4563
#: ../C/gdm.xml:4002(synopsis)
4564
#, no-wrap
4565
msgid "XineramaScreen=0"
4566
msgstr ""
4567
4568
#: ../C/gdm.xml:4003(para)
4569
msgid ""
4570
"If the Xinerama extension is active the login window will be centered on "
4571
"this physical screen (use 0 for the first screen, 1 for the second...)."
4572
msgstr ""
4573
4574
#: ../C/gdm.xml:4014(title)
4575
msgid "XDCMP Chooser Options"
4576
msgstr ""
4577
4578
#: ../C/gdm.xml:4017(title)
4579
msgid "[chooser]"
4580
msgstr ""
4581
4582
#: ../C/gdm.xml:4020(term)
4583
msgid "AllowAdd"
4584
msgstr ""
4585
4586
#: ../C/gdm.xml:4022(synopsis)
4587
#, no-wrap
4588
msgid "AllowAdd=true"
4589
msgstr ""
4590
4591
#: ../C/gdm.xml:4023(para)
4592
msgid ""
4593
"If true, allow the user to add arbitrary hosts to the chooser. This way the "
4594
"user could connect to any host that responds to XDMCP queries from the "
4595
"chooser."
4596
msgstr ""
4597
4598
#: ../C/gdm.xml:4032(term)
4599
msgid "Broadcast"
4600
msgstr ""
4601
4602
#: ../C/gdm.xml:4034(synopsis)
4603
#, no-wrap
4604
msgid "Broadcast=true"
4605
msgstr ""
4606
4607
#: ../C/gdm.xml:4035(para)
4608
msgid ""
4609
"If true, the chooser will broadcast a query to the local network and collect "
4610
"responses. This way the chooser will always show all available managers on "
4611
"the network. If you need to add some hosts not local to this network, or if "
4612
"you don't want to use a broadcast, you can list them explicitly in the "
4613
"<filename>Hosts</filename> key."
4614
msgstr ""
4615
4616
#: ../C/gdm.xml:4047(term)
4617
msgid "Multicast"
4618
msgstr ""
4619
4620
#: ../C/gdm.xml:4049(synopsis)
4621
#, no-wrap
4622
msgid "Multicast=true"
4623
msgstr ""
4624
4625
#: ../C/gdm.xml:4050(para)
4626
msgid ""
4627
"If true and IPv6 is enabled, the chooser will send a multicast query to the "
4628
"local network and collect responses from the hosts who have joined multicast "
4629
"group. If you don't want to send a multicast, you can specify IPv6 address "
4630
"in the <filename>Hosts </filename> key. The host will respond if it is "
4631
"listening to XDMCP requests and IPv6 is enabled there."
4632
msgstr ""
4633
4634
#: ../C/gdm.xml:4062(term)
4635
msgid "MulticastAddr"
4636
msgstr ""
4637
4638
#: ../C/gdm.xml:4064(synopsis)
4639
#, no-wrap
4640
msgid "MulticastAddr=ff02::1"
4641
msgstr ""
4642
4643
#: ../C/gdm.xml:4065(para)
4644
msgid "This is the Link-local Multicast address and is hardcoded here."
4645
msgstr ""
4646
4647
#: ../C/gdm.xml:4072(term)
4648
msgid "DefaultHostImage"
4649
msgstr ""
4650
4651
#: ../C/gdm.xml:4074(synopsis)
4652
#, no-wrap
4653
msgid "DefaultHostImage=<share>/pixmaps/nohost.png"
4654
msgstr ""
4655
4656
#: ../C/gdm.xml:4075(para)
4657
msgid ""
4658
"File name for the default host icon. This image will be displayed if no icon "
4659
"is specified for a given host. The file must be in a gdk-pixbuf supported "
4660
"format and it must be readable for the GDM user."
4661
msgstr ""
4662
4663
#: ../C/gdm.xml:4085(term)
4664
msgid "HostImageDir"
4665
msgstr ""
4666
4667
#: ../C/gdm.xml:4087(synopsis)
4668
#, no-wrap
4669
msgid "HostImageDir=<share>/hosts"
4670
msgstr ""
4671
4672
#: ../C/gdm.xml:4088(para)
4673
msgid ""
4674
"Repository for host icon files. The sysadmin can place icons for remote "
4675
"hosts here and they will appear in <filename>gdmchooser</filename>."
4676
msgstr ""
4677
4678
#: ../C/gdm.xml:4094(para)
4679
msgid ""
4680
"The file name must match the fully qualified name (FQDN) for the host. The "
4681
"icons must be stored in gdk-pixbuf supported formats and they must be "
4682
"readable to the GDM user."
4683
msgstr ""
4684
4685
#: ../C/gdm.xml:4104(term)
4686
msgid "Hosts"
4687
msgstr ""
4688
4689
#: ../C/gdm.xml:4106(synopsis)
4690
#, no-wrap
4691
msgid "Hosts=host1,host2"
4692
msgstr ""
4693
4694
#: ../C/gdm.xml:4107(para)
4695
msgid ""
4696
"The hosts which should be listed in the chooser. The chooser will only list "
4697
"them if they respond. This is done in addition to broadcast (if "
4698
"<filename>Broadcast</filename> is set), so you need not list hosts on the "
4699
"local network. This is useful if your networking setup doesn't allow all "
4700
"hosts to be reachable by a broadcast packet."
4701
msgstr ""
4702
4703
#: ../C/gdm.xml:4119(term)
4704
msgid "ScanTime"
4705
msgstr ""
4706
4707
#: ../C/gdm.xml:4121(synopsis)
4708
#, no-wrap
4709
msgid "ScanTime=4"
4710
msgstr ""
4711
4712
#: ../C/gdm.xml:4122(para)
4713
msgid ""
4714
"Specifies how many seconds the chooser should wait for replies to its "
4715
"BROADCAST_QUERY. Really this is only the time in which we expect a reply. We "
4716
"will still add hosts to the list even if they reply after this time."
4717
msgstr ""
4718
4719
#: ../C/gdm.xml:4134(title)
4720
msgid "Debug Configuration"
4721
msgstr ""
4722
4723
#: ../C/gdm.xml:4137(title)
4724
msgid "[debug]"
4725
msgstr ""
4726
4727
#: ../C/gdm.xml:4143(para)
4728
msgid ""
4729
"Setting to true sends debug ouput to the syslog. This can be useful for "
4730
"tracking down problems with GDM. This output tends to be verbose so should "
4731
"not be turned on for general use."
4732
msgstr ""
4733
4734
#: ../C/gdm.xml:4153(term)
4735
msgid "Gestures"
4736
msgstr ""
4737
4738
#: ../C/gdm.xml:4155(synopsis)
4739
#, no-wrap
4740
msgid "Gestures=false"
4741
msgstr ""
4742
4743
#: ../C/gdm.xml:4156(para)
4744
msgid ""
4745
"Setting to true sends debug ouput concerning the accessibility gesture "
4746
"listeners to the syslog. This can be useful for tracking down problems with "
4747
"them not working properly. This output tends to be verbose so should not be "
4748
"turned on for general use."
4749
msgstr ""
4750
4751
#: ../C/gdm.xml:4169(title)
4752
msgid "Custom Commands"
4753
msgstr ""
4754
4755
#: ../C/gdm.xml:4171(para)
4756
msgid ""
4757
"You can create up to 10 different commands. Gaps between command numbers are "
4758
"allowed and their relative positioning within the section and with respect "
4759
"to each other is not important as long as they conform to the permitted "
4760
"range of [0-9]."
4761
msgstr ""
4762
4763
#: ../C/gdm.xml:4180(title)
4764
msgid "[customcommand]"
4765
msgstr ""
4766
4767
#: ../C/gdm.xml:4183(term)
4768
msgid "CustomCommand[0-9]"
4769
msgstr ""
4770
4771
#: ../C/gdm.xml:4185(synopsis)
4772
#, no-wrap
4773
msgid "CustomCommand[0-9]="
4774
msgstr ""
4775
4776
#: ../C/gdm.xml:4186(para)
4777
msgid ""
4778
"Full path and arguments to command to be executed when user selects "
4779
"<filename>n-th</filename> \"Custom Command\" from the Actions menu. This can "
4780
"be a ';' separated list of commands to try. If the value is empty or "
4781
"missing, then the custom command is not available. By default this value is "
4782
"not enabled, so to enable \"Custom Command\" it must be set to a nonempty "
4783
"value. [0-9] represents the <filename>CustomCommand</filename> suffix and "
4784
"can be an integer between 0 and 9."
4785
msgstr ""
4786
4787
#: ../C/gdm.xml:4201(term)
4788
msgid "CustomCommandIsPersistent[0-9]"
4789
msgstr ""
4790
4791
#: ../C/gdm.xml:4203(synopsis)
4792
#, no-wrap
4793
msgid "CustomCommandIsPersistent[0-9]="
4794
msgstr ""
4795
4796
#: ../C/gdm.xml:4204(para)
4797
msgid ""
4798
"Specifies if <filename>n-th</filename> \"Custom Command\" will appear "
4799
"outside the login manager, for example on the desktop through the Log Out/"
4800
"Shut Down dialogs. If not specified the default value is \"false\". This "
4801
"option is only valid if corresponding <filename>CustomCommand</filename> is "
4802
"defined. [0-9] represents <filename>CustomCommand</filename> suffix and can "
4803
"be an integer between 0 and 9."
4804
msgstr ""
4805
4806
#: ../C/gdm.xml:4218(term)
4807
msgid "CustomCommandLabel[0-9]"
4808
msgstr ""
4809
4810
#: ../C/gdm.xml:4220(synopsis)
4811
#, no-wrap
4812
msgid "CustomCommandLabel[0-9]="
4813
msgstr ""
4814
4815
#: ../C/gdm.xml:4221(para)
4816
msgid ""
4817
"Specifies the stock label that will be displayed on the <filename>n-th</"
4818
"filename> \"Custom Command\" buttons and menu items. If not specified the "
4819
"default value is \"Custom_[0-9]\". This option is only valid if "
4820
"corresponding <filename>CustomCommand</filename> is defined. [0-9] "
4821
"represents <filename>CustomCommand</filename> suffix and can be an integer "
4822
"between 0 and 9. This option can't contain any semicolon characters (i.e. \";"
4823
"\")."
4824
msgstr ""
4825
4826
#: ../C/gdm.xml:4235(term)
4827
msgid "CustomCommandLRLabel[0-9]"
4828
msgstr ""
4829
4830
#: ../C/gdm.xml:4237(synopsis)
4831
#, no-wrap
4832
msgid "CustomCommandLRLabel[0-9]="
4833
msgstr ""
4834
4835
#: ../C/gdm.xml:4238(para)
4836
msgid ""
4837
"Specifies the stock label that will be displayed on the <filename>n-th</"
4838
"filename> \"Custom Command\" list items and radio buttons. If not specified "
4839
"the default value is \"Execute custom command _[0-9]\". This option is only "
4840
"valid if corresponding <filename>CustomCommand</filename> is defined. [0-9] "
4841
"represents <filename>CustomCommand</filename> suffix and can be an integer "
4842
"between 0 and 9."
4843
msgstr ""
4844
4845
#: ../C/gdm.xml:4252(term)
4846
msgid "CustomCommandNoRestart[0-9]"
4847
msgstr ""
4848
4849
#: ../C/gdm.xml:4254(synopsis)
4850
#, no-wrap
4851
msgid "CustomCommandNoRestart[0-9]="
4852
msgstr ""
4853
4854
#: ../C/gdm.xml:4255(para)
4855
msgid ""
4856
"Specifies if gdm will be stopped/restarted once <filename>n-th</filename> "
4857
"\"Custom Command\" has been executed. If not specified the default value is "
4858
"\"false\". This option is only valid if corresponding "
4859
"<filename>CustomCommand</filename> is defined. [0-9] represents "
4860
"<filename>CustomCommand</filename> suffix and can be an integer between 0 "
4861
"and 9. In addition when corresponding <filename>CustomCommandIsPersistent</"
4862
"filename> is set to true, setting CustomCommandNoRestart to false will place "
4863
"corresponding <filename>CustomCommand</filename> in the Shut Down dialog set "
4864
"of actions, setting it to true will place corresponding "
4865
"<filename>CustomCommand</filename> in the Log Out dialog set of actions."
4866
msgstr ""
4867
4868
#: ../C/gdm.xml:4275(term)
4869
msgid "CustomCommandText[0-9]"
4870
msgstr ""
4871
4872
#: ../C/gdm.xml:4277(synopsis)
4873
#, no-wrap
4874
msgid "CustomCommandText[0-9]="
4875
msgstr ""
4876
4877
#: ../C/gdm.xml:4278(para)
4878
msgid ""
4879
"Specifies the message that will be displayed on the warning dialog box once "
4880
"<filename>n-th</filename> \"Custom Command\" button/menu item/radio button/"
4881
"list item has been activated. If not specified the default value is \"Are "
4882
"you sure?\". This option is only valid if corresponding "
4883
"<filename>CustomCommand</filename> is defined. [0-9] represents "
4884
"<filename>CustomCommand</filename> suffix and can be an integer between 0 "
4885
"and 9."
4886
msgstr ""
4887
4888
#: ../C/gdm.xml:4292(term)
4889
msgid "CustomCommandTooltip[0-9]"
4890
msgstr ""
4891
4892
#: ../C/gdm.xml:4294(synopsis)
4893
#, no-wrap
4894
msgid "CustomCommandTooltip[0-9]="
4895
msgstr ""
4896
4897
#: ../C/gdm.xml:4295(para)
4898
msgid ""
4899
"Specifies the message that will be displayed on tooltips for <filename>n-th</"
4900
"filename> \"Custom Command\" entries. If not specified the default value is "
4901
"\"Execute custom command [0-9]\". This option is only valid if corresponding "
4902
"<filename>CustomCommand</filename> is defined. [0-9] represents "
4903
"<filename>CustomCommand</filename> suffix and can be an integer between 0 "
4904
"and 9."
4905
msgstr ""
4906
4907
#: ../C/gdm.xml:4310(title)
4908
msgid "X Server Definitions"
4909
msgstr ""
4910
4911
#: ../C/gdm.xml:4312(para)
4912
msgid ""
4913
"To set up X servers, you need to provide GDM with information about the "
4914
"installed X servers. You can have as many different definitions as you wish, "
4915
"each identified with a unique name. The name <filename>Standard</filename> "
4916
"is required. If you do not specify this server, GDM will assume default "
4917
"values for a 'Standard' server and the path given by <filename>daemon/"
4918
"StandardXServer</filename>. <filename>Standard</filename> is used as the "
4919
"default, in situations when no other server has been defined."
4920
msgstr ""
4921
4922
#: ../C/gdm.xml:4323(para)
4923
msgid ""
4924
"Servers are defined by sections named <filename>server-</filename> followed "
4925
"by the identifier of this server. This should be a simple ASCII string with "
4926
"no spaces. The GUI configuration program allows users to edit the servers "
4927
"defined in the GDM configuration files but currently does not allow adding "
4928
"or deleting entries. Like normal configuration options, <filename>server-</"
4929
"filename> sections in the GDM Custom Configuration File override values in "
4930
"the GDM System Defaults Configuration File. In other words, if a "
4931
"<filename>server-Standard</filename> section is defined in the GDM Custom "
4932
"Configuration File, then that will be used and the section in the GDM System "
4933
"Defaults Configuration File will be ignored."
4934
msgstr ""
4935
4936
#: ../C/gdm.xml:4338(title)
4937
msgid "[server-Standard]"
4938
msgstr ""
4939
4940
#: ../C/gdm.xml:4341(term)
4941
msgid "name"
4942
msgstr ""
4943
4944
#: ../C/gdm.xml:4343(synopsis)
4945
#, no-wrap
4946
msgid "name=Standard server"
4947
msgstr ""
4948
4949
#: ../C/gdm.xml:4344(para)
4950
msgid "The name that will be displayed to the user."
4951
msgstr ""
4952
4953
#: ../C/gdm.xml:4351(term)
4954
msgid "command"
4955
msgstr ""
4956
4957
#: ../C/gdm.xml:4353(synopsis)
4958
#, no-wrap
4959
msgid "command=/path/to/X"
4960
msgstr ""
4961
4962
#: ../C/gdm.xml:4354(para)
4963
msgid ""
4964
"The command to execute, with full path to the binary of the X server, and "
4965
"any extra arguments needed."
4966
msgstr ""
4967
4968
#: ../C/gdm.xml:4362(term)
4969
msgid "flexible"
4970
msgstr ""
4971
4972
#: ../C/gdm.xml:4364(synopsis)
4973
#, no-wrap
4974
msgid "flexible=true"
4975
msgstr ""
4976
4977
#: ../C/gdm.xml:4365(para)
4978
msgid ""
4979
"Indicates if this server is available as a choice when a user wishes to run "
4980
"a flexible, on demand server."
4981
msgstr ""
4982
4983
#: ../C/gdm.xml:4373(term)
4984
msgid "handled"
4985
msgstr ""
4986
4987
#: ../C/gdm.xml:4375(synopsis)
4988
#, no-wrap
4989
msgid "handled=true"
4990
msgstr ""
4991
4992
#: ../C/gdm.xml:4376(para)
4993
msgid ""
4994
"Indicates that GDM should run the login window on this server and allow a "
4995
"user to log in. If set to false, then GDM will just run this server and wait "
4996
"for it to terminate. This can be useful to run an X terminal using GDM. When "
4997
"this is done you should normally also add <filename>-terminate</filename> to "
4998
"the command line of the server to make the server terminate after each "
4999
"session. Otherwise the control of the slave will never come back to GDM and, "
5000
"for example, soft restarts won't work. This is because GDM assumes there is "
5001
"a login in progress for the entire time this server is active."
5002
msgstr ""
5003
5004
#: ../C/gdm.xml:4392(term)
5005
msgid "chooser"
5006
msgstr ""
5007
5008
#: ../C/gdm.xml:4394(synopsis)
5009
#, no-wrap
5010
msgid "chooser=false"
5011
msgstr ""
5012
5013
#: ../C/gdm.xml:4395(para)
5014
msgid ""
5015
"Indicates that GDM should instead of a login window run a chooser on this "
5016
"window and allow the user to choose which server to log into."
5017
msgstr ""
5018
5019
#: ../C/gdm.xml:4406(title)
5020
msgid "Local Static X Display Configuration"
5021
msgstr ""
5022
5023
#: ../C/gdm.xml:4408(para)
5024
msgid ""
5025
"The static display configuration specifies what displays should be always "
5026
"managed by GDM. GDM will restart the X server on the display if it dies, for "
5027
"example. There may be as many static displays that are managed as you wish, "
5028
"although typically each display is associated with a real display. For "
5029
"example, if a machine has two displays (say display \":0\" and display \":1"
5030
"\"), then this section can be used to specify that a separate login screen "
5031
"be managed for each screen. Each key in the <filename>[servers]</filename> "
5032
"section corresponds to the display number to be managed. Normally there is "
5033
"only one key, which is the key <filename>0</filename>, which corresponds to "
5034
"the display <filename>:0</filename>."
5035
msgstr ""
5036
5037
#: ../C/gdm.xml:4423(para)
5038
msgid ""
5039
"The GUI configuration program allows users to edit the static display "
5040
"configuration defined in the GDM configuration files and allows the user to "
5041
"add or delete entries. Like normal configuration options, the <filename>"
5042
"[servers]</filename> section in the GDM Custom Configuration File overrides "
5043
"values in the GDM System Defaults Configuration File."
5044
msgstr ""
5045
5046
#: ../C/gdm.xml:4433(title)
5047
msgid "[servers]"
5048
msgstr ""
5049
5050
#: ../C/gdm.xml:4436(term)
5051
msgid "<display number>"
5052
msgstr ""
5053
5054
#: ../C/gdm.xml:4438(synopsis)
5055
#, no-wrap
5056
msgid "0=Standard"
5057
msgstr ""
5058
5059
#: ../C/gdm.xml:4439(para)
5060
msgid ""
5061
"Control section for local displays. Each line indicates the local display "
5062
"number and the command that needs to be run to start the X server(s)."
5063
msgstr ""
5064
5065
#: ../C/gdm.xml:4445(para)
5066
msgid ""
5067
"The command can either be a path to an X executable, or a name of one of the "
5068
"server definitions. This can be followed by some arguments that should be "
5069
"passed to the X server when executed. The gdm daemon doesn't enforce the "
5070
"numbers to be in order or for them to be \"packed\". They keyword \"inactive"
5071
"\" can be used instead of a command to specify that the display should be "
5072
"not managed. This can be used in the GDM Custom Configuration File to turn "
5073
"off a display that is defined in the GDM System Defaults Configuration File."
5074
msgstr ""
5075
5076
#: ../C/gdm.xml:4458(para)
5077
msgid ""
5078
"GDM will splice \"<filename>-auth <ServAuthDir>/:n.Xauth :n</filename>"
5079
"\", where n is the display number. Inside the command line before all other "
5080
"arguments before running the X server."
5081
msgstr ""
5082
5083
#: ../C/gdm.xml:4465(para)
5084
msgid ""
5085
"On some systems it is necessary for GDM to know on which virtual consoles to "
5086
"run the X server. In this case, (if running XFree86) add \"vt7\" to the "
5087
"command line, for example, to run on virtual console 7. However on Linux and "
5088
"FreeBSD this is normally done automatically if the <filename>VTAllocation</"
5089
"filename> key is set."
5090
msgstr ""
5091
5092
#: ../C/gdm.xml:4474(para)
5093
msgid ""
5094
"Normally you do not need to add a <filename>-nolisten tcp</filename> flag as "
5095
"this is added automatically for local X servers when the "
5096
"<filename>DisallowTCP</filename> option is set."
5097
msgstr ""
5098
5099
#: ../C/gdm.xml:4484(term)
5100
msgid "priority"
5101
msgstr ""
5102
5103
#: ../C/gdm.xml:4486(synopsis)
5104
#, no-wrap
5105
msgid "priority=0"
5106
msgstr ""
5107
5108
#: ../C/gdm.xml:4487(para)
5109
msgid ""
5110
"Indicates that the X server should be started at a different process "
5111
"priority. Values can be any integer value accepted by the setpriority C "
5112
"library function (normally between -20 and 20) with 0 being the default. For "
5113
"highly interactive applications, -5 yields good responsiveness. The default "
5114
"value is 0 and the setpriority function is not called if the value is 0."
5115
msgstr ""
5116
5117
#: ../C/gdm.xml:4503(title)
5118
msgid "Per User Configuration"
5119
msgstr ""
5120
5121
#: ../C/gdm.xml:4505(para)
5122
msgid ""
5123
"There are some per user configuration settings that control how GDM behaves. "
5124
"GDM is picky about the file ownership and permissions of the user files it "
5125
"will access, and will ignore files if they are not owned by the user or "
5126
"files that have group/world write permission. It will also ignore the user "
5127
"if the user's $HOME directory is not owned by the user or if the user's "
5128
"$HOME directory has group/world write permission. files must also be smaller "
5129
"than the <filename>UserMaxFile</filename> value as defined in the GDM "
5130
"configuration. If it seems that GDM is not properly accessing user "
5131
"configuration settings, the problem is most likely caused by one of these "
5132
"checks failing."
5133
msgstr ""
5134
5135
#: ../C/gdm.xml:4519(para)
5136
msgid ""
5137
"First there is the <filename>~/.dmrc</filename> file. In theory this file "
5138
"should be shared between GDM and KDM, so users only have to configure things "
5139
"once. This is a standard <filename>.ini</filename> style configuration file. "
5140
"It has one section called <filename>[Desktop]</filename> which has two keys: "
5141
"<filename>Session</filename> and <filename>Language</filename>."
5142
msgstr ""
5143
5144
#: ../C/gdm.xml:4528(para)
5145
msgid ""
5146
"The <filename>Session</filename> key specifies the basename of the session "
5147
"<filename>.desktop</filename> file that the user wishes to normally use "
5148
"(without the <filename>.desktop</filename> extension, in other words). The "
5149
"<filename>Language</filename> key specifies the language that the user "
5150
"wishes to use by default. If either of these keys is missing, the system "
5151
"default is used. The file would normally look as follows:"
5152
msgstr ""
5153
5154
#: ../C/gdm.xml:4538(screen)
5155
#, no-wrap
5156
msgid ""
5157
"\n"
5158
"[Desktop]\n"
5159
"Session=gnome\n"
5160
"Language=cs_CZ.UTF-8\n"
5161
msgstr ""
5162
5163
#: ../C/gdm.xml:4544(para)
5164
msgid ""
5165
"Normally GDM will write this file when the user logs in for the first time, "
5166
"and rewrite it if the user chooses to change their default values on a "
5167
"subsequent login."
5168
msgstr ""
5169
5170
#: ../C/gdm.xml:4550(para)
5171
msgid ""
5172
"If the GDM Face Browser is turned on, then the file <filename>$HOME/.face</"
5173
"filename> is accessed. This file should be a standard image that GTK+ can "
5174
"read, such as PNG or JPEG. It also must be smaller than the "
5175
"<filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> "
5176
"values defined in the GDM configuration or it will be ignored. Users can run "
5177
"the <command>gdmphotosetup</command> program to specify a face image and it "
5178
"will copy the file to the <filename>$HOME/.face</filename> location and "
5179
"scale it so its longest dimension is not larger than the "
5180
"<filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> "
5181
"values. <command>gdmphotosetup</command> takes care to not change the aspect "
5182
"ratio of the image."
5183
msgstr ""
5184
5185
#: ../C/gdm.xml:4565(para)
5186
msgid ""
5187
"Face images can also be placed in the global face directory, which is "
5188
"specified by the <filename>GlobalFaceDir</filename> configuration option "
5189
"( normally <filename><share>/pixmaps/faces/</filename>) and the "
5190
"filename should be the name of the user, optionally with a <filename>.png</"
5191
"filename>, <filename>.jpg</filename>, etc. appended."
5192
msgstr ""
5193
5194
#: ../C/gdm.xml:4576(title)
5195
msgid "Controlling GDM"
5196
msgstr ""
5197
5198
#: ../C/gdm.xml:4578(para)
5199
msgid ""
5200
"You can control GDM behavior during runtime in several different ways. You "
5201
"can either run certain commands, or you can talk to GDM using either a unix "
5202
"socket protocol, or a FIFO protocol."
5203
msgstr ""
5204
5205
#: ../C/gdm.xml:4585(title)
5206
msgid "Commands"
5207
msgstr ""
5208
5209
#: ../C/gdm.xml:4587(para)
5210
msgid ""
5211
"To stop GDM, you can either send the TERM signal to the main daemon or run "
5212
"the <command>gdm-stop</command> command which is in the <filename><"
5213
"sbin>/</filename> directory. To restart GDM, you can either send the HUP "
5214
"signal to the main daemon or run the <command>gdm-restart</command> command "
5215
"which is also in the <filename><sbin>/</filename> directory. To "
5216
"restart GDM but only after all the users have logged out, you can either "
5217
"send the USR1 signal to the main daemon or run the <command>gdm-safe-"
5218
"restart</command> command which is in the <filename><sbin>/</filename> "
5219
"directory as well."
5220
msgstr ""
5221
5222
#: ../C/gdm.xml:4600(para)
5223
msgid ""
5224
"The <command>gdmflexiserver</command> command can be used to start new "
5225
"flexible (on demand) displays if your system supports virtual terminals. "
5226
"This command will normally lock the current session with a screensaver so "
5227
"that the user can safely walk away from the computer and let someone else "
5228
"log in. If more that two flexible displays have started "
5229
"<command>gdmflexiserver</command> will display a pop-up dialog allowing the "
5230
"user to select which session to continue. The user will normally have to "
5231
"enter a password to return to the session. On session exit the system will "
5232
"return to the previous virtual terminal. Run <command>gdmflexiserver --help</"
5233
"command> to get a listing of possible options."
5234
msgstr ""
5235
5236
#: ../C/gdm.xml:4616(title)
5237
msgid "The FIFO protocol"
5238
msgstr ""
5239
5240
#: ../C/gdm.xml:4618(para)
5241
msgid ""
5242
"GDM also provides a FIFO called <filename>.gdmfifo</filename> in the "
5243
"<filename>ServAuthDir</filename> directory (usually <filename><var>/"
5244
"gdm/.gdmfifo</filename>). You must be root to use this protocol, and it is "
5245
"mostly used for internal GDM chatter. It is a very simple protocol where you "
5246
"just echo a command on a single line to this file. It can be used to tell "
5247
"GDM things such as restart, suspend the computer, or restart all X servers "
5248
"next time it has a chance (which would be useful from an X configuration "
5249
"application)."
5250
msgstr ""
5251
5252
#: ../C/gdm.xml:4629(para)
5253
msgid ""
5254
"Full and up to date documentation of the commands and their use is contained "
5255
"in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look "
5256
"for the defines starting with <filename>GDM_SOP_</filename>. The commands "
5257
"which require the pid of the slave as an argument are the ones that are "
5258
"really used for internal communication of the slave with the master and "
5259
"should not be used."
5260
msgstr ""
5261
5262
#: ../C/gdm.xml:4641(title)
5263
msgid "Socket Protocol"
5264
msgstr ""
5265
5266
#: ../C/gdm.xml:4643(para)
5267
msgid ""
5268
"GDM provides a unix domain socket for communication at <filename>/tmp/."
5269
"gdm_socket</filename>. Using this you can check if GDM is running, the "
5270
"version of the daemon, the current displays that are running and who is "
5271
"logged in on them, and if GDM supports it on your operating system, also the "
5272
"virtual terminals of all the console logins. The <command>gdmflexiserver</"
5273
"command> command uses this protocol, for example, to launch flexible (on-"
5274
"demand) displays."
5275
msgstr ""
5276
5277
#: ../C/gdm.xml:4653(para)
5278
msgid "gdmflexiserver accepts the following commands with the --command option:"
5279
msgstr ""
5280
5281
#: ../C/gdm.xml:4658(screen)
5282
#, no-wrap
5283
msgid ""
5284
"\n"
5285
"ADD_DYNAMIC_DISPLAY\n"
5286
"ALL_SERVERS\n"
5287
"ATTACHED_SERVERS\n"
5288
"AUTH_LOCAL\n"
5289
"CLOSE\n"
5290
"FLEXI_XNEST\n"
5291
"FLEXI_XNEST_USER\n"
5292
"FLEXI_XSERVER\n"
5293
"FLEXI_XSERVER_USER\n"
5294
"GET_CONFIG\n"
5295
"GET_CONFIG_FILE\n"
5296
"GET_CUSTOM_CONFIG_FILE\n"
5297
"GET_SERVER_LIST\n"
5298
"GET_SERVER_DETAILS\n"
5299
"GREETERPIDS\n"
5300
"QUERY_LOGOUT_ACTION\n"
5301
"QUERY_CUSTOM_CMD_LABELS\n"
5302
"QUERY_CUSTOM_CMD_NO_RESTART_STATUS\n"
5303
"QUERY_VT\n"
5304
"RELEASE_DYNAMIC_DISPLAYS\n"
5305
"REMOVE_DYNAMIC_DISPLAY\n"
5306
"SERVER_BUSY\n"
5307
"SET_LOGOUT_ACTION\n"
5308
"SET_SAFE_LOGOUT_ACTION\n"
5309
"SET_VT\n"
5310
"UPDATE_CONFIG\n"
5311
"VERSION\n"
5312
msgstr ""
5313
5314
#: ../C/gdm.xml:4688(para)
5315
msgid ""
5316
"These are described in detail below, including required arguments, response "
5317
"format, and return codes."
5318
msgstr ""
5319
5320
#: ../C/gdm.xml:4694(title)
5321
msgid "ADD_DYNAMIC_DISPLAY"
5322
msgstr ""
5323
5324
#: ../C/gdm.xml:4695(screen)
5325
#, no-wrap
5326
msgid ""
5327
"\n"
5328
"ADD_DYNAMIC_DISPLAY: Create a new server definition that will\n"
5329
" run on the specified display leaving, it\n"
5330
" in DISPLAY_CONFIG state.\n"
5331
"Supported since: 2.8.0.0\n"
5332
"Arguments: <display to run on>=<server>\n"
5333
" Where <server> is either a configuration named in the\n"
5334
" GDM configuration or a literal command name.\n"
5335
"Answers:\n"
5336
" OK <display>\n"
5337
" ERROR <err number> <english error description>\n"
5338
" 0 = Not implemented\n"
5339
" 2 = Existing display\n"
5340
" 3 = No server string\n"
5341
" 4 = Display startup failure\n"
5342
" 100 = Not authenticated\n"
5343
" 200 = Dynamic Displays not allowed\n"
5344
" 999 = Unknown error\n"
5345
msgstr ""
5346
5347
#: ../C/gdm.xml:4717(title)
5348
msgid "ALL_SERVERS"
5349
msgstr ""
5350
5351
#: ../C/gdm.xml:4718(screen)
5352
#, no-wrap
5353
msgid ""
5354
"\n"
5355
"ALL_SERVERS: List all displays, including console, remote, xnest.\n"
5356
" This can, for example, be useful to figure out if\n"
5357
" the display you are on is managed by the gdm daemon,\n"
5358
" by seeing if it is in the list. It is also somewhat\n"
5359
" like the 'w' command but for graphical sessions.\n"
5360
"Supported since: 2.4.2.96\n"
5361
"Arguments: None\n"
5362
"Answers:\n"
5363
" OK <server>;<server>;...\n"
5364
"\n"
5365
" <server> is <display>,<logged in user>\n"
5366
"\n"
5367
" <logged in user> can be empty in case no one logged in yet\n"
5368
"\n"
5369
" ERROR <err number> <english error description>\n"
5370
" 0 = Not implemented\n"
5371
" 200 = Too many messages\n"
5372
" 999 = Unknown error\n"
5373
msgstr ""
5374
5375
#: ../C/gdm.xml:4741(title)
5376
msgid "ATTACHED_SERVERS"
5377
msgstr ""
5378
5379
#: ../C/gdm.xml:4742(screen)
5380
#, no-wrap
5381
msgid ""
5382
"\n"
5383
"ATTACHED_SERVERS: List all attached displays. Doesn't list XDMCP\n"
5384
" and xnest non-attached displays.\n"
5385
"Note: This command used to be named CONSOLE_SERVERS,\n"
5386
" which is still recognized for backwards\n"
5387
" compatibility. The optional pattern argument\n"
5388
" is supported as of version 2.8.0.0.\n"
5389
"Supported since: 2.2.4.0\n"
5390
"Arguments: <pattern> (optional)\n"
5391
" With no argument, all attached displays are returned. The optional\n"
5392
" <pattern> is a string that may contain glob characters '*', '?', and\n"
5393
" '[]'. Only displays that match the pattern will be returned.\n"
5394
"Answers:\n"
5395
" OK <server>;<server>;...\n"
5396
"\n"
5397
" <server> is <display>,<logged in user>,<vt or xnest\n"
5398
" display>\n"
5399
"\n"
5400
" <logged in user> can be empty in case no one logged\n"
5401
" in yet, and <vt> can be -1 if it's not known or not\n"
5402
" supported (on non-Linux for example). If the display is an\n"
5403
" xnest display and is a console one (that is, it is an xnest\n"
5404
" inside another console display) it is listed and instead of\n"
5405
" vt, it lists the parent display in standard form.\n"
5406
"\n"
5407
" ERROR <err number> <english error description>\n"
5408
" 0 = Not implemented\n"
5409
" 200 = Too many messages\n"
5410
" 999 = Unknown error\n"
5411
msgstr ""
5412
5413
#: ../C/gdm.xml:4775(title)
5414
msgid "AUTH_LOCAL"
5415
msgstr ""
5416
5417
#: ../C/gdm.xml:4776(screen)
5418
#, no-wrap
5419
msgid ""
5420
"\n"
5421
"AUTH_LOCAL: Setup this connection as authenticated for\n"
5422
" FLEXI_SERVER. Because all full blown\n"
5423
" (non-nested) displays can be started only from\n"
5424
" users logged in locally, and here GDM assumes\n"
5425
" only users logged in from GDM. They must pass\n"
5426
" the xauth MIT-MAGIC-COOKIE-1 that they were passed\n"
5427
" before the connection is authenticated.\n"
5428
"Note: The AUTH LOCAL command requires the\n"
5429
" --authenticate option, although only\n"
5430
" FLEXI XSERVER uses this currently.\n"
5431
"Note: Since 2.6.0.6 you can also use a global\n"
5432
" <ServAuthDir>/.cookie, which works for all\n"
5433
" authentication except for SET_LOGOUT_ACTION and\n"
5434
" QUERY_LOGOUT_ACTION and SET_SAFE_LOGOUT_ACTION\n"
5435
" which require a logged in display.\n"
5436
"Supported since: 2.2.4.0\n"
5437
"Arguments: <xauth cookie>\n"
5438
" <xauth cookie> is in hex form with no 0x prefix\n"
5439
"Answers:\n"
5440
" OK\n"
5441
" ERROR <err number> <english error description>\n"
5442
" 0 = Not implemented\n"
5443
" 100 = Not authenticated\n"
5444
" 200 = Too many messages\n"
5445
" 999 = Unknown error\n"
5446
msgstr ""
5447
5448
#: ../C/gdm.xml:4806(title)
5449
msgid "CLOSE"
5450
msgstr ""
5451
5452
#: ../C/gdm.xml:4807(screen)
5453
#, no-wrap
5454
msgid ""
5455
"\n"
5456
"CLOSE: Close sockets connection\n"
5457
"Supported since: 2.2.4.0\n"
5458
"Arguments: None\n"
5459
"Answers: None\n"
5460
msgstr ""
5461
5462
#: ../C/gdm.xml:4816(title)
5463
msgid "FLEXI_XNEST"
5464
msgstr ""
5465
5466
#: ../C/gdm.xml:4817(screen)
5467
#, no-wrap
5468
msgid ""
5469
"\n"
5470
"FLEXI_XNEXT: Start a new flexible nested display.\n"
5471
"Note: Supported on older version from 2.2.4.0, later\n"
5472
" 2.2.4.2, but since 2.3.90.4 you must supply 4\n"
5473
" arguments or ERROR 100 will be returned. This\n"
5474
" will start the nested X server command using\n"
5475
" the XAUTHORITY file supplied and as the uid\n"
5476
" same as the owner of that file (and same as\n"
5477
" you supply). You must also supply the cookie as\n"
5478
" the third argument for this display, to prove\n"
5479
" that you indeed are this user. Also this file\n"
5480
" must be readable ONLY by this user, that is\n"
5481
" have a mode of 0600. If this all is not met,\n"
5482
" ERROR 100 is returned.\n"
5483
"Note: The cookie should be the MIT-MAGIC-COOKIE-1,\n"
5484
" the first one GDM can find in the XAUTHORITY\n"
5485
" file for this display. If that's not what you\n"
5486
" use you should generate one first. The cookie\n"
5487
" should be in hex form.\n"
5488
"Supported since: 2.3.90.4\n"
5489
"Arguments: <display to run on> <uid of requesting user>\n"
5490
" <xauth cookie for the display> <xauth file>\n"
5491
"Answers:\n"
5492
" OK <display>\n"
5493
" ERROR <err number> <english error description>\n"
5494
" 0 = Not implemented\n"
5495
" 1 = No more flexi servers\n"
5496
" 2 = Startup errors\n"
5497
" 3 = X failed\n"
5498
" 4 = X too busy\n"
5499
" 5 = Xnest can't connect\n"
5500
" 6 = No server binary\n"
5501
" 100 = Not authenticated\n"
5502
" 200 = Too many messages\n"
5503
" 999 = Unknown error\n"
5504
msgstr ""
5505
5506
#: ../C/gdm.xml:4856(title)
5507
msgid "FLEXI_XNEST_USER"
5508
msgstr ""
5509
5510
#: ../C/gdm.xml:4857(screen)
5511
#, no-wrap
5512
msgid ""
5513
"\n"
5514
"FLEXI_XNEST_USER: Start a new flexible nested display and\n"
5515
" initialize the greeter with the given username.\n"
5516
"Note: This is a variant of the FLEXI_XNEST command.\n"
5517
"Note: The cookie should be the MIT-MAGIC-COOKIE-1,\n"
5518
" the first one GDM can find in the XAUTHORITY\n"
5519
" file for this display. If that's not what you\n"
5520
" use you should generate one first. The cookie\n"
5521
" should be in hex form.\n"
5522
"Supported since: 2.17.7\n"
5523
"Arguments: <username> <display to run on> <uid of requesting\n"
5524
" user> <xauth cookie for the display> <xauth file>\n"
5525
"Answers:\n"
5526
" OK <display>\n"
5527
" ERROR <err number> <english error description>\n"
5528
" 0 = Not implemented\n"
5529
" 1 = No more flexi servers\n"
5530
" 2 = Startup errors\n"
5531
" 3 = X failed\n"
5532
" 4 = X too busy\n"
5533
" 5 = Xnest can't connect\n"
5534
" 6 = No server binary\n"
5535
" 100 = Not authenticated\n"
5536
" 200 = Too many messages\n"
5537
" 999 = Unknown error\n"
5538
msgstr ""
5539
5540
#: ../C/gdm.xml:4886(title)
5541
msgid "FLEXI_XSERVER"
5542
msgstr ""
5543
5544
#: ../C/gdm.xml:4887(screen)
5545
#, no-wrap
5546
msgid ""
5547
"\n"
5548
"FLEXI_XSERVER: Start a new X flexible display. Only supported on\n"
5549
" connection that passed AUTH_LOCAL\n"
5550
"Supported since: 2.2.4.0\n"
5551
"Arguments: <xserver type>\n"
5552
" If no arguments, starts the standard X server\n"
5553
"Answers:\n"
5554
" OK <display>\n"
5555
" ERROR <err number> <english error description>\n"
5556
" 0 = Not implemented\n"
5557
" 1 = No more flexi servers\n"
5558
" 2 = Startup errors\n"
5559
" 3 = X failed\n"
5560
" 4 = X too busy\n"
5561
" 6 = No server binary\n"
5562
" 100 = Not authenticated\n"
5563
" 200 = Too many messages\n"
5564
" 999 = Unknown error\n"
5565
msgstr ""
5566
5567
#: ../C/gdm.xml:4909(title)
5568
msgid "FLEXI_XSERVER_USER"
5569
msgstr ""
5570
5571
#: ../C/gdm.xml:4910(screen)
5572
#, no-wrap
5573
msgid ""
5574
"\n"
5575
"FLEXI_XSERVER_USER: Start a new X flexible display and initialize the\n"
5576
" greeter with the given username. Only supported on\n"
5577
" connection that passed AUTH_LOCAL\n"
5578
"Supported since: 2.17.7 \n"
5579
"Arguments: <username> <xserver type>\n"
5580
" If no server type specified, starts the standard X server\n"
5581
"Answers:\n"
5582
" OK <display>\n"
5583
" ERROR <err number> <english error description>\n"
5584
" 0 = Not implemented\n"
5585
" 1 = No more flexi servers\n"
5586
" 2 = Startup errors\n"
5587
" 3 = X failed\n"
5588
" 4 = X too busy\n"
5589
" 6 = No server binary\n"
5590
" 100 = Not authenticated\n"
5591
" 200 = Too many messages\n"
5592
" 999 = Unknown error\n"
5593
msgstr ""
5594
5595
#: ../C/gdm.xml:4933(title)
5596
msgid "GET_CONFIG"
5597
msgstr ""
5598
5599
#: ../C/gdm.xml:4934(screen)
5600
#, no-wrap
5601
msgid ""
5602
"\n"
5603
"GET_CONFIG: Get configuration value for key. Useful so\n"
5604
" that other applications can request configuration\n"
5605
" information from GDM. Any key defined as GDM_KEY_*\n"
5606
" in gdm-daemon-config-keys.h is supported. Starting with version\n"
5607
" 2.13.0.2, translated keys (such as\n"
5608
" \"greeter/GdmWelcome[cs]\" are supported via GET_CONFIG.\n"
5609
" Also starting with version 2.13.0.2 it is no longer necessary to\n"
5610
" include the default value (i.e. you can use key\n"
5611
" \"greeter/IncludeAll\" instead of having to use\n"
5612
" \"greeter/IncludeAll=false\". \n"
5613
"Supported since: 2.6.0.9\n"
5614
"Arguments: <key>\n"
5615
"Answers:\n"
5616
" OK <value>\n"
5617
" ERROR <err number> <english error description>\n"
5618
" 0 = Not implemented\n"
5619
" 50 = Unsupported key\n"
5620
" 200 = Too many messages\n"
5621
" 999 = Unknown error\n"
5622
msgstr ""
5623
5624
#: ../C/gdm.xml:4958(title)
5625
msgid "GET_CONFIG_FILE"
5626
msgstr ""
5627
5628
#: ../C/gdm.xml:4959(screen)
5629
#, no-wrap
5630
msgid ""
5631
"\n"
5632
"GET_CONFIG_FILE: Get config file location being used by\n"
5633
" the daemon. If the GDM daemon was started\n"
5634
" with the --config option, it will return\n"
5635
" the value passed in via the argument.\n"
5636
"Supported since: 2.8.0.2\n"
5637
"Arguments: None\n"
5638
"Answers:\n"
5639
" OK <full path to GDM configuration file>\n"
5640
" ERROR <err number> <english error description>\n"
5641
" 0 = Not implemented\n"
5642
" 200 = Too many messages\n"
5643
" 999 = Unknown error\n"
5644
msgstr ""
5645
5646
#: ../C/gdm.xml:4976(title)
5647
msgid "GET_CUSTOM_CONFIG_FILE"
5648
msgstr ""
5649
5650
#: ../C/gdm.xml:4977(screen)
5651
#, no-wrap
5652
msgid ""
5653
"\n"
5654
"GET_CUSTOM_CONFIG_FILE: Get custom config file location being\n"
5655
" used by the daemon.\n"
5656
"Supported since: 2.14.0.0\n"
5657
"Arguments: None\n"
5658
"Answers:\n"
5659
" OK <full path to GDM custom configuration file>\n"
5660
" ERROR <err number> <english error description>\n"
5661
" 0 = Not implemented\n"
5662
" 1 = File not found\n"
5663
" 200 = Too many messages\n"
5664
" 999 = Unknown error\n"
5665
msgstr ""
5666
5667
#: ../C/gdm.xml:4993(title)
5668
msgid "GET_SERVER_DETAILS"
5669
msgstr ""
5670
5671
#: ../C/gdm.xml:4994(screen)
5672
#, no-wrap
5673
msgid ""
5674
"\n"
5675
"GET_SERVER_DETAILS: Get detail information for a specific server.\n"
5676
"Supported since: 2.13.0.4\n"
5677
"Arguments: <server> <key>\n"
5678
" Key values include:\n"
5679
" NAME - Returns the server name\n"
5680
" COMMAND - Returns the server command\n"
5681
" FLEXIBLE - Returns \"true\" if flexible, \"false\"\n"
5682
" otherwise\n"
5683
" CHOOSABLE - Returns \"true\" if choosable, \"false\"\n"
5684
" otherwise\n"
5685
" HANDLED - Returns \"true\" if handled, \"false\"\n"
5686
" otherwise\n"
5687
" CHOOSER - Returns \"true\" if chooser, \"false\"\n"
5688
" otherwise\n"
5689
" PRIORITY - Returns process priority\n"
5690
"Answers:\n"
5691
" OK <value>\n"
5692
" ERROR <err number> <english error description>\n"
5693
" 0 = Not implemented\n"
5694
" 1 = Server not found\n"
5695
" 2 = Key not valid\n"
5696
" 50 = Unsupported key\n"
5697
" 200 = Too many messages\n"
5698
" 999 = Unknown error\n"
5699
msgstr ""
5700
5701
#: ../C/gdm.xml:5023(title)
5702
msgid "GET_SERVER_LIST"
5703
msgstr ""
5704
5705
#: ../C/gdm.xml:5024(screen)
5706
#, no-wrap
5707
msgid ""
5708
"\n"
5709
"GET_SERVER_LIST: Get a list of the server sections from\n"
5710
" the configuration file.\n"
5711
"Supported since: 2.13.0.4\n"
5712
"Arguments: None\n"
5713
"Answers:\n"
5714
" OK <value>;<value>;...\n"
5715
" ERROR <err number> <english error description>\n"
5716
" 0 = Not implemented\n"
5717
" 1 = No servers found\n"
5718
" 200 = Too many messages\n"
5719
" 999 = Unknown error\n"
5720
msgstr ""
5721
5722
#: ../C/gdm.xml:5040(title)
5723
msgid "GREETERPIDS"
5724
msgstr ""
5725
5726
#: ../C/gdm.xml:5041(screen)
5727
#, no-wrap
5728
msgid ""
5729
"\n"
5730
"GREETERPIDS: List all greeter pids so that one can send HUP\n"
5731
" to them for config rereading. Of course one\n"
5732
" must be root to do that.\n"
5733
"Supported since: 2.3.90.2\n"
5734
"Arguments: None\n"
5735
"Answers:\n"
5736
" OK <pid>;<pid>;...\n"
5737
" ERROR <err number> <english error description>\n"
5738
" 0 = Not implemented\n"
5739
" 200 = Too many messages\n"
5740
" 999 = Unknown error\n"
5741
msgstr ""
5742
5743
#: ../C/gdm.xml:5057(title)
5744
msgid "QUERY_LOGOUT_ACTION"
5745
msgstr ""
5746
5747
#: ../C/gdm.xml:5058(screen)
5748
#, no-wrap
5749
msgid ""
5750
"\n"
5751
"QUERY_LOGOUT_ACTION: Query which logout actions are possible\n"
5752
" Only supported on connections that passed\n"
5753
" AUTH_LOCAL.\n"
5754
"Supported since: 2.5.90.0\n"
5755
"Answers:\n"
5756
" OK <action>;<action>;...\n"
5757
" Where action is one of HALT, REBOOT, SUSPEND or CUSTOM_CMD[0-9].\n"
5758
" An empty list can also be returned if no action is possible.\n"
5759
" A '!' is appended to an action if it was already set with\n"
5760
" SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION. Note that\n"
5761
" SET_LOGOUT_ACTION has precedence over\n"
5762
" SET_SAFE_LOGOUT_ACTION.\n"
5763
" ERROR <err number> <english error description>\n"
5764
" 0 = Not implemented\n"
5765
" 100 = Not authenticated\n"
5766
" 200 = Too many messages\n"
5767
" 999 = Unknown error\n"
5768
msgstr ""
5769
5770
#: ../C/gdm.xml:5080(title)
5771
msgid "QUERY_CUSTOM_CMD_LABELS"
5772
msgstr ""
5773
5774
#: ../C/gdm.xml:5081(screen)
5775
#, no-wrap
5776
msgid ""
5777
"\n"
5778
" QUERY_CUSTOM_CMD_LABELS: Query labels belonging to exported custom\n"
5779
" commands Only supported on connections that\n"
5780
" passed AUTH_LOCAL.\n"
5781
" Supported since: 2.5.90.0\n"
5782
" Answers:\n"
5783
" OK <label1>;<label2>;...\n"
5784
" Where labelX is one of the labels belonging to CUSTOM_CMDX\n"
5785
" (where X in [0,GDM_CUSTOM_COMMAND_MAX)). An empty list can\n"
5786
" also be returned if none of the custom commands are exported\n"
5787
" outside login manager (no CustomCommandIsPersistent options\n"
5788
" are set to true). \n"
5789
" ERROR <err number> <english error description>\n"
5790
" 0 = Not implemented\n"
5791
" 100 = Not authenticated\n"
5792
" 200 = Too many messages\n"
5793
" 999 = Unknown error\n"
5794
msgstr ""
5795
5796
#: ../C/gdm.xml:5102(title)
5797
msgid "QUERY_CUSTOM_CMD_NO_RESTART_STATUS"
5798
msgstr ""
5799
5800
#: ../C/gdm.xml:5103(screen)
5801
#, no-wrap
5802
msgid ""
5803
"\n"
5804
"QUERY_CUSTOM_CMD_NO_RESTART_STATUS: Query NoRestart config options\n"
5805
" for each of custom commands Only\n"
5806
" supported on connections that\n"
5807
" passed AUTH_LOCAL.\n"
5808
"Supported since: 2.5.90.0\n"
5809
"Answers:\n"
5810
" OK <status>\n"
5811
" Where each bit of the status represents NoRestart value for\n"
5812
" each of the custom commands.\n"
5813
" bit on (1): NoRestart = true, \n"
5814
" bit off (0): NoRestart = false.\n"
5815
" ERROR <err number> <english error description>\n"
5816
" 0 = Not implemented\n"
5817
" 100 = Not authenticated\n"
5818
" 200 = Too many messages\n"
5819
" 999 = Unknown error\n"
5820
msgstr ""
5821
5822
#: ../C/gdm.xml:5124(title)
5823
msgid "QUERY_VT"
5824
msgstr ""
5825
5826
#: ../C/gdm.xml:5125(screen)
5827
#, no-wrap
5828
msgid ""
5829
"\n"
5830
"QUERY_VT: Ask the daemon about which VT we are currently on.\n"
5831
" This is useful for logins which don't own\n"
5832
" /dev/console but are still console logins. Only\n"
5833
" supported on Linux currently, other places will\n"
5834
" just get ERROR 8. This is also the way to query\n"
5835
" if VT support is available in the daemon in the\n"
5836
" first place. Only supported on connections that\n"
5837
" passed AUTH_LOCAL.\n"
5838
"Supported since: 2.5.90.0\n"
5839
"Arguments: None\n"
5840
"Answers:\n"
5841
" OK <vt number>\n"
5842
" ERROR <err number> <english error description>\n"
5843
" 0 = Not implemented\n"
5844
" 8 = Virtual terminals not supported\n"
5845
" 100 = Not authenticated\n"
5846
" 200 = Too many messages\n"
5847
" 999 = Unknown error\n"
5848
msgstr ""
5849
5850
#: ../C/gdm.xml:5148(title)
5851
msgid "RELEASE_DYNAMIC_DISPLAYS"
5852
msgstr ""
5853
5854
#: ../C/gdm.xml:5149(screen)
5855
#, no-wrap
5856
msgid ""
5857
"\n"
5858
"RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in \n"
5859
" DISPLAY_CONFIG state\n"
5860
"Supported since: 2.8.0.0\n"
5861
"Arguments: <display to release>\n"
5862
"Answers:\n"
5863
" OK <display>\n"
5864
" ERROR <err number> <english error description>\n"
5865
" 0 = Not implemented\n"
5866
" 1 = Bad display number\n"
5867
" 100 = Not authenticated\n"
5868
" 200 = Dynamic Displays not allowed\n"
5869
" 999 = Unknown error\n"
5870
msgstr ""
5871
5872
#: ../C/gdm.xml:5166(title)
5873
msgid "REMOVE_DYNAMIC_DISPLAY"
5874
msgstr ""
5875
5876
#: ../C/gdm.xml:5167(screen)
5877
#, no-wrap
5878
msgid ""
5879
"\n"
5880
"REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server\n"
5881
" and purging the display configuration\n"
5882
"Supported since: 2.8.0.0\n"
5883
"Arguments: <display to remove>\n"
5884
"Answers:\n"
5885
" OK <display>\n"
5886
" ERROR <err number> <english error description>\n"
5887
" 0 = Not implemented\n"
5888
" 1 = Bad display number\n"
5889
" 100 = Not authenticated\n"
5890
" 200 = Dynamic Displays not allowed\n"
5891
" 999 = Unknown error\n"
5892
msgstr ""
5893
5894
#: ../C/gdm.xml:5184(title)
5895
msgid "SERVER_BUSY"
5896
msgstr ""
5897
5898
#: ../C/gdm.xml:5185(screen)
5899
#, no-wrap
5900
msgid ""
5901
"\n"
5902
"SERVER_BUSY: Returns true if half or more of the daemon's sockets\n"
5903
" are busy, false otherwise. Used by slave programs\n"
5904
" which want to ensure they do not overwhelm the \n"
5905
" sever.\n"
5906
"Supported since: 2.13.0.8\n"
5907
"Arguments: None\n"
5908
"Answers:\n"
5909
" OK <value>\n"
5910
" ERROR <err number> <english error description>\n"
5911
" 0 = Not implemented\n"
5912
" 200 = Too many messages\n"
5913
" 999 = Unknown error\n"
5914
msgstr ""
5915
5916
#: ../C/gdm.xml:5202(title)
5917
msgid "SET_LOGOUT_ACTION"
5918
msgstr ""
5919
5920
#: ../C/gdm.xml:5203(screen)
5921
#, no-wrap
5922
msgid ""
5923
"\n"
5924
"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n"
5925
" slave process exits. Only supported on\n"
5926
" connections that passed AUTH_LOCAL.\n"
5927
"Supported since: 2.5.90.0\n"
5928
"Arguments: <action>\n"
5929
" NONE Set exit action to 'none'\n"
5930
" HALT Set exit action to 'halt'\n"
5931
" REBOOT Set exit action to 'reboot'\n"
5932
" SUSPEND Set exit action to 'suspend'\n"
5933
" CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]'\n"
5934
"Answers:\n"
5935
" OK\n"
5936
" ERROR <err number> <english error description>\n"
5937
" 0 = Not implemented\n"
5938
" 7 = Unknown logout action, or not available\n"
5939
" 100 = Not authenticated\n"
5940
" 200 = Too many messages\n"
5941
" 999 = Unknown error\n"
5942
msgstr ""
5943
5944
#: ../C/gdm.xml:5226(title)
5945
msgid "SET_SAFE_LOGOUT_ACTION"
5946
msgstr ""
5947
5948
#: ../C/gdm.xml:5227(screen)
5949
#, no-wrap
5950
msgid ""
5951
"\n"
5952
"SET_SAFE_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend\n"
5953
" after everybody logs out. If only one\n"
5954
" person logs out, then this is obviously\n"
5955
" the same as the SET_LOGOUT_ACTION. Note\n"
5956
" that SET_LOGOUT_ACTION has precedence\n"
5957
" over SET_SAFE_LOGOUT_ACTION if it is set\n"
5958
" to something other then NONE. If no one\n"
5959
" is logged in, then the action takes effect\n"
5960
" effect immediately. Only supported on\n"
5961
" connections that passed AUTH_LOCAL.\n"
5962
"Supported since: 2.5.90.0\n"
5963
"Arguments: <action>\n"
5964
" NONE Set exit action to 'none'\n"
5965
" HALT Set exit action to 'halt'\n"
5966
" REBOOT Set exit action to 'reboot'\n"
5967
" SUSPEND Set exit action to 'suspend'\n"
5968
" CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]'\n"
5969
"Answers:\n"
5970
" OK\n"
5971
" ERROR <err number> <english error description>\n"
5972
" 0 = Not implemented\n"
5973
" 7 = Unknown logout action, or not available\n"
5974
" 100 = Not authenticated\n"
5975
" 200 = Too many messages\n"
5976
" 999 = Unknown error\n"
5977
msgstr ""
5978
5979
#: ../C/gdm.xml:5257(title)
5980
msgid "SET_VT"
5981
msgstr ""
5982
5983
#: ../C/gdm.xml:5258(screen)
5984
#, no-wrap
5985
msgid ""
5986
"\n"
5987
"SET_VT: Change to the specified virtual terminal.\n"
5988
" This is useful for logins which don't own /dev/console\n"
5989
" but are still console logins. Only supported on Linux\n"
5990
" currently, other places will just get ERROR 8.\n"
5991
" Only supported on connections that passed AUTH_LOCAL.\n"
5992
"Supported since: 2.5.90.0\n"
5993
"Arguments: <vt>\n"
5994
"Answers:\n"
5995
" OK\n"
5996
" ERROR <err number> <english error description>\n"
5997
" 0 = Not implemented\n"
5998
" 8 = Virtual terminals not supported\n"
5999
" 9 = Invalid virtual terminal number\n"
6000
" 100 = Not authenticated\n"
6001
" 200 = Too many messages\n"
6002
" 999 = Unknown error\n"
6003
msgstr ""
6004
6005
#: ../C/gdm.xml:5279(title)
6006
msgid "UPDATE_CONFIG"
6007
msgstr ""
6008
6009
#: ../C/gdm.xml:5280(screen)
6010
#, no-wrap
6011
msgid ""
6012
"\n"
6013
"UPDATE_CONFIG: Tell the daemon to re-read a key from the \n"
6014
" GDM configuration file. Any user can request\n"
6015
" that values are re-read but the daemon will\n"
6016
" only do so if the file has been modified\n"
6017
" since GDM first read the file. Only users\n"
6018
" who can change the GDM configuration file\n"
6019
" (normally writable only by the root user) can\n"
6020
" actually modify the GDM configuration. This\n"
6021
" command is useful to cause the GDM to update\n"
6022
" itself to recognize a change made to the GDM\n"
6023
" configuration file by the root user.\n"
6024
"\n"
6025
" Starting with version 2.13.0.0, all GDM keys are\n"
6026
" supported except for the following:\n"
6027
"\n"
6028
" daemon/PidFile\n"
6029
" daemon/ConsoleNotify\n"
6030
" daemon/User\n"
6031
" daemon/Group\n"
6032
" daemon/LogDir\n"
6033
" daemon/ServAuthDir\n"
6034
" daemon/UserAuthDir\n"
6035
" daemon/UserAuthFile\n"
6036
" daemon/UserAuthFBDir\n"
6037
"\n"
6038
" GDM also supports the following Psuedokeys:\n"
6039
"\n"
6040
" xdmcp/PARAMETERS (2.3.90.2) updates the following:\n"
6041
" xdmcp/MaxPending\n"
6042
" xdmcp/MaxSessions\n"
6043
" xdmcp/MaxWait\n"
6044
" xdmcp/DisplaysPerHost\n"
6045
" xdmcp/HonorIndirect\n"
6046
" xdmcp/MaxPendingIndirect\n"
6047
" xdmcp/MaxWaitIndirect\n"
6048
" xdmcp/PingIntervalSeconds (only affects new connections)\n"
6049
"\n"
6050
" xservers/PARAMETERS (2.13.0.4) updates the following:\n"
6051
" all [server-foo] sections.\n"
6052
"\n"
6053
" Supported keys for previous versions of GDM:\n"
6054
"\n"
6055
" security/AllowRoot (2.3.90.2)\n"
6056
" security/AllowRemoteRoot (2.3.90.2)\n"
6057
" security/AllowRemoteAutoLogin (2.3.90.2)\n"
6058
" security/RetryDelay (2.3.90.2)\n"
6059
" security/DisallowTCP (2.4.2.0)\n"
6060
" daemon/Greeter (2.3.90.2)\n"
6061
" daemon/RemoteGreeter (2.3.90.2)\n"
6062
" xdmcp/Enable (2.3.90.2)\n"
6063
" xdmcp/Port (2.3.90.2)\n"
6064
" daemon/TimedLogin (2.3.90.3)\n"
6065
" daemon/TimedLoginEnable (2.3.90.3)\n"
6066
" daemon/TimedLoginDelay (2.3.90.3)\n"
6067
" greeter/SystemMenu (2.3.90.3)\n"
6068
" greeter/ConfigAvailable (2.3.90.3)\n"
6069
" greeter/ChooserButton (2.4.2.0)\n"
6070
" greeter/SoundOnLoginFile (2.5.90.0)\n"
6071
" daemon/AddGtkModules (2.5.90.0)\n"
6072
" daemon/GtkModulesList (2.5.90.0)\n"
6073
"Supported since: 2.3.90.2\n"
6074
"Arguments: <key>\n"
6075
" <key> is just the base part of the key such as\n"
6076
" \"security/AllowRemoteRoot\"\n"
6077
"Answers:\n"
6078
" OK\n"
6079
" ERROR <err number> <english error description>\n"
6080
" 0 = Not implemented\n"
6081
" 50 = Unsupported key\n"
6082
" 200 = Too many messages\n"
6083
" 999 = Unknown error\n"
6084
msgstr ""
6085
6086
#: ../C/gdm.xml:5356(title)
6087
msgid "VERSION"
6088
msgstr ""
6089
6090
#: ../C/gdm.xml:5357(screen)
6091
#, no-wrap
6092
msgid ""
6093
"\n"
6094
"VERSION: Query GDM version\n"
6095
"Supported since: 2.2.4.0\n"
6096
"Arguments: None\n"
6097
"Answers:\n"
6098
" GDM <gdm version>\n"
6099
" ERROR <err number> <english error description>\n"
6100
" 200 = Too many messages\n"
6101
" 999 = Unknown error\n"
6102
msgstr ""
6103
6104
#: ../C/gdm.xml:5374(title)
6105
msgid "GDM Commands"
6106
msgstr ""
6107
6108
#: ../C/gdm.xml:5377(title)
6109
msgid "GDM User Commands"
6110
msgstr ""
6111
6112
#: ../C/gdm.xml:5379(para)
6113
msgid ""
6114
"The GDM package provides the following different commands in "
6115
"<filename>bindir</filename> intended to be used by the end-user:"
6116
msgstr ""
6117
6118
#: ../C/gdm.xml:5385(title)
6119
msgid ""
6120
"<command>gdmXnestchooser</command> and <command>gdmXnest</command> Command "
6121
"Line Options"
6122
msgstr ""
6123
6124
#: ../C/gdm.xml:5388(para)
6125
msgid ""
6126
"The <command>gdmXnestchooser</command> command automatically gets the "
6127
"correct display number, sets up access, and runs the nested X server command "
6128
"with the \"-indirect localhost\" argument. This provides an XDMCP chooser "
6129
"program. You can also supply as an argument the hostname whose chooser "
6130
"should be displayed, so <command>gdmXnestchooser somehost</command> will run "
6131
"the XDMCP chooser from host <command>somehost</command> inside a nested X "
6132
"server session. You can make this command do a direct query instead by "
6133
"passing the <command>-d</command> option as well. In addition to the "
6134
"following options, this command also supports standard GNOME options."
6135
msgstr ""
6136
6137
#: ../C/gdm.xml:5403(title)
6138
msgid "<command>gdmXnestchooser</command> Command Line Options"
6139
msgstr ""
6140
6141
#: ../C/gdm.xml:5406(term)
6142
msgid "-x, --xnest=STRING"
6143
msgstr ""
6144
6145
#: ../C/gdm.xml:5408(para)
6146
msgid ""
6147
"Nested X server command line, default is defined by the <filename>Xnest</"
6148
"filename> configuration option."
6149
msgstr ""
6150
6151
#: ../C/gdm.xml:5416(term)
6152
msgid "-o, --xnest-extra-options=OPTIONS"
6153
msgstr ""
6154
6155
#: ../C/gdm.xml:5418(para)
6156
msgid "Extra options for nested X server, default is no options."
6157
msgstr ""
6158
6159
#: ../C/gdm.xml:5425(term)
6160
msgid "-n, --no-query"
6161
msgstr ""
6162
6163
#: ../C/gdm.xml:5427(para)
6164
msgid "Just run nested X server, no query (no chooser)"
6165
msgstr ""
6166
6167
#: ../C/gdm.xml:5434(term)
6168
msgid "-d, --direct"
6169
msgstr ""
6170
6171
#: ../C/gdm.xml:5436(para)
6172
msgid "Do direct query instead of indirect (chooser)"
6173
msgstr ""
6174
6175
#: ../C/gdm.xml:5443(term)
6176
msgid "-B, --broadcast"
6177
msgstr ""
6178
6179
#: ../C/gdm.xml:5445(para)
6180
msgid "Run broadcast instead of indirect (chooser)"
6181
msgstr ""
6182
6183
#: ../C/gdm.xml:5452(term)
6184
msgid "-b, --background"
6185
msgstr ""
6186
6187
#: ../C/gdm.xml:5454(para)
6188
msgid "Run in background"
6189
msgstr ""
6190
6191
#: ../C/gdm.xml:5461(term)
6192
msgid "--no-gdm-check"
6193
msgstr ""
6194
6195
#: ../C/gdm.xml:5463(para)
6196
msgid "Don't check for running GDM"
6197
msgstr ""
6198
6199
#: ../C/gdm.xml:5472(title) ../C/gdm.xml:5515(title)
6200
msgid "<command>gdmflexichooser</command> Command Line Options"
6201
msgstr ""
6202
6203
#: ../C/gdm.xml:5474(para)
6204
msgid ""
6205
"The <command>gdmflexiserver</command> command provides three features. It "
6206
"can be used to run flexible (on demand) X displays, to run a flexible "
6207
"display via nested X server, and to send commands to the GDM daemon process."
6208
msgstr ""
6209
6210
#: ../C/gdm.xml:5481(para)
6211
msgid ""
6212
"Starting a flexible X display will normally lock the current session with a "
6213
"screensaver and will redisplay the GDM login screen so a second user can log "
6214
"in. This feature is only available on systems that support virtual terminals "
6215
"and have them enabled. This feature is useful if you are logged in as user "
6216
"A, and user B wants to log in quickly but user A does not wish to log out. "
6217
"The X server takes care of the virtual terminal switching so it works "
6218
"transparently. If there is more than one running display defined with "
6219
"flexible=true, then the user is shown a dialog that displays the currently "
6220
"running sessions. The user can then pick which session to continue and will "
6221
"normally have to enter the password to unlock the screen."
6222
msgstr ""
6223
6224
#: ../C/gdm.xml:5495(para)
6225
msgid ""
6226
"Nested displays works on systems that do not support virtual terminals. This "
6227
"option starts a flexible display in a window in the current session. This "
6228
"does not lock the current session, so is not as secure as a flexible server "
6229
"started via virtual terminals."
6230
msgstr ""
6231
6232
#: ../C/gdm.xml:5502(para)
6233
msgid ""
6234
"The <command>gdmflexiserver --command</command> option provides a way to "
6235
"send commands to the GDM daemon and can be used to debug problems or to "
6236
"change the GDM configuration."
6237
msgstr ""
6238
6239
#: ../C/gdm.xml:5508(para)
6240
msgid ""
6241
"In addition to the following options, <command>gdmflexiserver</command> also "
6242
"supports standard GNOME options."
6243
msgstr ""
6244
6245
#: ../C/gdm.xml:5518(term)
6246
msgid "-c, --command=COMMAND"
6247
msgstr ""
6248
6249
#: ../C/gdm.xml:5520(para)
6250
msgid "Send the specified protocol command to GDM"
6251
msgstr ""
6252
6253
#: ../C/gdm.xml:5527(term)
6254
msgid "-n, --xnest"
6255
msgstr ""
6256
6257
#: ../C/gdm.xml:5529(para)
6258
msgid "Start a flexible X display in Nested mode"
6259
msgstr ""
6260
6261
#: ../C/gdm.xml:5536(term)
6262
msgid "-l, --no-lock"
6263
msgstr ""
6264
6265
#: ../C/gdm.xml:5538(para)
6266
msgid "Do not lock current screen"
6267
msgstr ""
6268
6269
#: ../C/gdm.xml:5545(term)
6270
msgid "-d, --debug"
6271
msgstr ""
6272
6273
#: ../C/gdm.xml:5547(para)
6274
msgid ""
6275
"Turns on debugging output which gets sent to syslog. Same as turning on "
6276
"debug in the configuration file."
6277
msgstr ""
6278
6279
#: ../C/gdm.xml:5555(term)
6280
msgid "-a, --authenticate"
6281
msgstr ""
6282
6283
#: ../C/gdm.xml:5557(para)
6284
msgid "Authenticate before running --command"
6285
msgstr ""
6286
6287
#: ../C/gdm.xml:5564(term)
6288
msgid "-s, --startnew"
6289
msgstr ""
6290
6291
#: ../C/gdm.xml:5566(para)
6292
msgid ""
6293
"Starts a new flexible display without displaying a dialog asking the user if "
6294
"they wish to continue any existing sessions."
6295
msgstr ""
6296
6297
#: ../C/gdm.xml:5577(title) ../C/gdm.xml:5604(title)
6298
msgid "<command>gdmdynamic</command> Command Line Options"
6299
msgstr ""
6300
6301
#: ../C/gdm.xml:5579(para)
6302
msgid ""
6303
"<command>gdmdynamic</command> allows the management of displays in a dynamic "
6304
"fashion. It is typically used in environments where it is not possible to "
6305
"list the possible displays in the GDM configuration files. The "
6306
"<command>gdmdynamic</command> command can be used to create a new display on "
6307
"a particular display number, run all newly created displays, or remove a "
6308
"display. The <command>gdmdynamic</command> command can also be used to list "
6309
"all attached displays or only those attached displays that match a pattern. "
6310
"The -a option is used to add a display, the -r option is used to run (or "
6311
"release) a display, the -d option is used to delete a display, and the -l "
6312
"option lists existing displays. Only one of these four options can be "
6313
"specified at a time, so in the life cycle of a particular display, the "
6314
"command will be run once to add, again to release (run) the display, and "
6315
"finally to delete when the session is to be terminated."
6316
msgstr ""
6317
6318
#: ../C/gdm.xml:5596(para)
6319
msgid ""
6320
"This program is designed to manage multiple simultaneous requests and tries "
6321
"to avoid flooding the daemon with requests. If the sockets connection is "
6322
"busy, it will sleep and retry a certain number of times that can be tuned "
6323
"with the -s and -t options."
6324
msgstr ""
6325
6326
#: ../C/gdm.xml:5607(term)
6327
msgid "-a display=server"
6328
msgstr ""
6329
6330
#: ../C/gdm.xml:5609(para)
6331
msgid ""
6332
"Add a new display configuration, leaving it in the DISPLAY_CONFIG state. For "
6333
"example, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a 3=/usr/"
6334
"X11R6/bin/X -dev /dev/fb2\"</command>"
6335
msgstr ""
6336
6337
#: ../C/gdm.xml:5615(para)
6338
msgid ""
6339
"The display will not actually be started until the display is released by "
6340
"calling <command>gdmdynamic</command> again with the -r option."
6341
msgstr ""
6342
6343
#: ../C/gdm.xml:5623(term)
6344
msgid "-r"
6345
msgstr ""
6346
6347
#: ../C/gdm.xml:5625(para)
6348
msgid "Release (run) all displays waiting in the DISPLAY_CONFIG state."
6349
msgstr ""
6350
6351
#: ../C/gdm.xml:5632(term)
6352
msgid "-d display"
6353
msgstr ""
6354
6355
#: ../C/gdm.xml:5634(para)
6356
msgid ""
6357
"Delete a display, killing the X server and purging the display "
6358
"configuration. For example, \"-d 3\"."
6359
msgstr ""
6360
6361
#: ../C/gdm.xml:5642(term)
6362
msgid "-l [pattern]"
6363
msgstr ""
6364
6365
#: ../C/gdm.xml:5644(para)
6366
msgid ""
6367
"List displays via the ATTACHED_SERVERS <command>gdmflexiserver</command> "
6368
"command. Without a pattern lists all attached displays. With a pattern will "
6369
"match using glob characters '*', '?', and '[]'. For example: <command>\"-l "
6370
"Standard*\"</command><command>\"-l *Xorg*\"</command>"
6371
msgstr ""
6372
6373
#: ../C/gdm.xml:5655(term)
6374
msgid "-v"
6375
msgstr ""
6376
6377
#: ../C/gdm.xml:5657(para)
6378
msgid "Verbose mode. Prints diagnostic messages. to GDM."
6379
msgstr ""
6380
6381
#: ../C/gdm.xml:5665(term)
6382
msgid "-b"
6383
msgstr ""
6384
6385
#: ../C/gdm.xml:5667(para)
6386
msgid "Background mode. Fork child to do the work and return immediately."
6387
msgstr ""
6388
6389
#: ../C/gdm.xml:5674(term)
6390
msgid "-t RETRY"
6391
msgstr ""
6392
6393
#: ../C/gdm.xml:5676(para)
6394
msgid ""
6395
"If the daemon socket is busy, <command>gdmdynamic</command> will retry to "
6396
"open the connection the specified RETRY number of times. Default value is 15."
6397
msgstr ""
6398
6399
#: ../C/gdm.xml:5685(term)
6400
msgid "-s SLEEP"
6401
msgstr ""
6402
6403
#: ../C/gdm.xml:5687(para)
6404
msgid ""
6405
"If the daemon socket is busy, <command>gdmdynamic</command> will sleep an "
6406
"amount of time between retries. A random number of seconds 0-5 is added to "
6407
"the SLEEP value to help ensure that multiple calls to gdmdynamic do not all "
6408
"try to restart at the same time. A SLEEP value of zero causes the sleep time "
6409
"to be 1 second. Default value is 8 seconds."
6410
msgstr ""
6411
6412
#: ../C/gdm.xml:5702(title)
6413
msgid "<command>gdmphotosetup</command> Command Line Options"
6414
msgstr ""
6415
6416
#: ../C/gdm.xml:5704(para)
6417
msgid ""
6418
"Allows the user to select an image that will be used as the user's photo by "
6419
"GDM's face browser, if enabled by GDM. The selected file is stored as "
6420
"<filename>~/.face</filename>. This command accepts standard GNOME options."
6421
msgstr ""
6422
6423
#: ../C/gdm.xml:5713(title)
6424
msgid "<command>gdmthemetester</command> Command Line Options"
6425
msgstr ""
6426
6427
#: ../C/gdm.xml:5715(para)
6428
msgid ""
6429
"<command>gdmthemetester</command> takes two parameters. The first parameter "
6430
"specifies the environment and the second parameter specifies the path name "
6431
"or the name of a theme to view. This is a tool for viewing a theme outside "
6432
"of GDM. It is useful for testing or viewing themes. <command>gdmthemetester</"
6433
"command> requires that the system support <command>gdmXnest</command>. Note "
6434
"that themes can display differently depending on the theme's \"Show mode\". "
6435
"<command>gdmthemetester</command> allows viewing the themes in different "
6436
"modes via the environment option. Valid environment values and their "
6437
"meanings follow: <screen>\n"
6438
"console - In console mode.\n"
6439
"console-timed - In console non-flexi mode.\n"
6440
"flexi - In flexi mode.\n"
6441
"xdmcp - In remote (XDMCP) mode.\n"
6442
"remote-flexi - In remote (XDMCP) & flexi mode.\n"
6443
"</screen>"
6444
msgstr ""
6445
6446
#: ../C/gdm.xml:5741(title)
6447
msgid "GDM Root User Commands"
6448
msgstr ""
6449
6450
#: ../C/gdm.xml:5743(para)
6451
msgid ""
6452
"The GDM package provides the following different commands in "
6453
"<filename>sbindir</filename> intended to be used by the root user:"
6454
msgstr ""
6455
6456
#: ../C/gdm.xml:5749(title) ../C/gdm.xml:5765(title)
6457
msgid "<command>gdm</command> and <command>gdm-binary</command> Command Line Options"
6458
msgstr ""
6459
6460
#: ../C/gdm.xml:5752(para)
6461
msgid ""
6462
"The <command>gdm</command> command is really just a script which runs the "
6463
"<command>gdm-binary</command>, passing along any options. Before launching "
6464
"<command>gdm-binary</command>, the gdm wrapper script will source the "
6465
"<filename><etc>/profile</filename> file to set the standard system "
6466
"environment variables. In order to better support internationalization, it "
6467
"will also set the LC_MESSAGES environment variable to LANG if neither "
6468
"LC_MESSAGES or LC_ALL are set. If you really need to set some additional "
6469
"environment before launching GDM, you can do so in this script."
6470
msgstr ""
6471
6472
#: ../C/gdm.xml:5769(term)
6473
msgid "--help"
6474
msgstr ""
6475
6476
#: ../C/gdm.xml:5771(para)
6477
msgid "Gives a brief overview of the command line options."
6478
msgstr ""
6479
6480
#: ../C/gdm.xml:5778(term)
6481
msgid "--nodaemon"
6482
msgstr ""
6483
6484
#: ../C/gdm.xml:5780(para)
6485
msgid ""
6486
"If this option is specified, then GDM does not fork into the background when "
6487
"run. You can also use a single-dash version, \"-nodaemon\" for compatibility "
6488
"with other display managers."
6489
msgstr ""
6490
6491
#: ../C/gdm.xml:5790(term)
6492
msgid "--no-console"
6493
msgstr ""
6494
6495
#: ../C/gdm.xml:5792(para)
6496
msgid ""
6497
"Tell the daemon that it should not run anything on the console. This means "
6498
"that none of the local servers from the <filename>[servers]</filename> "
6499
"section will be run, and the console will not be used for communicating "
6500
"errors to the user. An empty <filename>[servers]</filename> section "
6501
"automatically implies this option."
6502
msgstr ""
6503
6504
#: ../C/gdm.xml:5804(term)
6505
msgid "--config=CONFIGFILE"
6506
msgstr ""
6507
6508
#: ../C/gdm.xml:5806(para)
6509
msgid "Specify an alternative configuration file."
6510
msgstr ""
6511
6512
#: ../C/gdm.xml:5813(term)
6513
msgid "--preserve-ld-vars"
6514
msgstr ""
6515
6516
#: ../C/gdm.xml:5815(para)
6517
msgid ""
6518
"When clearing the environment internally, preserve all variables starting "
6519
"with LD_. This is mostly for debugging purposes."
6520
msgstr ""
6521
6522
#: ../C/gdm.xml:5823(term)
6523
msgid "--version"
6524
msgstr ""
6525
6526
#: ../C/gdm.xml:5825(para)
6527
msgid "Print the version of the GDM daemon."
6528
msgstr ""
6529
6530
#: ../C/gdm.xml:5832(term)
6531
msgid "--wait-for-go"
6532
msgstr ""
6533
6534
#: ../C/gdm.xml:5834(para)
6535
msgid ""
6536
"If started with this option, gdm will init, but only start the first local "
6537
"display and then wait for a GO message in the fifo protocol. No greeter will "
6538
"be shown until the GO message is sent. Also flexiserver requests will be "
6539
"denied and XDMCP will not be started until GO is given. This is useful for "
6540
"initialization scripts which wish to start X early, but where you don't yet "
6541
"want the user to start logging in. So the script would send the GO to the "
6542
"fifo once it is ready and GDM will then continue. This functionality was "
6543
"added in version 2.5.90.0."
6544
msgstr ""
6545
6546
#: ../C/gdm.xml:5852(title)
6547
msgid "<command>gdmsetup</command> Command Line Options"
6548
msgstr ""
6549
6550
#: ../C/gdm.xml:5854(para)
6551
msgid ""
6552
"<command>gdmsetup</command> runs a graphical application for modifying the "
6553
"GDM configuration file. Normally on systems that support the PAM userhelper, "
6554
"this is setup such that when you run <command>gdmsetup</command> as an "
6555
"ordinary user, it will first ask you for your root password before starting. "
6556
"Otherwise, this application may only be run as root. This application "
6557
"supports standard GNOME options."
6558
msgstr ""
6559
6560
#: ../C/gdm.xml:5866(title)
6561
msgid "<command>gdm-restart</command> Command Line Options"
6562
msgstr ""
6563
6564
#: ../C/gdm.xml:5868(para)
6565
msgid ""
6566
"<command>gdm-restart</command> stops and restarts GDM by sending the GDM "
6567
"daemon a HUP signal. This command will immediately terminate all sessions "
6568
"and log out users currently logged in with GDM."
6569
msgstr ""
6570
6571
#: ../C/gdm.xml:5876(title)
6572
msgid "<command>gdm-safe-restart</command> Command Line Options"
6573
msgstr ""
6574
6575
#: ../C/gdm.xml:5878(para)
6576
msgid ""
6577
"<command>gdm-safe-restart</command> stops and restarts GDM by sending the "
6578
"GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out."
6579
msgstr ""
6580
6581
#: ../C/gdm.xml:5886(title)
6582
msgid "<command>gdm-stop</command> Command Line Options"
6583
msgstr ""
6584
6585
#: ../C/gdm.xml:5888(para)
6586
msgid ""
6587
"<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM "
6588
"signal."
6589
msgstr ""
6590
6591
#: ../C/gdm.xml:5896(title)
6592
msgid "GDM Internal Commands"
6593
msgstr ""
6594
6595
#: ../C/gdm.xml:5898(para)
6596
msgid ""
6597
"The GDM package provides the following different commands in "
6598
"<filename>libexecdir</filename> intended to be used by the gdm daemon "
6599
"process."
6600
msgstr ""
6601
6602
#: ../C/gdm.xml:5905(title)
6603
msgid ""
6604
"<command>gdmchooser</command> and <command>gdmlogin</command> Command Line "
6605
"Options"
6606
msgstr ""
6607
6608
#: ../C/gdm.xml:5908(para)
6609
msgid ""
6610
"The <command>gdmgreeter</command> and <command>gdmlogin</command> are two "
6611
"different login applications, either can be used by GDM. "
6612
"<command>gdmgreeter</command> is themeable with GDM themes while "
6613
"<command>gdmlogin</command> is themable with GTK+ themes. These applications "
6614
"are normally executed by the GDM daemon. Both commands support standard "
6615
"GNOME options."
6616
msgstr ""
6617
6618
#: ../C/gdm.xml:5919(title) ../C/gdm.xml:5929(title)
6619
msgid "<command>gdmchooser</command> Command Line Options"
6620
msgstr ""
6621
6622
#: ../C/gdm.xml:5921(para)
6623
msgid ""
6624
"The <command>gdmchooser</command> is the XDMCP chooser application. The "
6625
"<command>gdmchooser</command> is normally executed by the GDM daemon. It "
6626
"supports the following options for XDM compatibility. This command supports "
6627
"standard GNOME options."
6628
msgstr ""
6629
6630
#: ../C/gdm.xml:5932(term)
6631
msgid "--xdmaddress=SOCKET"
6632
msgstr ""
6633
6634
#: ../C/gdm.xml:5934(para)
6635
msgid "Socket for XDM communication."
6636
msgstr ""
6637
6638
#: ../C/gdm.xml:5941(term)
6639
msgid "--clientaddress=ADDRESS"
6640
msgstr ""
6641
6642
#: ../C/gdm.xml:5943(para)
6643
msgid ""
6644
"Client address to return in response to XDM. This option is for running "
6645
"gdmchooser with XDM, and is not used within GDM."
6646
msgstr ""
6647
6648
#: ../C/gdm.xml:5951(term)
6649
msgid "--connectionType=TYPE"
6650
msgstr ""
6651
6652
#: ../C/gdm.xml:5953(para)
6653
msgid ""
6654
"Connection type to return in response to XDM. This option is for running "
6655
"gdmchooser with XDM, and is not used within GDM."
6656
msgstr ""
6657
6658
#: ../C/gdm.xml:5963(command)
6659
msgid "gdm-ssh-session"
6660
msgstr ""
6661
6662
#: ../C/gdm.xml:5965(para)
6663
msgid ""
6664
"The <command>gdm-ssh-session</command> is normally executed by the GDM "
6665
"daemon when starting a secure remote connection through ssh. It does not "
6666
"take any options."
6667
msgstr ""
6668
6669
#: ../C/gdm.xml:5977(title)
6670
msgid "Themed Greeter"
6671
msgstr ""
6672
6673
#: ../C/gdm.xml:5979(para)
6674
msgid ""
6675
"This section describes the creation of themes for the Themed Greeter. For "
6676
"examples including screenshots, see the standard installed themes and the "
6677
"themes from <ulink type=\"http\" url=\"http://art.gnome.org/themes/"
6678
"gdm_greeter/\"> the theme website</ulink>."
6679
msgstr ""
6680
6681
#: ../C/gdm.xml:5988(title)
6682
msgid "Theme Overview"
6683
msgstr ""
6684
6685
#: ../C/gdm.xml:5990(para)
6686
msgid ""
6687
"GDM Themes can be created by creating an XML file that follows the "
6688
"specification in gui/greeter/greeter.dtd. Theme files are stored in the "
6689
"directory <filename><share>/gdm/themes/<theme_name></filename>. "
6690
"Usually this would be under <filename>/usr/share</filename>. The theme "
6691
"directory should contain a file called <filename>GdmGreeterTheme.desktop</"
6692
"filename> which has similar format to other .desktop files and looks like:"
6693
msgstr ""
6694
6695
#: ../C/gdm.xml:6001(screen)
6696
#, no-wrap
6697
msgid ""
6698
"\n"
6699
"[GdmGreeterTheme]\n"
6700
"Encoding=UTF-8\n"
6701
"Greeter=circles.xml\n"
6702
"Name=Circles\n"
6703
"Description=Theme with blue circles\n"
6704
"Author=Bond, James Bond\n"
6705
"Copyright=(c) 2002 Bond, James Bond\n"
6706
"Screenshot=screenshot.png\n"
6707
msgstr ""
6708
6709
#: ../C/gdm.xml:6012(para)
6710
msgid ""
6711
"The Name, Description, Author and Copyright fields can be translated just "
6712
"like the other <filename>.desktop</filename>files. All the files that are "
6713
"mentioned should be in the theme directory itself. The Screenshot field "
6714
"points to a file which should be a 200x150 screenshot of the theme in action "
6715
"(it is OK not to have one, but it makes it nicer for user). The Greeter "
6716
"field points to an XML file that contains the description of the theme. The "
6717
"description will be given later."
6718
msgstr ""
6719
6720
#: ../C/gdm.xml:6022(para)
6721
msgid ""
6722
"Once you have theme ready and installed you can test it with the installed "
6723
"<command>gdmthemetester</command> script. This script assumes that the X "
6724
"server supports a nested server command. This command takes two arguments, "
6725
"first the environment that should be used. This is one of console, console-"
6726
"timed, flexi, remote-flexi, xdmcp. Where console is a standard console "
6727
"login, console-timed is a console login with a timed login going on, flexi "
6728
"is for any local flexible display, remote-flexi is for flexi displays that "
6729
"are not local (such as an Xnest flexiserver run from a remote display) and "
6730
"xdmcp is for remote XDMCP connections. The second argument is the theme "
6731
"name. So for example to test how things look in the XDMCP mode with the "
6732
"circles theme you would run:"
6733
msgstr ""
6734
6735
#: ../C/gdm.xml:6038(command)
6736
msgid "gdmthemetester xdmcp circles"
6737
msgstr ""
6738
6739
#: ../C/gdm.xml:6041(para)
6740
msgid ""
6741
"Be sure to test all the environments with your theme, and make sure to test "
6742
"how the caps lock warning looks by pressing caps lock. This is also a good "
6743
"way to take screenshots, just take a screenshot of the nested display "
6744
"window. This can be done in GNOME by focusing the nested login window and "
6745
"pressing Alt-PrintScreen."
6746
msgstr ""
6747
6748
#: ../C/gdm.xml:6049(para)
6749
msgid ""
6750
"Once you have all this done, then make a tarball that contains the directory "
6751
"name (so that you could just untar it in the <filename><share>/gdm/"
6752
"themes</filename> directory). And this is the tarball you distribute and "
6753
"people can install from the graphical configuration application. You can do "
6754
"this with the commands: <screen>\n"
6755
"cd <share>/gdm/themes\n"
6756
"tar czvf <theme_name>.tar.gz <theme_name>/\n"
6757
"</screen>"
6758
msgstr ""
6759
6760
#: ../C/gdm.xml:6063(title)
6761
msgid "Detailed Description of Theme XML format"
6762
msgstr ""
6763
6764
#: ../C/gdm.xml:6066(title)
6765
msgid "greeter tag"
6766
msgstr ""
6767
6768
#: ../C/gdm.xml:6068(para)
6769
msgid ""
6770
"The GDM theme format is specified in XML format contained within a <"
6771
"greeter> tag. You may specify a GTK+ theme to be used with this theme by "
6772
"using the gtk-theme element in the greeter tag as in the following example."
6773
msgstr ""
6774
6775
#: ../C/gdm.xml:6075(screen)
6776
#, no-wrap
6777
msgid ""
6778
"\n"
6779
"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
6780
"<!DOCTYPE greeter SYSTEM \"greeter.dtd\">\n"
6781
"<greeter gtk-theme=\"Crux\">\n"
6782
"[...]\n"
6783
"</greeter>\n"
6784
msgstr ""
6785
6786
#: ../C/gdm.xml:6083(para)
6787
msgid ""
6788
"Contained within the greeter tag can be the nodes described in the next "
6789
"sections of this document. Some of these nodes are containers (box nodes, "
6790
"rect item nodes) which can be used to organize how to display the nodes that "
6791
"the user sees and interacts with (such as button, pixmap and entry item "
6792
"nodes)."
6793
msgstr ""
6794
6795
#: ../C/gdm.xml:6093(title)
6796
msgid "Box Nodes"
6797
msgstr ""
6798
6799
#: ../C/gdm.xml:6095(para)
6800
msgid ""
6801
"Box nodes are container nodes for item nodes. Box nodes are specified as "
6802
"follows: <screen>\n"
6803
"<box orientation=\"alignment\" min-width=\"num\"\n"
6804
"xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n"
6805
"homogeneous=\"bool\">\n"
6806
"</screen> Where \"num\" means number and bool means either \"true\" or "
6807
"\"false\" The alignment value can be either \"horizontal\" or \"vertical\". "
6808
"If you leave any property off it will default to zero or \"false\" in case "
6809
"of \"homogeneous\" and \"vertical\" for the orientation."
6810
msgstr ""
6811
6812
#: ../C/gdm.xml:6111(para)
6813
msgid ""
6814
"If the box is homogeneous then the children are allocated equal amount of "
6815
"space."
6816
msgstr ""
6817
6818
#: ../C/gdm.xml:6116(para)
6819
msgid ""
6820
"The \"min-width\" must be specified in pixels. Obviously there is also a "
6821
"corresponding \"min-height\" property as well."
6822
msgstr ""
6823
6824
#: ../C/gdm.xml:6124(title)
6825
msgid "Fixed Nodes"
6826
msgstr ""
6827
6828
#: ../C/gdm.xml:6126(para)
6829
msgid ""
6830
"Fixed is a container that has its children scattered about laid out with "
6831
"precise coordinates. The size of this container is the biggest rectangle "
6832
"that contains all the children. Fixed has no extra properties and so you "
6833
"just use: <screen>\n"
6834
"<fixed>\n"
6835
"</screen> Then you put other items with proper position nodes inside this."
6836
msgstr ""
6837
6838
#: ../C/gdm.xml:6137(para)
6839
msgid "The \"toplevel\" node is really just like a fixed node."
6840
msgstr ""
6841
6842
#: ../C/gdm.xml:6143(title)
6843
msgid "Item Nodes"
6844
msgstr ""
6845
6846
#: ../C/gdm.xml:6145(para)
6847
msgid ""
6848
"A GDM Theme is created by specifying a hierarchy of item and box nodes. Item "
6849
"nodes can have the following value for \"type\":"
6850
msgstr ""
6851
6852
#: ../C/gdm.xml:6153(term)
6853
msgid "button"
6854
msgstr ""
6855
6856
#: ../C/gdm.xml:6155(para)
6857
msgid ""
6858
"A button field. This field uses a GTK+ button. It is also possible to make a "
6859
"\"rect\" item act like a button by setting its button element to true. "
6860
"However it is better to use GTK+ buttons in GDM themes since these are "
6861
"accessible to users with disabilities. Also, GTK+ buttons can be themed. "
6862
"This feature is supported in GDM 2.14.6 and later."
6863
msgstr ""
6864
6865
#: ../C/gdm.xml:6167(term)
6866
msgid "entry"
6867
msgstr ""
6868
6869
#: ../C/gdm.xml:6169(para)
6870
msgid "Text entry field."
6871
msgstr ""
6872
6873
#: ../C/gdm.xml:6176(term)
6874
msgid "label"
6875
msgstr ""
6876
6877
#: ../C/gdm.xml:6178(para)
6878
msgid "A text label. Must have a \"text\" node to specify the text."
6879
msgstr ""
6880
6881
#: ../C/gdm.xml:6186(term)
6882
msgid "list"
6883
msgstr ""
6884
6885
#: ../C/gdm.xml:6188(para)
6886
msgid ""
6887
"A face browser widget. Only useful if the face browser is enabled via the "
6888
"configuration."
6889
msgstr ""
6890
6891
#: ../C/gdm.xml:6196(term)
6892
msgid "pixmap"
6893
msgstr ""
6894
6895
#: ../C/gdm.xml:6198(para)
6896
msgid ""
6897
"An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, Tiff, "
6898
"etc...)"
6899
msgstr ""
6900
6901
#: ../C/gdm.xml:6206(term)
6902
msgid "rect"
6903
msgstr ""
6904
6905
#: ../C/gdm.xml:6208(para)
6906
msgid "Rectangle."
6907
msgstr ""
6908
6909
#: ../C/gdm.xml:6215(term)
6910
msgid "svg"
6911
msgstr ""
6912
6913
#: ../C/gdm.xml:6217(para)
6914
msgid "Scaled Vector Graphic image."
6915
msgstr ""
6916
6917
#: ../C/gdm.xml:6224(para)
6918
msgid ""
6919
"For example: <screen>\n"
6920
"<item type=\"label\">\n"
6921
"</screen> Items can specify ID values which gives them a specific look and "
6922
"feel or formatting. Furthermore you can customize the login process by "
6923
"adding custom widgets with custom id's for some items (currently only the "
6924
"list item)"
6925
msgstr ""
6926
6927
#: ../C/gdm.xml:6235(para)
6928
msgid "Entry items can have id values as follows:"
6929
msgstr ""
6930
6931
#: ../C/gdm.xml:6241(term)
6932
msgid "user-pw-entry"
6933
msgstr ""
6934
6935
#: ../C/gdm.xml:6243(para)
6936
msgid ""
6937
"Entry field for userid and password entry. This is the field used for "
6938
"responses for the PAM/GDM questions (Username, Password, etc..)."
6939
msgstr ""
6940
6941
#: ../C/gdm.xml:6252(para)
6942
msgid ""
6943
"List items by default display as lists, but the combo=\"true\" attribute can "
6944
"be used to specify combo box style (combo style supported since GDM 2.16.2). "
6945
"Some predefined lists may be included in a theme by using the following id "
6946
"values. Customized lists may also be defined, which are explained below."
6947
msgstr ""
6948
6949
#: ../C/gdm.xml:6262(term)
6950
msgid "session"
6951
msgstr ""
6952
6953
#: ../C/gdm.xml:6264(para)
6954
msgid ""
6955
"A list of available sessions, which allows the user to pick the session to "
6956
"use. Supported since GDM 2.16.2."
6957
msgstr ""
6958
6959
#: ../C/gdm.xml:6274(term)
6960
msgid "language"
6961
msgstr ""
6962
6963
#: ../C/gdm.xml:6276(para)
6964
msgid ""
6965
"A list of available languages, which allows the user to pick the language to "
6966
"use. Supported since GDM 2.16.2."
6967
msgstr ""
6968
6969
#: ../C/gdm.xml:6286(term)
6970
msgid "userlist"
6971
msgstr ""
6972
6973
#: ../C/gdm.xml:6288(para)
6974
msgid ""
6975
"A Face Browser list, so that users can pick their username by clicking on "
6976
"this instead of typing. This obviously exposes the usernames to viewers of "
6977
"the login screen, and is not recommended for users who feel that this "
6978
"reduces security. The face browser does not support combo box style."
6979
msgstr ""
6980
6981
#: ../C/gdm.xml:6301(term)
6982
msgid "userlist-rect"
6983
msgstr ""
6984
6985
#: ../C/gdm.xml:6303(para)
6986
msgid ""
6987
"This id can be specified for the <rect> object containing the userlist "
6988
"and if the userlist is empty then this rectangle will not be shown. This "
6989
"allows the theme to define something like an area with a different color and/"
6990
"or alpha to surround the userlist, but only if there are users to display. "
6991
"Supported since 2.16.2."
6992
msgstr ""
6993
6994
#: ../C/gdm.xml:6315(para)
6995
msgid ""
6996
"Furthermore, you can have an arbitrary id (I'd recommend starting the id "
6997
"with 'custom' not to conflict with future additions to this spec) and ask "
6998
"extra information of the user. See the section 'Custom Widgetry'"
6999
msgstr ""
7000
7001
#: ../C/gdm.xml:6322(para)
7002
msgid "Label items can have id values as follows:"
7003
msgstr ""
7004
7005
#: ../C/gdm.xml:6328(term)
7006
msgid "clock"
7007
msgstr ""
7008
7009
#: ../C/gdm.xml:6330(para)
7010
msgid "Label that displays the date and time."
7011
msgstr ""
7012
7013
#: ../C/gdm.xml:6337(term)
7014
msgid "pam-prompt"
7015
msgstr ""
7016
7017
#: ../C/gdm.xml:6339(para)
7018
msgid ""
7019
"Label that displays the PAM prompt. This is the prompt that PAM uses to ask "
7020
"for username, password, etc..."
7021
msgstr ""
7022
7023
#: ../C/gdm.xml:6347(term)
7024
msgid "pam-error"
7025
msgstr ""
7026
7027
#: ../C/gdm.xml:6349(para)
7028
msgid "Label that displayst PAM/GDM error messages. Such as when user can't log in."
7029
msgstr ""
7030
7031
#: ../C/gdm.xml:6357(term)
7032
msgid "pam-error-logo"
7033
msgstr ""
7034
7035
#: ../C/gdm.xml:6359(para)
7036
msgid ""
7037
"An image that will be displayed only when a pam-error message is being "
7038
"displayed. This is useful for displaying an \"Attention\" icon, for example. "
7039
"This feature is supported in GDM 2.14.6 and later."
7040
msgstr ""
7041
7042
#: ../C/gdm.xml:6369(term)
7043
msgid "pam-message"
7044
msgstr ""
7045
7046
#: ../C/gdm.xml:6371(para)
7047
msgid ""
7048
"Label that displays the PAM message. These are messages that PAM/GDM gives "
7049
"about state of the account, help about the prompts and other information."
7050
msgstr ""
7051
7052
#: ../C/gdm.xml:6380(term)
7053
msgid "timed-label"
7054
msgstr ""
7055
7056
#: ../C/gdm.xml:6382(para)
7057
msgid "Label that displays timed login information."
7058
msgstr ""
7059
7060
#: ../C/gdm.xml:6389(para)
7061
msgid "Rectangles can have id values as follows:"
7062
msgstr ""
7063
7064
#: ../C/gdm.xml:6395(term)
7065
msgid "caps-lock-warning"
7066
msgstr ""
7067
7068
#: ../C/gdm.xml:6397(para)
7069
msgid ""
7070
"Displays an icon that shows if the CAPS LOCK key is depressed. This "
7071
"rectangle will be hidden/shown appropriately"
7072
msgstr ""
7073
7074
#: ../C/gdm.xml:6406(para)
7075
msgid ""
7076
"If an item is of type rect, the item can be a button. Buttons must also "
7077
"include a \"button\" value as follows: <screen>\n"
7078
"<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n"
7079
"</screen>"
7080
msgstr ""
7081
7082
#: ../C/gdm.xml:6414(para)
7083
msgid "Possible values for button ids are as follows."
7084
msgstr ""
7085
7086
#: ../C/gdm.xml:6420(term)
7087
msgid "chooser_button"
7088
msgstr ""
7089
7090
#: ../C/gdm.xml:6422(para)
7091
msgid "Runs the XDMCP chooser."
7092
msgstr ""
7093
7094
#: ../C/gdm.xml:6429(term)
7095
msgid "config_button"
7096
msgstr ""
7097
7098
#: ../C/gdm.xml:6431(para)
7099
msgid "Runs the GDM configuration application."
7100
msgstr ""
7101
7102
#: ../C/gdm.xml:6438(term)
7103
msgid "custom_cmd_button[0-9]"
7104
msgstr ""
7105
7106
#: ../C/gdm.xml:6440(para)
7107
msgid "Runs the <filename>n-th</filename> custom command."
7108
msgstr ""
7109
7110
#: ../C/gdm.xml:6447(term)
7111
msgid "disconnect_button"
7112
msgstr ""
7113
7114
#: ../C/gdm.xml:6449(para)
7115
msgid "Disconnect from remote session."
7116
msgstr ""
7117
7118
#: ../C/gdm.xml:6456(term)
7119
msgid "language_button"
7120
msgstr ""
7121
7122
#: ../C/gdm.xml:6458(para)
7123
msgid "Displays the language selection dialog."
7124
msgstr ""
7125
7126
#: ../C/gdm.xml:6465(term)
7127
msgid "halt_button"
7128
msgstr ""
7129
7130
#: ../C/gdm.xml:6467(para)
7131
msgid "Halt (shuts down) the system."
7132
msgstr ""
7133
7134
#: ../C/gdm.xml:6474(term)
7135
msgid "reboot_button"
7136
msgstr ""
7137
7138
#: ../C/gdm.xml:6476(para)
7139
msgid "Restart the system."
7140
msgstr ""
7141
7142
#: ../C/gdm.xml:6483(term)
7143
msgid "session_button"
7144
msgstr ""
7145
7146
#: ../C/gdm.xml:6485(para)
7147
msgid "List and select from available sessions."
7148
msgstr ""
7149
7150
#: ../C/gdm.xml:6492(term)
7151
msgid "suspend_button"
7152
msgstr ""
7153
7154
#: ../C/gdm.xml:6494(para)
7155
msgid "Suspend the system."
7156
msgstr ""
7157
7158
#: ../C/gdm.xml:6501(term)
7159
msgid "system_button"
7160
msgstr ""
7161
7162
#: ../C/gdm.xml:6503(para)
7163
msgid ""
7164
"Perform halt/restart/suspend/etc. options (if allowed by GDM configuration). "
7165
"Also allows user to run configurator if user enters root password (again if "
7166
"allowed by GDM configuration). This is usually now labeled Actions, and "
7167
"referred to as the Actions menu."
7168
msgstr ""
7169
7170
#: ../C/gdm.xml:6514(para)
7171
msgid ""
7172
"By default, the GDM login screen will disappear after authentication. This "
7173
"can result in flicker between the login screen and the session. The "
7174
"\"background\" property allows users to specify what elements of the theme "
7175
"are the background image. When used, this will cause GDM to remove all non-"
7176
"background items from the display and render the remaining \"background\" "
7177
"items to the root window. This can be used to create a smooth transition "
7178
"between the login screen and the session. For example, if the GDM theme and "
7179
"the session use the same background, then this will make the background "
7180
"apear seamless."
7181
msgstr ""
7182
7183
#: ../C/gdm.xml:6527(para)
7184
msgid ""
7185
"Item nodes may specify a \"background\" property which can be set to \"true"
7186
"\" or \"false\" (not setting this property is equivalent to \"false\"), as "
7187
"follows:"
7188
msgstr ""
7189
7190
#: ../C/gdm.xml:6533(screen)
7191
#, no-wrap
7192
msgid ""
7193
"\n"
7194
"<item type=\"rect\" background=\"true\">\n"
7195
" <normal file=\"background.svg\"/>\n"
7196
" <pos x=\"0\" y=\"0\" width=\"100%\" height=\"-75\"/>\n"
7197
"</item>\n"
7198
msgstr ""
7199
7200
#: ../C/gdm.xml:6540(para)
7201
msgid ""
7202
"If no item node has \"background\" property set, then the background is not "
7203
"modified when greeter exits."
7204
msgstr ""
7205
7206
#: ../C/gdm.xml:6545(para)
7207
msgid ""
7208
"To use a different background for login transition than the one used for "
7209
"login, the theme should specify two item nodes (which could contain pixmaps "
7210
"or svg images, for example). The item which corresponds to the greeter "
7211
"background should not have the \"background\" property while the item which "
7212
"corresponds to the transition background should have the \"background\" "
7213
"property. For instance :"
7214
msgstr ""
7215
7216
#: ../C/gdm.xml:6554(screen)
7217
#, no-wrap
7218
msgid ""
7219
"\n"
7220
"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
7221
"<!DOCTYPE greeter SYSTEM \"greeter.dtd\">\n"
7222
" <greeter>\n"
7223
"\n"
7224
" <item type=\"rect\" background=\"true\">\n"
7225
" <normal file=\"background_for_login.svg\"/>\n"
7226
" <pos x=\"0\" y=\"0\" width=\"100%\" height=\"100%\"/>\n"
7227
" </item>\n"
7228
" <item type=\"rect\">\n"
7229
" <normal file=\"background_for_greeter.svg\"/>\n"
7230
" <pos x=\"0\" y=\"0\" width=\"100%\" height=\"100%\"/>\n"
7231
" </item>\n"
7232
"[...]\n"
7233
"</greeter>\n"
7234
msgstr ""
7235
7236
#: ../C/gdm.xml:6573(title)
7237
msgid "Position Node"
7238
msgstr ""
7239
7240
#: ../C/gdm.xml:6575(para)
7241
msgid ""
7242
"Each item can specify its position and size via the \"pos\" node. For "
7243
"example: <screen>\n"
7244
"<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n"
7245
"</screen>"
7246
msgstr ""
7247
7248
#: ../C/gdm.xml:6583(para)
7249
msgid ""
7250
"Both position and size can be given in percent and it will be taken as the "
7251
"percentage of the size of the current container. For toplevel items it's the "
7252
"percentage of the whole screen."
7253
msgstr ""
7254
7255
#: ../C/gdm.xml:6589(para)
7256
msgid ""
7257
"For x and y, you can also specify a negative position which means position "
7258
"from the right or bottom edge. But this only applies with absolute "
7259
"coordinates. With percentage you can specify negative position and it will "
7260
"be still from the same edge."
7261
msgstr ""
7262
7263
#: ../C/gdm.xml:6596(para)
7264
msgid ""
7265
"The position also specifies the anchor of the item, this can be \"n\" \"ne\" "
7266
"\"e\" \"se\" \"s\" \"sw\" \"w\" and \"nw\" or \"center\" which stand for the "
7267
"different edges/corners or \"center\" for center. For example: <screen>\n"
7268
"<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/>\n"
7269
"</screen>"
7270
msgstr ""
7271
7272
#: ../C/gdm.xml:6607(para)
7273
msgid ""
7274
"If the item contains a box, you can specify width and height to be \"box\" "
7275
"to mean that they are supposed to be the width and height of the box, that "
7276
"is the items in the box plus the padding."
7277
msgstr ""
7278
7279
#: ../C/gdm.xml:6613(para)
7280
msgid ""
7281
"If the item contains an SVG image, you can specify width and height to be "
7282
"\"scale\" to mean that the SVG image should be scaled to fit the requested "
7283
"area."
7284
msgstr ""
7285
7286
#: ../C/gdm.xml:6619(para)
7287
msgid ""
7288
"You can also specify an \"expand\" property to either be \"true\" or false. "
7289
"If true then the child will be expanded in the box as much as possible (that "
7290
"is it will be given more space if available)."
7291
msgstr ""
7292
7293
#: ../C/gdm.xml:6626(para)
7294
msgid ""
7295
"There are two extra properties you can specify (as of 2.4.4.3) for labels "
7296
"(and labels only). The first is \"max-width\" which will specify the maximum "
7297
"width of the label in pixels. And the second is \"max-screen-percent-width\" "
7298
"which specifies the maximum percentage of the screen width that the label "
7299
"can occupy. By default no label will occupy more then 90% of the screen by "
7300
"width. An example may be: <screen>\n"
7301
"<item type=\"label\">\n"
7302
"<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n"
7303
"</screen>"
7304
msgstr ""
7305
7306
#: ../C/gdm.xml:6642(title)
7307
msgid "Show Node"
7308
msgstr ""
7309
7310
#: ../C/gdm.xml:6644(para)
7311
msgid ""
7312
"Some items may only display in certain modes, like when doing a remote "
7313
"display. Multiple values can be specified and must be separated with commas. "
7314
"The following values are possible:"
7315
msgstr ""
7316
7317
#: ../C/gdm.xml:6650(para)
7318
msgid "<filename>console</filename> - In console mode."
7319
msgstr ""
7320
7321
#: ../C/gdm.xml:6653(para)
7322
msgid "<filename>console-fixed</filename> - In console non-flexi mode."
7323
msgstr ""
7324
7325
#: ../C/gdm.xml:6656(para)
7326
msgid "<filename>console-flexi</filename> - In console & flexi mode."
7327
msgstr ""
7328
7329
#: ../C/gdm.xml:6659(para)
7330
msgid "<filename>flexi</filename> - In flexi mode."
7331
msgstr ""
7332
7333
#: ../C/gdm.xml:6662(para)
7334
msgid "<filename>remote</filename> - In remote mode."
7335
msgstr ""
7336
7337
#: ../C/gdm.xml:6665(para)
7338
msgid "<filename>remote-flexi</filename> - In remote & flexi mode."
7339
msgstr ""
7340
7341
#: ../C/gdm.xml:6669(para)
7342
msgid ""
7343
"For example: <screen>\n"
7344
"<show modes=\"flexi,remote\"/>\n"
7345
"</screen>"
7346
msgstr ""
7347
7348
#: ../C/gdm.xml:6676(para)
7349
msgid ""
7350
"You can also specify the \"type\" value to indicate that certain items "
7351
"should only be displayed if the type is true. Valid values include the "
7352
"following:"
7353
msgstr ""
7354
7355
#: ../C/gdm.xml:6682(para)
7356
msgid ""
7357
"<filename>chooser</filename>, if ChooserButton is set to \"true\" in the GDM "
7358
"configuration."
7359
msgstr ""
7360
7361
#: ../C/gdm.xml:6686(para)
7362
msgid ""
7363
"<filename>config</filename>, if ConfigAvailable is set to \"true\" in the "
7364
"GDM configuration."
7365
msgstr ""
7366
7367
#: ../C/gdm.xml:6690(para)
7368
msgid ""
7369
"<filename>custom_cmd[0-9]</filename>, if <filename>n-th</filename> "
7370
"CustomCommand is specified in the GDM configuration."
7371
msgstr ""
7372
7373
#: ../C/gdm.xml:6694(para)
7374
msgid ""
7375
"<filename>halt</filename>, if HaltDaemon is specified in the GDM "
7376
"configuration."
7377
msgstr ""
7378
7379
#: ../C/gdm.xml:6698(para)
7380
msgid ""
7381
"<filename>reboot</filename>, if RebootCommand is specified in the GDM "
7382
"configuration."
7383
msgstr ""
7384
7385
#: ../C/gdm.xml:6702(para)
7386
msgid ""
7387
"<filename>suspend</filename>, if SuspendCommand is specified in the GDM "
7388
"configuration."
7389
msgstr ""
7390
7391
#: ../C/gdm.xml:6706(para)
7392
msgid ""
7393
"<filename>system</filename>, if SystemMenu is specified in the GDM "
7394
"configuration."
7395
msgstr ""
7396
7397
#: ../C/gdm.xml:6710(para)
7398
msgid ""
7399
"<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in the "
7400
"GDM configuration."
7401
msgstr ""
7402
7403
#: ../C/gdm.xml:6715(para)
7404
msgid ""
7405
"For example: <screen>\n"
7406
"<show modes=\"console\" type=\"system\"/>\n"
7407
"</screen>"
7408
msgstr ""
7409
7410
#: ../C/gdm.xml:6722(para)
7411
msgid ""
7412
"Alternatively, you can specify a \"min-screen-width\" or \"min-screen-height"
7413
"\" value to indicate that certain items should only be displayed if the "
7414
"screen resolution is the at least the given required size."
7415
msgstr ""
7416
7417
#: ../C/gdm.xml:6729(para)
7418
msgid ""
7419
"For example: <screen>\n"
7420
"<show min-screen-height=\"768\"/>\n"
7421
"</screen>"
7422
msgstr ""
7423
7424
#: ../C/gdm.xml:6736(para)
7425
msgid ""
7426
"Note that if SystemMenu is off then the halt, restart, suspend, chooser and "
7427
"config choices will not be shown, so this is a global toggle for them all. "
7428
"See some of the standard themes for how the show modes are used."
7429
msgstr ""
7430
7431
#: ../C/gdm.xml:6745(title)
7432
msgid "Normal/Active/Prelight Nodes"
7433
msgstr ""
7434
7435
#: ../C/gdm.xml:6747(para)
7436
msgid ""
7437
"Depending on the item type (except for userlist - refer to Color node "
7438
"below), it can specify its color, font, or image via the following tags:"
7439
msgstr ""
7440
7441
#: ../C/gdm.xml:6753(para)
7442
msgid "<filename>normal</filename> - normal state."
7443
msgstr ""
7444
7445
#: ../C/gdm.xml:6756(para)
7446
msgid "<filename>active</filename> - when the item has active focus."
7447
msgstr ""
7448
7449
#: ../C/gdm.xml:6759(para)
7450
msgid "<filename>prelight</filename> - when the mouse is hovering over the item."
7451
msgstr ""
7452
7453
#: ../C/gdm.xml:6764(para)
7454
msgid ""
7455
"When item is \"rect\" (alpha can be omitted and defaults to 0.0): <screen>\n"
7456
"<normal color=\"#ffffff\" alpha=\"0.0\">\n"
7457
"</screen>"
7458
msgstr ""
7459
7460
#: ../C/gdm.xml:6772(para)
7461
msgid ""
7462
"When item is \"label\" <screen>\n"
7463
"<normal color=\"#ffffff\" font=\"Sans 14\"/>\n"
7464
"</screen>"
7465
msgstr ""
7466
7467
#: ../C/gdm.xml:6779(para)
7468
msgid ""
7469
"When the item type is \"pixmap\" or \"SVG\", then the normal, active, and "
7470
"prelight tags specify the images to use as follows: <screen>\n"
7471
"<normal file=\"picture.png\" tint=\"#dddddd\"/>\n"
7472
"</screen>"
7473
msgstr ""
7474
7475
#: ../C/gdm.xml:6788(para)
7476
msgid ""
7477
"Note that relative pathnames are assumed to be in the same directory as the "
7478
"theme <filename>.xml</filename> file in <filename><share>/gdm/themes/"
7479
"<theme_name></filename>."
7480
msgstr ""
7481
7482
#: ../C/gdm.xml:6794(para)
7483
msgid ""
7484
"Note that alternative image file can be specified using the altfile[n] "
7485
"property. GDM will use the last valid image filename specified. For example: "
7486
"<screen>\n"
7487
"<normal file=\"picture.png\" altfile1=\"distribution-blah-image.png\" "
7488
"altfile2=\"distribution-foo-image.png\"/>\n"
7489
"</screen> If <filename>distribution-foo-image.png</filename> is a valid "
7490
"image filename it will be used. Otherwise distribution-blah-image.png will "
7491
"be used if valid. This feature supported since 2.16.3."
7492
msgstr ""
7493
7494
#: ../C/gdm.xml:6809(title)
7495
msgid "Face Browser Icon/Label Color Nodes"
7496
msgstr ""
7497
7498
#: ../C/gdm.xml:6811(para)
7499
msgid ""
7500
"If the item type is of userlist, then the background color for the icon and "
7501
"label can be set separately via the the following tag:"
7502
msgstr ""
7503
7504
#: ../C/gdm.xml:6817(screen)
7505
#, no-wrap
7506
msgid ""
7507
"\n"
7508
"<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n"
7509
msgstr ""
7510
7511
#: ../C/gdm.xml:6824(title)
7512
msgid "Text Node"
7513
msgstr ""
7514
7515
#: ../C/gdm.xml:6826(para)
7516
msgid ""
7517
"Text tags are used by labels. They can be used to display localized text as "
7518
"follows (if the \"xml:lang\" attribute is omitted, the C locale is assumed): "
7519
"<screen>\n"
7520
"<text xml:lang=\"fr\">Option</text>\n"
7521
"</screen>"
7522
msgstr ""
7523
7524
#: ../C/gdm.xml:6835(para)
7525
msgid ""
7526
"You can include pango markup in the text nodes for labels, however you must "
7527
"encode it. So for example to have the label of \"foo<sup>bar</"
7528
"sup>\", you must type: <screen>\n"
7529
"<text>\"foo<sup>bar</sup>\"</text>\n"
7530
"</screen>"
7531
msgstr ""
7532
7533
#: ../C/gdm.xml:6844(para)
7534
msgid ""
7535
"Text nodes can contain the following special character sequences which will "
7536
"be translated as follows:"
7537
msgstr ""
7538
7539
#: ../C/gdm.xml:6849(para)
7540
msgid "%% - A literal % character"
7541
msgstr ""
7542
7543
#: ../C/gdm.xml:6852(para)
7544
msgid ""
7545
"%c - Clock time. Only labels with the \"clock\" id will update automatically "
7546
"every second. Other labels will contain a static timestamp."
7547
msgstr ""
7548
7549
#: ../C/gdm.xml:6857(para)
7550
msgid "%d - Display name (DISPLAY environment variable)"
7551
msgstr ""
7552
7553
#: ../C/gdm.xml:6860(para)
7554
msgid "%h - Hostname (gethostname output)"
7555
msgstr ""
7556
7557
#: ../C/gdm.xml:6863(para)
7558
msgid "%m - Machine name (uname.machine output)"
7559
msgstr ""
7560
7561
#: ../C/gdm.xml:6866(para)
7562
msgid "%n - Node name (uname.nodename output)"
7563
msgstr ""
7564
7565
#: ../C/gdm.xml:6869(para)
7566
msgid "%o - Domain name (getdomainname output)"
7567
msgstr ""
7568
7569
#: ../C/gdm.xml:6872(para)
7570
msgid "%r - Release name (uname.release output)"
7571
msgstr ""
7572
7573
#: ../C/gdm.xml:6875(para)
7574
msgid "%s - System name (uname.sysname output)"
7575
msgstr ""
7576
7577
#: ../C/gdm.xml:6878(para)
7578
msgid ""
7579
"%t - Current timed delay value from configuration file (0 if off) followed "
7580
"by the word \"seconds\" if value is greater than 1 or the word \"second\" if "
7581
"the value is 1. This character sequence is intended to be only used "
7582
"internally to display the \"timed-label\" message, which is automatically "
7583
"updated every second."
7584
msgstr ""
7585
7586
#: ../C/gdm.xml:6886(para)
7587
msgid ""
7588
"%u - Timed username value from configuration file (empty if off) This "
7589
"character sequence is intended to be only used internally to display the "
7590
"\"timed-label\" message, which is automatically updated every second."
7591
msgstr ""
7592
7593
#: ../C/gdm.xml:6892(para)
7594
msgid "\\n - Carriage return"
7595
msgstr ""
7596
7597
#: ../C/gdm.xml:6895(para)
7598
msgid ""
7599
"_ - An underscore causes the following character to be underlined. If it "
7600
"precedes a % character sequence, the string that replaces the character "
7601
"sequence is underlined."
7602
msgstr ""
7603
7604
#: ../C/gdm.xml:6903(title)
7605
msgid "Stock node"
7606
msgstr ""
7607
7608
#: ../C/gdm.xml:6905(para)
7609
msgid ""
7610
"Certain common localized labels can be specified via the stock tags. The "
7611
"\"text\" tag is ignored if the \"stock\" tag is used. You should really use "
7612
"the stock labels rather then just putting all the translations into the "
7613
"themes. This gives faster load times and likely better translations. The "
7614
"following values are valid:"
7615
msgstr ""
7616
7617
#: ../C/gdm.xml:6914(para)
7618
msgid "<filename>cancel</filename>, _(\"_Cancel\""
7619
msgstr ""
7620
7621
#: ../C/gdm.xml:6917(para)
7622
msgid "<filename>caps-lock-warning</filename>, _(\"Caps Lock is on.\""
7623
msgstr ""
7624
7625
#: ../C/gdm.xml:6921(para)
7626
msgid "<filename>chooser</filename>, _(\"Remote Login via _XDMCP\""
7627
msgstr ""
7628
7629
#: ../C/gdm.xml:6924(para)
7630
msgid "<filename>config</filename>, _(\"_Configure\""
7631
msgstr ""
7632
7633
#: ../C/gdm.xml:6927(para)
7634
msgid "<filename>custom_cmd[0-9]</filename>, getting label from config file"
7635
msgstr ""
7636
7637
#: ../C/gdm.xml:6930(para)
7638
msgid "<filename>disconnect</filename>, _(\"D_isconnect\""
7639
msgstr ""
7640
7641
#: ../C/gdm.xml:6933(para)
7642
msgid "<filename>halt</filename>, _(\"Shut _Down\""
7643
msgstr ""
7644
7645
#: ../C/gdm.xml:6936(para)
7646
msgid "<filename>language</filename>, _(\"_Language\""
7647
msgstr ""
7648
7649
#: ../C/gdm.xml:6939(para)
7650
msgid "<filename>ok</filename>, _(\"_OK\""
7651
msgstr ""
7652
7653
#: ../C/gdm.xml:6942(para)
7654
msgid "<filename>options</filename>, _(\"_Options\""
7655
msgstr ""
7656
7657
#: ../C/gdm.xml:6945(para)
7658
msgid "<filename>quit</filename>, _(\"_Quit\""
7659
msgstr ""
7660
7661
#: ../C/gdm.xml:6948(para)
7662
msgid "<filename>reboot</filename>, _(\"_Restart\""
7663
msgstr ""
7664
7665
#: ../C/gdm.xml:6951(para)
7666
msgid "<filename>session</filename>, _(\"_Session\""
7667
msgstr ""
7668
7669
#: ../C/gdm.xml:6954(para)
7670
msgid "<filename>startagain</filename>, _(\"_Start Again\""
7671
msgstr ""
7672
7673
#: ../C/gdm.xml:6957(para)
7674
msgid "<filename>suspend</filename>, _(\"Sus_pend\""
7675
msgstr ""
7676
7677
#: ../C/gdm.xml:6960(para)
7678
msgid "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\""
7679
msgstr ""
7680
7681
#: ../C/gdm.xml:6964(para)
7682
msgid "<filename>timed-label</filename>, _(\"User %u will login in %t\""
7683
msgstr ""
7684
7685
#: ../C/gdm.xml:6968(para)
7686
msgid "<filename>username-label</filename>, _(\"Username:\""
7687
msgstr ""
7688
7689
#: ../C/gdm.xml:6971(para)
7690
msgid "<filename>welcome-label</filename>, _(\"Welcome to %n\""
7691
msgstr ""
7692
7693
#: ../C/gdm.xml:6975(para)
7694
msgid ""
7695
"For example: <screen>\n"
7696
"<stock type=\"welcome-label\">\n"
7697
"</screen>"
7698
msgstr ""
7699
7700
#: ../C/gdm.xml:6984(title)
7701
msgid "Custom Widgetry"
7702
msgstr ""
7703
7704
#: ../C/gdm.xml:6986(para)
7705
msgid ""
7706
"Currently there is one item which is customizable and this is the list item. "
7707
"If you need to ask the user extra things, such as to pick from a list of "
7708
"places to log into, or set of custom login sessions you can setup the list "
7709
"item and add listitem children that describe the choices. Each listitem must "
7710
"have an id and a text child. The choice will be recorded in the file "
7711
"<filename><ServAuthDir>/<display>.GreeterInfo</filename> as "
7712
"<filename><list id>=<listitem id></filename>."
7713
msgstr ""
7714
7715
#: ../C/gdm.xml:6997(para)
7716
msgid ""
7717
"For example suppose we are on display :0, <filename>ServAuthDir</filename> "
7718
"is <filename><var>/lib/gdm</filename> and we have the following in the "
7719
"theme:"
7720
msgstr ""
7721
7722
#: ../C/gdm.xml:7004(screen)
7723
#, no-wrap
7724
msgid ""
7725
"\n"
7726
"<item type=\"list\" id=\"custom-config\">\n"
7727
"<pos anchor=\"nw\" x=\"1\" y=\"1\" height=\"200\" width=\"100\">\n"
7728
"<listitem id=\"foo\">\n"
7729
"<text>Foo</text>\n"
7730
"</listitem>\n"
7731
"<listitem id=\"bar\">\n"
7732
"<text>Bar</text>\n"
7733
"</listitem>\n"
7734
"</item>\n"
7735
msgstr ""
7736
7737
#: ../C/gdm.xml:7016(para)
7738
msgid ""
7739
"Then if the user chooses 'Foo' then <filename><var>/lib/gdm/:0."
7740
"GreeterInfo</filename> will contain: <screen>\n"
7741
"custom-config=foo\n"
7742
"</screen>"
7743
msgstr ""
7744
7745
#: ../C/gdm.xml:7028(title)
7746
msgid "Accessibility"
7747
msgstr ""
7748
7749
#: ../C/gdm.xml:7029(para)
7750
msgid ""
7751
"GDM supports \"Accessible Login\", allowing users to log into their desktop "
7752
"session even if they cannot easily use the screen, mouse, or keyboard in the "
7753
"usual way. Accessible Technology (AT) programs such as <command>GOK</"
7754
"command> (on-screen keyboard) and <command>orca</command> (magnifier and "
7755
"text-to-speech) are supported. The \"GTK+ Greeter\" best supports "
7756
"accessibility, so it is recommended for accessibility support. The \"Themed "
7757
"Greeter\" supports some accessibility features and may be usable by some "
7758
"users. But some AT programs, such as <command>GOK</command>, do not yet work "
7759
"with the \"Themed Greeter\"."
7760
msgstr ""
7761
7762
#: ../C/gdm.xml:7042(para)
7763
msgid ""
7764
"Accessibility is enabled by specifying the \"GTK+ Greeter\" in the \"Local\" "
7765
"tab for the console display and specifying the \"GTK+ Greeter\" in the "
7766
"\"Remote\" tab for remote displays. Or you can modify the <filename>Greeter</"
7767
"filename> and <filename>RemoteGreeter</filename> configuration options by "
7768
"hand to be <command>/usr/lib/gdmlogin</command>."
7769
msgstr ""
7770
7771
#: ../C/gdm.xml:7051(para)
7772
msgid ""
7773
"The GDM greeter programs support the ability to launch AT's at login time "
7774
"via configurable \"gestures\". These gestures can be defined to be standard "
7775
"keyboard hotkeys, switch device event, or mouse motion events. When using "
7776
"the \"GTK+ Greeter\", the user may also change the visual appearance of the "
7777
"login UI. For example, to use a higher-contrast color scheme for better "
7778
"visibility."
7779
msgstr ""
7780
7781
#: ../C/gdm.xml:7060(para)
7782
msgid ""
7783
"Note that <command>gdmsetup</command> does not yet work with accessibility, "
7784
"so that users who require AT programs should only configure GDM by editing "
7785
"the ASCII files directly."
7786
msgstr ""
7787
7788
#: ../C/gdm.xml:7067(title)
7789
msgid "Accessibility Configuration"
7790
msgstr ""
7791
7792
#: ../C/gdm.xml:7069(para)
7793
msgid ""
7794
"In order to enable Accessible Login, the system administrator must make some "
7795
"changes to the default login configuration by manually modifying three human-"
7796
"readable configuration files, stored in the GDM Custom Configuration File, "
7797
"AccessKeyMouseEvents File, and AccessDwellMouseEvents File. The "
7798
"AccessKeyMouseEvents and AccessDwellMouseEvents contain reasonable default "
7799
"gestures for launching <command>GOK</command> and <command>orca</command>, "
7800
"but some users may require these gestures to be configured to best meet "
7801
"their needs. For example, shorter or longer duration for holding down a "
7802
"button or hotkey might make the login experience more usable for some users. "
7803
"Also, additional AT programs may be added to the configuration file if "
7804
"needed."
7805
msgstr ""
7806
7807
#: ../C/gdm.xml:7085(title)
7808
msgid "Accessibile Theming"
7809
msgstr ""
7810
7811
#: ../C/gdm.xml:7087(para)
7812
msgid ""
7813
"If using the \"GTK+ Greeter\" users can easily switch the color and contrast "
7814
"scheme of the dialog. To do this, ensure the <filename>AllowGtkThemeChange</"
7815
"filename> parameter in the GDM configuration is set to \"true\". This should "
7816
"be the default value. When true, the \"Standard Greeter\" contains a menu "
7817
"allowing the user to change to a different GTK+ theme. The "
7818
"<filename>GtkThemesToAllow</filename> configuration choice can also be used "
7819
"to limit the choices available as desired. For example:"
7820
msgstr ""
7821
7822
#: ../C/gdm.xml:7099(screen)
7823
#, no-wrap
7824
msgid ""
7825
"\n"
7826
"GtkThemesToAllow=HighContrast,HighContrastInverse\n"
7827
msgstr ""
7828
7829
#: ../C/gdm.xml:7103(para)
7830
msgid ""
7831
"If using the \"Themed Greeter\" there may be suitable GDM themes available "
7832
"that provide needed color and contrast schemes, but these are not yet "
7833
"shipped with the GDM program. Some distributions may ship such themes. There "
7834
"is not yet any mechanism to switch between themes in the \"Themed Greeter\", "
7835
"so if an accessible theme is required by one user, then all users would need "
7836
"to use the same theme."
7837
msgstr ""
7838
7839
#: ../C/gdm.xml:7115(title)
7840
msgid "AT Program Support"
7841
msgstr ""
7842
7843
#: ../C/gdm.xml:7117(para)
7844
msgid ""
7845
"To enable user to launch AT such as the <command>GOK</command> or "
7846
"<command>orca</command>, the <filename>AddGtkModules</filename> parameter in "
7847
"the GDM configuration must be set to \"true\". Also the "
7848
"<filename>GtkModulesList</filename> parameter must be uncommented and set as "
7849
"follows:"
7850
msgstr ""
7851
7852
#: ../C/gdm.xml:7126(screen)
7853
#, no-wrap
7854
msgid ""
7855
"\n"
7856
"GtkModulesList=gail:atk-bridge:/usr/lib/gtk-2.0/modules/libdwellmouselistener:/usr/lib/gtk-2.0/modules/libkeymouselistener\n"
7857
msgstr ""
7858
7859
#: ../C/gdm.xml:7130(para)
7860
msgid ""
7861
"This causes all GDM GUI programs to be run with the appropriate GTK modules "
7862
"for launching AT programs. The use of assistive technologies and the atk-"
7863
"bridge module requires the registry daemon, <command>at-spi-registryd</"
7864
"command>, to be running. This is handled by the GDM GUI starting with "
7865
"version 2.17."
7866
msgstr ""
7867
7868
#: ../C/gdm.xml:7138(para)
7869
msgid ""
7870
"System administrators may wish to load only the minimum subset of these "
7871
"modules which is required to support their user base. The "
7872
"\"libkeymouselistener\" provides hotkey and switch gesture support while the "
7873
"\"libdwellmouselistener\" provides mouse motion gesture support. If your "
7874
"user base only requires one or the other, it is only necessary to include "
7875
"the gesture listener that is needed. Also, some AT programs may not require "
7876
"gail or atk-bridge. If you find the AT programs you need works fine without "
7877
"including these, then they may be omitted. Note that some AT programs work "
7878
"with a reduced feature set if gail and/or atk-bridge are not present. "
7879
"However, for general accessibility use, including all four is suitable."
7880
msgstr ""
7881
7882
#: ../C/gdm.xml:7153(para)
7883
msgid ""
7884
"Once \"keymouselistener\" and/or \"dwellmouselistener\" have been added to "
7885
"the <filename>AddGtkModules</filename> loaded by GDM, then you may need to "
7886
"modiify the gesture configurations to meet your user's needs. Default "
7887
"gestures are provided for launching <command>GOK</command> and "
7888
"<command>orca</command>, but it is recommended to modify these gestures so "
7889
"they work best for your user base. These gesture associations are contained "
7890
"in files <filename>AccessKeyMouseEvents</filename> and "
7891
"<filename>AccessDwellMouseEvents</filename>, respectively. Both files are "
7892
"located in the <filename><etc>/gdm/modules</filename> directory. The "
7893
"gesture configuration format is described in the comment section of the two "
7894
"configuration files."
7895
msgstr ""
7896
7897
#: ../C/gdm.xml:7170(para)
7898
msgid ""
7899
"The AccessKeyMouseEvents file controls the keymouselistener Gesture Listener "
7900
"and is used to define key-press, mouse button, or XInput device sequences "
7901
"that can be used to launch applications needed for accessibility. In order "
7902
"to reduce the likelihood of unintentional launch, these \"gestures\" may be "
7903
"associated with multiple switch presses and/or minimum durations. Note that "
7904
"the XKB extension is needed for key gestures to work, so you may need to add "
7905
"+xkb to your X server command line for gestures to work properly. The X "
7906
"server command line is specified in the GDM configuration file in the "
7907
"\"server-foo\" sections."
7908
msgstr ""
7909
7910
#: ../C/gdm.xml:7184(para)
7911
msgid ""
7912
"The DwellKeyMouseEvents file controls the dwellmouselistner and supports "
7913
"gestures that involve the motion of a pointing device such as the system "
7914
"mouse of an alternative pointing device such as a head pointer or trackball "
7915
"may also be defined. Motion gestures are defined as \"crossing events\" into "
7916
"and out of the login dialog window. If the \"dwellmouselistener\" gesture "
7917
"listener is loaded, then alternative pointing devices are temporarily "
7918
"\"latched\" to the core pointer, such that motion from alternative devices "
7919
"results in movement of the onscreen pointer. All gestures are specified by "
7920
"the same syntax; that is, there is no distinction between a \"core mouse\" "
7921
"gesture and motion from an alternate input device."
7922
msgstr ""
7923
7924
#: ../C/gdm.xml:7200(para)
7925
msgid ""
7926
"On some operating systems, it is necessary to make sure that the GDM user is "
7927
"a member of the \"audio\" group for AT programs that require audio output "
7928
"(such as text-to-speech) to be functional."
7929
msgstr ""
7930
7931
#: ../C/gdm.xml:7207(para)
7932
msgid ""
7933
"Currently GDM does not remember what accessible technology programs have "
7934
"been started when switching applications. So if the user switches between "
7935
"the login program and the chooser, for example, then it is necessary for the "
7936
"user to redo the gesture. Users may need to also set up their default "
7937
"session so that the assistive technologies required are started "
7938
"automatically (or have appropriate key-bindings defined to start them) after "
7939
"the user session has started."
7940
msgstr ""
7941
7942
#: ../C/gdm.xml:7220(title)
7943
msgid "AT Troubleshooting"
7944
msgstr ""
7945
7946
#: ../C/gdm.xml:7222(para)
7947
msgid ""
7948
"There are some common issues that cause users to have problems getting the "
7949
"gesture listeners to work. It is recommended that people use GDM version "
7950
"2.18.0 or later for best results."
7951
msgstr ""
7952
7953
#: ../C/gdm.xml:7228(para)
7954
msgid ""
7955
"Some older X servers have a bug which causes detectable autorepeat to fail "
7956
"when XEVIE is enabled (which happens when atk-bridge is included as a GTK "
7957
"Module). This bug causes key gestures with a duration greater than 0 to "
7958
"always fail. A workaround is to simply redefine all key gestures so they "
7959
"have zero length duration, or upgrade your X server."
7960
msgstr ""
7961
7962
#: ../C/gdm.xml:7237(para)
7963
msgid ""
7964
"Some versions of <command>GOK</command> and <command>orca</command> will not "
7965
"launch unless the \"gdm\" user has a writable home directory. This has been "
7966
"fixed in GNOME 2.18, but if using an older version of GNOME, then making "
7967
"sure that the GDM user has a writable home directory should make these "
7968
"programs functional."
7969
msgstr ""
7970
7971
#: ../C/gdm.xml:7246(para)
7972
msgid ""
7973
"If you see an hourglass cursor when you complete a gesture but the program "
7974
"does not start, then this indicates that the gesture was received, but that "
7975
"there was a problem starting the program. Most likely the issue may be the "
7976
"lack of a writable gdm home directory."
7977
msgstr ""
7978
7979
#: ../C/gdm.xml:7254(para)
7980
msgid ""
7981
"Also note that some input devices require X server configuration before GDM "
7982
"will recognize them."
7983
msgstr ""
7984
7985
#: ../C/gdm.xml:7261(title)
7986
msgid "Accessibility Login Sound Configuration"
7987
msgstr ""
7988
7989
#: ../C/gdm.xml:7263(para)
7990
msgid ""
7991
"By default, GDM requires a media application such as \"play\" to be present "
7992
"to play sounds for successful or failed login. GDM defaults the location of "
7993
"this application to <filename><bin>/play</filename> (or <filename><"
7994
"bin>/audioplay</filename> on Solaris. This can be changed via the "
7995
"<filename>SoundProgram</filename> GDM configuration option. Typically most "
7996
"text-to-speech programs (such as <command>orca</command>) use a separate "
7997
"mechanism to play audio, so this configuration setting is not needed for "
7998
"them to work."
7999
msgstr ""
8000
8001
#: ../C/gdm.xml:7281(title)
8002
msgid "Solaris Specific Features"
8003
msgstr ""
8004
8005
#: ../C/gdm.xml:7284(title)
8006
msgid "Using GDM on Solaris"
8007
msgstr ""
8008
8009
#: ../C/gdm.xml:7286(para)
8010
msgid ""
8011
"GDM is not yet the default login program on Solaris. If you wish to switch "
8012
"to using GDM, then you need to turn off CDE login and start the GDM service. "
8013
"Note that turning off or disabiling CDE login will cause any running "
8014
"sessions to immediately exit, and any unsaved data will be lost. Only run "
8015
"these commands if you are sure there is no unsaved data in your running "
8016
"sessions. It would be best to run these commands from console login, or a "
8017
"Failsafe Terminal rather than from a running GUI session. The first step is "
8018
"to run the following command to see if CDE login is running as an SMF "
8019
"service."
8020
msgstr ""
8021
8022
#: ../C/gdm.xml:7299(screen)
8023
#, no-wrap
8024
msgid ""
8025
"\n"
8026
"svcs cde-login\n"
8027
msgstr ""
8028
8029
#: ../C/gdm.xml:7303(para)
8030
msgid ""
8031
"If the <command>svcs</command> command responds that this service is "
8032
"enabled, then run this command to disable CDE login:"
8033
msgstr ""
8034
8035
#: ../C/gdm.xml:7308(screen)
8036
#, no-wrap
8037
msgid ""
8038
"\n"
8039
"svcadm disable cde-login\n"
8040
msgstr ""
8041
8042
#: ../C/gdm.xml:7312(para)
8043
msgid ""
8044
"If the <command>svcs</command> command responds that this pattern doesn't "
8045
"match any instances, then run these commands to stop CDE login:"
8046
msgstr ""
8047
8048
#: ../C/gdm.xml:7318(screen)
8049
#, no-wrap
8050
msgid ""
8051
"\n"
8052
"/usr/dt/config/dtconfig -d\n"
8053
"Either reboot, or kill any running dtlogin processes.\n"
8054
msgstr ""
8055
8056
#: ../C/gdm.xml:7323(para)
8057
msgid ""
8058
"At this point you will be presented with a console login. Login as root, and "
8059
"run the following command. If on Solaris 10 the servicename is \"gdm2-login"
8060
"\", if on Solaris Nevada the servicename is \"gdm\"."
8061
msgstr ""
8062
8063
#: ../C/gdm.xml:7330(screen)
8064
#, no-wrap
8065
msgid ""
8066
"\n"
8067
"svcadm enable servicename\n"
8068
msgstr ""
8069
8070
#: ../C/gdm.xml:7336(title)
8071
msgid "Solaris Configuration"
8072
msgstr ""
8073
8074
#: ../C/gdm.xml:7337(para)
8075
msgid ""
8076
"On Solaris, the following configuration is recommended. This turns on IPv6 "
8077
"and also turns on PreFetch for performance benefit. <screen>\n"
8078
"./autogen.sh --prefix=/usr --sysconfdir=/etc/X11 --localstatedir=/var\n"
8079
" --libexecdir=/usr/lib --enable-ipv6=yes --with-at-bindir=/usr/sfw/bin\n"
8080
" --with-prefetch --with-post-path=/usr/openwin/bin --with-pam-prefix=/etc\n"
8081
" --with-lang-file=/etc/default/init\n"
8082
"</screen>"
8083
msgstr ""
8084
8085
#: ../C/gdm.xml:7350(para)
8086
msgid ""
8087
"Configuring GDM with the \"--with-post-path=/usr/openwin/bin\" on Solaris is "
8088
"recommended for accessing X server programs."
8089
msgstr ""
8090
8091
#: ../C/gdm.xml:7358(title)
8092
msgid "Solaris /etc/logindevperm"
8093
msgstr ""
8094
8095
#: ../C/gdm.xml:7359(para)
8096
msgid ""
8097
"GDM supports /etc/logindevperm, but only on Solaris 10 and higher. Refer to "
8098
"the logindevperm.4 man page for more information."
8099
msgstr ""
8100
8101
#: ../C/gdm.xml:7365(para)
8102
msgid ""
8103
"To make /etc/logindevperm functionality work on Solaris 9 or earlier you "
8104
"would have to hack the GDM PreSession and PostSession script to chmod the "
8105
"device permissions directly. In other words, if /etc/logindevperm had a "
8106
"listing like this:"
8107
msgstr ""
8108
8109
#: ../C/gdm.xml:7372(screen)
8110
#, no-wrap
8111
msgid ""
8112
"\n"
8113
"/dev/console 0600 /dev/sound/* # audio devices\n"
8114
msgstr ""
8115
8116
#: ../C/gdm.xml:7376(para)
8117
msgid ""
8118
"Then the PreSession script would need to be modified to chown /dev/console "
8119
"to the user:group who is logging into the console and ensure whatever "
8120
"permissions is specified in /etc/logindevperm (0600 for the line above). "
8121
"Then in the PostSession script chmod the device back to root:root and ensure "
8122
"0600 this time (do not use the value in the /etc/logindevperm file). Linux "
8123
"uses a different mechanism for managing device permissions, so this extra "
8124
"scripting is not needed."
8125
msgstr ""
8126
8127
#: ../C/gdm.xml:7389(title)
8128
msgid "Solaris Automatic Login"
8129
msgstr ""
8130
8131
#: ../C/gdm.xml:7390(para)
8132
msgid ""
8133
"Automatic login does not work on Solaris 10 and earlier because PAM is not "
8134
"configured to support this feature by default. Automatic login is a GDM "
8135
"feature that is not enabled by default, so you would only notice this "
8136
"problem if you try to make use of it. Turning this feature on causes your "
8137
"computer to login to a specified username on startup without asking for "
8138
"username and password. This is an insecure way to set up your computer."
8139
msgstr ""
8140
8141
#: ../C/gdm.xml:7401(para)
8142
msgid ""
8143
"If using Solaris 10 or lower, then you need to compile the pam_allow.c code "
8144
"provided with the GDM release and install it to /usr/lib/security (or "
8145
"provide the full path in /etc/pam.conf) and ensure it is owned by uid 0 and "
8146
"not group or world writable."
8147
msgstr ""
8148
8149
#: ../C/gdm.xml:7408(para)
8150
msgid ""
8151
"The following are reasonable pam.conf values for turning on automatic login "
8152
"in GDM. Make sure to read the PAM documentation (e.g. pam.d/pam.conf man "
8153
"page) and be comfortable with the security implications of any changes you "
8154
"intend to make to your configuration."
8155
msgstr ""
8156
8157
#: ../C/gdm.xml:7416(screen)
8158
#, no-wrap
8159
msgid ""
8160
"\n"
8161
" gdm-autologin auth required pam_unix_cred.so.1\n"
8162
" gdm-autologin auth sufficient pam_allow.so.1\n"
8163
" gdm-autologin account sufficient pam_allow.so.1\n"
8164
" gdm-autologin session sufficient pam_allow.so.1\n"
8165
" gdm-autologin password sufficient pam_allow.so.1\n"
8166
msgstr ""
8167
8168
#: ../C/gdm.xml:7424(para)
8169
msgid ""
8170
"The above setup will cause no lastlog entry to be generated. If a lastlog "
8171
"entry is desired, then use the following for session:"
8172
msgstr ""
8173
8174
#: ../C/gdm.xml:7429(screen)
8175
#, no-wrap
8176
msgid ""
8177
"\n"
8178
" gdm-autologin session required pam_unix_session.so.1\n"
8179
msgstr ""
8180
8181
#: ../C/gdm.xml:7435(title)
8182
msgid "Solaris RBAC support for Shutdown, Reboot, and Suspend"
8183
msgstr ""
8184
8185
#: ../C/gdm.xml:7437(para)
8186
msgid ""
8187
"Starting with GDM 2.19, GDM supports RBAC (Role Based Access Control) for "
8188
"enabling the system commands (Shutdown, Reboot, Suspend, etc.) that appear "
8189
"in the greeter system menu and via the <command>gdmflexiserver</command> "
8190
"QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION commands."
8191
msgstr ""
8192
8193
#: ../C/gdm.xml:7446(para)
8194
msgid ""
8195
"On Solaris GDM has the following value specified for the "
8196
"<filename>RBACSystemCommandKeys</filename> configuration option."
8197
msgstr ""
8198
8199
#: ../C/gdm.xml:7452(screen)
8200
#, no-wrap
8201
msgid ""
8202
"\n"
8203
"HALT:solaris.system.shutdown;REBOOT:solaris.system.shutdown\n"
8204
msgstr ""
8205
8206
#: ../C/gdm.xml:7456(para)
8207
msgid ""
8208
"This will cause the SHUTDOWN and REBOOT features to only be enabled for "
8209
"users who have RBAC authority. In other words, those users who have the "
8210
"\"solaris.system.shutdown\" authorization name specified. The GDM greeter "
8211
"will only display these options if the gdm user (specified in the "
8212
"<filename>User</filename> configuration option, \"gdm\" by default) has such "
8213
"RBAC permissions."
8214
msgstr ""
8215
8216
#: ../C/gdm.xml:7466(para)
8217
msgid ""
8218
"Therefore, add the \"solaris.system.shutdown\" authorization name to the "
8219
"<filename>/etc/user_attr</filename> for all users who should have authority "
8220
"to shutdown and reboot the system. If you want these options to appear in "
8221
"the greeter program, also add this authorization name to the gdm user. If "
8222
"you don't want to use RBAC, then you may unset the "
8223
"<filename>RBACSystemCommandKeys</filename> GDM configuration key, and this "
8224
"will make the system commands available for all users. Refer to the "
8225
"<filename>user_attr</filename> man page for more information about setting "
8226
"RBAC privileges."
8227
msgstr ""
8228
8229
#: ../C/gdm.xml:7480(para)
8230
msgid ""
8231
"Note that on Solaris there are two programs that can be used to shutdown the "
8232
"system. These are GDM and <command>gnome-sys-suspend</command>. "
8233
"<command>gnome-sys-suspend</command> is a GUI front-end for the <command>sys-"
8234
"suspend</command>."
8235
msgstr ""
8236
8237
#: ../C/gdm.xml:7488(para)
8238
msgid ""
8239
"If GDM is being used as the login program and the user has RBAC permissions "
8240
"to shutdown the machine (or RBAC support is disabled in GDM), then the GNOME "
8241
"panel \"Shut Down..\" option will use GDM to shutdown, reboot, and suspend "
8242
"the machine. This is a bit nicer than using <command>gnome-sys-suspend</"
8243
"command> since GDM will wait until the user session has finished (including "
8244
"running the PostSession script, etc.) before running the shutdown/reboot/"
8245
"suspend command. Also the <command>gnome-sys-suspend</command> command is "
8246
"less functional since it does not support a reboot option, only shutdown and "
8247
"suspend."
8248
msgstr ""
8249
8250
#: ../C/gdm.xml:7503(para)
8251
msgid ""
8252
"If GDM is not being used to manage shutdown, reboot, and suspend; then the "
8253
"GNOME panel uses <command>gnome-sys-suspend</command> when you select the "
8254
"\"Shut Down...\" option from the application menu. If the pop-up that "
8255
"appears when you select this only shows the suspend and shutdown options, "
8256
"then you are likely using <command>gnome-sys-suspend</command>. If you are "
8257
"using this, then refer to the <command>sys-suspend</command> man page for "
8258
"information about how to configure it. Or consider using GDM and configuring "
8259
"it to provide these options."
8260
msgstr ""
8261
8262
#: ../C/gdm.xml:7519(title)
8263
msgid "Other Solaris Features"
8264
msgstr ""
8265
8266
#: ../C/gdm.xml:7520(para)
8267
msgid "GDM supports a few features specific to Solaris, as follows:"
8268
msgstr ""
8269
8270
#: ../C/gdm.xml:7524(para)
8271
msgid ""
8272
"GDM supports Solaris Auditing if running on Solaris 10 or higher. GDM should "
8273
"not be used if auditing is needed and running Solaris 9 or older."
8274
msgstr ""
8275
8276
#: ../C/gdm.xml:7530(para)
8277
msgid ""
8278
"GDM supports a security feature which causes the X server to run as the user "
8279
"instead of as the root user. GDM must be using PAM for this feature to be "
8280
"enabled, which is the normal case for Solaris. This second feature has the "
8281
"side-effect of causing the X server to always restart between sessions, "
8282
"which disables the AlwaysRestartServer configuration option."
8283
msgstr ""
8284
8285
#: ../C/gdm.xml:7539(para)
8286
msgid ""
8287
"Solaris supports the <filename>/etc/default/login</filename> interface, "
8288
"which affects the <filename>DefaultPath</filename>, <filename>RootPath</"
8289
"filename>, <filename>PasswordRequired</filename>, and "
8290
"<filename>AllowRemoteRoot</filename> options as described in the "
8291
"\"Configuration\" section."
8292
msgstr ""
8293
8294
#: ../C/gdm.xml:7551(title)
8295
msgid "Example Configurations"
8296
msgstr ""
8297
8298
#: ../C/gdm.xml:7553(para)
8299
msgid ""
8300
"This section has some example configurations that are useful for various "
8301
"setups."
8302
msgstr ""
8303
8304
#: ../C/gdm.xml:7559(title)
8305
msgid "Terminal Lab With One Server"
8306
msgstr ""
8307
8308
#: ../C/gdm.xml:7561(para)
8309
msgid ""
8310
"Suppose you want to make a lab full of X terminals that all connect to one "
8311
"server machine. So let's call one X terminal <filename>xterminal</filename> "
8312
"and let's call the server machine <filename>appserver</filename>. You "
8313
"install GDM on both."
8314
msgstr ""
8315
8316
#: ../C/gdm.xml:7568(para)
8317
msgid ""
8318
"On <filename>appserver</filename> you enable XDMCP, so you have <screen>\n"
8319
"[xdmcp]\n"
8320
"Enable=true\n"
8321
"</screen> If you want no local screens here, you can then make the <filename>"
8322
"[servers]</filename> section empty."
8323
msgstr ""
8324
8325
#: ../C/gdm.xml:7578(para)
8326
msgid ""
8327
"On the <filename>xterminal</filename> you disable XDMCP (you don't want "
8328
"anyone to connect to the xterminal really). You will add a server type "
8329
"perhaps called <filename>Terminal</filename> as follows: <screen>\n"
8330
"[server-Terminal]\n"
8331
"name=Terminal server\n"
8332
"command=/path/to/X -terminate\n"
8333
"flexible=false\n"
8334
"handled=false\n"
8335
"</screen> This definition should in fact be included in the standard "
8336
"configuration file. Notice that we made the <filename>handled</filename> key "
8337
"false since we don't want GDM to handle this server localy. Also note that "
8338
"we have not yet added the <filename>-query</filename> argument, you can add "
8339
"that here, or in the <filename>[servers]</filename> section. We'll define "
8340
"our local servers as follows: <screen>\n"
8341
"[servers]\n"
8342
"0=Terminal -query appserver\n"
8343
"</screen> This will run a direct XDMCP query to the server named "
8344
"<filename>appserver</filename>."
8345
msgstr ""
8346
8347
#: ../C/gdm.xml:7606(title)
8348
msgid "Terminal Lab With Two Or More Servers"
8349
msgstr ""
8350
8351
#: ../C/gdm.xml:7608(para)
8352
msgid ""
8353
"Suppose you want to make a lab full of X terminals that all connect to some "
8354
"choice of servers. For now let's make it <filename>appserverone</filename> "
8355
"and <filename>appservertwo</filename>. Again we'll call our example X "
8356
"terminal server <filename>xterminal</filename>. The setup on both servers is "
8357
"the same as with the case of one server in the previous section. You do not "
8358
"need to explicitly enable indirect queries on the server since we'll run the "
8359
"choosers locally on the X terminals."
8360
msgstr ""
8361
8362
#: ../C/gdm.xml:7619(para)
8363
msgid ""
8364
"So on the <filename>xterminal</filename> you again disable XDMCP. You will "
8365
"add a server type perhaps called <filename>Chooser</filename> as follows: "
8366
"<screen>\n"
8367
"[server-Chooser]\n"
8368
"name=Chooser server\n"
8369
"command=/path/to/X\n"
8370
"flexible=false\n"
8371
"chooser=true\n"
8372
"</screen> And again this definition should in fact be included in the "
8373
"standard configuration file. Notice that we made the <filename>chooser</"
8374
"filename> key true here. This will run the XDMCP chooser for this server, "
8375
"and when the user chooses a host GDM will run a query for that host. Then we "
8376
"will define our local servers as follows: <screen>\n"
8377
"[servers]\n"
8378
"0=Chooser\n"
8379
"</screen>"
8380
msgstr ""
8381
8382
#: ../C/gdm.xml:7642(para)
8383
msgid ""
8384
"The XDMCP chooser on the X terminal will normally give a broadcast query to "
8385
"see which servers exist on the network. If the two servers are not reachable "
8386
"by a broadcast query, you must add them by hand to the configuration file. "
8387
"So in the <filename>[chooser]</filename> section you would have: <screen>\n"
8388
"Hosts=appserverone,appservertwo\n"
8389
"</screen> and any other servers you wish the users to be able to connect to."
8390
msgstr ""
8391
8392
#: ../C/gdm.xml:7654(para)
8393
msgid ""
8394
"Sometimes you may want to run the chooser on the server side however. Then "
8395
"what you want to do is to run a configuration similar to the previous "
8396
"section about the one server configuration with XDMCP indirect queries "
8397
"enabled on <filename>appserver</filename> and on the X terminals you'd have "
8398
"<screen>\n"
8399
"[servers]\n"
8400
"0=Terminal -indirect appserver\n"
8401
"</screen> This way for example you only have to maintain one "
8402
"<filename>Hosts</filename> entry. However as a disadvantage then, the "
8403
"<filename>appserver</filename> must then always be available. So it's not "
8404
"good for situations where you want to have several servers and not all of "
8405
"them have to be on all the time. You could also have one of the X terminals "
8406
"handle indirect XDMCP queries and serve up the chooser to the other X "
8407
"terminals."
8408
msgstr ""
8409
8410
#: ../C/gdm.xml:7675(title)
8411
msgid "Defining Custom Commands"
8412
msgstr ""
8413
8414
#: ../C/gdm.xml:7677(para)
8415
msgid ""
8416
"Suppose you want to add a custom command to the GDM menu that will give you "
8417
"the opportunity to boot into other operating system such as Windoze. Just "
8418
"add the following options into the <filename>[customcommand]</filename> "
8419
"section of the GDM configuration file. <screen>\n"
8420
" [customcommand]\n"
8421
" CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze\n"
8422
" CustomCommandLabel0=_Windoze\n"
8423
" CustomCommandLRLabel0=Reboot into _Windoze\n"
8424
" CustomCommandText0=Are you sure you want to restart the computer "
8425
"into Windoze?\n"
8426
" CustomCommandTooltip0=Restarts the computer into Windoze\n"
8427
" CustomCommandIsPersistent0=true\n"
8428
" </screen> CustomCommand0 specifies two commands separated by a "
8429
"semicolon: <filename>/sbin/rebootwindoze</filename> and <filename>/usr/local/"
8430
"sbin/rebootwindoze</filename>. GDM will use the first valid command in the "
8431
"list. This allows different commands for different operating systems to be "
8432
"included."
8433
msgstr ""
8434
8435
#: ../C/gdm.xml:7700(para)
8436
msgid ""
8437
"Note, that besides being able to customise this option to reboot into "
8438
"different operating systems you can also use it to define your own custom "
8439
"behaviours that you wish to run from the GDM menu. Suppose you want to give "
8440
"users the opportunity to run system update scripts from the login screen. "
8441
"Add the following options into the <filename>[customcommand]</filename> "
8442
"section of your GDM configuration file. <screen>\n"
8443
" [customcommand]\n"
8444
" CustomCommand0=/sbin/updatesystem;/usr/local/sbin/updatesystem\n"
8445
" CustomCommandLabel0=_Update Me\n"
8446
" CustomCommandLRLabel0=Update the system\n"
8447
" CustomCommandText0=Are you sure you want to update the system "
8448
"software?\n"
8449
" CustomCommandTooltip0=Updates the system\n"
8450
" CustomCommandNoRestart0=true\n"
8451
" </screen>"
8452
msgstr ""
8453
8454
#: ../C/gdm.xml:7720(para)
8455
msgid ""
8456
"Both custom commands could be defined as follows. <screen>\n"
8457
" [customcommand]\n"
8458
" CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze\n"
8459
" CustomCommandLabel0=_Windoze\n"
8460
" CustomCommandLRLabel0=Reboot into _Windoze\n"
8461
" CustomCommandText0=Are you sure you want to restart the computer "
8462
"into Windoze?\n"
8463
" CustomCommandTooltip0=Restarts the computer into Windoze\n"
8464
" CustomCommandIsPersistent0=true\n"
8465
" \n"
8466
" CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem\n"
8467
" CustomCommandLabel1=_Update Me\n"
8468
" CustomCommandLRLabel1=Update the system\n"
8469
" CustomCommandText1=Are you sure you want to update the system "
8470
"software?\n"
8471
" CustomCommandTooltip1=Updates the system\n"
8472
" CustomCommandNoRestart1=true\n"
8473
" </screen>"
8474
msgstr ""
8475
8476
#: ../C/gdm.xml:7741(para)
8477
msgid ""
8478
"There can be up to 10 custom commands numbered 0-9. <screen>\n"
8479
" [customcommand]\n"
8480
" CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze\n"
8481
" CustomCommandLabel0=_Windoze\n"
8482
" CustomCommandLRLabel0=Reboot into _Windoze\n"
8483
" CustomCommandText0=Are you sure you want to restart the computer "
8484
"into Windoze?\n"
8485
" CustomCommandTooltip0=Restarts the computer into Windoze\n"
8486
" CustomCommandIsPersistent0=true\n"
8487
" \n"
8488
" CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem\n"
8489
" CustomCommandLabel1=_Update Me\n"
8490
" CustomCommandLRLabel1=Update the system\n"
8491
" CustomCommandText1=Are you sure you want to update the system "
8492
"software?\n"
8493
" CustomCommandTooltip1=Updates the system\n"
8494
" CustomCommandNoRestart1=true\n"
8495
" \n"
8496
" CustomCommand3=/sbin/do_something\n"
8497
" .\n"
8498
" .\n"
8499
" .\n"
8500
" \n"
8501
" CustomCommand4=/sbin/do_something_else\n"
8502
" .\n"
8503
" .\n"
8504
" .\n"
8505
" </screen>"
8506
msgstr ""
8507
8508
#: ../C/gdm.xml:7775(title)
8509
msgid "Troubleshooting"
8510
msgstr ""
8511
8512
#: ../C/gdm.xml:7777(para)
8513
msgid ""
8514
"This section discusses helpful tips for getting GDM working. In general, if "
8515
"you have a problem using GDM, you can submit a bug to the \"gdm\" category "
8516
"in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\">bugzilla.gnome."
8517
"org</ulink> or send an email to the <address><email>gdm-list@gnome.org</"
8518
"email></address> mail list."
8519
msgstr ""
8520
8521
#: ../C/gdm.xml:7787(para)
8522
msgid ""
8523
"If GDM is failing to work properly, it is always a good idea to include "
8524
"debug information. Use the <command>gdmsetup</command> command to turn on "
8525
"debug (\"Enable debug messages to system log\" checkbox in the \"Security\" "
8526
"tab), then use GDM to the point where it fails, and include the GDM output "
8527
"sent to your system log (<filename><var>/log/messages</filename> or "
8528
"<filename><var>/adm/messages</filename> depending on your operating "
8529
"system). Since the system log can be large, please only include the GDM "
8530
"debug information and do not sent the entire file. If you do not see any GDM "
8531
"syslog output, you may need to configure syslog (see syslog.3c man page)."
8532
msgstr ""
8533
8534
#: ../C/gdm.xml:7801(para)
8535
msgid ""
8536
"You should not leave debug on after collecting data. It will clutter your "
8537
"syslog and slow system performance."
8538
msgstr ""
8539
8540
#: ../C/gdm.xml:7807(title)
8541
msgid "GDM Will Not Start"
8542
msgstr ""
8543
8544
#: ../C/gdm.xml:7809(para)
8545
msgid ""
8546
"There are a many problems that can cause GDM to fail to start, but this "
8547
"section will discuss a few common problems and how to approach tracking down "
8548
"a problem with GDM starting. Some problems will cause GDM to respond with an "
8549
"error message or dialog when it tries to start, but it can be difficult to "
8550
"track down problems when GDM fails silently."
8551
msgstr ""
8552
8553
#: ../C/gdm.xml:7818(para)
8554
msgid ""
8555
"First make sure that the X server is configured properly. The GDM "
8556
"configuration file contains a command in the [server-Standard] section that "
8557
"is used for starting the X server. Verify that this command works on your "
8558
"system. Running this command from the console should start the X server. If "
8559
"it fails, then the problem is likely with your X server configuration. Refer "
8560
"to your X server error log for an idea of what the problem may be. The "
8561
"problem may also be that your X server requires different command-line "
8562
"options. If so, then modify the X server command in the GDM configuration "
8563
"file so that it is correct for your system."
8564
msgstr ""
8565
8566
#: ../C/gdm.xml:7831(para)
8567
msgid ""
8568
"Another common problem is that the GDM greeter program is having trouble "
8569
"starting. This can happen, for example, if GDM cannot find a needed library "
8570
"or other resource. Try starting the X server and a terminal program, set the "
8571
"shell environment variable DOING_GDM_DEVELOPMENT=1 and run <command><"
8572
"lib>/gdmlogin</command> or <command><lib>/gdmgreeter</command>. Any "
8573
"error messages echoed to the terminal will likely highlight the problem. "
8574
"Also, turning on debug and checking the output sent to the system log will "
8575
"often highlight the problem."
8576
msgstr ""
8577
8578
#: ../C/gdm.xml:7844(para)
8579
msgid ""
8580
"Also make sure that the <filename>/tmp</filename> directory has reasonable "
8581
"ownership and permissions, and that the machine's file system is not full. "
8582
"These problems will cause GDM to fail to start."
8583
msgstr ""
8584
8585
#: ../C/gdm.xml:7852(title)
8586
msgid "GDM Will Not Access User Settings"
8587
msgstr ""
8588
8589
#: ../C/gdm.xml:7854(para)
8590
msgid ""
8591
"GDM saves user settings, such as your default session and default language, "
8592
"in the <filename>~/.dmrc</filename>. Other files, such as the user's "
8593
"<filename>~/.Xauthority</filename> file will also affect login. GDM, by "
8594
"default, is strict about how it tries to access files in the user's home "
8595
"directory, and will ignore the file if they do not conform to certain rules. "
8596
"You can use the <filename>RelaxPermissions</filename> configuration option "
8597
"to make GDM less strict about how it accesses files in the user's home "
8598
"directory, or correct the permissions issues that cause GDM to ignore the "
8599
"file. This is discussed in detail described in the \"File Access\" section "
8600
"of the \"Overview\"."
8601
msgstr ""
8602
8603
#: ../C/gdm.xml:7873(title)
8604
msgid "License"
8605
msgstr ""
8606
8607
#: ../C/gdm.xml:7874(para)
8608
msgid ""
8609
"This program is free software; you can redistribute it and/or modify it "
8610
"under the terms of the <ulink type=\"help\" url=\"gnome-help:gpl"
8611
"\"><citetitle>GNU General Public License</citetitle></ulink> as published by "
8612
"the Free Software Foundation; either version 2 of the License, or (at your "
8613
"option) any later version."
8614
msgstr ""
8615
8616
#: ../C/gdm.xml:7882(para)
8617
msgid ""
8618
"This program is distributed in the hope that it will be useful, but WITHOUT "
8619
"ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or "
8620
"FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public "
8621
"License</citetitle> for more details."
8622
msgstr ""
8623
8624
#: ../C/gdm.xml:7888(para)
8625
msgid ""
8626
"A copy of the <citetitle>GNU General Public License</citetitle> is included "
8627
"as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also "
8628
"obtain a copy of the <citetitle>GNU General Public License</citetitle> from "
8629
"the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://"
8630
"www.fsf.org\">their Web site</ulink> or by writing to <address> Free "
8631
"Software Foundation, Inc. <street>51 Franklin Street, Fifth Floor</"
8632
"street><city>Boston</city>, <state>MA</state><postcode>02110-1301</"
8633
"postcode><country>USA</country></address>"
8634
msgstr ""
8635
8636
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
8637
#: ../C/gdm.xml:0(None)
8638
msgid "translator-credits"
8639
msgstr ""
8640
Loggerhead is a web-based interface for Breezy
Version: 2.0.1