Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think!yale!ox.com!oxtrap!oxtrap!tc From: tc@oxtrap.aa.ox.com (Tse Chih Chao) Newsgroups: comp.sys.isis Subject: Re: isis start up probs on SUN4 Message-ID: Date: 2 Mar 90 15:52:25 GMT References: <1200@swbatl.UUCP> <37894@cornell.UUCP> <38015@cornell.UUCP> Sender: tc@oxtrap.aa.ox.com (Tse Chih Chao) Organization: Ocwen Trading Inc. - Ann Arbor, MI Lines: 20 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: I have never seen this on a non-Ultrix system, or on Ultrix on anything but the 3100 workstation. To be more specific: This problem only occurs on Ultrix on a DECstation 3100 which runs the name server and news. And, protos logs do include timestamps. If a message is logged after a delay of more than 1 minute since the prior message, there will always be a line "... time is now xx:xx:xx". We'll give some thought to improving our logging facility, although not in time for the V2.0 beta release. My mistake. Protos logs do have timestamps. I was talking about the monitor's logs. Tse Chih