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