Socket timeouts without ALARM

ton has asked for the wisdom of the Perl Monks concerning the following question:

Does anyone know how to set socket timeouts on a Win32 machine? I am using the raw sockets, not IO::Socket (long story), and I'd like to avoid using the ALARM signal if possible. I've tried using setsockopt in the C-like way, e.g.

setsockopt($socket, SOL_SOCKET, SO_RCVTIMEO, 1000);
[download]

This call will not flag strict, and it won't return an undef signifying an error, but it doesn't seem to alter the functionality of $socket. I tried the same call with 1 as the timeout value, and had the same lack of effect. Any ideas?

-Ton
-----
Be bloody, bold, and resolute; laugh to scorn
The power of man...

Comment on Socket timeouts without ALARM Download Code

Replies are listed 'Best First'.
Re: Socket timeouts without ALARM by dws (Chancellor) on Nov 09, 2001 at 08:11 UTC
Does anyone know how to set socket timeouts on a Win32 machine? This questions comes up periodically (as yet another victim finds themself banging their head into the wall). One of the responses in LWP - timeout suggests that socket timeouts are only partially implemented on Win32. For further info, opinion, and conjecture, use Super Search to look for "socket timeout Win32" or "socket alarm win32". You'll get several hits that are worth looking at.	[reply]
Re: Socket timeouts without ALARM by mitd (Curate) on Nov 09, 2001 at 08:14 UTC
This is a little out there but you aren't connecting your local socket to an outside socket through a IP Masquarading router by any chance?? this one has bitten moi before. You may be getting timed out at the router. I only know the exact fix on a Linux based router. Assuming 2.2 > kernel nad IPCHAIN: ipchains -M -S 86400 60 120 which set tcp tcpfin udp timeouts. Again this probably a long shot. mitd-Made in the Dark 'My favourite colour appears to be grey.'	[reply]
ObPOE Plug by Fletch (Bishop) on Nov 09, 2001 at 07:36 UTC
POE is your friend when it comes to network programming. Trust POE. POE plugging aside, given that you're on Wintendo you're probably not going to find things behaving like they would on a real OS. And I seem to recall anectdotal stories about `$SIG{ALARM}` not playing nice on Wintendo as well.	[reply] [d/l]
Re: Socket timeouts without ALARM by kschwab (Vicar) on Nov 09, 2001 at 07:26 UTC
Set nonblocking mode and use select or just use IO::Socket, where the work is already done for you. Internally it's using nonblocking mode. The Timeout value is used for other operations, so you may want to reset it once the connection is up. `my $socket=IO::Socket::INET->new(PeerAddr => '127.0.0.1', PeerPort => 80, Proto => 'tcp', Timeout => 5);` [download]	[reply] [d/l]
(tye)Re: Socket timeouts without ALARM by tye (Sage) on Nov 09, 2001 at 10:06 UTC
IO::Socket's timeouts mostly require alarm and so are just silently ignored under Win32. - tye (but my friends call me "Tye")	[reply]
Re: (tye)Re: Socket timeouts without ALARM by kschwab (Vicar) on Nov 12, 2001 at 03:30 UTC
~~Perhaps this was true at some point, but at least for ActiveState's perl, IO::Socket uses non-blocking mode in conjuction with IO::Select to implement the timeouts.~~ Update: Well, this is true, the code is there, it uses non-blocking mode instead of alarm(), but it appears to be broken in Win32. <sigh>	[reply]


The stupid question is the question not asked
	PerlMonks