Kris Kerwin wrote:
I've tried catting the output from dmesg and running it regularly with
crontab, as was advised below. This, unfortunately doesn't work because cron
can only run as often as once a minute. This means that if a crash happens in
between these dmesg snapshots, the debugging information is lost. The only
way that catting dmesg to a file will work is if the crash just so happens to
occur right as dmesg is being logged. I might be able to increase my chances
if there was anyway to set up vixie-cron to run more often than once a minute
(once a second? more?)
Why not run a bash script, something like (not tested or debugged! And I
can't remember how to do a while loop in bash;)
while true; do
if [ -e /tmp/stopdmesg ]; then
exit;
else
dmesg > dmesg-$(date +%Y%m%d%H%m%s)
sleep(5)
fi
done
Open up your terminal and run the script (and append & to send it to the
background). If needs be, change sleep(5) to as low as you need to get the
dmesg information.
--
Jonathan Wright ~ mail at djnauk.co.uk
~ www.djnauk.co.uk
--
2.6.12-gentoo-r6-djnauk-b2 AMD Athlon(tm) XP 2100+
up 1 day, 9:03, 3 users, load average: 3.62, 2.94, 2.42
--
"The Bible contains six admonishments to homosexuals and three
hundred sixty two admonishments to heterosexuals. That doesn't
mean that God doesn't love heterosexuals. It's just that they
need more supervision."
~ Lynne Lavner
--
[email protected] mailing list
