Hal Murray wrote:
> In article
> <884d589f-378f-4568-a641-003c6bea9...@d12g2000vbr.googlegroups.com>,
> pc writes:
>>The Motorola Oncore UT GPS receiver, which was designed as a precision
>>time source, has a T-RAIM (time receiver autonomous integrity
>>monitoring)
>>feature which, properly con
unruh wrote:
>> That of course could happen, but the scenario requires some really
>> convenient failure in the GPS unit. If the GPS lock is lost, at least
>> the GPS units I have tested will indicate their clock is freewheeling.
>> The time is then discarded by gpsd as invalid and will not be fed
unruh wrote:
> On 2010-06-01, Rob wrote:
>> unruh wrote:
>>>> If we assume there is a private subnet that has two GPS reference
>>>> clocks to synchronize the rest of the machines, what would be the
>>>> expected failure mode where one of the stra
unruh wrote:
>> If we assume there is a private subnet that has two GPS reference
>> clocks to synchronize the rest of the machines, what would be the
>> expected failure mode where one of the stratum 1 servers go crazy, and
>> having three GPS clocks actually makes a difference?
>
> The gps falls
Terje Mathisen <"terje.mathisen at tmsw.no"> wrote:
> Going from YMDHMS to unix (or ntp) seconds is really quite trivial,
> while the opposite direction is much harder!
>
> My most efficient algorithm for the reverse function needs somewhere
> between 30 and 50 clock cycles (compare with 40 cycle
Garrett Wollman wrote:
> IEEE Std.1003.1-2001 (the only version I have conveniently to hand)
> supplies the following definition of "Seconds Since the Epoch":
>
> tm_sec + tm_min*60 + tm_hour*3600 + tm_yday*86400 +
> (tm_year-70)*31536000 + ((tm_year-69)/4)*86400 -
> ((tm
unruh wrote:
>> Maybe the chrony people should have started with a fork from ntpd.
>> Then I would probably be using it now.
>
> I doubt it. chrony was largely written by one person, Richard Curnow.
> His philosophy on how to control clocks was completely different from
> Mill's and has been shown
Richard B. Gilbert wrote:
> Rob wrote:
>> Richard B. Gilbert wrote:
>>> Please feel free to design your own algorithms to deal with the "systems
>>> not running 24h/day" and, while you're at it, deal with temperature
>>> variations and supp
John Hasler wrote:
> Rob writes:
>> I think ntpd has a good number of features and advantages...
>
> Why not add those features and advantages to Chrony?
Because I have good experience with ntpd.
>> ...I only wonder why nobody has yet decided to take the code and
>&
John Hasler wrote:
> Rob writes:
>> I don't feel free to design those because I can anticipate that the
>> changes will be rejected and will not go into the distribution
>> version.
>
> Then use and contribute to Chrony. We welcome contributions. Why
> con
Richard B. Gilbert wrote:
> Please feel free to design your own algorithms to deal with the "systems
> not running 24h/day" and, while you're at it, deal with temperature
> variations and support drift rates up to 5,000 PPM, etc, etc.
I don't feel free to design those because I can anticipate t
Richard B. Gilbert wrote:
> The clock CHIP is not the problem. The problem is that the quartz
> crystal that provides the "tick" is usually one that failed quality
> control at a wristwatch factory.
The issue under discussion is not the accuracy of the clock, but the
"fact" that it does not pr
Andy Helten wrote:
>
> Rob wrote:
>> Kalle Pokki wrote:
>>
>>> Yes, but reference clock drivers don't use the ntp timestamp. Take a
>>> look at e.g. the SHM driver. There
>>>
>>
>> Is this piece of code something that our fri
Kalle Pokki wrote:
> Yes, but reference clock drivers don't use the ntp timestamp. Take a
> look at e.g. the SHM driver. There
Is this piece of code something that our friend does not want to change
because he believes it is doing the right thing? Or is it merely badly
written by a contributor a
Movis wrote:
> Hello,
>
> For reasons outside my control, I wish to configure ntpd on Red Hat to
> use as the refclock a time obtained by repeatedly telnetting to a
> remote machine and using the "date" command.
>
> In other words, I will have a string from a script which would then be
> given to
Terje Mathisen <"terje.mathisen at tmsw.no"> wrote:
> Ryan Malayter wrote:
>> It's from VMware, but I imagine the basics apply to Xen, Hyper-V, and
>> other virtualization solutions:
>> http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=1006427
>
> Very nice indeed, I wa
Hal Murray wrote:
>
>>The serial chip does not do that. It will send the interrupt at the
>>time it has assembled a full character.
>
> Some of the serial chips have large FIFOs and wait until the FIFO
> has several characters and/or there is no activity for a while.
> The idea is to save CPU cyc
unruh wrote:
> I think that depends on how you set up the chip. I think you can set it
> up so it will interrupt on each byte. This is not terribly efficient for
> a serial port driver, but if it is timing you want, then that is
> probably what you want.
It will give you little more than a warm f
John Hasler wrote:
> Terje writes:
>> It would still be limited to the resolution of the rs232 clock,
>> i.e. ~1ms, instead of the ~1us we usually get from PPS receivers.
>
> The documentation claims 1us (again, that just what I read. I don't
> have one.) The RS232 could be synchronized to the P
Uwe Klein wrote:
> nemo_outis wrote:
>> It is frequently the case that OPs (for a variety of reasons) misstate or
>> mispecify their problem or overconstrain its solution (either in terms of
>> what can or must be done or what can't or mustn't). I submit that the
>> current OP is a classic cas
John Hasler wrote:
> Richard B. Gilbert writes:
>> With a closed network the options are limited. With a place to site a
>> GPS antenna, you can install a GPS clock that will be accurate to
>> within +/- 50 nanoseconds.
>
> It occurs to me that the sort of fancy GPS that an oceanographic ship is
lhommedumatch wrote:
> Hi,
>
> Some news:
> remote refid st t when poll reach delay
> offset jitter
> ==
> *ntpgmtaceb .1PPS. 1 u 734 1024 377 29.779
> 1.182 0.228
>
> So still t
nemo_outis wrote:
> True, one can chase any number of will-o-the-wisps such as the causes of
> the network latency and asymmetry, but that is not the central problem
> posed by the OP.
But it is!
> In short, Unruh may be boring in his reiteration of his simple GPS
> solution, but that is beca
unruh wrote:
> Of course. That is the thing about solutions. You provide extra
> information or hardware that is needed to impliment the solution. Now if
> you have a better one, I am sure he would welcome it. But I have not
> seen it.
In his position, I would investigate the cause of the delay.
David J Taylor wrote:
> "Rob" wrote in message
> []
>> Ok, that is good.
>> When you get an openSUSE 11.2 DVD you can install a system and configure
>> NTP on it using only the GUI, no need to edit any files.
>
> .. what, even if I want to add a
unruh wrote:
> That may be what he wants, but it is not what he asked for. He stated
> that he was using an external source as his ntp server, and wanted his
> machine to be within a ms of it. That is a job admirably suited to a GPS
> receiver. He then stated that this was on an oceanographic vess
David J Taylor wrote:
> "Rob" wrote in message []
>> It probably uses Emacs-style key bindings. That can be very frustrated
>> for users that are not familiar with Emacs. I remember trying to
>> install
>> some Linux distribution, I think it was debian, a
David J Taylor wrote:
>> It took a couple of days just to get FreeBSD V8.0 installed correctly in
>> the first place. One false move (hair trigger enter key) and it's
>> "start over" time. (OK, so there are probably ways to backtrack, but
>> like many things, it's just not documented.)
>
> Agree
unruh wrote:
> On 2010-04-13, lhommedumatch wrote:
>> On 13 avr, 00:48, unruh wrote:
>>> On 2010-04-12, lhommedumatch wrote:
>>>
>>> > I'm working on a oceanographic vessel
>>> > ntpgmtaceb is our reference clock that is synchronised with a gps at
>>> > the beginning of a cruise.
>>>
>>> Why no
David J Taylor wrote:
> "Todd Glassey" wrote in message
> news:4bc31c47.1000...@glassey.com...
> []
>> I want to know about non ECC memory based PC's running NTP and how many
>> NTP errors are caused by single and multi-bit memory errors.
>>
>> Todd
>
> I am not aware of any. I rather imagine t
Maarten Wiltink wrote:
> Do VMs still have problems responding to timer ticks when there are
> enough cores to go around?
If anything, the problems tend to get worse when you have many cores.
I am trying to get everything working in a VM environment right now,
and I have many different versions
David J Taylor wrote:
>> It can also be difficult to buy items from suppliers with no existing
>> relationship. I.e. it may be easy to buy new computers or supplies, but
>> difficult to get a GPS receiver from some online shop.
>> E.g. where I work it is not possible to buy anything from a shop w
David Woolley wrote:
> unruh wrote:
>
>> I am sorry, but getting an authoritative time source is trivial. A
>> GPS18x is cheap ( a lot less than you have spent on your salary in these
>> postings) reliable and easy. If they do not need the microsecond
>
> In many business environments it can be re
Richard B. Gilbert wrote:
> Rob wrote:
>> Richard B. Gilbert wrote:
>>> The easiest thing to do if you can site an antenna where it will have an
>>> unobstructed view of the sky, is to purchase a "hardware reference
>>> clock". The cheapest go
Richard B. Gilbert wrote:
> The easiest thing to do if you can site an antenna where it will have an
> unobstructed view of the sky, is to purchase a "hardware reference
> clock". The cheapest goes for about $100 US. It's called a GPS18-LVC
> if memory serves me. If my memory fails me I'm
Yan Seiner wrote:
>> Ah, that looks wrong. The SHM(0) PPS should be GPS and the SHM(1) should
>> be GPS1. The rewfid is how the client and server of the shm find each
>> other.
That must be new... AFAIK the refid is not even in the SHM segment,
it is configured in ntpd but not known to gpsd.
_
Kelsey Cummings wrote:
> Rob wrote:
>> This is normal with NMEA. You never will get stable time when using
>> an NMEA time source. For that, you need PPS. Your PPS is apparently
>> not working.
>
> It feels like I must be missing something here, running with -
Yan Seiner wrote:
> I'm struggling to get ntpd and gpsd 2.90 to play nice. The API to gpsd
> has changed, and I can't figure out how to get ntpd to talk to it.
Are you running 32-bit executables (gpsd or ntpd) on a 64-bit system?
___
questions mailin
Kelsey Cummings wrote:
> Hal Murray wrote:
>> How about turning off the PPS fudge flag so you know you are
>> using the text mode. Then watch it for a while and add a
>> fudge time2 to get it reasonably close. When that works,
>> turn the PPS back on.
>
> I added time2 to zero out the offset and
unruh wrote:
> On 2010-02-16, Rob wrote:
>> unruh wrote:
>>> Now, I am not sure whether gpsd will run on bsd, but I suspect it should
>>> not be hard to convert it to do so. The ioctl calls to the serial port
>>> or parallel port may well be different, but t
David Lord wrote:
> David Woolley wrote:
>> David Lord wrote:
>>>
>>> Systems seem heavily overloaded.
>>>
>>> My 3G mobile broadband has seconds of latency whilst initiating
>>> connections, that is how the system works, maybe 10 seconds, but
>>
>> That's likely to be result of the power managem
unruh wrote:
> Now, I am not sure whether gpsd will run on bsd, but I suspect it should
> not be hard to convert it to do so. The ioctl calls to the serial port
> or parallel port may well be different, but there are very few of them
> in the code.
There may be few of them, but one is very essen
unruh wrote:
>> That might be a Linux specific feature of gpsd.
>>
>> Man page mentions Linux version of gpsd detecting PPS on
>> serial DCD line otherwise best accuracy around 10ms.
>
> There is also the shmpps program, which detects pps either on the serial
> or the parallel port and uses the sh
unruh wrote:
> ["Followup-To:" header set to comp.protocols.time.ntp.]
> On 2010-02-12, Rob wrote:
>> Jonathan de Boyne Pollard wrote:
>>>
>>>>
>>>>
>>>> We use our one of our data centers internal default gateway (Router).
&g
Jonathan de Boyne Pollard wrote:
>
>>
>>
>> We use our one of our data centers internal default gateway (Router).
>> Everything feeds off of that.
>> It had best work well. It was $100K +.
>>
> So what benefit is that $100K extra stratum gaining you? It has to be
> more than just splitting the U
Jonathan de Boyne Pollard wrote:
>>
Anyway, most, if not, ALL of them have cheap routers that provide
this functionally without additional cost.
>>> I have a cheap router sitting by my left hand as I type this, and I'm
>>> here to tell you that it doesn't contain an NTP serve
David J Taylor
wrote:
>
> "David Woolley" wrote in message
> news:hkjre8$7b...@news.eternal-september.org...
>> David J Taylor wrote:
>>
>>> OK, I mis-read the table. If the 9 microseconds is the true offset,
>>
>> What do you mean by true offset? That is not actually measurable
>
> As oppose
Danny Mayer wrote:
> Ryan Malayter wrote:
>> On Tue, Jan 19, 2010 at 3:57 PM, Rob wrote:
>>> Compare it with a RAID-1 disk system. Â When one disk has an unreadable
>>> sector, the situation is clear: use the sector from the other disk.
>>> When both disks ar
David Woolley wrote:
> Richard B. Gilbert wrote:
>
>>
>> If I see a notation in code saying, in effect, "can't get here" I add
>> whatever call means "suicide with crash dump" if it's not already
>> present. I don't get many crash dumps but if the impossible happens I
>> like to have it docum
Rob wrote:
> Martin Burnicki wrote:
>>> Is that really correct as even I can tell 0.977 is less than the
>>> "minimun" 1.000 ms" in the previous line?
>>
>> I think 1 ms is just the nominal value and 0.977 is due to rounding errors
>> or an
Martin Burnicki wrote:
>> Is that really correct as even I can tell 0.977 is less than the
>> "minimun" 1.000 ms" in the previous line?
>
> I think 1 ms is just the nominal value and 0.977 is due to rounding errors
> or an inexact measurement interval.
I thought the timer interval was 1/1024 Hz?
David Woolley wrote:
> E-Mail Sent to this address will be added to the BlackLists wrote:
>
>>
>> I can perhaps see idling the connection to keep it open when the
>> poll rate is at ~ 1 minute, however what about when the poll
>> rate decreases to ~ 17 minutes? (or less often if so configured)
Hal Murray wrote:
> The problem is that IF they give wildly different answers
> (perhaps because one of them is broken) THEN you don't know
> which one is good.
As they say here: IF the sky falls down THEN we all have a blue hat.
Compare it with a RAID-1 disk system. When one disk has an unread
Richard B. Gilbert wrote:
> Rob wrote:
>> Richard B. Gilbert wrote:
>>> The fundamental problem with two servers is this: which one do you
>>> believe when the two differ? You know that at least one of the two must
>>> be wrong but it's impossible t
Richard B. Gilbert wrote:
> The fundamental problem with two servers is this: which one do you
> believe when the two differ? You know that at least one of the two must
> be wrong but it's impossible to determine WHICH one!
This is not relevant when the two servers return the same time within
nodata wrote:
> Am 2010-01-14 20:38, schrieb Rob:
>> You could stop ntpd, and then use the adjtimex program to set the
>> clock rate to a slower value, so that the systems will lose time.
>> (using the --tick option)
>> Calculate how long it is going to take to arrive a
You could stop ntpd, and then use the adjtimex program to set the
clock rate to a slower value, so that the systems will lose time.
(using the --tick option)
Calculate how long it is going to take to arrive at the correct time
using the setting you decide on, and then come back to the system
(proba
Richard B. Gilbert wrote:
> Rob wrote:
>> Maynard wrote:
>>> On 1/7/10, the date on our domain controller jumped to 12/7/10, and
>>> was there for about 11 minutes before it reverted back to the current
>>> date. At the time this happened, our NTP server
Maynard wrote:
> On 1/7/10, the date on our domain controller jumped to 12/7/10, and
> was there for about 11 minutes before it reverted back to the current
> date. At the time this happened, our NTP server was pointed to
> pool.ntp.org. We also have a few Novell servers that were pointed to
> t
David Lord wrote:
> I'm pretty sure us accuracy is available at closer range
> since it is possible to sync to exact cycle of carrier
> with period of around 13us, ie to within a fraction of
> that so 1us shouldn't be a problem.
The problem is not in the accuracy of the transmitter or your
capabi
Steve Kostecke wrote:
> On 2009-12-25, Marc-Andre Alpers wrote:
>> Es schrieb Rob:
>>
>>> Be patient. After a while things will stabilize and you can make another
>>> judgement about the accuracy of your offset.
>>
>> I think that's good enoug
Marc-Andre Alpers wrote:
> Es schrieb Rob:
>
>> Get a better set of time references on the network (that a referenced
>> off a GPS or similar clock) and that agree to eachother.
>> With this set, there is no way to tell where you are.
>
> And now?
>
> r
Marc-Andre Alpers wrote:
> Es schrieb David Lord:
>
>> I've fudged the SHM with
>> "fudge 127.127.28.0 time1 0.024550 refid MSFa"
>
> I'm about 400km away from DCF77. What a fudge should I use?
The fudge is determined by the way the clock interfaces to the computer
(via RXS introduces a large del
===
+GENERIC(0) .DCF7. 0 l 61 64 377 0.000 0.151 0.002
Regards
Rob
--
Nowadays people know the price of everything, and the value of nothing
Oscar Wilde
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
--> Brown
The circuit 'expects' NTPD to raise RTS and read from CTS or RI.
As far as I can tell NTPD does raize RTS but does not read from CTS or RI.
Regards,
Rob
--
Nowadays people know the price of everything, and the value of nothing
Oscar Wilde
_
blinks?
Regards,
Rob
--
Nowadays people know the price of everything, and the value of nothing
Oscar Wilde
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
data on RXD.
Maybe you can post a link to the receiver you're using.
Regards,
Rob
--
Nowadays people know the price of everything, and the value of nothing
Oscar Wilde
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/
Hi there
I read that kernel PPS support is now part of vanilla kernels (no patch
required). Since when? Which is the oldest kernel with PPS support?
Regards,
Rob
--
Nowadays people know the price of everything, and the value of nothing
Oscar Wilde
Richard B. Gilbert wrote:
> I've not used them myself; my laptop came equipped with Ethernet and
> RS232-C. If I ever buy another laptop, I will be sure that it has both
> Ethernet and RS232-C interfaces.
Then I would not postpone buying that new laptop for too long...
___
Richard B. Gilbert wrote:
> Certificates cost money! Apparently nobody is willing to pay the
> freight for one. The NTP project is not, AFAIK, funded at anything like
> the level required to purchase a certificate. That's why the "self
> certification"!!!
The money is not the only problem.
Bill Unruh wrote:
> On Sun, 29 Nov 2009, Richard B. Gilbert wrote:
>>>
>> A much oversimplified explanation is that short poll intervals are used to
>> correct large errors quickly and long intervals are to correct small errors
>> very accurately.
>
> That is true if you are refering to rate er
I have a strange problem with NTP in a Cisco 877.
On a couple of locations we have Cisco routers and NTP works "ok"
on them (of course, better NTP software exists). But this one router
won't remain locked.
When I remove the NTP server and add it again, and then look with
"sh ntp as", it looks li
gizero wrote:
> My question is: should I expect to be able to set-up my configuration
> that allow a single NTP server to be defined and, optionally, the GPS,
> when available? Or am I out of the track?
There are many simple devices that allow only a single NTP server to
be configured, so you are
David J Taylor
wrote:
>
> "Unruh" wrote in message
> news:qsbam.47742$db2.29...@edtnps83...
> []
>> Actually those Gb ethernet switches seems to have some really bad and
>> variable
>> latencies. My system, before they installed Gb switches, had a
>> consistant
>> roundtrip of 140 usec and ga
Towli wrote:
> Hello all
>
> By chance i just saw 2 undefined ntp-servers showing up on my 3750 doing a
> "show ntp ass". I have defined 3 internal DCF77 servers and 1
> Gps-Ntp_server.
> The 2 "scavenger" ntp-servers are not mentioned in the running config - how
> on earth can my switches be
David Lord wrote:
> David Lord wrote:
>> David J Taylor wrote:
>>> OT: GPS18x LVC failure
>>>
>>> My GPS18x LVC stopped working a couple of days ago. There appears to
>>> +5V going into the unit, and the serial output is stuck around -5V
>>> with no signs of data on the 'scope. Garmin have acc
Richard B. Gilbert wrote:
> Unruh wrote:
>> Steve Kostecke writes:
>>
>>> On 2009-10-03, Rob wrote:
>>
>>>> It is worse when you start to twiddle the config and shutdown/restart
>>>> ntpd often. Then it can take a very long time before
Steve Kostecke wrote:
> On 2009-10-03, Rob wrote:
>
>> It is worse when you start to twiddle the config and shutdown/restart
>> ntpd often. Then it can take a very long time before it becomes stable
>> again.
>
> In my experience with ntpd "warm restarts"
Richard B. Gilbert wrote:
>> * On a system not locking stopping ntp and restarting having set the drift
>> file to -28, results in the drift going back to -400 over a couple of
>> hours - so not some odd start-up state that confuses the control loop.
>
> This suggests that your local clock is de
Hi there
pc wrote:
> FWIW, it's possible that the antenna/receiver modules are manufactured
> by this company:
>
> http://www.hkw-elektronik.de/
http://www.hkw-elektronik.de/englisch/products/products.php
http://www.hkw-elektronik.de/englisch/products/assemblys.php
Regar
Hi there
Rob van der Putten wrote:
> This will probably work;
>
>+-> DATA
>|
>|
>| / c
> +-+
--+-- |
47 kΩ | | /|\ |
| | --+-- |
+++| 1N|
| | 4148 |
| | |
| | |
GND >--*-*---*-> GND
You have to write software to drive it.
Regards,
Rob
--
There are 707 days until Ce
On Wed, 9 Sep 2009, rom...@ntp.org wrote:
> Greetings,
>
> I write with a concern from my day job, working on APM (application
> performance monitoring) devices for OPNET Technologies, Inc. I'm
> attempting to help a customer who is using an NTP v3 server running
> under a VMware virtual machin
start the pulse on the second.
Regards,
Rob
--
There are 703 days until Central Registry IPv4 address exhaustion.
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
ver, I'd rather just pull time from the client Linux box next to my
> desk. Does anyone have or know of a USB or serial device that can output a
> DCF-77 signal to a number of clocks (4)?
You could send a series of pulses from a serial port to the clocks.
Regards,
Rob
--
There are
data but I think that also does WWV (output is
> just demodulated carrier).
http://en.wikipedia.org/wiki/DCF77
http://en.wikipedia.org/wiki/WWV_(radio_station)
Regards,
Rob
--
There are 703 days until Central Registry IPv4 address exhaustion.
_
s well.
>
> Can anyone here advise regarding serial to usb adapters on
> Linux/BSD?
AFAIK USB (ESP 232 over USB) causes timing problems. You are probably
better off with syncing over ethernet.
Regards,
Rob
--
There are 691 days until Central Registry IPv4 address exhaustion.
On Thu, 13 Aug 2009, Unruh wrote:
> "Richard B. Gilbert" writes:
>
>> Unruh wrote:
>>> "Richard B. Gilbert" writes:
>>>
Unruh wrote:
> Ulrich Windl writes:
>
>> "David J Taylor"
>> writes:
>>> I've recent been suggesting the Windows port of NTP as a program
>>>
nasa138 wrote:
> I would like to add a few printf statement in the ntpd source code,
> and recompile it, and then run it, so that I can see the value.
> Here's what I did:
> 1) ./configure --->> it configure ok
> 2) add some printf statements in ntpd.c
> 3) make
> 4) go to ntpd_directory
> 5) ru
rackety.udel.edu is not synchronized.
ntpq -crv rackety.udel.edu:
associd=0 status=00f8 leap_none, sync_unspec, 15 events, no_sys_peer,
version="ntpd 4.2.5p...@1.1874-o Sun May 24 18:56:51 UTC 2009 (2)",
processor="i386", system="FreeBSD/6.1-RELEASE", leap=00, stratum=1,
precision=-18, rootdelay=
Dave wrote:
> I assume, for absolute accuracy (which is not important here, but I'm
> intersted), this is going to be better than any attempt to set the time
> from the ntp pool. Is that correct?
You never know that.
What you get from the pool may be a stratum-1 server locked to GPS time
on a f
Ronaldo Mexico wrote:
> In reply to Gene Miller and Steve Kostecke:
>
>> If the PTS is connected to a reference clock, why does it report
>> itself as a stratum 2 with a refid of either 73.78.73.84 or LOCAL(0),
>> as shown in the original posting:
>
> The PTS -is- it's reference. It's time is bas
Rick Jones wrote:
> Rob wrote:
>> This is no longer required. You can just use pool.ntp.org or
>> 0.pool.ntp.org and the DNS servers for the pool will automatically
>> determine which servers are closest to you.
>
> Is that by geography, hop count or ICMP echo RTT?
David J Taylor
wrote:
> When I used FreeBSD, I had to rebuild the kernel to get the PPS support.
> Not quite double-click and go!
On Linux, and probably also FreeBSD, you can install the package gpsd
alongside ntpd and have PPS support without rebuilding te kernel.
Of course it will not be as
David J Taylor
wrote:
> Have you tried the Windows/Meinberg installation? It includes configuring
> the "pool" server lines for the user's specified region. One which is
> pre-installed by default probably doesn't have the region optimisation.
This is no longer required. You can just use p
Rick Jones wrote:
> Allen Kistler wrote:
>> For example, http://www.ntp.org.
>
>> NTP.org has a perfectly good IPv4 site, but the IPv6 site doesn't
>> answer to SYNs. I have no problem with other IPv6 sites, but maybe
>> I'll find some in the future.
>
>> Since RFC-compliant behavior is to try t
David J Taylor
wrote:
> Whether they have such user-friendly install routines I can't say for
> sure, but I don't think so.
Of course they do. At least Linux does.
The NTP package installation is nothing special, it is just one of the
many packages that can be installed on the system. Often e
j...@specsol.spam.sux.com wrote:
> John Hasler wrote:
>> Jim Pennino writes:
>>> If you limit the problem to Olson, the problem was solved years ago at:
>>> ftp://elsie.nci.nih.gov/pub/
>>
>> Until they have a budget cut, a server reorganization, decide the traffic
>> is excessive, or just get b
E-Mail Sent to this address will be added to the BlackLists
wrote:
> ... and, what do all those millions of embedded systems
> do now to get time zone data?
They don't. DST support is usually hardwired, manually configured
or nonexistent.
The user has to set the clock himself twice a year or a
Richard B. Gilbert wrote:
> Rod Dorman wrote:
>> In article ,
>> Richard B. Gilbert wrote:
>>> ...
>>> Kludging local timezone conversions into the NTP protocol somehow would
>>> be a nightmare if you could persuade anyone to do it! 24 or more
>>> timezones ...
>>
>> Don't forget that there
701 - 800 of 948 matches
Mail list logo
