On Thu, Jun 15, 2006 at 07:48:53AM -0400, Camp.external at qimonda.com wrote:
It happened again. I tried adjusting the vmstat from 300 to 290 just as a guess, but no luck. I cannot find any cores, any logs anything that indicates anything going on. Is there some sort of debug mode I can turn on or tracing I can do to figure out why it is dying?
Login as the hobbit client user, cd to the the client/ directory, then cut-and-paste this to start the hobbitlaunch utility as a foreground task with debug output enabled:
MACHINEDOTS="uname -n"
MACHINE="uname -n | sed -e's/\./,/g'"
BBOSTYPE="uname -s | tr '[A-Z]' '[a-z]'"
BBOSSCRIPT="hobbitclient-uname -s | tr '[A-Z]' '[a-z]'.sh"
HOBBITCLIENTHOME="pwd"
bin/hobbitlaunch --config=etc/clientlaunch.cfg --no-daemon --debug
Henrik