This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Rick, re: > Back in October I wanted to check to see if one of our machines was > receiving all the files from ldm or if McIDAS-XCD was not filing grib > data correctly. I was creating a list back then, but never realized > /home/ldm/vars/ldmd.log was full of errors. Now I'm trying to again the > list for a new machine. > > I was trying the following: > Entry in /home/ldm/etc/pqact.conf > > CONDUIT (.*) > EXEC /home/ldm/list-prods \1 > > [oper@pollux ldm]$ cat list-prods > #!/bin/ksh > echo $1 | grep gfs | grep 0p5 >> /home/ldm/file-list.txt > > Now I'm not even getting a list. > > Suggestions. The EXEC action kicks off the "decoder" (process) specified, but it does not do anything with the product that caused the action to be executed. What you probably want to do is PIPE the product to the "decoder" so it can be acted on. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: OII-423146 Department: Support IDD Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.