Date: Wed, 04 Nov 2015 19:17:02 -0700 From: Ian Lepore <ian@freebsd.org> To: Doug Hardie <bc979@lafn.org>, freebsd-stable <freebsd-stable@freebsd.org> Cc: current@freebsd.org Subject: Re: Segmentation fault running ntpd Message-ID: <1446689822.91534.386.camel@freebsd.org> In-Reply-To: <3178C067-4C33-49E1-9ED7-501EDEFDB256@lafn.org> References: <20150718120956.GC1155@albert.catwhisker.org> <86pozwbvds.fsf@desk.des.no> <20151030113449.GF13438@albert.catwhisker.org> <e7dd89564e34d1cc0b8e61d64f8e1d2b@mailbox.ijs.si> <20151101093116.GA5457@voyager> <9145a2d0228d9d025b2b0b6b5612726c@mailbox.ijs.si> <3178C067-4C33-49E1-9ED7-501EDEFDB256@lafn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2015-11-04 at 17:49 -0800, Doug Hardie wrote: > > On 4 November 2015, at 08:15, Mark Martinec < > > Mark.Martinec+freebsd@ijs.si> wrote: > > > > Upgrading 10.2-RELEASE-p6 to 10.2-RELEASE-p7 now solved ntpd > > crashes > > (apparently fixed by: FreeBSD Errata Notice FreeBSD-EN-15:20.vm). > > > > Thanks!!! > > > > Mark > > > > ntpdc hangs when you do a peers command on 9.3. Eventually it > returns a no response from the server. However, ntpq works just fine > and nagios is able to get the status without problems. Both of those > did not work properly before. > > — Doug The protocol used by ntpdc is no longer supported by ntpd, and that change came along for the ride with the security and bugfixes that were recently merged back to the 9 and 10 branches. Everything that can be done with ntpdc on older releases can now be done using ntpq with the new release. The ntpdc program itself is still present so that you can still administer remote servers running older code, since they won't be able to do everything via ntpq. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1446689822.91534.386.camel>