Multiple groups with same GID conflict
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all. I was trying to figure out why alsa was acting so strangely on my primary users account and not causing problems with my secondary/backup acct when I went into yast user/groups settings and it complained that there where multiple groups with the same GID and that I needed to manually correct this before yast could proceed. So upon looking at /etc/group if found the following: distcc:!:101: nobody:x:65533:nobody nogroup:x:65534:nobody users:x:100:bin,crey,crrey,ftp,gdm,lp,mail,man,news,wwwrun haldaemon:!:102: messagebus:!:101: beagleindex:!:103: icecream:!:104: Now my question is, what GID # should I set "messagebus" or "distcc" to. Which one should I change to avoid any further problems and what GID # should I use? TIA, Curtis. - -- Spammers Beware: Tresspassers will be shot, survivors will be shot again! Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD65ib7CQBg4DqqCwRAkCMAJ4t34aUOFe/4uMjMNX5H3rO4eGXngCePusU 4FsXOHn1izDCnwJjVINVTfQ= =5owP -----END PGP SIGNATURE-----
On Thu, 2006-02-09 at 11:31 -0800, Curtis Rey wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello all. I was trying to figure out why alsa was acting so strangely on my primary users account and not causing problems with my secondary/backup acct when I went into yast user/groups settings and it complained that there where multiple groups with the same GID and that I needed to manually correct this before yast could proceed. So upon looking at /etc/group if found the following:
distcc:!:101: nobody:x:65533:nobody nogroup:x:65534:nobody users:x:100:bin,crey,crrey,ftp,gdm,lp,mail,man,news,wwwrun haldaemon:!:102: messagebus:!:101: beagleindex:!:103: icecream:!:104:
Now my question is, what GID # should I set "messagebus" or "distcc" to. Which one should I change to avoid any further problems and what GID # should I use?
I would suggest changing any group that you added manually or that may have been added after system install. It matters not what you change it to as long as there are no dups. It is also suggested that you use numbers over 500 I believe. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Thu, 2006-02-09 at 14:31 -0500, Ken Schneider wrote:
On Thu, 2006-02-09 at 11:31 -0800, Curtis Rey wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello all. I was trying to figure out why alsa was acting so strangely on my primary users account and not causing problems with my secondary/backup acct when I went into yast user/groups settings and it complained that there where multiple groups with the same GID and that I needed to manually correct this before yast could proceed. So upon looking at /etc/group if found the following:
distcc:!:101: nobody:x:65533:nobody nogroup:x:65534:nobody users:x:100:bin,crey,crrey,ftp,gdm,lp,mail,man,news,wwwrun haldaemon:!:102: messagebus:!:101: beagleindex:!:103: icecream:!:104:
Now my question is, what GID # should I set "messagebus" or "distcc" to. Which one should I change to avoid any further problems and what GID # should I use?
I would suggest changing any group that you added manually or that may have been added after system install. It matters not what you change it to as long as there are no dups. It is also suggested that you use numbers over 500 I believe.
To be more precise in this situation the one that seems to be in error is distcc. Change it to 105 (provided no other group is using that number) and you should be all set. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu February 9 2006 12:05, Ken Schneider wrote:
On Thu, 2006-02-09 at 14:31 -0500, Ken Schneider wrote:
On Thu, 2006-02-09 at 11:31 -0800, Curtis Rey wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello all. I was trying to figure out why alsa was acting so strangely on my primary users account and not causing problems with my secondary/backup acct when I went into yast user/groups settings and it complained that there where multiple groups with the same GID and that I needed to manually correct this before yast could proceed. So upon looking at /etc/group if found the following:
distcc:!:101: nobody:x:65533:nobody nogroup:x:65534:nobody users:x:100:bin,crey,crrey,ftp,gdm,lp,mail,man,news,wwwrun haldaemon:!:102: messagebus:!:101: beagleindex:!:103: icecream:!:104:
Now my question is, what GID # should I set "messagebus" or "distcc" to. Which one should I change to avoid any further problems and what GID # should I use?
I would suggest changing any group that you added manually or that may have been added after system install. It matters not what you change it to as long as there are no dups. It is also suggested that you use numbers over 500 I believe.
To be more precise in this situation the one that seems to be in error is distcc. Change it to 105 (provided no other group is using that number) and you should be all set.
Thanks Ken. I changed it to the 500's you suggested, but it's not really a problem to go back and edit the group and passwd file - since changing to the 500s it is treated more as a user. Again, thanks. Curtis. - -- Spammers Beware: Tresspassers will be shot, survivors will be shot again! Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD6+CZ7CQBg4DqqCwRAlD3AJ0bWSbqSGWdFYsylBQJxn9ez9rnrQCg12oQ 91rLsGsZdXpQgG5ZP2UmACo= =nods -----END PGP SIGNATURE-----
participants (2)
-
Curtis Rey
-
Ken Schneider