On 2014-09-25 00:23, harik...@gmail.com wrote:
Does anybody know why the IP address reported in NTP log messages is always
0.0.0.0?
For example the message written while stepping the clock looks like this:
Sep 25 13:03:47 ntpd[1818]: 0.0.0.0 061c 0c clock_step +340.491291 s
I looked into ntpd so
On Monday, September 29, 2014 2:48:33 PM UTC+8, Hari Mahadevan wrote:
> On Friday, September 26, 2014 7:12:04 PM UTC+8, Martin Burnicki wrote:
>
> > Hari Mahadevan wrote:
>
> >
>
> > > On Thursday, September 25, 2014 2:27:01 PM UTC+8, Hari Mahadevan wrote:
>
> >
>
> > >> On Thursday, Septemb
On Monday, June 13, 2011 8:17:54 AM UTC-7, Chris Albertson wrote:
..
>
> My purpose for getting WWWV is to compare it with GPS time and I hope
> maybe learn something about the atmosphere. Any different in the two
> times must be because of the path delay.
Partly solved problem:
There are in
We have had a couple of NTP servers we provide to pool.ntp.org for a few years
with one IPv4 address on each server.
We have rolled out IPv6 access and wanted to know if we should be setting these
NTP servers up as dual stack with IPv4 and IPv6.
We are not sure if there is a way to show one s
I'm running ntpd 4.2.6p5 on an Ubuntu 14.04.1 system (kernel version =
3.13.0-36-generic). I'm thinking of setting up the ACTS_MODEM driver to
give me a backup time reference in case my GPS loses its signal.
I have an old Conexant HSF modem card, which I was able to install on an
old Linux box ma
On Friday, September 26, 2014 7:12:04 PM UTC+8, Martin Burnicki wrote:
> Hari Mahadevan wrote:
>
> > On Thursday, September 25, 2014 2:27:01 PM UTC+8, Hari Mahadevan wrote:
>
> >> On Thursday, September 25, 2014 2:23:13 PM UTC+8, Hari Mahadevan wrote:
>
> >>
>
> >>> Does anybody know why the IP
