[Xen-devel] [OSSTEST PATCH 3/4] README.dev: Miscellaneous minor improvements

[Ian Jackson <ian.jackson@xxxxxxxxxxxxx>]

Clarify documentation on mg-blockage, and also suggest using
allocation instead.

No longer advise removing crontab as a way to shut osstest down.  The
stop file approach works fine and is less disruptive.

Minor formatting changes.

Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
---
 README.dev | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/README.dev b/README.dev
index 09b9531..6d37ada 100644
--- a/README.dev
+++ b/README.dev
@@ -22,11 +22,14 @@ Removing machines for servicing/outage
 ======================================
 
 mg-blockage <date-from> <date-to> <hostflag> [<extra-xinfo>]
-OSSTEST_CONFIG=production-config ./mg-blockage '2014-05-21 0955' '2014-05-21 
1400' equiv-marilith
 
+Eg
+ OSSTEST_CONFIG=production-config ./mg-blockage '2014-05-21 0955' '2014-05-21 
1400' equiv-marilith
 
 Keeps running for the duration, so run it in a screen on the osstest VM.
 
+Or you can use mg-allocate.
+
 Commisioning a new machine
 ==========================
 
@@ -70,17 +73,16 @@ blessing and add the production ones, e.g.
 
 $ mg-hosts setflags HOSTA HOSTB -- \!blessed-commission 
blessed-{real,play,adhoc}
 
-Shutting down
-=============
 
-crontab -r (remove)
-crontab < crontab (restore afterwards)
+Shutting down the whole system
+==============================
 
-you can create a file "stop" in ~osstest/testing.git or
+You can create a file "stop" in ~osstest/testing.git or
 ~osstest/for-blah/something.git to cause that cron job to not start
 any new things. Put a note in the stop file to say why...  (in the
 former case, disables everything; in the latter, just that "branch")
 
+
 Creating a new branch
 =====================
 
-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel