xref: /freebsd/usr.sbin/mountd/netgroup.5 (revision afe61c15161c324a7af299a9b8457aba5afc92db)
1.\" Copyright (c) 1992, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
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 the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\"     @(#)netgroup.5	8.2 (Berkeley) 12/11/93
33.\"
34.Dd December 11, 1993
35.Dt NETGROUP 5
36.Os
37.Sh NAME
38.Nm netgroup
39.Nd defines network groups
40.Sh SYNOPSIS
41.Nm netgroup
42.Sh DESCRIPTION
43The
44.Nm netgroup
45file
46specifies ``netgroups'', which are sets of
47.Sy (host, user, domain)
48tuples that are to be given similar network access.
49.Pp
50Each line in the file
51consists of a netgroup name followed by a list of the members of the
52netgroup.
53Each member can be either the name of another netgroup or a specification
54of a tuple as follows:
55.Bd -literal -offset indent
56(host, user, domain)
57.Ed
58where the
59.Sy host ,
60.Sy user ,
61and
62.Sy domain
63are character string names for the corresponding component.
64Any of the comma separated fields may be empty to specify a ``wildcard'' value
65or may consist of the string ``-'' to specify ``no valid value''.
66The members of the list may be separated by whitespace and/or commas;
67the ``\e'' character may be used at the end of a line to specify
68line continuation.
69The functions specified in
70.Xr getnetgrent 3
71should normally be used to access the
72.Nm netgroup
73database.
74.Pp
75Lines that begin with a # are treated as comments.
76.Sh FILES
77.Bl -tag -width /etc/netgroup -compact
78.It Pa /etc/netgroup
79the netgroup database.
80.El
81.Sh SEE ALSO
82.Xr getnetgrent 3 ,
83.Xr exports 5
84.Sh COMPATIBILITY
85The file format is compatible with that of various vendors, however it
86appears that not all vendors use an identical format.
87.Sh BUGS
88The interpretation of access restrictions based on the member tuples of a
89netgroup is left up to the various network applications.
90Also, it is not obvious how the domain specification
91applies to the BSD environment.
92