You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rb...@apache.org on 2001/09/13 06:37:21 UTC
cvs commit: httpd-2.0/docs/manual/misc perf-tuning.html
rbowen 01/09/12 21:37:21
Modified: docs/manual/misc perf-tuning.html
Log:
Mention of logrotate as an alternative to HostnameLookups
Revision Changes Path
1.26 +9 -0 httpd-2.0/docs/manual/misc/perf-tuning.html
Index: perf-tuning.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/misc/perf-tuning.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- perf-tuning.html 2000/12/21 22:36:01 1.25
+++ perf-tuning.html 2001/09/13 04:37:20 1.26
@@ -123,6 +123,15 @@
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