From: André Malo Date: Wed, 30 Apr 2003 23:25:09 +0000 (+0000) Subject: fresh manpage for dbmmanage. Some grammatical review desired ... :) X-Git-Tag: pre_ajp_proxy~1755 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7c386476eef32cc45b2d7f1c9a22f86b27a93626;p=apache fresh manpage for dbmmanage. Some grammatical review desired ... :) git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@99663 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/STATUS b/docs/STATUS index ccd44b8710..ced5efe8da 100644 --- a/docs/STATUS +++ b/docs/STATUS @@ -1,5 +1,5 @@ Apache HTTP Server 2.1 Documentation Status File. -Last modified: $Date: 2003/04/29 23:07:52 $ +Last modified: $Date: 2003/04/30 23:25:08 $ For more information on how to contribute to the Apache Documentation Project, please see http://httpd.apache.org/docs-project/ @@ -189,7 +189,6 @@ http://httpd.apache.org/docs-project/docsformat.html developer/API.html # converting from nroff to xml -programs/dbmmanage.html programs/htdigest.html programs/htpasswd.html programs/other.html diff --git a/docs/man/dbmmanage.1 b/docs/man/dbmmanage.1 index 376bdb8b93..555f955d1e 100644 --- a/docs/man/dbmmanage.1 +++ b/docs/man/dbmmanage.1 @@ -1,168 +1,124 @@ -.TH dbmmanage 1 "March 1998" -.\" The Apache Software License, Version 1.1 -.\" -.\" Copyright (c) 2000-2003 The Apache Software Foundation. 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. The end-user documentation included with the redistribution, -.\" if any, must include the following acknowledgment: -.\" "This product includes software developed by the -.\" Apache Software Foundation (http://www.apache.org/)." -.\" Alternately, this acknowledgment may appear in the software itself, -.\" if and wherever such third-party acknowledgments normally appear. -.\" -.\" 4. The names "Apache" and "Apache Software Foundation" must -.\" not be used to endorse or promote products derived from this -.\" software without prior written permission. For written -.\" permission, please contact apache@apache.org. -.\" -.\" 5. Products derived from this software may not be called "Apache", -.\" nor may "Apache" appear in their name, without prior written -.\" permission of the Apache Software Foundation. -.\" -.\" THIS SOFTWARE IS PROVIDED ``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 SOFTWARE FOUNDATION 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. -.\" -.\" This software consists of voluntary contributions made by many -.\" individuals on behalf of the Apache Software Foundation. For more -.\" information on the Apache Software Foundation, please see -.\" . -.\" +.\" XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX +.\" DO NOT EDIT! Generated from XML source. +.\" XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "DBMMANAGE" 1 "2003-04-30" "Apache HTTP Server" "dbmmanage" + .SH NAME -dbmmanage \- Create and update user authentication files in DBM format -.SH SYNOPSIS -.B dbmmanage -.I filename -[ -.I command -] [ -.I username -[ -.I encpasswd -] ] +dbmmanage \- Manage user authentication files in DBM format + +.SH "SYNOPSIS" + +.PP +\fBdbmmanage\fR [ \fIencoding\fR ] \fIfilename\fR add|adduser|check|delete|update \fIusername\fR [ \fIencpasswd\fR [ \fIgroup\fR[,\fIgroup\fR\&.\&.\&.] [ \fIcomment\fR ] ] ] + +.PP +\fBdbmmanage\fR \fIfilename\fR view [ \fIusername\fR ] + +.PP +\fBdbmmanage\fR \fIfilename\fR import + + +.SH "SUMMARY" + .PP -.SH DESCRIPTION -.B dbmmanage -is used to create and update the DBM format files used to store -usernames and password for basic authentication of HTTP users. -Resources available from the -.B httpd -Apache web server can be restricted to just the users listed -in the files created by -.B dbmmanage. -This program can only be used -when the usernames are stored in a DBM file. To use a -flat-file database see -\fBhtpasswd\fP. +dbmmanage is used to create and update the DBM format files used to store usernames and password for basic authentication of HTTP users\&. Resources available from the Apache HTTP server can be restricted to just the users listed in the files created by dbmmanage\&. This program can only be used when the usernames are stored in a DBM file\&. To use a flat-file database see htpasswd\&. + .PP -This manual page only lists the command line arguments. For details of -the directives necessary to configure user authentication in -.B httpd -see -the Apache manual, which is part of the Apache distribution or can be -found at http://www.apache.org/. -.SH OPTIONS -.IP \fB\fIfilename\fP -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 -.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 -\fIfilename\fP . -.TP 12 -.B check -Asks for a password and then checks if -\fIusername\fP is in \fIfilename\fP and if it's password matches -the specified one. -.TP 12 -.B delete -Deletes the \fIusername\fP entry from \fIfilename\fP. -.TP 12 -.B import -Reads username:password entries (one per line) from STDIN and adds them to -\fIfilename\fP. The passwords already has to be crypted. -.TP 12 -.B update -Same as the "adduser" command, except that it makes sure \fIusername\fP -already exists in \fIfilename\fP. -.TP 12 -.B view -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 +This manual page only lists the command line arguments\&. For details of the directives necessary to configure user authentication in httpd see the httpd manual, which is part of the Apache distribution or can be found at http://httpd\&.apache\&.org/\&. + + +.SH "OPTIONS" + +.RS + +.TP +\fIfilename\fR +The filename of the DBM format file\&. Usually without the extension \&.db, \&.pag, or \&.dir\&. +.TP +\fIusername\fR +The user for which the operations are performed\&. The \fIusername\fR may not contain a colon (:)\&. +.TP +\fIencpasswd\fR +This is the already encrypted password to use for the update and add commands\&. You may use a hyphen (-) if you want to get prompted for the password, but fill in the fields afterwards\&. Additionally when using the update command, a period (\&.) keeps the original password untouched\&. +.TP +\fIgroup\fR +A group, which the user is member of\&. A groupname may not contain a colon (:)\&. You may use a hyphen (-) if you don't want to assign the user to a group, but fill in the comment field\&. Additionally when using the update command, a period (\&.) keeps the original groups untouched\&. +.TP +\fIcomment\fR +This is the place for your opaque comments about the user, like realname, mailaddress or such things\&. The server will ignore this field\&. +.RE + +.Sh "ENCODINGS" + +.RS + +.TP +-d +crypt encryption (default, except on Win32, Netware) +.TP +-m +MD5 encryption (default on Win32, Netware) +.TP +-s +SHA1 encryption +.TP +-p +plaintext (\fInot recommended\fR) +.RE + +.Sh "COMMANDS" + +.RS + +.TP +add +Adds an entry for \fIusername\fR to \fIfilename\fR using the encrypted password \fIencpasswd\fR\&. +.TP +adduser +Asks for a password and then adds an entry for \fIusername\fR to \fIfilename\fR\&. +.TP +check +Asks for a password and then checks if \fIusername\fR is in \fIfilename\fR and if it's password matches the specified one\&. +.TP +delete +Deletes the \fIusername\fR entry from \fIfilename\fR\&. +.TP +import +Reads \fIusername\fR:\fIpassword\fR entries (one per line) from STDIN and adds them to \fIfilename\fR\&. The passwords already have to be crypted\&. +.TP +update +Same as the adduser command, except that it makes sure \fIusername\fR already exists in \fIfilename\fR\&. +.TP +view +Just displays the contents of the DBM file\&. If you specify a \fIusername\fR, it displays the particular record only\&. +.RE + +.SH "BUGS" + .PP -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 -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. +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 -.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. +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 -Apache's -.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) -. +One can usually use the file program supplied with most Unix systems to see what format a DBM file is in\&. + diff --git a/docs/manual/programs/dbmmanage.html b/docs/manual/programs/dbmmanage.html deleted file mode 100644 index edc8770e62..0000000000 --- a/docs/manual/programs/dbmmanage.html +++ /dev/null @@ -1,126 +0,0 @@ - - - - - - - Manual Page: dbmmanage - Apache HTTP Server - - - -
- [APACHE DOCUMENTATION] - -

Apache HTTP Server Version 2.1

-
- - - -

Manual Page: dbmmanage

- -
-NAME
-     dbmmanage - Create and update user authentication  files  in
-     DBM format
-
-SYNOPSIS
-     dbmmanage filename [ command ] [ username [ encpasswd ] ]
-
-DESCRIPTION
-     dbmmanage is used to create and update the DBM format  files
-     used  to  store usernames and password for basic authentica-
-     tion of HTTP users.   Resources  available  from  the  httpd
-     Apache web server can be restricted to just the users listed
-     in the files created by dbmmanage. This program can only  be
-     used  when  the usernames are stored in a DBM file. To use a
-     flat-file database see htpasswd.
-
-     This manual page only lists the command line arguments.  For
-     details  of  the  directives  necessary  to  configure  user
-     authentication in httpd see the Apache manual, which is part
-     of   the   Apache   distribution   or   can   be   found  at
-     http://www.apache.org/.
-
-OPTIONS
-     filename
-          The filename of the DBM format  file.  Usually  without
-          the extension .db, .pag, or .dir.
-
-     command
-          This selects the operation to perform:
-
-     add         Adds an entry for username to filename using the
-                 encrypted password encpassword.
-
-     adduser     Asks for a password and then adds an  entry  for
-                 username to filename .
-
-     check       Asks for a password and then checks if  username
-                 is  in filename and if it's password matches the
-                 specified one.
-
-     delete      Deletes the username entry from filename.
-
-     import      Reads username:password entries (one  per  line)
-                 from  STDIN and adds them to filename. The pass-
-                 words already has to be crypted.
-
-     update      Same as the "adduser" command,  except  that  it
-                 makes sure username already exists in filename.
-
-     view        Just displays the complete contents of  the  DBM
-                 file.
-
-     username    The user for which the update operation is  per-
-                 formed.
-
-BUGS
-     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 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 filename is the same  format  that  dbmmanage
-     expects  to see. dbmmanage currently has no way of determin-
-     ing 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.
-
-     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, and then GDBM.   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.
-
-     Apache's mod_auth_dbm.c  corresponds  to  the  NDBM
-     library.  Also, one can usually use the  file  program  sup-
-     plied  with  most Unix systems to see what format a DBM file
-     is in.
-
-SEE ALSO
-     httpd(8)
-
-
-
- -

Apache HTTP Server Version 2.1

- Index - Home - - - - - diff --git a/docs/manual/programs/dbmmanage.html.en b/docs/manual/programs/dbmmanage.html.en new file mode 100644 index 0000000000..ababb460a1 --- /dev/null +++ b/docs/manual/programs/dbmmanage.html.en @@ -0,0 +1,164 @@ + + + +dbmmanage - Manage user authentication files in DBM format - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.1

+
+
<-
+

dbmmanage - Manage user authentication files in DBM format

+

dbmmanage is used to create and update the DBM format files + used to store usernames and password for basic authentication of HTTP users. + Resources available from the Apache HTTP server can be restricted to just + the users listed in the files created by dbmmanage. This + program can only be used when the usernames are stored in a DBM file. To + use a flat-file database see htpasswd.

+ +

This manual page only lists the command line arguments. For details of + the directives necessary to configure user authentication in + httpd see the httpd manual, which is part of + the Apache distribution or can be found at http://httpd.apache.org/.

+
+ +
top
+
+

Synopsis

+

dbmmanage [ encoding ] + filename add|adduser|check|delete|update + username + [ encpasswd + [ group[,group...] + [ comment ] ] ]

+ +

dbmmanage filename + view [ username ]

+ +

dbmmanage filename import

+
top
+
+

Options

+
+
filename
+
The filename of the DBM format file. Usually without the extension + .db, .pag, or .dir.
+ +
username
+
The user for which the operations are performed. The username + may not contain a colon (:).
+ +
encpasswd
+
This is the already encrypted password to use for the + update and add commands. You may use a hyphen + (-) if you want to get prompted for the password, but fill + in the fields afterwards. Additionally when using the update + command, a period (.) keeps the original password + untouched.
+ +
group
+
A group, which the user is member of. A groupname may not contain a + colon (:). You may use a hyphen (-) if you don't + want to assign the user to a group, but fill in the comment field. + Additionally when using the update command, a period + (.) keeps the original groups untouched.
+ +
comment
+
This is the place for your opaque comments about the user, like + realname, mailaddress or such things. The server will ignore this + field.
+
+ +

Encodings

+
+
-d
+
crypt encryption (default, except on Win32, Netware)
+ +
-m
+
MD5 encryption (default on Win32, Netware)
+ +
-s
+
SHA1 encryption
+ +
-p
+
plaintext (not recommended)
+
+ + +

Commands

+
+
add
+
Adds an entry for username to filename using the + encrypted password encpasswd.
+ +
adduser
+
Asks for a password and then adds an entry for username to + filename.
+ +
check
+
Asks for a password and then checks if username is in + filename and if it's password matches the specified one.
+ +
delete
+
Deletes the username entry from filename.
+ +
import
+
Reads username:password entries + (one per line) from STDIN and adds them to + filename. The passwords already have to be crypted.
+ +
update
+
Same as the adduser command, except that it makes + sure username already exists in filename.
+ +
view
+
Just displays the contents of the DBM file. If you specify a + username, it displays the particular record only.
+
+ +
top
+
+

Bugs

+

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 filename 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.

+ +

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.

+ +

One can usually use the file program supplied with most + Unix systems to see what format a DBM file is in.

+
+ + \ No newline at end of file diff --git a/docs/manual/programs/dbmmanage.xml b/docs/manual/programs/dbmmanage.xml new file mode 100644 index 0000000000..26dae9be90 --- /dev/null +++ b/docs/manual/programs/dbmmanage.xml @@ -0,0 +1,151 @@ + + + + +Programs + +dbmmanage - Manage user authentication files in DBM format + + +

dbmmanage is used to create and update the DBM format files + used to store usernames and password for basic authentication of HTTP users. + Resources available from the Apache HTTP server can be restricted to just + the users listed in the files created by dbmmanage. This + program can only be used when the usernames are stored in a DBM file. To + use a flat-file database see htpasswd.

+ +

This manual page only lists the command line arguments. For details of + the directives necessary to configure user authentication in + httpd see the httpd manual, which is part of + the Apache distribution or can be found at http://httpd.apache.org/.

+ +httpd +mod_authn_dbm +mod_authz_dbm + +
Synopsis +

dbmmanage [ encoding ] + filename add|adduser|check|delete|update + username + [ encpasswd + [ group[,group...] + [ comment ] ] ]

+ +

dbmmanage filename + view [ username ]

+ +

dbmmanage filename import

+
+ +
Options +
+
filename
+
The filename of the DBM format file. Usually without the extension + .db, .pag, or .dir.
+ +
username
+
The user for which the operations are performed. The username + may not contain a colon (:).
+ +
encpasswd
+
This is the already encrypted password to use for the + update and add commands. You may use a hyphen + (-) if you want to get prompted for the password, but fill + in the fields afterwards. Additionally when using the update + command, a period (.) keeps the original password + untouched.
+ +
group
+
A group, which the user is member of. A groupname may not contain a + colon (:). You may use a hyphen (-) if you don't + want to assign the user to a group, but fill in the comment field. + Additionally when using the update command, a period + (.) keeps the original groups untouched.
+ +
comment
+
This is the place for your opaque comments about the user, like + realname, mailaddress or such things. The server will ignore this + field.
+
+ +
Encodings +
+
-d
+
crypt encryption (default, except on Win32, Netware)
+ +
-m
+
MD5 encryption (default on Win32, Netware)
+ +
-s
+
SHA1 encryption
+ +
-p
+
plaintext (not recommended)
+
+
+ +
Commands +
+
add
+
Adds an entry for username to filename using the + encrypted password encpasswd.
+ +
adduser
+
Asks for a password and then adds an entry for username to + filename.
+ +
check
+
Asks for a password and then checks if username is in + filename and if it's password matches the specified one.
+ +
delete
+
Deletes the username entry from filename.
+ +
import
+
Reads username:password entries + (one per line) from STDIN and adds them to + filename. The passwords already have to be crypted.
+ +
update
+
Same as the adduser command, except that it makes + sure username already exists in filename.
+ +
view
+
Just displays the contents of the DBM file. If you specify a + username, it displays the particular record only.
+
+
+
+ +
Bugs +

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 filename 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.

+ +

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.

+ +

One can usually use the file program supplied with most + Unix systems to see what format a DBM file is in.

+
+ + diff --git a/docs/manual/programs/dbmmanage.xml.meta b/docs/manual/programs/dbmmanage.xml.meta new file mode 100644 index 0000000000..f2dbe79cea --- /dev/null +++ b/docs/manual/programs/dbmmanage.xml.meta @@ -0,0 +1,11 @@ + + + + dbmmanage + /programs/ + .. + + + en + + diff --git a/docs/manual/style/chm/hhc.xsl b/docs/manual/style/chm/hhc.xsl index 4a085e7d73..75e2906bab 100644 --- a/docs/manual/style/chm/hhc.xsl +++ b/docs/manual/style/chm/hhc.xsl @@ -84,7 +84,6 @@ developer/API.xml - programs/dbmmanage.xml programs/htdigest.xml programs/htpasswd.xml programs/other.xml