1 .\" Copyright (c) 1992, 1993
2 .\" The Regents of the University of California. 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. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
33 .Nd defines network groups
40 specifies ``netgroups'', which are sets of
41 .Sy (host, user, domain)
42 tuples that are to be given similar network access.
45 consists of a netgroup name followed by a list of the members of the
47 Each member can be either the name of another netgroup or a specification
48 of a tuple as follows:
49 .Bd -literal -offset indent
58 are character string names for the corresponding component.
59 Any of the comma separated fields may be empty to specify a ``wildcard'' value
60 or may consist of the string ``-'' to specify ``no valid value''.
61 The members of the list may be separated by whitespace and/or commas;
62 the ``\e'' character may be used at the end of a line to specify
64 Lines are limited to 1024 characters.
65 The functions specified in
67 should normally be used to access the
71 Lines that begin with a # are treated as comments.
72 .Sh NIS/YP INTERACTION
73 On most other platforms,
75 are only used in conjunction with
83 can be used with either
85 or local files, but there are certain
89 system is extremely inefficient where
91 lookups are concerned since
93 memberships are computed on the fly.
97 database consists of three separate maps (netgroup, netgroup.byuser
98 and netgroup.byhost) that are keyed to allow
100 lookups to be done quickly.
104 system can interact with the
107 maps in the following ways:
108 .Bl -bullet -offset indent
112 file does not exist, or it exists and is empty, or
113 it exists and contains only a
119 lookups will be done exclusively through
123 taking advantage of the netgroup.byuser and
124 netgroup.byhost maps to speed up searches.
126 is more or less compatible with the behavior of SunOS and
131 exists and contains only local
136 token), then only the local
138 information will be processed (and
144 exists and contains both local netgroup data
149 token, the local data and the
152 map will be processed as a single combined
155 While this configuration is the most flexible, it
156 is also the least efficient: in particular,
158 lookups will be especially slow if the
162 .Bl -tag -width /etc/netgroup -compact
164 the netgroup database
167 The file format is compatible with that of various vendors, however it
168 appears that not all vendors use an identical format.
173 The interpretation of access restrictions based on the member tuples of a
174 netgroup is left up to the various network applications.
175 Also, it is not obvious how the domain specification
182 database should be stored in the form of a
185 database just like the
187 database to speed up reverse lookups.