On Sun, 15 May 2022 at 15:20, Ludovic Courtès wrote:
>
> The extra ‘setsid’ call LGTM, but why add an extra ‘primitive-fork’
> call?
Sorry, but don't use this patch.
The setsid call makes things slightly better but if Shepherd prints
anything (for example, a service's status update), it will cras
Hi,
Kevin Boulain skribis:
> First, Guix Home correctly tells the user Shepherd to daemonize itself
> via an 'action'
> (https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/home/services/shepherd.scm#n64)
> but, from my understanding, the daemonization process is missing at
> least a setsid call
On 2022-03-12 18:49, Kevin Boulain wrote:
> So, I've done some digging and I'm coming back with two findings :)
>
> First, Guix Home correctly tells the user Shepherd to daemonize itself
> via an 'action'
> (https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/home/services/shepherd.scm#n64)
> but,
So, I've done some digging and I'm coming back with two findings :)
First, Guix Home correctly tells the user Shepherd to daemonize itself
via an 'action'
(https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/home/services/shepherd.scm#n64)
but, from my understanding, the daemonization process is m
Hello,
I did a quick search in the tracker and the mailing list archives but
couldn't find a similar topic, apologies if this was already
discussed.
I was playing with Guix Home and I'm a bit surprised by how user
services are managed, especially the Shepherd itself.
Let's say I start from a cle
