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

[LDM #KYZ-560013]: pqact.conf questions

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 #KYZ-560013]: pqact.conf questions
  • Date: Wed, 25 Oct 2017 08:27:31 -0600
Tiros,

> Our regular pqact.conf has hundreds of entries, to decode gridded data, 
> satellite, radar, metar... as well as entries for encrypted lightning data.  
> We ran the LDM and got some decoded lightning data.
> 
> Then We removed all  the entries in pqact.conf but  kept the lightning 
> entries before restart the LDM again (ldmadmin pqactHUP).  When we display 
> the decoded files from the two pqact.confs using Nmap2, the plots are not the 
> same.   We are wondering why?

You seem to have one "pqact.conf" file in the first instance, but then two in 
the second. Please explain.

How many EXEC-s of pqact(1) do you have in the LDM configuration-file?

Do you have multiple EXEC-s of pqact(1) in the LDM configuration-file? If so, 
do any of them use the same pqact(1) configuration-file (which is a no-no)? If 
not, could you have duplicate entries for handling lightning data in multiple 
active pqact(1) configuration-files?

Can you send me the original "pqact.conf" file (with the hundreds of entries) 
and the second (with only the lightning entries)?

Offhand, I have no idea why you're seeing what you're seeing.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: KYZ-560013
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.