Path: utzoo!attcan!uunet!snorkelwacker!think!yale!ox.com!oxtrap!sendai!rich
From: rich@sendai.sendai.ann-arbor.mi.us (K. Richard Magill)
Newsgroups: comp.sys.isis
Subject: Re: isis start up probs on SUN4
Message-ID: <RICH.90Mar2133250@sendai.sendai.ann-arbor.mi.us>
Date: 2 Mar 90 18:32:50 GMT
References: <1200@swbatl.UUCP> <37894@cornell.UUCP>
	<TC.90Mar1134550@oxtrap.aa.ox.com> <38015@cornell.UUCP>
Sender: rich@sendai.UUCP
Reply-To: rich@sendai.ann-arbor.mi.us
Organization: Digital Works, Ltd. - Ann Arbor, MI
Lines: 13
In-reply-to: ken@gvax.cs.cornell.edu's message of 2 Mar 90 01:22:17 GMT

In article <38015@cornell.UUCP> ken@gvax.cs.cornell.edu (Ken Birman) writes:

   We'll give some thought to improving our logging facility, although
   not in time for the V2.0 beta release.

I've actually been toying with the idea of an isis based syslog
replacement.  ie, I'd like my applications to do something very much
like syslog logging but without resorting to tcp communications.  I'd
also like to be potentially able to log all error/status messages from
a distributed application in a common log file.

'spose this would be a useful approach?  Could it be used for isis
system logging?