Triode wrote: > 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?
I added LOG_INFO code to utils.c and I also put back sleep(5) in slimproto.c. Here is what I see when server IP is changed: [00:54:16.480556] send_packet:92 failed writing to socket: Broken pipe [00:54:16.480872] slimproto_run:481 error reading from socket: closed [00:54:26.586495] slimproto:745 unable to connect to server 0 [00:54:36.588881] slimproto:745 unable to connect to server 1 [00:54:46.589753] slimproto:745 unable to connect to server 2 [00:54:48.618917] connect_timeout:212 sock: 5 error: 113 [00:54:48.619468] slimproto:754 connected [00:54:48.619903] sendHELO:114 mac: 00:25:31:02:c4:14 So for some strange reason, select() returns 1 saying the socket is writable (the server at the old IP addr), and getsockopt() returns error code 113. According to errno.h, 113 is host unreachable. #define EHOSTUNREACH 113 /* No route to host */ The strange thing is that if I removed sleep(5), select will never return 1 with the old sock connection. ------------------------------------------------------------------------ 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
