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.
Hi Chris and Bob, re: > No error messages this morning. I must have missed piping the installation > through pax. We really appreciate the assistance. No worries. I now (as of a minute ago) think I have a handle on why you were having a problem running 'ldmadmin' from cron. The problem was indeed caused by a non-standard installation of the LDM. Here is the code in the 'ldmadmin' script that was causing the problem: $ldmhome = "$ENV{'LDMHOME'}"; if (!$ldmhome) { $ldmhome = "/local/ldm"; } srand; # called once at start # Some parameters used by this script: $progname = "ldmadmin"; $feedset = "ANY"; chop($os = `uname -s`); chop($release = `uname -r`); $begin = 19700101; $end = 30000101; $lock_file = "$ldmhome/.ldmadmin.lck"; $pid_file = "$ldmhome/ldmd.pid"; $line_prefix = ""; $pqact_conf_option = 0; # Ensure that the utilities of this version are favored $ENV{'PATH'} = "$ldmhome/ldm-6.13.6/bin:$ENV{'PATH'}"; The last line in ldmadmin snippit is possibly the culprit since it assumes that there is a ~ldm/ldm-6.13.6/bin directory, and your installation did not have one. It seems to me that this should still have worked since your existing PATH did have the ~ldm/bin directory in it, but... Out of curiosity: can you tell me which cron-initiated 'ldmadmin' invocation was causing the errors previously? Thanks in advance... Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: ROJ-852250 Department: Support LDM Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.