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