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.
Gerry, > > The correspondence between pqact(1) processes and their configuration-files > > must be one-to-one in order for the etc/pqact*.conf.state files to have any > > meaning. You can, however, symbolically link to a pqact(1) > > configuration-file using various file names. > > I'm a little lost by this explanation... Sorry. If you could expand a > bit it might help me. Each pqact(1) process creates a file that has the same pathname as the process' configuration-file but with the suffix ".state". This file contains information on the last successfully-processed data-product so that pqact(1) processing can bridge LDM restarts. Problems can arise if multiple pqact(1) processes have the same configuration-file (and, hence, the same ".state" file). Regards, Steve Emmerson Ticket Details =================== Ticket ID: HTX-391676 Department: Support LDM Priority: Normal Status: Closed