http://bugzilla.suse.com/show_bug.cgi?id=933043
James Fehlig changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |systemd-maintainers@suse.de
Flags| |needinfo?(systemd-maintaine
| |rs@suse.de)
--- Comment #3 from James Fehlig ---
I can patch the libvirt socket activation file with something like
Index: libvirt-1.2.16/daemon/libvirtd.socket.in
===================================================================
--- libvirt-1.2.16.orig/daemon/libvirtd.socket.in
+++ libvirt-1.2.16/daemon/libvirtd.socket.in
@@ -2,10 +2,8 @@
ListenStream=@runstatedir@/libvirt/libvirt-sock
ListenStream=@runstatedir@/libvirt/libvirt-sock-ro
-; The following settings must match libvirtd.conf file in order to
-; work as expected because libvirtd can't change them later.
+; The following setting must match libvirtd.conf file in order to
+; work as expected because libvirtd can't change it later.
; SocketMode=0777 is safe only if authentication on the socket is set
; up. For further information, please see the libvirtd.conf file.
SocketMode=0777
-SocketUser=root
-SocketGroup=root
and apply the patch when suse_version <= 1320. Or perhaps there is some
interest in backporting the systemd patches adding SocketUser and SocketGroup
to older systemd (e.g. version 210 used in 13.2 and SLE12)?
@systemd-maintainers: What is your opinion? Should I patch out these options
when building libvirt for everything but Factory. (I see Factory contains
systemd 219, which supports SocketUser and SocketGroup.)
--
You are receiving this mail because:
You are on the CC list for the bug.