From: james <garftd@verizon.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Signed push & clock drift rejection
Date: Mon, 18 Jul 2016 16:25:34 -0500 [thread overview]
Message-ID: <7c540560-d38a-4326-da1b-0a0f73671367@verizon.net> (raw)
In-Reply-To: <20160718200335.ukkvr5l42uzqv2hr@schiffbauer.net>
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 <bircoph@gentoo.org> 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?
hth,
James
next prev parent reply other threads:[~2016-07-18 20:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 18:03 [gentoo-dev] Signed push & clock drift rejection Robin H. Johnson
2016-07-16 9:33 ` Andrew Savchenko
2016-07-18 1:12 ` Rafael Goncalves Martins
2016-07-18 20:03 ` Marc Schiffbauer
2016-07-18 20:27 ` Andrew Savchenko
2016-07-19 2:21 ` waltdnes
2016-07-19 2:37 ` Kent Fredric
2016-07-19 8:07 ` Chí-Thanh Christopher Nguyễn
2016-07-19 11:29 ` waltdnes
2016-07-19 15:42 ` Chí-Thanh Christopher Nguyễn
2016-07-19 18:23 ` Andrew Savchenko
2016-07-19 19:28 ` R0b0t1
2016-07-19 20:22 ` Patrick McLean
2016-07-19 20:28 ` Patrick McLean
2016-07-19 20:34 ` Alec Warner
2016-07-18 21:25 ` james [this message]
2016-07-18 23:06 ` Mart Raudsepp
2016-07-18 23:34 ` Bill Kenworthy
2016-07-19 8:09 ` Andrew Savchenko
2016-07-19 15:46 ` Michał Górny
2016-07-18 20:35 ` Ulrich Mueller
2016-07-18 21:20 ` Rich Freeman
2016-07-19 17:20 ` Andrew Savchenko
2016-07-19 11:31 ` Consus
2016-07-19 20:22 ` Alec Warner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c540560-d38a-4326-da1b-0a0f73671367@verizon.net \
--to=garftd@verizon.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox