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

Re: 20010223: LDM for two computers

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: 20010223: LDM for two computers
  • Date: Mon, 26 Feb 2001 17:04:07 -0700
Unidata Support wrote:
> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >From: Bunny Pfau <address@hidden>
> >Subject: LDM for two computers
> >Organization: NCAR/HAO
> >Keywords: 200102231648.f1NGmdL01689 LDM install ldmadmin
> 
> Hello:
> 
> I have a case where I would like to run an LDM server
> on two different computers (Solaris 2.5.1/LDM 5.1.2)
> and I would like to keep the binaries and so on on
> an NFS shared file system...in other words, so that although
> two computers are running independent LDM servers that I do not
> have two absolute and redundant installations.
> 
> Of course, I would need to have separate .conf files and
> queues.   One thing that prevents this is that the ldmadmin
> file has a place where the hostname is hardwired in.
> Naturally, that could be modified to check which host its
> running on and derive the hostname in that way.
> 
> I didn't want to toy with this before first asking why things
> are set up this way and if there are some inherent difficulties
> in using a shared installation.
> 
> Thanks,
> Bunny
> 
> ---
> 
> Bunny Pfau                      National Center for Atmospheric Research
> address@hidden                  High Altitude Observatory
> tel: 303 497-1555               P.O. Box 3000
> fax: 303 497-1589               Boulder, CO  80307-3000
> 
> ------- End of Forwarded Message

Hi Bunny,

Although I don't know of any site that has done this, I think it would
work.  You're right about needing separate conf files and queues.  I
assume the path to LDMHOME would be the same for each host.  Regarding
the hostname in ldmadmin, you could just rename ldmadmin something like
ldmadmin.<host> then in your shell alias ldmadmin to be
ldmadmin.<host>.  Then you wouldn't have to edit the script every time
you upgrade.

If you implement this and find out anything else about it, will you
please let me know?  I'll add it to our support archives so others will
know.

Thanks!

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