topic Re: Any Ideas -- Checking client status. in Operating System - HP-UX

Any Ideas -- Checking client status.

Russ Hancock_1 — Fri, 05 Dec 2003 08:54:11 GMT

I run a number of scripts that go around the client machines on our system doing different jobs.
The problem I have is when machines are switched off the script hangs, trying to connect.
In short is there a way to check whether a machine is up or not from the server, without waiting for the Connection Timeout message.

Thanks in advance.
Russ.

Re: Any Ideas -- Checking client status.

Pete Randall — Fri, 05 Dec 2003 09:00:23 GMT

Russ,

Ping?

Pete

Re: Any Ideas -- Checking client status.

PVR — Fri, 05 Dec 2003 09:00:39 GMT

Hi,

Why don't u ping the client machines and check???
#ping a.b.c.d(client ip address)

Re: Any Ideas -- Checking client status.

Dave Hutton — Fri, 05 Dec 2003 09:01:13 GMT

Can try adding in your script to:
ping server -n 1
and checking to see if you get 100% packetloss before continuing on.

Dave

Re: Any Ideas -- Checking client status.

RAC_1 — Fri, 05 Dec 2003 09:01:21 GMT

ping machine for three pings only. check status and proceed.

ping -n3 host_name
if [ $? -ne 0 ]
then
echo "machine not available"
exit

Re: Any Ideas -- Checking client status.

Mark Grant — Fri, 05 Dec 2003 09:13:15 GMT

If you want to check if your remsh is going to work even if the machine is up. You need to do a test remsh with a timeout and then remsh again.

Attached is a perl script called remsh.pl that attempts to remsh but times out after 30 seconds.

call it with "remsh.pl host command"

Oh, and read the comments at the start :)