Novell SuSE SLES 10 client issue.
I've lots of SuSE 9,10,10sp1 clients with no client problems.
? are other clients able to send?
-Steve
=======================================================
Geoff Hallford wrote:
? are other clients able to send?
-Steve
=======================================================
Geoff Hallford wrote:
I would also check the ghost client report to make sure that the SLES client is sending the correct hostname to the Hobbit server. I have found on some linux clients, it send the hostname and some send the FQDN. I usually just manually modify the client config to send the hostname I want and not rely on the automatic (which I think is uname -n by default ... don't quote me on that though ... not near my Hobbit box right now).
'Nobody goes there anymore. It's too crowded.' --Yogi BerraOn Mon, Dec 1, 2008 at 11:10 PM, Great D Dilla <user-3e85c7b9d5a4@xymon.invalid> wrote:
A couple of things to check on the client:
[1] Make sure that the hostname of the hobbit server is resolvable from the
client side. Or better yet, use the IP address of the hobbit server on the
config file ==> BBDISPLAY=[IP_or_HOSTNAME_of_hobbit_server].
[2] Check to see if indeed the master is getting files. Usually there are
files in the data directory generated for your client.
Side note:
To configure the hobbit client, simply use "./configure.client" and supply
the IP of the hobbit server. It should work out of the box.
Hope this helps.