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

["Steve Werby" <steve-lists@xxxxxxxxxxxx>]

"Ashby Gochenour" <cobalt@xxxxxxxxxxxxxxxx> wrote:
> I have a raq2 that is complaining that 'group file is locked' when I try
> to add a virtual site.
>
> I've read the archives and seen people that have had the same symptoms,
> but did not find a solution/resolution. One post reccomended looking in
> /etc/lock. I  looked and on this machine there is no /etc/lock. If
> anyone could give a  solution or suggestion much appriciated.

But there is an /etc/locks/ directory.  Try there.

> 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
>
> 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)
>
> 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
> to the document root of the site it wants to point to.

You can do this, but it's overkill.  Use the ServerAlias line, but instead
of replacing one of the existing ServerAlias lines add two more:

ServerAlias newdomain.com
ServerAlias www.newdomain.com

On newer versions of Apache you can even do the following, but I'm not sure
about the Apache 1.3.x that's factory installed on the RaQ2.

ServerAlias newdomain.com www.newdomain.com

And make sure both have A records pointing to the same IP as
www.existingvirtualdomain.com.

 I've noticed that
> these raqs don't like things done manually, so I think this idea is a
> bad one too. One more twist to the story is that DNS for these domains
> is also handled by the raq, so I don't know if this will complicate
> things more or not.

My preferred solution is to store VirtualHost containers that I have edited
in a separate file so they're not overwritten by the Cobalt GUI.  Anywhere
in httpd.conf add:

Include /etc/httpd/conf/httpd_other.conf (or whatever you want to name it).

Then create that file and put the VirtualHost blocks in there and delete
them from httpd.conf.  You can have as many Include lines as you want.

--
Steve Werby
President, Befriend Internet Services LLC
http://www.befriend.com/