<?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 hunt - round 3 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cron-hunt-round-3/m-p/2652016#M46263</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;One other suggestion is to use cron to back itself up:&lt;BR /&gt;&lt;BR /&gt;0 0 * * * crontab -l &amp;gt; /usr/local/etc/crontab&lt;BR /&gt;&lt;BR /&gt;then you haven't got to worry about it.&lt;BR /&gt;&lt;BR /&gt;Rgds, Robin.</description>
    <pubDate>Thu, 24 Jan 2002 14:46:34 GMT</pubDate>
    <dc:creator>Robin Wakefield</dc:creator>
    <dc:date>2002-01-24T14:46:34Z</dc:date>
    <item>
      <title>cron hunt - round 3</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cron-hunt-round-3/m-p/2652012#M46259</link>
      <description>When I do a crontab -l it shows me a cron script; but thus far, I have not been able to find out this script is located.  I did a &lt;BR /&gt;find . -name 'cron' and picked through the results.&lt;BR /&gt;&lt;BR /&gt;Comments would be appreciated.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Bill&lt;BR /&gt;&lt;BR /&gt;D. Allen nailed round 2.  There was a cron script that referenced a directory that had been removed.  There were chmod commands in there that whacked other directories.  Thanks to all who responded.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 24 Jan 2002 14:08:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cron-hunt-round-3/m-p/2652012#M46259</guid>
      <dc:creator>Bill Brutzman</dc:creator>
      <dc:date>2002-01-24T14:08:26Z</dc:date>
    </item>
    <item>
      <title>Re: cron hunt - round 3</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cron-hunt-round-3/m-p/2652013#M46260</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;/var/spool/cron/crontabs&lt;BR /&gt;&lt;BR /&gt;Andreas</description>
      <pubDate>Thu, 24 Jan 2002 14:11:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cron-hunt-round-3/m-p/2652013#M46260</guid>
      <dc:creator>Andreas D. Skjervold</dc:creator>
      <dc:date>2002-01-24T14:11:22Z</dc:date>
    </item>
    <item>
      <title>Re: cron hunt - round 3</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cron-hunt-round-3/m-p/2652014#M46261</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Have you looked in /var/spool/cron/crontabs - file name is same as the user you are logged in as.&lt;BR /&gt;&lt;BR /&gt;Hilary&lt;BR /&gt;</description>
      <pubDate>Thu, 24 Jan 2002 14:13:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cron-hunt-round-3/m-p/2652014#M46261</guid>
      <dc:creator>BFA6</dc:creator>
      <dc:date>2002-01-24T14:13:25Z</dc:date>
    </item>
    <item>
      <title>Re: cron hunt - round 3</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cron-hunt-round-3/m-p/2652015#M46262</link>
      <description>Hi Bill,&lt;BR /&gt;&lt;BR /&gt;Crontabs are stored in /var/spool/cron/crontabs.  You should not edit these files directly.&lt;BR /&gt;&lt;BR /&gt;You have 2 options.  "crontab -e" makes a temp copy of your crontab, puts you into edit mode on the temp copy (generally with vi), then replaces the original in /var/spool/cron/crontabs.&lt;BR /&gt;&lt;BR /&gt;The preferred method of editing a crontab is to use "crontab -l &amp;gt;crontab.cpy" to make a copy of the crontab.  Edit that file then use "crontab crontab.cpy" to make it active.&lt;BR /&gt;&lt;BR /&gt;man crontab for more info.&lt;BR /&gt;&lt;BR /&gt;Before doing any edits on your crontab I'd suggest you back it up.  For root, a number of people do:&lt;BR /&gt;cd /var/spool/cron&lt;BR /&gt;cp -p crontabs/root root.crontab&lt;BR /&gt;&lt;BR /&gt;Personally, as the admin of the box, I like to backup all the crontabs:&lt;BR /&gt;cd /var/spool/cron&lt;BR /&gt;mkdir crontabs.bak&lt;BR /&gt;cp -p crontabs/* crontabs.bak&lt;BR /&gt;&lt;BR /&gt;Darrell</description>
      <pubDate>Thu, 24 Jan 2002 14:17:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cron-hunt-round-3/m-p/2652015#M46262</guid>
      <dc:creator>Darrell Allen</dc:creator>
      <dc:date>2002-01-24T14:17:32Z</dc:date>
    </item>
    <item>
      <title>Re: cron hunt - round 3</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cron-hunt-round-3/m-p/2652016#M46263</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;One other suggestion is to use cron to back itself up:&lt;BR /&gt;&lt;BR /&gt;0 0 * * * crontab -l &amp;gt; /usr/local/etc/crontab&lt;BR /&gt;&lt;BR /&gt;then you haven't got to worry about it.&lt;BR /&gt;&lt;BR /&gt;Rgds, Robin.</description>
      <pubDate>Thu, 24 Jan 2002 14:46:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cron-hunt-round-3/m-p/2652016#M46263</guid>
      <dc:creator>Robin Wakefield</dc:creator>
      <dc:date>2002-01-24T14:46:34Z</dc:date>
    </item>
  </channel>
</rss>

