1996-04-28 04:16:06 +00:00
|
|
|
.\" Copyright (c) 1995, 1996
|
|
|
|
.\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
|
|
|
|
.\"
|
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
.\" are met:
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
|
|
.\" 3. All advertising materials mentioning features or use of this software
|
|
|
|
.\" must display the following acknowledgement:
|
|
|
|
.\" This product includes software developed by Bill Paul
|
|
|
|
.\" 4. Neither the name of the University nor the names of its contributors
|
|
|
|
.\" may be used to endorse or promote products derived from this software
|
|
|
|
.\" without specific prior written permission.
|
|
|
|
.\"
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR CONTRIBUTORS BE LIABLE
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
.\"
|
1999-08-28 01:35:59 +00:00
|
|
|
.\" $FreeBSD$
|
1996-04-28 04:16:06 +00:00
|
|
|
.\"
|
|
|
|
.Dd March 12, 1996
|
|
|
|
.Dt YP_MKDB 8
|
|
|
|
.Os
|
|
|
|
.Sh NAME
|
|
|
|
.Nm yp_mkdb
|
|
|
|
.Nd "generate the NIS databases"
|
|
|
|
.Sh SYNOPSIS
|
|
|
|
.Nm yp_mkdb
|
|
|
|
.Fl c
|
|
|
|
.Nm yp_mkdb
|
|
|
|
.Fl u Ar dbname
|
|
|
|
.Nm yp_mkdb
|
|
|
|
.Op Fl c
|
1996-10-24 14:52:50 +00:00
|
|
|
.Op Fl b
|
|
|
|
.Op Fl s
|
1999-08-22 15:34:47 +00:00
|
|
|
.Op Fl f
|
1996-04-28 04:16:06 +00:00
|
|
|
.Op Fl i Ar inputfile
|
|
|
|
.Op Fl o Ar outputfile
|
1997-10-27 12:29:25 +00:00
|
|
|
.Op Fl d Ar domainname
|
1996-04-28 04:16:06 +00:00
|
|
|
.Op Fl m Ar mastername
|
|
|
|
.Ar inputfile
|
|
|
|
.Ar dbname
|
|
|
|
.Sh DESCRIPTION
|
1997-10-27 12:29:25 +00:00
|
|
|
.Nm Yp_mkdb
|
1996-04-28 04:16:06 +00:00
|
|
|
creates
|
|
|
|
.Xr db 3
|
|
|
|
style databases for use with FreeBSD's NIS server.
|
1997-10-27 12:29:25 +00:00
|
|
|
.Nm Yp_mkdb
|
1996-04-28 04:16:06 +00:00
|
|
|
reads data from
|
1997-10-27 12:29:25 +00:00
|
|
|
.Ar inputfile ,
|
1996-04-28 04:16:06 +00:00
|
|
|
and writes it to
|
1997-10-27 12:29:25 +00:00
|
|
|
.Ar dbname
|
1996-04-28 04:16:06 +00:00
|
|
|
in
|
|
|
|
.Xr db 3
|
|
|
|
format (using the hash table method).
|
|
|
|
The input should be in 'key data' format, which is to say
|
1997-10-27 12:29:25 +00:00
|
|
|
two fields of
|
|
|
|
.Tn ASCII
|
|
|
|
data separated by white space. The first field
|
1996-04-28 04:16:06 +00:00
|
|
|
is assumed to be the key, and everything else is assumed to be
|
|
|
|
the data.
|
|
|
|
These databases are typically stored in
|
1997-10-27 12:29:25 +00:00
|
|
|
.Pa /var/yp/[domainname]
|
1996-04-28 04:16:06 +00:00
|
|
|
where
|
1997-10-27 12:29:25 +00:00
|
|
|
.Ar domainname
|
1996-04-28 04:16:06 +00:00
|
|
|
is the name of the NIS domain being served.
|
1997-10-27 12:29:25 +00:00
|
|
|
.Nm Yp_mkdb
|
1996-04-28 04:16:06 +00:00
|
|
|
is usually invoked by
|
1997-10-27 12:29:25 +00:00
|
|
|
.Pa /var/yp/Makefile .
|
|
|
|
.Nm Yp_mkdb
|
1996-04-28 04:16:06 +00:00
|
|
|
can also be used to dump an NIS database file so that its
|
|
|
|
contents can be examined. For security reasons, all databases that
|
1997-10-27 12:29:25 +00:00
|
|
|
.Nm
|
1996-04-28 04:16:06 +00:00
|
|
|
creates are readable and writable by owner only (and usually the
|
|
|
|
owner is root).
|
2000-01-23 20:32:24 +00:00
|
|
|
.Pp
|
|
|
|
The following options are available:
|
1997-10-27 12:29:25 +00:00
|
|
|
.Bl -tag -width indent
|
1996-04-28 04:16:06 +00:00
|
|
|
.It Fl c
|
1997-10-27 12:29:25 +00:00
|
|
|
Cause
|
|
|
|
.Nm
|
1996-04-28 04:16:06 +00:00
|
|
|
to send a YPPROC_CLEAR request to
|
|
|
|
.Xr ypserv 8
|
|
|
|
on the local host. This signal tells the server to close any open
|
|
|
|
database descriptors and flush out its database cache. If used alone,
|
|
|
|
this flag signals the server and does nothing else. If used as part
|
|
|
|
of a database creation command,
|
1997-10-27 12:29:25 +00:00
|
|
|
.Nm
|
1996-04-28 04:16:06 +00:00
|
|
|
will send the signal only after the new database has been successfully
|
|
|
|
created.
|
1996-10-24 14:52:50 +00:00
|
|
|
.It Fl b
|
2000-01-23 20:32:24 +00:00
|
|
|
Cause
|
1997-10-27 12:29:25 +00:00
|
|
|
.Nm
|
1996-10-24 14:52:50 +00:00
|
|
|
to add a special entry to the database with a key of
|
|
|
|
.Em YP_INTERDOMAIN
|
|
|
|
and an empty data field. If this key is present in a map, it alters the
|
|
|
|
behavior of the 'match' procedure in
|
|
|
|
.Xr ypserv 8
|
|
|
|
slightly. If a match query fails (because the server couldn't find
|
|
|
|
a record that matched the supplied key), and the
|
|
|
|
.Em YP_INTERDOMAIN
|
1997-04-15 07:06:15 +00:00
|
|
|
key exists within the queried map,
|
1996-10-24 14:52:50 +00:00
|
|
|
.Xr ypserv 8
|
|
|
|
will try to match the entry again using a DNS lookup. Note that this
|
|
|
|
special behavior only applies to the
|
|
|
|
.Em hosts
|
|
|
|
maps. Using the
|
|
|
|
.Fl b
|
|
|
|
flag for other maps has no effect.
|
|
|
|
.It Fl s
|
|
|
|
This flag is used to add a special entry to the database with a key of
|
|
|
|
.Em YP_SECURE
|
|
|
|
and an empty data field. If this key is present in a map,
|
|
|
|
.Xr ypserv 8
|
|
|
|
will deny access to the map to any client that is not using a
|
|
|
|
reserved port for its query. This is used mainly for the
|
|
|
|
.Em master.passwd
|
|
|
|
maps, which should be restricted to privileged access only.
|
1999-08-22 15:34:47 +00:00
|
|
|
.It Fl f
|
|
|
|
This flag is used to turn on filtering of lines in the source file
|
|
|
|
input that start with ``+'' or ``-'' characters. These characters
|
|
|
|
have special meaning for the
|
|
|
|
.Pa group ,
|
|
|
|
.Pa passwd
|
|
|
|
and
|
|
|
|
.Pa master.passwd
|
|
|
|
maps and hence should not be allowed to appear in them as the first
|
|
|
|
character of a key or datum. If the
|
|
|
|
.Fl f
|
|
|
|
flag is used,
|
|
|
|
.Nm
|
|
|
|
will reject any source line that starts with a ``+'' or ``-''
|
|
|
|
character and issue a warning message displaying the line that
|
|
|
|
was dropped.
|
1996-04-28 04:16:06 +00:00
|
|
|
.It Fl u Ar dbname
|
|
|
|
Dump (or 'unwind') an NIS database. This option can be used to
|
|
|
|
inspect the contents of an existing NIS database.
|
1997-10-27 12:29:25 +00:00
|
|
|
.It Fl i Ar inputfile
|
1996-04-28 04:16:06 +00:00
|
|
|
When generating an NIS map, encode
|
1997-10-27 12:29:25 +00:00
|
|
|
.Ar inputfile
|
1996-10-24 14:52:50 +00:00
|
|
|
as a special entry in the database with a key of
|
1997-04-15 07:06:15 +00:00
|
|
|
.Em YP_INPUT_FILE .
|
1997-10-27 12:29:25 +00:00
|
|
|
.It Fl o Ar outputfile
|
1996-04-28 04:16:06 +00:00
|
|
|
When generating an NIS map, encode
|
1997-10-27 12:29:25 +00:00
|
|
|
.Ar outputfile
|
1996-10-24 14:52:50 +00:00
|
|
|
as a special entry in the database with a key of
|
|
|
|
.Em YP_OUTPUT_FILE .
|
1997-10-27 12:29:25 +00:00
|
|
|
.It Fl d Ar domainname
|
|
|
|
When generating an NIS map, encode
|
|
|
|
.Ar domainname
|
|
|
|
as a special entry in the database with a key of
|
|
|
|
.Em YP_DOMAIN_NAME .
|
|
|
|
.It Fl m Ar mastername
|
|
|
|
When generating an NIS map, encode
|
|
|
|
.Ar mastername
|
1996-10-24 14:52:50 +00:00
|
|
|
as a special entry in the database with a key of
|
|
|
|
.Em YP_MASTER_NAME .
|
1996-04-28 04:16:06 +00:00
|
|
|
This entry in the database is frequently used by various NIS utilities
|
|
|
|
to determine the name of an NIS master server for a domain. By default,
|
1997-10-27 12:29:25 +00:00
|
|
|
.Nm
|
1996-04-28 04:16:06 +00:00
|
|
|
assumes that the local host is the NIS master; the
|
1997-10-27 12:29:25 +00:00
|
|
|
.Fl m
|
1996-04-28 04:16:06 +00:00
|
|
|
option is used to override this default.
|
|
|
|
.Sh FILES
|
1997-10-27 12:29:25 +00:00
|
|
|
.Bl -tag -width /var/yp/Makefile -compact
|
1996-04-28 04:16:06 +00:00
|
|
|
.It Pa /var/yp/Makefile
|
1997-10-27 12:29:25 +00:00
|
|
|
the Makefile that calls
|
|
|
|
.Nm
|
|
|
|
to build the NIS databases
|
1996-04-28 04:16:06 +00:00
|
|
|
.Sh SEE ALSO
|
1997-01-20 00:03:00 +00:00
|
|
|
.Xr db 3 ,
|
|
|
|
.Xr ypserv 8
|
1998-03-23 08:31:20 +00:00
|
|
|
.Sh AUTHORS
|
1997-10-27 12:29:25 +00:00
|
|
|
.An Bill Paul Aq wpaul@ctr.columbia.edu
|