At what time intervals does ntpd update the time?
I'm running the latest ntpd.
When I start ntpd my system time synchronizes with ntp server's ntp. After synchronizing I changed my system time manually using date command date -s '1997-02-22 12:00:00'
My system time got changed as per the date command.
NTPD is still running, I want to know at what time interval my system time will sync with the internet via ntp.
ntp
edited Jul 13 '16 at 9:59
Zanna
50.1k13131240
asked Jul 13 '16 at 6:32
Sharath Manchala
2415
add a comment |
I'm running the latest ntpd.
When I start ntpd my system time synchronizes with ntp server's ntp. After synchronizing I changed my system time manually using date command date -s '1997-02-22 12:00:00'
My system time got changed as per the date command.
NTPD is still running, I want to know at what time interval my system time will sync with the internet via ntp.
ntp
edited Jul 13 '16 at 9:59
Zanna
50.1k13131240
asked Jul 13 '16 at 6:32
Sharath Manchala
2415
add a comment |
I'm running the latest ntpd.
When I start ntpd my system time synchronizes with ntp server's ntp. After synchronizing I changed my system time manually using date command date -s '1997-02-22 12:00:00'
My system time got changed as per the date command.
NTPD is still running, I want to know at what time interval my system time will sync with the internet via ntp.
ntp
edited Jul 13 '16 at 9:59
Zanna
50.1k13131240
asked Jul 13 '16 at 6:32
Sharath Manchala
2415
I'm running the latest ntpd.
When I start ntpd my system time synchronizes with ntp server's ntp. After synchronizing I changed my system time manually using date command date -s '1997-02-22 12:00:00'
My system time got changed as per the date command.
NTPD is still running, I want to know at what time interval my system time will sync with the internet via ntp.
ntp
ntp
edited Jul 13 '16 at 9:59
Zanna
50.1k13131240
asked Jul 13 '16 at 6:32
Sharath Manchala
2415
edited Jul 13 '16 at 9:59
Zanna
50.1k13131240
asked Jul 13 '16 at 6:32
Sharath Manchala
2415
edited Jul 13 '16 at 9:59
Zanna
50.1k13131240
edited Jul 13 '16 at 9:59
Zanna
50.1k13131240
edited Jul 13 '16 at 9:59
Zanna
50.1k13131240
50.1k13131240
asked Jul 13 '16 at 6:32
Sharath Manchala
2415
asked Jul 13 '16 at 6:32
Sharath Manchala
2415
asked Jul 13 '16 at 6:32
Sharath Manchala
2415
2415
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Generally we can also call it as polling interval and minimum time is 64 sec and maximum time 1024 sec , but you can still change it as you want by doing changes at /etc/ntp.conf.
minpoll minpoll
maxpoll maxpoll
These options specify the minimum and
maximum poll intervals for NTP messages, in seconds as a power of two.
The maximum poll interval defaults to 10 (1,024 s), but can be
increased by the maxpoll option to an upper limit of 17 (36.4 h). The
minimum poll interval defaults to 6 (64 s), but can be decreased by
the minpoll option to a lower limit of 3 (8 s). These option are valid
only with the server and peer commands.
answered Jul 13 '16 at 6:58
rɑːdʒɑ
56.9k84216301
thanks Raja. I'm seeing one more issue.My ntpd is crashing with the error message "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled ". Do you have any idea regarding this
– Sharath Manchala
Jul 13 '16 at 7:12
1
@SharathManchala forums.freebsd.org/threads/53885
– rɑːdʒɑ
Jul 13 '16 at 7:15
@SharathManchala novell.com/coolsolutions/feature/15345.html
– rɑːdʒɑ
Jul 13 '16 at 7:15
my understanding was if we dont configure minpoll and maxpoll then it sets default values as 64s and 1024s(17 mins). Is it dam sure that within this interval time will get sync from server.
– Sharath Manchala
Jul 13 '16 at 9:44
add a comment |
What is is saying is "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled " because of event that happened ntpd stopped. The event is you changing the time of the clock. NTPD is angry that you changed the time of the clock too far away form the time that it knows, and NTPD wants you to make sure you get the time within within 1000s or 16 minutes. NTPD does not like having to jump too far. For example if you computer did not have a internet connection for a long time and then you reconnected it, it would not jump to the correct time right away, but slowly get the time closer until it was correct.
answered Dec 13 '18 at 18:48
doanerock
111
1
This RH Q&A discusses this a little serverfault.com/q/847998
– jdv
Dec 13 '18 at 19:07
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f798023%2fat-what-time-intervals-does-ntpd-update-the-time%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Generally we can also call it as polling interval and minimum time is 64 sec and maximum time 1024 sec , but you can still change it as you want by doing changes at /etc/ntp.conf.
minpoll minpoll
maxpoll maxpoll
These options specify the minimum and
maximum poll intervals for NTP messages, in seconds as a power of two.
The maximum poll interval defaults to 10 (1,024 s), but can be
increased by the maxpoll option to an upper limit of 17 (36.4 h). The
minimum poll interval defaults to 6 (64 s), but can be decreased by
the minpoll option to a lower limit of 3 (8 s). These option are valid
only with the server and peer commands.
answered Jul 13 '16 at 6:58
rɑːdʒɑ
56.9k84216301
thanks Raja. I'm seeing one more issue.My ntpd is crashing with the error message "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled ". Do you have any idea regarding this
– Sharath Manchala
Jul 13 '16 at 7:12
1
@SharathManchala forums.freebsd.org/threads/53885
– rɑːdʒɑ
Jul 13 '16 at 7:15
@SharathManchala novell.com/coolsolutions/feature/15345.html
– rɑːdʒɑ
Jul 13 '16 at 7:15
my understanding was if we dont configure minpoll and maxpoll then it sets default values as 64s and 1024s(17 mins). Is it dam sure that within this interval time will get sync from server.
– Sharath Manchala
Jul 13 '16 at 9:44
add a comment |
Generally we can also call it as polling interval and minimum time is 64 sec and maximum time 1024 sec , but you can still change it as you want by doing changes at /etc/ntp.conf.
minpoll minpoll
maxpoll maxpoll
These options specify the minimum and
maximum poll intervals for NTP messages, in seconds as a power of two.
The maximum poll interval defaults to 10 (1,024 s), but can be
increased by the maxpoll option to an upper limit of 17 (36.4 h). The
minimum poll interval defaults to 6 (64 s), but can be decreased by
the minpoll option to a lower limit of 3 (8 s). These option are valid
only with the server and peer commands.
answered Jul 13 '16 at 6:58
rɑːdʒɑ
56.9k84216301
thanks Raja. I'm seeing one more issue.My ntpd is crashing with the error message "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled ". Do you have any idea regarding this
– Sharath Manchala
Jul 13 '16 at 7:12
1
@SharathManchala forums.freebsd.org/threads/53885
– rɑːdʒɑ
Jul 13 '16 at 7:15
@SharathManchala novell.com/coolsolutions/feature/15345.html
– rɑːdʒɑ
Jul 13 '16 at 7:15
my understanding was if we dont configure minpoll and maxpoll then it sets default values as 64s and 1024s(17 mins). Is it dam sure that within this interval time will get sync from server.
– Sharath Manchala
Jul 13 '16 at 9:44
add a comment |
Generally we can also call it as polling interval and minimum time is 64 sec and maximum time 1024 sec , but you can still change it as you want by doing changes at /etc/ntp.conf.
minpoll minpoll
maxpoll maxpoll
These options specify the minimum and
maximum poll intervals for NTP messages, in seconds as a power of two.
The maximum poll interval defaults to 10 (1,024 s), but can be
increased by the maxpoll option to an upper limit of 17 (36.4 h). The
minimum poll interval defaults to 6 (64 s), but can be decreased by
the minpoll option to a lower limit of 3 (8 s). These option are valid
only with the server and peer commands.
answered Jul 13 '16 at 6:58
rɑːdʒɑ
56.9k84216301
Generally we can also call it as polling interval and minimum time is 64 sec and maximum time 1024 sec , but you can still change it as you want by doing changes at /etc/ntp.conf.
minpoll minpoll
maxpoll maxpoll
These options specify the minimum and
maximum poll intervals for NTP messages, in seconds as a power of two.
The maximum poll interval defaults to 10 (1,024 s), but can be
increased by the maxpoll option to an upper limit of 17 (36.4 h). The
minimum poll interval defaults to 6 (64 s), but can be decreased by
the minpoll option to a lower limit of 3 (8 s). These option are valid
only with the server and peer commands.
answered Jul 13 '16 at 6:58
rɑːdʒɑ
56.9k84216301
answered Jul 13 '16 at 6:58
rɑːdʒɑ
56.9k84216301
answered Jul 13 '16 at 6:58
rɑːdʒɑ
56.9k84216301
answered Jul 13 '16 at 6:58
rɑːdʒɑ
56.9k84216301
56.9k84216301
thanks Raja. I'm seeing one more issue.My ntpd is crashing with the error message "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled ". Do you have any idea regarding this
– Sharath Manchala
Jul 13 '16 at 7:12
1
@SharathManchala forums.freebsd.org/threads/53885
– rɑːdʒɑ
Jul 13 '16 at 7:15
@SharathManchala novell.com/coolsolutions/feature/15345.html
– rɑːdʒɑ
Jul 13 '16 at 7:15
my understanding was if we dont configure minpoll and maxpoll then it sets default values as 64s and 1024s(17 mins). Is it dam sure that within this interval time will get sync from server.
– Sharath Manchala
Jul 13 '16 at 9:44
add a comment |
thanks Raja. I'm seeing one more issue.My ntpd is crashing with the error message "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled ". Do you have any idea regarding this
– Sharath Manchala
Jul 13 '16 at 7:12
1
@SharathManchala forums.freebsd.org/threads/53885
– rɑːdʒɑ
Jul 13 '16 at 7:15
@SharathManchala novell.com/coolsolutions/feature/15345.html
– rɑːdʒɑ
Jul 13 '16 at 7:15
my understanding was if we dont configure minpoll and maxpoll then it sets default values as 64s and 1024s(17 mins). Is it dam sure that within this interval time will get sync from server.
– Sharath Manchala
Jul 13 '16 at 9:44
thanks Raja. I'm seeing one more issue.My ntpd is crashing with the error message "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled ". Do you have any idea regarding this
– Sharath Manchala
Jul 13 '16 at 7:12
thanks Raja. I'm seeing one more issue.My ntpd is crashing with the error message "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled ". Do you have any idea regarding this
– Sharath Manchala
Jul 13 '16 at 7:12
1
1
@SharathManchala forums.freebsd.org/threads/53885
– rɑːdʒɑ
Jul 13 '16 at 7:15
@SharathManchala forums.freebsd.org/threads/53885
– rɑːdʒɑ
Jul 13 '16 at 7:15
@SharathManchala novell.com/coolsolutions/feature/15345.html
– rɑːdʒɑ
Jul 13 '16 at 7:15
@SharathManchala novell.com/coolsolutions/feature/15345.html
– rɑːdʒɑ
Jul 13 '16 at 7:15
my understanding was if we dont configure minpoll and maxpoll then it sets default values as 64s and 1024s(17 mins). Is it dam sure that within this interval time will get sync from server.
– Sharath Manchala
Jul 13 '16 at 9:44
my understanding was if we dont configure minpoll and maxpoll then it sets default values as 64s and 1024s(17 mins). Is it dam sure that within this interval time will get sync from server.
– Sharath Manchala
Jul 13 '16 at 9:44
add a comment |
What is is saying is "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled " because of event that happened ntpd stopped. The event is you changing the time of the clock. NTPD is angry that you changed the time of the clock too far away form the time that it knows, and NTPD wants you to make sure you get the time within within 1000s or 16 minutes. NTPD does not like having to jump too far. For example if you computer did not have a internet connection for a long time and then you reconnected it, it would not jump to the correct time right away, but slowly get the time closer until it was correct.
answered Dec 13 '18 at 18:48
doanerock
111
1
This RH Q&A discusses this a little serverfault.com/q/847998
– jdv
Dec 13 '18 at 19:07
add a comment |
What is is saying is "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled " because of event that happened ntpd stopped. The event is you changing the time of the clock. NTPD is angry that you changed the time of the clock too far away form the time that it knows, and NTPD wants you to make sure you get the time within within 1000s or 16 minutes. NTPD does not like having to jump too far. For example if you computer did not have a internet connection for a long time and then you reconnected it, it would not jump to the correct time right away, but slowly get the time closer until it was correct.
answered Dec 13 '18 at 18:48
doanerock
111
1
This RH Q&A discusses this a little serverfault.com/q/847998
– jdv
Dec 13 '18 at 19:07
add a comment |
What is is saying is "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled " because of event that happened ntpd stopped. The event is you changing the time of the clock. NTPD is angry that you changed the time of the clock too far away form the time that it knows, and NTPD wants you to make sure you get the time within within 1000s or 16 minutes. NTPD does not like having to jump too far. For example if you computer did not have a internet connection for a long time and then you reconnected it, it would not jump to the correct time right away, but slowly get the time closer until it was correct.
answered Dec 13 '18 at 18:48
doanerock
111
What is is saying is "event at 1020 0.0.0.0 0617 07 panic_stop +611777596 s; set clock manually within 1000 s. event at 1020 0.0.0.0 061d 0d kern kernel time sync disabled " because of event that happened ntpd stopped. The event is you changing the time of the clock. NTPD is angry that you changed the time of the clock too far away form the time that it knows, and NTPD wants you to make sure you get the time within within 1000s or 16 minutes. NTPD does not like having to jump too far. For example if you computer did not have a internet connection for a long time and then you reconnected it, it would not jump to the correct time right away, but slowly get the time closer until it was correct.
answered Dec 13 '18 at 18:48
doanerock
111
answered Dec 13 '18 at 18:48
doanerock
111
answered Dec 13 '18 at 18:48
doanerock
111
answered Dec 13 '18 at 18:48
doanerock
111
111
1
This RH Q&A discusses this a little serverfault.com/q/847998
– jdv
Dec 13 '18 at 19:07
add a comment |
1
This RH Q&A discusses this a little serverfault.com/q/847998
– jdv
Dec 13 '18 at 19:07
1
1
This RH Q&A discusses this a little serverfault.com/q/847998
– jdv
Dec 13 '18 at 19:07
This RH Q&A discusses this a little serverfault.com/q/847998
– jdv
Dec 13 '18 at 19:07
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f798023%2fat-what-time-intervals-does-ntpd-update-the-time%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
