Hi Ludo,
Le mardi 09 juin 2026 à 15:52 +0200, Ludovic Courtès a écrit :
> Could you also show /etc/systemd/system/guix-daemon.service?
# This is a "service unit file" for the systemd init system to launch
# 'guix-daemon'. Drop it in /etc/systemd/system or similar to have
# 'guix-daemon' automatically started.
[Unit]
Description=Build daemon for GNU Guix
[Service]
ExecStart=/var/guix/profiles/per-user/root/current-guix/bin/guix-daemon \
--build-users-group=_guixbuild --discover=no
Environment=LC_ALL=C.UTF-8
StandardOutput=journal
StandardError=journal
# Work around a nasty systemd ‘feature’ that kills the entire process tree
# (including the daemon!) if any child, such as cc1plus, runs out of memory.
OOMPolicy=continue
# Despite the name, this is rate-limited: a broken daemon will eventually
fail.
Restart=always
# See <https://lists.gnu.org/archive/html/guix-devel/2016-04/msg00608.html>.
# Some package builds (for example, [email protected]) may require even more than
# 1024 tasks.
TasksMax=8192
[Install]
WantedBy=multi-user.target
> It would seem that the daemon was installed with Trisquel, not with
Guix, right?
This is correct, but I modified this file according to the instructions in
the Guix manual section 2.5. Looking at this again, I notice that in my file
there is the "--discover=no" that is not mentioned in the manual, I don't
know whether that could be a problem or not.
Thanks,
David.
