|
From: | Ludovic Courtès |
Subject: | Re: Configuring a service but not starting it on boot |
Date: | Thu, 29 Nov 2018 11:49:49 +0100 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Arun Isaac <address@hidden> 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 how to do it. One thing I proposed long ago is this: <https://issues.guix.info/issue/27155>. 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. Needs more thought… Ludo’.
[Prev in Thread] | Current Thread | [Next in Thread] |