systemd on debian8, a possible solution

[ng0 <contact.ng0@cryptolab.net>]

Hi,

could we point out the solution redhat had in this case?

root@sharknado9000:~# systemctl enable guix-daemon
Failed to execute operation: No such file or directory

The output above was when you follow our documentation.
Now redhat has this workaround
https://bugzilla.redhat.com/show_bug.cgi?id=955379#c30 in
https://bugzilla.redhat.com/show_bug.cgi?id=955379

which seems to work for some versions of systemd (including the one
which is currently used in Debian 8 stable):

root@sharknado9000:~# systemctl enable
/root/.guix-profile/lib/systemd/system/guix-daemon.service
Created symlink from
/etc/systemd/system/multi-user.target.wants/guix-daemon.service to
/root/.guix-profile/lib/systemd/system/guix-daemon.service.
root@sharknado9000:~# systemctl status guix-daemon
● guix-daemon.service - Build daemon for GNU Guix
   Loaded: loaded
(/root/.guix-profile/lib/systemd/system/guix-daemon.service; enabled)
   Active: active (running) since Di 2017-03-28 09:56:52 UTC; 24min ago
 Main PID: 5355 (guix-daemon)
   CGroup: /system.slice/guix-daemon.service
           └─5355
/var/guix/profiles/per-user/root/guix-profile/bin/guix-daemon
--build-users-group=guixbuild

Mär 28 09:56:52 sharknado9000 systemd[1]: Starting Build daemon for GNU
Guix...
Mär 28 09:56:52 sharknado9000 systemd[1]: Started Build daemon for GNU
Guix.
Mär 28 09:56:55 sharknado9000 guix-daemon[5355]: accepted connection
from pid 5356, user root (trusted)
Mär 28 10:06:23 sharknado9000 guix-daemon[5355]: accepted connection
from pid 5378, user root (trusted)
Mär 28 10:15:19 sharknado9000 systemd[1]:
[/root/.guix-profile/lib/systemd/system/guix-daemon.service:16] Unknown
lvalue 'TasksMax' in section 'Service'
Mär 28 10:20:50 sharknado9000 systemd[1]:
[/root/.guix-profile/lib/systemd/system/guix-daemon.service:16] Unknown
lvalue 'TasksMax' in section 'Service'

After reboot the service was still there.
As the files in ~root/guix-profile/ are symlinks, I expect that this is
permanent and will still work when the systemd file changes.