| From: |
"Massimo S." <ecs-isp@2rosenthals.com> |
Full Headers
Undecoded message |
| Subject: |
Re: [eCS-ISP] ntp day issue |
| Date: |
Sat, 18 Jan 2025 11:09:06 +0100 |
| To: |
eCS ISP Mailing List <ecs-isp@2rosenthals.com> |
|
|---|
Il 17/01/2025 21:57, Steven Levine ha scritto:
In <list-11990234@2rosenthals.com>, on 01/17/25
at 05:14 PM, "Massimo S." <ecs-isp@2rosenthals.com> said:
Hi Massimo,
today my SRV1/MTA1 have 18th jen. 2025 date, while we are at 17th jen. :)
interesting...
Any suggestion?
There's always
http://www.warpcave.com/betas/os2_ntpd-1.7beta-shl-2023-04-11.zip
thanks
FWIW, my current cfg_data is
; 2020-02-18 SHL
cfg_data
poll interval = 16
us.pool.ntp.org
0.us.pool.ntp.org
1.us.pool.ntp.org
2.us.pool.ntp.org
pool.ntp.org
0.pool.ntp.org
1.pool.ntp.org
2.pool.ntp.org
and rtc_type is set to 1
this tool can run scheduled and not allways in memory?
Normally os2_ntpd can figure out the clock type, but I've heard some VMs
can confuse it.
Steven
i've this issue since years
even when the MTA1 was running on bare metal
i run the time sync at each reboot, sometimes it show the date issue
i've never understand why
some years ago INRIM went for 2 atomic clocks from daytime to NTP
and i tought the issue was due to this change
but it have another IP (the one i use) with daytime protocol
so i use that one, but i don't understand why sometimes this issue happens
massimo
|