Hi Danny, > Based on the talk you referenced it looks like expiry was something they > wanted to add. If you knew the end time of the project the easiest way to > make it so the account couldn't run is set the GrpCPUMins=0 when the end > time happens, or just remove the account from Slurm. I am unaware of > anything that does this automatically with Slurm, but a cronjob running a > script every day or so might give you what you are looking for.
thanks - this was my line of thinking as well, just wanted to check with you guys that there isn't anything else I'm missing. We can certainly enforce the expiry of limits with setting GrpCPUMins=0 via cronjob, but we also need a command to display allocation dates/sizes/expiry etc. Looks like something we need to script around SLURM :) cheers, Maciej -- Maciej Olchowik HPC Systems Administrator KAUST Supercomputing Laboratory (KSL) Al Khawarizmi Bldg. (1) Room 0134 Thuwal, Kingdom of Saudi Arabia tel +966 2 808 0684 ________________________________ This message and its contents including attachments are intended solely for the original recipient. If you are not the intended recipient or have received this message in error, please notify me immediately and delete this message from your computer system. Any unauthorized use or distribution is prohibited. Please consider the environment before printing this email.
