[ntp:hackers] 1. ntpd's sync state (Harlan Stenn)
mayer at ntp.isc.org
Sun Jun 1 02:21:32 UTC 2008
What should such a log file contain? If you can define it we can
implement it. However I don't see how it can be made automatic since you
need to have a directory to write to and that's not such a simple
question especially with embedded systems. The only file that's written
by default as far as I'm aware is the drift file.
Judah Levine wrote:
> Sure. There are lots of way of doing it with the existing software. The
> trouble is that they are not used in the real world, especially in financial
> and commercial servers, where the data may be needed in a future
> adversary proceeding. My suggestion was to link the capability into a
> relatively simple and small log file that was turned on by default. This
> is particularly important for many of the commercial NTP-only boxes
> that are sold by various companies. The user is usually unable to
> change the internal firmware on these systems and the log files are
> either turned off completely or inadequate.
> Best wishes,
> Judah Levine
>>>> There is a need to be able to easily and consistently determine if
>>>> system clock and/or ntpd's idea of its internal state and the system
>>>> clock are "correct" (for some definition of correct).
>> Isn't this exactly what the ntp_gettime() systemcall is for ?
>> The ntp_gettime() function provides the time, maximum error (sync dis-
>> tance) and estimated error (dispersion) to client user application pro-
>> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
>> phk at FreeBSD.ORG | TCP/IP since RFC 956
>> FreeBSD committer | BSD since 4.3-tahoe
>> Never attribute to malice what can adequately be explained by incompetence.
> Judah Levine
> Time and Frequency Division
> NIST Boulder
> hackers mailing list
> hackers at lists.ntp.org
More information about the hackers