dbmbuild -- build the MMDF hashed database of alias and routing information


/usr/mmdf/table/dbmbuild [ -nvdk ] [ database [ table ... ] ]


dbmbuild reads the tables specified in the mmdftailor(F) file into a hashed database for use in quickly verifying addresses and efficiently assigning channels to submitted messages. Whenever you change MMDF alias or routing information, you must rebuild the hashed database by logging in as mmdf and running dbmbuild from the /usr/mmdf/table directory. Note that when you use the graphical MMDF Configuration Utility to change alias and routing information, it is unnecessary to run dbmbuild; the utility does it for you.

If no database file is specified, the default database mmdfdbm is used. If no table files are specified, all tables listed in the mmdftailor file are used. In particular, three tables are read for each channel definition: the list of authorized sources, the list of authorized destinations, and the table of names/aliases for that channel. Also, the remaining tables (MTBL and MDMN) are read.

The options are:

Create a new database. If this option is omitted, dbmbuild updates an existing database. If you specify any options (even -v), you must specify the -n option if you want to create a new database.

Run in verbose mode, displaying information during table processing.

Run in debug mode, reporting everything that happens.

Keep going. If a file is mentioned that does not exist, ignore it. This option might be an appropriate default at some sites.
Appropriate locks are placed on the database so that dbmbuild can safely be run while MMDF is in operation.


$(tbldbm).dir database directory
$(tbldbm).pag database pages
$(tbldbm).lck database locking file
$(tbldfldir)/* various tables that form the database

See also

dbm(S-osr5), mmdftailor(F), tables(F)

``Editing MMDF configuration files manually'' in Managing Mail with MMDF

Standards conformance

MMDF is not part of any currently supported standard; it was developed at the University of Delaware and is used with permission.
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 03 June 2005