From 84b9b20ca6241b6f40dbd5afe22d6df3078751cf Mon Sep 17 00:00:00 2001 From: Alvaro Lopez Garcia Date: Wed, 15 Feb 2012 09:49:15 +0100 Subject: Fix the description of the --vnc_enabled option Change-Id: If03c8613ec11e6f95f830ef48dd3978e874ecf5d --- doc/source/runnova/vncconsole.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/source') diff --git a/doc/source/runnova/vncconsole.rst b/doc/source/runnova/vncconsole.rst index fa8fb3f26..264bc6b71 100644 --- a/doc/source/runnova/vncconsole.rst +++ b/doc/source/runnova/vncconsole.rst @@ -124,8 +124,8 @@ Support for a streamlined flow via dashboard will land in essex. Important Options ----------------- -* :option:`--vnc_enabled=[True|False]` - defaults to True. If this flag is - not set your instances will launch without vnc support. +* :option:`--[no]vnc_enabled` - defaults to enabled. If this flag is + disabled your instances will launch without vnc support. * :option:`--vncserver_listen` - defaults to 127.0.0.1 This is the address that vncservers will bind, and should be overridden in production deployments as a private address. Applies to libvirt only. -- cgit