LDM Binary Installation

Contents:

  1. Become the LDM user
  2. Obtain the distribution
  3. Unpack the distribution
  4. Vet the ldmadmin script
  5. Make rpc.ldmd and hupsyslog set-uid-root
  6. Copy configuration files if first-time LDM

Become the LDM user

Follow this advice on becoming the LDM user.

Obtain the LDM Binary-Distribution

Binary-distributions of the LDM package might be available via anonymous FTP for some of the known compatible systems at ftp://ftp.unidata.ucar.edu/pub/binary/.

NOTE: There's no guarantee that a binary version of the latest release (or, indeed, any release) will be available!

Drop into the appropriate subdirectory for your system and download the file ldm.binary.tar.Z.

Unpack the Distribution

Unpack the distribution in the LDM user's home directory using the zcat(1) and tar(1) utilities. For example: 

cd $HOME
zcat ldm.binary.tar.Z | tar xvf -

This will unpack the source distribution into a subdirectory. The name of the subdirectory will contain the version identifier of the just-unpacked package (e.g., ldm-6.m.b, where m and b are the "minor" and "bug-fix" release-levels).

The remaining instructions pretend that the pathname of this version subdirectory was assigned to the shell variable VERSIONDIR.

Vet the ldmadmin script

Follow these instructions on vetting the ldmadmin script.

Copy distribution configuration files if first-time LDM

If this is the LDM user's first LDM installation, then copy the contents of $VERSIONDIR/etc to $HOME/etc. For example: 

cd $HOME/$VERSIONDIR/etc
cp * $HOME/etc

Make rpc.ldmd and hupsyslog set-uid-root

For example: 

cd $HOME/$VERSIONDIR/bin
su
...
chown root rpc.ldmd hupsyslog
chmod u+srwx,g+rx,o+rx rpc.ldmd hupsyslog
Note that this step must be done as the superuser (i.e. root).

This step is necessary for the LDM to use port 388 (which is restricted) for its communications and for the hupsyslog(1) utility to notify the syslogd(8) daemon when a new log-file has been created.