From: Randy Kobes <[EMAIL PROTECTED]>
To: Ray Chuan <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: [error] Can't locate object method "bootstrap" via package
"DBI"
Date: Sun, 28 Nov 2004 22:02:00 -0600 (CST)
On Mon, 29 Nov 2004, Ray Chuan wrote:
> Hi, I have DBI 1.45, Apache 2.052 Win32,
Hello,
Here is the startup script modified as you recommended:
(I replaced the call to warn by Apache->server->log->debug because warn does not
log anything - at least under win32)
=
# mod_perl startup script
use Apache2 ();
use ModPerl::Util ();
use Apache::Reques
Hi, what's wrong whit this script.
I need to detect when the user press the stop button.
I read:
http://perl.apache.org/docs/1.0/guide/debug.html#Handling_the__User_pressed_Stop_button__case
SO: Debian Sarge.
This is my apache.http:
---
# If the perl module is installed, t
Federico M. wrote:
Hi, what's wrong whit this script.
I need to detect when the user press the stop button.
I read:
http://perl.apache.org/docs/1.0/guide/debug.html#Handling_the__User_pressed_Stop_button__case
SO: Debian Sarge.
This is my apache.http:
---
# If the perl module i
Tony Clayton wrote:
> Hi,
>
> I am using a 3rd party compiled apache module that implements a
> response handler, but DECLINES all the other handlers with no
> processing.
>
> I want to do authentication in mod_perl before calling the handler,
> based on some custom HTTP headers sent by the cli
Sorry, this is my source.
#!/usr/bin/perl
my $r=shift;
$r->send_http_header('text/plain');
print"PID=$$\n";
$r->rflush;
while(1)
{
$r->print("\0");
$r->rflush;
last if $r->connection->aborted;
$i++;
sleep 1;
}
ERROR: Can't call method "send_http_header" on an
undefined value at scan2.cgi line 3
Federico M. wrote:
Sorry, this is my source.
#!/usr/bin/perl
my $r=shift;
$r->send_http_header('text/plain');
[...]
ERROR: Can't call method "send_http_header" on an
undefined value at scan2.cgi line 3.
bizarre, are you sure you don't have some other config and it tries to run
it under mod_cgi ins
On Mon, 29 Nov 2004, Ray Chuan wrote:
[ ... ]
> >If you don't have another Perl, do you have problems using
> >other modules with an xs component? For example, does
> >use Digest::MD2;
> >cause problems (assuming you have Digest::MD2 installed)?
>
> here's the script i ran:
> --
> #!F:/Net/Perl
[Federico, always reply to the list! Thanks]
Federico M. wrote:
The script return:
Running under_modCGI
What's wrong ?
You should check your config file. Make sure that your modperl config is
the last in httpd.conf and that you access your script at the right path.
(e.g. try to drop any ScriptAli
Shreeguru KS wrote:
Hi,
I'm using mod_perl 2.0 with apache server 2.0.52 and perl version
5.8.0. The problem is that with mod_perl alarm() doesn't get timeout
through apache mod_perl. It works fine on the command with perl 5.8.0.
It also works with cgi.
I wrote a test and indeed it doesn't work. No
Jan, do you have any idea why the CLONE trick doesn't work? CLONE is
running inside the newly-clonned perl, so thread-safety shouldn't get on
the way, no?
Thierry Valentin wrote:
Hello,
Here is the startup script modified as you recommended:
(I replaced the call to warn by Apache->server->log->d
Geoffrey Young wrote:
what _does_ need to happen, though, is for Apache::compat to redefine
filename() so that it behaves like mp1 did. I just don't have the
tuits at
the moment.
Right, but there are issues with doing that:
1) that should probably be overridable and not loaded by default:
http://
Stas Bekman wrote:
>Jan, do you have any idea why the CLONE trick doesn't work? CLONE is
>running inside the newly-clonned perl, so thread-safety shouldn't get on
>the way, no?
>
Just a guess -- it may be the same problem with CoInitialize() that I
experienced not long ago with Win32::Shortcut.
Quoting Geoffrey Young <[EMAIL PROTECTED]>:
> using a PerlAuthenHandler in no way affects who can run in any other
> apache
> phase, such as fixups or (in your case) content generation. well,
> outside
> of the normal duties of an authen handler, anyway :)
Geoff,
Thanks for the great pointers
Stas Bekman wrote:
Shreeguru KS wrote:
Hi,
I'm using mod_perl 2.0 with apache server 2.0.52 and perl version
5.8.0. The problem is that with mod_perl alarm() doesn't get timeout
through apache mod_perl. It works fine on the command with perl 5.8.0.
It also works with cgi.
I wrote a test and indeed
Stas Bekman wrote:
I'm using mod_perl 2.0 with apache server 2.0.52 and perl version
5.8.0. The problem is that with mod_perl alarm() doesn't get timeout
through apache mod_perl. It works fine on the command with perl 5.8.0.
It also works with cgi.
The news so far: at the moment the use of signals
Apparently we're not quite there yet. See the report for details. Note
that I am including the bug report because it might have useful details, not
because this is necessarily a bug.
-8<-- Start Bug Report 8<--
1. Problem Description:
I am trying to get
On Mon, 29 Nov 2004, Stas Bekman wrote:
> Jan, do you have any idea why the CLONE trick doesn't work? CLONE is
> running inside the newly-clonned perl, so thread-safety shouldn't get
> on the way, no?
Is CLONE running inside the new *thread* ? It is not good enough to run
it in the correct Perl in
Jan Dubois wrote:
On Mon, 29 Nov 2004, Stas Bekman wrote:
Jan, do you have any idea why the CLONE trick doesn't work? CLONE is
running inside the newly-clonned perl, so thread-safety shouldn't get
on the way, no?
Is CLONE running inside the new *thread* ? It is not good enough to run
it in the cor
Stephen Jungels wrote:
Apparently we're not quite there yet. See the report for details. Note
that I am including the bug report because it might have useful details, not
because this is necessarily a bug.
-8<-- Start Bug Report 8<--
1. Problem Description:
On Mon, 29 Nov 2004, Stas Bekman wrote:
> If you just call perl_clone it runs in the new perl context, but
> inside the same thread. At least on Unix. Under ithreads.pm it
> probably starts a new thread first (but I'm not sure). Under
> modperl 2, there is no 1:1 relationship between interpreters a
On Fri, 2004-11-26 at 18:57 -0500, [EMAIL PROTECTED] wrote:
> On the other hand I understand the emotion. You may have felt threatened
> by a new embedded perl system on Apache. I hope I have allayed your fears
> since mod_perlservice doesn't threaten your work, but instead complements
> it.
After
Stas Bekman wrote:
> show us the output of:
> cd modperl-1.99_17
> grep PERLPREFIX Makefile
> grep SITEPREFIX Makefile
Ok, here it is:
snip
[EMAIL PROTECTED]:/usr/local/mod_perl-1.99_17# grep PERLPREFIX Makefile
[EMAIL PROTECTED]:/usr/local/mod_perl-1.99_17# grep SITEPREFIX Makef
23 matches
Mail list logo
