Hi Dererk,
I'm afraid it's not yet so easy to debug on kfreebsd-* flavors, as the port lack most common (unless for me) debugging tools, therefore, you might understand it's not a matter like " noone cares".
Ok, so I understand you are having problems debugging on kfreebsd for reasons that are beyond you. I would say this is even more reason to exclude kfreebsd from the build until the situation gets better.
On the other hand, against what common sense could tell you, openntpd doesn't adjust the system's clock rate (it uses adjtime()), although Its something you take for granted when you install a software like this, it really ends up being more painful than useful for end-users that "just want their sandboxes clocked" (#306106).
I understand that there may be other problems with the openntpd package, but I do not see them tagged 'grave' at this point. Therefore I do not think that bringing them into discussion here will change anything w.r.t. to this bug.
Unfortunately, the only patch I could manage to get running on replacing adjtime() with adjtimex() didn't work as expected.
[ OT for this bug ] Do you mean this patch? http://dtucker.freeshell.org/openntpd/patches/openntpd-3.6.1p1-linux-adjtimex.patch What is the problem with it? Regards, Robbert -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
