On 05/12/2020, Patrick Wildt wrote:
>
> -s doesn't exist anymore.
>
... and other replies...
You've all proved what I guess I already knew.
I don't live in the world anymore. It just passes me by.
On December 6, 2020 7:44:01 AM UTC, Otto Moerbeek wrote:
>> 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
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 wrote:
> > >
> > > > Does ntpd need DNS to set the time? Because my
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 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
On Sat, Dec 05, 2020 at 07:42:48PM -0700, Theo de Raadt wrote:
> Andy Goblins 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
On Sat, Dec 05, 2020 at 09:10:19PM +, Maurice McCarthy wrote:
> Perhaps add
>
> ntpd_flags="-s"
>
> to /etc/rc.conf.local
>
Nope, that's no longer needed.
Andy Goblins 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.
You have filtered ntpd so much that it can't do the job it wants to do.
Andy Goblins wrote:
> > From: "Theo de Raadt"
> >
> > ntpd is run by default, and magically will correct the time almost
> > immediately.
> >
> > Some significant effort went into this a few years ago.
> >
> > However,
> From: "Theo de Raadt"
>
> ntpd is run by default, and magically will correct the time almost
> immediately.
>
> Some significant effort went into this a few years ago.
>
> However, the kernel message will always be there. You can ignore it.
>
> Run ntpctl -s all, and you'll see the time has
andygoblins wrote:
> Ever since updating to 6.8, I've had trouble with the system clock not
> getting set on boot.
>
> I know the easy answer is to script a call to rdate, but that feels like a
> bandaid solution.
>
> I'm running from an EdgeRouter Lite (octeon) that afaik does not have a
>
On Sat, Dec 05, 2020 at 09:10:19PM +, Maurice McCarthy wrote:
> Perhaps add
>
> ntpd_flags="-s"
>
> to /etc/rc.conf.local
>
-s doesn't exist anymore.
Perhaps add
ntpd_flags="-s"
to /etc/rc.conf.local
Ever since updating to 6.8, I've had trouble with the system clock not getting
set on boot.
I know the easy answer is to script a call to rdate, but that feels like a
bandaid solution.
I'm running from an EdgeRouter Lite (octeon) that afaik does not have a
persistent clock. Before 6.8, I
13 matches
Mail list logo