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.
Gabe, The product-queue was on an NFS-mounted disk from a remote system. This caused the problems you encountered (the product-queue file is memory-mapped by the LDM server and this isn't supported by NFS-mounted filesystems). I removed the data/ symbolic link to /nfs/polarmet8/data5/langbauer/ldm/data/ and recreated the data/ subdirectory as a real directory of the LDM user's home-directory. This works. I also added symbolic links in the (now real) data/ subdirectory to the conduit/ and EXP/ subdirectories in /nfs/polarmet8/data5/langbauer/ldm/data/. Accessing those directories, however, is extremely slow. So, if the LDM is decoding into those directories, then the performance might be unsatisfactory and you might want to reify those subdirectories in the new data/ directory. You'll also need to edit the files etc/ldmd.conf (to request data) and etc/pqact.conf (to process the data). Regards, Steve Emmerson