Configuring and Managing MPE/iX Internet Services (August 2002)

Chapter 1

Introduction to Internet Services

Overview of Internet Services

5. Check for any error messages, such as a module is missing, or a message telling you of a version

mismatch, for example:

Version levels differ in one or more modules. (NMERR 103)

Internet Services for the HP e3000 overall version = ?.??.??

Using Domain Name Resolver

To use the domain name resolver to resolve domain names to their IP addresses, you will need to configure a

set of ASCII files on each node that contain the necessary information. Refer to the “Configuring the DNS

Resolver” section of this chapter, or the HP e3000/iX Network Planning and Configuration Guide.

Sample Configuration Files

When you install or update to version C.60.00 of MPE/iX, a set of sample configuration files is automatically

copied to the NET group of the SYS account for you. For example, INCNFSMP is the name of the sample inetd

configuration file. These files were named and installed in this form to prevent overwriting any genuine

configuration files already in use.

To view the group of files installed in NET.SYS, enter:

:LISTFILE @.NET.SYS

To configure Internet Services, you will do one of two things:

• If there are configuration files already in use, you will add the information needed to use each of the

Internet Services to those files.

• If you are not already using Internet Services configuration files, you will use the sample configuration

files that were installed with the FOS as templates for your own set. In this case, you will use the COPY

command to create each of the configuration files, then create a symbolic link from a file name in the

POSIX name space to the actual file, which exists in the MPE name space. (Linking the files is explained

next.) Finally, you will edit the new configuration files to suit your needs.

Linking Configuration Files

The Internet Services software looks for some of its configuration files in the POSIX name space and not in

the MPE name space. For example, it accesses the /etc directory and looks for the file named inetd.conf to

read inetd configuration data. It does not look for the file INETDCNF.NET.SYS.

Rather than create two copies of the configuration file, one for each name space, Hewlett-Packard

recommends that you create a symbolic link from a POSIX-named file to the MPE-named file. The

instructions in the remainder of this manual describe this process. Linking the files, as opposed to making

another copy of each one, offers three important advantages.

• Linking the file ensures consistency of content because regardless of which name you use to access the

file, you will be reading or updating the same file.

• Giving the file a name in each name space allows you to view the file from either the POSIX or the MPE

name space, but it is recommended that you use an MPE text editor to make changes. This is due to

potential conflicts with the MPE/iX EOF marker if any lines are added using a POSIX editor program.

• Making the POSIX name point to the MPE name ensures that the file will be backed up with standard

MPE STORE procedures in case you haven’t modified your STORE command to back up new or changed files

in the POSIX name space.