All configuration files: Purpose

Next Previous Contents

## 1. Purpose

Linuxconf uses, manages, probes and generates various files. The current list shows all of them. The list presents the path of the file and a set of flags. Here are the different values possible:

(A blank)

  This file is only read by Linuxconf. This means two things. Either it is a reference file used by Linuxconf or Linuxconf does not know yet how to manage this file, but use its content.

E

  This file is erased at boot time by linuxconf.

G

  This file is generated by Linuxconf. It never reads it again. Linuxconf use other files (probably `/etc/conf.linuxconf`) to store the configuration related to this service. `/etc/sendmail.cf` is an example of this.

M

  The file is fully managed by Linuxconf. This means that 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 the ability of Linuxconf to manage it.

O

  This file is optional on a Linux system. Not having it is not bad. This does not mean erasing it is a good idea.

P

  Linuxconf knows little about this file. It only probes for its presence and modification time. Based on this, Linuxconf will decide if a service is needed or a daemon must be restarted, or signaled.

V

  Linuxconf uses special virtual files. They generally represent limited views of some real config file. This is used especially to achieve fine grain system profile versionning and cluster management.

*

  This flag indicates that the path of the configuration file has been changed from the original/official value known by linuxconf.

Next Previous Contents