<?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: crontab in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544374#M223855</link>
    <description>Something like this:&lt;BR /&gt;&lt;BR /&gt;########################################################&lt;BR /&gt;# Check to see if it's necessary to make a new recovery tape&lt;BR /&gt;#&lt;BR /&gt; 00 05 * * 1 /opt/ignite/bin/check_recovery&lt;BR /&gt;#&lt;BR /&gt;&lt;BR /&gt;would run check_recovery at 5 minutes after midnight on Monday.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
    <pubDate>Fri, 13 May 2005 12:21:37 GMT</pubDate>
    <dc:creator>Pete Randall</dc:creator>
    <dc:date>2005-05-13T12:21:37Z</dc:date>
    <item>
      <title>crontab</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544372#M223853</link>
      <description>Do you have any example for execute a script in the crontab file?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 13 May 2005 12:15:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544372#M223853</guid>
      <dc:creator>Adrian_72</dc:creator>
      <dc:date>2005-05-13T12:15:12Z</dc:date>
    </item>
    <item>
      <title>Re: crontab</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544373#M223854</link>
      <description>min  hr  day_of_month  month  day_of_week&lt;BR /&gt;&lt;BR /&gt;Example&lt;BR /&gt;0  1  15  *  * /usr/local/bin/my_script&lt;BR /&gt;&lt;BR /&gt;Execute /usr/local/bin/my_script at 0100 hrs on the 15th day of every month.&lt;BR /&gt;&lt;BR /&gt;0 1 * * *&lt;BR /&gt;execute everyday at 0100 hrs.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 13 May 2005 12:21:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544373#M223854</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2005-05-13T12:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: crontab</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544374#M223855</link>
      <description>Something like this:&lt;BR /&gt;&lt;BR /&gt;########################################################&lt;BR /&gt;# Check to see if it's necessary to make a new recovery tape&lt;BR /&gt;#&lt;BR /&gt; 00 05 * * 1 /opt/ignite/bin/check_recovery&lt;BR /&gt;#&lt;BR /&gt;&lt;BR /&gt;would run check_recovery at 5 minutes after midnight on Monday.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Fri, 13 May 2005 12:21:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544374#M223855</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2005-05-13T12:21:37Z</dc:date>
    </item>
    <item>
      <title>Re: crontab</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544375#M223856</link>
      <description>It is very important that you do not edit the cron files directly. For one thing, the cron daemon wouldn't have a clue that you have done anything.&lt;BR /&gt;&lt;BR /&gt;You should do something like this:&lt;BR /&gt;&lt;BR /&gt;Login (or su) as the appropriate user.&lt;BR /&gt;crontab -l &amp;gt; /var/tmp/mycrontab&lt;BR /&gt;edit /var/tmp/mycrontab to add an entry as indicated in the above responses.&lt;BR /&gt;crontab &amp;lt; /var/tmp/mycrontab&lt;BR /&gt;&lt;BR /&gt;Running the crontab command without -l has the effect of reading stdin and sending a SIGHUP to the cron daemon to let it know it should reread the file. Man crontab for details.&lt;BR /&gt;&lt;BR /&gt;A common error when building scripts that are run by cron is not explicitly setting and exporting needed environment variables (including PATH) in the script itself. Cron has an intentionally very sparse environment.&lt;BR /&gt;</description>
      <pubDate>Fri, 13 May 2005 12:27:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544375#M223856</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-05-13T12:27:43Z</dc:date>
    </item>
    <item>
      <title>Re: crontab</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544376#M223857</link>
      <description>I tend to do:&lt;BR /&gt;&lt;BR /&gt;crontab -e&lt;BR /&gt;&lt;BR /&gt;when editing...&lt;BR /&gt;&lt;BR /&gt;Here's a sample entry:&lt;BR /&gt;&lt;BR /&gt;0 6 21 * * [ -d /var/adm/lp/XEBEC ] &amp;amp;&amp;amp; /usr/local/bin/lpqpurge &amp;gt;/tmp/lpqpurge.cronlog 2&amp;gt;&amp;amp;1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;What it does:&lt;BR /&gt;&lt;BR /&gt;at 6 am on the 21st day of every month, it checks to see if the filesystem /var/adm/lp/XEBEC exists - if yes - it then executes the script called /usr/local/bin/lpqpurge.&lt;BR /&gt;&lt;BR /&gt;the &amp;gt;/tmp/lpqpurge.cronlog 2&amp;gt;&amp;amp;1 tells cron to send any output and / or errors to a logfile called /tmp/lpqpurge.cronlog &lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Fri, 13 May 2005 13:05:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544376#M223857</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-05-13T13:05:08Z</dc:date>
    </item>
    <item>
      <title>Re: crontab</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544377#M223858</link>
      <description>Well i hope u will never forget this&lt;BR /&gt;&lt;BR /&gt;MHDMW - mad husband doubt mad wife :)&lt;BR /&gt;      - minute hour day month week.&lt;BR /&gt;&lt;BR /&gt;Remember if you donot redirect your command outputs/error, by default crond will mail the respective owner.&lt;BR /&gt;&lt;BR /&gt;A bit of advice always use "crontab -e" to edit a cron entry entry.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 15 May 2005 05:12:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544377#M223858</guid>
      <dc:creator>Senthil Kumar .A_1</dc:creator>
      <dc:date>2005-05-15T05:12:01Z</dc:date>
    </item>
    <item>
      <title>Re: crontab</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544378#M223859</link>
      <description>LOL, great Senthil, I'll remember that one ;) he he</description>
      <pubDate>Sun, 15 May 2005 14:10:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544378#M223859</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-05-15T14:10:26Z</dc:date>
    </item>
    <item>
      <title>Re: crontab</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544379#M223860</link>
      <description>Adrian,&lt;BR /&gt;&lt;BR /&gt;put this heading in your crontab:&lt;BR /&gt;##############################################################################################&lt;BR /&gt;##  minute  hour   day_month  month_year  day_week   program  [argument(s)]                 ##&lt;BR /&gt;##  (0-59)  (0-23) (1-31)     (1-12)      (0-6 with 0=Sunday)                               ##&lt;BR /&gt;##############################################################################################&lt;BR /&gt;&lt;BR /&gt;Paul.</description>
      <pubDate>Thu, 19 May 2005 08:35:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/crontab/m-p/3544379#M223860</guid>
      <dc:creator>Rob van Buiten</dc:creator>
      <dc:date>2005-05-19T08:35:35Z</dc:date>
    </item>
  </channel>
</rss>

