1 '\" te
2 .\" Copyright (C) 2004, Sun Microsystems, Inc. All Rights Reserved.
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH YPSERV 1M "Dec 15, 2004"
7 .SH NAME
8 ypserv, ypxfrd \- NIS server and binder processes
9 .SH SYNOPSIS
10 .LP
11 .nf
12 \fB/usr/lib/netsvc/yp/ypserv\fR [\fB-dv\fR] [\fB-i\fR | \fB-I\fR] [\fB-r\fR | \fB-R\fR]
13 .fi
14
15 .LP
16 .nf
17 \fB/usr/lib/netsvc/yp/ypxfrd\fR
18 .fi
19
20 .SH DESCRIPTION
21 .sp
22 .LP
23 The Network Information Service (\fBNIS\fR) provides a simple network lookup
24 service consisting of databases and processes. The databases are \fBndbm\fR
25 files in a directory tree rooted at \fB/var/yp\fR. See \fBndbm\fR(3C). These
26 files are described in \fBypfiles\fR(4). The processes are
27 \fB/usr/lib/netsvc/yp/ypserv\fR, the \fBNIS\fR database lookup server, and
28 \fB/usr/lib/netsvc/yp/ypbind\fR, the \fBNIS\fR binder. The programmatic
29 interface to the \fBNIS\fR service is described in \fBypclnt\fR(3NSL).
30 Administrative tools are described in \fByppoll\fR(1M), \fByppush\fR(1M),
31 \fBypset\fR(1M), \fBypxfr\fR(1M), and \fBypwhich\fR(1). Tools to see the
32 contents of \fBNIS\fR maps are described in \fBypcat\fR(1), and
33 \fBypmatch\fR(1). Database generation and maintenance tools are described in
34 \fBypinit\fR(1M), \fBypmake\fR(1M), and \fBmakedbm\fR(1M).
35 .sp
36 .LP
37 The \fBypserv\fR utility is a daemon process typically activated at system
38 startup from \fBsvc:/network/nis/server:default\fR. Alternatively, you can, as
39 the root user, start \fBNIS\fR services using \fBypstart\fR(1M) from the
40 command-line. \fBypserv\fR runs only on \fBNIS\fR server machines with a
41 complete \fBNIS\fR database. You can halt all \fBNIS\fR services using the
42 \fBypstop\fR(1M) command.
150 When a NIS read access is made and the TTL entry has expired, a warning is
151 logged.Information that is returned from the cache has not been updated.
152 .RE
153 .RS +4
154 .TP
155 3.
156 When a NIS write access is made, a warning is logged. The cache will not be
157 updated, and a NIS failure will be returned.
158 .RE
159 .sp
160 .LP
161 If \fBypxfrd\fR is running in N2L mode and is asked to transfer a map,
162 \fBypxfrd\fR first checks whether the map is out of date. If the map is out of
163 date, \fBypxfrd\fR initiates an update from the DIT. \fBypxfrd\fR cannot wait
164 for the update to complete. If \fBypxfrd\fR waited, the client end \fBypxfr\fR
165 operation could time out. To prevent \fBypxfrd\fR from timing out, the existing
166 map is transferred from the cache. The most up to date map will be transferred
167 on subsequent \fBypxfrd\fR operations.
168 .SH OPTIONS
169 .SS "ypserv"
170 .sp
171 .ne 2
172 .na
173 \fB\fB-d\fR\fR
174 .ad
175 .RS 7n
176 The \fBNIS\fR service should go to the \fBDNS\fR for more host information.
177 This requires the existence of a correct \fB/etc/resolv.conf\fR file pointing
178 to a \fBDNS\fR server. This option turns on \fBDNS\fR forwarding regardless of
179 whether or not the \fBYP_INTERDOMAIN\fR flag is set in the \fBhosts\fR maps.
180 See \fBmakedbm\fR(1M). In the absence of an \fB/etc/resolv.conf\fR file,
181 \fBypserv\fR complains, but ignores the \fB-d\fR option.
182 .RE
183
184 .sp
185 .ne 2
186 .na
187 \fB\fB-i\fR\fR
188 .ad
189 .RS 7n
190 If in N2L mode, initialize the NIS related parts of the \fBDIT\fR based on the
250 .RE
251
252 .sp
253 .LP
254 When run with the \fB-i\fR, \fB-r\fR, \fB-I\fR, \fB-ir\fR or \fB-Ir\fR options,
255 the \fBypserv\fR command runs in the foreground and exits once map
256 initialization has been completed. Once the \fBypserv\fR command exits, the
257 user knows the maps are ready and can restart \fBypserv\fR and the other
258 \fByp\fR daemons by running \fBypstart\fR(1M).
259 .sp
260 .LP
261 If there is a requirement to initialize the \fBDIT\fR from the NIS source
262 files, which may have been modified since the maps were last remade, run
263 \fBypmake\fR before running \fBypserv\fR \fB-i\fR or \fBypserv\fR \fB-ir\fR.
264 \fBypmake\fR regenerated old style NIS maps. Then \fBypserv\fR \fB-ir\fR dumps
265 them into the \fBDIT\fR. When the \fB-ir\fR option is used, the \fBLDAP_\fR
266 prefixe maps are also generated or updated. Since these maps will be more
267 recent than the old style maps, \fBypmake\fR will not be reported as erroneous
268 when it is run.
269 .SH FILES
270 .sp
271 .ne 2
272 .na
273 \fB\fB/var/yp/securenets\fR\fR
274 .ad
275 .sp .6
276 .RS 4n
277 Defines the hosts and networks that are granted access to information in the
278 served domain. It is read at startup time by both \fBypserv\fR and
279 \fBypxfrd\fR.
280 .RE
281
282 .sp
283 .ne 2
284 .na
285 \fB\fB/var/yp/ypserv.log\fR\fR
286 .ad
287 .sp .6
288 .RS 4n
289 If the \fB/var/yp/ypserv.log\fR file exists when \fBypserv\fR starts up, log
290 information is written to it when error conditions arise.
291 .RE
292
293 .sp
294 .ne 2
295 .na
296 \fB\fB/var/yp/binding/domainname/ypservers\fR\fR
297 .ad
298 .sp .6
299 .RS 4n
300 Lists the \fBNIS\fR server hosts that \fBypbind\fR can bind to.
301 .RE
302
303 .SH SEE ALSO
304 .sp
305 .LP
306 \fBsvcs\fR(1), \fBypcat\fR(1), \fBypmatch\fR(1), \fBypwhich\fR(1),
307 \fBdomainname\fR(1M), \fBmakedbm\fR(1M), \fBsvcadm\fR(1M), \fBypbind\fR(1M),
308 \fBypinit\fR(1M), \fBypmake\fR(1M), \fByppoll\fR(1M), \fByppush\fR(1M),
309 \fBypset\fR(1M), \fBypstart\fR(1M), \fBypstop\fR(1M), \fBypxfr\fR(1M),
310 \fBndbm\fR(3C), \fBypclnt\fR(3NSL), \fBlibnsl\fR(3LIB),
311 \fBNISLDAPmapping\fR(4), \fBsecurenets\fR(4), \fBypfiles\fR(4),
312 \fBypserv\fR(4), \fBattributes\fR(5), \fBsmf\fR(5)
313 .sp
314 .LP
315
316 .sp
317 .LP
318 \fI\fR
319 .SH NOTES
320 .sp
321 .LP
322 \fBypserv\fR supports multiple domains. The \fBypserv\fR process determines the
323 domains it serves by looking for directories of the same name in the directory
324 \fB/var/yp\fR. It replies to all broadcasts requesting yp service for that
325 domain.
326 .sp
327 .LP
328 The Network Information Service (\fBNIS\fR) was formerly known as Sun Yellow
329 Pages (\fBYP\fR). The functionality of the two remains the same; only the name
330 has changed. The name Yellow Pages is a registered trademark in the United
331 Kingdom of British Telecommunications PLC, and must not be used without
332 permission.
333 .sp
334 .LP
335 \fBNIS\fR uses \fBndbm()\fR files to store maps. Therefore, it is subject to
336 the 1024 byte limitations described in the USAGE and NOTES sections of the
337 \fBndbm\fR(3C) man page.
338 .sp
339 .LP
340 The NIS server service is managed by the service management facility,
341 \fBsmf\fR(5), under the service identifier:
|
1 '\" te
2 .\" Copyright (C) 2004, Sun Microsystems, Inc. All Rights Reserved.
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH YPSERV 1M "Dec 15, 2004"
7 .SH NAME
8 ypserv, ypxfrd \- NIS server and binder processes
9 .SH SYNOPSIS
10 .nf
11 \fB/usr/lib/netsvc/yp/ypserv\fR [\fB-dv\fR] [\fB-i\fR | \fB-I\fR] [\fB-r\fR | \fB-R\fR]
12 .fi
13
14 .LP
15 .nf
16 \fB/usr/lib/netsvc/yp/ypxfrd\fR
17 .fi
18
19 .SH DESCRIPTION
20 The Network Information Service (\fBNIS\fR) provides a simple network lookup
21 service consisting of databases and processes. The databases are \fBndbm\fR
22 files in a directory tree rooted at \fB/var/yp\fR. See \fBndbm\fR(3C). These
23 files are described in \fBypfiles\fR(4). The processes are
24 \fB/usr/lib/netsvc/yp/ypserv\fR, the \fBNIS\fR database lookup server, and
25 \fB/usr/lib/netsvc/yp/ypbind\fR, the \fBNIS\fR binder. The programmatic
26 interface to the \fBNIS\fR service is described in \fBypclnt\fR(3NSL).
27 Administrative tools are described in \fByppoll\fR(1M), \fByppush\fR(1M),
28 \fBypset\fR(1M), \fBypxfr\fR(1M), and \fBypwhich\fR(1). Tools to see the
29 contents of \fBNIS\fR maps are described in \fBypcat\fR(1), and
30 \fBypmatch\fR(1). Database generation and maintenance tools are described in
31 \fBypinit\fR(1M), \fBypmake\fR(1M), and \fBmakedbm\fR(1M).
32 .sp
33 .LP
34 The \fBypserv\fR utility is a daemon process typically activated at system
35 startup from \fBsvc:/network/nis/server:default\fR. Alternatively, you can, as
36 the root user, start \fBNIS\fR services using \fBypstart\fR(1M) from the
37 command-line. \fBypserv\fR runs only on \fBNIS\fR server machines with a
38 complete \fBNIS\fR database. You can halt all \fBNIS\fR services using the
39 \fBypstop\fR(1M) command.
147 When a NIS read access is made and the TTL entry has expired, a warning is
148 logged.Information that is returned from the cache has not been updated.
149 .RE
150 .RS +4
151 .TP
152 3.
153 When a NIS write access is made, a warning is logged. The cache will not be
154 updated, and a NIS failure will be returned.
155 .RE
156 .sp
157 .LP
158 If \fBypxfrd\fR is running in N2L mode and is asked to transfer a map,
159 \fBypxfrd\fR first checks whether the map is out of date. If the map is out of
160 date, \fBypxfrd\fR initiates an update from the DIT. \fBypxfrd\fR cannot wait
161 for the update to complete. If \fBypxfrd\fR waited, the client end \fBypxfr\fR
162 operation could time out. To prevent \fBypxfrd\fR from timing out, the existing
163 map is transferred from the cache. The most up to date map will be transferred
164 on subsequent \fBypxfrd\fR operations.
165 .SH OPTIONS
166 .SS "ypserv"
167 .ne 2
168 .na
169 \fB\fB-d\fR\fR
170 .ad
171 .RS 7n
172 The \fBNIS\fR service should go to the \fBDNS\fR for more host information.
173 This requires the existence of a correct \fB/etc/resolv.conf\fR file pointing
174 to a \fBDNS\fR server. This option turns on \fBDNS\fR forwarding regardless of
175 whether or not the \fBYP_INTERDOMAIN\fR flag is set in the \fBhosts\fR maps.
176 See \fBmakedbm\fR(1M). In the absence of an \fB/etc/resolv.conf\fR file,
177 \fBypserv\fR complains, but ignores the \fB-d\fR option.
178 .RE
179
180 .sp
181 .ne 2
182 .na
183 \fB\fB-i\fR\fR
184 .ad
185 .RS 7n
186 If in N2L mode, initialize the NIS related parts of the \fBDIT\fR based on the
246 .RE
247
248 .sp
249 .LP
250 When run with the \fB-i\fR, \fB-r\fR, \fB-I\fR, \fB-ir\fR or \fB-Ir\fR options,
251 the \fBypserv\fR command runs in the foreground and exits once map
252 initialization has been completed. Once the \fBypserv\fR command exits, the
253 user knows the maps are ready and can restart \fBypserv\fR and the other
254 \fByp\fR daemons by running \fBypstart\fR(1M).
255 .sp
256 .LP
257 If there is a requirement to initialize the \fBDIT\fR from the NIS source
258 files, which may have been modified since the maps were last remade, run
259 \fBypmake\fR before running \fBypserv\fR \fB-i\fR or \fBypserv\fR \fB-ir\fR.
260 \fBypmake\fR regenerated old style NIS maps. Then \fBypserv\fR \fB-ir\fR dumps
261 them into the \fBDIT\fR. When the \fB-ir\fR option is used, the \fBLDAP_\fR
262 prefixe maps are also generated or updated. Since these maps will be more
263 recent than the old style maps, \fBypmake\fR will not be reported as erroneous
264 when it is run.
265 .SH FILES
266 .ne 2
267 .na
268 \fB\fB/var/yp/securenets\fR\fR
269 .ad
270 .sp .6
271 .RS 4n
272 Defines the hosts and networks that are granted access to information in the
273 served domain. It is read at startup time by both \fBypserv\fR and
274 \fBypxfrd\fR.
275 .RE
276
277 .sp
278 .ne 2
279 .na
280 \fB\fB/var/yp/ypserv.log\fR\fR
281 .ad
282 .sp .6
283 .RS 4n
284 If the \fB/var/yp/ypserv.log\fR file exists when \fBypserv\fR starts up, log
285 information is written to it when error conditions arise.
286 .RE
287
288 .sp
289 .ne 2
290 .na
291 \fB\fB/var/yp/binding/domainname/ypservers\fR\fR
292 .ad
293 .sp .6
294 .RS 4n
295 Lists the \fBNIS\fR server hosts that \fBypbind\fR can bind to.
296 .RE
297
298 .SH SEE ALSO
299 \fBsvcs\fR(1), \fBypcat\fR(1), \fBypmatch\fR(1), \fBypwhich\fR(1),
300 \fBdomainname\fR(1M), \fBmakedbm\fR(1M), \fBsvcadm\fR(1M), \fBypbind\fR(1M),
301 \fBypinit\fR(1M), \fBypmake\fR(1M), \fByppoll\fR(1M), \fByppush\fR(1M),
302 \fBypset\fR(1M), \fBypstart\fR(1M), \fBypstop\fR(1M), \fBypxfr\fR(1M),
303 \fBndbm\fR(3C), \fBypclnt\fR(3NSL), \fBlibnsl\fR(3LIB),
304 \fBNISLDAPmapping\fR(4), \fBsecurenets\fR(4), \fBypfiles\fR(4),
305 \fBypserv\fR(4), \fBattributes\fR(5), \fBsmf\fR(5)
306
307 .SH NOTES
308 \fBypserv\fR supports multiple domains. The \fBypserv\fR process determines the
309 domains it serves by looking for directories of the same name in the directory
310 \fB/var/yp\fR. It replies to all broadcasts requesting yp service for that
311 domain.
312 .sp
313 .LP
314 The Network Information Service (\fBNIS\fR) was formerly known as Sun Yellow
315 Pages (\fBYP\fR). The functionality of the two remains the same; only the name
316 has changed. The name Yellow Pages is a registered trademark in the United
317 Kingdom of British Telecommunications PLC, and must not be used without
318 permission.
319 .sp
320 .LP
321 \fBNIS\fR uses \fBndbm()\fR files to store maps. Therefore, it is subject to
322 the 1024 byte limitations described in the USAGE and NOTES sections of the
323 \fBndbm\fR(3C) man page.
324 .sp
325 .LP
326 The NIS server service is managed by the service management facility,
327 \fBsmf\fR(5), under the service identifier:
|