> Debian have packages for 'xntp3' and 'chrony' - a friendlier implementation
> of the same sort of thing. These are probably rather too heavyweight for most
> applications, but the chrony daemon is only 90K so if you do need to keep
> reasonably accurate time on a net or occaisionally-connected system this
How do you figure 90k? Out of curiosity I just compiled it on an
ia32 system and the chronyd binary is 382k. Is there some reason why it
would be smaller rather than large on a RISC archetecture? Or are you
refering to the memory footprint?
On the ia32 system in question, both of the chrony binaries
together come to about 523k, all of the various and sundry xntp3 binaries
come to 435k.
And you really only need ntpdate, xntpd, and xntpdc, which comes
out to 336k, again on ia32. And I believe it may be possible to turn off
the files it insists on writing to disk.
So, I'm confused. If the chronyd binary is 60k on arm systems, why
is it more like 340k on an ia32 system?
- Eric
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
