[ntp:questions] NTP 4.2.5p236-RC Released
Redwood City, CA - 2009/10/22 - The NTP Public Services Project (http://support.ntp.org/) is pleased to announce that NTP 4.2.5p236-RC, a Release Candidate of the NTP Reference Implementation from the NTP Project, is now available at http://www.ntp.org/downloads.html and http://support.ntp.org/download. File-size: 4257481 bytes MD5 sum: 78bb13572241e624e456698e3e574840 Bug Fixes: * [Bug 1353] ntpq rv 0 settimeofday always shows UNKNOWN on unix. http://bugs.ntp.org/1353 * [Bug 1343] ntpd/ntp_io.c close_fd() does not compile on Solaris 7. http://bugs.ntp.org/1343 Other Changes: * Do not attempt to execute built binaries from ntpd/Makefile when cross-compiling (keyword-gen and ntpd --saveconfigquit). * sntp/main.c: Remove duplicate global adr_buf[] (also defined in networking.c) which Piotr Grudzinski identified breaking his build. * Correct in6addr_any test in configure.ac to attempt link too. * Cleanup from Dave Mills. Please report any bugs, issues, or desired enhancements at http://bugs.ntp.org/. The NTP (Network Time Protocol) Public Services Project, which is hosted by Internet Systems Consortium, Inc. (http://www.isc.org/), provides support and additional development resources for the Reference Implementation of NTP produced by the NTP Project (http://www.ntp.org/). ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
[ntp:questions] cgps command question
Hello, I set up alix1d box running debian etch with a garmin 18x lvc receiver. I am using gpsd and ntp with the shared memory driver running both gps and pps signal. The data output provided by ntpq –p looks good with excellent readings for the GPS and the PPS signal but my question concerns the output from cgps command. The status line blinks between 2D and 3D fix counting up only to 1 every second. It continually blinks/refreshes while it updates. The gps type reads generic nmea. There is no data showing on the right side of the screen. Is this the way it should look? We have another box running a garmin 18x usb not doing pps and the status shows 3d fix and the seconds count up and there is data on the right side and it does not blink while it updates. Is it the pps signal on the lvc unit making it refresh every second? Being new to all of this I’m just trying to figure out what is normal. Should I even care what the cgps commands shows me? Is this command only helpful when using the GPS signal only and not helpful when using the PPS signal? Thanks for any help, Jim ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] testing slew only mode (-x), not slewing correctly (linux sles10, ntpd v 4.1.1)
On 2009-10-22, David Woolley da...@djwhome.demon.co.uk wrote: I believe that the official policy line is that database systems that require monotonic time for their distributed transaction logic are fundamentally flawed. It is the database people who require monotonic time. If there is an official policy line it is that any system with a clock which drifts past the step threshold is fundamentally flawed. -- Steve Kostecke koste...@ntp.org NTP Public Services Project - http://support.ntp.org/ ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] testing slew only mode (-x), not slewing correctly (linux sles10, ntpd v 4.1.1)
Steve Kostecke wrote: On 2009-10-22, David Woolley da...@djwhome.demon.co.uk wrote: I believe that the official policy line is that database systems that require monotonic time for their distributed transaction logic are fundamentally flawed. It is the database people who require monotonic time. Transaction logic implied databases. If there is an official policy line it is that any system with a clock which drifts past the step threshold is fundamentally flawed. Dave Mills on not using NTP for critical database timestamps: http://groups.google.co.uk/group/comp.protocols.time.ntp/msg/20d802c94f87c274. On the other hand, the low end of the ADSL speed range will easily cause 128ms to be exceeded unless both you and your ISP have NTP traffic prioritised. ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] testing slew only mode (-x), not slewing correctly (linux sles10, ntpd v 4.1.1)
David Woolley wrote: Steve Kostecke wrote: On 2009-10-22, David Woolley wrote: I believe that the official policy line is that database systems that require monotonic time for their distributed transaction logic are fundamentally flawed. It is the database people who require monotonic time. Transaction logic implied databases. If there is an official policy line it is that any system with a clock which drifts past the step threshold is fundamentally flawed. I guess I could see 10 minutes (or more) if the time had never been set to anything reasonable; However 10 minutes seems really far out for something that was previously syncing with NTP servers (or any other source of time). Dave Mills on not using NTP for critical database timestamps: http://groups.google.co.uk/group/comp.protocols.time.ntp/msg/20d802c94f87c274. -- E-Mail Sent to this address blackl...@anitech-systems.com will be added to the BlackLists. ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] testing slew only mode (-x), not slewing correctly (linux sles10, ntpd v 4.1.1)
E-Mail Sent to this address will be added to the BlackLists wrote: David Woolley wrote: Steve Kostecke wrote: On 2009-10-22, David Woolley wrote: I believe that the official policy line is that database systems that require monotonic time for their distributed transaction logic are fundamentally flawed. It is the database people who require monotonic time. Transaction logic implied databases. If there is an official policy line it is that any system with a clock which drifts past the step threshold is fundamentally flawed. I guess I could see 10 minutes (or more) if the time had never been set to anything reasonable; However 10 minutes seems really far out for something that was previously syncing with NTP servers (or any other source of time). I don't see what previously synching has to do with anything. If previously synching means three weeks ago, it's meaningless! If it means thirty minutes ago, I would expect the clock to be within a few milliseconds of the correct time. If not I would regard the clock as broken! I'm assuming reasonably constant temperature! snip ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] cgps command question
If you aren't seeing any right-hand data from cgps, I would guess this is most likely because your GPS isn't currently configured to report which satellites it can see (via $GPGSV sentences). I don't believe the output of cgps shows PPS info. Questions about gpsd and cgps should really be directed to the gpsd-users list (gpsd-us...@lists.berlios.de), so if this answer isn't sufficient, you should ask again on that list. -- Rich Wales / ri...@richw.org / ri...@stanford.edu Wikipedia: http://en.wikipedia.org/wiki/User:Richwales Facebook: http://www.facebook.com/richwales ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
