Re: [mod-security-users] When will we see 1.8?

[Mark <ad...@as...>]

Ivan Ristic wrote:

>>>>>  BTW, I've also added a check to v1.8. If chroot fails for any
>>>>>  reasons, Apache will refuse to serve requests.
>>>>
>>>> I have a request, though. Can you make it so, that, instead of not
>>>> serving requests, Apache will exit? (with a log message, of
>>>> course).
>>>
>>>  Actually, that's what it does at the moment. But there is a catch.
>>>  Since at that time the configuration phase is over, it is only
>>>  one child that exits. I cannot affect other Apache processes.
>>
>> I hadn't thought of that. No big deal, though: "MinSpareServers"
>> should take care of respawning a new child.
>
>    Sure, but mod_security will kill every child Apache spawns. I've
>    added a delay to prevent too many processes to get created and
>    killed at the same time, but the whole thing will prevent Apache
>    from serving any requests.

Hmm, in that case, why can mod_security not simply kill the "mother" Apache
process itself? (the child, running as "nobody", or "www", can obviously not
kill the parent, who runs as root; but mod_security could kill its own
Apache process, right?). Or am I missing something again?

- Mark

        System Administrator Asarian-host.org

---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx