From f7acdb6c01dbdf5bed728e6c4b990bfc57ca646a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tam=C3=A1s=20G=C3=A9rczei?= Date: Tue, 15 Nov 2016 16:10:54 +0100 Subject: [PATCH] corrected erroneous example command --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3062e9a..a8a7223 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ A logical pre-requisite of all this is tagging the VMs ideally upon creation or This will tag all VMs with the priority of 0 which will leave them stopped. Afterwards an actual order needs to be established by assigning non-zero values to them one by one in ascending order where lesser values represent higher priorities - with the notable exception of 0 - and thus earlier start-up: -vmadm update \ \<\<\< "{\"set_tags\": {\"priority\": 100}}"; done +vmadm update \ \<\<\< "{\"set_tags\": {\"priority\": 100}}" ...and so on. Informational messages are logged via the syslog facility as 'daemon.notice' entries tracking the determined order as well as the outcome for every step taken. The solution comprises two services backed by the same single method script: one activated before svc:/system/zones in order to convince it not to start any guests and the actual payload starting once vmadmd is available to evaluate the tags and complete the sequence.