From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carlo Zancanaro Subject: Re: Don't auto-start a service in Shepherd Date: Sun, 25 Feb 2018 09:27:49 +1100 Message-ID: <87fu5qyqe2.fsf@zancanaro.id.au> References: <20180223102236.0aef2eac@mykolab.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55525) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1epiIU-0007b3-N7 for help-guix@gnu.org; Sat, 24 Feb 2018 17:28:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1epiIR-0004nR-GU for help-guix@gnu.org; Sat, 24 Feb 2018 17:28:02 -0500 Received: from mail-wm0-x235.google.com ([2a00:1450:400c:c09::235]:38470) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1epiIR-0004lO-9a for help-guix@gnu.org; Sat, 24 Feb 2018 17:27:59 -0500 Received: by mail-wm0-x235.google.com with SMTP id z9so10712723wmb.3 for ; Sat, 24 Feb 2018 14:27:59 -0800 (PST) In-reply-to: <20180223102236.0aef2eac@mykolab.com> 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: Rutger Helling Cc: help-guix@gnu.org --=-=-= Content-Type: text/plain; format=flowed On Fri, Feb 23 2018, Rutger Helling wrote: > Is there a way to prevent auto-starting a service in Shepherd? I > find that if I use "herd disable service" it still automatically > starts the service on a reboot/reconfigure. I've just had a look at gnu/services/shepherd.scm, and it looks like system services can set `auto-start?` to #f when creating their shepherd-service, but not many expose this. I think openssh is the only service to expose it to the system configuration. You could try patching the service you want to use to expose the option to not automatically start it. Which service are you trying to disable? There's a discussion to be had about whether shepherd should remember disabled services across a reboot/reconfigure. I don't think it should, because the running services should be considered a part of the system specification. Carlo --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE1lpncq7JnOkt+LaeqdyPv9awIbwFAlqR5uUACgkQqdyPv9aw Ibxknw/9Fcu4aw0vMPXSBczeEqiDCxcmQC5NCn1QyxtqqU79AqsQAQ8ZrWui3m3s ysLo8EXz6zV4bzykcN4EhK5WaTM9UtmPnd6Yjo7HnRAYHZhhhgcbY6GhrInXN6Ko usqwyZjxzFUYrQ5JQZzk1vAJ9uN64X4srzGMFfbyOwACpfvKRicfMbQPbKq+20d7 1nbZtNQ+5JIC0StZFVr8H7cgb+wT83Jf9jbSSh0QP40Tt8xwuTaR/uiMQd/h6tZ9 1MJ+DlVAECG4F09Lms5bXSUV+MC0JeqjNExKYfxxS+jKCeMQcoNsa0Cu+GKy8YHi +zU0MWoSHKK7a3J4NyChqDyjoAwPzvOJOccgx0I/SkzRFOxTvRegL+L/62B+SYaF NxiCqRgjQqhcJzpq2rbZdNxFdJekhmtXS7LbTbrrjr8jYnDpHEpBeqOq0jZUF10q iXylnyT033voVpPbyfdv1RxpsKuqSWs2+EQabVAGGE8UqMtiLcamJ8Nsv0srsmsN 2QvARndIpcKBxxFOBZ00aoWOvkiz1fFNiB0/fCjsPxtxIcZ/vNBqvRMVSX9/t7sS 0RJSCHw+7yDKdPwggHstv05IQjhTxoxSwf4Y8k3u7s7cfurmjzzW60/p09oibQ4j f8eo0CHaCCHbhg0dqdhQs+ThyhuBEkeo7OWLPf7bsXHjx4SyJzM= =k3El -----END PGP SIGNATURE----- --=-=-=--