Chrony is not restarted when new configuration is deployed.

[jamesfreeman959]

Love your code - it has been so useful - however just spotted something this morning. When the time synchronization service is set to chrony, and a new configuration file is deployed, there is no handler to restart chrony, thus the new configuration is not picked up. Is this by design? A handler to restart this in the event that the config changes would be excellent. I can submit some code or a pull request to help if you would like.

Many thanks

James

[florianutz]

Hi James, thank you for your feedback. You're right. There is currently no handler for this service. I will add this to one of the next versions. You are also invited to submit a pull request to resolve this issue.

Regards Florian