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, re: > Is there a way to grab the .status. files from the CONDUIT feed on the > LDM? For example, using 'ldmadmin watch -f CONDUIT' I will see the > following line: > > Jun 25 16:19:35 pqutil INFO: 85698 20200625161854.639 CONDUIT 588 > .status.data/nccf/com/gfs/prod/gfs.20200625/12/gfs.t12z.pgrb2.0p25.f156 000588 > > Can this be gotten using the pqact.conf? Yes, absolutely. re: > What would the regex syntax be for this for a pqact.conf entry? CONDUIT<tab>\.status\.data{0,1}(.*) [0-9]{6}$ <tab>FILE<tab>-close <top_level_directory>\1 Here, you would replace <top_level_directory> with the directory name of your choice. re: > I've tried several different things and can't seem to get it to work. You can test the extended regular expression (ERE) to be used in an LDM pattern-action file action (e.g., pqact.conf) using the LDM utility 'notifyme'. For instance: <as 'ldm'> notifyme -vl- -f CONDUIT -o 3600 -p "\.status\.data{0,1}(.*) [0-9]{6}$" Adjust the ERE specified in the pattern ('-p' flag value) until you match exactly what you want, and then use the ERE in the pattern-action file action. re > Thanks! No worries. 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: TDC-646361 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.