yppush(NADM)
yppush --
force propagation of a changed NIS map
Syntax
yppush [ -d domain ]
[ -v ] 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 make in /etc/yp after the master
databases are changed. It first constructs a list of
NIS server hosts by reading the NIS map
ypservers within the domain 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.
When the attempt has completed (successfully or not) and
the transfer agent has sent yppush a status
message, the results may 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(NF)
and
ypserv(NADM)
for an overview of the Network Information Service.
Options
-d-
specify a domain
-v-
verbose. This causes messages to be printed when each
server is called and for each response. If this flag is
omitted, only error messages are printed.
Limitations
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
(by 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 check later to see that the
transfer has actually taken place.
Files
/etc/yp/domainname/ypservers.{dir, pag}
See also
ypfiles(NF),
ypmapxlate(NF),
ypserv(NADM),
ypxfr(NADM)
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 02 June 2005