"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Hi All,
> OK. I figured out how to get my blog stuff working in English, so you
> can also read about the modified mdb on my blog,
> http://mbruning.blogspot.com/
Well, let me take your use your work on mdb as a cause for thoughts on kmdb
usability on Solaris x86.
Problem:
If you do not own a x86 system that itself implements remote
administration, you need to run Solaris x86 permanently under kmdb.
This is because the only way to abort a hung x86 system is to send
a <break> to ttya and to let kmdb handle abortion.
Pitfall:
If such a system panics for some reason, it will not auto-reboot
but hang until the sysadmin types e.g. ":c" at the kmdb prompt.
Idea for solution:
Allow to configure kmdb to fall through to dumping core in case
of a panic() call and allow to configure kmdb to wait some time
for possible adminstrative input from ttya.
I asume that for a simple solution it would be sufficient to prepend a
if (!panicstr) to the for(;;) loop in kmdb_main.c::kmdb_main()
Is this correct?
My other question: how to let a stand alone program / co-routine like
kmdb to check for let's say 60 seconds of unsuccessful wait for input
from stdin?
Any thoughts? Any help?
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-discuss mailing list
[email protected]
