Re: ntpd time slewing

2003-09-10 Thread Tom Allison
David Cureton wrote: Tom, I had exactly the same situation. I pulled my hair out trying to find why one machine was operating fine whilst another was dropping time at 4 seconds an hour. I recall that the ntpd on the failing machine was always droping out of sync when the error became to great.

Re: ntpd time slewing

2003-09-10 Thread Steve Lamb
On Thu, 11 Sep 2003 09:32:30 +1000 David Cureton <[EMAIL PROTECTED]> wrote: > This was background work so my debugging process was probably not very > 'scientific' True. To check to see what ntp is doing just use ntpq. [EMAIL PROTECTED]:~} ntpq localhost ntpq> peers remote re

Re: ntpd time slewing

2003-09-10 Thread David Cureton
Tom, I had exactly the same situation. I pulled my hair out trying to find why one machine was operating fine whilst another was dropping time at 4 seconds an hour. I recall that the ntpd on the failing machine was always droping out of sync when the error became to great. I went throu

Re: ntpd time slewing

2003-09-05 Thread John Hasler
Tom Allison writes: > For a simple 'star' topology on private LANs, is there a better solution > for the server than ntpd? You could try Chrony. Note that the default configuration is for a dialup. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE

ntpd time slewing

2003-09-05 Thread Tom Allison
I'm having some trouble getting a server to keep proper time. What's got me at a loss is that this is one of two almost identical machines and the other one is fine, always has been. The only difference I can see in the configurations are the $NTPSERVERS lists. They are different based on thei