[torqueusers] Torque not killing job exceeding memory requested

Seb Seb sebast2600 at yahoo.fr
Thu Jan 18 16:21:46 MST 2007

  As recommended by Seb, a couple of minutes ago I enabled the 

but so far it is still running...
  Did you restart MOAB after you made the change in the cfg file?
  It may takes a few minutes before the job gets killed though.

Troy Baer wrote:
> On Wed, 2007-01-17 at 11:04 -0600, Laurence Dawson wrote:
>> A user has two jobs running on a single (dual-dual processor box)
> node. 
>> It is exceeding the memory he requested, but torque is not killing 
>> it...why? Has anyone seen this on their configuration? We are running 
>> moab-4.5.0p4 and torque-2.1.0p0.
> What OS/architecture? And what does TORQUE report for memory usage vs.
> requested? (I.e. "qstat -f jobid | grep mem")
> --Troy

torqueusers mailing list
torqueusers at supercluster.org

 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 Yahoo! Questions/Réponses.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.supercluster.org/pipermail/torqueusers/attachments/20070119/06df2515/attachment.html

More information about the torqueusers mailing list