HP-UX LAN Administrator's Guide (Feburary 2007)

Table Of Contents
Manually Installing and Configuring HP-UX LANDRAFT COPY
Activating Optional Network Features
Chapter 432
alias
Common name or names for the service. An alias is a substitute for
service_name
. Alias names are optional.
/etc/services Format
Lines cannot start with a blank or tab character.
Fields can have any number of blanks or tab characters separating them.
Comments are allowed and designated by a pound sign (#) character preceding the
comment text.
Trailing blank and tab characters are allowed.
Blank line entries are allowed.
Only one entry per line is allowed.
/etc/services Permissions
The /etc/services file should be owned by user bin, group bin, and it should have 0x444
(-r--r--r--) access permission.
Refer to the /etc/services file for examples of actual format and contents. For more
information on /etc/services, refer to the services(4) man page in the HP-UX Reference
Pages.
/etc/services Example
The following /etc/services entry contains the service name, port number, protocol name,
and alias name for the shell service.
shell 514/tcp cmd #remote command, no passwd used
Creating the /etc/networks File
The /etc/networks file associates network addresses with mnemonic names and alias
names. The /etc/networks file contains the name and address of known internet networks
with which your host can communicate. The HP-UX LAN diagnostic netstat and the route
command use the /etc/networks file. You must configure this file for your host if you want
route or netstat to use symbolic network names instead of addresses.
You can create an /etc/networks file two ways:
From scratch, entering the known nodes in the format shown below.
By copying the file from another node.