1.\" Copyright (c) 1983, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. All advertising materials mentioning features or use of this software 13.\" must display the following acknowledgement: 14.\" This product includes software developed by the University of 15.\" California, Berkeley and its contributors. 16.\" 4. Neither the name of the University nor the names of its contributors 17.\" may be used to endorse or promote products derived from this software 18.\" without specific prior written permission. 19.\" 20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)services.5 8.1 (Berkeley) 6/5/93 33.\" 34.Dd June 5, 1993 35.Dt SERVICES 5 36.Os BSD 4.2 37.Sh NAME 38.Nm services 39.Nd service name data base 40.Sh DESCRIPTION 41The 42.Nm services 43file contains information regarding 44the known services available in the 45.Tn DARPA 46Internet. 47For each service a single line should be present 48with the following information: 49.Bd -unfilled -offset indent 50official service name 51port number 52protocol name 53aliases 54.Ed 55.Pp 56Items are separated by any number of blanks and/or 57tab characters. The port number and protocol name 58are considered a single 59.Em item ; 60a ``/'' is used to 61separate the port and protocol (e.g. ``512/tcp''). 62A ``#'' indicates the beginning of 63a comment; subsequent characters up to the end of the line are 64not interpreted by the routines which search the file. 65.Pp 66Service names may contain any printable 67character other than a field delimiter, newline, 68or comment character. 69.Sh NIS INTERACTION 70Access to the NIS 71.Pa services.byname 72map can be enabled by adding a single ``+'' on a line by itself 73in the 74.Pa /etc/services 75file. This causes the contents of the NIS services map to be inserted 76at the location where the ``+'' appears. 77.Sh FILES 78.Bl -tag -width /etc/services -compact 79.It Pa /etc/services 80The 81.Nm services 82file resides in 83.Pa /etc . 84.El 85.Sh SEE ALSO 86.Xr getservent 3 87.Sh BUGS 88A name server should be used instead of a static file. 89.Sh HISTORY 90The 91.Nm 92file format appeared in 93.Bx 4.2 . 94