<?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: cron schedule on tecli command in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cron-schedule-on-tecli-command/m-p/34409#M13427</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks&amp;nbsp;Michael,&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;#!/bin/bash -f&lt;BR /&gt;source /opt/CPshrd-R77/tmp/.CPprofile.sh&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Made the trick.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 Feb 2019 18:12:14 GMT</pubDate>
    <dc:creator>Michal_Gans</dc:creator>
    <dc:date>2019-02-20T18:12:14Z</dc:date>
    <item>
      <title>cron schedule on tecli command</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cron-schedule-on-tecli-command/m-p/34407#M13425</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would like to monitor emulation status on SandBlast appliance, so I want to run "tecli s e v s" by cron every x min.&lt;/P&gt;&lt;P&gt;But if I start&amp;nbsp;tecli command by cron, it ended with this error&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;/opt/CPsuite-R77/fw1/bin/tecli: line 49: /teCurrentPack/temain: No such file or directory&lt;BR /&gt;/opt/CPsuite-R77/fw1/bin/tecli: line 49: exec: /teCurrentPack/temain: cannot execute: No such file or directory&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I want to ask if anybody know which environment parameters need to be set for tecli to run?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2019 16:56:36 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cron-schedule-on-tecli-command/m-p/34407#M13425</guid>
      <dc:creator>Michal_Gans</dc:creator>
      <dc:date>2019-02-19T16:56:36Z</dc:date>
    </item>
    <item>
      <title>Re: cron schedule on tecli command</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cron-schedule-on-tecli-command/m-p/34408#M13426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;tecli requires the $FWDIR environment variable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will need to adjust your cronjob to source the &lt;STRONG&gt;.CPprofile.sh&lt;/STRONG&gt; file under the &lt;STRONG&gt;/opt/CPshrd-RXX.YY/tmp &lt;/STRONG&gt;directory. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2019 17:55:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cron-schedule-on-tecli-command/m-p/34408#M13426</guid>
      <dc:creator>masher</dc:creator>
      <dc:date>2019-02-19T17:55:20Z</dc:date>
    </item>
    <item>
      <title>Re: cron schedule on tecli command</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cron-schedule-on-tecli-command/m-p/34409#M13427</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks&amp;nbsp;Michael,&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;#!/bin/bash -f&lt;BR /&gt;source /opt/CPshrd-R77/tmp/.CPprofile.sh&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Made the trick.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Feb 2019 18:12:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cron-schedule-on-tecli-command/m-p/34409#M13427</guid>
      <dc:creator>Michal_Gans</dc:creator>
      <dc:date>2019-02-20T18:12:14Z</dc:date>
    </item>
  </channel>
</rss>

