/Magnus
On 2015-04-21 14:40, Andy Riebs wrote:
Never mind; which I changed "#sbatch" to the correct "#SBATCH", I got 4 tasks. According to the man page, this is a bug. For now, I like Magnus's suggestion :-) On 04/21/2015 08:21 AM, Andy Riebs wrote:Hendryk, what sbatch command line options are you using? How are you determining that job 1 got 2 tasks? I just tried the following script, and it correctly ran just 1 task: $ cat test.sh #!/bin/bash #SBATCH --ntasks=1 srun hostname #sbatch --ntasks=4 ## end of script $ sbatch test.sh Submitted batch job 18720 $ cat slurm-18720.out node09 $ For further discussion on this topic, please 1. Reply to the whole list, not just me 2. Indicate what OS and Slurm versions you are using 3. Provide a copy of your slurm.conf file with any sensitive information, like node names or IP addresses, removed Andy On 04/21/2015 07:50 AM, Hendryk Bockelmann wrote:Hello, is there a way to prevent slurm from parsing the whole jobscript for #SBATCH statements? Assume I have the following jobscript "job1.sh": #!/bin/bash #SBATCH --nodes=1 #SBATCH --ntasks=1 #SBATCH --job-name=job1 srun -l echo "slurm jobid $SLURM_JOB_ID named: $SLURM_JOB_NAME" cat > job2.sh <<EOF #!/bin/bash #SBATCH --nodes=1 #SBATCH --ntasks=2 #SBATCH --job-name=job2 srun -l echo "slurm jobid \$SLURM_JOB_ID named: \$SLURM_JOB_NAME" EOF sbatch job2.sh If I submit the job1.sh the resources are allocated such that 2 tasks are given and not 1. I would like to have 1 task for the first job (as in the very first lines) and then a different setting for the created job ... Thanx for any help, Hendryk
-- Magnus Jonsson, Developer, HPC2N, Umeå Universitet
smime.p7s
Description: S/MIME Cryptographic Signature
