Robert Spier wrote:
This gets us into DJB vs not-DJB, which is not somewhere I really want
to go. Personally, I like all my configuration in one place, instead
of having to look in multiple files.
That ship sailed a really long time ago:
1) we are using daemontools as the process management framework;
2) we still have tcpserver in the run file for non-forked execution;
3) we have a bazillion config/files for each and every plugin.
I have three servers running with the same configuration files (all
stored in Subversion). I cannot tell you how much easier it is that I
have separated configuration this way. Installing a new release is a
matter of checking out the new release, copying the env/ directory
(which isn't version controlled) from the old installation, and starting
it up.
As long as there's an env-sample/ directory, your run file is peachy
keen.
I'll do that, plus I'll have multiple run files included, with the
default being the forkserver variant that I use. I'll add a
README.running where I document the multiple ways of starting up qpsmtpd
(including anything from README which doesn't belong there any more).
You can revert it if you hate it! ;-)
John
