<?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: Escaping backslashes for Windows paths in props.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Escaping-backslashes-for-Windows-paths-in-props-conf/m-p/478591#M82165</link>
    <description>&lt;P&gt;Yeah, the doc team was really responsive when I reached out once before. I just wanted to make sure it's actually an error and not just a case of Idiot User.&lt;/P&gt;</description>
    <pubDate>Tue, 25 Feb 2020 14:42:18 GMT</pubDate>
    <dc:creator>Ranazar</dc:creator>
    <dc:date>2020-02-25T14:42:18Z</dc:date>
    <item>
      <title>Escaping backslashes for Windows paths in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Escaping-backslashes-for-Windows-paths-in-props-conf/m-p/478589#M82163</link>
      <description>&lt;P&gt;In my props.conf I need a [source::] stanza to override some settings from a [sourcetype] stanza. The source is a file on a Windows server, so I take a look at the &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.2/Admin/Propsconf#GLOBAL_SETTINGS"&gt;props.conf documentation&lt;/A&gt;, and follow these instructions:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;When you specify Windows-based file paths as part of a [source::&amp;lt;source&amp;gt;] stanza, you must escape any backslashes contained within the specified file path.
Example: [source::c:\\path_to\\file.txt]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But that seems to be flat out wrong. If I use this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::C:\\dir1\\dir2\\app.log]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;it doesn't match. Change it to:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::C:\dir1\dir2\app.log]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and it matches.&lt;BR /&gt;
Am I missing something obvious, or is the documentation just wrong?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2020 19:30:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Escaping-backslashes-for-Windows-paths-in-props-conf/m-p/478589#M82163</guid>
      <dc:creator>Ranazar</dc:creator>
      <dc:date>2020-02-24T19:30:57Z</dc:date>
    </item>
    <item>
      <title>Re: Escaping backslashes for Windows paths in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Escaping-backslashes-for-Windows-paths-in-props-conf/m-p/478590#M82164</link>
      <description>&lt;P&gt;As far as I remember, you don't have to escape any paths as long as they don't contain spaces. You can scroll to the end of the docs page and use the "provide feedback" form. The docs team should reply to you in a few days. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Skalli&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2020 22:26:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Escaping-backslashes-for-Windows-paths-in-props-conf/m-p/478590#M82164</guid>
      <dc:creator>skalliger</dc:creator>
      <dc:date>2020-02-24T22:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: Escaping backslashes for Windows paths in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Escaping-backslashes-for-Windows-paths-in-props-conf/m-p/478591#M82165</link>
      <description>&lt;P&gt;Yeah, the doc team was really responsive when I reached out once before. I just wanted to make sure it's actually an error and not just a case of Idiot User.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Feb 2020 14:42:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Escaping-backslashes-for-Windows-paths-in-props-conf/m-p/478591#M82165</guid>
      <dc:creator>Ranazar</dc:creator>
      <dc:date>2020-02-25T14:42:18Z</dc:date>
    </item>
  </channel>
</rss>

