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
|
All configuration files
11.. PPuurrppoossee
_L_i_n_u_x_c_o_n_f uses, manages, probes and generates various files. The
current list shows the filenames, the path to the files, and a set of
flags. The following values are possible:
((AA bbllaannkk))
This file is only read by _l_i_n_u_x_c_o_n_f, which means one of two
things. Either it is a reference file used by _L_i_n_u_x_c_o_n_f or
_L_i_n_u_x_c_o_n_f does not know yet how to manage this file, but may use
its contents.
EE This file is erased at boot time by linuxconf.
GG This file is generated by _L_i_n_u_x_c_o_n_f. It never reads it again.
_L_i_n_u_x_c_o_n_f uses other files (probably /etc/conf.linuxconf) to
store the configuration related to this service. For example,
the file /etc/sendmail.cf is used this way.
MM The file is fully managed by _L_i_n_u_x_c_o_n_f. _L_i_n_u_x_c_o_n_f knows how to
parse it and write it back properly. This also means that you
are allowed to edit the file by hand (using a text editor)
without breaking _L_i_n_u_x_c_o_n_f's ability to manage the file.
OO This file is optional on a _L_i_n_u_x system; its existence is not
crucial. However, erasing it is not a good idea.
PP _L_i_n_u_x_c_o_n_f knows little about this file, but does probe for its
presence and modification time. Based on these facts, _L_i_n_u_x_c_o_n_f
will decide if a service is needed or if a daemon must be
restarted or signaled.
VV _L_i_n_u_x_c_o_n_f uses special virtual files. They generally represent
limited views of some real config file. These files are used
especially to achieve fine-grain-system-profile- versioning and
cluster management.
** This flag indicates that the path to the configuration file has
been changed from the original/official value known by
Linuxconf.
|
