1
.TH YPPUSH 8 "August 2002" "YP Server" "Reference Manual"
3
yppush \- force propagation of changed NIS databases
33
copies updated NIS databases (or maps) from the master NIS server to
34
the slave servers within a NIS domain. It is normally run only on
36
.I @YPMAPDIR@/Makefile
37
after the master databases are changed.
38
.I @YPMAPDIR@/Makefile
43
line must be commented out.
46
first constructs a list of NIS slave servers by reading the NIS map
50
A destination host (or a list of hosts with multiple \-h commands)
51
can also be specified on the command line.
52
A "transfer map" request is sent to the NIS serger at each slave, along
53
with the information needed by the transfer agent ypxfr(8) to callback
54
to yppush, which may be printed the result to stderr. Messages are
55
also printed when a transfer is not possible; for instance when the request
56
message is undeliverable.
60
Specify a particular domain. The NIS domain of the local host system is
61
used by default. If the local host's domain name is not set, the domain
62
name must be specified with this flag.
65
The timeout flag is used to specify a timeout value in seconds. This timeout
68
will wait for a response from a slave server before sending a
69
map transfer request to the next slave server in the list.
72
will wait 90 seconds. For big maps, this is not long enough.
74
.BI \-\^\-parallel " #" "\fR,\fP \-p " #
76
normally performs transfers serially, meaning that it will
77
send a map transfer request to one slave server and then wait for
78
it to respond before sending the next map transfer request to the
79
next slave server. In environments with many slaves, it is more
80
efficient to initiate several map transfers at once so that the
81
transfers can take place in parallel.
82
It is not possible to run in parallel and assign a fixed port with
90
to listen on. By default,
94
to assign it a random port number.
95
It is not possible to assign a port with this option and run in parallel with
103
The host flag can be used to transfer a map to a user-specified machine or
104
group of machines instead of the list of servers contained in
107
map. A list of hosts can be specified by using multiple
115
to print debugging messages as it runs. Note specifying this flag twice
126
The mechanism for transferring NIS maps in NIS v1 is different
127
that that in NIS version 2. This version of
129
has support for transferring maps to NIS v2 systems only.
132
Thorsten Kukuk <kukuk@suse.de>