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

[LDM #JXK-104385]: using PIPE with CONDUIT data



Debra,

If the PIPE and FILE outputs differ, then it's because the piped-to decoder 
didn't create an exact copy of its input.

Put another way, piping to a decoder script that simply cat(1)s its input into 
a new file will result in the same file as FILE-ing it.

You can run sequential FILE and then EXEC actions on the same file. Just be 
sure to use the "-close" option of the FILE action.

I regret that I don't have the time to vet your binWriter(1) script.

> I'm trying to use PIPE to capture CONDUIT data and run it through a 
> processing script.
> I modified the binWriter decoder so I can invoke a processing script on 
> ingest.  The
> output files from PIPE->decoder and from FILE are the same length but the 
> output file
> contents are different.  I've tried multiple config options (-strip -close 
> -overwrite).
> 
> Is PIPEing through a decoder the right option, or can I run both FILE and EXEC
> commands upon ingest (haven't been able to get that to work so examples would 
> be appreciated).


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: JXK-104385
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.



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.