[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guix shepherd user services
From: |
Tanguy Le Carrour |
Subject: |
Re: Guix shepherd user services |
Date: |
Wed, 8 May 2019 09:30:10 +0200 |
User-agent: |
NeoMutt/20180716 |
Hi Tobias, hi Guix!
Le 05/04, Tobias Geerinckx-Rice a écrit :
> My apologies for not replying sooner. I fail at managing the scarce free
> time I have these days.
I'm not much better, so no need to apologise! ;-)
> Tanguy Le Carrour wrote:
> No, you're right, I'd simply never checked this before. Stopping emacs
> gives me… Zombie emacs. And mu.
Just to make sure, I tried and checked with the "system wide" shepherd.
Everything seem to be OK, no Zombies lurking in the corner. But… I
noticed that `wpa-supplicant` was running and, as I don't need it on my
desktop, I stopped it:
~# herd stop wpa-supplicant
Service ntpd has been stopped.
Service avahi-daemon has been stopped.
Service networking has been stopped.
Service wpa-supplicant has been stopped.
?! I was not expecting `networking` to stop too.
~# herd status
…
Stopped:
- avahi-daemon
- networking
- ntpd
- term-auto
- user-homes
- wpa-supplicant
And event if `network` is listed as "stopped", I still have access
to the network!? This is not clear to me!? Does `networking` mean
something different?!
And if I start `network` again, `wpa-supplicant` comes up with it, but
not `avahi-daemon` and `ntpd`.
# herd start networking
Service wpa-supplicant has been started.
Service networking has been started.
Not quite the behaviour I was expecting! But maybe I didn't understand
correctly how things were supposed to work! :-(
I'll dig a bit in the doc, but any input is welcomed!
--
Tanguy