On Fri, Aug 16, 2013 at 07:39:37AM -0400, Marc-André Lureau wrote: > > > ----- Mensaje original ----- > > On Fri, Aug 16, 2013 at 01:05:12PM +0200, Marc-André Lureau wrote: > > > We want to keep the app alive, in fullscreen, by all means, Even if > > > the remote session ended for example. Ie, we want to prevent the app > > > from quiting itself. > > > > What is the "recovery" scenario for this then. Is it expected to > > reconnect when the remote session starts again ? > > > > Can this not just be handled by people using the '--reconnect' arg > > if they want the app to stay around, rather than forcing all users > > of kiosk mode to have this behaviour. > > I agree with you that it would be eventually interesting to make > this optional, although it should be by default in kiosk mode. So > perhaps a different argument --kiosk-quit-on-disconnect? Or make it key/value, eg --kiosk-quit POLICY where POLICY is one of 'never', or 'on-disconnect', so people can be explicit ? > --reconnect is only implemented in virt-viewer, we may want to use > kiosk mode with remote-viewer too. Oh, I hadn't noticed that. > Btw, how does libvirt handle libvirt disconnections? APIS will just return errors. There is an async event notification you can listen for to find out about disconnects though. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
