Bug 624399 – rresvport man entry misleading

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 624399 - rresvport man entry misleading

Summary:	rresvport man entry misleading

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	man-pages (Show other bugs)
Sub Component:
Version:	12
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Ivana Varekova
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-08-16 06:19 EDT by JW
Modified:	2010-09-08 09:21 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-09-08 09:21:34 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description JW 2010-08-16 06:19:34 EDT

Description of problem:
The man entry for rresvport states: "The rresvport() function is used to obtain a socket with a privileged address bound to it." Then it continues to state: "Privileged Internet ports are those in the range 0 to 1023." All of which is true. But in actual fact the notes fail to mention that rresvport() returns a port number in the range 512 through 1023 only.


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

How reproducible:
Always

Steps to Reproduce:
1. man rresvport

  
Actual results:
See description


Expected results:
It should instead state: "The rresvport() function is used to obtain a socket with its port number bound to an available value between 512 and 1023 inclusive, being a subset of the privileged port range (0 through 1023).

Additional info:

Comment 1 Ivana Varekova 2010-09-08 09:21:34 EDT

Thanks fixed in man-pages-3.26-1.

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