Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

yppush(1m) [hpux man page]

yppush(1M)																yppush(1M)

NAME
yppush - force propagation of Network Information Service database SYNOPSIS
domain] host] maxm] mint] mapname Remarks The Network Information Service (NIS) was formerly known as Yellow Pages (YP). Although the name has changed, the functionality of the service remains the same. DESCRIPTION
copies a Network Information Service (NIS) map (database), mapname, from the map's master NIS server to each slave NIS server. It is usu- ally executed only on the master NIS server by shell script which is run either after changes are made to one or more of the master's NIS databases or when the NIS databases are first created. See ypmake(1M) and ypinit(1M) for more information on these processes. constructs a list of NIS server host names by reading the NIS map within the domain. Keys within the map are the host names of the machines on which the NIS servers run. then sends a "transfer map" request 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 When the transfer attempt is complete, whether successful or not, and the transfer agent sends a status message, the results can be printed to standard output. Messages are printed when a transfer is not possible, such as when the request message is undeliverable or when the timeout period on responses expires. Refer to ypfiles(4) and ypserv(1M) for an overview of Network Information Service. Options recognizes the following options: Copy mapname to the NIS servers in domain rather than to the domain returned by (see domainname(1)). Propagate the map(s) only to the specified host. Attempt to run maxm transfers in parallel to as many servers simultaneously. Without the option, attempts to transfer a map to each server, one at a time. When a network has many servers, such serial transfers can result in long delays to complete all transfers. A maxm value greater than 1 reduces total transfer time through better utilization of CPU time at the mas- ter. maxm can be any value from 1 through the number of NIS servers in the domain. Set the minimum timeout value to mint seconds. When transferring to one slave at a time, waits up to 80 seconds for the transfer to complete, after which it begins transferring to the next slave. When multiple parallel transfers are attempted by use of the option, it may be necessary to set the transfer timeout limit to a value larger than the default 80 seconds to prevent timeouts caused by network delays related to parallel transfers. Verbose mode: messages are printed when each server is called and when each response is received. If this option is omitted, only error messages are printed. WARNINGS
In the current implementation (Version 2 NIS protocol), the transfer agent is ypxfr(1M) which is started by the ypserv(1M) program at yppush's request (see ypxfr(1M) and ypserv(1M)). Starting with ONCplus version B.11.31.02, the NIS Version 1 protocol is no longer available. AUTHOR
was developed by Sun Microsystems, Inc. FILES
SEE ALSO domainname(1), ypserv(1M), ypxfr(1M), ypfiles(4). yppush(1M)

Check Out this Related Man Page

yppush(8)						      System Manager's Manual							 yppush(8)

NAME
yppush - force propagation of a changed Network Information Service (NIS) map SYNOPSIS
yppush [-d domain] [-v] mapname OPTIONS
Specify a domain. Verbose. This causes messages to be printed when each server is called, and for each response. Without this option, only error messages are printed. DESCRIPTION
The yppush command 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 make utility accessing the /var/yp/Makefile after the master NIS databases have been changed. When invoked, yppush first constructs a list of NIS server hosts by reading the NIS map ypservers within the domain. Keys within the map ypservers 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 which actually moves the map) to call back the yppush command. 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(8) for an overview of NIS. RESTRICTIONS
In the current implementation (version 2 NIS protocol), the transfer agent is ypxfr, 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 was performed for version 1 servers. The yppush command 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. ERRORS
Map xxx no such map in server's domain -- using ypservers Explanation: This is an informational message that indicates that the yppush command will push the maps to all servers listed in the ypservers map. FILES
SEE ALSO
Commands: ypserv(8), ypxfr(8) Files: ypfiles(4) yppush(8)
Man Page