|
|
1.1 root 1: .\" Copyright (c) 1983 The Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted provided
5: .\" that: (1) source distributions retain this entire copyright notice and
6: .\" comment, and (2) distributions including binaries display the following
7: .\" acknowledgement: ``This product includes software developed by the
8: .\" University of California, Berkeley and its contributors'' in the
9: .\" documentation or other materials provided with the distribution and in
10: .\" all advertising materials mentioning features or use of this software.
11: .\" Neither the name of the University nor the names of its contributors may
12: .\" be used to endorse or promote products derived from this software without
13: .\" specific prior written permission.
14: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
15: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
16: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
17: .\"
18: .\" @(#)protocols.5 6.4 (Berkeley) 6/23/90
19: .\"
20: .TH PROTOCOLS 5 "June 23, 1990"
21: .UC 5
22: .SH NAME
23: protocols \- protocol name data base
24: .SH DESCRIPTION
25: The
26: .I protocols
27: file contains information regarding the known protocols used in the DARPA
28: Internet. For each protocol a single line should be present
29: with the following information:
30: .HP 10
31: official protocol name
32: .br
33: .ns
34: .HP 10
35: protocol number
36: .br
37: .ns
38: .HP 10
39: aliases
40: .PP
41: Items are separated by any number of blanks and/or
42: tab characters. A ``#'' indicates the beginning of
43: a comment; characters up to the end of the line are
44: not interpreted by routines which search the file.
45: .PP
46: Protocol names may contain any printable
47: character other than a field delimiter, newline,
48: or comment character.
49: .SH FILES
50: /etc/protocols
51: .SH "SEE ALSO"
52: getprotoent(3N)
53: .SH BUGS
54: A name server should be used instead of a static file.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.