Re: [cobalt-users] two issues (redirecting domain and groupfile lock)

[flash22@xxxxxxx]

On Mon, 23 Apr 2001, Ashby Gochenour wrote:

> Hello Guys,
> I have inherited administration on a fleet of Cobalt raqs (raq2, 3, and 
> 4s).
> 
> I have a raq2 that is complaining that 'group file is locked' when I try 
> to add a virtual site.

  /etc/group.lock

  also make sure the / partition is not full, this is a common cause of
  stuck locks

  other locks are in /var/lock

> Issue 2:
> (this is also on the same raq2)
> 
> I have a domain that needs to be pointed at another domain on the raq 
> (via http).
> 
> www.newdomain.com should end up at www.existingvirtualdomain.com

I will assume you mean 'keeping the domain name in the browser, not
redirecting to the new domain name...

> 
> The way the former admin was doing it was replacing the server alias 
> (usually domain.com without the www) with the domain that wants to be 
> pointed at the other. I don't like this way as it seems like a cheap 
> hack and loses the ability of the first domain to be accessed without 
> the www's. (I think they were doing this manual through editing httpd.conf)

They didn't do it properly...

> 
> I was thinking about adding the second site as a virtual domain and then 
> editing the httpd.conf file to point the document root of the new domain 

Editing the httpd.conf file is about as easy as it gets ;)

Done properly there should be 3 ServerAlias 's , with and without the www,
then both will work....

It's possible to have the raq continue to do the domain -> www.domain
redirect also, but you need to change the rewrite rules around...

The reason that this is better than changing the documentroot is that the
group owner for the site is based on the site number, making one site
point to another sites directory space will cause you no end of file
ownership problems, especially with cgi-wrap, which will be trying to set
user/group based on the site that is trying to make the cgi request, but
it will be setting it for the wrong site...it also causes havoc with
site-adm users ;)

On the raq3's there are additional issues, for example setting up email
for a user on a domain where you didn't create a site is somewhat of a
project, but the raq2's are fairly easy to fool into accepting
email@domain where the domain doesn't really have a complete site..


gsh