1YPPUSH(8) Reference Manual YPPUSH(8)
2
6 yppush - force propagation of changed NIS databases
7
9 /usr/sbin/yppush [ -d domain ] [ -t timeout ] [ --parallel # | --port
10 port ] [ -h host ] [ -v ] mapname ...
11
13 yppush copies updated NIS databases (or maps) from the master NIS
14 server to the slave servers within a NIS domain. It is normally run
15 only on the NIS master by /var/yp/Makefile after the master databases
16 are changed. /var/yp/Makefile does not invoke yppush by default, the
17 NOPUSH=true line must be commented out.
18 yppush first constructs a list of NIS slave servers by reading the NIS
19 map ypservers within the domain. A destination host (or a list of
20 hosts with multiple -h commands) can also be specified on the command
21 line. A "transfer map" request is sent to the NIS serger at each
22 slave, along with the information needed by the transfer agent ypxfr(8)
23 to callback to yppush, which may be printed the result to stderr. Mes‐
24 sages are also printed when a transfer is not possible; for instance
25 when the request message is undeliverable.
26 To specify a port number or to use any other yppush options you can
28 edit /var/yp/Makefile directly.
29
32 -d domain
33 Specify a particular domain. The NIS domain of the local host
34 system is used by default. If the local host's domain name is
35 not set, the domain name must be specified with this flag.
36 -t timeout
38 The timeout flag is used to specify a timeout value in seconds.
39 This timeout controls how long yppush will wait for a response
40 from a slave server before sending a map transfer request to the
41 next slave server in the list. By default, yppush will wait 90
42 seconds. For big maps, this is not long enough.
43 --parallel #, -p #
45 yppush normally performs transfers serially, meaning that it
46 will send a map transfer request to one slave server and then
47 wait for it to respond before sending the next map transfer
48 request to the next slave server. In environments with many
49 slaves, it is more efficient to initiate several map transfers
50 at once so that the transfers can take place in parallel. It is
51 not possible to run in parallel and assign a fixed port with the
52 --port flag
53 --port port
55 specify a port for yppush to listen on. By default, yppush
56 will ask portmap(8) to assign it a random port number. It is
57 not possible to assign a port with this option and run in paral‐
58 lel with the --parallel or -p flag
59 -h host
61 The host flag can be used to transfer a map to a user-specified
62 machine or group of machines instead of the list of servers con‐
63 tained in the ypservers map. A list of hosts can be specified by
64 using multiple instances of the -h flag.
65 -v Verbose mode: causes yppush to print debugging messages as it
67 runs. Note specifying this flag twice makes yppush even more
68 verbose.
69
71 domainname(1), ypserv(8), ypxfr(8)
72
74 The mechanism for transferring NIS maps in NIS v1 is different that
75 that in NIS version 2. This version of yppush has support for transfer‐
76 ring maps to NIS v2 systems only.
77
79 Thorsten Kukuk <kukuk@suse.de>
80YP Server August 2002 YPPUSH(8)