Re: Suggested clockspeed/taiclockd invocation at boot
"Mariano Absatz" <[email protected]> Mon, 02 Dec 2002 19:25:14 -0300
| Newsgroups | gmane.comp.lib.libtai |
|---|---|
| Organization | Pert Consultores |
| Message-ID | <3DEBB39A.13440.14FB51EE@localhost> |
El 2 Dec 2002 a las 16:30, Paul Jarc escribió: > "Mariano Absatz" <[email protected]> wrote: > > If you want to "periodically correct clockspeed's knowledge of that > > skew" you should put a > > taiclock `dnsip my.taiclockd.server` |clockadd > > inside your crontab or similar... > > No. Do not run clockadd (or date -s, or equivalent) while clockspeed > is running. clockspeed will not know about, and will eventually > override, those changes. Write the adjustments to > /usr/local/clockspeed/adjust instead. > > > paul You're right... my crontab entry is more like: taiclock `dnsip my.taiclockd.server` >/usr/local/clockspeed/adjust In fact one minute _before_ this I have an entry like: taiclock `dnsip my.taiclockd.server` | clockview >> /var/log/clockskew.log to see how good, or rather, how _BAD_ the clock is working... I have one machine that's been up & running for a week or so and adjusts daily from another one (that has a much more decent clock)... I've seen differences ranging from 1 to almost 5 seconds (1 beeing the "normal" difference)... this is with clockspeed running.