Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

group(4) [sunos man page]

group(4)							   File Formats 							  group(4)

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) routines 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 maximize 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 supplementary 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. 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 22 Jul 2004 group(4)

Check Out this Related Man Page

grpck(1B)                                            SunOS/BSD Compatibility Package Commands                                            grpck(1B)

grpck - check group database entries SYNOPSIS
/etc/grpck [filename] DESCRIPTION
The grpck utility checks that a file in group(4) does not contain any errors; it checks the /etc/group file by default. FILES
/etc/group ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
groups(1), group(4), passwd(4), attributes(5) DIAGNOSTICS
Too many/few fields An entry in the group file does not have the proper number of fields. No group name The group name field of an entry is empty. Bad character(s) in group name The group name in an entry contains characters other than lower-case letters and digits. Invalid GID The group ID field in an entry is not numeric or is greater than 65535. Null login name A login name in the list of login names in an entry is null. Logname not found in password file A login name in the list of login names in an entry is not in the password file. Line too long A line (including the newline character) in the group file exceeds the maximum length of 512 characters. Duplicate logname entry A login name appears more than once in the list of login names for a group file entry. Out of memory The program cannot allocate memory in order to continue. Maximum groups exceeded for logname A login name's group membership exceeds the maximum, NGROUPS_MAX. SunOS 5.10 10 Jan 2000 grpck(1B)
Man Page