[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Admin Site Limits
- Subject: RE: [cobalt-users] Admin Site Limits
- From: "Paul Alcock" <webmgr@xxxxxxxxxxxxxxxxxx>
- Date: Sun Sep 23 23:21:52 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> Carrie wrote a message detailing the steps for setting up admin1 and
> admin2...all having 25 domains each so it was hard to go over by accident
> and easy to remember which adminX managed which site numbers...
Having just modified my httpd.conf to the Nimba exclusion, I took a closer
look
at the file (httpd.conf) than usual (I normally let the GUI take care of
it.)
And I noticed this and wondered if it is relavant to the Admin Site Limit
problem.
Out of 30 virtual hosts, 17 have the ServerAdmin admin
and the remaining sites have ServerAdmin Sitex where x is the site number.
After reviewing the sites carefully I cannot figure out how come some
are set to admin and some set to sitex.
I'm guessing that if I continue to add hosts and those with the
ServerAdmin admin values exceed 31 then I'll have a problem.
So my questions on this topic are.
1. anyone know what causes some sites to be set to ServerAdmin admin
and others ServerAdmin sitex
2. If I modify the httpd.conf file to make all sites except the
server sites (eg except nameserver hosts, machine hosts, etc.)
to ServerAdmin sitex will that get overwritten next time I add
a virtual host. And will it create an acces (ftp) problem.
At present we ftp to each site using the site admins id not the
RAQ admin user id.
BTW. I would have posted this from the cobalt site as a new
thread, but figured it was relavant to the current one.
Paul
-- sig
Get an account at http://www.ourfaqsite.com
and keep your FAQs up to date.