On Mon, 18 Jul 2016 16:25:34 -0500 james wrote: > On 07/18/2016 03:03 PM, Marc Schiffbauer wrote: > > * Rafael Goncalves Martins schrieb am 18.07.16 um 03:12 Uhr: > >> On Sat, Jul 16, 2016 at 11:33 AM, Andrew Savchenko <[email protected]> > >> wrote: > >>> Set it for a minute or two. This will protect from commits from > >>> really out-of-sync systems (like 14 days mentioned above) and will > >>> keep usablity hight for others. > >> > >> I second this "request" :) > >> > >> remote: Your system clock is off by 6 seconds (limit 5) > > > > Why not fix your system clock? No ntpd running? > > > > Check 'ntpq -pn' > > > > -Marc > > > > net-misc/openntpd is simple and might do the job well enough, or is > net-misc/ntp a hard requirement ? > > I just use the default (gentoo) time servers, for now, but perhaps > using specified servers in different regions might work too?
Any ntp sync daemon will be fine. I prefer net-misc/chrony: it is simpler and more secure than ntpd (e.g. look at CVE counts) and handles well situations when upstream servers go offline (e.g. continues to apply calculated drift to rtc clock). Though it doesn't support all features of ntpd (e.g. ssl), it has all subset of them sufficient IRL. Best regards, Andrew Savchenko
pgpmupo_hke3F.pgp
Description: PGP signature
