> >>solves the problem, so it looks like the lastest patch by Robert
> >>Hegemann caused the problem.
> > Who?
>
> He meant you, dude! ;-)
Duh ;) But I still had to check.>
> The deal is that the logging functionality is very delicate while
> starting up (you cannot log anything until you have loaded the
> logging). If we could require that hook_logging was first when in
> _register_standard_hooks, then I /think/ we could use the new-style
> hook_* functionality in the logging plugins. Unfortunately, %hooks is
> a hash and hash order is not predictable, so we have to use the old
> methods instead.
our %hooks = map { $_ => 1 } qw(
config queue data data_post quit rcpt mail ehlo helo
auth auth-plain auth-login auth-cram-md5
connect reset_transaction unrecognized_command disconnect
deny logging ok pre-connection post-connection
);
The hash is only used to check for validity of the hook name. If it
helps us, we could split out @hooks and %hooks.
-R
