Stas Bekman wrote:
> Geoffrey Young wrote:
>
>>> It doesn't work in Child(Init|Exit) phases. Not only it doesn't exit, it
>>> doesn't even log the error. See the test in my patch. Add die in
>>> child_init() and you will see.
>>
>> ok, that's problematic - anyplace you call die() from perl-land ou
Geoffrey Young wrote:
It doesn't work in Child(Init|Exit) phases. Not only it doesn't exit, it
doesn't even log the error. See the test in my patch. Add die in
child_init() and you will see.
ok, that's problematic - anyplace you call die() from perl-land ought to
show up in the logs. the curr
> It doesn't work in Child(Init|Exit) phases. Not only it doesn't exit, it
> doesn't even log the error. See the test in my patch. Add die in
> child_init() and you will see.
ok, that's problematic - anyplace you call die() from perl-land ought to
show up in the logs. the current behavior is bad
Geoffrey Young wrote:
Stas Bekman wrote:
At the moment Child(Init|Exit) phases are of type VOID, i.e. any
failures are ignored, which sucks, since you now can't do any reliable
initialization in the child init phase (e.g. let's say Apache::DBI's
child_init phase fails).
a call to die() sho
Philippe M. Chiasson wrote:
Stas Bekman wrote:
Actually
$PerlSetVar = "foo $bar";
works. As I've later figured out thanks to Philippe's examples is that
my problem was that I was calling:
$PerlSetVar = ["foo", $bar],
which mod_perl has happily ignored or something... it didn't generat
Stas Bekman wrote:
> At the moment Child(Init|Exit) phases are of type VOID, i.e. any
> failures are ignored, which sucks, since you now can't do any reliable
> initialization in the child init phase (e.g. let's say Apache::DBI's
> child_init phase fails).
a call to die() shouldn't be ignored.
Stas Bekman wrote:
> Actually
>
>
>
> $PerlSetVar = "foo $bar";
>
>
>
> works. As I've later figured out thanks to Philippe's examples is that
> my problem was that I was calling:
>
> $PerlSetVar = ["foo", $bar],
>
> which mod_perl has happily ignored or something... it didn't generate
At the moment Child(Init|Exit) phases are of type VOID, i.e. any failures
are ignored, which sucks, since you now can't do any reliable
initialization in the child init phase (e.g. let's say Apache::DBI's
child_init phase fails). How about making it RUN_ALL instead? The
immediate gain is that e
On Wed, 2005-09-07 at 13:57 -0400, Philip M. Gollucci wrote:
> Say Perrin, do you have the perltidy options/args/config handy.
I was just referring to the default settings, which are based on
perlstyle.
- Perrin
-
To unsubscrib
Stas Bekman wrote:
Perrin Harkins wrote:
On Fri, 2005-08-26 at 12:28 -0400, Geoffrey Young wrote:
personally, I find the former painful to look at :)
I agree, and so does perltidy.
I don't really care either way, as long as things are consistent.
Say Perrin, do you have the perltidy o
Philip M. Gollucci wrote:
> Are any instructions for getting, and setting up PGP keys for code
> signing for ASF things i.e. mod_perl ?
hmm...
I think modperl-docs/src/dist/KEYS should have all the info you need. but
ping again if there's something missing.
--Geoff
--
Are any instructions for getting, and setting up PGP keys for code signing for
ASF things i.e. mod_perl ?
--
END
What doesn't kill us can only make us stronger.
Nothing is impossible.
12 matches
Mail list logo
