flood STATUS: -*-text-*-
Last modified at [$Date: 2002/07/23 18:45:14 $]
Release:
1.0: Released July 23, 2002
milestone-03: Tagged January 16, 2002
ASF-transfer: Released July 17, 2001
milestone-02: Tagged August 13,
httpd-test/perl-framework STATUS: -*-text-*-
Last modified at [$Date: 2002/03/09 05:22:48 $]
Stuff to do:
* finish the t/TEST exit code issue (ORed with 0x2C if
framework failed)
* change existing tests that frob the DocumentRoot (e.g.,
Hi.
Sorry if this is covered somewhere else which I failed to find. But..., is it
normal that the first instance of apache2 is running as root?
root 2355 1.2 1.3 5832 3448 ?S16:35 0:00 httpd2
apache2363 0.0 1.4 5968 3608 ?S16:35 0:00 httpd2
apache
Justin Erenkrantz wrote:
On Wed, Jul 24, 2002 at 04:58:55PM -0400, Greg Ames wrote:
If I'm reading the Makefile correctly, current HEAD no longer updates the
manual/ directory if it exists, unlike 1.3. What good is a downlevel manual?
Yeah, that looks bogus. I'd move the copying of
Sorry if this is covered somewhere else which I failed to find. But..., is it
normal that the first instance of apache2 is running as root?
Yes because if it wasn't it would be unable to bind to port 80. (on usual
Unix system; there's patches for some systems out there where you dont have
to
Hi Oden,
yes it is normal that the initial proces
of the apache is running as root because
only the root user is able to switch
to another user or bind the apache to a
special port etc.
Bye,
Werner.
On Thursday 25 July 2002 16.50, johannes m. richter wrote:
Sorry if this is covered somewhere else which I failed to find. But..., is
it normal that the first instance of apache2 is running as root?
Yes because if it wasn't it would be unable to bind to port 80. (on usual
Unix system;
On Thursday 18 July 2002 19.54, Oden Eriksson wrote:
Hi.
Since stuff like CacheRoot moved from mod_proxy into mod_disk_cache, that
should be reflected in the documentation.
Thanks.
Since there where no responce on this, I have to repeat it...
--
Regards // Oden Eriksson
Deserve-IT
Since stuff like CacheRoot moved from mod_proxy into mod_disk_cache, that
should be reflected in the documentation.
Since there where no responce on this, I have to repeat it...
hm.. try filing a bug report (http://nagoya.apache.org/bugzilla/) or
subscribe to the documentation mailing
On Thursday 25 July 2002 17.06, johannes m. richter wrote:
Since stuff like CacheRoot moved from mod_proxy into mod_disk_cache,
that should be reflected in the documentation.
Since there where no responce on this, I have to repeat it...
hm.. try filing a bug report
I would be in favor of never installing them on an upgrade. They
are
useless on a production machine that already has a configuration.
They
are meant as DEFAULT values to help people get up and running.
And they also provide examples of how things are done. When those
things change on
On Wed, 2002-07-24 at 12:34, Jeff Trawick wrote:
Larry Rosenman [EMAIL PROTECTED] writes:
10156
I will plan to commit your patch in the next 24 hours. e-mail me
directly if this doesn't happen.
Just checked the commit logs, and you did this, thanks. Can you close
the bug out?
Ryan Bloom wrote:
You are working around a problem in your script in the Apache
upgrade step.
no sir. It would have been a piece of cake to change my perl script
to
insure
that conf/ has enough stuff so the server can start. But I couldn't
take
the
easy way out with a
On Thu, 25 Jul 2002, Oden Eriksson wrote:
On Thursday 18 July 2002 19.54, Oden Eriksson wrote:
Hi.
Since stuff like CacheRoot moved from mod_proxy into mod_disk_cache, that
should be reflected in the documentation.
Thanks.
Since there where no responce on this, I have to repeat
On Wed, 24 Jul 2002, Rodent of Unusual Size wrote:
Joshua Slive wrote:
LogVariable %s 40[0-9] exclude
Fine and cool -- except that this is mod_log_config specific, and it
would be nice to have something that was module-neutral. Or are the
logging format effectors dissociated from
We need to make sure that we're not using bigger values that what we're using
internally anyway. After all, if when all is said and done, we only
honor long in ranges, then supporting long longs sporadically
doesn't make full sense. But I'm +1 on looking into this.!
--
Hi,
It would be nice to be able to specify as ErrorLog TransferLog argument
/dev/stdout on apache 1.3.x
I tried this but it can't get it to work.
Or is this already possible with apache 2.0.x ?
I wanted this because I want apache to log to 1 multilog process
Robert Simonson wrote:
We've been testing with 2.0.39, and we've run into a strange problem when
negotiating for a directory index page. There is no response to the
request - no file, no headers, nothing. The connection is simply closed.
From what we have been able to determine, we
18 matches
Mail list logo
