From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Configuring a service but not starting it on boot Date: Wed, 28 Nov 2018 18:20:38 +0100 Message-ID: <87ftvl15ll.fsf@gnu.org> References: <87y39dy28x.fsf@lassieur.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]:59793) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gS3Vy-0000Fp-Ic for help-guix@gnu.org; Wed, 28 Nov 2018 12:20:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gS3Vw-0000CU-Ka for help-guix@gnu.org; Wed, 28 Nov 2018 12:20:42 -0500 In-Reply-To: (Arun Isaac's message of "Wed, 28 Nov 2018 21:41:13 +0530") 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: Arun Isaac Cc: help-guix@gnu.org, =?utf-8?Q?Cl=C3=A9ment?= Lassieur Hello Arun, Arun Isaac skribis: >> Attached is a hack I did a while ago. > > Hacks like the one you showed could work, but it would be nice to have a > general purpose #:auto-start? property common to all services. Is there > such a feature? If not, could we implement such a feature? The openssh service has such an option, but currently, it=E2=80=99s really per-service, which isn=E2=80=99t great. It would be best if we had a gener= ic way to say which Shepherd services should be started automatically and which shouldn=E2=80=99t. Ludo=E2=80=99.