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

Re: 20040115: pqact(1) PIPE problems

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: Re: 20040115: pqact(1) PIPE problems
  • Date: Wed, 14 Jan 2004 14:47:14 -0700
Karen,

>Date: Wed, 14 Jan 2004 15:30:45 -0600
>From: "Karen Cooper" <address@hidden>
>Organization: NOAA/NWS/NSSL
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20040115: pqact(1) PIPE problems
> Keywords: 200401141757.i0EHvIp2008899 LDM

The above message contained the following:

> I actually only have two entries in the pqact file.  One FILE entry -- 
> for all NEXRD2 data and one  PIPE entry -- for all NEXRD2 data.

I'll bet, however, that either the pathname argument of the FILE entry
or the arguments to the nexradII_bz(1) program in the PIPE entry undergo
string-substitution.  See

    
http://my.unidata.ucar.edu/content/software/ldm/ldm-6.0.14/basics/pqact.conf.html#argref

This causes a separate process to be created for each unique,
string-substituted instance of any entry.

I didn't make this clear in my previous email.  Sorry.

Regards,
Steve Emmerson