yppush(1M) yppush(1M)
NAME [Toc] [Back]
yppush - force propagation of Network Information Service database
SYNOPSIS [Toc] [Back]
/usr/sbin/yppush [-d domain] [-m maxm] [-t mint] [-v] mapname
Remarks [Toc] [Back]
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 [Toc] [Back]
yppush copies a Network Information Service (NIS) map (database),
mapname, from the map's master NIS server to each slave NIS server.
It is usually executed only on the master NIS server by shell script
ypmake 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.
yppush constructs a list of NIS server host names by reading the NIS
map ypservers within the domain. Keys within the ypservers map are
the host names of the machines on which the NIS servers run. yppush
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 yppush.
When the transfer attempt is complete, whether successful or not, and
the transfer agent sends yppush 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 [Toc] [Back]
yppush recognizes the following options:
-d domain Copy mapname to the NIS servers in domain rather than
to the domain returned by domainname (see
domainname(1)).
-m maxm Attempt to run maxm transfers in parallel to as many
servers simultaneously. Without the -m option,
yppush 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 master. maxm can be
Hewlett-Packard Company - 1 - HP-UX 11i Version 2: August 2003
yppush(1M) yppush(1M)
any value from 1 through the number of NIS servers in
the domain.
-t mint Set the minimum timeout value to mint seconds. When
transferring to one slave at a time, yppush 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 -m 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.
-v 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 [Toc] [Back]
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)). If yppush detects it
is interacting with a Version 1 NIS protocol server, it uses the older
protocol to send 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
comment saying that a Version 1 message was sent. The system
administrator should then verify by other means that the transfer
actually occurred.
AUTHOR [Toc] [Back]
yppush was developed by Sun Microsystems, Inc.
FILES [Toc] [Back]
/usr/sbin/domain/ypservers.{dir, pag}
/usr/sbin/domain/mapname.{dir, pag}
SEE ALSO [Toc] [Back]
domainname(1), ypserv(1M), ypxfr(1M), ypfiles(4).
Hewlett-Packard Company - 2 - HP-UX 11i Version 2: August 2003 [ Back ] |