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 .\" 4. 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
28 .\" @(#)netgroup.5 8.2 (Berkeley) 12/11/93
36 .Nd defines network groups
43 specifies ``netgroups'', which are sets of
44 .Sy (host, user, domain)
45 tuples that are to be given similar network access.
48 consists of a netgroup name followed by a list of the members of the
50 Each member can be either the name of another netgroup or a specification
51 of a tuple as follows:
52 .Bd -literal -offset indent
61 are character string names for the corresponding component.
62 Any of the comma separated fields may be empty to specify a ``wildcard'' value
63 or may consist of the string ``-'' to specify ``no valid value''.
64 The members of the list may be separated by whitespace and/or commas;
65 the ``\e'' character may be used at the end of a line to specify
67 Lines are limited to 1024 characters.
68 The functions specified in
70 should normally be used to access the
74 Lines that begin with a # are treated as comments.
75 .Sh NIS/YP INTERACTION
76 On most other platforms,
78 are only used in conjunction with
86 can be used with either
88 or local files, but there are certain
92 system is extremely inefficient where
94 lookups are concerned since
96 memberships are computed on the fly.
100 database consists of three separate maps (netgroup, netgroup.byuser
101 and netgroup.byhost) that are keyed to allow
103 lookups to be done quickly.
107 system can interact with the
110 maps in the following ways:
111 .Bl -bullet -offset indent
115 file does not exist, or it exists and is empty, or
116 it exists and contains only a
122 lookups will be done exclusively through
126 taking advantage of the netgroup.byuser and
127 netgroup.byhost maps to speed up searches.
129 is more or less compatible with the behavior of SunOS and
134 exists and contains only local
139 token), then only the local
141 information will be processed (and
147 exists and contains both local netgroup data
152 token, the local data and the
155 map will be processed as a single combined
158 While this configuration is the most flexible, it
159 is also the least efficient: in particular,
161 lookups will be especially slow if the
165 .Bl -tag -width /etc/netgroup -compact
167 the netgroup database
170 The file format is compatible with that of various vendors, however it
171 appears that not all vendors use an identical format.
176 The interpretation of access restrictions based on the member tuples of a
177 netgroup is left up to the various network applications.
178 Also, it is not obvious how the domain specification
185 database should be stored in the form of a
188 database just like the
190 database to speed up reverse lookups.