More than 1 user login
Mon Apr 7 10:25:01 2003
> -----Original Message-----
> From: Niels Bergsma [mailto:firstname.lastname@example.org]
> I manage a unix terminal server and I search for a way that users can
> login trought the web, with a java-based client or something. Now VNC
> can do almost all that but I'm wondering if different users (let's say
> Jim and Joe) can login to there own KDE session at the same time and
> work individually. (so they don't share the same desktop)
> Can VNC do this?
Once you have http://www.sourcecodecorner.com/articles/vnc/linux.asp
operational, everyone that connects, gets its own session at which he/she
must use its own account.
Best thing is to create a single website at which you distribute viewers for
all platforms. Users should download and run the binary viewer. There is no
installation needed (however, it can be comfortable to install it on some
Since the mentioned setup starts vnc-servers as needed, the webserver build
into those vncservers cannot be used (and are therefor not configured in
this setup). However, you can use any other webserver to get something
going, even an other vncserver. It just needs to be running. The
configuration is roughly as follows:
Have the webserver serve the files in .../vnc/classes/. The *.jar and
*.class files are the java viewer. Just serve them. The *.vnc files are
templates for html files, normally served by the vnc-server. You can edit
and rename them to match what you have if you look at the html-source you
get in the browser.
Example using the vncserver-webserver. Get a vncserver running that has the
webserver/javaviewer operational: if you browse to http://vncserver:5801/
you get your vncsession. (no configuration needed, it can be just blank or
whatever, just the webserver needs to run). Copy .../vnc/classes/index.vnc
to .../vnc/classes/index.html. Compare this new file to what you get as html
source in your webbrowser. In the webbrowser, there is 5901 assigned to a
variable (...port...) inside the index.html file. Inside the index.html
file, force it to 5950. Then put your browser to
http://vncserver:5801/index.html et voila.
If you have the above operational, you can see its disadvantages. As long as
the webbrowser is pointed to the index.html file, the session is available.
As soon as the webbrowser is pointing elsewhere and goes back, the session
is lost and a new session is started... This is the nature of the beast,
currently there is no solution for this problem. However, if this is
acceptable you can suit your needs: rename index.vnc to static, create a new
index.vnc file, just being a html page with urls to the static and many new
files, a-la index.html created above.