On 15 Feb 2014 03:47, Yuri D'Elia <[email protected]> wrote: > > > On 02/14/2014 02:54 AM, Franco Broi wrote: > > > > > > I'm also trying to pass some job dependent information to the trigger > > script. Is there somewhere in the job structure for user defined > > information to be stored? I could them retrieve this using the jobid. > > I was thinking of using an environment variable in the job itself (not > the trigger): > > sbatch --export DATA=[vvv] > > and retrieve it using the api (if that's possible at all).
I don't think you can do that as the trigger is run from the slurm scheduler. > > But depending on the trigger, the job state might be already gone by the > time you need it. > > Encoding it in the comment is also a possibility, since you could later > use sacct at any time to fetch it. But at the moment I'm already using > the comment to encode other job details (and feels unclean anyway). ________________________________ This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately notify the sender and delete the original.
