<?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: Restart SAS Deployment Manager -noexec in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Restart-SAS-Deployment-Manager-noexec/m-p/917030#M28041</link>
    <description>If you add the -templocation option in the launcherargs of sasdm.ini, does that prevent the issue?</description>
    <pubDate>Tue, 20 Feb 2024 18:41:28 GMT</pubDate>
    <dc:creator>gwootton</dc:creator>
    <dc:date>2024-02-20T18:41:28Z</dc:date>
    <item>
      <title>Restart SAS Deployment Manager -noexec</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Restart-SAS-Deployment-Manager-noexec/m-p/916943#M28036</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried to update latest Java in our SAS Platform 9.4M7 ( Linux )&amp;nbsp; by launching SAS Deployment Manager. Our /tmp directory has been set with noexec option. So while launching Deployment manager, we specify -templocation to launch, so that it will point to the temp location while launching. Deployment Manger successfully gets launched.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When we start applying hot fix, the required hotfix required restart of deployment manger . I simply provide 'Yes' to restart but Im getting error message as&amp;nbsp;&lt;/P&gt;&lt;P&gt;"the problem may be /tmp has been mounted with noexec option".&amp;nbsp; For launching the DM, I can able to specify the templocation , but I'm not sure how the restart happens in the backend.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there are any workaround for the issue? I dont see any SAS document for this. Please let me know&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;THanks&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 10:55:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Restart-SAS-Deployment-Manager-noexec/m-p/916943#M28036</guid>
      <dc:creator>freshstarter</dc:creator>
      <dc:date>2024-02-20T10:55:33Z</dc:date>
    </item>
    <item>
      <title>Re: Restart SAS Deployment Manager -noexec</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Restart-SAS-Deployment-Manager-noexec/m-p/917030#M28041</link>
      <description>If you add the -templocation option in the launcherargs of sasdm.ini, does that prevent the issue?</description>
      <pubDate>Tue, 20 Feb 2024 18:41:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Restart-SAS-Deployment-Manager-noexec/m-p/917030#M28041</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2024-02-20T18:41:28Z</dc:date>
    </item>
    <item>
      <title>Re: Restart SAS Deployment Manager -noexec</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Restart-SAS-Deployment-Manager-noexec/m-p/918020#M28062</link>
      <description>Thanks for the response. I have modified the sasdm.sh script under check_exec_permission function by changing the testTempLocation and that worked.</description>
      <pubDate>Tue, 27 Feb 2024 11:30:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Restart-SAS-Deployment-Manager-noexec/m-p/918020#M28062</guid>
      <dc:creator>freshstarter</dc:creator>
      <dc:date>2024-02-27T11:30:02Z</dc:date>
    </item>
  </channel>
</rss>

