Hi, app-emulation/libvirt-4.9.0 init script refers /var/run: /etc/init.d/libvirtd:pidfile="/var/run/libvirtd.pid"
/etc/init.d/libvirtd:pidfile="/var/run/libvirtd.pid" /etc/init.d/virtlockd:pidfile="/var/run/virtlockd.pid" /etc/init.d/virtlogd:pidfile="/var/run/virtlogd.pid" /etc/libvirt/libvirtd.conf:#unix_sock_dir = "/var/run/libvirt"
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=441d105c0035db3b557d03c66a24db90851af424 commit 441d105c0035db3b557d03c66a24db90851af424 Author: Matthias Maier <tamiko@gentoo.org> AuthorDate: 2019-05-19 22:14:34 +0000 Commit: Matthias Maier <tamiko@gentoo.org> CommitDate: 2019-05-19 23:42:11 +0000 app-emulation/libvirt: change '/var/run' to '/run' in rc init files (No revision bump for this minor change - a new revision for libvirt has to be stabilized for the mds vulnearbilities anyway, so let's just sneak this in :-)) Closes: https://bugs.gentoo.org/685302 Package-Manager: Portage-2.3.66, Repoman-2.3.12 Signed-off-by: Matthias Maier <tamiko@gentoo.org> app-emulation/libvirt/files/libvirtd.init-r16 | 4 ++-- app-emulation/libvirt/files/libvirtd.init-r17 | 2 +- app-emulation/libvirt/files/virtlockd.init-r1 | 4 ++-- app-emulation/libvirt/files/virtlogd.init-r1 | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-)
