> Personally, I've looked at the TAI library with interest but I've never > seen a good reason to move away from xntpd for time synchronization. If you want your system to tick TAI, clockspeed is the only game in town. > I find it convenient to have xntpd take care of > handling changing system clock drift for me (and I have a few machines > that don't have consistent clock drift), I have some prototype code to handle this. It's a bit kludgy, but it seems to work well enough on 50+ machines here. But in general you're right: xntpd is time synchronization for the masses; clockspeed (as yet) is only for those who like playing with their toys, or have serious religious objections to UTC. Tim (who scores on both counts :-).
- [OT] Achieving Time-Synch at mailserver martin langhoff
- Re: [OT] Achieving Time-Synch at mailserver James Raftery
- Re: [OT] Achieving Time-Synch at mailser... Peter van Dijk
- Re: [OT] Achieving Time-Synch at mai... Chris Garrigues
- Re: [OT] Achieving Time-Synch at mai... James Raftery
- Re: [OT] Achieving Time-Synch at... Peter van Dijk
- Re: [OT] Achieving Time-Synch at mai... Russ Allbery
- Re: [OT] Achieving Time-Synch at mailserver Chris Johnson
- Re: [OT] Achieving Time-Synch at mailser... Daniel Augusto Fernandes
- Re: [OT] Achieving Time-Synch at mai... Russ Allbery
- Re: [OT] Achieving Time-Synch at... Tim Goodwin
- Re: [OT] Achieving Time-Synch at mailserver Aaron L. Meehan
- RE: [OT] Achieving Time-Synch at mailserver Ihnen, David
