Re: [cobalt-users] i should know this one ....

[Alfredo <alfredo@xxxxxxxxxxxxxxx>]

> Repyling to my own message - gotta be a sign of losing it.

Well, I changed the title back to the original then. I hope that 
doesn't mess things up.

> I've been digging through the archives because I remember something about
> how an Admin can only admin 32 sites. This, to me, completely sucks - but I
> suppose I'll have to deal with it.

As do we all. It's a system software limitation, not a Raq problem 
specifically.

> However, the instructions I found in this message completely lose me:
> http://list.cobalt.com/pipermail/cobalt-users/2000-October/022037.html
>
> And I still have no idea what actual 'level' of administration all of these
> different Admins have.

They actually aren't different Admins -- they are all you, Carrie. At 
least this is the case on Raq3 and I can't see how it would be 
different on Raq4s. When you create a site on the Raq, it makes you 
the admin for the site even if you have created a user and named this 
person the admin for the site. You are then both admins for that site.

This rather charming little anomaly then confronts you with the "site 
admin limit" and you can't ftp anything new after you've reached the 
limit. :-)

Solution is simple; we do it all the time. You go to etc/group with 
an editor and check it out -- you'll see admins for all those sites. 
You have two options. If you have made other users the site admin, as 
we do, then all you do is erase "admin" from the line for that 
particular site and that leaves the user you appointed administrator 
for that site. Right? We do it for ALL the sites we have on our 
servers because most of those folks administer their own sites or, if 
we manage them, we go in with the specific site's username and 
password. We NEVER use "admin" as a virtual site administrator -- to 
confusing for us.

The post you referred to is another workaround if you need to 
administer all sites yourself. Basically, you create one admin for 
the first 25 sites and then another admin (called something like 
admin2) for the next 25, etc. This way, you can use just two or three 
username/password combos to get in there.

Two remaining things to do after you've cleaned up "group":

1 -- After you've saved the rewritten "group" file, cp it to group- 
(that's its "shadow" file, so to speak) and that will make everything 
active. Otherwise, you can stop and restart Apache and that will also 
copy the file over. But, as we all know, make a backup of group 
before you start any of this -- sinus medication or not. :-)

2 -- Make sure that new admin owns all the files on the site or at 
least that they're owned by httpd. Although both admin and the 
appointed administrator have ownership privileges on the site, that 
appointed administrator may not own some of the files if you've ftp'd 
anything up to the site yourself while you had admin privileges for 
the site.

I hope this isn't more confusing than the confusion.
--
People-Link/Institute for Mass Communications
www.people-link.org
Communications for a Better World...and for the People Who are Building One!
Members, Local 1180, Communications Workers of America, AFL-CIO