Re: Configuring a service but not starting it on boot

> One thing I proposed long ago is this: > . It would allow us to address > this kind of issue but it has the drawback that it makes it harder to > reason about the relationships among services: anything can happen. I can see how the proposed finalization s

Re: Configuring a service but not starting it on boot

Arun Isaac skribis: >> It would be best if we had a generic way to say which Shepherd >> services should be started automatically and which shouldn’t. > > Could you describe some way to achieve this? If it's simple enough, I > can implement it and contribute a patch. I don’t have a good idea on

Re: Configuring a service but not starting it on boot

> It would be best if we had a generic way to say which Shepherd > services should be started automatically and which shouldn’t. Could you describe some way to achieve this? If it's simple enough, I can implement it and contribute a patch.

Re: Configuring a service but not starting it on boot

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 openss

Re: Configuring a service but not starting it on boot

Your words are awesome! We need this option! Nov 28, 2018, 7:11 PM by arunis...@systemreboot.net: >> 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 >

Re: Configuring a service but not starting it on boot

> 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?

Re: Configuring a service but not starting it on boot

Hi Arun, Arun Isaac writes: > I would like to have the a service (specifically the tor service) listed > in my config.scm and configured using `guix system reconfigure > config.scm'. But, I do not want the service to start up at boot time. I > want to start/stop it using `herd' later as and when

Configuring a service but not starting it on boot

I would like to have the a service (specifically the tor service) listed in my config.scm and configured using `guix system reconfigure config.scm'. But, I do not want the service to start up at boot time. I want to start/stop it using `herd' later as and when I require it. How do I achieve this?