Hello:
I built a NAS out of an older model, but new, Super Micro mobo ($140),
an older model Intel CPU ($15), good ECC memory ($100), and FreeNAS built on
FreeBSD. The NAS only uses about 40 Watts, so it is not expensive to run.
As luck would have it, FreeNAS came with NTPD built
Hello,
I'm trying to set up an NTP server on an RHEL 6.1.
Synchronization via *ntpdate *seems to work fine and apparently everything
works OK seing it as a *client*, however, the server itself its not
working, it shows a *stratum* of 16 and never decreases.
My */etc/ntp.conf *is as follows:
This performance is marginal for WSJTX. I need 10ms offset or less after
15 minutes.
One more time, this is what I have done to achieve sub-millisecond
accuracy (currently 0.092 offset and 0.033 jitter):
Make sure you are using a recent version of NTPD; I am using ntpd
If the reach is not 377, have you used WireShark or another TCP/IP
monitoring program to find out what is happening to the NTP packets? It is
not all hard to use.
-Original Message-
From: questions-bounces+elliott.ch=comcast@lists.ntp.org
Hi,
I just installed ntp on my Win 7 pc where it runs perfectly the
difference is around 0,5 sec.
Then I installed ntp on my 2008 R 2vps where the delay gets bigger and
bigger, around 12 sec per 30 min ??
For both installations I used more or less the default suggestion of ntp.
Is anybody
Hello
I have NTP server with Ublox LEA-6T GPS receiver. I want to determine my
server's oscillator accuracy and stability. I've read about Allan deviation
and learnt how to make ADEV plot, but I don't fully understand how to
use this method.
My question is: what method should I use to determine
I'm looking for information on best practices to configure ntp for a medium
sized network. I'm looking for something similar to the whitepapers
published by Cisco. Cisco outlines several configurations with a mixture
of peer and server definitions for a set of internal ntp servers.
Equally
Hi,
Our system uses NTP package version 4.2.6 (Linux CentOS 6.5). Due to
system constraints, we have configured the ntpd to update the clock only
using slewing.
At some point, one of our system's clock's was ahead by 20 minutes, and
we noticed what appears to be a faulty output from the ntpq
Hello,
We are running the above release. It works great until the interface for the
default route is
brought down and then back up. Then after a half hour or so it ntpstat starts
returning
synchronised to unspecified at stratum 4
time correct to within 1149 ms
polling server every 64 s
On 08/27/2014 08:46 PM, David Lord wrote:
Mike S wrote:
On 8/27/2014 5:48 AM, valizade...@gmail.com wrote:
I not sure, how should I write the ntp.conf file to achieve the
maximum accuracy using pps.
i don't know if the ntpd use the pps or not in my case!
Sometimes it is recognized as a
Hello,
This email is regarding NTP time synchronization issue that we see in our linux
embedded systems.
NTP version that is being used: 4.2.6p4.
Brief description about issue:
Our linux system is configured with NTP running 4.2.6.p4. After couple of weeks
the system clock has local time ahead
On Wed, Aug 27, 2014 at 4:44 PM, juergen perlinger
juergen.perlin...@t-online.de wrote:
The basic problem is that using a PPS clock and a GPS(NMEA) clock
separates what belongs together
This is not true. Normally I wouldn't fall prey to there's something
wrong on the Internet but this
Charles Elliott writes:
It is possible to distribute more accurate and stable time using a local GPS
device, either home built (e.g.,
http://www.satsignal.eu/raspberry-pi/index.html) or purchased (e.g.,
http://www.meinberg-usa.com/products/network-time-server.htm), but the
original cost is
13 matches
Mail list logo
