[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Shepherd and the --silent option
From: |
Dariqq |
Subject: |
Re: Shepherd and the --silent option |
Date: |
Mon, 9 Sep 2024 08:26:18 +0000 |
On 08.09.24 23:55, Ludovic Courtès wrote:
Oh, not sure what the deal was with that 2013 commit. :-)
Anyway your patch looks great to me; finally pushed as
6ffe404ffe794b06fddd304a963a47b62444edfa in ‘devel’.
Awesome, thanks :).
Would it be possible to also expose --silent as an option for the
home-shepherd auto-start script once it does something in a stable version?
Slightly related I noticed an issue with the devel shepherd invoked
via guix home not daemonizing blocking my login manager.
Weird; I haven’t tried this yet, I’ll give it a try.
I think the issue is that the shepherd config generated by guix-home uses
(action 'root 'daemonize)
which is deprecated in 0.10 and on the devel branch seems to create a
new action rather than invoking it. (So no error too).
When I change to the new way
(perform-service-action root-service 'daemonize)
daemonizing works.
Should guix-home be backwards compatible with older shepherds given that
shepherd-0.8 and shepherd-0.9 are still packaged?
Thanks,
Ludo’.