Triode wrote: > Can you include more of the debug and the test methodology? I get those > messages but it does recover when the network connection is restored.
I found that you have the function connect_timeout() with a 5 secs timeout to make the connection. So when combined with sleep(5), the total timeout is actually 10 secs instead of 5. So I commented out sleep(5) (line 745 of slimproto.c) and recompiled. Now the client timed out as expected (it reaches "unable to connect to server 5"), and it sent out the discovery requests. At this point, it was able to connect to the new server once the new server was booted and operational. 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. ------------------------------------------------------------------------ Kuro's Profile: http://forums.slimdevices.com/member.php?userid=16701 View this thread: http://forums.slimdevices.com/showthread.php?t=97046 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
