<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Search script - stdin contents in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Search-script-stdin-contents/m-p/68215#M13813</link>
    <description>&lt;P&gt;how do u get stdin to go to perl?&lt;/P&gt;</description>
    <pubDate>Tue, 17 Apr 2012 21:08:39 GMT</pubDate>
    <dc:creator>alexl1</dc:creator>
    <dc:date>2012-04-17T21:08:39Z</dc:date>
    <item>
      <title>Search script - stdin contents</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Search-script-stdin-contents/m-p/68213#M13811</link>
      <description>&lt;P&gt;Hi.  I'm starting to work with custom search commands.  For now, I need to use Perl.&lt;/P&gt;

&lt;P&gt;Just to get started, I did a simple thing to read STDIN and dump the results to a text file on the system.&lt;/P&gt;

&lt;P&gt;Along with the actual Results data I expected to see, I see things that start with some of this stuff (usually followed by things that are part of my actual Splunk search:&lt;BR /&gt;
 keywords: (+ elements of my search)&lt;BR /&gt;
 search:search%20 (+ my search)&lt;BR /&gt;
 sharedStorage: (location of my pooled search head shared storage)&lt;/P&gt;

&lt;P&gt;The painful part of this is that this extra info is interspersed with the rest of my actual search results, so it's not like I can skip lines until I start seeing valid data.&lt;/P&gt;

&lt;P&gt;I haven't found any information on exactly why this data appears in STDIN.&lt;/P&gt;

&lt;P&gt;Can anyone shed light on this or at least point me towards some documentation that I may have missed?&lt;/P&gt;

&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Aug 2011 20:47:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Search-script-stdin-contents/m-p/68213#M13811</guid>
      <dc:creator>Sqig</dc:creator>
      <dc:date>2011-08-31T20:47:06Z</dc:date>
    </item>
    <item>
      <title>Re: Search script - stdin contents</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Search-script-stdin-contents/m-p/68214#M13812</link>
      <description>&lt;P&gt;I think I found the answer to this one.  It looks like if I specify the following on commands.conf, I don't get the extra information:&lt;/P&gt;

&lt;P&gt;enableheader = false&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2011 18:46:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Search-script-stdin-contents/m-p/68214#M13812</guid>
      <dc:creator>Sqig</dc:creator>
      <dc:date>2011-09-01T18:46:08Z</dc:date>
    </item>
    <item>
      <title>Re: Search script - stdin contents</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Search-script-stdin-contents/m-p/68215#M13813</link>
      <description>&lt;P&gt;how do u get stdin to go to perl?&lt;/P&gt;</description>
      <pubDate>Tue, 17 Apr 2012 21:08:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Search-script-stdin-contents/m-p/68215#M13813</guid>
      <dc:creator>alexl1</dc:creator>
      <dc:date>2012-04-17T21:08:39Z</dc:date>
    </item>
  </channel>
</rss>

