From: "David S. Miller" <davem@redhat.com>
To: Manfred Bartz <mbartz@optushome.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: setsockopt(..,SO_RCVBUF,..) sets wrong value
Date: Thu, 2 Aug 2001 06:12:03 -0700 (PDT) [thread overview]
Message-ID: <15209.20899.731395.581746@pizda.ninka.net> (raw)
In-Reply-To: <20010802103447.992.qmail@optushome.com.au>
In-Reply-To: <20010802103447.992.qmail@optushome.com.au>
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.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-08-02 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 10:34 setsockopt(..,SO_RCVBUF,..) sets wrong value Manfred Bartz
2001-08-02 13:12 ` David S. Miller [this message]
[not found] <no.id>
2001-08-02 14:26 ` Alan Cox
2001-08-02 14:38 Andries.Brouwer
2001-08-02 15:59 ` Richard B. Johnson
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=15209.20899.731395.581746@pizda.ninka.net \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbartz@optushome.com.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).