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