On 10/09/2014 08:25 PM, Ronald F. Guilmette wrote: > In any event, regardless of how this key sentence is construed, it > self-evidently leaves open a rather obvious quetion: What happens, > exactly, when the $max_use limit is exceeded? The document makes > no effort at all to specify, leaving the reader to wonder why this > limit was even mentioned at all.
It is mentioned at that point only to make the reader understand that a policy daemon will usually perform well, even if written in a "slow" language with a relevant startup overhead. When there are say 10 incoming mails per second you do NOT spawn 10 ruby-processes per second, which would be a noticeable load, but reuse one process until $max_use is reached. > I now ask the analogous question: What happens after $max_use ? > > It seems a reasonable question. The document does not provide an > answer. The process is terminated, a new process will then be spawned on the next connection. This is nothing particular to the policy delegation, just the way the Postfix spawn(8) daemon works. And the suggested configuration is to have your policy service run under the control of spawn(8). Best regards, Lothar -- Lothar Gesslein Linux Consultant Mail: gessl...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
signature.asc
Description: OpenPGP digital signature
