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.\" $FreeBSD$ 34.\" 35.Dd June 5, 1993 36.Dt SERVICES 5 37.Os BSD 4.2 38.Sh NAME 39.Nm services 40.Nd service name data base 41.Sh DESCRIPTION 42The 43.Nm services 44file contains information regarding 45the known services available in the 46.Tn DARPA 47Internet. 48For each service a single line should be present 49with the following information: 50.Bd -unfilled -offset indent 51official service name 52port number 53protocol name 54aliases 55.Ed 56.Pp 57Items are separated by any number of blanks and/or 58tab characters. The port number and protocol name 59are considered a single 60.Em item ; 61a ``/'' is used to 62separate the port and protocol (e.g. ``512/tcp''). 63A ``#'' indicates the beginning of 64a comment; subsequent characters up to the end of the line are 65not interpreted by the routines which search the file. 66.Pp 67Service names may contain any printable 68character other than a field delimiter, newline, 69or comment character. 70.Sh NIS INTERACTION 71Access to the NIS 72.Pa services.byname 73map can be enabled by adding a single ``+'' on a line by itself 74in the 75.Pa /etc/services 76file. This causes the contents of the NIS services map to be inserted 77at the location where the ``+'' appears. 78.Sh FILES 79.Bl -tag -width /etc/services -compact 80.It Pa /etc/services 81The 82.Nm services 83file resides in 84.Pa /etc . 85.El 86.Sh SEE ALSO 87.Xr getservent 3 88.Sh BUGS 89A name server should be used instead of a static file. 90.Sh HISTORY 91The 92.Nm 93file format appeared in 94.Bx 4.2 . 95