<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Maybe they're relying on ntpdate in a cronjob at midnight.<br>
<br>
Dan Young wrote:
<blockquote
cite="mid:994441ae0911051348m16981bb1q1d62fb5029160f2f@mail.gmail.com"
type="cite">
<pre wrap="">On Thu, Nov 5, 2009 at 1:03 PM, Peter Beckman <a class="moz-txt-link-rfc2396E" href="mailto:beckman@angryox.com"><beckman@angryox.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> 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.
</pre>
</blockquote>
<pre wrap=""><!---->
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 <a class="moz-txt-link-rfc2396E" href="mailto:dyoung@mesd.k12.or.us"><dyoung@mesd.k12.or.us></a>
Multnomah ESD - Technology Services
503-257-1562
_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
</body>
</html>