Hey Steve,
Thanks for the patches.
On 06/08/11 - 09:25:47PM, Steven Dake wrote:
Signed-off-by: Steven Dake <sdake(a)redhat.com>
---
man/oz-install.1 | 11 ++++++++---
1 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/man/oz-install.1 b/man/oz-install.1
index b497813..7cf0077 100644
--- a/man/oz-install.1
+++ b/man/oz-install.1
@@ -70,9 +70,14 @@ will undefine the libvirt guest with the same name or UUID and delete
the diskimage, so it should be used with caution.
.TP
.B "\-t"
-Use a timeout value of \fBtimeout\fR for installation, rather than the
-oz default. This can be useful if you know you have slower storage
-and want to wait longer for the installation to timeout.
+Terminate the installation of the guest image in \fBtimeout\fR seconds
+rather then the default of 1200 seconds. This value can be increased in the
I've tried to some extent not to mention what the defaults here are. The
reason being that the defaults are different depending on what operating system
you are installing. For Linux guests, the default is indeed 1200, but for
Windows guests the default is 3600.
+case of slow storage or multiple oz-install operations on the same
machine
+consuming the disk bandwidth.
+
+Please note there is a separate termination action that occurs if 300 seconds
+elapses before any data is written to the VM image. This timer value is not
+configurable.
Right, this part makes sense. So maybe if we did a combination, and did
something like:
Terminate the installation of the guest in \fBtimeout\fR seconds rather than
the oz default. This value can be increased in the case of slow storage or
multiple oz-install operations on the same machine.
Please note that there is a separate termination action that occurs if 300
seconds elapses before any data is written to the VM image. This timer value
is not configurable.
Does that sound reasonable?
--
Chris Lalancette