| 1 |
On Mon, 18 Jul 2016 22:03:35 +0200 Marc Schiffbauer wrote: |
| 2 |
> * Rafael Goncalves Martins schrieb am 18.07.16 um 03:12 Uhr: |
| 3 |
> > On Sat, Jul 16, 2016 at 11:33 AM, Andrew Savchenko <bircoph@g.o> wrote: |
| 4 |
> > > Set it for a minute or two. This will protect from commits from |
| 5 |
> > > really out-of-sync systems (like 14 days mentioned above) and will |
| 6 |
> > > keep usablity hight for others. |
| 7 |
> > |
| 8 |
> > I second this "request" :) |
| 9 |
> > |
| 10 |
> > remote: Your system clock is off by 6 seconds (limit 5) |
| 11 |
> |
| 12 |
> Why not fix your system clock? No ntpd running? |
| 13 |
|
| 14 |
As I wrote earlier in this thread, ntp server is not a guarantee |
| 15 |
that such problems will not happen. If hardware clocked was |
| 16 |
significantly offset during boot, it may take several _hours_ for |
| 17 |
ntp to fix this via clock skew. Apparantly commit may be made |
| 18 |
during these several hours. |
| 19 |
|
| 20 |
Best regards, |
| 21 |
Andrew Savchenko |
Archives