| 1 |
>>>>> On Mon, 18 Jul 2016, Rafael Goncalves Martins wrote: |
| 2 |
|
| 3 |
> On Sat, Jul 16, 2016 at 11:33 AM, Andrew Savchenko <bircoph@g.o> wrote: |
| 4 |
>> Why such tight requirement? Why not a minute, which will not hurt |
| 5 |
>> git, but will help with system _temporarily_ out-of-sync. |
| 6 |
>> |
| 7 |
>> Some hardware clocks are real mess and can drift more that for 5 |
| 8 |
>> seconds in a few days (e.g. when system was shut down). And for NTP |
| 9 |
>> it will take time to correct system clock _properly_. While stuff |
| 10 |
>> like running ntpdate before ntp server if system is out of sync is |
| 11 |
>> possible, but it is not recommended nor possible on some workloads. |
| 12 |
>> So IRL NTP may take several hours to sync system properly. |
| 13 |
>> |
| 14 |
>> Set it for a minute or two. This will protect from commits from |
| 15 |
>> really out-of-sync systems (like 14 days mentioned above) and will |
| 16 |
>> keep usablity hight for others. |
| 17 |
|
| 18 |
> I second this "request" :) |
| 19 |
|
| 20 |
> remote: Your system clock is off by 6 seconds (limit 5) |
| 21 |
|
| 22 |
+1 |
| 23 |
|
| 24 |
Same here, push was rejected because of 8 seconds clock offset. |
| 25 |
This happened shortly after resuming from suspend, so apparently ntpd |
| 26 |
had not caught up yet. |
| 27 |
|
| 28 |
Ulrich |
Archives