If you really do want to have control over providing arbitrary strings back to the user, then a spank plugin might also be a possibility. We have used the slurm_spank_init_post_opt() callback as a mechanism to create a custom job submission filter for srun/sbatch.
It's nothing fancy, but it gives us a way to do some quick sanity checking and apply some local site requirements like: verifying user is not over any of their disk quotas, verifying user provided a max runlimit, additional ACLs for the queue's, maximum jobs per user, etc. In this approach, stdout will be seen by the user and you can customize as desired. On Jan 29, 2013, at 11:31 AM, Moe Jette <[email protected]> wrote: > > I would suggest an job_submit plugin: > > http://www.schedmd.com/slurmdocs/job_submit_plugins.html > > There is no mechanism to return a string to the user, only an exit > code, but adding a few new exit codes would be simple (see > slurm/slurm_errno.h and src/common/slurm_errno.c). We have also > discussed adding a mechanism to return an arbitrary string to the > user, but this is not possible today. > > Quoting Magnus Jonsson <[email protected]>: > >> Hi! >> >> I looking for a way to look at users submitted parameters and if >> they are using it in a "bad" way inform them that this might not be >> a good usage of the system and point them to documentation about how >> slurm works and how to best use it in our system. >> >> I have tried different approaches but failed on every one.. >> >> Any hints? >> >> Best regards, >> Magnus >> >> -- >> Magnus Jonsson, Developer, HPC2N, Umeå Universitet >> >> >
