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

Re: ldm upgrade...acting odd

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: ldm upgrade...acting odd
  • Date: Mon, 20 Jun 2005 10:01:02 -0600
Gabe,

>Date: Mon, 20 Jun 2005 11:20:17 -0400 (EDT)
>From: Gabe Langbauer <address@hidden>
>Organization: Ohio State University
>To: Steve Emmerson <address@hidden>
>Subject: Re: ldm upgrade...acting odd 

The above message contained the following:

> Sorry, I went out of town for a long weekend, just getting spun back 
> up...problem still seems to persist, but I haven't had a lot of time to 
> look into it since our last communication.  Any thoughts on where to look 
> for a version specific link to the conf files?

The root-cause of your problem is that the value of the environment
variable LDMHOME was "/usr/local/ldm/ldm-6.1.0" when version 6.3.0 of
the LDM package was built:

    $ grep LDMHOME ~ldm/src/config.status
    s,@LDMHOME@,/usr/local/ldm/ldm-6.1.0,;t t
    ...

This is causing the 6.3.0 LDM system to use the wrong directory as the
root-directory of the LDM system.

The solution is to rebuild the LDM 6.3.0 packge with LDMHOME either
unset or set to "/usr/local/ldm".  For example:

    $ su - ldm
    ...
    $ cd src
    $ make distclean
    ...
    $ LDMHOME=~ ./configure &>configure.log
    $ less configure.log
    $ make &>make.log
    $ less make.log
    $ make install &>install.log
    $ less install.log
    $ ldmadmin stop
    ...
    $ su root -c 'make install_setuids'
    ...
    $ ldmadmin start

> --Gabe

Regards,
Steve Emmerson