Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

initgroups(3c) [hpux man page]

initgroups(3C)															    initgroups(3C)

NAME
initgroups() - initialize group access list SYNOPSIS
DESCRIPTION
reads the login group file, and sets up the group access list for the user specified by name, using the system call (see setgroups(2)). If the value of basegid is zero or positive, it is automatically included in the groups list. Typically this value is given as the group num- ber from the password file. If the login group file is empty, basegid is the only member of the list. If the number of groups, including the basegid entry, exceeds {NGROUPS_MAX}, then subsequent group entries are ignored (see limits(5)). RETURN VALUE
Upon successful completion, returns 0; otherwise it returns -1 and sets to indicate the error. ERRORS
fails if any of the following conditions are encountered: The calling process does not have the appropriate privilege. Insufficient memory available to hold gidset. An entry in gidset is not a valid group ID. WARNINGS
uses the routines based on getgrent(3C). If the invoking program uses any of these routines, the group structure is overwritten by the call to Subsequent calls to with the same name parameter override the actions of previous calls. On many systems, no one seems to keep up to date. uses the Dynamic Name Service Switch. (See nsswitch.conf(4).) An application that uses this interface cannot be fully archive bound. NETWORKING FEATURES
NFS If is linked to tries to use the Network Information Service (NIS) for entries beginning with a plus sign If group membership for name is managed by NIS, and no NIS server is able to respond, a call to does not return until a server does respond. This lack of action causes commands such as and to wait indefinitely. See group(4) for proper syntax and operation. AUTHOR
was developed by the University of California, Berkeley. FILES
login group file SEE ALSO
login(1), su(1), getgroups(2), setgroups(2), group(4), thread_safety(5). initgroups(3C)

Check Out this Related Man Page

group(4)							   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) 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)

Featured Tech Videos