ypinit(NADM)


ypinit -- build and install Network Information Service (NIS) databases

Syntax

ypinit -m

ypinit -s master_name

ypinit -c master_name

ypinit -C

Description

ypinit sets up a Network Information Service (NIS) database on an NIS server or client. It can be used to set up a master server, a slave server, a copy-only server, or a NIS client. You must be the super user to run it. It asks a few self-explanatory questions and reports its success or failure to the terminal. If the host has previously been initialized with ypinit, you will be asked to confirm whether ypinit should overwrite the existing configuration.

It sets up a master server using the simple model in which that server is master to all maps in the database. This is the way to bootstrap the NIS system; later the association of maps to masters can be changed. All databases are built from scratch, either from information available to the program at runtime or from the ASCII database files in /etc. Some of these files are listed below under ``Files''. Additional files may be handled by the Network Information Service as required by the local environment. All such files should be in their ``traditional'' form.

An NIS database on a slave server is set up by copying an existing database from a running server. The master_name argument should be the hostname of an NIS server, either the master server for all the maps or a server on which the database is up-to-date and stable.

An NIS database on a copy-only server is set up by copying an existing database from a running server. The master_name argument should be the hostname of an NIS server, either the master server for all the maps or a server on which the database is up-to-date and stable. The differences between a slave server and a copy-only server are that the copy-only server does not respond to NIS requests from the network while the slave server does; the copy-only server must poll a master server or slave server to update its maps while a slave server's maps are updated by the master server when the master server changes its maps; and the copy-only server does not keep full copies of both NIS maps and ASCII versions of NIS maps while a slave server keeps full copies of both.

NIS databases are not stored on an NIS client. NIS requests are sent directly to the server to which the client is bound.

In all four cases, ypinit modifies the /etc/nis script to enable the automatic starting of the NIS daemons. It also makes sure that they are started with the correct arguments. If ypinit is run on a host already set up as a master server, copy-only server, or slave server, ypinit clears the host of any entries inserted by the previous execution of ypinit and, therefore, sets up the host from scratch.

Refer to ypfiles(NF) and ypserv(NADM) for an overview of the Network Information Service.

Options


-m
indicates that the local host is to be the NIS master

-s
set up a slave database

-c
set up a copy-only server database

-C
set up an NIS client

Files

/etc/passwd
/etc/passwd.local
/etc/passwd.yp
/etc/group
/etc/group.local
/etc/group.yp

See also

makedbm(NADM), map2ascii(NADM), nfs(NADM), ypfiles(NF), ypmake(NADM), yppush(NADM), ypserv(NADM), ypxfr(NADM)
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 02 June 2005