<?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: When developing an add-on, is there any way to use the same inputs.conf for Windows and Linux? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/When-developing-an-add-on-is-there-any-way-to-use-the-same/m-p/363627#M66232</link>
    <description>&lt;P&gt;Try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; [script://.[\\/]bin[\\/]myscript.py]
 disabled = 0
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Wed, 15 Mar 2017 17:14:49 GMT</pubDate>
    <dc:creator>lguinn2</dc:creator>
    <dc:date>2017-03-15T17:14:49Z</dc:date>
    <item>
      <title>When developing an add-on, is there any way to use the same inputs.conf for Windows and Linux?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/When-developing-an-add-on-is-there-any-way-to-use-the-same/m-p/363626#M66231</link>
      <description>&lt;P&gt;I am developing a Splunk add-on, I want that it to work on Linux as well as on a Windows machine.&lt;/P&gt;

&lt;P&gt;In inputs.conf I am providing script path&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[script://./bin/myscript.py]
disabled = 0
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;which is working in Linux but not in Windows.&lt;/P&gt;

&lt;P&gt;If I change script&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[script://.\bin\myscript.py]
disabled = 0
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;then it is working in Windows but not in Linux.&lt;/P&gt;

&lt;P&gt;Is there any way to use same path for Windows and Linux?&lt;/P&gt;

&lt;P&gt;thanks,&lt;BR /&gt;
yusuf&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2017 16:58:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/When-developing-an-add-on-is-there-any-way-to-use-the-same/m-p/363626#M66231</guid>
      <dc:creator>mkhan_splunk</dc:creator>
      <dc:date>2017-03-15T16:58:26Z</dc:date>
    </item>
    <item>
      <title>Re: When developing an add-on, is there any way to use the same inputs.conf for Windows and Linux?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/When-developing-an-add-on-is-there-any-way-to-use-the-same/m-p/363627#M66232</link>
      <description>&lt;P&gt;Try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; [script://.[\\/]bin[\\/]myscript.py]
 disabled = 0
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 15 Mar 2017 17:14:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/When-developing-an-add-on-is-there-any-way-to-use-the-same/m-p/363627#M66232</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2017-03-15T17:14:49Z</dc:date>
    </item>
    <item>
      <title>Re: When developing an add-on, is there any way to use the same inputs.conf for Windows and Linux?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/When-developing-an-add-on-is-there-any-way-to-use-the-same/m-p/363628#M66233</link>
      <description>&lt;P&gt;did not work&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2017 06:38:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/When-developing-an-add-on-is-there-any-way-to-use-the-same/m-p/363628#M66233</guid>
      <dc:creator>mkhan_splunk</dc:creator>
      <dc:date>2017-03-16T06:38:21Z</dc:date>
    </item>
  </channel>
</rss>

