LDP: Update original to LDP v3.79

[linuxjm/LDP_man-pages.git] / original / man5 / services.5

diff --git a/original/man5/services.5 b/original/man5/services.5
index 7aee726..a7a62e0 100644 (file)
--- a/original/man5/services.5
+++ b/original/man5/services.5
@@ -1,9 +1,8 @@
-.\" Hey Emacs! This file is -*- nroff -*- source.
-.\"
 .\" This manpage is Copyright (C) 1996 Austin Donnelly <and1000@cam.ac.uk>,
 .\" with additional material Copyright (c) 1995 Martin Schulze
 .\"     <joey@infodrom.north.de>
 .\"
+.\" %%%LICENSE_START(VERBATIM)
 .\" Permission is granted to make and distribute verbatim copies of this
 .\" manual provided the copyright notice and this permission notice are
 .\" preserved on all copies.
@@ -23,6 +22,7 @@
 .\"
 .\" Formatted or processed versions of this manual, if unaccompanied by
 .\" the source, must acknowledge the copyright and authors of this work.
+.\" %%%LICENSE_END
 .\"
 .\"   This manpage was made by merging two independently written manpages,
 .\"   one written by Martin Schulze (18 Oct 95), the other written by
@@ -56,8 +56,8 @@ protocols when assigning a port number.
 Therefore, most entries will
 have two entries, even for TCP-only services.
 
-Port numbers below 1024 (so-called "low numbered" ports) can only be
-bound to by root (see
+Port numbers below 1024 (so-called "low numbered" ports) can be
+bound to only by root (see
 .BR bind (2),
 .BR tcp (7),
 and
@@ -138,7 +138,7 @@ not stripped.
 can be any printable characters excluding space and tab.
 However, a conservative choice of characters should be used to minimize
 compatibility problems.
-E.g., a\-z, 0\-9, and hyphen (\-) would seem a
+For example, a\-z, 0\-9, and hyphen (\-) would seem a
 sensible choice.
 
 Lines not matching this format should not be present in the
@@ -152,7 +152,7 @@ However, this behavior should not be relied on.)
 
 .\" 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
+.\"   As a backward compatibility feature, the slash (/) between the
 .\"   .I port
 .\"   number and
 .\"   .I protocol
@@ -167,9 +167,9 @@ A sample
 .B services
 file might look like this:
 .RS
+.ft CW
 .nf
 .sp
-.ta 3i
 netstat         15/tcp
 qotd            17/tcp          quote
 msp             18/tcp          # message send protocol
@@ -180,6 +180,7 @@ ftp             21/tcp
 # 22 \- unassigned
 telnet          23/tcp
 .fi
+.ft
 .RE
 .SH FILES
 .TP
@@ -206,7 +207,7 @@ Definition of
 .\"    and
 .\"    .BR getservbyport (3).
 .\"    However, this will also cause the next line to be mis-parsed.
-.SH "SEE ALSO"
+.SH SEE ALSO
 .BR listen (2),
 .BR endservent (3),
 .BR getservbyname (3),
@@ -217,4 +218,13 @@ Definition of
 .BR protocols (5),
 .BR inetd (8)
 
-Assigned Numbers RFC, most recently RFC\ 1700, (AKA STD0002)
+Assigned Numbers RFC, most recently RFC\ 1700, (AKA STD0002).
+.SH COLOPHON
+This page is part of release 3.79 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.