Anselm Martin Hoffmeister wrote:
Am Montag, den 05.09.2005, 11:00 +0200 schrieb Ondrej Valousek:
Few points:
I am using the latest freenx (0.4.4) & nx 1.5.0 & nomachine's nxclient
and I have found the following:
- the nxproxy is never started. Once you connect and start a session,
only nxagent, nxserver and nxnode instances are running on the server.
The nxproxy are running on the client machine. As I wrote, you can
terminate the session from there by sending them SIGQUIT. That was just
a short test, I'm sure suspending can be initiated on the (application)
server (=X client/LTSP server) side.
This server/client role stuff becomes difficult if you have even more
layers, like introducing NX...
In my case, nxproxy is never run, even on client side. On client side,
only nxclient and nxssh is being run. I assume that nxproxy is a part of
nxclient binary then as nxproxy is not even part of nxclient
installation package from Nomachine.
- If the user has already suspended session suitable to reconnect, user
is automagically reconnected to the suspended session instead of
starting a new one.
That seems to be only partially true - it does not always work cleanly:
If you kill the terminal (power off or similar) and such terminate the
NX client, sometimes the NX server seems to keep the session open
without the possibility to resume it: Only "Terminate" is available.
This might depend on a buggy version I have though; it seems to be
neither the latest nor the most stable build ;-)
Yes, you have to suspend the session cleanly first :-(.
- If the user has already running session with another terminal and
tries to connect from another one, new session is started.
That is why you should disable users from logging in more than once. As
always, there is more than one way to do it. I implemented a small
script called on login - if the user already is logged in, show him a
message "You cannot login twice - log out first on the other terminal"
and terminate the session before it really began at all.
Can you send me that script ? :-)
- the suspended session can only be reconnected from suitable terminal.
Example: session started from terminal running Xsun X server can not be
resumed from Xorg or Windows terminals and so on.
This is true for SunRays, but I think that regular X sessions do not
support hibernate/resume anyway. This is a feature only applicable on
Sun stations, as they use a framebuffer between display and applications
that simply supports suspending of sessions. This of course is not true
for X sessions like "X -query ip.of.sun.server".
Yes, I was talking about SunRays only.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
