On Wed, 12 Dec 2001, Perrin Harkins wrote:
what about
$r-headers_out-add(Connection = 'close');
Good idea! I'll put that into a future release.
Some bug report about Apache::SizeLimit diagnostic:
I don't know about Linux and Solaris but under
FreeBSD shared memory shows some
Geoff wrote:
what about
$r-headers_out-add(Connection = 'close');
I tried each of these changes in turn. Neither worked to
immediately exit
the child. I never saw that either of them would exit the
child at all
but I may not have kept them running long enough.
hmph... are
Some bug report about Apache::SizeLimit diagnostic:
I don't know about Linux and Solaris but under
FreeBSD shared memory shows some incredible numbers:
Okay, I'll ask the guy who wrote the *BSD support to look into it. I don't
have a FreeBSD system to test with.
And some recomendation -
Perrin Harkins wrote:
Try changing the call
$r-child_terminate() to Apache::exit(). If this seems to work better
for you, let me know and I'll consider changing this in a future release
of Apache::SizeLimit.
Geoff wrote:
what about
$r-headers_out-add(Connection = 'close');
I tried
On Thu, 13 Dec 2001, Perrin Harkins wrote:
And some recomendation - I'm using Apache::SizeLimit as
PerlCleanupHandler - so Apache would exit after request is completed.
You should use it in an early phase, like PerlFixupHandler. It pushes a
cleanup handler if it needs to exit. It will
You should use it in an early phase, like PerlFixupHandler. It pushes a
cleanup handler if it needs to exit. It will not exit until after the
request is done.
I didn't know it. I think you should document it.
But any way I think it's better to check size in cleanup.
I agree and I plan
On Thu, 13 Dec 2001, Perrin Harkins wrote:
You should use it in an early phase, like PerlFixupHandler. It pushes a
cleanup handler if it needs to exit. It will not exit until after the
request is done.
I didn't know it. I think you should document it.
But any way I think it's
Hi there,
On Thu, 13 Dec 2001, Igor Sysoev wrote:
On Thu, 13 Dec 2001, Perrin Harkins wrote:
How about sending Stas a patch for the guide with information on this? It
might be useful to other BSD'ers.
My English is too poor for it.
Send it to me then. :)
73,
Ged.
Perrin Harkins wrote:
That was it. The child exited immediately when I hit the limit with
KeepAlive Off. Now the question is: Is there a way to force an exit
even
with KeepAlive On?
As Jay already pointed out, you usually don't want KeepAlive on with
mod_perl. However, you could
what about
$r-headers_out-add(Connection = 'close');
Good idea! I'll put that into a future release.
- Perrin
Hi Jay, Perrin, and Geoff,
Thanks for your thoughts on this problem.
Jay yohimbe Thorne wrote:
For what its worth, I'd recommend KeepAlive Off for almost any mod_perl
deployment. It basically is a waste of memory and a process slot.
Especially
if you put graphics on a separate server.
My
Hi,
I'm using Apache::SizeLimit (on both Solaris and Linux) and getting the
error_log entry:
[Tue Dec 11 15:01:19 2001] (2520) Apache::SizeLimit httpd process too big,
exiting at SIZE=44964 KB SHARE=10900 KB REQUESTS=389 LIFETIME=9505
seconds
But the child process often doesn't exit right
I'm using Apache::SizeLimit (on both Solaris and Linux) and getting the
error_log entry:
[Tue Dec 11 15:01:19 2001] (2520) Apache::SizeLimit httpd process too big,
exiting at SIZE=44964 KB SHARE=10900 KB REQUESTS=389 LIFETIME=9505
seconds
But the child process often doesn't exit right
[EMAIL PROTECTED] writes:
I'm using Apache::SizeLimit (on both Solaris and Linux) and getting the
error_log entry:
[Tue Dec 11 15:01:19 2001] (2520) Apache::SizeLimit httpd process too
big,
exiting at SIZE=44964 KB SHARE=10900 KB REQUESTS=389 LIFETIME=9505
seconds
But the child process
On December 11, 2001 04:25 pm, Mod_perl Mailing List wrote:
Hi Perrin,
That was it. The child exited immediately when I hit the limit with
KeepAlive Off. Now the question is: Is there a way to force an exit even
with KeepAlive On?
Thanks!
Bob
For what its worth, I'd recommend
That was it. The child exited immediately when I hit the limit with
KeepAlive Off. Now the question is: Is there a way to force an exit
even
with KeepAlive On?
As Jay already pointed out, you usually don't want KeepAlive on with
mod_perl. However, you could try changing the call
That was it. The child exited immediately when I hit the limit with
KeepAlive Off. Now the question is: Is there a way to force an exit
even
with KeepAlive On?
As Jay already pointed out, you usually don't want KeepAlive on with
mod_perl. However, you could try changing the call
17 matches
Mail list logo
