libvirt/src/remote/libvirtd-admin.socket.in

[Unit]
Description=Libvirt admin socket
Before=libvirtd.service
BindsTo=libvirtd.socket
After=libvirtd.socket

[Socket]
# The directory must match the @sysconfdir@/libvirt/libvirtd.conf unix_sock_dir setting
# when using systemd version < 227
ListenStream=@localstatedir@/run/libvirt/libvirt-admin-sock
Service=libvirtd.service
SocketMode=0600

[Install]
WantedBy=sockets.target
remote: add systemd socket units for UNIX/TCP sockets We don't do socket activation of libvirtd, since we need to unconditionally start libvirtd in order to perform autostart. This doesn't mean we can't have systemd socket units. Some use cases will not need libvirt's autostart & are thus free to use activation. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> 2019-04-30 15:41:10 +00:00			`[Unit]`
			`Description=Libvirt admin socket`
			`Before=libvirtd.service`
			`BindsTo=libvirtd.socket`
			`After=libvirtd.socket`

			`[Socket]`
build: don't hardcode /etc in the config related files Substitute in the @sysconfigdir@ value instead of /etc. Reviewed-by: Christophe de Dinechin <dinechin@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> 2019-07-18 15:17:07 +00:00			`# The directory must match the @sysconfdir@/libvirt/libvirtd.conf unix_sock_dir setting`
remote: update config files to note usage wrt systemd socket activation Certain libvirtd.conf settings are not honoured when using systemd socket activation. Certain systemd unit file settings must match those defined in libvirtd.conf for systemd socket activation to work with systemd version < 227, otherwise libvirtd cannot determine which inherited FD to use for which service. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> 2019-06-24 11:00:37 +00:00			`# when using systemd version < 227`
remote: add systemd socket units for UNIX/TCP sockets We don't do socket activation of libvirtd, since we need to unconditionally start libvirtd in order to perform autostart. This doesn't mean we can't have systemd socket units. Some use cases will not need libvirt's autostart & are thus free to use activation. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> 2019-04-30 15:41:10 +00:00			`ListenStream=@localstatedir@/run/libvirt/libvirt-admin-sock`
			`Service=libvirtd.service`
			`SocketMode=0600`

			`[Install]`
			`WantedBy=sockets.target`