<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Maybe consol user can simply use interactive job? Other approach would be to reboot the computer to different os image, probably killing the job. You can also think about those hosts reservation for working hours to prevent long jobs start just before interactive use in form of slurm job or just someone using it directly even without server reboot..</div><div><br></div><div>Cheers, </div><div>marcin</div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Patrick Goetz <pgoetz@math.utexas.edu> </div><div>Date: 06/04/2018 06:00 (GMT-11:00) </div><div>To: Slurm User Community List <slurm-users@lists.schedmd.com> </div><div>Subject: [slurm-users] Running Slurm on a single host? </div><div><br></div></div>I've been using Slurm on a traditional CPU compute cluster, but am now <br>looking at a somewhat different issue. We recently purchased a single <br>machine with 10 high end graphics cards to be used for CUDA calculations <br>and which will shared among a couple of different user groups.<br><br>Does it make sense to use Slurm for scheduling in this case? We'll want <br>to do things like limit the number of GPU's any one user can use and <br>manage resource contention the same way one would for a cluster. <br>Potentially this would mean running slurmctld and slurmd on the same host?<br><br>Bonus question: these research groups (they do roughly the same kind of <br>work) also have a pool of GPU workstations they're going to share. It <br>would be super cool if we could somehow rope the workstations into the <br>resource pool in cases where no one is working at the console. Because <br>some of this stuff involves steps with interactive components, the <br>understanding would be that all resources go to a console user when <br>there is a console user.<br><br><br><br><br></body></html>