> Is there a reason why you would want to launch the vncserver from within
> the user environment ?
> The reason why I ask this is that you could start the vncserver by the
inetd
> process,
> which would allow any user to connect through VNC to your host.
> The server that whould be started could connect to a XDMCP server (in oder
> words
> receive a graphical login to your station). This would ensure that only
> clients known
> to the system would be able to connect.
Hmmm... this is really tempting, as I generally like inetd. It often makes
things so darn SIMPLE.
I think I see some problems with this approach, though.
The first user would get display #0. Let's say the first user disconnects
without terminating the application (God I wish there were a way to avoid
that!). The second user to connect would resume the first user's instance
of the application. This is not good, for our application.
Question: Is there any way to cause VNC to terminate the application when a
user disconnects from VNC ? That would solve a lot of problems.
My other concern: I am a bit new to all this, and I am anticipating there
will be times when a session "gets in trouble" somehow. I think we may need
the capability to kill and restart the session (VNC server instance and the
associated GUI application) for a specific user. With the inetd approach, I
don't think we could identify which processes are associated with each user.
-Lee Allen
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
