2014-08-22 10:39 GMT+02:00 Antony Cleave <antony.cle...@gmail.com>: > This is great news, the final part of the puzzle is how do you access the > text of the job script? I'd assume that there is an environment variable > with the script in it but I can't find it in the prolog guide. Getting it > into mysql won't be a problem > > Cheers > > Antony > > this SCRIPT=$(base64 -w0 /var/spool/slurm/job.$JOBID/script) ENVIRONMENT=$(base64 -w0 /var/spool/slurm/job.$JOBID/environment) is part of our script:
the exec location may depend on your configuration - check StateSaveLocation in your slurm.conf. You may be also interested in using slurmmon whitespace's, you can find slurmmon project on github. cheers, marcin > > > On 21/08/2014 19:18, Marcin Stolarek wrote: > > > > W dniu czwartek, 21 sierpnia 2014 Antony Cleave <antony.cle...@gmail.com> > napisał(a): > >> >> Is it possible to store the job submission script and the environment >> variables passed to it in the account database or log this data >> automatically to /path/to/spylog/<SLURM_JOB_ID>.log files in SLURM? >> >> I'm interested in analysing what the cluster is used for over time and >> this would be a good start in working out what is really being submitted. > > > You can slurmctld prologue, we use this and put every job script into > mysql. > Cheers, > Marcin > >> >> Thanks >> >> Antony >> > >
