Hi, You should take a look at the job_submit plugin. That is the nest place to check if a job should be queued or it can be rejected otherwise.
Regards, Carlos On Thu, Jan 26, 2017 at 1:03 PM, Dmitry Chirikov <[email protected]> wrote: > Hi all, > > Playing with SPANK I faced up with an issue > Seems I can't get any useful bits about job which user is about to submit. > > I am trying to add a hook to allocator context in slurm_spank_init > or slurm_spank_init_post_opt functions. > > Idea was to check some option of the committed job file (or srun options) > and make a decision about should it be accepted to be queued or not: > > But seems like it is not possible to get very basic variables > like S_JOB_ARGV or S_JOB_ENV > > If i get it right this check limits the variables spank able to use to, > literally, slurm version. > https://github.com/SchedMD/slurm/blob/d7770b9b68d992f4f38417d5ef7204 > 895954eff8/src/common/plugstack.c#L1765 > > Prolog facilies were looking promised, but they cannot drop the job - it > can be re-queued only. > > So the question is, how to do it properly, when variables are available to > use, and it is not too late to deny user to submit a job? > > Thank you in advance. > > Kind regards, > Dmitry Chirikov > -- -- Carles Fenoy
