Ken Schneider - openSUSE said the following on 11/10/2013 05:02 PM:
On 11/10/2013 09:20 AM, Anton Aylward pecked at the keyboard and wrote:
I have set up vnc on some of my servers but I'm faced with a few conundrums.
First, if I run
# systemctl isolate multi-user.target
it goes away. But if I use "ssh -X" to the server I can run the X/GTK GUI tools.
Secondly all the ways I've found to set up a vcnserver start it ip as a singleton. I cant see how to treat it like I do other network services and have it started from XinetD and have it (a) run on demand and (b) run more than once. Call it "multi-seat" if you will. Since it uses, or can use, a software framebuffer (eating memory) then why not? It sounds better than the way Citrix/Cisco do Windows VDIs.
You DO NOT need X running on the remote servers to start their GUI programs, you only need to install the needed programs/libraries. ssh -X should be enough.
Yes, that's right. That's what I said. The "systemctl isolate multi-user.target" means its not running the GUI, so I can "ssh -X", as you say, and get the programs to run "over there" but display "over here". That's what the X protocol was always about. That's how we could 'call home" using the X-terminals in the terminal room at USENIX back in the '80s to read mail on our home SUN workstations. Or server. The SSHD can support many connections. Many people could use "ssh -X" and run the GUI programs on the same server. UNIX always was 'multi-seat" :-) Fine. Good. Yes. Now lets move on and leave the issue of "ssh-X' behind and address VNC, please. My point is that that this doesn't seem to be the same with vnc. Or at least I haven't found a way to, for example, have the XinetD spawn copies of the vncserver on demand, allowing many people to make a vnc connection to the server, each getting their own instance. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org