From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Isaac Subject: Re: Configuring a service but not starting it on boot Date: Wed, 28 Nov 2018 23:22:03 +0530 Message-ID: References: <87y39dy28x.fsf@lassieur.org> <87ftvl15ll.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 ([2001:4830:134:3::10]:46074) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gS40Z-0005OF-Ry for help-guix@gnu.org; Wed, 28 Nov 2018 12:52:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gS40W-0006cW-La for help-guix@gnu.org; Wed, 28 Nov 2018 12:52:19 -0500 In-Reply-To: <87ftvl15ll.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: help-guix@gnu.org > It would be best if we had a generic way to say which Shepherd > services should be started automatically and which shouldn=E2=80=99t. Could you describe some way to achieve this? If it's simple enough, I can implement it and contribute a patch.