Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!cornell!ken
From: ken@gvax.cs.cornell.edu (Ken Birman)
Newsgroups: comp.sys.isis
Subject: Re: isis start up probs on SUN4
Message-ID: <38053@cornell.UUCP>
Date: 2 Mar 90 20:32:12 GMT
References: <1200@swbatl.UUCP> <37894@cornell.UUCP> <TC.90Mar1134550@oxtrap.aa.ox.com> <38015@cornell.UUCP> <RICH.90Mar2133250@sendai.sendai.ann-arbor.mi.us>
Sender: nobody@cornell.UUCP
Reply-To: ken@gvax.cs.cornell.edu (Ken Birman)
Organization: Cornell Univ. CS Dept, Ithaca NY
Lines: 11

In article <RICH.90Mar2133250@sendai.sendai.ann-arbor.mi.us> rich@sendai.ann-arbor.mi.us writes:
>I've actually been toying with the idea of an isis based syslog...
>'spose this would be a useful approach?  Could it be used for isis
>system logging?

Sounds like what I had in mind, and I guess this makes more sense
than sending messages to a system console (those of you who run ISIS
at boot time presumably know what is bothering me...) If you do this,
let us know.  Maybe we can make it standard.

Ken