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

[LDM #ROJ-852250]: Cron job can't reset LDM registry?

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 #ROJ-852250]: Cron job can't reset LDM registry?
  • Date: Thu, 13 Apr 2017 14:53:41 -0600
Bob,

Your GEMPAK decoders like this process

> ldm       7350  0.2  0.3  67648 31516 ?        S    08:00   0:00
> decoders/dcisig -e GEMTBL=/home/gempak/NAWIPS/gempak/tables -d
> data/gempak/logs/dcisig.log data/gempak/isig/YYYYMMDDHH_isig.gem

assume that the current working directory (CWD) is the LDM user's home
directory. The CWD of every pqact(1) process is actually given by the value
of the registry parameter "/pqact/datadir-path". What's the output of the
command

    regutil | grep /pqact/datadir-path

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: ROJ-852250
Department: Support IDD
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.