[EMAIL PROTECTED] wrote:
> You can't break graceful restarts with this change. The problem is that
> adding mod_status using a graceful restart is actually a common occurance.
> People do that because they are having problems with the server, and they
> want to monitor it, but they don't want to kick people off the server.
>
> Until the shared memory problem is solved, I am -1 for this change.
I hadn't thought about the debugging aspects of turning mod_status on via a
restart. Disallowing mod_status on restarts was one of two documented
possibilities (the one that would allow the memory to be saved). The other
possibility is to continue to always allocate the memory so that mod_status
can come and go. I assume that your veto is on the first option and not
the second since the second is the way the code works now.
Saving the unused mod_status memory was one side benefit of this design,
not a required mainstay. If we can't reap this benefit now, I would hope
that we can fix things eventually so that we can. It is not required now,
it just happens to be a possible side benefit.
Can you please clarify what you are vetoing so that I have an opportunity
to encourage your support.
--
Paul J. Reder
-----------------------------------------------------------
"The strength of the Constitution lies entirely in the determination of each
citizen to defend it. Only if every single citizen feels duty bound to do
his share in this defense are the constitutional rights secure."
-- Albert Einstein
