From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: One-shot Shepherd services Date: Fri, 03 May 2019 15:53:38 +0200 Message-ID: <87pnozbq59.fsf@gnu.org> References: <87ftqfngda.fsf@gnu.org> <87h8agyxoq.fsf@gmail.com> <878svrlggj.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:38514) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMYdA-00049J-Na for guix-devel@gnu.org; Fri, 03 May 2019 09:53:41 -0400 In-Reply-To: (=?utf-8?Q?=22G=C3=A1bor?= Boskovits"'s message of "Tue, 30 Apr 2019 19:24:23 +0200") 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: =?utf-8?Q?G=C3=A1bor?= Boskovits Cc: Guix-devel Hi G=C3=A1bor, G=C3=A1bor Boskovits skribis: > Ludovic Court=C3=A8s ezt =C3=ADrta (id=C5=91pont: 2019. = =C3=A1pr. 30., K, 16:24): > >> Chris Marusich skribis: >> >> > At first I was a little confused about why we would ever want to use a >> > one-shot shepherd service instead of an activation snippet, but after >> > reviewing the account-shepherd-service, I think I understand. It seems >> > that we make it a one-shot shepherd service instead of an activation >> > snippet so that we can take advantage of shepherd's service dependency >> > management. In the case of account-shepherd-service, it looks like we >> > made it a shepherd service to ensure that it would run after >> > 'file-systems' is up. This makes sense, since it could be a little >> > awkward to try to ensure proper execution order by extending the >> > activation service, and even if we did that, it would duplicate the >> > dependency management logic that shepherd gives us already. >> >> Yes, that=E2=80=99s exactly the reason. >> >> > This raises the question, if we are willing to convert some more activati= on > snippets to one-shot services. Are there any candidates for that? Good question, maybe things like ssh-keygen. Or maybe we could turn all the service activation snippets into one-shot services that the service depends on. However, since the Shepherd 0.6.0 UI doesn=E2=80=99t allow users to disting= uish between one-shot and normal services, it=E2=80=99s probably a good idea to = not do this yet. Otherwise =E2=80=9Cherd status=E2=80=9D would list loads of s= topped services, which could be confusing. I think we should first adjust the Shepherd UI. Ludo=E2=80=99.