Yes, absolutely; these are one-shot sessions: Not useful for say getting
on to a compile server and unthinkingly starting lots of compile
sessions in a twisty little maze of terminal windows.
What I would myself really like is to have a combined form: the
automatic niceness of the scheme I presented combined with persistent
sessions that can be identified and reattached in a vnc viewer app.
Ther persistent session form can still be obtained in the traditional
way, login, start vncserver in the background, go back and start a vnc
viewer tool. Security seems less than perfect then.
The two ways complement each other.
On 2013-03-29 12:20, Edward Ned Harvey (openindiana) wrote:
From: Hans J. Albertsson [mailto:hans.j.alberts...@branneriet.se]
http://wiki.openindiana.org/oi/4.7+Remote+Graphical+Login:+Using+Xvnc+
and+gdm
That's interesting ... So correct me if I'm wrong, you VNC to your server on
5900, and you get a login prompt as if you were sitting down in front of the
physical console. Every new connection to 5900 gets a new login prompt, so you
don't have to consume more ports (5901, 5902, etc).
But if your VNC client crashes for some reason, what happens? I'm guessing the
VNC session dies and all the programs inside it die too. There is no session
manager; when you login to 5900 you can't reconnect to a previously existing
session. Right?
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss