We're pleased to announce the move of the OpenBSM source code
repository from the FreeBSD Perforce server to Github.After a
period of dormancy, we hope this will make the code more accessible
and stimulate outside contributions.
Since the converter (git-p4) could not export the release labels
fro
Mark Felder writes:
> I'm not an expert on the leapsecond operation, but if I understand it
> correctly there are two ways a system can be notified of a leapsecond:
> via a tzdata update or through NTP.
Answering a bit late, but no: in practical terms, only NTP works.
Recording leap seconds in tz
On Wed, Jul 1, 2015, at 08:47, Dag-Erling Smørgrav wrote:
> Mark Felder writes:
> > I'm not an expert on the leapsecond operation, but if I understand it
> > correctly there are two ways a system can be notified of a leapsecond:
> > via a tzdata update or through NTP.
>
> Answering a bit late,
Is there a reasonable way to enable awareness of leap-seconds while syncing
with ntpd? That is to say, how can I get the system to include leap-seconds
in calculating `date +%s`, without having `date` be off by 26[1] seconds?
The default configuration produces incorrect results when computing
hist
On 2015-Jul-01 12:46:21 -0500, Leif Pedersen wrote:
>Is there a reasonable way to enable awareness of leap-seconds while syncing
>with ntpd? That is to say, how can I get the system to include leap-seconds
>in calculating `date +%s`, without having `date` be off by 26[1] seconds?
ntpd(8) has prov
Peter Jeremy wrote this message on Thu, Jul 02, 2015 at 06:27 +1000:
> On 2015-Jul-01 12:46:21 -0500, Leif Pedersen wrote:
> >Is there a reasonable way to enable awareness of leap-seconds while syncing
> >with ntpd? That is to say, how can I get the system to include leap-seconds
> >in calculating
On Wed, Jul 1, 2015 at 4:01 PM, John-Mark Gurney wrote:
> Though from my reading of the code, you need to have TZ files compiled
> w/ leap seconds which FreeBSD doesn't do by default...
>
I did an equivalent, see my note [2]...and afaict ntp doesn't use tzdata.
--
As implied by email protoco
On Wed, Jul 1, 2015 at 3:27 PM, Peter Jeremy wrote:
>
> On 2015-Jul-01 12:46:21 -0500, Leif Pedersen wrote:
> >Is there a reasonable way to enable awareness of leap-seconds while
syncing
> >with ntpd? That is to say, how can I get the system to include
leap-seconds
> >in calculating `date +%s`, w
< said:
> ntpd(8) has provision for specifying a leapsecond file which presumably
> makes it leap-second aware. I haven't looked into the details.
The current NTP protocol, as implemented by ntpd, distributes
leap-second information if provided. This information may be provided
by higher-stratu
