PROTOCOLS(5) BSD File Formats Manual PROTOCOLS(5)NAME
protocols -- protocol name data base
DESCRIPTION
The protocols file contains information regarding the known protocols used in the DARPA Internet. For each protocol a single line should be
present with the following information:
official protocol name
protocol number
aliases
Items are separated by any number of blanks and/or tab characters. A ``#'' indicates the beginning of a comment; characters up to the end of
the line are not interpreted by routines which search the file.
Protocol names may contain any printable character other than a field delimiter, newline, or comment character.
INTERACTION WITH DIRECTORY SERVICES
Processes generally find protocol records using one of the getprotoent(3) family of functions. On Mac OS X, these functions interact with
the DirectoryService(8) daemon, which reads the /etc/protocols file as well as searching other directory information services to determine
protocol name and number information.
FILES
/etc/protocols
SEE ALSO getprotoent(3), DirectoryService(8)HISTORY
The protocols file format appeared in 4.2BSD.
4.2 Berkeley Distribution June 5, 1993 4.2 Berkeley Distribution
Check Out this Related Man Page
SERVICES(5) BSD File Formats Manual SERVICES(5)NAME
services -- service name data base
DESCRIPTION
The services file contains information regarding the known services available in the DARPA Internet. For each service a single line should
be present with the following information:
official service name
port number
protocol name
aliases
Items are separated by any number of blanks and/or tab characters. The port number and protocol name are considered a single item; a ``/''
is used to separate the port and protocol (e.g. ``512/tcp''). A ``#'' indicates the beginning of a comment; subsequent characters up to the
end of the line are not interpreted by the routines which search the file.
Service names may contain any printable character other than a field delimiter, newline, or comment character.
INTERACTION WITH DIRECTORY SERVICES
Processes generally find service records using one of the getservent(3) family of functions, or using getaddrinfo(3). On Mac OS X, these
functions interact with the DirectoryService(8) daemon, which reads the /etc/services file as well as searching other directory information
services to determine service name, protocol, and port information.
FILES
/etc/services
SEE ALSO getservent(3), getaddrinfo(3), DirectoryService(8)HISTORY
The services file format appeared in 4.2BSD.
4.2 Berkeley Distribution June 5, 1993 4.2 Berkeley Distribution
iam doing a research on WAN so pliz any body can give me or tell me where i would find communication protocol map..thats all 7 layers..OIS MODEL (1 Reply)
I've been trying to set up the phantom protocol just to try it out. I compiled it fine, but when I ran it I got an error that the configuration file wouldn't load. I found that file didn't exist, so I created it with a blank file, but got this:
./phantom
Loading configuration file... (4 Replies)
Hello all,
planning to secure AIX sever by disabling insecure protocols/cipher suites; got the below requirements from secuirty team.
1.configure the server to disable support for DES and IDEA cipher suites
2.disable insecure TLS/SSL protocol support
Configure the server to... (4 Replies)
Source
a quick google search making clear that this isn't really new, and if we look at our bsd Forum we see that its the only operation systems forum with the last comment dated to June last year, whereas all the others have more recent comments.
One comment dated to 2014 is exactly what I... (10 Replies)