Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ypinit(8) [freebsd man page]

YPINIT(8)						    BSD System Manager's Manual 						 YPINIT(8)

ypinit -- build and install NIS databases SYNOPSIS
ypinit -m [domainname] ypinit -s master_server [domainname] ypinit -u [domainname] DESCRIPTION
The ypinit utility is a script which sets up databases on a Network Information Service (NIS) master or slave server. On a master server, ypinit creates the /var/yp/$DOMAINNAME directory, the /var/yp/ypservers file, and calls /var/yp/Makefile to create and populate an initial set of NIS maps. The maps are created from local source files using the yp_mkdb(8) utility. The utility will prompt the user for a list of servers that support the specified domain; this list is used to populate the ypservers map. On a slave server, ypinit creates the /var/yp/$DOMAINNAME, populates it with copies of the NIS maps from the master. The maps are obtained from the master using the ypxfr(8) utility. The ypinit utility obtains the list of maps to transfer in one of two ways: if the system is configured as an NIS client and is bound to the master server, ypinit is able to use the ypwhich(1) utility to obtain a list of maps exported by the master server. If the system is not configured as a client of the NIS master, ypinit uses a hardcoded list of maps, some of which may or may not actually exist on the master. The system administrator can edit the ypinit script and modify the map list if necessary. Other- wise, individual maps can be transferred manually from the master using ypxfr(8). OPTIONS
The ypinit utility supports the following options: -m [domainname] Set up a master server. By default, ypinit sets up a server for the system default domain. The user can override this default by specifying domainname explicitly. Maps are constructed from scratch using local files as templates using the yp_mkdb(8) utility. -s master_server [domainname] Set up a slave server using master_name as the master. Maps are copied from master_server to the slave using ypxfr(8). By default, ypinit sets up a server for the system default domain. The user can override this default by specifying domainname explicitly. -u [domainname] Update the ypservers map on the master server. When a new slave server is added to a domain, its hostname must be added to the ypservers map so that yppush(8) can propagate updates on the master to all of the slaves. FILES
/etc/bootparams Bootparams source file /etc/ethers Ethers data source file /etc/group Group source file /etc/hosts Hostname/IP address source file /etc/netid RPC netid source file /etc/networks Networks source file /etc/protocols Protocols source file /etc/publickey RPC public key/secret key source file /etc/services Services data source file /etc/shells Shells source file /var/yp/master.passwd Passwd database source file /var/yp/netgroup Netgroup data source file /var/yp/ypservers Ypservers source file (generated by ypinit) SEE ALSO
mknetid(8), revnetgroup(8), yp(8), yp_mkdb(8), yppush(8), ypserv(8), ypxfr(8) HISTORY
This version of ypinit is based on the ypinit script in OpenBSD. It first appeared in FreeBSD 3.0. AUTHORS
The original script was written by Mats O Jansson <>. It was modified for FreeBSD by Bill Paul <>. BSD
November 10, 1997 BSD

Check Out this Related Man Page

ypinit(1M)						  System Administration Commands						ypinit(1M)

ypinit - set up NIS client SYNOPSIS
/usr/sbin/ypinit [-c] [-m] [-s master_server] DESCRIPTION
ypinit can be used to set up an NIS client system. You must be the superuser to run this command. This script need not be used at all if ypbind(1M) is started with the -broadcast option (it is invoked with this option from the svc:/network/nis/client:default service). Normally, ypinit is run only once after installing the system. It may be run whenever a new NIS server is added to the network or an existing one is decommissioned. ypinit prompts for a list of NIS servers to bind the client to; this list should be ordered from the closest to the furthest server. Each of these NIS servers must be listed in either the /etc/hosts or the /etc/inet/ipnodes file along with its IP address. ypinit stores the list in file /var/yp/binding/domain/ypservers. This file is used by ypbind when run without the -broadcast option. OPTIONS
-c Set up a ypclient system. -m Build a master ypserver data base. -s master_server Slave data base. master_server must be the same master configured in the YP maps and returned by the ypwhich -m command. FILES
/etc/hosts /etc/inet/ipnodes /var/yp/binding/domain/ypservers ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnisu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), svcadm(1M), ypbind(1M), sysinfo(2), hosts(4), ipnodes(4), attributes(5), smf(5) NOTES
The NIS client service is managed by the service management facility, smf(5), under the service identifier: svc:/network/nis/client:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. BUGS
ypinit sets up the list of NIS servers only for the current domain on the system when it is run, that is, the domain returned by the SI_SRPC_DOMAIN command to sysinfo(2). Care should be taken to ensure that this is the same as the desired domain for NIS client processes. SunOS 5.10 13 Aug 2004 ypinit(1M)
Man Page

Featured Tech Videos