unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
* Knowing which services to restart
@ 2020-07-08  4:56 Matthew Kraai
  2020-07-08  8:53 ` Pierre Neidhardt
  2020-09-25 13:12 ` Joshua Branson
  0 siblings, 2 replies; 5+ messages in thread
From: Matthew Kraai @ 2020-07-08  4:56 UTC (permalink / raw)
  To: help-guix

Hi,

When I ran `sudo guix system reconfigure /etc/config.scm`, it printed

> To complete the upgrade, run 'herd restart SERVICE' to stop,
> upgrade, and restart each service that was not automatically restarted.

How do I know which services need to be restarted?

-- 
Matthew Kraai


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Knowing which services to restart
  2020-07-08  4:56 Knowing which services to restart Matthew Kraai
@ 2020-07-08  8:53 ` Pierre Neidhardt
  2020-07-08 11:08   ` Carlo Zancanaro
  2020-09-25 13:12 ` Joshua Branson
  1 sibling, 1 reply; 5+ messages in thread
From: Pierre Neidhardt @ 2020-07-08  8:53 UTC (permalink / raw)
  To: Matthew Kraai, help-guix

[-- Attachment #1: Type: text/plain, Size: 187 bytes --]

I too have been wondering about this since ever :)

Couldn't Guix be smarter about this?  Or at least provide a less
puzzling message.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Knowing which services to restart
  2020-07-08  8:53 ` Pierre Neidhardt
@ 2020-07-08 11:08   ` Carlo Zancanaro
  2020-07-24 15:28     ` Ludovic Courtès
  0 siblings, 1 reply; 5+ messages in thread
From: Carlo Zancanaro @ 2020-07-08 11:08 UTC (permalink / raw)
  To: Pierre Neidhardt; +Cc: help-guix

On Wed, Jul 08 2020, Pierre Neidhardt wrote:
> Couldn't Guix be smarter about this?  Or at least provide a less puzzling message.

This was brought up when we originally implemented upgrading of services on a live system. The discussion about this starts in an email from Ludovic[1], and proceeds from there (although you'll have to skip over some other unrelated conversations).

There are definitely ways that things can be improved. I made an attempt at doing this at the end of 2018[2], but that didn't result in anything being merged into Guix. I don't think we've yet settled on an approach for how to resolve this (and the related issue of automatically upgrading services).

Carlo

[1]: https://issues.guix.info/22039#11
[2]: https://issues.guix.info/33508


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Knowing which services to restart
  2020-07-08 11:08   ` Carlo Zancanaro
@ 2020-07-24 15:28     ` Ludovic Courtès
  0 siblings, 0 replies; 5+ messages in thread
From: Ludovic Courtès @ 2020-07-24 15:28 UTC (permalink / raw)
  To: Carlo Zancanaro; +Cc: help-guix

Hi,

Carlo Zancanaro <carlo@zancanaro.id.au> skribis:

> On Wed, Jul 08 2020, Pierre Neidhardt wrote:
>> Couldn't Guix be smarter about this?  Or at least provide a less puzzling message.
>
> This was brought up when we originally implemented upgrading of services on a live system. The discussion about this starts in an email from Ludovic[1], and proceeds from there (although you'll have to skip over some other unrelated conversations).
>
> There are definitely ways that things can be improved. I made an attempt at doing this at the end of 2018[2], but that didn't result in anything being merged into Guix. I don't think we've yet settled on an approach for how to resolve this (and the related issue of automatically upgrading services).
>
> Carlo
>
> [1]: https://issues.guix.info/22039#11
> [2]: https://issues.guix.info/33508

The general issue here is that we cannot safely stop+start a service
without notice, unless the user explicitly said this is OK.
Consequently, in practice, only services that the user explicitly ‘herd
restart’s are up-to-date.  It’s OK when you know you what service you
want to update here and now, but it’s suboptimal otherwise.

I figured there’s one way to mostly sidestep the issue: when we have
“socket activation” in the Shepherd, then unused services will be
“stopped” at reconfigure time and thus safe to upgrade.  Thus, in
practice, more services will be upgraded by default.

It’d still be up to the user to restart currently running services when
they deem appropriate.

Thanks,
Ludo’.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Knowing which services to restart
  2020-07-08  4:56 Knowing which services to restart Matthew Kraai
  2020-07-08  8:53 ` Pierre Neidhardt
@ 2020-09-25 13:12 ` Joshua Branson
  1 sibling, 0 replies; 5+ messages in thread
From: Joshua Branson @ 2020-09-25 13:12 UTC (permalink / raw)
  To: Matthew Kraai; +Cc: help-guix


The real simple answer is to reboot your computer.  :)

But for the most part, it'll restart the necessary services.  Most
things that are essential won't get restarted.  For instance your X
server or your gnome session.  Because if it tried to restart those,
then you'd have to log in again.  :)

--
Joshua Branson
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
"You can have whatever you want, as long as you help enough other people
get what they want." - Zig Ziglar


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2020-09-25 13:17 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-08  4:56 Knowing which services to restart Matthew Kraai
2020-07-08  8:53 ` Pierre Neidhardt
2020-07-08 11:08   ` Carlo Zancanaro
2020-07-24 15:28     ` Ludovic Courtès
2020-09-25 13:12 ` Joshua Branson

unofficial mirror of help-guix@gnu.org 

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://yhetil.org/guix-user/0 guix-user/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-user guix-user/ https://yhetil.org/guix-user \
		help-guix@gnu.org
	public-inbox-index guix-user

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.gnu.guix.user
	nntp://news.gmane.io/gmane.comp.gnu.guix.user


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git