2009/1/3 christopher hoover :
> Hal Murray wrote:
>> Two of my Linux systems hung. One was running a 2.6.25 kernel and one
>> 2.6.26. A system running 2.6.23 worked fine. I saw a couple of notes
>> on
>> comp.protocols.time.ntp about Linux systems locking up. One said that
>> it was
>> a kernel
Hal Murray wrote:
> Two of my Linux systems hung. One was running a 2.6.25 kernel and one
> 2.6.26. A system running 2.6.23 worked fine. I saw a couple of notes
> on
> comp.protocols.time.ntp about Linux systems locking up. One said that
> it was
> a kernel bug in ntp.c but I haven't seen any
On Fri, Jan 02, 2009 at 12:13:32PM -0800, Tom Van Baak wrote:
> I was sent a NMEA log of a Garmin GPS12 (f/w 4.60) showing
> the strangest leap second trace yet. Has anyone else see this
> before? In the ~15 seconds below, note:
>
> - double 235957
> - missing 235958 for the RMC sentence
> - no se
Poul-Henning Kamp skrev:
> In message , Joe Gwinn writes:
>
>> This was done long before GPS was invented, or NTP for that matter.
>
> You should check the age of NTP, it is one of the oldest protocols
> around being initially standardized in september 1985, but inhereting
> most of its features
I was sent a NMEA log of a Garmin GPS12 (f/w 4.60) showing
the strangest leap second trace yet. Has anyone else see this
before? In the ~15 seconds below, note:
- double 235957
- missing 235958 for the RMC sentence
- no second 235960 for either sentence
- strange 59 for the BWC sentence
- miss
In message , Joe Gwinn writes:
>This was done long before GPS was invented, or NTP for that matter.
You should check the age of NTP, it is one of the oldest protocols
around being initially standardized in september 1985, but inhereting
most of its features from "ICS" which were first standardiz
The first column is MJD. The second column is seconds within that day.
(I chopped off the right end to avoid line wrap.)
54831 86384.488 $GPRMC,235944.000,A,3726.0731,N,12212.2624,W,0.30,
54831 86385.489 $GPRMC,235945.000,A,3726.0738,N,12212.2624,W,0.45,
54831 86386.489 $GPRMC,235946.000,A,3726.
Magnus,
At 12:00 PM + 1/2/09, time-nuts-requ...@febo.com wrote:
>Message: 1
>Date: Fri, 02 Jan 2009 09:45:23 +0100
>From: Magnus Danielson
>Subject: Re: [time-nuts] Leap seconds and POSIX
>To: Discussion of precise time and frequency measurement
>
>
>>> : In practice, in platforms tha
Hi Magnus, Joe, et al,
Please move the "leap seconds and POSIX" thread over
to the LEAPSECS list.
/tvb
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instr
Magnus,
At 8:39 AM + 1/2/09, time-nuts-requ...@febo.com wrote:
>
>Message: 9
>Date: Fri, 02 Jan 2009 09:35:59 +0100
>From: Magnus Danielson
>Subject: Re: [time-nuts] Leap seconds and POSIX
>To: Discussion of precise time and frequency measurement
>
>Message-ID: <495dd1ef.7030...@rubidi
Steve,
At 8:39 AM + 1/2/09, time-nuts-requ...@febo.com wrote:
>
>Message: 6
>Date: Fri, 2 Jan 2009 14:00:56 +1300
>From: "Steve Rooke"
>Subject: Re: [time-nuts] Leap seconds and POSIX
>To: "Discussion of precise time and frequency measurement"
>
>
>2009/1/2 Joe Gwinn :
>
>> Platforms
>> : In practice, in platforms that have access to GPS, NTP is used to
>> : servo the local computer clock into alignment with UTC (or GPS System
>> : Time (UTC without the accumulated leaps) in systems that abhor time
>> : steps), and there is a transient error just after a leap second while
>> :
Joe Gwinn skrev:
> Having worked in the POSIX committee for many years, I can shed some
> light on how POSIX handles leap seconds:
>
> In short, POSIX adamantly ignores leap seconds. All days in POSIX
> have the same length, 86,400 seconds.
>
> This omission is not by accident, instead having
13 matches
Mail list logo
