Kuro wrote: > So seems like it is fixed. But from what I can see, connect_timeout() > was returning a value >=0 to cause the previous error. In the > connect_timeout() code, the function that causes this is the > getsockopt(), I think you were trying to retrieve the error code for the > sock in question and it returned 0 (no error) hence causing the timeout > code not to function.
If it is timing out at 5 seconds in select I would have expected select to return with 0? Can you instrument that and see what is going on with the select response? ------------------------------------------------------------------------ Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=97046 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
