There's no guarantee that a socket was involved at this point, so avoid displaying...
authorYang Tse <yangsita@gmail.com>
Mon, 13 Oct 2008 06:16:02 +0000 (06:16 +0000)
committerYang Tse <yangsita@gmail.com>
Mon, 13 Oct 2008 06:16:02 +0000 (06:16 +0000)
commitc3a959cc37d69f2634fa3b6a0a4775c7cf08ce27
tree72f57487c1f786089a99bbac6ba812627d7b9502
parentca70beec479f40f87610b964ebe0bab4ed07edac
There's no guarantee that a socket was involved at this point, so avoid displaying any error code.

And on the other hand a message after setsockopt() certainly must use SOCKERRNO.
lib/connect.c