Date: Thu, 7 Feb 2013 08:08:27 -0700 From: Warner Losh <imp@bsdimp.com> To: Tim Kientzle <tim@kientzle.com> Cc: freebsd-arm@freebsd.org, Ian Lepore <ian@freebsd.org> Subject: Re: SD card -image- for the beaglebone Message-ID: <AAB676CD-FE50-41EA-9AEE-E282035D2E6E@bsdimp.com> In-Reply-To: <933D29A2-B78E-44D5-A701-7397CD532CD1@kientzle.com> References: <510A4F5B.7000407@g7iii.net> <1359646574.93359.327.camel@revolution.hippie.lan> <510AE1D6.8010203@g7iii.net> <1360124308.93359.557.camel@revolution.hippie.lan> <5112115D.5040709@g7iii.net> <1360158409.93359.590.camel@revolution.hippie.lan> <52928DD2-AA41-4B3C-A22A-1F755832D220@bsdimp.com> <1360177280.93359.611.camel@revolution.hippie.lan> <933D29A2-B78E-44D5-A701-7397CD532CD1@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 6, 2013, at 7:12 PM, Tim Kientzle wrote: >>=20 >> Well, besides running a little roll-your-own clock ensemble system, a >> more mundane use of multiple PPS inputs would be simple failover for >> ntpd. At least, I think in theory it should work fine to configure = ntpd >> with multiple refclocks and if one goes bad it can continue with = others. >=20 > Hmmm=85 I think I would instead have multiple > BeagleBones, each with a single PPS input and > each acting as an independent NTP master. >=20 > If one goes bad, the NTP clients will fail over > to use another master. That matches what I've had the best experience with ntpd...=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AAB676CD-FE50-41EA-9AEE-E282035D2E6E>