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
|
<!doctype linuxdoc system>
<article>
<title>All configuration files
<sect>Purpose
<p>
<em/Linuxconf/ 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:
<descrip>
<tag/(A blank)/
This file is only read by <em/linuxconf/, which means
one of two things. Either it is a reference file used by
<em/Linuxconf/ or <em/Linuxconf/ does not know yet how
to manage this file, but may use its contents.
<tag/E/
This file is erased at boot time by linuxconf.
<tag/G/
This file is generated by <em/Linuxconf/. It never
reads it again. <em/Linuxconf/ uses other files
(probably <tt>/etc/conf.linuxconf</tt>) to store
the configuration related to this service.
For example, the file <tt>/etc/sendmail.cf</tt> is used this way.
<tag/M/
The file is fully managed by <em/Linuxconf/.
<em/Linuxconf/ 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 <em/Linuxconf/'s ability to manage the file.
<tag/O/
This file is optional on a <em/Linux/ system; its existence
is not crucial. However, erasing it is not a good idea.
<tag/P/
<em/Linuxconf/ knows little about this file, but does
probe for its presence and modification time. Based on
these facts, <em/Linuxconf/ will decide if a service is needed
or if a daemon must be restarted or signaled.
<tag/V/
<em/Linuxconf/ 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.
<tag/*/
This flag indicates that the path to the configuration file
has been changed from the original/official value
known by Linuxconf.
</descrip>
</article>
|
