It is currently necessary to load/protect mod_status so that some other
module can use the extended status information in the scoreboard.
mod_status is by far the most common use of the extended status.
The comment in mod_status explains the reason why it is a mod_status
directive:
/*
*
On Thu, Jan 15, 2009 at 9:31 AM, traw...@gmail.com wrote:
These are in the 1.3.x branch but not trunk. From the number of hits on the
web I'd guess that some folks have made tweaks to them but there's no
obvious place to maintain those tweaks. (I've received a patch or two via
e-mail before.)
how long will version 2.0 be available for use? Always? or until a certain
date generally speaking?
--
View this message in context:
http://www.nabble.com/Longevity-of-versions-tp21479665p21479665.html
Sent from the Apache HTTP Server - Dev mailing list archive at Nabble.com.
traw...@gmail.com wrote:
Specific proposal: Take what is in 1.3 branch and port to trunk. This
should be very close to
http://people.apache.org/~trawick/mod_backtrace.c and
http://people.apache.org/~trawick/mod_whatkilledus.c
+1 in principle
How do you propose to deal with configuration?
Thomas Steinbach wrote:
Hello,
I have a small win32 program which starts
and stops apache (win) as a program (not service)
in a hidden console.
Well, httpd should work fine, but...
void StartApache()
{
g_sia.dwFlags = STARTF_USESHOWWINDOW;
g_sia.wShowWindow = SW_HIDE;
... does not
rts wrote:
how long will version 2.0 be available for use? Always? or until a certain
date generally speaking?
Forever. It's open source, if it's broke, you get to keep both pieces
(and fix them if you like). If you see http://archives.apache.org/
the foundation generally makes source code
On Jan 15, 2009 11:16am, Nick Kew n...@webthing.com wrote:
How do you propose to deal with configuration? Specifically,
the interaction with enable-exception-hook, which means that
a server built without it breaks the expectation that new
modules can be added using apxs?
I may
William A. Rowe, Jr. wrote:
rts wrote:
how long will version 2.0 be available for use? Always? or until a certain
date generally speaking?
Forever. It's open source, if it's broke, you get to keep both pieces
(and fix them if you like). If you see http://archives.apache.org/
the foundation
traw...@gmail.com wrote:
On Jan 15, 2009 11:16am, Nick Kew n...@webthing.com wrote:
How do you propose to deal with configuration? Specifically,
the interaction with enable-exception-hook, which means that
a server built without it breaks the expectation that new
modules can be
-Ursprüngliche Nachricht-
Von: Nick Kew
Gesendet: Donnerstag, 15. Januar 2009 18:27
An: dev@httpd.apache.org
Betreff: Re: mod_backtrace and mod_whatkilledus to trunk?
traw...@gmail.com wrote:
On Jan 15, 2009 11:16am, Nick Kew n...@webthing.com wrote:
How do you propose
Thank you for answering the question that I should have asked.
Paul Querna wrote:
William A. Rowe, Jr. wrote:
rts wrote:
how long will version 2.0 be available for use? Always? or until a
certain
date generally speaking?
Forever. It's open source, if it's broke, you get to keep both
On Thu, Jan 15, 2009 at 12:40 PM, Plüm, Rüdiger, VF-Group
ruediger.pl...@vodafone.com wrote:
-Ursprüngliche Nachricht-
Von: Nick Kew
Gesendet: Donnerstag, 15. Januar 2009 18:27
An: dev@httpd.apache.org
Betreff: Re: mod_backtrace and mod_whatkilledus to trunk?
On 01/15/2009 07:39 PM, Jeff Trawick wrote:
On Thu, Jan 15, 2009 at 12:40 PM, Plüm, Rüdiger, VF-Group
ruediger.pl...@vodafone.com wrote:
Another option would be to add this hook by default and prevent its
execution by a directive (haven't dug into this to check if this is
possible).
Paul Querna wrote:
However, I expect if there was a critical security vulnerability, we
would at least provide patches, and/or do a release -- lots of peoples
jobs are still tied to 2.0.x :-)
Right - the question is more between bug fixes (possibly disruptive to the
user and certainly
httpd has a feature called reliable piped logs. When a log process like
rotatelogs dies, httpd automatically restarts it. This can be used to
close open log files from outside httpd by simply killing rotatelogs.
This procedure does not work for the error logs, because those are
started with a
15 matches
Mail list logo
