On Sat, Nov 06, 2021 at 04:34:02PM +0000, lik...@gmx.de wrote: > On 11/6/21 16:23, badgateway wrote: > > Is it an option to clone your current template and disable the services > > permanently in your new template? > > > > It is an option. But in this case I'd prefer the way using > /rw/config/rc.local not to maintain another template. > > I've learned there must be 3 alternatives, otherwise you've not done enough > research. Maybe there's a 3rd way? >
There is indeed a third way, which fits nicely in to the Qubes framework, and is used by qvm-service. Instead of disabling the service, control it. If your service is foo.service: Create a folder foo.service.d, and create a file 10_qubes.conf with something like ``` [Unit] ConditionPathExists=/var/run/qubes/service/foo After=qubes.sysinit.service ``` Now you can control with `qvm-service --enable <qube> foo` in qubes where you want the service to run. You could invert the sense of control by using ConditionPathExists=!<some parameter> but this may lead to confusion. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/YYbELu4D%2Bcs250a9%40thirdeyesecurity.org.
