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

[IDD #WED-630974]: Back with another problem...

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: [IDD #WED-630974]: Back with another problem...
  • Date: Wed, 22 May 2019 16:06:42 -0600
Hi again Gerry,

Quick follow-up to previous email:

I wanted to make sure that you remembered that you do NOT have to
restart the LDM after changes to active pattern-action file actions.
Instead, all you need to do is:

- make a modification to the pattern-action file

- run 'ldmadmin pqactcheck' to check for gross syntax errors in
  your change(s)

- run 'ldmadmin pqactHUP' to tell all 'pqact's to reread their 
  configuration files

This should make the process of figuring out which action(s) is(are)
causing the 'filel.c:reap() ERROR Child xxxxx exited with status 1'
messages pretty easy/quick.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: WED-630974
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.