that somebody else who's on Solaris could step in
and help.
I do hope that someone can explain to me why mod_cgi and mod_perl don't
work well together. It worked just fine using apache 1.3.14 and mod_perl
1.X (another version I can't remember). But with apache 1.3.27 and
mod_perl 1.27, it didn't.
Sending you a piece of my httpd.conf file:
LoadModule perl_module /local/lib/apache/libperl.so
AddHandlercgi-script.cgi
IfModule mod_perl.c
Location /tools/admin/perl-status
SetHandlerperl-script
PerlHandlerApache::Status
PerlSetVar
Magnar Stav Johanssen wrote:
Sending you a piece of my httpd.conf file:
[...]
looks fine to me.
Have you tried looking in the archives? I have found:
http://marc.theaimsgroup.com/?l=apache-modperlw=2r=1s=libthread+panicq=b
Well, I've used google.com alot, but maybe I didn't push the magic
@(none) @genuity.no wrote:
Thanks!
I've actually made some kind of progress on this case... I've found a
workaround... I don't fully like it, so if anyone got a sugestion for
aprovement, please tell me!
This was the problem area in my old httpd.conf:
(...)
AddHandler cgi-script .cgi
Hi!
On my Solaris 5.8 machine I'm running apache 1.3.27 with mod_cgi and mod_perl
1.0. mod_cgi is compiled into apache and mod_perl are loaded in my httpd.conf.
When I'm requesting for any .cgi script (tested with: #!/usr/bin/perl or
#!/bin/sh) everything works fine, and the scripts compile
Magnar Stav Johanssen wrote:
Hi!
On my Solaris 5.8 machine I'm running apache 1.3.27 with mod_cgi and
mod_perl 1.0. mod_cgi is compiled into apache and mod_perl are loaded in
my httpd.conf.
When I'm requesting for any .cgi script (tested with: #!/usr/bin/perl or
#!/bin/sh) everything works
That was it. I redefined Sig{__WARN__} to drop all STDERR output and my
script output everything it was supposed to and exited cleanly. Now
there is another bug that undoubtedly came from my trying to track down
the original issue...
Thanks. That saved me a ton of time.
Tom
Terra Info wrote:
as well) and it runs fine. I run it as a typical CGI and it
has problems that, in *some* ways, mirror the behavior of a poorly
written (symptoms associated with unscoped globals, etc;) perl app under
mod_perl. And since this is a poorly written app I am curious. Is there
any link between mod_perl
that, in *some* ways, mirror the behavior of a poorly
written (symptoms associated with unscoped globals, etc;) perl app under
mod_perl. And since this is a poorly written app I am curious. Is there
any link between mod_perl (1.99..) and mod_cgi (Apache 2)? Does mod_perl
in anyway influence or maybe
curious. Is there any link between mod_perl (1.99..)
and mod_cgi (Apache 2)? Does mod_perl in anyway influence or maybe
cause PerlRun like caching under mod_cgi? I am just trying to
eliminate all possibilities as this one has been a real PITFA.
You can turn the debugging on and see whether it gets
registry
aren't chdir()'ing to the scripts directory. That may change in the
future. But this may be unrelated to your problem.
So, is there any link between mod_perl (1.99..) and mod_cgi (Apache 2)?
No.
Does mod_perl in anyway influence or maybe cause PerlRun like caching
under mod_cgi
Stas Bekman wrote:
I still don't understand you. When do you see the problem? When you
run the script under mod_cgi or mod_perl? I don't understand why do
you keep referring to mod_cgi.
And we are talking about Apache/mod_perl 2.0 here, right?
No. I am talking about mod_cgi when I say mod_cgi
OK, now it's clear, thanks for the explanation. FWIW, there were
discussions of possible pipes read/write deadlocks in the current
mod_cgi implementation in Apache 2.0, so you may experience just that.
Check the httpd-dev list archives.
[...]
* Given that, I noticed PerlRun was no longer
Ugh! I checked the users list archives but I never checked the dev
archives. I liked p5p back in the day because it was all one in the
same. Chaos, but oddly efficient. Thanks for the pointer.
As for the docs, I freely admit I missed it. I was not looking for
PerlRun stuff when I went through
Konstantin Yotov wrote:
MaxClients 150
MaxRequestsPerChild 0
You're probably running out of memory and going into swap, which will
give terrible performance. MaxClients 150 is really high, and you
should only set MaxRequestsPerChild to 0 if you're using
Apache::SizeLimit or
Hello!
Here some details of my httpd.conf
PerlTaintcheck On
Alias /perl/ /home/httpd/perl/
PerlModule Apache::Registry
Location /perl
SetHandler perl-script
PerlHandler Apache::Registry
Options ExecCGI
allow from all
PerlSendHeader On
/Location
Konstantin Yotov wrote:
On my
development machine everything was ok, but when I move
to productional server the mod_perl version works
twice slower than mod_cgi.
Start by making sure you really have mod_perl installed and your scripts
are running under it, and not mod_cgi. You can verify
At 17:38 15.05.2002, Konstantin Yotov wrote:
Hello! :)
I'm webmaster for a small site about /3000 hits and
4 host daily/. I rewrote my cgi scripts for
mod_perl/made all global variables local and etc/
following the instructions of mod_perl guide. On my
development machine everything was ok,
Hello! :)
I'm webmaster for a small site about /3000 hits and
4 host daily/. I rewrote my cgi scripts for
mod_perl/made all global variables local and etc/
following the instructions of mod_perl guide. On my
development machine everything was ok, but when I move
to productional server the
19 matches
Mail list logo
