On 05/14/2013 05:17 PM, Christophe Fergeau wrote:
Hey,
On Wed, May 08, 2013 at 01:22:47PM +0800, Guannan Ren wrote:
-vnc :5900,share=allow-exclusive
allows clients to ask for exclusive access which is
implemented by dropping other connections Connecting
multiple clients in parallel requires all clients asking
for a shared session (vncviewer: -shared switch)
-vnc :5900,share=force-shared
disables exclusive client access. Useful for shared
desktop sessions, where you don't want someone forgetting
specify -shared disconnect everybody else.
-vnc :5900,share=ignore
completely ignores the shared flag and allows everybody
connect unconditionally
rdp seems to support some similar (though they don't look identical)
features through replaceUser/multiUser.
« The replaceUser attribute is a boolean deciding whether multiple
simultaneous connections to the VM are permitted. The multiUser attribute
is a boolean deciding whether the existing connection must be dropped and a
new connection must be established by the VRDP server, when a new client
connects in single connection mode. »
I'm wondering if we should try to use similar attributes for both rdp and
vnc for more consistency?
These vnc server flags need to work together with vnc client flag
(like: -Shared for vncviewer)
for a certain behaviour, and these flags focus on how to share
more than whether to share
or not.
I don't know more about RDP, it seems that their common behaviours
are not quite same
according to above docs.
Guannan
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list