NTP issue - time drifting, ntpd crashing?
in [Slackware]
|
Prev: Driver for Buffalo LPC PCM CLX
Next: Apple iPod
From: Felix Rawlings on 14 Jan 2006 11:49 On Sat, 14 Jan 2006 16:43:08 +1100, Grant wrote: > On Sat, 14 Jan 2006 15:50:29 +1100, Logical <me(a)privacy.net> wrote: > >>Been fiddling with ntpd on my slackware 10.0 box for a while now but it >>constantly seems to be freezing and allowing the time to drift >>significantly. >> >>root[at]mythtv:/home/mythtv# uname -a Linux mythtv 2.6.12.3-mythtv #3 Tue >>Jul 26 23:03:30 EST 2005 i686 unknown unknown GNU/Linux > > That's a very old kernel :( As of 01/14/06, a 2.6.12.3 kernel is very old? Are you serious?
From: Loki Harfagr on 14 Jan 2006 12:32 Le Sat, 14 Jan 2006 16:49:14 +0000, Felix Rawlings a ?crit?: >>>root[at]mythtv:/home/mythtv# uname -a Linux mythtv 2.6.12.3-mythtv #3 Tue >>>Jul 26 23:03:30 EST 2005 i686 unknown unknown GNU/Linux >> >> That's a very old kernel :( > > As of 01/14/06, a 2.6.12.3 kernel is very old? Are you serious? I think he is :-) 6 or 7 months are quite a long time for a still evolving kernel and, depending on your hardware, many issues -- especially related to time and latency -- were noted and worked on. Besides, Grant would probably think that my 2.6.14 is quite old, and that'd be correct for a developer :-) That's one of the diffs in the IT world, you have lusers, users, keen users, part time developers and real programers, they tend to have different views on the sharpness of time scaling ;-) Back on 'Logical' topic, what do you use ntpd for ? Do you really need it ? In case you're just on your personal desktop you'd be easier with 'ntpdate'. Now if it is for a server and you mean to drive an ntp tier 2 or 3 for your LAN that's different but then you'll have to struggle a bit with the docs, ntp is a sharp mistress :-) Do you have the same time drifting experience with a stable 2.4.* kernel ? Did you build your ntp yourself or was it a package ? You may check that the glibs used for your kernel and ntp are of the same family. You may scan your logs to find if anything funny happened, hardware or leakage. And I have had several issues with ntpd in different setups after some upgrade, like kernel, glib, use or realtime or not. Many running Perl daemons (e.g. a spamfilter) tend to make ntpd a zombie (I don't have explaination on this, that's just an observation :-) In your situation I'd first try and test your ntpd config on another machine/kernel/installation, so as to get a clue on what direction to investigate.
From: Grant on 14 Jan 2006 14:57 On Sat, 14 Jan 2006 16:49:14 GMT, Felix Rawlings <fraw(a)yahoo.com> wrote: >On Sat, 14 Jan 2006 16:43:08 +1100, Grant wrote: > >> On Sat, 14 Jan 2006 15:50:29 +1100, Logical <me(a)privacy.net> wrote: >> >>>root[at]mythtv:/home/mythtv# uname -a Linux mythtv 2.6.12.3-mythtv #3 Tue >>>Jul 26 23:03:30 EST 2005 i686 unknown unknown GNU/Linux >> >> That's a very old kernel :( > > As of 01/14/06, a 2.6.12.3 kernel is very old? Are you serious? Six months old, current stable is 2.6.14.6 or 2.6.15 for the adventurous, the first stable bugfix for 2.6.15.1 be out very soon. Grant. -- Cats are smarter than dogs. You can't make eight cats pull a sled through the snow.
From: Logical on 14 Jan 2006 21:47 Loki Harfagr wrote: > Back on 'Logical' topic, what do you use ntpd for ? > Do you really need it ? > In case you're just on your personal desktop you'd be easier with > 'ntpdate'. Now if it is for a server and you mean to drive an ntp > tier 2 or 3 for your LAN that's different but then you'll have to struggle > a bit with the docs, ntp is a sharp mistress :-) The PC is a MythTV frontend/backend for watching digital TV and use as a PVR (personal video recorder). Once the time drifts the recordings it makes based on it's TV schedule become out of whack. I was reading up on using ntpdate in a crontab script but most articles say to avoid it (being the easy way out?) > Do you have the same time drifting experience with a stable 2.4.* kernel ? I rarely use the 2.4 kernel, and never used ntpd on anything I had with it. > Did you build your ntp yourself or was it a package ? It would have been the slackware package, grabbed either through the installation CDs or upgraded through swaret afterwards, I forget which one I used. root(a)mythtv:/etc# ntpd --version ntpd: ntpd 4.2.0(a)1.1161-r Mon Mar 29 22:23:49 PST 2004 (1)
From: Chu Mai Fat on 16 Jan 2006 08:11
Grant wrote: > > Six months old, current stable is 2.6.14.6 or 2.6.15 for the adventurous, > the first stable bugfix for 2.6.15.1 be out very soon. > Grant If we assume that 2.6.12.3 kernel was a "current" and "stable" kernel six months ago, why would it need to be updated now? I was under the impression that odd numbered kernels, ie 2.1.x, 2.3.x and 2.5.x were development kernels and should be updated but that even numbered kernels were considered stable and if they contained all the needed functionality then they were suitable and sufficient for general use. Seems to me that this continuous necessity to upgrade is far worse than the much maligned Windows model of regularly releasing security fixes and patches. Regards Chu |