Re: clock not set on boot

On Sun, Dec 06, 2020 at 08:39:36AM +0100, Otto Moerbeek wrote:

> On Sun, Dec 06, 2020 at 08:33:33AM +0100, Otto Moerbeek wrote:
>
> > On Sat, Dec 05, 2020 at 07:42:48PM -0700, Theo de Raadt wrote:
> >
> > > Andy Goblins <andygoblins@gmx.com> wrote:
> > >
> > > > Does ntpd need DNS to set the time? Because my reslov.conf points to
> > > > 127.0.0.1 and unbound needs the time before it will work properly.
> > >
> > > A problem of your own creation.
> > >
> >
> > We do attept to work even in this situation, by doing CD (checking
> > disbaled) queries if needed. But in some cases this does not work,
> > esepcially if the net and/or unbound is slow to start.
> >
> > e.g. I have one machine that nees a !sleep 1 in it's hostname.if
> > file since the network interface it tto slow to startup and ntpd
> > gives up doing the initial settime.
> >
> > Add ntpd_flags=-vv and show me the /var/log/daemon lines.
> >
> > -Otto
> >
>
> Ah, I see the info is already there in another post. This edgerouter
> is a slow machine. You can try what I suggested, e.g. by putting a
> sleep after unbound starts in /etc/rc.
>
> But an easier solution is not to rely on a single resolved and add
> another one in /etc/resolve.conf

Sorry about the typos. *resolver and */etc/resolv.conf

-Otto