Bug 1387958 - minpoll and maxpoll only communication but not really synchronize,isn't it?
Summary: minpoll and maxpoll only communication but not really synchronize,isn't it?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ntp
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Miroslav Lichvar
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-24 03:45 UTC by muahao
Modified: 2016-10-24 06:35 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-24 06:35:46 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description muahao 2016-10-24 03:45:03 UTC
## MY QUESTION:minpoll and maxpoll only communication but not really synchronize,isn't it?

Hello my friends,I have a problem want to know,why ntp syncorized from uppper stratum NTP server so slowly??

minpoll ,maxpoll at my view is not really "synchronize and do adjust system's time to correct ",but only "communication with upper NTP server and after almost 10-20mins really do synchronize and adjust system's time by upper NTP server"

__My question is can I adjust my client server's parameter to make my client to synchronize from upper NTP server frequently?__


## Steps to Reproduce:
Bellow is just a test ,so only one NTP server was configured,just want to know NTP's synchronization behavior

NOW:


	#date
	Mon Oct 24 10:54:55 CST 2016


reset date time:


	#date -s "2016-10-24 10:52"


after about 10min:


	#ntpq -np
	     remote           refid      st t when poll reach   delay   offset  jitter
	==============================================================================
	10.101.242.8    10.233.7.230     3 u    4   64  377    0.102  175930.   0.070



after about 10min:



	#ntpq -np
     remote           refid      st t when poll reach   delay   offset  jitter
	==============================================================================
	*10.101.242.8    10.233.7.230     3 u    4   64  377    0.102  175930.   0.070



after about  10min:

time was adjusted by NTP

Comment 2 Miroslav Lichvar 2016-10-24 06:35:46 UTC
There is an option called "tinker stepout" (described in the ntp_misc(5) man page), which controls how long ntpd waits before stepping the clock. The default value is 900 seconds (15 minutes). It's mainly useful to avoid steps when the network is congested and the NTP measurements include a large error. If you need a faster reaction, you can add "tinker stepout 300" or similar to ntp.conf.


Note You need to log in before you can comment on or make changes to this bug.