You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by jo...@apache.org on 2003/12/02 12:53:50 UTC
cvs commit: httpd-2.0/docs/man ab.8 dbmmanage.1 httpd.8 rotatelogs.8 suexec.8
jorton 2003/12/02 03:53:50
Modified: docs/man ab.8 dbmmanage.1 httpd.8 rotatelogs.8 suexec.8
Log:
Regenerate man pages.
Revision Changes Path
1.13 +2 -2 httpd-2.0/docs/man/ab.8
Index: ab.8
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/man/ab.8,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -u -r1.12 -r1.13
--- ab.8 25 Nov 2003 13:37:31 -0000 1.12
+++ ab.8 2 Dec 2003 11:53:50 -0000 1.13
@@ -19,7 +19,7 @@
.el .ne 3
.IP "\\$1" \\$2
..
-.TH "AB" 8 "2003-11-25" "Apache HTTP Server" "ab"
+.TH "AB" 8 "2003-12-02" "Apache HTTP Server" "ab"
.SH NAME
ab \- Apache HTTP server benchmarking tool
@@ -53,7 +53,7 @@
Do not display the "percentage served within XX [ms] table"\&. (legacy support)\&.
.TP
-e \fIcsv-file\fR
-Write a Comma separated value (CSV) file which contains for each percentage (from 1% to 100%) the time (in milli seconds) it took to serve that percentage of the requests\&. This is usually more useful than the 'gnuplot' file; as the results are already 'binned'\&.
+Write a Comma separated value (CSV) file which contains for each percentage (from 1% to 100%) the time (in milliseconds) it took to serve that percentage of the requests\&. This is usually more useful than the 'gnuplot' file; as the results are already 'binned'\&.
.TP
-g \fIgnuplot-file\fR
Write all measured values out as a 'gnuplot' or TSV (Tab separate values) file\&. This file can easily be imported into packages like Gnuplot, IDL, Mathematica, Igor or even Excell\&. The labels are on the first line of the file\&.
1.12 +2 -2 httpd-2.0/docs/man/dbmmanage.1
Index: dbmmanage.1
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/man/dbmmanage.1,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -u -r1.11 -r1.12
--- dbmmanage.1 25 Nov 2003 13:37:31 -0000 1.11
+++ dbmmanage.1 2 Dec 2003 11:53:50 -0000 1.12
@@ -19,7 +19,7 @@
.el .ne 3
.IP "\\$1" \\$2
..
-.TH "DBMMANAGE" 1 "2003-11-25" "Apache HTTP Server" "dbmmanage"
+.TH "DBMMANAGE" 1 "2003-12-02" "Apache HTTP Server" "dbmmanage"
.SH NAME
dbmmanage \- Manage user authentication files in DBM format
@@ -111,7 +111,7 @@
One should be aware that there are a number of different DBM file formats in existence, and with all likelihood, libraries for more than one format may exist on your system\&. The three primary examples are SDBM, NDBM, the GNU project's GDBM, and Berkeley DB 2\&. Unfortunately, all these libraries use different file formats, and you must make sure that the file format used by \fIfilename\fR is the same format that dbmmanage expects to see\&. dbmmanage currently has no way of determining what type of DBM file it is looking at\&. If used against the wrong format, 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\&.
.PP
-dbmmanage has a list of DBM format preferences, defined by the @AnyDBM::ISA array near the beginning of the program\&. Since we prefer the Berkeley DB 2 file format, the order in which dbmmanage will look for system libraries is Berkeley DB 2, then NDBM, then GDBM and then SDBM\&. The first library found will be the library dbmmanage will attempt to use for all DBM file transactions\&. This ordering is slightly different than the standard @AnyDBM::ISA ordering in perl, as well as the ordering used by the simple dbmopen() call in Perl, so if you use any other utilities to manage your DBM files, they must also follow this preference ordering\&. Similar care must be taken if using programs in other languages, like C, to access these files\&.
+dbmmanage has a list of DBM format preferences, defined by the @AnyDBM::ISA array near the beginning of the program\&. Since we prefer the Berkeley DB 2 file format, the order in which dbmmanage will look for system libraries is Berkeley DB 2, then NDBM, then GDBM and then SDBM\&. The first library found will be the library dbmmanage will attempt to use for all DBM file transactions\&. This ordering is slightly different than the standard @AnyDBM::ISA ordering in Perl, as well as the ordering used by the simple dbmopen() call in Perl, so if you use any other utilities to manage your DBM files, they must also follow this preference ordering\&. Similar care must be taken if using programs in other languages, like C, to access these files\&.
.PP
One can usually use the file program supplied with most Unix systems to see what format a DBM file is in\&.
1.14 +2 -2 httpd-2.0/docs/man/httpd.8
Index: httpd.8
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/man/httpd.8,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -u -r1.13 -r1.14
--- httpd.8 25 Nov 2003 13:37:31 -0000 1.13
+++ httpd.8 2 Dec 2003 11:53:50 -0000 1.14
@@ -19,7 +19,7 @@
.el .ne 3
.IP "\\$1" \\$2
..
-.TH "HTTPD" 8 "2003-11-25" "Apache HTTP Server" "httpd"
+.TH "HTTPD" 8 "2003-12-02" "Apache HTTP Server" "httpd"
.SH NAME
httpd \- Apache Hypertext Transfer Protocol Server
@@ -89,7 +89,7 @@
Show the settings as parsed from the config file (currently only shows the virtualhost settings)\&.
.TP
-t
-Run syntax tests for configuration files only\&. The program immediately exits after these syntax parsing with either a return code of 0 (Syntax OK) or return code not equal to 0 (Syntax Error)\&. If -D \fIDUMP\fR_\fIVHOSTS \fRis also set, details of the virtual host configuration will be printed\&.
+Run syntax tests for configuration files only\&. The program immediately exits after these syntax parsing tests with either a return code of 0 (Syntax OK) or return code not equal to 0 (Syntax Error)\&. If -D \fIDUMP\fR_\fIVHOSTS \fRis also set, details of the virtual host configuration will be printed\&.
.TP
-v
Print the version of httpd, and then exit\&.
1.19 +2 -2 httpd-2.0/docs/man/rotatelogs.8
Index: rotatelogs.8
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/man/rotatelogs.8,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -u -r1.18 -r1.19
--- rotatelogs.8 25 Nov 2003 13:37:31 -0000 1.18
+++ rotatelogs.8 2 Dec 2003 11:53:50 -0000 1.19
@@ -19,7 +19,7 @@
.el .ne 3
.IP "\\$1" \\$2
..
-.TH "ROTATELOGS" 8 "2003-11-25" "Apache HTTP Server" "rotatelogs"
+.TH "ROTATELOGS" 8 "2003-12-02" "Apache HTTP Server" "rotatelogs"
.SH NAME
rotatelogs \- Piped logging program to rotate Apache logs
@@ -42,7 +42,7 @@
.fi
.PP
-This creates the files /var/logs/logfile\&.nnnn where nnnn is the system time at which the log nominally starts (this time will always be a multiple of the rotation time, so you can synchronize cron scripts with it)\&. At the end of each rota- tion time (here after 24 hours) a new log is started\&.
+This creates the files /var/logs/logfile\&.nnnn where nnnn is the system time at which the log nominally starts (this time will always be a multiple of the rotation time, so you can synchronize cron scripts with it)\&. At the end of each rotation time (here after 24 hours) a new log is started\&.
.nf
1.12 +2 -2 httpd-2.0/docs/man/suexec.8
Index: suexec.8
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/man/suexec.8,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -u -r1.11 -r1.12
--- suexec.8 25 Nov 2003 13:37:31 -0000 1.11
+++ suexec.8 2 Dec 2003 11:53:50 -0000 1.12
@@ -19,7 +19,7 @@
.el .ne 3
.IP "\\$1" \\$2
..
-.TH "SUEXEC" 8 "2003-11-25" "Apache HTTP Server" "suexec"
+.TH "SUEXEC" 8 "2003-12-02" "Apache HTTP Server" "suexec"
.SH NAME
suexec \- Switch user before executing external programs
@@ -44,5 +44,5 @@
.TP
-V
-If you are root, this option displays the compile options of suexec\&. For security reasons all configuration options are changable only at compile time\&.
+If you are root, this option displays the compile options of suexec\&. For security reasons all configuration options are changeable only at compile time\&.