Hi,
I was wondering if anyone has tried deleting/commenting out ALL of the
_default_ VirtualHost sections in httpd.conf/ssl.conf?
Does doing this cause any problems with Apache?
One of my colleagues has suggested that doing this helps secure Apache, because
then Apache wouldn't process any
Seems like the parent apache process creates the pipe to cronolog. The
children must be sending their output to the parent that will in turn
pipe it to cronolog.
The only other thing is that we're using an environment variable
expansion (macro) in the CustomLog string, as described here :
On 10/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,
I was wondering if anyone has tried deleting/commenting out ALL of the
_default_ VirtualHost sections in httpd.conf/ssl.conf?
Does doing this cause any problems with Apache?
One of my colleagues has suggested that doing this helps
It seems that cronolog does not play well with apache 2.2.3 . when you
shut down apache, none of the cronolog sessions are terminated. they
just left hanging. This didn't happen with Apache 2.0.5X.
I looked at the cronolog src code and none of it is Apache specific so
I would assume that you
Also, when we tried that (deleting the _default_ sections), I *think*
(but am not sure) that we may have been seeing some behavior where Apache
would slow down, i.e., serve content very slowly.
No. It should make no difference in speed.
Joshua,
Thanks for the response(s). Re. the
On 10/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Thanks for the response(s). Re. the comments above, my understanding of the way the
Apache works is that when it receives an incoming request, it searches through the
VirtualHosts that have been defined, for a match, and I was thinking
I think, but am not sure, that from some diagnostics we did at that time,
it also looked like Apache was processing requests for IP address
0.0.0.0, which kind of puzzled me.
By default apache listens on all available addresses. I don't know
what is puzzling you about that.
Joshua,
[EMAIL PROTECTED] wrote:
I think, but am not sure, that from some diagnostics we did at that time,
it also looked like Apache was processing requests for IP address
0.0.0.0, which kind of puzzled me.
By default apache listens on all available addresses. I don't know
what
Hi All,
we notice that some time (not consistent) some of the Apache
process hang.
They start taking memory and do nothing.
Here is the strace of one such process
strace p 5762
futex(0x9dfe690, FUTEX_WAKE,
1) = 0
gettimeofday({1161960021, 481837}, NULL) = 0
