blob: 559823b863ac28edc5ef1f1f107a17ffcd200964 [file] [log] [blame]
Patrick Williamsb48b7b42016-08-17 15:04:38 -05001# GDM Custom Configuration file.
2#
3# This file is the appropriate place for specifying your customizations to the
4# GDM configuration. If you run gdmsetup, it will automatically edit this
5# file for you and will cause the daemon and any running GDM GUI programs to
6# automatically update with the new configuration. Not all configuration
7# options are supported by gdmsetup, so to modify some values it may be
8# necessary to modify this file directly by hand.
9#
10# This file overrides the default configuration settings. These settings
11# are stored in the GDM System Defaults configuration file, which is found
12# at the following location.
13#
14# /usr/share/gdm/defaults.conf.
15#
16# This file contains comments about the meaning of each configuration option,
17# so is also a useful reference. Also refer to the documentation links at
18# the end of this comment for further information. In short, to hand-edit
19# this file, simply add or modify the key=value combination in the
20# appropriate section in the template below this comment section.
21#
22# For example, if you want to specify a different value for the Enable key
23# in the "[debug]" section of your GDM System Defaults configuration file,
24# then add "Enable=true" in the "[debug]" section of this file. If the
25# key already exists in this file, then simply modify it.
26#
27# Older versions of GDM used the "gdm.conf" file for configuration. If your
28# system has an old gdm.conf file on the system, it will be used instead of
29# this file - so changes made to this file will not take effect. Consider
30# migrating your configuration to this file and removing the gdm.conf file.
31#
32# If you hand edit a GDM configuration file, you can run the following
33# command and the GDM daemon will immediately reflect the change. Any
34# running GDM GUI programs will also be notified to update with the new
35# configuration.
36#
37# gdmflexiserver --command="UPDATE_CONFIG <configuration key>"
38#
39# e.g, the "Enable" key in the "[debug]" section would be "debug/Enable".
40#
41# You can also run gdm-restart or gdm-safe-restart to cause GDM to restart and
42# re-read the new configuration settings. You can also restart GDM by sending
43# a HUP or USR1 signal to the daemon. HUP behaves like gdm-restart and causes
44# any user session started by GDM to exit immediately while USR1 behaves like
45# gdm-safe-restart and will wait until all users log out before restarting GDM.
46#
47# For full reference documentation see the gnome help browser under
48# GNOME|System category. You can also find the docs in HTML form on
49# http://www.gnome.org/projects/gdm/
50#
51# NOTE: Lines that begin with "#" are considered comments.
52#
53# Have fun!
54
55[daemon]
56
57[security]
58
59[xdmcp]
60
61[gui]
62
63[greeter]
64
65[chooser]
66
67[debug]
68
69# Note that to disable servers defined in the GDM System Defaults
70# configuration file (such as 0=Standard, you must put a line in this file
71# that says 0=inactive, as described in the Configuration section of the GDM
72# documentation.
73#
74[servers]
75
76# Also note, that if you redefine a [server-foo] section, then GDM will
77# use the definition in this file, not the GDM System Defaults configuration
78# file. It is currently not possible to disable a [server-foo] section
79# defined in the GDM System Defaults configuration file.
80#