On 9 December 2017 at 09:40, Christian Weisgerber
wrote:
> On 2017-12-08, Darren Tucker wrote:
>
> > If your hardware doesn't have a clock (or the clock is bad) then it can
> > take ntpd a long time to adjust it back to the correct time (it uses
> > adjtime(), which I think adjusts at +/- 10%).
On 2017-12-08, Darren Tucker wrote:
> If your hardware doesn't have a clock (or the clock is bad) then it can
> take ntpd a long time to adjust it back to the correct time (it uses
> adjtime(), which I think adjusts at +/- 10%).
Actually, 5000 parts per million, so 0.5%.
--
Christian "naddy" W
On 9 December 2017 at 01:58, mabi wrote:
>
> I have a new Lanner FW-7526B firewall loaded with OpenBSD 6.2. I must say
> it's a nice small firewall but unfortunately the ntp daemon does not seem
> to manage to set the time correctly with this hardware. The time is off by
> approximately 1:20h and
Mhh thanks, totally forgot about that good old rdate. That did it and now ntp
is happy in sync.
> Original Message
>Subject: Re: NTP issue on Lanner FW-7526B
>Local Time: December 8, 2017 7:22 PM
>UTC Time: December 8, 2017 6:22 PM
>From: dan...@pressco
It is adjusting the time, but your clock is way off, so it try to do it
slowly as to not mess any logs, but if you want to adjust it al at once
and don't care about that for now
rdate -n4 pool.ntp.org
Simple.
On 12/8/17 9:58 AM, mabi wrote:
> Hi,
>
> I have a new Lanner FW-7526B firewall load
Hi,
I have a new Lanner FW-7526B firewall loaded with OpenBSD 6.2. I must say it's
a nice small firewall but unfortunately the ntp daemon does not seem to manage
to set the time correctly with this hardware. The time is off by approximately
1:20h and every 2-3 minutes I see the following log en
6 matches
Mail list logo
