Jason, I don't have any solid formula for setting the size of the swapfile. I've found that just going with 64mb of swap has solved any problems that I've encountered.
As for "all situations", i'm sure there's a point where you could run out of ram, even with 64mb of ram and 64mb of swap. Jim. On Mon, 22 Aug 2005, Jason Maas wrote: > Hi Jim, > > On Mon, 22 Aug 2005, Jim McQuillan wrote: > > > There's just no getting around the fact that the Xserver is going to > > consume memory. And for the most part, it's not X's fault, it's the > > applications. the Xserver allocates memory on the apps behalf, and most > > apps don't tell the Xserver to release the memory when it is done with > > it. > > Thanks for the explanation, it's very helpful for someone like me who's not > familiar with the nitty gritty details of X. > > > So, for now, we have the NFS-Swap safety net, which is better than > > having the Xserver croak. > > Definitely! So does NFS-Swap prevent X from getting nuked in all situations? > Do you have any recommendations from your experience regarding RAM, swap, or > total combined memory size? > > Thanks so much for all of your hard work on LTSP, it's a fantastic project! > > Jason > > -- > Jason Maas > DiscipleMakers Systems Dept -- www.dm.org > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _____________________________________________________________________ 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
