1 |
On Tue, October 18, 2005 7:03 pm, Michael Kjorling wrote: |
2 |
> So they say, but I'd be careful with running ntpdate from a cron job. |
3 |
> I recall a recent discussion (think it was on linux@×××××××××××.com, |
4 |
> but could be wrong) where one person was having real trouble because |
5 |
> of it resetting the system clock. When he converted to running ntpd |
6 |
> instead, the problem disappeared. |
7 |
> |
8 |
|
9 |
Hmm, my guess (somewhat educated) is that ntpdate is abruptly changing the |
10 |
clock, while ntpd normally just slews the clock by adjusting the timer |
11 |
settings. This means that every second on the clock still ticks with |
12 |
ntpd, but not with ntpdate. That probably has a big impact on anything |
13 |
that uses real-time-clock scheduling - especially if you're running |
14 |
ntpdate once a minute or something like that. |
15 |
|
16 |
I'm not sure how multimedia works in linux - it may not use the system |
17 |
clock for timing. If it did I could definintely see issues happening if |
18 |
buffers run out or if video/audio get out of sync. |
19 |
|
20 |
I personally just let leave the RTC on GMT and run ntpd. It is mostly |
21 |
fire-and-forget. As others have pointed out though, it doesn't handle |
22 |
clock slews this large easily (maybe there is a parameter or |
23 |
source-code-constant that can be tweaked to compensate). |
24 |
-- |
25 |
gentoo-amd64@g.o mailing list |