1.\" $OpenBSD: protocols.5,v 1.8 2000/10/26 00:37:05 aaron Exp $ 2.\" $NetBSD: protocols.5,v 1.3 1994/11/30 19:31:27 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.\" @(#)protocols.5 8.1 (Berkeley) 6/5/93 36.\" 37.Dd June 5, 1993 38.Dt PROTOCOLS 5 39.Os 40.Sh NAME 41.Nm protocols 42.Nd protocol name database 43.Sh DESCRIPTION 44The 45.Nm 46file contains information regarding the known protocols used in the 47.Tn DARPA 48Internet. 49For each protocol, a single line should be present 50with the following information: 51.Bd -unfilled -offset indent 52official protocol name 53protocol number 54aliases 55.Ed 56.Pp 57Items are separated by any number of blanks and/or tab characters. 58.Pp 59A hash mark 60.Pq Ql # 61indicates the beginning of a comment; subsequent characters up to the 62end of the line are not interpreted by the routines which search the file. 63.Pp 64Protocol names may contain any printable character other than a 65field delimiter, newline, or comment character. 66.Sh FILES 67.Bl -tag -width /etc/protocols -compact 68.It Pa /etc/protocols 69.El 70.Sh SEE ALSO 71.Xr getprotoent 3 72.Sh BUGS 73A name server should be used instead of a static file. 74Lines in 75.Pa /etc/protocols 76are limited to 77.Dv BUFSIZ 78characters (currently 1024). 79Longer lines will be ignored. 80.Sh HISTORY 81The 82.Nm 83file format appeared in 84.Bx 4.2 . 85