[GE users] How to disable the qsub command ?

Andy Schwierskott andy.schwierskott at sun.com
Mon Dec 3 16:31:33 GMT 2007


Hi,

the simplest way to disable new submits is to create an empty access list and
attach it to the global cluster config ("qconf -mconf") after the keyword
"user_lists"

To stop scheduling just disable all queues or shutdown the scheduler daemon.

Andy

On Mon, 3 Dec 2007, Mulley, Nikhil wrote:

> Its not yet clear whether you want to forbid the jobs getting submitted
> or scheduled;
> I guess if you are looking for stopping the job from getting submitted
> -- ideally nullify the submit hosts (qconf -ss ; qconf -ds) would be
> better when the entire grid is considered.
> If you are just looking for forbidding a user to submit the jobs further
> -- then you could just suspend the queues or alternatively just rename
> the qsub/qrsh until further action required.
>
>
> ________________________________
>
> 	From: Pradeilles Christoph
> [mailto:christoph.pradeilles at consultant.volvo.com]
> 	Sent: Monday, December 03, 2007 3:45 PM
> 	To: users at gridengine.sunsource.net
> 	Subject: [GE users] How to disable the qsub command ?
>
>
> 	Hi,
>
> 	When we are processing intervention/modification on some node,
> or on the whole HPC cluster, we want to forbid to user the submission
> command (qsub, qrsh, etc..). Is there a way to do that without killing
> the 'sge.qmaster' process. Currently we are just disabling the queue...
>
> 	Thank you in advance.
>
> 	Regards,
>
> 	Christophe PRADEILLES
>
>
>
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list