While systemd will automatically match foo.socket with foo.service based on their names, it's nicer to connect the two explicitly.
This is what we do for all services, with virtlogd and virtlockd being the only exceptions. Signed-off-by: Andrea Bolognani <abolo...@redhat.com> --- src/locking/virtlockd.socket.in | 1 + src/logging/virtlogd.socket.in | 1 + 2 files changed, 2 insertions(+) diff --git a/src/locking/virtlockd.socket.in b/src/locking/virtlockd.socket.in index 52014f45ec..4ce75391ae 100644 --- a/src/locking/virtlockd.socket.in +++ b/src/locking/virtlockd.socket.in @@ -4,6 +4,7 @@ Before=libvirtd.service [Socket] ListenStream=@runstatedir@/libvirt/virtlockd-sock +Service=virtlockd.service SocketMode=0600 [Install] diff --git a/src/logging/virtlogd.socket.in b/src/logging/virtlogd.socket.in index 9749a33197..ff3e66e09b 100644 --- a/src/logging/virtlogd.socket.in +++ b/src/logging/virtlogd.socket.in @@ -4,6 +4,7 @@ Before=libvirtd.service [Socket] ListenStream=@runstatedir@/libvirt/virtlogd-sock +Service=virtlogd.service SocketMode=0600 [Install] -- 2.41.0
