[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Upgrading Shepherd services
From: |
Attila Lendvai |
Subject: |
Re: Upgrading Shepherd services |
Date: |
Thu, 23 May 2024 19:25:55 +0000 |
hi Felix,
> Here is a small one for not booting, although the service activation
> during 'guix deploy' succeeds.
>
> Please try the Guix timer below with the Shepherd development branch.
> My equipment does not boot when the apparently erroneous (actions ...)
> field in the shepherd-service record is present.
i cannot reproduce this.
maybe it fails for you due to some missing modules that are available in my
test env?
this below is with my shepherd branch, but later i double checked with vanilla
'devel', and it works the same.
# herd trigger garbage-collector
Triggering timer.
#
herd[210]: [debug] Got a reply, processing it
shepherd[1]: [debug] fork+exec-command for (guix gc --free-space=1G), user #f,
group #f, supplementary-groups (), log-file #f
shepherd[1]: [debug] exec-command for (guix gc --free-space=1G), user #f, group
#f, supplementary-groups (), log-file #f, log-port #
shepherd[1]: Timer 'garbage-collector' spawned process 212.
shepherd[1]: [debug] query-service-controller; message status, service
#<<service> provision: (garbage-collector) requirement: (guix
shepherd[1]: [debug] query-service-controller; message running, service
#<<service> provision: (garbage-collector) requirement: (gui
shepherd[1]: [guix] guix gc: already 30082.59 MiBs available on /gnu/store,
nothing to do
shepherd[1]: Process 212 of timer 'garbage-collector' terminated with status 0
after 1 seconds.
HTH,
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“There are two ways to be fooled. One is to believe what isn't true; the other
is to refuse to believe what is true.”
— Søren Kierkegaard (1813–1855)
Re: Upgrading Shepherd services, Ludovic Courtès, 2024/05/17