LDM Preinstallation Steps

The platform on which the LDM package is to be installed must be prepared in advance prior to the installation. If your platform already has an LDM installation, then, in all likelihood, the preinstallation steps have already been completed. If you are installing the first LDM package on your platform, however, then the steps described here should be done before the LDM distribution is unpacked.

Contents


Steps to Perform as root

  1. Create the LDM user-account

  2. (Optional) Edit file /etc/services

  3. (Optional) Edit file /etc/rpc

  4. Edit file /etc/syslog.conf

Create the LDM user-account

This is, necessarily, a system-dependent operation. Consult with your system's administrator, if necessary.

Keep the following in mind when creating the account:

Workshop-specific instructions.

(Optional) Edit file /etc/services

Add the following line:

ldm 388/tcp ldmd  # UCAR Unidata LDM

This allows programs such as netstat(1) to use "ldm" and "ldmd" instead of "388" (the LDM port number).

Workshop-specific instructions.

(Optional) Edit file /etc/rpc

Add the following line:

ldm 300029 ldmd

This allows programs such as rpcinfo(1) to use "ldm" and "ldmd" instead of "300029" (the LDM program number for RPC).

Workshop-specific instructions.

Edit file /etc/syslog.conf

The LDM uses the system logging daemon, syslogd(8), to write error messages using the localn logging facility Such messages should end up in the LDM logfile.

Workshop-specific instructions.


Steps to Perform as the LDM User

  1. Become the LDM user in the user's home-directory

  2. Edit the LDM user's profile-file

Become the LDM user in the user's home-directory

For example:

su - ldm

The "-" option guarantees that the current working directory is the LDM user's home-directory. Alternatively, just log-out and log back in as the LDM user.

Workshop-specific instructions.

Edit the LDM user's profile-file

Add the following lines to the appropriate profile-file of the LDM user's user-shell. If more than one person might manage the LDM, then it's a good idea to add both of the following snippets in case the other person prefers a different user-shell.

SysManPath is the pathname for the manual-pages of the operating system (e.g., /usr/man or /usr/share/man). The MANPATH environment variable might already contain this path.

The UDUNITS_PATH environment variable conains the pathname of the database of the UDUNITS package. It should only be necessary to define this variable if your LDM system will decode incoming products using the gribtonc(1) utility (i.e. if an exec entry that uses gribtonc exists in a pqact configuration-file).

If necessary, modify the setting of the PATH environment variable above to ensure that the necessary build utilities can be found.

Don't forget to source the profile-file so that the modifications take effect. For example: