Dear Reuti.
Yes, i use the -now no .
So, there is no way to limit the time of a interactive job like i do
here....
Thank's.
Le 26/11/2017 à 11:51, Reuti a écrit :
Hi,
Am 24.11.2017 um 19:52 schrieb Jerome:
Hi all
I've a cluster with a special queue for interactive jobs, named express.q.
My default queue "all.q" is normaly not for interactive jobs, as define here..
$ qconf -sq all.q
qname all.q
hostlist @allhosts
seq_no 0
load_thresholds np_load_avg=1.25
../..
qtype BATCH
../..
$ qconf -sq express.q
qname express.q
hostlist @allhosts
seq_no 0
load_thresholds np_load_avg=1.75
../..
qtype INTERACTIVE
For a while now, when i run a qrsh command, i go to the all.q queue, not to
express.q. the problem is that the special interactive queue have a time limit
of 2 hours. That don't have all.q!
Where i'm wrong in my configuration?
Did you use by chance "-now n"? This will route the job to a queue of type BATCH. Specifying
INTERACTIVE in a queue definition is more like "immediate" than "interactive".
-- Reuti
Regards.
--
-- Jérôme
Conduire dans Paris, c'est une question de vocabulaire.
(Michel Audiard)
_______________________________________________
SGE-discuss mailing list
SGE-discuss@liv.ac.uk
https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
--
-- Jérôme
Beau jeune homme, il doit pas être loin de ses 75 kilos.
- J'l'ai pas pesé!
- Dans ces poids-là, j'peux vous l'embaumer façon Cléopatre, le Chef
d'Oeuvre égyptien, inaltérable!
- Mais on vous demande pas de conserver, on vous demande de détruire!
(Michel Audiard)
_______________________________________________
SGE-discuss mailing list
SGE-discuss@liv.ac.uk
https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
