-
-
Notifications
You must be signed in to change notification settings - Fork 139
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.
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
timedatectl support #377
Labels
Comments
I would use it, especially if this eliminates the need for a separate time zone module. |
The only sensible use cases would be |
jcpunk
added a commit
to jcpunk/puppet-systemd
that referenced
this issue
May 22, 2024
jcpunk
added a commit
to jcpunk/puppet-systemd
that referenced
this issue
May 24, 2024
jcpunk
added a commit
to jcpunk/puppet-systemd
that referenced
this issue
May 24, 2024
jcpunk
added a commit
to jcpunk/puppet-systemd
that referenced
this issue
May 27, 2024
jcpunk
added a commit
to jcpunk/puppet-systemd
that referenced
this issue
May 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
What behaviour did you expect instead
I'm wondering if it would make sense to add the
timedatectl set-timezone
andtimedatectl set-local-rtc
feature set to this module.Output log
Any additional information you'd like to impart
https://www.freedesktop.org/software/systemd/man/timedatectl.html
The text was updated successfully, but these errors were encountered: