1
by joey
move from cvs import |
1 |
# This is the main config file for debconf. It tells debconf where to
|
2 |
# store data. The format of this file is a set of stanzas. Each stanza
|
|
3 |
# except the first sets up a database for debconf to use. For details, see
|
|
4 |
# debconf.conf(5) (in the debconf-doc package).
|
|
5 |
#
|
|
6 |
# So first things first. This first stanza gives the names of two databases.
|
|
7 |
||
8 |
# Debconf will use this database to store the data you enter into it,
|
|
9 |
# and some other dynamic data.
|
|
10 |
Config: configdb |
|
11 |
# Debconf will use this database to store static template data.
|
|
12 |
Templates: templatedb |
|
13 |
||
14 |
# World-readable, and accepts everything but passwords.
|
|
15 |
Name: config |
|
16 |
Driver: File |
|
17 |
Mode: 644 |
|
18 |
Reject-Type: password |
|
19 |
Filename: /var/cache/debconf/config.dat |
|
20 |
||
21 |
# Not world readable (the default), and accepts only passwords.
|
|
22 |
Name: passwords |
|
23 |
Driver: File |
|
24 |
Mode: 600 |
|
25 |
Backup: false |
|
26 |
Required: false |
|
27 |
Accept-Type: password |
|
28 |
Filename: /var/cache/debconf/passwords.dat |
|
29 |
||
30 |
# Set up the configdb database. By default, it consists of a stack of two
|
|
31 |
# databases, one to hold passwords and one for everything else.
|
|
32 |
Name: configdb |
|
33 |
Driver: Stack |
|
34 |
Stack: config, passwords |
|
35 |
||
36 |
# Set up the templatedb database, which is a single flat text file
|
|
37 |
# by default.
|
|
38 |
Name: templatedb |
|
39 |
Driver: File |
|
40 |
Mode: 644 |
|
41 |
Filename: /var/cache/debconf/templates.dat |
|
42 |
||
43 |
# Well that was pretty straightforward, and it will be enough for most
|
|
44 |
# people's needs, but debconf's database drivers can be used to do much
|
|
45 |
# more interesting things. For example, suppose you want to use config
|
|
46 |
# data from another host, which is mounted over nfs or perhaps the database
|
|
47 |
# is accessed via LDAP. You don't want to write to the remote debconf database,
|
|
48 |
# just read from it, so you still need a local database for local changes.
|
|
49 |
#
|
|
50 |
# A remote NFS mounted database, read-only. It is optional; if debconf
|
|
51 |
# fails to use it it will not abort.
|
|
52 |
#Name: remotedb
|
|
53 |
#Driver: DirTree
|
|
54 |
#Directory: /mnt/otherhost/var/cache/debconf/config
|
|
55 |
#Readonly: true
|
|
56 |
#Required: false
|
|
57 |
#
|
|
58 |
# A remote LDAP database. It is also read-only. The password is really
|
|
59 |
# only necessary if the database is not accessible anonymously.
|
|
582
by joeyh
* Applied Davor Ocelic's patch adding a keybykey option to the LDAP |
60 |
# Option KeyByKey instructs the backend to retrieve keys from the LDAP
|
61 |
# server individually (when they are requested), instead of loading all
|
|
62 |
# keys at startup. The default is 0, and should only be enabled if you
|
|
63 |
# want to track accesses to individual keys on the LDAP server side.
|
|
1
by joey
move from cvs import |
64 |
#Name: remotedb
|
65 |
#Driver: LDAP
|
|
66 |
#Server: remotehost
|
|
67 |
#BaseDN: cn=debconf,dc=domain,dc=com
|
|
68 |
#BindDN: uid=admin,dc=domain,dc=com
|
|
69 |
#BindPasswd: secret
|
|
582
by joeyh
* Applied Davor Ocelic's patch adding a keybykey option to the LDAP |
70 |
#KeyByKey: 0
|
1
by joey
move from cvs import |
71 |
#
|
72 |
# A stack consisting of two databases. Values will be read from
|
|
73 |
# the first database in the stack to contain a value. In this example,
|
|
74 |
# writes always go to the first database.
|
|
75 |
#Name: fulldb
|
|
76 |
#Driver: Stack
|
|
77 |
#Stack: configdb, remotedb
|
|
78 |
#
|
|
79 |
# In this example, we'd use Config: fulldb at the top of the file
|
|
80 |
# to make it use the combination of the databases.
|
|
81 |
#
|
|
82 |
# Even more complex and interesting setups are possible, see the
|
|
83 |
# debconf.conf(5) page for details.
|