From 4b1d8df6e6472f28c6f91f0a76e3bbbe7163802d Mon Sep 17 00:00:00 2001 From: Harald Pfeiffer Date: Tue, 10 Jul 2018 10:16:35 +0200 Subject: Updated README to match commit @ea030c2 --- README.md | 19 ++----------------- 1 file changed, 2 insertions(+), 17 deletions(-) diff --git a/README.md b/README.md index 6ef9fc1..76db710 100644 --- a/README.md +++ b/README.md @@ -7,6 +7,8 @@ Some examples: * freshclam? No reason for it on Debian, but on Fedora (no package with a service on FC28). * KVM machines? libvirtd-guests is great, but not always wanted or available. + (Obsolete exmple, that is now in a repo of its own. The idea behind still + works ;) ) Consider this repository examples for now. Some of this is still heavy WiP, e.g. the KVM stuff is still too specific and not all dependencies required, @@ -24,20 +26,3 @@ self-explanatory. Therein, you'll find the following: for administering this is called freshclamd, it does not interfere with anything on a Fedora 28. Rename it if your distro is different, a Debian user will not need this at all ;) - -* **kvm-\*:** Stuff I wrote for starting and stopping KVM networks and virtual - machines through systemd. Networks usually are covered by the - autostart function of KVM, and machines can be safely shut down - with libvirt-guests - but in this scenario I wanted to automate - through and integrate everything into systemd services, so, - well - here we are.
- The script usr/local/bin/kvmhelper can also serve as a shortcut - or beautification, but its main purpose is to serve the systemd - units as a short-definition target with timeouts in itself to - come before the systemd timeout, *and* this has proper failure - values for a systemd unit (stop machine, oh it's down? not a - failure, we're satisfied!) -* **cluster-\*:** A simple systemd target describing dependencies on three - *KVM* machines (see above) which form a pacemaker (Red Hat pcs) - cluster, so they should be alive at the same time. One systemd - unit instead of a long command, whey! :) -- cgit v1.2.3