GNU bug report logs - #46712
Removed service extensions are not unloaded from Shepherd upon reconfiguring

Previous Next

Package: guix;

Reported by: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Date: Mon, 22 Feb 2021 20:38:01 UTC

Severity: normal

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #8 received at 46712 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 46712 <at> debbugs.gnu.org
Subject: Re: bug#46712: Removed service extensions are not unloaded from
 Shepherd upon reconfiguring
Date: Tue, 23 Feb 2021 16:34:13 +0100
Hi!

At the Shepherd level, there’s no notion of service extension.
Normally, after reconfiguring, “herd restart guix-daemon” (really
“restart”, not “stop” + “start”) should start the new service, which
doesn’t have all these ‘--chroot-directory’ options.

Note that the guix-daemon process you should seems to be a child process
(presumably because there was still a client running when you restarted
the service), not the main guix-daemon process.

You should check the command line of the main process, the one returned
by “herd status guix-daemon”.

HTH!

Ludo’.




This bug report was last modified 4 years and 144 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.