GDM has a number of configuration interfaces. These include scripting. These types of integration are. The GDM script integration points can be found in the. The Init, Post. Login. Pre. Session, and Post.
Ubuntu manuals. go. NAME gdm - GNOME Display Manager SYNOPSIS gdm DESCRIPTION gdm is the equivalent of xdm. gdm reads /etc/gdm/custom.conf for its configuration.
Session. scripts all work as described below. For each type of script, the default one which will be executed is. Default" and is stored in a directory associated with. So the default Init script is. Init/Default. A per- display. Such scripts are stored in the same directory as the. Xserver DISPLAY value for.
For example, if the < Init> /: 0. DISPLAY ": 0". All of these scripts are run with root privilege and return 0 if run. Also note that GDM will. When the Xserver for the login GUI has been successfully started, but.
GUI is actually displayed, GDM will run the. Init script. This script is useful for starting. After the user has been successfully authenticated GDM will run the.
Manual Pages; Documentation Project Primer; All Books and Articles. What location does GDM look for the custom.conf? I've seen /etc/gdm, /etc/X11/etc. From ArchWiki. Jump to: navigation, search. add the following to /etc/gdm/custom.conf. GDM Reference Manual. 2.2. The Configuration File - gdm.conf. The daemon and the accompanying utilities share a common configuration file: etc/gdm/gdm.conf. Troubleshooting. GNOME Display Manager Reference Manual. set the debug/Enable key to 'true' in the <etc>/gdm/custom.conf file and restart GDM.
Post. Login script. This is done before any session. This. script is useful for doing any session initialization that needs to.
For example, you might setup the. HOME directory if needed. After the user session has been initialized, GDM will run the. Pre. Session script.
GNOME Display Manager Reference Manual; GDM has a number of configuration interfaces. The GDM daemon is configured using the <etc>/gdm/custom.conf file.
This script is useful for. It can be used for session management or.
When a user terminates their session, GDM will run the. Post. Session script.
Note that the Xserver will. Note that the Post. Session script will be run. I/O error or. similar. Thus, there is no guarantee that X applications will work.
All of the above scripts will set the. RUNNING_UNDER_GDM environment variable to. If the scripts are also shared with other. GDM is calling these. GDM is used. The < share> /gdm/autostart/Login. Window. directory contains files in the format specified by the. Free. Desktop. org Desktop Application Autostart.
Specification". Standard features in the specification may be. GConf configuration value is set, etc. Any . desktop files in this directory will cause. GUI. greeter. By default, GDM is shipped with files which will autostart.
GUI greeter itself, the. These programs are needed for the greeter. In addition, desktop files are provided for starting. AT programs if the configuration values specified in the. Accessibility Configuration section below are set. There is also an Xsession script located at.
Xsession which is called between. Pre. Session and the. Post. Session scripts. This script does not. This script is used for. This script is run as the user. Desktop session. file the user selected to start.
The GDM daemon is configured using the. Default. values are stored in GConf in the gdm. It is recommended that end- users modify the. GDM. Note that older versions of GDM supported additional configuration. GDM. The < etc> /gdm/custom. Keywords in brackets.
Empty lines or. lines starting with the hash mark (#) are ignored. The file < etc> /gdm/custom.
Within each group, there are particular key/value. GDM behaves. For example. Timed. Login. Enable=true. A full list of supported configuration keys follow. Multicast. If true and IPv. Multicast. Addr. This is the Link- local multicast address.
Timed. Login. Enable. If the user given in Timed. Login should be. logged in after a number of seconds (set with. Timed. Login. Delay) of inactivity on the. This is useful for public access terminals or. If the user uses the keyboard or.
Timed. Login. Delay or 3. If the user does not enter a username but just. ENTER key while the login program is requesting the.
GDM will assume the user wants to login. Note that no password will be. PAM it can be configured to require password entry before. Refer to the "Security- > PAM". Timed. Login. This is the user that should be logged in after a specified. If the value ends with a vertical bar | (the pipe symbol).
GDM will execute the program specified and use whatever. The program is run with the DISPLAY environment variable set so. For example if the value is "/usr/bin/getloginuser|".
Timed. Login. Delay. Delay in seconds before the Timed. Login. user will be logged in. Automatic. Login.
Enable. Automatic. Login. Enable=false. If true, the user given in Automatic. Login. should be logged in immediately. This feature is like timed. Automatic. Login.
This is the user that should be logged in immediately if. Automatic. Login.
Enable is true. If the value ends with a vertical bar | (the pipe symbol). GDM will execute the program specified and use whatever. The program is run with the DISPLAY environment variable set so. For example if the value is "/usr/bin/getloginuser|". User. The username under which the greeter and other GUI programs. Refer to the Group. Security- > GDM User And.
Group" section of this document for more information. Group. The group name under which the greeter and other GUI programs. Refer to the User. Security- > GDM User And. Group" section of this document for more information. Enable. To enable debugging, set the debug/Enable key to. GDM. Then debug output will be sent to the.
Operating System). Include. All. If true, then the face browser will show all users on the local. If false, the face browser will only show users who. When this key is true, GDM will call fgetpwent() to get a list.
Any users with a user id less. Oracle Solaris) are filtered. The Face Browser also will display any users that have. NIS/LDAP. users). It gets this list via calling the. Console. Kit interface.
It will. also filter out any users which do not have a valid shell. If false, then GDM more simply only displays users that have. NIS/LDAP users) by. Console. Kit interface. Include. Set to a list of users to always include in the Face Browser.
This value is set to a list of users separated by commas. By. default, the value is empty. Exclude. Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody. Set to a list of users to always exclude in the Face Browser. This value is set to a list of users separated by commas. Note. that the setting in the custom. Disallow. TCP. If true, then always append - nolisten tcp.
Xservers, thus. disallowing TCP connection. This is a more secure. Displays. Per. Host. To prevent attackers from filling up the pending queue, GDM.
If. you want to provide display services to computers with more. Note that the number of attached DISPLAYS allowed is not. Only remote connections via XDMCP are limited by. Enable. Setting this to true enables XDMCP support allowing remote. X terminals to be managed by GDM.
UDP port 1. 77. See the Port option for more information. If GDM is compiled to support it, access from remote displays. TCP Wrappers library. The service. name is gdm. You should add. to your < etc> /hosts.
TCP Wrappers configuration. See the. hosts. allow. Please note that XDMCP is not a particularly secure protocol. UDP port 1. 77 on your.
Honor. Indirect. Enables XDMCP INDIRECT choosing (i. X- terminals which do not. Max. Pending. To avoid denial of service attacks, GDM has fixed size queue.
Only Max. Pending displays can start at. Please note that this parameter does not limit the number of. It only limits the number.
Max. Sessions. Determines the maximum number of remote display connections. I. e. the total number of. Max. Wait. When GDM is ready to manage a display an ACCEPT packet is sent. XDMCP conversations. GDM will then place the session id in the pending queue. MANAGE request. If no response is received within Max. Wait seconds, GDM will.
Max. Wait. Indirect. The Max. Wait. Indirect parameter determines the maximum number of.
When the timeout is exceeded, the information about the. The information may be forgotten earlier if. Max. Pending. Indirect. Ping. Interval. Seconds. If the Xserver does not respond in the specified number of. When this happens the slave daemon dies with an ALARM signal.
Note that GDM 2. 2. GDM 2. 2. 0 and earlier to a newer version. Note that GDM in the past used to have a.
Ping. Interval configuration key which was. For most purposes you'd want this setting.
However since in most cases where. XDMCP would be used (such as terminal labs), a lag of more. Port. The UDP port number gdm should listen to. XDMCP requests. Do not change this unless you know what. Willing. Willing=< etc> /gdm/Xwilling.
When the machine sends a WILLING packet back after a QUERY it. The default message is the system ID, but it is possible to. If this. script does not exist or this key is empty the default message.
If this script succeeds and produces some output. It runs at most once every 3 seconds to prevent. QUERY. packets. The GDM default greeter is called the simple Greeter and is. GConf. Default values are stored in GConf in the. These defaults. can be overridden if the "gdm" user has a writable $HOME.
GConf settings. These values can be edited using. The following configuration options are supported.
Greeter Configuration Keys/apps/gdm/simple- greeter/banner_message_enable. Controls whether the banner message text is displayed. Specifies the text banner message to show on the greeter. Controls whether to show the restart buttons in the login. If true, then the face browser with known users is not shown.
Set to the themed icon name to use for the greeter logo. Set to a list of languages to be shown by default in the login. Default value is "[]". With the default setting only. Other..". which pops- up a dialog box showing a full list of available. Users are not intended to change this setting by hand. Instead. GDM keeps track of any languages selected in this configuration.
Other.." choice. This way, commonly selected languages. Set to a list of keyboard layouts to be shown by default in the. Default value is "[]". With the default setting. Other.." which pops- up a dialog box showing a full list of. Users are not intended to change this setting by hand. Instead. GDM keeps track of any keyboard layouts selected in this.
Other.." choice. This way, commonly. Controls whether compiz is used as the window manager instead. This section describes the accessibility configuration options available.
The GDM greeter panel at the login screen displays an accessibility. Clicking on that icon opens the GDM Accessibility Dialog.
Ubuntu Manpage. Provided by: gdm_3. NAME. gdm - GNOME Display Manager.
DESCRIPTIONgdm is the equivalent of xdm(1x) or wdm(1x), but uses the GNOME. GNOME look- and- feel. It provides the GNOME. For each local. display, gdm starts an X server and runs a minimal GNOME session. If configured so, the main gdm process. XDMCP requests from remote displays.
These requests. can either be direct, causing gdm to start a session on the remote. When managing a display, gdm attempts to execute /etc/gdm/Init/display. Init/Default if that does not exist. When a user logs in.
Pre. Session/display (or. Pre. Session/Default), and then one of the sessions defined in. When the session has completed, gdm attempts to. Post. Session/display, or /etc/gdm/Post. Session/Default. gdm maintains information about the displays it is managing in. This includes xauth information, so this directory is not. PAM to perform authentication using the config file.
XAUTHORITY. Upon session startup, GDM sets the XAUTHORITY environment variable. Applications and scripts that assume this file is set to. Xauthority will not work. To access the display you need both.
DISPLAY and XAUTHORITY variables. Martin Kasper Petersen < mkp@Sun. SITE. auc. dk>. This manual page written by Steve Haslam < araqnid@debian. Debian GNU/Linux. Updated by Raphaeel Hertzog < hertzog@debian.
Ryan Murray < rmurray@debian. Josselin Mouette < joss@debian. Vincent Lefevre < vincent@vinc. Powered by the Ubuntu Manpage Repository generator. Dustin Kirkland© 2. Canonical Ltd. Ubuntu and Canonical are registered trademarks of Canonical Ltd.