NTP long jump is enabled - Fix for 5007 #17195
Open
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.
…k time even when NTP is synchronized to it
Root-Cause: NTP long jump is disabled in the NTP daemon
What I did: Enabled NTP longjump so that sonic device clock is synchronized with NTP server
Why I did it
As NTP long jump is disabled causing system clock to stay away from actual time even when NTP server is configured
Work item tracking
How I did it
Reenabled NTP long jump in code
How to verify it
Description for the changelog
NTP long jump is enabled in NTP config file when it is restarted by ntp-config.sh file
Issue Link: #5007