From e198274bd57f0df7acf739d62cc17d9aa2960593 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Sun, 22 Jan 2012 00:25:42 -0600 Subject: Part 1 of 2 of kdm rename --- tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook | 198 +++++++++++----------- 1 file changed, 99 insertions(+), 99 deletions(-) (limited to 'tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook') diff --git a/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook b/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook index 18d6a847588..a778a4b0d2f 100644 --- a/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook +++ b/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook @@ -1,20 +1,20 @@ - + - + The Files &kdm; Uses for Configuration +>The Files &tdm; Uses for Configuration This chapter documents the files that control &kdm;'s behaviour. Some of this can be also controlled from the &kcontrol; module, but not all. +>This chapter documents the files that control &tdm;'s behaviour. Some of this can be also controlled from the &kcontrol; module, but not all. &kdmrc; - The &kdm; master configuration file +>&tdmrc; - The &tdm; master configuration file The basic format of the file is INI-like. Options are key/value pairs, placed in sections. Everything in the file is case sensitive. Syntactic errors and unrecognised key/section identifiers cause &kdm; to issue non-fatal error messages. +>. Options are key/value pairs, placed in sections. Everything in the file is case sensitive. Syntactic errors and unrecognised key/section identifiers cause &tdm; to issue non-fatal error messages. Lines beginning with A pristine &kdmrc; is very thoroughly commented. All comments will be lost if you change this file with the kcontrol frontend.A pristine &tdmrc; is very thoroughly commented. All comments will be lost if you change this file with the kcontrol frontend. - + The [General] section of &kdmrc; +>The [General] section of &tdmrc; This section contains global options that do not fit into any specific section. @@ -183,7 +183,7 @@ This option exists solely for the purpose of clean automatic upgrades. Do not change it, you may interfere with future upgrades and this could result in &kdm; failing to run. +> change it, you may interfere with future upgrades and this could result in &tdm; failing to run. @@ -194,9 +194,9 @@ > If the value starts with a slash (/), it specifies a file to read &X-Server; definitions from; otherwise, it is an &X-Server; definition by itself. See for the details. If the value starts with a slash (/), it specifies a file to read &X-Server; definitions from; otherwise, it is an &X-Server; definition by itself. See for the details. The default is an &X-Server; definition that is usually reasonable for the system on which &kdm; was built. +>The default is an &X-Server; definition that is usually reasonable for the system on which &tdm; was built. @@ -209,7 +209,7 @@ List of Virtual Terminals to allocate to &X-Server;s. For negative numbers the absolute value is used, and the VT will be allocated only if the kernel says it is free. If &kdm; exhausts this list, it will allocate free will be allocated only if the kernel says it is free. If &tdm; exhausts this list, it will allocate free VTs greater than the absolute value of the last entry in this list. The filename specified will be created to contain an ASCII representation of the process ID of the main &kdm; process; the PID will not be stored if the filename is empty. +>The filename specified will be created to contain an ASCII representation of the process ID of the main &tdm; process; the PID will not be stored if the filename is empty. Empty by default. @@ -237,7 +237,7 @@ > This option controls whether &kdm; uses file locking to keep multiple display managers from running onto each other. +>This option controls whether &tdm; uses file locking to keep multiple display managers from running onto each other. The default is true This names a directory under which &kdm; stores &X-Server; authorisation files while initialising the session. &kdm; expects the system to clean up this directory from stale files on reboot. This names a directory under which &tdm; stores &X-Server; authorisation files while initialising the session. &tdm; expects the system to clean up this directory from stale files on reboot. The authorisation file to be used for a particular display can be specified with the This boolean controls whether &kdm; automatically re-reads its configuration files if it finds them to have changed. +>This boolean controls whether &tdm; automatically re-reads its configuration files if it finds them to have changed. The default is true Additional environment variables &kdm; should pass on to all programs it runs. Additional environment variables &tdm; should pass on to all programs it runs. LD_LIBRARY_PATH and XCURSOR_THEMEPrngdSocket and ) is running, &kdm; will fall back to its own pseudo-random number generator that will, among other things, successively checksum parts of this file (which, obviously, should change frequently). ) is running, &tdm; will fall back to its own pseudo-random number generator that will, among other things, successively checksum parts of this file (which, obviously, should change frequently). This option does not exist on Linux and various BSDs. The path to a character device which KDM should read random data from. Empty means to use the system's preferred entropy device if there is one. The path to a character device which TDM should read random data from. Empty means to use the system's preferred entropy device if there is one. This option does not exist on OpenBSD, as it uses the arc4_random function instead. The directory in which &kdm; should store persistent working data; such data is, for example, the previous user that logged in on a particular display. +>The directory in which &tdm; should store persistent working data; such data is, for example, the previous user that logged in on a particular display. The default is /var/lib/kdm/var/lib/tdm. @@ -416,7 +416,7 @@ > The directory in which &kdm; should store users' The directory in which &tdm; should store users' .dmrc files. This is only needed if the home directories are not readable before actually logging in (like with AFS). - + The [Xdmcp] section of &kdmrc; +>The [Xdmcp] section of &tdmrc; This section contains options that control &kdm;'s handling of &XDMCP; requests. +>This section contains options that control &tdm;'s handling of &XDMCP; requests. @@ -444,7 +444,7 @@ > Whether &kdm; should listen to incoming &XDMCP; requests. +>Whether &tdm; should listen to incoming &XDMCP; requests. The default is true This indicates the UDP port number which &kdm; uses to listen for incoming &XDMCP; requests. Unless you need to debug the system, leave this with its default value. +>This indicates the UDP port number which &tdm; uses to listen for incoming &XDMCP; requests. Unless you need to debug the system, leave this with its default value. The default is 177 XDM-AUTHENTICATION-1 style &XDMCP; authentication requires a private key to be shared between &kdm; and the terminal. This option specifies the file containing those values. Each entry in the file consists of a display name and the shared key. +>XDM-AUTHENTICATION-1 style &XDMCP; authentication requires a private key to be shared between &tdm; and the terminal. This option specifies the file containing those values. Each entry in the file consists of a display name and the shared key. Empty by default. @@ -487,12 +487,12 @@ > To prevent unauthorised &XDMCP; service and to allow forwarding of &XDMCP; IndirectQuery requests, this file contains a database of hostnames which are either allowed direct access to this machine, or have a list of hosts to which queries should be forwarded to. The format of this file is described in . +>To prevent unauthorised &XDMCP; service and to allow forwarding of &XDMCP; IndirectQuery requests, this file contains a database of hostnames which are either allowed direct access to this machine, or have a list of hosts to which queries should be forwarded to. The format of this file is described in . The default is ${kde_confdir}/kdm/Xaccess}/tdm/Xaccess. @@ -519,7 +519,7 @@ > When computing the display name for &XDMCP; clients, the name resolver will typically create a fully qualified host name for the terminal. As this is sometimes confusing, &kdm; will remove the domain name portion of the host name if it is the same as the domain name of the local host when this option is enabled. +>When computing the display name for &XDMCP; clients, the name resolver will typically create a fully qualified host name for the terminal. As this is sometimes confusing, &tdm; will remove the domain name portion of the host name if it is the same as the domain name of the local host when this option is enabled. The default is true - + The [Shutdown] section of &kdmrc; +>The [Shutdown] section of &tdmrc; This section contains global options concerning system shutdown. @@ -581,7 +581,7 @@ The command to run to halt/poweroff the system. The default is something reasonable for the system on which &kdm; was built, like The default is something reasonable for the system on which &tdm; was built, like /sbin/shutdown  The command to run to reboot the system. The default is something reasonable for the system &kdm; on which was built, like The default is something reasonable for the system &tdm; on which was built, like /sbin/shutdown   Instructs &kdm; to offer LiLo boot options in the shutdown dialogue. Instructs &tdm; to offer LiLo boot options in the shutdown dialogue. Only available on Linux i386 & x86-64. - + The [X-*-Core] section class of &kdmrc; +>The [X-*-Core] section class of &tdmrc; This section class contains options concerning the configuration of the &kdm; backend (core). +>This section class contains options concerning the configuration of the &tdm; backend (core). @@ -753,7 +753,7 @@ > These options control the behaviour of &kdm; when attempting to open a connection to an &X-Server;. is the length of the pause (in seconds) between successive attempts, How many times &kdm; should attempt to start a How many times &tdm; should attempt to start a foreign display listed in the Xservers How many times &kdm; should attempt to start up a local &X-Server;. Starting up includes executing it and waiting for it to come up. +>How many times &tdm; should attempt to start up a local &X-Server;. Starting up includes executing it and waiting for it to come up. The default is 1 How many seconds &kdm; should wait for a local &X-Server; to come up. +>How many seconds &tdm; should wait for a local &X-Server; to come up. The default is 15To discover when remote displays disappear, &kdm; regularly pings them. specifies the time (in minutes) between the pings and Whether &kdm; should restart the local &X-Server; after session exit instead of resetting it. Use this if the &X-Server; leaks memory or crashes the system on reset attempts. +>Whether &tdm; should restart the local &X-Server; after session exit instead of resetting it. Use this if the &X-Server; leaks memory or crashes the system on reset attempts. The default is false Controls whether &kdm; generates and uses authorisation for Controls whether &tdm; generates and uses authorisation for local &X-Server; connections. For &XDMCP; displays the authorisation requested by the display is used; foreign non-&XDMCP; displays do not support authorisation at all. Some old &X-Server;s re-read the authorisation file at &X-Server; reset time, instead of when checking the initial connection. As &kdm; generates the authorisation information just before connecting to the display, an old &X-Server; would not get up-to-date authorisation information. This option causes &kdm; to send SIGHUP to the &X-Server; after setting up the file, causing an additional &X-Server; reset to occur, during which time the new authorisation information will be read. +> &X-Server;s re-read the authorisation file at &X-Server; reset time, instead of when checking the initial connection. As &tdm; generates the authorisation information just before connecting to the display, an old &X-Server; would not get up-to-date authorisation information. This option causes &tdm; to send SIGHUP to the &X-Server; after setting up the file, causing an additional &X-Server; reset to occur, during which time the new authorisation information will be read. The default is false This file is used to communicate the authorisation data from &kdm; to the &X-Server;, using the &X-Server; command line option. It should be kept in a directory which is not world-writable as it could easily be removed, disabling the authorisation mechanism in the &X-Server;. If not specified, a random name is generated from xconsole here). The conventional name for a file used here is Xsetup. See . +>. See . Empty by default. @@ -1043,7 +1043,7 @@ >root) after the user authentication process succeeds. The conventional name for a file used here is Xstartup. See . +>. See . Empty by default. @@ -1060,7 +1060,7 @@ >root) after the session terminates. The conventional name for a file used here is Xreset. See . +>. See . Empty by default. @@ -1075,7 +1075,7 @@ This specifies the session program to be executed (as the user owning the session). The conventional name for a file used here is Xsession. See . +>. See . The default is ${If the program fails to execute, &kdm; will fall back to this program. This program is executed with no arguments, but executes using the same environment variables as the session would have had (see ). +> program fails to execute, &tdm; will fall back to this program. This program is executed with no arguments, but executes using the same environment variables as the session would have had (see ). The default is ${Sessions. The default depends on the system &kdm; was built on. +>The default depends on the system &tdm; was built on. @@ -1140,7 +1140,7 @@ >. (the current directory) into this entry. The default depends on the system &kdm; was built on. +>The default depends on the system &tdm; was built on. @@ -1170,7 +1170,7 @@ > When &kdm; is unable to write to the usual user authorisation file ($When &tdm; is unable to write to the usual user authorisation file ($HOME/.Xauthority), it creates a unique file name in this directory and points the environment variable XAUTHORITY If enabled, &kdm; will automatically restart a session after an &X-Server; crash (or if it is killed by Alt-Ctrl-BackSpace). Note that enabling this feature opens a security hole: a secured display lock can be circumvented (unless &kde;'s built-in screen locker is used). +>If enabled, &tdm; will automatically restart a session after an &X-Server; crash (or if it is killed by Alt-Ctrl-BackSpace). Note that enabling this feature opens a security hole: a secured display lock can be circumvented (unless &kde;'s built-in screen locker is used). The default is falsechmod  kdmrctdmrc for obvious reasons. The default is ${kde_datadir}/kdm/sessions}/tdm/sessions. @@ -1564,12 +1564,12 @@ - + The [X-*-Greeter] section class of &kdmrc; +>The [X-*-Greeter] section class of &tdmrc; This section class contains options concerning the configuration of the &kdm; frontend (greeter). +>This section class contains options concerning the configuration of the &tdm; frontend (greeter). @@ -1678,7 +1678,7 @@ > The relative coordinates (percentages of the screen size; X,Y) at which the centre of the greeter is put. &kdm; aligns the greeter to the edges of the screen it would cross otherwise. +>The relative coordinates (percentages of the screen size; X,Y) at which the centre of the greeter is put. &tdm; aligns the greeter to the edges of the screen it would cross otherwise. The default is 50,50If is enabled, this specifies where &kdm; gets the images from: +> is enabled, this specifies where &tdm; gets the images from: The images can be in any format Qt recognises, but the filename must match &kdm;'s expectations: The images can be in any format Qt recognises, but the filename must match &tdm;'s expectations: .face.icon should be a 48x48 icon, while .faceThe default is ${kde_datadir}/kdm/faces}/tdm/faces. @@ -2312,7 +2312,7 @@ > If enabled, &kdm; will automatically start the If enabled, &tdm; will automatically start the krootimage program to set up the background; otherwise, the The default is ${kde_confdir}/kdm/backgroundrc}/tdm/backgroundrc. @@ -2378,7 +2378,7 @@ > This option specifies the maximum time &kdm; will wait for the grabs to succeed. A grab may fail if some other X-client has the &X-Server; or the keyboard grabbed, or possibly if the network latencies are very high. You should be cautious when raising the timeout, as a user can be spoofed by a look-alike window on the display. If a grab fails, &kdm; kills and restarts the &X-Server; (if possible) and the session. +>This option specifies the maximum time &tdm; will wait for the grabs to succeed. A grab may fail if some other X-client has the &X-Server; or the keyboard grabbed, or possibly if the network latencies are very high. You should be cautious when raising the timeout, as a user can be spoofed by a look-alike window on the display. If a grab fails, &tdm; kills and restarts the &X-Server; (if possible) and the session. The default is 3 Enable &kdm;'s built-in Enable &tdm;'s built-in xconsole. Note that this can be enabled for only one display at a time. This option is available only if &kdm; was . Note that this can be enabled for only one display at a time. This option is available only if &tdm; was configured with --enable-tdm-xconsole. The default is The data source for &kdm;'s built-in The data source for &tdm;'s built-in xconsole. If empty, a console log redirection is requested from /dev/consoleShow the Console Login action in the greeter. For this to work, a console must be configured for this particular display, see . +> action in the greeter. For this to work, a console must be configured for this particular display, see . The default is true - + Specifying permanent &X-Server;s Each specification indicates a display which should constantly be managed and which is not using &XDMCP;. This method is typically used only for local &X-Server;s that are started by &kdm;, but &kdm; can manage externally started (Each specification indicates a display which should constantly be managed and which is not using &XDMCP;. This method is typically used only for local &X-Server;s that are started by &tdm;, but &tdm; can manage externally started (foreign) &X-Server;s as well, may they run on the local machine or rather remotely. @@ -2714,12 +2714,12 @@ >localhost prefix from locally running &XDMCP; displays is not stripped to make them distinguishable from local &X-Server;s started by &kdm;. +> stripped to make them distinguishable from local &X-Server;s started by &tdm;. The display class portion is also used in the display-specific sections. This is useful if you have a large collection of similar displays (such as a corral of X terminals) and would like to set options for groups of them. When using &XDMCP;, the display is required to specify the display class, so the manual for your particular X terminal should document the display class string for your device. If it does not, you can run &kdm; in debug mode and portion is also used in the display-specific sections. This is useful if you have a large collection of similar displays (such as a corral of X terminals) and would like to set options for groups of them. When using &XDMCP;, the display is required to specify the display class, so the manual for your particular X terminal should document the display class string for your device. If it does not, you can run &tdm; in debug mode and grep the log for classtty specifies which text console an &X-Server; is covering, so &kdm; knows which console it should monitor for activity after switching to , so &tdm; knows which console it should monitor for activity after switching to Console login to find out when the console session ends. Note that this concept (originating from Solaris) is not perfectly suited for Linux, as there &X-Server;s run on separate virtual terminals and consequently do not actually cover consoles (gettyThe reserve keyword instructs &kdm; to start the display not when &kdm; starts up, but when it is explicitly requested via the command keyword instructs &tdm; to start the display not when &tdm; starts up, but when it is explicitly requested via the command FiFo. If reserve displays are specified, the &kde; menu will have a Start New SessionThe server command specifies the complete &X-Server; command line, including a display number for secondary displays. When &kdm; starts a session, it sets up authorisation data for the &X-Server;. For local servers, &kdm; passes specifies the complete &X-Server; command line, including a display number for secondary displays. When &tdm; starts a session, it sets up authorisation data for the &X-Server;. For local servers, &tdm; passes  filename on the &X-Server;'s command line to point it at its authorisation data. For &XDMCP; displays, &kdm; passes the authorisation data to the &X-Server; via the on the &X-Server;'s command line to point it at its authorisation data. For &XDMCP; displays, &tdm; passes the authorisation data to the &X-Server; via the Accept &XDMCP; message. - + &XDMCP; access control The file specified by the option provides information which &kdm; uses to control access from displays requesting service via &XDMCP;. The file contains four types of entries: entries which control the response to option provides information which &tdm; uses to control access from displays requesting service via &XDMCP;. The file contains four types of entries: entries which control the response to Direct and BroadcastIndirect queries, macro definitions for Indirect entries and entries which control on which network interfaces &kdm; listens for &XDMCP; queries. Blank lines are ignored, entries and entries which control on which network interfaces &tdm; listens for &XDMCP; queries. Blank lines are ignored, # is treated as a comment delimiter causing the rest of that line to be ignored and \Direct queries for a host or pattern, it can be followed by the optional NOBROADCAST keyword. This can be used to prevent a &kdm; server from appearing on menus based on keyword. This can be used to prevent a &tdm; server from appearing on menus based on Broadcast queries. @@ -2811,7 +2811,7 @@ >CHOOSER, Indirect queries are not forwarded, but instead a host chooser dialogue is displayed by &kdm;. The chooser will send a queries are not forwarded, but instead a host chooser dialogue is displayed by &tdm;. The chooser will send a Direct query to each of the remaining host names in the list and offer a menu of all the hosts that respond. The host list may contain the keyword BROADCAST If one or more LISTEN lines are specified, &kdm; listens for &XDMCP; requests only on the specified interfaces. lines are specified, &tdm; listens for &XDMCP; requests only on the specified interfaces. interface may be a hostname or IP address representing a network interface on this machine, or the wildcard * to represent all available network interfaces. If multicast group addresses are listed on a LISTEN line, &kdm; joins the multicast groups on the given interface. For IPv6 multicasts, the IANA has assigned ff0 line, &tdm; joins the multicast groups on the given interface. For IPv6 multicasts, the IANA has assigned ff0X:0:0:0:0:0:0:12b as the permanently assigned range of multicast addresses for &XDMCP;. The X in the prefix may be replaced by any valid scope identifier, such as 1 for Node-Local, 2 for Link-Local, 5 for Site-Local, and so on (see IETF RFC 2373 or its replacement for further details and scope definitions). &kdm; defaults to listening on the Link-Local scope address ff02:0:0:0:0:0:0:12b to most closely match the IPv4 subnet broadcast behavior. If no in the prefix may be replaced by any valid scope identifier, such as 1 for Node-Local, 2 for Link-Local, 5 for Site-Local, and so on (see IETF RFC 2373 or its replacement for further details and scope definitions). &tdm; defaults to listening on the Link-Local scope address ff02:0:0:0:0:0:0:12b to most closely match the IPv4 subnet broadcast behavior. If no LISTEN lines are given, &kdm; listens on all interfaces and joins the default &XDMCP; IPv6 multicast group (when compiled with IPv6 support). To disable listening for &XDMCP; requests altogether, a lines are given, &tdm; listens on all interfaces and joins the default &XDMCP; IPv6 multicast group (when compiled with IPv6 support). To disable listening for &XDMCP; requests altogether, a LISTEN line with no addresses may be specified, but using the [Xdmcp]Supplementary programs The following programs are run by &kdm; at various stages of a session. They typically are shell scripts. +>The following programs are run by &tdm; at various stages of a session. They typically are shell scripts. The Setup, Startup and Reset programs are run as auto if the session results from an automatic login; otherwise, no arguments are passed to them. - + Setup program @@ -2949,7 +2949,7 @@ Note that since &kdm; grabs the keyboard, any other windows will not be able to receive keyboard input. They will be able to interact with the mouse, however; beware of potential security holes here. If is set, Xsetup - + Startup program @@ -3054,11 +3054,11 @@ &kdm; waits until this program exits before starting the user session. If the exit value of this program is non-zero, &kdm; discontinues the session and starts another authentication cycle. +>&tdm; waits until this program exits before starting the user session. If the exit value of this program is non-zero, &tdm; discontinues the session and starts another authentication cycle. - + Session program @@ -3190,7 +3190,7 @@ - + Reset program -- cgit v1.2.1