LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

Can't use comma instead of slash to separate port and protocol. 

Remove crufty text about use of comma instead of slash to separate
port and protocol.  It's not true as at glibc 2.8, and it's not
clear if/when it was ever true.
This commit is contained in:
Michael Kerrisk 2008-09-23 11:20:21 +02:00
parent afeb98dc09
commit c3ea9f2ded
2 changed files with 13 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Changes
View File

@ -79,3 +79,6 @@ services.5
mtk, after a note from Pavel Heimlich
Remove SEE ALSO references to nonexistent Guides to Yellow Pages
and Bind/Hesiod docs.
mtk
Crufty remove text about use of comma instead of slash to separate
port and protocol.

18
man5/services.5
View File

@ -150,14 +150,16 @@ and
.BR getservbyport (3).
However, this behavior should not be relied on.)
As a backwards compatibility feature, the slash (/) between the
.I port
number and
.I protocol
name can in fact be either a slash or a comma (,).
Use of the comma in
modern installations is deprecated.
.\" The following is not true as at glibc 2.8 (a line with a comma is
.\" ignored by getservent()); it's not clear if/when it was ever true.
.\" As a backwards compatibility feature, the slash (/) between the
.\" .I port
.\" number and
.\" .I protocol
.\" name can in fact be either a slash or a comma (,).
.\" Use of the comma in
.\" modern installations is deprecated.
.\"
This file might be distributed over a network using a network-wide
naming service like Yellow Pages/NIS or BIND/Hesiod.