The sample code have some problem. When i telnet then
CommandServer in win32 everything is ok.
But if i close then console window(terminal) immediate,
the apache is hang. CPU use 100% resource.
I try to use
$c->aborted()OR
($@ == APR::Const::ECONNABORTED )
to check the connect but it can
On Thu, 21 Jul 2005, [big5] [EMAIL PROTECTED] wrote:
> The sample code have some problem. When i telnet then
> CommandServer in win32 everything is ok. But if i close
> then console window(terminal) immediate, the apache is
> hang. CPU use 100% resource.
>
> I try to use
> $c->aborted()
> OR
> (
Thanks!
But the problem is still exist.
- Original Message -
From: "Randy Kobes" <[EMAIL PROTECTED]>
To: "薛共和" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, July 21, 2005 12:47 PM
Subject: Re: The mod_perl protocol handler sample code have some problem!
On
LUKE wrote:
Thanks!
But the problem is still exist.
The sample code have some problem. When i telnet then
CommandServer in win32 everything is ok. But if i close
then console window(terminal) immediate, the apache is
hang. CPU use 100% resource.
I try to use
$c->aborted()
OR
($@ == APR::Co
On Thu, 21 Jul 2005, Stas Bekman wrote:
LUKE wrote:
Thanks!
But the problem is still exist.
The sample code have some problem. When i telnet then
CommandServer in win32 everything is ok. But if i close
then console window(terminal) immediate, the apache is
hang. CPU use 100% resource.
I
On Sun, 31 Jul 2005, Randy Kobes wrote:
If someone has a test linux box, could they see if things
spin out of control if one uses an xterm to telnet in, and
then closes the xterm? This probably won't happen, but it
would be good to see if it's a Win32-specific problem.
Here's a scaled-down v
On Sun, 31 Jul 2005, Randy Kobes wrote:
On Sun, 31 Jul 2005, Randy Kobes wrote:
[ ... ]
Here's a scaled-down version of the problem - I used
commands with single letters, as my Win32 console sent a \r\n after each
letter.
[ ... ]
sub handler {
my $c = shift;
$| = 1;
my $socket = $c->clie
Randy Kobes wrote:
On Sun, 31 Jul 2005, Randy Kobes wrote:
On Sun, 31 Jul 2005, Randy Kobes wrote:
[ ... ]
Here's a scaled-down version of the problem - I used
commands with single letters, as my Win32 console sent a \r\n after
each letter.
[ ... ]
sub handler {
my $c = shift;
$| = 1
On Fri, 12 Aug 2005, Stas Bekman wrote:
OK, I wrote a test case that reproduces the problem.
If you run:
perl Makefile.PL
make test
things work, but if you do:
t/TEST -start
t/TEST -run
the process starts spinning in the getline() call, as $sock->recv doesn't
fail.
[ ... ]
Here is a rewri
