xref: /netbsd-src/share/man/man5/protocols.5 (revision 48360965f30c307b6836d0d898d15ce6c1d9b387)
1.\"	$NetBSD: protocols.5,v 1.7 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.\"     @(#)protocols.5	8.1 (Berkeley) 6/5/93
31.\"
32.Dd June 5, 1993
33.Dt PROTOCOLS 5
34.Os
35.Sh NAME
36.Nm protocols
37.Nd protocol name data base
38.Sh DESCRIPTION
39The
40.Nm protocols
41file contains information regarding the known protocols used in the
42.Tn DARPA
43Internet.  For each protocol a single line should be present
44with the following information:
45.Bd -unfilled -offset indent
46official protocol name
47protocol number
48aliases
49.Ed
50.Pp
51Items are separated by any number of blanks and/or
52tab characters.  A hash
53.Pq Dq \&#
54indicates the beginning of
55a comment; characters up to the end of the line are
56not interpreted by routines which search the file.
57.Pp
58Protocol names may contain any printable
59character other than a field delimiter, newline,
60or comment character.
61.Sh FILES
62.Bl -tag -width /etc/protocols -compact
63.It Pa /etc/protocols
64The
65.Nm protocols
66file resides in
67.Pa /etc .
68.El
69.Sh SEE ALSO
70.Xr getprotoent 3
71.Sh HISTORY
72The
73.Nm
74file format appeared in
75.Bx 4.2 .
76.Sh BUGS
77A name server should be used instead of a static file.
78