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

[LDM #PJU-328972]: pqact.conf question

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 #PJU-328972]: pqact.conf question
  • Date: Sun, 04 Dec 2022 08:40:03 -0700
Kevin - I apologize, but my earlier response was incomplete.

The pqact.conf entries in the earlier examples were too abbreviated.  For the 
sake of example, if you edited the script example, and it was in the path:

/home/ldm/util

And you called it "myuuid.sh"

The full pqact.conf entry for the first example script using your question 
would be:

NGRID .*
    PIPE -close /bin/bash /home/ldm/util/myuuid.sh /data/myfilename

And the pqact.conf entry for the second example would be:

NGRID .*
    PIPE -close /bin/bash /home/ldm/util/myuuid.sh 
/data/myfilename.UUID.mysuffix

You would need to put the shell reference if you do not chmod on the new 
script, but if you do make the new script executable, then you can omit the 
"/bin/bash":

# First example
NGRID .*
    PIPE -close /home/ldm/util/myuuid.sh /data/myfilename


# Second example
NGRID .*
    PIPE -close /home/ldm/util/myuuid.sh /data/myfilename.UUID.mysuffix

Let us know if you would like additional clarification.

Stonie

Ticket Details
===================
Ticket ID: PJU-328972
Department: Support LDM
Priority: Normal
Status: Open
===================
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.