On Sun, Jun 29, 2014 at 12:28 PM, Ken Schneider - openSUSE <suse-list3@bout-tyme.net> wrote:
I truly do not understand the reason all of the computers need to be set to the "same exact" time. :-) A time sensitive protocol like Kerberos usually starts to exhibit problems when the time on the KDC and client differs by approximately five minutes.
Therefore, I think we could all live with a half second discrepancy.
Now to return to the subject, I would like to mention that if your hardware clock has an error of only 0.001% due to temperature or a poorly designed circuit, your clock will be off by a second a day. I'd just check over the motherboard for blown capacitors if you have time, I've seen clocks run oddly when electrolytics fail and increase their ESR. My main computer has a new mom board. My notebook is over 2.5 years
On 06/29/2014 04:01 PM, Brandon Vincent wrote: old. Both show the same discrepancy.
KDE also has a long history of problems with the clock applet. I'd be curious to see a comparsion with a problem like xclock with the -digital or -d flags.
Xclock in digital mode shows only the time when it was started. It does not advance, so you have no idea how accurate it is. There used to be kclock, but that's long gone. I was looking in software management for a suitable clock, but none were listed. Suggestions? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org