From: Rich Bowen <rbowen@apache.org>
Date: Thu, 13 Sep 2001 04:37:20 +0000 (+0000)
Subject: Mention of logrotate as an alternative to HostnameLookups
X-Git-Tag: 2.0.26~265
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=366797b86a7c209e4f04c42728aad5fd8a4f7b1d;p=apache

Mention of logrotate as an alternative to HostnameLookups


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@91016 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/misc/perf-tuning.html b/docs/manual/misc/perf-tuning.html
index ce31fe5653..ce9d009a7f 100644
--- a/docs/manual/misc/perf-tuning.html
+++ b/docs/manual/misc/perf-tuning.html
@@ -123,6 +123,15 @@ But even still, if you just need DNS names
 in some CGIs you could consider doing the
 <CODE>gethostbyname</CODE> call in the specific CGIs that need it.
 
+<p>Similarly, if you need to have hostname information in your server
+logs in order to generate reports of this information, you can
+postprocess your log file with <a href="../programs/logresolve.html"
+>logresolve</a>, so that these lookups can be done without making the
+client wait. It is recommended that you do this postprocessing, and any
+other statistical analysis of the log file, somewhere other than your
+production web server machine, in order that this activity does not
+adversely affect server performance.</p>
+
 <H4>FollowSymLinks and SymLinksIfOwnerMatch</H4>
 <P>Wherever in your URL-space you do not have an
 <CODE>Options FollowSymLinks</CODE>, or you do have an