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. Hmmm...maybe each time something is logged inside -forkserver it
could create a new instance too as it would then pick up logging config
changes on the fly like:
--- BEGIN UNTESTED ----
# qpsmtpd-forkerserver frag
sub log {
my ($level, @msg) = @_;
my $qp = Qpsmtpd::new();
$qp->load_plugins();
$qp->log($level, @msg);
}
----- END UNTESTED -----
Would this irk anyone?
peter
On 11/28/04 12:22 PM, "John Peacock" <[EMAIL PROTECTED]> wrote:
> Peter Eisch wrote:
>> Either way, I like having the flexibility. There is a little chicken/egg
>> issue though with the second example in that there's no place for connection
>> logging prior to the plugin getting loaded.
>
> I like this rather a lot, because it would make it very easy for me to set up
> adaptive logging (higher log level for DENY's than for OK's). I don't see a
> chicken/egg thing if you include a default logging plugin which is loaded only
> if no other logging plugin is loaded.
>
> John
>
