Network time won't synchronize clock at boot

[Giova84]

Since i have installed hrev45110, at every startup i found that the clock is one hour behind (with Haiku Alpha 4.1 i don't have this issue). In Time Preference time is set correctly to my time zone. If i click on "Synchronize" in the "Network Time" tab, clock will show the correct time, but if i select "Synchronize at boot", at the boot time the clock is not synchronized.

[diver]

Synchronize at boot has never worked for me since it was added in hrev41956. Maybe Time should wait for an active network interface before trying to sync?

[leavengood]

I'm pretty sure I tested that, but it may work on some systems but not others if there is a race condition in it running before a network is up. I think we could change Time to wait for a network with a reasonable timeout when the --update command-line option is provided. Or a --boot option could be added to turn on this behavior.

[anevilyak]

Replying to leavengood:

I'm pretty sure I tested that, but it may work on some systems but not others if there is a race condition in it running before a network is up. I think we could change Time to wait for a network with a reasonable timeout when the --update command-line option is provided. Or a --boot option could be added to turn on this behavior.

What would be more ideal is to use BNetworkRoster/BNetworkDevice to watch for interface changes in order to actually know when the device is up and in a usable state. That rules out time-based races entirely.

[axeld]

It could simply keep trying for a while if the synchronization fails. It should just not keep the system from booting in case it's currently doing that.

[leavengood]

Taking ownership since I added the feature to Time. I may not get around to fixing this for a while though.

[waddlesplash]

Fixed in hrev53049.

[nielx]

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone