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.
=============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ =============================================================================== ---------- Forwarded message ---------- Date: Fri, 05 Nov 1999 10:23:59 -0700 From: Teresa Van Hove <address@hidden> To: Robb Kambic <address@hidden>, address@hidden, address@hidden Subject: Re: idd data request Thanks Rob, I was able to get the log messages from the info in that e-mail, and tracked the problem down to the fact that Myron has been setting up the ldm's to have ldm_cpuname for the home area instead of just ldm to differentiate the unavco and utah gps ldm's since he has them both email him with any messages. They have been not been able to do binary installations anyway because they have not had exact OS vs matches, so that worked for them, but the binary installation was compiled expecting files in the standard /usr/local/ldm/ area and does not just use the $ldmhome definition everywhere. Since this ldm installation is for my own GPS water vapor use, I am having any email directed just to me anyway so I can just reintall the ldm with the standard directory and it should work. I'm cc'ing Natalie and Myron so they will know that they have to continue doing source installations so long as they want to continue having ldm_cpuname instead of ldm as the ldmhome directory. Teresa Robb Kambic wrote: > > > Teresa, > > For the log problem look at e-mail written for another user, the path will > be different but all the other info should be the same. Once you have log > messages, then you can see the problem with pqact. > > http://www.unidata.ucar.edu/glimpse/ldm/3277 > > Also, UPC only supports the LDM on Redhat Linux because of all the > differences in Linux versions. > > Look at the pqact man page for more info: > > http://www.unidata.ucar.edu/cgi-bin/man-cgi?pqact+1 > > > > So I am wondering if there may be some linux or perl version > > inconsistency? Perl 5.005 is what is installed on my cpu and I > > am running linux vs. 6.0. We installed the binary linux vs of > > ldm from unidata. > > > As long as it's Perl 5 there will be no problems. > > Robb... >