matthew green wrote:
don't getsockopt/setsockopt take socklen_t? oh ouch. their manual pages claim socklen_t but their implementations use unsigned int. that should really be fixed. socklen_t is the right type.
I think it should not be part of the socket options KPI changes; can you please take care of it and I'll adapt the diff afterwards? -e.