It shouldn't, so if it is there, it's a bug to fix.
I just noticed "crontab -e" also gives an error, so that should be fixed too.
NTP force sync option
Started by Pr2, 22 Jul 2021 19:37
45 replies to this topic
Re: NTP force sync option #41
-
- PLi® Core member
- 68,609 posts
+1,739
Excellent
Posted 16 August 2021 - 21:47
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: NTP force sync option #42
-
- Senior Member
- 391 posts
+8
Neutral
Posted 16 August 2021 - 21:55
afair 20yrs ago with ntp there was a maximum drift of 1000sec after that the clock was 'too far off'.
There are many config options and args, I eventually moved to OpenNTP.
I did not check the busybox implementation but anyway the ntpdate command should set the clock.
My 2 cents
A.A.
Re: NTP force sync option #43
-
- PLi® Core member
- 68,609 posts
+1,739
Excellent
Posted 16 August 2021 - 22:15
A.A.
It does, but oscam contains what they call CLOCKFIX, and we call CLOCKDESTROYER. If oscam detects a large clock drift, it resets the clock to what it was before. Which is a nightmare if oscam starts and the time is not set yet.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: NTP force sync option #44
-
- PLi® Core member
- 68,609 posts
+1,739
Excellent
Posted 16 August 2021 - 22:16
Bug was in the ntp package, it creates a crontab entry for ntpdate-silent in the wrong place. And the crontab -e error was a busybox defconfig error.
Both are fixed.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: NTP force sync option #45
-
- Senior Member
- 1,227 posts
+82
Good
Posted 17 August 2021 - 19:03
we could consider adding a fake-hwclock option as well
Debian -- Details of package fake-hwclock in sid
Re: NTP force sync option #46
-
- PLi® Core member
- 68,609 posts
+1,739
Excellent
Posted 17 August 2021 - 19:11
Possible, but that doesn't solve the problem you have with a oscam from streamboard. It will also refuse a time update with a fake-hwclock, if the box had been off overnight.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
