[Sorry if this not entirely coherent: it's growing late here.]

On Wednesday 03 April 2013 22:45:11 Mick wrote:

> Do you have chronyc set up to signal off/online status to chronyd? If

> so, where do you run it from?

No, I don't need to bother with manual control: it just works for me. I did play with chronyc years ago but I soon got bored.

I have chronyd running on my LAN server, getting its time from several hosts Out There, then internal hosts get their time from the LAN server. All very straightforward. Any time errors just ramp themselves steadily down to zero. I can show you my config files if you like.

In those old 486/586 days the author used to publish a new version for each new generation of CPU, but I haven't seen that since x86_64 came on the scene. I suppose he must have found another way of calibrating his object code's execution time. Whatever the case, I'm happy that gkrellm etc. show the time to at least the nearest half-second relative to BBC time signals.

I started using chrony in those old dial-up days because it can handle slow links. Also intermittent ones, by which I mean systems that shut down for some of the day, or that dual-boot with Windross,. I haven't felt a need to change since then. At that time ntpd was at a disadvantage IIRC. You might say that chrony is designed for desktop boxes rather than the servers that ntpd likes, though the edges are pretty blurred.

--

Yours, happy camper of Tideswell,

Peter