At 11:27 AM 5/12/2006 -0400, Ng, Bill wrote:
> I have many scripts that have to hit every machine in my domain
>.. about 2400. I can't use Net::Ping to test the alive status of the
>boxes because our internal DNS system is a real PITA to clean up and
>using as-is will leave me with bad resul
al Message-
From: Glenn Linderman [mailto:[EMAIL PROTECTED]
Sent: Friday, May 12, 2006 2:52 PM
To: Ng, Bill
Cc: Peter Eisengrein; perl-win32-users@listserv.ActiveState.com
Subject: Re: Network Timeouts
How about Net::Ping used with
$p->ping($ip, $timeout);
instead of $host... if you know t
Read my second sentence
Bill in Brooklyn
-Original Message-
From: Peter Eisengrein [mailto:[EMAIL PROTECTED]
Sent: Friday, May 12, 2006 12:29 PM
To: Ng, Bill; perl-win32-users@listserv.ActiveState.com
Subject: RE: Network Timeouts
>
> Dilemma,
>
> I have
Thanks John ... that sux, but thanks =)
Bill
-Original Message-
From: John Serink [mailto:[EMAIL PROTECTED]
Sent: Friday, May 12, 2006 12:14 PM
To: Ng, Bill; perl-win32-users@listserv.ActiveState.com
Subject: RE: Network Timeouts
You're only option is to spawn threads and detach
You're only option is to spawn threads and detach them. Have them write
their results to a shared hash or something and define your own
timeout...if you don't see the result from that thread ID in X seconds,
declare it timed out and forget about it. When it actually does timeout
is will error and t
>
> Dilemma,
>
> I have many scripts that have to hit every machine in my domain
> .. about 2400. I can't use Net::Ping to test the alive status of the
> boxes because our internal DNS system is a real PITA to clean up and
> using as-is will leave me with bad results.
>
> For now,
