Why bother Google when your program can timeout while connecting to the real destination?
This has also the advantage that the protocol used for testing is the same as later on for
communication - which can be a good idea in the presence of firewalls.
More specific advice might be possible if you tell us more about the protocol/application.
A Super Search for connection timeout delivers some more suggestions.
Update:
To check for presence of a server that is not confused if someone
is ringing off without saying a word...
sub check_port {
my $host = shift; # hostname or hostname:port
my $timeoutseconds = shift || 1;
my $proto = "tcp";
my $handle = IO::Socket::INET->new('PeerAddr'=>$host,'Timeout'=>$tim
+eoutseconds, 'Proto'=>$proto);
if (defined $handle && $handle) {
$handle->close();
return 1; # port in use
}
return 0; # not reachable or timeout
}
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|