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

group(4)						     Kernel Interfaces Manual							  group(4)

group, logingroup - group file, grp.h DESCRIPTION
contains for each group the following information: o group name o encrypted password o numerical group ID o comma-separated list of all users allowed in the group The file is an ASCII file. Fields are separated by colons, and each group is separated from the next by a new-line. No spaces should sep- arate the fields or parts of fields on any line. If the password field is null, no password is associated with the group. There are two files of this form in the system, and The file exists to supply names for each group, and to support changing groups by means of the utility (see newgrp(1)). provides a default group access list for each user via and (see login(1) and initgroups(3C)). The real and effective group ID set up by for each user is defined in (see passwd(4)). If is empty, the default group access list is empty. If and are links to the same file, the default access list includes the entire set of groups associated with the user. The group name and password fields in are never used; they are included only to give the two files a uniform format, allowing them to be linked together. All group IDs used in or should be defined in These files reside in directory Because of the encrypted passwords, these files can and do have general read permission and can be used, for example, to map numerical group IDs to names. The group structure is defined in and includes the following members: NETWORKING FEATURES
NIS The file can contain a line beginning with a plus which means to incorporate entries from Network Information Services (NIS). There are two styles of entries: means to insert the entire contents of NIS group file at that point, and means to insert the entry (if any) for name from NIS at that point. If a entry has a non-null password or group member field, the contents of that field overide what is contained in NIS. The numerical group ID field cannot be overridden. A group file can also have a line beginning with a minus these entries are used to disallow group entries. There is only one style of entry; an entry that consists of means to disallow any subsequent entry (if any) for name. These entries are disallowed regardless of whether the subsequent entry comes from the NIS or the local group file. WARNINGS
Group files must not contain any blank lines. Blank lines can cause unpredictable behavior in system administration software that uses these files. Group ID (gid) 9 is reserved for the Pascal Language operating system and the BASIC Language operating system. These are operating systems for Series 300/400 computers that can co-exist with HP-UX on the same disk. Using this gid for other purposes can inhibit file transfer and sharing. The length of each line in is limited to as defined in Because of this limit, users should not be listed in their primary group - only in their additional groups. If is linked to group membership for a user is managed by NIS, and no NIS server is able to respond, that user cannot log in until a server does respond. There is no single tool available to completely ensure that and are compatible. However, and can be used to simplify the task (see pwck(1M)). There is no tool for setting group passwords in DEPENDENCIES
NIS Here is a sample file: Group has a gid of 1 and members and The group is ignored since it appears after the entry Also, the group has members and and the password and group ID of the NIS entry for the group All groups listed in the NIS are pulled in and placed after the entry for The plus and minus features are part of NIS. Therefore if NIS is not installed, these features cannot work. FILES
groups(1), newgrp(1), passwd(1), setgroups(2), crypt(3C), getgrent(3C), initgroups(3C), passwd(4). STANDARDS CONFORMANCE
Man Page

Featured Tech Videos