Unidata - To provide the data services, tools, and cyberinfrastructure leadership that advance Earth system science, enhance educational opportunities, and broaden participation. Unidata
         
  advanced  
 

Vet the ldmadmin configuration-file (ldmadmin-pl.conf)

["To vet" is to examine and possibly modify or correct.]

The perl(1)-script for administering the LDM should have been installed as the file $HOME/ldm-6.7.0/bin/ldmadmin The configuration-file for this script should have been installed as the file $HOME/etc/ ldmadmin-pl.conf, if it didn't already exist. What follows is information on possible modifications to this configuration-file for your site.

If this is your first LDM installation, then you will probably need to manually configure several variables in the ldmadmin configuration-file. Versions 6.1 and earlier of the LDM package did not have this configuration-file. If you have a version 6.1 or earlier installation of the LDM package, then you can use that installation's ldmadmin script to help you determine appropriate values.

Vet the following variables in the ldmadmin configuration-file, $HOME/etc/ ldmadmin-pl.conf:

Variable Meaning
hostname The fully-qualified name of the host computer on which the LDM will execute. This name must contain periods. If the command uname -n doesn't return such a name, then set the value appropriately.
pq_size The size, in bytes, of the data portion of the LDM's product-queue. This parameter is used when the product-queue is created. The size should be greater than the desired minimum residency-time for a data-product in the product-queue (e.g., 1 hour) times the maximum rate of data arrival. (e.g., 13.4 MB/h if only the IDS|DDPLUS data-feed is being received). If the value is less than this, then late-arriving data-products that are older than the minimum residency time could, nevertheless, still be inserted into the product-queue because their predecessors will have been purged from the queue.

For convenience, a "K", "M", or "G" suffix can be appended to the numeric specification to mean "kilo", "mega", and "giga", respectively. Thus the specifications "1G" "1000M", "1000000K", and "1000000000", are all equivalent, for example.

The value for this parameter can be fine-tuned by using the pqmon utility.

pq_slots The number of data-product slots for the LDM product-queue. This is the maximum number of data-products that the product-queue can contain (assuming that the data portion of the product-queue is sufficiently capacious). This parameter is used when the product-queue is created. The number of slots should equal the maximum number of data-products expected over the desired minimum residency-time (e.g., 16000 for one hour of IDS|DDPLUS data, if that is all that's being received). If this parameter is defaulted, then the number of slots will be computed using the size of the data portion of the product-queue and 4096 bytes as the mean data-product size (which is, undoubtably, incorrect).

The value for this parameter can be fine-tuned by using the pqmon utility.

numlogs The maximum number of LDM logfiles to keep around.
ip_addr The IP address of the network interface on which the LDM server should listen for connections. This variable doesn't exist in older versions of the configuration-file and may be added manually. If this variable isn't set, then the LDM server will listen on all available network interfaces.
port The port on which the LDM server should listen for connections. This variable doesn't exist in older versions of the configuration-file and may be added manually. If this variable isn't set, then the LDM server will listen on the port that was specified when the package was built.

Workshop-specific instructions.

You can check the configuration of the ldmadmin configuration-file by executing the following command:

$HOME/ldm-6.7.0/bin/ldmadmin config
 
 
  Contact Us     Site Map     Search     Terms and Conditions     Privacy Policy     Participation Policy
 
National Science Foundation (NSF) UCAR Office of Programs University Corporation for Atmospheric Research (UCAR)   Unidata is a member of the UCAR Office of 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