Casey Bralla on 25 Mar 2008 13:55:03 -0700 |
I've got an NTP server setup very much like JP's, but I'm confused by the term "ST2". Could someone define this for me? Like you, JP, I just want it to be within a half second or so. (Actually, I'd **like** it to be within microseconds, but that's because I'm a little anal-retentive <grin>) On Tuesday 25 March 2008 4:37:52 pm Eugene Smiley wrote: > JP Vossen wrote: > > Not "the NTP server" *my* NTP server... > > The/my. We are talking about one and the same. ;) > > > It's just my quick & dirty way of making sure *my local time server* is > > actually synced. I've had issues in the past where it was ST 16 > > (unsynced) for a while, and that's bad. I don't care about 100ms > > accuracy, just as long as it's more-or-less synced. > > I see. I'd recommend being a bit more lenient then. I had a server in the > pool that once got up to ST 5. This means that any clients I had where ST > 6. I doubt it happens very often, though. The big issue is not being ST 16. > That should be your test. > > The question that this leads me to is how many servers do you have in your > ntp.conf? Do you have enough to protect yourself from false tickers? What > would have your NTP go ST 16 besides a downed Internet link? > -- Casey Bralla Chief Nerd in Residence The NerdWorld Organisation ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|