On 10/12/2014 12:39, Miroslav Lichvar wrote:
On Wed, Dec 10, 2014 at 11:50:22AM +, David Taylor wrote:
With -D 4 I get a list of devices ending with PPS, but presumably that is
not the same as KPPS?
In gpsd the PPS without K is the userspace timestamping. With kernel
timestamping the log
Harlan Stenn st...@ntp.org wrote:
Rob writes:
Harlan Stenn st...@ntp.org wrote:
Rob writes:
Harlan Stenn st...@ntp.org wrote:
If you disgree and think NTP should provide the file all the time, then:
- how do you propose we find out if the underlying API is really
provided in the
Harlan Stenn st...@ntp.org wrote:
Paul writes:
--001a11c12566ef4fbd050a04ed7c
Content-Type: text/plain; charset=ISO-8859-1
On Dec 12, 2014 12:39 AM, Harlan Stenn st...@ntp.org wrote:
It's an OS-specific file that should be provided by the OS if the
underlying API exists.
To repeat
Harlan Stenn st...@ntp.org wrote:
Rob writes:
Harlan Stenn st...@ntp.org wrote:
Martin Burnicki writes:
IMO the best approach would be to detect this at runtime.
That means we'd need a header file...
If I'm not mistaken (and it's getting late for me), if the header file
is missing
On Sat, Dec 13, 2014 at 2:52 AM, David Taylor
david-tay...@blueyonder.co.uk.invalid wrote:
For some reason, gpsd seems to be stuck at a lower release for the
Raspberry Pi version of Debian, so I will have a go at recompiling it once
I can find the right instructions! That's if there's no
On Sat, Dec 13, 2014 at 5:01 AM, Rob nom...@example.com wrote:
Current build dependencies on Debian are:
That's better said on my install of Debian. I wouldn't expect it be the
case on all release tracks and it doesn't help Ubuntu.
Of course for an S1 operator the fact that this approach
Paul tik-...@bodosom.net wrote:
On Sat, Dec 13, 2014 at 5:01 AM, Rob nom...@example.com wrote:
Current build dependencies on Debian are:
That's better said on my install of Debian. I wouldn't expect it be the
case on all release tracks and it doesn't help Ubuntu.
Of course for an S1
Hi all
I was wondering if it makes sense to set up Autokey authentication on a client
for when it wants to sync time from *.pool.npt.org. My goal is to encrypt
communication between client and server and to make sure the server is really
the one it claims to be. Can this be even done with
On Sat, Dec 13, 2014 at 3:16 PM, Rob nom...@example.com wrote:
You know what? On the ntp-dev package for Debian THE BUILD DEPENDENCIES
ARE INCORRECT AS WELL!!
This is an example of what NTF doesn't want to deal with. My instance of
Wheezy doesn't have ntp-dev.
Fortunately there is gpsd.
Rob writes:
Harlan Stenn st...@ntp.org wrote:
Paul writes:
--001a11c12566ef4fbd050a04ed7c
Content-Type: text/plain; charset=ISO-8859-1
On Dec 12, 2014 12:39 AM, Harlan Stenn st...@ntp.org wrote:
It's an OS-specific file that should be provided by the OS if the
underlying API
d_anderson writes:
Hi all
I was wondering if it makes sense to set up Autokey authentication on
a client for when it wants to sync time from *.pool.npt.org. My goal
is to encrypt communication between client and server and to make sure
the server is really the one it claims to be. Can this
On 2014-12-12 03:25, Harlan Stenn wrote:
It's pretty easy to download and install a leapsecond file, and ntpd
will pay attention to that...
Not that easy - unless you are one of the lucky few to have encrypted
access to a NIST source, when it may be automatic.
You have to use a NIST server,
Brian Inglis writes:
On 2014-12-12 03:25, Harlan Stenn wrote:
It's pretty easy to download and install a leapsecond file, and ntpd
will pay attention to that...
Not that easy - unless you are one of the lucky few to have encrypted
access to a NIST source, when it may be automatic.
On 14/12/14 03:28, Harlan Stenn wrote:
Not that easy - unless you are one of the lucky few to have encrypted
access to a NIST source, when it may be automatic.
http://www.ietf.org/timezones/data/leap-seconds.list
Added to the Wiki at http://support.ntp.org/bin/view/Support/ConfiguringNTP
14 matches
Mail list logo
