<?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: How to set Execute rights for shell scripts on Windows Forwarder Management? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Execute-rights-for-shell-scripts-on-Windows-Forwarder/m-p/165596#M33588</link>
    <description>&lt;P&gt;There is probably some utility to modify the permissions for the shell script while on a Windows system, but if I were you I would copy the file to a linux system, chmod it, then put it back into place on the deploy server.&lt;/P&gt;</description>
    <pubDate>Sat, 07 Mar 2015 03:25:54 GMT</pubDate>
    <dc:creator>muebel</dc:creator>
    <dc:date>2015-03-07T03:25:54Z</dc:date>
    <item>
      <title>How to set Execute rights for shell scripts on Windows Forwarder Management?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Execute-rights-for-shell-scripts-on-Windows-Forwarder/m-p/165595#M33587</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;I'm using Forwarder Management on a Splunk instance running on Windows. I've created an app to get some data inputs running shell scripts. When I distributed the app to the forwarders, the execute attribute -x is not set on the scripts, so they don't get executed. When manually setting the scripts using chmod 755 *.sh the inputs are generated. &lt;/P&gt;

&lt;P&gt;Is there a way I could set the execute rights on the App for Linux inputs? Are there any post copy scripts i could execute after the app is deployed from Forwarder Management?&lt;/P&gt;

&lt;P&gt;Cheers,&lt;/P&gt;

&lt;P&gt;Andreas&lt;/P&gt;</description>
      <pubDate>Fri, 06 Mar 2015 10:58:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Execute-rights-for-shell-scripts-on-Windows-Forwarder/m-p/165595#M33587</guid>
      <dc:creator>schose</dc:creator>
      <dc:date>2015-03-06T10:58:47Z</dc:date>
    </item>
    <item>
      <title>Re: How to set Execute rights for shell scripts on Windows Forwarder Management?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Execute-rights-for-shell-scripts-on-Windows-Forwarder/m-p/165596#M33588</link>
      <description>&lt;P&gt;There is probably some utility to modify the permissions for the shell script while on a Windows system, but if I were you I would copy the file to a linux system, chmod it, then put it back into place on the deploy server.&lt;/P&gt;</description>
      <pubDate>Sat, 07 Mar 2015 03:25:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Execute-rights-for-shell-scripts-on-Windows-Forwarder/m-p/165596#M33588</guid>
      <dc:creator>muebel</dc:creator>
      <dc:date>2015-03-07T03:25:54Z</dc:date>
    </item>
    <item>
      <title>Re: How to set Execute rights for shell scripts on Windows Forwarder Management?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Execute-rights-for-shell-scripts-on-Windows-Forwarder/m-p/165597#M33589</link>
      <description>&lt;P&gt;You can't do this to Windows Forwarders from a Linux Deployment server. You need a Windows Deployment Server to manage windows permissions / environment. &lt;/P&gt;</description>
      <pubDate>Sat, 07 Mar 2015 18:14:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Execute-rights-for-shell-scripts-on-Windows-Forwarder/m-p/165597#M33589</guid>
      <dc:creator>mcronkrite</dc:creator>
      <dc:date>2015-03-07T18:14:48Z</dc:date>
    </item>
    <item>
      <title>Re: How to set Execute rights for shell scripts on Windows Forwarder Management?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Execute-rights-for-shell-scripts-on-Windows-Forwarder/m-p/165598#M33590</link>
      <description>&lt;P&gt;As mentioned, if you are using a *Nix based Deployment Server and pulling from Windows Machines, the permissions will not get copied over.&lt;/P&gt;

&lt;P&gt;Your best bet here is to set execution rights on the $splunk_home/etc/apps folder, and enable "Inherit Permissions" with execute bit set. This should set the execution bit on all folders above $splunk_home/etc/apps. One side note to this, it does set execute on all files. If you are running a secured windows box, this might not be ideal.&lt;/P&gt;

&lt;P&gt;In that case, you best bet would be to write a powershell script that will set execute on $splunk_home/etc/apps/*/bin/, and cron that to run frequently, or manually run this everytime you push an updated app.. &lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 19:07:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-Execute-rights-for-shell-scripts-on-Windows-Forwarder/m-p/165598#M33590</guid>
      <dc:creator>esix_splunk</dc:creator>
      <dc:date>2020-09-28T19:07:46Z</dc:date>
    </item>
  </channel>
</rss>

