NIS and FNS Maps and Makefiles

FNS uses six new maps which are stored in /var/yp/domainname directories on the NIS master and slave servers:

• fns_host.ctx which stores host attributes and subcontext data. When this is first created, it derives its information from the hosts.byname map.

• fns_host.ctx which stores user attributes and subcontext data. When this is first created, it derives its information from the passwd.byname map.

• fns_org.ctx which stores organization attributes and subcontext data.

• fns_host.attr which stores host attributes for attribute based searches.

• fns_user.attr which stores user attributes for attribute based searches.

• fns_org.attr which stores organization attributes for attribute based searches.

Service and file context information for hosts, users, and the organization are stored in the respective fns_host.ctx, fns_user.ctx, and fns_org.ctx maps. Printer context information is stored in the same maps as other service context information. However, the older printers.conf.byname map is still supported.

Sites are subcontexts of the organization and site context information is stored in the fns_org.ctx map.

These FNS maps should not be edited directly. You modify or work with these maps by running the appropriate FNS commands such as fncreate, fndestroy, fnbind, fnunbind, fnrename, fnattr, fnlookup, and fnlist. These commands must be run on the NIS master server. You cannot run them on slave servers or client machines.

The FNS map files are placed in the /var/yp/domainname directory. The NIS Makefile in /var/yp is modified to be aware of the FNS Makefile in /etc/fn/domainname.