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

[LDM #GNJ-752174]: Need advice on hupping persistent daemons (pqinsert, pqing)

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 #GNJ-752174]: Need advice on hupping persistent daemons (pqinsert, pqing)
  • Date: Thu, 13 Sep 2018 10:09:42 -0600
Anne,

pqing(1) is for creating LDM data-products from a serial port of some kind and 
inserting them into the LDM product-queue. It's intended to run indefinitely 
and, therefore, should be started via an EXEC entry in the LDM 
configuration-file so that it can both send signals to and receive signals from 
the LDM process-group.

pqinsert(1) is for inserting files into the LDM product-queue as data-products. 
It will terminate upon inserting the last file; consequently, it doesn't need 
to be part of the LDM process-group in order to receive signals. If it is not, 
however, then the LDM process group will not receive the SIGCONT signals which 
are sent whenever a data-product is inserted into the queue; consequently, the 
newly-inserted data-products will not be acted upon immediately but, rather, 
will be acted upon sometime within a 30 second "fallback" window.

I hope this helps. Contact us if you have any additional questions.

> We have been experiencing an occasional problem with our log rotate and our
> pqing processes not moving to the new log.
> 
> Do you have any advice on how best to insert data into our queue (pqing vs
> pqinsert) and the best way that they should be hupped for log rotate?


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: GNJ-752174
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.