Red Hat Bugzilla – Bug 171124
First user has unexpected GID 501
Last modified: 2007-11-30 17:07:21 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12) Gecko/20050919 Firefox/1.0.7
Description of problem:
In previous versions of RHEL, user UIDs and GIDs started at 500. The first user was allocated UID=GID=500, the next had UID=GID=501 and so on (see RHEL4 Introduction to System Administration manual, section 188.8.131.52)
With RHEL4 Update 2, a new group 'pegasus' is created during the installation. This has GID=500, and the first user then gets UID=500, GID=501. This conflicts with our existing GID allocations.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install a new RHEL4 Update 2 system
Actual Results: A group 'pegasus' was created with GID=500. First new user has UID=500, GID=501.
Expected Results: System groups should be allocated GIDs less than 500 to avoid conflict with user groups. The first user should have UID=500, GID=500.
OK, this will be changed in the next RHEL-4 tog-pegasus version .
A workaround would be to create the pegasus userid and group during installation
with a different uid / gid, or to create the user / group you want to have
UID 500 GID 500 before pegasus gets installed, during installation.
You should in general not depend on specific numeric uids / gids always being
available after installation.
Note also that pegasus is optional; nothing else in the distro depends on it.
Removing the package would also remove the pegasus user and group.
This bug is now fixed with tog-pegasus-2.4.1-4.5.rhel4 .
Moving to RHEL4U4Proposed as it is ON_QA.
How is this fixed? By adding "-r" to the groupadd command?
This issue is on Red Hat Engineering's list of planned work items
for the upcoming Red Hat Enterprise Linux 4.4 release. Engineering
resources have been assigned and barring unforeseen circumstances, Red
Hat intends to include this item in the 4.4 release.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.