I took your sample and experimented with it. 
#!/usr/bin/perl

use strict;
use warnings;
use LWP::UserAgent;

my $mac = 'http://www.perlmonks.org/?node_id=848086';

eval {
    do {
        my $request    = HTTP::Request->new( GET => $mac );
        my $ua         = LWP::UserAgent->new;
        $ua->timeout(30);
        $ua->env_proxy;
        my $response = $ua->request($request);
        if ( $response->is_success ) {
            print $response->decoded_content;
        }
        else {
            print $response->status_line, "\n";
        }
    };
}

[download]
Update: I took out $SIG{ALRM}. It didn't work and seemed unnecessary. Added print to status_line and timeout. "status_line' works better.

In reply to Re: The curious case of LWP - the SIG{ALRM} robber by Khen1950fx
in thread The curious case of LWP - the SIG{ALRM} robber by MonkeyMonk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.