On Tue, 2018-02-13 at 01:40 +0700, Eugene Grosbein wrote: > 13.02.2018 1:30, Ian Lepore wrote: > > > > > > > > > > > > > > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND > > > > 911 root 1 22 0 8816K 8844K select 0:39 4.20% ntpd > > > Your Soekris system can live without bloated ntpd, use ntpdate or try sntp > > > to periodically check your clock with cron, unless you need to > > > re-distribute > > > NTP to your LAN. > > > > > Heh. I think 1) you don't realize you're saying "you don't need ntpd" > > to, and 2) you didn't notice the hostname of the system in some of the > > debugging output (ntp1.us.grundclock.com). :) > You are partialy right :-) I skipped hostname. > > Btw, is Soektris system has good enough hardware clock and/or > enough horsepower to provide quality public NTP service? > Also thinking of lots of garbage traffic these days UDP/123 suffers from...
Should be plenty of horsepower. For years I ran a pool.ntp.org server using a 60mhz armv4 system with 64MB ram. You don't need anything special in the way of a clock to run a public ntp server at stratum 2 or lower and achieve millisecond accuracy (or sub-millisecond at stratum 1, with a PPS input). I've never seen a system whose kernel timekeeping was so bad that ntpd couldn't steer the clock and provide accurate time. -- Ian _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
