[libvirt] [PATCH] remote: Improve error message when libvirtd isn't running

[Dave Allan]

On 02/24/2010 12:55 PM, Cole Robinson wrote:
> While this could lead people in the wrong direction, people most commonly
> hit this error when libvirtd isn't running, so let's mention a possible
> fix.
>
> Signed-off-by: Cole Robinson<crobinso at redhat.com>
> ---
>   src/remote/remote_driver.c |    4 ++--
>   1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/remote/remote_driver.c b/src/remote/remote_driver.c
> index 8914c39..e10312c 100644
> --- a/src/remote/remote_driver.c
> +++ b/src/remote/remote_driver.c
> @@ -723,8 +723,8 @@ doRemoteOpen (virConnectPtr conn,
>                   }
>               }
>               virReportSystemError(errno,
> -                                 _("unable to connect to '%s'"),
> -                                 sockname);
> +              _("unable to connect to '%s', libvirtd may need to be started"),
> +              sockname);
>               goto failed;
>           }
>

ACK.  True, it could lead people in the wrong direction, but you've 
phrased it nicely, and I think on the whole it's a good usability 
enhancement.

Dave