[torqueusers] Queue configuration question
garrick at clusterresources.com
Wed Oct 4 15:26:19 MDT 2006
On Wed, Oct 04, 2006 at 01:44:10PM -0700, scoggins alleged:
> Is there a way to not allow the bypass?
Well, no, because any command that can typed in interactively can also
be put in a script or piped into qsub.
What kind of actual policy are you trying to enforce?
> If you implement the interactive tag on the queue will that mean it
> will know that the -I option was passed to qsub. In the documents
> using the -I option will set an PBS environment variable to let you
> know they are using it interactively. Can that be something I could
> check for in a prologue script and have that script alter the job to
> the interactive queue?
> Is this an option anyone have tried?
prologue runs as the job is starting, so altering the queue at that
point is useless.
> On Oct 4, 2006, at 11:25 AM, Garrick Staples wrote:
> >On Wed, Oct 04, 2006 at 12:57:24PM -0400, Troy Baer alleged:
> >>On Wed, 2006-10-04 at 09:36 -0700, scoggins wrote:
> >>>I have a cluster and I want to have interactive queues and batch
> >>>queues. I am running torque-1.2.0p2-1.caos and I have the following
> >>>queue configuration:
> >>>What I want is the following behavior to occur:
> >>>qsub -I <script> Goes to the interactive queue by default
> >>>qsub <script> WIll go to the batch queues - geophys or
> >>>geochem which ever one is specified in the script to run on.
> >>>The only queue that has limits is interactive. I want the routing
> >>>queue to be able to submit all interactive jobs to the interactive
> >>>queue and only allow batch (non-interactive) jobs to run on the
> >>>Please advice. Any help will be appreciated.
> >>I don't think that's possible with TORQUE currently -- AFAIK, it's
> >>possible to use whether a job is interactive or not to make a queue
> >>routing decision. That being said, people ask me for something like
> >>that on a regular basis, and it *would* be a very handy feature to
> >>For example:
> >># to enable
> >>qmgr: set queue myqueue interactive = ( True | False )
> >># to disable
> >>qmgr: unset queue myqueue interactive
> >>The default should be that a queue will accept both interactive
> >>and non-
> >>interactive jobs. I have no idea how easy/hard it would be to
> >>implement, though.
> >Easy to implement, but what is the point? Users can trivially bypass
> >any enforced policy based on interactive.
> >torqueusers mailing list
> >torqueusers at supercluster.org
More information about the torqueusers