1 .\" Copyright (c) 1995, 1996
2 .\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
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 Bill Paul.
15 .\" 4. Neither the name of the author nor the names of contributors
16 .\" may be used to endorse or promote products derived from this software
17 .\" without specific prior written permission.
19 .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
20 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR CONTRIBUTORS BE LIABLE
23 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
24 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
25 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
26 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
27 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
28 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
38 .Nd "NIS map transfer server"
45 utility is used to speed up the distribution of very large NIS maps
46 from NIS master to NIS slave servers.
47 The normal method for transfering
48 maps involves several steps:
49 .Bl -bullet -offset indent
51 The master server calls
53 to inform the slave servers to start a transfer.
55 The slave servers invoke
57 which reads the entire contents of a map from the master server
58 using the yp_all() function.
62 program then creates a new map database file by using the
64 library hash method to store the data that it receives from the server.
66 When all the data has been retrieved,
68 moves the new file into place and sends
70 on the local machine a YPPROC_CLEAR to tell it to refresh its
74 This process can take several minutes when there are very large
76 For example: a passwd database with several tens of
77 thousands of entries can consume several megabytes of disk space,
80 library package a long time to sort and store all the records
82 Consider also that there are two sets of map
84 .Pa master.passwd.by{name,uid}
86 .Pa passwd.by{name,uid} .
90 utility speeds up the transfer process by allowing NIS slave servers to
91 simply copy the master server's map files rather than building their
95 implements an RPC-based file transfer protocol.
97 a multi-megabyte file in this fashion takes only a few seconds compared
98 to the several minutes it would take even a reasonably fast slave server
99 to build a new map from scratch.
103 utility uses the same access restriction mechanism as
105 This means that slave servers will only be permitted to transfer
106 files if the rules in the
109 Furthermore, only slave servers using reserved
110 ports will be allowed to transfer the
114 The following option is available:
115 .Bl -tag -width indent
117 This option can be used to override the default path to
118 the location of the NIS
120 The compiled-in default path is
124 .Bl -tag -width Pa -compact
125 .It Pa /var/yp/[domainname]/[maps]
126 The NIS maps for a particular NIS domain.
137 protocol is not compatible with that used by SunOS.
139 but unavoidable: Sun's protocol is not freely available, and even if it
140 were it would probably not be useful since the SunOS NIS v2 implementation
141 uses the original ndbm package for its map databases whereas the
143 implementation uses Berkeley DB.
144 These two packages use vastly different
146 Furthermore, ndbm is byte-order sensitive and not very
147 smart about it, meaning that am ndbm database created on a big endian
148 system can't be read on a little endian system.
150 .An Bill Paul Aq wpaul@ctr.columbia.edu