e finds it useful.
>
> best regards,
> Simon.
>
> -------- Original Message
> Subject: Re: Apache::SizeLimit snaffoo?
> Date: Fri, 11 Aug 2006 07:36:36 -0500 (CDT)
> From: Dave Rolsky <[EMAIL PROTECTED]>
> To: Simon Luff <[EMAIL PROTECTED]>
> References
Perrin Harkins wrote:
On Tuesday 24 May 2005 2:36 pm, Philip M. Gollucci wrote:
httpd -X
What would be appropriate behavior in that case? Report the size but not kill
the process?
That sounds good to me. I wasn't really following this thread. I just
saw something I could answe
On Tuesday 24 May 2005 2:36 pm, Philip M. Gollucci wrote:
> httpd -X
What would be appropriate behavior in that case? Report the size but not kill
the process?
- Perrin
Perrin Harkins wrote:
On Tuesday 24 May 2005 3:39 am, [EMAIL PROTECTED] wrote:
I claim, the "main process " detection does never work and does not make
sense.
As other have pointed out, it does work, but apparently has issues on some
platforms for some people. However, I can't see a
On Tuesday 24 May 2005 3:39 am, [EMAIL PROTECTED] wrote:
> I claim, the "main process " detection does never work and does not make
> sense.
As other have pointed out, it does work, but apparently has issues on some
platforms for some people. However, I can't see any reason why the main
process
On Tuesday 24 May 2005 11:48, Marc Gràcia wrote:
> > But there is a problem with Perls getppid() implementation. Modern Perls
> > issue the syscall only once and cache the result. Maybe you somehow hit
> > that. Normally the cache is invalidated when Perl forks, but Apache does
> > its own fork. Th
El dt 24 de 05 del 2005 a les 11:19 +0200, en/na Torsten Foertsch va escriure:
On Tuesday 24 May 2005 09:39, [EMAIL PROTECTED] wrote:
> I claim, the "main process " detection does never work and does not make
> sense. Why? Not even when the apache is started on boot through init, the
> PPID
On Tuesday 24 May 2005 09:39, [EMAIL PROTECTED] wrote:
> I claim, the "main process " detection does never work and does not make
> sense. Why? Not even when the apache is started on boot through init, the
> PPID will be 1, but some shell / rc pid. You can only find the PPID in the
> PID file that
Perrin Harkins wrote:
On Wed, 2005-05-11 at 13:20 -0400, Stas Bekman wrote:
It's not that SizeLimit and GTop no longer work, it's the recent linux
kernels that have stopped maitaining certain information about shared
memory. So the sharing happens, but there is no way to measure it.
My impressio
On Wed, 2005-05-11 at 13:20 -0400, Stas Bekman wrote:
> It's not that SizeLimit and GTop no longer work, it's the recent linux
> kernels that have stopped maitaining certain information about shared
> memory. So the sharing happens, but there is no way to measure it.
My impression was that our m
Perrin Harkins wrote:
On Wed, 2005-05-11 at 13:27 +0200, Torsten Foertsch wrote:
Is there a way on linux to get the amount of pages shared among processes by
copy on write?
No. There was a lengthy discussion about this on the list a few months
back. The methods used by SizeLimit and GTop no lon
On Wed, 2005-05-11 at 13:27 +0200, Torsten Foertsch wrote:
> Is there a way on linux to get the amount of pages shared among processes by
> copy on write?
No. There was a lengthy discussion about this on the list a few months
back. The methods used by SizeLimit and GTop no longer work, if they
Perrin Harkins wrote:
On Thu, 2003-10-16 at 11:15, Mike Norton wrote:
Yes I understand this however when I watch a particular process
using Apache::VMonitor the process carries on serving requests
even once it has exceeeded the size I have specified
What platform are you on? There may be a dif
On Thu, 2003-10-16 at 11:38, Mike Norton wrote:
> Platform is RedHat Advanced Server 2.1,
Have you modified the page size? A::SL assumes 4K page sizes on Linux.
You can change it easilly in the linux_size_check sub.
Also, A::VM is being more precise about bytes. There are really 1024 KB
in 1
>What platform are you on? There may be a difference in the size
>calculations that the two modules are using. VMonitor uses GTop to get
>sizes, while SizeLimit uses various approaches depending on platform.
>On Linux it reads the /proc filesystem.
Platform is RedHat Advanced Server 2.1,
Mike
On Thu, 2003-10-16 at 11:15, Mike Norton wrote:
> Yes I understand this however when I watch a particular process
> using Apache::VMonitor the process carries on serving requests
> even once it has exceeeded the size I have specified
What platform are you on? There may be a difference in the siz
>Processes don't exit until they finish serving a request, so they will
>be larger for the time it takes to finish. What are you looking at to
>determine size?
Yes I understand this however when I watch a particular process using Apache::VMonitor
the process carries on serving requests even onc
On Thu, 2003-10-16 at 10:55, Mike Norton wrote:
> We have just put the Apache::SizeLimit in place to try and cap the
> size of the processes however we still seem to see processes that are
> larger than the limit we set any ideas on why this would be ?
Processes don't exit until they finish servin
18 matches
Mail list logo
