Systems that need a leap second free time scale these days seem to be using GPS
time instead of TAI. It seems to be rather popular in the financial industry.
___
time-nuts mailing list -- time-nuts@lists.febo.com
To unsubscribe, go to
On Thu, Aug 8, 2019 at 8:07 AM Adam Kumiszcza wrote:
>
> Hi everybody! My first post here, I hope the subject is adequate for this
> mailing list.
>
> I'm using a tiny layer 1 NTP server consisting of Raspberry Pi 3B+ with
> Ublox MAX-M8Q expansion board providing GNSS (currently GPS, Galileo and
Hi everybody! My first post here, I hope the subject is adequate for this
mailing list.
I'm using a tiny layer 1 NTP server consisting of Raspberry Pi 3B+ with
Ublox MAX-M8Q expansion board providing GNSS (currently GPS, Galileo and
Glonass, sometimes I switch to Beidou, too) reference with PPS
Hi Adam,
I've only ever used hardware PTP servers (and I'm far from an expert), but PTP
is pretty sensitive to latency. It's common for PTP to deployed on dedicated
networks to help keep jitter to a minimum (I think I remember one place doing
it on Infiniband but I might be wrong). The
On 8/8/19 4:24 AM, Greg Troxel wrote:
The POSIX specification says that unix time (what gettimeofday returns,
the numbers that are stored in the filesystem for mod times) is a
strange version of UTC, where it's expressed in seconds since the epoch
as if there were no leap seconds.
which is
On 8/8/19 2:51 AM, Tim Dunker wrote:
Dear Ralph
I keep all our GNU/Linux machines on UTC (i.e., <>). Our
timezone is off by one or two hours, but the actual offset does not
matter to me. What matters to me is to have all systems using the same
timezone, and for our purposes, nobody cares about
Ralph Aichinger wrote:
> TAI would probably be the more logical way to store and do
> calculations with time, only including leap seconds when
> formatting time for human consumption.
Indeed. Just about everybody I know who's studied this issue
carefully has come to more or less the same
On 8/8/19 1:30 AM, Ralph Aichinger wrote:
Hi!
Another newbie type question: When thinking about how computers represent
time,
TAI would probably be the more logical way to store and do calculations
with time, only including leap seconds when formatting time for human
consumption. Or am I wrong
Ralph Aichinger writes:
> Another newbie type question: When thinking about how computers
> represent time, TAI would probably be the more logical way to store
> and do calculations with time, only including leap seconds when
> formatting time for human consumption. Or am I wrong in this?
There
Dear Ralph
I keep all our GNU/Linux machines on UTC (i.e., <>). Our
timezone is off by one or two hours, but the actual offset does not
matter to me. What matters to me is to have all systems using the same
timezone, and for our purposes, nobody cares about our local time.
>> Can the same thing
Hi!
Another newbie type question: When thinking about how computers represent
time,
TAI would probably be the more logical way to store and do calculations
with time, only including leap seconds when formatting time for human
consumption. Or am I wrong
in this?
There is a CLOCK_TAI on Linux, but
[sorry for the messed up formatting in my previous email, I normally use my
linux
"mutt" mailer, but as I had subscription problems I am sending this over
the yet unfamiliar
to me Google web interface]
Am Mi., 7. Aug. 2019 um 20:02 Uhr schrieb Tom Van Baak :
>
> Mimicking a NMEA ZDA sentence is
Am Do., 8. Aug. 2019 um 05:09 Uhr schrieb Gary Chatters <
gcarlis...@garychatters.com>:
> I would expect that making your Arduino device look like a GPS receiver
> outputting NMEA messages and a PPS signal would be about the simplest
> approach you could take. It has the advantage that there is
13 matches
Mail list logo
