[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 13:52:21 -0600
Anne,

> We're running 6.11.5 but have plans to upgrade to 6.13.6 in the next month
> or so. We're hoping that the upgrade will be a good time to implement any
> of the suggestions you give us.

Logging changed in version 6.13.0 to become independent of the system logging 
daemon (which was a pain in the...). The new logging system will still respond 
to an "ldmadmin newlog".

Please send me the output of the commands
    ls -l ~/bin/hupsyslog
    mount | grep nosuid

> We are calling pqing directly from the LDM source code: ~ldm/bin/pqing. We
> are calling it within our queueing software, it calls pqing each time a new
> file that matches particular patterns come in.

Is the queuing software started via an EXEC entry in the LDM 
configuration-file, ~/etc/ldmd.conf?

> We are rotating the log using ldmadmin newlog.


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.