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