atic approach. Of course, the recommendation came from the gentle
> folks on this list originally.
>
> Eric
>
> From: Heiko Weber [mailto:he...@wecos.de]
> Sent: Thursday, February 18, 2010 3:22 AM
> To: Salvador Ortiz Garcia
> Cc: mod_perl list
> Subject: Re: [mp2] mod_perl c
: Re: [mp2] mod_perl closes apache's stdin and/or stdout
Salvador,
to avoid such issues my "external" tasks don't use STDOUT, STDIN or STDERR.
They take their parameters from control files and write their results back to a
status file. This tasks don't send any output back t
Salvador,
to avoid such issues my "external" tasks don't use STDOUT, STDIN or STDERR.
They take their parameters from control files and write their results back to a
status file. This tasks don't send any output back to the browsers. As I said,
usually some "sudo's to change some system setting
On 02/05/2010 12:16 PM, Heiko Weber wrote:
Hi André,
I know what you mean, and I can't agree with you - the server response time is really low
- most pages are finished loading in less 1-2 seconds, and the overall load of the server
is at a low level. I believe there is an issue, maybe somethi
Hi André,
I know what you mean, and I can't agree with you - the server response time is
really low - most pages are finished loading in less 1-2 seconds, and the
overall load of the server is at a low level. I believe there is an issue,
maybe something what Jon is talking about, I also using s
Heiko Weber wrote:
Dear List-Members,
with interest I found the below thread. Starting in Oct. or Nov. last year I am
getting a lot of messages in apaches error_log like:
[Fri Feb 5 11:07:09 2010] -e: Software caused connection abort at ...
And it always happen in a print to STDOUT. I notic
Dear List-Members,
with interest I found the below thread. Starting in Oct. or Nov. last year I am
getting a lot of messages in apaches error_log like:
[Fri Feb 5 11:07:09 2010] -e: Software caused connection abort at ...
And it always happen in a print to STDOUT. I notice that it also happen
On Tue, Jan 26, 2010 at 5:20 PM, Jonathan Swartz wrote:
> This never got a response. Which surprises me, since I think it is a
> legitimate and nasty bug.
>
> So is the silence because
> 1) people don't think it's really a bug
> 2) people glazed over while reading the description
> 3) ??
4) Don't
This never got a response. Which surprises me, since I think it is a
legitimate and nasty bug.
So is the silence because
1) people don't think it's really a bug
2) people glazed over while reading the description
3) ??
Thanks :)
Jon
On Jan 8, 2010, at 6:15 AM, Jonathan Swartz wrote:
(A cont
Fred Moyer wrote:
> Peter Valdemar Mørch wrote:
>> Hi,
>>
>> Dmitry Karasik dmitry-at-karasik.eu.org wrote:
>>> mod_perl during the initialization process closes file descriptor 0,
>>> and frees it for further reuse in other processes. Therefore, any cgi
>>> script
>>> executing after mod_perl is
Peter Valdemar Mørch wrote:
Hi,
Dmitry Karasik dmitry-at-karasik.eu.org wrote:
mod_perl during the initialization process closes file descriptor 0,
and frees it for further reuse in other processes. Therefore, any cgi
script
executing after mod_perl is initialized, and in the same process tre
Hi,
Dmitry Karasik dmitry-at-karasik.eu.org wrote:
mod_perl during the initialization process closes file descriptor 0,
and frees it for further reuse in other processes. Therefore, any cgi script
executing after mod_perl is initialized, and in the same process tree, will
have file descriptor 0
Dmitry Karasik wrote:
>> What did I wrong?
Not running a perlio Perl ?
> Try the same input but with apache freshly started, it must be the very first
> apache request, then the error is fully reproducible.
Philippe M. Chia
> What did I wrong?
Try the same input but with apache freshly started, it must be the very first
apache request, then the error is fully reproducible.
--
Sincerely,
Dmitry Karasik
> I took a quick swing at putting one together but my mod_perl environment
> is a bit screwed up right now. Can you see if it runs on your setup?
I don't know. I've run "perl ModPerl-Registry/t/cgi-bin/stdin.pl" and it
(unsurprisingly) fails with a "Can't connect to localhost:8529", and
I can'
On Tuesday 25 September 2007 19:52, Fred Moyer wrote:
> I took a quick swing at putting one together but my mod_perl environment
> is a bit screwed up right now. Can you see if it runs on your setup?
With a few tweaks the test runs in my environment (trunk+2.2.6-worker). But it
succeeds in both
Dmitry Karasik wrote:
Hello,
In mixed environment of mod_perl and cgi, cgi scripts may choose to not use
mod_perl request interface, and read content of POST requests directly from
STDIN. mod_perl during the initialization process closes file descriptor 0,
and frees it for further reuse in othe
17 matches
Mail list logo
