cvs commit: apache-1.3/src/support dbmmanage.1
rse 98/09/12 04:16:33 Modified:src CHANGES src/support dbmmanage.1 Log: Fix dbmmanage.1 manual page. Submitted by: Youichirou Koga <[EMAIL PROTECTED]> PR: 2992 Revision ChangesPath 1.1055+3 -0 apache-1.3/src/CHANGES Index: CHANGES === RCS file: /export/home/cvs/apache-1.3/src/CHANGES,v retrieving revision 1.1054 retrieving revision 1.1055 diff -u -r1.1054 -r1.1055 --- CHANGES 1998/09/10 09:23:57 1.1054 +++ CHANGES 1998/09/12 11:16:31 1.1055 @@ -1,5 +1,8 @@ Changes with Apache 1.3.2 + *) Fix dbmmanage.1 manual page. + [Youichirou Koga <[EMAIL PROTECTED]>] PR#2992 + *) Fix possible buffer overflow situation in suexec.c. [Jeff Stewart <[EMAIL PROTECTED]>] PR#2790 1.3 +1 -2 apache-1.3/src/support/dbmmanage.1 Index: dbmmanage.1 === RCS file: /export/home/cvs/apache-1.3/src/support/dbmmanage.1,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- dbmmanage.1 1998/03/31 12:53:47 1.2 +++ dbmmanage.1 1998/09/12 11:16:33 1.3 @@ -84,8 +84,7 @@ found at http://www.apache.org/. .SH OPTIONS .IP \fB\fIfilename\fP -The filename of the DBM format file. Usually without the extension .pag or -.dir. +The filename of the DBM format file. Usually without the extension .pag or .dir. .IP \fB\fIcommand\fP This selects the operation to perform: .TP 12
cvs commit: apache-1.3/src/support dbmmanage.1
rse 98/11/18 00:54:37 Modified:src CHANGES src/support dbmmanage.1 Log: Document the `add' command of `dbmmanage' in `dbmmanage.1' manpage. Submitted by: David MacKenzie <[EMAIL PROTECTED]> Reviewed by: Ralf S. Engelschall PR: 3394 Revision ChangesPath 1.1147+3 -0 apache-1.3/src/CHANGES Index: CHANGES === RCS file: /export/home/cvs/apache-1.3/src/CHANGES,v retrieving revision 1.1146 retrieving revision 1.1147 diff -u -r1.1146 -r1.1147 --- CHANGES 1998/11/14 00:36:01 1.1146 +++ CHANGES 1998/11/18 08:54:34 1.1147 @@ -1,5 +1,8 @@ Changes with Apache 1.3.4 + *) Document the `add' command of `dbmmanage' in `dbmmanage.1' manpage. + [David MacKenzie <[EMAIL PROTECTED]>] PR#3394 + *) Ignore a "ErrorDocument 401" directive with a full URL and write a notice to the error log. It is not possible to send a 401 response and a redirect at the same time. [Lars Eilebrecht] 1.4 +7 -1 apache-1.3/src/support/dbmmanage.1 Index: dbmmanage.1 === RCS file: /export/home/cvs/apache-1.3/src/support/dbmmanage.1,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- dbmmanage.1 1998/09/12 11:16:33 1.3 +++ dbmmanage.1 1998/11/18 08:54:37 1.4 @@ -60,7 +60,9 @@ .I command ] [ .I username -] +[ +.I encpasswd +] ] .PP .SH DESCRIPTION .B dbmmanage @@ -87,6 +89,10 @@ The filename of the DBM format file. Usually without the extension .pag or .dir. .IP \fB\fIcommand\fP This selects the operation to perform: +.TP 12 +.B add +Adds an entry for \fIusername\fP to \fIfilename\fP using the encrypted +password \fIencpassword\fP. .TP 12 .B adduser Asks for a password and then adds an entry for \fIusername\fP to
cvs commit: apache-1.3/src/support dbmmanage.1
brian 99/03/03 12:39:34 Modified:src/support dbmmanage.1 Log: Scratching an itch... documenting the difference between different DBM files in an attempt to stave off some support questions. Revision ChangesPath 1.6 +48 -1 apache-1.3/src/support/dbmmanage.1 Index: dbmmanage.1 === RCS file: /home/cvs/apache-1.3/src/support/dbmmanage.1,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- dbmmanage.1 1999/01/01 19:05:33 1.5 +++ dbmmanage.1 1999/03/03 20:39:33 1.6 @@ -86,7 +86,8 @@ found at http://www.apache.org/. .SH OPTIONS .IP \fB\fIfilename\fP -The filename of the DBM format file. Usually without the extension .pag or .dir. +The filename of the DBM format file. Usually without the +extension .db, .pag, or .dir. .IP \fB\fIcommand\fP This selects the operation to perform: .TP 12 @@ -118,6 +119,52 @@ Just displays the complete contents of the DBM file. .IP \fB\fIusername\fP The user for which the update operation is performed. +.PD +.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 +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 +that the file format used by +.I filename +is the same format that +.B dbmmanage +expects to see. +.B dbmmanage +currently has no way of determining what type of DBM file it is +looking at. If used against the wrong format, +.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. +.PP +.B dbmmanage +has a list of DBM format preferences, defined by the +.B @AnyDBM::ISA +array near the beginning of the program. Since we prefer the Berkeley +DB 2 file format, the order in which +.B dbmmanage +will look for system libraries is Berkeley DB 2, then NDBM, and then +GDBM. The first library found will be the library +.B dbmmanage +will attempt to use for all DBM file transactions. This ordering is +slightly different than the standard +.B @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 +Apache's +.B mod_auth_db.c +module corresponds to Berkeley DB 2 library, while +.B mod_auth_dbm.c +corresponds to the NDBM library. Also, one can usually use the +.B file +program supplied with most Unix systems to see what format a DBM file is in. .PD .SH SEE ALSO .BR httpd(8)
cvs commit: apache-1.3/src/support dbmmanage.1 suexec.8 htdigest.1 rotatelogs.8 logresolve.8 htpasswd.1
rse 98/03/19 02:05:51 Modified:.STATUS src CHANGES src/support htpasswd.1 Added: src/support dbmmanage.1 suexec.8 htdigest.1 rotatelogs.8 logresolve.8 Log: Here they come, fresh out of my fingers: Manual pages for support programs which still don't have one. Revision ChangesPath 1.197 +1 -0 apache-1.3/STATUS Index: STATUS === RCS file: /export/home/cvs/apache-1.3/STATUS,v retrieving revision 1.196 retrieving revision 1.197 diff -u -r1.196 -r1.197 --- STATUS1998/03/17 15:47:30 1.196 +++ STATUS1998/03/19 10:05:37 1.197 @@ -96,6 +96,7 @@ * Ralf's new ApacheBench support program (src/support/ab.c) * Ken's change HIDE default to "yes", always include hide.h * Ralf's major Configure cleanup +* Ralf's additional manual pages for the support programs Available Patches: 1.722 +6 -0 apache-1.3/src/CHANGES Index: CHANGES === RCS file: /export/home/cvs/apache-1.3/src/CHANGES,v retrieving revision 1.721 retrieving revision 1.722 diff -u -r1.721 -r1.722 --- CHANGES 1998/03/17 15:42:22 1.721 +++ CHANGES 1998/03/19 10:05:40 1.722 @@ -1,5 +1,11 @@ Changes with Apache 1.3b6 + *) Add five new and fresh manpages for the support programs: dbmmanage.1, + suexec.8, htdigest.1, rotatelogs.8 and logresolve.8. Now all up-to-date + and per default compiled support programs have manual pages - just to + document our stuff a little bit more and to be able to do really + Unix-like installations ;-) [Ralf S. Engelschall] + *) Major cleanups to the Configure script to make it and its generated Makefiles again readable and maintainable: add SRCDIR option, removed INCLUDES_DEPTH[0-2] kludge, cleanup of TARGET option, cleanup of 1.5 +2 -1 apache-1.3/src/support/htpasswd.1 Index: htpasswd.1 === RCS file: /export/home/cvs/apache-1.3/src/support/htpasswd.1,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- htpasswd.11998/03/16 16:04:22 1.4 +++ htpasswd.11998/03/19 10:05:45 1.5 @@ -90,4 +90,5 @@ \fIusername\fP does not exist is this file, an entry is added. If it does exist, the password is changed. .SH SEE ALSO -httpd(8) +.BR httpd(8) +. 1.1 apache-1.3/src/support/dbmmanage.1 Index: dbmmanage.1 === .TH dbmmanage 1 "March 1998" .\" Copyright (c) 1998 The Apache Group. All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" .\" 1. Redistributions of source code must retain the above copyright .\"notice, this list of conditions and the following disclaimer. .\" .\" 2. Redistributions in binary form must reproduce the above copyright .\"notice, this list of conditions and the following disclaimer in .\"the documentation and/or other materials provided with the .\"distribution. .\" .\" 3. All advertising materials mentioning features or use of this .\"software must display the following acknowledgment: .\""This product includes software developed by the Apache Group .\"for use in the Apache HTTP server project (http://www.apache.org/)." .\" .\" 4. The names "Apache Server" and "Apache Group" must not be used to .\"endorse or promote products derived from this software without .\"prior written permission. .\" .\" 5. Redistributions of any form whatsoever must retain the following .\"acknowledgment: .\""This product includes software developed by the Apache Group .\"for use in the Apache HTTP server project (http://www.apache.org/)." .\" .\" THIS SOFTWARE IS PROVIDED BY THE APACHE GROUP ``AS IS'' AND ANY .\" EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE GROUP OR .\" ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, .\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; .\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, .\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED .\" OF THE POSSIBILITY OF SUCH DAMAGE.