From: Raphael_Manfredi@pobox.com (Raphael Manfredi)
To: linux-kernel@vger.kernel.org
Subject: Re: setsockopt(SOL_SOCKET, SO_SNDBUF) broken on 2.4.18?
Date: 26 Feb 2002 12:54:03 GMT [thread overview]
Message-ID: <a5g0hb$12d$1@lyon.ram.loc> (raw)
In-Reply-To: <a5feh2$bvs$1@lyon.ram.loc> <E16fe55-0008UQ-00@the-village.bc.nu>
In-Reply-To: <E16fe55-0008UQ-00@the-village.bc.nu>
Quoting Alan Cox <alan@lxorguk.ukuu.org.uk> from ml.linux.kernel:
:> If I can't use the returned value from getsockopt(SO_SNDBUF) to do a
:> setsockopt(SO_SNDBUF), then it's broken! You'll have a hard time convincing
:> me otherwise.
:
:I'd like to see a standards document cite for that. The behaviour we follow
:is not atypical for a lot of ioctls and syscalls were you ask for one size
:and the kernel gives you its preferred variant. In the other cases I can
:think of the kernel also does not lie about its preferred variant
Practical experience shows that the test program I sent "works" (i.e.
returns the least surprising results) on OpenBSD, HP-UX 11.x. I'm having
a friend testing it for me on Solaris, but my guess is that it will work
there as well.
Raphael
next prev parent reply other threads:[~2002-02-26 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 21:08 setsockopt(SOL_SOCKET, SO_SNDBUF) broken on 2.4.18? Raphael Manfredi
2002-02-25 21:34 ` Richard B. Johnson
2002-02-25 22:19 ` Raphael Manfredi
2002-02-25 23:21 ` Alan Cox
2002-02-25 22:39 ` Alan Cox
2002-02-26 7:46 ` Raphael Manfredi
2002-02-26 9:39 ` Alan Cox
2002-02-26 12:54 ` Raphael Manfredi [this message]
2002-02-27 16:17 ` Horst von Brand
[not found] <E16_Tly-0006Va-00@the-village.bc.nu>
2002-02-26 0:11 ` Ton Hospel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='a5g0hb$12d$1@lyon.ram.loc' \
--to=raphael_manfredi@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.