Ok the --debug help me locate the problem. A sol 5.6 client was causing it . After shutting this client on and off a couple of time to verify it, I rolled back to a june 8 build and its fine! Since Ive just two 5.6 host no problem. I have not updated any other client thats I can tell but my severs 5.9 so I guess that ok.
Question can I just tar up the client on the server and use it on other
sol 5.9 systems and any
changes need to be made after untarring?
Also is there a way that clients can id themselves on the web page?
Lastly, a requested , be nice if at least "drop host test" could be added to disable/enable page! "drop host" understand would be more complicated.
--
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
| _p_ Mike Nemeth
| ___| |_____ email(w) michael.nemeth at lmco.com Work: 856 359-1425
|><___________) | Home Page:http://www.geocities.com/mjnemeth/
| Work Page:http://faraday.motown.lmco.com:3000/~nemethm/
| Work Page:http://ortfsb/~mnemeth/
|++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
On Fri, Jun 16, 2006 at 10:29:05AM -0400, Michael Nemeth wrote:
Ok the --debug help me locate the problem. A sol 5.6 client was causing it . After shutting this client on and off a couple of time to verify it, I rolled back to a june 8 build and its fine!
Could you mail me a copy of the ~hobbit/client/tmp/msg.*.txt file from one of those Solaris 5.6 systems ? Or is it one of the secret servers?
Question can I just tar up the client on the server and use it on other
sol 5.9 systems and any changes need to be made after untarring?
Yes, the client should be copy-able across clients, as long as they report to the same Hobbit server. If not, you'll have to change the server-IP setting in hobbitclient.cfg.
Also is there a way that clients can id themselves on the web page?
Not sure what you mean with this.
Regards, Henrik
participants (2)
-
henrik@hswn.dk
-
michael.nemeth@lmco.com