Lines Matching full:clients

26 NTP servers also pass a leap second warning flag down to their clients via
27 the normal NTP packet exchange, so clients also become aware of an
60 Thus it is not required to use a smearing NTP server for Windows clients,
69 sent to its clients, so that after some predefined interval the leap second
71 e.g. several hours, so that NTP clients can easily follow the clock drift
79 With this approach the time an NTP server sends to its clients still matches
86 Of course, clients which receive the "smeared" time from an NTP server don't
88 just transparent to the clients, and the clients don't even notice there's a
159 NTP clients can follow the smeared time it doesn't matter at all which
163 Since all clients follow the same smeared time the time difference between
164 the clients during the smear interval is as small as possible, compared to
178 *to clients* are modified by the smear offset, so this makes sure the basic
191 project.  There would be a high risk that NTP clients get the time from a
194 configured on time servers providing dedicated clients with time, if all
195 those clients can accept smeared time.
207 is applied too quickly for clients to follow.  86400s (1 day) is a good
214 requests.  Since the leap second is applied gradually the clients don't even
216 message or similar related to the leap second be visible on the clients.
218 - Since clients don't (and must not) become aware of the leap second at all,
219 clients getting the time from a smearing NTP server MUST NOT be configured
225 - Clients MUST NOT be configured to poll both smearing and non-smearing NTP
240 hours' long.  With shorter values clients may not be able to follow the
270 used to monitor if and how the time sent to clients is smeared.  With a