New sites get created in
/usr/sausalito/handlers/base/vsite/vsite_create.pl ....
This is the file I edited to fix my problem ages ago - but it appears
the code has been over-written by either an update or some other action
since my code changes.
If you're interested in the other part of the path, the details are in
/usr/sausalito/perl/Base/HomeDir.pm
This file contains a method called homedir_get_group_dir..... This
method will get a home directory location for a group. The location is
hashed to avoid having more than a few hundred entries per directory for
performance reasons. It returns the empty string, '', if it fails for
any reason.
It calls a private function called "_hash_path". This takes a directory
name and system group or user name, and returns where the directory
should lie in the filesystem.
Best Regards,
Greg Kuhnert.
--
Compass Networks.
Pointing you in the right direction
http://www.compassnetworks.com.au/
Lucas Peyatt - Ohio Web Hosting & Development wrote:
> Thanks Greg,
>
> I fixed this a few days ago, I just deleted everything in "/home/.sites/"
> except the "server" directory. That fixed the disk usage issue, It looks like
> that script does something similar.
>
> If someone is reading this in the future please note, I had no vsites on the
> server anymore, therefore was able to do this with no repercussions.
>
> On another note, does anyone know where those "random" numbers that are in
> "/home/.sites/" come from? Is is CCE's OID number?
>
> On Mon, 16 Feb 2009 10:31:16 +1100, Greg Kuhnert wrote
>
>> Lucas Peyatt - Ohio Web Hosting & Development wrote:
>>
>>> Now I have two "blank" vsites in the disk usage gui, I looked in
>>>
> /home/.sites/
>
>>> and there are many numbered directories, It looks like the old sites were
>>>
> not
>
>>> completely deleted.
>>>
>>> Would it be safe to delete those directories?
>>>
>>>
>> Hi Blue*.
>>
>> I have come across this problem many times, where things seem to get
>> out of sync with regard to the allocation of sitenames. The core of
>> the problem is how bluequartz picks the next sitename. It does not
>> adequately check if it will be able to fully use that name.
>>
>> I did create a fix ages ago for this, but I didn't have access to the
>> development tree.... so I just forgot about it..... When I get some
>> time, I will look around to see if I still have the patch...
>>
>> In the meantime, I did find a script I wrote a long time ago that may
>> help you find the root cause of your problem.
>>
>> The details are available at
>> http://www.compassnetworks.com.au/?page=sitecheck
>>
>> I hope this helps find your problem.
>>
>> Best Regards,
>> Greg Kuhnert.
>>
>> --
>> Compass Networks.
>> Pointing you in the right direction
>>
>> http://www.compassnetworks.com.au/
>>
>
>
> --
> Lucas Peyatt
> Ohio Web Hosting & Development
> lucas (at mark) ohiowebhosting.net
> www.ohiowebhosting.net
> 937.969.4476 dayton
> 614.441.8169 columbus
> 513.258.2376 cincinnati
> 206.350.1292 facsimile
>
>
>