So, I get [mahmood@rocks7 ~]$ salloc --spankx11 srun ./run_qemu.sh salloc: Granted job allocation 281 srun: error: Bad value for --x11: (null) srun: error: Invalid argument ((null)) for environment variable: SLURM_SPANK__SLURM_SPANK_OPTION_spankx11_spankx11 salloc: Relinquishing job allocation 281
It seems that there is problem with spankx11. However, the "salloc srn hostname" is working as you said and it is fine. [mahmood@rocks7 ~]$ salloc srun hostname salloc: Granted job allocation 282 compute-0-2.local salloc: Relinquishing job allocation 282 Regards, Mahmood On Thu, Jan 3, 2019 at 12:25 AM Ryan Novosielski <novos...@rutgers.edu> wrote: > > On Jan 2, 2019, at 3:49 PM, Mark Hahn <h...@mcmaster.ca> wrote: > > > >> [mahmood@rocks7 ~]$ salloc -n1 hostname > >> salloc: Granted job allocation 278 > >> rocks7.jupiterclusterscu.com > >> salloc: Relinquishing job allocation 278 > >> salloc: Job allocation 278 has been revoked. > >> [mahmood@rocks7 ~]$ > >> > >> As you can see whenever I run salloc, I see the rocks7 prompt which is > the > >> login node. > > > > this is precisely as expected. salloc allocates; srun runs. > > > > to get a compute node do this instead: > > salloc srun hostname > > > > if you actually want to srun an interactive shell each time, > > why are you not using SallocDefaultCommand as others have suggested? > > > > you earlier mentioned wanting to run an X-requiring script. why not > just: > > salloc --x11 srun ./whateveryourscriptwas > > For that matter, however, what’s the advantage of “salloc --x11 srun” vs. > just "srun --x11”? > > -- > ____ > || \\UTGERS, |---------------------------*O*--------------------------- > ||_// the State | Ryan Novosielski - novos...@rutgers.edu > || \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus > || \\ of NJ | Office of Advanced Research Computing - MSB C630, Newark > `' > >
