Prakash,
Could be that your clients are running out of ram.
Try turning on NFS swap, to see if the problem goes away.
Sure it will be slower than real ram, but at least it shouldn't
crash.
The setting is:
USE_NFS_SWAP = Y
SWAPFILE_SIZE = 32m
What usually happens is a process asks the kernel for more ram.
The kernel can't fulfill the request, so it goes looking for
virtual ram. If there is no swap, it then gets serious, and
in an effort to save itself (The kernel doesn't want to die due
to lack of ram), it goes on a killing spree, killing whatever it
can, to regain some memory. Well, there arent very many processes
usually running on the client, but one really big process that the
kernel can kill to regain memory is the Xserver. Well, if it kills
the Xserver, you lose your session.
I hope that helps,
Jim McQuillan
[EMAIL PROTECTED]
PS: If you say "lack of ram" 10 times really fast, it ends up
sounding like "Rack of Lamb".
Which brings up the question: Is it lunch time yet ? :)
On 12 Feb 2003, Prakash Advani wrote:
> Occationally some of our Terminals get logged out, which means they lose
> all their unsaved data. This happens even if the load isn't very high
> say around 2. Out of 40 Clients that we have this happens to atleast one
> a day.
>
> We use Red Hat 7.2, KDE, LTSP 3.x, Evolution 1.0.8, Mozilla 1.0.1, Open
> Office 1.0.1. Server is Dual Pentium III, 1.5 GB RAM, 2 X 80 GB IDE HDD.
>
> Does anyone has any ideas whats going on? Has anyone experienced
> anything similar?
>
>
--
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_____________________________________________________________________
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
