On Fri, 7 Jun 2002, Stas Bekman wrote:
> Should the + in:
>
> Perl<>Handler +Foo
>
> work?
it should now.
> yes, but it doesn't seem to complain if the return code is not supplied.
> tested with PerlChildInitHandler
it should, i'll look into it later.
--
Doug MacEachern wrote:
> On Thu, 6 Jun 2002, Stas Bekman wrote:
>
>
>>The problem: PerlChildInitHandler handler runs in the parent instead of
>>the child
>
>
> fixed. also fixed the OpenLogs issue with the same change.
confirmed. Thanks!
Should the + in:
Perl<>Handler +Foo
work?
>>Also
On Thu, 6 Jun 2002, Stas Bekman wrote:
> The problem: PerlChildInitHandler handler runs in the parent instead of
> the child
fixed. also fixed the OpenLogs issue with the same change.
> Also ap_hook_child_init() doesn't expect any return value, why does
> PerlChildInitHandler? 1.x's version
The problem: PerlChildInitHandler handler runs in the parent instead of
the child
Consider:
PerlModule Apache::ChildInit
PerlChildInitHandler Apache::ChildInit
package Apache::ChildInit;
use strict;
use Apache::Log;
use Apache::Const -compile => 'OK';
sub handler {
Apache->warn("warn:
