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

[LDM #RVD-274057]: pqact

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 #RVD-274057]: pqact
  • Date: Tue, 09 Aug 2016 10:00:41 -0600
Dave,

One, single-threaded, pqact(1) process is started for every "EXEC pqact ..." 
entry in the LDM configuration-file.

Each pqact(1) process: 1) gets a product from the queue; 2) sequentially 
matches that product against the entries in that pqact(1)'s configuration-file; 
3) for every matching entry, synchronously performs that entry's action (except 
for the action "EXEC -nowait"); and 4) goes back to #1.

Because of this design: 1) sites often invoke multiple pqact(1) processes, each 
tuned for a specific category of products via the pqact(1) "-f feed" and "-p 
pattern" options and a specific pqact(1) configuration-file; and 2) the 
importance of high-performance decoders for the PIPE actions cannot be 
overemphasized.

I hope this answers your question.

> Is pqact threaded?
> 
> Example:
> 
> If we have a downstream system with n 'FILE' entries in pqact.conf,
> will there be just one pqact process doing the writing serially or is
> there a separate pqact process started for each entry in pqact.conf or
> is it handled yet some other way?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RVD-274057
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.