p.kenn...@fugro.com.au wrote:
> On Feb 6, 7:23 am, Dave Hart wrote:
>> It's running with a patch to lock the main and timer threads to the
>> 2nd CPU using SetThreadAffinity. I haven't tried locking the async I/
>> O thread as well, but I will now. It's also running with a patch to
>> the interp
On Feb 6, 3:25 am, Paul Kennedy wrote:
> Under windows OS, I believe working in the 10's of microsecod range is
> pretty good, and a darn site better than flat NMEA. Terje, can you
> let me know what is bad about this?
That is encouraging to hear. Keep in mind I was deliberately vague in
the ori
On Feb 6, 7:23 am, Dave Hart wrote:
> On Feb 5, 9:33 pm, Terje Mathisen <"terje.mathisen at tmsw.no"> wrote:
>
>
>
> > Dave Hart wrote:
> > > Looking at the last 800 loopstats lines for the refclock, representing
> > > a bit more than 3 hours of 16s polls, the offsets in microseconds look
> > > li
On Feb 5, 9:33 pm, Terje Mathisen <"terje.mathisen at tmsw.no"> wrote:
> Dave Hart wrote:
> > Looking at the last 800 loopstats lines for the refclock, representing
> > a bit more than 3 hours of 16s polls, the offsets in microseconds look
> > like
>
> > -79.497 min
> > -26.961 mean
> > 20.56
Dave Hart wrote:
> After close to a week of calibration, I fudged then flipped off
> noselect on my GPS+PPS refclock in the early minutes of the UTC day.
>
> It looks to me (from my limited perspective of no other local
> refclocks) that I've gone from single-digit milliseconds to double-
> digit
>>> In article ,
>>> narai...@hotmail.com (Gaurav Narain Mathur) writes:
Gaurav> ~ $ ntpq -c "pe" remote refid st t when poll reach delay offset
Gaurav> jitter
Gaurav>
=
Gaurav> = 10.0.0.1 64.247.17.254 3 u 117 128 377 1
>>> In article <7q7r56-9tb@gateway.py.meinberg.de>, Martin Burnicki
>>> writes:
Martin> *only* sends via an unprivileged port if either -q (query only), -u
Martin> (unpriv. port), or -d (debug) is given on the command line.
Harlan> First, given that ntpdate is about to be deprecated in f
On 2009-02-05, balajisun...@midascomm.com wrote:
> Assume PC1 is currently Active and its Network is goes down or
> Shutdown the PC1 then the Floating IP will be host in PC2 and
> respectively
I don't understand this at all. What, exactly, do you mean by "Floating
IP"?
--
Steve Kostecke
NTP P
On Feb 5, 6:00 am, balajisun...@midascomm.com wrote:
> Currently i am using Red Hat 7.2 Linux PC
> I have 3 Red Hat 7.2 Linux PCs for Testing
> I have using 2 Linux PC as Redundant PC
> I have configured floating IP as NTP Server on 3 Linux PCs
> Floating IP is 172.16.0.3
> PC1 IP is 172.16.0.1
>
Hello,
I would like to know if the PPSAPI must implement the optional (by
RFC-2783) function time_pps_kcbind?
I see in the source, that without the function's implementation, the
PPSAPI is not initialized. How does that affect the work with PPS interface
127.0.0.22?
/* /ntpd/refclock_atom.c:
Dear All,
Currently i am using Red Hat 7.2 Linux PC
I have 3 Red Hat 7.2 Linux PCs for Testing
I have using 2 Linux PC as Redundant PC
I have configured floating IP as NTP Server on 3 Linux PCs
Floating IP is 172.16.0.3
PC1 IP is 172.16.0.1
PC2 IP is 172.16.0.2
PC3 IP is 172.16.0.8
I have Written
I have a problem where the NTPd would not sync the time with the
timeserver (10.0.0.1) if minpoll value is 7 and maxpoll is 8. It works
if the minpoll is 4 maxpoll is 5. Can anybody please help me out in
identifying what the problem could be? The "flash" never becomes
"0" I think. Also another h
Hi,
I am currently trying to run the ntp autokey protocol with the Trusted
Certificate identity scheme.
I use 3 systems (serverT1, server2,server3) all running ntp-4.2.4p6 on
windows 2003.
#
1)The stratum 1 system , serverT1 is trusted.
#
ntp.conf of serverT1:
driftfile
Harlan Stenn wrote:
In article , Martin Burnicki
writes:
>
> Martin> By default ntpdate sends and receives packets via port 123/UDP. It
> Martin> *only* sends via an unprivileged port if either -q (query only),
> -u
> Martin> (unpriv. port), or -d (debug) is given on the command line.
After close to a week of calibration, I fudged then flipped off
noselect on my GPS+PPS refclock in the early minutes of the UTC day.
It looks to me (from my limited perspective of no other local
refclocks) that I've gone from single-digit milliseconds to double-
digit microseconds accuracy.
Looki
15 matches
Mail list logo
