1 |
Ühel kenal päeval, E, 18.07.2016 kell 16:25, kirjutas james: |
2 |
> On 07/18/2016 03:03 PM, Marc Schiffbauer wrote: |
3 |
> > * Rafael Goncalves Martins schrieb am 18.07.16 um 03:12 Uhr: |
4 |
> > > On Sat, Jul 16, 2016 at 11:33 AM, Andrew Savchenko <bircoph@gento |
5 |
> > > o.org> wrote: |
6 |
> > > > Set it for a minute or two. This will protect from commits from |
7 |
> > > > really out-of-sync systems (like 14 days mentioned above) and |
8 |
> > > > will |
9 |
> > > > keep usablity hight for others. |
10 |
> > > |
11 |
> > > I second this "request" :) |
12 |
> > > |
13 |
> > > remote: Your system clock is off by 6 seconds (limit 5) |
14 |
> > |
15 |
> > Why not fix your system clock? No ntpd running? |
16 |
> > |
17 |
> > Check 'ntpq -pn' |
18 |
> > |
19 |
> > -Marc |
20 |
> > |
21 |
> |
22 |
> net-misc/openntpd is simple and might do the job well enough, or is |
23 |
> net-misc/ntp a hard requirement ? |
24 |
> |
25 |
|
26 |
or just |
27 |
|
28 |
systemctl enable systemd-timesyncd.service |
29 |
systemctl start systemd-timesyncd.service |
30 |
|
31 |
if you are fortunate enough to run systemd. |
32 |
If not, well, some other ntp client indeed, no need to debate fortunes |
33 |
further :) |
34 |
|
35 |
If there's no RTC clock ticking and syncing during/after suspend, |
36 |
something seems off in my experience. Disabled ACPI? :D |
37 |
|
38 |
I didn't find any indications of why this is actually a problem in the |
39 |
announcement or replies, and I couldn't read the backlog for the |
40 |
explanation that I saw might have skimmed through. I think if we want |
41 |
to nitpick what the actual drift allowed is, we need to know the |
42 |
reasons this restriction is needed and what could be the difference to |
43 |
that unspecified potential rsync issue between a seconds of drifts and |
44 |
a couple minutes or an hour or so of drift. |
45 |
I'm sure infra will adjust if possible and choose what's best :) |
46 |
|
47 |
|
48 |
Mart |