xref: /netbsd-src/share/man/man5/services.5 (revision 23c8222edbfb0f0932d88a8351d3a0cf817dfb9e)
1.\"	$NetBSD: services.5,v 1.8 2003/08/07 10:31:17 agc 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. Neither the name of the University nor the names of its contributors
15.\"    may be used to endorse or promote products derived from this software
16.\"    without specific prior written permission.
17.\"
18.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28.\" SUCH DAMAGE.
29.\"
30.\"     @(#)services.5	8.1 (Berkeley) 6/5/93
31.\"
32.Dd June 5, 1993
33.Dt SERVICES 5
34.Os
35.Sh NAME
36.Nm services
37.Nd service name data base
38.Sh DESCRIPTION
39The
40.Nm services
41file contains information regarding
42the known services available in the
43.Tn DARPA
44Internet.
45For each service a single line should be present
46with the following 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
55tab characters.  The port number and protocol name
56are considered a single
57.Em item ;
58a slash
59.Pq Dq /
60is used to separate the port and protocol (e.g.
61.Dq 512/tcp ) .
62A hash
63.Pq Dq \&#
64indicates the beginning of
65a comment; subsequent characters up to the end of the line are
66not interpreted by the routines which search the file.
67.Pp
68Service names may contain any printable
69character other than a field delimiter, newline,
70or comment character.
71.Sh FILES
72.Bl -tag -width /etc/services -compact
73.It Pa /etc/services
74The
75.Nm services
76file resides in
77.Pa /etc .
78.El
79.Sh SEE ALSO
80.Xr getservent 3
81.Sh HISTORY
82The
83.Nm
84file format appeared in
85.Bx 4.2 .
86.Sh BUGS
87A name server should be used instead of a static file.
88