From: ng0 <ng0@libertad.pw>
To: Hilco Wijbenga <hilco.wijbenga@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: SystemD & Symbolic Links
Date: Tue, 27 Dec 2016 10:02:11 +0000 [thread overview]
Message-ID: <87ful97krg.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CAE1pOi2HfE+AMYYr3eTtgrHdBA13capxejBfC66ttn_ou=A+pA@mail.gmail.com>
Hilco Wijbenga <hilco.wijbenga@gmail.com> writes:
> On 26 December 2016 at 19:48, Leo Famulari <leo@famulari.name> 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.
There exists a package (and service) for Gentoo in the
youbroketheinternet-overlay, but I no longer maintain
it. Improvements welcome, especially for the service which can
slow down shutdown / reboot to 30 minutes and more.
I no longer use Gentoo, but contributions are easy and
welcome. Maybe we can get the openrc one day generic enough to
include it in Guix.
I no longer use Gentoo so I can't test.
The way most people who use Gentoo here seem to have done it is
using not the package. At least one person in IRC uses Guix on
Gentoo (ZombieChicken ?).
>
>> 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! ;-)
>
>
--
♥Ⓐ ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org
next prev parent reply other threads:[~2016-12-27 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 23:14 SystemD & Symbolic Links Hilco Wijbenga
2016-12-27 3:48 ` Leo Famulari
2016-12-27 4:40 ` Hilco Wijbenga
2016-12-27 10:02 ` ng0 [this message]
2016-12-27 22:18 ` Leo Famulari
2016-12-28 20:46 ` Joshua Branson
2016-12-30 20:41 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ful97krg.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=ng0@libertad.pw \
--cc=help-guix@gnu.org \
--cc=hilco.wijbenga@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).