[VoiceOps] DST handling

[Lee Riemer]

Maybe they're relying on ntpdate in a cronjob at midnight.

Dan Young wrote:
> On Thu, Nov 5, 2009 at 1:03 PM, Peter Beckman <beckman at angryox.com> wrote:
>   
>>  In discussing time, one of my providers avoids syncing their servers to
>>  the correct time on an ongoing basis (i.e. with ntpd), with the argument
>>  that if they sync during calls, billing would be wrong.  Some of there
>>  servers therefore skew a LOT, and sometimes their call servers can be off
>>  the real time by _HOURS_ (I suspect this is due to running Asterisk on VMs
>>  which are notoriously bad at keeping time).  I've griped about it, but
>>  they say they only sync the time when there are no calls at midnight,
>>  which never happens.
>>     
>
> I'm sure this isn't news to you, but... By default, ntpd will not snap
> to a new time, but rather slew slowly towards the correct time.
>
> How slowly? man 8 ntpd:
> "about 2,000 s for each second the clock is outside the acceptable range."
>
> --
> Dan Young <dyoung at mesd.k12.or.us>
> Multnomah ESD - Technology Services
> 503-257-1562
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20091105/1fc98c58/attachment.html>