Hi all,
On Mon, 22 Aug 2005, Jason Maas wrote:
Does anyone know how to see the kernel log on an LTSP client?
I do! (Yes, I realize that I'm replying to myself. I finally got
motivated enough to try things.)
On our Debian "unstable" LTSP server I just copied the /bin/dmesg binary
to /bin in the LTSP client filesystem. And it works.
Next I went ahead and froze a terminal (64MB RAM, no swap) with a web page
of monster images, and now I finally know what was happening: the client's
linux kernel is killing X! Here is the kernel output as seen by 'dmesg':
---- [Begin kernel error messages] ----
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
VM: killing process Xorg
---- [End kernel error messages] ----
Turning on swap does prevent that from happening on that same terminal, so
that's an excellent workaround. It sure would be nice if there was a way
to make X just work with less memory rather requesting so much that the
kernel kills it. Maybe a different kernel OOM (out of memory) setting
would help for the standard LTSP kernels?
Jason
-------------------------------------------------------
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
