Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
OpenNTPD 3.6.1p1 was released yesterday. ChangeLog: ftp://ftp.openbsd.org/pub/OpenBSD/OpenNTPD/ChangeLog Primary Mirror: ftp://ftp.openbsd.org/pub/OpenBSD/OpenNTPD/
Created an attachment (id=45729) [details] openntpd-3.6.1_p1.ebuild just a bump from 3.6p1 with the following changes: - Removed manpage patch, was fixed upstream - Changed URL, location has changed from .../portable/ to .../
Created an attachment (id=45731) [details] files/3.6.1_p1-ntpd.8.patch new manpage patch which removes _new_ openbsd specific text
Created an attachment (id=45732) [details] openntpd-3.6.1_p1.ebuild new ebuild which uses the new files/3.6.1_p1-ntpd.8.patch
awesome, i didnt have to do any work :) added to cvs, thanks !
hehe, no problem :) FYI: There seems to be a little problem if you have "server host1" in your config and on host1 there is no ntpd listening. OpenNTPD then uses all your CPU. I contacted Daren Tucker, as he does the portable stuff an this error does not occur on openbsd.
I have a patch for that problem here.
Created an attachment (id=45876) [details] files/3.6.1_p1-pollerr.patch This patch fixes the errorhandling if one server is not reachable, CPU consumption stays normal and does not rise to 100%. Fix is from dtucker@openbsd.org.
Created an attachment (id=45877) [details] openntpd-3.6.1_p1.ebuild
Well, this should be -r1 perhaps, as the original version is in tree
Created an attachment (id=45879) [details] 3.6.1_p1-pollerr.patch Bigger diff which fixes all occurences of such a problem where pollerr isnt checked. From dtucker@openbsd.org again.
On the good news front : this version should support the "-s" startup option to safely set time at startup if difference >=180sec. Allows openntpd users to get rid of ntp-client...
yes, that works without problems. Just add -s to $NTPD_OPTS
fixed in 3.6.1_p1-r1 please file new bugs in the future ;)