services(4) [hpux man page]

services(4)						     Kernel Interfaces Manual						       services(4)

NAME

       services - 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 routines 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.

EXAMPLES

AUTHOR

       was developed by the University of California, Berkeley.

FILES

SEE ALSO

       getservent(3N).

																       services(4)

services(4)							   File Formats 						       services(4)

NAME

       services - Internet services and aliases

SYNOPSIS

       /etc/inet/services

       /etc/services

DESCRIPTION

       The services file  is a local source of information regarding each service available through the Internet. The services file can be used in
       conjunction with or instead of other services sources, including the NIS maps "services.byname" and the NIS+  table  "services."   Programs
       use the getservbyname(3SOCKET) routines to access this information.

       The services file contains an entry for each service. Each entry has the form:

	 service-name	port/protocol	aliases

       service-name	This is the official Internet service name.

       port/protocol	This field is composed of the port number and protocol through which the service is provided, for instance, 512/tcp.

       aliases		This is a list of alternate names by which the service might be requested.

       Fields  can  be separated by any number of SPACE and/or TAB characters. A number sign (#) indicates the beginning of a comment; any charac-
       ters that follow the comment character up to the end of the line are not interpreted by routines which search the file.

       Service names may contain any printable character other than a field delimiter, a NEWLINE, or a comment character.

       Any changes to a port assignment do not affect the actual port registration of the service.

FILES

       /etc/nsswitch.conf    configuration file for name-service switch

SEE ALSO

       getservbyname(3SOCKET), inetd.conf(4), nsswitch.conf(4)

NOTES

       /etc/inet/services is the official SVR4 name of the services file.  The symbolic link /etc/services exists for BSD compatibility.

SunOS 5.11							    12 Oct 2000 						       services(4)