mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-02-06 03:39:29 +00:00
c46e1a92ce
Since we can't know at service start how many VMs will be running we
can't calculate an apropriate shutdown timeout. So instead of killing
off the service just let it use it's own internal timeout mechanism.
References:
http://bugs.debian.org/803714
https://bugzilla.redhat.com/show_bug.cgi?id=1195544
(cherry picked from commit ba08d16d6cec81656b333435650aef36a012034c)
20 lines
504 B
SYSTEMD
20 lines
504 B
SYSTEMD
[Unit]
|
|
Description=Suspend Active Libvirt Guests
|
|
After=network.target libvirtd.service time-sync.target
|
|
Documentation=man:libvirtd(8)
|
|
Documentation=http://libvirt.org
|
|
|
|
[Service]
|
|
EnvironmentFile=-/etc/sysconfig/libvirt-guests
|
|
# Hack just call traditional service until we factor
|
|
# out the code
|
|
ExecStart=@libexecdir@/libvirt-guests.sh start
|
|
ExecStop=@libexecdir@/libvirt-guests.sh stop
|
|
Type=oneshot
|
|
RemainAfterExit=yes
|
|
StandardOutput=journal+console
|
|
TimeoutStopSec=0
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|