ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000073ClearOSpublic2010-04-20 12:272010-06-02 13:23
Reporterdloper 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version5.1 
Target Version5.2Fixed in Version5.2 
Summary0000073: allusers group mapped to low number RID.
DescriptionThe allusers group gives unpredictable behavior because its RID is too low (sub1000, typically around 400). For future versions of ClearOS, new systems installations should be assign the next available RID above 1000. For existing systems or systems being upgraded, the RID should be validated with the following command:

net groupmap list |grep allusers

A typical result would be:

allusers (S-1-5-21-1244819374-4214811992-3147932985-400) -> allusers

If the number in the RID of the result is < 1000 then the following should be run:

net groupmap delete ntgroup=allusers

Which will state:
Sucessfully removed allusers from the mapping db

net groupmap add ntgroup=allusers unixgroup=allusers

Which will state:
No rid or sid specified, choosing a RID
Got RID -94967295
Successfully added group allusers to the mapping db as a domain group

net groupmap list |grep allusers
allusers (S-1-5-21-1597500725-3060052246-2658335623-4200000001) -> allusers
TagsNo tags attached.
Attached Files

- Relationships
duplicate of 0000045closedjterpstra All Users group RID needs to be changed from the default 400 

-  Notes
(0000088)
user2
2010-04-20 21:09

Added document on the topic of UIDs, GIDs, and RIDs @ http://www.clearfoundation.com/docs/developer/features/cleardirectory/uids_gids_and_rids [^]
(0000116)
user2
2010-05-12 14:38
edited on: 2010-08-18 15:07

Source Code Changelog
---------------------------------------------------
- Changed allusers gidNumber [tracker 0000073]

File Changes
---------------------------------------------------
U legacy/modules/trunk/app-users/upgrade-4xusers


- Issue History
Date Modified Username Field Change
2010-04-20 12:27 dloper New Issue
2010-04-20 13:33 user2 Relationship added duplicate of 0000045
2010-04-20 13:33 user2 Status new => confirmed
2010-04-20 13:33 user2 Target Version => 5.2
2010-04-20 21:09 user2 Note Added: 0000088
2010-04-29 12:31 user2 Checkin
2010-04-29 12:31 user2 Note Added: 0000096
2010-04-29 12:31 user2 Status confirmed => resolved
2010-04-29 12:31 user2 Resolution open => fixed
2010-04-29 17:03 user2 Checkin
2010-04-29 17:03 user2 Note Added: 0000101
2010-05-12 14:38 user2 Checkin
2010-05-12 14:38 user2 Note Added: 0000116
2010-05-19 11:27 user2 Fixed in Version => 5.2
2010-06-02 13:23 user2 Status resolved => closed
2010-08-18 15:05 user2 Note Deleted: 0000096
2010-08-18 15:06 user2 Note Deleted: 0000101
2010-08-18 15:07 user2 Note Edited: 0000116