On 26 December 2016 at 19:48, Leo Famulari <[email protected]> wrote: > On Mon, Dec 26, 2016 at 03:14:42PM -0800, Hilco Wijbenga wrote: >> Specifically, "systemctl enable guix-daemon" fails with "Failed to >> execute operation: Too many levels of symbolic links" (see [1]). Is >> there a workaround for this? I suppose I could simply copy >> guix-daemon.service into /etc/systemd/system instead of linking to it >> but I'm not sure how many other things will fail because of this >> symlink limitation. > > I recommend copying the service file as you suggested. It's exactly what > I do on Debian, both before systemd 231 and after, and it works fine for > me.
Okay, thanks. Why also for systemd >=231? > If the ExecStart value contains a path to '/gnu/store/...', you should > replace that path with > '/var/guix/profiles/per-user/root/guix-profile/bin/guix-daemon'. > > Using the absolute path to /gnu/store only works properly if the service > file is a symlink to root's profile, in which case the executable path > would get updated as root updates their packages. My suggested > replacement will have the same effect. > > If you do that, make sure to recreate the rest of the ExecStart value > after the path to the guix-daemon. Mmm, okay, I'll keep that in mind. > PS What OS are you using? I'm wondering if it's too early to rely on > systemd 231 being widely deployed. This was the latest OpenSUSE (LEAP 42.2) that I'm thinking of using at work. At home I use Gentoo but without systemd so I should not have any issues there. > PPS It's "Guix", without all capital letters :) Huh, yes, I don't know why I made it all caps. :-) And systemd doesn't have any caps either. What is this world coming too! ;-)
