Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!ames!uakari.primate.wisc.edu!samsung!uunet!shelby!SAYSHELL.UMD.EDU!louie
From: louie@SAYSHELL.UMD.EDU ("Louis A. Mamakos")
Newsgroups: comp.protocols.kerberos
Subject: Re: Time Synchronization for IBM VM and MVS System
Message-ID: <9102081743.AA14858@sayshell.umd.edu>
Date: 8 Feb 91 17:43:14 GMT
References: <910208.090843.PST.OPSRJH@UCCVMA>
Sender: news@shelby.stanford.edu (USENET News System)
Organization: Internet-USENET Gateway at Stanford University
Lines: 13


Rather than synchronizing the clock on the IBM system, you can just
provide the "correct" time to the Kerberos related entities on the
system.  Provide a service on the system that can supply "correct"
time, and don't worry about correcting the system's clock.

One possibility is to have a shared segment with the current offset
between the system time and the correct time maintained by an NTP
process.  The offset is not likely to change very rapidly, and this
might be a "cheap" way to supply correct time to cooperating
applications.

louie