Workshop-Specific Instructions

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

Create the LDM user-account

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

Edit file /etc/services

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

grep ldm /etc/services

Edit file /etc/rpc

This should already have been done. You can verify this 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/syslog.conf

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

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

cat <<'EOF' >>.bash_profile
export PATH=$HOME/bin:$PATH
export MANPATH=$HOME/man:/usr/share/man
export LDMHOME=$HOME
EOF
. .bash_profile
Otherwise, do the equivalent of the above for your user-shell.

Build and Install the Distribution

If bash(1) is your user-shell (which is the default) the 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
Otherwise, do the equivalent of the above for your user-shell.

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|NNEXRAD:

(For average rates of the various feedtypes, see, for example, the data-volume summary webpage for a computer at the UPC.)

Create directories for data-files and LDM logfiles

Execute the commands 

mkdir /var/ldm/data /var/ldm/logs
cd
ln -s /var/ldm/data /var/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

Un-comment-out the "EXEC pqact" entry to enable local processing of received data-products.

Add the following entries to the LDM configuration file, ldmd.conf, to request the IDS|DDPLUS and NNEXRAD data-feeds: 

REQUEST	IDS|DDPLUS	.*	workshop19.ucar.edu
REQUEST	NNEXRAD		.*	workshop19.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
Remember to start the continuation-lines with a tab character.

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
This will remove all files in the data directory hierarchy that are older than one day.

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

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.