<?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 Is /home/cp_extensions ok to use for GDCO files? in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Is-home-cp-extensions-ok-to-use-for-GDCO-files/m-p/225885#M37675</link>
    <description>&lt;P&gt;A lot of the examples use the /tmp directory to store a json for configuring Generic Data Center Objects.&amp;nbsp; I find using /tmp risky as that will be one of the places a person will look to save space when free space is needed.&amp;nbsp; Since GDCO is "Check Point", it made sense at the moment to use the /home/cp_extensions directory to store the .json files.&lt;BR /&gt;&lt;BR /&gt;I would consider that we would need to verify the changes to that directory during upgrades.&amp;nbsp; But is there a reason not to touch that directory?&lt;BR /&gt;&lt;BR /&gt;If you wonder why, during troubleshooting network issues, our team wants to be able to run a Cisco Thousands Eyes client on the troubled client or server.&amp;nbsp; So we can add an ad hoc ip to enable it on a temporary basis without a firewall push.&lt;/P&gt;</description>
    <pubDate>Fri, 06 Sep 2024 14:55:06 GMT</pubDate>
    <dc:creator>George_Ellis</dc:creator>
    <dc:date>2024-09-06T14:55:06Z</dc:date>
    <item>
      <title>Is /home/cp_extensions ok to use for GDCO files?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Is-home-cp-extensions-ok-to-use-for-GDCO-files/m-p/225885#M37675</link>
      <description>&lt;P&gt;A lot of the examples use the /tmp directory to store a json for configuring Generic Data Center Objects.&amp;nbsp; I find using /tmp risky as that will be one of the places a person will look to save space when free space is needed.&amp;nbsp; Since GDCO is "Check Point", it made sense at the moment to use the /home/cp_extensions directory to store the .json files.&lt;BR /&gt;&lt;BR /&gt;I would consider that we would need to verify the changes to that directory during upgrades.&amp;nbsp; But is there a reason not to touch that directory?&lt;BR /&gt;&lt;BR /&gt;If you wonder why, during troubleshooting network issues, our team wants to be able to run a Cisco Thousands Eyes client on the troubled client or server.&amp;nbsp; So we can add an ad hoc ip to enable it on a temporary basis without a firewall push.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Sep 2024 14:55:06 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Is-home-cp-extensions-ok-to-use-for-GDCO-files/m-p/225885#M37675</guid>
      <dc:creator>George_Ellis</dc:creator>
      <dc:date>2024-09-06T14:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: Is /home/cp_extensions ok to use for GDCO files?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Is-home-cp-extensions-ok-to-use-for-GDCO-files/m-p/225889#M37677</link>
      <description>&lt;P&gt;I have no clue in the world if thats officially supported, but I did it before and worked fine, no issues.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Fri, 06 Sep 2024 16:05:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Is-home-cp-extensions-ok-to-use-for-GDCO-files/m-p/225889#M37677</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-09-06T16:05:22Z</dc:date>
    </item>
  </channel>
</rss>

