It seems the warning is needed only when a socket smaller than that
requested is created. Then, the Linux oddity would not be apparent.
Kent
--On July 22, 2003 02:28:42 PM <[EMAIL PROTECTED]> wrote:
This is a Linux oddity. If you look at
http://www.ussg.iu.edu/hypermail/linux/kernel/0202.3/0292.html you'll see
a discussion. The code calls setsockopt to suggest the desired value and
then calls getsockopt to see what it was actually set to - I didn't want
you to request 1M and, unbeknownst to you, use 1K. Maybe I should get rid
of the warning. Opinions?
