5.4 Application Configuration

Typically, installed applications have their own configuration files, with their own syntax, etc. It is important that these files be kept separate from the base system, so that they may be easily located and managed by the package management tools.

Typically, these files are installed in diferent place then the usual /etc. In the case where an application has a large number of configuration files, a subdirectory will be created to hold them. For example Apache keeps it's configuration files in /var/www/conf:

drwxr-xr-x  2 root  daemon    512 Jan  1 15:11 .
drwxr-xr-x  8 root  daemon    512 Jan  1 06:21 ..
-r--r--r--  1 root  bin       285 Jul 23 15:40 access.conf
-r--r--r--  1 root  bin       285 Jul 23 15:40 access.conf-dist
-r--r--r--  1 root  daemon  34480 Jan  1 15:11 httpd.conf
-r--r--r--  1 root  daemon  44153 Jan  1 15:11 httpd.conf-dist
-r--r--r--  1 root  daemon  12965 Jan  1 15:11 magic
-r--r--r--  1 root  daemon  12381 Jan  1 15:11 mime.types
-r--r--r--  1 root  bin       297 Jul 23 15:40 srm.conf
-r--r--r--  1 root  bin       297 Jul 23 15:40 srm.conf-dist

The Apache application is chrooted by default and can be started from rc.conf file located in /etc. To remove the chroot environment which can cause prolems with some web applications you can start it with:

# httpd -u

You can use apachectl tool to start, stop, restart, configtest the httpd server.

This, and other documents, can be downloaded from MicroBSD.

For questions about MicroBSD, read the documentation before contacting <MicroBSD Support>.
Copyright © 1995-2003 by The FreeBSD Documentation Project, OpenBSD FAQ Copyright © 1998-2003 OpenBSD, Modified for MicroBSD