From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 46712-done@debbugs.gnu.org
Subject: bug#46712: Removed service extensions are not unloaded from Shepherd upon reconfiguring
Date: Thu, 25 Feb 2021 08:35:46 -0500 [thread overview]
Message-ID: <87tuq08e31.fsf@gmail.com> (raw)
In-Reply-To: <87a6ru4x3e.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 23 Feb 2021 16:34:13 +0100")
Hello!
Ludovic Courtès <ludo@gnu.org> writes:
> 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.
FTR, I had used 'guix deploy' and issued 'sudo herd restart guix-daemon'
on the remote after it completed successfully. Why should stop + start
be different than restart though? That seems counter-intuitive.
> 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”.
You are right that this process has the correct arguments:
$ sudo herd status guix-daemon
Status of guix-daemon:
It is started.
Running value is 25628.
It is enabled.
Provides (guix-daemon).
Requires (user-processes).
Conflicts with ().
Will be respawned.
$ cat /proc/25628/cmdline
/gnu/store/rqif4yxa6ny4nxrdq6whnva2r089jm0c-guix-1.2.0-13.a53f711/bin/guix-daemon--build-users-groupguixbuild--max-silent-time0--timeout0--log-compressionnone--discover=no--substitute-urlshttps://ci.guix.gnu.org--max-jobs=20
Some of the other process were apparently caused by 'guix
environment' shells still running in screen; I've terminated them all
now and ran 'sudo herd stop guix-daemon'; surprisingly I still had two
remaining guix-daemon processes that were launched manually for testing
purposes. That's on a Guix system with an uptime of 174 days and
counting :-).
Thank you for the answer and sorry for the noise! It works as designed.
Closing.
Maxim
prev parent reply other threads:[~2021-02-25 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 20:37 bug#46712: Removed service extensions are not unloaded from Shepherd upon reconfiguring Maxim Cournoyer
2021-02-23 15:34 ` Ludovic Courtès
2021-02-25 13:35 ` Maxim Cournoyer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tuq08e31.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=46712-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.