Re: [hobbit] Different Tests for different clients: but same localclient.cfg

[William Ottley <wottley (at) cmicanada.com>]

Thank you Greg!
You were right. 
I ended up finding out the hostname is different, and now I get everything
the same!
Thanks!!!
William


On 19/03/09 4:18 PM, "Hubbard, Greg L" <greg.hubbard (at) eds.com> wrote:

> Your Mac client is probably not communicating correctly with the Hobbit server
> on your Solaris 10 machine.  Check your ghosts report to see if you have a
> naming mismatch between your bb-hosts file and what the Darwin client is
> sending.  If there is a mismatch, you either fix it at the client (with a
> startup parameter for the bbclient process) or at the server end with a CLIENT
> tag in the bb-hosts file.  (Or something like that, I am working from memory).
>  
> GLH
> 
>>  
>>  
>> 
>>  From: William Ottley  [mailto:wottley (at) cmicanada.com]
>> Sent: Thursday, March 19, 2009 3:09  PM
>> To: hobbit (at) hswn.dk
>> Subject: [hobbit] Different Tests  for different clients: but same
>> localclient.cfg
>> 
>>  
>> Hi all,
>> 
>> I compiled the client for solaris 10  and for the mac OSX.
>> They have been added to the bbhosts file on the hobbit  server.
>> They both have the same localclient.cfg, pointing to the hobbit  server.
>> 
>> I¹m trying to get all the tests to show up.
>> But only some  of them do so. What needs to be changed to do so?
>> 
>> Solaris10:  Bbd,  conn, cpu,  disk, files, http,  info,  memory,  msgs,
>> ports,   procs,  trends
>> OSX:    conn,  info, trends
>> 
>> The mac has almost no tests on it: is this because the  server isn¹t talking
>> to the client?
>> 
>> Any help would be  appreciated.
>> 
>> Thanks
>> 
>> Will
>> 
>> 
>> On 19/03/09 2:38 PM, "Taylor  Lewick" <tlewick (at) tradebotsystems.com>  wrote:
>> 
>>  
>>> Is anyone doing anything to be alerted on a per Core  basis instead of
>>> overall CPU.  This would apply to both Linux and  Windows, under windows
>>> using the bbwin  client?


-- 
This message has been scanned for dangerous content by MailScanner, and is believed to be clean.