•         advanced

Workshop-Specific Instructions

The following comprises workshop-specific instructions and details for the Summer 2009 LDM Training Workshop.

Create the LDM user-account

An account for the LDM user should already exist on your workstation.

Edit file /etc/services

Many modern operating systems already have entries for the LDM. You should, however, verify your system with the command

grep ldm /etc/services

Edit file /etc/rpc

Many modern operating systems already have entries for the LDM. You should, however, verify your system with the command

grep ldm /etc/rpc

Edit file /etc/syslog.conf

This should already have been done. You can verify this with the command

grep local0 /etc/rsyslog.conf

Ensure that TCP connections can be made

This should already have been done.

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

If you became root by executing the su command as the LDM user in a terminal window, then simply execute the command exit in the terminal window; otherwise, log off the computer and log in as the LDM user.

Edit the LDM user's profile-file

This should already have been done. You can verify this with the command

cat .bash_profile

Build and Install the Distribution

If bash(1) is your user-shell (which is the default) then do the following:

cd $HOME/$VDIR/src
make distclean
./configure >&configure.log && make >&make.log && 
make install >&install.log && sudo make install_setuids &&
make clean &&
echo OK

Vet the ldmadmin(1) configuration-file

From monitoring the product-queue, it is known that the following are good values for the queue parameters for receiving data-products of the feedtype IDS|DDPLUS|NEXRAD3:

• Set the $pq_size variable to 200M:

  $pq_size = "200M";
  

• Set the $pq_slots variable to 50000:

  $pq_slots = "50000";
  

Create directories for data-files and LDM logfiles

Execute the commands

cd
mkdir /machine/data/ldm/data /machine/data/ldm/logs
ln -s /machine/data/ldm/data /machine/data/ldm/logs .

Request authorization at the upstream LDM

Add the following entry to the file $HOME/etc/ldmd.conf to allow all workshop LDM-s to obtain data from any workshop LDM:

ALLOW	ANY	^workshop[0-9]{2}\.ucar\.edu$

For reference, see LDM Basics: ldmd.conf.

Edit the LDM configuration-file, etc/ldmd.conf

The "EXEC pqact" entry should already be enabled to allow local processing of received data-products.

Add the following entries to the LDM configuration file, ldmd.conf, to request the IDS|DDPLUS and NEXRAD3 data-feeds from the instructor's LDM:

REQUEST	IDS|DDPLUS	.*	workshop00.ucar.edu
REQUEST	NEXRAD3		.*	workshop00.ucar.edu

For reference, see LDM Basics: ldmd.conf.

Edit the pqact configuration-file, etc/pqact.conf

Ensure that the following is the only active entry:

IDS|DDPLUS
	^(..)(..).. .... (..)(..)
	FILE
	data/IDS_DDPLUS/\1/\2/(\3:yyyy)(\3:mm)(\3:dd)T\4.txt

This entry will file data-products of feedtype IDS|DDPLUS in an appropriate directory hierarchy with the canonical time of the data-product as the file name.

For reference, see LDM Basics: pqact.conf.

Edit the scour configuration-file, etc/scour.conf

Add the following line to the scour(1) configuration-file, etc/scour.conf:

data/IDS_DDPLUS 1

For reference, see LDM Basics: scour.conf.

Edit the LDM-user's crontab(1) file

Add the following lines via the command "crontab -e":

0 * * * * bin/ldmadmin scour >/dev/null
0 0 * * * bin/ldmadmin newlog
* * * * * bin/ldmadmin addmetrics
* * * * 0 bin/ldmadmin newmetrics

Ensure that the LDM is started at boot-time

We're not concerned about restarting the LDM at boot-time for this workshop. So we'll skip this step.

Contact Us   •   Site Map   •   Search   •   Terms and Conditions   •   Privacy Policy   •   Participation Policy

Unidata is a member of the UCAR Community Programs, is managed by the University Corporation for Atmospheric Research, and is sponsored by the National Science Foundation. P.O. Box 3000   •   Boulder, CO 80307-3000 USA   •   Tel: 303-497-8643   •   Fax: 303-497-8690