Red Hat Bugzilla – Bug 114080
htdbm man page missing
Last modified: 2007-11-30 17:07:00 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install httpd rpm
-bash: /usr/bin/dbmmanage: No such file or directory
Usage: dbmmanage [enc] dbname command [username [pw [group[,group]
where enc is -d for crypt encryption (default except on Win32,
Netware) -m for MD5 encryption (default on Win32,
-s for SHA1 encryption
-p for plaintext
command is one of: add|adduser|check|delete|import|update|view
pw of . for update command retains the old password
pw of - (or blank) for update command prompts for the password
groups or comment of . (or blank) for update command retains old
groups or comment of - for update command clears the existing
groups or comment of - for add and adduser commands is the empty
I'm attaching a working dbmmanage file in the next section. This is
the same as the dbmmanage.in file that is in the support directory of
httpd-2.0.40.tar.gz in the source package, except that it specifies
the exact directory of the perl binary, /usr/bin/perl.
Created attachment 97162 [details]
dbmmanage perl script
This is the missing perl script.
Thanks for the report. htdbm should be used instead of dbmmanage with
the 2.0-based packages: this is covered along with other migration
issues in /usr/share/doc/httpd-2.0.40/migration.html.
Thanks for the rapid pointer, Joe. However, why do you still have the
manual pages for dbmmanage, but no manual page for htdbm?
#rpm -ql httpd | grep dbmmanage
No manual entry for htdbm
RHEL 3.0 doesn't appear to have this problem, or a man page for htdbm
(I know man pages are awful, but the habit of 12 years is hard to
Anyway, I shall try to use htdbm instead.
The presence of dbmmanage.1 and lack of htdbm.1 are genuine bugs, yes,
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.