yppush(8) [redhat man page]
YPPUSH(8) Reference Manual YPPUSH(8) NAME
yppush - force propagation of changed NIS databases SYNOPSIS
/usr/sbin/yppush [ -d domain ] [ -t timeout ] [ -p # parallel jobs ] [ -h host ] [ -v ] mapname ... DESCRIPTION
yppush copies updated NIS databases (or maps) from the master NIS server to the slave servers within a NIS domain. It is normally run only on the NIS master by /var/yp/Makefile after the master databases are changed. /var/yp/Makefile does not invoke yppush by default, the NOPUSH=true line must be commented out. yppush first constructs a list of NIS slave servers by reading the NIS map ypservers within the domain. A destination host (or a list of hosts with multiple -h commands) can also be specified on the command line. A "transfer map" request is sent to the NIS serger at each slave, along with the information needed by the transfer agent ypxfr(8) to callback to yppush, which may be printed the result to stderr. Messages are also printed when a transfer is not possible; for instance when the request message is undeliverable. OPTIONS
-d domain Specify a particular domain. The NIS domain of the local host system is used by default. If the local host's domain name is not set, the domain name must be specified with this flag. -t timeout The timeout flag is used to specify a timeout value in seconds. This timeout controls how long yppush will wait for a response from a slave server before sending a map transfer request to the next slave server in the list. By default, yppush will wait 90 seconds. For big maps, this is not long enough. -p # parallel jobs yppush normally performs transfers serially, meaning that it will send a map transfer request to one slave server and then wait for it to respond before sending the next map transfer request to the next slave server. In environments with many slaves, it is more efficient to initiate several map transfers at once so that the transfers can take place in parallel. -h host The host flag can be used to transfer a map to a user-specified machine or group of machines instead of the list of servers con- tained in the ypservers map. A list of hosts can be specified by using multiple instances of the -h flag. -v Verbose mode: causes yppush to print debugging messages as it runs. Note specifying this flag twice makes yppush even more verbose. SEE ALSO
domainname(1), ypserv(8), ypxfr(8) BUGS
The mechanism for transferring NIS maps in NIS v1 is different that that in NIS version 2. This version of yppush has support for transfer- ring maps to NIS v2 systems only. AUTHOR
Thorsten Kukuk <kukuk@suse.de> YP Server August 2002 YPPUSH(8)
Check Out this Related Man Page
yppush(1M) System Administration Commands yppush(1M) NAME
yppush - force propagation of changed NIS map SYNOPSIS
/usr/lib/netsvc/yp/yppush [-v] [-h host] [-d domain] [-p #parallel-xfrs] mapname DESCRIPTION
yppush copies a new version of a Network Information Service (NIS) map from the master NIS server to the slave NIS servers. It is normally run only on the master NIS server by the Makefile in /var/yp after the master databases are changed. It first constructs a list of NIS server hosts by reading the NIS ypservers map within the domain. Keys within the ypservers map are the ASCII names of the machines on which the NIS servers run. A "transfer map" request is sent to the NIS server at each host, along with the information needed by the transfer agent (the program that actually moves the map) to call back the yppush. When the attempt has completed (successfully or not), and the transfer agent has sent yppush a status message, the results can be printed to stdout. Messages are also printed when a transfer is not possible, for instance, when the request message is undeliverable, or when the timeout period on responses has expired. Refer to ypfiles(4) and ypserv(1M) for an overview of the NIS service. OPTIONS
The following options are supported: -d domain Specifies a domain. -h host Propagates only to the named host. -p #parallel-xfrs Allows the specified number of map transfers to occur in parallel. -v Verbose. This prints messages when each server is called, and for each response. If this flag is omitted, only error messages are printed. FILES
/var/yp Directory where NIS configuration files reside. /var/yp/domain/ypservers.{dir, pag} Map containing list of NIS servers to bind to when running in server mode. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ |ATTRIBUTE TYPE |ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWypu | +-----------------------------+-----------------------------+ SEE ALSO
ypserv(1M), ypxfr(1M), ypfiles(4), attributes(5) NOTES
The Network Information Service (NIS) was formerly known as Sun Yellow Pages (YP). The functionality of the two remains the same; only the name has changed. The name Yellow Pages is a registered trademark in the United Kingdom of British Telecommunications PLC, and must not be used without permission. BUGS
In the current implementation (version 2 NIS protocol), the transfer agent is ypxfr(1M), which is started by the ypserv program. If yppush detects that it is speaking to a version 1 NIS protocol server, it uses the older protocol, sending a version 1 YPPROC_GET request and issues a message to that effect. Unfortunately, there is no way of knowing if or when the map transfer is performed for version 1 servers. yppush prints a message saying that an "old-style" message has been sent. The system administrator should later check to see that the transfer has actually taken place. SunOS 5.10 26 Aug 1999 yppush(1M)