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