Xref: utzoo comp.unix.wizards:21007 comp.unix.xenix:10561
Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.unix.wizards,comp.unix.xenix
Subject: Re: System V kernel panic not syncing
Keywords: Panic SystemV
Message-ID: <610@sixhub.UUCP>
Date: 13 Mar 90 19:12:06 GMT
References: <779@s5.Morgan.COM>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Followup-To: comp.unix.wizards
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 15

In article <779@s5.Morgan.COM> amull@Morgan.COM (Andrew P. Mullhaupt) writes:
| Anyone know how to get the SCO UNIX System V/386 r3.2 kernel
| to do sync when it panics so fsck is happy when you start up again?

  I believe that an attempt is made to determine if a sync can be done
or not. If the kernel thinks the in-memory info is bad it should NOT try
to sync, since this may keep fsck from recovering anything. I seem to
recall installing a patch in SysIII to prevent the sync.

  Or you could use a version which doesn't panic ;-(
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc
"Getting old is bad, but it beats the hell out of the alternative" -anon