On Thu, May 08, 2014 at 05:56:33PM -0400, Wietse Venema wrote:
> The first step to adopting this into Postfix is now approaching
> completion. Viktor ported the latest Debian-style dynamicmaps.cf
> support to Postfix 2.12, and I have been working to finish it.
One thing we need to nail down is the location of the dynamicmaps.cf
file itself.
With Debian this goes into ${config_directory}/dynamicmaps.cf,
which is problematic with multiple instances. There really should
be only one dynamicmaps.cf per system, not per Postfix instance.
The postfix-2.12-20140508-nonprod solution is to put dynamicmaps.cf
into $daemon_directory, which addresses the above issue, but raises
a new one. We now have a volatile system-specific configuration
file that needs to get updated by packages that install new table
drivers that lives in $daemon_directory.
Until not too long ago, I used to maintain multiple Postfix releases
in AFS, and daemon_directory was in read-only AFS storage, it was
the same for all systems with that particular Postfix release. In
other words, daemon-directory was shareable between hosts and could
be mounted read-only.
Adding dynamicmaps.cf to $daemon_directory forces it to be non-shared
and writable by each system. This is also not backwards compatible
with the existing location of the file on Debian.
I had suggested putting dynamicmaps.cf in the compile-time default
configuration directory, which is typically /etc/postfix (no change
for Debian) and is definitely system-specific. I don't recall why
we switched to $daemon_directory, but perhaps we should reconsider?
--
Viktor.
