From owner-freebsd-stable@freebsd.org Mon Feb 12 18:47:48 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 585C3F11576 for ; Mon, 12 Feb 2018 18:47:48 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D9C1D850CE for ; Mon, 12 Feb 2018 18:47:47 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 2c6e8826-1025-11e8-bb8e-b35b57339d60 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 2c6e8826-1025-11e8-bb8e-b35b57339d60; Mon, 12 Feb 2018 18:47:28 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w1CIleno035276; Mon, 12 Feb 2018 11:47:40 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1518461260.94819.36.camel@freebsd.org> Subject: Re: FreeBSD on 64MB memory From: Ian Lepore To: Eugene Grosbein , Ask =?ISO-8859-1?Q?Bj=F8rn?= Hansen Cc: freebsd-stable@freebsd.org Date: Mon, 12 Feb 2018 11:47:40 -0700 In-Reply-To: <5A81DF8F.7070000@grosbein.net> References: <5FB97479-C49D-4C6E-8416-015ECA656C14@develooper.com> <5A8123CE.9050609@grosbein.net> <5A81D72A.7020408@grosbein.net> <1518460232.94819.25.camel@freebsd.org> <5A81DF8F.7070000@grosbein.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 18:47:48 -0000 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