Perrin Harkins wrote:
001c01c156c1$d5d0eac0$553dfea9@charlotte">
Unfortunately, I've now noticed that my server is unbearably slow -setting 'ThreadsPerChild 1' in my httpd.conf made my server slow to asnails pace (and it really is a pretty quick server on a T1 linededicated to it,
By making 'ThreadsPerChild 1' - the entire server runs as a single
thread, mod_perl and any other requests (e.g. images) that come in -
this is why the server slows to a snails pace. I've set up two
instances now, one to handle all incoming requests, the other to serve
as a backend proxy
Perrin Harkins wrote:
006101c1571b$7930a850$18020c0a@PerriHar">
By making 'ThreadsPerChild 1' - the entire server runs as a singlethread, mod_perl and any other requests (e.g. images) that come in -this is why the server slows to a snails pace. I've set up twoinstances now, one to
I have a perl script that was running fine under IIS/5.0 with
ActivePerl 6xx - I'll put the salient parts here:
use IO::Socket;
use CGI;
$in = new CGI;
$server = IO::Socket::INET-new( PeerAddr= ...,PeerPort=
...,Proto=tcp,Type= SOCK_STREAM) or die Error message ... $@;
What is the difference between doing the following:
close( $server );
#
$server-close();
#
$server-shutdown();
??
Sincerely,
Brice Ruth
Brice D Ruth wrote:
I have a perl script that was running fine under IIS/5.0 with
ActivePerl 6xx - I'll put the salient parts here:
use IO::Socket;
Brice D Ruth wrote:
What is the difference between doing the following:
close( $server );
functional interface. flush and close the file handle for this instance
of the program.
#
$server-close();
object interface - same as above.
#
$server-shutdown();
object interface. cause
Why OT? I have a script that works under IIS/5 using CGI Perl that doesn't
work under Apache with mod_perl - I'd say that's on-topic for this list!
-Brice
___cliff rayman___ wrote:
[EMAIL PROTECTED]">
Brice D Ruth wrote:
What is the difference between doing the following:close(
hi brice,
because this particular question is one of basic perl,
and not mod_perl. this just alerts all mod_perl readers
that they can safely skip this particular question/answer
and not miss any relevant mod_perl content.
u sound upset - no reason to be - u got the answer u were
looking for.
It *seems* that the script can run once, but
that the next time it is accessed, it cannot connect to the $server
anylonger, it dies with a 'connection timed out' message ... What
'gotcha' is causing this?
It sounds like this problem:
Yeah, I thought about that earlier today ... I did that and the script is
still crappin' out ... basically, the first time through, it works. The
next time, it doesn't seem to be able to build the connection, but it doesn't
'die' at that line, either.
I'll go check out the links you sent me
Perrin Harkins wrote:
00a601c1568c$224f0a20$18020c0a@PerriHar">
It *seems* that the script can run once, butthat the next time it is accessed, it cannot connect to the $serveranylonger, it dies with a 'connection timed out' message ... What'gotcha' is causing this?
It sounds
Brice D Ruth wrote:
[EMAIL PROTECTED]">
Perrin Harkins wrote:
00a601c1568c$224f0a20$18020c0a@PerriHar">
It *seems* that the script can run once, butthat the next time it is accessed, it cannot connect to the $serveranylonger, it dies with a 'connection timed out' message
Unfortunately, I've now noticed that my server is unbearably slow -
setting 'ThreadsPerChild 1' in my httpd.conf made my server slow to a
snails pace (and it really is a pretty quick server on a T1 line
dedicated to it, pretty much).
That's odd. On Win32, mod_perl runs as a single blocking
13 matches
Mail list logo
