Ulrich Zehl wrote:
In my setup, I have a hash table that's used in relay_domains, like so:
relay_domains =
hash:/etc/postfix-incoming/maps/domains,
hash:/etc/postfix-incoming/maps/auto/domains
Currently, this table is completely rebuilt from a database every five
minutes or so, even if there are no changes. (This makes the programm that
builds it simpler.)
This causes qmgr to restart itself whenever it notices that the table has
changed:
May 6 11:49:42 allina postfix-incoming/qmgr[19084]: table
hash:/etc/postfix-incoming/maps/auto/domains(0,lock|fold_fix has changed --
restarting
From what I read in the documentation, qmgr is supposed to be a long-living
process. Are there any important drawbacks from having it restarted so
frequently, like extra work that has to be performed at process startup?
Should I modify my program to change the table only when there are changes?
What other settings (and the files they reference) may have this impact on
qmgr?
I apologize if the answers are already in the documentation, and I simply
didn't find them. Please tell me in which READMEs or man pages they are,
and I'll go look for them myself.
Ulrich
Yes, frequently restarting qmgr will cause excessive load.
Basically the same as restarting postfix - all mail in the
active queue is moved to incoming, then reprocessed and moved
back to active. This is a killer for performance.
Anyway, far far better to only rebuild the file if the input
has changed.
-- Noel Jones
