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.
Justin, The new version is available. Because it's impossible to test all the ways the LDM system is used, I can't guarantee that it will solve your problem (or, indeed, even work). I do have hopes for it, however, so if your willing to try it, I'm willing to help. Do the following (assuming you have a standard installation): 1. Become the LDM user in that user's home directory. 2. Unpack ftp://ftp.unidata.ucar.edu/pub/ldm/ldm-6.4.2.0.tar.Z in the LDM user's home directory. 3. Drop into the directory ldm-6.4.2.0/src. 4. Execute the equivalent of the command ./configure >configure.log 2>&1 && make >make.log 2>&1 && make install >install.log 2>&1 5. Become root and execute the command make install_setuids 6. Become the LDM user in that user's home directory. 7. Execute the following command: ldmadmin stop && rm runtime && ln -s ldm-6.4.2.0 runtime && ldmadmin start 8. Keep an eye on the LDM logfile and keep me apprised. 9. If things go sufficiently bad that reverting is necessary, then execute the following command as the LDM user in that user's home directory: ldmadmin stop && rm runtime && ln -s ldm-6.3.0 runtime && ldmadmin start Regards, Steve Emmerson