-.TH ab 1 "February 2004"
+.TH ab 8 "February 2004"
.\" Copyright 1999-2004 The Apache Software Foundation
.\"
.\" Licensed under the Apache License, Version 2.0 (the "License");
.BI \-T " content-type"
] [
.BI \-v " verbosity"
-]
] [
.BI \-w " output HTML"
-]
] [
.BI \-g " output GNUPLOT"
-]
] [
.BI \-e " output CSV"
-]
] [
.BI \-x " <table> attributes"
-]
] [
.BI \-y " <tr> attributes"
-]
] [
.BI \-z " <td> attributes"
]
.P
Up to version 1.3d
.B ab
-has propably reported values way to low for most measurements;
+has propably reported values way too low for most measurements;
as a single timeout (which is usually in the order of seconds)
-will shift several thousands of milli-second responses by a
+will shift several thousands of millisecond responses by a
considerable factor. This was further componded by a serious
-interger overrun which would for realistic run's (i.e. those
+integer overrun which would for realistic run's (i.e. those
longer than a few minutes) produce believable but totally
bogus results. Thanks to Sander Temme for solving this riddle.
.B dbmmanage
currently has no way of determining what type of DBM file it is
looking at. If used against the wrong format,
-.dbmmanage
+.B dbmmanage
will simply return nothing, or may create a different DBM file with a
different name, or at worst, it may corrupt the DBM file if you were
attempting to write to it.
.fi
TransferLog "| rotatelogs /path/to/logs/access_log 86400"
-.mf
+.nf
This creates the files /path/to/logs/access_log.nnnn where nnnn is the system
time at which the log nominally starts (this time will always be a multiple of