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.service.d/
and drop files into it via the Configuration Management System Of Your
Choice to override/augment the vendor supplied configuration.
https://www.freedesktop.org/software/systemd/man/systemd.unit.html
> Along with a unit file foo.service, a "drop-in" directory
> foo.service.d/ may exist. All files with the suffix ".conf"
> from this directory will be merged in the alphanumeric order
> and parsed after the main unit file itself has been parsed.
> This is useful to alter or add configuration settings for a
> unit, without having to modify unit files. Each drop-in file
> must contain appropriate section headers. For instantiated
> units, this logic will first look for the instance ".d/"
> subdirectory (e.g. "foo@bar.service.d/") and read its ".conf"
> files, followed by the template ".d/" subdirectory
> (e.g. "foo@.service.d/") and the ".conf" files there.
Caveat: written whilst travelling and without testing or even having
access to a system where I can test, but we do use this method for other
services already.
All the best,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA
