Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Chrony is not restarted when new configuration is deployed. #48

Open
jamesfreeman959 opened this issue Nov 5, 2019 · 1 comment
Open

Chrony is not restarted when new configuration is deployed. #48

jamesfreeman959 opened this issue Nov 5, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@jamesfreeman959
Copy link

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
Copy link
Owner

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

@florianutz florianutz added the enhancement New feature or request label Feb 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jamesfreeman959 @florianutz