Hi, all, Those of use who have used Windows terminal servers are familiar with the annoyance of the client disconnecting every 30 seconds or so, causing a CPU spike on the server. A colleague of mine has an elegant solution for this on his Windows-based thin clients, wherein he has written a simple shell, to which the client boots, presenting only a large button that says to the effect of "Click Here to Log In". The client boots to this shell and sits quietly until a user clicks the button. Only then does the client attempt to contact the terminal server for login, and the server is unmolested by idle clients.
When my colleague told me about this I thought it was great, and I wondered why I hadn't thought or read about this in the Linux world. We love LTSP here. My colleague is on another campus and is not familiar with LTSP, but he recognizes the power of centralized management and diskless booting, not to mention all the advantages of open source. Unfortunately, all the programmers here are of the Windows/VS/.net breed. I am the most knowledgeable about Linux, but have virtually no programming skill. So I'm wondering if this sort of thing has been done. If so, where can I learn about it? Is it integrated into LTSP? Could it be? It really seems to me that this is the right way to handle rdesktop logins from a thin client. What say ye? db ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-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
