HP3000-L Archives

July 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Doug Werth <[log in to unmask]>
Reply To:
Doug Werth <[log in to unmask]>
Date:
Thu, 8 Jul 1999 15:25:49 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
Several people pointed out to me in private messages that my PING command
file did not work in all cases. Due to things like routing configurations it
is possible to get messages other than what I was checking for. As
programmers know it is difficult to prove a negative, especially when you
really don't know every single possible negative that can occur!

Anyway, here is an updated version of my command file that will work a bit
better. (If you recall the original question was how to ping a large number
of IP addresses and only point out the ones that did not respond.)

parm IPAddr="192.1.1.1"
setvar InvVid,chr(27) + "&dB"
purge pingout,temp >$null
if finfo("PINGOUT","EXISTS") = false
   build pingout;rec=-80,,f,ascii
endif
file pingout,old;dev=disc
ping.net.sys "!IPAddr,3,64" >*PINGOUT
grep.hpbin.sys "'100 % packet loss' PINGOUT" >$null
if cjcw = 0 then
   echo !InvVId!IPAddr not found
else
   grep.hpbin.sys "'Unknown node' PINGOUT" >$null
   if cjcw = 0 then
      echo !InvVId!IPAddr not found
   else
      comment !IPAddr is a good address.
   endif
endif

As always, YMMV!

Doug.

Doug Werth                                     Beechglen Development Inc.
[log in to unmask]                                       Cincinnati, Ohio

The opinions expressed do not necessarily represent the views or opinions
of Beechglen Development. They might, but not necessarily. They represent
solely the opinions of the author.

ATOM RSS1 RSS2