1.\" Copyright (c) 1992, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" %sccs.include.redist.roff% 5.\" 6.\" @(#)netgroup.5 8.2 (Berkeley) 12/11/93 7.\" 8.Dd 9.Dt NETGROUP 5 10.Os 11.Sh NAME 12.Nm netgroup 13.Nd defines network groups 14.Sh SYNOPSIS 15.Nm netgroup 16.Sh DESCRIPTION 17The 18.Nm netgroup 19file 20specifies ``netgroups'', which are sets of 21.Sy (host, user, domain) 22tuples that are to be given similar network access. 23.Pp 24Each line in the file 25consists of a netgroup name followed by a list of the members of the 26netgroup. 27Each member can be either the name of another netgroup or a specification 28of a tuple as follows: 29.Bd -literal -offset indent 30(host, user, domain) 31.Ed 32where the 33.Sy host , 34.Sy user , 35and 36.Sy domain 37are character string names for the corresponding component. 38Any of the comma separated fields may be empty to specify a ``wildcard'' value 39or may consist of the string ``-'' to specify ``no valid value''. 40The members of the list may be separated by whitespace and/or commas; 41the ``\e'' character may be used at the end of a line to specify 42line continuation. 43The functions specified in 44.Xr getnetgrent 3 45should normally be used to access the 46.Nm netgroup 47database. 48.Pp 49Lines that begin with a # are treated as comments. 50.Sh FILES 51.Bl -tag -width /etc/netgroup -compact 52.It Pa /etc/netgroup 53the netgroup database. 54.El 55.Sh SEE ALSO 56.Xr getnetgrent 3 , 57.Xr exports 5 58.Sh COMPATIBILITY 59The file format is compatible with that of various vendors, however it 60appears that not all vendors use an identical format. 61.Sh BUGS 62The interpretation of access restrictions based on the member tuples of a 63netgroup is left up to the various network applications. 64Also, it is not obvious how the domain specification 65applies to the BSD environment. 66