From owner-freebsd-bugs@freebsd.org Fri Feb 26 04:35:12 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20160AB4B63 for ; Fri, 26 Feb 2016 04:35:12 +0000 (UTC) (envelope-from johnandsara2@cox.net) Received: from eastrmfepo103.cox.net (eastrmfepo103.cox.net [68.230.241.215]) by mx1.freebsd.org (Postfix) with ESMTP id C791F139B for ; Fri, 26 Feb 2016 04:35:11 +0000 (UTC) (envelope-from johnandsara2@cox.net) Received: from eastrmimpo305.cox.net ([68.230.241.237]) by eastrmfepo103.cox.net (InterMail vM.8.01.05.15 201-2260-151-145-20131218) with ESMTP id <20160226043511.ITNS30397.eastrmfepo103.cox.net@eastrmimpo305.cox.net> for ; Thu, 25 Feb 2016 23:35:11 -0500 Received: from [192.168.3.15] ([72.219.207.23]) by eastrmimpo305.cox.net with cox id NsbA1s0070WpXgw01sbA7M; Thu, 25 Feb 2016 23:35:10 -0500 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020202.56CFD5FE.0143, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.1 cv=bqfCBSqi c=1 sm=1 tr=0 a=mYpcIwsqoufCTD7dyaqayA==:117 a=mYpcIwsqoufCTD7dyaqayA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=8nJEP1OIZ-IA:10 a=6I5d2MoRAAAA:8 a=pGLkceISAAAA:8 a=AazEzAPzbedPSS8cmkwA:9 a=wPNLvfGTeEIA:10 X-CM-Score: 0.00 Authentication-Results: cox.net; none Message-ID: <56CFD143.1070405@cox.net> Date: Thu, 25 Feb 2016 23:14:59 -0500 From: anonymous User-Agent: Thunderbird 2.0.0.24 (X11/20100228) MIME-Version: 1.0 To: bugzilla-noreply@freebsd.org CC: freebsd-bugs@FreeBSD.org Subject: Re: [Bug 202212] ntpd always crash with attached config References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Feb 2016 04:35:12 -0000 bugzilla-noreply@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202212 > > rozhuk.im@gmail.com changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|New |Closed > Resolution|--- |FIXED > > --- Comment #2 from rozhuk.im@gmail.com --- > 10.3 Beta 1 - OK. > another problem i see (though i was years ago i ran ntp) i read your config it names many servers and clients in configuration another problem with ntp is the author requested that people ONLY configure as clients never server UNLESS they are serious and also have the proper hardware (a radio clock or better) most ntp sites request only client connections, only if permission is given ahead of time, and of course to not use ntpq in ways to bother the servers that's another problem with NTP is that it's really not meant for "setting time for better web acess for http hackers, cause web servers need good time", nor updating ones time for bettter (city) webcam synchronization: it's really more for keeping time seriously between radio clocks that *allows* those interested in time keeping to be a QUIET client of. and automated "rdate" script is all a client needs or should use, unless interested in the science of NTP and participating within the boundaries -------------------- doubless your either a radio clock owner or the people who are have found ways to filter out misconfigured clients by now, as ntp has been long and running some time now. but maybe they haven't: so please be care making config files, do not bother serious time keepers with bsd chaos