On 25/03/2011 12:06, Peter Sørensen wrote:
I've already used the proxymap solution. We ran into serious problems with the
clustered mysql backend.
I have 5 servers with smtd set to max 300.
I will get back to the proxymap solution. I have adjusted some settings in the
mysql backend.
But still - this annoys me. What is triggering postfix to make this behavior?
Postfix reads its config files at startup, so if you change a file then
you have to restart it for the changes to take effect. To save you the
effort of manually restarting it every time, Postfix automatically
restarts if a hash file is changed. This is desired behaviour, because
there is no point changing the file if you don't want the changes to be
picked up by Postfix.
If you don't want Postfix restarting every five minutes then either
a) use MySQL directly as the backend (either via mysql: or proxy:mysql:)
b) only regenerate the hash files when there is actually a need to (ie,
when something changes in the database) rather than every five minutes
on a schedule
c) change the schedule so that it runs less frequently
Mark
--
http://mark.goodge.co.uk
http://www.ratemysupermarket.com
