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

Re: 20010829: LDM install

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: 20010829: LDM install
  • Date: Wed, 29 Aug 2001 11:50:06 -0600
Unidata Support wrote:
> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >From: Tim Alberta <address@hidden>
> >Subject: LDM install
> >Organization: UCAR/COMET
> >Keywords: 200108291603.f7TG3f116324
> 
> Hi Unidata folks,
> 
> Our AWIPS crashed pretty hard this past weekend, and one of the things
> that is not coming back up is the LDM we have running on our data
> server.
> 
> I was thinking this might be a good time to install the latest version,
> but I'd like to make it a truly clean install, since I wasn't around
> when the old version was installed.
> 
> Would there be any problem with me getting rid of everything associated
> with the current LDM before I install a newer version?  (Other than the
> configuration files, of course)  Do you know of any "gotchas" I might
> encounter if I do this?
> 
> Thanks for your input,
> 
> Tim
> 
> ------- End of Forwarded Message

Hi Tim,

Nah, no problem, blast away!!  I'll listen for the explosion.

Nothing in any distribution depends on anything in a previous
distribution.  I assume you mean that you're going to keep the same
'ldm' user account.  I assume your .cshrc will remain the same (assuming
you use csh).  The syslog configuration, cron jobs, and any boot scripts
would remain the same.

The directories that are "localized" are the etc, util, and decoders
directories.  I would set those aside and reinstall them under the new
installation.   That way, you'll preserve any failover and scour config
files under etc plus whatever else might have been installed in those
directories.

The data and logs directories are links to elsewhere, so if you remove
the links you'll just remake them under the new installation.  Thus, the
contents of those directories will be preserved.  If you knew your queue
was still good, it would be preserved.  Very few upgrades require
building a new queue, so this could be useful if you have a very large
queue.  In your case, however, I'd blow away the queue and make a new
one.

That leaves just the bin, src, lib, include, and man directories, and
they all come with the distribution.

You might want to set aside your most recent version of ldmadmin so that
you can configure the new version with your current queue size, or
migrate any other changes that might have been made.  That's the one
executable that folks tend to modify.

You might want to scan through the preinstallation instructions:
http://www.unidata.ucar.edu/packages/ldm/ldmPreInstallList.html to see
if there's anything else to consider.  Then, you can always use the
installation instructions, and setup instructions to guide you.  They're
available from the LDM home page:
http://www.unidata.ucar.edu/packages/ldm/index.html

Really, it should be pretty simple.  Good luck.  If you have problems
let me know.

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