Bug 163120 - socket(7) is wrong regarding RCVLOWAT
socket(7) is wrong regarding RCVLOWAT
Product: Fedora
Classification: Fedora
Component: man-pages (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ivana Varekova
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2005-07-12 21:00 EDT by Andy Grover
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-09 04:42:29 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andy Grover 2005-07-12 21:00:20 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:
The man pages say that socket options SO_SNDLOWAT and SO_RCVLOWAT are not changeable in Linux and attempting to set them will return ENOPROTOOPT.

SNDLOWAT is not settable but RCVLOWAT is (I tried it), and the man page should reflect this.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
int i, j, lowat;
lowat = 1000;

i = socket(PF_INET, SOCK_STREAM, 0);

j = setsockopt(i, SOL_SOCKET, SO_RCVLOWAT, &lowat, sizeof(lowat));

if (!j)
  printf("the manpage is wrong\n");

Additional info:
Comment 3 Ivana Varekova 2005-09-12 05:13:53 EDT
Thank you for your notice. This man page is fixed in the last version of
man-pages (2.07-3).
The fixed version is:

              Specify the minimum number of bytes in  the  buffer  until  the
              socket  layer  will pass the data to the protocol (SO_SNDLOWAT)
              or the user on receiving (SO_RCVLOWAT).  Their argument size is
              always  fixed  to  1  byte.   SO_SNDLOWAT  is not changeable in
              Linux.  SO_RCVLOWAT option is changeable only since Linux  2.4.
              getsockopt  is able to read them; setsockopt will always return

Note You need to log in before you can comment on or make changes to this bug.