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 April 4, 2010 36.Dt SERVICES 5 37.Os 38.Sh NAME 39.Nm services 40.Nd service name data base 41.Sh DESCRIPTION 42The 43.Nm 44file contains information regarding 45the known services available in the 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 tab characters. 57The port number and protocol name are considered a single 58.Em item ; 59a ``/'' is used to 60separate the port and protocol (e.g.\& ``512/tcp''). 61A ``#'' indicates the beginning of 62a comment; subsequent characters up to the end of the line are 63not interpreted by the routines which search the file. 64.Pp 65Service names may contain any printable 66character other than a field delimiter, newline, 67or comment character. 68.Pp 69If 70.Dq db 71is specified as source in the 72.Xr nsswitch.conf 5 , 73.Pa /var/db/services.db 74is searched. 75The database in 76.Pa /var/db/services.db 77needs to be updated with 78.Xr services_mkdb 8 79after changes to the services file have been applied. 80.Sh NIS INTERACTION 81Access to the NIS 82.Pa services.byname 83map can be enabled by adding a single ``+'' on a line by itself 84in the 85.Pa /etc/services 86file. 87This causes the contents of the NIS services map to be inserted 88at the location where the ``+'' appears. 89.Sh FILES 90.Bl -tag -width /etc/services -compact 91.It Pa /etc/services 92The 93.Nm 94file resides in 95.Pa /etc . 96.El 97.Sh SEE ALSO 98.Xr getservent 3 99.Xr nsswitch.conf 5 100.Xr services_mkdb 8 101.Sh HISTORY 102The 103.Nm 104file format appeared in 105.Bx 4.2 . 106.Sh BUGS 107A name server should be used instead of a static file. 108