NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Teresa, The pqexpire command should be commented out in the ldmd.conf file... I thought we commented this out on all the cloned disks, so it is a bit of a mystery as to why it is not, but it is an easy fix. If it is commented out, and still being called, then we have an issue. local/ldm% more ldmd.conf ##### # Simple setup for testing pqinsert actions #### #exec "pqexpire" #exec "xcd_run MONITOR" #exec "pqact" #exec "pqbinstats" #exec "pqsurf" Thank you, -Jeff ____________________________ _____________________ Jeff Weber address@hidden Unidata Support PH:303-497-8676 NWS-COMET Case Study Library FX:303-497-8690 University Corp for Atmospheric Research 3300 Mitchell Ln http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 ________________________________________ ______________________ On Wed, 24 Oct 2001, Teresa Van Hove wrote: > Jeff, > > I have a bit of an LDM mystery. pqexpire is running on the suominet > field cpu's and they are not accumulating files - they never have > more than 2 files, I cant figure out what is starting the pqexpire > - its not running on my suomildm1 cpu that "catches" the incoming > data and I don't see any line in the ldmadmin file that starts > pqexpire (or stops/prevents it on my cpu.) Can you tell me how to > avoid having the pqexpire process on the field cpu's. (the ps start > time matches the ldmamdin start time) > > THanks, > Teresa >