Slashdot Mirror

← Back to Domains

Domain: meinberg.de

Stories and comments across the archive that link to meinberg.de.

Comments · 8

  1. Re:Horribly misleading by rkit · · Score: 1 · on New Speed Cameras Catch You From Space

    Yes I know how GPS works. But NTP is the standard way to integrate a GPS receiver as a precision time source into a general purpose system. See e.g. here for a provider of GPS-based ntp solutions.

  2. NTP and Leap by EyelessFade · · Score: 1 · on Leap Second To Be Added Dec 31, 2008

    I get the new second in 2009 since I live in UTC +1

    leap-second

    Summary: NTP and GPS know about leap seconds, operating system might not.

    From TA:
    "Linux kernels and most other Unix-like systems care about the leap seconds and handle them correctly. Some systems even add a notification to the system log when the leap second is inserted."

    "The Windows system clock does not know about leap seconds, either. However, there is a precompiled version of ntpd for Windows available which is capable of slewing the Windows system time quickly in order to account for the insertion of a leap second, without affecting the clock synchronization loop provided by ntpd."

  3. Re:GPS time with OpenBSD by hgerstung · · Score: 3, Informative · on NTP Pool Reaches 1000 Servers, Needs More

    ...and the nice thing is that there is already a driver for OpenBSD for that device, thanks to the opensource driver policy of Meinberg. Heiko

  4. Re:GPS time with OpenBSD by ask · · Score: 5, Informative · on NTP Pool Reaches 1000 Servers, Needs More

    Actually ... The USB latency can be pretty bad, so it's likely you'd get better time from a well-picked internet time server. You'd definitely get MUCH better time with a proper PPS (Pulse Per Second) time keeping GPS receiver or variations of that.

  5. Re:NTP is great, except if you need it in Windows by ldspartan · · Score: 2, Interesting · on Computer Network Time Synchronization

    If its synchronizing on a schedule ("synchronizing them every minute"), you don't have an NTP client, you have an SNTP client. Real NTP doesn't have a concept of a synchronization interval, the clock is either synchronized or it isn't.

    I think.

    This appears to be a port of real-deal NTP code to windows. I've never used it, just found it in a few minutes of googling, but its worth a shot.

    --
    Phil

  6. Re:It's all software by amorsen · · Score: 1 · on U.S. Scientists Call for a Time Change
    Unfortunately NTP is broken for leap seconds -- the NTP time stamp stays the same during the leap second, effectively stopping time. Meinberg has a page which shows what happens. If NTP had been implemented correctly, it would keep time without leap seconds, but include an announcement of the accumulated leap seconds.

    NTP is probably broken because POSIX time is broken. You never get the time 23:59:60 in POSIX. Instead you get 23:59:59 twice, or even stuff like 23:59:59.993 followed shortly by 23:59:59.123. Many services do not like time jumps, time stops, or time speedups/slowdowns. And those are the options if you stick with POSIX time.

  7. Re:Not for Windows users, or BSD users by KenSeymour · · Score: 1 · on Expert Network Time Protocol

    I have used this binary with success: ntp4172.zip

    Just checking today, this source seems more up to date.

  8. The blame game by trolman · · Score: 5, Interesting · on US/Canada Power Outage Task Force Event Timeline
    The really bizarre part that has not been explained is that the frequency deviated. I saw frequency deviation alarms on my equipment (ups and pdus) on the data center floor in NY, NJ, and CT and this is the first time in my 20 years that this has happened. A glaring ommission is is that PJM stayed up as an entity. Kudos to PJM.

    The blame will be put onderegulation and lack of government oversight.