On 04/06/2011 06:15 PM, dchil...@bestmail.us wrote:
postscreen& stress support. I see in the postscreen docs that certain
paramaters support stress parameters. To find out how to turn it on, I
have to go to the stress docs, and find the "-o stress=yes" param, then
surmise that it need to be added to the master.cf entry that contains
postscreen, only in the postfix instance that invokes it, and not in the
'primary' config that's declared to be "more equal than others" ...
As the documentation for -o stress= explains, this is not an option that
YOU enable.
Rather, specific postfix configuration settings either support it, or not.
If they support it, when (any of) the limits defined for
stress-dependent configuration options are exceeded, *postfix* turns on
the stress-adaptive option:
http://www.postfix.org/STRESS_README.html#adapt
In retrospect, or to the experienced user, the answer may be obvious.
To me it wasn't. It could've been made much simpler, imo, without
really changing the docs, but rather by having a commented set of config
files from a single, working, 'complex' example -- where I could SEE
what was done.
You probably haven't calculated the absurd number of possible
configurations.
as a 2nd example, TLS, which I'd mentioned in another message. again,
I've found the docs& man pages, and read through them. I'm still not
sure in how many places I'm supposed to add my key definitions, for
example. Only in the postscreen containing postfix instance's main.cf?
as "tls_" params for tlsproxy? Do I also need to add key defs in other
instances' configs? And if so, as "tls_" params for tlsproxy or as
"smtpd_" params? (this, e.g., "tlsproxy_tls_CAfile ($smtpd_tls_CAfile)"
is not clear as usage from the docs ...).
What IS clear from the docs, since it is referred to multiple times, is
that in general, the settings in main.cf are the defaults for the daemon
that uses each particular setting.
You can override most of the per-daemon settings in master.cf in their
respective service definitions - and in some cases, it only makes sense
to do so in master.cf (think of syslog_name for separate smtpd
listeners, for example.)
When using multiple instances, this applies to each instances' main.cf
and respective master.cf services.
Multiple instances do not share any configuration that's not directly
related to multi-instance management.
My advice is to read the man pages for each daemon carefully, and refer
back to them whenever you have questions such as these, since the man
page will tell you exactly what function each program performs, and
which configuration options apply to it.
--
J.
