When replacing (overwriting) an so module, Apache needs to be down
(probably platform dependent, but definitely on Linux and Windows). I
believe you can get by by doing something like, move (rename) existing
so, move in new one, graceful restart (not a "graceful" ie reload, but
"graceful-stop" fol
Following up on a very old thread (below). Brian, thanks for your very
useful instructions, and sorry for not following them sooner.
Excerpts from Brian Rectanus's message of Sat Mar 20 14:51:16 -0700 2010:
> Often if you upgrade/replace mod_security2.so on a running httpd you
> will see this (
Alberto Gonzalez Iniesta wrote:
> Hi,
>
> I got this [1] bug report about ModSecurity segfaulting. I couldn't
> reproduce it, it may be related to the arch of the reporter (x86_64).
> Please, feel free to write to the bug report (574...@bugs.debian.org) if
> you need further information.
>
> Than
3 matches
Mail list logo
