> > And so on. Adjustment delta grows and grows, strace shows that adjtimex > > returns TIME_BAD (5), and ntpdate -q shows that local clock is in no way > > synchronized with uplevel server. Which as a result makes openntpd > > unusable. I see there is some patch from RedHat to make openntpd use > > Linux adjtimex syscall. May be it is worth trying ? > > You have a url to that patch?
In response to Brad Knowles' "OpenNTPd Considered Harmful" article <http://web.archive.org/web/20050304032724/http://bradknowles.typepad.com/considered_harmful/2004/09/openntpd.html>, the maintainer of portable OpenNTPD posted a blog entry <http://www.advogato.org/person/dtucker/diary.html?start=52> which links to a patch that makes OpenNTPD use the adjtimex system call <http://www.zip.com.au/~dtucker/openntpd/patches/openntpd-3.6.1p1-linux-adjtimex.patch>. There are also other patches in that directory that appear to be for later OpenNTPD releases. -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
signature.asc
Description: This is a digitally signed message part
