1YPPUSH(8)                      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
10       port ] [ -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       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

OPTIONS

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

AUTHOR

75       Thorsten Kukuk <kukuk@suse.de>
76
77
78
79YP Server                         August 2002                        YPPUSH(8)
Impressum