<?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: at queues in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087962#M309953</link>
    <description>But users won't be able to send an atjob while the queue being stopped, will they ?</description>
    <pubDate>Thu, 18 Oct 2007 07:20:02 GMT</pubDate>
    <dc:creator>jigeay</dc:creator>
    <dc:date>2007-10-18T07:20:02Z</dc:date>
    <item>
      <title>at queues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087960#M309951</link>
      <description>Bonjour,&lt;BR /&gt;I'd like to know if there is anyway to stop and restart an atqueue ? eg. I don't wan't the queue "d" to run between 7am and 7pm, but people still can enqueue jobs in it during the day. At 7pm, the queue is "released", and jobs piles down.&lt;BR /&gt;&lt;BR /&gt;thank you.</description>
      <pubDate>Thu, 18 Oct 2007 02:42:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087960#M309951</guid>
      <dc:creator>jigeay</dc:creator>
      <dc:date>2007-10-18T02:42:15Z</dc:date>
    </item>
    <item>
      <title>Re: at queues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087961#M309952</link>
      <description>Hi Matthieu:&lt;BR /&gt;&lt;BR /&gt;You could craft a root crontask that swaps either the file '/usr/lib/cron/at.allow' or '/usr/lib/cron/at.deny' before and after the period of time you want to restrict.&lt;BR /&gt;&lt;BR /&gt;For example, to stop 'at' queuing, by all users, replace the '/usr/lib/cron/at.allow' file with a null file, saving the current file with an alternate name.  To re-enable 'at' activity, copy the saved file back.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Thu, 18 Oct 2007 04:56:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087961#M309952</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2007-10-18T04:56:29Z</dc:date>
    </item>
    <item>
      <title>Re: at queues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087962#M309953</link>
      <description>But users won't be able to send an atjob while the queue being stopped, will they ?</description>
      <pubDate>Thu, 18 Oct 2007 07:20:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087962#M309953</guid>
      <dc:creator>jigeay</dc:creator>
      <dc:date>2007-10-18T07:20:02Z</dc:date>
    </item>
    <item>
      <title>Re: at queues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087963#M309954</link>
      <description>Hi (again) Matthieu:&lt;BR /&gt;&lt;BR /&gt;&amp;gt; But users won't be able to send an atjob while the queue being stopped, will they ?&lt;BR /&gt;&lt;BR /&gt;Yes, that is true.  I'm sorry, I glossed over that part of your requirement in answering your original query.&lt;BR /&gt;&lt;BR /&gt;My suggestion treats the 'at' mechanism as an interactive, ad hoc one.  Hence, my thinking is/was that the user would be denied the submission but could perform it again later.&lt;BR /&gt; &lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Thu, 18 Oct 2007 07:33:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087963#M309954</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2007-10-18T07:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: at queues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087964#M309955</link>
      <description>No, they will be rejected.&lt;BR /&gt;But I doubt that an at job is the appropriate form since you daily seem to want to have an accumulated bunch of users' jobs executed, if I understood you correctly.&lt;BR /&gt;Maybe you could script up something where you build up a batch of users' jobs over the day and parse them with sufficient authorization checking, which I assume can be cumbersome, to finally have them run at usual batch jobs at a scheduled time.&lt;BR /&gt;Linux boxes usually come with a daemon that is called "anacron" and which caters for the usual desktop PC situation where the host is not running continuously like a server but powered down at irregular intervals.&lt;BR /&gt;Maybe you can get a port for other Unices as well?&lt;BR /&gt;&lt;A href="http://en.wikipedia.org/wiki/Anacron" target="_blank"&gt;http://en.wikipedia.org/wiki/Anacron&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 18 Oct 2007 07:42:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087964#M309955</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2007-10-18T07:42:47Z</dc:date>
    </item>
    <item>
      <title>Re: at queues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087965#M309956</link>
      <description>Thank you for your replies.&lt;BR /&gt;Ralph, i'm totally agree with you, and that is what i've tried to explain to the user who wants me to do such a thing. Finaly, i wrote a script which tests the time befor executing each job but i'm not happy with that. &lt;BR /&gt;I'm going to look for anacron.</description>
      <pubDate>Thu, 18 Oct 2007 07:59:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/at-queues/m-p/4087965#M309956</guid>
      <dc:creator>jigeay</dc:creator>
      <dc:date>2007-10-18T07:59:28Z</dc:date>
    </item>
  </channel>
</rss>

