| 1 |
On Tue, Jul 19, 2016 at 10:07:12AM +0200, Chí-Thanh Christopher Nguy???n wrote |
| 2 |
> Kent Fredric schrieb: |
| 3 |
> > On Mon, 18 Jul 2016 22:21:22 -0400 |
| 4 |
> > waltdnes@××××××××.org wrote: |
| 5 |
> > |
| 6 |
> >> I'm amazed that "robust linux servers" are deathly afraid of simply |
| 7 |
> >> setting the time, and being done with it. |
| 8 |
> > |
| 9 |
> > There's problems at the software level everywhere that are not so |
| 10 |
> > simply solved. |
| 11 |
> > |
| 12 |
> > A more obvious example is in the event your system time gets *ahead* of |
| 13 |
> > real-time. |
| 14 |
> |
| 15 |
> And even if the system is behind time, it can cause problems. cronjobs |
| 16 |
> running unexpectedly close to each other (or missed cronjobs in extreme |
| 17 |
> cases). User sessions expiring early, etc. |
| 18 |
> |
| 19 |
> And even if there is only one second, and that is known well ahead |
| 20 |
> (e.g. leap seconds): Unless you know that there isn't going to be |
| 21 |
> a problem, a great deal of care needs to go into handling that. |
| 22 |
|
| 23 |
In that case, the dev machine should be a separate machine from the |
| 24 |
server. They don't even have to be separate physical machines. Do the |
| 25 |
dev work in a VM, and set the time in the VM just before doing the push. |
| 26 |
|
| 27 |
-- |
| 28 |
Walter Dnes <waltdnes@××××××××.org> |
| 29 |
I don't run "desktop environments"; I run useful applications |
Archives