| [chrony-dev] Leap seconds using SOCK driver |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-dev] Leap seconds using SOCK driver
- From: Michael Scherer <michael.scherer@xxxxxxxxxxxxx>
- Date: Mon, 19 Dec 2016 14:06:46 -0600
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=michael.scherer@xxxxxxxxxxxxx;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=asvglobal.onmicrosoft.com; s=selector1-asvglobal-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=rj0izS8q0q1Wuo5MbL/bcJjfzeC0O+t8T5tDQ3i9gFQ=; b=Aa6U3F//BEj/Q5IUAauU8wdD5ogmiucXNFDPrjNyqZ9rd/e+Ns5t6St06n1D/wzKK3gmMhu5NsduEWFB2clzlXidL9WW8qWSA22P7G+2Jl+3qY8vzjOVPft/es/r1q4bwu1LrusoteiwrrkpGcDBOUJcrXC9s6YHA5eYEI8NpBk=
- Organization: Autonomous Surface Vehicles, LLC
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Hello,
We're presently using the SOCK driver with chrony, and I wanted to
verify the correct usage of the leap parameter.
struct sock_sample {
struct timeval tv;
double offset;
int pulse;
int leap;
int _pad;
int magic;
};
As far as I can tell, setting leap to 1 will schedule the insertion of a
leap second, and won't apply it until the last day of June or December.
Is there an expected minimum amount of time in advance that this needs
to get set? Does it matter if we keep that set after the leap second
should be applied, so long as it gets cleared before the next schedule
window?
Thanks,
--
Michael Scherer
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.