This annotation being missing resulted in virtlogd and virtlockd
being marked as "indirect" services, i.e. services that cannot
be started directly but have to be socket activated instead.
While this is our preferred configuration, we shouldn't prevent
the admin to start them at boot if they want to.
Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
---
src/locking/virtlockd.service.in | 1 +
src/logging/virtlogd.service.in | 1 +
2 files changed, 2 insertions(+)
diff --git a/src/locking/virtlockd.service.in b/src/locking/virtlockd.service.in
index 18873f86a6..f12c3040e9 100644
--- a/src/locking/virtlockd.service.in
+++ b/src/locking/virtlockd.service.in
@@ -21,5 +21,6 @@ OOMScoreAdjust=-900
LimitNOFILE=1024:524288
[Install]
+WantedBy=multi-user.target
Also=virtlockd.socket
Also=virtlockd-admin.socket
diff --git a/src/logging/virtlogd.service.in b/src/logging/virtlogd.service.in
index 14a991f348..e665e8a02e 100644
--- a/src/logging/virtlogd.service.in
+++ b/src/logging/virtlogd.service.in
@@ -21,5 +21,6 @@ OOMScoreAdjust=-900
LimitNOFILE=1024:524288
[Install]
+WantedBy=multi-user.target
Also=virtlogd.socket
Also=virtlogd-admin.socket
--
2.41.0