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

[Unit]
Description=libvirt legacy monolithic daemon read-only socket
BindsTo=libvirtd.socket
After=libvirtd.socket

[Socket]
ListenStream=@runstatedir@/libvirt/libvirt-sock-ro
Service=libvirtd.service
SocketMode=0666
RemoveOnStop=yes

[Install]
WantedBy=sockets.target
Also=libvirtd.socket
Also=libvirtd-admin.socket
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 16:41:10 +01:00			`[Unit]`
systemd: Improve and unify unit descriptions Hypervisors are referred to by their user-facing name rather than the name of their libvirt driver, the monolithic daemon is explicitly referred to as legacy, and a consistent format is used throughout. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> 2023-09-25 16:06:09 +02:00			`Description=libvirt legacy monolithic daemon read-only socket`
systemd: Drop parametrization from libvirtd sockets Up until now the files have been used as template for most services, but now that those have been converted to common templates we can drop parametrization and make it clear that these files are for libvirtd only. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> 2023-09-25 16:14:43 +02:00			`BindsTo=libvirtd.socket`
			`After=libvirtd.socket`
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 16:41:10 +01:00
			`[Socket]`
systemd: Drop parametrization from libvirtd sockets Up until now the files have been used as template for most services, but now that those have been converted to common templates we can drop parametrization and make it clear that these files are for libvirtd only. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> 2023-09-25 16:14:43 +02:00			`ListenStream=@runstatedir@/libvirt/libvirt-sock-ro`
			`Service=libvirtd.service`
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 16:41:10 +01:00			`SocketMode=0666`
systemd: Add RemoveOnStop=yes to all sockets Currently we only set this for the main sockets, which means that $ systemctl stop virtqemud.socket will make the socket disappear from the filesystem while $ systemctl stop virtqemud-ro.socket won't. Get rid of this inconsistency. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> 2023-09-27 17:13:32 +02:00			`RemoveOnStop=yes`
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 16:41:10 +01:00
			`[Install]`
			`WantedBy=sockets.target`
systemd: Add Also between sockets This results in all sockets for a service being enabled when a single one of them is. The -tcp and -tls sockets are intentionally excluded, because enabling them should require explicit action on the administrator's part; moreover, disabling them should not result in the local sockets being disabled too. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> 2023-09-25 17:24:34 +02:00			`Also=libvirtd.socket`
			`Also=libvirtd-admin.socket`