You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by Chris Pepper <pe...@mail.reppep.com> on 2001/01/20 05:54:23 UTC
[PATCH] httpd-2.0/docs/man ab.8 apxs.8 dbmmanage.1 htpasswd.1
logresolve.8
Typo fixes for httpd-2.0 man pages.
Index: ab.8
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/man/ab.8,v
retrieving revision 1.4
diff -u -d -b -r1.4 ab.8
--- ab.8 2000/03/31 09:42:54 1.4
+++ ab.8 2001/01/20 04:50:55
@@ -65,9 +65,9 @@
] [
.BI \-p " POST file"
] [
-.BI \-A " Authenticate username:password"
+.BI \-A " Authentication username:password"
] [
-.BI \-P " Proxy Authenticate username:password"
+.BI \-P " Proxy Authentication username:password"
] [
.BI \-H " Custom header"
] [
@@ -101,23 +101,23 @@
.SH DESCRIPTION
.B ab
is a tool for benchmarking your Apache HyperText Transfer Protocol (HTTP)
-server. It is designed to give you an impression on how performant is your
-current Apache installation. This especially shows you how much requests per
-time your Apache installation is capable to serve.
+server. It is designed to give you an impression of how your current
+Apache installation performs. This especially shows you how many
+requests per second your Apache installation is capable of serving.
.PP
.SH OPTIONS
.TP 12
.B \-k
-Enable the HTTP KeepAlive feature, i.e. perform multiple requests within one
-HTTP session instead. Default is no KeepAlive.
+Enable the HTTP KeepAlive feature, i.e., perform multiple requests within one
+HTTP session. Default is no KeepAlive.
.TP 12
.BI \-n " requests"
Number of requests to perform for the benchmarking session. The default is to
-just perform one single request which usually leads to not very representative
+just perform a single request which usually leads to non-representative
benchmarking results.
.TP 12
.BI \-t " timelimit"
-Seconds to max. spend for benchmarking. This implies
+Maximum number of seconds to spend for benchmarking. This implies
a
.B \-n
.B 50000
@@ -125,26 +125,26 @@
time. Per default there is no timelimit.
.TP 12
.BI \-c " concurrency"
-Number of multiple requests per time to perform.
-Default is one request per time.
+Number of multiple requests to perform at a time.
+Default is one request at a time.
.TP 12
.BI \-p " POST file"
File containing data to POST.
.TP 12
-.BI \-A " Authorization username:password"
-Supply BASIC Authentification credentials to the server. The username
-and password are separated by a single ':' and send on the wire uuencoded.
-The string is send regardless of wether the server needs it; (i.e. has
-send an 401. Authentifcation needed).
+.BI \-A " Authentication username:password"
+Supply BASIC Authentication credentials to the server. The username
+and password are separated by a single ':' and sent on the wire uuencoded.
+The string is sent regardless of whether the server needs it; (i.e., has
+sent an 401 authentication needed).
.TP 12
-.BI \-p " Proxy-Authorization username:password"
-Supply BASIC Authentification credentials to a proxy en-route. The username
-and password are separated by a single ':' and send on the wire uuencoded.
-The string is send regardless of wether the proxy needs it; (i.e. has
-send an 407 Proxy authentifcation needed).
+.BI \-p " Proxy-Authentication username:password"
+Supply BASIC Authentication credentials to a proxy en-route. The username
+and password are separated by a single ':' and sent on the wire uuencoded.
+The string is sent regardless of whether the proxy needs it; (i.e., has
+sent an 407 proxy authentication needed).
.TP 12
.BI \-C " Cookie name=value"
@@ -153,9 +153,9 @@
.TP 12
.BI \-p " Header string"
-Postfix extra headers to the request. The argument is typically in the form
-of a valid header line; containing a colon separated field value pair. (i.e.
-'Accept-Encoding: zip/zop;8bit').
+Append extra headers to the request. The argument is typically in the form
+of a valid header line, containing a colon-separated field-value pair.
+(i.e., 'Accept-Encoding: zip/zop;8bit').
.TP 12
.BI \-T " content-type"
@@ -193,13 +193,13 @@
.SH BUGS
There are various statically declared buffers of fixed length. Combined
with the lazy parsing of the command line arguments, the response headers
-from the server and other external inputs this might bite you.
+from the server and other external inputs, this might bite you.
.P
It does not implement HTTP/1.x fully; only accepts some 'expected' forms
of responses. The rather heavy use of
.BR strstr(3)
shows up top in profile,
-which might indicate a performance problem; i.e. you would measure the
+which might indicate a performance problem; i.e., you would measure the
.BR ab
performance rather than the server's.
Index: apxs.8
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/man/apxs.8,v
retrieving revision 1.4
diff -u -d -b -r1.4 apxs.8
--- apxs.8 2001/01/10 19:47:59 1.4
+++ apxs.8 2001/01/20 04:50:55
@@ -183,10 +183,10 @@
can be any C source file (.c), a object file (.o) or
even a library archive (.a). The
.B apxs
-tool automatically recognizes these extensions and automtaically used the C
+tool automatically recognizes these extensions and automatically used the C
source files for compilation while just using the object and archive files for
the linking phase. But when using such pre-compiled objects make sure they are
-compiled for position independend code (PIC) to be able to use them for a
+compiled for position independent code (PIC) to be able to use them for a
dynamically loaded shared object.
For instance with GCC you always just have to use
.BR -fpic .
@@ -394,7 +394,7 @@
.fi
is added to the configuration file if still not present.
-If you want to have this this disabled per default use the
+If you want to have this disabled per default use the
.B \-A
option, i.e.
Index: dbmmanage.1
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/man/dbmmanage.1,v
retrieving revision 1.3
diff -u -d -b -r1.3 dbmmanage.1
--- dbmmanage.1 2000/03/31 09:42:55 1.3
+++ dbmmanage.1 2001/01/20 04:50:55
@@ -122,7 +122,7 @@
.SH BUGS
.PP
One should be aware that there are a number of different DBM file
-formats in existance, and with all likelihood, libraries for more than
+formats in existence, and with all likelihood, libraries for more than
one format may exist on your system. The three primary examples are
NDBM, the GNU project's GDBM, and Berkeley DB 2. Unfortunately, all
these libraries use different file formats, and you must make sure
Index: htpasswd.1
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/man/htpasswd.1,v
retrieving revision 1.4
diff -u -d -b -r1.4 htpasswd.1
--- htpasswd.1 2000/05/25 16:45:49 1.4
+++ htpasswd.1 2001/01/20 04:50:55
@@ -169,14 +169,14 @@
.B httpd
server on Windows and TPF.
.IP \-s
-Use SHA encryption for passwords. Faciliates migration from/to Netscape
+Use SHA encryption for passwords. Facilitates migration from/to Netscape
servers using the LDAP Directory Interchange Format (ldif).
.IP \-p
Use plaintext passwords. Though
.B htpasswd
-will support creation on all platofrms, the
+will support creation on all platforms, the
.B httpd
-deamon will only accept plain text passwords on Windows and TPF.
+daemon will only accept plain text passwords on Windows and TPF.
.IP \fB\fIpasswdfile\fP
Name of the file to contain the user name and password. If \-c
is given, this file is created if it does not already exist,
Index: logresolve.8
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/man/logresolve.8,v
retrieving revision 1.3
diff -u -d -b -r1.3 logresolve.8
--- logresolve.8 2000/03/31 09:42:55 1.3
+++ logresolve.8 2001/01/20 04:50:55
@@ -51,7 +51,7 @@
.\" <http://www.apache.org/>.
.\"
.SH NAME
-logresolve \- resolve hostnames for IP-adresses in Apache logfiles
+logresolve \- resolve hostnames for IP-addresses in Apache logfiles
.SH SYNOPSIS
.B logresolve
[
@@ -65,7 +65,7 @@
.PP
.SH DESCRIPTION
.B logresolve
-is a post-processing program to resolve IP-adresses in Apache's access
+is a post-processing program to resolve IP-addresses in Apache's access
logfiles. To minimize impact on your nameserver, logresolve has its very own
internal hash-table cache. This means that each IP number will only be looked
up the first time it is found in the log file.