From 2d158b8ab2ffce28bf42f6219eaa1111b60bb929 Mon Sep 17 00:00:00 2001 From: marmarta Date: Sat, 1 Jul 2017 21:14:45 +0200 Subject: [PATCH] clearer explanation of qubes-service It's wasn't perfectly clear that the 30_qubes.conf file should be created in the targeted VM, not in dom0 --- reference/qubes-service.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/reference/qubes-service.md b/reference/qubes-service.md index 6ef67841..568ebc99 100644 --- a/reference/qubes-service.md +++ b/reference/qubes-service.md @@ -12,7 +12,7 @@ Usage documentation is on [qvm-service manual page](/doc/dom0-tools/qvm-service/ Under the hood enabled service in VM is signaled by file in /var/run/qubes-service. This can be used to implement almost enable/disable **per-VM** switch controlled by dom0. Adding support for systemd services is pretty simple: -Create `/etc/systemd/system/.service.d/30_qubes.conf` file +In the VM, create `/etc/systemd/system/.service.d/30_qubes.conf` file containing (you may need to create a directory for this file first): ~~~ @@ -20,4 +20,4 @@ containing (you may need to create a directory for this file first): ConditionPathExists=/var/run/qubes-service/ ~~~ -This will cause service to be started only when you enable it with qvm-service for given VM. +This will cause service to be started only when you enable it with qvm-service for this VM.