search for: sys_gid_max

Displaying 5 results from an estimated 5 matches for "sys_gid_max".

2015 Sep 03
1
groupadd failure
...Values between 0 and 999 are typically > reserved for system accounts.", but I bet that's just the usual case > of generic documentation not tailored to the distribution. > > The highest id in the group file is 499. Combined with the error, this > could be consistent with a SYS_GID_MAX of 499. But no ids between 189 > and 485 have been assigned at all. Is groupadd really this limited? there exist a distinction between normal and system accounts/groups. For example: everything under 499 are system accounts (e.g. daemons) and 500 is your first user account ... -- LF
2015 Sep 02
2
groupadd failure
...lar machine. This is why # /usr/sbin/groupadd -r munin groupadd: Can't get unique system GID (no more available GIDs) # but I don't understand why this happens. Even after checking the man pages for groupadd and login.defs, I have been unable to determine what the settings for SYS_GID_MIN/SYS_GID_MAX on RHEL/CentOS are. None of the 5/6 machines I have access to list them in login.defs. Even assuming relatively conservative values of 201/499, resp. (examples from other distros include 101/999), this doesn't add up. # grep munin /etc/group # ypmatch munin group # wc -l /etc/group 100 /etc/gr...
2015 Sep 02
3
groupadd failure
...> groupadd: Can't get unique system GID (no more available GIDs) > > # > > > > but I don't understand why this happens. Even after checking the man pages > > for groupadd and login.defs, I have been unable to determine what the > > settings for SYS_GID_MIN/SYS_GID_MAX on RHEL/CentOS are. None of the 5/6 > > machines I have access to list them in login.defs. Even assuming > > relatively conservative values of 201/499, resp. (examples from other > > distros include 101/999), this doesn't add up. > > > > # grep munin /etc/group &g...
2015 Sep 02
0
groupadd failure
...sr/sbin/groupadd -r munin > groupadd: Can't get unique system GID (no more available GIDs) > # > > but I don't understand why this happens. Even after checking the man pages > for groupadd and login.defs, I have been unable to determine what the > settings for SYS_GID_MIN/SYS_GID_MAX on RHEL/CentOS are. None of the 5/6 > machines I have access to list them in login.defs. Even assuming > relatively conservative values of 201/499, resp. (examples from other > distros include 101/999), this doesn't add up. > > # grep munin /etc/group > # ypmatch munin group...
2015 Sep 03
0
groupadd failure
...the same man page, "Values between 0 and 999 are typically reserved for system accounts.", but I bet that's just the usual case of generic documentation not tailored to the distribution. The highest id in the group file is 499. Combined with the error, this could be consistent with a SYS_GID_MAX of 499. But no ids between 189 and 485 have been assigned at all. Is groupadd really this limited?