Lines Matching refs:ntpd

7 The NTP software protocol and its reference implementation, ntpd, were
19 Whenever a leap second is to be handled ntpd either:
57 the Windows port of ntpd provides a workaround where the system time is
67 recently been implemented in ntpd.  This means that to insert a leap second
74 During the period while the leap smear is being performed, ntpd will include
113 Here is some historical background for ntpd, related to smearing/slewing
116 Up to ntpd 4.2.4, if kernel support for leap seconds was either not
117 available or was not enabled, ntpd didn't care about the leap second at all.
118 So if ntpd was run with -x and thus kernel support wasn't used, ntpd saw a
120 time by -1 s a few minutes later.  However, 'ntpd -x' does not step the time
131 In ntpd 4.2.6 some code was added which let ntpd step the time at UTC
133 Unfortunately this also happened if ntpd was started with -x, so the folks
134 who expected that the time was never stepped when ntpd was run with -x found
136 learn that there were even some folks who patched ntpd to get the 4.2.4
141 i.e. ntpd with -x would still step the time.  This has only recently been
142 fixed in the current ntpd stable code, but this fix is only available with a
143 certain patch level of ntpd 4.2.8.
147 version of ntpd installed on each of their systems.  If it's still 4.2.4 be
148 sure to start the client ntpd with -x.  If it's 4.2.6 or 4.2.8 it won't work
149 anyway except if you had a patched ntpd version instead of the original
151 run ntpd with -x and get the desired result, so you'd still have the
153 that runs ntpd.
160 version of ntpd is installed on a client machine, it just works, and it even
165 the -x approach.  The current leap second code in ntpd determines the point
172 by -x in ntpd 4.2.4, so if users could accept the old behavior they would
176 smear support currently implemented in ntpd does not affect the internal
179 functionality of ntpd is not accidentally broken.  Also peer packets
202 - Even if ntpd has been compiled to enable leap smearing support, leap
245 When ntpd starts and a smear interval has been specified then a log message
248  ntpd[31120]: config: leap smear interval 86400 s
250 While ntpd is running with a leap smear interval specified the command:
258 version="ntpd 4.2.8p3-RC1@1.3349-o Mon Jun 22 14:24:09 UTC 2015 (26)",