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

[THREDDS #LYS-595449]: ldm and thredds

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: [THREDDS #LYS-595449]: ldm and thredds
  • Date: Mon, 19 Nov 2007 13:25:04 -0700
Leigh,

you found a small loop hole in my documentation, i'll fix it.   since  all the 
ldm data is written to
~ldm/data, one needs a large partition to hold the data, about 1 terabytes. 
most installation create one
data partition to store the data different then the code installation point, 
then link data to the data
partition ie  ~ldm/data -> /data/ldm    it sounds like your installation and 
the data are on the same 
partition.  you can resolve the problem by making a link from ~ldm/data to 
/data/ldm, ie

ln -s  ~ldm/data  /data/ldm 

and everything should work. The catalogs are looking for the data at 
/data/ldm/pub .... not ~ldm/data/pub

Robb...


Ticket Details
===================
Ticket ID: LYS-595449
Department: Support THREDDS
Priority: Normal
Status: Open