Advanced NIS administration

Adding new NIS maps to the Makefile

Adding a new NIS map entails getting copies of the map's dbm files into the /var/yp/domainname directory on each of the NIS servers in the domain. A full description is given in ``Propagating an NIS map''. This section only describes how to update the Makefile so that propagation works correctly.

After deciding which NIS server is the master of the map, modify /var/yp/Makefile on the master server so that you can conveniently rebuild the map.

NOTE: As indicated previously, different servers can be masters of different maps, but in most cases this can lead to administrative confusion. It is strongly recommended that you set only one server as the master of all maps.

Actual case-by-case modification is too varied to describe here, but typically a human-readable ASCII file is filtered through awk, sed, and/or grep to make it suitable for input to makedbm. Refer to the existing /var/yp/Makefile for examples and to ``Modifying the Makefile''.

Use the mechanisms already in place in /var/yp/Makefile when deciding how to create dependencies that ypbuild will recognize; specifically, the use of .time files allows you to see when the Makefile was last run for the map. Also, be aware that ypbuild is sensitive to the presence or absence of tabs at the beginning of lines within the dependency rules and that a missing tab can invalidate an entry that is otherwise well-formed.

To get an initial copy of the map, you can have ypbuild run yppush on the NIS master server. The map must be available globally before clients begin to access it.

NOTE: If the map is available from some NIS servers but not all, you will encounter unpredictable behavior from client programs.

© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 22 April 2004