Thanks Paul, this helps.
I don't have any PrivateData line in either config file. According to the
docs, "By default, all information is visible to all users" so this should
not be an issue. I tried to add a line with "PrivateData=jobs" to the conf
files, just in case, but that didn't change the b
At least in our setup, users can see their own scripts by doing sacct -B
-j JOBID
I would make sure that the scripts are being stored and how you have
PrivateData set.
-Paul Edmon-
On 10/2/2023 10:57 AM, Davide DelVento wrote:
I deployed the job_script archival and it is working, however it
I deployed the job_script archival and it is working, however it can be
queried only by root.
A regular user can run sacct -lj towards any jobs (even those by other
users, and that's okay in our setup) with no problem. However if they run
sacct -j job_id --batch-script even against a job they own
This is a strange one
I have built a Slurm cluster using AWS parallelcluster and noticed that the
permissions of my /etc/sysconfig directory are broken!
I have found the logs that support this find but don't have any idea why this
is happening nor where to find the necessary script/config file t
