On Thu, 1 Apr 2010, Savvas Radevic wrote: > It looks like that "Correctly apply +-500 ppm sanity check" applied for > version 1.28 is causing problems. > Also, bug #559882 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559882 ) > seems to be a duplicate of this one.
Question for James: It is really useful to have those "sanity checks" at all? In my case, the very reason I use adjtimex is that my computer has a too big clock skew that may not be fixed just by using ntpd (it's an old powerpc Mac Mini). As ntpd already refuses to work corretly outside the +-500 ppm margin, I would expect adjtimex not to have any sanity checks at all, or, at least, be a *lot* more permissive. What about +-5000 ppm, for example? The typical clock skew for a Mac Mini is about 2800 ppm. A sanity check lower than that would force me to do special things to be able to use this package. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
