diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2012-07-23 15:00:23 +0200 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2012-07-23 15:00:23 +0200 |
| commit | 3de2d3be31dad253cd6cbda92f7bb903b3dd6395 (patch) | |
| tree | e4632d72ad2149f3e7ff3f139592cbf9a302937a | |
| parent | 5011ecfd2bb9a7579cf83d3a41635a4c7ca27eeb (diff) | |
| download | man-pages-3de2d3be31dad253cd6cbda92f7bb903b3dd6395.tar.gz | |
socket.7: srcfix
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
| -rw-r--r-- | man7/socket.7 | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/man7/socket.7 b/man7/socket.7 index 88a4fda539..7097ae2fc7 100644 --- a/man7/socket.7 +++ b/man7/socket.7 @@ -397,6 +397,10 @@ when it is set using .BR setsockopt (2), and this doubled value is returned by .BR getsockopt (2). +.\" The following thread on LMKL is quite informative: +.\" getsockopt/setsockopt with SO_RCVBUF and SO_SNDBUF "non-standard" behaviour +.\" 17 July 2012 +.\" http://thread.gmane.org/gmane.linux.kernel/1328935 The default value is set by the .I /proc/sys/net/core/rmem_default file, and the maximum allowed value is set by the @@ -493,6 +497,7 @@ Sets or gets the maximum socket send buffer in bytes. The kernel doubles this value (to allow space for bookkeeping overhead) when it is set using .\" Most (all?) other implementations do not do this -- MTK, Dec 05 +.\" See also the comment to SO_RCVBUF (17 Jul 2012 LKML mail) .BR setsockopt (2), and this doubled value is returned by .BR getsockopt (2). |