Unix User Management Using Edirectory - Novell NETWARE 6-DOCUMENTATION Manual

NIS Slave Server
You can set up read-only copies of the NIS database on secondary servers. The
secondary servers are referred to as slaves. When the server is set up as an NIS
slave, it contacts the master NIS server and requests a complete copy of the
NIS maps on that server.
Once the slave server is set up, you don't need to manage the update process
manually. The slave servers periodically query the master and request an
update when the slave detects a more recent time stamp on the master. A slave
server can be added to the Ypservers map in the master.
We recommend that you set up at least one slave server for each NIS domain.
The slave server can then function as a standby if the master server goes down,
although it might not be necessary in all networks. Slave servers can also be
used for load distribution in the network. A master NIS server for one domain
can also function as a slave NIS server for another domain.
NIS Client
NIS client enables users to query NIS map information from NIS servers.
For more information on setting up and managing NIS, see "NIS Server" on
page 94.

UNIX User Management Using eDirectory

With the implementation of NIS over eDirectory, there exists only one user/
group in the network which contains both eDirectory information and UNIX
information. This brings up the user management to single point, namely
eDirectory.
For this purpose, the eDirectory schema has been extended and the relevant
user information is placed in the eDirectory Library. The User object now
stores UNIX information such as UID, GID, password, home directory, and
shell on eDirectory.
By default, UNIX users /groups are looked for within the containers specified
by the parameter SEARCH_ROOT in the configuration file NFS.CFG. The
search is recursive within the containers specified by this parameter. In case
the parameter does not contain any value, then the search is done under the
default bindery or servers context.
When a set of users/groups are migrated to eDirectory from a UNIX server,
corresponding User/Group objects are created /updated in eDirectory. During
63
Working with UNIX Machines