[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: newbie on ldm territories (fwd)

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.

  • Subject: Re: newbie on ldm territories (fwd)
  • Date: Mon, 11 Dec 2000 13:42:16 -0700
> ---------- Forwarded message ----------
> Date: Fri, 8 Dec 2000 09:12:40 -0800 (PST)
> From: rafael mahecha <address@hidden>
> To: address@hidden
> Subject: newbie on ldm territories
> 
> hi jeff...
> 
> i went ahead and complete the ldm source installation with the 
> .bash_profile...
> 
> this is what it looks like:
> 
> =-=-=-=-=-=-=-=-=-
> 
> # .bash_profile
> 
> # Get the aliases and functions
> if [ -f ~/.bashrc ]; then
>         . ~/.bashrc
> fi
> 
> # User specific environment and startup programs
> 
> PATH=$PATH:$HOME/bin:$HOME/decoders:$HOME/bin
> export PATH
> MANPATH=$MANPATH:$HOME/man
> export MANPATH
> BASH_ENV=$HOME/.bashrc
> USERNAME=""
> 
> export USERNAME BASH_ENV
> 
> =-=-=-=-=-=-=-=-=-==-=-=-=-
> 
> i completed step by step the installation...
> 
> when i ran ldmadmin start, it said that it was not found....
> 
> i can't even view my logs...
> 
> i'm looking into it... paths,etc
> 
> any ideas????
> 
> RAFAEL MAHECHA
> Meteorologist/Technical Assistant HPVCI/JSUMP
> Phone: (601)-979-3617
> Fax: (601)-979-3630
> address@hidden
> address@hidden
> :)

Hi Rafael,

I'm sorry not to respond sooner.  It's been quite busy here.

At the command line do 'echo $PATH'.  You should see
/usr/local/ldm/bin somewhere in your path.  It's probably
not there, or the OS would have found it.  But, this could
reveal the problem with your path.  If you don't see a
problem email the result to me.

You could 'cd' to /usr/local/ldm/bin and do './ldmadmin
start' to get around the path problem, assuming your ldm
isn't looking for other programs that it can't find.  But,
this should at least allow you to start the ldm and see
something in the logs.

Similarly, you can 'cd' to /usr/local/ldm/bin and do
'./ldmadmin log' or './ldmadmin tail' to see the log or
follow the end of the log.

If things aren't working, send me a copy of your log.

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************