|
Hopefully, this page is exactly what you are looking for, but if not, you can always find further assistance on Unix/Linux Forum!
File Formats group(4)
NAME
group - group file
DESCRIPTION
The group file is a local source of group information. The
group file can be used in conjunction with other group
sources, including the NIS maps group.byname and
group.bygid, the NIS+ table group, or group information
stored on an LDAP server. Programs use the getgrnam(3C) rou-
tines to access this information.
The group file contains a one-line entry for each group
recognized by the system, of the form:
groupname:password: gid:user-list
where
groupname The name of the group.
gid The group's unique numerical ID (GID) within
the system.
user-list A comma-separated list of users allowed in
the group.
The maximum value of the gid field is 2147483647. To maxim-
ize interoperability and compatibility, administrators are
recommended to assign groups using the range of GIDs below
60000 where possible.
If the password field is empty, no password is demanded.
During user identification and authentication, the supple-
mentary group access list is initialized sequentially from
information in this file. If a user is in more groups than
the system is configured for, {NGROUPS_MAX}, a warning will
be given and subsequent group specifications will be
ignored.
Malformed entries cause routines that read this file to
halt, in which case group assignments specified further
along are never made. To prevent this from happening, use
grpck(1B) to check the /etc/group database from time to
time.
SunOS 5.10 Last change: 22 Jul 2004 1
File Formats group(4)
Previous releases used a group entry beginning with a `+'
(plus sign) or `-' (minus sign) to selectively incorporate
entries from a naming service source (for example, an NIS
map or data from an LDAP server) for group. If still
required, this is supported by specifying group:compat in
nsswitch.conf(4). The compat source may not be supported in
future releases. Possible sources are files followed by ldap
or nisplus. This has the effect of incorporating information
from an LDAP server or the entire contents of the NIS+ group
table after the group file.
EXAMPLES
Example 1: Sample of a group File.
Here is a sample group file:
root::0:root
stooges:q.mJzTnu8icF.:10:larry,moe,curly
and the sample group entry from nsswitch.conf:
group: files ldap
With these entries, the group stooges will have members
larry, moe, and curly, and all groups listed on the LDAP
server are effectively incorporated after the entry for
stooges.
If the group file was:
root::0:root
stooges:q.mJzTnu8icF.:10:larry,moe,curly
+:
and the group entry from nsswitch.conf:
group: compat
all the groups listed in the NIS group.bygid and
group.byname maps would be effectively incorporated after
the entry for stooges.
SEE ALSO
groups(1), grpck(1B), newgrp(1), getgrnam(3C),
initgroups(3C), nsswitch.conf(4), unistd.h(3HEAD)
System Administration Guide: Basic Administration
SunOS 5.10 Last change: 22 Jul 2004 2
Man(1) output converted with
man2html and wrapped by fishsponge
This page was generated on Wed Sep 12 11:27:24 GMT 2007
|
Your favourite pages:
No pages logged yet.
Trying to save cookie... Top 10 most popular pages:
CPAN man page (4196 hits)
(Suse Linux 10.1)
ssh man page (4111 hits)
(Suse Linux 10.1)
svn man page (2354 hits)
(FreeBSD 6.2)
startproc man page (1695 hits)
(Suse Linux 10.1)
adv_cap_autoneg man page (1445 hits)
(Solaris 10 11_06)
signal man page (1357 hits)
(Suse Linux 10.1)
sqlite3 man page (1329 hits)
(openSUSE 10.2)
netcat man page (1188 hits)
(Suse Linux 10.1)
pprosetup man page (1177 hits)
(Solaris 10 11_06)
lwptut man page (1105 hits)
(Suse Linux 10.1)
|
Man Pages 
