[slurm-users] Question: How to see all srun/sbatch commands in one place?

2019-01-24 Thread AiO
Hi guys! Is there a way to 'tail -f' or equivalent some file (with some slurmctld configuration) tå see what shell commands are deployed to all the slurm hosts? I would like to centralize logging interleaved with other security-related logging to get chronological chain of events perfromed.

Re: [slurm-users] Question: How to see all srun/sbatch commands in one place?

2019-01-24 Thread mercan
Hi; You can use a job submit plugin to logging. We use lua job_submit plugin. The slurm.log_info() function writes a string to slurmctl log file. But we use a seperate file as a user activity log file. The logging lua code something as below:     dt = os.date()     jaccount = job_des

[slurm-users] Email parameters

2019-01-24 Thread Andre Torres
Hi all, Does anyone know how can I change the “from address”  for the job emails ? Thanks in advance, Andre

Re: [slurm-users] Email parameters

2019-01-24 Thread Sternberger, Sven
Hello! a simple way is to set MailProg in slurm.conf like MailProg = /usr/local/bin/myscript.sh and write a simple script #! /bin/bash /bin/mail -r "SLURM Daemon " "$@" best regards > Von: "Andre Torres" > An: slurm-users@lists.schedmd.com > Gesendet: Donnerstag, 24. Januar 2019 17:10

[slurm-users] salloc --no-shell question

2019-01-24 Thread Pritchard Jr., Howard
Hello Slurm experts, We have a workflow where we have a script which invoke salloc —noshell and then launches a series of MPI jobs using srun with the jobid= option to make use of the reservation we got from the salloc invocation. We are needing to do things this way because the script itself ne

Re: [slurm-users] salloc --no-shell question

2019-01-24 Thread Douglas Jacobsen
Hmmm, I can't quite replicate that: dmj@cori11:~> salloc -C knl -q interactive -N 2 --no-shell salloc: Granted job allocation 18219715 salloc: Waiting for resource configuration salloc: Nodes nid0[2318-2319] are ready for job dmj@cori11:~> srun --jobid=18219715 /bin/false srun: error: nid02318: t