On 02/09/2015 11:49 AM, Miroslav Lichvar wrote:
> Should be leap seconds threated as a normal offset and not corrected
> by step when the threshold is larger than 1.0? Should there be a
> separate option for them?
I have practical use cases for *both* variants (*), so I'ld prefer being
given the possibility to do either. Whether I have an *option* to do
that or can effect it by *config* (setting the limit, which is otherwise
unused) is, however, secondary.
FWIW, I could also imagine people to be interested in having leap
seconds handled by the *kernel* even when steps are generally disabled -
*especially* if the method *how* a kernel handles them is going to
become a zoo of variants outside ntpd's control in the future ...
(*)
a) Even leap seconds should be *slews* when the reason to disable steps
is that some software cannot handle such behavior of the OS clock.
b) We're distributing appliances where the ntpd on the appliance losing
sync leads to alerts getting raised with the local admin. The server
has steps disabled so as to prevent clients losing sync over a step.
However, the clients can and will process leap seconds "normally", so
the server should do the same.
Regards,
J. Bern
--
*NEU* - NEC IT-Infrastruktur-Produkte im <http://www.linworks-shop.de/>:
Server--Storage--Virtualisierung--Management SW--Passion for Performance
Jochen Bern, Systemingenieur --- LINworks GmbH <http://www.LINworks.de/>
Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt
PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27
Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202
Unternehmenssitz Weiterstadt, Geschäftsführer Metin Dogan, Oliver Michel
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
