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