re: Socket options KPI

[matthew green]

   > so_setsockopt:
   > Shouldn't valsize be the normal size_t? Does socklen_t really make sense
   > here? 
   
   I vaguely remember there was a reason for this socklen_t... maybe the 
   original FreeBSD changes. Anyway, I'm thinking it should be unsigned
   int, actually, to fit the len parameter to sys_setsockopt() and
   sys_getsockopt(), no?


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.


mrg.