chrony @4.2, Ventura, daemondo (in base) does not start chrony daemon after a system restart

[snowflake (Dave Evans)]

I've been using Ventura for several months. chrony has not given any problems in that time.

Yesterday, I upgraded Ventura to this version:

ProductName:		macOS
ProductVersion:		13.1
BuildVersion:		22C5033e

After restarting, I found that the chrony daemon had not started. I started it manually with port load chronyand all was well until the next restart.

I noticed that putting the system to sleep did not restart chrony when reawakening. Normally, this would send a network changed event to daemondo which causes it to reload chrony.

In System Preferences there are many instances of daemondo in the Login Items preference. They are all enabled.

I am currently using port version 2.8.99 [564c146af7cdc9f3be0152204367ab60ed208129/macports-base]

[ryandesign (Ryan Carsten Schmidt)]

Reminder to avoid disclosing information about pre-release versions of macOS: wiki:FAQ#prerelease

[snowflake (Dave Evans)]

I installed a release version of Venture, macOS 13.2.1, on my release partition and chrony now starts after a reboot.

I now have macOS beta 13.3 on my beta partition and chrony is also working on it.

[jmroot (Joshua Root)]

Closing as per comment:3.