Hi Lachele, as the moments when the logoffs accur seem to be related to graphics (moving window to another desktop, open xterm, start Unity3D...): could it be a problem of the graphics driver?
I have had (and still have) big problem with the intel X driver, especially 3d acceleration. Your setting XRAMPERC so low might simply have prevented the driver from activating 3d acceleration. Just a wild idea. Good luck! Rüdiger On 01/03/2012 05:29 PM, Lachele Foley (Lists) wrote: > I'm really confused about why changing X_RAMPERC fixed one problem, > and if so, why it didn't fix another. > > The issue is that clients with less RAM won't need to have X_RAMPERC > set lower, but clients with more RAM will. There are other > differences, of course -- different hardware, different client image > (64 vs 32). But, it seems odd that a client with 1 GB of RAM can > handle something that a client with 2 or 4 GB can't. > > And, I'm not talking about a system that has other programs eating > memory. I mean (1) boot client, (2) log in, (3) start or start to use > program, (4) back to login immediately. On one machine (loaner, no > longer available for testing), this would cause it: (1) boot (2) log > in (3) open terminal (4) "ltsp-localapps xterm". I'm surprised that > opening a couple terminals could eat that much memory that quickly. I > didn't try resetting X_RAMPERC on that machine because I simply could > not believe that was the problem. I could open and run other programs > -- there were only a few that caused it. When they did, though, they > did so immediately or almost immediately. > > Most recently, the program VMD would cause crash-to-login if its > display window was moved from one monitor to the other. Again, this > is at fresh boot and login, and without having even loaded any files > into VMD. Oddly, running VMD as a localapp on the client worked fine > (and a lot faster). However, I finally decided to try lowering > X_RAMPERC, and, lo-and-behold, VMD stopped crashing when not run > locally. These clients have 4 GB and the server has 32. During these > tests, there was very little load on the server either. Right now, > with three different browsers, each with multiple windows, evince and > a handful of terminals running, that same client says it has 3.37 GB > of its 3.94 GB free (using "free"). I just opened VMD, and that > changed to 3.36 free. We also have several dual-monitor setups on > older equipment that handle this sort of thing just fine, and lots of > other stuff, all at once. > > So, even though setting X_RAMPERC fixed the VMD issue... I wonder if > the problem isn't really somewhere else. > > By the way, even setting X_RAMPERC to 20 didn't make the default > Unity3D session work. It still appears to accept a password, then > makes the theme music, then back to login. Other sessions (2D, XFCE, > LDXE, xterm) work fine. > -- Dr. Rüdiger Kupper <[email protected]> Kepler-Gymnasium Freudenstadt
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_____________________________________________________________________
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
