430 prepare timesync.sh chronyd support #1739
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Details:
Type: Enhancement
Impact: Low
Reference to related issue (URL):
#1622 and #1623
Created CentOS 6 (init-based) and CentOS 7 (systemd-based) VMs in Virtualbox and tested rescue ISOs for all 4 TIMESYNC options on both systems.
Added chrony support so that newer systems that ship with chrony vs ntp, like RHEL/CentOS 7, are able to sync system time during rescue/restore.
430_prepare_timesync.sh will also not update ROOTFS_DIR/etc/inittab if the system is systemd-based.
While I was here, I updated the options for rdate to include -l (use syslog) and -p (print remote system time) so that rdate output is as close to the other 3 TIMESYNC options.