On Aug 1, 2016, at 6:32 AM, Kurt Roeckx wrote:
>>
>> The DHCPACK that assigns the IP address to the interface occurs during the
>> middle of ntpd's startup, so two of three pool statements get failed DNS.
>> The third one succeeds, so ntpd gets some servers, but not all the
On Mon, Aug 01, 2016 at 04:23:54AM -0700, Rick Thomas wrote:
> > May 18 03:52:23 ultimate ntpd[381]: ntpd 4.2.8p7@1.3265-o Sat Apr 30
> > 11:18:37 UTC 2016 (1): Starting
> > May 18 03:52:23 ultimate ntpd[381]: Command line: /usr/sbin/ntpd -p
> > /var/run/ntpd.pid -g -u 112:120
> > May 18
On Mon, Aug 01, 2016 at 03:53:29AM -0700, Rick Thomas wrote:
> First of all, thanks very much for the prompt reply!
>
> I'll try it again in sid and stretch, but it was there the last time I looked.
>
> The problem is not getting dhcpclient to give ntp servers. I've put hard
> coded ipv4
First of all, thanks very much for the prompt reply!
I’ll try it again in sid and stretch, but it was there the last time I looked.
The problem is not getting dhcpclient to give ntp servers. I’ve put hard coded
ipv4 addresses in /etc/default/ntpdate, so that’s not it.
The problem is that the
On Mon, Aug 01, 2016 at 02:37:58AM -0700, Rick Thomas wrote:
> This 8 year old bug is still present in jessie and stretch -- the change to
> systemd did not fix it!
>
> Please, somebody pay attention! This bug makes ntpd unreliable tending to
> useless on systems that get their network config
5 matches
Mail list logo