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

20030530: Problems with LDM 6.0.12: connecting to LDM 5

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: 20030530: Problems with LDM 6.0.12: connecting to LDM 5
  • Date: Fri, 30 May 2003 14:45:33 -0600
Christian,

>Date: Fri, 30 May 2003 13:51:20 -0400
>From: =?ISO-8859-1?Q?Christian_Pag=E9?= <address@hidden>
>Organization: UQAM
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20030530: Problems with LDM 6.0.12: connecting to LDM 5 

The above message contained the following:

> You should be able to get in now!

I slightly modified the code for connecting to an upstream LDM.  I
suspect that it won't make any difference -- but it's worth testing.

At your convenience, would you please

    1.  Go to "/io/ldm/ldm-6.0.12/src".

    2.  Become root.

    3.  Execute the command "make install_setuids".

Then, either let me know that you're done or, if you're feeling
experimental, do the following:

    1.  Go to "/io/ldm".

    2.  Execute the command

            bin/ldmadmin stop && rm runtime && \
            ln -s ldm-6.0.12 runtime && bin/ldmadmin start

    3.  Wait until the file "logs/ldmd.log" indicates either success or
        failure to connect to host "dns2.cmc.ec.gc.ca".

    4.  Execute the command

            bin/ldmadmin stop && rm runtime && \
            ln -s ldm-6.0.11 runtime && bin/ldmadmin start

    5.  Send me the file "logs/ldmd.log.1".

Regards,
Steve Emmerson