<?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: Inputs.Conf - Historical Logging - Chicken and the Egg? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-Conf-Historical-Logging-Chicken-and-the-Egg/m-p/36952#M6830</link>
    <description>&lt;P&gt;Thanks!  CLI options work great.&lt;/P&gt;</description>
    <pubDate>Tue, 19 Feb 2013 20:33:19 GMT</pubDate>
    <dc:creator>vragosta</dc:creator>
    <dc:date>2013-02-19T20:33:19Z</dc:date>
    <item>
      <title>Inputs.Conf - Historical Logging - Chicken and the Egg?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-Conf-Historical-Logging-Chicken-and-the-Egg/m-p/36950#M6828</link>
      <description>&lt;P&gt;I know that you can control the Universal Forwarder to grab historical event logs from Windows using "current_only = 1", but... how do you install the Universal Forwarder without it starting the SplunkForwarder service automatically?&lt;/P&gt;

&lt;P&gt;In other words, you can't modify inputs.conf, before it exits, to force it to not send over historical logs, correct?  Am I missing something?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 19 Feb 2013 19:04:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-Conf-Historical-Logging-Chicken-and-the-Egg/m-p/36950#M6828</guid>
      <dc:creator>vragosta</dc:creator>
      <dc:date>2013-02-19T19:04:51Z</dc:date>
    </item>
    <item>
      <title>Re: Inputs.Conf - Historical Logging - Chicken and the Egg?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-Conf-Historical-Logging-Chicken-and-the-Egg/m-p/36951#M6829</link>
      <description>&lt;P&gt;Option 1: Install with the command line parameter STARTSPLUNK=0 to not have Splunk forwarder start automatically (with caveats- see &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/installation/installonwindowsviathecommandline"&gt;command line installer documentation&lt;/A&gt;. &lt;/P&gt;

&lt;P&gt;Option 2: Install splunk, point to a deployment server during installation. Keep all other defaults (no receiving indexer, no logs to monitor, etc). On your deployment server, create one or more apps with all of the appropriate settings for your environment... this is what we do. See &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.2/Deploy/Aboutdeploymentserver"&gt;deployment server documentation&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Feb 2013 20:03:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-Conf-Historical-Logging-Chicken-and-the-Egg/m-p/36951#M6829</guid>
      <dc:creator>jeff</dc:creator>
      <dc:date>2013-02-19T20:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: Inputs.Conf - Historical Logging - Chicken and the Egg?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-Conf-Historical-Logging-Chicken-and-the-Egg/m-p/36952#M6830</link>
      <description>&lt;P&gt;Thanks!  CLI options work great.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Feb 2013 20:33:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-Conf-Historical-Logging-Chicken-and-the-Egg/m-p/36952#M6830</guid>
      <dc:creator>vragosta</dc:creator>
      <dc:date>2013-02-19T20:33:19Z</dc:date>
    </item>
  </channel>
</rss>

