ypinit(1Mnis)


ypinit -- build and install NIS database

Synopsis

/usr/sbin/ypinit -c

/usr/sbin/ypinit -m

/usr/sbin/ypinit -s master-name

Description

The ypinit command sets up the Network Information Service (NIS) on a server or a client.

Files

/var/yp/binding/domainname/ypservers

Usage

ypinit can be used to set up an NIS master server, an NIS slave server, or an NIS client. To run ypinit, you must be the NIS administrator root with the appropriate privileges. It asks a few self-explanatory questions, and reports success or failure to the terminal.

ypinit sets up a master server using the simple model in which that server is master to all maps in the data base. This is the way to bootstrap the NIS system; later if you want you can change the association of maps to masters.

All databases are built from scratch, either from information available to the program at runtime, or from the ASCII data base files in /etc. These files should be in their ``traditional'' form, rather than the abbreviated form used on client machines.

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 a NIS server (either the master server for all the maps, or a server on which the data base is up-to-date and stable).

To set up a client, ypinit prompts for a list of NIS servers to bind the client to, this list should be ordered from closest to farthest server.

Refer to ypfiles(4nis) and ypserv(1Mnis) for an overview of the NIS service.

Options

ypinit takes the following options:

-c
Set up a client system.

-m
Indicate that the local host is to be the NIS master.

-s master-name
Set up a slave database.

References

makedbm(1Mnis), ypbuild(1Mnis), yppush(1Mnis), ypserv(1Mnis), ypxfr(1Mnis), ypfiles(4nis)
30 January 1998
© 1998 The Santa Cruz Operation, Inc. All rights reserved.