<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"> <div>As recommended by Seb, a couple of minutes ago I enabled the <BR>RESOURCELIMITPOLICY MEM:ALWAYS:CANCEL,<BR><BR>but so far it is still running...</div> <div> </div></BLOCKQUOTE> <div>Did you restart MOAB after you made the change in the cfg file?</div> <div> </div> <div>It may takes a few minutes before the job gets killed though.</div> <div> </div> <div>Seb.<BR><BR><BR><BR><BR><BR>Troy Baer wrote:<BR>> On Wed, 2007-01-17 at 11:04 -0600, Laurence Dawson wrote:<BR>> <BR>>> A user has two jobs running on a single (dual-dual processor box)<BR>>> <BR>> node. <BR>> <BR>>> It is exceeding the memory he requested, but torque is not killing <BR>>> it...why? Has anyone seen this on their configuration? We are running <BR>>> moab-4.5.0p4 and torque-2.1.0p0.<BR>>> <BR>><BR>> What OS/architecture? And what
does TORQUE report for memory usage vs.<BR>> requested? (I.e. "qstat -f jobid | grep mem")<BR>><BR>> --Troy<BR>> <BR><BR>_______________________________________________<BR>torqueusers mailing list<BR>torqueusers@supercluster.org<BR>http://www.supercluster.org/mailman/listinfo/torqueusers<BR></div><BR><p> 
<hr size="1">
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur <a href="http://fr.rd.yahoo.com/evt=42054/*http://fr.answers.yahoo.com">Yahoo! Questions/Réponses</a>.