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