On 01/12/2016 01:31 AM, Martin Kletzander wrote:
> On Mon, Jan 11, 2016 at 08:22:33PM -0500, Cole Robinson wrote:
>> When we autolaunch libvirtd for session URIs, we spin in a retry
>> loop waiting for the daemon to start and the connect(2) to succeed.
>>
>> However if we exceed the retry count,
When we autolaunch libvirtd for session URIs, we spin in a retry
loop waiting for the daemon to start and the connect(2) to succeed.
However if we exceed the retry count, we don't explicitly raise an
error, which can yield a slew of different error messages elsewhere
in the code.
Explicitly
On Mon, Jan 11, 2016 at 08:22:33PM -0500, Cole Robinson wrote:
When we autolaunch libvirtd for session URIs, we spin in a retry
loop waiting for the daemon to start and the connect(2) to succeed.
However if we exceed the retry count, we don't explicitly raise an
error, which can yield a slew of
