|
|
|
good chemistry is complicated, and a little bit messy -LW |
|
| PerlMonks |
A better way to test network elementsby tradez (Pilgrim) |
| on Mar 07, 2002 at 18:34 UTC ( #150080=perlquestion: print w/ replies, xml ) | Need Help?? |
|
tradez has asked for the
wisdom of the Perl Monks concerning the following question:
Fellow Monks,
  &nsbp I am sure that there is a better way to do what I am trying to do. I am writing a script that allows people to input an IP from our call center and do simple tests. Forward and Reverse NS Lookup, Ping, and the killer, Traceroute. Pretty simple stuff, but the traceroute is killing me. I am on sunOS 5.7, and the traceroute binary I have running does not seem to have a way to die. Basically, if someone puts in a bad a ip, ie 1.2.3.4 it will get to the gateway and just hang. Currently I work around this by A simple, yet archaic answer to an issue that I know can be solved more easily. I was thinking about just using a system() call, sleeping, then checking it to see if I got results, but that would really not speed things up much. Please help me to find a better way! Tradez "Never underestimate the predicability of stupidity" - Bullet Tooth Tony, Snatch (2001)
Back to
Seekers of Perl Wisdom
|
|
||||||||||||||||||||||||