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.
Check your environment. If you have some path or environmental variables set when you are in your own shell, you may have to have them set in the LDM's environment before starting up the LDM. Steve Chiswell Unidata User SUpport On Fri, 5 Oct 2001, Jason J. Levit wrote: > > > Make sure that the LDM has write permission to the entire path. Also > > check that your executable is in the correct place. > > Chances are, something is configured on the other machine that has not been > > done > > on the new box. > > Hi Steve, > > Ugh, I set all the permissions, and the executable is in the write > place. In fact, when I run it all on the command line, everything works > fine, including writing to the correct directory. > > I can't think of any system settings that would cause LDM to not run > the executable correctly, since I can run it all from the command line. > Is there something I'm missing? This is really weird! > > Jason > > -- > ---------------------------------------------------------------------------- > Jason J. Levit, N9MLA Research Scientist, > address@hidden Center for Analysis and Prediction of Storms > Room 1022 University of Oklahoma > 405/325-3503 http://www.caps.ou.edu/ >