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 Mike, re: > Thanks for the quick response. No worries. Thanks for sending along the pattern-action file, I think I see why the action for CONUS is working while the ones for FullDisk, Mesoscale-1 and Mesoscale-2 are not: The fully qualified name of the GRB log file for the CONUS case is specified correctly: /usr/local/ldm/var/logs/grb\4.log The fully qualified pathnames for the other 3 coverages look like they have a simple typo: /user/local/ldm/var/logs/grb\4.log The difference is 'usr' versus 'user'. I think that all you need to do is: - edit the FullDisk, Mesoscale-1 and Mesoscale-2 actions in your pattern-action file and: change: user to: usr - after finishing the editing, run the following to check for gross errors in all patter-action files: ldmadmin pqactcheck - if there are not errors indicated, run the following to tell all 'pqact' invocations to re-read their pattern-action files: ldmadmin pqactHUP Please let me know if the typo was, in fact, the problem. 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: VOZ-961042 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.