[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Importance of clock synchronization?

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-01-05 00:22:41 CET

On 1/4/07, Andy Levy <andy.levy@gmail.com> wrote:
> On 1/4/07, Erik Huelsmann <ehuels@gmail.com> wrote:
> > On 1/4/07, Andy Levy <andy.levy@gmail.com> wrote:
> > > For reasons I don't fully understand, the system clock on our VMWare
> > > ESX server, which will soon host a virtual machine in which we'll run
> > > our new Subversion server, is not synced with the rest of the world -
> > > it's about 9 minutes behind. As a result, any virtual machine running
> > > on this host is also behind.
> >
> > Only if syncing it later means a jump back in time, because then you
> > may get non-continuously-increasing commit times which is technically
> > no problem, but will break -r {date} revision specification.
> >
> > But, since your clock is behind, this is not a problem.
> Great news, thanks.
> One followup though. If the clock was ahead by 10 minutes instead of
> behind, couldn't I just disallow commits (shut down Apache, the whole
> box, or just ask people to stay out) for 15 minutes and then resume as
> normal?

That would totally solve the issue I raised, yes.

> More a curiosity than anything else, since we seem to be in the better
> of the 2 out-of-sync situations by being behind.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 5 00:23:04 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.