xref: /freebsd/usr.sbin/yppush/yppush.8 (revision 5521ff5a4d1929056e7ffc982fac3341ca54df7c)
1.\" Copyright (c) 1991, 1993, 1995
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" $FreeBSD$
33.\"
34.Dd February 5, 1995
35.Dt YPPUSH 8
36.Os
37.Sh NAME
38.Nm yppush
39.Nd "force propagation of updated NIS databases"
40.Sh SYNOPSIS
41.Nm
42.Op Fl d Ar domain
43.Op Fl t Ar timeout
44.Op Fl j Ar #parallel jobs
45.Op Fl h Ar host
46.Op Fl p Ar path
47.Op Fl v
48.Ar mapname
49.Sh DESCRIPTION
50.Nm Yppush
51distributes updated NIS databases (or
52.Pa maps )
53from an NIS master server to NIS slave servers within an NIS
54domain.
55It is normally only run on the NIS master by
56.Pa /var/yp/Makefile
57whenever any of the NIS maps are updated.
58Note that
59.Pa /var/yp/Makefile
60does not invoke
61.Nm
62by default: the
63.Dq Li NOPUSH=True
64entry in the Makefile must first be commented out
65(the default
66.Fx
67configuration assumes a small network with only
68a single NIS server; in such a configuration,
69.Nm
70is not needed).
71.Pp
72By default,
73.Nm
74determines the names of the slave servers for a domain by searching the
75.Pa ypservers
76map. A destination host (or a list of hosts) can also be manually
77specified on the command line.
78Once it has a complete list of slave servers, it sends a 'map transfer'
79request to each slave, which in turn reads a copy of the map from
80the master NIS server using
81.Xr ypxfr 8 .
82Included within each request is the name of the map to be copied
83and some special information required by
84.Xr ypxfr 8
85to successfully 'callback' to
86.Nm
87and carry out the transfer.
88Any error messages
89.Nm
90receives from
91.Xr ypxfr 8
92via callback will be printed to stderr.
93.Pp
94The following options are available:
95.Bl -tag -width indent
96.It Fl d Ar domain
97Specify a particular domain.
98The NIS domain of
99the local host system is used by default.
100If the local host's domain
101name is not set, the domain name must be specified with this flag.
102.It Fl t Ar timeout
103Specify a timeout value in seconds.
104This timeout
105controls how long
106.Nm
107will wait for a response from a slave server before sending a
108map transfer request to the next slave server in its list.
109.It Fl j Ar #parallel jobs
110.Nm Yppush
111normally performs transfers serially, meaning that it will
112send a map transfer request to one slave server and then wait for
113it to respond before moving on to the next slave server.
114In environments
115with many slaves, it is more efficient to initiate several map transfers
116at once so that the transfers can take place in parallel.
117The
118.Fl j
119flag is used to specify the desired number of parallel jobs:
120.Nm
121will initiate the specified number of transfers immediately and
122listen for responses.
123If the number of specified parallel jobs is
124less than the number of slave servers,
125.Nm
126will initiate only the number of specified jobs and then wait
127for some of them to finish before starting any more.
128.Pp
129Note that
130.Nm
131handles callbacks asynchronously, which means that it will collect
132and display the callback information received from
133.Xr ypxfr 8
134as soon as it arrives, even it arrives before all of the map
135transfer requests have been sent.
136.It Fl h Ar host
137Can be used to transfer a map to a user-specified machine or
138group of machines instead of the list of servers contained in
139the
140.Pa ypservers
141map. A list of hosts can be specified by using multiple
142instances of the
143.Fl h
144flag.
145.It Fl p Ar path
146By default,
147.Nm
148expects all the local NIS maps to be stored under
149.Pa /var/yp .
150The
151.Fl p
152flag can be used to specify an alternate path in the event that
153the system administrator decides to store the NIS maps somewhere else.
154.It Fl v
155Verbose mode: causes
156.Nm
157to print debugging messages as it runs.
158Specifying this flag twice
159makes
160.Nm
161even more verbose.
162.El
163.Sh FILES
164.Bl -tag -width Pa -compact
165.It Pa /var/yp/[domainname]/ypservers
166the NIS ypservers map containing the names of all servers in
167a particular NIS domain
168.El
169.Sh SEE ALSO
170.Xr yp 4 ,
171.Xr ypserv 8 ,
172.Xr ypxfr 8
173.Sh BUGS
174The mechanism for transferring NIS maps in NIS v1 is different
175than that in NIS version 2. This version of
176.Nm
177has support for transferring maps to NIS v2 systems only.
178.Sh AUTHORS
179.An Bill Paul Aq wpaul@ctr.columbia.edu
180