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

[LDM #CBT-761337]: GOES-17 data

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: [LDM #CBT-761337]: GOES-17 data
  • Date: Fri, 30 Aug 2019 11:47:40 -0600
Hi again Mike,

One quick question:

- is GEMPAK installed on vulcan, and, if yes, are you running GEMPAK
  scripts from the LDM account?

  If both answers are yes, what is the PATH for your LDM user?

Why is he asking this, you ask?

GEMPAK has a routine that clears out shared memory constructs at
the end of execution.  Current versions of the LDM use shared 
memory, and things like the feed REQUEST(s) and regular
expression patterns are stored in the shared memory segment
(Steve will correct me if this is not statement is not quite
correct).  If the LDM shared memory segment gets deleted,
all bets are off for continued LDM receipt of data.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: CBT-761337
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.