Re: setsockopt(..,SO_RCVBUF,..) sets wrong value

[Ton Hospel]

In article <[e-mail]>,
	"David S. Miller" <[e-mail]> writes:
> Manfred Bartz writes:
> > When I do a setsockopt(..,SO_RCVBUF,..) and then read the value back
> > with getsockopt(), the reported value is exactly twice of what I set.
> 
> That's correct.  Please search the list archives to learn why things
> behave this way and why they are not going to change.
> 
> I wish that this long winded, and often occuring thread not occur
> again.
> 

Why not simply divide it by two again before returning it on a get ?

What semantics you give exactly to the value is your business, but the
get/set assymetry is just pointless weirdness.