Mailinglist Archive: opensuse (3767 mails)
| < Previous | Next > |
Re: [SLE] Multiple groups with same GID conflict
- From: Ken Schneider <suse-list@xxxxxxxxxxxxx>
- Date: Thu, 09 Feb 2006 15:05:31 -0500
- Message-id: <1139515531.31949.31.camel@xxxxxxxxxxxxxxxxx>
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
> 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
| < Previous | Next > |