Gentoo Archives: gentoo-dev

From: "Chí-Thanh Christopher Nguyễn" <chithanh@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Signed push & clock drift rejection
Date: Tue, 19 Jul 2016 15:42:52
Message-Id: 578E4A5A.5070800@gentoo.org
In Reply to: Re: [gentoo-dev] Signed push & clock drift rejection by waltdnes@waltdnes.org
1 waltdnes@××××××××.org schrieb:
2 >> And even if the system is behind time, it can cause problems. cronjobs
3 >> running unexpectedly close to each other (or missed cronjobs in extreme
4 >> cases). User sessions expiring early, etc.
5 >>
6 >> And even if there is only one second, and that is known well ahead
7 >> (e.g. leap seconds): Unless you know that there isn't going to be
8 >> a problem, a great deal of care needs to go into handling that.
9 > In that case, the dev machine should be a separate machine from the
10 > server. They don't even have to be separate physical machines. Do the
11 > dev work in a VM, and set the time in the VM just before doing the push.
12
13 I am not talking about bircoph's dev machine, I am explaining why ntpd
14 works the way it does. Which usually doesn't lead to problems as the
15 drift will be corrected sooner or later. So there was never a problem
16 nor reason for action in either case, until it was decided that 5
17 seconds is the maximum drift for a push to gentoo.git.
18
19
20 Best regards,
21 Chí-Thanh Christopher Nguyễn