Of all its parts, only dbfile is required. It specifies the file name (either absolute or relative) of the database file. If the underlying implementation stores the database in two files (as it is the case with NBDM), dbfile will be used as a base name for those files (i.e. the suffixes .pag and .dir will be appended to it).
If scheme is specified, it declares the DBM implementation to use. Valid values are:
In the absense of scheme the default database implementation will be used. This is the first one shown in the list of DBMs when configuring the package. For example, if configure showed:
Use DBM ....................... GDBM,Berkeley DB v. 4,NDBM
then gdbm:// will be assumed by default.
The optional params is a list of safety check criteria, separated by semicolons. The default keyword is synonymous with all. In addition to the usual safety criteria, the following parameter can be used:
- Enable the MU_FILE_SAFETY_OWNER_MISMATCH check. Assume that the database files must be owned by the real UID of the current user.
- Enable that check and set the user which must own the database file. The user argument is either a valid user name or UID.
- Disable that check.
/etc/apop.db bdb:///etc/apop.db bdb:///etc/apop.db;owner=root;all;-grdfil