GNU bug report logs - #36517
'guix deploy' does not restart services

Previous Next

Full log

View this message in rfc822 format

From: zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 36517 <at> debbugs.gnu.org
Subject: bug#36517: 'guix deploy' does not restart services
Date: Thu, 11 Jul 2019 13:05:00 -0400

[Message part 1 (text/plain, inline)]

Hi, Ludovic!

Ludovic Courtès <ludo <at> gnu.org> writes:

> Hi,
>
> zerodaysfordays <at> sdf.lonestar.org (Jakob L. Kreuze) skribis:
>
>> This issue is described in more detail at [1]. Essentially, 'guix
>> deploy' is will happily load and start new services, as well as unload
>> obsolete services, but does nothing to restart valid services that are
>> already running.
>
> That’s not a bug: ‘guix system reconfigure’ does not restart already
> running services, simply because it cannot tell whether now is a good
> time to restart them.  It’s a decision that’s left to the system
> administrator.
>
> However, note that ‘guix system reconfigure’ loads “replacements” for
> each Shepherd service, such that next time you run ‘herd restart FOO’,
> you spawn that new version of FOO.
>
> Does that make sense?

Yes, that does make sense. I suppose the way I worded the initial report
wasn't great; I opened this to track support for 'restart-strategy' as
described in #33508 in 'guix deploy'. This takes care of the question of
when a good time to restart the service would be.

Regards,
Jakob

[signature.asc (application/pgp-signature, inline)]

Previous Next

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