Maps for each domain are located in a separate, distinct /var/yp/domainname directory on the NIS server. For example, the maps for a machine that belong to the domain accounting will be located in the directory /var/yp/accounting on their corresponding NIS server.
UnixWare supplies a Makefile in the directory /var/yp of machines designated as master servers at installation time. Running ypbuild in that directory (as explained in ``Making the maps'') causes makedbm(1Mnis) to create the default NIS maps from the input files.
The manual pages for ypfiles(4nis) and dbm(3rpc) completely explain the dbm file format. Input to makedbm must be in the form of key/value pairs, where key is the first word of each line and value is whatever follows in that line. The pairs of keys and values are preserved in the NIS maps, so programs can use the keys to look up the values. The input can be from a file or from standard input (as when modified through a script; see ``Making the maps''). After passing through makedbm, the data is collected in non-ASCII form in two files, mapname.dir and mapname.pag, both in the /var/yp/domainname directory on the master server.
``A summary of NIS maps'' provides a complete listing and explanation of NIS maps.
A summary of NIS maps
|Map name||Administration file||Description|
|bootparams||/etc/bootparams||Contains pathnames of files clients need during booting such as root, swap, possibly others. Once the NIS map is created, /etc/bootparams is never consulted.|
|ethers.byaddr||/etc/ethers||Contains machine names and Ethernet addresses. The Ethernet address is the key in the map. Once the NIS map is created, /etc/ethers is never consulted.|
|ethers.byname||/etc/ethers||Same as ethers.byaddr, except key is machine name instead of Ethernet address.|
|group.byid||/etc/group||Contains group security information with group ID as the key. With NIS, the local /etc/group is consulted first, then the map.|
|group.byname||/etc/group||Contains group security information with group name as the key. With NIS, the local /etc/group is consulted first, then the map.|
|hosts.byaddr||/etc/hosts||Contains host names and IP addresses. The IP address is the key in the map. The source for host information is determined by the entries in the /etc/netconfig file. For more information, see the netconfig(4bnu) manual page.|
|hosts.byname||/etc/hosts||Same as hosts.byaddr, except key is host name instead of IP address.|
|mail.aliases||/etc/aliases||Contains aliases and mail addresses. The alias is the key in the map. With NIS, the local /etc/aliases is consulted first, then the map.|
|mail.byaddr||/etc/aliases||Same as mail.aliases, except key is mail address instead of alias.|
|netgroup.byhost||/etc/netgroup||Contains group name, user name and host name. The host name is the key in the map. Once the NIS map is created, /etc/netgroup is never consulted.|
|netgroup.byuser||/etc/netgroup||Same as netgroup.byhost, except key is user name instead of host name.|
|netgroup||/etc/netgroup||Same as netgroup.byhost, except key is group name instead of host name.|
|Contains machine name and mail address (including domain name). If there is a netid file available, it is consulted in addition to the data available through the other files.|
|netmasks.byaddr||/etc/netmasks||Contains network masks to be used with IP subnetting. The network mask is the key in the map. Once the NIS map is created, /etc/netmasks is never consulted.|
|networks.byaddr||/etc/netmasks||Contains names of networks known to your system and their IP addresses. The network address is the key in the map. Once the NIS map is created, /etc/networks is never consulted.|
|networks.byname||/etc/networks||Same as networks.byaddr, except key is network name instead of network address.|
|passwd.byname||/etc/passwd||Contains password information. The user name is the key in the map. With NIS, the local /etc/passwd is consulted first, then the map.|
|passwd.byuid||/etc/passwd||Same as passwd.byname, except key is user ID instead of user name.|
|protocols.byname||/etc/protocols||Contains network protocols known to your system. The protocol name is the key in the map. Once the NIS map is created, /etc/protocols is never consulted.|
|protocols.bynumber||/etc/protocols||Same as protocols.byname, except key is protocol number instead of protocol name.|
|publickey.byname||/etc/publickey||Contains public and secret keys. Once the NIS map is created, /etc/publickey is never consulted.|
|rpc.bynumber||/etc/rpc||Contains program number and name of RPCs known to your system. The RPC program number is the key in the map. Once the NIS map is created, /etc/rpc is never consulted.|
|services.byname||/etc/services||Lists Internet services known to your network. The service name is the key in the map. Once the NIS map is created, /etc/services is never consulted.|
|ypservers||-||Lists NIS servers known to your network.|