Rolf; KDE runs in memory on the server, virtual screens and all. X runs on the terminal, managing the display.
In the case of LTSP, the entire screen displays an XDMCP session running on the server, KDE and all. This is the default for LTSP, unless you've done some *heavy* modification so it operates like the Terminal server on Knoppix. In any event, virtual window managers don't necessarily use a lot of memory. The REAL memory usage is by the processes running in those virtual sessions. Tom > when you've got KDE for instance, the user can choose to have a number > of virtual screens. > > Where is the RAM used for saving these screens, on the server or on the > client? What I mean is, might it be critical to have clients with few > RAM and too many virtual screens running, or is there only one single > surface on the client which must be saved by the client itself, and the > screens are managed by the server? -- ---------------------------------------------------------------------- Thomas L. Griffing Red Hat Certified Engineer Pondus Solutions, Inc. [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _____________________________________________________________________ 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
