System's groups must have a fix gid

Bug #113220 reported by Oumar Aziz OUATTARA
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Hi,

When working on a bug with Sbackup , I decided to make sbackup runs under root:admin so I set the process gid to 117 thinking it was the admin gid on every ubuntu installation . Then when testing on a virtual machine on VMware I noticed that the admin GID was 116 and 117 was GDM .
I don't remember what I did uninstall on that VM but this should *NEVER* happened. The worst is all of the GID after 116 have been changed .

I think this is dangerous for the stability of the system.

Revision history for this message
Martin Pitt (pitti) wrote :

There has never been a promise about stability of user/group IDs above 100. Only the IDs below 100 are assigned statically.

http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/uidrange.html

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.