1YPPUSH(8)                    NIS Reference Manual                    YPPUSH(8)
2
3
4

NAME

6       yppush - force propagation of changed NIS databases
7

SYNOPSIS

9       /usr/sbin/yppush [-d domain] [-t timeout] [--parallel # | --port port]
10                        [-h host] [-v] mapname...
11

DESCRIPTION

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 serger 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

OPTIONS

29       -d domain
30           Specify a particular domain. The NIS domain of the local host
31           system is used by default. If the local host´s domain name is not
32           set, the domain name must be specified with this flag.
33
34       -t timeout
35           The timeout flag is used to specify a timeout value in seconds.
36           This timeout controls how long yppush will wait for a response from
37           a slave server before sending a map transfer request to the next
38           slave server in the list. By default, yppush will wait 90 seconds.
39           For big maps, this is not long enough.
40
41       --parallel #, -p #
42           yppush normally performs transfers serially, meaning that it will
43           send a map transfer request to one slave server and then wait for
44           it to respond before sending the next map transfer request to the
45           next slave server. In environments with many slaves, it is more
46           efficient to initiate several map transfers at once so that the
47           transfers can take place in parallel. It is not possible to run in
48           parallel and assign a fixed port with the --port flag
49
50       --port port
51           specify a port for yppush to listen on. By default, yppush will ask
52           portmap(8) to assign it a random port number. It is not possible to
53           assign a port with this option and run in parallel with the
54           --parallel or -p flag
55
56       -h host
57           The host flag can be used to transfer a map to a user-specified
58           machine or group of machines instead of the list of servers
59           contained in the ypservers map. A list of hosts can be specified by
60           using multiple instances of the -h flag.
61
62       -v
63           Verbose mode: causes yppush to print debugging messages as it runs.
64           Note specifying this flag twice makes yppush even more verbose.
65

SEE ALSO

67       domainname(1), ypserv(8), ypxfr(8)
68

BUGS

70       The mechanism for transferring NIS maps in NIS v1 is different that
71       that in NIS version 2. This version of yppush has support for
72       transferring maps to NIS v2 systems only.
73

AUTHOR

75       Thorsten Kukuk <kukuk@linux-nis.org>
76
77
78
79NIS Reference Manual              06/12/2009                         YPPUSH(8)
Impressum