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.
Gilbert, > OK, so all future 6.9.X will just follow the soft link into /dev/shm for > the queues, is that what you are saying. Yes. All future installations will follow the symbolic link to /dev/shm. > > Did you configure the "/reconciliation-mode" parameter for automatic > > re-creations of the product-queue? > Ummm, no. I haven't gotten to that part nor even heard of it yet. It's a major feature of this release. > Now, I use a tcsh shell for the LDM user. I hard-coded in the paths so > that they would work. They *should* as you had them, but call me > paranoid. Should I try it without the absolute paths first? You can check how a crontab(1) entry will work on your system by having the entry be something inocuous (e.g., "ldmadmin config"). > Question: If the LDM is running fine, but NOAAPort's SES-1 bird decides to > shut down and not give me data, BUT Level2 data is working, Profiler data, > McIDAS data are all working, will it say "hey, NOAAport is down!". No. > I'd > like to see a per-feed check of things, rather than just "LDM crashed". Interesting idea! I'll see what I can do. > ******************************************************************************* > Gilbert Sebenste ******** > (My opinions only!) ****** > Staff Meteorologist, Northern Illinois University **** > E-mail: address@hidden *** > web: http://weather.admin.niu.edu ** > ******************************************************************************* Regards, Steve Emmerson Ticket Details =================== Ticket ID: TMA-441215 Department: Support LDM Priority: Normal Status: Closed