From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tanguy Le Carrour Subject: Re: Guix shepherd user services Date: Wed, 8 May 2019 09:30:10 +0200 Message-ID: <20190508073010.gxhetsxdbc5n25df@melmoth> References: <20190429195749.t2kksa5lujoafnlf@melmoth> <87sgu0mv2b.fsf@nckx> <20190501090058.q34wlnxhbn6k3hwg@melmoth> <20190504070718.xdt6i5475xydvh7i@melmoth> <87d0kysat8.fsf@nckx> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:51999) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hOH1s-0005az-Mx for guix-devel@gnu.org; Wed, 08 May 2019 03:30:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hOH1r-0006nM-S5 for guix-devel@gnu.org; Wed, 08 May 2019 03:30:16 -0400 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:58947) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hOH1r-0006me-LZ for guix-devel@gnu.org; Wed, 08 May 2019 03:30:15 -0400 Content-Disposition: inline In-Reply-To: <87d0kysat8.fsf@nckx> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Tobias Geerinckx-Rice Cc: guix-devel@gnu.org 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