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.

diff --git a/Changes b/Changes
index e82215ea41b9992a2ce904829729c345547aa5c2..7ac90a9127748a9113323a08c40d96dbdc937933 100644 (file)
--- a/Changes
+++ b/Changes
@@ -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.

diff --git a/man5/services.5 b/man5/services.5
index b7ac9e69211102bd25f5a46c9787fb05ba32fac8..aea1a954558fc09e9acb4bcf41869b24942ca253 100644 (file)
--- a/man5/services.5
+++ b/man5/services.5
@@ -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.