httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: httpd-docs-1.3/htdocs/manual/misc perf-tuning.html
Date Thu, 13 Sep 2001 04:37:41 GMT
rbowen      01/09/12 21:37:41

  Modified:    htdocs/manual/misc perf-tuning.html
  Mention of logrotate as an alternative to HostnameLookups
  Revision  Changes    Path
  1.26      +9 -0      httpd-docs-1.3/htdocs/manual/misc/perf-tuning.html
  Index: perf-tuning.html
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/misc/perf-tuning.html,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- perf-tuning.html	2001/09/04 18:16:26	1.25
  +++ perf-tuning.html	2001/09/13 04:37:41	1.26
  @@ -115,6 +115,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

View raw message