I see. Thanks a lot for the in depth explanation.
On Tue, 9 Jul 2019 at 16:27, Jeffrey Frey wrote:
> "-uid" is a perfectly valid sbatch flag:
>
>
>-u, --usage
> Display brief help message and exit.
>
>-i, --input=
> Instruct Slurm to connect the batch
"-uid" is a perfectly valid sbatch flag:
-u, --usage
Display brief help message and exit.
-i, --input=
Instruct Slurm to connect the batch script's standard input
directly to the file name specified in the
"filename pattern".
Slight correction, it does not look for a file named "d" in the home folder
of the user in the (mistyped) -uid parameter, it looks for a file named "d"
in the home folder of the user running sbatch. If this is not an expected
behaviour, I will make a complete bug report.
On Tue, 9 Jul 2019 at 15
Thanks a lot for your answers again!
@Marcus Thanks a lot for the clarification.
About --uid, you are correct, I was mistyping it as -uid. But, the
behaviour is slightly inconsistent:
* If correctly typed (--uid) sbatch properly complains about needing to be
root
* If not present at all, or ignor
> So, if I understand this correctly, for some reason, `srun` does not need
> root privileges on the computation node side, but `sbatch` does when
> scheduling. I was afraid doing so would mean users could do things such as
> apt install and such, but it does not seem the case.
The critical par
Hi Daniel,
I strongly recommend to let SlurmdUser be root.
slurmd starts slurmstepd, but without root privileges, as the specific
user. That is the program, that actually executes the jobscript.
But slurmd needs to bee root, e.g. to execute prolog and epilog scripts,
which in many cases need
Thanks a lot for the answers!
So, if I understand this correctly, for some reason, `srun` does not need
root privileges on the computation node side, but `sbatch` does when
scheduling. I was afraid doing so would mean users could do things such as
apt install and such, but it does not seem the cas
Hi
I can't find the reference here, but if I recall correctly the preferred
user for slurmd is actually root. It is the default.
> I assume this can be fixed by modifying the configuration so
"SlurmdUser=root", but does this imply that anything run with `srun` will
be actually executed by root?
Sudo is more flexible than than; for example you can just give the
slurmduser sudo access to the chown command and nothing else.
On 7/8/19 11:37 AM, Daniel Torregrosa wrote:
> You are right. The critical part I was missing is that chown does not
> work without sudo.
>
> I assume this can be fix
You are right. The critical part I was missing is that chown does not work
without sudo.
I assume this can be fixed by modifying the configuration so
"SlurmdUser=root", but does this imply that anything run with `srun` will
be actually executed by root? This seems dangerous.
Thanks a lot.
On Mon
Hi all,
I am currently testing slurm (slurm-wlm 17.11.2 from a newly installed and
updated Ubuntu server LTS). I managed to make it work on a very simple 1
master node and 2 compute nodes configuration. All three nodes have the
same users (namely root, slurm and test), with slurm running both slur
11 matches
Mail list logo
