On 08/08/16 16:27, Michal Privoznik wrote:
> On 29.07.2016 14:06, Erik Skultety wrote:
>> Just like we decide on which URI we go with based on EUID for qemu in remote
>> driver, do a similar thing for admin except we do not spawn a daemon in this
>> case.
>>
>> Resolves: https://bugzilla.redhat.com
On 29.07.2016 14:06, Erik Skultety wrote:
> Just like we decide on which URI we go with based on EUID for qemu in remote
> driver, do a similar thing for admin except we do not spawn a daemon in this
> case.
>
> Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1356858
>
> Signed-off-by: Erik
On Fri, Jul 29, 2016 at 03:40:28PM +0200, Michal Privoznik wrote:
On 29.07.2016 14:08, Daniel P. Berrange wrote:
On Fri, Jul 29, 2016 at 02:06:00PM +0200, Erik Skultety wrote:
Just like we decide on which URI we go with based on EUID for qemu in remote
driver, do a similar thing for admin excep
On 29.07.2016 14:08, Daniel P. Berrange wrote:
> On Fri, Jul 29, 2016 at 02:06:00PM +0200, Erik Skultety wrote:
>> Just like we decide on which URI we go with based on EUID for qemu in remote
>> driver, do a similar thing for admin except we do not spawn a daemon in this
>> case.
>
> IMHO we shoul
On Fri, Jul 29, 2016 at 02:06:00PM +0200, Erik Skultety wrote:
> Just like we decide on which URI we go with based on EUID for qemu in remote
> driver, do a similar thing for admin except we do not spawn a daemon in this
> case.
IMHO we should auto-spawn the daemon too, so we have consistent
behav
Just like we decide on which URI we go with based on EUID for qemu in remote
driver, do a similar thing for admin except we do not spawn a daemon in this
case.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1356858
Signed-off-by: Erik Skultety
---
src/libvirt-admin.c | 10 +++---
1 f