diff options
author | H. P. <harald.p.@xmart.de> | 2018-07-09 17:42:39 +0200 |
---|---|---|
committer | H. P. <harald.p.@xmart.de> | 2018-07-09 17:42:39 +0200 |
commit | acedee054e3427880b10b0537f971b8eec9f99e5 (patch) | |
tree | 6362edfb548d69ba9910c3a70b7310b638645a0f | |
parent | e28143db4c0cf9d2c203445eb92b05f98ad828e4 (diff) | |
download | systemd-units-acedee054e3427880b10b0537f971b8eec9f99e5.tar.bz2 |
Update of README
-rw-r--r-- | README.md | 10 |
1 files changed, 7 insertions, 3 deletions
@@ -30,9 +30,13 @@ self-explanatory. Therein, you'll find the following: 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. Still under development, look at the - comments in the services - the starting and stopping of the VMs - is still insufficiently written. + well - here we are.<br/> + 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 |