apache::status on win32

2002-08-31 Thread [EMAIL PROTECTED]
Hi with winXP Embedded Perl version v5.6.1 for Apache/1.3.26 (Win32) mod_perl/1.27_01-dev Apache Status is not working as expected the httpd.conf configuration is Perl Module Apache::Status (before any other module) PerlModule B::TerseSize location /perl-status SetHandler perl-script

Re: Filehandles

2002-08-31 Thread Joe Schaefer
Stas Bekman [EMAIL PROTECTED] writes: [...] perl 5.8.0 internals are thread-safe, so does mod_perl 2.0-dev. By saying that perl is thread-safe, I mean that operations like push, =, /, map, chimp, etc. are thread-safe. ^ A thread-safe chimp; amazing! Try doing *that* in

problems installing libapreq-1.0

2002-08-31 Thread Michael Robinton
I have two identical hosts with the following mod_perl-1.26 apache apache_1.3.26 ben apachessl_1.48 openssll-0.9.6b on one, libapreq-1.0 installs just fine, on the other I get this error: In file included from /usr/lib/perl5/site_perl/i386-linux/auto/Apache/include/include/httpd.h:79,

Re: problems installing libapreq-1.0

2002-08-31 Thread Michael Robinton
never mind. It appears that the order in which things are done is important. I finally got it to work by reinstalling mod-perl for the umpteenth time and then again trying libapreq. Strange, the old version that was installed would no re-install until I did this. I have two identical hosts

Apache::PerlRun weird behavior?

2002-08-31 Thread valerian
Hi I'm new at mod_perl, and I decided to start running my scripts with Apache::PerlRun so I don't have to rewrite them right away (they're too 'dirty' to run under Apache::Registry). Anyway, I figured it was going to be easy since PerlRun provides an environment similar to CGI, but something

$r-push_handlers('PerlAuthenHandler', 'Some::handler') doesn't work

2002-08-31 Thread Rodney Broom
Hi all, I'm sure I'm just missing something, but I'm stumped. I've got an access handler that does some tests and then conditionaly does this: $r-push_handlers('PerlAuthenHandler', 'Some::handler'); return OK; Some::handler() starts by printing the current callback to the error log, which

Re: $r-push_handlers('PerlAuthenHandler', 'Some::handler') doesn't work

2002-08-31 Thread Ryan Parr
If you have an access handler return OK, then the access handling stops. Because that handler handled it. So as far as I know: $r-push_handlers('PerlAuthenHandler', 'Some::handler'); return DECLINED; should work... -- Ryan - Original Message - From: Rodney Broom [EMAIL PROTECTED]

Re: $r-push_handlers('PerlAuthenHandler', 'Some::handler') doesn't work

2002-08-31 Thread Rodney Broom
From: Ryan Parr [EMAIL PROTECTED] If you have an access handler return OK, then the access handling stops. Because that handler handled it. So as far as I know: $r-push_handlers('PerlAuthenHandler', 'Some::handler'); return DECLINED; should work... Yeah, I tried that. I've also

Re: $r-push_handlers('PerlAuthenHandler', 'Some::handler') doesn'twork

2002-08-31 Thread Stas Bekman
Rodney Broom wrote: From: Ryan Parr [EMAIL PROTECTED] If you have an access handler return OK, then the access handling stops. Because that handler handled it. So as far as I know: $r-push_handlers('PerlAuthenHandler', 'Some::handler'); return DECLINED; should work... Yeah, I

Re: Apache::PerlRun weird behavior?

2002-08-31 Thread Stas Bekman
valerian wrote: Hi I'm new at mod_perl, and I decided to start running my scripts with Apache::PerlRun so I don't have to rewrite them right away (they're too 'dirty' to run under Apache::Registry). Anyway, I figured it was going to be easy since PerlRun provides an environment similar to