Rodney, I edited the "etc/pqact.conf" file to remove some ".*" prefixes from some, otherwise, pathological regular-expressions and sent a HUP signal to the pqact(1) process to cause it to reread its configuration-file. The original "pqact.conf" still exists as "pqact.conf.prev". Information on pathological regular-expressions can be found at http://my.unidata.ucar.edu/content/software/ldm/ldm-6.0.14/basics/ERE.html The pqact(1) process is showing what data-products it's seeing. One of the data-products was FSL2 000 FSL.CompressedNetCDF.MADIS.metar.20040527_2300.gz This should have matched the following entry in the pqact(1) configuration-file: FSL2 ^FSL\.CompressedNetCDF\.MADIS\.metar\.(.*) PIPE -close /home/rpp/scripts/store_MADIS.sh /data/fxa/point/mesonet/netcdf \1 The script "/home/rpp/scripts/store_MADIS.sh" looks pretty simple and should have created something in the directory "/data/fxa/point/mesonet/netcdf". It didn't, however. I suggest testing the script on some canned data to ensure that it works. Can the script find the gzip(1), echo(1), cut(1), and mv(1) utilities (i.e., is the PATH correct)? You might try expliciting setting the PATH environment variable in the script (which is a good idea, in general). Alternatively, you might be able to simplify the entry to the following: FSL2 ^FSL\.CompressedNetCDF\.MADIS\.metar\.(.............) PIPE -close /bin/bash -c "gzip -d >/data/fxa/point/mesonet/netcdf/\1" Be advised that I haven't tried this. Keep me apprised. Regards, Steve Emmerson
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.