I also read the following, and particularly the bit framed in
************** lines
---------------------------------
In the nowait mode, Xvnc uses its standard input and output
directly as the connection to a viewer. It never has a
listening socket, so cannot accept further connections from
viewers (it can however connect out to listening viewers by
use of the vncconfig program).
*************************
Further viewer connections
to the same TCP port result in inetd spawning off a new Xvnc
to deal with each connection.
*************************
When the connection to the
viewer dies, the Xvnc and any associated X clients die.
This behaviour is most useful when combined with the XDMCP
options -query and -once.
--------------------------------
I can't believe this design wouldn't include logic to just assign a new
display number for each new VNC session...
So it's a bad bad bad design under the hood, and the manual lies or is
at least very incomplete.
Or what?
BTW I haven't been able to find any document actually describing the
"-once" option to "Xvnc -inetd". Where should I look for that? What
alternatives are there, if any, beyond just leaving -once out?
On 2013-03-01 18:55, Jonathan Adams wrote:
I know that the xrdp project tried to wrap a VNC session starter
within the RDP protocol ... but it never really worked well for me,
even when I tried on Linux.
Jon
On 1 March 2013 17:31, Alan Coopersmith <[email protected]> wrote:
On 03/ 1/13 01:32 AM, Hans J. Albertsson wrote:
Given the below quote from man Xvnc, I thought I could use Xvnc+vncviewer for
multiple concurrent logins over the network, but no: It only ever accepts one
connection.
What am I missing?? Some detail in gdm??
----Quoted from the Xvnc manpage
In this configuration, connecting to :0 will result in a new
Xvnc for that connection which should display the standard
graphical login screen on that machine.
In both VNC & X11, display numbers uniquely identify a session - there can only
be one :0 at a time, otherwise when you started a new client with DISPLAY :0,
it wouldn't know which one to connect to.
I don't remember if there's any automated way to start additional vnc sessions
on demand (vs. simply preconfiguring a fixed number of additional displays) -
you can always just run vncserver to start more manually.
If it helps, the cheat sheet on VNC setup methods we made for our QA teams a
few years back (not all of which made it into the docs) can be seen at
https://hg.openindiana.org/upstream/oracle/x-cons/x-s12-clone/file/49256774ae10/open-src/xserver/xvnc/README.txt#l149
--
-Alan Coopersmith- [email protected]
Oracle Solaris Engineering - http://blogs.oracle.com/alanc
_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss
