[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] group siteX already exists RaQ4
- Subject: [cobalt-users] group siteX already exists RaQ4
- From: "Carrie Linn Bartkowiak" <ravencarrie@xxxxxxxx>
- Date: Wed Dec 20 22:33:01 2000
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Hey guess what! I ran into a problem tonight and fixed it myself without
even having to delve into the archives. There must be some semblance of
intelligence left in this brain after all.
In case anyone else has this problem, here's what happened.
I tried to add a new virtual site and received the error "group site22
already exists".
Well, sure enough, the last domain I added (one of my own) is folder site22.
Hmm. So why is it trying to do another site22? The "group" part tipped me
off.
I checked my /etc/group file and found that there was no entry for site22.
Weird!
I deduced that when I was messing around trying to get the admin-of-multiple
sites thing to work, I must have uploaded an old copy of 'group' (as I work
through FTP rather than vi most of the time, switching ownership in telnet
to admin and back to root) and *that* copy didn't yet have site22 listed.
The last two lines in the file were:
site20:x:132:admin,xxxxx
site21:x:133:admin
(where xxxxx is another username I don't care to release *s*)
So working on that premise, I added this line:
site22:x:134:admin
Re-uploaded group, copied to group- for the shadow, and tried adding the new
site again. Worked like a charm.
Checked the newly overwritten group file, and it had this:
site22:x:adminsite23
Ack. I had forgotten to leave the start of a new line for the GUI to write
to.
So I moved that down to a new line and added admin:
site22:x:admin
site23:x:admin (then hit enter to make sure there was a new line under this
one)
Everything still worked. Added a site administrator to the new site, checked
the group file again, and now it had:
site23:x:admin,xxxxx
Ta-da!
I'm so proud of myself. It doesn't take much to amuse me. ;)
I just went and checked in the archives and the consensus to fix this
problem seems to be to delete the offending site (in this case, site22)
through telnet and then add it again through the GUI. Either way will work,
but I like my solution better. <grin>
Carrie Bartkowiak