[ntp:questions] Re: ntpd transmit timestamp precision

Damion de Soto damion at cyberguard.com.au
Wed Feb 15 07:08:12 UTC 2006

David L. Mills wrote:
> Damion,
> Please don't copy my presonal mailbox with postings to this list. I 
> routinely throw them away without reading.

> See ntp-dev/libntp/systime.c line 85.
ahh, this is only the beta and dev versions.
I've been playing with the 4.2.0 production version and sometimes I get fuzz, 
sometimes I don't - so i guess it's just magic CPU fuzz.

Using 4.2.0b and manually forcing HAVE_CLOCK_GETTIME off gives me the correct 
randomization of the low bits.

Which then takes us back to the semi-original problem.

Should the ntp_random() function be applied to the result of clock_gettime() and 
getclock() ?

In my situation I would say yes - I can't see why it shouldn't always fuzz it.

Do any of the developers read this group, or should I submit a bug/patch some other way?

  | Damion de Soto --------------------------------------------------
  | Software Engineer   email:  Damion_deSoto at au.securecomputing.com
  | Secure Computing Corporation web: http://www.securecomputing.com
  | fax:        +61 7 3891 3630   ph:                +61 7 3435 2809
  ----  Free Embedded Linux Distro at  http://www.snapgear.org  ----

More information about the questions mailing list