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.
Sanket, >Date: Mon, 23 Jun 2003 21:56:43 -0500 >From: "Pai, Sanket Vasant (UMKC-Student)" <address@hidden> >Organization: University of Missouri at Kansas City >To: "Steve Emmerson" <address@hidden> >Subject: LDM UMKC The above message contained the following: > i have installed ldm on another machine > name: cirrus.geosci.umkc.edu > root password is same as cumulus > user: ldm > password is same as that for cumulus ... > please have a look into the installation and let me know if it has > been correctly done > thanks > Sanket The LDM administration-file (bin/ldmadmin) looks OK. The top-level directory structure looks OK. The "bin/" subdirectory looks OK. Regarding the LDM configuration-file: 1. There are no "request" lines, so no data will be received and pqact(1) won't have anything to do. 2. There's an "exec pqbinstats ..." entry but no corresponding "ldmadmin dostats" entry in the LDM user's crontab(1) file; consequently, I commented-out the "exec pqbinstats ..." entry. 3. If Cirrus will NOT be a "gateway" LDM host (i.e., a host that receives data from the outside or sends data to the outside) then you should comment-out the "exec rtstats" entry. The LDM product-queue needed to be created, so I did an "ldmadmin mkqueue". The syslogd(8) configuration-file looks OK. I suggest that you add some "request" entries to your LDM configuration-file and try the LDM. Contact me if you encounter any problems. Regards, Steve Emmerson