Re: IO modules possibly causing issues in Net::DNS module

About the issue with this other script and the timout of 5, I couldn't find any mention in the docs whether the timeout is given in seconds or milliseconds or whatever. A too short timeout might just produce a queue not emptied I imagine.

You could change the timeout to 5000 and see if it works then.

About your main problem: You didn't really say whether the original server-resolve script worked or if it has the same problem as the ported script

Comment on Re: IO modules possibly causing issues in Net::DNS module

Replies are listed 'Best First'.
Re^2: IO modules possibly causing issues in Net::DNS module by N3WWN (Initiate) on Apr 19, 2010 at 17:08 UTC
Hi jethro! The scripts have been working fine for years on the "old system" and the timeout value is in seconds (or was with the versions in use on the "old system"). My issues is not a matter of the script timing out or not, but rather it's a matter of IO::Select's can_read() function never returning, even when there is data waiting in the recv queue. If can_read() would return, the script would work normally, but can_read() is hanging indefinitely. Thanks for your response! -Rich	[reply]

Replies are listed 'Best First'.

Re^2: IO modules possibly causing issues in Net::DNS module
by N3WWN (Initiate) on Apr 19, 2010 at 17:08 UTC

Hi jethro!

The scripts have been working fine for years on the "old system" and the timeout value is in seconds (or was with the versions in use on the "old system").

My issues is not a matter of the script timing out or not, but rather it's a matter of IO::Select's can_read() function never returning, even when there is data waiting in the recv queue. If can_read() would return, the script would work normally, but can_read() is hanging indefinitely.

Thanks for your response!

-Rich

[reply]