This is different from bug #01 where it would never work because of a design issue.cherowley wrote:Martinus wrote:Current bugstatus:
- Bug #01 FIXED in R138 : Clock event at system boot issues
quote]
I'm not sure if it's related to the above but I'm still getting the problem whereby sometimes the clock is NOT set after boot in version 140.
Can't detect a pattern - seems random.
Sometimes enabling/disabling the use ntp feature and saving a few times with get it working..
Sometimes the NTP server does not reply, but in my network this is a rare condition. I'll see if a simple retry mechanism can be implemented to avoid failure on a single missed packet... Listed as bug #10, intermittent failure getting NTP time.