yppush(1m) - osol9

1yppush(1M)              System Administration Commands              yppush(1M)
2
3
4

NAME

6       yppush - force propagation of changed NIS map
7

SYNOPSIS

9       /usr/lib/netsvc/yp/yppush [-v] [-h host] [-d domain]
10            [-p #parallel-xfrs] mapname
11
12

DESCRIPTION

14       yppush copies a new version of a  Network Information Service (NIS) map
15       from the master NIS server to the slave NIS servers. It is normally run
16       only on the master NIS server by the Makefile in /var/yp after the mas‐
17       ter databases are changed. It first constructs a  list  of  NIS  server
18       hosts  by  reading the NIS ypservers map within the domain. Keys within
19       the ypservers map are the ASCII names of the machines on which the  NIS
20       servers run.
21
22
23       A  "transfer map" request is sent to the NIS server at each host, along
24       with the information needed by the transfer  agent  (the  program  that
25       actually  moves  the map) to call back the yppush. When the attempt has
26       completed (successfully or not), and the transfer agent has sent yppush
27       a  status  message,  the results can be printed to stdout. Messages are
28       also printed when a transfer is not possible, for  instance,  when  the
29       request  message  is  undeliverable,  or  when  the  timeout  period on
30       responses has expired.
31
32
33       Refer to ypfiles(4) and ypserv(1M) for an overview of the NIS service.
34

OPTIONS

36       The following options are supported:
37
38       -d domain            Specifies a domain.
39
40
41       -h host              Propagates only to the named host.
42
43
44       -p #parallel-xfrs    Allows the specified number of  map  transfers  to
45                            occur in parallel.
46
47
48       -v                   Verbose.  This prints messages when each server is
49                            called, and for each response.  If  this  flag  is
50                            omitted, only error messages are printed.
51
52

FILES

54       /var/yp
55
56           Directory where NIS configuration files reside.
57
58
59       /var/yp/domain/ypservers.{dir, pag}
60
61           Map  containing  list  of   NIS  servers to bind to when running in
62           server mode.
63
64

ATTRIBUTES

66       See attributes(5) for descriptions of the following attributes:
67
68
69
70
71       ┌─────────────────────────────┬─────────────────────────────┐
72       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
73       ├─────────────────────────────┼─────────────────────────────┤
74       │Availability                 │SUNWypu                      │
75       └─────────────────────────────┴─────────────────────────────┘
76

NOTES

81       The Network Information Service (NIS) was formerly known as Sun  Yellow
82       Pages  (YP).  The  functionality  of the two remains the same; only the
83       name has changed. The name Yellow Pages is a  registered  trademark  in
84       the  United  Kingdom of British Telecommunications PLC, and must not be
85       used without permission.
86

BUGS

88       In the current implementation (version 2 NIS  protocol),  the  transfer
89       agent  is  ypxfr(1M), which is started by the ypserv program. If yppush
90       detects that it is speaking to a version 1 NIS protocol server, it uses
91       the older protocol, sending a version 1 YPPROC_GET request and issues a
92       message to that effect. Unfortunately, there is no way of knowing if or
93       when the map transfer is performed for version 1 servers. yppush prints
94       a message saying that an "old-style" message has been sent. The  system
95       administrator  should later check to see that the transfer has actually
96       taken place.
97
98
99
100SunOS 5.11                        26 Aug 1999                       yppush(1M)