1) What's the clean way of remote restarting clients.
We have set up X script that monitors if terminal is idle (and
restarts the terminal, if it's not used so that next guest would not
find terminal open with some other peoples documents and webpages.
Right now we are calling "killall -u <user> icewm-session" from
thincan x environment, if user is idle some predefined time. Seems to
work most of the ime. Is there more elegant way?
There seems to be some problem here, since thincans report themselves
that they will kill the session (by just writing log to server), but
then the client is gone and never returns. It's a bit tricky to do
onsite monitoring right now to know what terminal is doing actually.
Remote access is all I can use right now. But i'm just asking if we are
doing something fundamentaly wrong.
2) These thincans sometomes lose internet connection and then all
processes the client had running will still be running on server. What's
the clean way of getting rid of these. Again - we are doing kill -9 on
all user processes (from terminal server)
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_____________________________________________________________________
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
