|
|
The services file associates an official service name and
alias with the port number and protocol that a service uses. You
will edit the services file for each new service that you want to
add to your system. The remaining chapters in this book, which describe
the configuration of individual services, will assume that you know
the following information. And, of course, you can refer back to
this section as needed.
You may already have a services file installed on your system.
If you know that you have such a file, and it is accessible by the
POSIX file name /etc/services you may skip these steps.
If you do not have a services file, follow these steps to
create the file and link to it. If you have such a file, but are
unsure whether or not it is linked, perform step 2 only.
Create your own services file by using the COPY command to
rename the sample file. Enter:
:COPY SERVSAMP.NET.SYS, SERVICES.NET.SYS
Create a symbolic link from a file named /etc/services in
the POSIX name space to SERVICES.NET.SYS. Enter:
:NEWLINK /etc/services, SERVICES.NET.SYS
Use an MPE text editor to edit the file.
Open the services file with an MPE text editor.
The contents will resemble the following:
# This file contains the information about the
# services provided.
# Copy this file to SERVICES.NET.SYS
# if that file does not already exist.
#
# The form for each entry is:
# <official service name> <port number/protocol name> <aliases>
#
# See the Configuring and Managing MPE/iX Internet Services
# Manual for more information (HP Part No. 32650-90835).
#
# Note: The entries cannot be preceded by a blank space.
#
echo 7/tcp # Echo
echo 7/udp #
discard 9/tcp sink null # Discard
discard 9/udp sink null #
daytime 13/tcp # Daytime
daytime 13/udp #
chargen 19/tcp ttytst source # Character Generator
chargen 19/udp ttytst source #
ftp 21/tcp
telnet 23/tcp
time 37/tcp timeserver # Time
time 37/udp timeserver #
domain 53/tcp nameserver # Domain Name Service
domain 53/udp nameserver #
bootps 67/udp # Bootstrap Protocol Server
bootpc 68/udp # Bootstrap Protocol Client
tftp 69/udp # Trivial File Transfer Protocol
DAServer 987/tcp # SQL distributed access
shell 514/tcp cmd # Remote command no password used
For the service that you are installing, check the file to see if
it has the appropriate entry. (Each chapter in the remainder of this
manual has this information.) If not, enter the line in the file
using the "Editing Tips" section, next, as a guideline.
 |
NOTE: For more information on FTP, refer to Installing
and Managing HP ARPA File Transfer Protocol Network Manager's
Guide or HP ARPA File Transfer Protocol User's Guide.
|
Save the file and exit the editor program.
Editing Tips
When you are editing the services file, use the following
information to enter the information correctly.
If you find the line that describes the service you are
configuring, but it has been "commented out" (that is, preceded by a
pound sign, #), the service has not yet been enabled. To
enable it, simply delete the pound sign and any
spaces that precede the service name.
If you need to type the line into the file:
use only lower case characters
enter the service name in the first column without any leading
spaces
separate the individual fields on the line with any number of
blanks or tab characters to improve readability
|