mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-02-11 06:01:33 +00:00
f496ce1df3
Commit 839a060 tied the lifecycle of virtlogd more closely to that of libvirtd. Unfortunately, while starting virtlogd when libvirtd is started is definitely a good idea, restarting virtlogd or shutting it down at any time outside of system poweroff is not. Revert part of that commit by removing the PartOf= lines, meaning that only startup requests will be propagated from libvirtd to virtlogd. Resolves: https://bugzilla.redhat.com/1372576
19 lines
479 B
SYSTEMD
19 lines
479 B
SYSTEMD
[Unit]
|
|
Description=Virtual machine log manager
|
|
Requires=virtlogd.socket
|
|
Before=libvirtd.service
|
|
Documentation=man:virtlogd(8)
|
|
Documentation=http://libvirt.org
|
|
|
|
[Service]
|
|
EnvironmentFile=-/etc/sysconfig/virtlogd
|
|
ExecStart=@sbindir@/virtlogd $VIRTLOGD_ARGS
|
|
ExecReload=/bin/kill -USR1 $MAINPID
|
|
# Loosing the logs is a really bad thing that will
|
|
# cause the machine to be fenced (rebooted), so make
|
|
# sure we discourage OOM killer
|
|
OOMScoreAdjust=-900
|
|
|
|
[Install]
|
|
Also=virtlogd.socket
|