<?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: props.conf change does not take effect in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-change-does-not-take-effect/m-p/74189#M15169</link>
    <description>&lt;P&gt;&lt;A href="http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F"&gt;http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F&lt;/A&gt;&lt;BR /&gt;
or &lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Configurationparametersandthedatapipeline"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Configurationparametersandthedatapipeline&lt;/A&gt;&lt;BR /&gt;
may help&lt;/P&gt;</description>
    <pubDate>Sat, 18 Feb 2012 20:04:07 GMT</pubDate>
    <dc:creator>gkanapathy</dc:creator>
    <dc:date>2012-02-18T20:04:07Z</dc:date>
    <item>
      <title>props.conf change does not take effect</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-change-does-not-take-effect/m-p/74188#M15168</link>
      <description>&lt;P&gt;By source type or file, I changed the line breaking setting but it never takes effect.&lt;BR /&gt;
On my local test system it works fine.  On the distributed environment it does not.&lt;BR /&gt;
The Splunk Web Server has been restarted, no effect.  I either need separate lines or all lines together.  I have tried both.  I have modified props.conf in the App directory and added the same stanza under system/local.&lt;/P&gt;

&lt;P&gt;Do the Splunk Forwarder Instances need to be changed?  I have several forwarders sending data to the central server.  I have not had those changed yet.&lt;/P&gt;

&lt;P&gt;Why do I need this done?  Default Splunk behavior is 256 lines followed by single lines.  This breaks the extract command when multiple values are extracted.  Counts are typically under reported.&lt;/P&gt;

&lt;P&gt;Samples that fail on distributed environment:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[stats_file]

MAX_EVENTS = 3000

[stats_file]

DATETIME_CONFIG=CURRENT

SHOULD_LINEMERGE=FALSE

LINE_BREAKER=([\r\n]+)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 18 Feb 2012 16:50:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-change-does-not-take-effect/m-p/74188#M15168</guid>
      <dc:creator>RalphT</dc:creator>
      <dc:date>2012-02-18T16:50:16Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf change does not take effect</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-change-does-not-take-effect/m-p/74189#M15169</link>
      <description>&lt;P&gt;&lt;A href="http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F"&gt;http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F&lt;/A&gt;&lt;BR /&gt;
or &lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Configurationparametersandthedatapipeline"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Configurationparametersandthedatapipeline&lt;/A&gt;&lt;BR /&gt;
may help&lt;/P&gt;</description>
      <pubDate>Sat, 18 Feb 2012 20:04:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-change-does-not-take-effect/m-p/74189#M15169</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2012-02-18T20:04:07Z</dc:date>
    </item>
  </channel>
</rss>

