![]() ![]() |
23.5 Database Maps with mc ConfigurationAll available mc database maps are implemented as mc features. Table 23-4 lists those that are available. The second column shows you where to find information about each.
Note that these features do not necessarily need to be used with database files. To illustrate, consider the domaintable feature (FEATURE(domaintable)). It is included in your mc file like this: FEATURE(`domaintable',`nis domaintable') Here, we specify that the database map is to be the nis type. This causes the key to be looked up via NIS and any match to be returned the same way. 23.5.1 Set a Default Database-Map Type for FeaturesFeatures that employ on-disk database files all share the common default database-map type hash. But if you wish to change that default to another type, you can do so with the following mc configuration command: define(`DATABASE_MAP_TYPE', `dbm') Here, we declare the default to be dbm, thereby causing all such features to use ndbm(3) database files. Note that if you declare a default, you must do so before declaring any database features. Many features that take arguments require you to declare the database type. For example: FEATURE(`authinfo', `dbm /etc/security/authinfo') That is, this DATABASE_MAP_TYPE's default is used only if no argument is given for the feature. |
![]() ![]() |