<?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: delay individual crontabs in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187993#M796199</link>
    <description>As long as the user is a cron user (as specified in /var/adm/cron/at.allow) then he can manage his own crontab. You simply drop the su - someuser commands in my above responce. You could put together a script to do all of this for him, saving his cronjobs file in his home directory.&lt;BR /&gt;</description>
    <pubDate>Tue, 10 Feb 2004 11:59:12 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2004-02-10T11:59:12Z</dc:date>
    <item>
      <title>delay individual crontabs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187988#M796194</link>
      <description>I would like to be able to stop an individual users crontab from time to time -- without effecting other crontabs.  Is there a slick way to go about this?  Why isn't there a "crontab -delay" swicth?&lt;BR /&gt;&lt;BR /&gt;Thanks!!</description>
      <pubDate>Tue, 10 Feb 2004 11:41:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187988#M796194</guid>
      <dc:creator>Mark Ellis</dc:creator>
      <dc:date>2004-02-10T11:41:16Z</dc:date>
    </item>
    <item>
      <title>Re: delay individual crontabs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187989#M796195</link>
      <description>Mark,&lt;BR /&gt;&lt;BR /&gt;I guess you could try editing, moving or renaming individual users crontabs in /var/spool/crontabs/&lt;USERNAME&gt;.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete&lt;/USERNAME&gt;</description>
      <pubDate>Tue, 10 Feb 2004 11:46:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187989#M796195</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2004-02-10T11:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: delay individual crontabs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187990#M796196</link>
      <description>The usual way to adjust crontab is to-&lt;BR /&gt;crontab -l &amp;gt;my.cron&lt;BR /&gt;vi my.cron&lt;BR /&gt;crontab &lt;MY.CRON&gt;&lt;/MY.CRON&gt; &lt;BR /&gt;Each individual user has a seperate crontab file (As I guess from your description). If you do the following as root, you can deactivate one specific user-&lt;BR /&gt; &lt;BR /&gt;echo "crontab -l &amp;gt;/tmp/joeuser.cron ; crontab  &lt;BR /&gt;This will save the users current crontab then clear out the crontab.&lt;BR /&gt; &lt;BR /&gt;HTH&lt;BR /&gt; &lt;BR /&gt;-- Rod Hills</description>
      <pubDate>Tue, 10 Feb 2004 11:50:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187990#M796196</guid>
      <dc:creator>Rodney Hills</dc:creator>
      <dc:date>2004-02-10T11:50:11Z</dc:date>
    </item>
    <item>
      <title>Re: delay individual crontabs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187991#M796197</link>
      <description>I don't know if this is slick enough to make you sweat Wesson Oil but here is one approach:&lt;BR /&gt;&lt;BR /&gt;su - someuser&lt;BR /&gt;crontab -l &amp;gt; someuser.crontab # don't lose this file!!&lt;BR /&gt;crontab &amp;lt; /dev/null&lt;BR /&gt;exit&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;At this point, someuser's crontab is now empty.&lt;BR /&gt;&lt;BR /&gt;To restore at some later time:&lt;BR /&gt;su - someuser&lt;BR /&gt;crontab &amp;lt; someuser.crontab&lt;BR /&gt;exit&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Feb 2004 11:52:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187991#M796197</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-02-10T11:52:45Z</dc:date>
    </item>
    <item>
      <title>Re: delay individual crontabs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187992#M796198</link>
      <description>I would like "root" intervention to be taken out of the loop and allow this user to stop their crontab jobs at any given time on their own.</description>
      <pubDate>Tue, 10 Feb 2004 11:52:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187992#M796198</guid>
      <dc:creator>Mark Ellis</dc:creator>
      <dc:date>2004-02-10T11:52:51Z</dc:date>
    </item>
    <item>
      <title>Re: delay individual crontabs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187993#M796199</link>
      <description>As long as the user is a cron user (as specified in /var/adm/cron/at.allow) then he can manage his own crontab. You simply drop the su - someuser commands in my above responce. You could put together a script to do all of this for him, saving his cronjobs file in his home directory.&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Feb 2004 11:59:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187993#M796199</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-02-10T11:59:12Z</dc:date>
    </item>
    <item>
      <title>Re: delay individual crontabs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187994#M796200</link>
      <description>The same technique (crontab -l &amp;gt; somefile, etc) can work for the user as well.  You could even script it for them.  One script to set it aside, one to put it back.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Tue, 10 Feb 2004 11:59:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187994#M796200</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2004-02-10T11:59:17Z</dc:date>
    </item>
    <item>
      <title>Re: delay individual crontabs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187995#M796201</link>
      <description>Thank you all!</description>
      <pubDate>Tue, 10 Feb 2004 12:02:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187995#M796201</guid>
      <dc:creator>Mark Ellis</dc:creator>
      <dc:date>2004-02-10T12:02:49Z</dc:date>
    </item>
    <item>
      <title>Re: delay individual crontabs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187996#M796202</link>
      <description>The other option would be to build in the delay mechanism to the jobs they're running.&lt;BR /&gt;&lt;BR /&gt;while [ -f /tmp/CRONLOCK ]&lt;BR /&gt;do&lt;BR /&gt;echo "Cron locked.  Sleeping."&lt;BR /&gt;sleep 30&lt;BR /&gt;done&lt;BR /&gt;&lt;BR /&gt;Then, when you create /tmp/CRONLOCK, the jobs will sleep until the file is removed.&lt;BR /&gt;&lt;BR /&gt;if you need to lock cron on a user-by-user basis, use a file from CRONLOCK.&lt;USERNAME&gt;&lt;BR /&gt;&lt;/USERNAME&gt;</description>
      <pubDate>Tue, 10 Feb 2004 12:06:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/delay-individual-crontabs/m-p/3187996#M796202</guid>
      <dc:creator>Chris Wilshaw</dc:creator>
      <dc:date>2004-02-10T12:06:55Z</dc:date>
    </item>
  </channel>
</rss>

