Ahhh, so it does.   But...

With a little juggling in -forkserver, it would even work.  Perhaps delaying
that the listener is active until the set[ug]id calls.  So, now that I have
that working, I guess it's time to write it again.  <grin>

peter


On 11/28/04 3:41 PM, "Matt Sergeant" <[EMAIL PROTECTED]> wrote:

> On 28 Nov 2004, at 20:46, Peter Eisch wrote:
> 
>> If you run with qpsmtpd-forkerver there are no native logging
>> entry-points
>> if the logging set up happens inside a transaction.  I guess
>> -forkserver
>> could create an instance of Qpsmtpd, ->load_plugins() and use it for
>> logging.
> 
> Forkserver already does that for config access, so it's the right thing
> to do.
> 
> 

Reply via email to