From bd4298d104ea8483f990c27e3cbfeec140102d79 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marek=20Marczykowski-G=C3=B3recki?=
 <marmarek@invisiblethingslab.com>
Date: Fri, 3 Feb 2017 04:04:23 +0100
Subject: [PATCH] Update qubes-service page to use drop-ins instead of full
 service override

---
 reference/qubes-service.md | 15 ++++++---------
 1 file changed, 6 insertions(+), 9 deletions(-)

diff --git a/reference/qubes-service.md b/reference/qubes-service.md
index b863d1cc..6ef67841 100644
--- a/reference/qubes-service.md
+++ b/reference/qubes-service.md
@@ -12,15 +12,12 @@ 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:
 
-1.  Disable old service: `systemctl disable <service name>`
-2.  Create `/etc/systemd/system/<service name>.service` file containing:
+Create `/etc/systemd/system/<service name>.service.d/30_qubes.conf` file
+containing (you may need to create a directory for this file first):
 
-    ~~~
-    .include /lib/systemd/system/<service name>.service
-    [Unit]
-    ConditionPathExists=/var/run/qubes-service/<service name>
-    ~~~
-
-3.  Enable new service: `systemctl enable <service name>`.
+~~~
+[Unit]
+ConditionPathExists=/var/run/qubes-service/<service name>
+~~~
 
 This will cause service to be started only when you enable it with qvm-service for given VM.