dnscheck-dispatcher shares configuration files with the DNSCheck perl
modules. Or, to be more precise, it creates such an object and then queries
its configuration object for its configuration information. It also uses the
DNSCheck object to get its database connection.
There are two keys in the configuration YAML files that are of interest for
the dispatcher. The first one is syslog. It has the subkeys ident, which
specifies the name the daemon will use when talking to syslogd, and
facility, which specifies the syslog facility to use.
The second one is daemon. It has the subkeys pidfile, errorlog,
maxchild and savelevel. They specify, in order, the file where the
daemon will write its PID after it has detached, the file it will redirect its
standard error to, the maximum number of concurrent child processes it may
have and the minumum log level to save to the database. Make sure to set the
pathnames to values where the user the daemon is running under has write
permission, since it will terminated if they are specified but cant be
written to. Additionally, running with a maxchild value of n means that at
least n+1 simultaneous connections to the database will be opened. Make sure
that the database can actually handle that, or everything will die with more
or less understandable error messages.
If everything works as intended nothing should ever be written to the
errorlog. All normal log outout goes to syslog (and, with the debug flag,