@leviathan
Thank you, for your answer!
You were right with the symbolic link. There were 2 symbolic links.
/etc/systemd/system/multi-user.target.wants/@hifi-domain-server.service
/etc/systemd/system/multi-user.target.wants/@hifi-assignment-client.service
According to your suggestion I deleted the symbolic links, and created copies from the original files from “/lib/systemd/system” into “/etc/systemd/system/multi-user.target.wants”. In this way the directory “.local/share/highfidelity” was created at the wrong place “/”. Also I put the copied files into “/etc/systemd/system”. But with the real configuration files in this place the system daemon are not started the domain-server and the assignment-client.
My Solution first step :
I put the copied files into “/etc/systemd/system”.
/etc/systemd/system/hifi-domain-server.service
/etc/systemd/system/hifi-assignment-client.service
My Solution second step:
I created again the symbolic links at the original place, but now from the new file copies.
/etc/systemd/system/multi-user.target.wants/@hifi-domain-server.service
/etc/systemd/system/multi-user.target.wants/@hifi-assignment-client.service
In this way the directory “.local/share/highfidelity” was created in the right place as:
/root/.local/share/highfidelity"
And the configuration files in the /etc directory were not overwritten with an update.
Ok, this is sure a solution, but I think there be a better way. It is possible, that you insert the defines for User and Group into the configuration files in your repository/source code? Also:
User=root
Group=root
into the original files
/lib/systemd/system/hifi-domain-server.service
/lib/systemd/system/hifi-assignment-client.service
PS: Sorry I forgot it. The copied files included the defines:
User=root
Group=root
in the [Service] section.