Date: Thu, 25 Feb 2016 22:32:33 -0500 From: anonymous <johnandsara2@cox.net> To: bugzilla-noreply@freebsd.org Cc: freebsd-bugs@FreeBSD.org Subject: Re: [Bug 202212] ntpd always crash with attached config Message-ID: <56CFC751.7030806@cox.net> In-Reply-To: <bug-202212-8-7qahF4IwV6@https.bugs.freebsd.org/bugzilla/> References: <bug-202212-8@https.bugs.freebsd.org/bugzilla/> <bug-202212-8-7qahF4IwV6@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > i've compiled and run ntp, also used debian ntp using same setup (after hacking out debain file install changes), so let me explain what works for me... a while back around slackware 7 or so i compiled and used ntpdate ntpd, i enjoyed using it a while but ran into two caveats. my isp signal attacked me shut down all my server ports (ie, 80). also ... i had issues with it: (1) used more bandwidth than i needed for my needs was used rdate is great. also i was aware that if a college were to allow malicous students use the timekeeping device, it could be used to "hack into my server" (2) the colleges that support it are often down or never set clock and are advertising the wrong time - exactly what author begged people not to do (3) still waiting for my expensive radio clock to arrive ! FILE: /etc/ntpdrift 51.728 FILE: /etc/ntp.conf server ntp.college.com server ntp.some.ipaddress driftfile /etc/host/ntp.drift statsdir /var/log/ntpstats/ statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable ## you can use script to decide which servers in your ip list are up which are responding fastest, use the top 3 in the file, as per directions dont list them all list only nearby ones ## note, use ntpdate first to get close or ntpd may not work # ntpdate $(cat /etc/ntp.conf | sed -n -e '/^server/{s/^server //;p;}') # ntpd -c /etc/ntp.conf -f /etc/host/ntp.drift ## try ntpq but remember the docs said not to do certain things as ## they are a nuisance to real timekeeping devices
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56CFC751.7030806>