Justin C. Walker wrote: > >> Do people agree that my suggestion of returning ENETDOWN is reasonable? > > > > Wow. There are other possibilities, EADDRNOTAVAIL or ECONNABORTED. > > It doesn't matter so long as it the errno is unique to this situation > > across all syscalls that might encounter it; ENETDOWN seems to meet > > this criteria. > > A thought: An attempt to reconnect will succeed, given the scenario > above, and ENETDOWN implies that the network is unavailable, so I don't > think this is a good response. ECONNABORTED might be better (and > EADDRNOTAVAIL isn't really germane).
Good point... ECONNABORTED is probably better. The particular error code can be determined later however... more interesting is the question, how should this be efficiently implemented? -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message