I really like having a local config file [much better than the old days of having to compile the database name in, etc]; and I like being able to just 'vi' a file to enable logging, adjust process levels on one of the hosts, etc.
If you want to do database configs as well, then the syntax below would work -- but rather than via hostname, I'd recommend making it some form of 'clientid/configid' which could be supplied on command lines (e.g. ./dbmail-pop3d -configkey DEFAULT) That would allow configs to be experimented with and changed between without having to affect other daemons on the same host, etc. Personally I just say keep the config files :) Cheers, Mark. > dbmail.conf: > Is a configuration file in /etc or wherever. > - database information > - logging info > - hostname / clustering info > > dbmail_conf: > Is a table in the database. > - Has detailed config info in host/key/value pairs: > > CREATE TABLE dbmail_conf ( > hostname VARCHAR(128) NOT NULL, > key VARCHAR(32) NOT NULL, > value TEXT NULL, > UNIQUE INDEX (hostname, key) > )
