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