From 35b5a99d7655ef853c0a87dd46693341c9e6b4cd Mon Sep 17 00:00:00 2001 From: Frank Brehm Date: Sun, 8 Apr 2018 15:41:35 +0200 Subject: [PATCH] committing changes in /etc after emerge run Package changes: --- .etckeeper | 1 - libvirt/libvirt-guests.conf | 57 ------------------------------------- 2 files changed, 58 deletions(-) delete mode 100644 libvirt/libvirt-guests.conf diff --git a/.etckeeper b/.etckeeper index c64dc01d..d5699dbe 100755 --- a/.etckeeper +++ b/.etckeeper @@ -1868,7 +1868,6 @@ maybe chmod 0644 'libnl/classid' maybe chmod 0644 'libnl/pktloc' maybe chmod 0755 'libvirt' maybe chmod 0644 'libvirt/libvirt-admin.conf' -maybe chmod 0644 'libvirt/libvirt-guests.conf' maybe chmod 0644 'libvirt/libvirt.conf' maybe chmod 0644 'libvirt/libvirtd.conf' maybe chmod 0775 'libvirt/lxc' diff --git a/libvirt/libvirt-guests.conf b/libvirt/libvirt-guests.conf deleted file mode 100644 index 2da172b0..00000000 --- a/libvirt/libvirt-guests.conf +++ /dev/null @@ -1,57 +0,0 @@ -# -# Warning: This configuration file is only sourced by the systemd -# libvirt-guests.service unit. The coresponding openrc facility is in -# /etc/init.d/libvirtd and /etc/conf.d/libvirtd -# - - -# URIs to check for running guests -# example: URIS='default xen:/// vbox+tcp://host/system lxc:///' -#URIS=default - -# action taken on host boot -# - start all guests which were running on shutdown are started on boot -# regardless on their autostart settings -# - ignore libvirt-guests init script won't start any guest on boot, however, -# guests marked as autostart will still be automatically started by -# libvirtd -#ON_BOOT=start - -# Number of seconds to wait between each guest start. Set to 0 to allow -# parallel startup. -#START_DELAY=0 - -# action taken on host shutdown -# - suspend all running guests are suspended using virsh managedsave -# - shutdown all running guests are asked to shutdown. Please be careful with -# this settings since there is no way to distinguish between a -# guest which is stuck or ignores shutdown requests and a guest -# which just needs a long time to shutdown. When setting -# ON_SHUTDOWN=shutdown, you must also set SHUTDOWN_TIMEOUT to a -# value suitable for your guests. -#ON_SHUTDOWN=suspend - -# Number of guests will be shutdown concurrently, taking effect when -# "ON_SHUTDOWN" is set to "shutdown". If Set to 0, guests will be shutdown one -# after another. Number of guests on shutdown at any time will not exceed number -# set in this variable. -#PARALLEL_SHUTDOWN=0 - -# Number of seconds we're willing to wait for a guest to shut down. If parallel -# shutdown is enabled, this timeout applies as a timeout for shutting down all -# guests on a single URI defined in the variable URIS. If this is 0, then there -# is no time out (use with caution, as guests might not respond to a shutdown -# request). The default value is 300 seconds (5 minutes). -#SHUTDOWN_TIMEOUT=300 - -# If non-zero, try to bypass the file system cache when saving and -# restoring guests, even though this may give slower operation for -# some file systems. -#BYPASS_CACHE=0 - -# If non-zero, try to sync guest time on domain resume. Be aware, that -# this requires guest agent with support for time synchronization -# running in the guest. For instance, qemu-ga doesn't support guest time -# synchronization on Windows guests, but Linux ones. By default, this -# functionality is turned off. -#SYNC_TIME=1 -- 2.39.5