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@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
LimitNOFILE=1024:524288
[Install]
+WantedBy=multi-user.target
Also=virtlockd.socket
Also=virtlockd-admin.socket
LimitNOFILE=1024:524288
[Install]
+WantedBy=multi-user.target
Also=virtlogd.socket
Also=virtlogd-admin.socket