[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Site name change causing havoc with Webalizer stats
- Subject: Re: [cobalt-users] Site name change causing havoc with Webalizer stats
- From: "MikeM" <MyRaQ@xxxxxxxxx>
- Date: Thu Nov 1 05:51:02 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On 11/1/01 at 7:51 AM Johan Pretorius wrote:
|We ran a test a couple of weeks ago, say for testdomain.mydomain.com ...
|
|The actual domain is now being hosted as testdomain.com, but to save
|some time and effort, I've merely renamed "testdomain.mydomain.com"
|to "testdomain.com" in the GUI.
|
|Host was testdomain, is now www; domain was mydomain.com and is now
|testdomain.com.
|
|All is working 100%, but for some reason or the other Webalizer (or
|could that be logrotate?) still shows stats for "testdomain.mydomain.com"
|...
|
|What would be the best way of solving this?
=============
The first thing to do is to find out where Webalizer is picking up the site name. If you installed from the Cobalt-aid.sourceforge.net Webalizer 2.01 package, the name is take from the name on the symbolic link in the /home/sites directory. The script that does this is /usr/bin/webalizer2.pl and you would be looking at the variable $asite as it is passed into the -n option on the webalizer command.
Other packages may (and probably do) operate differently.