xref: /freebsd/usr.sbin/yppush/yppush.8 (revision 4cf49a43559ed9fdad601bdcccd2c55963008675)
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 yppush
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. It is normally only run on the NIS master by
55.Pa /var/yp/Makefile
56whenever any of the NIS maps are updated. Note that
57.Pa /var/yp/Makefile
58does not invoke
59.Nm
60by default: the
61.Nm NOPUSH=True
62entry in the Makefile must first be commented out
63(the default
64.Bx Free
65configuration assumes a small network with only
66a single NIS server; in such a configuration,
67.Nm
68is not needed).
69.Pp
70By default,
71.Nm
72determines the names of the slave servers for a domain by searching the
73.Pa ypservers
74map. A destination host (or a list of hosts) can also be manually
75specified on the command line.
76Once it has a complete list of slave servers, it sends a 'map transfer'
77request to each slave, which in turn reads a copy of the map from
78the master NIS server using
79.Xr ypxfr 8 .
80Included within each request is the name of the map to be copied
81and some special information required by
82.Xr ypxfr 8
83to successfully 'callback' to
84.Nm
85and carry out the transfer. Any error messages
86.Nm
87receives from
88.Xr ypxfr 8
89via callback will be printed to stderr.
90.Pp
91.Sh OPTIONS
92The following options are available:
93.Bl -tag -width indent
94.It Fl d Ar domain
95Specify a particular domain. The NIS domain of
96the local host system is used by default. If the local host's domain
97name is not set, the domain name must be specified with this flag.
98.It Fl t Ar timeout
99Specify a timeout value in seconds. This timeout
100controls how long
101.Nm
102will wait for a response from a slave server before sending a
103map transfer request to the next slave server in its list.
104.It Fl j Ar #parallel jobs
105.Nm Yppush
106normally performs transfers serially, meaning that it will
107send a map transfer request to one slave server and then wait for
108it to respond before moving on to the next slave server. In environments
109with many slaves, it is more efficient to initiate several map transfers
110at once so that the transfers can take place in parallel. The
111.Fl j
112flag is used to specify the desired number of parallel jobs:
113.Nm
114will initiate the specified number of transfers immediately and
115listen for responses. If the number of specified parallel jobs is
116less than the number of slave servers,
117.Nm
118will initiate only the number of specified jobs and then wait
119for some of them to finish before starting any more.
120.Pp
121Note that
122.Nm
123handles callbacks asynchronously, which means that it will collect
124and display the callback information received from
125.Xr ypxfr 8
126as soon as it arrives, even it arrives before all of the map
127transfer requests have been sent.
128.It Fl h Ar host
129Can be used to transfer a map to a user-specified machine or
130group of machines instead of the list of servers contained in
131the
132.Pa ypservers
133map. A list of hosts can be specified by using multiple
134instances of the
135.Fl h
136flag.
137.It Fl p Ar path
138By default,
139.Nm
140expects all the local NIS maps to be stored under
141.Pa /var/yp .
142The
143.Fl p
144flag can be used to specify an alternate path in the event that
145the system administrator decides to store the NIS maps somewhere else.
146.It Fl v
147Verbose mode: causes
148.Nm
149to print debugging messages as it runs. Specifying this flag twice
150makes
151.Nm
152even more verbose.
153.Sh FILES
154.Bl -tag -width Pa -compact
155.It Pa /var/yp/[domainname]/ypservers
156The NIS ypservers map containing the names of all servers in
157a particular NIS domain.
158.El
159.Sh SEE ALSO
160.Xr yp 4 ,
161.Xr ypserv 8 ,
162.Xr ypxfr 8
163.Sh BUGS
164The mechanism for transferring NIS maps in NIS v1 is different
165than that in NIS version 2. This version of
166.Nm
167has support for transferring maps to NIS v2 systems only.
168.Sh AUTHORS
169.An Bill Paul Aq wpaul@ctr.columbia.edu
170