Hi Lois Thanks for letting us know!
So out of the box there's no way to know what script for example a user ran in a particular job? Wish that feature existed as we sometimes have users who contact us regarding jobs that exited weeks ago. We will look into the solution you suggest. Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: d...@med.cornell.edu<mailto:d...@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Wed, Nov 21, 2018 at 1:40 AM Loris Bennett <loris.benn...@fu-berlin.de<mailto:loris.benn...@fu-berlin.de>> wrote: Hi Douglas, Douglas Duckworth <dod2...@med.cornell.edu<mailto:dod2...@med.cornell.edu>> writes: > Hi > > We are in the process of migrating several clusters from SGE to Slurm. > > We discovered that accounting does not show what command a previous > job ran. For currently running jobs scontrol for example will show: > > JobId=33028 JobName=bash > Command=bash > > Yet we would like to have that stored in accounting as it's useful for > jobs that existed ungracefully. > > Any way to accomplish with Slurm version 17.02? > > "sacct -e" does not show "Command" as a possible field. As far as I am aware, Slurm does not retain this information. Even if it did, for jobs started with 'sbatch' the 'Command' field contains the name of the batch file, which may not be that useful. An approach some people have mentioned using is collecting the information via a submit plugin and then storing it outside of Slurm's standard accounting. Cheers, Loris -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email loris.benn...@fu-berlin.de<mailto:loris.benn...@fu-berlin.de>
