[virt-tools-list] [PATCHv2 virt-viewer 07/10] kiosk: add --kiosk-quit option

[Marc-André Lureau]

----- Mensaje original -----
> On Mon, Aug 19, 2013 at 03:51:45PM -0400, Marc-André Lureau wrote:
> > 
> > 
> > ----- Mensaje original -----
> > > On Fri, Aug 16, 2013 at 09:47:43PM +0200, Marc-André Lureau wrote:
> > > > In kiosk mode, it's useful to keep the app alive, even if the remote
> > > > session ended for example. Ie, we want to prevent the app from quiting
> > > > itself, even if the remote end closed, lost network, or crashed etc.
> > > 
> > > Any idea if after this commit virt-viewer --reconnect can be implemented
> > > by
> > > just setting the quit-on-disconnect property? I'm a bit annoyed that
> > > there
> > > are these 2 similar features with completely different
> > > implementations/option names/...
> > 
> > There are not at the same level. If virt-viewer --reconnect, virt-viewer
> > will attempt to reconnect on machine restart.
> 
> When using it, --reconnect is more 'if there is no connection, just sit
> there doing nothing until a connection comes up instead of quitting'

That, but also on VM restart for instance.

> > otoh, quit-on-disconnect
> > will quit when there is nothing else we can do (app is deactivated)
> 
> Oh, but when quit-on-disconnect is disabled, will the app just wait doing
> nothing, or will it reconnect if a SPICE connection becomes available
> again? I was assuming the latter when asking my questions, but on second
> thought, the former makes more sense.

If --kiosk-quit never (the default in kiosk mode), then v-v will stay open and do nothing on disconnections.

remote-viewer doesn't attempt to reconnect (although it could learn to do that, but perhaps it's better to recommend virt-viewer in this case)

> Christophe
> 
> > 
> 
> _______________________________________________
> virt-tools-list mailing list
> virt-tools-list at redhat.com
> https://www.redhat.com/mailman/listinfo/virt-tools-list