Slight updates.
[doldaconnect.git] / doc / doldacond.conf.5.in
... / ...
CommitLineData
1.\"
2.\" Copyright (C) 2007 Fredrik Tolf (fredrik@dolda2000.com)
3.\"
4.\" This is free documentation; you can redistribute it and/or
5.\" modify it under the terms of the GNU General Public License as
6.\" published by the Free Software Foundation; either version 2 of
7.\" the License, or (at your option) any later version.
8.\"
9.\" The GNU General Public License's references to "object code"
10.\" and "executables" are to be interpreted as the output of any
11.\" document formatting or typesetting system, including
12.\" intermediate and printed output.
13.\"
14.\" This manual is distributed in the hope that it will be useful,
15.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
16.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
17.\" GNU General Public License for more details.
18.\"
19.\" You should have received a copy of the GNU General Public
20.\" License along with this manual; if not, write to the Free
21.\" Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111,
22.\" USA.
23.\"
24.TH DOLDACOND.CONF 5 "@DATE@" "" "Dolda Connect manual"
25.SH NAME
26doldacond.conf \- Dolda Connect daemon configuration file
27.SH DESCRIPTION
28The \fBdoldacond\fP(8) daemon will examine the doldacond.conf file
29upon startup and reception of SIGHUP. The file is written in a
30line-oriented ASCII format, using the following rules.
31.P
32A line is either empty, a comment, or a configuration directive. Empty
33lines are permitted to contain horizontal whitespace, but nothing
34else. A comment line begins with a hash sign (`#'), optionally
35preceded by whitespace. A configuration directive is a line with at
36least one token, each token being a series of non-whitespace
37characters or quoted whitespace characters. Quoting can be done either
38by surrounding the characters to be quoted with double quotation
39marks, or by preceding a single character to be quoted with a
40backslash. The first token is considered the directive to be
41evaluated, and the rest being arguments to the directive. Each of the
42possible configuration directives are described in their own sections.
43.SH CONFIGURATION VARIABLES
44The vast majority of the daemon's configuration is controlled via
45named configuration variables. The \fBset\fP directive is used to set
46the value of the configuration variables, which obeys the following
47syntax:
48.P
49\fBset\fP \fIvariable\fP \fIvalue\fP
50.P
51The value of a variable is either a boolean, an integer, a string or
52an IPv4 address. Which one depends on the variable. A boolean may be
53specified using either \fBtrue\fP/\fBfalse\fP, \fBon\fP/\fBoff\fP,
54\fByes\fP/\fBno\fP or \fB1\fP/\fB0\fP. Integers may be given in either
55decimal, octal or hexadecimal format, using standard C syntax \- that
56is, hexadecimal numbers prefixed with \fB0x\fP, octal numbers prefixed
57with \fB0\fP, or directly entered decimal numbers. Strings may contain
58arbitrary Unicode characters, and are decoded according to the
59system's default character coding. IPv4 addresses are specified in
60dotted quad decimal notation. A list of all the known configuration
61variables follows.
62@VARIABLES@
63.SH TOS VALUES
64Some configuration variables specify IP Type of Service values. Valid
65values for those variables are as follows:
66.TP
670
68System default TOS.
69.TP
701
71Minimize cost
72.TP
732
74Maximize reliability
75.TP
763
77Maximize throughput
78.TP
794
80Minimize delay
81.P
82How routers interpret TOS values is defined by the administrator of
83those routers. For IPv6 connections, which use Diffserv instead of the
84older IPv4 TOS values, the Diffserv values to use are specified by the
85\fBnet.diffserv-mincost\fP, \fBnet.diffserv-maxrel\fP,
86\fBnet.diffserv-maxtp\fP and \fBnet.diffserv-mindelay\fP configuration
87variables, as described above.
88.SH FILES
89All file names specified in the configuration file, and the
90configuration file itself, are looked up by the daemon in a rather
91flexible manner. The only difference between the main configuration
92file and all other files is that the configuration must always be
93named \fBdoldacond.conf\fP, while the name of all other files may be
94specified in the configuration file. In all else, lookup is done
95according to the following rules:
96.TP
971
98If the specified name contains any slashes (not applicable for
99doldacond.conf), it will be considered absolute, and no locations
100other than the explicitly specified will be examined.
101.TP
1022
103The home directory of the user running the daemon (as specified by
104either the \fBHOME\fP environment variable or as returned by the
105\fBgetpwuid\fP(3) function) is checked for a dot-file with the
106specified name.
107.TP
1083
109If the \fBPATH\fP environment variable exists, the directories it
110specifies are iterated, the last path element of each is replaced by
111`etc', and the resulting directories are checked for the existence of
112the specified file. For example, if \fBPATH\fP is
113/bin:/opt/doldaconnect/bin:/usr/bin, the directories /etc,
114/opt/doldaconnect/etc and /usr/etc will be checked for the file.
115.TP
1164
117If the \fBPATH\fP environment variable does not exist (but \fInot\fP
118if \fBPATH\fP does exist and the file simply could not be found
119according to the previous rule), the directories /usr/local/etc, /etc
120and /usr/etc are checked for the file.
121.P
122For files that are created on the fly, such as the hash cache, the
123file will be overwritten in place if found. If not found, it will be
124created in the home directory of the user running the daemon. If the
125home directory cannot be determined, the file will be created in /etc.
126.SH BUGS
127IPv4 should also be able to use Diffserv instead of TOS. I have simply
128not been able to find the API to set IPv4 Diffserv values.
129.SH AUTHOR
130Fredrik Tolf <fredrik@dolda2000.com>
131.SH SEE ALSO
132\fBdoldacond\fP(8)