I Use a LTSP network for nearly 2 years in an Internetcafee in Amsterdam
Centrum. With two ubuntu-5.04 servers (hoary) and and the ltsp-4.1 scripts.
Works really great! Customers love it too.
Remotely starting up (etherwake) and shutting down (ltspinfo -h xxx -s) each
terminal was especially very handy. It also saved a lot of electricity
because we didn't always have all the 20 terminals (PII oldies) running.
I migrated this month to Ubuntu-6.10 (dapper) and ltsp-4.2 - from scratch
on a new disk - and I am very positive about the stability, short booting
time and extra possibilities of dapper and ltsp42
But there is one thing that doesn't function anymore. Shutting down the
terminals with the command 'ltspifo -h xxxx -s' gives a wierd result: The
terminals do not shut down, but the keyboards and IR-mouses die, leaving the
terminals in coma (Nice grafical gnome desktop, but no interaction.)
A friend also installed dapper and ltsp on very different hardware, and had
exactly the same result.
I hope it's a known problem fo which a solution exists.
Has anyone already figured out what's wrong, and how to fix this. Would be
great!
George
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_____________________________________________________________________
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
