Richard Megginson
Richard Megginson
> Some systems don't have sysconfig, e.g. on Debian the options are in `/etc/default/chrony`, so the I think the name should be general enough to work on all potentially supported...
How can we test this? e.g. add or modify a test in https://github.com/linux-system-roles/timesync/tree/main/tests ?
I had to close and reopen the PR to trigger checks - not sure why the checks were not being run . . .
Need a test for this in tests/
> Clients normally accept leap second information from their servers. The leapsectz option is mainly useful to set the TAI-UTC offset of the system clock. A potential issue is incompatibility...
> > Clients normally accept leap second information from their servers. The leapsectz option is mainly useful to set the TAI-UTC offset of the system clock. A potential issue is...
ping - any update?
ping - any update? Can we close this?
Do we need this PR at all? Can you use `timesync_chrony_custom_settings` https://github.com/linux-system-roles/timesync#role-variables: ```yaml timesync_chrony_custom_settings: - "leapsectz right/UTC" ``` ?