Opened 2 years ago
Last modified 13 months ago
#66122 closed defect
chrony @ 4.2, Ventura, daemondo (in base) does not start chrony daemon after a system restart — at Initial Version
| Reported by: | snowflake (Dave Evans) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 2.8.99 |
| Keywords: | ventura | Cc: | |
| Port: | chrony |
Description
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
Note: See
TracTickets for help on using
tickets.