in reply to UDP Client Multiple servers

What happens if you add use strict; at the top of your code and prefix your variables with my?

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

RIP Neil Armstrong

Replies are listed 'Best First'.
Re^2: UDP Client Multiple servers
by adwald (Initiate) on Oct 11, 2012 at 16:22 UTC

    I found the answer to my problem. I needed to eval whether a response was received in an amount of time and escape out if not.

    eval {
  local $SIG{ALRM} = sub { die 'Timed Out'; };
  alarm 1;

#receive response
  $handle->recv($newmsg, 1024) or die;
  $packet = Net::DHCP::Packet->new($newmsg);
  $data = $packet->toString();

  close $handle;
  alarm 0;
};

close $handle;

    [download]
[reply]
[d/l]

      That's not really a good idea. You could just set timeout option on the socket after creating it: 

      use Socket qw(SO_RCVTIMEO);
use POSIX qw(:errno_h);
...;
my $timeout = pack 'L!L!', $sec, $usec;
$handle->sockopt(SO_RCVTIMEO, $timeout);
...;
my $res = $handle->recv(...);
unless(defined $res) {
    if($! == EAGAIN or $! == EWOULDBLOCK) {
        say "time out";
    }
}

      [download]
[reply]
[d/l]

        Does the Timeout parameter to IO::Socket::INET->new() have the same effect as the sockopt() method?

        Maybe another WTDI.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom