Hello,
is it possible to restrict access to a queue by anything but ACL or
project? A complex/resource would be a favourite. Possible alternative -
is there a way to set things up so that interactive jobs aren't
suspended via queue subordination (on a specific hostgroup)?
Scenario is this - cluster with multiple (subordinate) queues; access to
the highest priority one is limited (both user and/or project, depending
on host group). Unfortunately, now also got an interactive job that
should not be suspended regardless of who's running it. Not quite sure
if they need to be in highest priority queue (might be the easiest).
I could introduce a project for this I suppose; however, if there was a
way to solve it with a resource I'd prefer that. Any suggestions?
Tina
--
Tina Friedrich, Computer Systems Administrator, Diamond Light Source Ltd
Diamond House, Harwell Science and Innovation Campus - 01235 77 8442
--
This e-mail and any attachments may contain confidential, copyright and or
privileged material, and are for the use of the intended addressee only. If you
are not the intended addressee or an authorised recipient of the addressee
please notify us of receipt by returning the e-mail and do not use, copy,
retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and
Wales with its registered office at Diamond House, Harwell Science and
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
