Xref: utzoo comp.unix.microport:1341 comp.unix.questions:8895 comp.unix.wizards:10586
Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!lll-winken!lll-tis!ames!killer!vector!rpp386!pigs!haugj
From: haugj@pigs.UUCP (Joe Bob Willie)
Newsgroups: comp.unix.microport,comp.unix.questions,comp.unix.wizards
Subject: Re: SVR3 console message capturing
Summary: system v error demon
Keywords: SVR3, Bell Tech, System V/386
Message-ID: <363@pigs.UUCP>
Date: 19 Aug 88 17:24:59 GMT
Article-I.D.: pigs.363
References: <184@thebes.Thalatta.COM>
Reply-To: haugj@pigs.UUCP (Joe Bob Willie)
Distribution: na
Organization: Big "D" Oil and Gas
Lines: 22

In article <184@thebes.Thalatta.COM> gregoire@Thalatta.COM (Keith Gregoire) writes:
>
>I am running Bell Tech System V/386, release 3 on a Bell Tech 386.
> 
>I am looking for a way of capturing console error messages (notices, 
>warnings and panics) to a file (or at least a printer) such as
>the way BSD and XENIX do with dmesg.  I have scoured the Bell Tech
>System Admin manuals and cannot find a clue as to whether there is 
>an existing way to do this.  The dmesg command cannot be found.  

is /usr/lib/errdemon present on your system?  we have it here.  it
takes reads from /dev/conslog and writes to /usr/adm/console_log.
i believe our system is S5R2 based.  one might assume bell tech didn't
remove features ...

however, the device driver for a console log output driver is very
simple.  read from the system error message ring buffer, write to
the user address space (passc() should be helpful here).  do this until
u.u_count goes to zero or passc() returns an error.
-- 
 jfh@rpp386.uucp	(The Beach Bum at The Big "D" Home for Wayward Hackers)
     "Never attribute to malice what is adequately explained by stupidity"
                -- Hanlon's Razor