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.
Patrick O'Reilly wrote: > > Hi Anne, > > I solved the cron problem, it seems that when I was at Unidata, Tom issued > crontab commands on blizzard over SSH, and auditing couldn't audit SSH > correctly, and messed up the /var/spool/cron/crontabs/ldm.au file, which > houses settings for ldm's cron jobs (I found this out searching the web). I > re-set up all the ldm's cron jobs and it created a new ldm.au file, which > works fine. > Hi Patrick, I'm glad you got the cron problem figured out. That was some good sleuthing! > Starting ldm at boot is another story. I did what you instructed. The > script worked fine from the command line, both with the 2 queue lines > commented out and not commented out. So I did a reboot and it didn't work. > I moved .cshrc and .login and it worked, but didn't work well. I guess lots > of environment variables for ldm were missing, and every console I opened > was a quickly running list of errors that were occurring due to decoding. > It makes sense that the ldm wouldn't run well without the environment being set properly, but were you able to simply *start* the ldm on booting the system without the .cshrc file in place? (.login is only executed if someone logs in from a terminal.) If so, then we can narrow the problem down to something in the environment. Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************