1 .\" $NetBSD: group.5,v 1.18 2007/06/21 15:12:59 ginsbach Exp $
3 .\" Copyright (c) 1980, 1991, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. Neither the name of the University nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
18 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30 .\" Portions Copyright(c) 1994, Jason Downs. All rights reserved.
32 .\" Redistribution and use in source and binary forms, with or without
33 .\" modification, are permitted provided that the following conditions
35 .\" 1. Redistributions of source code must retain the above copyright
36 .\" notice, this list of conditions and the following disclaimer.
37 .\" 2. Redistributions in binary form must reproduce the above copyright
38 .\" notice, this list of conditions and the following disclaimer in the
39 .\" documentation and/or other materials provided with the distribution.
41 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) ``AS IS'' AND ANY EXPRESS
42 .\" OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
43 .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
44 .\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR(S) BE LIABLE FOR ANY DIRECT,
45 .\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
46 .\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
47 .\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
48 .\" CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
49 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
50 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
53 .\" @(#)group.5 8.3 (Berkeley) 4/19/94
60 .Nd format of the group permissions file
66 is the local source of group information.
67 It can be used in conjunction with the Hesiod domain
80 file consists of newline separated
82 records, usually one per group, containing four colon
85 Each line has the form:
86 .Dl group:passwd:gid:[member[,member]...]
88 These fields are as follows:
89 .Bl -tag -width password -offset indent -compact
97 The group's decimal ID.
104 field is the group name used for granting file access to users
105 who are members of the group.
109 field is the number associated with the group name.
110 They should both be unique across the system (and often
111 across a group of systems) since they control file access.
119 This field is rarely used
120 and an asterisk is normally placed in it rather than leaving it blank.
124 field contains the names of users granted the privileges of
126 The member names are separated by commas without spaces or newlines.
127 A user is automatically in a group if that group was specified
130 entry and does not need to be added to that group in the
134 Very large groups can be accommodated over multiple lines by specifying the
135 same group name in all of them; other than this, each line has an identical
136 format to that described above.
137 This can be necessary to avoid the record's length limit, which is currently
138 set to 1024 characters.
139 Note that the limit can be queried through
142 .Li _SC_GETGR_R_SIZE_MAX
145 .Bd -literal -offset indent
146 biggrp:*:1000:user001,user002,user003,...,user099,user100
147 biggrp:*:1000:user101,user102,user103,...
150 The group with the name
152 has a special meaning to the
154 command: if it exists and has any members, only users listed in that group
165 .Xr nsswitch.conf 5 ,
168 lookups occur from the
177 .Xr nsswitch.conf 5 ,
180 lookups occur from the
198 .Xr nsswitch.conf 5 ,
201 file may also contain lines of the format
205 which causes the specified group to be included from the
213 If no group name is specified, or the plus sign
216 on line, all groups are included from the
223 compat references may appear anywhere in the file, but the single
226 form should be on the last line, for historical reasons.
227 Only the first group with a specific name encountered, whether in the
229 file itself, or included via Hesiod or
233 .Bl -tag -width /etc/group -compact
243 .Xr nsswitch.conf 5 ,
249 file format appeared in
254 file format first appeared in SunOS.
256 The Hesiod support first appeared in
261 command does not change the