reassign 758068 libapache2-mod-security2
thanks
On Sunday 07 September 2014 09:11:54, Stefan Fritsch wrote:
> there is now a bug report at
> https://github.com/SpiderLabs/ModSecurity/issues/768
>
> Can you please try if the patch for mod_security attached to this
> mail fixes the issue?
Re-assi
Hi,
On Friday 15 August 2014 21:33:07, Stefan Fritsch wrote:
> It seems mod_security does its own things with apr allocators, which
> causes MaxMemFree not to have any effect for mod_security's
> allocations. I have asked them why they do that. Let's see what
> they respond.
there is now a bug re
On Thursday 14 August 2014 17:02:04, Nelson Elhage wrote:
> On Thu, Aug 14, 2014 at 12:22 AM, Stefan Fritsch
wrote:
> > Can you please try if increasing MaxMemFree to a larger value
> > fixes your problem, too? 2048 (KB) is the default.
>
> Unfortunately setting that higher (we tried 100MB) does
On Thu, Aug 14, 2014 at 12:22 AM, Stefan Fritsch wrote:
> Can you please try if increasing MaxMemFree to a larger value fixes your
> problem, too? 2048 (KB) is the default.
>
Unfortunately setting that higher (we tried 100MB) doesn't seem to
noticeably improve the situation in our environment.
Hi,
On Wed, 13 Aug 2014, Nelson Elhage wrote:
> Please disable the experimental --enable-mmap-allocator option in the
> Debian libapr build.
Can you please try if increasing MaxMemFree to a larger value fixes your
problem, too? 2048 (KB) is the default.
I don't want to disable --enable-mmap-allo
Package: libapr1
Version: 1.5.0-1
Severity: normal
Dear Maintainer,
Please disable the experimental --enable-mmap-allocator option in the
Debian libapr build.
The mmap allocator forces APR to perform a huge number of tiny (1-2
page) mmap() calls.
On Linux, the process address space is protected
6 matches
Mail list logo
