Xref: utzoo comp.unix.microport:1333 comp.unix.questions:8887 comp.unix.wizards:10563 Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!zippy.berkeley.edu!ewv From: ewv@zippy.berkeley.edu (Eric Varsanyi) Newsgroups: comp.unix.microport,comp.unix.questions,comp.unix.wizards Subject: Re: SVR3 console message capturing Keywords: SVR3, Bell Tech, System V/386 Message-ID: <13439@agate.BERKELEY.EDU> Date: 18 Aug 88 23:04:15 GMT References: <184@thebes.Thalatta.COM> <11426@lll-winken.llnl.gov> Sender: usenet@agate.BERKELEY.EDU Distribution: na Organization: Cray Research, Inc. Lines: 12 In article <11426@lll-winken.llnl.gov> bowles@lll-crg.llnl.gov.UUCP (Jeff Bowles) writes: >In article <184@thebes.Thalatta.COM> gregoire@Thalatta.COM (Keith Gregoire) writes: >>I am looking for a way of capturing console error messages (notices, >Included in the Bell Tech release (and EVERY System V source release since >SVR3.0) is a driver called "osm". If you have another machine, you can patch 'kernputc' to either 0x2f8 or 0x3f8 and all kernel printf's will go to the serial port (at 9600 baud). The problem with osm is that it does not catch a panic message, you have to go look at the dump to find the panic since the 'cat' will never get dispatched after a panic. If you have another box that can record stuff off the serial port it is a great way to log disk errors and other stuff that usually scrolls away.