On 29/12/22 11:31 am, Timo Rothenpieler wrote:
Having service files in top level dirs like /run or /var/lib is bound to
cause issues like this.
You can use local systemd overrides for things like this. In this case I
suspect you can create this directory:
/etc/systemd/system/slurmrestd.serv
Ideally, the systemd service would specify the User/Group already, and
then also specify RuntimeDirectory=slurmrestd.
It then pre-creates a slurmrestd directory in /run for the service to
put its runtime files (like sockets) into, avoiding any permission issues.
Having service files in top leve
Thanks Brian!
I also discovered that I can edit the service file to remove the unix
socket. Doesn't seem to impact the things I'm working with anyway. But
this design choice still seems strange to me that editing the service
file is required. It seems like this should also be a configurable it
I dug up my old stuff for getting it started and see that I just
disabled the unix socket completely. I was never able to get it to work
for the reasons you are seeing, so I enabled it in listening mode. There
are comments in the service file about it, but to do so, I changed the
'ExecStart' li
Greetings,
Thanks for responding!
On 12/28/22 20:35, Brian Andrus wrote:
I suspect if you delete /var/lib/slurmrestd.socket and then start
slurmrestd, it will create it as the user you need it to be.
Or just change the owner of it to the slurmrestd owner.
No go on that. Because /var/lib re
