On Wed, 1 Dec 2004, Ray Chuan wrote:
> yes, the printenv.pl script works fine, and the CGI module
> works fine too, although I have to create a CGI object:
That's really strange then that you can use other modules
that don't have an xs component within ModPerl::Registry,
but those that do have su
> I've never used that under mp1, did it actually ever work?
>
Nop, it didn't work.
> I can see some experimental code which is enabled when compiled with
> -DPERL_TIE_SCRIPTNAME. but I won't have the time to look at it, until
> after modperl2 is released.
>
> Feel free to look through the code
SHAHNAWAZ OSMAN wrote:
Hi Stas,
Thank you for your speedy response. Now, when I try to
run the script
(http://www.mydoamin.com/perl/test.pl) I get a "404 -
file not found page"
and get the following message in the error log.
"/usr/local/httpd_perl/cgi-bin/test.pl not found or
unable to stat"
Hi Stas,
Thank you for your speedy response. Now, when I try to
run the script
(http://www.mydoamin.com/perl/test.pl) I get a "404 -
file not found page"
and get the following message in the error log.
"/usr/local/httpd_perl/cgi-bin/test.pl not found or
unable to stat"
I was g
Faisal Nasim wrote:
Okay here's a demonstration:
The test script is:
#!/usr/local/bin/perl
use strict;
use vars qw ($mydata);
$mydata = 'woodooeer';
my $data = 'woodoo';
my $data2 = 'dingdong';
print "Content-type: text/plain\n\n";
print scalar localtime () , "\n\n";
print `cat /tmp/modperltest.txt
Pratik wrote:
Hi !
I am using Apache/1.3.33 and Mod-Perl 1.29. I have following httpd.conf file.
ServerRoot "/home/pvnaik/lab/mp1"
Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15
DocumentRoot "/home/pvnaik/lab/mp1/htdocs"
ErrorLog logs/error_log
Port 50505
*0 = "MyApache
Malcom,
Thank you for your response.. It does sound like a possibility that the script isn't all the way into completion as we have query->process result->query->process result->query->disconnect (figuratively) scripts. We were thinking of using SQLRelay as a connection pool and concentrator
On Wednesday 1 December 2004 08:26 pm, Richard N. Fogle wrote:
> 1. We disabled Apache::DBI - the server can generate thousands of
> queries per second and this feature literally made the CPU catch fire.
Odd. Normally (in my limited experience) it has the reverse effect as you
aren't creating a
Malcom and Perrin,
Thank you for your quick replies!
1. We disabled Apache::DBI - the server can generate thousands of queries per second and this feature literally made the CPU catch fire.
2. Understood about placing the connect strings in startup.PL. That's why we wrote the list first :
On Wed, 2004-12-01 at 19:00 -0600, Richard N. Fogle wrote:
> The problem we're having is each time the CGI is called it seems to
> make a persistent connection to the database despite the fact that we
> have a $dbh->disconnect(); at the end of the code.
Are you using Apache::DBI anywhere? Make su
On Wednesday 1 December 2004 08:00 pm, Richard N. Fogle wrote:
> Basically, we have one MySQL cluster setup for reads and the other
> cluster for writes - the reads cluster alternates between master and
> slave. This works fine. The problem we're having is each time the CGI
> is called it seems
Hello,
We're having quite the time with CGIs being called in mod_perl, listed below is an example of the DBI connection code:
SNIP
use DBI
my $write_dbh = DBI->connect("DBI:mysql:writeDB:192.168.1.10","foouser","foopass") || die $DBI::errstr;
my $read_dbh;
if ( int(rand(4)) ) { $read_
Lars Eggert wrote:
Stas Bekman wrote:
Most likely cglee was running gmake, while you Lars -- make, which
makes a big diffference (but as stated in the other reply it should
have been working with make too).
I'll try that. If using gmake fixes it, that's an easy change to the
port Makefile.
I'd
> I am considering upgrading to a 64-bit Opteron-based machine running RH
> linux. Using perl 5.8, apache 2, mod_perl. Has anyone run into any
> problems running their mod_perl applications on a 64-bit box with a
> 64-bit linux OS?
I ran a mission critical web-app using Apache2/mod_perl2, and an s
Stas Bekman wrote:
Most likely cglee was running gmake, while you Lars -- make, which makes
a big diffference (but as stated in the other reply it should have been
working with make too).
I'll try that. If using gmake fixes it, that's an easy change to the
port Makefile.
In the future please al
Hi Mathew,
Some time ago I posted a message about libapreq failing on my 64bit
architecture.
http://www.gossamer-threads.com/lists/modperl/modperl/74261?search_string=x86_64;#74261
All other modules that I use seem to work fine. I was told that there
is a separate libapreq mailing list. I stil
I am considering upgrading to a 64-bit Opteron-based machine running RH
linux. Using perl 5.8, apache 2, mod_perl. Has anyone run into any
problems running their mod_perl applications on a 64-bit box with a
64-bit linux OS?
Thanks in advance,
Matthew
--
Report problems: http://perl.apache.org/b
> It might be that the FreeBSD ports build mechanism sets some environment variables or does some other things that are different from building from source.
Check your Makefile in the directory mod_perl-1.99_17/xs/APR/aprext.
$ cat ./Makefile...
dynamic ::
# End.$
you must see the 'dynamic :
++
| Perl 5.8.6 released|
| posted by rafael on Tuesday November 30, @06:42 (Releases) |
| http://use.perl.org/article.pl?sid=04/11/30/1125252 |
+--
Arshavir Grigorian wrote:
I have module called Application which handles all the requests to the
site (except for images, etc) and then dispatches the request to a
different module based on the $r->path_info().
Apache::Dispatch could do this for you if you like. You could also just
use httpd.co
pradeep kumar wrote:
Hi,
If Apache is gracefully rastarted multiplae times it dumps core. To
reproduce this problem there is a script that can be run which sends a
kill -HUP to httpd every 20 secs.
pradeep, your report is incomplete. Please read:
http://perl.apache.org/bugs/ and try again.
The s
SHAHNAWAZ OSMAN wrote:
Hi! I have been trying to configure two servers under Linux (CentOS-3.3) - one vanilla (frontend) & one mod_perl (backend) enabled server with a proxy setting in the front end. The frontend server is on port: 80 and the backend is on port 8000 and they are both in the same IP
Lars Eggert wrote:
cglee wrote:
on my FreeBSD 5.3 stabe, perl 5.8.5 from port, Apache 2.0.52 from
source, mod_perl 1.99_17 from source
...
$ make test
All tests successful
and Web service looks good with apache2&mod_perl2&Mason1.27
It might be that the FreeBSD ports build mechanism sets some env
Lars Eggert wrote:
Stas Bekman wrote:
Lars Eggert wrote:
patch-ab is required to build, otherwise I see the following error
during make:
Running Mkbootstrap for APR::PerlIO ()
chmod 644 PerlIO.bs
rm -f ../../../blib/arch/Apache2/auto/APR/PerlIO/PerlIO.so
LD_RUN_PATH="" cc -shared -L/usr/local/l
Hi,
If Apache is gracefully rastarted multiplae times it dumps core. To
reproduce this problem there is a script that can be run which sends a
kill -HUP to httpd every 20 secs. The scpirt is
#!/usr/bin/sh
COUNT=1
while true
do
kill -HUP `cat "path_to_httpd.pid/httpd.pid"`
date "+DATE: %m/%d/%y
Hi! I have been trying to configure two servers under Linux (CentOS-3.3) - one vanilla (frontend) & one mod_perl (backend) enabled server with a proxy setting in the front end. The frontend server is on port: 80 and the backend is on port 8000 and they are both in the same IP. The installation seem
cglee wrote:
on my FreeBSD 5.3 stabe, perl 5.8.5 from port, Apache 2.0.52 from source,
mod_perl 1.99_17 from source
...
$ make test
All tests successful
and Web service looks good with apache2&mod_perl2&Mason1.27
It might be that the FreeBSD ports build mechanism sets some environment
variables o
Stas Bekman wrote:
Lars Eggert wrote:
patch-ab is required to build, otherwise I see the following error
during make:
Running Mkbootstrap for APR::PerlIO ()
chmod 644 PerlIO.bs
rm -f ../../../blib/arch/Apache2/auto/APR/PerlIO/PerlIO.so
LD_RUN_PATH="" cc -shared -L/usr/local/lib PerlIO.o
modper
28 matches
Mail list logo
