home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!sdd.hp.com!spool.mu.edu!agate!ucbvax!DIKU.DK!thorinn
- From: thorinn@DIKU.DK
- Newsgroups: comp.protocols.time.ntp
- Subject: XNTP3/MIPS RISCos 5.01 solved (ish)
- Message-ID: <9301261100.AA13939@tyr.diku.dk>
- Date: 26 Jan 93 11:00:30 GMT
- References: <9301251646.AA07785@cgin.cto.citicorp.com>
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: inet
- Organization: The Internet
- Lines: 10
-
- Philip,
-
- thanks for the explanation. Anyway, as Alan pointed out, it can't be
- the SETTIMEOFDAY_DAMAGED code that causes his problem.
-
- It still looks to me as if, somehow, the system clock jumped one
- second backwards. Possibly the new RISC/os clock code is not robust in
- the face of multiple adjtime calls.
-
- Lars Mathiesen (U of Copenhagen CS Dep) <thorinn@diku.dk> (Humour NOT marked)
-