David Bustos wrote: >Quoth Nicolas Williams on Mon, Aug 27, 2007 at 05:03:29PM -0500: > > >>Instead we might have applications that want to have a dependency on >>time being within N microseconds of UTC (e.g., I'd want the KDC services >>to have a dependency of less than 2e6 us of UTC, while a satellite >>tracking application might want much, much more accurate time). >> >>So even my suggestion of marking the service degraded when the clock is >>out of sync (i.e., when the estimated offset to UTC is indeterminate or >>past some arbitrary cutoff). >> >>I'd like SMF to be able to represent such analog dependencies. >> >> > >How about we make the NTP daemon capable of answering requests about >clock accuracy and have the NTP service come online as soon as it is >able to answer such queries, and have time-sensitive services decline to >provide functionality and mark themselves degraded until the NTP daemon >says the clock is sufficiently accurate? > >
Will the changes to ntpd be offered back to www.ntp.org? Darren
