services(4)services(4)NAMEservices - service name data base
DESCRIPTION
The file associates official service names and aliases with the port
number and protocol the services use. For each service a single line
should be present with the following information:
<official service name> <port number/protocol name> <aliases>
Port numbers 0 through 1023 are assigned by RFC 1700. This RFC also
lists the conventional use of various ports with numbers greater than
1023.
Aliases are other names under which a service is known. Library rou‐
tines such as can be invoked with a service alias instead of the ser‐
vice official name. For example:
In this example, can be invoked with instead of
instead of
Both produce the same results.
Items are separated by any number of blanks (space or tab characters in
any combination). The port number and protocol name are considered a
single item. A is used to separate the port and protocol (for example,
A character indicates the beginning of a comment. Characters from the
to the end of the line are not interpreted by routines which search the
file.
Service names can contain any printable character other than a white
space, newline, or comment character. Trailing blanks (spaces or tabs)
are allowed at the end of a line.
Not all services listed in this file are available on HP-UX.
EXAMPLESAUTHOR
was developed by the University of California, Berkeley.
FILESSEE ALSOgetservent(3N).
services(4)
